Database Info

[Q] Bricked TF700 when trying to install TWRP

Current Status of my TF700:
-Boot looping with Asus "Inspiring Innovation - Persisten Perfection" logo. Approximately 5 seconds between reboots, with a vibrate every time it reboots.
-It says "Device is Unlocked" in the top left.
-Holding power for a long time (over 20s) will shut it off, and vibrate, but then it immediately vibrates again and resumes the bootloop.
-I cannot get it into the bootloader with Power + Vol Down. That combination does nothing.
-If I use the pinhole button, as long as I hold it, the screen remains blank. As soon as I release it again, the bootloop resumes immediately.
-It does not get to the second "shiny" Asus logo.
-It doesn't get far enough to recognize a new firmware file on the microSD card.
How I got to this point:
Stock ever since I bought it up until a few days ago. I decided it was time to root, unlock, install TWRP, and install CWM. I never got that far.
1. I unlocked first. I believe it was successful because it has said "Device is Unlocked" ever since.
2. I tried to root with the debugfs method. It reported it was successful, but despite several attempts, it was unsuccessful.
3. I tried using GooManager to install TWRP. It never worked.
4. I discovered that I wasn't running the latest Asus firmware. I then upgraded it. It ran successfully. (V10.6.1.14.10)
5. I tried rooting with Motochopper. It reported success. But it didn't work. I then discovered it wouldn't work with V10.6.1.14.10.
6. I then tried installing TWRP via fastboot. It reported success, but Power+VolDown didn't get me into TWRP. Nothing seemed to load TWRP. In case it's relevant, I was having trouble where Windows was saying there was a problem with the Bootloader Interface Driver, and after several reboots, I was able to get fastboot to reportedly load TWRP. It reported success, but I never saw TWRP.
7. I booted into Recovery, the latest version that said something to the effect of, "USB recovery loaded" or something, with 3 icons: RCK, Android, and Wipe Data. This is the only recovery I was ever able to see, by the way. I then selected "Wipe Data" hoping it would give me a new starting point.
Once it rebooted, it has been stuck in this bootloop. Have I royally screwed myself, or is there a way to recover?
Please ask any questions, I will answer them to the best of my ability. In the meantime, I will hope to run the power down on the tablet in the hopes it will make a difference.

blauciel said:
6. I then tried installing TWRP via fastboot. It reported success, but Power+VolDown didn't get me into TWRP.
....
7. I booted into Recovery, the latest version that said something to the effect of, "USB recovery loaded" or something, with 3 icons: RCK, Android, and Wipe Data. This is the only recovery I was ever able to see, by the way.
Click to expand...
Click to collapse
Power+VolDown activates the bootloader menu - this is the screen with the 3 icons, where you can use fastboot. Since you needed to go there to install TWRP via fastboot, you should have known that Power+VolDown doesn't get you into TWRP - you'd have to press VolUp in the bootloader menu, to activate RCK.
blauciel said:
I then selected "Wipe Data" hoping it would give me a new starting point.
Once it rebooted, it has been stuck in this bootloop. Have I royally screwed myself, or is there a way to recover?
Click to expand...
Click to collapse
Selecting "Wipe data" from the bootloader menu with a broken recovery is the best known way to brick a TF700. This can only be recovered via nvflash, which you can't use since you never got far enough to extract the required files from your tablet while it still worked. Your only option now is a new mainboard.

Well, crap. RCK never did anything except show a loading bar then reboot.
Thanks for the reply.
...from my phone...

Anyone know of a place that sells 64gb mainboards? Not finding anything thus far...
...from my phone...

in case anyone cares, I swapped the motherboard out with one from ebay, and it booted right up.

Stuck at "erasing" when doing a factory reset?

Anyone else had issues performing factory resets? My Nexus 5 seems incapable of completing it. So far I have tried doing a factory reset from the settings menu 4 times. Every single time it locks up on the erasing step. I don't mean it takes a little longer. I have let it sit for almost half an hour and the little android robot sits there taunting me.
Every time I have had to manually go into the bootloader and sideload a factory image, which works fine.
Any ideas why this problem is occurring? Faulty memory maybe?

