Related
Ok so I think I've bricked my Nexus One. Everything was working perfect until I re-rooted it (to have SetCPU to work). I am now stuck at the loading animation screen (Google Nexus One "X"). It just keeps going and going and going. I've even tried loading my Nandroid backup and still does the same and won't work. Also I've wiped to factory default settings and tried to reinstall Modaco's 1.3 rom.
Someone please help me out...
Flash bacon add-on on top
bye!
So reinstall Modaco's 1.3, then install Bacon Add-On, and then reboot?
Yep That's the solution for some users
ok cool I'll give it a shot right now... I really appreciate it
ok at this moment it's still stuck on the animated screen... now I really don't know what to do...
Try flashing the stock rom
if u have the sdk installed, the run ddms. power on the phone usb connected to pc and see the log in ddms, paste-bin here
I have no idea on how to do that... I'm pretty much stuck at this point
try not flashing Modaco's Rom,
just flash CM's bacon
i think there is a confusion because Modaco's rom is in the rooting threat (made me believe you HAVE to use Modaco's superboot and then go to CM's bacon.
reality is you don't need modaco's superboot. after bootloader unlocking and flashing Amon Ra's recovery image you can go straight flashing CM's Makin' Bacon.
It seems people have been successful with CM's
maybe just go straight back to the start, check that bootloader is unlocked, flash amon ra's recovery, then flash Makin' Bacon
good luck
shmigao said:
try not flashing Modaco's Rom,
just flash CM's bacon
i think there is a confusion because Modaco's rom is in the rooting threat (made me believe you HAVE to use Modaco's superboot and then go to CM's bacon.
reality is you don't need modaco's superboot. after bootloader unlocking and flashing Amon Ra's recovery image you can go straight flashing CM's Makin' Bacon.
It seems people have been successful with CM's
maybe just go straight back to the start, check that bootloader is unlocked, flash amon ra's recovery, then flash Makin' Bacon
good luck
Click to expand...
Click to collapse
WOW, I really appreciate it and that just worked for me. Thank you to the both of you guys!
if you can get into bootloader mode (this is the lowest level mode you can boot into), you can not brick. Even more so if you can get into recovery (which is usually always possible if you can get to bootloader)
Good you found a way to get out of your situation.
Like i said in Android 101, you CAN NOT brick the phone unless you are updating SPL and Radio. All other stuff is just a minor inconvenience.
risterdid said:
WOW, I really appreciate it and that just worked for me. Thank you to the both of you guys!
Click to expand...
Click to collapse
haha, i am glad it worked! I don't even have my Nexus One in my hands (my biz trip to the States has been delayed again ), but i spend the waiting time doing my research... it's a bit like the Holiday Season, just that the gift giving day gets pushed out further and further...
glad it worked and it confirmed my research - so i can go at it with ease once i can
This is good news. OP, you should update your thread titled with the prefix [SOLVED].
ahh how'd I miss that 101 sticky... thanks for the heads up again guys.
Edited title =)
Am I bricked?
Ok, my issue is that I cant boot into bootloader or recovery (I tried booting with rollerball pushed in, booting with down volume, abd-mac reboot recovery, abd-mac reboot bootloader) and it just goes right into my OS which is crashing every few minutes, and my radio wont work. Any suggestions? If I am bricked, can I send it to HTC even though its rooted and bootloader is unlocked? I dont care if I have to pay for fixing it.
DrBlast33 said:
Ok, my issue is that I cant boot into bootloader or recovery (I tried booting with rollerball pushed in, booting with down volume, abd-mac reboot recovery, abd-mac reboot bootloader) and it just goes right into my OS which is crashing every few minutes, and my radio wont work. Any suggestions? If I am bricked, can I send it to HTC even though its rooted and bootloader is unlocked? I dont care if I have to pay for fixing it.
Click to expand...
Click to collapse
First of all, if your phone boots at all, it isn't bricked. A brick is a paperweight - it doesn't do anything. Second, this thread of 5 months old. Third, people have talked A TON about sending phones in to HTC with an unlocked bootloader, do a bit of searching.
And finally, it is very peculiar that your phone doesn't boot into bootloader or recovery. Try plugging your phone into your computer, opening your command prompt, navigate to your adb install direction, typing "adb wait-for-device reboot bootloader", and turning on your phone. Best of luck!
People should be banned for bumping 5 month old threads with posts not even related to the OP's post. Ridiculous.
@rcxquake: thanks for your suggestion. That didnt work, it just rebooted the OS. Ill keep searching for my solution and how to send to HTC if I cant find the solution.
@GldRush98: Sorry for ruining your day. I put in a google search for what I was experiencing and this was one of the top result of anyone remotely close to my issue. Yes, this is an old post, but maybe someone had this issue months ago, and had a solution I wasnt aware of.
And like I said, I found this post, although not exactly my same issue, was as related as Ive been able to find. I didn't find it so ridiculous.
If you can find my same issue on another post, then please help by pointing me to it so I can find my solution. I didn't mean to cause any issues.
Thanks
I for one am glad you posted. I don't know whether this is a solution for you or not, but I'm sometimes only able to get to the bootloader after I've had the phone off the charges, with the battery out, for some time. It varies for me between a few minutes and many minutes. It is hard to say because when I try and it doesn't work, I don't know if I've reset the time by having tried.
Anyhow, I found this thread because I'm having trouble with an N1, and one of the earlier posts may help me. Thanks for bumping the thread for my benefit.
Ok, so I ran into a VERY weird issue and was wondering if anyone else has experienced this or has a better solution then what I found.
My Nexus7 was running stock JRO03D. I had it rooted, using the Motley kernel with CWM Recovery - but outside of that, everything else was pretty stock. Anyway, I decided to upgrade to the 4.1.2 image. I pulled the one it downloaded automatically out of /cache and looked at the updater-script to see what it did. I noticed it replaced a lot, including the boot image, so I figured it would be better just to let it do everything and revert my custom stuff later. So I replaced the kernel with the stock JRO03D kernel and, using CWM, flashed the upgrade. Everything seemed to go perfect and it completed the upgrade. Prior to rebooting it, I also flashed the "unofficial" motley 4.1.2 kernel posted on XDA. I rebooted the device, and CWM warned me that 'su' needed to be fixed (how nice!) and made it suid again. It rebooted and after android "updated", everything was up and running. I confirmed in settings that it was on 4.1.2 with the custom kernel. SU was suid root as well. Perfect!
Not quite.
I decided to try rebooting into recovery to make sure CWM was still there, or flash it back if it wasn't. I opened up a terminal emulator, removed the new recovery-recovery image in /system, and did "reboot recovery". The Nexus7 rebooted, but rebooted right back into normal operation. Very weird. So I hooked it up to my computer, figuring CWM was gone, and tried to fastboot flash it back. Fastboot said it did, but I still wasn't able to reboot into recovery. I tried three different versions of CWM and even TWRP, but no dice. Every time I tried rebooting into recovery (using terminal emulator, adb shell or bootloader method) it just went right back into the normal boot process.
I spoke to some people on IRC who recommended reflashing the stock image from Google (without wiping user data). I reflashed the bootloader and then did a fastboot update <stock image>, and it said it replaced boot, recovery, system, etc. It rebooted automatically, and I tried going into stock recovery. That still did NOT work. Instead, I got a very sick looking android guy who was lying down with a red triangle with an exclamation point over him. I was a bit worried and upset at this point. I tried reflashing CWM/TWRP again, but nothing. When I did this, I no longer got the unhappy android image, but it just booted up normally.
I decided to try and doing a more thorough wipe, using fastboot to wipe cache/boot/recovery/system manually. Then I reflashed the bootloader and stock image. Still no recovery (stock or custom).
As you can imagine, I was getting even more concerned now. Especially since I was no without root and no way to get it back (since I couldn't get into recovery to flash the zip for it).
I tried every other thing I could think of to flash recovery back, but nothing worked. It wouldn't load at all.
Finally, I was about to do a complete factory reset and wipe/reflash of everything, but one last thought crossed my mind. I found the older (JRO03D) bootloader and flashed that. Reloaded bootloader and selected "Recovery". Voila, I was in TWRP Recovery Mode! (which was the last one I tried installing). I was able to reinstall my SU.zip and get everything back up and running.
SO, long story short, I'm now on 4.1.2, running the newer unofficial motley kernel and have su back. But I'm also stuck on the older 3.34 bootloader. If I try upgrading it back to 3.41, I won't be able to get into recovery.
Has this happened to anyone else? It doesn't seem like it. Is there a HW issue with my device causing this problem? I can't believe it's software related since I tried two different copies of the 3.41 image. Does anyone have any other suggestions on how I can upgrade the bootloader while keeping the ability to get into recovery mode?
Also, while everything *seems* to be working OK using 3.34, do you think it will cause other problems since I'm using 4.1.2?
Thanks.
*MOD EDIT* please don't quote the entire OP
Thanks for the bootloader info. I was in the same boat, and once I found your post, I went back to JRO03D and my recovery has returned.
Again, thanks, you F'n rule!!!
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
MetalWych said:
Thanks for the bootloader info. I was in the same boat, and once I found your post, I went back to JRO03D and my recovery has returned.
Again, thanks, you F'n rule!!!
Click to expand...
Click to collapse
No problem. I'm glad to hear that my solution above helped someone else, and also that I'm not the only one experiencing the problem. I assume you mean you only went back to the JRO03D bootloader and not the whole image, right?
What I'm most concerned about is that it seems like my N7 (and possibly yours as well) is defective. I'm not an uber-expert on Android, but I'm fairly knowledgeable. With a stock system, outside of userdata, that I reflashed multiple times from multiple sources, to have any type of recovery (stock or custom) not work is a bit upsetting. Since it works fine on the older bootloader, it definitely seems to be an issue with that. But since most people do not have the same issue, the only variable I can see being the difference is hardware.
Metallice said:
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It looked more like a warning symbol that something went very wrong then a stock recovery screen.
I've gone into stock recovery on other Android devices before, and it looked similar to CWM. There was a menu that allowed you to install "authorized" update.zip files, factory reset the device, etc. There was no menu here, just a very pissed off and sick looking android guy .
I believe I am having the same issue. Would you mind linking me to the bootloader which worked for you? Tried searching but couldn't find it. Thanks, and great post!
Sent from my SCH-I535 using xda premium
There's a big thread around here somewhere with people having the same problem as the op. Unfortunately, staying with the 3.34 bootloader is the only 'fix' I've read about. I still can't figure out why some people run into this problem and some don't. I used twrp to flash the update when it became available, and twrp continued to work afterwards.
spongers said:
I believe I am having the same issue. Would you mind linking me to the bootloader which worked for you? Tried searching but couldn't find it. Thanks, and great post!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
It took me a long time to find the old full JRO03D update, since Google only has the latest one on their page. I uploaded the bootloader out of it and you can download it here:
http://core.routed.com/bootloader-grouper-3.34.img
Reboot the Nexus7 into bootloader mode and run:
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
and then you should be able to flash recovery and get into it.
Metallice said:
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The android with the red triangle does not sound like the stock recovery, it is THE stock recovery.
Under JB 4.1.2 you do not need anymore to connect the N7 to a computer - like it had to be under JB 4.1.1 - to access the bootloader and then the recovery.
Now, pressing volume + power brings the bootloader , the up volume, one press, and then power press put the N7 to recovery. The recovery is the android with the red triangle. To enter in the recovery menu pressing power + volume up brings the menu with the following options:
i) reboot system now,
ii) apply update from ADB,
iii) wipe data/factory reset,
iiii)wipe cache partition.
Concerning specifically the OTA update for an unlock and root N7 there should be no problem during the process using stock recovery or CWM 6.0.1.0 as long as OTA Rootkeeper is set, before the installation, in order to keep root.
the fact that you were able to do volume down + power button into bootloader, then select recovery, makes me know its working. and the android guy on his back is the stock recovery... so everything is working fine. you said you flashed motley kernel, it may have something to do with that, and a few other things. you really need to understand how the N7 works, and what it will do if you do not do certain things.
what u should try is, fastboot flash recovery, then fastboot boot recovery
flash a different rom, i prefer Paul's Jr8 as its close to stock with nice little tweaks and see if your issue continues.
at the end of everything, i honestly find this more user error then device related. not everyone understands what the N7 is doing, and why.
smirkis said:
the fact that you were able to do volume down + power button into bootloader, then select recovery, makes me know its working. and the android guy on his back is the stock recovery... so everything is working fine. you said you flashed motley kernel, it may have something to do with that, and a few other things. you really need to understand how the N7 works, and what it will do if you do not do certain things.
what u should try is, fastboot flash recovery, then fastboot boot recovery
flash a different rom, i prefer Paul's Jr8 as its close to stock with nice little tweaks and see if your issue continues.
at the end of everything, i honestly find this more user error then device related. not everyone understands what the N7 is doing, and why.
Click to expand...
Click to collapse
Smirkis, my initial thought was that something went wrong in the upgrade process, possibly with the kernel like you suggested, so, as I mentioned in the OP, I flashed everything back to stock 4.1.2. I used flashboot to manually erase boot, cache, recovery and system. I then reinstalled the bootloader from Google's update tarball. I then used fastboot to update to image-nakasi-jzo54k.zip. At this point, outside of wiping sdcard, everything was stock 4.1.2.
While I will admit that I didn't realize that the dead-looking android meant stock recovery (and that's good to hear), subsequently flashing a custom recovery (CWM or TWRP) would continually fail to load it. In fact, I couldn't even boot into the recovery manually without flashing it. While using 100% stock, I attempted to flash three different versions of CWM and one version of TWRP. It claimed it updated, but I was not able to get back into recovery - either through bootloader, adb or "reboot recovery".
I know it's easy for people to always jump to the "user error" answer, but I fail to see how that is the case here. Based on your response, I don't think you actually read what I did and just jumped to the wrong conclusion, especially since I already tried your recommendation and much more. I am not running any custom ROM - everything was always stock outside of recovery, root and kernel. If you can explain your reasoning for thinking I did something wrong in all of my numerous attempts to get it working, I would appreciate it since maybe that would provide a solution. While I did attempt to use a custom kernel originally, that obviously isn't the issue if going back to stock didn't fix it.
Additionally, reverting back to the older bootloader magically fixed everything, while all other attempts failed. Subsequently reinstalling the custom kernel didn't break anything either. So if it wasn't the bootloader and something else was broken, I would assume it would be broken in both versions of the bootloader. The fact that this problem is affecting others, granted a small number, and the same solution works for them, leads me to believe that there is either a bug in the bootloader affecting some N7s or some rare HW defect causing a few of us problems.
There is a conversation about the new android update the boot-loader update and A Power management chip on the nexus 7.. It seems this chip is being changed out. The new chip functions the same as they have been using but Its not compatible with the old boot-loader . The above is the reason for the boot-loader change.. Google is aware of the troubles everyone in this thread is having . I would be looking for a new very tiny update in the near days. Just a guess im wondering if the truth is they are gearing up for the 3g version of nexus .maybe the pm chip being changed has a issue with the added radios. They did say ITS NOT A Chip upgrade but will not say why they are making the switch .
sorry i do not have a link . but everyone knows how to get to google groups ..
Happy Reading..
I just got another N7 in the mail today, gonna unlock n root it when i get off work. hopefully i end up in your situation so i can attempt to assist in resolving this. why the old bootloader works for you, and never worked for the rest of the world is beyond me. they updated it for a reason lol, i even called google the first week i got mine in july to tell them about the bootloader and they "said" they would forward that info to the development team. it took almost 3 months for them to fix it.
if the old one works for you, then use the old one. the only difference really is the fact that reboot to recovery thru bootloader actually works. if it works for you, don't upgrade.
mine on the other hand, couldn't get into recovery via bootloader. i was dieing for that upgrade, and when it came i was beyond relieved. i did a RMA this week because my first one had screen lift since the 2nd day i owned it lol, so i'll report back when i get home in an hour or so on my results.
smirkis said:
I just got another N7 in the mail today, gonna unlock n root it when i get off work. hopefully i end up in your situation so i can attempt to assist in resolving this. why the old bootloader works for you, and never worked for the rest of the world is beyond me. they updated it for a reason lol, i even called google the first week i got mine in july to tell them about the bootloader and they "said" they would forward that info to the development team. it took almost 3 months for them to fix it.
if the old one works for you, then use the old one. the only difference really is the fact that reboot to recovery thru bootloader actually works. if it works for you, don't upgrade.
mine on the other hand, couldn't get into recovery via bootloader. i was dieing for that upgrade, and when it came i was beyond relieved. i did a RMA this week because my first one had screen lift since the 2nd day i owned it lol, so i'll report back when i get home in an hour or so on my results.
Click to expand...
Click to collapse
Just to clarify, going from bootloader->recovery never worked for me either. Whenever I needed to get into recovery mode, I just opened up a terminal, su'd to root and then ran "reboot recovery", or occasionally doing it via adb. However, those methods always worked for me until I upgraded to the latest bootloader. Then, no custom recoveries would load via any method.
My Nexus7 was first generation. I actually picked it up in Sams Club the day before they were officially released. So if Google made any HW changes in the different revisions, that might explain the difference in results on 4.1.2. Though I imagine most people on XDA also picked theirs up out of the first batch, so I don't think that could be the case. What seems more likely is that there are minor hardware differences that are causing some people's to fail with the 3.41 bootloader, while most don't have that issue. It will be interesting to see if you experience the same issue on your new one though.
gunner1937 said:
Concerning specifically the OTA update for an unlock and root N7 there should be no problem during the process using stock recovery or CWM 6.0.1.0 as long as OTA Rootkeeper is set, before the installation, in order to keep root.
Click to expand...
Click to collapse
It didn't worked for me. I've tried Rootkeeper apk, but it was useless.
This was driving me crazy until I've found this topic! I've tried resetting it to original settings, using rootkeeper and traditional methods, nothing, zero!
At last, phonic saved my life, and finally I a could root my Nexus 7!
I never responded but my RMA worked as it should. but the issue has been resolved with recovery updates from the developers. the rest of the world who had issues should be good to go. I ended up selling my 16gb unit and got a 32 and it works as it should as well. are we all happy campers now?
Sent from my Nexus 7 using xda premium
I've had similar experiences where the way certain kernels install zips are packaged, the wipe custom recoveries at install. In that situation, I've never wiped anything from system, but rebooted into bootloader and fastboot boot recovery "recovery.img". Then from there install the recovery.zip. The worst is when this happens when you get flash happy away from home and the kernel doesn't work. No way to fix without a comp w/SDK. Glad you're back up and running.
(I cannot be held responsible if the aforementioned damages your device; do the research and own the process.)
I am so glad to have found this thread. This problem was beginning to drive me nuts.
I was rooted on 7.3.0 from the day I got my replacement kfhd less than a month ago. I forgot to turn off automatic updates and yesterday 7.3.1 installed and immediately I'm having problems. Some apps I had installed are gone, like No Lock and Apex Launcher (I'm almost positive that's which one I was using) for starters. I tried to reinstall No Lock since I have Nova Launcher working and I'm sick of unlocking twice. Downloaded No Lock, went into ES File Explorer to move it, and there is NOTHING in /data/app to move.
I'm almost afraid to see what other problems there are. I downloaded a root checker and it says I'm not rooted anymore. Well that explains a lot. However Google Play has hung around problem free, which you did need root for.
How should I proceed? I fried my fiancee's kfhd a month ago after I rooted it. I was attempting to install TWRP, screwed up, and bricked it. She went out and bought another tablet. I called Amazon and told them it just died for no reason so they sent a replacement which became mine. If I brick another kfhd I don't think Amazon is going to want to replace it again.
I know 7.3.1 was just sent OTA and not to everyone a few days ago (found that info on the forum somewhere) so has anyone re-rooted after getting it? What other things can I safely try?
It might seem kind of obvious but why not simply root again? I don't see any reason why it wouldn't work. I rooted my KFHD running 7.2.3 with Kindle Fire First Aide no problem. I'd imagine that 7.2.1 should be no problem. If you follow the steps in this thread it's pretty easy.
Also I should mention that it's pretty difficult to really brick your KFHD. If you get a factory cable (either make one yourself or order one from SkOrPn on here for pretty cheap) you can almost always fix any software problems. The factory cable essentially puts the KFHD in "factory" mode which lets you flash it in fastboot almost regardless of anything you've manage to damage. I messed up my KFHD pretty bad (stuck at the boot logo and would refuse to be be detected at all via usb) but with a factory cable it was super easy to fix.
MightyBraeburn said:
It might seem kind of obvious but why not simply root again? I don't see any reason why it wouldn't work. I rooted my KFHD running 7.2.3 with Kindle Fire First Aide no problem. I'd imagine that 7.2.1 should be no problem. If you follow the steps in this thread it's pretty easy.
Also I should mention that it's pretty difficult to really brick your KFHD. If you get a factory cable (either make one yourself or order one from SkOrPn on here for pretty cheap) you can almost always fix any software problems. The factory cable essentially puts the KFHD in "factory" mode which lets you flash it in fastboot almost regardless of anything you've manage to damage. I messed up my KFHD pretty bad (stuck at the boot logo and would refuse to be be detected at all via usb) but with a factory cable it was super easy to fix.
Click to expand...
Click to collapse
Rooting it again would probably work from what I know about rooting phones. I'm kinda hoping someone else has already done it so I know for certain that it's gonna work before I do it.
Maybe I have to be the person who finds out if simply rooting again fixes the issue.
Rooting again should fix the problem. I would try that first.
Worst case scenario it doesn't help and you have to do a factory restore or re-flash in which case you can simply restore a clean copy and then either disable the OTA updates or else, better yet, let it update all the way to 7.2.3 and then root the latest version.
Yeah, I think I'll give rooting it a shot. I PM'ed the guy that made the Kinology 7.3.1 ROM about rooting and then flashing recovery from where I'm at right now since I can't post in the “development" forum until I have 10 posts. He also said it should go fine from where I'm at. I'd love to flash that ROM, I'm just afraid of screwing up since I massively screwed up the first time I flashed a recovery.
I'll give it a shot tonight when I've got time to mess with it.
SGoatS said:
Yeah, I think I'll give rooting it a shot. I PM'ed the guy that made the Kinology 7.3.1 ROM about rooting and then flashing recovery from where I'm at right now since I can't post in the “development" forum until I have 10 posts. He also said it should go fine from where I'm at. I'd love to flash that ROM, I'm just afraid of screwing up since I massively screwed up the first time I flashed a recovery.
I'll give it a shot tonight when I've got time to mess with it.
Click to expand...
Click to collapse
It's not hard as long as you follow the instructions... It works flawlessly on mine.
Well I'm happy to say that rooting again after the 7.3.1 update Amazon snuck in on us went perfectly. So when others get that update and aren't sure if they can root again easily I hope they see this thread and know that it is no different than the first time you rooted.
-a- said:
It's not hard as long as you follow the instructions... It works flawlessly on mine.
Click to expand...
Click to collapse
My only concern is messing up the TWRP install. If I actually read the instructions a few times before doing it I shouldn't mess it up this time. I'm gonna look into it some more this week in my spare time and convince myself to do it. The extra encouragement of it working no problem is appreciated.
SGoatS said:
Well I'm happy to say that rooting again after the 7.3.1 update Amazon snuck in on us went perfectly. So when others get that update and aren't sure if they can root again easily I hope they see this thread and know that it is no different than the first time you rooted.
My only concern is messing up the TWRP install. If I actually read the instructions a few times before doing it I shouldn't mess it up this time. I'm gonna look into it some more this week in my spare time and convince myself to do it. The extra encouragement of it working no problem is appreciated.
Click to expand...
Click to collapse
You're welcome.
Sent From my Kindle Fire HD running CM10.1
Ill try to keep this short. So my stock Moto X is for some unknown reason stuck in a boot loop. The only thing I can do is get into the fastboot by holding the vol down key however the "Barcodes" option is the only one that will do anything other than go back into this loop. Recovery / Factory / BP Tools all try to start but never make it past the Motorola splash screen, it stays there about 20 seconds or so and reboots.
It is running on 4.4.4 and from my understanding the bootloader can not be unlocked. I spent the better part of the last couple of days trying to figure out if there is any hope of bringing this thing back to life but I am still unsure. I was thinking maybe I could reload the official 4.4.4 but the only place I can even find it anywhere is on MotoFirmware but I cant get it to complete the download, I have tried numerous times with 3 different browsers.
I guess what I am trying to find out is if there is any way to reload the stock firmare or even load a custom ROM or something else I am not aware of yet?
Thanks much in advance for any help you can provide, it will certainly be much appreciated.
rikzjr said:
Ill try to keep this short. So my stock Moto X is for some unknown reason stuck in a boot loop. The only thing I can do is get into the fastboot by holding the vol down key however the "Barcodes" option is the only one that will do anything other than go back into this loop. Recovery / Factory / BP Tools all try to start but never make it past the Motorola splash screen, it stays there about 20 seconds or so and reboots.
It is running on 4.4.4 and from my understanding the bootloader can not be unlocked. I spent the better part of the last couple of days trying to figure out if there is any hope of bringing this thing back to life but I am still unsure. I was thinking maybe I could reload the official 4.4.4 but the only place I can even find it anywhere is on MotoFirmware but I cant get it to complete the download, I have tried numerous times with 3 different browsers.
I guess what I am trying to find out is if there is any way to reload the stock firmare or even load a custom ROM or something else I am not aware of yet?
Thanks much in advance for any help you can provide, it will certainly be much appreciated.
Click to expand...
Click to collapse
What carrier are you on?
Verizon.
It seems the more I am reading the more it is looking like I am likely out of luck.
rikzjr said:
Verizon.
It seems the more I am reading the more it is looking like I am likely out of luck.
Click to expand...
Click to collapse
HAve you wiped cache or factory reset in your stock recovery? When you boot to recovery do you get the dead android guy on his back with a triangle?
You've checked here for firmware?
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1
Otherwise, continue trying the site you've tried. It's bound to work eventually. ?
Travisdroidx2 said:
HAve you wiped cache or factory reset in your stock recovery? When you boot to recovery do you get the dead android guy on his back with a triangle?
Click to expand...
Click to collapse
Unfortunately I cant get into the stock recovery. It never gets to the injured android guy, gets hung up on the Motorola logo then reboots.
Thanks Darth I will check there.
rikzjr said:
Verizon.
It seems the more I am reading the more it is looking like I am likely out of luck.
Click to expand...
Click to collapse
The Verizon XT1060 Retail and Moto Maker versions use the same Rom/Recovery Images as the Verizon (VZW) Developer Edition phones. The the recovery images are available by request directly from Motorola. Visit -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images Once you request you will get a link from Moto to down load it. NOTE: it can take 5 min to 24 hours for the link to hit your email mailbox.
You can flash by following Method 2 at -> http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 (there are steps included which will erase all your data/apps from the phone). Please use mFastboot for All commands, not just flashing system.
However, I recommend flashing by following Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html It has a few extra steps, and a few different ones.
Always make sure you have the latest Android SDK/Platform Tools installed, along with the latest Moto device drivers, and the latest mFastboot. (If you need them, they are listed in the pre-req sections on http://mark.cdmaforums.com/MotoX-ReturnToStock.html ) If you get an error, please capture it, and post what it says.
Since you have 4.4.4 on there, yes you are out of luck from the stand point of unlocking your bootloader, and therefore can't root your phone or flash custom recovery or rom. And do NOT attempt to downgrade your rom! Since you say you have 4.4.4 on there, only use 4.4.4 SBF when flashing.
But you are not out of luck in that you can still flash STOCK Moto Signed Roms. So if its just a software issue, flashing back to stock moto Rom could help fix it. However, since you don't say what was done leading up to the issue, I must say that if this problem just "appeared on its own" and you weren't trying to flash anything, downgrade anything, use the older root processes, etc.. then you may have a hardware issue. BUT if you were trying to downgrade, use the old root processes, etc.. then you might not be able to fix the phone.
Hey KidJoe, Thanks much for the info, I really do appreciate it.
This particular phone was send to me from Motorola as a repair replacement for my original which I managed to drop and break the screen on. Totally my fault so I had no problem paying there $110 repair fee.
I do have to agree there is likely a hardware issue as I had never attempted any kind of modification at all to this phone. I was in the middle of a call when it just restarted for no reason at all. At first the phone would boot all the way up as it normally would but freeze after about 30 seconds then reboot. After reading a bit I tried to boot into the stock recovery to clean the cache and factory reset if I needed to however the first time I tried to boot into the stock recovery it just hung on the Motorola logo then rebooted. Now that is all it will ever do.
Thanks again for all the useful info for all of yall. I really do appreciate it.
rikzjr said:
This particular phone was send to me from Motorola as a repair replacement for my original which I managed to drop and break the screen on. Totally my fault so I had no problem paying there $110 repair fee.
Click to expand...
Click to collapse
How long ago did you get the replacement? Also, what was the purchase date of your original X?
i.e. are you still under the 1yr warranty of the original phone purchase, or the refurb you got for $110 might have a 30-90day warranty on it.
You can still try flashing the stock 4.4.4 rom on there. it MIGHT work. Its worth a try, especially if its completely out of warranty.
KidJoe said:
How long ago did you get the replacement? Also, what was the purchase date of your original X?
i.e. are you still under the 1yr warranty of the original phone purchase, or the refurb you got for $110 might have a 30-90day warranty on it.
You can still try flashing the stock 4.4.4 rom on there. it MIGHT work. Its worth a try, especially if its completely out of warranty.
Click to expand...
Click to collapse
Original purchase date was more than 1 year ago now. The refurb replacement i just received the day before Christmas.
At the moment I am waiting to hear back from Motorola, hopefully they will just replace this one and all will be good.
I had a TF701T tablet and dock I sold on ebay. It was neither rooted nor unlocked and worked fine. The buyer later complained saying it didnt work right, wouldn't read the SD nor an external drive. Now i know to read a external drive it needs to be rooted. But I advised it worked perfectly when it was sold. He filed a PP claim. It got here and guess what, it doesnt work right because he unloaded the bootloader flashed CWM on it. IDK what else was done but he lost the PP claim and rightfully so. But with that being said, the tablet would not turn off so eventually it will die. It will charge though. Where would I begin in flashing (I assume) the OEM software to make it usuable again?
Sounds like your buyer was a straight up dumbass.
The first thing I think you need to do is check the forum for the updated bootloader and recovery and go from there if you can install them. If you can't, idk.
You begin by determining which bootloader version you currently have: Boot holding Power and Volume Down until you see some small text. Let go, read the text and post it. Do not use the Wipe Data option from that page with CWM installed!!!!!!!!
Next you need to find the corresponding stock recovery (same firmware version) at Droidbasement and flash it in fastboot.
That done you download the Asus firmware for your SKU, unzip that file once resulting in another zip. If the tablet boots into Android, you can copy the second zip to the root of your internal storage. You should get a notification that an update is available. Confirm it and the stock recovery will flash it. That'll put you back onto stock. But there is no way to relock the bootloader - sorry.
If that does not work there's also a way to flash the stock firmware from a microSD. Let me know.
I wrote a pretty detailed guide on flashing a recovery and rom for the TF700. It's the first sticky in the TF700 General section.
Read that for the basics on getting fastboot to work.
The TF701 is very similar to the the TF700, but there are small but important differences and I wrote that guide for people trying to get AWAY from stock, so you're gonna have to extrapolate. But the basic steps are the same.
Ask here if not sure and flash only once you are clear on each step.
An easier option would be to flash one of sbdag's stock Asus roms. You still have to determine which bootloader you have now and if your CWM version is compatible. But if both are ok, you could just flash the rom and would be on pure Asus stock, but rooted with a custom recovery and could try to sell it as such.
There may be people who actually looking for a tablet all ready for flashing custom roms to it...
Lets face it: Nobody knows what that guy did to the tablet and you should disclose that to the next buyer. So I think you have a better chance to sell it to someone who wants to tinker with it. Swappa would be a good place for that.
Thanks guys. I finally got this back working.
weedahoe said:
Thanks guys. I finally got this back working.
Click to expand...
Click to collapse
Out of curiosity: How?
In the end, a data wipe though CWM that was installed by the buyer.
Thank God it was simple.