Develop Bugs

[Q] Can't get into recovery (to make a back up of stock ROM)

---- PLEASE MOVE POST TO WILDFIRE S - Questions section. wrong post sorry!!----
Hi everyone!
First of all, thank you for taking the time to read this!
I have tried to do research on my problem but can't solve it...
The problem is that i can't get into recovery to backup my stock rom.
Specs: HTC Wildfire S, marvel A510e, S-on, Bootloader unlocked, Rooted, Radio-7.54.39.28M, Andriod 2.3.5, HTC sence: 2.1, ClockworkMod 5.0.2.8, Super SU.
I followed the guide: "How to root the Wildfire S with S-ON"on Andriod forums by CafeKampuchia, thumbs up for him It got me this far but, now I want to do the thing for which I rooted my phone in the first place: Installing a costum ROM. Therefore I want to backup my stock ROM.
Installed CWM ROM manager, if use backup current ROM option, the phone reboots and i get the HTC letters on my screen these. After a few sec's they dissapear and my screen goes black and my buttons on the bottom light up. I can touch those but nothing happens besides that it buzzes.... When I it boot the normal way again and use the option 'manage and restore backups' in CMW ROM manager, it shows that there has been made a backup. Not shure if I can trust it though....
When I open in HBOOT (1.09.0099) and push recovery the same thing happens. When I boot the normal way and try to boot into recovery trough CWM ROM manager same thing happens again.
I saw a other topic http://forum.xda-developers.com/showthread.php?t=1213229&page=2 i tried to flash this recovery to see if a older version might work, but now i have got a problem flashing... See picture: View attachment 1031874. Anyway that is not my main problem, what i really want to make it clear: is to back up my stock ROM.
Many thanks in advantage!

wait for device，you boot your phone to fastboot，and is works
---------- Post added at 09:43 AM ---------- Previous post was at 09:40 AM ----------
I think your hboot is very high， you downgrade it to 1.030000 may be works.

Hey pal if I was you I wouldn't use rom manager, I've known it to have issues over both wildfires. Turn off your phone the normal way. Pull out the battery for 10-20 seconds or so, put it back in and hold volume down + power. Once your hboot is finished scanning the sdcard scroll down to recovery and select it with power. You should go into clockwork mod. Then scroll again with the rockers down to backup and hit it you can do as many backups as your sdcard will carry. So do that and you should have one you can trust. Also before you install your new custom rom read the main page throughout to see if it needs set up in any specific way, like with a special sdcard partition or something. And most important don't forger to wipe your cache, dalvik cache and factory reset the Device from clockwork mod recovery ! This will avoid bootloops good luck
sent from my android powered beast!

It would be best if you were to ask in the Wildfire S forum...just saying.

Downgrade HBOOT will downgrade Android?
gq455402012 said:
wait for device，you boot your phone to fastboot，and is works
---------- Post added at 09:43 AM ---------- Previous post was at 09:40 AM ----------
I think your hboot is very high， you downgrade it to 1.030000 may be works.
Click to expand...
Click to collapse
Hey, I'm would like to try this but when i searched for a tutorial one said: "In this tutorial, I will show you how to downgrade Any HBOOT and Radio to "around" HBOOT 1.03.001 and Radio 7.48.36.1 or less with S-ON. How amazing is that!
Disclaimer: I am not responsible for any damage that you bring to your android device! This will Downgrade you to Android 2.3.3!" Found in: http://forum.xda-developers.com/showthread.php?p=25255527
As it says i will downgrade my android aswell, this does not work for me because my main goal is to back up my stock ROM. correct me if i'm wrong.

heavy_metal_man said:
Once your hboot is finished scanning the sdcard scroll down to recovery and select it with power. You should go into clockwork mod. Then scroll again with the rockers down to backup and hit it you can do as many backups as your sdcard will carry.
Click to expand...
Click to collapse
Hey Thanks!
As you can read,
When I open in HBOOT (1.09.0099) and push recovery the same thing happens.
Click to expand...
Click to collapse
i tried to get into recovery trough HBOOT already.
The other tips are usefull

