Database Develop

[Recovery]Clockwork Mod 4.0.1.4 (3.2 compatable)

DJ Steve ported CWM 4.0.1.4 with the release of 507.
Requirements:
Stock 5xx based rom [Honeystreak is not supported!]
Ability to enter fastboot mode: Fastboot+ADB.zip
Battery with 60% or greater charge
Basic understanding of the command line
Install Instructions:
Download recovery.img
flash the recovery with "fastboot flash recovery recovery.img"
Finished
Credits:
DJ_Steve for porting it
Koush for creating clockwork mod
I take no credit beyond this basic guide
Notice:
The Streak 7 with HC might now detect the driver properly, if it doesnt you must force install it using the "Android ADB Interface" from the list of available drivers
Will not work on 2.2.x, you must use CWM 3.0 for that.
Do not attempt to wipe data from within CWM, it will likely case a boot loop afterwards.

Thank you!!
Can I just push this recovery to my recovery partition within 3.2?
Im having issues having my PC at work recognize the fastboot device, and installing the drivers.
I am on xp..
TIA!

'error: cannot load 'recovery.img'
I got fastboot going fine, commands like 'fastboot reboot' are working.
However just above when I use your line to flash recovery, any ideas on what it might be!?

Uploaded new version of fastboot+adb.zip hopefully it has the correct IDs so you dont have to force install it.
Are you sure you downloaded the image correctly, and did you name it correctly when using fastboot

Yeah I was making a repeated typo when pointing fastboot to the recovery but its all working now, thanks a lot.
Clockwork mod (cool blue writing) and rooted all within a few days, good work and thanks to all involved.

FWIW I tried this on the T-MO stock 2.2.2 ROM. The install went fine, I copied S7-4.0.1.4.img to recovery.img and ran the fastboot command with no problems.
I power up the Dell Streak 7 while holding power and the up volume key, and get the menu as expected. I Select "Software Upgrade via update.pkg on SD Card", and the message "Booting recovery kernel image" is displayed.
At this point the machine seems to be frozen. I can reset with a paper clip, and reboot the machine into 2.2.2 just fine, but if I cannot resolve why it does not show the clockwordmod menu, then I guess it is back to NVFLASH.
So what am I doing wrong? do I need an SD card in the device with an update.pkg on the card? Or is there something else?

Oh that was a strong possibility.
CWM 4.0 uses the 507 kernel as a base. 507 will not boot without updating the bootloaders.
So that means CWM 4.0 wouldnt be able to boot unless you had 50x installed.

TheManii said:
Oh that was a strong possibility.
CWM 4.0 uses the 507 kernel as a base. 507 will not boot without updating the bootloaders.
So that means CWM 4.0 wouldnt be able to boot unless you had 50x installed.
Click to expand...
Click to collapse
Probably a good idea then to remove that "Assumed to work on 2.2.2" phrase then from your first append.
So I guess it is NVFLASH time ... Or could I somehow flash back only the original recovery.img using fastboot somehow?

Post updated, i needed someone to actually confirm that it didnt work as i dont have access to a s7

dblml320 said:
Probably a good idea then to remove that "Assumed to work on 2.2.2" phrase then from your first append.
So I guess it is NVFLASH time ... Or could I somehow flash back only the original recovery.img using fastboot somehow?
Click to expand...
Click to collapse
I posted over at TabletRoms yesterday that the new recovery did not work with Froyo 2.2.2.
To answer your question, all you have to do is fastboot flash the old CWM recovery, version 3xx something I think it is.

"waiting for device " and nothing happen !!! what should i do? i can not install driver using files in : Fastboot+ADB\Win32\Streak 5+Streak 7+Venue\Win7 !

cdzo72 said:
I posted over at TabletRoms yesterday that the new recovery did not work with Froyo 2.2.2.
To answer your question, all you have to do is fastboot flash the old CWM recovery, version 3xx something I think it is.
Click to expand...
Click to collapse
Like he said if you flashed it on a s7 that's still on 2.2.x just reflash with the CWM 3.0 one and that one will work fine on 2.2.x

Is there another way to root stock 3.2?
I am getting this error in fastboot...
"Flashing StorMgr partition recovery
Read after write verify partition recovery"