Same issue here, phone is getting nice and warm but the little robot just sits there twiddling his antennae. Forced restart either normally or into recovery mode lands me right back on the erasing screen, looks like nothings going to happen unless I intervene another way. Any ideas?

Try pushing the system.img using fastboot. Might be best to start over and do a clean install.

Have you tried doing a factory reset in recovery instead?
Sent from my Nexus 5 using Tapatalk

Same problem
I have the same problem with the loop at the erasing screen. It will not go into recovery so that I can fix it. I tried flashing the Stock Rom again but no use. Please help me or at least give me some pointers what to try next.
jizkidjnr said:
Same issue here, phone is getting nice and warm but the little robot just sits there twiddling his antennae. Forced restart either normally or into recovery mode lands me right back on the erasing screen, looks like nothings going to happen unless I intervene another way. Any ideas?
Click to expand...
Click to collapse

martinancevski said:
I have the same problem with the loop at the erasing screen. It will not go into recovery so that I can fix it. I tried flashing the Stock Rom again but no use. Please help me or at least give me some pointers what to try next.
Click to expand...
Click to collapse
I have the same problem

I'm sure you wait a long time...but if not, mine probably took 10-15 minutes to finish...
Sent from my Nexus 5 using xda app-developers app

i have the same problem

What is your recovery? Version # also? How did you root? <--- this goes to the rest of you guys too because it seems like its happening to more than one person.
Follow this: Maybe flash the stock recovery found in here http://forum.xda-developers.com/showthread.php?t=2513701
fastboot flash recovery C:/image-hammerhead-krt16m/recovery.img
^^ the command
edit: on second thought start over.

lpforte said:
Anyone else had issues performing factory resets? My Nexus 5 seems incapable of completing it. So far I have tried doing a factory reset from the settings menu 4 times. Every single time it locks up on the erasing step. I don't mean it takes a little longer. I have let it sit for almost half an hour and the little android robot sits there taunting me.
Every time I have had to manually go into the bootloader and sideload a factory image, which works fine.
Any ideas why this problem is occurring? Faulty memory maybe?
Click to expand...
Click to collapse
hello
I have the same exact problem
I'm completely stock and I want to reset all so I do factory reset from menu setting, backup & reset
And since, my nexus stucked in "erasing...."
I have tried flashing factory image according to this guide, succeeded, but then still stucked in android logo with endless progress bar (but this time without "erasing....")
Need help how to restore it
All I want is to factory reset
How did you actually sideload factory image?
thanks

iori said:
hello
I have the same exact problem
I'm completely stock and I want to reset all so I do factory reset from menu setting, backup & reset
And since, my nexus stucked in "erasing...."
I have tried flashing factory image according to this guide, succeeded, but then still stucked in android logo with endless progress bar (but this time without "erasing....")
Need help how to restore it
All I want is to factory reset
How did you actually sideload factory image?
thanks
Click to expand...
Click to collapse
ADB sideload: place the rom you want to flash in the fastboot folder and in the phones recovery select adb sideload, then on the pc in cmd type: adb sideload namerom.zip and it will start flashing.

gee2012 said:
ADB sideload: place the rom you want to flash in the fastboot folder and in the phones recovery select adb sideload, then on the pc in cmd type: adb sideload namerom.zip and it will start flashing.
Click to expand...
Click to collapse
thanks
but i finally found out that the stock recovery was somehow corrupted after factory reset
then I unlocked the bootloader and flashed TWRP recovery, and voila! my device booted normally

Nexus 5 hung at reset
iori said:
hello
I have the same exact problem
I'm completely stock and I want to reset all so I do factory reset from menu setting, backup & reset
And since, my nexus stucked in "erasing...."
I have tried flashing factory image according to this guide, succeeded, but then still stucked in android logo with endless progress bar (but this time without "erasing....")
Need help how to restore it
All I want is to factory reset
How did you actually sideload factory image?
thanks
Click to expand...
Click to collapse
Exactly the same problem here. Nexus 5 running 4.4.2 kept powering off randomly roughly once a day. Attempted a factory reset and it got stuck at erasing. Having unlocked the bootloader and following the steps to unlock and reboot, I have a progress bar with the animated android icon, apparently stuck at the same stage, but without the "erasing" caption.
As far as I'm concerned, I can nothing with the phone at present short of taking it back, though they'll likely take issue with my attempts to rectify myself