Try booting to recovery via adb or terminal emulator.In both cases the code is
su
reboot recovery
Sent from my Optimus Me using xda premium

Your bootloader cannot be the issue. Go to here. And try there install recovery options. Also what happens if you cold boot the device with volume up + power?
http://forum.xda-developers.com/showthread.php?t=1325730
[INDEX] roms/recovery/guides/kernel/root/...
sent from my android powered beast!

adb reboot recovery
nerot said:
Try booting to recovery via adb or terminal emulator.In both cases the code is
su
reboot recovery
Sent from my Optimus Me using xda premium
Click to expand...
Click to collapse
Tried booting via adb but it says: error: device not found.
This is weird because i flashed recovery cmw just before and that worked perfectly fine... SDK works fine as far as i know. su command doenst work either.

install recovery options?
heavy_metal_man said:
Your bootloader cannot be the issue. Go to here. And try there install recovery options. Also what happens if you cold boot the device with volume up + power?
http://forum.xda-developers.com/showthread.php?t=1325730
[INDEX] roms/recovery/guides/kernel/root/...
sent from my android powered beast!
Click to expand...
Click to collapse
Ok thats good to know, about the bootloader so no downgrade?
What do you mean with intall recovery options? I can't find such a manual there...
Cold boot with volume up + power makes my device boot up as usual.
I tried to install
HTML:
http://forum.xda-developers.com/showthread.php?t=1213229
other version of cmw recovery, by following the guide instead of flashing. That gave me the following error.
CID incorret! Update fail! Press <power. to reboot.

ok how did you install your recovery to install super user? did you just use rom manager to do it? as far as i know it only installs a tempoary recovery. which would explain why you are only getting to it through rom manager. ok do you have adb installed onto your pc?
ok take the pg76img.zip attached to this post and put it on the root of your sdcard. then boot into bootloader (not fastboot) and your phone should say it found an update. flash it and it will install clockworkmod to your phone properly. then remove the pg76img.zip from your sdcard and boot back into bootloader, select recovery and with any luck you`ll be sorted. then follow my post above and you`ll be sorted pal
then, go to here and thank alquez for the recovery http://forum.xda-developers.com/showthread.php?t=1213229

samkuiper9 said:
Tried booting via adb but it says: error: device not found.
This is weird because i flashed recovery cmw just before and that worked perfectly fine... SDK works fine as far as i know. su command doenst work either.
Click to expand...
Click to collapse
If usb debugging isnt the problem then use terminal emulator from the phone itself, again with the the same lines.
Sent from my Optimus Me using xda premium

Terminal emulator: not permited
nerot said:
If usb debugging isnt the problem then use terminal emulator from the phone itself, again with the the same lines.
Sent from my Optimus Me using xda premium
Click to expand...
Click to collapse
Thanks, tried this but when i type in reboot recovery the terminal emulator says: not permited!
What to do?

samkuiper9 said:
Thanks, tried this but when i type in reboot recovery the terminal emulator says: not permited!
What to do?
Click to expand...
Click to collapse
Are you sure you typed in "su" before "reboot recovery"?

nejc121 said:
Are you sure you typed in "su" before "reboot recovery"?
Click to expand...
Click to collapse
Absolutely Super SU asked to grant permission and i did..

freezing emulator
samkuiper9 said:
Tried booting via adb but it says: error: device not found.
This is weird because i flashed recovery cmw just before and that worked perfectly fine... SDK works fine as far as i know. su command doenst work either.
Click to expand...
Click to collapse
Sorry made a mistake here, i tried to use adb commands while in hboot. When i tried it when the phone was on as usual i could use SU command and the # logo showed up bit than my terminal froze and i couldn't write anything else.
Than i tried it again this time only using the commands as follows:
cd c:\android
adb shell
su
reboot recovery
Difference is that the first time i typed: adb shell su. all together this freezes it up...
Anyhow it sitll doens't work.. i get an empty line in cmd, thats all..View attachment 1033568
But this could be because now a flash of a recovery img doens't work it gives: Waiting for device...

