I'm at wit's end here. My TF101 will not stop rebooting. it doesn't matter what firmware I have on it (stock rooted, stock UNrooted, CM9, Frozn). it just reboots. the majority of the time it goes into a boot loop, or, if I'm lucky, I'll actually get to the homescreen for about five seconds, then it reboots. I just tried flashing the stock rom again. can't even get to the welcome screen now. I Never had this problem until I downloaded a firmware update (for stock ROM)
Using Rogue XM Recovery 1.5.0 (cwm doesn't want to work, for some reason)
S/n: C10KAS158799
When you flash between firmware, are you wiping cache, Davlik and doing a factory reset?
Go back to stock using easyflasher. It'll wipe your device clean, so make sure to back up important data. Then start over. I suggest Fred's guide over at transformeforums, it's the most complete one out there.
frederuco said:
When you flash between firmware, are you wiping cache, Davlik and doing a factory reset?
Click to expand...
Click to collapse
Tried that. Still boot-looping. nothing I do seems to help. so far, I've had the most luck with Frozn. CM9 nor the Stock asus firmware seem to work at all anymore. apparently the recovery is borked too. anytime i try to wipe something, It freezes.
am I just SOL?
(edit) alright, so I tried it again. instead of boot-looping, now it just sits at the Eee pad screen forever
I would try using TWRP instead of Rogue. Never had an issue with Rogue myself, but TWRP is better IMO.
You can use EasyFlasher to push it in APX mode, or use ADB shell and push it using the dd command (see the terminal method here: http://www.teamw.in/project/twrp2/109)
frederuco said:
I would try using TWRP instead of Rogue. Never had an issue with Rogue myself, but TWRP is better IMO.
You can use EasyFlasher to push it in APX mode, or use ADB shell and push it using the dd command)
Click to expand...
Click to collapse
Treid TWRP. wiped everything (Dalvik, System, factory reset, Cache) and flashed stock rom. still rebooting.
Des0late Law said:
Treid TWRP. wiped everything (Dalvik, System, factory reset, Cache) and flashed stock rom. still rebooting.
Click to expand...
Click to collapse
Did flashing the stock ROM replace TWRP? It should have...
frederuco said:
Did flashing the stock ROM replace TWRP? It should have...
Click to expand...
Click to collapse
It did. Now I can actually get into the OS for awhile, but it still reboots randomly (and bootloops, although not as often). I've been doing some googling. apparently the reboot/bootloop problem Is ICS based (or so some think) and, to be honest, I didn't have any problems with it before I updated from Honeycomb. that being said, someone wouldn't happen to have a spare honeycomb ROM lying around, would they? google (oddly enough) turned up nothing, and Android Revolution just leads to dead links...
Edit: never mind, someone fixed the links. will try 3.2 after I get home from work.
IMO if you are getting RR and SOD on a fresh stock install with nothing installed, it is probably a hardware issue with a failing chip on one of the boards. If it is still under warranty you may want to try to return it for repair.
Well, I haven't had the SoD issue, just reboots. I was able to use it most of the day yesterday, before I shut it off myself. It turned on fine this morning, too (rebooted once).
Sent from my LGL75C using xda app-developers app
frederuco said:
IMO if you are getting RR and SOD on a fresh stock install with nothing installed, it is probably a hardware issue with a failing chip on one of the boards. If it is still under warranty you may want to try to return it for repair.
Click to expand...
Click to collapse
Alright. So, I flashed it back to Honeycomb. Haven't had a reset or reboot all weekend. I guess the problem WAS ICS-based. Can't figure why, though.
only downside to that is, can't use some apps on the market. oh well, I'll live!
Related
I only installed the software cwm recovery (not nvflash), so I have no way out now. I haven't done anything serious except flash paul's patch and use titanium to uninstall some crapware like qik, that reader software, polaris office, etc.. nothing OS related, just apps. I also removed the GPS software, so I don't know what killed it exactly.
After removing those apps with TB, everything ran fine except I kept getting a force close from Qik... so I rebooted. Now it doesn't load and freezes on the LG screen with the loading bar not moving.
I don't know of any other options at this point...
Load up nvflash and get CWM on there so you can vol down + power into it. Then wipe data/cache and reboot.
You're not bricked even tho you think you are
GideonX said:
Load up nvflash and get CWM on there so you can vol down + power into it. Then wipe data/cache and reboot.
You're not bricked even tho you think you are
Click to expand...
Click to collapse
brick means HARDWARE LOCK or SOFTWARE LOCK
if your screen turns on at all... there is hope
fallow gideonx instructions... they have a nice tut set up for Nvflash
plus a one click type thing in the development section
I'm bricked for the time being until I can get home. I'm locked out of the device manager here at work, so I can't install the nvflash driver. Ignorant sons o'....
Sometimes I really hate the IT department.
Hopefully this is a warning to everyone else that if they want a custom recovery, they should bypass the rom manager option as it's too dangerious and just do the nvflash option.
For now nvflash is a better option instead of RM.
So I got home and used nvflash to put the latest cwm recovery on it. I wiped cache and rebooted... it shutdown the phone instead. So I manually turned it back on and it did the same thing.
So I did a full wipe and flashed a rom... and now it bootloops. I may very well have a bricked device after all.
Flashed which rom?
Here's a nandroid restore you can use:
http://forum.xda-developers.com/showthread.php?t=1048274
Eagles Blood since it was the fastest available.
The stock backup image is taking a long time thanks to the slow download. It's really irritating when all I can get on my 20mbps connection is 64KB/s.
antoniouslj said:
Eagles Blood since it was the fastest available.
The stock backup image is taking a long time thanks to the slow download. It's really irritating when all I can get on my 20mbps connection is 64KB/s.
Click to expand...
Click to collapse
I'd do the nandroid restore if I were you...
antoniouslj said:
Hopefully this is a warning to everyone else that if they want a custom recovery, they should bypass the rom manager option as it's too dangerious and just do the nvflash option.
Click to expand...
Click to collapse
noone will heed that warning lol.
Not a brick bro...just a minor bump in the road..you will get wiser from this..
G2X
fcisco13 said:
Not a brick bro...just a minor bump in the road..you will get wiser from this..
G2X
Click to expand...
Click to collapse
Actually it is completely gone now... seems like I have a defective device.
It won't boot into recovery or anything for that matter now, it just freezes at the first LG screen (the one without the progress bar). What's even weirder is I haven't really done anything to it... just installed and ran apps/games. I shut it down so I could install CM, but it won't boot into recovery or anything.
I tried redoing nvflash and it went fine, but it still won't boot into recovery.
This really sucks too... right on the eve of CM for this thing.
Ok I will try to explain this.
If I do the software reset and reboot it comes back on and nothing happens as in nothing gets wiped or reset, nothing changes.
If I do a factory reset it reboots and nothing changes all apps settings even browser history is still there.
If I plug xoom into pc and try to erase storage part of it which windows shows it is and reboot everything comes right back.
I have tried loading the stock img files with fastboot(yes I unlocked it first).
I have even tried a custom rom with a different recovery and after a reboot it is right back the way I left it before I tried anything, no custom rom no custom recovery.
While using the tablet, if I try unistalling an app or several then rebooting it comes back as if I did nothing.
If I install an app it installs then try and use it and it force closes.
I am on 4.04 and IMM76.
It makes no difference what I do to it, after a reboot it goes back to the same stuff that was on there, no changes at all.
Thanks
try to delete everything in sdcard. not external, internal
There is not an sd card in it right now.
Can't you try reflashing your device? Maybe works... I mean the official firmware found on Motodev site.. you can try Stock Install feature of LordAIOTool Linux version (and Linux only! Windows is outdated!) Good luck!
Sent from my 3G Xoom using XDA HD - 1st Xoom Recognized Contributor
I have the same issue
XxLordxX said:
Can't you try reflashing your device? Maybe works... I mean the official firmware found on Motodev site.. you can try Stock Install feature of LordAIOTool Linux version (and Linux only! Windows is outdated!) Good luck!
Sent from my 3G Xoom using XDA HD - 1st Xoom Recognized Contributor
Click to expand...
Click to collapse
I have the same issue as well. Reflashing doesn't do anything because it just reverts back to how it was. It is as if the Xoom is stuck in time
I even contacted Motorola and they had no clue, and I can't get it repaired because it is out of warranty and there is no way I would pay $150 to get it repaired.
Hello, I've got a problem and I'd be very happy for any advice.
I am on rom JellyBean AOSP. I was using my Transformer and sound stopped working. So I decided to turn it off and on again and when I tried to turn it on and I wasn't able to start tablet anymore. I'm stuck on the first screen you see when you turn on the tablet. So I wanted to do factory reset in the recovery. In recovery everything works allright. When I click on the factory reset it says error when deleting something in /data/ and I also can't do "Format /data/" because of the same error.
Here is the log from recovery - https://dl.dropbox.com/u/3045404/recovery.log
How can I completely delete /data/ can I do it somehow from PC for example? I don't care about my data I can lose everything. I just want to get it work. I also tried to flash AOSP JellyBean ROM again, but with the same effect. I think that tablet just can't do the factory reset but I don't know why. Thanks for any advice.
Hi there !
I think you should try to start your tablet into ADB mode, connect it to your computer and use the "adb shell" command. If your tablet was rooted, then you might be able to use the "su" command, but that depends also on your settings (I mean your Android settings... those you can't change anymore ).
Another way to get your TF101 working again is to use the NVflash "unbrick pack". OK, you'll be running the stock non-rooted ROM, but you'll be able to root it again and install a new fresh copy of your Android AOSP. I'm going to search for a link to this nvflash and I'll post it asap.
By the way, were you using the AOSP "alpha" from RaymanFX ?
EDIT : NVflash unbrick pack is here, and you also might want to try with EasyFlasher !
Thanks, I'll try it. Yes, I've been using alpha from RaymanFX. I haven't done anything that could "brick" my device while using the tablet before I turned it off.
This is what tablet shows after I attempt to do a factory reset. https://dl.dropbox.com/u/3045404/DSC05813.JPG
GameEs said:
This is what tablet shows after I attempt to do a factory reset.
Click to expand...
Click to collapse
That's weird. And you're using an old CWM Recovery
I think in most CWM versions there's a "fix permissions" item, you could try this one first. Im' not sure of what it exactly does, but it might do the trick: a permission-related problem seems (to me) a good reason for displaying this kind of errors...
yeah I also tried fix permissions but didn't help. I also remembered that it sometimes freezes even in the recovery. Is it safe to flash a new recovery NOW when I'm not able to startup the tablet? Please could you link me to the best recovery that I should flash? thanks a lot. I'm careful about it and I don't want to do something that would brick my device.
I dunno if it is the best recovery, but I prefer to use the CWM Recovery.
You'll find the 6.x series here.
I actually use the 6.x on my Sony Xperia Ray.
On my TF101, I use this touch Rogue recovery, not as recent as the first one. In fact I never did the update 'cause I'm waiting for the next release of RaymanFX's CM10 release to flash everything
EDIT: And I think you can flash a new recovery safely, because it's not on the same partition as the Android system. And in the case it fails, you should be able to boot in ADB mode and use the NVflash unbrick pack to get your device up and running !
oh god thank you so much. New recovery helped a lot it did factory reset and everything works allright. I would like to ask you one more question. what's in your opinion best rom for Transformer? I just want it to be stable. Because I don't like freezing every day and slow motion through tablet. I tried many roms but it was always unreliable. Thank you )
Great !
About the ROM s, one told me that Revolver is a great one, but I never used it.
I never had problems with CyanogenMod 9. I would recommend that one !
For now I'm running RaymanFX's CM10 build, which is great too !
Sent from my Transformer using xda premium
i've been using CWM recovery and CM nightlies. they've been just fine. today i restored a two day old backup, as i didn't care for the current nightly.
now the phone black screens after the samsung splash.
i've tried:
factory reset
wipe dalvick/cache
restoring other backups
flashing other nightlies
and the phone will boot for the first time, but if i select 'reboot' or 'power down' on the next boot it's only a samsung splash, then black screen (no cm splash, no response from buttons input), and will not boot again.
what's the problem ?
ohgood said:
i've been using CWM recovery and CM nightlies. they've been just fine. today i restored a two day old backup, as i didn't care for the current nightly.
now the phone black screens after the samsung splash.
i've tried:
factory reset
wipe dalvick/cache
restoring other backups
flashing other nightlies
and the phone will boot for the first time, but if i select 'reboot' or 'power down' on the next boot it's only a samsung splash, then black screen (no cm splash, no response from buttons input), and will not boot again.
what's the problem ?
Click to expand...
Click to collapse
Happens once in a while when you flash over a back up.
Try making a clean flash.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Somcom3X said:
Happens once in a while when you flash over a back up.
Try making a clean flash.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Click to expand...
Click to collapse
i've done that. right now, i've wiped everything, and then flashed a nightly, and it will not reboot !
it will only boot the -one- time directly after flashing a new rom. any reboot attempts after that means it freezes, or fails, with a black screen directly after the samsung splash.
what have i missed ?
ohgood said:
i've done that. right now, i've wiped everything, and then flashed a nightly, and it will not reboot !
it will only boot the -one- time directly after flashing a new rom. any reboot attempts after that means it freezes, or fails, with a black screen directly after the samsung splash.
what have i missed ?
Click to expand...
Click to collapse
Try installing Samsung firmware via Odin. Root it and try again. Wouldn't hurt to try.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Somcom3X said:
Try installing Samsung firmware via Odin. Root it and try again. Wouldn't hurt to try.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Click to expand...
Click to collapse
could you point me to a specific samsung firmware, or is there only one ?
ohgood said:
could you point me to a specific samsung firmware, or is there only one ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=24660137
Make sure repartition is always unchecked in Odin
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
ohgood said:
could you point me to a specific samsung firmware, or is there only one ?
Click to expand...
Click to collapse
Check out this post from the brick fix thread.
http://forum.xda-developers.com/showpost.php?p=44626072&postcount=117
The full fix thread
http://forum.xda-developers.com/showthread.php?t=1591601
Sniped lol
i've wiped everything. flashed back to stock via odin, rooted, just like always.
i've even wiped in between.
after the FIRST clean boot, there is no rebooting. all it does is continue to hang after the samsung splash. no cyanogenmod, no stock rom, no nothing, nothing will boot the SECOND TIME.
i really don't understand this.
i'm using CWM recovery 5.5.0.4, cm-nightly 10-05, and it just don't think it's going to work properly again. it's a real shame, cause i really like the size, weight, and speed of this phone. but if it won't boot, i can't use it.
if anyone has any tips, i'll try them. at this point i really don't mind destroying it, and it might make me feel better to do so.
i meant to add, it doesn't matter if i use a backup, flash a fresh new rom, or use stock. the first boot works fine, but all boots after that wether from powering down or selecting 'reboot' fail.
maybe this part will help -
if i wipe the phone completely, it will boot. let's call this boot 1.
i can setup the phone, or change nothing in settings, doesn't appear to matter, and choose 'power down' or 'reboot'. let's call this reboot 1.
the next time i power on the phone, black screen. no CM splash, nothing. i guess we'll call this hang 1 ?
ideas ?
ohgood said:
i've wiped everything. flashed back to stock via odin, rooted, just like always.
i've even wiped in between.
after the FIRST clean boot, there is no rebooting. all it does is continue to hang after the samsung splash. no cyanogenmod, no stock rom, no nothing, nothing will boot the SECOND TIME.
i really don't understand this.
i'm using CWM recovery 5.5.0.4, cm-nightly 10-05, and it just don't think it's going to work properly again. it's a real shame, cause i really like the size, weight, and speed of this phone. but if it won't boot, i can't use it.
if anyone has any tips, i'll try them. at this point i really don't mind destroying it, and it might make me feel better to do so.
.
i meant to add, it doesn't matter if i use a backup, flash a fresh new rom, or use stock. the first boot works fine, but all boots after that wether from powering down or selecting 'reboot' fail.
Click to expand...
Click to collapse
The October nightlies are cm10.2 right? Your using the old recovery, that's the issue. And there are newer nightlies.
New recoveries
http://forum.xda-developers.com/showthread.php?t=2475802
Cm thread
http://forum.xda-developers.com/showthread.php?t=2459198
Romman0 said:
The October nightlies are cm10.2 right? Your using the old recovery, that's the issue. And there are newer nightlies.
New recoveries
http://forum.xda-developers.com/showthread.php?t=2475802
Cm thread
http://forum.xda-developers.com/showthread.php?t=2459198
Click to expand...
Click to collapse
yes, they're fairly recent nightlies. i skipped back to the 10-5 nightly as i thought that might ahve been part of the problem. since you're pointing to my recovery being an older version, i'll update it. thanks for the clue stick !
Romman0 said:
The October nightlies are cm10.2 right? Your using the old recovery, that's the issue. And there are newer nightlies.
New recoveries
http://forum.xda-developers.com/showthread.php?t=2475802
Cm thread
http://forum.xda-developers.com/showthread.php?t=2459198
Click to expand...
Click to collapse
hey thank you for that. i've removed the old cwm recovery, flashed new, lots of other flashes, and it finally works again. now to dig up a non-corrupted backup and hopefully be back to working.
thanks button was used
well, after all of that i'm going to roll with cm-10.0, cwm 6.xomething, so i can have a working compass on oruxmaps.
i won't be updating until 10.x begins to support compass functions again.
see yall then !
ohgood said:
well, after all of that i'm going to roll with cm-10.0, cwm 6.xomething, so i can have a working compass on oruxmaps.
i won't be updating until 10.x begins to support compass functions again.
see yall then !
Click to expand...
Click to collapse
Make sure you use the latest cm10 nightly, as the old stable one is a lot less "stable" than the name suggests, and is lacking features
Romman0 said:
Make sure you use the latest cm10 nightly, as the old stable one is a lot less "stable" than the name suggests, and is lacking features
Click to expand...
Click to collapse
thanks for the tip !
i finally got all the corrupted files (or whatever was causing problems) rm'd from both the phone and sdcard.
as of yesterday i had CM-10.o + CWM 6.0.3.8 and gapps 2012-8 (i think) working nicely on the phone. backed up a nandroid of all of it two times, and restored them to make sure restores were working. yes, everything fine.
as of today, i have CM-10.2 (latest nightly) + CMW 6.0.3.8 and gapps (current) working nicely on the phone. backed CURRENT up nandroid on sdcard, and restored a few times to make sure. yes, working fine.
seems it was
A) corrupted files/filessystems
and/or
B) too old a clockworkmod recovery
C) unstable CM version( s )
but now all is fine. thanks to all that helped !
I just rooted last night and everything was good... This morning all I did was freeze some of the stock Verizon apps, and the system crashed. Now when it reboots, it's stuck at the Verizon screen. I can access Bootloader/Recovery, and have tried "fastboot erase cache" but that hasn't fixed it. If I let it sit, I can hear notifications and stuff in the background (I also have MightyText installed, and can send/receive texts via that), so Android is running in the background - it's just "stuck" on this Verizon screen. I'd really rather not have to do a factory reset, since I just spent last night getting everything set back up from the root process.
Any suggestions? Please help!
Uncertain. Just a shot in the dark but which recovery do you have? Have you tried doing a "fix permissions" within it?
Drunkula said:
Uncertain. Just a shot in the dark but which recovery do you have? Have you tried doing a "fix permissions" within it?
Click to expand...
Click to collapse
TWRP. Just did that now, no changes.
You may have froze something you shouldn't have. At this point, I'd personally do a full wipe and reflash the ROM. If not on a ROM and on the stock RUU ROM. I would:
1) consider flashing a stock based ROM:
This ROM is 100% stock based off RUU -
http://forum.xda-developers.com/ver...-4-17-605-9-stock-resources-firmware-t3196906
2) run RUU again, and freeze one app at a time to narrow down what may have caused this.
3) you can try a wipe of just cache/dalvik cache
andybones said:
You may have froze something you shouldn't have. At this point, I'd personally do a full wipe and reflash the ROM. If not on a ROM and on the stock RUU ROM. I would:
1) consider flashing a stock based ROM:
This ROM is 100% stock based off RUU -
http://forum.xda-developers.com/ver...-4-17-605-9-stock-resources-firmware-t3196906
2) run RUU again, and freeze one app at a time to narrow down what may have caused this.
3) you can try a wipe of just cache/dalvik cache
Click to expand...
Click to collapse
Thanks, yeah I just wiped and flashed a ROM. I needed my phone running in the next two hours, and didn't have the time to investigate. Hopefully it doesn't happen again.
dajoip said:
Thanks, yeah I just wiped and flashed a ROM. I needed my phone running in the next two hours, and didn't have the time to investigate. Hopefully it doesn't happen again.
Click to expand...
Click to collapse
Next time when you're cleaning out Verizon bloat, don't take out anything that you're not sure of.
Leave in there: VZWAPN and vzwdummylibs if you dump any Verizon apps.
Besides being able to start the phone, it's got to be able to send and receive calls. I have learned this thru bad decisions and their results.....