Related
I had a working Transformer until earlier today when the OTA update came along. Having accepted installation, my device now gets to the Eee Pad / ASUS logo and hangs there (waited for about 45 minutes after the update). Trying to reboot into recovery gives:
Android WW_epad-user bootloader < e> released by "WW_epad-8.2.3.6-20110414".
Checking for android ota recovery
Booting recovery kernel image
It does not give me the Up to recovery, Down to wipe option.
Any thoughts on how I might recover the device?
Many thanks in advance for your help.
Ohh **** that dont sound good
Sorry i cant help with any advice on fixing it, apart from trying a factory reset ?
Did you apply the update with under 50% of the battery available ?
No, full. And connected to the mains.
I cant get any option to do a full wipe, it never asks me.
morak said:
No, full. And connected to the mains.
I cant get any option to do a full wipe, it never asks me.
Click to expand...
Click to collapse
There are some things you can try in this thread - http://forum.xda-developers.com/showthread.php?t=1032374
Here a few key combinations for anyone interested:
VOL_DOWN + POWER (continue holding VOL_DOWN when it starts booting until you get a prompt) = Bootloader which offers two prompted options: (1) Recovery if you press VOL_UP within 5 seconds or (2) Data wipe if you press VOL_UP later. None of these seem to offer any USB devices like fastboot etc.
VOL_UP + POWER or VOL_DOWN + VOL_UP + PLUG IN USB = NVFlash mode. It clearly is the NVFlash APX device that we see appearing, but it barfs as soon as we run any sort of nvflash on it (Many Windows and Linux versions have been tried). Please note that in this mode the screen stays completely blank and the only way to get out of it is the following option:
Hold POWER for ~10s = Forced power off. This always helps if you are stuck in some weird mode and nothing on the screen
Dont know if any of these key presses will work on yours, worth a try to get it to recover ?
Yeah I had seen that thread. Unfortunately no joy from either option. I dont get the prompt when I do VOL DOWN+POWER, just seems to go straight into recovery. And as the post says, NVflash doesn't help at the moment.
Can't even seem to get the ADB USB devices to show up, I can only get the APX device which seems to be fairly useless ATM. Looks like I may have to RMA the thing.
What is that small hole next to HDMI port? Did you try that, it may just be button (use paper pin) to reset it to factory default?
Or maybe microphone ? lol i personnaly don't think those tablets would actually have a reset button, would check the manual first before sticking a paper pin into every holes...
My Transformer just came in, I accepted the OTA update and while installing it saw this thread and had a dreadful feeling. Thankfully, it rebooted fine and is working... sounds like something's wrong with yours unfortunately OP .
If you haven't tried the 10 second power button method as mentioned in an earlier post it's definitely worth a try.
stuntdouble:
I thought the 10 sec power button thing just turned the device off. Is there something else I can do that I am missing?
I think it clears cache and/or ram too. I'm not saying it will definitely fix your problem, it may not, but if it was me I'd try everything. It won't damage anything so don't worry.
Have you tried getting into the Clockwork mod recovery? You need to place it on an external microsd and when you do the holding down when switching on thing, it goes into the recovery on the card instead of the stock one. It might allow you to flash a rom to get it running again.
You can find the Clockwork recovery with instructions here
http://android.modaco.com/content/a...od-recovery-for-the-asus-eee-pad-transformer/
Good idea, unfortunately it didnt work. It doesnt appear to be allowing me to get to the point where it will read EP101_SDUPDATE.zip from the SD.
You sure filename is EP101? Shouldnt it be TF?
All the instructions call for EP101, but I tried TF too just in case!
dotpro said:
What is that small hole next to HDMI port? Did you try that, it may just be button (use paper pin) to reset it to factory default?
Click to expand...
Click to collapse
It's a microphone. If you go poking a paperclip in there, good luck claiming under warranty.
Same thing just happened to me... reboot for update, stuck at boot screen.
Not sure if we can find a EP101_SDUPDATE.zip for higher than 20110414 if that'd be a fix or what... or even a PC restore process.
hecatomb said:
Same thing just happened to me... reboot for update, stuck at boot screen.
Not sure if we can find a EP101_SDUPDATE.zip for higher than 20110414 if that'd be a fix or what... or even a PC restore process.
Click to expand...
Click to collapse
sonofab*tch same here. You would think they would warn people that this could happen. This is ridiculous. Their worthless phone tech kept traying to get me to hold f9. I wanted to reach through the phone and punch him.
So you are getting bricked units with stock? No modications or rooted devices?
stuntdouble said:
So you are getting bricked units with stock? No modications or rooted devices?
Click to expand...
Click to collapse
Root doesnt work on the US devices, also, OP hadnt rooted.
I went out partying last night, woke up to a crack on my nexus 5 and wouldnt turn on but the led would flash red. I figured it lost its charge. Charge the phone for few hours, phone would turn on and off right away as if it still were not charged. It would than shut off but restart to a screen that said Firmware Update- Please wait while it installs- B100. Nothing would install, it would stay at 0%. So I held the power button and now, it only turns on to the google sign and keeps looping from there. I tried to turn it on in recovery mode but that doesnt work either. My phone was never rooted, bootloader never unlocked and I never put it in debugging. I dont know what to do!
so the ol' 3-button combo doesn't get you to the bootloader?
Yes, it does. Forgot to mention that.
tonytouch311 said:
Yes, it does. Forgot to mention that.
Click to expand...
Click to collapse
I don't know what you did, but your phone is not bricked. Hope you have a recent backup. If you can get into the bootloader I'd try a factory reset in recovery. If that doesn't work then you're going to have to unlock the bootloader and try to flash the factory image. None of this may work as idk what you did to your phone, but this is what I'd do.
Is flashing a factory image/unlocking bootloader possible even tho I can't get into the settings menu to turn on debugging option?
tonytouch311 said:
Is flashing a factory image/unlocking bootloader possible even tho I can't get into the settings menu to turn on debugging option?
Click to expand...
Click to collapse
Yes, adb and fastboot are not related.
Sent from my Nexus 10 using Tapatalk 4
Are there any guides you all might suggest that are easy to understand?
Ask your friends what happened last night. Sounds like a good party
==**Team Nexus 5 sucks.**==
-Underpowered battery for a 5inch 1080p screen that is non-removable. Weak generic antenna that drops signal. Worst speaker of any device on the market. Cheap plastic build
tonytouch311 said:
Are there any guides you all might suggest that are easy to understand?
Click to expand...
Click to collapse
Alright, here. The catch-all solution: flash the factory image as in this thread http://forum.xda-developers.com/showthread.php?t=2513701.
Just remember to cd to your adb directory, I made that mistake and almost fainted because I thought my device was totally broken when fastboot devices listed nothing.
dicecuber said:
Ask your friends what happened last night. Sounds like a good party
==**Team Nexus 5 sucks.**==
-Underpowered battery for a 5inch 1080p screen that is non-removable. Weak generic antenna that drops signal. Worst speaker of any device on the market. Cheap plastic build
Click to expand...
Click to collapse
Really?? Is this your sig or just something totally irrelevant that you decided to insert into your reply? Do you even own one?
droid_<3er said:
Really?? Is this your sig or just something totally irrelevant that you decided to insert into your reply? Do you even own one?
Click to expand...
Click to collapse
It's his sig. Just ignore him.
I was able to flash everything and it seemed successful. But, I can only get as far as GOOGLE and than it keeps rebooting.
tonytouch311 said:
I was able to flash everything and it seemed successful. But, I can only get as far as GOOGLE and than it keeps rebooting.
Click to expand...
Click to collapse
If that's the case it sounds like you may have knocked something loose internally when whatever happened that caused the damage to your screen. Possibly a solder point or a cable coming loose.
Opened up the back cover, looks like condensation.....ill leave it alone for a few days and try again.
Reset
tonytouch311 said:
I was able to flash everything and it seemed successful. But, I can only get as far as GOOGLE and than it keeps rebooting.
Click to expand...
Click to collapse
Did u do another factory reset after last flash as this may need doing on some phones from what I've watched on good old YouTube...Good luck..
^Why would he factory reset when the phone is wet? You'll short circuit it that way..
The only method of a factory reset I've read about was turning on in Recovery, waiting for the little android, and holding Vol + and Power. Thing is my phone would never get to the little android, just loop on the GOOGLE introduction. Is there another method to factory reset?
tonytouch311 said:
The only method of a factory reset I've read about was turning on in Recovery, waiting for the little android, and holding Vol + and Power. Thing is my phone would never get to the little android, just loop on the GOOGLE introduction. Is there another method to factory reset?
Click to expand...
Click to collapse
Turn your phone off. Then hold power + vol down. It should boot into the boot loader. You'll see a "start" Then use the vol rocker to toggle to recovery. Once there push the power button. You should be in recovery. Then use the vol rocker to toggle to factory reset. Then use power to select it.
jd1639 said:
Turn your phone off. Then hold power + vol down. It should boot into the boot loader. You'll see a "start" Then use the vol rocker to toggle to recovery. Once there push the power button. You should be in recovery. Then use the vol rocker to toggle to factory reset. Then use power to select it.
Click to expand...
Click to collapse
Thats the method I'm unable to use...I was hoping there might be a string of code I could type into a command prompt being that I can only turn on the phone into the boot loader.
tonytouch311 said:
Thats the method I'm unable to use...I was hoping there might be a string of code I could type into a command prompt being that I can only turn on the phone into the boot loader.
Click to expand...
Click to collapse
Try
fastboot reboot recovery
Edit, sorry that's not going to work. Find the stock recovery image. Then try
fastboot boot recovery.img
So I was able to boot in recovery and factory reset, although the problem still persists. I will try and flash all images tomorrow. Thanks for all the help! Happy holidays!
I'm going to try to keep this as simple as possible as I don't really know what I did wrong or how I ended up where I am now.
I have a Samsung Galaxy 8+ and I decided to root it. I decided to follow this guy's instructions on how to do it: youtube.com/watch?v=eh-I4uxAmUY.
I follow his steps and am bought to the "Unmodified System Partition" menu after having gone through the process of factory resetting, wiping my data and using Odin to flash twrp-3.1.0-r1_dreamlteks.
The problem is that now the touch screen is unresponsive. It does literally nothing.
I am stuck at the screen that says "Keep System Read only?" where I have to "Swipe to Unlock Modifications", but find myself unable to do so because my touch screen doesn't let me swipe!
So now I'm panicking:
Firstly, I can't get the phone to shut down. Holding the power button does nothing, even if I hold it for a full minute.
Secondly, I can't boot the phone into anything except this unresponsive TWRP thing.
Thirdly, my computer no longer recognizes my phone when I try to connect it via USB (might be unrelated?).
How ****ed am I?
Is my phone just bricked now?
Can I save this rooting attempt in any way, or at least revert to the stock?
Will bringing the phone to a retailer help me in any way, or have I already broken the warranty?
Please guys I am desperate for some assistance here.
ViRALiC said:
I'm going to try to keep this as simple as possible as I don't really know what I did wrong or how I ended up where I am now.
I have a Samsung Galaxy 8+ and I decided to root it. I decided to follow this guy's instructions on how to do it: youtube.com/watch?v=eh-I4uxAmUY.
I follow his steps and am bought to the "Unmodified System Partition" menu after having gone through the process of factory resetting, wiping my data and using Odin to flash twrp-3.1.0-r1_dreamlteks.
The problem is that now the touch screen is unresponsive. It does literally nothing.
I am stuck at the screen that says "Keep System Read only?" where I have to "Swipe to Unlock Modifications", but find myself unable to do so because my touch screen doesn't let me swipe!
So now I'm panicking:
Firstly, I can't get the phone to shut down. Holding the power button does nothing, even if I hold it for a full minute.
Secondly, I can't boot the phone into anything except this unresponsive TWRP thing.
Thirdly, my computer no longer recognizes my phone when I try to connect it via USB (might be unrelated?).
How ****ed am I?
Is my phone just bricked now?
Can I save this rooting attempt in any way, or at least revert to the stock?
Will bringing the phone to a retailer help me in any way, or have I already broken the warranty?
Please guys I am desperate for some assistance here.
Click to expand...
Click to collapse
You have voided your warranty so you can't take it down to the shop and get it replaced.
It isn't fully bricked because you can still boot into an "os" that isn't fully functional. It ain't recognised because you have to swipe past this and hop into the ADB sideload interface. Btw, try holding your home button, power button and volume up (or down) and report results.
If I was you, I would wait till the battery drains and shuts off and then let it be off for the rest of the night or something and then try again.
RAZERZDAHACKER said:
You have voided your warranty so you can't take it down to the shop and get it replaced.
It isn't fully bricked because you can still boot into an "os" that isn't fully functional. It ain't recognised because you have to swipe past this and hop into the ADB sideload interface. Btw, try holding your home button, power button and volume up (or down) and report results.
If I was you, I would wait till the battery drains and shuts off and then let it be off for the rest of the night or something and then try again.
Click to expand...
Click to collapse
Alright, I'll give it until it passes out from battery loss and then get back on when things change. Thanks for the reply!
Hi everyone. I have an honor 6x emui 5, android 7 Nougat, and I unlocked the bootloader but I have a problem (I followed this guide) after running the command C:\ adb> adb reboot recovery, it says:
"Your device has been unlocked and can not be trusted.
To learn more, visit:
...
your device is booting now "
but it stays stuck on this screen and does not let me access the twrp.
Do you have a solution?
I looked around for something but there is nothing concrete and clear. Thanks a lot.
Luigi (i'm not Mario's brother)
Hi Luigi (ouch, thought it was Mario's bro :silly: ), once you flash TWRP through fastboot, you boot directly to it in way to don't let Huawei Recovery overwrite it immediately after?
To do this, as you finish to flash the image you'll need to boot to TWRP using hardware keys (at least that's what i did to make it works). When you're still in fastboot mode and TWRP is flashed, keep pressed power button and wait until your phone's display becomes black.
Be ready to hold down power button and Vol+ together as soon as you feel the phone vibrating while restarting (pay many attention to this step because it's the trickiest part - power button should be released while phone it's on black screen, but you'll for have to re-hold down power button again shortly after! Basically just hold the two keys and release them immediately as you see the Honor logo) and if everything went well, you'll finally be in TWRP.
Lemme know if you'll be able to win the game or if you need a Power-Up mushroom.
RedSkull23 said:
Hi Luigi (ouch, thought it was Mario's bro :silly: ), once you flash TWRP through fastboot, you boot directly to it in way to don't let Huawei Recovery overwrite it immediately after?
To do this, as you finish to flash the image you'll need to boot to TWRP using hardware keys (at least that's what i did to make it works). When you're still in fastboot mode and TWRP is flashed, keep pressed power button and wait until your phone's display becomes black.
Be ready to hold down power button and Vol+ together as soon as you feel the phone vibrating while restarting (pay many attention to this step because it's the trickiest part - power button should be released while phone it's on black screen, but you'll for have to re-hold down power button again shortly after! Basically just hold the two keys and release them immediately as you see the Honor logo) and if everything went well, you'll finally be in TWRP.
Lemme know if you'll be able to win the game or if you need a Power-Up mushroom.
Click to expand...
Click to collapse
but then this operation I have to execute it before or even after visualizing the screen that I have told you before?
The point is that the twrp does not flash ...:crying:
I tried several times to execute the sequence, and now it is stuck on the screen of the 3 options, ie it does not start anymore
he did not want to. How do I do now? I've tried any combination of buttons but it remains locked :crying:
Nvust said:
but then this operation I have to execute it before or even after visualizing the screen that I have told you before?
Click to expand...
Click to collapse
Immediately after that you've flashed TWRP and you get "success" message, when you're still on fastboot mode. Just type "fastboot reboot" and prepare to hold the keys once phone vibrates.
Nvust said:
The point is that the twrp does not flash ...:crying:
Click to expand...
Click to collapse
Telling me what issues you're facing could help more than this. What you mean with TWRP does not flash?
Nvust said:
I tried several times to execute the sequence, and now it is stuck on the screen of the 3 options, ie it does not start anymore
he did not want to. How do I do now? I've tried any combination of buttons but it remains locked :crying:
Click to expand...
Click to collapse
That's weird. But until I'll know more about the steps you did, helping becomes harder. Tell me something because just flashing stuff to recovery partition could not mess system that much, unless that you've flashed a wrong TWRP or the correct TWRP but in a wrong partition.
RedSkull23 said:
Immediately after that you've flashed TWRP and you get "success" message, when you're still on fastboot mode. Just type "fastboot reboot" and prepare to hold the keys once phone vibrates.
Telling me what issues you're facing could help more than this. What you mean with TWRP does not flash?
That's weird. But until I'll know more about the steps you did, helping becomes harder. Tell me something because just flashing stuff to recovery partition could not mess system that much, unless that you've flashed a wrong TWRP or the correct TWRP but in a wrong partition.
Click to expand...
Click to collapse
look here
after it don't make nothing
Hello,
I've rooted my Pixel 3 as described here in the forum.
Everything went well and I was booting in TWRP without any problems; Bootloader is still unlocked. I didn't installed a custom ROM or anything else. After I've selcted "restore backup" my backup (which I've made before with TWRP) my phone is now messed up:
It's starting in Bootloader (Warning Screen for unlocked Bootloader) and than is switching on an white screen with Google logo for ca. 3-4 sec. and than it's jumping back into the Bootloader in an endless Loop.
Any idea what I can do to rescue my phone?
Thanks, Mags
MMoes said:
Hello,
I've rooted my Pixel 3 as described here in the forum.
Everything went well and I was booting in TWRP without any problems; Bootloader is still unlocked. I didn't installed a custom ROM or anything else. After I've selcted "restore backup" my backup (which I've made before with TWRP) my phone is now messed up:
It's starting in Bootloader (Warning Screen for unlocked Bootloader) and than is switching on an white screen with Google logo for ca. 3-4 sec. and than it's jumping back into the Bootloader in an endless Loop.
Any idea what I can do to rescue my phone?
Thanks, Mags
Click to expand...
Click to collapse
In bootloader mode can you get your computer to recognize the phone. If so, download the latest update from Google website and install using adb. This will wipe the phone but will get it restored. I've had to do this in my pixel 2 before. I don't have the pixel 3 yet as I just ordered it today.
MMoes said:
Hello,
I've rooted my Pixel 3 as described here in the forum.
Everything went well and I was booting in TWRP without any problems; Bootloader is still unlocked. I didn't installed a custom ROM or anything else. After I've selcted "restore backup" my backup (which I've made before with TWRP) my phone is now messed up:
It's starting in Bootloader (Warning Screen for unlocked Bootloader) and than is switching on an white screen with Google logo for ca. 3-4 sec. and than it's jumping back into the Bootloader in an endless Loop.
Any idea what I can do to rescue my phone?
Thanks, Mags
Click to expand...
Click to collapse
FilthyFord said:
In bootloader mode can you get your computer to recognize the phone. If so, download the latest update from Google website and install using adb. This will wipe the phone but will get it restored. I've had to do this in my pixel 2 before. I don't have the pixel 3 yet as I just ordered it today.
Click to expand...
Click to collapse
You can also edit the flash-all file to remove the -w and not completely wipe your phone. This way, your data will remain and it still resets the important factory stuff.
FilthyFord said:
In bootloader mode can you get your computer to recognize the phone. If so, download the latest update from Google website and install using adb. This will wipe the phone but will get it restored. I've had to do this in my pixel 2 before. I don't have the pixel 3 yet as I just ordered it today.
Click to expand...
Click to collapse
Thanks, I‘ve tried with adb devices & no device found. So obviously my computer doesn‘t recognize the Pixel
sliding_billy said:
You can also edit the flash-all file to remove the -w and not completely wipe your phone. This way, your data will remain and it still resets the important factory stuff.
Click to expand...
Click to collapse
Thanks. Loosing my data isn‘t the Problem. Actually I‘m even not able to connect to the phone and flash anything.
MMoes said:
Thanks. Loosing my data isn‘t the Problem. Actually I‘m even not able to connect to the phone and flash anything.
Click to expand...
Click to collapse
Have you hard powered the device down and then rebooted to BL with key combo to check connectivity?
sliding_billy said:
Have you hard powered the device down and then rebooted to BL with key combo to check connectivity?
Click to expand...
Click to collapse
No, could you please descripe the process what to do exactly. Would love to give it a try. Thank you
MMoes said:
No, could you please descripe the process what to do exactly. Would love to give it a try. Thank you
Click to expand...
Click to collapse
Hold down the power button until the phone completely shuts off. Hold power while holding the volume down button (start by holding the volume down and then immediately start holding the power button - it's is technically holding both at the same time but starting with volume down just a moment before keeps you from pressing power first). That should get you to fastboot.
MMoes said:
Thanks, I‘ve tried with adb devices & no device found. So obviously my computer doesn‘t recognize the Pixel
Click to expand...
Click to collapse
ADB doesn't work when booted to the bootloader. It only works when you're booted to the OS. To see if the computer recognizes the phone when in the bootloader, use fastboot devices instead of adb devices.
sliding_billy said:
Hold down the power button until the phone completely shuts off. Hold power while holding the volume down button (start by holding the volume down and then immediately start holding the power button - it's is technically holding both at the same time but starting with volume down just a moment before keeps you from pressing power first). That should get you to fastboot.
Click to expand...
Click to collapse
Holding the power button didn't had any effect, but holding volume - and holding power button at the same time was starting the bootloader and so I was now able to start TWRP Manager.
So if you could help me from here to fix the OS would be great, e.g. is there any chance to copy the original OS from Google or an custom ROM from my computer (e.g. I wotk on MAC and is there a way to copy via Terminal?) or does TWRP offers any way to reset/ reinstall?
robocuff said:
ADB doesn't work when booted to the bootloader. It only works when you're booted to the OS. To see if the computer recognizes the phone when in the bootloader, use fastboot devices instead of adb devices.
Click to expand...
Click to collapse
Yes, the computer recognizes the phone (via Terminal on my MAC)
MMoes said:
Holding the power button didn't had any effect, but holding volume - and holding power button at the same time was starting the bootloader and so I was now able to start TWRP Manager.
So if you could help me from here to fix the OS would be great, e.g. is there any chance to copy the original OS from Google or an custom ROM from my computer (e.g. I wotk on MAC and is there a way to copy via Terminal?) or does TWRP offers any way to reset/ reinstall?
Click to expand...
Click to collapse
Sorry, but I do not know the Mac commands, but if you are in Fastboot and the device shows/connects it is just a matter of running the flash-all and resetting. If you are not connecting in Fastboot but can get into TWRP, I would start with a reset in TWRP.
sliding_billy said:
Sorry, but I do not know the Mac commands, but if you are in Fastboot and the device shows/connects it is just a matter of running the flash-all and resetting. If you are not connecting in Fastboot but can get into TWRP, I would start with a reset in TWRP.
Click to expand...
Click to collapse
The commands on the MAC are almost the same and with your flash-all (flash.all.sh Mac Command) it worked very well with the factory image from google. Now I'm back in the race and my P3 is running again.
Thank you all guys!
MMoes said:
The commands on the MAC are almost the same and with your flash-all (flash.all.sh Mac Command) it worked very well with the factory image from google. Now I'm back in the race and my P3 is running again.
Thank you all guys!
Click to expand...
Click to collapse
Excellent news. On another note... if all you need from TWRP is to install Magisk to root, you do not need to permanently install TWRP. Just fastboot boot the [twrp].img file, install the Magisk .zip and keep stock recovery.
From messing around, it seems that trying to restore system from twrp is messed up. Data backup works fine. The only other way I got bootlooped was by messing with boot, vbmata, and vendor partitions. Out of those three, I think boot is the most likely to get messed up by normal users. I know this is sorted now, but in the future try to just reflash boot.img and see if it boots.
-The vbmeta and vendor thing is specific because I need to get the radio to work here.