heavy_metal_man said:
ok how did you install your recovery to install super user? did you just use rom manager to do it? as far as i know it only installs a tempoary recovery. which would explain why you are only getting to it through rom manager. ok do you have adb installed onto your pc?
Click to expand...
Click to collapse
I didn't use rom manager, i used a recovery img from CWM: ahttp://download.clockworkmod.com/recoveries/nd flashed it with sdk, trough cmd promt. So yes adb files are in place and working.
heavy_metal_man said:
ok take the pg76img.zip attached to this post and put it on the root of your sdcard. then boot into bootloader (not fastboot) and your phone should say it found an update. flash it and it will install clockworkmod to your phone properly. then remove the pg76img.zip from your sdcard and boot back into bootloader, select recovery and with any luck you`ll be sorted. then follow my post above and you`ll be sorted pal
then, go to here and thank alquez for the recovery http://forum.xda-developers.com/showthread.php?t=1213229
Click to expand...
Click to collapse
In my last quote i posted the link of the exact same file. So this didn't work either, same error.. Thanks anyway.

Why don't you try reflashing the recovery via fastboot flasher?It worked for me when I screwed up and flashed the wrong recovery
Sent from my Optimus Me using xda premium

Hmm. Fastboot flasher sounds like your best bet then.
sent from my android powered beast!

try this one
OK，use this one one-click flash recovery5.026 in the attachment. .just download and then decompression to anywhere，connect your phone to computer with ADB driver，and then found runme.bat，and automatic to flash recovery.when finished you can see recovery on your phone like the picture in the attachment.

[Q] No TWRP, using AOKP.

I flashed AOKP earlier today using TWRP, in the process I accidently removed TWRP I guess. I get the normal stock kindle fire logo on boot that then changes into Team Kangs logo and boot fine. I wanted to try another ROM, but I can't figure out how to do this now. ADB says it recognizes my device but after I try and install like Burritoroot3 it says device not recognized, I have to exit the shell and go back in but it does the same thing over and over. Any help or direction would be awesome. Thanks

while in the aokp rom hold down your power button and when it gives you the shutdown menu choose reboot and then choose recovery and see if that does anything.

its very unlikely that that flashing aokp removed twrp.img and fff in aokp you can reboot to recovery select reboot and then select the recovery option this should take you to twrp

I do not get an option to go into recovery. I think I do not have a recovery tool. No TWRP or FFF. It gets the default splash screen like from the riginal OS, then Loads AOKP M5 I think. When connected to adb on command prompt the device id is 01234ABCDE

Thank you both for your help. I finally got the KF to be recognized in the KindleFireUtility and installed twrp and FFF from there. All is well. Thanks again.

no problem man

something about your situation strikes me as very strange your recovery and or bootloader just dont go missing lol broken yes missing no unless you did something to try to manually remove it glad you got it fixed easily

I am glad you got it fixed but I am not sure how that would even be possible...
Sent from my Galaxy Nexus using Tapatalk 2

Dunno that it is system bootloader and recovery are all on seperate partitions

Also fyi, you can get a terminal emulator and type su then type reboot recovery to get into recovery
Sent from my Amazon Kindle Fire using xda app-developers app

[Q] Boot loop on firefirefire as i try to enter recovery

Title basically says it all however here is the long rundown. so I installed twrp and fff using kfu. Everything but the recovery mode boots fine. Using normal boot mode it will go right into the regular kindle and load up so that I can access apps books movies etc. However when I try to enter recovery mode using either the kfu bootmode menu or the fff boot menu on the kindle itself it gets stuck in a boot loop on the fff boot screen. I don't 'need' the recovery part but it would be nice to have especially if I screw something up. Any help would be appreciated.

