So I have a HTC One M8 (at&t) on Android 4.4.2.
Its a Deodexed pre-rooted Sense rom
it has TWRP as the bootloader
if it matters, xposed framework is installed.
I cannot S-Off. Out of the question. I am S-On.
I go do the OTA, it downloads, it reboots into TWRP, then does nothing when it goes to the main menu. I can reboot the phone to system and it boots normally into 4.4.2, but I cant update to 4.4.4
How do I fix this?
*Edit* Did some looking around, I think the issue is I have to be stock recovery and stock rom, so I downloaded them from http://forum.xda-developers.com/att...nt/att-stock-backups-recoveries-otas-t2855966 and got the firmware 1.58.502.1 versions, I checked with my phone to make sure its the right version.
*Edit 2* Will just installing the stock bootloader work? If not, I got the stock backup as well.
LightningKitsune said:
So I have a HTC One M8 (at&t) on Android 4.4.2.
Its a Deodexed pre-rooted Sense rom
it has TWRP as the bootloader
if it matters, xposed framework is installed.
I cannot S-Off. Out of the question. I am S-On.
I go do the OTA, it downloads, it reboots into TWRP, then does nothing when it goes to the main menu. I can reboot the phone to system and it boots normally into 4.4.2, but I cant update to 4.4.4
How do I fix this?
*Edit* Did some looking around, I think the issue is I have to be stock recovery and stock rom, so I downloaded them from http://forum.xda-developers.com/att...nt/att-stock-backups-recoveries-otas-t2855966 and got the firmware 1.58.502.1 versions, I checked with my phone to make sure its the right version.
*Edit 2* Will just installing the stock bootloader work? If not, I got the stock backup as well.
Click to expand...
Click to collapse
Copy the recovery to the folder where you have ADB and Fastboot executables/drivers on your computer and rename the file recovery.img
0. Make sure you have drivers required to use ADB and Fastboot loaded on your computer
1. TWRP is the recovery, not the bootloader
2. Boot into recovery (TWRP) and do a backup
3. From TWRP, reboot to bootloader
4. Connect your phone to your computer while the phone is still in fastboot mode
5. Make sure your phone's bootloader lists Fastboot as how it's connected
6. Make sure you have drivers required to ADB and Fastboot to your phone. Search this forum for info
7. On your computer, from a command prompt, go to the folder with the ADB/Fastboot drivers/exe files and that also contains the new recovery you downloaded and renamed.
8. In the command prompt, issue the following command:
fastboot flash recovery recovery.img
You will now have the original Stock HTC recovery for your 4.4.2 1.58.502.1 version.
Reboot the phone and check for an OTA update.
Once you have upgraded the phone, it will still have stock recovery, and won't have root, so you'll need to re-load TWRP (look for the latest version on this forum) just like you loaded the stock recovery, and then re-root.
Note:
I did this yesterday (OTA) and don't like 4.4.4. I reverted back to 4.4.2 and it's fine for me. Nothing in 4.4.4 is an advantage for me. Just my personal opinion, though.
DanGeorges said:
Note:
I did this yesterday (OTA) and don't like 4.4.4. I reverted back to 4.4.2 and it's fine for me. Nothing in 4.4.4 is an advantage for me. Just my personal opinion, though.
Click to expand...
Click to collapse
Well it's not only just for 4.4.4, but to return to stock seeing as I rooted to get firewater to work after a failed rom flash. That and my 2 year contract is almost over so I'll be able to get the m9, so I'll be able to sell my phone as stock.
Does anyone have a link to the OTA?
toby12188 said:
Does anyone have a link to the OTA?
Click to expand...
Click to collapse
PM me for the link to the actual OTA zip file. I'm not sure how it can be used, but I grabbed it.
DanGeorges said:
Copy the recovery to the folder where you have ADB and Fastboot executables/drivers on your computer and rename the file recovery.img
0. Make sure you have drivers required to use ADB and Fastboot loaded on your computer
1. TWRP is the recovery, not the bootloader
2. Boot into recovery (TWRP) and do a backup
3. From TWRP, reboot to bootloader
4. Connect your phone to your computer while the phone is still in fastboot mode
5. Make sure your phone's bootloader lists Fastboot as how it's connected
6. Make sure you have drivers required to ADB and Fastboot to your phone. Search this forum for info
7. On your computer, from a command prompt, go to the folder with the ADB/Fastboot drivers/exe files and that also contains the new recovery you downloaded and renamed.
8. In the command prompt, issue the following command:
fastboot flash recovery recovery.img
You will now have the original Stock HTC recovery for your 4.4.2 1.58.502.1 version.
Reboot the phone and check for an OTA update.
Once you have upgraded the phone, it will still have stock recovery, and won't have root, so you'll need to re-load TWRP (look for the latest version on this forum) just like you loaded the stock recovery, and then re-root.
Note:
I did this yesterday (OTA) and don't like 4.4.4. I reverted back to 4.4.2 and it's fine for me. Nothing in 4.4.4 is an advantage for me. Just my personal opinion, though.
Click to expand...
Click to collapse
All of this would work great except for one thing.
Stock is odex not deodex. So the ota would fail.
To take an ota you need to be 100% stock on /system (root is fine ) and on stock recovery.
LightningKitsune said:
Well it's not only just for 4.4.4, but to return to stock seeing as I rooted to get firewater to work after a failed rom flash. That and my 2 year contract is almost over so I'll be able to get the m9, so I'll be able to sell my phone as stock.
Click to expand...
Click to collapse
dottat said:
All of this would work great except for one thing.
Stock is odex not deodex. So the ota would fail.
To take an ota you need to be 100% stock on /system (root is fine ) and on stock recovery.
Click to expand...
Click to collapse
I missed the deodexed part. Sorry about that.
Another way:
Backup your personal data
Relock bootloader
RUU: http://www.htc.com/us/support/htc-one-m8-att/news/
Related
So I just got my One a few days ago and decided to root, unlock my bootloader, and flash a new rom. I unlocked, rooted, flashed twrp recovery and before I flashed a new rom, i wiped and ended up removing the roms from storage. Now i have no os to boot up into. No way to transfer a rom to the phone because clockwork and twrp dont support usb storage, adb sideload keeps failing, and ruu's wont install...on stock 4.3 ota from att....plz help.....
jm5503 said:
So I just got my One a few days ago and decided to root, unlock my bootloader, and flash a new rom. I unlocked, rooted, flashed twrp recovery and before I flashed a new rom, i wiped and ended up removing the roms from storage. Now i have no os to boot up into. No way to transfer a rom to the phone because clockwork and twrp dont support usb storage, adb sideload keeps failing, and ruu's wont install...on stock 4.3 ota from att....plz help.....
Click to expand...
Click to collapse
I use a usb OTG in TWRP almost everyday
and if sideload is failing it's likely because you don't have the drivers installed properly
and so you know the unlock is what wiped the phone not TWRP (unless you choose advanced and selected to wipe the sdcard which no one does)
get you drivers working
to test from recovery on the phone and command on the PC do adb devices and make sure you device is listed.
then in twrp you choose advanced/adb sideload
Connect phone to PC
Open command line where you have the file of ROM assuming you have ADB in Path of system, if you have not just copy the ROM to same place you have ADB files.
Type:
adb devices
(verify you phone are detect)
adb sideload name_of_the_rom_file.zip
(Wait the file is transfered to phone and recovery flash)
jm5503 said:
So I just got my One a few days ago and decided to root, unlock my bootloader, and flash a new rom. I unlocked, rooted, flashed twrp recovery and before I flashed a new rom, i wiped and ended up removing the roms from storage. Now i have no os to boot up into. No way to transfer a rom to the phone because clockwork and twrp dont support usb storage, adb sideload keeps failing, and ruu's wont install...on stock 4.3 ota from att....plz help.....
Click to expand...
Click to collapse
Thank you....
Sent from my HTC One using xda app-developers app
I have S-off, Unlocked Bootloader, and my EVO is rooted. I have HBOOT 2.09
I tried to install Vanir so I flashed the Gapps 4.4 in TWRP which seemed to work, then I tried to flash Vanir after and got an error.
Now no matter what I do I boot right into recovery and can't seem to figure my way out. Clearly I'm in over my head so if someone could just help me get back to stock at least I would really appreciate it. Thanks
Did you install the proper twrp for kitkat.. if so just try flashing the Rom first then let it boot up and sit for a minute.. then boot back into recovery and flash gapps this works for me..
Sent from my EVO using Tapatalk
It's 2.6.3 twrp, and whenever I tried to install the ROM it gave me an error message.
MrScrufff said:
I have S-off, Unlocked Bootloader, and my EVO is rooted. I have HBOOT 2.09
I tried to install Vanir so I flashed the Gapps 4.4 in TWRP which seemed to work, then I tried to flash Vanir after and got an error.
Now no matter what I do I boot right into recovery and can't seem to figure my way out. Clearly I'm in over my head so if someone could just help me get back to stock at least I would really appreciate it. Thanks
Click to expand...
Click to collapse
Even though you use TWRP 2.6.3.0, it has to be a modded one that allows SELinux support.
Click Me -Flash the Recovery in the OP of this thread
If you have a working fastboot and adb environment on your computer you can flash it by going to to fastboot USB in the bootloader of your phone, and make sure your phone is connected to your PC properly.
Place the .img file in your adb and fastboot folder and then open a command prompt from that location.
then type fastboot flash recovery "recoveryfilename.img" and ofcourse replace recoveryfilename with the actual filename.
after that reboot into recovery and try reflashing Vanir.
This is the method I use to flash recoveries, its fairly simple and fast in my opinion.
Hope this helps.
Link420able said:
Even though you use TWRP 2.6.3.0, it has to be a modded one that allows SELinux support.
Click Me -Flash the Recovery in the OP of this thread
If you have a working fastboot and adb environment on your computer you can flash it by going to to fastboot USB in the bootloader of your phone, and make sure your phone is connected to your PC properly.
Place the .img file in your adb and fastboot folder and then open a command prompt from that location.
then type fastboot flash recovery "recoveryfilename.img" and ofcourse replace recoveryfilename with the actual filename.
after that reboot into recovery and try reflashing Vanir.
This is the method I use to flash recoveries, its fairly simple and fast in my opinion.
Hope this helps.
Click to expand...
Click to collapse
Thanks, I just ran the RUU and went back to stock and everything's good
MrScrufff said:
Thanks, I just ran the RUU and went back to stock and everything's good
Click to expand...
Click to collapse
Ah ok. Glad you got everything sorted out.
Good deal.
Sometimes an RUU is all you have left. A powerful option no doubt.
Basically, I need the 4.4.2 OTA.
I unlocked the bootloader. I need root to get S-off. Except I'm currently on S-on and the only way to install a recovery and get root is to have S-off (correct me if I'm wrong). Any workaround to this that isn't super complicated?
I've checked USB ports, and I can't seem to get my device to be recognized. "fastboot devices" shows up nothing. Currently unlocked, and S-on.
Forgot that unlocking bootloader again would wipe my phone, forgot to make backup, so everything's deleted ;(. Not possible to get s-off anymore?
Any help would be appreciated.
mch277 said:
Basically, I need the 4.4.2 OTA.
I unlocked the bootloader. I need root to get S-off. Except I'm currently on S-on and the only way to install a recovery and get root is to have S-off (correct me if I'm wrong). Any workaround to this that isn't super complicated?
I've checked USB ports, and I can't seem to get my device to be recognized. "fastboot devices" shows up nothing. Currently unlocked, and S-on.
Forgot that unlocking bootloader again would wipe my phone, forgot to make backup, so everything's deleted ;(. Not possible to get s-off anymore?
Any help would be appreciated.
Click to expand...
Click to collapse
You just need an unlocked bootloader to install a recovery, when you are in fastboot (if you turn the phone on and do adb reboot fastboot, or hold down vol down and power and select fastboot when the HBOOT menu comes up) you can do the command line fastboot flash recovery recovery.img (recovery.img being your recovery you want to load) you can then start the phone up, copy superuser.zip on there somewhere and install with your custom recovery.
All that said, you don't need to do any of that to do 4.4.2 OTA, and in fact it wont install if you have a custom recovery. Are you having a problem that it wont download/install. If your phone is stock other than an unlocked bootloader it will install (trust me i just did it). If you have stock recovery just download the 4.4.2 OTA file from the other thread, then save it to the phone somewhere, the go to recovery in HBOOT, wait 1 second and then hold up vol and power for 5 seconds (may have to do this more than once). Menu comes up, do wipe cache, and then do install from device storage.
After thats done you can follow my above instructions and root it
Sorry if I didn't state it more clearly, but my issue is I can't install a recovery. I can boot into bootloader and fastboot but when I type in "fastboot" devices on my PC nothing comes up.
mch277 said:
Sorry if I didn't state it more clearly, but my issue is I can't install a recovery. I can boot into bootloader and fastboot but when I type in "fastboot" devices on my PC nothing comes up.
Click to expand...
Click to collapse
Have you installed HTC Sync? When you boot into the bootloader then fastboot and then plug in your usb cable does it say "fastboot usb" on screen?
Rogue Leader said:
Have you installed HTC Sync? When you boot into the bootloader then fastboot and then plug in your usb cable does it say "fastboot usb" on screen?
Click to expand...
Click to collapse
I uninstalled HTC sync so as to not have it interfere with any s-off/etc. programs. I still have HTC drivers installed. Re-install both HTC sync and drivers?
mch277 said:
I uninstalled HTC sync so as to not have it interfere with any s-off/etc. programs. I still have HTC drivers installed. Re-install both HTC sync and drivers?
Click to expand...
Click to collapse
HTC Sync won't interfere with anything. You need that and the drivers installed for it to work, I would start there and see what happens.
I'll re-install it again.
Is there anything I can do to just completely get back to stock everything? Willing to manually update it but I'd like to be able to just go to settings and just update via OTA from there.
mch277 said:
I'll re-install it again.
Is there anything I can do to just completely get back to stock everything? Willing to manually update it but I'd like to be able to just go to settings and just update via OTA from there.
Click to expand...
Click to collapse
As long as you have an active AT&T SIM card in there it will update even with an unlocked bootloader, even if its rooted. As long as you didn't mod anything. I just did the update like this, it worked fine.
I've rooted and unlocked the bootloader before but I've unrooted since then. Is there still a chance I just haven't gotten the update pushed to my device yet?
mch277 said:
I've rooted and unlocked the bootloader before but I've unrooted since then. Is there still a chance I just haven't gotten the update pushed to my device yet?
Click to expand...
Click to collapse
here's the OTAPkg.zip with instructions
http://forum.xda-developers.com/showthread.php?t=2659374
clsA said:
here's the OTAPkg.zip with instructions
http://forum.xda-developers.com/showthread.php?t=2659374
Click to expand...
Click to collapse
Thanks. I have that file all ready to go in my folder. Only problem I have now is that I can't get s-off. I've installed recovery + custom kernel but the su binaries are outdated for both superSU and superuser. I've tried to flash a 4.3 version of superSU only to have the same error.
I followed instructions for root after I flashed a super tool I also flashed a custom kernel. After I rebooted is where I started to get the "outdated binaries" prompts.
mch277 said:
Thanks. I have that file all ready to go in my folder. Only problem I have now is that I can't get s-off. I've installed recovery + custom kernel but the su binaries are outdated for both superSU and superuser. I've tried to flash a 4.3 version of superSU only to have the same error.
I followed instructions for root after I flashed a super tool I also flashed a custom kernel. After I rebooted is where I started to get the "outdated binaries" prompts.
Click to expand...
Click to collapse
Ok that changes things. IMO you need to backup your data, install the 4.3 RUU to wipe everything out and make sure you have stock recovery, then you can install the OTA zip from stock recovery, or go ahead and download it direct from AT&T. You can then root and go from there. Now as for S-Off if you have HBOOT 1.55 or newer I don't think you can get it. I can't get it on mine I tried every way possible. You don't need S-Off for this to work
I'm not new to flashing custom roms and rooting Android devices, so I don't think I'm a noob at this. I decided to help my friend unleash the power in his HTC One S by rooting it and giving it a custom recovery, I went through the right processes, Unlocked the phone's bootloader, and flashed the superuser zip and the twrp image, as it didn't seem like a clockworkmod image was compatible with the phone.
I then booted into recovery, wiped/factory reset and then flashed the latest CM11 nightly and got an error in TWRP recovery about the bootloader not been interoperable something like "
Code:
2.15==2.13"
in the error message , fine, I rebooted back into fastboot and checked the HBOOT Version and found out the phone was on HBOOT 1.13 and I think CM11 requires the most recent HBOOT version to work on HTC devices. The phone has got S-Off though.
Now I'm stuck in a bootloop cause I already wiped the OS in TWRP, I have everything in place, the right drivers and all that, I also tried re-installing the stock rom by downloading an HTC One S's RUU file but the device wasn't recognized at all by the RUU installer, I also tried to flash a stock 4.0.x rom as a zip file, no Joy. Now the phone is stuck at the point where it doesn't have an OS to boot into at all.
I'll really appreciate the community's support helping me fix this issue.
geek-x said:
I'm not new to flashing custom roms and rooting Android devices, so I don't think I'm a noob at this. I decided to help my friend unleash the power in his HTC One S by rooting it and giving it a custom recovery, I went through the right processes, Unlocked the phone's bootloader, and flashed the superuser zip and the twrp image, as it didn't seem like a clockworkmod image was compatible with the phone.
I then booted into recovery, wiped/factory reset and then flashed the latest CM11 nightly and got an error in TWRP recovery about the bootloader not been interoperable something like "
Code:
2.15==2.13"
in the error message , fine, I rebooted back into fastboot and checked the HBOOT Version and found out the phone was on HBOOT 1.13 and I think CM11 requires the most recent HBOOT version to work on HTC devices. The phone has got S-Off though.
Now I'm stuck in a bootloop cause I already wiped the OS in TWRP, I have everything in place, the right drivers and all that, I also tried re-installing the stock rom by downloading an HTC One S's RUU file but the device wasn't recognized at all by the RUU installer, I also tried to flash a stock 4.0.x rom as a zip file, no Joy. Now the phone is stuck at the point where it doesn't have an OS to boot into at all.
I'll really appreciate the community's support helping me fix this issue.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2322755
You need that. Luckily you're already S-Off, so shouldn't be terrible to get going again. Just update the firmware, reinstall TWRP and re-flash CM11. Should be good to go afterwards.
es0tericcha0s said:
http://forum.xda-developers.com/showthread.php?t=2322755
You need that. Luckily you're already S-Off, so shouldn't be terrible to get going again. Just update the firmware, reinstall TWRP and re-flash CM11. Should be good to go afterwards.
Click to expand...
Click to collapse
Thank you so much for the reply, does it matter that I don't have an OS to boot into as I already wiped and factory reset the phone for installation of a new rom.?
geek-x said:
Thank you so much for the reply, does it matter that I don't have an OS to boot into as I already wiped and factory reset the phone for installation of a new rom.?
Click to expand...
Click to collapse
Nah, shouldn't. The firmware we're referring to here is independent of the OS.
es0tericcha0s said:
Nah, shouldn't. The firmware we're referring to here is independent of the OS.
Click to expand...
Click to collapse
At the end of the guide, should help fix the issue, there's a part where I'm supposed to install the new CM kernel from the CM .zip package, how do I flash a kernel from Fastboot?
geek-x said:
At the end of the guide, should help fix the issue, there's a part where I'm supposed to install the new CM kernel from the CM .zip package, how do I flash a kernel from Fastboot?
Click to expand...
Click to collapse
Since you are S-Off, needing fastboot to install the boot.img is not necessary. It will install through recovery.
But, for future reference, you would boot to the bootloader screen, select fastboot, then assuming you have fastboot set up on the PC and the boot.img in the directory of said fastboot, you would use this command:
fastboot flash boot boot.img
then
fastboot reboot
es0tericcha0s said:
Since you are S-Off, needing fastboot to install the boot.img is not necessary. It will install through recovery.
But, for future reference, you would boot to the bootloader screen, select fastboot, then assuming you have fastboot set up on the PC and the boot.img in the directory of said fastboot, you would use this command:
fastboot flash boot boot.img
then
fastboot reboot
Click to expand...
Click to collapse
I tried flashing the firmware.zip file from the thread but I got a FAILED: (remote: not allowed) error in command prompt at the end of the process, what did I do wrong?
UPDATE: I was able to update the bootloader version successfully, as I forgot the part where I was to boot into RUU mode with fastboot oem rebootRUU and worked perfectly the second time.
I rebooted and found out the boot loader was updated to HBoot 2.15, and I also updated twrp to the latest S4 version but now in recovery I get errors about twrp been unable to mount the /data partition. Do I flash another recovery image?
UPDATE:
Thank you so much es0tericcha0s, I really appreciate the support, I got the /data mount issue fixed finally. I just had to flash an older twrp recovery image and then reflashed the new one in fastboot and I could then flash CM successfully.
I can't believe I finally unbricked this phone, its been bricked since Sunday. Once again, es0tericcha0s, Thank you!
geek-x said:
UPDATE: I was able to update the bootloader version successfully, as I forgot the part where I was to boot into RUU mode with fastboot oem rebootRUU and worked perfectly the second time.
I rebooted and found out the boot loader was updated to HBoot 2.15, and I also updated twrp to the latest S4 version but now in recovery I get errors about twrp been unable to mount the /data partition. Do I flash another recovery image?
Click to expand...
Click to collapse
You might need to RUU back then. If you have issues with the RUU exe, then you can extract the rom.zip and install it like you did the firmware. There are quite a few tutorials on how to extract it, or there might already be a version floating around for your phone.
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.