[Q] I don't think CWM is flashing properly. - Motorola Photon 4G

I've rooted and unlocked my MoPho as of now.
I've attempted to flash joker and romracer's recovery.
However, when I go to check to see how CWM is doing, I only get 4 options:
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
Both of the videos I have watched show other options such as backup's and such. I'm not sure what I'm doing wrong, and any help would be appreciated!

Which clockwork are you using?

I have used this:
http://forum.xda-developers.com/showthread.php?t=1216143
and the
AIO root
The standard cwm (The one from market) gives me all the options.
However, when I try to flash jokers or romracers cwm recovery I just get the 4 basic options again.

Fastboot erase recovery and then use fasboot to install the new, one romracers or jokers your choice. If flashing CM9 id use Jokers.

That is the method I attempted to flash both of them with.
I still get the triangle with the arrow and the android by it that I have to press both the up and down volume buttons to show the recovery screen.

cardinalsfre said:
That is the method I attempted to flash both of them with.
I still get the triangle with the arrow and the android by it that I have to press both the up and down volume buttons to show the recovery screen.
Click to expand...
Click to collapse
Thats the stock recovery.. You ARE unlocked correct? and you flashed it by putting phone into fastboot and with CMD pushing the new recovery?

Yes, I do believe I am unlocked.
Root check shows that I am rooted
Upon boot the phone says, "unlocked"
Yes, I am using the CMD prompt to attempt to flash, following qbking's video instructions.
Edit: Also, the CMD prompt says it has completed the recovery flash.

So you did all this below?
"moto-fastboot erase recovery
moto-fastboot flash recovery recoveryfilename.img"
and it came back saying
"sending 'recovery' (4780 KB)... OKAY [ 0.490s]
writing 'recovery'... OKAY [ 0.544s]"
If so id to redownload the recovery.img and try again..

That worked, at first.
Upon first boot up I was greeted with the right recovery module.
When I went restarted to flash my ROM I was brought back to the original Android Recovery.
Edit: Should I flash on first boot up or should I wait until I can get the recovery to stick?

You have to go into the files and rename the stock recovery to ".bak" to make the new one stick. If I can find the link again, I will post it , or you can Google it? I think that's how I found it to begin with.

Thanks, that worked!

Related

[Q] HTC One Recovery Fail