mike.anderson457 said:
Title basically says it all however here is the long rundown. so I installed twrp and fff using kfu. Everything but the recovery mode boots fine. Using normal boot mode it will go right into the regular kindle and load up so that I can access apps books movies etc. However when I try to enter recovery mode using either the kfu bootmode menu or the fff boot menu on the kindle itself it gets stuck in a boot loop on the fff boot screen. I don't 'need' the recovery part but it would be nice to have especially if I screw something up. Any help would be appreciated.
Click to expand...
Click to collapse
What recovery are you using? (version, build, etc.)

soupmagnet said:
What recovery are you using? (version, build, etc.)
Click to expand...
Click to collapse
umm TWRP 2.6.3.0 touch recovery I think as it says install latest twrp recovery and I am using kfu 0.9.9. I am sorry if I am being a complete idiot and missing something important.

mike.anderson457 said:
umm TWRP 2.6.3.0 touch recovery I think as it says install latest twrp recovery and I am using kfu 0.9.9. I am sorry if I am being a complete idiot and missing something important.
Click to expand...
Click to collapse
Try installing COTR and see if you get the same result

soupmagnet said:
Try installing COTR and see if you get the same result
Click to expand...
Click to collapse
should / can i remove the twrp files before i do that?

mostly wondering because i looked at the cotr page and it said to upgrade you must delete the settings.ini file. Now i know i am not upgrading from a previous version of the recovery however could just installing cotr cause a software conflict with twrp?

I don't know why twrp would not be fine. Are you sure the file you installed was a good download? You may simply need to redownload/reinstall twrp.
Sent from my GT-p511x

mike.anderson457 said:
mostly wondering because i looked at the cotr page and it said to upgrade you must delete the settings.ini file. Now i know i am not upgrading from a previous version of the recovery however could just installing cotr cause a software conflict with twrp?
Click to expand...
Click to collapse
No. By flashing a new recovery, the partition is completely overwritten. The only things that remains are the files saved to the sdcard. TWRP files on the sdcard have no effect on those for COTR and vice versa. The 'settings.ini' for COTR is located on the sdcard, which is why it needs to be deleted when upgrading.

sharonbw said:
I don't know why twrp would not be fine. Are you sure the file you installed was a good download? You may simply need to redownload/reinstall twrp.
Sent from my GT-p511x
Click to expand...
Click to collapse
i re-downloaded the kfu file 3 times and re installed twrp twice each i am reasonably sure that everything is fine unless the upload from this site is somehow corrupted
soupmagnet said:
No. By flashing a new recovery, the partition is completely overwritten. The only things that remains are the files saved to the sdcard. TWRP files on the sdcard have no effect on those for COTR and vice versa. The 'settings.ini' for COTR is located on the sdcard, which is why it needs to be deleted when upgrading.
Click to expand...
Click to collapse
aah okay... thank you both for helping with my problem and with clarification i really appreciate it.
did as suggested with same result no access to recovery but it still boots fine to the normal ui

[Q] HELP! Stuck in TWRP boot loop!

Howdy Everyone,
So just tried rooting my new m8 and now I'm stuck endlessly booting into TWRP. I thought I did everything correctly: Unlocked the bootloader, installed the USB drivers, installed the ADB fastboot drivers and then flashed twrp 2.7.0.3. I get to the the htc logo screen/warning and, bam, back to twrp everytime.
Does anyone know how to fix this??? The last time i was rooting and installing custom mods was back in samsung galaxy s2 days, so my knowledge is a little dated. Please help!!

Try flashing the recovery again. Download it from the link provided here and confirm the md5 checksum for the zip file.
http://forum.xda-developers.com/showthread.php?t=2694564
Sent from my HTC One_M8 using XDA Premium 4 mobile app

