Related
Well, I was using an app called screen dimmer, and did pressed the button to dim the screen when all of a sudden it froze. It was like this for a while so I restarted it, it is able to go in fastboot, but nothing else. When i start It it hangs on the boot loader screen and can stay like that all day. if I go into recovery the screen goes black and the display is only backlit. I was going to try to to use the adb to factory reset it, but I could not get it to recognize the nexus 5 as a device. I used a bunch of different drivers. I did root my phone, and have the exposed framework but this was done a long time ago and I had no problems since. no idea how to fix this any help?!?!? Sorry if this is the wrong place to put this I'm new to this site.
2point said:
Well, I was using an app called screen dimmer, and did pressed the button to dim the screen when all of a sudden it froze. It was like this for a while so I restarted it, it is able to go in fastboot, but nothing else. When i start It it hangs on the boot loader screen and can stay like that all day. if I go into recovery the screen goes black and the display is only backlit. I was going to try to to use the adb to factory reset it, but I could not get it to recognize the nexus 5 as a device. I used a bunch of different drivers. I did root my phone, and have the exposed framework but this was done a long time ago and I had no problems since. no idea how to fix this any help?!?!? Sorry if this is the wrong place to put this I'm new to this site.
Click to expand...
Click to collapse
You need to find a driver that works so it'll recognize the device. Once you do this, you need to flash boot.img to restore the recovery since not working. Then, redo the ROM or restore from backup if you can. Flashing a new recovery boot.img should fix the issue.
2point said:
Well, I was using an app called screen dimmer, and did pressed the button to dim the screen when all of a sudden it froze. It was like this for a while so I restarted it, it is able to go in fastboot, but nothing else. When i start It it hangs on the boot loader screen and can stay like that all day. if I go into recovery the screen goes black and the display is only backlit. I was going to try to to use the adb to factory reset it, but I could not get it to recognize the nexus 5 as a device. I used a bunch of different drivers. I did root my phone, and have the exposed framework but this was done a long time ago and I had no problems since. no idea how to fix this any help?!?!? Sorry if this is the wrong place to put this I'm new to this site.
Click to expand...
Click to collapse
Hi, In first place, You are in the right place to get help:good:
2. ADB won't work on fastboot nor in a damaged recovery.
3. fastboot works:victory: Try to flash recovery once again (fastboot flash recovery recoveryname.img)
4. if 3 works, wipe system, caches. Flash the Rom you want, don't use that app anymore.
GUGUITOMTG4 said:
Hi, In first place, You are in the right place to get help:good:
2. ADB won't work on fastboot nor in a damaged recovery.
3. fastboot works:victory: Try to flash recovery once again (fastboot flash recovery recoveryname.img)
4. if 3 works, wipe system, caches. Flash the Rom you want, don't use that app anymore.
Click to expand...
Click to collapse
Thanks! got to recognize any way to do this without loosing data?
2point said:
Thanks! got to recognize any way to do this without loosing data?
Click to expand...
Click to collapse
There is a chance to keep your data + storage contents. If you manage to flash and boot into recovery, in 'wipe' menu manually check-mark "cache,system"
don't mark internal "storate and data", nothing will happen to your media and apps data.
2point said:
Thanks! got to recognize any way to do this without loosing data?
Click to expand...
Click to collapse
May be able to dirty flash but most likely, since you had the screen dimmed too much, you'll have to wipe data in order to override/remove the problem. You can try this way but may just send you back through this whole process if problem reoccurs. I'd just wipe the data to be safe.
2point said:
Well, I was using an app called screen dimmer, and did pressed the button to dim the screen when all of a sudden it froze. It was like this for a while so I restarted it, it is able to go in fastboot, but nothing else. When i start It it hangs on the boot loader screen and can stay like that all day. if I go into recovery the screen goes black and the display is only backlit. I was going to try to to use the adb to factory reset it, but I could not get it to recognize the nexus 5 as a device. I used a bunch of different drivers. I did root my phone, and have the exposed framework but this was done a long time ago and I had no problems since. no idea how to fix this any help?!?!? Sorry if this is the wrong place to put this I'm new to this site.
Click to expand...
Click to collapse
Oy vey! You shouldn't have been tinkering as you clearly don't know what you're doing.
[TUTORIAL] How to flash a factory image | Return to stock | Unroot your Nexus 5
2point said:
Thanks! got to recognize any way to do this without loosing data?
Click to expand...
Click to collapse
No, and if you had done your homework you would know that. If the data is so important, back it up before modding.
GUGUITOMTG4 said:
There is a chance to keep your data + storage contents. If you manage to flash and boot into recovery, in 'wipe' menu manually check-mark "cache,system"
don't mark internal "storate and data", nothing will happen to your media and apps data.
Click to expand...
Click to collapse
When I do fastboot boot recovery.img I get the android bot with a red exclamation but nothing else I might just do flashall
2point said:
When I do fastboot boot recovery.img I get the android bot with a red exclamation but nothing else I might just do flashall
Click to expand...
Click to collapse
Reflash the recovery.img
2point said:
When I do fastboot boot recovery.img I get the android bot with a red exclamation but nothing else I might just do flashall
Click to expand...
Click to collapse
The general idea is that your recovery is broken.
So, you need to flash a new recovery by placing a recovery.img file into your fastboot folder in the computer(recommend twrp). Like you did the first time you fladhed a recovery.
Then, turn off the phone, press volume down+ power button and it will boot into bootloader. Make sure it is on fastboot mode. After that, on the computer open cmd on the fastboot folder and and type:
fastboot flash recovery nameofrecoveryfile.img,
press enter.
It should flash a new recovery image if done correctly. Then, poweroff the phone, boot again into bootloader, choose recovery and it will reboot into recovery. Then follow. The steps of my first post.
jd1639 said:
Reflash the recovery.img
Click to expand...
Click to collapse
GUGUITOMTG4 said:
The general idea is that your recovery is broken.
So, you need to flash a new recovery by placing a recovery.img file into your fastboot folder in the computer(recommend twrp). Like you did the first time you fladhed a recovery.
Then, turn off the phone, press volume down+ power button and it will boot into bootloader. Make sure it is on fastboot mode. After that, on the computer open cmd on the fastboot folder and and type:
fastboot flash recovery nameofrecoveryfile.img,
press enter.
It should flash a new recovery image if done correctly. Then, poweroff the phone, boot again into bootloader, choose recovery and it will reboot into recovery. Then follow. The steps of my first post.
Click to expand...
Click to collapse
Did that and get a
C:\Users\nkkou_000\programs\adt-bundle-windows-x86_64-20131030\sdk\platform-tool
s>fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img
sending 'recovery' (13272 KB)...
OKAY [ 0.620s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 44.593s
C:\Users\nkkou_000\programs\adt-bundle-windows-x86_64-20131030\sdk\platform-tool
s>
But I can do fastboot boot openrecovery-twrp-2.6.3.4-hammerhead.img and will will boot into the recovery just fine
And that twrp says that i have no os installed
2point said:
But I can do fastboot boot openrecovery-twrp-2.6.3.4-hammerhead.img and will will boot into the recovery just fine
And that twrp says that i have no os installed
Click to expand...
Click to collapse
You have a couple of options depending on how much data you can afford to lose on your phone. The least intrusive is to adb push a Rom on to your phone when you're in twrp Then flash that rom in twrp
The easier, but you'll lose all data on your phone is to flash the flash-all.bat file in fastboot
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
2point said:
But I can do fastboot boot openrecovery-twrp-2.6.3.4-hammerhead.img and will will boot into the recovery just fine
And that twrp says that i have no os installed
Click to expand...
Click to collapse
Then, it seems recovery now is good. If you have rom zip in the storage. Just wipe system and cache, flash the rom and see what happens
When in the twrp I can't get fastboot to recognize it as a device, or adb either
2point said:
When in the twrp I can't get fastboot to recognize it as a device, or adb either
Click to expand...
Click to collapse
Your adb drivers aren't setup correctly. They're different than the fastboot ones. Try Google tool adb fastboot drivers xda.
jd1639 said:
Your adb drivers aren't setup correctly. They're different than the fastboot ones. Try Google tool adb fastboot drivers xda.
Click to expand...
Click to collapse
When you are on twrp. You dont need to use fastboot nor adb. Just flash a rom if have one to flash
GUGUITOMTG4 said:
When you are on twrp. You dont need to use fastboot nor adb. Just flash a rom if have one to flash
Click to expand...
Click to collapse
How do i do that?
2point said:
How do i do that?
Click to expand...
Click to collapse
Have you flashed roms before? And do you have one on your internal sdcard? If so flash it in twrp
jd1639 said:
Have you flashed roms before? And do you have one on your internal sdcard? If so flash it in twrp
Click to expand...
Click to collapse
I have the factory image from google for my nexus 5
Hi, I have had this issue for a while now where my custom recovery looses the ability to mount data, this is the message I get,
E: could not mount /data to set up /data/media path. When the problem occurs which can be going into to recovery from any custom rom I just reboot the phone again which has always rebooted ok, but I am worried that it may not reboot ok some time in the future breaking my phone.
I have tried all 3 custom recovery's so I don't think it's a recovery problem, anyone have any ideas what the problem may be.
Usually a problem with /cache. Wipe it a few times or fastboot flash stock cache.img
Sent from my Nexus 5 using Tapatalk
rootSU said:
Usually a problem with /cache. Wipe it a few times or fastboot flash stock cache.img
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks, can I fastboot flash stock cache.img on any rom ?
maxal said:
Thanks, can I fastboot flash stock cache.img on any rom ?
Click to expand...
Click to collapse
Yeah, any ROM
Sent from my Nexus 5 using Tapatalk
rootSU said:
Yeah, any ROM
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ok I have just done fastboot flash stock cache.img and I get a failed (remote: partition table doesn't exist) any idea what is wrong now.
maxal said:
Ok I have just done fastboot flash stock cache.img and I get a failed (remote: partition table doesn't exist) any idea what is wrong now.
Click to expand...
Click to collapse
fastboot flash cache cache.img
Tapatalk-kal küldve az én Nexus 5-el
maxal said:
fastboot flash stock cache.img
Click to expand...
Click to collapse
This wasn't the command. This was me telling you what to do. As you're already rooted, I expected you would know the command. See @bitdomo posted.
Please read up about fastboot
Sent from my Nexus 5 using Tapatalk
rootSU said:
This wasn't the command. This was me telling you what to do. As you're already rooted, I expected you would know the command. See @bitdomo posted.
Please read up about fastboot
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks fastboot command worked that time. I normally use adb and fastboot commands but I have never had to use cache.img command before, Thanks again :good:
Update: I tried what rootSU said but it didn't resolve my problem so I tried one last thing which was to flash a factory image using the LG Flashtool and so far every thing seems fine. So should anyone else have the same problem that I had with their recovery give the LG Flashtool ago. Should my original fault reoccur I will post an update.
For what it's worth, I had the same issue as the OP. I didn't want to flash the .tot, because my computer was being weird(it said COM41 was in use, because I already used the LGFT for my G2, didn't want to risk it). Basically I just RMAed it, because all fixes were failing. Using e2fsck, flashing stock cache, etc. I could temporarily fix it by flashing a factory image, but when I flashed a new ROM, it would happen again. So if it keeps happening, just send it back. :good:
I would like to add to what Koopa777 said that flashing a factory image was just a tempory fix as I tried this several times, but so far so good the data issue has not re occured since I used the LG Flashtool.
maxal said:
I would like to add to what Koopa777 said that flashing a factory image was just a tempory fix as I tried this several times, but so far so good the data issue has not re occured since I used the LG Flashtool.
Click to expand...
Click to collapse
Cool, I'll keep that in mind in case the new one gets it. Could you try something for me though? PA 4.2 BETA 5 always set it off for me. It booted fine, but the recovery was always borked when I rebooted into recovery. If your's survives that, I think that it could definitely be the fix. :good:
Koopa777 said:
Cool, I'll keep that in mind in case the new one gets it. Could you try something for me though? PA 4.2 BETA 5 always set it off for me. It booted fine, but the recovery was always borked when I rebooted into recovery. If your's survives that, I think that it could definitely be the fix. :good:
Click to expand...
Click to collapse
No problem I will test PA 4.2 beta tomorrow for you.
I had the same problem on an installation of a kernel that didn't boot atop a CM rom. When it bootlooped, I went into recovery and found the infamous could not mount /data. I tried rootSU's recommendation about wiping cache several times and flashing a cache.img but it didn't work for me. I was about to do the whole factory stock image thing (and thus wipe my sdcard) when out of desperation to avoid that, I tried something that surprisingly succeeded. The following steps are for a newbie but presupposes a working knowledge of how to use adb and fastboot commands.
1. Download and copy a known stable ROM's zip file into your SDK's platform-tools, renaming it ROM.zip
2. Boot you phone into (TWRP 2.7.0.0) recovery
2. Choose ADB sideload in Advanced
3. From your computer's DOS prompt in the SDK platform-tools directory, type adb sideload ROM.zip
When it's done sideloading, it will flash
4. Choose reboot system
It will boot and get a series of FC's of android process and dialer
5. Hard reset into bootloader (hold down the power button until screen goes off (in like 7 secs) immediately hit vol-down) and choose recovery
Voila! Rebooted into recovery for me with data mounted as normal. No need to flash factory images!
Hope this helps and good luck!
I know that this thread is nearly a year old, but just wanted to report that my phone soft bricked when I flashed a kernel (without flashing the rom). TWRP (2.8.5) was unable to mount data, storage, /data/media. When I went into TWRP/Advanced/File Manager there was nothing in the sd card. After an ADB flash cache cache.img it was still the same. I decided to follow the @reeper000 post and it booted into the ROM i flashed (Slim Lollipop version) and it came up with only a couple errors. I was then able to go into TWRP and restore a nandroid backup and all is fine. I was sooooooo close to erasing data/restoring to a factory image!!!!!! THANKS, @reaper000!
Glad all well. I had 2 nasty surprises yesterday. First I flashed a nandroid
, only one I had. It kept going past 100 %on loading the data. Went to 300%! I'd one rom with Gapps I'd not tried so I thought saved.. Aghhhhhh Noo when it came on said playstore support missing. Had to tap like mad to get it off the screen in between putting my acc in. 2 hours later it linked and downloaded the missing file. Thank god. Then my baseband went! I was at my wits end. Decided I'd nothing to loose with a factory reset which fixed it. Good job as the new battery came today! Now I test backups and have two different ones
Nexus 5 stuck on 'formatting /data' screen after factory image flashing
Sorry for the long post. I just want to ensure I am providing all relevant history.
I have a Nexus 5 (Hammerhead) 32gb device, stock with no rooting. I mean, I had never done anything special on it ever.
1. Recently I started getting Google Play Store related problems, first 194 error and then couple of days back 495 (I think). After trying switching on/off, clearing cache and some other similar ways to fix this, I decided to do a factory reset :crying:
2. I backed up all my data, and followed the documented steps for factory reset. The phone got stuck on 'erasing'. After waiting for over 24 hours, I finally figured out that this 'erasing' is not going to complete, ever.
3. So I again did some research and figured that I should do a fastboot recovery. Tried that with no difference. Recovery again took me to 'erasing' screen.
4. Some more research and then I decided to flash a factory image using ADB. I was (and still am) a complete newbie, so first I figured out what was ADB and how to get to it. After completing the installation, I found out Nexus 5 factory images. There was no mention of which ones to chose, so I just picked up the latest one.
This is what I really followed:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
https://www.youtube.com/watch?v=DRp5jJO34PE
5. Having learnt my lessons, I read the flashing instructions many times and also watched some videos 3-4 times. Once I was confident that no more information was going to be had, and the phone was unlocked (fastboot oem unlock) I went ahead with the flashing. I did it step by step - bootloader, radio and they recovery image. The last one failed.
6. I did some more research and found a method which told me to unzip the last image and flash the component images one by one. I did. Success! However, the phone did not reboot by itself as the guide said it would. So I tried to boot it manually.
7. I did not get the dead android with red exclamation mark. Instead, I got an alive android with gears whirring on its tummy and back. Pressing power + vol-up button told me that this was the 'formatting /data' screen. I am unable to get past this screen. I am supposed to get to a screen where I can wipe data and cache etc. But I cannot get to it.
8. I have tried to wait it out (16 hours) and tried flashing the images again. Ultimately, I end up here.
9. I am unable to find any answers on what to do if stuck on this screen. So this is the end? Is my phone bricked? Is there anything else I can try? Will trying TWRP way help or is that just another way to same failure?
I would appreciate if there is anybody out there who can help me get my phone working again, or point me to a thread which helps me do it. Thanks!
Just wait it took me 5 hours of waiting
Try flashing Android 4.4.4 and see if that will boot. If that does not work try installing a custom recovery like TWRP, and do the wipes from there.
dicecuber said:
Just wait it took me 5 hours of waiting
Click to expand...
Click to collapse
I doubt it. 12 more hours have passed with no change.
eross said:
Try flashing Android 4.4.4 and see if that will boot. If that does not work try installing a custom recovery like TWRP, and do the wipes from there.
Click to expand...
Click to collapse
Thanks. I was thinking of trying TWRP anyway. I will try this today.
How does one select which image to flash? Is it always the latest one? In this case, how do I know which one is Android 4.4.4, and why are you recommending this specific one? I had purchased this phone in 2013 Feb (I think). So is there any specific image to be selected or the latest one is always to be picked?
Tom2403 said:
Thanks. I was thinking of trying TWRP anyway. I will try this today.
How does one select which image to flash? Is it always the latest one? In this case, how do I know which one is Android 4.4.4, and why are you recommending this specific one? I had purchased this phone in 2013 Feb (I think). So is there any specific image to be selected or the latest one is always to be picked?
Click to expand...
Click to collapse
UPDATE: Flashing 4.4.4. did not work. I again got the 'formatting /data' screen again instead of the phone booting up. However, the formatting screen with the android with diamond circling in the tummy also has a blue line below, possibly a progress bar. It is not growing though, just there... sizzling. Pressing power+vol-up buttons shows me that this is 'formatting /data' screen.
Will try custom recovery from TWRP now.
Tom2403 said:
UPDATE: Flashing 4.4.4. did not work. I again got the 'formatting /data' screen again instead of the phone booting up. However, the formatting screen with the android with diamond circling in the tummy also has a blue line below, possibly a progress bar. It is not growing though, just there... sizzling. Pressing power+vol-up buttons shows me that this is 'formatting /data' screen.
Will try custom recovery from TWRP now.
Click to expand...
Click to collapse
Reboot your phone into bootloader and download latest hammerhead 5.1.1 from Google. Extract everything and then extract the images. First use these commands
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Then fastboot flash everything including bootloader.
Use this as a guide http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Then after finished reboot phone and leave it alone it will boot right up in 5-10 mins no need to go to recovery. In future don't format partitions.
try this: fastboot format cache
matt1515 said:
Reboot your phone into bootloader and download latest hammerhead 5.1.1 from Google. Extract everything and then extract the images. First use these commands
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Then fastboot flash everything including bootloader.
Use this as a guide http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Then after finished reboot phone and leave it alone it will boot right up in 5-10 mins no need to go to recovery. In future don't format partitions.
Click to expand...
Click to collapse
Sorry for the late update. I was traveling over the weekend.
Thank you so much! Your post solved my issue. I wish I had this advice earlier!
First time it did not work, with reboot leading to a blank screen. Next time I following the guide completely, following the order in which different images were flashed. The phone went into boot animation for 5.1.1 and finally booted up, with all 32gb storage available.
Thanks again!
Tom2403 said:
UPDATE: Flashing 4.4.4. did not work. I again got the 'formatting /data' screen again instead of the phone booting up. However, the formatting screen with the android with diamond circling in the tummy also has a blue line below, possibly a progress bar. It is not growing though, just there... sizzling. Pressing power+vol-up buttons shows me that this is 'formatting /data' screen.
Will try custom recovery from TWRP now.
Click to expand...
Click to collapse
Tom2403 said:
Sorry for the late update. I was traveling over the weekend.
Thank you so much! Your post solved my issue. I wish I had this advice earlier!
First time it did not work, with reboot leading to a blank screen. Next time I following the guide completely, following the order in which different images were flashed. The phone went into boot animation for 5.1.1 and finally booted up, with all 32gb storage available.
Thanks again!
Click to expand...
Click to collapse
Glad to hear you got it up and running! No problem at all feels great to bring something f'd back to life.
Tom2403 said:
Sorry for the late update. I was traveling over the weekend.
Thank you so much! Your post solved my issue. I wish I had this advice earlier!
First time it did not work, with reboot leading to a blank screen. Next time I following the guide completely, following the order in which different images were flashed. The phone went into boot animation for 5.1.1 and finally booted up, with all 32gb storage available.
Thanks again!
Click to expand...
Click to collapse
I have same problem. I did everything that was written above but still my phone shows android with rotating cube on its tummy. Any ideas? Thanks in advance
dmuml10 said:
I have same problem. I did everything that was written above but still my phone shows android with rotating cube on its tummy. Any ideas? Thanks in advance
Click to expand...
Click to collapse
Go into bootloader and format the cache: fastboot format cache
inimaitimepass said:
Go into bootloader and format the cache: fastboot format cache
Click to expand...
Click to collapse
I did that but nothing changed. Still shows android with rotating gears.
Does anyone know what does that animation mean ?
dmuml10 said:
I did that but nothing changed. Still shows android with rotating gears.
Does anyone know what does that animation mean ?
Click to expand...
Click to collapse
How long did you leave at that? Sometimes it may take long time depending upon the storage size of your phone. Usually between 20 to 40 mins.
inimaitimepass said:
How long did you leave at that? Sometimes it may take long time depending upon the storage size of your phone. Usually between 20 to 40 mins.
Click to expand...
Click to collapse
I left it more than an hour.
Is it normal that my phone shows this Android animation after I flushed new factory image? Why is it trying to still "Format /data..." after new image flush?
Is there any other way to flush android factory image from scratch? I already used nexus root toolkit and fastboot
dmuml10 said:
I left it more than an hour.
Is it normal that my phone shows this Android animation after I flushed new factory image? Why is it trying to still "Format /data..." after new image flush?
Is there any other way to flush android factory image from scratch? I already used nexus root toolkit and fastboot
Click to expand...
Click to collapse
I'm really sorry that you are stuck in this mess. It is normal but more than 1 hour is way too much. I'm not sure about the causes, but you can try two more things and see how it goes. One is to use flash-all.bat script. If that didn't work then you can flash a custom ROM like Chroma and then try flashing the stock ROM.
inimaitimepass said:
I'm really sorry that you are stuck in this mess. It is normal but more than 1 hour is way too much. I'm not sure about the causes, but you can try two more things and see how it goes. One is to use flash-all.bat script. If that didn't work then you can flash a custom ROM like Chroma and then try flashing the stock ROM.
Click to expand...
Click to collapse
Thanks for help.
I flashed philz_touch recovery. From there I did factory reset and after that I executed this commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
fastboot flash radio "name of radio"
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot reboot
Now my phone works.:victory:
dmuml10 said:
Now my phone works.:victory:
Click to expand...
Click to collapse
Good to hear. Weren't you using a custom recovery before philz'?
inimaitimepass said:
Good to hear. Weren't you using a custom recovery before philz'?
Click to expand...
Click to collapse
No. I only used stock recovery before philz.
Not too long ago (Back in the fall) my Nexus stopped working properly.
I had it running Dirty Unicorn (9.6 I do believe), i was laying on the couch with my baby sister and i pulled my phone out, noticed it was turning off, so I figured I must have held the PWR button back accident or my sister did when she was jumping on me. I proceed to turn it back on, it's working fine. 3 mintues later, it reboots then powers off. I try to turn it on, it will load to boot animation then slow down and stop during boot animation after a few secs then turn off. I tried again, same. It got warm some, so I left it alone for a little bit since it did turn on and off a couple times, so that can explain the heat it had.
I came back to it, it turned on for a sec(Google Logo) then shut off. Wouldn't turn on again, I charged some, tried to turn on, same.
So, now, I can sometimes get it into TWRP, sometimes i have to try a few times to do so (sometimes it wont boot, so i unplug the battery, plug back in and boot into twrp)
Booting into OS just restarts it. TWRP will stay booted into, but sometimes will suddenly power off the phone. I've been able to finally get my files off(by using a flashdrive, had to sped 4 hours grabbing a few at a time before each power off)
I started to get it to stay in twrp longer, but if i touch certain parts, like system, data sometimes, and other folders, it will power off. I've tried to reinstall DU, but got some error during write before it powered off.
Is there anything I can do? I'm stuck using a Droid Turbo since my Nexus 6 needs the screen replaced, and its previous owner stripped 11/22 of the screws, so i need to get a small enough screw extractor (reverse thread bit) to be able to switch to the new screen I have laying on my desk, taunting me.
I'd love to get back to my Nexus and use my Turbo just for Vainglory like I used to.
I do have it BL unlocked & TWRP installed along with Root(kinda obvious)
I also have access to a desktop to run command to push files and such if needed to get a fix
Can u get into bootloader? Have u tried flashing stock?
Sent from my XT1526 using Tapatalk
soupysoup said:
Can u get into bootloader? Have u tried flashing stock?
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
I can get into bootloader, I've tried erasing system then install dirty unicorn and gapps, but it just gives an error for a second then powers off or just powers off when it attempted to install
xBØYxTØYx said:
I can get into bootloader, I've tried erasing system then install dirty unicorn and gapps, but it just gives an error for a second then powers off or just powers off when it attempted to install
Click to expand...
Click to collapse
OK try this from a terminal;
fastboot format system
fastboot reboot bootloader
fastboot format userdata
fastboot reboot bootloader
fastboot format cache
fastboot reboot bootloader
Download a factory image from google, extract the system, boot, and userdata imgs and flash them with fastboot like this
fastboot flash boot boot.IMG
fastboot reboot bootloader
fastboot flash system system.IMG
fastboot reboot bootloader
fastboot flash userdata
fastboot reboot system
See if that works and let me kno
Sent from my XT1526 using Tapatalk
soupysoup said:
OK try this from a terminal;
fastboot format system
fastboot reboot bootloader
fastboot format userdata
fastboot reboot bootloader
fastboot format cache
fastboot reboot bootloader
Download a factory image from google, extract the system, boot, and userdata imgs and flash them with fastboot like this
fastboot flash boot boot.IMG
fastboot reboot bootloader
fastboot flash system system.IMG
fastboot reboot bootloader
fastboot flash userdata
fastboot reboot system
See if that works and let me kno
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
I will once I get the chance, I got it to boot twice, but turned off each time after a little. Haven't been able to get it to boot for a couple hours now, so I'm gonna order a battery and swap them then see if I can get it to boot long enough to get rid of whatever the problem. While I wait on the battery, I'm gonna try to mess with my Note 2 that seems to not accept custom roms and just loops the boot animation when I tried two custom roms so far. Lol
Off topic but which note 2 do you have?
Possible power button issue with nexus 5?
Sounds like a power button issue. Many have had it. Search the forums for discussion about it.
Hello everyone,
I have accidentally messed up a TF700 device that my grandma received from a friend. Now I am stuck in a loop, when the device boots up directly into recovery. In recovery, I can connect with adb and reboot to bootloader with fastboot mode, where I see the three icons and I can connect with fastboot, I can even boot the stock ROM, which works fine now, because /data has been wiped.
I have been looking for recovery blob on Asus website, but it looks like Asus has totally cut off the device support, I can not find anything.
Because I have been doing lots of nasty things to the tablet, by following a guide for flashing the TF201 (long story including wrong model name on the device sticker ) the easiest solution is probably to flash the original recovery, bootloader and ROM. Does anyone has by accident the recovery blob for Bootloader 1.00e ww_epad-10.6.1.14.10-20130801 a03 ?
Or is there any other solution for the loop? The problem is that in the recovery, I can not do almost anything, no partition can be mounted, I have probably flashed recovery for TF201.
Thank you.
Yes, best would be if you reflash the Asus firmware, then start from scratch.
Geab the zip here https://www.androidfilehost.com/?fid=817550096634791660
Extract it until you see the system blob (called simply "blob"), move it to your fastboot directory and flash it in fastboot:
fastboot flash system blob
Reboot
That returns you to a stock system.
Then flash the latest TWRP, format /data, then flash your Katkiss rom of choice
Good luck
Sent from my Pixel 2 using Tapatalk
This is awesome, thank you for such quick reply. Just one more question, is it OK to flash US recovery if there is WW version bootloader? Just to be sure not to scew it even more
Yes, flash away. The bootloader is the same for WW and US, just some wifi modules are different, I think.
That firmware is US anyway and it includes the bootloader, so you'll have a US BL afterwards
Sent from my Pixel 2 using Tapatalk
OK, sounds good then
I have tried downloading the archive now several times and no matter what program I use for unpacking, I always get error. May I ask you please to verify that the file is alright?
hornmich19 said:
OK, sounds good then
I have tried downloading the archive now several times and no matter what program I use for unpacking, I always get error. May I ask you please to verify that the file is alright?
Click to expand...
Click to collapse
Works fine for me. Downloaded it and it opened without problem. Try this link, uploaded the same file here: https://www.dropbox.com/s/tz1lcspqayhs7ug/US_epad-user-10.6.1.14.10.zip?dl=0
No I just can not extract it
7-zip, winrar, gzip tried and I always get CRC error. I can however open it to see what files are inside, but not extract the blob to flash it. So maybe there was a little misunderstanding.
So Good news (partially), I have managed to find on the Internet similar package with WW. Extracted the blob and flashed to system partition. But nothing has changed, it is still booting right to recovery (FlatLine CWM)
Strange thing is, in recovery, I can not mount any partition.
Another strange thing is that in the fastboot mode, there is no blue progress bar as it used to be before I damaged it. Also it does not respond to any reboot commands. I have to do hard reset.
Any idea to try out, please?
Mhhh, maybe you have to go the super clean route.
Run these commands one after the other, letting every single one finish. Some are very fast, some take a bit longer
fastboot erase misc
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot flash system blob
fastboot reboot
If it hangs at any of the commands (30 min or more does not return to prompt) just reboot with the buttons and continue with the next command.
Good luck
Awesome, I have some progress here, thanks to you. After formating the other partitions, the fastboot screen finally started to react and the blue progressbar appeared and the blob has been flashed.
After that, I have rebooted the tablet and it was stuck on the ASUS splash screen. When I rebooted to fastboot again, and tried recovery, I got Dead Android image instead. So there was no recovery image on the partition. When I tried to select cold boot to Android, I gets stuck again. So I have at least flashed TWRP recovery back again and I can boot to that recovery.
Also it looks like, despite of what was the archive name, I have now US bootloader and not WW anymore
So how to ged rid of the ASUS splash screen now? I suspect there is no kernel and RAMdisk on the boot partition now, since I have formated it, right?
I have tried flashing the JB kernel linked in the thread here https://forum.xda-developers.com/showthread.php?t=1919961 but without any result. However I am not 100% sure about the android version.
Or maybe this is a good time to flash completely different ROM?
Ok, step-by-step...
Strange though that it did not boot after flashing the blob... hope you do not have something else going on.
The Asus blob contains everything: Every partition is reflashed with stock software so everything should be in place. The dead Android is the stock recovery showing that it cannot find anything to flash. That is perfectly normal and healthy.
Yes, do not try to piece the system together, flash a full rom now (after formatting /data in TWRP).
https://forum.xda-developers.com/tr.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
I would recommend one of the KatKiss roms, the latest is here:
https://forum.xda-developers.com/transformer-tf700/development/rom-t3457417
Hello and sorry for not replying long. The baby at home was sick so I didn't have time to play with the tablet.
I have flashed the ROM you linked and the tablet finally is booting and working :victory: Or so far it looks like that
Thank you so much for your asistance here, I learned a lot on this journey.
For whatever it is worth, I just had a sudden occurrence of a similar problem. Im still using this tablet on an almost daily basis and one day it started a boot loop. When I tried the RCK it would show TWRP and then bootloop again. Followed the 'simple clean' steps and reflashed twrp and clean version of KatKiss and now good to go! Thanks @berndblb for the refresher course in fastboot commands.....