Related
I'm on (or was) Gingerbread "ota" (second leak), and trying to sbf back to 2.340.
Using 2.340 SBF, on RSD lite 4.8, I get the error:
Failed flashing process. Phone[0000]: Error getting subscriber unit checksum. Device API Error: 0xE003003F. Command: RQRCS (0xE403203F); phone connected
Also, I cannot boot into the recovery.
Please help.
Other possibly relevant info:
Windows XP
RSD LIte 4.8
Not rooted (on GB)
Battery pull, only results in loading up the bootloader again (without pressing any buttons)
Bootloader says:
BOOTLOADER
30.04
Code Corrupt
re-download the SBF file (or check the checksum). Attempt to reflash again.
Will Re-Download SBF, however I've used this SBF before successfully.
I'm also now downloading RSD 4.9 rather than 4.8.
found this: Do a battery pull...then hold the home button and power at the same time to get into recovery. Press the search button, and use the volume button to select factory reset. Let it do it's thing, and select reboot system now...after that, it should boot.
snwagner said:
found this: Do a battery pull...then hold the home button and power at the same time to get into recovery. Press the search button, and use the volume button to select factory reset. Let it do it's thing, and select reboot system now...after that, it should boot.
Click to expand...
Click to collapse
I stated in my OP, that I cannot get into recovery. I know how to, but I cannot.
UPDATE:
Did all that was stated above, and was able to SBF.
However, once the SBF got to the rebooting process, it remained in a bootloop.
I am able to get into recovery now. And I did a factory wipe.
Still in bootloop.
SUggestions?
Pull battery...hold volume up and down then power....after about 3 seconds your phone will load up a black screen with white font and other stuff( debugging mode).... then plug usb to pc....load up rsd lite and flash sbf... if bootloops simply boot into recovery and wipe data... i had the same problem as you and this is how i fixed it....
Sent from my DROIDX using XDA Premium App
mr_villagomez said:
Pull battery...hold volume up and down then power....after about 3 seconds your phone will load up a black screen with white font and other stuff( debugging mode).... then plug usb to pc....load up rsd lite and flash sbf... if bootloops simply boot into recovery and wipe data... i had the same problem as you and this is how i fixed it....
Sent from my DROIDX using XDA Premium App
Click to expand...
Click to collapse
If you read my above post, I said that I did basically exactly what you just said. Im still in bootloops.
Oh sorry i thought that person mentioned holding the power button instead of the volume buttons... did you try rebooting your pc before using rsd again? If that doesnt work maybe try uninstalling drivers and rsd then reinstalling again.
Sent from my DROIDX using XDA Premium App
ITS ALIVE!
THE SOLUTION
I factory wiped like 3-4 times and then rebooted and it worked!
doronster195 said:
ITS ALIVE!
THE SOLUTION
I factory wiped like 3-4 times and then rebooted and it worked!
Click to expand...
Click to collapse
I joined the party late. Yea cwm sometimes wipes like a dirty person. I would always recommend doing it a few times when switching roms or in your case. It can't hurt the phone and sometimes the first wipe doesn't work.
im having the same problem!!!
except im STUCK on the
home+volume up+power screen
i used the same sbf i did the first time from the leaked gb and it worked fine
and well i downloaded nightlies to get liberty on my phone, and i wasnt a big fan of the text msg layout so i tried to clockwork mod (flash) into the deoxed gb but i still had a liberty boot and i thought nothing of it so i continued on and the phone worked fine itll it said gbkeyboard failed and i couldnt do anything!
so i turned it off and when i turned it back on flashwork was on!!! so i flashed the gb leak without root (the first one) and then i wanted root so i did the sbf but this time it said fail and my screen said it was still installing so i pulled the usb and the phone still said installing
so i battery pulled and my phone said code corrupted
so i tried the sbf back x3 still getting the same fail then i got to the part im at now,
code corrupted
battery low
cannot program
i left it on the charger for like an hour and its still "low"
am i soft bricked or hard?
[btw im stuck in the mode]
piax said:
im having the same problem!!!
except im STUCK on the
home+volume up+power screen
i used the same sbf i did the first time from the leaked gb and it worked fine
and well i downloaded nightlies to get liberty on my phone, and i wasnt a big fan of the text msg layout so i tried to clockwork mod (flash) into the deoxed gb but i still had a liberty boot and i thought nothing of it so i continued on and the phone worked fine itll it said gbkeyboard failed and i couldnt do anything!
so i turned it off and when i turned it back on flashwork was on!!! so i flashed the gb leak without root (the first one) and then i wanted root so i did the sbf but this time it said fail and my screen said it was still installing so i pulled the usb and the phone still said installing
so i battery pulled and my phone said code corrupted
so i tried the sbf back x3 still getting the same fail then i got to the part im at now,
code corrupted
battery low
cannot program
i left it on the charger for like an hour and its still "low"
am i soft bricked or hard?
[btw im stuck in the mode]
Click to expand...
Click to collapse
After the FULL sbf fails do the SYSTEM only and you should be good.
piax said:
im having the same problem!!!
except im STUCK on the
home+volume up+power screen
i used the same sbf i did the first time from the leaked gb and it worked fine
and well i downloaded nightlies to get liberty on my phone, and i wasnt a big fan of the text msg layout so i tried to clockwork mod (flash) into the deoxed gb but i still had a liberty boot and i thought nothing of it so i continued on and the phone worked fine itll it said gbkeyboard failed and i couldnt do anything!
so i turned it off and when i turned it back on flashwork was on!!! so i flashed the gb leak without root (the first one) and then i wanted root so i did the sbf but this time it said fail and my screen said it was still installing so i pulled the usb and the phone still said installing
so i battery pulled and my phone said code corrupted
so i tried the sbf back x3 still getting the same fail then i got to the part im at now,
code corrupted
battery low
cannot program
i left it on the charger for like an hour and its still "low"
am i soft bricked or hard?
[btw im stuck in the mode]
Click to expand...
Click to collapse
the low battery keeps it from being able to sbf (which is good because if it dies during an sbf, you are hard bricked. Since i am too lazy to type out full instructions, here is a quote from sysadmin x's guide
IF YOUR PHONE DIES DURING SBF
How to Fix
One thing that you may notice is that when you have this error, your phone will not charge the battery and you'll only be able to see the screen turn on if its plugged into the wall. Somewhere on the screen it will say "Your Battery is Low" and "Cannot Reprogram" or something like that. The easiest way to get through this is to find a friend with a charged battery or go to your local Verizon store and see if they have a demo phone they can use to charge your battery. If you're like me though you will not be lucky in any sense like this so you will have to find the MacGyver inside of you and get a little creative. What you need for this is an old USB cord. One end must be a standard USB cable head and the other can pretty much be anything. Once you have that, follow these steps:
NOTE: I TAKE NO RESPONSIBILITY FOR DAMAGE DONE TO ANY PHONE, BATTERY, ETC. FOLLOW THESE STEPS WITH CAUTION TO AVOID RISK OF DAMAGE.
1. Take your cable and cut off one of the ends, leaving a standard USB plug at the opposite end to plug into your computer.
2. Now you need to strip about and inch of the wire off until you get to the core where you should see 4 colored wires (red, black, white, and green). The colors don't really matter and they may vary, just as long as you can see a red wire and a black wire.
3. Strip off about a quarter inch of the rubber sleeving on the red and black cables, exposing the actual metal wire.
4. Twist the metal strands of each of the wires a couple of times so that all of the wires from the black cable are together and all of the wires from the red cable are together. This is just to make sure that you don't create a short circuit.
5. Here's where it gets a little tricky. You are going to use this cable to make the phone think the battery is fully charged, when in fact you will just be powering the phone using the power from the USB port. Pull out the battery on your phone and find the 4 exposed metal slots (the battery terminals).
6. Each of the far terminals should be labeled with a plus (+) or a minus (-). What you need to do is put exposed leads on the red wire up to the positive terminal and the leads of the black wire up to the negative terminal.
7. While still holding the leads on their respective terminals, slide the battery back into place in the phone. MAKE SURE THE WIRES ARE NOT TOUCHING WHEN YOU PUT THE BATTERY INTO THE PHONE! BAD THINGS COULD HAPPEN ONCE YOU PLUG THE CORD INTO THE COMPUTER!
Note: As tested by parm289, you can skip step 7 and just use the cable to charge the battery if you'd like. He recommends allowing it to charge for 6-7 minutes before placing it back into the phone. Thanks parm!
8. Once the battery is in place and the wires are on the correct terminals but not touching each other, plug the USB cord into the computer. If all has gone as it should, the screen on your phone should come on (may have to press the power button) and the phone should be telling you that the battery charge is okay and that it is okay to program. YAY! Your phone is almost back to normal!
9. Go back up to the previous section in this post that tells you how to reflash the .sbf and follow all of the instructions there. Once that has finished flashing the .sbf to your phone, your phone should be back to working order! You will most likely have to redo the entire setup on your phone but at least your phone is no longer a fancy paperweight
Click to expand...
Click to collapse
Borrow someone's droid x battery, or their phone to charge yours. that's gonna be alot easier than trying to strip the wires down. Also, check with p3droid (team black hat) they've been working on some fancy usb cables that will charge and flash.
thats exactly what the quote said, the numbers were there in case you cant get a charged battery. a last resort besides cutting the cable, you can go to verizon and ask to borrow a show floor battery, and give em yours so you can sbf. verizon is usually pretty nice
wow!!! thanks!
...but
now rsd says flashing failed
and the phone says its still installing
=/
I know the feeling! I have tried getiing into recovery from rooted GB usually just have to battery pull but have had to SBF for the 6th time. GB is great I benchmarked 2144 with Quadrant. Glad you fixed your phone.
And to think I went to Verizon and they wanted to send it to Motorola which they warned might charge me $300...
They also look at the battery to see if there's water damage... so this means you can just get a different battery and voila no water damage...
maybe if i use a different computer???
best part in all this i lost internet connection at home for a week
-.-
FFFMMMLLL
temp on blackberry storm ='[
i DOWNGRADED!!!!|
...ideas?
Here's the story...
I got this phone refurbished for a penny just over a month ago. It's awesome... sexy exterior, simple form, banging specs, super fast loads and renders. However, I tried to root it so I could use a force-Webtop app (for streaming Netflix to my TV), and apparently the phone was updated before it was resold to me, so when I tried to root it bricked.
To root, I used a YouTube link I found on XDA, but got a Failed To Boot error when restarting my phone. After searching for a while, people called it a "soft brick" and said to use RSD Lite to flash the factory sbf. I followed the instructions word for word and now it won't do anything... when I hit the power button, the green light goes on for 2 seconds. That's it.
Is there any hope for my phone? If not, I'm going to take it back to AT&T and try to get it replaced. It was refurbished and the deal is still going on, so they shouldn't balk.
Just an observation, but it sounds like it may need to be charged. You'll need to use a wall charger if it's totally dead.
Sent from my MB860 using XDA App
Even when charging for a while, it gives the same boot error 0x1000 and I can't enter flash mode... says "battery too low to flash" even after plugged in all day.
Did you plug in the phone itself? That may be not enough.
You need somehow charge the battery without your phone. Special cable, wall charger, or direct USB-to-battery connection.
I have this one:
http://www.ebay.com/itm/AC-Dock-Wal...098585?pt=PDA_Accessories&hash=item3368c56359
skywalker993 said:
Even when charging for a while, it gives the same boot error 0x1000 and I can't enter flash mode... says "battery too low to flash" even after plugged in all day.
Click to expand...
Click to collapse
Yes it's a hard brick and no solution (at least not yet). You had a soft brick until you flashed that sbf file. You flashed it and the sbf file is for android 2.2 and people who have 2.3 the use of that sbf file will hard brick the phone.
Ashenphoenix said:
Yes it's a hard brick and no solution (at least not yet). You had a soft brick until you flashed that sbf file. You flashed it and the sbf file is for android 2.2 and people who have 2.3 the use of that sbf file will hard brick the phone.
Click to expand...
Click to collapse
Not true. You can only verify a hard brick if the phone says "Entering Nvflash". As posted before, you need to charge you battery to really verify if the phone is bricked.
Actually, the error should read as this:
SVF:105.1:2
Failed to boot 0X1000
And then it would probably just shut off without even trying to enter any other modes.
http://forum.xda-developers.com/showthread.php?t=1160408
matthew5025 said:
Not true. You can only verify a hard brick if the phone says "Entering Nvflash". As posted before, you need to charge you battery to really verify if the phone is bricked.
Click to expand...
Click to collapse
skywalker993 said:
Here's the story...
I got this phone refurbished for a penny just over a month ago. It's awesome... sexy exterior, simple form, banging specs, super fast loads and renders. However, I tried to root it so I could use a force-Webtop app (for streaming Netflix to my TV), and apparently the phone was updated before it was resold to me, so when I tried to root it bricked.
To root, I used a YouTube link I found on XDA, but got a Failed To Boot error when restarting my phone. After searching for a while, people called it a "soft brick" and said to use RSD Lite to flash the factory sbf. I followed the instructions word for word and now it won't do anything... when I hit the power button, the green light goes on for 2 seconds. That's it.
Is there any hope for my phone? If not, I'm going to take it back to AT&T and try to get it replaced. It was refurbished and the deal is still going on, so they shouldn't balk.
Click to expand...
Click to collapse
did you even unlock the bootloader or did you "just root it b4 flashing the sbf"
Take it back to AT&T. If for some reason they won't take it, go to the Motorola website and see if it still has warranty. I bought it refurbed online as well and when I got the SVF:105.1:2
Failed to boot 0X1000
screen, they were able to fix it and send it back.
Try the auto unlock method for ATRIX 4g. Ur phone is soft bricked that will fix it.
http://forum.xda-developers.com/showthread.php?p=15930466
Sent from my MB860 using xda premium
live4nyy said:
Actually, the error should read as this:
SVF:105.1:2
Failed to boot 0X1000
And then it would probably just shut off without even trying to enter any other modes.
http://forum.xda-developers.com/showthread.php?t=1160408
Click to expand...
Click to collapse
It should flash Entering Nvflash for a brief moment before going blank. It doesn't turn off, it enters Nvflash mode, the last resort of fixing a bricked phone which only moto can use.
Hi All,
OK, I am both new and stuck, I have read every page in the unlocking Atrix thread and the one click root thread but I still do not know what is wrong.
I started off by running the one click root listed here, the root went fine and seemed to work, so I proceeded to install ROM Manager but when I tried to back up my phone the process failed.
I googled the error and it turned out that I did not unlock the Boot Loader, so I followed all the instructions that explained how to do it and nothing worked.
Thinking something must have gone wrong I went back to the one click root tool and unrooted my phone, I checked and everything was working and the phone seemed fine.
So then I started down the longer process of unlocking/rooting here , following the steps to the letter and here is where I come unstuck.
I have a UK carrier free phone so after downloading and installing the RSD Lite software I used the SBF_Flash file but when I selected this file the “Start” button remained greyed out.
I researched this issue and found the international flash called intl-fix-try1.sbf, this file looked like it was going to work, the start button became clickable and the process looked ok.
Once I clicked start the flashing started and percentage done went straight up to 98% in a matter of seconds, then as per the instructions the phone reboots but starts to reboot fully, the process % resets and starts from zero going up in increments of 3%, by the time the process is at 65% my phone has fully booted and is sitting at the lock screen, if I leave it there the process will go up to 100% but the status will still say "in progress" until I swipe the lock screen and then it says complete.
I was doubtful that the root had worked but just to make sure I proceeded to move the phone into Fastboot mode and go through the OEM Unlock process but once I have typed in fastbook oem unlock and hit enter the command prompt just comes up with a message waiting for device to respond and nothing more.
Please help as I am really stuck, I followed your guide to rooting my Galaxy tab 10.1 and had it sorted in minutes, my ICS rom installed and everything backed up via ROM Manager so I am not a total dummy.
Any suggestions?
Kind Regards
Chris
when you tried to flash the sbf on rsd lite did you have the phone pluged into the pc and have it put into rsd lite mode
prolly not if you still seen the lock screen
turn phone off then turn on by holding power button down and volume down
when u see fastboot word on the atrix use volume down to scroll to rsd mode then hit volume up and proceed with rsd lite and the sbf
Here might explain it little more..
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
That is exactly what I did, I have just done it again now . . . .
I clicked start
The console/flash starts,
The phones screen goes black,
Then the Red Motorola M appears
The flash progress jumps to 98%
Console Status says something about USB Pass through/phone rebooting
Then reboots and the Red Motorola M appears again
Then progress carries on and goes up and at 16% by now the phone is now fully in its boot process and by 26% it is at the swipe screen
I have the phone in USB debug mode and the usb connection set to mass storage. Could I be using the wrong SBF file?
Thanks
I have tried that method as well as it is uses a different sbf file called zomgunocklite.sbf when I use that file I an error saying sec_exception: febe, 35, 35 I googled that and it came up with a similar issue but it did not help.
So since my first post I have been speaking to ltdanno360 on here, I just wanted to take the time out to say a MASSIVE THANK YOU.
He has taken me through getting my phone back to a usable state and then all the way through fixing up with the latest bits and pieces.
I have taken up a good few hours of his time and I am now a very, very happy Atrix owner.
It is people like ltdanno360 that make this forum and the internet community such an amazing place. Just imagine driving home from work one day and you car breaks down on the freeway, a stranger stops and spends two hours of his day fixing your car before sending you on your way.
Things like that do not happen often in the real world but people like Danno are great examples of what humanity often misses.
Big Thanks Bro
Awesome guy, awesome forum.
I have a TMobile/MetroPCS GS4 model SGH-M919N that got stuck in a boot loop last week. I was finally able to find working firmware last night and used Odin to flash. Once it got to PASS my phone automatically rebooted with the blue recovery boot text in the top left, but then it just went back into a boot loop. I tried all other firmwares and none of them got to 100% so now I don't know what else I can do.
I have the same issue on a GT-i9505. I was using my phone this evening when it randomly rebooted and just keep rebooting until I removed my battery. After that, it was dead . Flashing stock firmwares like shooting a minigun and nothing works. Smells like a hard brick?
alesu69 said:
I have the same issue on a GT-i9505. I was using my phone this evening when it randomly rebooted and just keep rebooting until I removed my battery. After that, it was dead . Flashing stock firmwares like shooting a minigun and nothing works. Smells like a hard brick?
Click to expand...
Click to collapse
Have you tried replacing the battery? I figured I would try that but I havent gotten around to it yet
Not yet, i have no spare battery. Looks like when i plug the charger my phone just vibrates, like it's rebooting, and it's not showing anything. I found a similar issue here: http://forum.xda-developers.com/showthread.php?t=2532447
Looks like one guy did solve his problem.
*need to mention that by dead I mean it shows the "Samsung Galaxy S4 GT-I9505" logo and also shows "RECOVERY BOOTING", even though I didn't enter in recovery mode. Looks like now it doesn't shows anymore "RECOVERY BOOTING", but still, it doesn't boot. I was able to flash firmwares via odin and kies, but still no luck.
LE: It start booting by.. magic, i got to samsung boot logo, but that's all, crashed again.
After flash with Odin, immediately boot into recovery, perform a factory wipe, and reboot.
The problem is it doesn't boot into recovery.
LE: I managed to flash twrp via odin and boot into recovery, but i have an error:
"Unable to mount /data"
Any ideas?
LE2: Everything is useless, i managed to flash the rom, manage to boot into the rom, but then it will still reboot (which it did). Next step will be maybe to disassemble and clean all contacts.
alesu69 said:
The problem is it doesn't boot into recovery.
LE: I managed to flash twrp via odin and boot into recovery, but i have an error:
"Unable to mount /data"
Any ideas?
LE2: Everything is useless, i managed to flash the rom, manage to boot into the rom, but then it will still reboot (which it did). Next step will be maybe to disassemble and clean all contacts.
Click to expand...
Click to collapse
How did you manage to get into recovery?
harary said:
How did you manage to get into recovery?
Click to expand...
Click to collapse
Yes, but if I leave my phone in recovery (stock or custom), it just either freezes, either reboots, even though i don't do anything, just let it idle.
I can't manage to boot into the ROM 'cause eventually it will reboot. I couldn't finish the setup wizard.
OK so I don't know if this helps, but I managed to at least get past the "blue recovery boot" part. When the phone vibrated I let go of the power while still holding home + vol up, and I managed to get to the android guy with a blue progress bar below him. My phone shut off as the progress bar got 80-90% but now I know it's not impossible to start recovery.
Well, nothing works. After flashing pit file, an 4.4.2 odin prerooted image from here, cf auto root and then twrp, it will still randomly reboot. I manage to get past the boot logo into setup wizard, but phone just freezes after a couple of minutes, can't finish the setup wizard. Also, if i idle in twrp it will reboot sooner or later, tested already.I left my phone idling in twrp just to recharge my battery.
At least i have no more "unable to mount /data" errors.
I finally got it to work, all I had to do is keep flashing twrp and stock firmware back and forth. But it is just one problem after another with this thing, the problem now is every 5 minutes it will freeze and restart, also it tells me there is no sim even though it worked the first time i put it back in.
Operation Ivy said:
I finally got it to work, all I had to do is keep flashing twrp and stock firmware back and forth. But it is just one problem after another with this thing, the problem now is every 5 minutes it will freeze and restart, also it tells me there is no sim even though it worked the first time i put it back in.
Click to expand...
Click to collapse
What do you mean with back and forth?
harary said:
What do you mean with back and forth?
Click to expand...
Click to collapse
It means he flahsed and reflashed many times until he got lucky and it worked. That's what happened to me also. But i have the same issue, phone reboots or freezez after a couple of minutes, even though everything else is installed properly.
Dude, we have the same issue. Btw, is this happening to you too? Like, now and then when the phone freezes, that the screen is turning to a bright yellowish green?
I know a friend who repairs phone hardwares for a living, i gave it to him, i'll let you know how this went.
alesu69 said:
It means he flahsed and reflashed many times until he got lucky and it worked. That's what happened to me also. But i have the same issue, phone reboots or freezez after a couple of minutes, even though everything else is installed properly.
Dude, we have the same issue. Btw, is this happening to you too? Like, now and then when the phone freezes, that the screen is turning to a bright yellowish green?
I know a friend which repairs phone hardwares for a living, i gave it to him, i'll let you know how this went.
Click to expand...
Click to collapse
I got several times into Recovery Mode now, flashed several ROMs. I had no issues with freezing, especially not in TWRP Recovery Mode. But sometimes if i am trying to go into Recovery Mode or i just want to start ROMs, the screen turns into yellow behind the Samsung logo. If i dont take out the battery this wents into a complete white, but nothing happens.
Yes please tell if you got some news..
guys its not hard bricked its a problem wiht your power button
my friend had the same issue and then i killed the battery by letting it keeep bootlooping
then plugged it in and let it charge to around 10% and booted it
just try to press the power button slowly
Joashrox said:
guys its not hard bricked its a problem wiht your power button
my friend had the same issue and then i killed the battery by letting it keeep bootlooping
then plugged it in and let it charge to around 10% and booted it
just try to press the power button slowly
Click to expand...
Click to collapse
But it is sure that the power button is working because i get this blue "recovery booting". Or am i wrong?
So.... bad news, the guy whom i gave the phone to said that it's a short on the motherboard and there's nothing he can't do other than changing the motherboard. If you guys found another solution and that guy is mistaking, let me know.
alesu69 said:
So.... bad news, the guy whom i gave the phone to said that it's a short on the motherboard and there's nothing he can't do other than changing the motherboard. If you guys found another solution and that guy is mistaking, let me know.
Click to expand...
Click to collapse
Replace power button to new one. I have the same problems with s3 and this works. Try it.
Sent from my GT-I9300 using XDA-Developers mobile app
My phone is dead, it's not even charging anymore. The guy whom I give it to said it's a short on the motherboard. You guys managed to solve something with your phones? Or still a dead end?
alesu69 said:
My phone is dead, it's not even charging anymore. The guy whom I give it to said it's a short on the motherboard. You guys managed to solve something with your phones? Or still a dead end?
Click to expand...
Click to collapse
If You can't charge phone... Yup, motherboard is died. If You plug the charger and see something this have to be button but if You plug charger and don't see anything this is motherboard.
Upgraded to MM. Battery usage ridiculous. Barely get 7 hours, used to get 18-20 regularly. So I'm going to factory reset and just wipe it all and start over.
Problem 1. Can't get into recovery. I get the "No command" if I adb reboot recovery, or hold the power/volume+.
I can get into the fastboot/downloader screen with power/vol+.
Problem 2. Tried flashing recovery twrp-3.0.2-0-Z00A.img from fastboot, get "permission denied".
Tried on the "no command" screen to hold power/vol+, all that happens is the phone shuts off after about 8 seconds or so.
I can boot the phone normally and use it, so it's not end of the world, other than battery just sucking the big one.
WIth all the various threads on MM vs LP recovery tools, I'm thinking I dorked something up, but not sure which way to go. All I really want to do is factory reset, but I can go through the moorefield xfst blahblah stuff if I have to, did it once, can do it again.
Or if there's a tethered recovery I can use, I don't really care, I just want it reset.
Any tip appreciated on how to fix my recovery.
First of all, in recovery, you don't need to hold the power button for a long time, just hold it for a second or two, press volume up and then let go of both. This will show you the stock recovery console.
Second, you can try to use the MM to LP full ROM on Asus' site. I'm not sure if it needs to be in a specific MM version or not, though.
Third, when you updated to MM the bootloader was relocked, which is why you can't flash TWRP. There's a thread (or two?) on how to unlock the bootloader in MM.
From what I read, you should try to wipe cache after the upgrade to MM. This solves a lot of problems.
Personally I'm still on LP so I can't help you much more than that.
mrcpu said:
Upgraded to MM. Battery usage ridiculous. Barely get 7 hours, used to get 18-20 regularly. So I'm going to factory reset and just wipe it all and start over.
Problem 1. Can't get into recovery. I get the "No command" if I adb reboot recovery, or hold the power/volume+.
I can get into the fastboot/downloader screen with power/vol+.
Problem 2. Tried flashing recovery twrp-3.0.2-0-Z00A.img from fastboot, get "permission denied".
Tried on the "no command" screen to hold power/vol+, all that happens is the phone shuts off after about 8 seconds or so.
I can boot the phone normally and use it, so it's not end of the world, other than battery just sucking the big one.
WIth all the various threads on MM vs LP recovery tools, I'm thinking I dorked something up, but not sure which way to go. All I really want to do is factory reset, but I can go through the moorefield xfst blahblah stuff if I have to, did it once, can do it again.
Or if there's a tethered recovery I can use, I don't really care, I just want it reset.
Any tip appreciated on how to fix my recovery.
Click to expand...
Click to collapse
Its not so bad. 8 hours is enough time on the phone per day.
Hehe Im sure you are doing it wrong at the no command screen. Go to youtube where you can see the actual timming
Sent from my ASUS_Z00AD using XDA-Developers mobile app
sferrariba said:
Its not so bad. 8 hours is enough time on the phone per day.
Hehe Im sure you are doing it wrong at the no command screen. Go to youtube where you can see the actual timming
Sent from my ASUS_Z00AD using XDA-Developers mobile app
Click to expand...
Click to collapse
Not 8 hours on the phone, in 8 hours, my phone goes from 100% to 0% charge. Always warmish to the touch, and a few texts, few phone calls, few emails, just my usual routine.
However, after a kazillion tries, I was able to get in to recovery, factory reset, and now I'm getting over a day on the battery, like I used to before the MM upgrade.
So I am officially a happy camper now.
J.