PirateP3t3 said:
Howdy Everyone,
So just tried rooting my new m8 and now I'm stuck endlessly booting into TWRP. I thought I did everything correctly: Unlocked the bootloader, installed the USB drivers, installed the ADB fastboot drivers and then flashed twrp 2.7.0.3. I get to the the htc logo screen/warning and, bam, back to twrp everytime.
Does anyone know how to fix this??? The last time i was rooting and installing custom mods was back in samsung galaxy s2 days, so my knowledge is a little dated. Please help!!
Click to expand...
Click to collapse
some reason doing twrp from terminal on hte m8 gets us stuck (it did for me at least.)
just reflash the insecure boot image.. fastboot flash boot blah.img
that should get you back up

PirateP3t3 said:
Howdy Everyone,
So just tried rooting my new m8 and now I'm stuck endlessly booting into TWRP. I thought I did everything correctly: Unlocked the bootloader, installed the USB drivers, installed the ADB fastboot drivers and then flashed twrp 2.7.0.3. I get to the the htc logo screen/warning and, bam, back to twrp everytime.
Does anyone know how to fix this??? The last time i was rooting and installing custom mods was back in samsung galaxy s2 days, so my knowledge is a little dated. Please help!!
Click to expand...
Click to collapse
I encountered this issue as well. I'm almost certain that when you were flashing recovery, you used this command "fastboot flash boot recovery.img".
The right command should be "fastboot flash recovery recovery.img".
To rectify the issue look for a tread that has the boot.img for your specific M8 model and flash boot back using " fastboot flash boot boot.img".
This should fix the issue you are having

darll said:
I encountered this issue as well. I'm almost certain that when you were flashing recovery, you used this command "fastboot flash boot recovery.img".
The right command should be "fastboot flash recovery recovery.img".
To rectify the issue look for a tread that has the boot.img for your specific M8 model and flash boot back using " fastboot flash boot boot.img".
This should fix the issue you are having
Click to expand...
Click to collapse
Forgot to come back and update this thread, but this is exactly what I did and it worked!!! Now happily rooted and running.
Thanks for the help!

PirateP3t3 said:
Forgot to come back and update this thread, but this is exactly what I did and it worked!!! Now happily rooted and running.
Thanks for the help!
Click to expand...
Click to collapse
I followed the instructions on the TWRP site:
Download the above file. Save it to the root of your /sdcard directly (internal memory only) and rename it to twrp.img
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43
Then reboot to complete installation.
But that left me in a TWRP bootloop. Can you please give me step by step instructions on how to get out of this bootloop?
Thanks!

First off, being a noob and using dd without even knowing what partiton you're writing to is extremely dangerous.
Just use fastboot.
plug phone into PC in fastboot mode.
Code:
fastboot flash recovery twrpfilename.img
fastboot erase cache
on phone go back to hboot, select, recovery
In TWRP go to wipe, then swipe for a factory reset (Advanced wipe cannot properly wipe cache and dalvik after fastboot erase cache)
then go to advanced, select cache, dalvik and system and swipe to wipe those partitions.
then go to install, select the rom on your phone and flash. follow on screen instructions.
If you don't have the rom on your phone for whatever reason,
connect your phone, while in TWRP to your PC then, using adb on your PC
Code:
adb push romfilename.zip /sdcard/
Wait until it completes with bytes sent.
Then flash using method listed above.
Be careful if you want to keep your phone. I stress this, if you don't know what a command you are issuing does, exactly, DO NOT DO IT until you look it up and understand what you are doing. There is great risk even when you know what you're doing. There's a LOT more when you don't.

