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!
Related
Two weeks ago:
I rooted my phone using HTC's method since I had already ran the update to 1.5 shooter. I flashed CWM to the recovery of the phone and took a backup. Loaded ViperROM and all was good.
Last night:
I wanted to load a new kernel since the one I put on there was not working well with WiFi. At the time I did not know i could just boot to HBOOT then go to recovery I thought I had to use Fastboot. Using Fastboot and doing the commands from memory I think I flashed it to the boot instead of recovery... Not exactly sure what I did but whatever it was i'm stuck in a continual reboot that gets no further then HTC.
What I've tried so far to resolve issue:
1. Boot into recovery and restore from backup. - Did not work
2. Boot to recovery and load a new ROM (Myns zip). - Did not work
3. Boot to recovery and load a stock ROM (4.53.651.1_Rooted_deodexed_signed.zip) - Did not work
4. Rename the stock ROM(from above) as PG86IMG.zip and put on SD. - Didnt work
4. Used fastboot to do fastboot boot (stock kernel i found online.zip) (stock rom i found online.zip) - Did not work
Any ideas cause i'm out and I dont want to go back to my previous Evo 4g.
cgprelude said:
Two weeks ago:
I rooted my phone using HTC's method since I had already ran the update to 1.5 shooter. I flashed CWM to the recovery of the phone and took a backup. Loaded ViperROM and all was good.
Last night:
I wanted to load a new kernel since the one I put on there was not working well with WiFi. At the time I did not know i could just boot to HBOOT then go to recovery I thought I had to use Fastboot. Using Fastboot and doing the commands from memory I think I flashed it to the boot instead of recovery... Not exactly sure what I did but whatever it was i'm stuck in a continual reboot that gets no further then HTC.
What I've tried so far to resolve issue:
1. Boot into recovery and restore from backup. - Did not work
2. Boot to recovery and load a new ROM (Myns zip). - Did not work
3. Boot to recovery and load a stock ROM (4.53.651.1_Rooted_deodexed_signed.zip) - Did not work
4. Rename the stock ROM(from above) as PG86IMG.zip and put on SD. - Didnt work
4. Used fastboot to do fastboot boot (stock kernel i found online.zip) (stock rom i found online.zip) - Did not work
Any ideas cause i'm out and I dont want to go back to my previous Evo 4g.
Click to expand...
Click to collapse
From what I've read regarding the HTC unlock method, when you boot the custom recovery, the HTC unlock method does not grant the custom recovery write access to the boot partition.
There are only three ways I'm familar with having write access to the boot partition when having used the HTC unlock method:
1) From normal android mode, the boot partition is unlocked and you can flash a kernel/write to it. My application, Flash Image GUI, works great for this purpose.
2) Using fastboot to temporarily load the custom recovery. When using fastboot to temporarily load the custom recovery, the HTC unlock method grants the temporarily loaded custom recovery write access to the boot partition.
fastboot boot c:\downloads\custom-recovery.img or temporarily boot the custom recovery with write access to the boot partition to flash the .zip file
also, you can directly flash the kernel, but the modules will not work until you manually push those: fastboot flash boot c:\downloads\boot.img
3) Having the bootloader directly flash the boot partition via a PG86IMG.zip file.
All the stock RUU files are hosted at: http://goo-inside.me/shooter/ruu - the latest version is 2.08 which must be what you're using to have used the HTC unlock method.
Hope that helps! Good luck!
I downloaded the PG86IMG.zip file from goo-inside.me and it loaded the file then nothing happened. So I selected reboot and it went back to doing the same old loop.
Joey is the man! got it working. I was unaware that if i booted into recovery from bootloader it was read only not read write. using fastboot corrected it.
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
i have been running Synergy Rom and causing a lot of problems so I have been tryin to install a numerous amount of roms and after wiping the phone back to factory and the dalvik then when its time to reboot the system i reboot the phone it just stays in the HTC boot up screen. so after a wait 10 or so min i just reload the Synergy rom which is the only one that works.
i am also running Revolutionary CWM v4.0.1.4 if that helps
i would really appreciate it if someone could point me into the right the direction thank you.
Are you on hboot 1.5? Are you flashing the correct kernel?
We're comin from a pure power source.
Yes it is and to be honest I haven't flashed them with any kernels cuz I never have before
Hmmmm, and you're doing a full complete wipe right? Which recovery are you using
We're comin from a pure power source.
Revolutionary CWM v4.0.1.4 and yes full wipe and dalvik.
Have you tried a different recovery?
We're comin from a pure power source.
nspyr05 said:
i have been running Synergy Rom and causing a lot of problems so I have been tryin to install a numerous amount of roms and after wiping the phone back to factory and the dalvik then when its time to reboot the system i reboot the phone it just stays in the HTC boot up screen. so after a wait 10 or so min i just reload the Synergy rom which is the only one that works.
i am also running Revolutionary CWM v4.0.1.4 if that helps
i would really appreciate it if someone could point me into the right the direction thank you.
Click to expand...
Click to collapse
ok as you know the roms come as .zips and we apply them through recovery.... some times that recovery doesnt writ the boot img correctly.... try installing ANY rom....then try to boot up... if it hangs at htc then pull the battery out then put it right back in and hold vol down and press power..then connect the phone to your computer so on your phone you see "fastboot usb"now the rom you tried installing that was the zip have a copy of that on your computer and open up with any program you use to open zips...extract that boot.img file to your fast boot file and where adb is too ,once extracted go back to your terminal window and type in
fastboot flash boot boot.img
it should say that its sending the data then writing it and then from there wait about 30 seconds and then select reboot and the rom should boot up
nspyr05 said:
Yes it is and to be honest I haven't flashed them with any kernels cuz I never have before
Click to expand...
Click to collapse
You cannot directly install ROMs with custom kernels on hboot 1.5 .
You always have to use "fastboot boot <your recovery>.img" or "fastboot flash boot boot.img" like the above post says..... If you dont use PC to flash ROMs with custom kernels , you will always get stuck on the HTC screen.
If you want to be able to flash ROMs / kernels / radios etc without PC, downgrade your hboot from 1.5 to 1.4.
Get flash image GUI from market to bypass fast boot and install custom kernels, or downgrade using unbeknownforce method and closeones live cd
Sent from my PG86100 using xda premium
Are you s off and if your knott you may need to use the GUI app from the market
Sent from my HTC EVO 3D X515m using xda premium
Idk if someone already said this but for 1.5 boot you need to go into fasboot usb . Fastboot boot recovery.img
Replace "recovery" with recovery file name. If your using 4.0.1.0 it might be. Cwm-4.0.1.4-shooter.img something like that
Second option is use 4EXT and you won't need to use your computer to flash rooms or kernels
Sent from my PG86100 using Tapatalk
First I assume you have the adb drivers.
place new rom on sd card
boot phone in bootloader, select fastboot
Access the adb folder via CMD
type in fastboot boot recovery.img
it should say waiting for device then connect..
you'll see the recovery screen
this will let you wipe and install new rom on hboot 1.5
I've tried everything I've found to get back to stock recover but I'm always greeted with red triangle. Only way to get to recovery back on line is to re-flash twrp. I've tried fastboot method, flasing new firmware, windroid toolkit... nothing works. I can't even flash CWM. So how do I get that damn leech out of my phone?
[edit]
Can't even flash twrp back on..so no recovery in this phone at the moment. Tried using goomanager, but it didn't do it either.
[/edit]
FIrst of all Which phone do you Have (Int) or At&t , now if you have a stock recovery backup then in that case you can just use fastboot to push the image or use "recovery tool " to push it to the boot partition.
In case you are looking for the int stock recovery for the International version of the HOX+
http://forum.xda-developers.com/showthread.php?p=48470851#post48470851
ethanon said:
FIrst of all Which phone do you Have (Int) or At&t , now if you have a stock recovery backup then in that case you can just use fastboot to push the image or use "recovery tool " to push it to the boot partition.
In case you are looking for the int stock recovery for the International version of the HOX+
http://forum.xda-developers.com/showthread.php?p=48470851#post48470851
Click to expand...
Click to collapse
I have wwe version of HTC One X+. That stock_recovery results the same red triangle. Fastboot pushes it okay but it just doesnt work.
Wiper said:
I have wwe version of HTC One X+. That stock_recovery results the same red triangle. Fastboot pushes it okay but it just doesnt work.
Click to expand...
Click to collapse
Stock recovery is not ment to do much , unless you have an official signed package to push. I feel you want to have a functional recovery like CWM , it can give it a go .
ethanon said:
Stock recovery is not ment to do much , unless you have an official signed package to push. I feel you want to have a functional recovery like CWM , it can give it a go .
Click to expand...
Click to collapse
Problem is that I've tried flashing TWRP and CWM but neither works. Phone boots up ok otherwise, but recovery is gone. Recovery Tool and Goomanager tells that the recovery image flash was completed but it's not or then something else got effed up. fastboot mode works just fine as the hboot.
Tried using RUU, but that doesn't work either because it keeps telling me that the battery level is below 30% and its at 91%. I remember trying RUU few months ago and I ran into the same problem. Back then I tried resetting battery status but that didn't help.
Wiper said:
Problem is that I've tried flashing TWRP and CWM but neither works. Phone boots up ok otherwise, but recovery is gone. Recovery Tool and Goomanager tells that the recovery image flash was completed but it's not or then something else got effed up. fastboot mode works just fine as the hboot.
Tried using RUU, but that doesn't work either because it keeps telling me that the battery level is below 30% and its at 91%. I remember trying RUU few months ago and I ran into the same problem. Back then I tried resetting battery status but that didn't help.
Click to expand...
Click to collapse
I got the same problem with RUU battery stat
Flashing a kernel solved the problem
Flashing another kernel didn't solve that porblem.
Wiper said:
Flashing another kernel didn't solve that porblem.
Click to expand...
Click to collapse
Flash the TWRP recovery.....
and erase the cache also using
this command
Code:
fastboot erase cache
[email protected] said:
Flash the TWRP recovery.....
and erase the cache also using
this command
Code:
fastboot erase cache
Click to expand...
Click to collapse
Tried that as well..no go. Tried even fastboot boot recovery.img but the phone just turns itself off and doesn't load temporary recovery.
Wiper said:
Problem is that I've tried flashing TWRP and CWM but neither works. Phone boots up ok otherwise, but recovery is gone. Recovery Tool and Goomanager tells that the recovery image flash was completed but it's not or then something else got effed up. fastboot mode works just fine as the hboot.
Tried using RUU, but that doesn't work either because it keeps telling me that the battery level is below 30% and its at 91%. I remember trying RUU few months ago and I ran into the same problem. Back then I tried resetting battery status but that didn't help.
Click to expand...
Click to collapse
you are doing it wrong....goomanager and recovery tool CANNOT simply flash onto our devices,
you NEED to do ; fastboot flash recovery <insert recovery name here .img>
Lloir said:
you are doing it wrong....goomanager and recovery tool CANNOT simply flash onto our devices,
you NEED to do ; fastboot flash recovery <insert recovery name here .img>
Click to expand...
Click to collapse
The fastboot method doesn't work. It does say that the flash was successfull, but there's still no recovery.... and besides, when I had stock recovery months ago, I actually did install twrp with goomanager, not with fastboot.
What I have tried:
1. fastboot flash boot stock_recovery.img with fastboot erase cache (red triangle)
2. fastboot flash boot twrp_recovery.img with erase (phone turns off when entering recovery)
3. fastboot boot recovery.img and twrp_recovery.img (doesn't boot to recovery) (phone turns off when entering recovery)
4. Tried using RUU but that hasn't worked for me ever (always the battery level below 30% error)
5. tried fastboot flash recovery and then flash boot and then erase (and first boot, then recovery) (stock and custom kernels)
6. numerous other ways I cant even remember anymore.
If there only were a rom with all the needed img files, I'd try flash all (or flashing them one by one) but haven't found any.
Wiper said:
The fastboot method doesn't work. It does say that the flash was successfull, but there's still no recovery.... and besides, when I had stock recovery months ago, I actually did install twrp with goomanager, not with fastboot.
What I have tried:
1. fastboot flash boot stock_recovery.img with fastboot erase cache (red triangle)
2. fastboot flash boot twrp_recovery.img with erase (phone turns off when entering recovery)
3. fastboot boot recovery.img and twrp_recovery.img (doesn't boot to recovery) (phone turns off when entering recovery)
4. Tried using RUU but that hasn't worked for me ever (always the battery level below 30% error)
5. tried fastboot flash recovery and then flash boot and then erase (and first boot, then recovery) (stock and custom kernels)
6. numerous other ways I cant even remember anymore.
If there only were a rom with all the needed img files, I'd try flash all (or flashing them one by one) but haven't found any.
Click to expand...
Click to collapse
U tried every possible incorrect things.....and didn't even read Llior's post......
To flash a kernel the fastboot command is
Code:
fastboot flash boot boot.img
To flash a recovery the command is
Code:
fastboot flash recovery recovery.img
instead of this u had tried to write the recovery file in boot partition...
and the
Code:
fastboot boot recovery.img
is to enter into the recovery without even having to install it on phone....
and I haven't checked it in HOX+ so better flash the boot.img(Kernel) and recovery.img(Recovery) using the mentioned commands above. and erase the cache....(which you seem to do correctly)...
Wiper said:
The fastboot method doesn't work. It does say that the flash was successfull, but there's still no recovery.... and besides, when I had stock recovery months ago, I actually did install twrp with goomanager, not with fastboot.
What I have tried:
1. fastboot flash boot stock_recovery.img with fastboot erase cache (red triangle)
2. fastboot flash boot twrp_recovery.img with erase (phone turns off when entering recovery)
3. fastboot boot recovery.img and twrp_recovery.img (doesn't boot to recovery) (phone turns off when entering recovery)
4. Tried using RUU but that hasn't worked for me ever (always the battery level below 30% error)
5. tried fastboot flash recovery and then flash boot and then erase (and first boot, then recovery) (stock and custom kernels)
6. numerous other ways I cant even remember anymore.
If there only were a rom with all the needed img files, I'd try flash all (or flashing them one by one) but haven't found any.
Click to expand...
Click to collapse
ok i'll base my assumptions here on you using windows, and you don't have filename endings turned on.
i'm guessing you are renaming the files and adding in .img which is a bad idea, as .img is actually there but hidden. if i'm wrong, then try flashing the recovery with the PROPER file name without touching it.
so for CWMR it would be fastboot flash recovery recovery.img
for twrp it would be ; fastbootflash recovery openrecovery-twrp-2.6.3.0-enrc2b.img
Lloir said:
ok i'll base my assumptions here on you using windows, and you don't have filename endings turned on.
i'm guessing you are renaming the files and adding in .img which is a bad idea, as .img is actually there but hidden. if i'm wrong, then try flashing the recovery with the PROPER file name without touching it.
so for CWMR it would be fastboot flash recovery recovery.img
for twrp it would be ; fastbootflash recovery openrecovery-twrp-2.6.3.0-enrc2b.img
Click to expand...
Click to collapse
I haven't actually renamed anything (just in here to keep it short). And that 1. & 2. was miswritten. I haven't done fastboot flash boot recovery.img but fastboot flash recovery recovery.img.
I have tried exactly that file you posted but it's a no go (also tried other twrp versions and come cwm's too as well as stock recovery image).
Ive tried it with All-in-one tool as well...The weird thing is that all fastboot flashes or with that allinone tool there are no errors ever, only successfull flashes.
Wiper said:
I haven't actually renamed anything (just in here to keep it short). And that 1. was typo. I haven't done fastboot flash boot recovery.img but fastboot flash recovery recovery.img.
I have tried exactly that file you posted but it's a no go (also tried other twrp versions and come cwm's too as well as stock recovery image).
Click to expand...
Click to collapse
are you sure your device is the enrc2b and not the evitareul?
Lloir said:
are you sure your device is the enrc2b and not the evitareul?
Click to expand...
Click to collapse
Yup... But anyway...decided to try that twrp one more time with all-in-one tool, flashed okay but this time the recovery worked and I was able to flash working rom and boot.img. Phone works now, but this was the last time I try to remove twrp.
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.