I've tried everything I've found to get back to stock recover but I'm always greeted with red triangle. Only way to get to recovery back on line is to re-flash twrp. I've tried fastboot method, flasing new firmware, windroid toolkit... nothing works. I can't even flash CWM. So how do I get that damn leech out of my phone?
[edit]
Can't even flash twrp back on..so no recovery in this phone at the moment. Tried using goomanager, but it didn't do it either.
[/edit]
FIrst of all Which phone do you Have (Int) or At&t , now if you have a stock recovery backup then in that case you can just use fastboot to push the image or use "recovery tool " to push it to the boot partition.
In case you are looking for the int stock recovery for the International version of the HOX+
http://forum.xda-developers.com/showthread.php?p=48470851#post48470851
ethanon said:
FIrst of all Which phone do you Have (Int) or At&t , now if you have a stock recovery backup then in that case you can just use fastboot to push the image or use "recovery tool " to push it to the boot partition.
In case you are looking for the int stock recovery for the International version of the HOX+
http://forum.xda-developers.com/showthread.php?p=48470851#post48470851
Click to expand...
Click to collapse
I have wwe version of HTC One X+. That stock_recovery results the same red triangle. Fastboot pushes it okay but it just doesnt work.
Wiper said:
I have wwe version of HTC One X+. That stock_recovery results the same red triangle. Fastboot pushes it okay but it just doesnt work.
Click to expand...
Click to collapse
Stock recovery is not ment to do much , unless you have an official signed package to push. I feel you want to have a functional recovery like CWM , it can give it a go .
ethanon said:
Stock recovery is not ment to do much , unless you have an official signed package to push. I feel you want to have a functional recovery like CWM , it can give it a go .
Click to expand...
Click to collapse
Problem is that I've tried flashing TWRP and CWM but neither works. Phone boots up ok otherwise, but recovery is gone. Recovery Tool and Goomanager tells that the recovery image flash was completed but it's not or then something else got effed up. fastboot mode works just fine as the hboot.
Tried using RUU, but that doesn't work either because it keeps telling me that the battery level is below 30% and its at 91%. I remember trying RUU few months ago and I ran into the same problem. Back then I tried resetting battery status but that didn't help.
Wiper said:
Problem is that I've tried flashing TWRP and CWM but neither works. Phone boots up ok otherwise, but recovery is gone. Recovery Tool and Goomanager tells that the recovery image flash was completed but it's not or then something else got effed up. fastboot mode works just fine as the hboot.
Tried using RUU, but that doesn't work either because it keeps telling me that the battery level is below 30% and its at 91%. I remember trying RUU few months ago and I ran into the same problem. Back then I tried resetting battery status but that didn't help.
Click to expand...
Click to collapse
I got the same problem with RUU battery stat
Flashing a kernel solved the problem
Flashing another kernel didn't solve that porblem.
Wiper said:
Flashing another kernel didn't solve that porblem.
Click to expand...
Click to collapse
Flash the TWRP recovery.....
and erase the cache also using
this command
Code:
fastboot erase cache
[email protected] said:
Flash the TWRP recovery.....
and erase the cache also using
this command
Code:
fastboot erase cache
Click to expand...
Click to collapse
Tried that as well..no go. Tried even fastboot boot recovery.img but the phone just turns itself off and doesn't load temporary recovery.
Wiper said:
Problem is that I've tried flashing TWRP and CWM but neither works. Phone boots up ok otherwise, but recovery is gone. Recovery Tool and Goomanager tells that the recovery image flash was completed but it's not or then something else got effed up. fastboot mode works just fine as the hboot.
Tried using RUU, but that doesn't work either because it keeps telling me that the battery level is below 30% and its at 91%. I remember trying RUU few months ago and I ran into the same problem. Back then I tried resetting battery status but that didn't help.
Click to expand...
Click to collapse
you are doing it wrong....goomanager and recovery tool CANNOT simply flash onto our devices,
you NEED to do ; fastboot flash recovery <insert recovery name here .img>
Lloir said:
you are doing it wrong....goomanager and recovery tool CANNOT simply flash onto our devices,
you NEED to do ; fastboot flash recovery <insert recovery name here .img>
Click to expand...
Click to collapse
The fastboot method doesn't work. It does say that the flash was successfull, but there's still no recovery.... and besides, when I had stock recovery months ago, I actually did install twrp with goomanager, not with fastboot.
What I have tried:
1. fastboot flash boot stock_recovery.img with fastboot erase cache (red triangle)
2. fastboot flash boot twrp_recovery.img with erase (phone turns off when entering recovery)
3. fastboot boot recovery.img and twrp_recovery.img (doesn't boot to recovery) (phone turns off when entering recovery)
4. Tried using RUU but that hasn't worked for me ever (always the battery level below 30% error)
5. tried fastboot flash recovery and then flash boot and then erase (and first boot, then recovery) (stock and custom kernels)
6. numerous other ways I cant even remember anymore.
If there only were a rom with all the needed img files, I'd try flash all (or flashing them one by one) but haven't found any.
Wiper said:
The fastboot method doesn't work. It does say that the flash was successfull, but there's still no recovery.... and besides, when I had stock recovery months ago, I actually did install twrp with goomanager, not with fastboot.
What I have tried:
1. fastboot flash boot stock_recovery.img with fastboot erase cache (red triangle)
2. fastboot flash boot twrp_recovery.img with erase (phone turns off when entering recovery)
3. fastboot boot recovery.img and twrp_recovery.img (doesn't boot to recovery) (phone turns off when entering recovery)
4. Tried using RUU but that hasn't worked for me ever (always the battery level below 30% error)
5. tried fastboot flash recovery and then flash boot and then erase (and first boot, then recovery) (stock and custom kernels)
6. numerous other ways I cant even remember anymore.
If there only were a rom with all the needed img files, I'd try flash all (or flashing them one by one) but haven't found any.
Click to expand...
Click to collapse
U tried every possible incorrect things.....and didn't even read Llior's post......
To flash a kernel the fastboot command is
Code:
fastboot flash boot boot.img
To flash a recovery the command is
Code:
fastboot flash recovery recovery.img
instead of this u had tried to write the recovery file in boot partition...
and the
Code:
fastboot boot recovery.img
is to enter into the recovery without even having to install it on phone....
and I haven't checked it in HOX+ so better flash the boot.img(Kernel) and recovery.img(Recovery) using the mentioned commands above. and erase the cache....(which you seem to do correctly)...
Wiper said:
The fastboot method doesn't work. It does say that the flash was successfull, but there's still no recovery.... and besides, when I had stock recovery months ago, I actually did install twrp with goomanager, not with fastboot.
What I have tried:
1. fastboot flash boot stock_recovery.img with fastboot erase cache (red triangle)
2. fastboot flash boot twrp_recovery.img with erase (phone turns off when entering recovery)
3. fastboot boot recovery.img and twrp_recovery.img (doesn't boot to recovery) (phone turns off when entering recovery)
4. Tried using RUU but that hasn't worked for me ever (always the battery level below 30% error)
5. tried fastboot flash recovery and then flash boot and then erase (and first boot, then recovery) (stock and custom kernels)
6. numerous other ways I cant even remember anymore.
If there only were a rom with all the needed img files, I'd try flash all (or flashing them one by one) but haven't found any.
Click to expand...
Click to collapse
ok i'll base my assumptions here on you using windows, and you don't have filename endings turned on.
i'm guessing you are renaming the files and adding in .img which is a bad idea, as .img is actually there but hidden. if i'm wrong, then try flashing the recovery with the PROPER file name without touching it.
so for CWMR it would be fastboot flash recovery recovery.img
for twrp it would be ; fastbootflash recovery openrecovery-twrp-2.6.3.0-enrc2b.img
Lloir said:
ok i'll base my assumptions here on you using windows, and you don't have filename endings turned on.
i'm guessing you are renaming the files and adding in .img which is a bad idea, as .img is actually there but hidden. if i'm wrong, then try flashing the recovery with the PROPER file name without touching it.
so for CWMR it would be fastboot flash recovery recovery.img
for twrp it would be ; fastbootflash recovery openrecovery-twrp-2.6.3.0-enrc2b.img
Click to expand...
Click to collapse
I haven't actually renamed anything (just in here to keep it short). And that 1. & 2. was miswritten. I haven't done fastboot flash boot recovery.img but fastboot flash recovery recovery.img.
I have tried exactly that file you posted but it's a no go (also tried other twrp versions and come cwm's too as well as stock recovery image).
Ive tried it with All-in-one tool as well...The weird thing is that all fastboot flashes or with that allinone tool there are no errors ever, only successfull flashes.
Wiper said:
I haven't actually renamed anything (just in here to keep it short). And that 1. was typo. I haven't done fastboot flash boot recovery.img but fastboot flash recovery recovery.img.
I have tried exactly that file you posted but it's a no go (also tried other twrp versions and come cwm's too as well as stock recovery image).
Click to expand...
Click to collapse
are you sure your device is the enrc2b and not the evitareul?
Lloir said:
are you sure your device is the enrc2b and not the evitareul?
Click to expand...
Click to collapse
Yup... But anyway...decided to try that twrp one more time with all-in-one tool, flashed okay but this time the recovery worked and I was able to flash working rom and boot.img. Phone works now, but this was the last time I try to remove twrp.
Related
I installed that flash image gui app, tried a new kernel, I dont like it and tried to reset my backup from the cwm recovery I use to have, but the recovery wasnt there anymore and I had to flash the twrp recovery, which i dislike, and still cant figure out how to get my cwm backup of this rom back.
Check to see if the backup files are in the CWM folder if not then not to be a Debbie Downer but you're SOL. If they are boot into system and flash the recovery using Rom Manager then restore the backup like you normally would
I've tried that... I have twrp recovery, I've tried that and when booting into recovery it just shows the white HTC screen then reboots. I do have the backup in the cwm folder but can't flash it.
Nickdroid86 said:
I installed that flash image gui app, tried a new kernel, I dont like it and tried to reset my backup from the cwm recovery I use to have, but the recovery wasnt there anymore and I had to flash the twrp recovery, which i dislike, and still cant figure out how to get my cwm backup of this rom back.
Click to expand...
Click to collapse
just reflash cwm recovery via fastboot.
How do I do that? I tried flashing it from twrp recovery but it doesn't see the file. It is in the root of my SD. It's cwm 5.0 shooter
cwm backups dont work with twrp backups and vice versa.
Load your phone into the bootloader( power button and volume down).
Then connect to computer via usb, and press power button again to enter fastboot and it should say fastboot usb.
Then in terminal/command prompt execute this command where "recovery.img" is the file name of your cwm recovery.
Code:
fastboot flash recovery recovery.img
then when thats done execute this
Code:
fastboot boot recovery.img
Do i need to rename the cwm file, or use any program on the computer? I can get into the bootloader from my phone if there's an easier way, I don't quite understand that way. Also I have hboot 1.50 if it matters
it doesn't matter the name of the recovery but u just have to use that name instead of recovery.img when u type the command. since you have 1.50 your gonna have to use flashboot to flash anything when you arent able to boot into android.
I assume u have downloaded fastboot, adb, and the google usb drivers, since u have already rooted.
You will use your command prompt on your computer to boot phone into the recovery. See in 1.50 u can't just boot up the phone, goto recovery and flash things. You have to boot into boot loader, press power button when selector is on fastboot (normally default position aka first one in the list), then connect phone via usb to computer. The Red word fastboot should now say fastboot usb.
then execute the commands. "recovery.img" replace with your cwm file name
Code:
fastboot flash recovery recovery.img
Code:
fastboot boot recovery.img
alright I think I figured it out, thanks a lot man!
and don't worry your not the only this happened to. I had this happen to me this weekend. I just got the phone 5 days ago and killed it. So i had a great weekend playing catch up to learn how to reflash on 1.50 HBOOT.
---------- Post added at 11:46 AM ---------- Previous post was at 11:42 AM ----------
also if you still get white screen after you restore with cwm, its means the stock kernel didnt carry over. just reply if that happens.
once you loose its gone why dont you try 4ext custom recovery and gui doe's cause problem's ive used it and it wiped out my boot.img right now im useing 4ext as my custom recovery and it does'nt give any problems at all give it a try
jslim38 said:
once you loose its gone why dont you try 4ext custom recovery and gui doe's cause problem's ive used it and it wiped out my boot.img right now im useing 4ext as my custom recovery and it does'nt give any problems at all give it a try
Click to expand...
Click to collapse
NO bro, the apps works very well. It gets the Job done perfectly.
Suppose you were on a certain ROM and tried flashing a custom kernel with Flash Image GUI, and stuck in bootloop/htc screen , it doesnt mean that the Flash Image GUI caused that.
Even if you tried flashing the same kernel via fastboot boot recovery.img above the same ROM.......the result will be same i.e bootloop/htc screen.
I have a bit of a problem , i changed virus Twrp for the latest official twrp recovery. Now the phone boots in twrp recovery, when i choose to boot in recovery i get the virus recovery, so i have 2 recoverys on my phone it seems and offcourse android isnt booting . Dying for help here... !
Alright, flashed old boot.img back, rom _(Elegancia) is now booting again. Damn this trickier then i am used too.
Tried changing the kernel but android wont start with a new kernel, only with original boot.img
Still recovery is messed up, recovery not showing at bootloader.
Able to enter recovery from the rom. When flashing cwm it shows in the bootloader, but with twrp it doesnt..
When rebooting from the rom i end up in recovery, when rebooting from twrp to recovery the rom boots
Dont know how to fix this ....
phikal said:
I have a bit of a problem , i changed virus Twrp for the latest official twrp recovery. Now the phone boots in twrp recovery, when i choose to boot in recovery i get the virus recovery, so i have 2 recoverys on my phone it seems and offcourse android isnt booting . Dying for help here... !
Alright, flashed old boot.img back, rom _(Elegancia) is now booting again. Damn this trickier then i am used too.
Tried changing the kernel but android wont start with a new kernel, only with original boot.img
Still recovery is messed up, recovery not showing at bootloader.
Able to enter recovery from the rom. When flashing cwm it shows in the bootloader, but with twrp it doesnt..
When rebooting from the rom i end up in recovery, when rebooting from twrp to recovery the rom boots
Dont know how to fix this ....
Click to expand...
Click to collapse
i would advice going back to stock completely and then repeat the process of installing everything all over and use the toolkit its very easy to follow and fast
Did you tried to erase your Recovery?
fastboot erase recovery (enter)
fastboot erase cache (enter)
fastboot flash recovery TWRP_recovery.img (enter)
fastboot erase cache (enter)
Let us know how it went.
Lucky Thirteen said:
Did you tried to erase your Recovery?
fastboot erase recovery (enter)
fastboot erase cache (enter)
fastboot flash recovery TWRP_recovery.img (enter)
fastboot erase cache (enter)
Let us know how it went.
Click to expand...
Click to collapse
Managed to flashed original ruu, unlock again etc.
In bootloader it says: re-locked and beneath a line with security warning. Should be like that after relock ?
Now i have no wifi or network, baseband not showing at settings/info
Relocked again, flashed ruu, wifi and network working so i did flash the right ruu :laugh:
problem solved !
Well today i flashed buttered toast's kernel today, i got a bootloop so to fix that i went on command and did fastboot to flash the stock kernel to fix the boot loop (i've done this before and worked) now what i did was mistakenly i don't even know what was going through my head, i flashed the stock kernel as my recovery. So i wrote "fastboot flash recovery boot.img" instead of "fastboot flash boot boot.img" and so i quickly realized that and did it again except the correct way this time. Realizing that my 4EXT recovery was erased so after successfully booting up my cell i noticed i had wifi error, so i figured ill flash stock kernel again from recovery after i go through "fastboot flash recovery cwm.img" and flash cwm. That did not work, my phone just reboots to system. I do not know what to do. I cant get wifi to download a 4EXt recovery or cwm and flash it through system, but how could i without wifi even if fastboot recovery won't work?
Shariq Ahmed said:
Well today i flashed buttered toast's kernel today, i got a bootloop so to fix that i went on command and did fastboot to flash the stock kernel to fix the boot loop (i've done this before and worked) now what i did was mistakenly i don't even know what was going through my head, i flashed the stock kernel as my recovery. So i wrote "fastboot flash recovery boot.img" instead of "fastboot flash boot boot.img" and so i quickly realized that and did it again except the correct way this time. Realizing that my 4EXT recovery was erased so after successfully booting up my cell i noticed i had wifi error, so i figured ill flash stock kernel again from recovery after i go through "fastboot flash recovery cwm.img" and flash cwm. That did not work, my phone just reboots to system. I do not know what to do. I cant get wifi to download a 4EXt recovery or cwm and flash it through system, but how could i without wifi even if fastboot recovery won't work?
Click to expand...
Click to collapse
Try to boot into recovery from fast boot command
Fastboot boot cwm.img or what ever recovery img you have
Sent from my DOWNGRADED EVO 3D
jcfunk said:
Try to boot into recovery from fast boot command
Fastboot boot cwm.img or what ever recovery img you have
Sent from my DOWNGRADED EVO 3D
Click to expand...
Click to collapse
Well i just got a newer version of recovery from clock work mod's website and i used command prompt to flash it and i got my recovery back, booted up my phone, flashed 4EXT recovery, then flashed a custom kernel with smart flash on and the wifi works now
Thanks for your help though!
see
I unlocked the boot loader, then I rebooted my phone, then rebooted into recovery mode. Once I install either a custom rom, or supersu, even if it works to install, once i try to reboot, it only reboots to TWRP. Even when I reboot to system it still does that. Is my phone just bricked?
bobbymacy said:
I unlocked the boot loader, then I rebooted my phone, then rebooted into recovery mode. Once I install either a custom rom, or supersu, even if it works to install, once i try to reboot, it only reboots to TWRP. Even when I reboot to system it still does that. Is my phone just bricked?
Click to expand...
Click to collapse
No its not bricked.. maybe soft bricked, but not bricked bricked how are you flashing recovery? are you using
fastboot flash recovery twrp.img
or
fastboot flash boot twrp.img
2nd way is incorrect. Try
fastboot flash recovery twrp.img
fastboot erase cache
then boot to twrp and flash rom and let me know what happens. Make sure you are using correct gsm twrp if you are on an att phone.
He probably followed these instructions here which direct you to flash twrp to boot instead of recovery just like you said above.
I don't know why he leaves it up there like that but seeing as it's the first link on Google when you search "root att HTC one m8" , he needs to change it cause I'm sure it's causing plenty of headaches.
Sent from my HTC One_M8 using Tapatalk
an0ther said:
No its not bricked.. maybe soft bricked, but not bricked bricked how are you flashing recovery? are you using
fastboot flash recovery twrp.img
or
fastboot flash boot twrp.img
2nd way is incorrect. Try
fastboot flash recovery twrp.img
fastboot erase cache
then boot to twrp and flash rom and let me know what happens. Make sure you are using correct gsm twrp if you are on an att phone.
Click to expand...
Click to collapse
I did
./fastboot flash recovery twrp.img
because I'm using mac. I didn't erase the cache though. Also on twrp, it says my phone has no os, and installing a custom rom failed to install.
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.