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?
Related
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.
NEW: YOU SHOULD UNLOCK YOUR BOOTLOADER : http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
Hi !
Since @vortox found and created an unlock method (!) for our devices (see original development section) you'll find here twrp recovery for the 7" kindle fire hdx (Thor).
WARNING
THIS OPERATION IS DANGEROUS
THE ONLY WAY TO RECOVER FROM A RECOVERY PROBLEM IS TO HAVE A WORKING SYSTEM ROM
Installation (from stock rom)
Be sure to have a rooted, 7" hdx with firmware <= 13.3.2.3 (for bootloader compatibility)
Use an application from the market to flash the recovery image like Rashr or Flashify (from vortox)
OR use dd application from a root shell : "dd of=/dev/block/platform/msm_sdcc.1/by-name/recovery if=/sdcard/twrp.img"
Installation (from twrp)
Flash zip file from twrp recovery...
Download
Please see @ggow thread for up to date recovery : http://forum.xda-developers.com/kin...ecovery-twrp-recovery-2-8-1-0-apollo-t2991155
Thanks
@vortox for the exploit !
Cpasjuste said:
Hi !
Since an unlock method seems to be coming to our devices (see original development section) you'll find here a twrp recovery for the kindle hdx (Thor). I will try to compile an Apollo version as soon as an unlock method is reveled. (Or @ggow will do it )
Oups I'm sorry I didn't fully read the unlock thread. The recovery need to be patched to run so I removed the link for now. The recovery was sent to the right person, well see !
Click to expand...
Click to collapse
Hello, yes I have a build of twrp for apollo waiting here ready to go...
Sent from my Nexus 6 using Tapatalk
Hi !
First post updated with download link ! I'm unable to test the recovery myself as i own an unlocked device so thanks to wait for some experienced users to report back. If the recovery is not working for you then you can boot to your system rom and restore your backed up recovery from there...
Thanks to @vortox again and happy new year !
Cpasjuste said:
Hi !
First post updated with download link ! I'm unable to test the recovery myself as i own an unlocked device so thanks to wait for some experienced users to report back. If the recovery is not working for you then you can boot to your system rom and restore your backed up recovery from there...
Thanks to @vortox again and happy new year !
Click to expand...
Click to collapse
Do you have to be on stock rom or would it work with safestrap and nexus 2.2 on stock slot?
Sent from my A0001
It should work from any rom/configuration as soon as you have root and a rom <= 3.2.4 (version to be confirmed).
I tried applying the recovery with flashify on 3.2.4 and it hasn't worked as far as I can tell, though I didn't remove safestrap yet. It just gets stuck on grey kindle fire logo 9/10 boots then finally gets into safestrap. Don't really want to remove my only safety net unless it's confirmed I have to.
derpadoodle said:
I tried applying the recovery with flashify on 3.2.4 and it hasn't worked as far as I can tell, though I didn't remove safestrap yet. It just gets stuck on grey kindle fire logo 9/10 boots then finally gets into safestrap. Don't really want to remove my only safety net unless it's confirmed I have to.
Click to expand...
Click to collapse
Did you try to power on the device with volume up to trigger the recovery ? Else maybe 3.2.4 is too late for the recovery sig exploit.
Yeah I tried that, no effect.
I'll downgrade to 3.2.1 later today.
derpadoodle said:
Yeah I tried that, no effect.
I'll downgrade to 3.2.1 later today.
Click to expand...
Click to collapse
Cool thanks, let us know !
Looks like you butchered the original post while you were editing.
I just downgraded to 13.3.1.0 so I'm ready to test it out. But —before proceeding — how do you backup the stock recovery?
It's not working on 3.2.4, but works atleast at 3.1.0. I didn't test other versions.
I ended up finding an app on the Play Store to backup the recovery.
Anyways, I can now also confirm that this works on 13.3.1.0.
EncryptedCurse said:
Looks like you butchered the original post while you were editing. [emoji14]
I just downgraded to 13.3.1.0 so I'm ready to test it out. But —before proceeding — how do you backup the stock recovery?
Click to expand...
Click to collapse
Ho crap :/ This is the worst part for me and I screwed it ^^
Should I uninstall safestrap before flashing the recovery?
Is it just me, or does the screen have a yellowish tint while in recovery mode?
EncryptedCurse said:
Is it just me, or does the screen have a yellowish tint while in recovery mode?
Click to expand...
Click to collapse
I do not seems to have the problem here but its possible that we need to update the adreno fw in the persist partition. You'll have a better visibility when you'll try CM to be sure.
I have placed rollback images here...
http://forum.xda-developers.com/kindle-fire-hdx/development/13-3-2-4-rollback-images-t2991015
I am rolled back from 13.3.2.4 to 13.3.1.0 successfully and the Recovery-Image works fine with locked Bootloader
[email protected]
Cpasjuste said:
Hi !
[*]OR use dd application from a rooted system : "dd of=/dev/block/platform/msm_sdcc.1/by-name/boot if=/sdcard/twrp.img"
Click to expand...
Click to collapse
Not dd of=/dev/block/platform/msm_sdcc.1/by-name/recovery if=/sdcard/twrp.img ?
ONYXis said:
Not dd of=/dev/block/platform/msm_sdcc.1/by-name/recovery if=/sdcard/twrp.img ?
Click to expand...
Click to collapse
Thanks for the head up, this was very dangerous :x Main post has been updated.
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
I've been trying to find how to install a kernel for a few days but i couldn't find any good and updated source. I'm thinking of installing latest helium to my device. Can anyone help me?
ExclusiveBFS said:
I've been trying to find how to install a kernel for a few days but i couldn't find any good and updated source. I'm thinking of installing latest helium to my device. Can anyone help me?
Click to expand...
Click to collapse
Through any recovery is the most easy way, but you have to unlock bootloader first.
Do you even know what it does?
Bigrrd225 said:
Do you even know what it does?
Click to expand...
Click to collapse
Yeah, I do. I just didn't want to flash it and take risk. I must have learned details
HUEguy said:
Through any recovery is the most easy way, but you have to unlock bootloader first.
Click to expand...
Click to collapse
My bootloader is unlocked. And I have the twrp. Thanks!
ExclusiveBFS said:
Yeah, I do. I just didn't want to flash it and take risk. I must have learned details
My bootloader is unlocked. And I have the twrp. Thanks!
Click to expand...
Click to collapse
Then just flash the .zip file via TWRP. Simple. Of course you'll need a ROM compatible with helium otherwise you'll be stuck in a bootloop.
Also goes without saying that you should take a nandroid backup via TWRP first in case something goes wrong.
Edit : When you say you have TWRP, is it part of your current kernel or you flashed it in your FOTA kernel partition via Rashr or something? If its the former then flashing Helium would overwrite TWRP and you could wind up without a working recovery cause I don't think Helium comes with any. Might want to flash TWRP in your FOTA partition with Rashr before you proceed.
XenolithicYardZone said:
Then just flash the .zip file via TWRP. Simple. Of course you'll need a ROM compatible with helium otherwise you'll be stuck in a bootloop.
Also goes without saying that you should take a nandroid backup via TWRP first in case something goes wrong.
Edit : When you say you have TWRP, is it part of your current kernel or you flashed it in your FOTA kernel partition via Rashr or something? If its the former then flashing Helium would overwrite TWRP and you could wind up without a working recovery cause I don't think Helium comes with any. Might want to flash TWRP in your FOTA partition with Rashr before you proceed.
Click to expand...
Click to collapse
I was on latest candy5, i flashed adrian dc's twrp from recovery but now I'm installing the stock ftf, I will try carbon lp rom. When the installation completed, I will flash adrian dc's twrp again. Then I will flash the helium kernel with twrp. Is there a problem with that? Should I install twrp with rashr?
ExclusiveBFS said:
I was on latest candy5, i flashed adrian dc's twrp from recovery but now I'm installing the stock ftf, I will try carbon lp rom. When the installation completed, I will flash adrian dc's twrp again. Then I will flash the helium kernel with twrp. Is there a problem with that? Should I install twrp with rashr?
Click to expand...
Click to collapse
If you're gonna flash stock firmware via Flashtool then your FOTA recovery will be wiped out. How are you gonna flash TWRP & Carbon LP rom when you don't have a recovery in the first place?
http://forum.xda-developers.com/xperia-sp/development/recovery-twrp-3-0-0-touch-recovery-t3309938
The recovery from the above thread is flashable but you still need an working recovery on your device to be able to do it right? What you can do it use the fastboot bootable image and install whatever you want if you're gonna go stock.
Actually you only need Rashr if you wanna stay stock but still want a working recovery.
XenolithicYardZone said:
If you're gonna flash stock firmware via Flashtool then your FOTA recovery will be wiped out. How are you gonna flash TWRP & Carbon LP rom when you don't have a recovery in the first place?
http://forum.xda-developers.com/xperia-sp/development/recovery-twrp-3-0-0-touch-recovery-t3309938
The recovery from the above thread is flashable but you still need an working recovery on your device to be able to do it right? What you can do it use the fastboot bootable image and install whatever you want if you're gonna go stock.
Actually you only need Rashr if you wanna stay stock but still want a working recovery.
Click to expand...
Click to collapse
I guess I couldn't explained my situation well. I installed carbon rom just now, and flashed gapps. I didn't check if carbon comes with a recovery but if it comes, I'm going to flash adrian dc's twrp through stock recovery. That's what I'm asking, is there a difference between using rashr to install twrp or flashing through recovery.
ExclusiveBFS said:
I guess I couldn't explained my situation well. I installed carbon rom just now, and flashed gapps. I didn't check if carbon comes with a recovery but if it comes, I'm going to flash adrian dc's twrp through stock recovery. That's what I'm asking, is there a difference between using rashr to install twrp or flashing through recovery.
Click to expand...
Click to collapse
Carbon provides CM recovery. Flash TWRP only through recovery, don't use Rashr.
ExclusiveBFS said:
I guess I couldn't explained my situation well. I installed carbon rom just now, and flashed gapps. I didn't check if carbon comes with a recovery but if it comes, I'm going to flash adrian dc's twrp through stock recovery. That's what I'm asking, is there a difference between using rashr to install twrp or flashing through recovery.
Click to expand...
Click to collapse
The recovery that comes with Carbon is most probably Cyanogen recovery which will not let you flash unsigned zip files like custom kernels & roms, SuperSU, Xposed, etc.
Its the reason why people install a recovery in their FOTA partitions because installing new kernels or roms (which include their own kernel) wipes out the previous recovery since Xperia phones esp older one's like ours don't have a separate recovery partition - the recovery is part of the kernel so it gets replaced by whatever came (or didn't) with the new kernel or rom. Atleast that's how it works to the best of my knowledge.
With fastboot, you could boot the device into TWRP recovery using the twrp-3.0.0-rX-boot-huashan.img file and the command "fastboot boot *filename*.img". This way its just temporary and doesn't permanently flash anything. Once in the recovery, flash the rom, kernel, recovery and you are done. That's how I did it on my Mi4i though you might want to confirm but since the description next to it says fastboot bootable, I guessing it works on the same principal.
Edit : If the kernel creator says no Rashr then its no Rashr.
XenolithicYardZone said:
The recovery that comes with Carbon is most probably Cyanogen recovery which will not let you flash unsigned zip files like custom kernels & roms, SuperSU, Xposed, etc.
Its the reason why people install a recovery in their FOTA partitions because installing new kernels or roms (which include their own kernel) wipes out the previous recovery since Xperia phones esp older one's like ours don't have a separate recovery partition - the recovery is part of the kernel so it gets replaced by whatever came (or didn't) with the new kernel or rom. Atleast that's how it works to the best of my knowledge.
With fastboot, you could boot the device into TWRP recovery using the twrp-3.0.0-rX-boot-huashan.img file and the command "fastboot boot *filename*.img". This way its just temporary and doesn't permanently flash anything. Once in the recovery, flash the rom, kernel, recovery and you are done. That's how I did it on my Mi4i though you might want to confirm but since the description next to it says fastboot bootable, I guessing it works on the same principal.
Edit : If the kernel creator says no Rashr then its no Rashr.
Click to expand...
Click to collapse
I find that flashing TWRP from CM recovery and then Helium from TWRP is much simpler than flashing TWRP as a kernel in the boot partition, then flashing the rom again and the kernel.
Tomoms said:
Carbon provides CM recovery. Flash TWRP only through recovery, don't use Rashr.
Click to expand...
Click to collapse
I flashed helium v5 for lollipop through twrp 3.0.0 and rebooted. It's not booted yet, i'm waiting for 2 minutes and the screen is black. Is it normal?
Tomoms said:
I find that flashing TWRP from CM recovery and then Helium from TWRP is much simpler than flashing TWRP as a kernel in the boot partition, then flashing the rom again and the kernel.
Click to expand...
Click to collapse
Wait hang on, CM recovery lets you flash custom zip files now without moaning about file verification? Since when?
Yes that's why I asked him to temporarily boot up with the TWRP img and then flash whatever he liked from it but hey if you can flash stuff via CM recovery now then that's one less step to worry about.
Also why no Rashr? I haven't used it in a while that's why I am asking.
---------- Post added at 05:10 PM ---------- Previous post was at 05:07 PM ----------
ExclusiveBFS said:
I flashed helium v5 for lollipop through twrp 3.0.0 and rebooted. It's not booted yet, i'm waiting for 2 minutes and the screen is black. Is it normal?
Click to expand...
Click to collapse
You mean black screen after the Sony splash screen? Is that rom compatible with Helium?
XenolithicYardZone said:
Wait hang on, CM recovery lets you flash custom zip files now without moaning about file verification? Since when?
Yes that's why I asked him to temporarily boot up with the TWRP img and then flash whatever he liked from it but hey if you can flash stuff via CM recovery now then that's one less step to worry about.
Also why no Rashr? I haven't used it in a while that's why I am asking.
---------- Post added at 05:10 PM ---------- Previous post was at 05:07 PM ----------
You mean black screen after the Sony splash screen? Is that rom compatible with Helium?
Click to expand...
Click to collapse
First, yes it lets you flash custom zip files, that's what I was trying to tell I always used cm recovery to install twrp
And I haven't used rashr before, I didn't know how to use it. So I flashed it with cm recovery and perfectly installed.
About helium, my phone finally booted after 9 minutes, how I scared
ExclusiveBFS said:
First, yes it lets you flash custom zip files, that's what I was trying to tell I always used cm recovery to install twrp
And I haven't used rashr before, I didn't know how to use it. So I flashed it with cm recovery and perfectly installed.
About helium, my phone finally booted after 9 minutes, how I scared
Click to expand...
Click to collapse
Sorry man didn't know that CM recovery lets you do that now. Been out of the loop for a while.
Lol yeah I can relate but as long as you can see a splash screen, you're good and when you don't, Flashtool is your light in the darkness :victory:
ExclusiveBFS said:
I flashed helium v5 for lollipop through twrp 3.0.0 and rebooted. It's not booted yet, i'm waiting for 2 minutes and the screen is black. Is it normal?
Click to expand...
Click to collapse
The reboot button is broken on TWRP. Causes black screen for a long time. You must always use the Power off option instead.
XenolithicYardZone said:
Sorry man didn't know that CM recovery lets you do that now. Been out of the loop for a while.
Lol yeah I can relate but as long as you can see a splash screen, you're good and when you don't, Flashtool is your light in the darkness :victory:
Click to expand...
Click to collapse
CM recovery lets you flash signed zip, and TWRP is provided in a signed zip, while even though Helium is provided in a signed zip, it can't be flashed.
Tomoms said:
The reboot button is broken on TWRP. Causes black screen for a long time. You must always use the Power off option instead.
CM recovery lets you flash signed zip, and TWRP is provided in a signed zip, while even though Helium is provided in a signed zip, it can't be flashed.
Click to expand...
Click to collapse
@Tomoms, @XenolithicYardZone Thanks for all your help, I used more than 10 roms so far but never used a custom kernel before. You two helped me a lot
Tomoms said:
The reboot button is broken on TWRP. Causes black screen for a long time. You must always use the Power off option instead.
CM recovery lets you flash signed zip, and TWRP is provided in a signed zip, while even though Helium is provided in a signed zip, it can't be flashed.
Click to expand...
Click to collapse
Yeah kinda guessed it was signed cause in all my time flashing roms, I have never known CM recovery to allow the flashing of unsigned zips. So why doesn't it work with Helium if its signed?
ExclusiveBFS said:
@Tomoms, @XenolithicYardZone Thanks for all your help, I used more than 10 roms so far but never used a custom kernel before. You two helped me a lot
Click to expand...
Click to collapse
Your welcome man. As a famous author once said, "Help will always be given at XDA to those who ask for it. "
XenolithicYardZone said:
Yeah kinda guessed it was signed cause in all my time flashing roms, I have never known CM recovery to allow the flashing of unsigned zips. So why doesn't it work with Helium if its signed?
Click to expand...
Click to collapse
Because CM recovery sucks
Tomoms said:
Because CM recovery sucks
Click to expand...
Click to collapse
True that!
Code:
[B]NOTE : [/B]PROCEED AT YOUR OWN RISK. Guide tested successfully to flash [U]Stock WW-15.2016.1805.309[/U] from AOSP extended (22/06 build) on primary device. Also I will try to help out in case of issues.
If already on Stock Rom then visit THIS THREAD for OTA updates.
This thread is useful for those who want to return to stock ROM from custom ROM while keeping TWRP & unlocked bootloader.
How to ,
Backup all your important app data.
Do a TWRP backup of current ROM. (precautionary step)
Download modified full recovery stock rom - TWRP_Stock_v340.zip from this post.
Download decrypt.zip from HERE.
Reboot to TWRP.
Go to wipe and select swipe to Factory reset.
Flash the ROM file.
Flash decrypt.zip file.
Reboot & Enjoy.
Users coming from Android Pie reported microphone issues - in case you face it then flash DolbyPlus-Oreo_8.1.zip from THIS post via Magisk which might resolve the issue.
(optional) If you want to boost up by debloating then use this MOD.
(optional) If you want to boost up BATTERY then use this GUIDE.
Remember that it takes a lot of time to create , test and upload these huge files for everyones use. So please hit Thanks! button on the bottom right of the post to keep me motivated
NOTE : ROM works independant of RAM i.e. applicable for 3/4/6 GB variants.
Recommended TWRP : https://androidfilehost.com/?fid=3700668719832241089 by @SagarMakhar.
To ROOT the ROM
Flash Magisk from TWRP and you will have root access
Well I am trying to flash this ROM coming from RR but somehow its taking half an hour to encrypt so is it necessary to encrypt can't we just skip it ???
also it did erased TWRP as when I am trying to get in TWRP using volume up + power button its get back to default bootloader that came with mobile .....
also do I have to flash again TWRP again after this to get back root via magisk......
piku2008 said:
Well I am trying to flash this ROM coming from RR but somehow its taking half an hour to encrypt so is it necessary to encrypt can't we just skip it ???
also it did erased TWRP as when I am trying to get in TWRP using volume up + power button its get back to default bootloader that came with mobile .....
also do I have to flash again TWRP again after this to get back root via magisk......
Click to expand...
Click to collapse
Did you performed factory reset and flashed ROM & decrypt.zip
The TWRP survives the flash and Magisk can be flashed to Root the ROM but after above two files are flashed.
Well I successfully flashed ROM after complete factory reset with internal memory tooo ......
But some how TWRP got replaced with factory default (the one with root checker) with bootloader unlocked screen
Thank you. Just updated to latest version from old stock rom. Please update new versions also whenever available
Aftab_khatri said:
Thank you. Just updated to latest version from old stock rom. Please update new versions also whenever available
Click to expand...
Click to collapse
Will do
Thank You bro.. Your Guide has tested successfully from AOSiP build to stock ROM 309.. [emoji16]
Sent from my [device_name] using XDA-Developers Legacy app
AOSP to Stock
Good day, Can I use this method to go back in Stock Rom? Currently using AEX but I can't use my mobile data here in the Philippines, your answer would be a great help, Thank you...
[Update]
Good day mate, just flashed this, and I'm back to stock with root, Thanks Mate for this...
jroviel18 said:
Good day, Can I use this method to go back in Stock Rom? Currently using AEX but I can't use my mobile data here in the Philippines, your answer would be a great help, Thank you...
[Update]
Good day mate, just flashed this, and I'm back to stock with root, Thanks Mate for this...
Click to expand...
Click to collapse
Great .. Sorry could not reply earlier but you got the resolution of the query.
For subseqeunt update with TWRP intact .. please follow this guide in future .. https://forum.xda-developers.com/as...to/rom-update-stock-firmware-keeping-t3808269
Update - WW-15.2016.1805.311
Updated Stock ROM file - TWRP_Stock_v311.zip now avaliable.
For those who are already on stock ROM,
The instructions to flash are in THIS POST.
For those who are on custom ROM,
The instruction to flash are in THIS POST
Do these zips format internal storage or not ??
aadi50 said:
Do these zips format internal storage or not ??
Click to expand...
Click to collapse
No
aadi50 said:
Do these zips format internal storage or not ??
Click to expand...
Click to collapse
I believe this is the exact same firmware as the official one. It is just modified to work with TWRP. Nothing more, nothing less.
aadi50 said:
Do these zips format internal storage or not ??
Click to expand...
Click to collapse
You will have to format data (i.e. factory reset) but the Internal Storage will be safe.
aaa
Work For Max Pro M1 ?
This rom XOOT not XOOTD
---------- Post added at 11:26 AM ---------- Previous post was at 11:07 AM ----------
.A.V.i.n.a.S.h. said:
Code:
[B]NOTE : [/B]Guide tested successfully to flash [U]Stock WW-15.2016.1805.309[/U] from AOSP extended (22/06 build) on primary device. Also I will try to help out in case of issues. BUT still proceed at your own risk.
This thread is useful for those who want to return to stock ROM from custom ROM while keeping TWRP & unlocked bootloader.
How to ,
Backup all your important app data.
Do a TWRP backup of current ROM. (precautionary step)
Download modified full recovery stock rom - Stock_X00T_Patch_May_Version_311_TWRP.zip.
Download decrypt.zip from HERE.
Reboot to TWRP.
Go to wipe and select swipe to Factory reset.
Flash the ROM file.
Flash decrypt.zip file.
Reboot & Enjoy.
(optional) If you want to boost up by debloating then use this MOD.
This will update your firmware to WW-15.2016.1805.311 to have updates after this follow THIS THREAD.
Remember that it takes a lot of time to create , test and upload these huge files for everyones use. So please hit Thanks! button on the bottom right of the post to keep me motivated
Click to expand...
Click to collapse
My Devices Zenfone Max Pro M1 X00TD
This your Rom Not WORKING X00T
Flash to TWRP error TWRP Has Restarting
sory bad english
arielrizuly said:
My Devices Zenfone Max Pro M1 X00TD
This your Rom Not WORKING X00T
Flash to TWRP error TWRP Has Restarting
sory bad english
Click to expand...
Click to collapse
This ROM should work on X00T and X00TD both. Can you please validated checksum again for the downloaded file.
.A.V.i.n.a.S.h. said:
This ROM should work on X00T and X00TD both. Can you please validated checksum again for the downloaded file.
Click to expand...
Click to collapse
I am on stock build 311 and Rom X00TD , i am unable to root or even unlock bootloader on my device.
Tried all methods , on YouTube and xda but all wasted.
Though , i debloated my phone using one of the methods mention in a thread in xda and even installed xda navbar using adb.
Please help.
Abby 244 said:
I am on stock build 311 and Rom X00TD , i am unable to root or even unlock bootloader on my device.
Tried all methods , on YouTube and xda but all wasted.
Though , i debloated my phone using one of the methods mention in a thread in xda and even installed xda navbar using adb.
Please help.
Click to expand...
Click to collapse
Have you checked the drivers if they are installed.
Do one thing .. see if in fastboot .. if you get any responce for fastboot devices command from pc.
.A.V.i.n.a.S.h. said:
Have you checked the drivers if they are installed.
Do one thing .. see if in fastboot .. if you get any responce for fastboot devices command from pc.
Click to expand...
Click to collapse
No response even in fastboot.