Related
My recovery image seems to be messed up since I can't boot into it. My phone will boot but everytime it does ADW crashes over and over not allowing me to do anything. What can I do to go about getting the recovery fixed again and reflashing to try to smooth everything out?
*Edit*.I think I may have thought of a work around. I emailed my self the launcherpro.apk and installed it through gmail. Now I can access my phone. Now I just need to flash a working recovery..
I do appreciate your help though Riley.
You can try downloading ADW Launcher, putting it on your SD card and boot from recovery, then flash the launcher. It is a far shot, but if launcher is the only problem, maybe reflashing it will do the trick.
** EDIT ** My apologies. I misunderstood. I thought you were referring to a corrupted recovery image that you had made of your ROM!
You say you can't boot into recovery/ what's your phone do or say when trying to boo4 in recovery? You may have to push new recovery image via fastboot.
CGriffiths86 said:
My recovery image seems to be messed up since I can't boot into it. My phone will boot but everytime it does ADW crashes over and over not allowing me to do anything. What can I do to go about getting the recovery fixed again and reflashing to try to smooth everything out?
Click to expand...
Click to collapse
If you have USB debugging turned on you can flash Amon_RA via an adb shell using the flash_image tool - exactly the way the original Eris rooting process worked. With your phone looping, it will run very slowly, but will still succeed.
If you have the S-OFF bootloader installed, you can flash the recovery with fastboot.
I'll have an XDA admin move this thread to the Q&A forum.
Ok guys..I got launcher pro installed so I can actually access my phone now. I attempted to Flash a recovery with Rom Manager and it says it succeeds but it will never boot into it. I do have the bootloader with the "off". Is there a market app or something that can easily flash the recovery? I only ask because I am not at my PC with the android sdk stuff.
CGriffiths86 said:
Ok guys..I got launcher pro installed so I can actually access my phone now. I attempted to Flash a recovery with Rom Manager and it says it succeeds but it will never boot into it. I do have the bootloader with the "off". Is there a market app or something that can easily flash the recovery? I only ask because I am not at my PC with the android sdk stuff.
Click to expand...
Click to collapse
If you can't get to a PC to use adb, you could use a root shell in a terminal emulator to flash recovery using flash_image. That's kind of painful/tedious though - almost enough so to make it worth your while to just wait until you get back to your PC.
It is technically feasible to put together a flashable ROM to re-flash the recovery, but I'm not aware of anyone having done so for the Eris.
Oh ok..well I have RA Eris 1.6.2 recovery on my sd card. So I can just flash it via the termninal emulator, right?
** I tried to install via terminal and it says "header is the same, not flashing recovery". Do you think I could install the stock Eris recovery and reflash Amon's?
UPDATE!!: I got a recovery to flash..YAY..thanks guys
CGriffiths86 said:
Oh ok..well I have RA Eris 1.6.2 recovery on my sd card. So I can just flash it via the termninal emulator, right?
** I tried to install via terminal and it says "header is the same, not flashing recovery". Do you think I could install the stock Eris recovery and reflash Amon's?
Click to expand...
Click to collapse
are you using "flash_image"? If so, where is it from? To my knowledge (the statically linked version from Amon_RA - /sbin/flash_image) is a pretty simplistic program - it performs no checks, and will let you flash total garbage to any named partition on your phone. (Which is why you should verify the md5 of the recovery image before you flash it, BTW; you can use the AFV app for that)
so I have the latest software, used the HTC unlock method, was rooted and had the TWRP recovery working just fine, I'm an idiot and flashed the CM recovery through RM and of course it didn't work, so I've tried every which way I can find to re-flash the TWRP and even tried flashing AMON but it will not go into recovery with any of them after it says it successfully wrote the recovery.
TWRP and CM just wait for a minute then reboot normal, AMON reboots then sits at the HTC screen... forever and i have to pull the battery.
I tried uninstalling RM to see if it was F'ing with it, didn't matter.
not sure what to try next to get a working recovery back onto the phone, I'm still rooted just running the stock ROM, I had loaded an alternate ROM successfully last week, just didn't like it. So I know all is 'working' as expected I just F'd up the recovery part now
any help??
afaik if you used the HTC unlock you need to fastboot flash it, or maybe hboot zip it? What have you tried so far?
I've tried using fastboot to flash amon and TWRP, same result
tried doing TWRP as a zip as well
what's weird is each method seems to "work" i get that it's pushing, writing, completed, no errors with any of them but then it just won't go into recovery and if i change to different recoveries I get different reboot behaviors just none of them work.
that's where I'm stuck, I feel like I've tried all the methods it just refuses to actually go into recovery when it's loaded.
another thing I thought was weird though, when I reflashed TWRP, and then go into RM it would say at the top that I had the latest version of CM installed like it didn't take? I uninstalled RM and tried it all again, same result.
morellox said:
I've tried using fastboot to flash amon and TWRP, same result
tried doing TWRP as a zip as well
what's weird is each method seems to "work" i get that it's pushing, writing, completed, no errors with any of them but then it just won't go into recovery and if i change to different recoveries I get different reboot behaviors just none of them work.
that's where I'm stuck, I feel like I've tried all the methods it just refuses to actually go into recovery when it's loaded.
another thing I thought was weird though, when I reflashed TWRP, and then go into RM it would say at the top that I had the latest version of CM installed like it didn't take? I uninstalled RM and tried it all again, same result.
Click to expand...
Click to collapse
*my opinion*
delete rom manager
boot into recovery using adb
"adb reboot recovery"
or terminal emulator
"reboot recovery"
or the app "quickboot"
does that work?
I've tried all those except Quickboot... *trying now......*
annnnnd
same thing with the app...
I'm thinking at this point I almost need to just write everything over again? use a flashable zip in the bootloader and just have it write everything over again, I was going to do a new rom anyways bored with the stock again.
so I need to find that I guess? re-write everything go back to fresh and start over
1. Make sure u r not flashing CDMA recovery over a GSM device, or vice versa.
2. How did u get ur device rooted in the first place?
3. Last resort, relock ur device and apply the correct RUU, then unlock and root again.
Sent from my HTC EVO 3D X515m using XDA App
1) good there
2) I followed a tutuorial where I pushed the recovery and the SU file after doing the HTC official unlock method, worked great at first, I'm the idiot that pushed the CM recovery over top of it and now I can't get a working recovery back on.
3) do I really have to relock first, I've seen the simple tutorial on doing so, I was hoping maybe I could find an all in one flashable ROM that would at least get me back to operational on all partitions and then re-work that one with a new ROM later or something, not possible?
This is of no help to you but - I had the same error. TWRP v1.0.3. I tried everything in the book to get it to work... but got stuck at the HTC splash screen like you. And I tried installing the 1.13 PG86IMG and then my device turned off while installing the PG86IMG (it was fully charged during flashing, I checked). Be careful with what you do.
I was unlocked with AlphaRev's tool, running my own ROM.
mine hung like that if i flashed AMON, but i could still pull the battery and go back into the bootloader to flash at least TRWP using FastBoot so I could get back into the phone
ugh
morellox said:
mine hung like that if i flashed AMON, but i could still pull the battery and go back into the bootloader to flash at least TRWP using FastBoot so I could get back into the phone
ugh
Click to expand...
Click to collapse
htc unlock method has proven to be a bit shady for the community in that it doesnt allow all the features/functions the revolutionary (and prior unrevoked) unlock method does.
most developers unlocked with revolutionary and haven't performed the htc unlock method so it has been hard to gather technical details on the htc unlock method.
one item we can eliminate in the effort to narrow down your issue: there is no working Amon RA recovery for the EVO 3D. not sure where you obtained Amon RA recovery. TWRP was created to pick up the torch from the Amon RA recovery as he retired from developing his recovery to support emmc devices.
stick to either flashing the twrp or cwm recovery images. there are only a handful of ways to load a custom recovery and only a handful of ways to boot the device into recovery mode.
i'd follow a logical pattern and work your way through the avaiable options. by following the available options one step at a time you should be able to narrow down which methods work and don't work. sorry it has been difficult as this htc unlock method is newer to the community we aren't as familiar with it as we are the revolutionary method.
ways to flash a custom recovery:
1) fastboot - fastboot flash recovery c:\downloads\recovery.img
2) bootloader - PG86IMG.zip file containing recovery.img and android-info.txt
3) flash_image - while in normal android mode (my app Flash Image GUI works well for this)
ways to boot into recovery mode:
1) turn device completely off and unplug USB. vol down + pwr loads bootloader. select recovery from the menu
2) from android mode: adb shell reboot recovery
3) from android mode: use a 3rd party app like quick boot.
this is all off the top of my head so it might not be an *exhaustive* list but it should cover all the common approaches. hope that helps and keep us updated! good luck!
damn...
I really appreciate everyone's help here I've been a part of various forums for a REALLY REALLY long time... from the days of Nextel, then I was a Palm Lover for a few years and now Android.
this obviously isn't urgent as my phone is working just fine, I just can't flash a new ROM since I can't get any recoveries working.
unfortunately I'm pretty sure I've tried all the methods listed above, I'm going to probably sit down sometime this weekend and systematically go through each method one more time just to be sure. TWRP worked for me just fine in the beginning, I flashed a ROM more than once, reverted back to my old ROM, made back ups, cleared cache's all the stuff I'd need to do.
thanks everyone, I'll keep trying
and no one knows of a flashable 'rom' that would have all the different partitions included in a zip or something like that? like.... what is in place of recovery in a stock phone? I can always unroot and start over but I did use the HTC unlock method so I hope that even works
got one to work! followed this method
http://forum.xda-developers.com/showthread.php?t=1239455
hi.
i have never had problems with my hero before but suddenly i'm unable to flash anything on it. i have always been on the stock recovery with S-OFF and rooted.
i flashed VanillaEclair 6.2 a while back and had no problems.
yesterday when i tried to flash another rom, i got signature verification error. I thought i'd flash TWRP or CWMR to bypass the signature verification but when i tried to flash it, i got the same error.
i tried to flash the recovery through rom manager but it failed...even with adb!
frustrated, i thought to use the official rom RUU...i ran the RUU, it went halfway in flashing the rom and then gave error.
now i don't have any recovery and pressing 'home+power' leaves me at the HERO screen forever.
luckily i can still boot in android so my device is not bricked.
I have tried pushing the recovery via adb but even the fastboot doesn't work.
i tried starting from scratch to check for the bootloader lock. fastboot oem get_identifier_token returns an error.
phone is working fine but i don't like the rom and want to be able to flash via custom recovery.
please help!
much appreciated.
http://wiki.cyanogenmod.com/wiki/HTC_Hero_(GSM):_Full_Update_Guide Check the installing a custom recovery page, use the FLASH_IMAGE method
I have the castor windy version 16gb SGP511. I was previously rooted but not unlocked. I unlocked the boot loader. Installed the twrp image on the pac man thread which i think was dual recovery cause Philz,Cwm came out, so I can install lollipop version of the rom. Made a backup of the stock rom. Followed this instructions - Install the Lollipop ROM + GApps+SuperSU using whatever Recovery you have.
- Turn off device completely.
- Press <Volume Up> and plug USB cable.
- LED should turn blue.
- Send command: "fastboot erase recovery"
- Send command for Castor_Windy: "fastboot flash recovery TWRP_Castor_Windy.img"
- Send command for Castor: "fastboot flash recovery TWRP_Castor.img"
- Unplug USB cable.
- Device will reboot.
- When LED turns pink press <Volume Up> and <Volume Down> several times.
- You should now see TWRP
I wasnt fast enough so stock rom booted. I used Adb reboot recovery to access recovery and did as the above mentioned. Wiped i tried to install the rom which failed. Rebooted back to system and got stuck in Sony boot up screen. I can access fastboot. Read though the forums I have to find a ftf or a system image file and use a flash tool. What ftf file or system image my I use use which will let me root my device again.
Thanks Steve
Kamaleon said:
What ftf file or system image my I use use which will let me root my device again.
Thanks Steve
Click to expand...
Click to collapse
Try this Xperia downloader tool. Should let you see which versions are which. If you want an easy root, then stay away from the KitKat builds, unless you want to unlock bootloader.
http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
Use Flashtool to flash your downloaded ftf file. Just make sure your device is charged.
http://forum.xda-developers.com/showthread.php?t=2335555
I believe flashtool will even install the drivers for your 511
Thanks for the reply. Flashed ftf file and my tablet is up an running. Do I have to unlock my bootloader again or is it unlocked already?
Kamaleon said:
Thanks for the reply. Flashed ftf file and my tablet is up an running. Do I have to unlock my bootloader again or is it unlocked already?
Click to expand...
Click to collapse
Well, now this depends.
If you previously had KK running, and flashed a original version JellyBean ROM, then it probably locked the bootloader again.
If you flashed the same version as you had previously installed, then it didn't lock it again.
Moscow Desire said:
Well, now this depends.
If you previously had KK running, and flashed a original version JellyBean ROM, then it probably locked the bootloader again.
If you flashed the same version as you had previously installed, then it didn't lock it again.
Click to expand...
Click to collapse
Thanks. Yes i was unlocked already, went through the process again to verify. Trying to upgrade my firmware which is 17...........402. to a kk build firmware. I have the old cwm recovery 6.0.4.6. being trying to upgrade or even change recovery to any recovery except dual recovery. Through fastboot which none of them stick. Fastboot erase recovery
fastboot flash recovery recovery.img all of them(CWM,TWRP,PHILZ). The process goes smoothly but when I access recovery the old recovery comes up. What seems to be problem? I cant change my recovery or even upgrade it. I never have had this problem before some insight needed before i take a wrong turn. LOL.
Kamaleon said:
Thanks. Yes i was unlocked already, went through the process again to verify. Trying to upgrade my firmware which is 17...........402. to a kk build firmware. I have the old cwm recovery 6.0.4.6. being trying to upgrade or even change recovery to any recovery except dual recovery. Through fastboot which none of them stick. Fastboot erase recovery
fastboot flash recovery recovery.img all of them(CWM,TWRP,PHILZ). The process goes smoothly but when I access recovery the old recovery comes up. What seems to be problem? I cant change my recovery or even upgrade it. I never have had this problem before some insight needed before i take a wrong turn. LOL.
Click to expand...
Click to collapse
You mean the "factory" recovery comes up.
Well, just for info, you don't need to run the fastboot "erase" command when installing a recovery. Not necessary as the new image file will overwrite the existing.
Also, you don't exactly need to flash a recovery either. You can connect via USB, boot to bootloader, and run the "fastboot boot recovery.img (or whatever you named it) as long as your custom recovery is in the same folder as the fastboot.exe. This will just the custom recovery without installing it, thus allowing you to flash stuff.
As to why your fastboot flash isn't sticking, I'm new to the Sony tab, so haven't learned all the quirks yet as compared to Acer tabs.
Moscow Desire said:
You mean the "factory" recovery comes up.
Well, just for info, you don't need to run the fastboot "erase" command when installing a recovery. Not necessary as the new image file will overwrite the existing.
Also, you don't exactly need to flash a recovery either. You can connect via USB, boot to bootloader, and run the "fastboot boot recovery.img (or whatever you named it) as long as your custom recovery is in the same folder as the fastboot.exe. This will just the custom recovery without installing it, thus allowing you to flash stuff.
As to why your fastboot flash isn't sticking, I'm new to the Sony tab, so haven't learned all the quirks yet as compared to Acer tabs.
Click to expand...
Click to collapse
I mean cwm recovery v6.0.4.6 comes up the one I installed Doomlords thread with the advanced kernel. I ran fastboot erase recovery command to see if the new recoverys would stick and replace it but it didn't. I have done your instructions before hand thats how I am accessing the bootloader. "fastboot boot recovery.img all add this command to see If the new recovery would pop up. Thanks for the reply.
Kamaleon said:
I mean cwm recovery v6.0.4.6 comes up the one I installed Doomlords thread with the advanced kernel. I ran fastboot erase recovery command to see if the new recoverys would stick and replace it but it didn't. I have done your instructions before hand thats how I am accessing the bootloader. "fastboot boot recovery.img all add this command to see If the new recovery would pop up. Thanks for the reply.
Click to expand...
Click to collapse
Well, here's what I think is going on.
1. You installed Doomlords kernel. Note that this is a foto-kernel, which means the kernel itself has a partition that contains a recovery. What this means, is that as long a the fota-kernel was not replaced, then that specific recovery will be there.
2. You flashed a normal recovery. Now, I think this is there, but because of the fota-kernel, the fota-kernel is taking precedence.
Like I said, I don't know a lot about this Sony tab and the different partitions,as they are different from other tablets I am familiar with.
What puzzles me, is that if you flash a new "ftf" without changing any options in Flashtool, it "should" rewrite "every" partition on the tab, and install Stock recovery.
Now, based on my experience with Acer A500x and A700x tablets, I can say there are times when your issue happens. Rare, but it does happen. Things say they flash ok, but the old stuff still remains. The only option at that point, was to go back to a totally original version of the firmware.
Not sure I'm helping you on this. But the good thing, is that you can Fastboot Boot Recovery.
MD
Moscow Desire said:
Well, here's what I think is going on.
1. You installed Doomlords kernel. Note that this is a foto-kernel, which means the kernel itself has a partition that contains a recovery. What this means, is that as long a the fota-kernel was not replaced, then that specific recovery will be there.
2. You flashed a normal recovery. Now, I think this is there, but because of the fota-kernel, the fota-kernel is taking precedence.
Like I said, I don't know a lot about this Sony tab and the different partitions,as they are different from other tablets I am familiar with.
What puzzles me, is that if you flash a new "ftf" without changing any options in Flashtool, it "should" rewrite "every" partition on the tab, and install Stock recovery.
Now, based on my experience with Acer A500x and A700x tablets, I can say there are times when your issue happens. Rare, but it does happen. Things say they flash ok, but the old stuff still remains. The only option at that point, was to go back to a totally original version of the firmware.
Not sure I'm helping you on this. But the good thing, is that you can Fastboot Boot Recovery.
MD
Click to expand...
Click to collapse
I started from zero again flashed ftf Firmware SGP511_17.1.1.A.0.402. Verfied that i was bootloader unlocked I still was. Used fastboot to flash Dooms Kernel, without a problem used cwm revovery to flash Supersu. Tried to upgrade my firmware with the prerooted rooms in thread flashed with out a problem but no difference was provided. Verified in settings and initial firmware stands (SGP511_17.1.1.A.0.402). Tried to flash CM12 got stuck on a bootloop. Fastboot flashed the boot img provided didn't work for me so I flahed Teslas rom Followed instructions provided
1. Make sure you have CWM installed and a working nandroid backup
2. Download the ROM.
3. Place the ROM on your SD-Card.
4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD
5. Reboot to recovery.
6. Wipe data-factory reset/cache partition/dalvik cache
7. Flash the ROM.
Flash went through but when I try to access recovery through the rom or adb recovery doesnt come up. The tablet just stays black on recovery screen and the tablets led turns yellow. I have adb access so went to access fastboot flashed different recoverys. None of them (flashed without a problem), work but if a flashed Dooms I have access to recovery again, but loose functionality of the rom it gets stuck on sony screen. I have to do the steps all over again without a working recovery. This has being a learning experience I am HTC guy so the process with sony products is new to me as well. So where do you think I should go on from here; flash a newer ftf or lock and unlock my bootloader again to see if something happens or just move on jajajajj . Anyways thanks a lot for your help.
Kamaleon said:
I started from zero again flashed ftf Firmware SGP511_17.1.1.A.0.402. Verfied that i was bootloader unlocked I still was. Used fastboot to flash Dooms Kernel, without a problem used cwm revovery to flash Supersu. Tried to upgrade my firmware with the prerooted rooms in thread flashed with out a problem but no difference was provided. Verified in settings and initial firmware stands (SGP511_17.1.1.A.0.402). Tried to flash CM12 got stuck on a bootloop. Fastboot flashed the boot img provided didn't work for me so I flahed Teslas rom Followed instructions provided
1. Make sure you have CWM installed and a working nandroid backup
2. Download the ROM.
3. Place the ROM on your SD-Card.
4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD
5. Reboot to recovery.
6. Wipe data-factory reset/cache partition/dalvik cache
7. Flash the ROM.
Flash went through but when I try to access recovery through the rom or adb recovery doesnt come up. The tablet just stays black on recovery screen and the tablets led turns yellow. I have adb access so went to access fastboot flashed different recoverys. None of them (flashed without a problem), work but if a flashed Dooms I have access to recovery again, but loose functionality of the rom it gets stuck on sony screen. I have to do the steps all over again without a working recovery. This has being a learning experience I am HTC guy so the process with sony products is new to me as well. So where do you think I should go on from here; flash a newer ftf or lock and unlock my bootloader again to see if something happens or just move on jajajajj . Anyways thanks a lot for your help.
Click to expand...
Click to collapse
Well, I'm not sure which route to take.
However, I will tell you what I have learned the other day.
I have the 521 with unlocked bootloader. Rooted with my own boot.img, flashed SuperSU using "flashboot boot recovery.img" (yeah, sometimes it doesn't show on the display, so it takes a few times).
Now, other day I was going to check out the new LyPop pre-rooted. Fastboot flash recovery recovery,img, and it won't boot it to recovery like it should. Like it's not flashed. Tried it a couple times. Now, I didn't install the dual recovery as I'm not sure how that kernel (boot.img) will interact with my current tabs OS. Not to mention I need it for my work until tomorrow. But strangely it sounds like the same issue you have.
This weekend I will investigate it. As for me, I will probably flash the Stock ftf lyPop build, and just root it using a modified boot.img.
One thing I do know, is flashing a custom recovery to the "recovery" partition, doesn't seem to work like it used to work on other devices. It seems the flashing to the "Fota kernel" partition seems to be the only method that works. This is what happens when you flash that dual recovery, or any recovery that has a boot image using "Fota". Probably explains why you can't get rid of it using "fastboot erase recovery". because it's erasing the wrong partition. Only flashing a full ftf gets rid of it, because the ftf has a new FotaKernel it flashes.
Eh, something like that. Will look at it this weekend.
No matter how I try to flash the TWRP recovery image to the recovery partition, TWRP gets replaced by the crappy stock recovery!! This is absolutely maddening!
Specifically, it seems that no matter what method to use to flash the TWRP recovery, it gets overriden by the stock loader when the phone reboots.
My bootloader is UNLOCKED and I've installed a custom rom just fine by using the command fastboot boot twrp.img to boot into the twrp image. This is the only way I'm able to use TWRP at all.
I've tried:
fastboot flash recovery twrp.img
Booting into TWRP, and flashing the image over the recovery partition
Flashify to flash the TWRP over the recovery partition from within the rom
Trying to flash cyangenmod's recovery from within the rom (was pretty desperate at this point..)
I've also tried many different versions of TWRP, I can boot into them just fine but none of them stick when I flash them to the recovery partition.
It always says it's successful when I try to flash it, I reboot into recovery, and it boots into the piece of crap EmUI stock recovery screen every time
Anyone have any pointers here? It's not the end of the world but it's pretty aggravating having a completely useless recovery if I'm not near a computer,.
Try using Flashify or Flashfire.
Sadly didn't work. It doesn't seem to matter how I flash the recovery, the bootloader replaces it with the stock recovery when it boots. I'll update the OP to clarify, but thank you
I am having same issue have you found a fix
Have you tried starting completely over? Like, downloading the official MM build (b331, C564D003) from Huawei (Assuming you're on L24)?
On the new, freshly installed ROM, make sure that USB Debugging is and enable OEM Unlock are on in the developer settings.
Then, try flashing this build of TWRP again.
Before rebooting, do a Cache/Dalvik Wipe.
Boot up into the stock rom, then use 'adb reboot recovery' to see what happens next. It should work...
Hi mate,
It'd be easier to help you if you could post a screenshot of your FASTBOOT screen. There will be a line that will say FRP=LOCKED/UNLOCKED something like this.
if it is locked,
you have to install stock rom & enable OEM unlock from setting.
Then relock the boot loader. Then again unlock the boot loader.
For myself, I unlocked my BL unofficially, & this problem occurred . I solved it this way...
Hope it helps.
Cheers!