Sorry, this is likely a noob question. I am working to flash a new rom on my ATT HTC One (cant stand all the ATT BS). I was trying to get the Android_Revolution_HD-One_12.0 working. I have unlocked the phone, and flashed a custom recovery image (stock image linked here http://forum.xda-developers.com/showthread.php?t=2224752) The boot loader now shows unlocked and tampered. Next I attempted to enter the recovery mode, when I select it the phone appears to reboot then shows me a pic of a phone with the green circle of arrows on it for a few secs then pic of a phone with a red exclamation mark. After a few minutes the phone will then reboot and run normally.
I have tried:
1) 'fastboot erase cache' prior to entering recovery
2) adb reboot recovery command
3) GooManager to load TWRP, which it did, but it will not load a rom (says its starting then nothing happens) or reboot into recovery (nothing happens)
All of these result in nothing happening or the same phone with green circle, then phone with red exclamation... I have not been able to access the recovery menu... any other ideas, or am I missing something
Thanks
T
bluecoller33 said:
Sorry, this is likely a noob question. I am working to flash a new rom on my ATT HTC One (cant stand all the ATT BS). I was trying to get the Android_Revolution_HD-One_12.0 working. I have unlocked the phone, and flashed a custom recovery image (stock image linked here http://forum.xda-developers.com/showthread.php?t=2224752) The boot loader now shows unlocked and tampered. Next I attempted to enter the recovery mode, when I select it the phone appears to reboot then shows me a pic of a phone with the green circle of arrows on it for a few secs then pic of a phone with a red exclamation mark. After a few minutes the phone will then reboot and run normally.
I have tried:
1) 'fastboot erase cache' prior to entering recovery
2) adb reboot recovery command
3) GooManager to load TWRP, which it did, but it will not load a rom (says its starting then nothing happens) or reboot into recovery (nothing happens)
All of these result in nothing happening or the same phone with green circle, then phone with red exclamation... I have not been able to access the recovery menu... any other ideas, or am I missing something
Thanks
T
Click to expand...
Click to collapse
I think your trying to flash the stock recovery image. You need to flash either TWRP or CWM custom recoveries. GO to this link and at the bottom it will show the commands to install TWRP from fastboot. It will also give you the link for the newest version of twrp, which is 2.6.0.0 i believe,
http://forum.xda-developers.com/showpost.php?p=42556698&postcount=24958
Hope it helps
Jmarv said:
I think your trying to flash the stock recovery image. You need to flash either TWRP or CWM custom recoveries. GO to this link and at the bottom it will show the commands to install TWRP from fastboot. It will also give you the link for the newest version of twrp, which is 2.6.0.0 i believe,
http://forum.xda-developers.com/showpost.php?p=42556698&postcount=24958
Hope it helps
Click to expand...
Click to collapse
Exactly as he said above. Download twrp (I stuck with 2.3.3.1 bc 2.5 was having problems flashing ROMs)
Put the twrp file in your folder that has fastbootand launch a CMD window (hold shift and right click, there will be an option to launch a CMD window)
Boot into the bootloader and then fastboot (be sure your phone says Fastboot USB)
on the command terminal type:
fastboot devices -- to make sure your device is being recognized (should say HTXXXXXXXXXXXXXX)
fastboot erase cache -- clears cache
fastboot flash recovery recovery.img (recovery.img is the name of the twrp file you downloaded EXACTLY)
Worked like a Champ, thanks for the help. I loaded twrp and the rom installed without a hitch. This phone us definitely faster now that all of the att crappie is gone.

[Q] Soft bricked my Atrix 4g

