Related
Hi, So I'm kinda new to all this Android stuff.
I got my Nexus S with ICS 4.0.3 > which SUCKS!
I can't use Wi-Fi at ALL
But that was OK until I wanted to protect my stuff with a pattern lock!
My little sister came and missed with it which locked the phone and asked me to enter my Google account email and password (I don't have internet access for a while, not to mention no Wi-Fi!)
then I tried to Recover the phone and Hard reset it but couldn't due to known bugs n issues!
NOW I think about going back to the GingerBread 2.3.6 and wait for updates for the ICS and bug fixes
SO My question is: HOW CAN I DOWNGRADE TO GINGERBREAD IF I CAN'T ACCESS THE CLOCKWORLD? I can't use USB! I REALLY NEED HELP
Sorry for writing too much but I need help and a couple of good Advices!
THANK YOU!
Assassio said:
NOW I think about going back to the GingerBread 2.3.6 and wait for updates for the ICS and bug fixes
Click to expand...
Click to collapse
4.0.4 resolves a lot of problems of 4.0.3, I would consider upgrade instead.
I think you can always get in to the bootloader by switching off the phone and then switching it on while pressing Volume Up. There you should be able to performe a complete reset by unlocking the bootloader and then flashing the factory image via fastboot, but you will loose everything you have in the phone's internal memory.
Well, I did go to the bootloader screen but whenever I choose the Recovery choice it takes me to a picture of an android with an Exclamation mark on it for a sec then POFF! I can't do anything.
What should I do?
Assassio said:
Well, I did go to the bootloader screen but whenever I choose the Recovery choice it takes me to a picture of an android with an Exclamation mark on it for a sec then POFF! I can't do anything.
What should I do?
Click to expand...
Click to collapse
You don't have to get into the recovery.
Here are the instructions to perform a flash of the factory image:
http://www.androidaddicted.com/firm...4-imm76d-with-factory-image-firmware-836.html
Use fastboot
Assassio said:
Well, I did go to the bootloader screen but whenever I choose the Recovery choice it takes me to a picture of an android with an Exclamation mark on it for a sec then POFF! I can't do anything.
What should I do?
Click to expand...
Click to collapse
What happened is - when you update to newer version, after the first reboot android puts a new updated recovery.
You need to use fastboot in bootloader mode to re-flash or reboot with the clockwork recovery.
Instructions can be found here:
wiki.cyanogenmod.com/wiki/Fastboot
Good luck!
After my Fido XT925 received OTA update, it installed succesfully. Some days ago phone working slow down, and i did the factory reset from settings. After that it bootloped (M logo the black screen than green android guy). and when i select "normal booting" through the boot selector menu but it stuck on the Fido logo. after many attempts to boot with other options it booted once from the "Factory" option, but it soo slooow working and i've tryed to do factory reset from the recovery. After that it wan't boot anyway with any options, always stucks on the Fido logo or bootloop. Only after that i've try to unlock the bootloader to full flash. On the last step (when i send command with unique key) it said "failed (too many links)", but when phone reboot it show the warning logo about unlocked bootloader, and in AP Fastboot Mode string with device status is "device is UNLOCKED status code 3".
1) Now it can't be flashed through RSD Lite (it looks like flashing, RSD and fastboot.exe show all steps, no error but on the phone nothing changes)
2) It boot but stuck on the FIdo logo
3) I can access to the ADB Interface from the BP Tools (boot option) after manually edit & install usb driver
4) Bootloader Unlocked
4) i've made logcat boot process (in the attachments)
5) No motorola service in Russia (no way to use hardware programmer)
6) Battery no problem - i charge it using BP Tools
Now there is the question - is there any way to get it work?
mine had strange behaviour 'out-of-the-box' like reboots, bootloops, unwanted factory resets, until from recovery menu I wiped every partition twice.
give it a try :good:
bgumble said:
mine had strange behaviour 'out-of-the-box' like reboots, bootloops, unwanted factory resets, until from recovery menu I wiped every partition twice.
give it a try :good:
Click to expand...
Click to collapse
thanks, but it no success. (still stuck on the Fido Logo)
from adb shell, looks like there is no access to /data, /cache, /tmp partitions (also in log similar errors). when i try any commands said there is no permissions. For /sdcard also no access but there is another failure - i/o error.
Also, from adb shell i've found binary "restore_userdata" in /system/bin when i've tried to did it it cannot be done, cause no permissions.
I can't install any apk's through the adb cause data partition non accessable and i don't have root for install it in the system partition =( If i had that i can install custom recovery (Safestrap maybe) and then flash custom...
maks.xt925 said:
thanks, but it no success. (still stuck on the Fido Logo)
from adb shell, looks like there is no access to /data, /cache, /tmp partitions (also in log similar errors). when i try any commands said there is no permissions. For /sdcard also no access but there is another failure - i/o error.
Also, from adb shell i've found binary "restore_userdata" in /system/bin when i've tried to did it it cannot be done, cause no permissions.
I can't install any apk's through the adb cause data partition non accessable and i don't have root for install it in the system partition =( If i had that i can install custom recovery (Safestrap maybe) and then flash custom...
Click to expand...
Click to collapse
Try to boot in recovery mode and do a factory reset. See what happens then. Booting in factory mode is different than doing a factory reset, maybe your data partition is full
Sent from my XT925 using Tapatalk 2
danifunker said:
Try to boot in recovery mode and do a factory reset. See what happens then. Booting in factory mode is different than doing a factory reset, maybe your data partition is full
Sent from my XT925 using Tapatalk 2
Click to expand...
Click to collapse
Already tried, it wrote wiping data, wiping cache, then prepairing for BP masterclear and no one error.
maks.xt925 said:
Already tried, it wrote wiping data, wiping cache, then prepairing for BP masterclear and no one error.
Click to expand...
Click to collapse
Try jelly bean fastboot, let me know.
Sent from my XT925 using Tapatalk 2
danifunker said:
Try jelly bean fastboot, let me know.
Sent from my XT925 using Tapatalk 2
Click to expand...
Click to collapse
Tryed to flash new xml 9.8.2Q-8-XT925_VQL-12.2 FULL through the fatsboot.exe (unzip and manually flash step by step) and RSD, nothing changes. Already tried to flash many other xml fw with no success. Also tryed flashing backup Rogers Jelly Bean FullXML-Feb.11-21.06.41
remove sdcard
it looks like a broken hardware.
last idea I have: remove sdcard and start wiping again
bgumble said:
it looks like a broken hardware.
last idea I have: remove sdcard and start wiping again
Click to expand...
Click to collapse
there is no sdcard installed. also nosim card. (but i've already tried with installed)
UPD: Now, dont't worry about buggy-phone, sell it for parts...
Looks like I am having same issue with my Fido Motorola RAZR HD, after receiving JB update, I couldn't do a security wipe within the OS, so power cycled the phone and did factory reset via Android boot screen, but now my phone can't boot into the OS. keeps rebooting over and over again, the green android guy with blue bar beneath it.
All Rogers/Fido have a bug after JB ota update ... if you security wipe by the setting menu or via recovery... you stuck on Motorola Logo ... you can't enter in recovery mode too ... I just imagine all return... There are two ways to recover your phone ... send in repair center ... or flash the JB rom via RSD ...
in the two case ... you loose the root forever ! and you can't get back to ics to root again ;( ( until you unlock the bootloader and void your moto warranty )
This is a basic bug .. why motorola don't update their ota package to fix this bug !
o2qc418 said:
All Rogers/Fido have a bug after JB ota update ... if you security wipe by the setting menu or via recovery... you stuck on Motorola Logo ... you can't enter in recovery mode too ... I just imagine all return... There are two ways to recover your phone ... send in repair center ... or flash the JB rom via RSD ...
in the two case ... you loose the root forever ! and you can't get back to ics to root again ;( ( until you unlock the bootloader and void your moto warranty )
This is a basic bug .. why motorola don't update their ota package to fix this bug !
Click to expand...
Click to collapse
Look, I was just passing by and thought that maybe the firmwares from Brazil could help you. The firmwares from brazilian ICS never gave any problem to the users. Try to download retail brazilian ICS. I have my moto with unlocked bootloader and have flashed the brazilian firmware more than 10 times and never had problems. (After flash, phone will reboot and load itself but you will have bootloop. Then, you reboot cellphone (power + vol - for 10 seconds), enter recovery and wipe everything.)
=)
The problem is when the consumer don't have the bootloader unlocked ...
and the retail brazil don't have all languages .... i need french ;p !
If your problem sounds anything like this, please let me know..I'll post the solution.
"So you did a factory reset.then phone tried to reset but couldn't and goes into a boot loop. The Motorola symbol comes then the green android guy..then it dies after a few seconds..then the cycle goes on and on " ..
Is this what you're experiencing?? I'm on the Fido RAZR HD too.Let me know
Sent from my XT925 using xda premium
slickfing said:
If your problem sounds anything like this, please let me know..I'll post the solution.
"So you did a factory reset.then phone tried to reset but couldn't and goes into a boot loop. The Motorola symbol comes then the green android guy..then it dies after a few seconds..then the cycle goes on and on " ..
Is this what you're experiencing?? I'm on the Fido RAZR HD too.Let me know
Sent from my XT925 using xda premium
Click to expand...
Click to collapse
I have this exact problem after the Rogers OTA update!
Any solution would be most appreciated.
like i say ... in up : All Rogers/Fido have a bug after JB ota update ... if you security wipe by the setting menu or via recovery... you stuck on Motorola Logo ... you can't enter in recovery mode too ... I just imagine all return... There are two ways to recover your phone ... send in repair center ... or flash the JB rom via RSD ...
in the two case ... you loose the root forever ! and you can't get back to ics to root again ;( ( until you unlock the bootloader and void your moto warranty )
This is a basic bug .. why motorola don't update their ota package to fix this bug !
THE ONLY SOLUTION :
... Download the rogers jelly bean roms and flash with rsd lite ... FLASH ! ( you dont need to unlock the bootloader ) all work great after ! ...
slickfing said:
If your problem sounds anything like this, please let me know..I'll post the solution.
"So you did a factory reset.then phone tried to reset but couldn't and goes into a boot loop. The Motorola symbol comes then the green android guy..then it dies after a few seconds..then the cycle goes on and on " ..
Is this what you're experiencing?? I'm on the Fido RAZR HD too.Let me know
Sent from my XT925 using xda premium
Click to expand...
Click to collapse
This is exactly what happened to mine, I managed to fix mine (not really sure how) via getting into menu and selecting factory reset but I had to do it about 10 times for it to finally get past the bootloop and stick. The first few times I tried I could get past the bootloop and into the OS but when I powered the phone off and then back on it would bootloop again, persistance paid off though.The phone has been faultless since and that was about 2 months ago.
What is the solution you used to fix as I would be grateful for future reference?
Cheers
XRCIST said:
This is exactly what happened to mine, I managed to fix mine (not really sure how) via getting into menu and selecting factory reset but I had to do it about 10 times for it to finally get past the bootloop and stick. The first few times I tried I could get past the bootloop and into the OS but when I powered the phone off and then back on it would bootloop again, persistance paid off though.The phone has been faultless since and that was about 2 months ago.
What is the solution you used to fix as I would be grateful for future reference?
Cheers
Click to expand...
Click to collapse
I'd just like to announce that this fix has worked for me.
Even better, I did not have to do it 10 times like you said. It was fixed after the first try. No problems getting into the OS after power off/boot or after a forced reboot. :highfive:
For others' reference, to get into the menu you have to press the "middle of the volume rocker" (basically to get both buttons pressed, some have tried it by doing vol down first then vol up), which will send it into a data wipe procedure. Once it gets to the recovery menu, go back to factory reset and do the data wipe again. Then, reboot. After X number of tries (for poster above it required 10, for me it required 1) the problem should have gone away.
Thanx for this thread it worked for me as well
First I'd like to thank the mods and everyone who contributes to this forum. It's an invaluable resource. Now to my problem.
Asus Tf700 is unlocked and rooted on latest TWRP recovery, which does work. However, after making a backup with the new TWRP version, the tablet is stuck on the boot screen (spinning wheel). Last week I flashed a JB ROM, didn't like it, so went back to ICS with the .30 firmware. Flashed it using old version of TWRP from micro-SD card. Device has been working fine since then. I tried reflashing the .30 kernel again using the same method. It installs kernel, but no luck, still stuck on boot screen. Then I tried TWRP restore, using the new restore file. It restores, but goes to the boot screen and just spins. Any ideas? nvFlash is unavailable to me. What else can I do? Should I try a factory restore in TWRP? I'll keep messing with it later today, but any suggestions are appreciated.
When you install a stock rom, doesnt it install back the stock recovery? I would try reflashing twrp and installing cleanrom, keep it as stock as possible and see if it boots.
Sent from my ASUS Transformer Pad TF700T Infinity using Tapatalk HD
Rom: CleanRom 3.4.4
A spinning Asus wheel is always recoverable.
You have some incompatible rom / kernel / bootloader / data combination I suspect. It's easily done.
I'd make sure you are on a more recent version of TWRP - something like 2.3.1.0 or 2.3.3.0 that supports ICS and JB. It's very dangerous leaving such an old version of TWRP if you go to JB.....
Personally I'd update TWRP to 2.3.1.0 and then install the latest JB file from the Asus website to start with.
missiveusa said:
First I'd like to thank the mods and everyone who contributes to this forum. It's an invaluable resource. Now to my problem.
Asus Tf700 is unlocked and rooted on latest TWRP recovery, which does work. However, after making a backup with the new TWRP version, the tablet is stuck on the boot screen (spinning wheel). Last week I flashed a JB ROM, didn't like it, so went back to ICS with the .30 firmware. Flashed it using old version of TWRP from micro-SD card. Device has been working fine since then. I tried reflashing the .30 kernel again using the same method. It installs kernel, but no luck, still stuck on boot screen. Then I tried TWRP restore, using the new restore file. It restores, but goes to the boot screen and just spins. Any ideas? nvFlash is unavailable to me. What else can I do? Should I try a factory restore in TWRP? I'll keep messing with it later today, but any suggestions are appreciated.
Click to expand...
Click to collapse
1. What bootloader are you on currently? (See 4)
2. By flashing the ".30 kernel" I assume you mean flashing the .30 stock ROM, am I right?
Your device went into a hung boot after making the backup, so I'm not really surprised it does exactly the same when you restore that backup. Have you tried flashing .30 stock ROM again?
3. Which recovery do you currently have? As Tylorw1 said, if you flash a full stock ROM, you'll reflash everything, up to and including the bootloader and recovery.
4. If you still have fastboot available (pick the USB symbol instead of RCK after POWER+VOL_DOWNing), you might want to try to reflash either TWRP or CWM (http://forum.xda-developers.com/showthread.php?t=1926286 for the latter; I have VERY limited experience with the former and you may well have more than me ).
Updating your bootloader just to be sure is recommended, as most current ROMs will not boot properly without it.
Has the fiddling brought any new points of view, or new discoveries?
Update
Just got in from work. Of course can't do anything else but try to get this unworking device to boot. Not in panic mode yet, as I assume if I get to the spinning wheel, there is hope for recovery.
Just flashed back to the stock ROM, which indeed restored stock recovery. Still would not boot past Asus wheel. Now I will attempt to install the latest TWRP version using fastboot, then try to flash new ROM. Panic is slowly creeping in, but I think I just need to keep at it. How should I proceed once latest version of TWRP is installed? Backup? Flash? Android is new territory for me, a bit rockier than Windows. If this were a laptop on Windows 7 I'd be up and running already . Thanx for the replies and any help.
OK. I used stock recovery to to a system restore. That worked, but of course all user data and apps are gone. Assume root access is also history, so it's just a matter of getting root access and restoring apps. I made a backup to SD card using Titanium Backup. Can I restore from here using the backup file, or should I just stop complaining and be happy I got the damn thing to boot?!!! No big deal really: I'm back to STOCK .26, virgin device (except for being unlocked). Guess I'll get root and move on. Thanks. Great work here. I've learned a lot browsing these forums. Maybe one day I'll graduate from N00B status!
missiveusa said:
Just got in from work. Of course can't do anything else but try to get this unworking device to boot. Not in panic mode yet, as I assume if I get to the spinning wheel, there is hope for recovery.
Click to expand...
Click to collapse
Agreed.
Just flashed back to the stock ROM, which indeed restored stock recovery. Still would not boot past Asus wheel. Now I will attempt to install the latest TWRP version using fastboot, then try to flash new ROM. Panic is slowly creeping in, but I think I just need to keep at it. How should I proceed once latest version of TWRP is installed? Backup?
Click to expand...
Click to collapse
No use -- it won't boot.
Flash?
Click to expand...
Click to collapse
CROMI, redownload, hash check.
Android is new territory for me, a bit rockier than Windows. If this were a laptop on Windows 7 I'd be up and running already .
Click to expand...
Click to collapse
I know exactly what you're talking about. Was there once as well, and still it is changing so fast it's hard to keep up.
Thanx for the replies and any help.
OK. I used stock recovery to to a system restore. That worked, but of course all user data and apps are gone. Assume root access is also history, so it's just a matter of getting root access and restoring apps. I made a backup to SD card using Titanium Backup. Can I restore from here using the backup file, or should I just stop complaining and be happy I got the damn thing to boot?!!!
Click to expand...
Click to collapse
I would not take the chance, and just leave it as it is.
No big deal really: I'm back to STOCK .26, virgin
Click to expand...
Click to collapse
<< and still complaining?
device (except for being unlocked). Guess I'll get root and move on. Thanks. Great work here. I've learned a lot browsing these forums. Maybe one day I'll graduate from N00B status!
Click to expand...
Click to collapse
Maybe...
J/K!
You've done great, and I am happy to hear you got it up and running. I started out answering before reading your post in full, assuming it wasn;t fixed yet. Left the comments for reference (and fun, or mockery... -- good job, see you around!
same issue
Hi,
I have a same issue. I still was using the original ROM of ASUS. Now JB.
The device was once rooted in ICS, but that was lost when going to JB. And I did not yet try to reroot it. I was running JB already several months.
The device is unlocked, but I did not install a custom boatloader yet.
This week I was working in the car. Using the 3G connection of my phone and shared it via bluetooth to my pad to access my mails.
Suddenly the pad rebooted, and it never got further than the ASUS screen with the spinning wheel.
I can boot in recovery mode (power and V-), but then I cannot use my V+ buttom. I can only select the RCK, but unfortunately, It's not succesful. I first get the android with open lid and the spinning ball, but after a few seconds it changes to the android with the open lid laying on his bag with the red triangle on it. And it stays like this forever.
I cannot seem to enter fastboot mode (power and V+)
any suggenstion? All data can be erased. No problem as long as the tablet is working again.
TeTTiweTTi said:
Hi,
I have a same issue. I still was using the original ROM of ASUS. Now JB.
The device was once rooted in ICS, but that was lost when going to JB. And I did not yet try to reroot it. I was running JB already several months.
The device is unlocked, but I did not install a custom boatloader yet.
This week I was working in the car. Using the 3G connection of my phone and shared it via bluetooth to my pad to access my mails.
Suddenly the pad rebooted, and it never got further than the ASUS screen with the spinning wheel.
I can boot in recovery mode (power and V-), but then I cannot use my V+ buttom. I can only select the RCK, but unfortunately, It's not succesful. I first get the android with open lid and the spinning ball, but after a few seconds it changes to the android with the open lid laying on his bag with the red triangle on it. And it stays like this forever.
I cannot seem to enter fastboot mode (power and V+)
any suggenstion? All data can be erased. No problem as long as the tablet is working again.
Click to expand...
Click to collapse
When you hold down vol- and power button to boot into stock recovery, then when you see white text on the screen, let go both buttons, then hitting the Vol down button to move the highlighted to USB icon, can you try that?
Edit: if that's working move the highlighted to the "WIPE" icon, then hit Volume up twice, this will perform factory reset and wipe all your data and reset your device back to factory setup. You will see the Android spinning for awhile then your tablet will reboot and you will have to do the setup again, just like when you just brought the device.
buhohitr said:
When you hold down vol- and power button to boot into stock recovery, then when you see white text on the screen, let go both buttons, then hitting the Vol down button to move the highlighted to USB icon, can you try that?
Edit: if that's working move the highlighted to the "WIPE" icon, then hit Volume up twice, this will perform factory reset and wipe all your data and reset your device back to factory setup. You will see the Android spinning for awhile then your tablet will reboot and you will have to do the setup again, just like when you just brought the device.
Click to expand...
Click to collapse
Thanks for your help. I can boot into stock recovery. But I could move to the USB icon or the the Wipe Icon previously. Now I was able to select the Wipe Data Icon and currently I'm at the virgin "Welcome" screen again.
I don't understand why now it's working and previously not. Did I switch the v- and v+ button? If that's the case, I'm even a bigger idiot then I thought :silly:
Anyhow, All well that ends well.
Stuck on spinning wheel as well
sbdags said:
A spinning Asus wheel is always recoverable.
You have some incompatible rom / kernel / bootloader / data combination I suspect. It's easily done.
I'd make sure you are on a more recent version of TWRP - something like 2.3.1.0 or 2.3.3.0 that supports ICS and JB. It's very dangerous leaving such an old version of TWRP if you go to JB.....
Personally I'd update TWRP to 2.3.1.0 and then install the latest JB file from the Asus website to start with.
Click to expand...
Click to collapse
Hi sdbags! Thanks for all the work that you have put in to make this rom!
I am stuck on the spinning wheel as well. I installed cromi x last week. The tab was working okay. Very laggy, was very disappointed. I guess I did something wrong? Last night I used lagfix and rebooted. Since then the tablet has been stuck on the spinning wheel stage. I am pretty sure I installed the latest version of TWRP and checked I had the latest bootloader. Can I check these things now? Also if they are outdated how I do I update them if my tablet wont boot up?
Thanks!
TransformingPad said:
Hi sdbags! Thanks for all the work that you have put in to make this rom!
I am stuck on the spinning wheel as well. I installed cromi x last week. The tab was working okay. Very laggy, was very disappointed. I guess I did something wrong? Last night I used lagfix and rebooted. Since then the tablet has been stuck on the spinning wheel stage. I am pretty sure I installed the latest version of TWRP and checked I had the latest bootloader. Can I check these things now? Also if they are outdated how I do I update them if my tablet wont boot up?
Thanks!
Click to expand...
Click to collapse
Lagfix takes a good 20 mins to complete, even though it says it has finished after 5. I wonder if you rebooted too early. If you have sync off it can cause corruption on the data partition which might be your issue.
The fix is to format data from the twrp wipe menu and reflash. You will lose Everything on internal so back up in twrp first please.
Sigh - all for naught
stuck on spinning cyan screen
i rooted the tf700t and installed twrp, flash cm 10.2 rc 1, then rebooted and now it is stuck on boot screen. now i find i cant get back to stock recovery or twrp to correct the issue or bootloader. anyway that my tablet isnt totalled?
tcemle said:
i rooted the tf700t and installed twrp, flash cm 10.2 rc 1, then rebooted and now it is stuck on boot screen. now i find i cant get back to stock recovery or twrp to correct the issue or bootloader. anyway that my tablet isnt totalled?
Click to expand...
Click to collapse
Why can't you go back? Vol down and power doesn't work?
CM requires you to be on the 10.6.1.14.4+ bootloader first. Also a wipe before installing is mandatory.
sbdags said:
Why can't you go back? Vol down and power doesn't work?
CM requires you to be on the 10.6.1.14.4+ bootloader first. Also a wipe before installing is mandatory.
Click to expand...
Click to collapse
i have tried several times to use the vol- and power buttons but it doesnt seem to work. i press them and then i feel like its trying but doesnt go anywhere just stays on the black screen. adb recognizes the tablet but says it is offline because the boot screen is stuck. it usually only took a few seconds for it to go to the fastboot screen but nothing now. any ideas, if i get to the fastboot i can correct the problem.
tcemle said:
i have tried several times to use the vol- and power buttons but it doesnt seem to work. i press them and then i feel like its trying but doesnt go anywhere just stays on the black screen. adb recognizes the tablet but says it is offline because the boot screen is stuck. it usually only took a few seconds for it to go to the fastboot screen but nothing now. any ideas, if i get to the fastboot i can correct the problem.
Click to expand...
Click to collapse
Hmm that sounds like apx mode to me. If you didn't save nvflash backups I suspect it has bricked
I just updated to KitKat via this threat: http://forum.xda-developers.com/showthread.php?p=52214068
I noticed that the tablet was running excessively slow and so I decided to do a Factory Reset from within the tablets Setting. Now it's rebooted and it's sitting at the Android and the spinning thing in it's chest for more than 5 mins. Does it normally take this long?
stuck itwrp 2.7.0.0
Hey guys
Long time reader 1st time asking for help. Had tf700t unlocked, rooted and running cm 10.2.1 with twrp 2.6.3.1. Tried several times to load cm 11 and met only with failure. Read a post to try twrp 2.7.0.0. Loaded twrp 2.7.0.0, via goo, backed up everything and tried to flash cm 11. Tablet stuck in wipe mode for 90 minutes. (didn't even get a chance to load it!) I stopped it and re-started into twrp 2.7.0.0. Tried to recover and got pictured error, basically stating that at the wiping data point - E:Unable to mount '/data'. Tried to flash new rom and get the same thing. I can get into recovery but that is about it..............spock help me
gothamhill said:
Hey guys
Long time reader 1st time asking for help. Had tf700t unlocked, rooted and running cm 10.2.1 with twrp 2.6.3.1. Tried several times to load cm 11 and met only with failure. Read a post to try twrp 2.7.0.0. Loaded twrp 2.7.0.0, via goo, backed up everything and tried to flash cm 11. Tablet stuck in wipe mode for 90 minutes. (didn't even get a chance to load it!) I stopped it and re-started into twrp 2.7.0.0. Tried to recover and got pictured error, basically stating that at the wiping data point - E:Unable to mount '/data'. Tried to flash new rom and get the same thing. I can get into recovery but that is about it..............spock help me
Click to expand...
Click to collapse
TWRP 2.7 does take a long time to wipe. You shouldn't have interrupted it. Now you probably have a corrupted data partition and you will have to format it. That will erase all your data, but if the nandroid you made was successful, that should not be a problem.
stolen
berndblb said:
TWRP 2.7 does take a long time to wipe. You shouldn't have interrupted it. Now you probably have a corrupted data partition and you will have to format it. That will erase all your data, but if the nandroid you made was successful, that should not be a problem.
Click to expand...
Click to collapse
1st of all thank you, unfortunately the nandroid bu was on a laptop that was stolen. Anything else I can do?
Looked around a lot and found no solution so here it goes.
I was trying to update to KitKat and at the Pwr Volume- screen I mistakingly hit the wipe data. I wasn't on a custom ROM before, I used the clockwork mod app to install TWRP. Now I'm stuck on the screen where it says This Device is Unlocked and won't do anything else. I've tried every restart button combo but it always goes back to that screen. Can anyone help me out please or is this a lost cause.
Also the computer does not recognize it since it won't get past the opening screen and fastboot/adb wont do anything either
Wipe data in bootloader mode when unlocked = bricked for good unless you have nvflash backups
Or, if you can get back into bootloader mode, follow busters method to unbrick
Sent from my GS3 on AOSB 4.4.2 using Tapatalk 4
Don't have NVFlash backups and I cant get to the boot loader so I guess I'm boned. Was good while it lasted, was running slow towards the end so I guess it was about that time lol
First of all, I'm pretty noob this days on Android so I'm very sorry guys, also english is not my first language.
My nexus was working great until today. I ended a Whatsapp Call and get a black screen, phone looks frozen (happened before). Reboot it and works fine for 5-10 minutes, after that it started to reboot itself the whole time in bootlop, stuck in the rom intro, after the Google text. My rom is one of the very first roms from Slim Roms, I'm sorry I don't remember the Android Version, but is "old".
I can access to the recovery mode tho. I tried to wipe dalvik cache and the TWRP failed, wipe and factory reset, fail as well... I don't know what else to do. I don't have any image to install in the sd, or any backup. Windows 10 recognize an "android" but can't access to it so I can't copy any file to it.
Is my phone dead or can I do something? I love this phone :crying:
Any help please? I tried using ADB and get to copy some files into the phone but still every time I try to do a wipe cache, factory reset or what ever I get a Unable to mount Data / Cache / Storage... every time the same error.
I google it and found that some people could fix that error by repairing the file system and select ext4. But I can't do that, my TWRP build is quite old (v2.6.3.4) and doesn't have that option here. Any suggestions?
Thanks btw
Me again
I've been reading forums for more than 7 hours today and trying different solutions, and nothing. But found this guy here https://androidforums.com/threads/is-my-nexus-5-dead.1099076/
He basically had the same issue as me few years ago, exactly the same, He didn't find any luck apparently.
How is it possible that a phone that can get access to TWRP or copy/flash files via ADB/Fastboot can't be saved? Theoretically in this case this is not a hard bricked, right? So? This is so so weird
It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.
No OS but twrp working
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!
audit13 said:
It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.
Click to expand...
Click to collapse
I tried that already, it does the installation thing but always fail in the end
mevrik_007 said:
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!
Click to expand...
Click to collapse
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad
ekeixdurden said:
I tried that already, it does the installation thing but always fail in the end
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad
Click to expand...
Click to collapse
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.
audit13 said:
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.
Click to expand...
Click to collapse
I tried that with the Nexus root tool kit and the bootloader still is unlocked
ekeixdurden said:
I tried that with the Nexus root tool kit and the bootloader still is unlocked
Click to expand...
Click to collapse
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.
audit13 said:
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.
Click to expand...
Click to collapse
Shieeeet... So nothing to do I guess? I already ordered a new phone but if I can save this beauty would be great
It would be great to fix it but the simplest solution may be to buy a nexus 5 with a smashed screen and working motherboard. I've done this before and it's worked out well because the nexus 5 is pretty old by today's phone standards so I got it cheap.
hmm not a bad idea at all. Thank you!