Not the stock one, as no other rooting tools work on it.
Ways to get around it include: using a pre-rooted rom or using a custom rom (which are normally pre-rooted)
Something may be wrong with your device/install if that is coming up. Or possibly your download was bad, try re-downloading it.

I tried re-downloading didn't work, I have stock rom, I don't think I can install a custom or pre-rooted rom without installing CWM?

You can with nvflash, as honeystreak is ment to be installed with nvflash then updated with the bundled CWM, which is prerooted
Whichever method you decide is up to you, as I cannot formally recommend that one method is better then the other.

thesmacker11 said:
Is there another way to root stock 3.2?
I am getting this error in fastboot...
"Flashing StorMgr partition recovery
Read after write verify partition recovery"
Click to expand...
Click to collapse
Well just as an update I tried this on a windows xp, windows 7 32bit, windows 7 64bit computer, and redownloaded that file each time and it still does the same thing on my device.

It's likely your device itself that's the issue then, I cant be more specific as I dont own a S7

I'm not sure if I should be asking questions here or over in another forum. Figure I'll start here...
I was sorely missing app2sd in honeycomb so went to use and install Link2SD figuring I'd use that. But it doesn't seem to see the second partition I've made on my SDHC card. I can mount the card on Mac OS and Linux and both mount the two partitions on the card so I feel pretty sure I formatted the card correctly. I saw some comment about a change in the way CW mounts things and it causing troubles in the Link2SD thread but I don't understand enough about the magic of Android and how it mounts discs, although I know it had Linux roots, so the comments in that thread weren't clear to me what I can do to get Link2SD working or for that matter even start to gather info to try to figure out what's wrong. Can anyone help me out or point me to a thread that can get me started in figuring out what's going wrong?
Sent from my HTC Flyer P512 using Tapatalk

ok so i installed the drivers for fastboot and i can enter fast boot , but how can i push the file? soory im a newb with the streak.

[RECOVERY] Official CWM Recovery 6.0.4.7 for Nexus 4; revert recovery disabler

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?

CWM is available to flash through Rom Manager

Rom Manager was just updated to version 5.0.2.4 and allows you to flash to CWM 6.0.1.6 recovery. Booting to recovery just gives me the Android with a red flag though. Just a FYI till it gets sorted.
Pressing and holding the pwr button will boot you back to the OS. Not a huge deal as we don't have anything to flash at the moment.
If you need to get back to the stock recovery in the meantime which can be found in this thread
http://forum.xda-developers.com/showthread.php?t=1993331
Edit:
Don't Flash this yet, you'll have to re-install the stock recovery or wait for a fix and could possibly brick your phone if you don't know what you're doing.

Is there like an easy way to root other than manually adb pushing? Flashable zip maybe?

I get the same thing as you, says flash successful then the red flag.

F4M0U569 said:
Is there like an easy way to root other than manually adb pushing? Flashable zip maybe?
Click to expand...
Click to collapse
You can use the temporary "boot" method as opposed to "flash" when using the current CWM recovery which is posted here http://forum.xda-developers.com/showthread.php?t=1993331
Don't flash the recovery yet though, it's obviously not sorted. I used the adb method to root which worked fine. I got excited when I saw the new Rom Manager which allowed me to flash recovery because Koush's G+ messages earlier today.

kchino said:
You can use the temporary "boot" method as opposed to "flash" when using the current CWM recovery which is posted here http://forum.xda-developers.com/showthread.php?t=1993331
Don't flash the recovery yet though, it's obviously not sorted. I used the adb method to root which worked fine. I got excited when I saw the new Rom Manager which allowed me to flash recovery because Koush's G+ messages earlier today.
Click to expand...
Click to collapse
I tried using the adb boot method but it doesn't work for me. After booting the insecure boot and taking me to the Android screen, I tried using the codes listed there but it says no device found.

F4M0U569 said:
I tried using the adb boot method but it doesn't work for me. After booting the insecure boot and taking me to the Android screen, I tried using the codes listed there but it says no device found.
Click to expand...
Click to collapse
i did it last night and it was quite late, but if i remember correctly i had the same problem but just had to reselect USB debugging
Sent from my Nexus 7 using xda app-developers app

