[Q] recovery/bootloader issues - Asus Transformer TF700

after i got my tf700 tablet i unlocked the bootloader and put cwm and cm11 on it, without any problems.
then i tried the same thing on my brothers tf300 i accidentally bricked it, after we bought another one i used the nvflash bricksafe setup on my tf700 so the same thing would not happen to me. then i changed from cwm to philz. later i tried to change the wallpaper in philz and my device froze, so i rebooted and found myself bricked. so i used apx to recover. i got android functionality back but now i have some issues.
1. i cant access recovery, selecting the rck command results in an error: unrecoverable bootloader error (0x00000000)
2. i cant make fastboot flash commands work to reflash a recovery, because the tablet freezes after i hit enter
i have used the "fastboot erase recovery" command too, which seemed to work...
recovery mode usability needs to be restored and possibly a fresh install of the bootloader too.
any help putting it back together either through apx recovery or the android system would be much appriciated!

Did you try to flash the stock blob? Sounds to me like a case for buster99's method:
http://forum.xda-developers.com/showthread.php?t=2179759&page=2

berndblb said:
Did you try to flash the stock blob? Sounds to me like a case for buster99's method:
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
Click to expand...
Click to collapse
Buster99 said:
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
Click to expand...
Click to collapse
thanks for the instructions but i think i will leave this as a last resort as i would rather not have to redo everything i have already done to my device, i hate starting over

A nandroid would have done the trick
Sometimes you have to learn the hard way...
I'm talking about myself: made a nandroid of my CROMi-X installation before flashing CROMBi-KK and then formatted data - without copying the nandroid to microSD - DOH!
Sent from my K00C using Tapatalk

berndblb said:
A nandroid would have done the trick
Sometimes you have to learn the hard way...
I'm talking about myself: made a nandroid of my CROMi-X installation before flashing CROMBi-KK and then formatted data - without copying the nandroid to microSD - DOH!
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
i have a nandroid, on an external source too,
but if you cant get into recovery there is no way to use (or at lease not one that i know)

kirbyonwarpstar said:
i have a nandroid, on an external source too,
but if you cant get into recovery there is no way to use (or at lease not one that i know)
Click to expand...
Click to collapse
In that case, it's easy:
Flash system blob
Flash custom recovery
Restore nandroid
Sent from my K00C using Tapatalk

Related

[Q] How to mount sdcard in ICS Encrypted phone?

