I've tried to look around, and the only method I seem to find is to flash back to ics, root, then install it. But is there a way to install it on jelly bean without going back to ics?
I had successfully rooted my go before, but that was with bin4ry's easy root exe. I kinda regretted not installing cwm sooner when I was still rooted in ICS. I also have no idea how to fast boot on this phone, I read a guide before, but my phone goes into charging mode before I get to click anything.
arenaboy007 said:
I had successfully rooted my go before, but that was with bin4ry's easy root exe. I kinda regretted not installing cwm sooner when I was still rooted in ICS. I also have no idea how to fast boot on this phone, I read a guide before, but my phone goes into charging mode before I get to click anything.
Click to expand...
Click to collapse
try this.
http://forum.xda-developers.com/showthread.php?t=2250695
Ben Ling said:
try this.
http://forum.xda-developers.com/showthread.php?t=2250695
Click to expand...
Click to collapse
OK last night I was stuck at step 13, but just this morning for some reason, my phone went on fastboot mode, and the computer automatically installed the drivers. Now that it's on fastboot, I tried moving on to step 14-15, this is where I get stuck again... It says open a cmd within the sdk folder, and enter the command on step 15, I get the message, "fastboot.exe is not recognized as an internal or external command." I checked both tools, and platform-tools, they both have fastboot.exe. what am I missing? I extracted the adt-bundle on my desktop if that helps.
Ben Ling said:
try this.
http://forum.xda-developers.com/showthread.php?t=2250695
Click to expand...
Click to collapse
I have not tried any custom ROM yet, the only thing I tried before was rooting my official ICS .10 from bin4ry..
hmmmm..
arenaboy007 said:
OK last night I was stuck at step 13, but just this morning for some reason, my phone went on fastboot mode, and the computer automatically installed the drivers. Now that it's on fastboot, I tried moving on to step 14-15, this is where I get stuck again... It says open a cmd within the sdk folder, and enter the command on step 15, I get the message, "fastboot.exe is not recognized as an internal or external command." I checked both tools, and platform-tools, they both have fastboot.exe. what am I missing? I extracted the adt-bundle on my desktop if that helps.
Click to expand...
Click to collapse
Try just fastboot without the .exe.
fastboot flash boot.img
androidmeda said:
Try just fastboot without the .exe.
fastboot flash boot.img
Click to expand...
Click to collapse
Actually it doesn't have the ".exe", maybe I should try it with ".exe"?
arenaboy007 said:
Actually it doesn't have the ".exe", maybe I should try it with ".exe"?
Click to expand...
Click to collapse
Put the boot.img in platform-tools and open a command window from there (shift+rclick on empty spot > open command window from here)
Then try fastboot again. Should work with or without .exe
PS. How did you get this far with the steps and have fastboot not work if you went through unlocking bootloader?
Stock and locked xGO beans.
androidmeda said:
Put the boot.img in platform-tools and open a command window from there (shift+rclick on empty spot > open command window from here)
Then try fastboot again. Should work with or without .exe!
PS. How did you get this far with the steps and have fastboot not work if you went through unlocking bootloader?
Stock and locked xGO beans.
Click to expand...
Click to collapse
Fastboot was already working, I just need to unlock the bootloader. How the fastboot driver installed, I have no idea, maybe it was when I restarted my pc this morning that sorted things out. The computer found the driver by itself for some reason. Another thing that probably help was when I pressed the volume up button by itself, and not with the power button.
-delete-
I'm an idiot. Lol. How'd it go?
Stock and locked xGO beans.
androidmeda said:
-delete-
I'm an idiot. Lol. How'd it go?
Stock and locked xGO beans.
Click to expand...
Click to collapse
I get this when I put the line from step 15, I get this message...
What now?
In the beginning I used this guide to install fastboot. Maybe it will help.
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
Drivers I installed from latest flashtool.
Stock and locked xGO beans.
androidmeda said:
In the beginning I used this guide to install fastboot. Maybe it will help.
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
Drivers I installed from latest flashtool.
Stock and locked xGO beans.
Click to expand...
Click to collapse
So I tried looking around the forums for another method on unlocking the bootloader. And I tried the SE bootloader unlocker. It seemed to me it worked in unlocking the bootloader although I still don't know how to confirm, since I still get the error on my previous post. I tried moving on and flash the boot.img and I started to get the 4 flashing colors, but I'm a bit confused on step 5 and 6 in installing cwm. And I get the flashing colors everytime I restart my phone, is this normal? I'm not finish in installing cwm so that might be a reason.
arenaboy007 said:
So I tried looking around the forums for another method on unlocking the bootloader. And I tried the SE bootloader unlocker. It seemed to me it worked in unlocking the bootloader although I still don't know how to confirm, since I still get the error on my previous post. I tried moving on and flash the boot.img and I started to get the 4 flashing colors, but I'm a bit confused on step 5 and 6 in installing cwm. And I get the flashing colors everytime I restart my phone, is this normal? I'm not finish in installing cwm so that might be a reason.
Click to expand...
Click to collapse
4 flashing colors indicate boot.img was flashed successfully (because normal boot img doesn't do that). And you will be seeing that everytime while using this ROM. You should be able to boot to CWM by holding down vol- when it starts flashing and right after the vibrate. Keep it held til you see CWM. If that doesn't work, pop your question over there in that thread for OP to read.
Stock and locked xGO beans.
androidmeda said:
4 flashing colors indicate boot.img was flashed successfully (because normal boot img doesn't do that). And you will be seeing that everytime while using this ROM. You should be able to boot to CWM by holding down vol- when it starts flashing and right after the vibrate. Keep it held til you see CWM. If that doesn't work, pop your question over there in that thread for OP to read.
Stock and locked xGO beans.
Click to expand...
Click to collapse
Thanks for the advice! CWM is installed. Time to look for custom roms!
arenaboy007 said:
I've tried to look around, and the only method I seem to find is to flash back to ics, root, then install it. But is there a way to install it on jelly bean without going back to ics?
Click to expand...
Click to collapse
I have a networked locked go (ST27i) on O2 network in the UK. The boot loader cannot be unlocked. I installed the latest generic firmware 6.2.A.1.100 via flashtool (to de-brand the O2 startup/shutdown sequence which slowed the phone a little). I rooted the phone via the DoomLoRD .bat exploit.
I have tried three versions of CWM from playstore and they all say they are incompatible with my device, so I cannot install it? As my bootloader cannot be unlocked I understand I cannot flash a custom kernel or use a custom rom.
I assume as the OP says (and after many hours reading), to install CWM recovery to a ST27i on the latest JB rom, you must flash the device from JB back to ICS, then install the CWM recovery/kernel. Then to flash the JB rom you do it through CWM and not via flash tool if you want to go back to JB, is that correct? Thus keeping the CWM recovery option on startup.
thanks in advance for any help with this!
smirnofred
smirnofred said:
I have a networked locked go (ST27i) on O2 network in the UK. The boot loader cannot be unlocked. I installed the latest generic firmware 6.2.A.1.100 via flashtool (to de-brand the O2 startup/shutdown sequence which slowed the phone a little). I rooted the phone via the DoomLoRD .bat exploit.
I have tried three versions of CWM from playstore and they all say they are incompatible with my device, so I cannot install it? As my bootloader cannot be unlocked I understand I cannot flash a custom kernel or use a custom rom.
I assume as the OP says (and after many hours reading), to install CWM recovery to a ST27i on the latest JB rom, you must flash the device from JB back to ICS, then install the CWM recovery/kernel. Then to flash the JB rom you do it through CWM and not via flash tool if you want to go back to JB, is that correct? Thus keeping the CWM recovery option on startup.
thanks in advance for any help with this!
smirnofred
Click to expand...
Click to collapse
You assumed it right. Installing CWM was actually quite easy, I was just not familiar with the steps provided on sony's website. Don't use the CWM from playstore, use the ones on this forum. Make sure the necessary files are installed, like ADB, and Android SDK tools, then install CWM through your PC with your phone connected on fastboot(Press volume up as you connect your phone). Replace the boot.img from the android platform-tools, with the boot.img from the CWM file you downloaded. Open command prompt inside platform-tools folder and type "fastboot flash boot boot.img " without the quote. When you see a bunch of numbers come up that means you have just successfully installed CWM, then type "fastboot reboot". If you see flashing colors during boot then that means you were successful. To go to CWM menu, wait for the led to flash then press volume down.
Related
Hi All,
Long time lurker and I appreciate all the work everyone does here. It makes owning an android device a great amount of fun...but as you can see by the title of the thread, a great amount of stress as well :laugh:
My device is unlocked and I've used CWM and recenlty noticed that along one of my flashes TWRP 2.4 installed over CWM. All is well because I was meaning to switch over and try this recovery out. Smooth, fast, I like. But I recently installed CM 10.1 using the october version with the JB bootloader because I did not have it. Everything was nice, but I wanted to update CM 10.1 to a more recent UNOFFICIAL build so I flased the 3/20 version on my device. Everything was smooth but the WiFi dropped all the time so I decided to wait out a more stable "official" version of CM 10.1. Take note that I have(had) TWRP 2.4. Now I wanted to stick with JB 4.2.X so I decided to flash Energy's 3/21 build but this hung up on the ASUS screen... So I decided to reflash the rom but first installing the JB bootloader and partitions zip. Still no luck and while exiting TWRP, I noticed that it stated that my device isn't rooted and would I like to root? So I swiped and did it but it seems that the JB bootloader and partitions zip file erased everything on my device, Roms, GAPPS, SU, backups...gone.
The next thing I did was execute Urkels fresh root and fresh start and that seemed to go through all the steps with no issue. When I went back into recovery I noticed that I now have TWRP 2.2.2.1 with a JB bootloader... so what ever I did downgraded TWRP? Ok... Now I wanted to play it safe and stick to the October version of CM 10.1 with the JB bootloader but while flashing the rom (ext SDCARD) i receive an error. I decided to re-execute Urkels fresh root and fresh start and now all my device does is boot into TWRP 2.2.2.1. I can't use fastboot even with holding the power button and vol down.
At this point I feel lost and defeated, I can't use external SD anymore and I can only mount the system. So I decided to see if ADB works. ADB works great in recovery and am able to send files to the device. I sent a ROM to see if I can install but it fails because it can't mount the cache and this is where I am now. Lost... confused and desperate for help :crying: I'll make sure XDA gets a nice donation if anyone can help me out!
What works -
boot to TWRP 2.2.2.1 (thats all)
ADB in recovery
What doesn't-
No rom installed
No backup
No fastboot
My troubleshooting
Again ANY help is appreciated!
Mike
Would I be able to update TWRP within TWRP using a 2.4.4.0 zip file?
TheYoz said:
Would I be able to update TWRP within TWRP using a 2.4.4.0 zip file?
Click to expand...
Click to collapse
This is happening because you are now on 4.2.1 bootloader with an old TWRP which is not compatible with the new bootloader.
When you say you cannot access fast boot do you mean the usb icon is missing? If you do that is part of the new bootloader. As soon as you get to where the icons are you are automatically in fast boot unless you select one of the icons.
I'm out at the moment but if you reply letting me know that you can get to the icons I will post a file when I get back and some instructions to downgrade you to old bootloader and compatible TWRP.
flumpster said:
This is happening because you are now on 4.2.1 bootloader with an old TWRP which is not compatible with the new bootloader.
When you say you cannot access fast boot do you mean the usb icon is missing? If you do that is part of the new bootloader. As soon as you get to where the icons are you are automatically in fast boot unless you select one of the icons.
I'm out at the moment but if you reply letting me know that you can get to the icons I will post a file when I get back and some instructions to downgrade you to old bootloader and compatible TWRP.
Click to expand...
Click to collapse
I figured my TWRP version might have been the culprit...
When I restart and hold the vol down button it normally would activate fastboot, now it goes directly to TWRP, no icons whatso ever. Before I would get the recovery icon, a usb (I think) and an option to wipe data. I can't get to that screen anymore. Is there a command in adb that will allow me to restart to fastboot from recovery? I myself am at work too so I will test anything I can in 3 - 4 hours. Thanks for taking the time to respond! :good:
So basically I won't be able to put TWRP 2.4.4.0 within my current version of TWRP?
TheYoz said:
I figured my TWRP version might have been the culprit...
When I restart and hold the vol down button it normally would activate fastboot, now it goes directly to TWRP, no icons whatso ever. Before I would get the recovery icon, a usb (I think) and an option to wipe data. I can't get to that screen anymore. Is there a command in adb that will allow me to restart to fastboot from recovery? I myself am at work too so I will test anything I can in 3 - 4 hours. Thanks for taking the time to respond! :good:
So basically I won't be able to put TWRP 2.4.4.0 within my current version of TWRP?
Click to expand...
Click to collapse
The version of TWRP you have will not mount the partitions you need to flash anything. You either need to downgrade the bootloader so that version of TWRP will work or get the version of TWRP back on there that was edited to work with the new 4.2.1 bootloader.
When you installed that partition.zip from energy rom it installed the new bootloader and the compatible twrp the same time. To go back he also has a zip that will restore old bootloader and old twrp. This is what you should have done.
What I am worried about now is the fact that you cannot even get to fastboot from the buttons.
Try adb reboot bootloader.
If that lets you in then download this .. http://flumpster.lolcakes.com/android/blob and place it in your fastboot directory.
Now type.
fastboot -i 0x0B05 flash staging blob
wait for it to fully flash and then type
fastboot -i 0x0B05 reboot
Give it about 20 seconds, if it doesn't restart then you will have to hold the power button down for 10 seconds to force a restart.
When it restarts it should now start to fill the blue line on the Asus screen which will flash the old bootloader and compatible TWRP. If it does this then great, just wait until it has finished and it should put you back into twrp where you will be able to install a rom off your external SD.
If it does not do the blue line then we have bigger probs and I hope you have nvflash backup files.
flumpster said:
The version of TWRP you have will not mount the partitions you need to flash anything. You either need to downgrade the bootloader so that version of TWRP will work or get the version of TWRP back on there that was edited to work with the new 4.2.1 bootloader.
When you installed that partition.zip from energy rom it installed the new bootloader and the compatible twrp the same time. To go back he also has a zip that will restore old bootloader and old twrp. This is what you should have done.
What I am worried about now is the fact that you cannot even get to fastboot from the buttons.
Try adb reboot bootloader.
If that lets you in then download this .. http://flumpster.lolcakes.com/android/blob and place it in your fastboot directory.
Now type.
fastboot -i 0x0B05 flash staging blob
wait for it to fully flash and then type
fastboot -i 0x0B05 reboot
Give it about 20 seconds, if it doesn't restart then you will have to hold the power button down for 10 seconds to force a restart.
When it restarts it should now start to fill the blue line on the Asus screen which will flash the old bootloader and compatible TWRP. If it does this then great, just wait until it has finished and it should put you back into twrp where you will be able to install a rom off your external SD.
If it does not do the blue line then we have bigger probs and I hope you have nvflash backup files.
Click to expand...
Click to collapse
Crossing my fingers... I will try what you mentioned and no, I don't have NVFLASH. Something that I have been meaning to do for a few weeks now too. Thanks for the help I will update when I get a chance to try.
Mikw
TheYoz said:
Crossing my fingers... I will try what you mentioned and no, I don't have NVFLASH. Something that I have been meaning to do for a few weeks now too. Thanks for the help I will update when I get a chance to try.
Mikw
Click to expand...
Click to collapse
You cannot do the nvflash process now. You could only do it while on ICS and there is no way back to ICS without having nvflash backups.
flumpster said:
You cannot do the nvflash process now. You could only do it while on ICS and there is no way back to ICS without having nvflash backups.
Click to expand...
Click to collapse
I am able to adb reboot bootloader, and it brings me to fastboot!
I successfully executed the steps you gave me but I didn't get the android screen with the blue line... it went back to TWRP 2.2.2.1. Can I fastboot the new version of TWRP?
TheYoz said:
I am able to adb reboot bootloader, and it brings me to fastboot!
I successfully executed the steps you gave me but I didn't get the android screen with the blue line... it went back to TWRP 2.2.2.1. Can I fastboot the new version of TWRP?
Click to expand...
Click to collapse
Tried one more time with no success... Please let me know if I have any other options since I can get to fastboot via ADB.
I think the reason I am running into this mess is because I didn't download the JB update from ASUS and move the system.blob file according to Urkel fresh start
TheYoz said:
Tried one more time with no success... Please let me know if I have any other options since I can get to fastboot via ADB.
I think the reason I am running into this mess is because I didn't download the JB update from ASUS and move the system.blob file according to Urkel fresh start
Click to expand...
Click to collapse
I have even tried installing the TWRP.blob (newest JB version) file using this method but still reverts to version 2.2.2.1. I'm stumped
TheYoz said:
I have even tried installing the TWRP.blob (newest JB version) file using this method but still reverts to version 2.2.2.1. I'm stumped
Click to expand...
Click to collapse
I was worried about this. I have seen loads of people with the same problem you have over on the tf300 forums.
They can access fastboot thru adb reboot fastboot and it appears to send the file over ok but then it doesn't work.
When you mentioned you couldn't get to fastboot by holding button combo it looked like the same prob as them.
Have a look at this thread. http://forum.xda-developers.com/showthread.php?t=2179874
flumpster said:
I was worried about this. I have seen loads of people with the same problem you have over on the tf300 forums.
They can access fastboot thru adb reboot fastboot and it appears to send the file over ok but then it doesn't work.
When you mentioned you couldn't get to fastboot by holding button combo it looked like the same prob as them.
Have a look at this thread. http://forum.xda-developers.com/showthread.php?t=2179874
Click to expand...
Click to collapse
So I probably need to send it to ASUS or wait for a solution? That is for the TF300 would I be able to use any steps for that device with mine?
Also,
I purchased this in January 2012 from best buy, any possibility I can go through them to have this issue fixed?
TheYoz said:
I have even tried installing the TWRP.blob (newest JB version) file using this method but still reverts to version 2.2.2.1. I'm stumped
Click to expand...
Click to collapse
Flash the .img not the blob that should fix your issue.
Loco0729 said:
Flash the .img not the blob that should fix your issue.
Click to expand...
Click to collapse
I doubt it will but he can try.
No luck flashing the .img file instead. This is the worst
Flumpster thanks a bunch for all of your help. I ended up sending in the tablet, as expected they had to replace the motherboard.:
They quoted me this origionally:
Parts: $165
Labor: $65
Shipping $10
TOTAL $240!!!
I called and complained until my eyes popped out of my head and they ended up replacing the motherboad and shipped it back to me for $150. Now I think I'm going to sell this thing with the dock and buy a Nexus 10. Again, thanks for your help.
Another note... It will probably be a pain to unlock and root this thing again after the RMA im assuming. No more ASUS.
Hello,
I 'm new to the android community and i'm so glad to be among you. So i rooted my HTC Desire X (with ICS) a couple of days ago using CWM recovery and now I want to install this DEODEXED stock ROM: http://forum.xda-developers.com/showthread.php?p=40682127
(Note: I have CID:T-MOB101 and HBOOT 1.24.0000).
While rooting the phone i installed CWM recovery while the guide on the link demands to install TWRP. How can i install TWRP over CWM? Because while doing the steps of the guide i got stuck in the 3rd step(Command Prompt says:sending "recovery" but the process never finishes)...
Forgive me if i have forgotten any info of my phone, just let me know!
Thanks in advance,
Tassos
Download this tool http://forum.xda-developers.com/showthread.php?t=1943822
Its much easier.
Important! make a nandroid backup first before flash anything,
ειναι σημαντικο να εχεις ενα!!
Tried with the way above, didn't worked...
I tried this and it didnt worked, i also tried manually through terminal with no luck. As i said above the process gets stuck when the terminal says "sending recovery" and the bar on the screen of my phone doesn't fill. I 've been reading that there are some other users of HTC DX that have the same problem with me, that is they can't flash TWRP and finally they install CWM. Has this something to do with the details of my phone(CID, hboot, etc.)?
So can anyone help me on how to flash TWRP on my phone with CWM on it.?
tassos_chry said:
How can i install TWRP over CWM?
Click to expand...
Click to collapse
Try Clearing the Dalvik Cache
Download this toolkit ,extract it on desktop
replace its recovery.img with this RECOVERY
boot into bootloader
Connect to PC
run 'Install Recovery.img.bat'
AND U"RE DONE :laugh:
if this does not work then try factory format
AND REMEMBER MAKE AN NAND :good: BEFORE DOING THIS
Thanks
Ok thanks, i'll try these methods and post feedback.
Thanks again
Update:
First method didn't work...
Just tried factory reset!
Update 2:
I factory resetted the phone through CWM and went to repeat the process. Still NO luck...
tassos_chry said:
Ok thanks, i'll try these methods and post feedback.
Thanks again
Update:
First method didn't work...
Just tried factory reset!
Update 2:
I factory resetted the phone through CWM and went to repeat the process. Still NO luck...
Click to expand...
Click to collapse
1. Start your PC
2. Go in folder containing fastboot.exe and related binaries.
3. Download the recovery.img for (ICS or JB) as required.
4. Type this command in cmd.exe
fastboot.exe flash recovery recovery.img
5. Press power button so that phone goes from fasboot to hboot mode. Then press VOLDOWN and then POWER to boot into recovery.
Its a simple enough process, just try to be calm and do it one step at a time.
Regards
Yasir
Sorry for not posting this earlier, but i just saw that when i boot into hboot the following message comes up:
"SD Checking
Loading PM66DIAG.zip
No Image
Loading PM66DIAG.nbh
No Image
Loading PM66IMG.zip
No Image
Loading PM66IMG.nbh
No Image or Wrong Image"
Then it disappears immediately and the normal screen of hboot comes up...
Maybe this has something to do, with me not being able to flash TWRP...
Any help?
tassos_chry said:
Sorry for not posting this earlier, but i just saw that when i boot into hboot the following message comes up:
"SD Checking
Loading PM66DIAG.zip
No Image
Loading PM66DIAG.nbh
No Image
Loading PM66IMG.zip
No Image
Loading PM66IMG.nbh
No Image or Wrong Image"
Then it disappears immediately and the normal screen of hboot comes up...
Maybe this has something to do, with me not being able to flash TWRP...
Any help?
Click to expand...
Click to collapse
I said to you thru PM... check whether you are at the correct fastboot usb screen. This SD checking and blablabla is hboot screen, fastboot flash won't work on hboot screen, only on fastboot/bootloader screen.
After this SD checking and blablabla screen, press power once to go to bootloader/fastbboot screen
ckpv5 said:
I said to you thru PM... check whether you are at the correct fastboot usb screen. This SD checking and blablabla is hboot screen, fastboot flash won't work on hboot screen, only on fastboot/bootloader screen.
After this SD checking and blablabla screen, press power once to go to bootloader/fastbboot screen
Click to expand...
Click to collapse
All the times I've tried to flash a recovery i 'm on the fastboot/bootloader screen, which says Fastboot USB. I tried with neXus PRIME's way too but it didn't work out. I think i'm not doing anything wrong and don't know why it doesn't work...
Check/change your cable and also change the usb port (use usb2.0 instead of usb3.0) or try on other PC
BTW.. you also can use CWM to flash ROM... the only reason to use TWRP is it has a reboot option in recovery where you can select reboot to bootloader. So using CWM, you must manually put your device to bootloader after installing ROM.
But I suggest, you stick with your current ROM. That JB ROM is only for people who want to test how the JB ROM is. Most of them revert back to ICS
ckpv5 said:
Check/change your cable and also change the usb port (use usb2.0 instead of usb3.0) or try on other PC
BTW.. you also can use CWM to flash ROM... the only reason to use TWRP is it has a reboot option in recovery where you can select reboot to bootloader. So using CWM, you must manually put your device to bootloader after installing ROM.
But I suggest, you stick with your current ROM. That JB ROM is only for people who want to test how the JB ROM is. Most of them revert back to ICS
Click to expand...
Click to collapse
FML. It was the USB port that caused the mess(I was using USB 3). Just flashed TWRP using USB 2
Thank you man. I was so dissapointed, thinking that something is wrong with my phone!!
Thank you very much!:laugh:
Update:Any info when the official update for JB from HTC comes out for all of us who don't have it yet?
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
PLEASE HELP ,i have a sony xperia z ultra g.p.e with 4.4.4 rooted and a locked bootloader which i managed to delete a system file and immediately started boot looping the boot animation.
I can still get into the stock recovery.
I've searched everywhere and all i see is instruction for unlocked bootloader .
I've read that i can't flash an ftf with a locked boot loader,please help
i have a macbook but also have access to a windows comp
please if anyone can help me with step by step instruction to bring the phone back to a working state i would forever be thankful.
icotulookn said:
PLEASE HELP ,i have a sony xperia z ultra g.p.e with 4.4.4 rooted and a locked bootloader which i managed to delete a system file and immediately started boot looping the boot animation.
I can still get into the stock recovery.
I've searched everywhere and all i see is instruction for unlocked bootloader .
I've read that i can't flash an ftf with a locked boot loader,please help
i have a macbook but also have access to a windows comp
please if anyone can help me with step by step instruction to bring the phone back to a working state i would forever be thankful.
Click to expand...
Click to collapse
If you do have a GPe DO NOT FLASH AN FTF it will result in a permanent hard brick. Look for DooMLoRD's return to stock thread in GPe development section, it will return you to stock 4.4.2 and then you can let it update from there.
Thank you I will give that a try and post back results
icotulookn said:
Thank you I will give that a try and post back results
Click to expand...
Click to collapse
I must apologize for giving out bad advice. Stock recovery will not allow flashing older firmware.
I think what may be possible is flashing the 4.4.4 system IMG with fastboot. Maybe @egzthunder1 or @blueether will be nice enough to offer some better advice.
adfurgerson said:
I must apologize for giving out bad advice. Stock recovery will not allow flashing older firmware.
I think what may be possible is flashing the 4.4.4 system IMG with fastboot. Maybe @egzthunder1 or @blueether will be nice enough to offer some better advice.
Click to expand...
Click to collapse
OK thanks yea I'm really lost, I've been searching and I can't find any instruction on this.
Is this even possible with a locked boot loader?
icotulookn said:
OK thanks yea I'm really lost, I've been searching and I can't find any instruction on this.
Is this even possible with a locked boot loader?
Click to expand...
Click to collapse
Is it bootlooping or just stuck?
You should be able to flash a 4.4.4 system image
Instructions would be:
Download system_4.4.4.7z from http://forum.xda-developers.com/showthread.php?t=2799423
Extract the system_4.4.4.img
Code:
fastboot flash system <path_to_system_4.4.4.img>
blueether said:
Is it bootlooping or just stuck?
You should be able to flash a 4.4.4 system image
Instructions would be:
Download system_4.4.4.7z from http://forum.xda-developers.com/showthread.php?t=2799423
Extract the system_4.4.4.img
Code:
fastboot flash system <path_to_system_4.4.4.img>
Click to expand...
Click to collapse
Its boot looping the boot animation over and over .
OK this is my first Sony phone, I'm sorta familiar with fast boot from my HTC days but its been along time
If I remember correctly I had to install android SDK and fast boot, do I need all the same in this case?
Like i said its been along time and i would be thankfull for any and all instruction given ...
icotulookn said:
OK thanks yea I'm really lost, I've been searching and I can't find any instruction on this.
Is this even possible with a locked boot loader?
Click to expand...
Click to collapse
Again I apologize for posting without refreshing my memory by looking up the older threads. There was two issues with my first post.
1. Stock recovery will not allow flashing older firmware as I mentioned.
2. There is an edited ota zip but it needs to be flashed with custom recovery, which I believe can only be used with an unlocked bootloader.
Hopefully fastboot flashing the system img does the trick.
---------- Post added at 12:22 AM ---------- Previous post was at 12:20 AM ----------
icotulookn said:
Its boot looping the boot animation over and over .
OK this is my first Sony phone, I'm sorta familiar with fast boot from my HTC days but its been along time
If I remember correctly I had to install android SDK and fast boot, do I need all the same in this case?
Like i said its been along time and i would be thankfull for any and all instruction given ...
Click to expand...
Click to collapse
This should do what you need.
http://forum.xda-developers.com/showthread.php?t=2317790
Thank you so much for the fast replies and the assistance, I think I just need the Sony drivers which I can do a search for.
Its getting late so I will give it a go tomorrow and report back.
Fingers Crossed !!
icotulookn said:
Thank you so much for the fast replies and the assistance, I think I just need the Sony drivers which I can do a search for.
Its getting late so I will give it a go tomorrow and report back.
Fingers Crossed !!
Click to expand...
Click to collapse
Easiest way to get the drivers may to download flashtool and grab them from the drivers folder.
ok I'm on a windows 8 comp and I've downloaded and installed adb and fast boot along with the sony drivers ..i have the phone in fast boot mode and usb connected and no matter what i do i can't get the comp to connect with the phone, am i missing something with windows 8 ?
am i doing something wrong with driver installation?
What am i doing wrong? i will gladly and thankfully accept any advice..
icotulookn said:
ok I'm on a windows 8 comp and I've downloaded and installed adb and fast boot along with the sony drivers ..i have the phone in fast boot mode and usb connected and no matter what i do i can't get the comp to connect with the phone, am i missing something with windows 8 ?
am i doing something wrong with driver installation?
What am i doing wrong? i will gladly and thankfully accept any advice..
Click to expand...
Click to collapse
Yes Windows 8 is a pain, Google for "disable driver signature verification in Windows 8" and see if that helps.
blueether said:
Is it bootlooping or just stuck?
You should be able to flash a 4.4.4 system image
Instructions would be:
Download system_4.4.4.7z from http://forum.xda-developers.com/showthread.php?t=2799423
Extract the system_4.4.4.img
Code:
fastboot flash system <path_to_system_4.4.4.img>
Click to expand...
Click to collapse
please help me , i put the system_4.4.4.img in drive C:\ and I'm having a problem remembering how to do the flash boot commands ,,what i have done is "fastboot flash system system_4.4.4.img" but without the quotes and its not working, can u tell me how to direct it to the path of C:\ because I'm pulling my hair out..can u help?
adfurgerson said:
Yes Windows 8 is a pain, Google for "disable driver signature verification in Windows 8" and see if that helps.
Click to expand...
Click to collapse
i think i got it but i can't remember the how to do the fastboot to where the system file is.
the file name is (system_4.4.4.img) and i have it on the C:\ drive
can u tell me the exact command for fast boot to that file?
many many thanks
icotulookn said:
please help me , i put the system_4.4.4.img in drive C:\ and I'm having a problem remembering how to do the flash boot commands ,,what i have done is "fastboot flash system system_4.4.4.img" but without the quotes and its not working, can u tell me how to direct it to the path of C:\ because I'm pulling my hair out..can u help?
Click to expand...
Click to collapse
You need the whole path ex. C:\user\icotulookn\downloads\4.4.4 system img.
I am positive I found the file and was able to copy and paste the path into adb, not sure if that works for fastboot.
adfurgerson said:
You need the whole path ex. C:\user\icotulookn\downloads\4.4.4 system img.
I am positive I found the file and was able to copy and paste the path into adb, not sure if that works for fastboot.
Click to expand...
Click to collapse
i have it directly on C:\ so would i go
fastboot flash system system_4.4.4.img C:\
when i go( fastboot flash system system_4.4.4.img ) it starts but then says<remote:command not allowed
icotulookn said:
i have it directly on C:\ so would i go
fastboot flash system system_4.4.4.img C:\
when i go( fastboot flash system system_4.4.4.img ) it starts but then says<remote:command not allowed
Click to expand...
Click to collapse
I havent used windows (if I can help it) for near 15 years but something like
fastboot flash system C:\system_4.4.4.img
"remote:command not allowed" is probably because of the locked BootLoader, I thought that may happen
Do you know what the fole you deleted was? you may be able to adb push it back onto the system if the GPe boots far enough.
The only other options I can think of are:
Ask Sony for a singed update.zip of the full 4.4.4 (no patch files) so it can be flashed by the stock recovery
Or use adb to do an oem unlock* - but this will wipe DRM keys and render the camera without auto focus
* You could try and run TA backup, but I think it will fail to gain root to do the back up... can you get shell access to the device? "adb shell"
Gonna suggest something off the left field, but if you have access to stock recovery... Have you tried doing a full wipe? I mean, unless ypu royally messed something up elsewhere, flashing system would give you the same end result as a full wipe.
Hopefully this helps.
blueether said:
I havent used windows (if I can help it) for near 15 years but something like
fastboot flash system C:\system_4.4.4.img
"remote:command not allowed" is probably because of the locked BootLoader, I thought that may happen
Do you know what the fole you deleted was? you may be able to adb push it back onto the system if the GPe boots far enough.
The only other options I can think of are:
Ask Sony for a singed update.zip of the full 4.4.4 (no patch files) so it can be flashed by the stock recovery
Or use adb to do an oem unlock* - but this will wipe DRM keys and render the camera without auto focus
* You could try and run TA backup, but I think it will fail to gain root to do the back up... can you get shell access to the device? "adb shell"
Click to expand...
Click to collapse
Some things I am wondering.
1. Can 5.0 update be flashed in stock recovery or would.it fail due to missing files?
2. Can a kernel with recovery be hotbooted to flash the edited 4.4.2 ota?
3. Can the 4.4.4 system img be flashed with flashtool?
4. Is there a fastboot command similar to "adb devices" that will confirm it is connected properly?
I swear that I had the same error trying to return GPe to stock using WIN 8.1 laptop, on WIN 7 desktop it worked fine.
adfurgerson said:
Some things I am wondering.
1. Can 5.0 update be flashed in stock recovery or would.it fail due to missing files?
2. Can a kernel with recovery be hotbooted to flash the edited 4.4.2 ota?
3. Can the 4.4.4 system img be flashed with flashtool?
4. Is there a fastboot command similar to "adb devices" that will confirm it is connected properly?
I swear that I had the same error trying to return GPe to stock using WIN 8.1 laptop, on WIN 7 desktop it worked fine.
Click to expand...
Click to collapse
1. Yes it can but you need to place the zip file in a folder that recovery will recognize (/cache or /sd)
2. Technically yes. However, you still need to be unlocked for that AFAIK.
3. I don't see why not
4. Flashtool will confirm if you have a properly connected devices
There are two rules in life for being successful:
1. Never reveal everything you know;
2.
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.