[Firmware] Nvidia Root-Friendly Updates [No Wipe]

If coming from the original JellyBean and have not updated your custom recovery since, you will need to install the recovery provided below. This step only needs to be performed once to support the newer updates.
Recovery Update
Boot into bootloader mode, connect the USB cable, and from a terminal window or command prompt type:
Code:
fastboot flash recovery recovery.img
To root an OTA, the procedure is pretty simple.
Code:
Copy the OTA from the cache folder to the sdcard.
Move the OTA zip somewhere it can be opened and unzip it
Go to system/etc/ to find the file named recovery and delete it
(extension may vary, but it is always named recovery)
Open the META-INF/com/google/android/updater-script
Delete all of step 1 and step 3 so that all that is left is the large middle portion without any steps
That's it. You have made the same files you find here.
Download the desired package below and copy it to your sdcard, along with the SuperSU recovery package.
Boot into recovery, select install from sdcard, and choose the update. Go back and repeat the install for SuperSU.
KitKat Update 98
KitKat Update 99
Lollipop Update 110
XDA:DevDB Information
Nvidia Root-Friendly Updates [No Wipe], ROM for the Nvidia Shield
Contributors
twistedumbrella
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2014-11-08
Last Updated 2018-07-05

twistedumbrella said:
The new update has a few things that require updating the recovery, but since a recovery is not officially developed, updating the kernel of the existing recovery will do the trick. Flash this first.
Recovery Update
The install requires removing the assert checks since there is an error that the device is a Thor but looking for a Roth (same thing, right?). Install this from the new recovery.
KitKat Update
Immediately after installing the update, install the SuperSU recovery package to restore root and you're all set.
http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
So install the first zip in your current recovery and then reboot recovery. After that, flash the next two back to back?

NapalmDawn said:
So install the first zip in your current recovery and then reboot recovery. After that, flash the next two back to back?
Click to expand...
Click to collapse
Recovery first, then the two back to back. The old recovery won't flash it properly because of new metadata commands

twistedumbrella said:
Recovery first, then the two back to back. The old recovery won't flash it properly because of new metadata commands
Click to expand...
Click to collapse
Currently my shield is 4.3, rooted and has a kernel of 3.4.10. When I boot to recovery, I get the broken android guy with the red triangle. I think if I remember right, when I was rooting it, I had issues getting a working recovery on there since mine was fairly new when I got it. So what is thebest way to install that first zip? Would I be doing it via fastboot?

NapalmDawn said:
Currently my shield is 4.3, rooted and has a kernel of 3.4.10. When I boot to recovery, I get the broken android guy with the red triangle. I think if I remember right, when I was rooting it, I had issues getting a working recovery on there since mine was fairly new when I got it. So what is thebest way to install that first zip? Would I be doing it via fastboot?
Click to expand...
Click to collapse
First off I want to say thanks umbrella, for coming up with this method.
Bit off topic but I figured I would throw it out there, when you get the broken android guy, your recovery is doing exactly what it's supposed to. It's working, dont quote me here but I think pressing home and back simultaneously will get the menu to come up. I could be wrong on the button combo but there is a combination of button's to get the stock recovery menu to come up. If I remember right my droid X was the same way.

KitKat Update Without Complete Re-root
hexitnow said:
First off I want to say thanks umbrella, for coming up with this method.
Bit off topic but I figured I would throw it out there, when you get the broken android guy, your recovery is doing exactly what it's supposed to. It's working, dont quote me here but I think pressing home and back simultaneously will get the menu to come up. I could be wrong on the button combo but there is a combination of button's to get the stock recovery menu to come up. If I remember right my droid X was the same way.
Click to expand...
Click to collapse
Quite possible. I stripped out the recovery in the update and used fastboot on recovery for this one. I rushed through it a bit lol.
If I remember right, I think it's by-name/SOS and the update uses it to install the system before flashing the recovery to the partition. I didn't update it, though, just in case that wasn't a secondary partition.