exad said:
First off, being a noob and using dd without even knowing what partiton you're writing to is extremely dangerous.
Just use fastboot.
plug phone into PC in fastboot mode.
Code:
fastboot flash recovery twrpfilename.img
fastboot erase cache
on phone go back to hboot, select, recovery
In TWRP go to wipe, advanced, select cache, dalvik and system
then go to install, select the rom on your phone and flash. follow on screen instructions.
If you don't have the rom on your phone for whatever reason,
connect your phone, while in TWRP to your PC then, using adb on your PC
Code:
adb push romfilename.zip /sdcard/
Wait until it completes with bytes sent.
Then flash using method listed above.
Be careful if you want to keep your phone. I stress this, if you don't know what a command you are issuing does, exactly, DO NOT DO IT until you look it up and understand what you are doing. There is great risk even when you know what you're doing. There's a LOT more when you don't.
Click to expand...
Click to collapse
Thanks for the detailed instructions. I opened fastboot on my PC with phone plugged in and entered the code but the cmd prompt just says <waiting for device>

Do you have the HTC drivers installed on your PC with HTC sync uninstalled?
Does it say fastboot USB on your phone?
Sent from my HTC One_M8 using xda app-developers app

Update: I ended up just installing the Viper ROM and the system rebooted fine. It's strange that I couldn't reboot the device to get out of recovery without having to install a custom ROM.
Sent from my HTC6525LVW using Tapatalk

No it's not. You flashed recovery to the boot partition.
Sent from my HTC One_M8 using xda app-developers app

How do i fix TWRP Bootloop on my HTC explorer a310e... ?
How do i fix TWRP Bootloop on my HTC explorer a310e... ?
I hav custom cm11 Kitkat ROM installed on it...
but after I installed the rom, and again tried to reboot
into TWRP recovery, it is just stuck on the blue color
TEAMWIN screen... Please help how to fix it...!

HELP PLEASE
I pressed factory reset on my cm13 rom htc one m8 with twrp and now its just stuck flashing the teamwin logo and i cant do anything, i tried using fastboot but it cant see the device.

Maxxour said:
HELP PLEASE
I pressed factory reset on my cm13 rom htc one m8 with twrp and now its just stuck flashing the teamwin logo and i cant do anything, i tried using fastboot but it cant see the device.
Click to expand...
Click to collapse
You need cwm recovery to factory reset from cm roms.
Also you need to be in FASTBOOT mode for it to detect your device.
Boot to fastboot, erase cache, reinstall twrp.
Next time reset/wipe from recovery.

ashyx said:
You need cwm recovery to factory reset from cm roms.
Click to expand...
Click to collapse
cwm recovery or cm recovery?

[Q] Bricked after accidentally flashing older stock firmware

Ok so to start this was my first time roots and putting a custom os on an android device. It's a first gen kindle fire the firmware originally on it was 6.3.3. I rooted it using safe root with success. I then proceeded to install TWRP and that worked with out an issue. I basically followed lthis tutorial. I then booted into TWRP and cleared the cache then did a factory reset. I then install the newest version of CM 11 without issue then proceeded to install gaaps for it but it failed I figured it wouldn't matter (dumb thing to think). Then i rebooted it got stuck at the boot logo so i figured i messed up a step so I figured I'd just start from scratch just to be safe. I went back into TWRP and cleared all the caches and did a factory reset and installed the os from amazons website which i thought was the same firmware as before (6.3.3) but I later found out it was 6.2.1 and rebooted and got stuck at the boot logo again but this time there was no TWRP to boot into which is where I am stuck now. Windows picks it up as kindle in the device manager adb can pick it up too. I figured I'd try rooting it again all the commands it does fails because /system/bin/sh doesn't exist. Then it reboots and says something has deleted su looking for backup copy then says the back up is gone too and it can't recover. I then tried putting it into fastboot mode again with the commands and no luck it says /system/bin/sh doesn't exist so I can't do that. Im stumped now couldn't find anything through googling and searching the forums. Is my kindle bricked?

Think you need a fastboot cable
Sent from my XT907 using Tapatalk

sd_shadow said:
Think you need a fastboot cable
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
alright I was hoping I didn't have to. Is there any good places to buy it from other than ebay that ship to canada?
Edit: Nevermind I decided just to go to ebay. Thanks for the help.