mannschaftpag said:
Exactly the same problem here. Nexus 5 running 4.4.2 kept powering off randomly roughly once a day. Attempted a factory reset and it got stuck at erasing. Having unlocked the bootloader and following the steps to unlock and reboot, I have a progress bar with the animated android icon, apparently stuck at the same stage, but without the "erasing" caption.
As far as I'm concerned, I can nothing with the phone at present short of taking it back, though they'll likely take issue with my attempts to rectify myself
Click to expand...
Click to collapse
I'll add that I've also tried the Nexus Root Toolkit v1.8.0 to flash stock. Appears to go fine, recreating the file system and loading software, then as soon as it gets to the "erasing cache" step it just sits there for hours and makes no progress.

I know I probably shouldn't promote toolkits but you can always try this. Seems to have worked for a lot of people.
http://forum.xda-developers.com/showthread.php?t=2513937
Sent from The Deathstar

Same thing happened to me yesterday. My N5 is rooted, running stock rom and recovery. I had some corrupted app date showing in Titanium that I could not remove that were causing a Play store issue for me. I backed up my phone with TB and ran a factory reset in settings. The phone was stuck on the 'erasing' screen for maybe 20 minutes, so I put the phone in fastboot and from there back into recovery. This took me back to the 'erasing' screen to my dismay. I put the phone down and started searching for a solution online, but then I noticed after about 7 minutes the erase process had finally finished on its own and the phone rebooted normally again.
Based on what others are saying in this thread it appears the factory reset process via settings or stock recovery can hang sometimes. If you power off, start the phone in fastboot and select recovery again, I'm guessing the factory reset process restarts and hopefully it will then work properly the next time, like it did for me.

Well when I did a factory reset from settings, it took nearly 20-25 minutes to finish. The next time I did a reset, it completed within 10 minutes
I guess this problem occurs randomly.

Be patient
My guess is that you just need to be patient -- my device took nearly 45 minutes to reset. It seems to me that the time required is proportional to either the amount of data or the number of files you have on the device. My device had a mix of large files (such as musics and photos) and many many small files (sensor data log files), so it's hard for me to say which of those contributed more to the long reset time.

Based on what others are saying in this thread it appears the factory reset process via settings or stock recovery can hang sometimes. If you power off, start the phone in fastboot and select recovery again, I'm guessing the factory reset process restarts and hopefully it will then work properly the next time, like it did for me.
Click to expand...
Click to collapse
This worked for me too. On the initial 'Return to factory defaults' it got stuck for about 45 minutes. I then follow the advice above:
- Put the N5 in Fastboot by pressing: Vol. Up + Vol. Down + Power
- Select: Recovery and press on Power to proceed
- Phone reboots, still into the 'Androidman' but it seems that the 'Return to factory defaults' also restarts.
- Wait about 10 minutes and the Phone powers down automatically. Upon startup you enter the 'Initial configuration menu' so the factory reset has been completed.