twistedumbrella said:
Quite possible. I stripped out the recovery in the update and used fastboot on recovery for this one. I rushed through it a bit lol.
If I remember right, I think it's by-name/SOS and the update uses it to install the system before flashing the recovery to the partition. I didn't update it, though, just in case that wasn't a secondary partition.
Click to expand...
Click to collapse
Ahh I gotcha. Well that's good to know. I haven't had a chance to really look at many of the files yet. Do you know if nvidia released the factory recovery packages yet?
EDIT:
Nevermind looks like 72 is out now.

Yeah, they are pretty good about that. It may be nearing the last update for this version, though

hexitnow said:
First off I want to say thanks umbrella, for coming up with this method.
Bit off topic but I figured I would throw it out there, when you get the broken android guy, your recovery is doing exactly what it's supposed to. It's working, dont quote me here but I think pressing home and back simultaneously will get the menu to come up. I could be wrong on the button combo but there is a combination of button's to get the stock recovery menu to come up. If I remember right my droid X was the same way.
Click to expand...
Click to collapse
Shield+home at the broken android guy brought up a menu.
What is the best way to install the recovery update file? Is this something that is done by booting the shield into the bootloader and then doing it via fastboot on the PC?

NapalmDawn said:
Shield+home at the broken android guy brought up a menu.
What is the best way to install the recovery update file? Is this something that is done by booting the shield into the bootloader and then doing it via fastboot on the PC?
Click to expand...
Click to collapse
Exactly

twistedumbrella said:
Exactly
Click to expand...
Click to collapse
Awesome. Thank you. Alternatively, I could accept the OTA and then push SU back to it again like I did the first time it was rooted right?
Last question-we have a working CWM recovery for the shield I believe. Are there any recoveries that work with the shield while running KitKat?

NapalmDawn said:
Awesome. Thank you. Alternatively, I could accept the OTA and then push SU back to it again like I did the first time it was rooted right?
Last question-we have a working CWM recovery for the shield I believe. Are there any recoveries that work with the shield while running KitKat?
Click to expand...
Click to collapse
The OTA will restore the stock recovery. This way updates it to one compatible with KitKat.

KitKat Update Without Complete Re-root
OTA 98 has been added. No recovery update is needed coming from 72. Flash the build and SuperSU and off you go. No data wipe necessary, either.

Link to the Recovery is not working :crying:
I am trying to install with the CWM Recovery and getting Status 7 errors, I try in stock recovery and get errors for Signature Verifications.

Neoistheone2000 said:
Link to the Recovery is not working :crying:
I am trying to install with the CWM Recovery and getting Status 7 errors, I try in stock recovery and get errors for Signature Verifications.
Click to expand...
Click to collapse
Updated

twistedumbrella said:
Updated
Click to expand...
Click to collapse
Thanks, that worked a treat

Yeah, to clarify, in recovery, you must press and hold Shield and Home buttons for a second, then release to bring up the menu. Then use X and Y to navigate, A to select. Don't understand why the bootloader or recovery don't use the D-pad at all. They're weird. Anyway, downloading this now, and will report back in a few minutes. This is just sideloaded via the stock recovery, right? I hope so, that's how I'm doing it right now.
EDIT: Nope. Failed again.
E:footer is wrong
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
I think I'll try that new recovery (funny, because I had flashed the one included in the original update archive, still had issues). I shouldn't have to use that one, I was on update 92 already.
EDIT 2: Oh, I'm dumb. Here I thought this was still being done with the STOCK recovery. Didn't realize this would flash in CWM. Awesome. Flashed SuperSU 2.16 while I was at it. Rebooted, and it's at .98, with root access. You ROCK, @twistedumbrella!

Did you do this with update 99 yet? Just came out today.

GuyInDogSuit said:
Did you do this with update 99 yet? Just came out today.
Click to expand...
Click to collapse
I don't even have it yet. I usually wait for it to come through on the device instead of going to the site. Faster to copy than download again.

twistedumbrella said:
I don't even have it yet. I usually wait for it to come through on the device instead of going to the site. Faster to copy than download again.
Click to expand...
Click to collapse
Hmmm. It started downloading as soon as I turned mine on. I'm just gonna do the usual process.

[RECOVERY] TWRP Recovery 2.8.7.0 - Apollo/Thor

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