I was using a CM9 Nightlies. My company requires us to encrypt our phone.
Now that I was trying to update my phone to the latest version of CM9, I found I couldn't mount /sdcard in CWM recovery...
Is there anyway either to de-encrypt the phone without full-wipe or mount encrypted /sdcard in CWM?
By encrypting your phone you are unable to mount /sdcard currently(stock recovery can flash through it) and the only way you could do it is a full wipe or mounting a "fake" sdcard(idk how to, sorry)
So in short, you pretty much need to full wipe to update
Sent from my ice cream powered Nexus S
I'm running CWM with AOKP and recently encrypted for work policies and now that I want to upgrade and flash a new ROM it is stating that the sd card is unable to be mounted, even after a full wipe in CWM. What is needed? I don't mind wiping but would rather not lose what was on my sd card (titanium backups, etc)
Thanks in advance!
You need to do it within android. Did you do a cwm backup before wiping?
yes, I have a nandroid but it will not restore due to the inability to mount sd storage. Actually it can't even load the option to restore from a nandroid.
Good, now let's hope that actually helps. Unsure if anyone else has tried, but maybe it'll let you flash a new ROM and decrypt it through there. Worst case scenario you end up in the same position as now and you'll have to do an sd wipe, unless someone else knows different. As on the Nexus S the sdcard is seperate to the /data partition (unlike the GN), it flashing a fastboot image shouldn't erase it.
Try to flash a ROM via fastboot images which you can find here. Select your phone and choose an ICS fastboot image (not full ROM, update, etc - must be fastboot). You'll want to download the appropriate image and store it on your computer, then extract the archive until you end up with several files and another archive. You want to have boot.img, system.img and userdata.img ready. Use the following commands in fastboot mode:
fastboot flash boot boot.img
fastboot flash system system.img
[try to boot - if fails, continue]
fastboot flash data userdata.img
The last one should be correct, but maybe it is userdata. Havn't actually tried that one myself - it may not even be necessary (try booting it without this first, if it doesn't work you may need to do this). You can also use the fastboot -w update method but i wouldn't recommend it this time just so we know exactly what is being flashed. After this, boot into android and hope it asks you for decryption information.
edit: also, if those commands don't work, you'll need to flash the contained radio.img and recovery.img files too. It might be picky.
Thanks for the advice. If I flash the stock image via fastboot it sounds like I will lose root and custom recovery since it flashes the bootloader, correct? Will this also wipe my sd card?
If so I may just try to format my sd card in Android so that will be all that I lose versus having to reroot and install CWM again.
Thanks again for your time and info. Very helpful.
*Thanked*
katmandu421 said:
Thanks for the advice. If I flash the stock image via fastboot it sounds like I will lose root and custom recovery since it flashes the bootloader, correct? Will this also wipe my sd card?
If so I may just try to format my sd card in Android so that will be all that I lose versus having to reroot and install CWM again.
Thanks again for your time and info. Very helpful.
*Thanked*
Click to expand...
Click to collapse
You will lose all you data, it will be as if you just bought it, your SD card is NOT wiped
You will only lose recovery as a result of the stock rom script
Oh and you only have to flash boot.img, system.img and userdata.img
Sent from my ice cream powered Nexus S
Thanks guys. Got it flashed to stock and booted (had to use fastboot flash userdata userdata.img, btw) but I did not get any prompt to enter encryption password, and I now have no usb storage showing. I don't even get the "unmounted" icon like I had before. Not sure whats going on.
Any thoughts?
EDIT: I even tried all of these commands as well after I read somewhere it is the bootloader preventing the encrypted sd card from being read
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
Still unable to mount sd card. Man this sucks. Can't use my camera and many apps are kinda hosed without sd card support.
EDIT 2: I tried going into recovery just to see what was there (power on + volume up, then selecting "Recovery" and I got the android with the exclamation point. I guess that means there is no custom recovery anymore which is good but I thought there was a white screen that went into checking for update.zips automatically when you select the stock recovery.
MuthaF$%er...
I just got a pop up stating that the sd card was in an unsupported format and that I should reformat it. I did and all looks good now, but am unrooted and no recovery...dammit.
Guess I should've done that the other day before going through all the fast boot steps. Lost my data either way. Oh well, most was in the cloud anyways.
Thanks again for all the help. Now I know how to use fastboot at least

[Q] Softbricked Tf300t

Hi I have been reading a ton in the forums trying to figure out how to fix my tf300t. A few days ago I updated to the newest CM 10.1 nightly and when it restarted it was stuck at the Asus screen. So I have been able to hold vol down button and get to a screen that says
RCK Android [usb symbol] and Wipe Data
I have fastboot access and thought I would try to fix the problem myself by following instructions on another thread
"pyovue - If you have ADB access then unbricking it should be easy as you can push and edit any file on the system with it as well as fastboot? Or can ADB & Fastboot not mount (not just the sdcard) anything? If you don't care what happens to your tablet MB, then try this....
fastboot -i 0x0b05 erase system
fastboot -i 0x0b05 erase recovery
Then reboot (this should rid you of your bootloop to recovery and nothing should start)
Then download the stock ASUS Rom (from ASUS, look under Firmware)
Then try sending it with fastboot -i 0x0b05 flash system blob (you will have to extract two zips from the firmware files until you get to a file called "blob" then put it in your fastboot)
I almost guarantee if you have fastboot/adb working there is ALWAYS a way to fix it... only a hardbrick is impossible to fix.
"
I get cannot load 'blob' so I tried
fastboot -i 0x0B05 flash recovery recovery.img
seeing as I already had the recovery.img from when I first unlocked, rooted, and put cm 10.1 on it
please help I have no idea what to do and thank you in advance <3
musicfreak58 said:
Hi I have been reading a ton in the forums trying to figure out how to fix my tf300t. A few days ago I updated to the newest CM 10.1 nightly and when it restarted it was stuck at the Asus screen. So I have been able to hold vol down button and get to a screen that says
RCK Android [usb symbol] and Wipe Data
I have fastboot access and thought I would try to fix the problem myself by following instructions on another thread
"pyovue - If you have ADB access then unbricking it should be easy as you can push and edit any file on the system with it as well as fastboot? Or can ADB & Fastboot not mount (not just the sdcard) anything? If you don't care what happens to your tablet MB, then try this....
fastboot -i 0x0b05 erase system
fastboot -i 0x0b05 erase recovery
Then reboot (this should rid you of your bootloop to recovery and nothing should start)
Then download the stock ASUS Rom (from ASUS, look under Firmware)
Then try sending it with fastboot -i 0x0b05 flash system blob (you will have to extract two zips from the firmware files until you get to a file called "blob" then put it in your fastboot)
I almost guarantee if you have fastboot/adb working there is ALWAYS a way to fix it... only a hardbrick is impossible to fix.
"
I get cannot load 'blob' so I tried
fastboot -i 0x0B05 flash recovery recovery.img
seeing as I already had the recovery.img from when I first unlocked, rooted, and put cm 10.1 on it
please help I have no idea what to do and thank you in advance <3
Click to expand...
Click to collapse
What's the question again? If you have fastboot, you can always flash the system blob from your PC. Or you can push the rom (zip) to your internal storage, turn it off and on again. If you select rck on official recovery, it should look for the zip file on its own and proceed to flash it. If you have custom recovery, get to it and flash the same zip file. Make sure you have the right recovery for the rom though. Good luck.
Hi,
and we ansered this kind of prob 2 days ago here: http://forum.xda-developers.com/showthread.php?p=44244313
and yeah - my probs came from an error during cm update.
cheers
-Buster
Buster99 said:
Hi,
and we ansered this kind of prob 2 days ago here: http://forum.xda-developers.com/showthread.php?p=44244313
and yeah - my probs came from an error during cm update.
cheers
-Buster
Click to expand...
Click to collapse
It wouldn't load the blob but i followed that and found that link last night after posting I tried to delete this post but it just allows me to edit
Thanks

[Q] Bootloop with acess to Recovery

I've been using Cromi-X 4.7 since Mid to Late summer for my daily and have had zero issues. Last night however, my TF300 chirped to let me know I had an email, I turned the screen on and then it began bootlooping. I do have access to Recovery, and I've tried wiping and flashing a few other ROMs that I had on my SD card, but they all make it as far as the splash screen then freeze and reboot. So I'm a little confused as to where to go from here.
Recovery: TWRP v2.5.0.0
ww_epad-10.6.1.27.1-20130711
Any advice would be much appreciated. Thanks!
cresco299 said:
I've been using Cromi-X 4.7 since Mid to Late summer for my daily and have had zero issues. Last night however, my TF300 chirped to let me know I had an email, I turned the screen on and then it began bootlooping. I do have access to Recovery, and I've tried wiping and flashing a few other ROMs that I had on my SD card, but they all make it as far as the splash screen then freeze and reboot. So I'm a little confused as to where to go from here.
Recovery: TWRP v2.5.0.0
ww_epad-10.6.1.27.1-20130711
Any advice would be much appreciated. Thanks!
Click to expand...
Click to collapse
If you can use recovery, I suppose you can use fastboot too?
Try the following:
fastboot erase misc
fastboot erase staging
fastboot reboot
If that won't work, look for Buster99's script to erase everything and reflash stock Asus ROM. Fixed issues for a lot of people allowing you a fresh start.
Sent from my TF300T using Tapatalk
f69m said:
If you can use recovery, I suppose you can use fastboot too?
Try the following:
fastboot erase misc
fastboot erase staging
fastboot reboot
If that won't work, look for Buster99's script to erase everything and reflash stock Asus ROM. Fixed issues for a lot of people allowing you a fresh start.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
Thankyou! I had to re-educate myself on Fastboot but once that was done I was able to try your suggestions. Your first one did not do the trick, but Buster99's got me most of the way. I had to reflash the TWRP near the end of his process to get it to work for me.
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash recovery C:\Users\Jeff\Downloads\twrp-2.5.0.0-JB.blob (THIS IS THE LINE I ADDED)
fastboot -i 0x0B05 flash system C:\Users\Jeff\Documents\WW_epad-user-10.6.1.15.3\blob
fastboot -i 0x0B05 reboot
So maybe my recovery was messed up? At anyrate, it looks like I'm back in action. For anyone who needs to follow how all this was done, there is a good fastboot tutorial here. and here is the link to Buster99's solution.
Thankyou for pointing me in the right direction f69m!
cresco299 said:
Thankyou! I had to re-educate myself on Fastboot but once that was done I was able to try your suggestions. Your first one did not do the trick, but Buster99's got me most of the way. I had to reflash the TWRP near the end of his process to get it to work for me.
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash recovery C:\Users\Jeff\Downloads\twrp-2.5.0.0-JB.blob (THIS IS THE LINE I ADDED)
fastboot -i 0x0B05 flash system C:\Users\Jeff\Documents\WW_epad-user-10.6.1.15.3\blob
fastboot -i 0x0B05 reboot
So maybe my recovery was messed up? At anyrate, it looks like I'm back in action. For anyone who needs to follow how all this was done, there is a good fastboot tutorial here. and here is the link to Buster99's solution.
Thankyou for pointing me in the right direction f69m!
Click to expand...
Click to collapse
Oops, careful!
You are using the wrong recovery.
For the bootloaders coming with 10.6.* ROMs you need to use TWRP -42.
Don't use -jb, that is for the older 10.4.* bootloaders.
Sent from my TF300T using Tapatalk
f69m said:
Oops, careful!
You are using the wrong recovery.
For the bootloaders coming with 10.6.* ROMs you need to use TWRP -42.
Don't use -jb, that is for the older 10.4.* bootloaders.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
That would explain why I had to reinstall an updated TWRP to access recovery. I know just enough to make my self dangerous
Thank you again.

Bricked XT1032

So I have a cousins XT1032 I'm trying to fix. What happens is that it doesn't want to boot. After the Motorola Bootanimation it goes to a Black screen, I've read about going into Recovery and Factory Resetting or Wiping Cache and I've done it hundreds of times now and it hasn't changed a thing. I've tried flashing the Stock ROM and everything flashes correctly but when I reboot it goes to the same Black Screen after the Boot animation. I've tried putting a custom recovery (CWM, TWRP, Philz) and it flashes, but when I press Recovery on the phone after flashing, it boots into the Stock Dead android recovery. I'm not sure what else to do. So any help would be great, thanks.
Hmm, so I found something weird... So I said that I had factory reset man times, using Fastboot and Android Recovery, well today I was trying to convert it to a GPE to see if it would work and it didn't. It still did the same thing (black screen after bootanimation) So I tried to Sideload a ROM through Android Recovery and it aborted the installation so I pressed on the android recovery. "Update from SD Card" or something like that and I saw that my cousins old files were still there, they haven't been erased...So I'm starting to think that this is a defect...
But anyways, If anyone knows the solution I would really appreciate it!
No one? :/
Gus194 said:
No one? :/
Click to expand...
Click to collapse
If your cousins files are still there then you can get them onto your computer, if you have cwm or twrp use adb sideload to transfer the contents on to your computer directly. Then you can try whatever you want knowing that the files are back since im guessing thats the most important.
1st: Download http://forum.xda-developers.com/showthread.php?p=42407269#post42407269 ??? Install this
2nd: Put phone in recovery either into cwm or twrp, then open up minimal adb
3rd: Use this command to pull your files into your computer, these will be located in you hdd where you go into program files and etc, basically the root of your computers hdd at C:\
Command = adb pull /sdcard/ c:\
Hopefully this helps you, good luck, mate.
NextGenGTR said:
If your cousins files are still there then you can get them onto your computer, if you have cwm or twrp use adb sideload to transfer the contents on to your computer directly. Then you can try whatever you want knowing that the files are back since im guessing thats the most important.
1st: Download http://forum.xda-developers.com/showthread.php?p=42407269#post42407269 ??? Install this
2nd: Put phone in recovery either into cwm or twrp, then open up minimal adb
3rd: Use this command to pull your files into your computer, these will be located in you hdd where you go into program files and etc, basically the root of your computers hdd at C:\
Command = adb pull /sdcard/ c:\
Hopefully this helps you, good luck, mate.
Click to expand...
Click to collapse
Thanks for trying to help man, but like I said if I try to flash anything like a Recovery or anything else it shows that it flashes correctly but when I try to get into recovery it just boots into the dead android recovery one
Gus194 said:
Thanks for trying to help man, but like I said if I try to flash anything like a Recovery or anything else it shows that it flashes correctly but when I try to get into recovery it just boots into the dead android recovery one
Click to expand...
Click to collapse
When you flash the recovery do you get an error like some mb error? Try to flash this recovery, it worked for me, i had a similar problem because i flashed android l and the bootloader was different so you need a compatible recovery, i downloaded one today, i need to find link, stay online
---------- Post added at 06:51 AM ---------- Previous post was at 06:46 AM ----------
Gus194 said:
Thanks for trying to help man, but like I said if I try to flash anything like a Recovery or anything else it shows that it flashes correctly but when I try to get into recovery it just boots into the dead android recovery one
Click to expand...
Click to collapse
Here is the recovery i used that worked for me Link for download: https://docs.google.com/file/d/0B3sIJMABIGzAelpNX1RUZUFvV0U/edit
I think you know but enter bootloader than connect your usb and fastboot flash recovery recovery.img
NextGenGTR said:
When you flash the recovery do you get an error like some mb error? Try to flash this recovery, it worked for me, i had a similar problem because i flashed android l and the bootloader was different so you need a compatible recovery, i downloaded one today, i need to find link, stay online
---------- Post added at 06:51 AM ---------- Previous post was at 06:46 AM ----------
Here is the recovery i used that worked for me Link for download: https://docs.google.com/file/d/0B3sIJMABIGzAelpNX1RUZUFvV0U/edit
I think you know but enter bootloader than connect your usb and fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Alright, let me try that Recovery! Thanks so much. By the way it says: Mismatched partition size (recovery)
when I try to flash the recovery
Gus194 said:
Alright, let me try that Recovery! Thanks so much. By the way it says: Mismatched partition size (recovery)
when I try to flash the recovery
Click to expand...
Click to collapse
Im sure it should work, i had the same error i believe, lol, today i tried changing my dalvik size in build.prop and my phone wasnt booting so i tried flashing recovery and i had the error you was having, then i used these adb commands, i guess i messed my phone up so i can help you in a couple hours later on, lol, coincidences! xD Did it work for you?
NextGenGTR said:
Im sure it should work, i had the same error i believe, lol, today i tried changing my dalvik size in build.prop and my phone wasnt booting so i tried flashing recovery and i had the error you was having, then i used these adb commands, i guess i messed my phone up so i can help you in a couple hours later on, lol, coincidences! xD Did it work for you?
Click to expand...
Click to collapse
Just flashed the recovery you linked to. And nope, didn't do anything. I still boot up to the Dead Android guy recovery. Hmm I'm starting to think that this is a Hardware Defect
Gus194 said:
Just flashed the recovery you linked to. And nope, didn't do anything. I still boot up to the Dead Android guy recovery. Hmm I'm starting to think that this is a Hardware Defect
Click to expand...
Click to collapse
Since you flashed GPE, try doing this, flash back Motorola stock without doing the erase commands and then try flashing this recovery.
---------- Post added at 07:03 AM ---------- Previous post was at 06:58 AM ----------
Gus194 said:
Just flashed the recovery you linked to. And nope, didn't do anything. I still boot up to the Dead Android guy recovery. Hmm I'm starting to think that this is a Hardware Defect
Click to expand...
Click to collapse
This is something i found on a thread --- You have to enter recovery straight after you flash it, or the old one will replace it,when you exit the new recovery there will be an option to disable the old recovery.
NextGenGTR said:
Since you flashed GPE, try doing this, flash back Motorola stock without doing the erase commands and then try flashing this recovery.
---------- Post added at 07:03 AM ---------- Previous post was at 06:58 AM ----------
This is something i found on a thread --- You have to enter recovery straight after you flash it, or the old one will replace it,when you exit the new recovery there will be an option to disable the old recovery.
Click to expand...
Click to collapse
Yea I know about that entering recovery right after flashing and I've done that every time. It never has worked. Hmm something is wrong with this phone. I've factory resetted the phone at least 10 times using the Recovery and another 10 times using Fastboot and the files are still there. I think that it's definitely is a Hardware problem :/ dang
Gus194 said:
Yea I know about that entering recovery right after flashing and I've done that every time. It never has worked. Hmm something is wrong with this phone. I've factory resetted the phone at least 10 times using the Recovery and another 10 times using Fastboot and the files are still there. I think that it's definitely is a Hardware problem :/ dang
Click to expand...
Click to collapse
I do not know if this will work but it is a wild guess, i had a htc sensation and i was able to use adb commands at the start of boot even when it didnt boot up, so what i am trying to say is boot up your phone and then plug in your usb cable and then try the adb pull command i gave you earlier, im sure this wont work but give it a shot.
NextGenGTR said:
I do not know if this will work but it is a wild guess, i had a htc sensation and i was able to use adb commands at the start of boot even when it didnt boot up, so what i am trying to say is boot up your phone and then plug in your usb cable and then try the adb pull command i gave you earlier, im sure this wont work but give it a shot.
Click to expand...
Click to collapse
It probably would work If the phone had USB Debugging on before it got bricked :/ I'm about to give up on this phone. I've tried everything lol.
I'm thinking that the Partitions are corrupted since none of them will format using fastboot. It just says it cant format Raw type partitions or something like that
You have not done ALL of the necessary fastboot commands when flashing the firmware image. Make sure you have an XT1032 4.4.4 image.
Do the following manually, report any errors. Use no other fastboot commands other than those stated below.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot​

Nothing can be written on internal storage (insert sd card error on camera, etc)

I posted this on reddit...but didn't get much help...i hope the geniuses at xda can help me
As the title says, the camera app (any camera app) won't work because as you start any of them, it asks to insert the sd card, but this is a 2013 Nexus 5...so it doesn't have an sd card.
I've done a fair amount of research and the only thing that seems to be mentioned is factory reset. I've done that...both through the settings and twrp. The phone has a stock marshmallow rom.
I tried to download any other file and it won't let me download anything becauase the "sd card" is not available. So it's as if the internal sd card isn't mounted? how do I fix this? I don't have a computer nearby to do anything with adb...any help would be GREATLY appreciated...
The amount of storage according to the settings is correct (3gb used of 12 gb..16gb nexus 5)...all app permissions are correct. I've reflashed two different stock firmwares with the exact same result.
Try this:
boot into fastboot;
run this fastboot command: fastboot erase recovery (to erase existing recovery);
run this fastboot command: fastboot flash recovery recovery.img (to flash stock recovery from stock ROM)
run this fastboot command: fastboot erase userdata;
run this fastboot command to flash the usedata img from the stock ROM: fastboot flash userdata userdata.img;
boot into stock recovery and perform a factory wipe/reset and wipe cache;
reboot.
audit13 said:
Try this:
boot into fastboot;
run this fastboot command: fastboot erase recovery (to erase existing recovery);
run this fastboot command: fastboot flash recovery recovery.img (to flash stock recovery from stock ROM)
run this fastboot command: fastboot erase userdata;
run this fastboot command to flash the usedata img from the stock ROM: fastboot flash userdata userdata.img;
boot into stock recovery and perform a factory wipe/reset and wipe cache;
reboot.
Click to expand...
Click to collapse
I'll try that tonight or tomorrow morning. Where do you suggest I download recovery.img (the stock recovery)?
Thanks for the help one way or another.. Hehe
The stock Google images are here: https://developers.google.com/android/nexus/images?hl=en
I assume the phone has an unlocked bootloader since you were able to flash stock ROMs.
What did you do between all being fine and now this problem?
Sent from my Xperia z5 using Tapatalk
Ben36 said:
What did you do between all being fine and now this problem?
Sent from my Xperia z5 using Tapatalk
Click to expand...
Click to collapse
I sold the phone to someone I know. I had a rom (i can't remember which)...so before i sold the phone, i encrypted it, wiped it clean, flashed the stock rom (and radio)....and did a factory reset.
audit13 said:
Try this:
boot into fastboot;
run this fastboot command: fastboot erase recovery (to erase existing recovery);
run this fastboot command: fastboot flash recovery recovery.img (to flash stock recovery from stock ROM)
run this fastboot command: fastboot erase userdata;
run this fastboot command to flash the usedata img from the stock ROM: fastboot flash userdata userdata.img;
boot into stock recovery and perform a factory wipe/reset and wipe cache;
reboot.
Click to expand...
Click to collapse
Thanks! I used the factory images and flashed everything from the compressed archive and it worked..you're a lifesaver. I guess I had to go further and reset everything..but thanks again!

Categories

Resources