I am new to cell phone mods. My goal was to gain some experience by rooting and replacing the os image on my Atrix 4G. I use it for my alarm clock which uses an application that won't run on newer version of android than v2.x.x. I successfully rooted and installed super use. I then installed Titanium Backup and did a full backup to sdcard. I installed Rom Manager, chose ClockworkMod Recovery and then the correct image, and told it to flash the recovery partition. Rebooted. Got an error with the android logo and a circle with a triangle. Went back to all the how to's and attempted to install unlockable_bootloader. It now comes up to rsd, seems to fail, then goes into fastboot. Fastboot devices sees it and I can reboot from fastboot but it goes back to the same place. HELP.
Forget about any and all automatic methods, including ROM manager and similar. Good old-fashioned manual methods work best.
Try this guide. http://forum.xda-developers.com/showthread.php?t=2262869
ravilov said:
Forget about any and all automatic methods, including ROM manager and similar. Good old-fashioned manual methods work best.
Click to expand...
Click to collapse
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Phatdaddy said:
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Click to expand...
Click to collapse
Ỳou need to download the image of the recovery partition and flash it using fastboot flash recovery recovery.img
flash recovery failed
andresrivas said:
Ỳou need to download the image of the recovery partition and flash it using fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I previously found a thread that described that process and tried it. Fastboot reported it failed flashing recovery.
That usually happens if the BL is not unlocked (properly).
Phatdaddy said:
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Click to expand...
Click to collapse
reflash the pudding sbf to unlock the bl, then go ahead and flash recovery as advised. if I remember correctly, when it says failed to boot 1, its automatically in rsd, which means just hook it up and let rsd lite do its job then fastboot for recovery
flash boot failed
palmbeach05 said:
reflash the pudding sbf to unlock the bl, th
en go ahead and flash recovery as advised. if I remember correctly, when it says failed to boot 1, its automatically in rsd, which means just hook it up and let rsd lite do its job then fastboot for recovery
Click to expand...
Click to collapse
Installed pudding successfully with RSD Lite. Attempted to flash recovery with "fastboot flash recovery image_name". Reports "sending recovery" and then "writing recovery". When I reboot, it still has has the stock recovery utility.Otherwise, I'm back to stock 2.3.6 except that it reports unlocked upon rebooting. Am I not flashing the correct thing? Thanks for the pointers.
Phatdaddy said:
Installed pudding successfully with RSD Lite. Attempted to flash recovery with "fastboot flash recovery image_name". Reports "sending recovery" and then "writing recovery". When I reboot, it still has has the stock recovery utility.Otherwise, I'm back to stock 2.3.6 except that it reports unlocked upon rebooting. Am I not flashing the correct thing? Thanks for the pointers.
Click to expand...
Click to collapse
hmm, sounds like you're on the 145 build of 2.3.6. Check to see what your phone says in about phone. its going to give you a system version ending in 141 or 145.
palmbeach05 said:
hmm, sounds like you're on the 145 build of 2.3.6. Check to see what your phone says in about phone. its going to give you a system version ending in 141 or 145.
Click to expand...
Click to collapse
This one says "4.5.141". Before undertaking to hack this piece, it was 4.5.145. I have flashed preinstall and boot and attempted to flash recovery. I don't know where it stores the build number. Could it be reporting .141 while really .145 ? I am confident the .145 is correct because we have two phones purchased the same day from same vendor and the other reports .145. I also remember it as .145 but my memory is pretty faulty.
Phatdaddy said:
This one says "4.5.141". Before undertaking to hack this piece, it was 4.5.145. I have flashed preinstall and boot and attempted to flash recovery. I don't know where it stores the build number. Could it be reporting .141 while really .145 ? I am confident the .145 is correct because we have two phones purchased the same day from same vendor and the other reports .145. I also remember it as .145 but my memory is pretty faulty.
Click to expand...
Click to collapse
ok. I think the file we need to look for in order to fix this is in system/etc. its called install-recovery.sh and that file forces stock recovery to be installed. delete that file and try flashing the custom recovery.
palmbeach05 said:
ok. I think the file we need to look for in order to fix this is in system/etc. its called install-recovery.sh and that file forces stock recovery to be installed. delete that file and try flashing the custom recovery.
Click to expand...
Click to collapse
ls of /system/etc/install-recovery.sh says the file does not exist.
When I bricked my atrix i used the xatrix tool to unbrick it. works really well and once unbricked was fully unlocked so was easy to flash new roms
xatrix (dot) webs (dot) com
once on there website click to download tab to get the downloads
This tool will remove everything from phone root, unlock and install cwm. What you do after that is upto you. sometimes its easier to start over then figure out what went wrong when installing a mod.
My problem is now this, I'm recovered, rooted, and unlocked. If I flash recovery with fastboot, it says I am successful but when I reboot the original recovery image still exists.
And thats the part that confuses me. It says 141, but the recovery issue is acting like its a 145. I'm stumped, but i do believe there is an install-recovery.sh script or something thats preventing this thing from sticking after flashing. I'm really baffled by this b/c i ran 141 for the longest time, i did all my rooting, unlocking, and recovery flashing on 141, and got no issues. I could advise that you download and flash the ICS leak (the true leak, not the ROMs we have available) via fastboot and see if that changes the situation, but i don't want to advise you to do something and then a bigger mess appears.
Sent from my MB886 using xda app-developers app
Phatdaddy said:
My problem is now this, I'm recovered, rooted, and unlocked. If I flash recovery with fastboot, it says I am successful but when I reboot the original recovery image still exists.
Click to expand...
Click to collapse
sounds like you had 145 installed and flashed 141 over it without doing a wipe first. i would use cwm recovery and do a factory reset wipe all data and flash the rom you want to run.
overboard1978 said:
sounds like you had 145 installed and flashed 141 over it without doing a wipe first. i would use cwm recovery and do a factory reset wipe all data and flash the rom you want to run.
Click to expand...
Click to collapse
he can't get cwm installed. it may say it gets flashed correctly, but he cannot get cwm to show up and be usable.
as a work around, via fastboot, run the commands:
fastboot erase data
fastboot erase cache
that would cover what factory reset does.
palmbeach05 said:
he can't get cwm installed. it may say it gets flashed correctly, but he cannot get cwm to show up and be usable.
as a work around, via fastboot, run the commands:
fastboot erase data
fastboot erase cache
that would cover what factory reset does.
Click to expand...
Click to collapse
That should do it. If for some reason it doesnt the xatrix tool will wipe everything off the phone and start it over with 141 unlocked bootloader, with cwm. Only automated tool i found that will unbrick phone with rsd lite. Make sure phone is fully charged before starting xatrix tool as it wipes battery fast and if it dies you will need to start over.
Erase cashe was successful, erase data failed. Found reference to additional file to delete but it did not exist either. If I conttinue, I will repost. Thanks for everyone's effort trying to get this working.

