Autoboot
Custom bootloader for all G2 variants
I hold absolutely no responsibility if your device becomes inoperable, outoperable, or if by-name/aboot becomes self aware
AOSP...
AOSP compatibility with Autoboot is hit or miss! All of the variants differ, and some combinations simply won't work. If you find a kernel/rom/variant combination that works, share it!
Stock ROMs have been tested thoroughly, there shouldn't be any issues using Autoboot with stockroms unless otherwise stated.
Click to expand...
Click to collapse
What is it..?
Autoboot is a custom bootloader that comes with many features not allowed by the stock LG bootloader, such as fastboot access and dual booting support. Autoboot does not replace your stock bootloader, it runs alongside at boot, and does not interfere with the bootloader structure that already exists on your phone. It can be installed over any ROM and can be uninstalled any time!
Click to expand...
Click to collapse
Why should I care..?
LG's bootloader completely removes support for fastboot unless the user corrupts their boot, recovery or laf partitions. AutoBoot allows the user to enter fastboot mode any time they want, just like a Nexus device!
Autoboot supports dual booting, (however it's up to the devs to hammer that one out, I'm maintaining this project along with 3 other kernels!) By default, you can dual boot kernels almost effortlessly!
[dev] Autoboot supports AnyKernel zip installation, by having the ability to load any boot.img that isn't loki'd! Kernel devs will have to utilize the new use of 'spare' and 'grow' partitions and mention specifically in their OP's that Autoboot must be installed to use!
Click to expand...
Click to collapse
How do I use it..?
From the device being powered off, after you release the power key to boot the device, you can immediately hold one of the 2 keys to enter different modes.
Volume Up: Fastboot, your device will show a persistent "LG" Logo in fastboot mode, it will look like a frozen boot, but you can connect it to a PC and start fastbooting whatever you want!
Volume Down: Dual Boot, this boots the secondary device which can hold a second kernel. By default, this is empty!
Nothing: Simply boots your primary device, which is typically whatever kernel you had installed before you installed Autoboot
Click to expand...
Click to collapse
Install/Uninstalling
Installing is as easy as flashing a zip, that's it! Add it to the end of your zip-queue after you install a new ROM, or flash it after installing a new kernel to utilize it.
"What if I want to install a new ROM?! D:"
Well I just answered that but incase you didn't understand, flash it as you always would. There won't be any issues. Just make sure to flash Autoboot again if you still want to utilize it!
You should never install Autoboot twice in a row! Use the uninstaller zip before flashing an update to Autoboot.
If you do happen to install Autoboot twice in a row, do NOT use autoboot_uninstall.zip, you should flash a new kernel or use "fastboot flash spare boot.img" to get back in action, fastboot mode will still work if you flash it twice, though you may not be able to boot a ROM until you remedy.
Click to expand...
Click to collapse
Uninstalling is as easy as flashing a new ROM or kernel and it's out of your life, if you don't want a new ROM or kernel, I've included an autoboot_uninstall.zip you can flash in recovery to restore your previous boot configuration and uninstall Autoboot.
Click to expand...
Click to collapse
Is it safe..?
Totally! Tested again and again! Make sure you totally understand it before doing something you're unsure about! Autoboot does not effect recovery, download mode, or the original bootloader process in any way, shape or form. Worst case scenario is your device hangs on boot, if that miraculously ever happens, hop back into recovery and use the autoboot_uninstall.zip, it returns you to the exact state you were in before you installed it!
Click to expand...
Click to collapse
How does it work..?
By default, the LG bootloader can load "patched" or loki'd boot.img's, Autoboot is a build of LK (The same bootloader source LG uses) that hides inside of a loki'd boot.img, once LG's bootloader see's the loki'd bootloader, it passes the signature check and proceeds to boot. Usually at this point, a kernel would boot and your ROM would load up, but in this case, Autoboot starts.
Autoboot acts as our own bootloader, we can manipulate it to do anything we can't do with the stock bootloader. It uses two extra partitions that the G2 has to hold and boot unloki'd boot.img's. These partitions are 'spare' (primary) and 'grow' (secondary).
On install, Autoboot will take the current .img file in the boot partition, unloki it, and move it into the spare partition. Autoboot well then loki and place itself in the boot partition.
On uninstall, the spare partition is pulled, loki'd and placed over the boot partition, wiping autoboot. The spare partition is also wiped. (grow is not incase of using autoboot_uninstall.zip to upgrade versions of Autoboot)
You can flash new, unloki'd or clean boot.img's to the grow and spare partitions using dd, or easier fastboot commands.
Code:
fastboot flash spare boot.img
fastboot flash grow boot.img
Note: The 'grow' partition is roughly 12MB and the 'spare' partition is roughly 16MB, developers making kernels/ROMs may need to use a compression method such as LZMA for a smaller kernel to fit the 'grow' partition.
Click to expand...
Click to collapse
LS980ZVC...
Currently, the install method for ZVC is to take the entire bootstack, this isn't a very good idea as it breaks support for Download Mode when the aboot is downgraded to ZV7/8 (same thing)
To use ZVC and maintain your custom recovery, you need to flash this ZV7/8 compatible kernel and follow it up with an installation of Autoboot. Remember that if you're on the ZVC bootstack, you won't be able to use download mode unless you downgrade your laf partition to ZVA!
You can use this method to get to ZVC, or you can get a hold of the ZVC system.img and fastboot flash that and the boot.img (from above) to get booting with a custom recovery!
autoprime has an in-depth walkthrough of his steps to keep custom recovery and download mode on ZVC available here.
Autoboot currently does not work AOSP-LS980 ROMs using Furnace Kernel or PAEK, it's a kernel side issue I will be looking into, use dr87's kernel or stock at the moment!
Click to expand...
Click to collapse
Questions or concerns..?
Hop in freenode at #lg-g2, I'm on all the time and I can help you with anything you need! Therapy starts at $1 a minute.
Click to expand...
Click to collapse
Credits
Absolutely none of this would be possible without the LK work by detule, if there's anyone you need to donate to, it's him.
@autoprime
@djrbliss
@Shelnutt2
@garwynn
@dr87
@xdabbeb
@Cloudyfa
@JackpotClavin
Click to expand...
Click to collapse
Downloads
All downloads are available here!
http://downloads.codefi.re/savoca/autoboot
source
Click to expand...
Click to collapse
Savoca said:
Autoboot
Custom bootloader for all G2 variants
Click to expand...
Click to collapse
Great job, buddy
Good project, helped Savoca do some testing on this so I can confirm it works on my D801 :good:
Awesome! Great work, dude. I also tested and can confirm it works perfectly
Crazy project Good Job :good:
Good job mate
Sent from my LG-D802 using xda app-developers app
@Savoca killin it for the G2
excellent work again :beer:
I'll put this here too. Verizon source for Kit Kat kernel https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=VS980
Sent from my VS980 4G using Tapatalk
Good job. ...Thanks to all u devs....I'm still scratching my head on what the h3ll Autoboot really is and does...Lol
Sent from my VS980 4G using Tapatalk
youdug said:
@Savoca killin it for the G2
excellent work again :beer:
Click to expand...
Click to collapse
Killin it for real.
Bad asd work, Savoca!
Wow didn't see this coming. Great work. Devs are really pushing the envelope for us. Thank you!
Sent from my VS980 4G using Tapatalk
i flashed it but it doesnt boot the shows the lg logo and the says fastboot started
and thats when i press nothing? im on the d801
Alpha_wolf said:
i flashed it but it doesnt boot the shows the lg logo and the says fastboot started
and thats when i press nothing? im on the d801
Click to expand...
Click to collapse
Flash uninstaller, link me to your kernel. Looks like it's too big.
Ll this work on the d806?
Enviado desde mi LG-D800 mediante Tapatalk
Great work, savoca!
Does that mean we may be finally able to repartition our devices? Over 2,5 GB of my 16 GB are unusable...
Just commenting about autoboot + LS980 ZVC 4.4.2 KK... this is the ideal setup for someone that's 100% stock on ZVC and wants custom recovery.
Of course all of this isn't needed if you just want root.
I was 100% stock on ZVC... rooted with ioroot25.
1. Downgraded aboot partition through rooted adb shell to use ZV7 aboot.img. this allows you to install twrp and continue to have loki.
2. Install twrp 2.6.3.2.img through rooted adb shell.
3. Downgraded laf partition through rooted adb shell to use ZVA laf.img. downgrading aboot causes download mode not to work properly. downgrading to ZVA laf makes it work again.
4. Powered off then booted into twrp through the "hard reset" screen using the vol up + power button combo.
5. Flashed the twrp 2.7 zip while in recovery. Then reboot > recovery to boot into twrp 2.7.
6. Flashed the savoca's kk ls980 kernel zip.
7. Flashed the ls980 autoboot zip.
Rebooted and everything is working on stock ZVC. I have working download mode, fastboot, twrp and the rom boots(takes a lil longer to boot up but no biggie).
Then I went through the App Settings on the phone to uninstall some of the bloat and disable a lot of stuff I don't use. Install Xposed for G2. All set.
Alpha_wolf said:
i flashed it but it doesnt boot the shows the lg logo and the says fastboot started
and thats when i press nothing? im on the d801
Click to expand...
Click to collapse
I got the same thing. I'm using dr87 v7 kernel on LiquidSmooth
Savoca said:
Flash uninstaller, link me to your kernel. Looks like it's too big.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2572992
furnace 1.8.1
its about 6-7 mb boot.img
what kernels will work??
Let me see if I get this right
Running 802 international.
To install this and a second Rom i have to.
1 nandroid.
2 install this
3 Power off and restart using power then volume-
4 go in to recover
5 flash the second ROM
That's it?
But how do I enter recovery of I flash this
Thank you for your work m8 :good:
Related
As there is now an official version of CWM Recovery I updated this thread now. Thanks to everyone who used my version and helped me. I will keep on what I'm doing and maybe there will be other interesting things I will release.
The official CWM Recovery by Koush can be downloaded here:
Images to flash via fastboot
touch-version: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.7-mako.img
nontouch-version: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.7-mako.img
Flashable zips
touch-version: https://www.mediafire.com/?nx826v1jo0bdqdj
nontouch-version: https://www.mediafire.com/?69kmvtcvgooc0gv
For the fastboot images:
You can try this out and boot it via
Code:
fastboot boot recovery-clockwork(-touch)-6.0.4.7-mako.img
(only Android 4.2.X)
Code:
fastboot -c "lge.kcal=0|0|0|x" boot recovery-clockwork(-touch)-6.0.4.7-mako.img
(Android 4.3 and above)
If you want to flash it you can use
Code:
fastboot flash recovery recovery-clockwork(-touch)-6.0.4.7-mako.img
If you have the touch-version use this commands without '(' and ')' but with its content.
If you have the nontouch-version use this commands without '(' and ')' and its content-
Outdated as all new recoveries already provide this function.
I also want to present you my revert recovery disabler.
As you know if you flash CWM on Nexus 4 it reverts back to the stock recovery. This patch prevents this. This is not needed at the moment for CWM as CWM offers the possibly to disable the revert by itself.
You can download my revert recovery disabler here: http://www.mediafire.com/?78fkhdh5icz3zdg
This disabler is compatible with mskip's toolkit (uses the same methode).
To use it boot in CWM recovery and flash this as a zip.
If you want to restore the default option and make your Nexus 4 reverting back to the stock recovery you can flash the enabler: http://www.mediafire.com/?19enww985e2gpnc
Thanks to:
Stryder5 providing some information
Kstarz for some testing and providing information
mskip for his toolkit and giving me the idea to do this
pankaj88 for his sample update zip
Old thread said:
I just want to release my CWM Touch Recovery for the Nexus 4.
This version also allows to flash zips from internal storage (and hopefully other storage related stuff).
If you want to you can download it here: http://www.mediafire.com/?f9b9av06ui5vcdm (UPDATED 11/16/2012)
Using it is at your own risk!
Please test it first via
Code:
fastboot boot cwm-recovery-mako.img
Flashing is not supported at the moment as secured boot prevents from booting flashed recovery. Please note that you need an unlocked bootloader.
For reverting back to original recovery use this one: http://www.mediafire.com/?57zmq7yw089gcr8 (not needed at the moment as only booted recovery works at the moment)
Thanks to:
Stryder5 for testing and providing some information
Kstarz for testing and providing some information
Also thanks to Koush for creating CWM Recovery and to the other devs for Nexus 4 making it a really good device.
If you have any questions ask below. I will rework this post later the day.
Click to expand...
Click to collapse
To clarify, I can confirm the boot method will allow you to boot the recovery and flash a zip file. I did not attempt to flash this as my recovery yet.
---------- Post added at 12:53 AM ---------- Previous post was at 12:21 AM ----------
I tried to flash the recovery instead of booting from it, but that doesn't work. I ran the command:
Code:
fastboot flash recovery cwm-recovery-mako.img
When I try to boot into recovery after that, it'll show the Google logo twice, then proceed with the regular boot.
I think this is because Secure Boot is still enabled.
Same thing here..recovery will not stick if flashed
Sent from my Nexus 4
good news! https://plus.google.com/u/0/103583939320326217147/posts/CzstapsDpYf
fkrone said:
I just want to release my CWM Touch Recovery for the Nexus 4.
This version also allows to flash zips from internal storage (and hopefully other storage related stuff).
If you want to you can download it here: http://www.mediafire.com/?f9b9av06ui5vcdm (more mirrors will be added soon)
Using it is at your own risk!
Please test it first via
Code:
fastboot boot cwm-recovery-mako.img
Flashing is not supported at the moment as secured boot prevents from booting flashed recovery. Please note that you need an unlocked bootloader.
For reverting back to original recovery use this one: http://www.mediafire.com/?57zmq7yw089gcr8 (not needed at the moment as only booted recovery works at the moment)
Thanks to my tester Stryder5.
Also thanks to Koush for creating CWM Recovery and to the other devs for Nexus 4 making it a really good device.
If you have any questions ask below. I will rework this post later the day.
Click to expand...
Click to collapse
What RAMDISK load address are you using? 0x81200000?
Thanks to the tip by Stryder5, I have updated my rooting guide with instructions for rooting via CWM, linking to this thread for the recovery and providing the due credit. =)
g33k3r said:
What RAMDISK load address are you using? 0x81200000?
Click to expand...
Click to collapse
If I could I would provide you that information but as I only used the CWM's online builder I can't tell you that. If you need some information you can pm me
To all: As there is a new update in the sources I am currently syncing the sources and building an new version. Furthermore I am working on a possibility to make the CWM permanent (and easy to do so even without root; I know already what I have to do).
fkrone said:
If I could I would provide you that information but as I only used the CWM's online builder I can't tell you that. If you need some information you can pm me
To all: As there is a new update in the sources I am currently syncing the sources and building an new version. Furthermore I am working on a possibility to make the CWM permanent (and easy to do so even without root; I know already what I have to do).
Click to expand...
Click to collapse
Looking forward to it!
Sent from my Nexus 4 using xda app-developers app
does anyone actually build cwm these days?
Sweet!! So our Nexus 4 is codenamed "MAKO?"
DaX05 said:
Sweet!! So our Nexus 4 is codenamed "MAKO?"
Click to expand...
Click to collapse
The hardware is calles mako, the software itself has the codename occam. As of my building methode it was automatically called mako
fkrone said:
The hardware is calles mako, the software itself has the codename occam. As of my building methode it was automatically called mako
Click to expand...
Click to collapse
Hey do you mind if I put this recovery in the Toolkit for now until koush has released the official cwm?
Is it touch or non touch? What version is it?
Mark.
mskip said:
Hey do you mind if I put this recovery in the Toolkit for now until koush has released the official cwm?
Is it touch or non touch? What version is it?
Mark.
Click to expand...
Click to collapse
No problem at all. Just give credits and use it. This is a touch recovery.
If koush will release CWM for Nexus 4 it won't be different to this (except he changes some sources).
fkrone said:
No problem at all. Just give credits and use it. This is a touch recovery.
If koush will release CWM for Nexus 4 it won't be different to this (except he changes some sources).
Click to expand...
Click to collapse
Thanks and of course
What version is it? V6.0.1.5?
Mark.
mskip said:
Thanks and of course
What version is it? V6.0.1.5?
Mark.
Click to expand...
Click to collapse
As I built it this afternoon (GMT+1) it is V6.0.1.5 with the latest bugfix which was released today.
Man I can't wait to see some custom ROM's outta here. The phone is sweet and snappy but I've had a few problems that I'm not sure if they're hardware or software related. Quadrant scores are around 4400-4900, the phone rings hot and I'm getting the worst speed test results. Like I get 11-18 MBS on my gs2 and I'm getting like 2-3mbs now. I got two weeks before I can return it so I hope it just needs to stettle. Anyhoo. Good luck guys!
Sent from my Nexus 4 using XDA Premium HD app
Link to the new recovery (6.0.1.6-mako)
But assuming that I flashed it correctly with Rom Manager and fastboot, it isn't working, it didn't matter which way i flashed it.
Arasthel said:
Link to the new recovery (6.0.1.6-mako)
But assuming that I flashed it correctly with Rom Manager and fastboot, it isn't working, it didn't matter which way i flashed it.
Click to expand...
Click to collapse
Flashing does not work at the moment. Only booting via fastboot even with official CWM Recovery.
fkrone said:
Flashing does not work at the moment. Only booting via fastboot even with official CWM Recovery.
Click to expand...
Click to collapse
Sorry, I misunderstood you. I thought this bugfix would allow us to flash the recovery in our devices, then I realized that the bugfix was what let us boot it, as you said a few messages back. Anyway, there you have the official build link.
Can somebody please explain, in simple terms, why we can't flash this permanently yet? What do we need to enable us to flash it permanently?
OUYA Safe Recovery v1.0.0
Because the OUYA lacks a hardware recovery button combination.Purpose
To create a safe environment where the end user can flash their OUYA with confidence.
How This is Achieved
By switching the roles of the boot image and the recovery image, the user is presented with a customized recovery before entering the actual ROM. This gives the user a failsafe before they start to flash their OUYA. This way if something were to go wrong in the flashing process, the recovery image is still in tact and the system can be restored to a working state.
Features
Custom font size that looks better on HDTV's.
Custom color scheme that matches that of the OUYA theming.
Custom reboot options.
Installation Methods
Method 1 - Computer
Simply download the archieve containing a script that will flash your OUYA. Follow the on-screen directions based on the OS your computer is running.
Method 2 - Recovery
This method is a little more dangerous, but if you already have Clockworkmod Recovery installed on your OUYA you can flash the specified zip to install OUYA Safe Recovery.
Downloads
Computer Method: Ouya Safe Recovery Installer v1.0.0.zip - 16.08 MB
Recovery Method: update_v1.0.0.zip - 6.93 MB
Source and GPL
The source for this project is quite simple, but will continue to evolve over time. If you are interested in taking a look at the required source code or compiling your own Safe Recovery binary, you can find the requested material here.
Credits
Credit to koush for maintaining ClockworkMod Recovery which this recovery is built and compiled from, and to mybook4 for the original CWM port to the OUYA.
Donations and Thanks
If you like the work that I am doing and would like to send a donation my way, please feel free to do so, even though it is not required. Every dollar is appreciated, and will go towards future development costs.
Changelog
Will we be able to install Cyanogenmod 10 with this recovery? Or will we need to replace the boot.Img in the zip so it will gflash correctly without having to use fastboot?
Edit: Where are my manners, AWESOME! Thanks for the recovery! I remember you talking about it in the Cyanogenmod Thread and I didn't expect it to be made so fast!
qwasz123 said:
Will we be able to install Cyanogenmod 10 with this recovery? Or will we need to replace the boot.Img in the zip so it will gflash correctly without having to use fastboot?
Edit: Where are my manners, AWESOME! Thanks for the recovery! I remember you talking about it in the Cyanogenmod Thread and I didn't expect it to be made so fast!
Click to expand...
Click to collapse
To install Cyanogenmod 10 you will need to manually flash the boot.img to the recovery partition.
Code:
fastboot flash recovery 20130702-boot.img
Thanks for the nice comment!
ProfessorAnomaly said:
To install Cyanogenmod 10 you will need to manually flash the boot.img to the recovery partition.
Code:
fastboot flash recovery 20130702-boot.img
Thanks for the nice comment!
Click to expand...
Click to collapse
You're welcome!
So I'm guessing all of the roms need to be updated to install to the recovery partition instead of the boot partition?
Hi, you have done A Great Job, i flashed (via CWM) the recovery and Its working, i also flashed boot image (via Fastboot) and its booting.. Everything is working, we are safe Now!!! Finally!!!! Thanks to you!!!
This should be in Xda Portal!!!!
Only one thing remains what should we choose when we are asked to disable recovery flash... ?
Tried the installer from windows and it reset the ouya and booted back into the ouya launcher? Am I doing something wrong? So far im rooted and adb is working as its sending the files to my internal SD Card. Driver is installed correctly on the pc. Im running Windows 7 (x86).
Sent from my A210 using Tapatalk 4
Does this have any passthrough mode? I mean, is there any functionality to make it automatically boot into the rom by default, and only show the recovery screen if you are holding the power button or some key on the usb keyboard?
qwasz123 said:
You're welcome!
So I'm guessing all of the roms need to be updated to install to the recovery partition instead of the boot partition?
Click to expand...
Click to collapse
The updated fstab should allow for the existing ROMs to flash the boot image to the recovery partition granted developers are writing the image the correct way.
suruceanu.nick said:
Hi, you have done A Great Job, i flashed (via CWM) the recovery and Its working, i also flashed boot image (via Fastboot) and its booting.. Everything is working, we are safe Now!!! Finally!!!! Thanks to you!!!
This should be in Xda Portal!!!!
Only one thing remains what should we choose when we are asked to disable recovery flash... ?
Click to expand...
Click to collapse
I've been choosing no, but I doubt it makes much of a difference.
martinbrettphilo said:
Tried the installer from windows and it reset the ouya and booted back into the ouya launcher? Am I doing something wrong? So far im rooted and adb is working as its sending the files to my internal SD Card. Driver is installed correctly on the pc. Im running Windows 7 (x86).
Sent from my A210 using Tapatalk 4
Click to expand...
Click to collapse
It should work. I don't see why it wouldn't if adb is working correctly.
Maybe a bad download is to blame?
gianptune said:
Does this have any passthrough mode? I mean, is there any functionality to make it automatically boot into the rom by default, and only show the recovery screen if you are holding the power button or some key on the usb keyboard?
Click to expand...
Click to collapse
This is what I have planned for the next update. Shouldn't be too long before I get it worked out.
ProfessorAnomaly said:
It should work. I don't see why it wouldn't. Maybe try rebooting?
Click to expand...
Click to collapse
I did and nothing also the batch file is reporting unknown id for some of the commands. :S
Sent from my A210 using Tapatalk 4
ProfessorAnomaly said:
This is what I have planned for the next update. Shouldn't be too long before I get it worked out.
Click to expand...
Click to collapse
I believe that for koush bootstrap recovery what it does is puts a certain file /system/etc on successful shut down and when it restarts the recovery checks first if the file is there and it moves into normal boot and after that it destroys the file to be rebuilt on successful shutdown.
But if the file is not found it goes into recovery mode
martinbrettphilo said:
I did and nothing also the batch file is reporting unknown id for some of the commands. :S
Sent from my A210 using Tapatalk 4
Click to expand...
Click to collapse
Could you please screenshot the errors you are seeing?
I installed this but I'm confused on how to get into recovery. When trying to boot into recovery, it boots into a screen with a Ouya logo and an exclamation mark right under it (Ouya !")
martinbrettphilo said:
I did and nothing also the batch file is reporting unknown id for some of the commands. :S
Sent from my A210 using Tapatalk 4
Click to expand...
Click to collapse
Sam3gX said:
I installed this but I'm confused on how to get into recovery. When trying to boot into recovery, it boots into a screen with a Ouya logo and an exclamation mark right under it (Ouya !")
Click to expand...
Click to collapse
The installation was not successful. Please try again.
Hello All,
NOTE: You should unlock your bootloader.
These are patched TWRP recovery images for the Apollo and Thor devices only. Now Built from the latest .4.5.3 sources.
WARNING:
- Be sure to have a working /system partition before proceeding with installation.
Installation
- Ensure you are running stock firmware .3.2.3.2
- Obtain Root
- Copy the recovery image to the root of your sdcard
- Flash the recovery image by issuing the following commands:
Code:
adb shell
su
dd if=/sdcard/signed-<device>-twrp-2870.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Download
- Apollo Recovery Image
- Thor Recovery Image
Thanks
- @vortox for the exploit
I see that everyone (well, almost) is using his exploit now. Is there a tool and/or link that I missed?
r3pwn said:
I see that everyone (well, almost) is using his exploit now. Is there a tool and/or link that I missed?
Click to expand...
Click to collapse
I gave @Cpasjuste and @ggow an earlier access to my tool, because I could't write my guide as fast as thought.
vortox said:
I gave @Cpasjuste and @ggow an earlier access to my tool, because I could't write my guide as fast as thought.
Click to expand...
Click to collapse
Ah.
I wrote the recovery on my apollo device which is running 14.3.2.3.2_user_323001720 version and it appears to work flawlessly. I booted into recovery (TWRP) successfully and rebooted the system successfully as well. Awesome!
Thanks for the feedback, glad it's all working
I haven't got a device at the moment to try it out on.
Sent from my Kindle Fire HDX using Tapatalk
Thanks ggow. Could we expect CM roms soon from your new release?
Working on 14.3.1.0
I just want to confirm, on 14.3.1.0_user_310078820 everything so far is working correctly, I can enter into TWRP, reboot system aswell, successfully tested backup and restore (from Safestrap created backups)
Thanks.
tuanda82 said:
Thanks ggow. Could we expect CM roms soon from your new release?
Click to expand...
Click to collapse
Hello tuanda82,
It depends on Amazon, my unlocked Apollo stopped working so they sent me a new one but came pre-installed with 4.5.2.
They have refused to downgrade me back to the old firmware. And after a lot of to and fro they agreed to replace it again .
I hope I have luck with the new device been on the required firmware.
But yes I definitely would like to make such a release.
dangerous
jeryll said:
I just want to confirm, on 14.3.1.0_user_310078820 everything so far is working correctly, I can enter into TWRP, reboot system aswell, successfully tested backup and restore (from Safestrap created backups)
Thanks.
Click to expand...
Click to collapse
I would not be trying interchang eROMs and or backups ppluntil certain things are verified by our developersgosh it only takes a few minutes to understand that one is built for locked bootloader the other one bypasses and they both flash completely different partitions and have different installation scripts.you're just asking to be one of the ignorant whiners on the sidelines while we have fun ..stuck with your brick. be patient guys this is all new stuff if you can't afford to be a developer then I devise you let somebody else take the risk
Can you tell me where TWRP Recovery is stored and what the boot process is like? Is TWRP called by the boot loader instead of the Linux kernel and it will in turn then start the Linux kernel from your installed system?
What happens when TWRP Recovery is damaged? Is there still a way to recover?
And is there a difference in how TWRP is started as opposed to Safestrap?
Edit: ok, so I see that TWRP Recovery is flashed to the recovery partition, so I guess it's separate from the boot image. And pressing volume up + the power button presumably activates the recovery image rather than the boot image. Did Safestrap work in the fashion I described? Why are we using TWRP for recovery now instead of Safestrap? Are there any advantages?
tbm13 said:
Can you tell me where TWRP Recovery is stored and what the boot process is like? Is TWRP called by the boot loader instead of the Linux kernel and it will in turn then start the Linux kernel from your installed system?
What happens when TWRP Recovery is damaged? Is there still a way to recover?
And is there a difference in how TWRP is started as opposed to Safestrap?
Edit: ok, so I see that TWRP Recovery is flashed to the recovery partition, so I guess it's separate from the boot image. And pressing volume up + the power button presumably activates the recovery image rather than the boot image. Did Safestrap work in the fashion I described? Why are we using TWRP for recovery now instead of Safestrap? Are there any advantages?
Click to expand...
Click to collapse
New recovery system
- Allows for custom kernels (meaning, CyanogenMod, Overclocking, and other things)
- Installed to "recovery" partition
- Bypasses signature verification check with some weird thing about exponents of 3 and the cubed root of something. I don't entirely understand how the exploit works.
- Called from the bootloader
- If you're in a bootloop, hold VOL+ & POWER (I think) to boot into TWRP.
SafeStrap
- No custom kernels (no CM)
- Installed to "system" partition (no key presses can get you to here if you're in a bootloop)
- Designed to provide semi-custom ROMs on devices with locked bootloaders
- Called from the Kernel
r3pwn said:
New recovery system
- Allows for custom kernels (meaning, CyanogenMod, Overclocking, and other things)
- Installed to "recovery" partition
- Bypasses signature verification check with some weird thing about exponents of 3 and the cubed root of something. I don't entirely understand how the exploit works.
- Called from the bootloader
- If you're in a bootloop, hold VOL+ & POWER (I think) to boot into TWRP.
SafeStrap
- No custom kernels (no CM)
- Installed to "system" partition (no key presses can get you to here if you're in a bootloop)
- Designed to provide semi-custom ROMs on devices with locked bootloaders
- Called from the Kernel
Click to expand...
Click to collapse
Do you have to be in the stock rom slot to install? Or can you be on a custom rom slot and install?
Håvi said:
Do you have to be in the stock rom slot to install? Or can you be on a custom rom slot and install?
Click to expand...
Click to collapse
Flash the rollback image to stock slot. This will then enable you to get back to 3.1.0
ggow said:
Flash the rollback image to stock slot. You need to be on stock version < 3.2.4.[/QUOT
Edit, found answer in OP
Click to expand...
Click to collapse
I was able to roll back to 3.1.0 and installed twrp. I was able to make a backup and successfully restored the backup. However after about an hour I came back to my kindle an noticed it updated itself to 4.1.1. I was under the impression with recovery installed any new updates would . Not be able to install. Now when I try to boot into recovery it on l y boots kindle recovery not twrp.
Sent from my KFAPWI using Tapatalk
tuanda82 said:
Thanks ggow. Could we expect CM roms soon from your new release?
Click to expand...
Click to collapse
The main problem for cm on appolo seems to be the kernel/bootloader. To run CM kernel (or amazon > 3.2.4) we need (or at least its the only way I found) to modifiy the boot image to manually happen the DT information's to the kernel zImage. Unfortunately this was tested with @ggow and it's not working on appolo. If someone if willing to send me an appolo device I could work on that ...
Cpasjuste said:
The main problem for cm on appolo seems to be the kernel/bootloader. To run CM kernel (or amazon > 3.2.4) we need (or at least its the only way I found) to modifiy the boot image to manually happen the DT information's to the kernel zImage. Unfortunately this was tested with @ggow and it's not working on appolo. If someone if willing to send me an appolo device I could work on that ...
Click to expand...
Click to collapse
Man, I wish I had more time for XDA. First time I've checked in in months. At any rate, it is awesome to see y'all learning & sticking with it! Since I haven't had much time for anything that isn't work related lately, I passed my rooted 3.2.6 Apollo to my Mom. I don't know if she uses it much, but I'll ask her & unless she did a complete 180 & is now becoming a tablet-phile, I could probably send you mine. I will ask her if I can have it back tonight & let you know.
Cpasjuste said:
The main problem for cm on appolo seems to be the kernel/bootloader. To run CM kernel (or amazon > 3.2.4) we need (or at least its the only way I found) to modifiy the boot image to manually happen the DT information's to the kernel zImage. Unfortunately this was tested with @ggow and it's not working on appolo. If someone if willing to send me an appolo device I could work on that ...
Click to expand...
Click to collapse
Amazon are sending me a new Apollo device (again)... hopefully I'll be back in business soon. I think there was something wrong with my device which is why I was having so many problems.
When I get the new device, hopefully it will be on the required firmware for me to try out the new kernel and CM. I'll report back when I have something... Shouldn't take me too long to get something up and running once I have a working device.
GSLEON3 said:
Man, I wish I had more time for XDA. First time I've checked in in months. At any rate, it is awesome to see y'all learning & sticking with it! Since I haven't had much time for anything that isn't work related lately, I passed my rooted 3.2.6 Apollo to my Mom. I don't know if she uses it much, but I'll ask her & unless she did a complete 180 & is now becoming a tablet-phile, I could probably send you mine. I will ask her if I can have it back tonight & let you know.
Click to expand...
Click to collapse
Thanks gsleon but don't rob your mom
---------- Post added at 10:57 AM ---------- Previous post was at 10:53 AM ----------
ggow said:
Amazon are sending me a new Apollo device (again)... hopefully I'll be back in business soon. I think there was something wrong with my device which is why I was having so many problems.
When I get the new device, hopefully it will be on the required firmware for me to try out the new kernel and CM. I'll report back when I have something... Shouldn't take me too long to get something up and running once I have a working device.
Click to expand...
Click to collapse
Crossing fingers
Thanks goes to @nilezon for giving me the rundown, as it is all from his repos, save for a couple of things to make it work for the Z5 instead.
(Yes, your bootloader has to be unlocked)
Kernel is based on firmware version 32.0.A.6.152
There is two versions of the kernel: one with a recovery script, and one without.
The one with the recovery script will allow you to boot into recovery during your phone's startup process.
To enter recovery:
Boot up your phone like normal. Wait for the LED status light to turn amber. Once that happens, start pressing the volume buttons a few times. This will take you into the recovery menu.
The one without the recovery script does not have this option. This means that your phone will boot up a few seconds faster than the one with it.
Xposed: The Camera 2.0.apk plays nicely with Xposed now. No need to deoxed it manually!
Anyways:
TWRP
https://goo.gl/k9PiFV - TWRP 2.8.7.0
KERNELS
https://goo.gl/wzUAv4 - With recovery script, flashable zip file
https://goo.gl/8LTc9l - No recovery script, .img file that must be flashed through fastboot
For the recovery:
Code:
fastboot boot recovery.img
to just boot into it to flash a zip
OR
Code:
fastboot flash recovery.img
to flash it (although, you will need to do fastboot boot recovery the first time to get into it)
Kernel:
Code:
fastboot flash boot z5_stock_fixed_fixed.img
- For the .img file
The blues are oranges instead, like his, but it is kinda cute.
Have fun.
For unlocked bootloaders?
Sent from my Sony Xperia Z5
Snaqejack said:
For unlocked bootloaders?
Sent from my Sony Xperia Z5
Click to expand...
Click to collapse
Yes.
Technically you can flash the boot.img in the recovery ?
bazhip said:
This isn't flashable, only bootable:
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
It's fairly easy to make it bootable.
Modify your boot.img ramdisk using this code and instructions:
https://github.com/jackfagner/twrp-sony-recovery-boot-script
Then just flash the recovery with fastboot.
nilezon said:
It's fairly easy to make it bootable.
Modify your boot.img ramdisk using this code and instructions:
https://github.com/jackfagner/twrp-sony-recovery-boot-script
Then just flash the recovery with fastboot.
Click to expand...
Click to collapse
I saw that at the bottom of your post right afterwards I'll modify it in a bit here, but I wanted to make sure it was going first. Thanks for making that script!
Thanks, bazhip.
Can you provide the modified source and a quick run through on how to compile it on github?
yannik~ said:
Thanks, bazhip.
Can you provide the modified source and a quick run through on how to compile it on github?
Click to expand...
Click to collapse
The kernel or TWRP? I'm kinda busy though so I'm not sure when I'll get around to it. If you want, look at the dirty ROOT thread for nizelion and my posts. I was pretty vocal about the process and what I was doing, as it was my first time ever doing it. You should be able to follow it, I think.
Were the only changes you made disabling SONY_SECURITY_RIC and DM_VERITY in the defconfig?
zwliew said:
Were the only changes you made disabling SONY_SECURITY_RIC and DM_VERITY in the defconfig?
Click to expand...
Click to collapse
That, and ro.secure disabled and ro.debuggable enabled. As close to stock as possible.
bazhip said:
Thanks goes to @nilezon for giving me the rundown, as it is all from his repos, save for a couple of things to make it work for the Z5 instead.
(Yes, your bootloader has to be unlocked)
Anyways:
https://goo.gl/k9PiFV - TWRP 2.8.7.0
https://goo.gl/8LTc9l - Kernel that I compiled that allows root
This isn't flashable, only bootable:
Code:
fastboot boot recovery.img
Kernel:
Code:
fastboot flash boot z5_stock_fixed_fixed.img
The blues are oranges instead, like his, but it is kinda cute.
Have fun.
Click to expand...
Click to collapse
Can it be use on E6683
Build no - 32.0.A.6.152
winkhant said:
Can it be use on E6683
Build no - 32.0.A.6.152
Click to expand...
Click to collapse
It's built for the 6653, but I think it should work for the 6683. Give it a shot. If it doesn't, just flash back the stock kernel.sin from the ftf.
winkhant said:
Can it be use on E6683
Build no - 32.0.A.6.152
Click to expand...
Click to collapse
I've applied this on my E6683. All looks good :good:
magadaner said:
I've applied this on my E6683. All looks good :good:
Click to expand...
Click to collapse
Awesome! That's what I figured, but good to have confirmation. I'll edit accordingly.
nilezon said:
It's fairly easy to make it bootable.
Modify your boot.img ramdisk using this code and instructions:
https://github.com/jackfagner/twrp-sony-recovery-boot-script
Then just flash the recovery with fastboot.
Click to expand...
Click to collapse
Is there anything that needs to be changed with the recovery script to work on the Z5? I threw it into my kernel and followed the directions to a tee and I get a bootloop. I saw @AndroPlus made a kernel too using your script, so I flashed it to see if it worked and it was fine. I unpacked his boot.img and looked at it and the structure was the exact same. After hitting my head against a wall for a while, I tried repacking his just to make sure I wasn't crazy. The file size between his initial boot.img and the repacked one was a few KB different, and when I repack his, it bootloops too. So then I made sure mkboot tools were working fine and I unpacked/repacked my initial kernel, and it boots just fine.
Then I tried breaking it down:
I took my kernel, unpacked/repacked and it was fine. Then I copied over the bootrec folder, repacked, and it was fine. Then I made sure the symlink was working, so I:
Code:
mv init init.real
ln -s init.real init
and it booted just fine.
Then I did the final
Code:
rm init
ln -s /bootrec/init.sh init
and repacked, and it bootloops forever Any ideas about what is happening?
The only thing I can think of is that I messed up the symlink some how, but I dont know why AndroPlus's works before repacking and not after. Bleh :/
EDIT: **** everything. I ended up using SuperRs kitchen instead. That worked just fine. Noooo idea why mkbootimg_tools failed me.
External SD card is not detected on E6683.
Masa. T said:
External SD card is not detected on E6683.
Click to expand...
Click to collapse
Once I get my Z5 dual (E6683) in I may try to build a kernel specifically for the E6683's. I need to figure out how much I'll lose from losing the DRM keys.
Masa. T said:
External SD card is not detected on E6683.
Click to expand...
Click to collapse
In the kernel or TWRP?
EDIT: My bad, I spaced on the variants. I thought the 6683 was the baseband variant, not the dual sim. Yeah, I wouldn't roll with this on there.
And this is confirmed as working on the Z5 ?. because I have waited for root for this for some time now, and if it works I will be a happy man.
MeX_DK said:
And this is confirmed as working on the Z5 ?. because I have waited for root for this for some time now, and if it works I will be a happy man.
Click to expand...
Click to collapse
This is not an exploit, if that is what you are asking. As stated in OP, you need to unlock your bootloader first. The kernel is merely the stock kernel with the security features disabled, which allows you to be able to flash SuperSU. But yes, it works.
Here is the stock kernel from the latest 32.0.A.6.200 5.1.1 firmware with TWRP 3.0.0-0
SONY RIC and dm-verity disabled so you can root your phone and modify the system partition.
Flash the boot.img with fastboot by turning your phone off and holding volume up whilst plugging it in to your computer, you will see the led light up. If the drivers and adb/fastboot are installed properly it will show up under devices. If you just unlocked your bootloader then it is set up properly, but just to be sure type this-
Code:
fastboot devices
If it shows up properly, flash the kernel.
Code:
fastboot flash boot boot.img
If you are already rooted flash this in recovery 32.0.A.6.200_TWRPv3.0.0-0.zip
After flashing press volume up to boot into TWRP, or volume down to boot in to your current recovery.
Downloads-
boot.img
32.0.A.6.200_TWRPv3.0.0-0.zip
Thanks to @tobias.waldvogel for making this much easier.
Also @AndroPlus for TWRP v3.0.0-0
Tip-
For people that have just unlocked their bootloader and want to root their device the easiest way, flash the kernel with fastboot like I said before and turn off your phone by unplugging it.
Press volume up when booting, the led will turn blue, it will go red and boot into TWRP when pressing it, now download this on your computer SuperSU v2.65
Connect your phone and transfer the file over via mtp in TWRP, now flash it and you have rooted your phone safely and fast.
Somebody test it ?
You don't need to test, i've been using using it for the past 2 weeks
Sent from my E6653 using Tapatalk
I'm testing it, Androplus kernel too unstable...
Thanks
nreuge said:
I'm testing it, Androplus kernel too unstable...
Thanks
Click to expand...
Click to collapse
We are waiting your feedback.
Bro this is stock kernel what are you testing ?
gm007 said:
We are waiting your feedback.
Bro this is stock kernel what are you testing
Click to expand...
Click to collapse
For the moment, it's fine.
I'm testing androplus kernels for more than one year (on the Z2 before) and although I appreciate his work, I'm tired of random reboots... Stock kernel is less fun for sure
@nreuge Thanks for the testing. Wondering what is the lost comparing with stock kernel to Android Plus one? Seem the tweak can be done with root in the OS anyway...
chenliangchen said:
@nreuge Thanks for the testing. Wondering what is the lost comparing with stock kernel to Android Plus one? Seem the tweak can be done with root in the OS anyway...
Click to expand...
Click to collapse
No, there are things at the kernel level that you can't do just tweaking android, e.g. additional CPU governors, hotplugs, thermal managements, etc...
But are these things really a gain if the device stability is affected?...
For the moment, I'm happy with this stock kernel
thank you very much
noob question :
I'm not familiar with Sony's this Z5 is my first .. after flashing this kernel ,will I get OTA updates ? because I'm waiting for the 6.0
korom42 said:
thank you very much
noob question :
I'm not familiar with Sony's this Z5 is my first .. after flashing this kernel ,will I get OTA updates ? because I'm waiting for the 6.0
Click to expand...
Click to collapse
You wont get ota updates after unlocking bootloader, but you can flash stock MM firmware when it's released with flashtool.
gm007 said:
You wont get ota updates after unlocking bootloader, but you can flash stock MM firmware when it's released with flashtool.
Click to expand...
Click to collapse
That's bad :crying: .. I'll wait more before customizing my Z5
*** deleted
celderic said:
Here is the stock kernel from the latest 32.0.A.6.200 5.1.1 firmware with TWRP 3.0.0-0
SONY RIC and dm-verity disabled so you can root your phone and modify the system partition.
Flash the boot.img with fastboot by turning your phone off and holding volume up whilst plugging it in to your computer, you will see the led light up. If the drivers and adb/fastboot are installed properly it will show up under devices. If you just unlocked your bootloader then it is set up properly, but just to be sure type this-
Code:
fastboot devices
If it shows up properly, flash the kernel.
Code:
fastboot flash boot boot.img
If you are already rooted flash this in recovery 32.0.A.6.200_TWRPv3.0.0-0.zip
After flashing press volume up to boot into TWRP, or volume down to boot in to your current recovery.
Downloads-
boot.img
32.0.A.6.200_TWRPv3.0.0-0.zip
Thanks to @tobias.waldvogel for making this much easier.
Also @AndroPlus for TWRP v3.0.0-0
Tip-
For people that have just unlocked their bootloader and want to root their device the easiest way, flash the kernel with fastboot like I said before and turn off your phone by unplugging it.
Press volume up when booting, the led will turn blue, it will go red and boot into TWRP when pressing it, now download this on your computer SuperSU v2.65
Connect your phone and transfer the file over via mtp in TWRP, now flash it and you have rooted your phone safely and fast.
Click to expand...
Click to collapse
Hi and thanks for this beautiful and simple guide, I have a small problem because i flashed boot.img with stock 5.1 a.200 i mean, and it start but after i press vol up it doesnt go to recovery, do i have something wrong ? many thanks and really perfect work! hope to use it soon