Hi,
I've never changed anything on my transformer as far as custom roms, never gained root, never even previously booted into the stock recovery. But after one night i woke up to my tablet being burning hot while it was charging. Further investigation showed that it was just rebooting over and over.
I turned it off. left it off to cool down, turned it on.
Bootloop.
I then downloaded the asus firmware put it on an SD card and followed the steps for installing it through asus recovery.
Bootloop.
I can't seem to find a guide on how to actually get nvflash going which is how i'd assume i should fix this.
By the way, I killed my warranty 6 months ago when my girlfriend stood on my tablet (it was on the bed and she walked on the bed in shoes/heels) and cracked the screen. It's been running fine and when it's on it's not noticible. But obviously without the warranty i'm kind of ****ed for an issue that probably Asus did cause.
This actually happened a few weeks ago but my last effort to fix it went south and i haven't thought about it for a while but now i was thinking of taking another crack at it again..
Short question (TL;DR):
Can someone link me a good guide to get nvflash to put either a better recovery or a new non-corrupt rom on my tablet?
Update1: Okay so people here confirm that I have fastboot enabled. But i don't understand how to use it. I've installed the fastboot driver. I've below posted what outputs when i try to push a CWM recovery to it (it looks fine but doesn't seem to work?).
If anyone has some links to how to use any tools via fastboot or APX to recover from here that would be good. Even if you just want me to dump information just tell me how and i'll run anything.
Update2: This time i found out that the fastboot icon is visible to anyone with JB. But fastboot isn't unlocked unless you run the asus apk. So I do not actually have fastboot enabled. Which explains the strange behaviour below.
Because even after trying to install asus official firmwares from SD card and failing, the only alternative remaining is to send it back to asus.
well you need to get it to boot in order to unlock.
perhaps follow the downgrade instructions in general?
lafester said:
well you need to get it to boot in order to unlock.
perhaps follow the downgrade instructions in general?
Click to expand...
Click to collapse
That resulted in a dead android with a red exclaimation mark from his chest cavity.
No dice.
Any other ideas?
Edit: There's a newer version than the one which is on my device, but updating causes it also to die Stupid triangle of death.
I've got 4 options in the pre-boot stuff; which is RCK Android USB and Wipe Data. None of these seem helpful, i was hoping there might be a way to push across using adb but i guess that requires root beforehand.
skythra said:
I've got 4 options in the pre-boot stuff; which is RCK Android USB and Wipe Data. None of these seem helpful, i was hoping there might be a way to push across using adb but i guess that requires root beforehand.
Click to expand...
Click to collapse
If the USB option is available, that should mean your tablet is unlocked and you can use fastboot from your PC to flash a custom recovery.
_that said:
If the USB option is available, that should mean your tablet is unlocked and you can use fastboot from your PC to flash a custom recovery.
Click to expand...
Click to collapse
Okay, that's odd, well so this is a good thing for me then. I can just follow one of the guides here for pushing a firmware onto it? Can you recommend one?
My understanding is i need to get ADB to work by installing the google tools and then install the ADB driver and something something.. I'm going to go read up now about that and pray to my favourite diety of the minute. I assume there should be one for electronics..
Okay so,
using fastboot, installing the drivers and etc. I tried to flash a custom recovery, but so far it doesn't look like it worked; here's the output:
C:\Users\X\Desktop\Android Tools\platform-tools>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.552s
C:\Users\X\Desktop\Android Tools\platform-tools>fastboot -i 0x0B05 flash rec
overy recovery-jb-touch.img
sending 'recovery' (6866 KB)...
OKAY [ 0.867s]
writing 'recovery'...
OKAY [ 0.069s]
finished. total time: 0.944s
C:\Users\X\Desktop\Android Tools\platform-tools>fastboot -i 0x0B05 reboot
rebooting...
It doesn't reboot my tablet at all. It doesn't load the recovery from any form of way i can tell. I'm at a loss again. I still can't find a guide to use fastboot to send any kind of stock firmware or custom firmware to the tablet reliably either. So i'd like any tips/links etc please
Okay so i'm still struggling to do this alone with tidbits strewn across the internet. Every time i think i find new information I find that I can't follow the directions because something else prevents me. Having 'fastboot' hasn't really helped me at all yet.
So i found http://android.stackexchange.com/questions/28077/bricked-my-asus-tf300t-manual-jb-update and i was using that but i'm still finding odd behaviour with fastboot.
Let me explain in copy-paste form.
C:\Users\Skythra\Desktop\Android\platform-tools>fastboot devices
???????????? fastboot
C:\Users\Skythra\Desktop\Android\platform-tools>fastboot devices
015d262e990c0c08 fastboot
C:\Users\Skythra\Desktop\Android\platform-tools>fastboot flash system 01\blob
sending 'system' (800199 KB)...
OKAY [ 97.595s]
writing 'system'...
OKAY [ 0.067s]
finished. total time: 97.665s
C:\Users\Skythra\Desktop\Android\platform-tools>fastboot devices
???????????? fastboot
After using fastboot and issuing a second command it then stops for a countable 5 seconds before it says ??????????. If i say fastboot -reboot it says success but it doesn't reboot the device. So here's my understanding of what happens:
I load the staging area with the BLOB file
The copy to the staging area completes
fastboot goes crazy and doesn't listen
Next reboot doesn't do the android installation (which people have mentioned but i've never myself seen)
I go back to bootloop
If i reboot the device go back to fastboot, i can send it the command "Fastboot reboot" and it works. But any command after "Flash" nothing else works.
So far there has been a total of zero success I'm about to try the older firmware instead of the same as what's on there.
Okay so,
Apparently because fastboot is there doesn't mean I have real fastboot access. Probably this is my guess:
With JB you get access to Read from fastboot but it doesn't truthfully write. The simplified USB interface might take your data as it's sent but it's probably not storing it.
So the truth of the matter is i'm NOT unlocked. It's exactly as I thought.
I can't recover from trying to move any version of asus official firmware onto the ext_sd card and RCKing (even when the android man appears to work correctly, it still clearly restarts into a bootloop).
So this has to be sent back. Which likely won't be covered by warranty due to the fact that many months ago my now-ex-girlfriend broke the screen.
Fantastic
I can only assume this: Either the OTA update failed and my TF700 then melted itself from the charging+bootloop heat. Else when my ex stood on it, it broke something that would only be used in recovery.
Either way I'm down my 700AUD item and sad for the experience
Ahwell. I suppose i could change the title of this to "Solved" and update the OP as "Unfixable".
Seeing what ASUS was telling people fixing their Prime would cost for user incurred damage, you might be better off just to buy a new tablet. Fixing it would only save a hundred bucks or so and they might void your warranty.
hello xda. i need your help. im desperate. i dont know what else to do with my moto g here's what happened:
first of all, i dropped my moto g into the water.
right after i got it out, it startet bootlooping. then it turned off by itself after almost an hour had passed.
i put it in a bag full of rice for the rest of the night and almost the whole following day. then i plugged it into the wall charger, and it wouldnt charge at all. the only sign of life was the blinking led.
so i took it to Movistar-Peru for repair, and told me the obvious: water damage was not covered in the warranty, then my phone was returned to me.
so i decided to tear it down by myself.
everything was looking fine. the water indicators were red, but everything was clean except for the battery socket: there was mineral condensation around it. i wiped it out, cleaned it away and then the phone would actually charge the battery icon displayed normally.
so i let it charge for 3 hours and after it was completely charged i turned it on. just to run into a black screen after the bootnimation.
good news is it actually can boot into fastboot mode and can access recovery menu.
i did some research here, and seemed like my phone needed a full stock flash (that´s what i thought). i decided to unlock the bootloader, using motorola unique code. (i thought it may be needed for flashing, but it seems it is not necessary)
in recovery, my sdcard folders display normally, i can wipe data/factory reset it normally, BUT when i try to erase cache partition, the phone reboots.
so i started flashing my device through fastboot. i should mention that before i dropped it into the water, i had installed 4.4.2 ota update. but whenever i tried to flash a 4.4.2 rom, i got hab check failed for sysyem, for recovery and sometimes for boot.
now, i've tried several official motorola signed jelly bean roms (nextel br, movistar sp, claro ar, etc etc) including original Movistar Pe jb rom (which ive already flashed uncountable times) with no errors on flashing, but neither of them got me passed the black screen after bootanimation. (the phone is not off, cause the backlight remains on). the only way of getting out of it is rebooting into fastboot mode again (volume- and power).
i've also tried relocking the bootloader, and the process gives me no errors (the word "locked" displays by the end, though the phone then reboots into the "warning bl unlcked" screen) , but regardless of that and the relocking process turning out okay, status code 3 is displayed in menu, meaning the bl wasnt really relocked..?)
in short:
-dropped into water, started bootloop, then it turned itself off.
-next day it would display black screen after bootnimation, no matter what i did.
-if i choose wipe cache partition, the phone reboots.
-i've flashed it "sucsessfully" several times, still runs into a black screen after bootnimation.
-i've unlocked the boootloader
-if i try to reclock: process turns out okay("locked" word by the end), but status code remains being 3.
-i dont care about backups, i had nothing important in my phone (gdrive ftw)
my concearns are:
-possible hardware unrepairable damage
-bootloader got corrupted
-mineral condensation is still there deep inside the components
-maybe gpu? emmc corrupted? semi brick? idk..
my questions are:
-what can i do from now?
-i've read that a new bootloader can be flashed into the phone. risk of bricking my phone?
-if the bootloader is the problem, flashing a new one would solve it?
-in general, what am i doing wrong in all of this? has my phone any chance of functioning normally, at all?
please help me , i miss my phone, i got it for christmas, it is my first smartphone and i woudl like to bring it back to life if possible. thank you for reading.
I can help!
My girlfriend dropped her Moto G in water too, and it also started showing a black screen after the boot animation. I just managed to fix it.
Even if you have done some of this stuff, do it again anyway.
1-Power phone off
2-Press and hold volume down key for 3 seconds, then press the power key, then release both
3-You will see the boot options menu
4-Press the volume down key to scroll to RECOVERY, then press volume up to select it
5-You will see the Motorola logo, then after 10-30 seconds (maybe longer), you will see a Android logo with an exclamation symbol
6-Press and hold the Volume Up key for 10 seconds, then tap the power button
7-You will see a new menu
8-Use the Volume down key to scroll to Wipe data/factory reset, and then press the power key to select it.
9-Then use the volume down key to select yes, and use the power button to confirm
10-Let the phone format, then press the power key to reboot.
Once the phone has switched back on, wait and see what happens. If the Motorola logo comes on and then stays on for ages WAIT! It takes ages, but the phone will come back to life normally and be working in a few minutes! If you see a black screen again:
Repeat steps 1-7
When you see the new menu again, this time select the cache wipe option (it's the last option on the list)
Let the phone wipe and then it should reboot
This time you will defo see the Motorola logo on the screen for ages. Just keep waiting and press nothing. Hopefully after a minute or 2 it will then take you to the welcome screen
Hope this helped. I couldnt find any advice so had to experiment haha
Thank you for replying to my problem
i have already done your steps uncountable times.
every time i try to wipe cache, the phone reboots. it does not wipe anything at all, it just instantly reboots. then bootanimation, then black screen again, but nothing happens. not even after 2 minutes, after 5 or 10. nothing. just black screen until battery drains completely from continously powering the backlight. do you think maybe the water hardware-bricked my phone? also, im ocassionally getting blue screens out of a sudden, then the phone powers itself off.
Ah, ok, sorry my suggestion didn't help. I had exactly the same problem, so surprised this didn't help you. After being dropped in water, all I got was a black screen after the initial start animation. I don't really know much about phones tbh, I just managed to fix mine through trial and error. My girlfriends phone was initially sent to a shop for repair, and although the guy couldn't fix it, he said there was no signs of water damage. Not really sure then why the phone stopped working, but the method I suggested did work for me. I don't think there was anything else I tried. It's worth mentioning maybe that it took 6 weeks before I could fix the phone. Maybe it took that long to fully dry out? Straight after the accident though the phone was put in a bowl of rice for days so it should have been dried pretty quick. Don't really know what else to suggest, sorry I couldn't be more help. Have faith though, I reckon it'll come back to life soon
thank you for posting a reply and thank you for your advice. i appreciatte the attention given. i will further try some other methods in hope of a solution.
Your bootloader is working fine, dont touch it.
Unlock the bootloader and try to install cwm or twrp recovery, mount and format /data , /cache , /system through the recovery (if you manage it get recovery working ofc).
After that download mfastboot and flash stock rom with it.
Btw if you ever put anything into bag of rise, DON'T CLOSE the bag, you`ll probably do more damage than good this way.It should be done in open-air conditions.
liveroy said:
Your bootloader is working fine, dont touch it.
Unlock the bootloader and try to install cwm or twrp recovery, mount and format /data , /cache , /system through the recovery (if you manage it get recovery working ofc).
After that download mfastboot and flash stock rom with it.
Btw if you ever put anything into bag of rise, DON'T CLOSE the bag, you`ll probably do more damage than good this way.It should be done in open-air conditions.
Click to expand...
Click to collapse
are you sure it has nothing to do with the bootloader? now that you mention this.. can a 4.4.2 bl load a 4.3 rom successfully? and moreover, if i flash another bl, it will overwrite my original one right? is there eny problem on that? i am asking because no matter what i do, regardless of the "locked!" message, the menu keeps showing code status 3.
what happens if i flash the recovery and cant mount or flash any rom? or if the black screen persist after that?
and i wish i had known the rice trick before, cause i kept the bag closed for almost a day :s
grahameaddicott said:
My girlfriend dropped her Moto G in water too, and it also started showing a black screen after the boot animation. I just managed to fix it.
Even if you have done some of this stuff, do it again anyway.
1-Power phone off
2-Press and hold volume down key for 3 seconds, then press the power key, then release both
3-You will see the boot options menu
4-Press the volume down key to scroll to RECOVERY, then press volume up to select it
5-You will see the Motorola logo, then after 10-30 seconds (maybe longer), you will see a Android logo with an exclamation symbol
6-Press and hold the Volume Up key for 10 seconds, then tap the power button
7-You will see a new menu
8-Use the Volume down key to scroll to Wipe data/factory reset, and then press the power key to select it.
9-Then use the volume down key to select yes, and use the power button to confirm
10-Let the phone format, then press the power key to reboot.
Once the phone has switched back on, wait and see what happens. If the Motorola logo comes on and then stays on for ages WAIT! It takes ages, but the phone will come back to life normally and be working in a few minutes! If you see a black screen again:
Repeat steps 1-7
When you see the new menu again, this time select the cache wipe option (it's the last option on the list)
Let the phone wipe and then it should reboot
This time you will defo see the Motorola logo on the screen for ages. Just keep waiting and press nothing. Hopefully after a minute or 2 it will then take you to the welcome screen
Hope this helped. I couldnt find any advice so had to experiment haha
Click to expand...
Click to collapse
It worked for me, Thanks
liveroy said:
Your bootloader is working fine, dont touch it.
Unlock the bootloader and try to install cwm or twrp recovery, mount and format /data , /cache , /system through the recovery (if you manage it get recovery working ofc).
After that download mfastboot and flash stock rom with it.
Click to expand...
Click to collapse
ok i did what you said, i tried to flash cwm and fastboot presented no problems, (output is "okay"), but un the phone screen there's a message "mismatched partition size (recovery)", and when i enter recovery, it boots normal STOCK recovery!! i donw know whats happening. i renamed the cwm image to cwm.img and typed in these commands:
fastboot erase recovery
fastboot flash recovery cwm.img
then i clicked recovery option in the bootloader menu... but it booted into stock recovery!! this is so confusing
Now
mfastboot flash partition gpt.bin
mfastboot flash fsg fsg.mbn
at first since it seems you got partitions a bit messed for some reason.
Then flash everything in order, skip those 2
Also if you are really suspcious about the bl is not working fine, just flash motoboot.img from the same version of android you need.
thank you i will proceed to try what you said. though i have a question: is it possible for the bootloader to be overwritten with a previous version?
and what does it mean when the phone outputs "hab check failed for boot/recovery/system (etc)" ? i sometimes get those errors when flashing other region (official) roms
liveroy said:
Now
mfastboot flash partition gpt.bin
mfastboot flash fsg fsg.mbn
at first since it seems you got partitions a bit messed for some reason.
Then flash everything in order, skip those 2
Also if you are really suspcious about the bl is not working fine, just flash motoboot.img from the same version of android you need.
Click to expand...
Click to collapse
i tried what you said and it is all the same. i choose "recovery" after flashing a custom recovery image, but it boots into stock recovery. any ideas on what might be going on?? is it possible for water damage to cause this behaviour ?
tenjou_89 said:
i tried what you said and it is all the same. i choose "recovery" after flashing a custom recovery image, but it boots into stock recovery. any ideas on what might be going on?? is it possible for water damage to cause this behaviour ?
Click to expand...
Click to collapse
Hmm, maybe leave the recovery aside for now and try to boot a 4.3 ROM (stock one).
Also you cannot downgrade to bootloader afaik, but the newer ones work fine with 4.3 ROMs.
I don't think that the eMMC got damaged, cos nothing will work then.I really can't say if your problems are coming from the water dip or it's just the Moto G being stubborn if you do even one thing the wrong way.
PS. How do you flash the recovery?
fastboot erase recovery
fastboot flash recovery recovery.bin
fastboot reboot bootloader
This way?
what about the ram? a guy on some other forum said that maybe the ram got damaged to a point where only a part of it is now writable, and it gets flooded just before the complete boot up of the system, wichi is why the phone would then crash and display a black screen. what do you think about that theory?
i am going to try with 4.3 roms now. oficial and custom and post the results.
liveroy said:
PS. How do you flash the recovery?
fastboot erase recovery
fastboot flash recovery recovery.bin
fastboot reboot bootloader
This way?
Click to expand...
Click to collapse
yes, exactly that way.
edit: except i have images instead of bins, so:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot bootloader
Typo of mine, should be .img
About that RAM theory, it really doesn't sound viable to me, but who knows.
If I have to guess, I would say it's probably some crucial component failing to initialize properly and the kernel halts the system.
hmmm do you know of a method of checking for the conditions of individual hardware componets through a pc? like probing or running a full check of everything, not just the emmc..?
These seem not to work.
But if you find the correct details, maybe there is something to test in the service menu.
I have the same problem without water damage. I guess its the 4.4 OTA bug.
Tried reflashing the firmware i already have but of no use.
Mine shows the Blue Motorola logo and then doesn't show the boot animation.
Please can anyone help me out :'(
Hi Folks,
The problem I am facing is, that, after i used the TWRP-formatting method, my TF700 won't get past the opening-screen of TWRP, instead, this screen continues to kind of blink in a 3 second rythm.
I installed the newest ZOMBI-POP, learned, that it didn't install the Google-Play-Services and the Gopple-Play-Store, reflashed it again and got massive lags (didn't check for the apps though) . I decided to wipe data and did this in twrp, using the command-line sbdag proposed, in the 'advanced' section. Somehow, I must have messed it up, because the 'blinkin' occured since then. I went into fastboot and tried to reinstall twrp 2.85, the result was the following:
C:\adb>fastboot devices
015d29955e53f60e fastboot
C:\adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (7276 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.010s
Since then, the device 'blinks' as described and i even can't switch it off. Is there anything I can do? Searching the forum didnt give any results (maybe because of my minor knowledge) . I appreciate any help or tip, Thanks in advance!!
Tom
edit: Seems, that the problem was a not-working/installed adb-driver, i reinstalled it and fastboot flash worked. So, after two nights of try and error, it solved itself, finally when I overcame to get help here But trying to get into twrp still remains in that blinking with no step egtting further. Booting the system works.
frozentoes said:
But trying to get into twrp still remains in that blinking with no step egtting further. Booting the system works.
Click to expand...
Click to collapse
This means that TWRP crashes after starting, then it's restarted by init. Run "adb pull /tmp/recovery.log" and paste it.
Hello _that,
thank you for your reply. Alay, I did a step back, reflashed twrp with adp (2.8.5, i know, its not the recommended choice 'cause of the formatting-issue, but I will step around it) and flashed my B4-restore back. Since now, it works quite well in the behaviour that it showed before, a bit slow and a bit laggy, but working. I did this, because the device went hot and had a massive battery-drain, altough I installed the patch. Pretty sure, I messed something up while following the recommendations and tuts here, no one to blame but me! I appreciate the help I always find here by reading through the posts and I really appreciate the effort by every helper here - and yours and sbdags for the massive fun you put back in a tablet, that has been abandoned by its creators!! One issue I found with installing RC1 was, that it did not install gplaystore and gplayservices, was that left out or does it fall under rtfm?
Thanks
Tom