How to get rid off TWRP and flash stock recovery

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.

[Q] Stuck On Sony Screen

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.

[Q] Broken system, recovery and bootloader flash failes - What to do?

First of, I'm running Cyanogenmod 12.1 on my Z2.
On the install it vanished my TWRP Recovery, so I decided to reflash it using their app - this was unsucessfull. I thought I would flash it the next day using adb, so I didn't mind.
However in the next hours I needed to reboot the phone - resulting in the Sony logo and nothing more. So I bootet into the CM recovery and tried to reflash the CyanDelta zip - this failed and resulted in "footer is wrong - signature verification failed - Installation aborted". The next thing I tried was flashing a zip by adb recovery sideload - this failed as well and resulted in "protocol fault (no status)".
This was when I tried to boot into the bootloader using the recovery menu entry. The screen got black, the LED lighted up blue and nothing happened forever. The same thing occours when I try to boot into the bootloader by hardware keys (hold VolUp and insert MicroUSB cable).
So, in short:
I can't boot android
I can't install zips by CM recovery
I can't boot into the bootloader [EDIT: I can.]
I can't install nandroid backups since the CM recovery doesn't offer that
Any idea?
If the phone's LED lights up blue it means that you are in fastboot mode (AKA the bootloader) . It is normal for the screen to be black. I suggest that you download a stock FTF and flash it using the windows flashtool application. Your phone is fine. Good luck.
the_crevis said:
If the phone's LED lights up blue it means that you are in fastboot mode (AKA the bootloader) . It is normal for the screen to be black. I suggest that you download a stock FTF and flash it using the windows flashtool application. Your phone is fine. Good luck.
Click to expand...
Click to collapse
Ah, I feel dumb now. I might be damaged from the informational Nexus bootloader.
So, I tried to flash a new recovery - fastboot flash twrp-2.8.6.0-sirius.img - which succeded, but it still boots the CM Recovery. Buh.
Seems like something is overriding the recovery on boot. So lets erase everything:
Code:
fastboot erase system
fastboot erase userdata
fastboot erase recovery
fastboot flash twrp-2.8.6.0-sirius.img
Aaaand - still CM Recovery.
I also tried to flash a stock image as you suggested, however:
Code:
fastboot flash system system.sin
sending 'system' (1800183 KB)...
FAILED (remote: data too large)
finished. total time: 0.002s
No worries, I came from a nexus 4 and it confused me as well at first. Try exacting http://forum.xda-developers.com/xperia-z2/development/kernel-m5-kernel-t2858912 and flashing the boot image via fastboot. That should give you a working recovery.
As I said, flashing a recovery by fastboot results in the CM Recovery.
I just tried to wipe my device using the CM Recovery, it told me it was unable to mount /data - my guess? The filesystem is ****ed up.
EDIT: I got it. Seems like TWRP needs some custom stuff to work (which is provided by CM). Flashing philz worked fine and allowed me to sideload a proper ROM. Everything fine now

Categories

Resources