Still stuck on Erasing screen, running out of options
Hello,
I am a newbie with zero developer knowledge and received my Nexus 5 in the mail yesterday. I liked the phone specs and that is the only reason I got it. I left it alone while it charged up and the first thing I did once it was finished was perform a Factory Reset (it was a "like new" phone so I just wanted to be safe) and have been stuck on the Erasing screen ever since. Pressing Vol- and Power button does take me to the bootloader screen, however, any option I choose by pushing the power button, such as Recovery Mode, sends me back to the Erasing screen. Pushing Vol+, Vol-, and Power shuts the phone off completely. Holding the Power button down does nothing more than restart the phone into the Erasing screen. I have also let the phone die twice and as soon as it has enough juice to come back on, it goes straight to the Erasing screen. Everything on the phone is stock and it is completely unrooted. The bootloader screen also indicates it is unlocked. I have attempted to flash it as per instructions I have found on here but I am unable to download the stock factory images. It gets to about 90% before the install fails and I have tried to install three times already. I do have the 15 Second ADB installed, however. I assumed the install of the factory images failed because I don't have WiFi and I'm running completely off of limited 3G data (I live in the middle of no where with no high speed internet to speak of). So in lieu of all that I have attempted, is there ANYTHING at all that can be done to get the phone off of this Erasing screen? Or do I just need to try and return it because it's useless at this point? I did at first let the process run but it's now been 24 hours stuck on this Erasing screen with no improvement. I'm fairly certain it runs KitKat 4.4.0.

Kyocera Rise soft bricked. Suggestions?

Hello everyone. I am an old member, seeing as I registered almost four years ago, but I guess either your database was refreshed and it lost my username, or I only lurked. So, as the title suggests I have one of those lowly, inexpensive, down right cheap Kyocera phones. Here is what I have figured out so far. I was able to root it using Kingroot. That went splendidly, though because of my over adventurousness I decided to swap some apps out. I added a new launcher to the /system/app folder and wanted to upgrade the com.android.settings.apk with one from a newer build. This phone (was) running Android 4.0.4 Kyocera release r77 build date 2013. Apparently Kyocera loves to lock the bootloader so if I was able to spin a custom system rom I wouldn't be able to flash it. Another thing which discovered was upon boot up the system checks the integrity of app the system apps. If one of them fails the check it will not boot the system fully. I was able to recover the stock boot/recovery/system roms from a thread on here, but I seem to be stuck in a soft brick loop. One thing that another thread said, the thread that had the rom images, it said that you could used ADB to flash the roms to the phone. Thing is, when I boot the phone it restarts, and if I put it into recovery mode (press and hold volume down plus power for ten to fifteen seconds) the only options I have are "reboot system now", "wipe data/factory reset", "wipe cache partition." There is no "flash update from sd card" or wipe dalvik cache option. As I have said before, I could try to flash the rom to it using adb but I believe that wiping the system partition unset the USB debugging setting. When I connect it to my computer windows device manager notices the kyocera removable device for a second then as the phone reboots it goes away. Setting it into recovery mode does not make it show up in windows. Is there any way I can flash the stock rom onto it? Any android sdk or adb trick I can use that can boot it into some recovery mode? I was trying to see if I can get it to boot into download mode but seeing as it has soft keys and not a physical home button I do not know if I can manage that. I was thinking that maybe they tied one of the physical keyboard buttons to the home button but I have yet to uncover that one. Any help would be appreciated.

Zestypanda said:
Hello everyone. I am an old member, seeing as I registered almost four years ago, but I guess either your database was refreshed and it lost my username, or I only lurked. So, as the title suggests I have one of those lowly, inexpensive, down right cheap Kyocera phones. Here is what I have figured out so far. I was able to root it using Kingroot. That went splendidly, though because of my over adventurousness I decided to swap some apps out. I added a new launcher to the /system/app folder and wanted to upgrade the com.android.settings.apk with one from a newer build. This phone (was) running Android 4.0.4 Kyocera release r77 build date 2013. Apparently Kyocera loves to lock the bootloader so if I was able to spin a custom system rom I wouldn't be able to flash it. Another thing which discovered was upon boot up the system checks the integrity of app the system apps. If one of them fails the check it will not boot the system fully. I was able to recover the stock boot/recovery/system roms from a thread on here, but I seem to be stuck in a soft brick loop. One thing that another thread said, the thread that had the rom images, it said that you could used ADB to flash the roms to the phone. Thing is, when I boot the phone it restarts, and if I put it into recovery mode (press and hold volume down plus power for ten to fifteen seconds) the only options I have are "reboot system now", "wipe data/factory reset", "wipe cache partition." There is no "flash update from sd card" or wipe dalvik cache option. As I have said before, I could try to flash the rom to it using adb but I believe that wiping the system partition unset the USB debugging setting. When I connect it to my computer windows device manager notices the kyocera removable device for a second then as the phone reboots it goes away. Setting it into recovery mode does not make it show up in windows. Is there any way I can flash the stock rom onto it? Any android sdk or adb trick I can use that can boot it into some recovery mode? I was trying to see if I can get it to boot into download mode but seeing as it has soft keys and not a physical home button I do not know if I can manage that. I was thinking that maybe they tied one of the physical keyboard buttons to the home button but I have yet to uncover that one. Any help would be appreciated.
Click to expand...
Click to collapse
Hi and thank you for using XDA Assist
If you can access your recovery it is already a good thing, try first to wipe data and see how it goes.

