Related
Hey guys I was having some problems with my xoom's wifi on Tiamat's 1.4.4 so i decided to relock the device and use stock.
It's a US model and had build HMJ37 but i decided to follow this thread
http://www.xoomforums.com/forum/mot...4600-thinking-about-unrooting-read-first.html
I downloaded img build HRI66 and followed all the steps and it was ok. Then, i rebooted and now my device is at the motorola logo's dual core screen. Everytime i manually reboot with power and volume up it automatically reboots the device instead of shutting it down, it literally won't shut down and keeps hanging at the moto logo. It just keeps rebooting and getting stuck at the motorola logo. I then unlocked again, and performed the same process with the HRI39 img and still got the same problem
So im stuck. Please help me out guys, i'm in serious ****.
So you have gone as far as the "fastboot erase cache" and "fastboot oem lock" right? This is kind of funny because I tried to install Tiamat 1.1 ROM tonight and ended up going through this HUGE loop of problems.
Here's the problem I had: some time ago I installed ROMManager from the market. I thought it would be easier. It SHOULD be easier. I let it update my recovery to its own version 4.something. It allowed me to SORT OF install the ROM, but I wound up with some persistent system files that weren't getting wiped and a bcm4329.ko version mismatch.
This stumped me for a long time because all I could see was an "Error" message where I was supposed to be able to toggle the wifi on and off. I tried rolling back to my previous ROM. No go. And the culprit the whole time was ROMManager's CWM.
I tried rolling back my recovery.img file to the Tiamat version recommended in this forum. I kept getting all of these crazy "could not mount" errors for pretty much EVERYTHING. I thought my recovery partition was effed. So I rolled back to stock. Followed pretty much the same instructions you linked to.
From there I was able to boot into the stock OS. WiFi worked. I breathed deeply for a minute or two then dove right back in.
If I was in your position I would (and I did, though not from a boot loop) boot into fastboot and unlock the bootloader again. You can do it by holding the Vol down key as the device boots. When fastboot loads type "fastboot oem unlock". Press the Vol down key then the Vol up key. Do that again. Your device is unlocked now! Hooray!
Now you need to install a recovery.img. (I just did this too.) Get the .img file here: http://forum.xda-developers.com/showthread.php?t=1074979
Boot into fastboot again. Put the recovery img file you downloaded into the same directory as your adb and fastboot executables (if you haven't already linked to them in your PATH). Type "fastboot flash recovery recovery-lotsofstuffhere.img". Type "fastboot reboot". 2 seconds after the Motorola logo pops up press the Vol Down key. Then press the Vol Up key to enter recovery.
Ok, here's where I found out what a dumbass I was. I got all of the stupid "can't mount anything" errors again. I thought, HOLY ****. I just did all of that work, spent hours troubleshooting and reformatting and bringing it back to stock and flashing the custom recovery all over again just to run into the SAME error. I really thought I was screwed. Then I found some forum where a guy was complaining about the same error. He realized he was getting it because his sd card was half-way out. I thought - "SD CARD?!?" Some guys told me I needed one earlier too, but the ROMManager CWM didn't require it. It just screwed up my system files. So I popped one in and rebooted. Voila. Everything's kosher. If YOU have the same problem, make sure you've got an SD card in.
Ok, so now you're in recovery. You'll need to flash an OS of course. If you haven't already got it, get Tiamat 1.1 rom. Put it on the sd card. Wipe data/factory reset. Install zip from sd card. You're golden. At least I was. 5 hours later.
-Mike
Hey Mike I'm gonna give this a go. Just when i downloaded the img file to flash through fastboot i got an error saying battery was too lower to perform the recovery....damn it! The xoom isn't able to charge at the moment so i have to wait until it dies i guess (or i hope at least) and then charge it up and try again later.
Thanks again dude, hope i sort this out too. I'll download tiamat 1.1 in the meantime.
DUDE YOU'RE MY ****ING HERO!!!! I got it running can't say if everything is 100% just yet but the fac tthat im back in is enough to thank you so very much Mike!!! What a guy!
It worked? Great that's excellent news. Just out of curiosity - did you get there because you had ROMManager's ClockWorkMod? Or maybe you didn't do a full wipe before flashing a new rom? Or maybe you restored some WiFi settings with Titanium Backup after a new flash? How did you wind up with tthe problem in the first place - you know, for posterity.
well to be honest i am not 100% sure. I think the source of the problem msut have come from my previous installation of tiamat's 1.4.4 rom, it was always actin up on me and i don't believe i wiped the mod before i updated it and that may have done it. I wish i could give you more than just a pseudo answer.
DeeJayCruiser said:
Hey Mike I'm gonna give this a go. Just when i downloaded the img file to flash through fastboot i got an error saying battery was too lower to perform the recovery....damn it! The xoom isn't able to charge at the moment so i have to wait until it dies i guess (or i hope at least) and then charge it up and try again later.
Thanks again dude, hope i sort this out too. I'll download tiamat 1.1 in the meantime.
Click to expand...
Click to collapse
This is why they say to make sure you're plugged in when doing this important stuff, lol.
okantomi said:
This is why they say to make sure you're plugged in when doing this important stuff, lol.
Click to expand...
Click to collapse
Normally, I'd agree but in this rare case, he actually needed it to fully drain because he couldn't get it to power off using any normal method. Weird! so, it seems his only shot was to let it die to finally kill the screen and then start over. Very odd...
From original post
DeeJayCruiser said:
Everytime i manually reboot with power and volume up it automatically reboots the device instead of shutting it down, it literally won't shut down and keeps hanging at the moto logo.
Click to expand...
Click to collapse
farmsatguy said:
Normally, I'd agree but in this rare case, he actually needed it to fully drain because he couldn't get it to power off using any normal method. Weird! so, it seems his only shot was to let it die to finally kill the screen and then start over. Very odd...
From original post
Click to expand...
Click to collapse
You are right...I had forgotten that from the OP. Very strange indeed.
Yeah I dunno why, my xoom was just acting up. It's fantastic now, albeit the wifi still has a couple kinks but android market issues have been resolved, i get much better streams and with tiamat 1.1 everything is already built in and with a quickboot option =)
Xda...where would i be without you!
farmsatguy said:
Normally, I'd agree but in this rare case, he actually needed it to fully drain because he couldn't get it to power off using any normal method. Weird! so, it seems his only shot was to let it die to finally kill the screen and then start over. Very odd...
From original post
Click to expand...
Click to collapse
You should be able to reboot the device using vol up + power, then holding vol down and vol up until it says "Cold booting Linux.....".
This should do the same as letting the battery drain, plugging it in and turning it on.
DeeJay - dunno if you've done this already, but if you haven't you should go back to the Tiamat 1.1 thread and find the Modpack. It fixes the Market update issue and gives you built-in screenshot capabilities and an option to reboot into recovery from the power off menu. It's in there - you just have to scroll down a bit before you find it.
Also - what issues are you having with WiFi?
Thanks for that important tidbit, solarnz. I'm going to file it away for future use.
OMG!!!! Dude you just saved my life! I thought my baby was out the window. I had the exact same problem as you did. I was trying everything from every thread that had anything to do with this problem. I just finished installing and it booted. WHEWWW!!!
Thank u thank u thank u!!
Glad it helped. I'm seeing all kinds of posts in here about the ROMManager CWM. Not good.
Sent from my Xoom using Tapatalk
Hello everyone,
First i know this is the general Q&A but since i do not post often [ever] i can't post directly to the development forum for the Prime [ROM]
My Transformer is a B6 model
So here is my issue, I installed Prime about 4 days ago was working fine no problems, and just today (silly of me) i realized that the time zone for the table was at default (don't remember what it was) i think UTC - 0, in any case i went ahead and changed that to Eastern didn't install anything new other the amazon market app.
In any case the table was working fine but as soon as it went to sleep it got locked into a rebooting mode it will perform the mem check and POST, it completes initialization but when it reaches "Activating root access..." it reboots and the cycle repeats.
I can obviously re-flash it and get back to working order but is a rather a unusual error, by the way i do have APX access.
Any ideas?
Thank you very much
Cheers for posting in the correct section dude. You have a problem, you are asking a question.
Thanks for not cluttering up the DEV threads with this.
Have you tried a cold boot?
Also, boot into CWM and clear the caches
Still havin probs? then reinstall the rom and see what happens
Cheers
CaNsA
XRACER said:
Hello everyone,
First i know this is the general Q&A but since i do not post often [ever] i can't post directly to the development forum for the Prime [ROM]
My Transformer is a B6 model
So here is my issue, I installed Prime about 4 days ago was working fine no problems, and just today (silly of me) i realized that the time zone for the table was at default (don't remember what it was) i think UTC - 0, in any case i went ahead and changed that to Eastern didn't install anything new other the amazon market app.
In any case the table was working fine but as soon as it went to sleep it got locked into a rebooting mode it will perform the mem check and POST, it completes initialization but when it reaches "Activating root access..." it reboots and the cycle repeats.
I can obviously re-flash it and get back to working order but is a rather a unusual error, by the way i do have APX access.
Any ideas?
Thank you very much
Click to expand...
Click to collapse
Hi, I doubt that changing the timezone would have a negative effect on your transformer so I'm wondering if maybe something else causes this. Maybe some app that doesn't like the TZ to be changed or maybe even something completely unrelated. Can you get a logcat of the problem and it might help to shed some light on this problem you are experiencing?
you probably have a bad download. Redownload the Tom and try again.
Redownloading the Rom would be better though...oopps
Hello everyone,
thanks for the quick reply, although i am familiar with computers in general i am not very familiar with the android platform.
How do i get it if the system keeps rebooting every 5-7 seconds? or is by default created when the system reboots?
I have been reading through the android dev tools and it needs to be access via adb, i am not very familiar with this environment. Any guidance will be appreciated.
power on with power / vol - and when it says to hit vol up. Yhis will boot you into CWM. Clear dalvik and cache and reboot. If that doesnt work then just flash the rom again. If that doesnt work then wipe data.
thebadfrog said:
power on with power / vol - and when it says to hit vol up. Yhis will boot you into CWM. Clear dalvik and cache and reboot. If that doesnt work then just flash the rom again. If that doesnt work then wipe data.
Click to expand...
Click to collapse
Hello,
Thanks for the reply, i have already try, all of the above mentioned steps, except for the last one i am not really sure what you mean (If that doesnt work then wipe data)
Also i attempted to install another rom (revolver) in this case since it hides the POST procedures it just shows the eee Pad and Asus logo for about 7-10 secs and then reboots
There is an option in CWM that wipes data/factory reset. It wont wipe your personal folders or your external sdcards but it will reset the system back to the beginning and remove all your apps which you have to reinstall
thanks i also did that as a last ditch effort, yet nothing.
hmmm... i refuse to believe my tablet is bricked.
What i will try to do is restore to stock 3.1 and see if that works.
it just seems weird that it was working with no issues until i modified the TZ.
But thanks, and i will give the reset one more try.
----Update----
On a side note.
when in recovery mode i have tried the restore option, but it keeps giving me
E:Can't mount /sdcard
i do presume that is the internal memory where the recovery image is located am i right?
--------------------------Update 2--------------
So i went ahead and nvflash with stock 3.1 that got me back in to working mode, however when attempting to go into the recovery meny it seems something got messed up.
First the prime animation shows up (although i have flashed, revolver and stock on top of that)
then the android logo shows up with a warning triangle on his chest, i guess that is the typical something is wrong here logo.
and then nothing no access to recovery.
So i am trying to flash this one more time, let see if that fixes the issues.
---------------Update 3----------------
well that got me no where :S
i flashed the system with revolver 3.2 via nvflash and i am back to the rebooting loop.
I will wait to see if any of you guys have some ideas, in order to further proceed
Sorry to keep asking.
Does any one have any idea how to resolve this?
Also Roach you mention a log dump, could you please let me know how i can get this log.
thank you.
I know this doesn't help all of your problems, but people have reported having trouble with the nvflash version of Revolver. (myself included) I would recommend, because this is always what works for me when I soft-brick my tablet, nvflashing the latest version of Prime again. Assuming it boots successfully, you can always put the normal version of Revolver on your sdcard, reboot into Recovery, wipe data, and then install Revolver from there.
I hope something works for you soon
Sent from my DROIDX using Tapatalk
Well it seems that did the job.
Although weird why the issue happened in the first place, well i would like to thank everyone who replied. Next time i will keep a rom on my sdcard all the time :-D.
Also thanks XDA And all the community in here.
Sent from my transformer using XDA Premium. (Revolver ROM)
Yesterday afternoon I attempted the Bionic Path Saver update with 901 and Liberty 2.0. Due to issues with flashing the Webtop image and some flaws in the script I wound up with a dead phone. After hacking up a charger and over 12 hours of experimentation I was able to get the phone and and was able to update it. I do not want anyone to have to go through what I went through so I am posting this. I do not take credit for the files, I only came up with the combination. All download links lead to the creators. Let me know how this works out and of course always create backups before performing this.
**Things you will need**
A FULLY charged battery
My SafeBionicPathSaver_v2.rar - http://www.filesharesite.com/files/201201/1327968223SafeBionicPathSaver_v2.rar.html
RSDLite 5.5 - In this package
Motorola Drivers - In this package
flashme.zip - In this package
Liberty 2.0 (.901 OTA Compatible) - http://rootzwiki.com/topic/13096-901-radio-working-with-custom-rom/
bionicbootstrap.apk - http://droidmodderx.com/bionic/bootstrap-recovery-for-the-bionic/
**Instructions**
1.) Install RSDLite 5.5 and Motorola Drivers (32-bit or 64-bit accordingly).
2.) Extract flashme.zip to any location on your computer.
3.) Extract SafeBionicPathSaver_v2.rar (ME) files to any location on your computer.
4.) Copy bionicbootstrap.apk and copy the Liberty 2.0 (.901 OTA Compatible) ZIP to the root directory of your SD card.
5.) Connect phone to computer, set phone to USB Debugging Mode, and set it to Charge Only. You will also need to allow "Unknown sources" in your application settings.
6.) Go to the directory from Step 3 and run SBPSscript.bat. Let it run and wait for Phase 1 to complete.
7.) Phone should now be at the bootloader. Open up RSDLite and browse to the XML in the directory from Step 2. Flash this and the phone should reboot, it will take a while.
8.) The phone should now be at the Android setup screen. *The phone has been reflashed and reset, you now need to follow STEP 5 again to continue*. You may now contune following the prompts in the SBPSscript.bat script. Watch for any errors as directed. The phone should end up booted into stock recovery.
9.) At the recovery menu you are going to install updates manually. First do update893.zip, then do update901.zip. Make sure there were no errors then reboot the phone.
10.) You are now at version .901 and should still be rooted. To test root you can try and update Superuser by going to Superuser's menu and updating the binary. If it fails with a permission issue, you do not have root and have to start over.
***IF YOU WOULD LIKE TO REMAIN ON THE STOCK ROOTED .901 ROM YOU CAN STOP HERE. THE REST OF THE STEPS ARE FOR GETTING LIBERTY3 2.0 INSTALLED.***
11.) Now install bionicbootstrap.apk, open the application, and press the "Bootstrap Recovery" button (grant any SU access). This will install the Clockwork Recovery ROM and would fail if you were not still rooted.
12.) Now click the "Reboot Recovery" button. You will now be in the Clockwork Recovery Mod.
13.) At this menu you will need to wipe data, cache, dalvik cache, and format /system.
14.) Now you will select "install zip from sdcard" using the volume and power buttons and choose the Liberty ZIP you uploaded in Step 6.
15.) After this is done you can reboot the phone and you will have a Liberty3 2.0 / .901 Radio Bionic!
-Mark DePalma | MNetwork
I will be trying this later tonight. I'm hoping it goes well and I'll be sure to let you know. Thanks for taking the time to make the write-up. If it works properly, it's exactly what I've been looking for.
utcu said:
I will be trying this later tonight. I'm hoping it goes well and I'll be sure to let you know. Thanks for taking the time to make the write-up. If it works properly, it's exactly what I've been looking for.
Click to expand...
Click to collapse
You're welcome, a user just notified me of a typo "fixme = flashme" and I have updated that in my ZIP and in the post. The same user also told me that the flashme.zip file isn't available for download at the moment. I would host it myself, but I know that within 30 minutes my pipe would be saturated. Hopefully this link comes back up soon, if not I will find a way to host it somewhere.
utcu said:
I will be trying this later tonight. I'm hoping it goes well and I'll be sure to let you know. Thanks for taking the time to make the write-up. If it works properly, it's exactly what I've been looking for.
Click to expand...
Click to collapse
Worked like a charm. Greatly appreciated. Nothing like being on Liberty with 901.
utcu said:
Worked like a charm. Greatly appreciated. Nothing like being on Liberty with 901.
Click to expand...
Click to collapse
Great! Good to hear. I have updated the post with a 2nd link to download the flashme.zip file since that went down last night. Very happy XDA is finally back online.
can this be used to go back to 5.5.839 from .901?
waffleb051 said:
can this be used to go back to 5.5.839 from .901?
Click to expand...
Click to collapse
I believe you can, but you MAY have to flash a .901 CDT image after you flash back to .839. I came back from a failed root attempt on .901, but I was also playing with different CDTs. If you try it out you can definately get it working, may or may not have to flash that .901 CDT.
I haven't able to have any success with this. I tried it twice but it keeps hanging on the Motorola screen. This is after I flash flashme (step 9) and when it goes to reboot. I've waited both time for 15-20 minutes but nothing. Is there something I'm missing? I have RSDLite 5.5 and Drivers 5.4
Stealth36 said:
I haven't able to have any success with this. I tried it twice but it keeps hanging on the Motorola screen. This is after I flash flashme (step 9) and when it goes to reboot. I've waited both time for 15-20 minutes but nothing. Is there something I'm missing? I have RSDLite 5.5 and Drivers 5.4
Click to expand...
Click to collapse
Well since you have rebooted you now have to manually get it into the fastboot mode. Turn the phone off, hold both volume buttons down, then hold the power button down for a second or two and the phone should enter fast loader mode. At this point you can connect it to the computer and RSDLite will see the phone and you can resume. Let me know if this works for you...
so I'm taking this doesn't work... files aren't even there
all i need is the last one... BPS_Safe_Scripts
plus there is a safe strap now... whats' going on.
Slie said:
all i need is the last one... BPS_Safe_Scripts
plus there is a safe strap now... whats' going on.
Click to expand...
Click to collapse
My web server runs on an old P2V'd box in my ESXi cluster and I've been meaning to port all my web sites over to a new web server VM, but haven't had the chance. I have to restart this VM every once in a while... I just rebooted it and the web site is back up. You can download this file now.
mnetwork said:
Well since you have rebooted you now have to manually get it into the fastboot mode. Turn the phone off, hold both volume buttons down, then hold the power button down for a second or two and the phone should enter fast loader mode. At this point you can connect it to the computer and RSDLite will see the phone and you can resume. Let me know if this works for you...
Click to expand...
Click to collapse
I went to try it again and it worked this time. It ended up on the Android welcome screen. Thanks for the script!
Stealth36 said:
I went to try it again and it worked this time. It ended up on the Android welcome screen. Thanks for the script!
Click to expand...
Click to collapse
Good to hear!
I have one more question. Right before I installed the Liberty(.901).zip my system version said 901 but after installing Liberty it now says 886. So is that telling the truth?
Stealth36 said:
I have one more question. Right before I installed the Liberty(.901).zip my system version said 901 but after installing Liberty it now says 886. So is that telling the truth?
Click to expand...
Click to collapse
I am in the same boat. I believe since the ROM is built on .886 that is what it is going to report. The radio, however, has already been updated and Liberty doesn't contain a radio and therefor would not roll it back. The version of Liberty used in here is only patched with libraries to handle the .901 radio. Since the upgrade I have not had the contant data drops and 3g/4g switching that I had before. The only time the data really drops now is when I'm going through a tunnel or something like that.
Unfortunately it seems that all of the servers for these files have been stopped or are now unavailable. Anyone got the files or a new location for the files? This situation has gotten out of control with the sites.
treefrog20012003 said:
Unfortunately it seems that all of the servers for these files have been stopped or are now unavailable. Anyone got the files or a new location for the files? This situation has gotten out of control with the sites.
Click to expand...
Click to collapse
The governement is getting out of control with the piracy protection... I can make one complete package that would be much smaller than all of them combined, but if I host it I know I will be out of bandwidth in 30 min (it would still be fairly large).
treefrog20012003 said:
Unfortunately it seems that all of the servers for these files have been stopped or are now unavailable. Anyone got the files or a new location for the files? This situation has gotten out of control with the sites.
Click to expand...
Click to collapse
Which files did you find were missing? I was able to download two of the larger ones with no problem.
The flash me zip was not available and one other file was blocked on two of the sites and on a third it called for four hours to download. I want to get off the 901 system and downgrade so I can run the ics ROM. I tried once and was bricked for 24 hours until I found the bin swap method to get back to 893 from the motorola files using rsdlite.
Sent from my DROID BIONIC using XDA App
Same Problem -- Need Help
mnetwork said:
Well since you have rebooted you now have to manually get it into the fastboot mode. Turn the phone off, hold both volume buttons down, then hold the power button down for a second or two and the phone should enter fast loader mode. At this point you can connect it to the computer and RSDLite will see the phone and you can resume. Let me know if this works for you...
Click to expand...
Click to collapse
I am running into the same problem. I have re-ran the RSDLite script, it finishes but the phone never goes to the Android Welcome Screen. It stays on the Motorola Dual Core start-up screen
Hi,
Someone gave me a Tf700t. On bootup it says unlocked, shows the Asus screen and then keeps rebooting. If I reboot and hold down the volume down arrow I get the menu with four choice ROC, Android, USB, Wipe.
When I press ROC I get the red triangle.
I've read many threads and I think this indicates its bricked and can't be recovered. I just want to confirm before I sell it for parts.
Thanks in advance for the help.
Mark
mmanis said:
Hi,
Someone gave me a Tf700t. On bootup it says unlocked, shows the Asus screen and then keeps rebooting. If I reboot and hold down the volume down arrow I get the menu with four choice ROC, Android, USB, Wipe.
When I press ROC I get the red triangle.
I've read many threads and I think this indicates its bricked and can't be recovered. I just want to confirm before I sell it for parts.
Thanks in advance for the help.
Mark
Click to expand...
Click to collapse
Actually, since you do have access to the bootloader this may be recoverable.
You have 4 icons in the BL menu, so it's a ICS bootloader. The dead Droid on his back when you select RCK is normal - it's the stock recovery not finding a valid update file.
The easiest way to try to get your tablet back to life would be to download the full Asus firmware from here: http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS Transformer Pad Infinity TF700T&p=28&s=1
Select "Android" as the OS. From the resulting list, choose the firmware for your SKU: US if you are in the USA.
If you are considering running a custom rom do yourself a favor and go for the 10.6.1.14.8 version, NOT the latest firmware 10.6.1.14.10. The .8 version can be rooted, the .10 not.
Download the .zip file, extract it ONCE, getting another zip and rename that file to: EP201_768_SDUPDATE.zip
Copy that file to a FAT32 formatted microSD (that's the factory default) and insert it into the tablet.
Boot into recovery (Power and Volume Down, then Volume Up to select RCK) and hopefully the recovery will recognize the file and start to flash it. Be patient - it'll take a while. Wait for it to reboot.
berndblb said:
Actually, since you do have access to the bootloader this may be recoverable.
You have 4 icons in the BL menu, so it's a ICS bootloader. The dead Droid on his back when you select RCK is normal - it's the stock recovery not finding a valid update file.
The easiest way to try to get your tablet back to life would be to download the full Asus firmware from here:
Select "Android" as the OS. From the resulting list, choose the firmware for your SKU: US if you are in the USA.
If you are considering running a custom rom do yourself a favor and go for the 10.6.1.14.8 version, NOT the latest firmware 10.6.1.14.10. The .8 version can be rooted, the .10 not.
Download the .zip file, extract it ONCE, getting another zip and rename that file to: EP201_768_SDUPDATE.zip
Copy that file to a FAT32 formatted microSD (that's the factory default) and insert it into the tablet.
Boot into recovery (Power and Volume Down, then Volume Up to select RCK) and hopefully the recovery will recognize the file and start to flash it. Be patient - it'll take a while. Wait for it to reboot.
Click to expand...
Click to collapse
Well that partially worked. Thanks so much!!!
It was able to flash the firmware. It rebooted 5 times before the os came up. I then shut it down. When I turned it on it goes to the Asus screen and then keeps on rebooting indefinitely. I then hit the volume up and power button to reset and then it rebooted 5 times before the OS came up. BTW I flash with 10.6.1.14.10.
Any ideas?
Thanks again,
Mark
mmanis said:
Well that partially worked. Thanks so much!!!
It was able to flash the firmware. It rebooted 5 times before the os came up. I then shut it down. When I turned it on it goes to the Asus screen and then keeps on rebooting indefinitely. I then hit the volume up and power button to reset and then it rebooted 5 times before the OS came up. BTW I flash with 10.6.1.14.10.
Any ideas?
Thanks again,
Mark
Click to expand...
Click to collapse
Hmm, still bootlooping.
Next thing I would try is to boot into the bootloader, select 'Wipe Data' with the Volume Down button, hit Volume Up execute.
And actually, before even booting back to system (that would be choosing the Android), I would reflash the firmware - just for good measure after the data wipe.
Can't wait to hear if that solves it!
So I downgraded to .8. Rooted. Was able to install TWRP. Reflashed, wiped and it still reboots multiple time before coming up. I tried to flash CyanogenMod but all I get is the spinning Cyanogen wheel. I was able to restore .8. Its not bricked anymore. Its just weird that it keeps rebooting before coming up. But at least its now consistent and will come up every time whether from power on or reset.
Thanks,
Mark
mmanis said:
So I downgraded to .8. Rooted. Was able to install TWRP. Reflashed, wiped and it still reboots multiple time before coming up. I tried to flash CyanogenMod but all I get is the spinning Cyanogen wheel. I was able to restore .8. Its not bricked anymore. Its just weird that it keeps rebooting before coming up. But at least its now consistent and will come up every time whether from power on or reset.
Thanks,
Mark
Click to expand...
Click to collapse
Great job so far! That you got TWRP installed is very good and gives you many more options. It's version 3.6.1? Have you tried to capture a logcat of the boot process?
The logcat may reveal the cause of this and then you could target the problem easier.
If you can't get a logcat my next step would be to format the data partition. Since you probably do not have that much data on it yet, this is the perfect time for that. Always a good idea when you move to a different rom and major framework change.
Go for a Wipe > Advanced > Format Data. It could be that there's something left behind from a former installation that causes the bootloop.
After the format you have to reflash the rom - or restore your .8 nandroid. Although I would go for CROMi-X 5.0.4. Love that rom. Excellent support too.
sbdags, creator of this rom, also provides a bootloader and several kernels.
I mean, if you flash a new bootloader and kernel, format data, clean install the rom and you still get bootloops, it's got to be hardware related. At least I would be out of ideas at that point.
berndblb said:
Great job so far! That you got TWRP installed is very good and gives you many more options. It's version 3.6.1? Have you tried to capture a logcat of the boot process?
The logcat may reveal the cause of this and then you could target the problem easier.
If you can't get a logcat my next step would be to format the data partition. Since you probably do not have that much data on it yet, this is the perfect time for that. Always a good idea when you move to a different rom and major framework change.
Go for a Wipe > Advanced > Format Data. It could be that there's something left behind from a former installation that causes the bootloop.
After the format you have to reflash the rom - or restore your .8 nandroid. Although I would go for CROMi-X 5.0.4. Love that rom. Excellent support too.
sbdags, creator of this rom, also provides a bootloader and several kernels.
I mean, if you flash a new bootloader and kernel, format data, clean install the rom and you still get bootloops, it's got to be hardware related. At least I would be out of ideas at that point.
Click to expand...
Click to collapse
Hi, how do you capture a logcat. FYI, I flashed with CROMi. It kept hanging on reboot. Finally it booted and worked. I shut it down and now I'm back into the endless looping boot cycle. One thing I didn't mention before when the unit is off the only way it will turn on is if I hold the power button down for 10 seconds.
Thanks,
Mark
mmanis said:
Hi, how do you capture a logcat. FYI, I flashed with CROMi. It kept hanging on reboot. Finally it booted and worked. I shut it down and now I'm back into the endless looping boot cycle. One thing I didn't mention before when the unit is off the only way it will turn on is if I hold the power button down for 10 seconds.
Thanks,
Mark
Click to expand...
Click to collapse
Did you format data?
http://forum.xda-developers.com/showthread.php?t=1378491
berndblb said:
Did you format data?
http://forum.xda-developers.com/showthread.php?t=1378491
Click to expand...
Click to collapse
Yes I formatted data. Its very weird it only will boot correctly after I re-flash or about once every 10 times.
Thanks again.
Mark
mmanis said:
Hi, how do you capture a logcat
Click to expand...
Click to collapse
This was at the top of the xda portal http://forum.xda-developers.com/showthread.php?t=2274119
best bookmark it for future reference its a really good tutorial
mmanis said:
Yes I formatted data. Its very weird it only will boot correctly after I re-flash or about once every 10 times.
Thanks again.
Mark
Click to expand...
Click to collapse
At this point only a bootloop logcat can shed light on this. Check the tutorial JTR recommended. It's truly good - thanks for the link!
Hi,
I've attached the logcat. What I did first was do a total wipe, system, data, cache and then reinstalled the rom.
Still having trouble booting once I shutdown and turn it back on.
All the help is greatly appreciated.
Thanks,
Mark
mmanis said:
Hi,
I've attached the logcat. What I did first was do a total wipe, system, data, cache and then reinstalled the rom.
Still having trouble booting once I shutdown and turn it back on.
All the help is greatly appreciated.
Thanks,
Mark
Click to expand...
Click to collapse
Great! Now we need to try to get someone's attention who can actually read and interpret the logcat - that is where my usefulness ends...
@sbdags, @_that, @JoinTheRealms to the rescue???
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
berndblb said:
Great! Now we need to try to get someone's attention who can actually read and interpret the logcat - that is where my usefulness ends...
@sbdags, @_that, @JoinTheRealms to the rescue???
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Right try booting without the microsd card in. Something is wrong with it. Also turn off the Bluetooth, what ever it is trying to connect to is adding lots of entries to the log.
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you try flashing factory images?
ryukiri said:
Did you try flashing factory images?
Click to expand...
Click to collapse
Yeah, that was what I flashed :/
If you can get into fastboot you "should" be able to flash stock images... Obviously this will revert any root and you will need to flash TWRP/CWM recovery after.
I assume you have a Windows PC with fastboot/adb setup and all drivers etc..
- Download latest "stock" hammerhead images (I cannot post links due to XDA rules... so: "developers.google.com/android/nexus/images#hammerhead"
- Extract the .tgz archive contents on your PC into a folder
- Boot the N5 into fastboot and plug USB cable from phone into your PC
- Go to the folder with the extracted files and run the "flash-all.bat" script on Windows
**Hopefully at this point your device will start to respond.. I.e, on fastboot screen, at the bottom you will see "writing" or something, as the script runs on the command window on your PC.**
If this works, you should be able to reboot once complete and then wait to see if you can get back into your phone.. then you can fastboot again and flash custom recovery, and then whatever rom.
If however you have a hardware issue (i.e, even after the above process it fails) then I am not sure what you could do... I guess ensure it has a complete charge. If you can get into fastboot and the buttons are responsive then it should not be a faulty power button.
Hope this helps :good:
Have you tried a simple factory reset? Reason I ask is it was working fine so sounds like something needs "flushing out" clear cache etc.
kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you choose the right model and firmware before you flash in WugFresh NRT?
The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.
howard bamber said:
The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.
Click to expand...
Click to collapse
Hello! I am apologize for that I didn't read the OP carefully. This happened to me once in that particulary way, but it was immediately after flashing. OP says that it happened suddenly, without reason. So now I am the one, who doesn't read, right? Sorry for that.
Regards, Zagor
Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.
kyle313 said:
Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.
Click to expand...
Click to collapse
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.
theesotericone said:
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.
Click to expand...
Click to collapse
I was actually able to relock the phone.
Luckily I called google and they're going to send me a replacement.
If anyone else has any other ideas, I'll still take them...I'd rather not be without a phone for the next week!
You won't be without a phone - they are sending a refurbish unit to you , putting a block on your credit card and waiting for you phone to arive at them. Once that happens they will release the funds.