Related
I haven't done any flashing in about a week. Everything was working fine. And just today I ran the battery completely dry (which I usually do and it keeps my battery happy).
So I power it back up after a few mins of charging.....the LG screen comes on.....then the Ultimate 1.0 Rom loading logo comes up..after that every 10-15 seconds it turns on the screen, shuts it off, turns it on, off, etc. It keeps turning on and off...even after I left it there for 5 mins.
I'm going to flash back my Froyo stock rooted rom that I made a back up. The Ultimate 1.0 isn't the only rom I've flashed in the past. CM7 as well..many of the builds.
Argh.
I have my nandroid froyo backup on my SDcard and it says it can't find it.
This whole internal sd and external sd storage is a pain in the ass. The good old G1 days. Sigh. I went ahead with formatting the card as well and copying back the nandroid backup onto the card. Nothing.
That happened to me. I had to reset - battery pull alone wouldn't work. That phone is now on its way to T-Mobile, and its warranty replacement is going to be soon due to really bad screen bleed (affects my watching video and game play).
flexnix said:
Argh.
I have my nandroid froyo backup on my SDcard and it says it can't find it.
This whole internal sd and external sd storage is a pain in the ass. The good old G1 days. Sigh. I went ahead with formatting the card as well and copying back the nandroid backup onto the card. Nothing.
Click to expand...
Click to collapse
What was "it says" - ROM Manager?
If so, it looks for a androids on the internal SD. If you had used the easy recovery install tool, you would have been able to select internal or external to use with Recovery - NOT ROM Manager.
Based on your choice, you should be able to access you nandroid in the place you chose in RECOVERY MODE.
Since you fully drained you battery, you might want to erase battery specs in recovery, turn it off, and fully charge with it turned off for 8 hours. It is not recommended that you fully drain the battery and that may be your problem.
Then you could try wiping cache, dalvek, and format /system - and reflash your ROM. Save flashing the nandroid for last.
flexnix said:
I haven't done any flashing in about a week. Everything was working fine. And just today I ran the battery completely dry (which I usually do and it keeps my battery happy).
Click to expand...
Click to collapse
have you tried a different battery?
According to the experts at Popular Mechanics running your battery dry is very bad for it. It greatly reduces the life according to them. There was a post about it last week. There are physics involved that apply to all.
when this phone crashes and won't reboot, how do we even get into recovery without rom manager??
You need to NVflash your Recovery
EmceeGeek said:
when this phone crashes and won't reboot, how do we even get into recovery without rom manager??
Click to expand...
Click to collapse
You boot the phone holding Volume Up & Power buttons until recovery screen appears.
Recovery, if you flashed it using the NVflash tool, will be accessible by booting your phone while holding Vol Up & Power. You will go into Recovery. If you have never done this or do not get recovery its because you did not flash the Recovery onto your phone.
Basically, if all you did was download ROM Manager and start flashing the G2x you are playing with fire. You need to flash the Recovery onto the phone using NVflash tool. ( Follow Step2 in the following link: http://forum.xda-developers.com/showthread.php?t=1060715 )
I would recommend anyone with the same problem or the same question to go thru the link above and you will find answers to most of your problems.
EmceeGeek said:
when this phone crashes and won't reboot, how do we even get into recovery without rom manager??
Click to expand...
Click to collapse
You need to properly install Clockworkmod recovery with NVflash. Its a process but well worth it. Rom manager is a no no with out phones.
flexnix said:
You need to properly install Clockworkmod recovery with NVflash. Its a process but well worth it. Rom manager is a no no with out phones.
Click to expand...
Click to collapse
Did you rename your nandroid backup?
If you did that would be the problem. if you want to rename it, don't leave any spaces.
Sent from my G2x
Guys, wondering if someone could give me some direction to restoring my TF101 to working conditions.
I have a rooted TF101 that was running 9.1.2.27.
This setup has been running great since .27 (not done OTA, Found here) came out, so I haven't bothered upgrading recently.
Fast forward to this week and it seems the Tablet started locking up at some point in the last couple days I hadn't used it. This would cause a battery drain until the device turned off. Upon rebooting I could get into the OS for maybe a minute before it would freeze again.
I decided to wipe the device, I went into CWM Recovery and wiped all caches and then tried to wipe all data/factory reset. It is at this time I get the following error:
Error removing /data/data/com.android.browser/databases/webview.db-wal!Error formatting /data!
Try starting back up and get a boot loop.
Upon reflashing the ROM, I find the TF101 in constant boot loop not making it 8 seconds into the bootup before rebooting.
I can still get into recovery so I try various kernels and roms with no success. Through searching I find CWM 6.0.1.4 and load it. Everything loads normally and I can now wipe data/factory reset, wipe all Cache even format all parts. I try to flash every ROM I can get my hands on from stock to older roms that I have ran succesfully to EOS Nighties, Every rom goes into Boot Loop after about 10 seconds.
Any Idea on where to go from here? I have been reading threads for hours now with no solution.
MODS: Putting in DEV since this is a Rooted TF, but if this should go to Q&A please move
This question should be in the QA section...
But your stock ROM was ICS and the newest EOS nightlies are based on JB which have different partitions. If you flash back and forth with ICS and JB you could be running into problems there.
Have you tried the option in CWM called "Fix Permissions"? This is supposed to reset the permissions correctly for the system apps area I believe which helped a lot of people with force close issues. It's worth a shot.
Are you installing ROM's from external SD card or the Internal SD card? That shouldn't matter but I have always stuck with the External SD card.
One thing you could also try is to wipe the big 3 several times a piece before installing the ROM. I found it had made some ROM's load better when I encountered a few issues. Also, stick with one ROM either ICS or JB. Going back and forth will cause problems.
Also, I remember that from ICS to JB, some ROM's required the ROM to be installed twice literally after it installs install it again or some ROM's may reboot themselves back into recovery to complete the install.
Try that with the ROM you pick to get things back on track.
There is also some "Super Wipe" scripts floating around but I believe they were for a specific ROM and I think it was ICS based. You should be able to search XDA for that here in the Dev section.
TomTcom said:
This question should be in the QA section...
But your stock ROM was ICS and the newest EOS nightlies are based on JB which have different partitions. If you flash back and forth with ICS and JB you could be running into problems there.
Have you tried the option in CWM called "Fix Permissions"? This is supposed to reset the permissions correctly for the system apps area I believe which helped a lot of people with force close issues. It's worth a shot.
Are you installing ROM's from external SD card or the Internal SD card? That shouldn't matter but I have always stuck with the External SD card.
One thing you could also try is to wipe the big 3 several times a piece before installing the ROM. I found it had made some ROM's load better when I encountered a few issues. Also, stick with one ROM either ICS or JB. Going back and forth will cause problems.
Also, I remember that from ICS to JB, some ROM's required the ROM to be installed twice literally after it installs install it again or some ROM's may reboot themselves back into recovery to complete the install.
Try that with the ROM you pick to get things back on track.
There is also some "Super Wipe" scripts floating around but I believe they were for a specific ROM and I think it was ICS based. You should be able to search XDA for that here in the Dev section.
Click to expand...
Click to collapse
The ICS to JB isn't the issue as the issue started happening randomly with a ICS Rom that has been working for 4+ months when it has never had anything put ICS (well HC when I got it last year). Trying the JB rom was a near last ditch effort
I tried Revolutions superwipe several times, didn't help.
I probably completely screwed it up now in frustration. Tried to load the stock rom and now Recovery is screwed and it is boot loop so I don't think I can connect it to the computer now.
Hosed you think?
So now the question is, with a Tab that won't stay on longer then 8 seconds and no longer has a recovery, is there any other hope? I'm guessing bricked.
Firehawkns said:
So now the question is, with a Tab that won't stay on longer then 8 seconds and no longer has a recovery, is there any other hope? I'm guessing bricked.
Click to expand...
Click to collapse
You held down pwr + volume down when turning on and no text appears at the top left?
If not follow this thread
http://forum.xda-developers.com/showthread.php?t=1688012&highlight=nvflash
or http://forum.xda-developers.com/showthread.php?t=1688447&highlight=bootloop
Firehawkns said:
Guys, wondering if someone could give me some direction to restoring my TF101 to working conditions.
I have a rooted TF101 that was running 9.1.2.27.
This setup has been running great since .27 (not done OTA, Found here) came out, so I haven't bothered upgrading recently.
Fast forward to this week and it seems the Tablet started locking up at some point in the last couple days I hadn't used it. This would cause a battery drain until the device turned off. Upon rebooting I could get into the OS for maybe a minute before it would freeze again.
I decided to wipe the device, I went into CWM Recovery and wiped all caches and then tried to wipe all data/factory reset. It is at this time I get the following error:
Error removing /data/data/com.android.browser/databases/webview.db-wal!Error formatting /data!
Try starting back up and get a boot loop.
Upon reflashing the ROM, I find the TF101 in constant boot loop not making it 8 seconds into the bootup before rebooting.
I can still get into recovery so I try various kernels and roms with no success. Through searching I find CWM 6.0.1.4 and load it. Everything loads normally and I can now wipe data/factory reset, wipe all Cache even format all parts. I try to flash every ROM I can get my hands on from stock to older roms that I have ran succesfully to EOS Nighties, Every rom goes into Boot Loop after about 10 seconds.
Any Idea on where to go from here? I have been reading threads for hours now with no solution.
MODS: Putting in DEV since this is a Rooted TF, but if this should go to Q&A please move
Click to expand...
Click to collapse
Try using NV flash to go back to stock if you can get into APX mode.
Sent from my DROID RAZR HD using xda premium
morphuex said:
You held down pwr + volume down when turning on and no text appears at the top left?
If not follow this thread
http://forum.xda-developers.com/showthread.php?t=1688012&highlight=nvflash
or http://forum.xda-developers.com/showthread.php?t=1688447&highlight=bootloop
Click to expand...
Click to collapse
Yea, I can do the power + vol down and then up and get the recovery android guy, then he goes on his back and a red exclamation comes up (which I believe means no recovery mode installed
I can also do the pwr + vol down and then wait 5 seconds and get the wipe device or android options, but it won't let me choose anything, 10 seconds later it reboots.
clouse2013 said:
Try using NV flash to go back to stock if you can get into APX mode.
Sent from my DROID RAZR HD using xda premium
Click to expand...
Click to collapse
Will try tonight, but I believe all of those involve the computer having time to recognize the device, which it doesn't stay on long enough for the computer to recognize is and it won't seem to connect USB when the android guy is up.
nice rom! going to check this out tonight, thanks!
So I got into APX mode, windows shows no drivers, but it does show in devices. Trying NVFLash it says it is doing something, but nothing on the TF changes. Is there another step I am missing?
Firehawkns said:
So I got into APX mode, windows shows no drivers, but it does show in devices. Trying NVFLash it says it is doing something, but nothing on the TF changes. Is there another step I am missing?
Click to expand...
Click to collapse
Have a search for universal naked driver in the dev section, that should sort the drivers out I believe then you should be good to go.
---------- Post added at 10:37 PM ---------- Previous post was at 10:34 PM ----------
http://forum.xda-developers.com/showthread.php?t=1514942&highlight=naked+driver
There you go
pops106 said:
Have a search for universal naked driver in the dev section, that should sort the drivers out I believe then you should be good to go.
---------- Post added at 10:37 PM ---------- Previous post was at 10:34 PM ----------
http://forum.xda-developers.com/showthread.php?t=1514942&highlight=naked+driver
There you go
Click to expand...
Click to collapse
Thanks for the info, truly! I had searched for Drivers, but not naked.
That worked and it allowed me to use Easyflasher to get CWM back on.
Now I am back where I started, I have tried loading several Roms. Everyone hangs up about 15 seconds into first boot while the setup splash screen is on (for example the dotted circle on stock Asus rom or the simon says color circle like the JB rom or what ever it was in the ICS rom I was using. Something in the tab is stopping it from booting on up.
But I can now format everything and wipe data. I can connect APX mode. Anything else I can try from there. Starting to seem like something Hardware is busted.
Firehawkns said:
Something in the tab is stopping it from booting on up.
But I can now format everything and wipe data. I can connect APX mode. Anything else I can try from there. Starting to seem like something Hardware is busted.
Click to expand...
Click to collapse
Did you fix permissions while you were in recovery? It's a long shot but that may help. You may have a folder that's chmod'ed incorrectly. If so that'll prevent the system from being able to write or read to that folder making it impossible to install to, or run from it. Fix permissions, re-flash and reboot.
I know TomTcom mentioned it already. I don't see if you tried it in your replies though.
grgmre said:
Did you fix permissions while you were in recovery? It's a long shot but that may help. You may have a folder that's chmod'ed incorrectly. If so that'll prevent the system from being able to write or read to that folder making it impossible to install to, or run from it. Fix permissions, re-flash and reboot.
I know TomTcom mentioned it already. I don't see if you tried it in your replies though.
Click to expand...
Click to collapse
Yea, I tried that first. Sorry forgot to mention.
Are you able to flash the stock firmware using Easyflasher?
cabraswell said:
Are you able to flash the stock firmware using Easyflasher?
Click to expand...
Click to collapse
yes, I am able to flash to stock rom I got from Asus and the one I took for Rooted with stock on the forum. The flash, and it gives you the initial progress bar on first boot, then reboots at the end of the progress bar and goes to the Asus with the moving circles for about 5 seconds then keeps rebooting from there.
In a PC world I would wonder Ram issues, Over heating, or insuffecent power supply at this point. Not sure what to think here.
Is there a way to use TWOP and delete everything you see on the system and then reflash?
Firehawkns said:
yes, I am able to flash to stock rom I got from Asus and the one I took for Rooted with stock on the forum. The flash, and it gives you the initial progress bar on first boot, then reboots at the end of the progress bar and goes to the Asus with the moving circles for about 5 seconds then keeps rebooting from there.
In a PC world I would wonder Ram issues, Over heating, or insuffecent power supply at this point. Not sure what to think here.
Is there a way to use TWRP and delete everything you see on the system and then reflash?
Click to expand...
Click to collapse
In Addition, I have tried several times using TWRP to format Data and it fails. Could this be a clue?
Firehawkns said:
In Addition, I have tried several times using TWRP to format Data and it fails. Could this be a clue?
Click to expand...
Click to collapse
Have you tried using nvflash that blasts everything, takes you back to as clean as clean can be.
I am starting to think hardware though but if you can sit in recovery of adb / apx mode without issue then maybe it is a software thing.
No probs wiith the drivers by the way, its not really the right website for searching for the word naked.... dam don't can't won't imagine what you could of found with the members in here...
SUCCESS!!
I am not totally sure what finally worked as I just kept trying to reset/wipe/format/ and reflash, but this last time finally worked it seems. I have the stock Asus rom back on and going through setup.
I do find that if I try to put EOS on it just sits at the color things that show loading and never moves forward, so I just put the stock rom back on for now. Try to get Root back on for Titanium backup and enjoy the tablet again and worry about JB later maybe.
Firehawkns said:
SUCCESS!!
I am not totally sure what finally worked as I just kept trying to reset/wipe/format/ and reflash, but this last time finally worked it seems. I have the stock Asus rom back on and going through setup.
I do find that if I try to put EOS on it just sits at the color things that show loading and never moves forward, so I just put the stock rom back on for now. Try to get Root back on for Titanium backup and enjoy the tablet again and worry about JB later maybe.
Click to expand...
Click to collapse
I'm glad you finally got it fixed. I had some issues a while back (two weeks after I bought it) and I panicked and caused more trouble. Finally after stepping away from it for a day or two and a wife encouraging me I was able to get it going again...but my gut was in knots for that day or two.
Tablet after redoing the original root does not go over the system.
Not have access to ADB DEVICE or by Windows or the Linux Ubuntu, no longer accepts update totally blocked.
Ask help for those who have been through this problem.
Noob looking for all the help he can get!!!!!
Hi, I recently rooted my Samsung Galaxy S 2 for T-mobile, because I was sick of waiting for jelly bean to officialy come out for it, and ever since it's been a nightmare. I was running the most recent version of ICS that t-mobile has for my phone.
I got instructions on how to root at the unlocker . com
After that, I went to the Cyanogenmod website, went through their wiki and found the zip for my phone, (I also put the gapps zip on too). I booted into Clockwork mod recovery, did a back up, did a data wipe, but not a cache wipe as the instructions i was using from theunlocker.com did not say I had too. Flashed both zips from my external sd, then restarted. It booted with the Cyanogenmod name inside two spining circles. I left it like this knowing it may take a bit, and I come back 20 mins later expecting it to be done and it is in the same place i left it 20 mins ago. I decide to take out the battery, boot into Clockworkmod and restore. It booted fine back into ICS and all my data was still there, except all of the apps I had stored on my sd card would not work/show up with the icon it was supposed to. when i tapped it, it said that it was not installed on the phone. I decided not to let this worry me, as i decided to use ROM Manager app to do the job instead.
When i opened ROM Manager it prompted me to flash Clockworkmod recovery, so I did. It flashed my phone to Clockworkmod Recovery v6.0.2.7. I then went to download Cyanogenmod 10 for my phone. It downloaded with gapps 4.1. When I tapped install, it restarted my phone into Clockworkmod recovery, but did not install anything, just sent me to the main menu. So I decided i'd try getting the zip from the Cyanogenmod website again. I booted into Clockworkmod, wiped data AND cache this time. installed the zips, and restarted. I get the same problem, stuck at the cyanogenmod boot up circles spining. so i turn off my phone, boot back into clockworkmod, restore, and now i'm stuck in boot cycle with the stock ICS.
Please can anyone help me!?!?!?!
airplane888 said:
Noob looking for all the help he can get!!!!!
Hi, I recently rooted my Samsung Galaxy S 2 for T-mobile, because I was sick of waiting for jelly bean to officialy come out for it, and ever since it's been a nightmare. I was running the most recent version of ICS that t-mobile has for my phone.
I got instructions on how to root at the unlocker . com
After that, I went to the Cyanogenmod website, went through their wiki and found the zip for my phone, (I also put the gapps zip on too). I booted into Clockwork mod recovery, did a back up, did a data wipe, but not a cache wipe as the instructions i was using from theunlocker.com did not say I had too. Flashed both zips from my external sd, then restarted. It booted with the Cyanogenmod name inside two spining circles. I left it like this knowing it may take a bit, and I come back 20 mins later expecting it to be done and it is in the same place i left it 20 mins ago. I decide to take out the battery, boot into Clockworkmod and restore. It booted fine back into ICS and all my data was still there, except all of the apps I had stored on my sd card would not work/show up with the icon it was supposed to. when i tapped it, it said that it was not installed on the phone. I decided not to let this worry me, as i decided to use ROM Manager app to do the job instead.
When i opened ROM Manager it prompted me to flash Clockworkmod recovery, so I did. It flashed my phone to Clockworkmod Recovery v6.0.2.7. I then went to download Cyanogenmod 10 for my phone. It downloaded with gapps 4.1. When I tapped install, it restarted my phone into Clockworkmod recovery, but did not install anything, just sent me to the main menu. So I decided i'd try getting the zip from the Cyanogenmod website again. I booted into Clockworkmod, wiped data AND cache this time. installed the zips, and restarted. I get the same problem, stuck at the cyanogenmod boot up circles spining. so i turn off my phone, boot back into clockworkmod, restore, and now i'm stuck in boot cycle with the stock ICS.
Please can anyone help me!?!?!?!
Click to expand...
Click to collapse
First things first: the Jelly Bean update brings with it changes to the core file system organization in Android. Google "Android 4.2 Updates, Multi-User, and TWRP | TeamWin" for a brief explanation from TWRP (which, by the way, I recommend over ClockworkMod Recovery, although both can do the job). That, I believe, explains your missing data.
How are you obtaining your ROM/gapps zips? Are you downloading on your phone? If so, over wifi or mobile data? It is always a good idea to a) download on your computer and transfer the file to the phone and b) make a note of the MD5 checksum and verify the zip file before installing (any file browser worth its salt should be able to generate an MD5 sum). What it sounds like to me is your ROM download was borked in some way but it installed far enough to screw with your file system. I would recommend using your ICS backup to connect to a computer and load a ROM file downloaded from there before attempting to re-flash.
Maybe, just maybe you didn't clear cache and dalvik when installing cm. I had this problem and I realised I didn't wipe it. I wiped cache and dalvik cache from cwm and it booted fine.
Sent from my Xperia Mini Pro
ooddiittyy said:
First things first: the Jelly Bean update brings with it changes to the core file system organization in Android. Google "Android 4.2 Updates, Multi-User, and TWRP | TeamWin" for a brief explanation from TWRP (which, by the way, I recommend over ClockworkMod Recovery, although both can do the job). That, I believe, explains your missing data.
How are you obtaining your ROM/gapps zips? Are you downloading on your phone? If so, over wifi or mobile data? It is always a good idea to a) download on your computer and transfer the file to the phone and b) make a note of the MD5 checksum and verify the zip file before installing (any file browser worth its salt should be able to generate an MD5 sum). What it sounds like to me is your ROM download was borked in some way but it installed far enough to screw with your file system. I would recommend using your ICS backup to connect to a computer and load a ROM file downloaded from there before attempting to re-flash.
Click to expand...
Click to collapse
Thanks I will look into TWRP. I am getting my ROM/gapps zips straight from cyanogenmod's wiki for my phone, i get gapps from the link they provide. As for MD5, I do not know what that is other than it was generated when i backed up, and checked when i restored.
i have the same problem
i tried it with my galaxy fit s5670
i tried to flash cm-10.1-20130117-NIGHTLY-beni, some another version named of jelly bean pure rom and also TouchWiz_JB_V5
always the same thing it gets stuck at logo than nothing
i did everithing in order clear data, factory reset, clear cache, clear dalvik cache through cwm recovery
can someone help?
is it because of low int. space?
i found app named s2e to make sd card as int. memory but it didn't work
any suggestions?
thanks in advance
Here's my new problem, I'm stuck in boot loop with my restore of stock ICS, so when I go into download mode (+and- with power button while usb plugged in) I hear the "ching" that windows makes when you plug in a usb device, bu when I navigate to where removable disc should be in my computer, it is not there, so i don't know what to do, I just want my phone to work again, even if that means starting all over with stock ICS.
I appreciate your time and help.
airplane888 said:
Here's my new problem, I'm stuck in boot loop with my restore of stock ICS, so when I go into download mode (+and- with power button while usb plugged in) I hear the "ching" that windows makes when you plug in a usb device, bu when I navigate to where removable disc should be in my computer, it is not there, so i don't know what to do, I just want my phone to work again, even if that means starting all over with stock ICS.
I appreciate your time and help.
Click to expand...
Click to collapse
what ROM are you coming from?
Sounds to me like the new multi-user stuff
I experienced something similar and determined that the phone wasn't hung at that bootscreen -- it was busy moving my 18 gigs of stuff (i9300) from /storage/sdcard to /storage/sdcard/0. Apparently this is the "home data" folder for the primary user of a 4.2 device and CM10.1 (I'm assuming you're using that because of the problem) appears to be that way. It would have been nice to know beforehand that I should have just waited the 1/2-hour I needed (took about that long to move back what had been moved; very little hadn't)
So look for that 0 folder and move the contents up one -- your old ROM will (hopefully) be the way it was before. If you decide to go CM10.1 again, just wait, *really* long, at first boot -- or clean out your internal sd card to make the transition quicker.
---------- Post added at 11:06 PM ---------- Previous post was at 10:53 PM ----------
airplane888 said:
Here's my new problem, I'm stuck in boot loop with my restore of stock ICS, so when I go into download mode (+and- with power button while usb plugged in) I hear the "ching" that windows makes when you plug in a usb device, bu when I navigate to where removable disc should be in my computer, it is not there, so i don't know what to do, I just want my phone to work again, even if that means starting all over with stock ICS.
I appreciate your time and help.
Click to expand...
Click to collapse
You won't see it appear as removable storage because it's in download mode -- removable storage (and the later MTP mode) are done by the OS, and the downloader screen is much "dumber" than that.
HOWEVER, all is not lost!
Try get a ROM which you can flash with ODIN. Either something off of www . samfirmware . com (stock firmwares available there) or DarkyROM (darkyrom . com) (Sorry, can't post actual links because I'm apparently not allowed to until I've posted more stuff . I've found the S1 and S3 to be practically unbrickable in this regard -- I assume the S2 to be the same. ODIN can push a completely new ROM onto your device, rescuing it. If you download from samfirmware, there is a pdf with instructions available on their site, but it basically boils down to:
1) Download a ROM. If you are downloading a zip file, extract the .tar.md5 file inside somewhere -- this is the file you need to flash via ODIN
1) ensure you have the samsung drivers installed (they will be if you have Kies installed, otherwise google for them -- or ask, and I'll try to help)
2) put your phone into download mode (vol-down+home+power)
3) plug your phone into your PC
4) fire up ODIN, you should see a message about a connected device on-screen
5) click the "PDA" button, browse to the ROM image (the .tar.md5 file) and select it
6) the default options have always worked for me -- just click "Start". The process will take some time, but there is feedback in ODIN. Your phone should (after 1-5 minutes) reboot into a fresh, clean ROM.
If you installed a stock ROM from samfirmware.com, you'll have to go about rooting and installing Clockwork mod again. Hope this helps.
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?
So today i decided to change my stock recovery into TWRP. Somehow managed to come across a one-click twrp installer.
After i tried that, everything went downhill. Tried to wipe cache/ dalvik to try out faux kernel.
it just stood at formatting cache for a long time and didn't budge.
after 15 mins or so, i held on the power button and restarted my phone that way.
Now nothing seems to work, no service, google play crashing, and more importantly my storage isn't being detected so i can't even push files around.
Whats something i can do? im confused and stressed its 4am here
AndroidKills said:
So today i decided to change my stock recovery into TWRP. Somehow managed to come across a one-click twrp installer.
After i tried that, everything went downhill. Tried to wipe cache/ dalvik to try out faux kernel.
it just stood at formatting cache for a long time and didn't budge.
after 15 mins or so, i held on the power button and restarted my phone that way.
Now nothing seems to work, no service, google play crashing, and more importantly my storage isn't being detected so i can't even push files around.
Whats something i can do? im confused and stressed its 4am here
Click to expand...
Click to collapse
I would recommend to flash the stock image to get the phone running again and not use toolkits anymore.
Look here for how to flash a factory image: http://forum.xda-developers.com/showthread.php?t=2513701.
gee2012 said:
I would recommend to flash the stock image to get the phone running again and not use toolkits anymore.
Look here to flash a factory image: http://forum.xda-developers.com/showthread.php?t=2513701.
Click to expand...
Click to collapse
yeah i figured i should flash stock back, but the problem is trying to push the file or something. but ill look into that link asap!
thanks for the quick response
You'd probably do best to start from the top by reflashing the stock image... http://forum.xda-developers.com/showthread.php?t=2513701
This time don't use any toolkits or canned scripts, learn how to do each step by yourself, get familiar with all the commands, and do it yourself. You're less likely to screw anything up that way.
AndroidKills said:
So today i decided to change my stock recovery into TWRP. Somehow managed to come across a one-click twrp installer.
After i tried that, everything went downhill. Tried to wipe cache/ dalvik to try out faux kernel.
it just stood at formatting cache for a long time and didn't budge.
after 15 mins or so, i held on the power button and restarted my phone that way.
Now nothing seems to work, no service, google play crashing, and more importantly my storage isn't being detected so i can't even push files around.
Whats something i can do? im confused and stressed its 4am here
Click to expand...
Click to collapse
I had the exactly same situation before. What I did was a factory reset by using the wiping function in TWRP, Then you get a freshly-new system. Hopefully you have backed up your data.
Guys stop flashing the cache it really isn't needed and causes issues... I haven't done it since Android 4.3 and not had one problem
Sent from my Nexus 5 using Tapatalk