nilac said:
Hi and thank you for using XDA Assist
If you can access your recovery it is already a good thing, try first to wipe data and see how it goes.
Click to expand...
Click to collapse
So, I boot into recovery and I do the wipe data/factory reset then the wipe cache partition for good measure and it still halts on boot. Same thing. Boot, kyocera logo, virgin mobile boot splash, then it halts where it would normally go into android. Then it reboots. Rinse repeat.

Any suggestions? I sorta need the information off the phone.

Issues flashing stock with odin J700t

I have a question, dont really know where to ask. I have the tmobile j700t, and I've tried restoring with odin, (with the j700t firmware of course) and im not sure if its doing everything. Everything seems to go fine in odin, flashes boot, modem, system etc. reboots, rebuilds cache, then it just goes to my original lock screen with my custom wallpaper and all my apps still on. I can do a factory reset after, but it doesnt seem to do anything but clear the cache. Am I missing something? I enables OEM UNLOCK and USB debugging before hand.

The inability to make write changes sounds like a bad NAND issue, you could try flashing with a .pit file but the phones internal memory could be physically damaged.

Andromendous said:
I have a question, dont really know where to ask. I have the tmobile j700t, and I've tried restoring with odin, (with the j700t firmware of course) and im not sure if its doing everything. Everything seems to go fine in odin, flashes boot, modem, system etc. reboots, rebuilds cache, then it just goes to my original lock screen with my custom wallpaper and all my apps still on. I can do a factory reset after, but it doesnt seem to do anything but clear the cache. Am I missing something? I enables OEM UNLOCK and USB debugging before hand.
Click to expand...
Click to collapse
Try clicking the Nand erase all box and unclicking auto reboot. Flash the factory ROM and when it completes hold volume down, home and power buttons until the screen goes black. This is important, as soon as the download screen is gone you need to hold the recovery buttons (volume up, home and power) so the phone can erase all system data and update itself the way it's designed to after flashing a factory update. If the device reboots before you enter recovery you have to start over. Hit thanks if this helps bro.

Metabolic12 said:
Try clicking the Nand erase all box and unclicking auto reboot. Flash the factory ROM and when it completes hold volume down, home and power buttons until the screen goes black. This is important, as soon as the download screen is gone you need to hold the recovery buttons (volume up, home and power) so the phone can erase all system data and update itself the way it's designed to after flashing a factory update. If the device reboots before you enter recovery you have to start over. Hit thanks if this helps bro.
Click to expand...
Click to collapse
well that seems to have fixed it, weird though, when I rebooted into recovery like you said, it did an update, there was a progress bar, then it rebooted, and rebooted AGAIN, did an "update" and then rebooted. Weird, I usually see it say "updating" but then it will stop and you can bring up the recovery menu. Never seen a progress bar and then it just reboot twice. Well anyway it seems to have worked so thank you!

Andromendous said:
well that seems to have fixed it, weird though, when I rebooted into recovery like you said, it did an update, there was a progress bar, then it rebooted, and rebooted AGAIN, did an "update" and then rebooted. Weird, I usually see it say "updating" but then it will stop and you can bring up the recovery menu. Never seen a progress bar and then it just reboot twice. Well anyway it seems to have worked so thank you!
Click to expand...
Click to collapse
Whenever you flash back to stock or update a stock firmware through official means, it automatically boots into recovery and erases the system you have in place, very similar to TWRP. If you try to flash a stock firmware without erasing everything you will always run into some kind of incompatible memory error. The screen you're thinking of is just the stock recovery checking your system and OTA's for an official upgrade. Glad I could help man.

