Related
hi guys iive unlocked my evo with the htcdev mod and no problem has come out , bun i'm unable to run any recovery.
iìve tryed all cwm twrp and any i found on the site.
i try with fastboot method and abd, all say that the recovery vas written , no error but when i try to lunch recovery the phone show the htc logo stay 10/15 second then reboot the phone.
pls help me
Have you tried downloading the twrp pg86img.zip & make sure it's named PG86IMG.zip then put it on the root of you're sdcard, boot into bootloader and update that way?
CM powered EVO 3D, enough said.
luca73n said:
hi guys iive unlocked my evo with the htcdev mod and no problem has come out , bun i'm unable to run any recovery.
iìve tryed all cwm twrp and any i found on the site.
i try with fastboot method and abd, all say that the recovery vas written , no error but when i try to lunch recovery the phone show the htc logo stay 10/15 second then reboot the phone.
pls help me
Click to expand...
Click to collapse
when the device either hangs on the htc logo or reboots while on the htc logo, it means there is an issue with the actual kernel/ramdisk.
when dealing with a custom recovery, they should always boot without any issues. the best suggestion off the top of my head is to make sure if you're on the CDMA version, use the shooter recovery and if you're on the GSM version, use the shooteru version of the custom recovery.
otherwise, as suggested above, reflash the confirmed correct custom recovery for your device. there are a few ways to flash the custom recovery although, being you used the htc unlock method, regular custom recovery mode will not have write access to the boot/kernel partition.
if you're interested in loading any ROMs which come with kernels or separately flashing a custom kernel, there are essentially two complete methods:
1) use my Flash Image GUI app from normal android mode to flash the kernel. then flash the ROM from custom recovery.
2) use fastboot boot c:\android\cwm-recovery.img . this will temporarily boot the custom recovery and htc unlock will grant it write access to the kernel/boot partition. this command is different than fastboot flash recovery c:\android\cwm-recovery.img. the fastboot boot will temporarily boot into the custom recovery while fastboot flash will permanently write it into the recovery partition.
hope all the extra details make sense and helps!
Ummm.....Just my 2 cents, but it sounds as though the most basic possible problem has been overlooked here. You need to go into menu>settings>power and uncheck the "fast boot" box or do a battery pull, then try to boot into your bootloader to access recovery. With your phone completely powered down (fast boot unchecked or after battery pull), hold volume down and press power. That will put you in your bootloader with an option to boot recovery from there.
ok i'm a noob i've used thr shooter and not the shooteru cwm img, now all works
ty guys
Hello xda every I have an major problem I tried to flash an rom today via the rom manager app and cleared cache and others that was requires now I cannOt get into recovery mode it's just shows the htc logo and boots up regular but I can acres fastboot I'm on 1.50 s-on all help would be very appreciated other i I searched other threads to no avail
If you tried flashing a rom with a custom kernel through rom manager it won't work. You have to flash that through fastboot. You say that your phone "boots up regular" as in boots into android?
Sent from my PG86100 using XDA App
Sofocused504 said:
Hello xda every I have an major problem I tried to flash an rom today via the rom manager app and cleared cache and others that was requires now I cannOt get into recovery mode it's just shows the htc logo and boots up regular but I can acres fastboot I'm on 1.50 s-on all help would be very appreciated other i I searched other threads to no avail
Click to expand...
Click to collapse
Not all of your infmration is easy to follow or understand.
Essentially, if you're looking to flash a kernel or ROM (which many times also include a kernel), there are three basic methods (two seem the easier) with hboot 1.50 and htc's unlock method:
1) For Kernel Flashing: From Android mode, using my application, Flash Image GUI. Put the kernel .zip file on your sdcard, select from inside the application and flash.
If flashing a ROM, pull out the kernel file (usually named boot.img), push to sdcard and flash using Flash Image GUI.
If you're away from a computer and want to flash a kernel, this is a great tool.
2) Load the custom recovery, NOT using the traditional method (reboot recovery, bootloader -> recovery, etc), but a specific method for Hboot 1.5. From the prompt use: fastboot boot c:\downloads\cwm-recovery.img.
This will temporarily boot the custom recovery image and the HTC unlock method will grant it write access to the boot partition while in this mode.
In this temporarily booted recovery mode, when a full ROM (with kernel included) is flashed, the kernel will flash correctly.
3) Boot into recovery using the traditional methods, reboot recovery, bootloader -> recovery, etc, and after the custom recovery has loaded, flash the ROM. Reboot into fastboot mode and then separately flash the kernel from the computer: fastboot flash boot c:\boot.img.
Downside to this method would be if a zImage is included instead of the boot.img for the kernel, won't flash correctly.
If you're issues are with not entering a custom recovery mode when following step 3, there are a few options. If you're able to boot into normal android mode w/o any issues and you seem familar with ROM manager, flash the custom recovery again from there.
My app, Flash Image GUI, also offers the same feature, select the recovery.img or PG86IMG.zip file off the sdcard and Flash Image GUI will flash it.
Another option is to flash it via fastboot: fastboot flash recovery c:\downloads\cwm-recovery.img
Hope that helps clarify!
flonker said:
If you tried flashing a rom with a custom kernel through rom manager it won't work. You have to flash that through fastboot. You say that your phone "boots up regular" as in boots into android?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
yes i meant boots into android regular just cannot get into custom recover I navigate to it and press power the htc logo appears and the phone shuts itself off and booth back into android
Sofocused504 said:
yes i meant boots into android regular just cannot get into custom recover I navigate to it and press power the htc logo appears and the phone shuts itself off and booth back into android
Click to expand...
Click to collapse
If the device does not make it past the splash screen this usually indicates a bad kernel (or ramdisk) or bad flash.
Either flash the same recovery file again or download a new recovery file.
Sometimes a bad flash can occur, usually rare. Sometimes the recovery file can corrupt while downloading, usually rare. But these things do occur.
Good luck!
Guys,
I followed this guide to unlock my phone and gain superuser access step by step:
http://forum.xda-developers.com/showthread.php?t=1239821
I then installed Rom Manager, and restarted in Recovery.
I placed this zip: http://forum.xda-developers.com/showthread.php?t=1421065 onto my SD Card, and did not rename it. Once in recovery I installed that ROM. It installed with no errors however now the phone gets stuck at the htc logo screen.
Any thoughts?
What was contained that .zip file you flashed, and did you make a backup of your system before you flashed?
Sent from my Droid Razr Maxx
Did you wipe data cache and dalvik? If not wipe again. If it bootloops again try pushing the kernel with fastboot.
Sent from my PG86100 using Tapatalk
The .zip contains the following files:
data
devices
kernel
META-INF
sdcard
system
CHANGELOG
check_data_app
mike, can you tell me how to push the update with fastboot, I'm kind of new to all of this telephone wizardry
I can get into FASTBOOT/HBOOT/RECOVERY, however nothing I do seems to help me get past the HTC Logo. Any thoughts? Maybe I'm not waiting long enough? Can someone please tell me exactly what I need to do (if I can even do something). I might just be approaching this whole process the wrong way.
Do I install a ROM from ZIP from Recovery? Do I need to fastboot an .img file first?
Sounds like your hboot 1.5 and your phone is hanging due to you need to place a copy of your recovery in your adb folder...
The while in Hboot
Using adb with phone plugged in and debug turned on
fastboot boot recovery.img
Then wipe and flash the rom you were trying to flash...
You can't just flash a rom with recovery since your s-on
Two methods
One is fastboot boot recovery.img which is easy
Other is boot.img pain in the ass
I tried booting directly into recovery like you just said. I am using TWRP recovery.img file.
Can this be caused by the type of ROM that I am trying to install?
Everything works fine, the .zip gets applied and seems to install correctly, but it still hangs at the htc logo.
I also forgot to mention that originally I used Clockwork Recovery Mod, which i got from the market, and selected the option to boot into recovery. I don't know if that makes any difference.
You should Google shooter ruu. Get back to stock. Retry this with another shot at reading the instructions.
You must plug your phone into pc while in fastboot and give it a command to boot recovery recovery.img .
Then reflash a rom.
Read more I'm hboot 1.4 and I can still flash a 1.5 hboot correctly cause I've read how to.
Sent from my PG86100 using Tapatalk
If u haven't figured it out yet, see if this helps:
[Guide] My Hboot 1.50 HTC Unlock/recovery/rom/kernel flashing notes http://forum.xda-developers.com/show....php?t=1495358
If u have updated your phone to the newest radio in the 2.17.651.5 update you may have problems if the Rom is based on an earlier kernel/radio like I think Warm is, but I could be wrong.
You may have flashed the Rom incorrectly & not had the kernel get flashed causing the boot loop.
Sent from my "Up all night, sleep all day" Evo3D via Tapatalk.
Hi,
Let me start off by saying that I have viewed other threads but have not been able to find one that has this same exact problem. Can someone please help?
I have an HTC Evo 3D unlocked with the HTC method, S-On.
I put a new rom on my SD card, I was using InfectedRom but it had some issues. I loaded into bootloader and used revolutionary to flash the rom. I didn't do a wipe or anything else, thinking that it would just flash the rom and I would be good to go.
The phone gets stuck on the HTC splash screen when I go to boot it. I have tried everything from restoring from a back up, to wiping the phone to wiping the cache and am at a loss.
Can someone please offer me some advice? I really need to get this phone back up and running.
Thanks in advance.
Did you flash the boot.img for the ROM?
How can I do that?
Jep4444 said:
Did you flash the boot.img for the ROM?
Click to expand...
Click to collapse
Thanks for the quick response. How can I go about doing that?
thealist said:
Thanks for the quick response. How can I go about doing that?
Click to expand...
Click to collapse
Considering you're S-ON, how did you install a custom ROM in the first place without doing so?
thealist said:
Thanks for the quick response. How can I go about doing that?
Click to expand...
Click to collapse
You can do that by using fastboot to boot your recovery image.
Code:
fastboot boot [NAMEOFRECOVERY].img
Just running your recovery normally won't allow flashing to certain partitions.
From there, you shouldn't have any problems flashing the full image. The second option would be to use 4EXT recovery (There's a CDMA/GSM version, but don't know off the top of my head), or joeykrim's FlashImageGUI to assist in flashing to specific partitions from the phone.
Edit: CDMA and GSM correction.
Jep4444 said:
Considering you're S-ON, how did you install a custom ROM in the first place without doing so?
Click to expand...
Click to collapse
thealist took the HTCDev unlock which doesn't give S-OFF, but does allow the user to flash custom ROMs.
~co~
closeone said:
You can do that by using fastboot to boot your recovery image.
Code:
fastboot boot [NAMEOFRECOVERY].img
Just running your recovery normally won't allow flashing to certain partitions.
From there, you shouldn't have any problems flashing the full image. The second option would be to use 4EXT recovery (There's a CDMA/GSM version, but don't know off the top of my head), or joeykrim's FlashImageGUI to assist in flashing to specific partitions from the phone.
Edit: CDMA and GSM correction.
thealist took the HTCDev unlock which doesn't give S-OFF, but does allow the user to flash custom ROMs.
~co~
Click to expand...
Click to collapse
Don't S-ON roms still need the boot.img to be flashed to install any ROM?
closeone said:
You can do that by using fastboot to boot your recovery image.
Code:
fastboot boot [NAMEOFRECOVERY].img
Where do I find my recovery image?
Just running your recovery normally won't allow flashing to certain partitions.
From there, you shouldn't have any problems flashing the full image. The second option would be to use 4EXT recovery (There's a CDMA/GSM version, but don't know off the top of my head), or joeykrim's FlashImageGUI to assist in flashing to specific partitions from the phone.
Edit: CDMA and GSM correction.
Thanks. Where would I find this and do I put that into the root sd card portion of my phone and then run through the bootloader? Sorry, I am relatively new to this process. Thanks for your patience.
thealist took the HTCDev unlock which doesn't give S-OFF, but does allow the user to flash custom ROMs.
That's exactly what I did.
~co~
Click to expand...
Click to collapse
Thanks for all the help. It's very much appreciated.
closeone said:
You can do that by using fastboot to boot your recovery image.
Code:
fastboot boot [NAMEOFRECOVERY].img
Just running your recovery normally won't allow flashing to certain partitions.
From there, you shouldn't have any problems flashing the full image. The second option would be to use 4EXT recovery (There's a CDMA/GSM version, but don't know off the top of my head), or joeykrim's FlashImageGUI to assist in flashing to specific partitions from the phone.
Edit: CDMA and GSM correction.
thealist took the HTCDev unlock which doesn't give S-OFF, but does allow the user to flash custom ROMs.
~co~
Click to expand...
Click to collapse
Sorry, my last post did not quote correctly.
How do I find my recovery image?
Once I get FlashImageGUI, do I put that into the root of my SD card by plugging it into my mac?
Jep4444 said:
Don't S-ON roms still need the boot.img to be flashed to install any ROM?
Click to expand...
Click to collapse
Well, all ROMs will need to have a boot.img flashed to boot, but since they are included in the ZIP file containing the ROM, they are normally flashed along with the ROM. If you use FlashImageGUI, you can flash from a boot.img or from a kernel zip file. By running the fastboot boot command, this allows the user to flash to partitions that are locked when booted into recovery from the bootloader.
thealist said:
Sorry, my last post did not quote correctly.
How do I find my recovery image?
Once I get FlashImageGUI, do I put that into the root of my SD card by plugging it into my mac?
Click to expand...
Click to collapse
These are two different methods for accomplishing the same task.
Have you loaded a custom recovery (like ClockworkMod Recovery, TWRP, or 4EXT) before? If you've kept the recovery image on your computer, you can just use that one. Instead of flashing it to your recovery partition (fastboot flash recovery [NAMEOFRECOVERY].img), you would boot to it instead (fastboot boot [NAMEOFRECOVERY].img).
If you use want to use FlashImageGUI, you would copy it to your SD card, install it on the phone, and run the app. Make sure that you've got the ROM you want to flash on the SDCard. If I remember correctly, FlashImageGUI will pull the boot.img out of the ZIP and flash it. Then you will have to boot into your custom recovery to flash the rest of the image. Flashing just the boot image will most likely leave you with a phone that won't boot (until you flash the rest of the ROM).
~co~
closeone said:
Well, all ROMs will need to have a boot.img flashed to boot, but since they are included in the ZIP file containing the ROM, they are normally flashed along with the ROM. If you use FlashImageGUI, you can flash from a boot.img or from a kernel zip file. By running the fastboot boot command, this allows the user to flash to partitions that are locked when booted into recovery from the bootloader.
These are two different methods for accomplishing the same task.
Have you loaded a custom recovery (like ClockworkMod Recovery, TWRP, or 4EXT) before? If you've kept the recovery image on your computer, you can just use that one. Instead of flashing it to your recovery partition (fastboot flash recovery [NAMEOFRECOVERY].img), you would boot to it instead (fastboot boot [NAMEOFRECOVERY].img).
If you use want to use FlashImageGUI, you would copy it to your SD card, install it on the phone, and run the app. Make sure that you've got the ROM you want to flash on the SDCard. If I remember correctly, FlashImageGUI will pull the boot.img out of the ZIP and flash it. Then you will have to boot into your custom recovery to flash the rest of the image. Flashing just the boot image will most likely leave you with a phone that won't boot (until you flash the rest of the ROM).
~co~
Click to expand...
Click to collapse
I have never loaded ClockworkMod Recovery, TWRP, or 4EXT to my phone. Is that something I can download online and then transfer to my phone using the bootloader? I have Revolutionary which allows me to mount the SD card. Same thing goes for FlasImageGUI. I can't get past the HTC load screen so is that something I can just transfer and use Bootloader with?
thealist said:
I have never loaded ClockworkMod Recovery, TWRP, or 4EXT to my phone. Is that something I can download online and then transfer to my phone using the bootloader? I have Revolutionary which allows me to mount the SD card. Same thing goes for FlasImageGUI. I can't get past the HTC load screen so is that something I can just transfer and use Bootloader with?
Click to expand...
Click to collapse
What is this 'Revolutionary' that you're talking about? I realize that multiple pieces of software can be called the same thing though. How did you load on the ROM that you're currently on? Also, before I link you anywhere (because I don't want you loading the wrong recovery on your phone), is your phone on Sprint, or another carrier? You'd use Recovery to load ROMs, back them up, and so on.
What exactly was it that you were trying to do? Or rather, how did the phone get to a state where it's frozen on the HTC logo? Do you have a custom ROM loaded, or the stock ROM?
Sorry for all the questions, and hopefully this response doesn't come off rude (I don't mean it to ). I'm just trying to figure out what's going on before I suggest anything.
If you are on Sprint, you can run this recovery from Fastboot USB mode.
Code:
fastboot boot cwm-4.0.1.4-shooter.img
~co~
closeone said:
What is this 'Revolutionary' that you're talking about? I realize that multiple pieces of software can be called the same thing though. How did you load on the ROM that you're currently on? Also, before I link you anywhere (because I don't want you loading the wrong recovery on your phone), is your phone on Sprint, or another carrier? You'd use Recovery to load ROMs, back them up, and so on.
What exactly was it that you were trying to do? Or rather, how did the phone get to a state where it's frozen on the HTC logo? Do you have a custom ROM loaded, or the stock ROM?
Sorry for all the questions, and hopefully this response doesn't come off rude (I don't mean it to ). I'm just trying to figure out what's going on before I suggest anything.
If you are on Sprint, you can run this recovery from Fastboot USB mode.
Code:
fastboot boot cwm-4.0.1.4-shooter.img
~co~
Click to expand...
Click to collapse
Your questions are really appreciated. Sorry I haven't been more clear.I really appreciate the help as I've gotten myself in trouble here.
I went on htcevohack and found how to flash the synergy infectedrom. The rom has some bugs in it so I downloaded a new rom and placed in the root folder of my SD card. Revolutionary is a program that allows me to wipe data, install from zip card, mount storage so and so forth. I tried to flash the zip from the new rom using this program and this is where I have had the problem. I have the Sprint Evo 3D. I am relatively new to this and just want a stable rom that has wifi tether on it. Thanks again for the help and for the patience.
thealist said:
Your questions are really appreciated. Sorry I haven't been more clear.I really appreciate the help as I've gotten myself in trouble here.
I went on htcevohack and found how to flash the synergy infectedrom. The rom has some bugs in it so I downloaded a new rom and placed in the root folder of my SD card. Revolutionary is a program that allows me to wipe data, install from zip card, mount storage so and so forth. I tried to flash the zip from the new rom using this program and this is where I have had the problem. I have the Sprint Evo 3D. I am relatively new to this and just want a stable rom that has wifi tether on it. Thanks again for the help and for the patience.
Click to expand...
Click to collapse
Oh! Now I know what your talking about. Max from HTCEVOHacks put the Revolutionary branded version of ClockworkMod Recovery in that archive. I know that for a fact (I downloaded it). It's actually the same version of ClockworkMod Recovery that I linked you to.
Okay. Here's my suggestion to start out with. Flash the recovery.img he included (CWM) onto your phone by booting it up into the bootloader, connecting it to your computer making sure that the phone is in FASTBOOT USB mode. Instead of running the command:
Code:
fastboot boot recovery.img
Run the command:
Code:
fastboot flash recovery recovery.img
That will put a copy of ClockworkMod Recovery on your phone. It's accessible by selecting Recovery from the HBOOT menu.
Now, because HTC's Unlock method doesn't unlock enough to flash most images to your phone, you'll still have to run the 'fastboot boot recovery.img' command each time you want to flash different image. That's the classic way we have used to get around HTC's restrictions.
From there, you can flash another image. Make sure to wipe data before flashing.
The reason I told you to also flash the recovery image to your phone is because, you can still create NANDroid backups without connecting to a computer. However, to restore those backups, you'll have to 'fastboot boot ...' the recovery image.
Now, his archive is quite dated. I'd personally recommend after you flash a new ROM, that you take a look at the 4EXT recovery thread in the EVO 3D CDMA development forum. It's really very good (I also like TWRP as well).
Now, there probably wasn't a problem with the ROM. I've used it myself, and have found it to be quite stable. If you flash a ROM onto the phone without wiping data first, you'll probably run into problems booting the ROM. If you liked InfectedRom Eternity, you can always try it again.
This is where NANDroid backups are important. If anything gets messed up, you can easily restore from one in your custom recovery (CWM/4EXT/TWRP).
I hope I didn't throw too much out there. Hopefully this gets you off the ground.
~co~
closeone said:
Oh! Now I know what your talking about. Max from HTCEVOHacks put the Revolutionary branded version of ClockworkMod Recovery in that archive. I know that for a fact (I downloaded it). It's actually the same version of ClockworkMod Recovery that I linked you to.
Okay. Here's my suggestion to start out with. Flash the recovery.img he included (CWM) onto your phone by booting it up into the bootloader, connecting it to your computer making sure that the phone is in FASTBOOT USB mode. Instead of running the command:
Code:
fastboot boot recovery.img
Run the command:
Code:
fastboot flash recovery recovery.img
That will put a copy of ClockworkMod Recovery on your phone. It's accessible by selecting Recovery from the HBOOT menu.
Now, because HTC's Unlock method doesn't unlock enough to flash most images to your phone, you'll still have to run the 'fastboot boot recovery.img' command each time you want to flash different image. That's the classic way we have used to get around HTC's restrictions.
From there, you can flash another image. Make sure to wipe data before flashing.
The reason I told you to also flash the recovery image to your phone is because, you can still create NANDroid backups without connecting to a computer. However, to restore those backups, you'll have to 'fastboot boot ...' the recovery image.
Now, his archive is quite dated. I'd personally recommend after you flash a new ROM, that you take a look at the 4EXT recovery thread in the EVO 3D CDMA development forum. It's really very good (I also like TWRP as well).
Now, there probably wasn't a problem with the ROM. I've used it myself, and have found it to be quite stable. If you flash a ROM onto the phone without wiping data first, you'll probably run into problems booting the ROM. If you liked InfectedRom Eternity, you can always try it again.
This is where NANDroid backups are important. If anything gets messed up, you can easily restore from one in your custom recovery (CWM/4EXT/TWRP).
I hope I didn't throw too much out there. Hopefully this gets you off the ground.
~co~
Click to expand...
Click to collapse
Thanks a lot! I am going to try this right now. I have a mac so I am assuming that I need to use terminal which is what I originally used. Do you know if the extension you provided were also for a mac?
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.