My Google Pixel seems bricked - Could someone confirm there is nothing I can do ?

Hi, here's a description of what happened, what I did to solve my problem, and where I am now...
I left my Google Pixel and 2 hours later found it stuck into a booting loop (Google logo displayed > black screen > Google logo displayed > blackscreen...).
I first entered fastboot and tried to power off, restart, etc a few times, but it stayed stuck into the booting loop.
So I downloaded latest OTA from Google for my phone (my phone was already updated to the latest version via the phone update manager, which goes back to december 2019 I think).
I first verified that my linux pc could correctly see the devices, and then from fastboot I entered recovery mode and chose "Apply update from ADB".
I used the adb command to load the OTA I had downloaded.
The update progressed until it finished with the following error message :
Code:
install from ADB completed with status 1
Installation aborted
E:Failed to clear BCB messages: failed to write /dev/block/platform/soc/62400.ufshc/by-name/misc: I/O error
I was back on the recovery menu screen, and this is where I think I did something stupid : I selected "Reboot system now".
The phone did not reboot, the screen just went black and stays black. The phone is cold so I guess not running anything. And it does not respond to any button, so not starting up, no fastboot, etc. No more when I connect it to a PC or plug it in a power plug.
I don't really care about the phone, I was just trying to get back my picture/videos from the last 6 months.
I don't have much hope but I will appreciate any help, even if its just to confirm that there is nothing to do

rraphrr said:
Hi, here's a description of what happened, what I did to solve my problem, and where I am now...
I left my Google Pixel and 2 hours later found it stuck into a booting loop (Google logo displayed > black screen > Google logo displayed > blackscreen...).
I first entered fastboot and tried to power off, restart, etc a few times, but it stayed stuck into the booting loop.
So I downloaded latest OTA from Google for my phone (my phone was already updated to the latest version via the phone update manager, which goes back to december 2019 I think).
I first verified that my linux pc could correctly see the devices, and then from fastboot I entered recovery mode and chose "Apply update from ADB".
I used the adb command to load the OTA I had downloaded.
The update progressed until it finished with the following error message :
Code:
install from ADB completed with status 1
Installation aborted
E:Failed to clear BCB messages: failed to write /dev/block/platform/soc/62400.ufshc/by-name/misc: I/O error
I was back on the recovery menu screen, and this is where I think I did something stupid : I selected "Reboot system now".
The phone did not reboot, the screen just went black and stays black. The phone is cold so I guess not running anything. And it does not respond to any button, so not starting up, no fastboot, etc. No more when I connect it to a PC or plug it in a power plug.
I don't really care about the phone, I was just trying to get back my picture/videos from the last 6 months.
I don't have much hope but I will appreciate any help, even if its just to confirm that there is nothing to do
Click to expand...
Click to collapse
Well you could try and see if the phone is in deep flash mode, if it is flash system, boot and other sensitive partitions but make sure that the versions are the same. If you don't have the firmware you can pull user data partition from phone and get your data back that way

muhammad42620 said:
Well you could try and see if the phone is in deep flash mode, if it is flash system, boot and other sensitive partitions but make sure that the versions are the same. If you don't have the firmware you can pull user data partition from phone and get your data back that way
Click to expand...
Click to collapse
Thanks for your help. This is probably beyond my capabilities. I don't know how to check if it's in deep flash mode. Pulling the data out is what I'm interested in most.
Maybe this is something that a phone repair shop is able to do...

rraphrr said:
Thanks for your help. This is probably beyond my capabilities. I don't know how to check if it's in deep flash mode. Pulling the data out is what I'm interested in most.
Maybe this is something that a phone repair shop is able to do...
Click to expand...
Click to collapse
These phones get emmc errors. Common issue with this device