Related
I have been trying since yesterday to get my Nexus back in to working function. I had CM 6.0 with ClockWork recovery. Through recovery I wiped data/cache/etc then attempted to flash a stock frf91.zip from the sd card. As it was in the process of doing so recovery gave me an error and said it would reboot into Rom Manager. Now my phone hangs on Nexus X logo before the boot animation. I can power the device into fastboot to choose bootloader-reboot-reboot bootload-power off.
I believe that recovery process had the error/issue right after it deleted the system image.
YET I do not have the function of my Power/Multi-Use Button on the top of the phone. So I tried to use adb (which I have used with my phone previously without any issues) to attempt to install the stock rom image.
With adb running I sent the command to display the devices connected. It shows the list but with nothing connected (NOT an error or no devices connected), just blank. I then tried fastboot and sent the command to list connected devices, fastboot showed my devices serial as a connected device.
I was able to flash a system.img file using fastboot yet nothing happened, an all other restore attempts, like userdata.img or boot.img, etc. will not work and come back with a error of no remote permission.
Sorry for the entire book, but I am sort of lost.
My reason for this whole mess is because I wanted to restore my phone to a stock rom and recovery to send it in to have the power button fixed while retaining my warranty (my bootloaded IS locked).
When I get home from college today I am going try loading a stock factory passimg.zip of ERD79 on my sd and let fastboot try to pick up on it. I really have no other option haha.
Anyone have a suggestion? Honestly I am willing to just send it in AS-IS or brick it an tell them I had no idea what happened that I couldn't use the power button and it died after an update.
I see that no one has any idea really haha.
Couldn't tell from reading your write up - can you boot into recovery?
Sent from my Nexus One using XDA App
no I cannot. I do not have use of my power button. I am going to read through the new thread concerning accessing recovery without use of the power button.
To use adb, you need to be in recovery, or fully booted with debugging enabled.
To use fastboot, you need to unlock your boot loader.
Try reverting to stock via passimg method (one of the newer ones, if you have the Froyo radio).
Sent from my Nexus One using XDA App
I recently realized that was the issue with adb. So fastboot is out of the question then. Doesn't the passimg method require use of the power button though?
Unroot/Restore (use passimg method):
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Sent from my Nexus One using XDA App
hboot scrolls quickly when I try this and I catch that it says that is not a valid passimg.img
any ideas?
Should be passimg.zip (not img).
Makes sure it's not a zip inside a zip.
FRG83 seems problematic, so try FRG33 instead.
Sent from my Nexus One using XDA App
Just discovered this gem:
http://forum.xda-developers.com/showthread.php?t=825909
Sent from my Nexus One using XDA App
I got the passimg method working correctly. I mean passimg.zip in the previous post. I tried frf91 and it went through then said checking and went straight back to hboot without asking for permission. I'm going to try frg33 and if that doesn't work I will try the app you found.
frg33 seems to be working
hboot with FRG33 worked and the phone booted up with rom. thank you very much for all of your awesome help danger-rat.
No worries...
Sent from my Nexus One using XDA App
Okay I recently rooted my phone like 2 or 3 months ago and then I flashed it to rom liberty 3 and it worked perfectly for about 2 months. I really don't do anything else to my phone and now my phone loses service all the time and a half black screen will flash saying something like BP core mode trying to open usb. It will flash for a couple minutes then it will turn off then when the phone is set it will say insert AIM card but card is in securely. What is the problem.
Sent from my DROID3 using XDA
Completely incorrect section.
But, this is what I would do:
Wipe data/factory reset.
Format /system
Wipe cache/delvik
Reflash your ROM.
Still didn't work phone still messing up. I even used the Verizon one click unbrick method
Sent from my DROID3 using XDA
So I have a rooted Atrix HD that I tried to restore to stock using the original fastboot files from this thread:
http://forum.xda-developers.com/showthread.php?t=1853522&page=2
I ended up getting error messages with the 1st xml file so I used the modified one in Post #14 of the same thread.
Phone appears to flash properly but gets stuck at AT&T logo and RDS makes me power cycle the phone after an eternity.
When I do and get back into fastboot it says pass and thinks everything is good.
Bad news for me is I'm stuck at the AT&T logo and can't move forward.
I can still get into boot mode selection menu so that appears to be good but I'm at a loss on how to recover this thing into a working phone again.
Anyone have any insight?
Battery life was right around 50% when I started.
Maybe RDS puked since it wasn't at 75%?
Any help would be greatly appreciated.
Make you are using the latest version of RDS 6.1.4 and make sure that your cable is perfect and that your phone is detecting properly.
I think I figured out part of my problem.
Used the modified xml file for 144 with the MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip file.
RDS lets it flash but never gets past the AT&T logo.
Now if I try to go back and flash with the right file for the modified XML I get 1/24 flash partition "gpt_main0.bin" -> Phone returned FAIL.
I think I might have borked this phone......
windago said:
I think I figured out part of my problem.
Used the modified xml file for 144 with the MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip file.
RDS lets it flash but never gets past the AT&T logo.
Now if I try to go back and flash with the right file for the modified XML I get 1/24 flash partition "gpt_main0.bin" -> Phone returned FAIL.
I think I might have borked this phone......
Click to expand...
Click to collapse
That fastboot is not for Retail AT&T devices.
Well after booting phone into BP tools to let it charge all night I attempted to reflash this morning with a full battery and a new USB cable using the MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip file and we're back in and now on 4.1.1.
Time will tell if we're back to normal for good.
What is the BP tools you mentioned? Because I've known that it's imposible to charge the phone while it is stcuked into bootloop or even being in the Bootloader screen.
jics91 said:
What is the BP tools you mentioned? Because I've known that it's imposible to charge the phone while it is stcuked into bootloop or even being in the Bootloader screen.
Click to expand...
Click to collapse
BP Tools is the fifth option available when I boot into the boot mode selection menu by pressing Vol Up/Vol Down + Power.
Boot Mode Selection Menu (10.9B)
Available Boot Modes:
Normal
Recovery
AP Fastboot
Factory
BP Tools
I ended up plugging the phone into my Galaxy S3 wall charger last night and then selecting BP Tools when I entered the Boot Mode Selection Menu.
A simple battery icon appeared telling me I had 9% battery left.
This morning after keeping it plugged in all night I had 100% battery.
As I stated earlier after a full charge I was able to flash using RSD lite and now have a working phone again.
windago said:
BP Tools is the fifth option available when I boot into the boot mode selection menu by pressing Vol Up/Vol Down + Power.
Boot Mode Selection Menu (10.9B)
Available Boot Modes:
Normal
Recovery
AP Fastboot
Factory
BP Tools
I ended up plugging the phone into my Galaxy S3 wall charger last night and then selecting BP Tools when I entered the Boot Mode Selection Menu.
A simple battery icon appeared telling me I had 9% battery left.
This morning after keeping it plugged in all night I had 100% battery.
As I stated earlier after a full charge I was able to flash using RSD lite and now have a working phone again.
Click to expand...
Click to collapse
Congrats. I know exactly how that feels. I was in a similar situation not too many days earlier! It is a little sad that there is very little help online when you get stuck when trying something on this phone. You end up having to figure things out by yourself.
windago said:
Well after booting phone into BP tools to let it charge all night I attempted to reflash this morning with a full battery and a new USB cable using the MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip file and we're back in and now on 4.1.1.
Time will tell if we're back to normal for good.
Click to expand...
Click to collapse
So flashing this worked for you? I think someone tried this a week or so ago and it bricked their phone.
Sent from my MB886
ReverseZero said:
So flashing this worked for you? I think someone tried this a week or so ago and it bricked their phone.
Sent from my MB886
Click to expand...
Click to collapse
Please no one try that file... it will only work on bootloader-unlocked Atrix HD devices since it is not a build meant for retail AT&T devices.
Makes sense. Don't think I'll be trying that.
Sent from my MB886
As mattlgroff stated:
Please do not flash the file I linked to/reference to in my OP.
He's a developer and has much more insight into the workings of these files then I do.
I'm not sure why mine worked but I defer to his statement about not flashing that particular file.
I was on stock JB. Rooted with new exploit. Installed bootstrap and custom ROM. Wanted to get back to stock, so I uninstalled bootstrap, and flashed MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip.
RSD failed with 'getvar' and 'oem'. I then edited the xml, removed 'getvar' and 'oem', and retried the flash. RSD failed at system.img.
I then booted the phone into fastboot and did the whole thing manually thru fastboot and terminal. This time everything went through okay. I rebooted the phone into stock recovery and erased cache. But now the phone is stuck in bootloop on the red m logo.
What am I missing?
I am having trouble to flash back to stock ICS with RSD lite everytime i use it and connect my phone it says USB connected but that is it. I cannot find the associated file anywhere to flash back to stock any ideas?
so I rooted my Atrix HD (running 4.1.1) and decided to flash a custom ROM, so after installing a recovery and downloading a ROM I wanted, I flashed it.
problem is, I forgot to unlock the bootloader
after I flashed the ROM, I rebooted the phone and it booted into AP Fastboot
I tried using RSD Tool to flash the 4.1.1 firmware I found at sbf.droid-developers but it fails and says "Failed flashing process. Failed flashing process. 1/23 flash partition "gpt_main0.bin" -> Phone returned FAIL; phone connected"
I already edited the xml file and removed the two lines containing max-download-size
also it says low battery on the Fastboot screen and I assume it's not charging at all when plugged in on the Fastboot screen so this may be a problem in the very near future or may already be a problem
am I totally screwed? how can I fix this?
buttwhole said:
so I rooted my Atrix HD (running 4.1.1) and decided to flash a custom ROM, so after installing a recovery and downloading a ROM I wanted, I flashed it.
problem is, I forgot to unlock the bootloader
after I flashed the ROM, I rebooted the phone and it booted into AP Fastboot
I tried using RSD Tool to flash the 4.1.1 firmware I found at sbf.droid-developers but it fails and says "Failed flashing process. Failed flashing process. 1/23 flash partition "gpt_main0.bin" -> Phone returned FAIL; phone connected"
I already edited the xml file and removed the two lines containing max-download-size
also it says low battery on the Fastboot screen and I assume it's not charging at all when plugged in on the Fastboot screen so this may be a problem in the very near future or may already be a problem
am I totally screwed? how can I fix this?
Click to expand...
Click to collapse
I had the exact same problem, I could not get it to work no matter what I did, I finally got it working by using MythTools http://forum.xda-developers.com/showthread.php?t=2262726 That ones recovery got it working for me, I hope you can get it fixed, but don't give up, it took me about 6-7 hours before I fixed it lol, I ended up flashing stock ICS and then it finally came back for me.
And no, it does not charge in fastboot, or at least it doesn't seem to, and battery seems to drain rapidly, I'd say let it charge on USB for a while while it's off and start trying again
Silentwidow said:
I had the exact same problem, I could not get it to work no matter what I did, I finally got it working by using MythTools http://forum.xda-developers.com/showthread.php?t=2262726 That ones recovery got it working for me, I hope you can get it fixed, but don't give up, it took me about 6-7 hours before I fixed it lol, I ended up flashing stock ICS and then it finally came back for me.
And no, it does not charge in fastboot, or at least it doesn't seem to, and battery seems to drain rapidly, I'd say let it charge on USB for a while while it's off and start trying again
Click to expand...
Click to collapse
tried this, doesn't work
still fails to boot (Fastboot Reason: Boot Failure)
whenever I plug it in it automatically turns on and goes to Fastboot so I can't charge it with the screen off
buttwhole said:
tried this, doesn't work
still fails to boot (Fastboot Reason: Boot Failure)
whenever I plug it in it automatically turns on and goes to Fastboot so I can't charge it with the screen off
Click to expand...
Click to collapse
a couple more details
I tried this with both 4.0.4 and 4.1.1
the tool extracts them, asks me if I'm ready to flash, I say yes, then it asks me if I'm in normal mode or fastboot mode to which I answer fastboot
the only difference between 4.0.4 and 4.1.1 is at this point on 4.0.4 it asks me if I'm flashing 4.0.4 ICS
after that it says "Starting flash process..." and reboots my phone into fastboot again (and it lists the fastboot reason as sticky bit instead of boot failure)
and stays on this for about a minute, then asks if I want to use stock or CWM recovery (stock), then it says flashing stock and it reboots my device...
...which reboots back into fastboot with reason listed as boot failure
also I tried following /showthread.php?t=2231249 to a T but the same thing that I described in the OP happened
Did you try to flash system using fast boot?
Sent from my MB886 using xda premium
ai6908 said:
Did you try to flash system using fast boot?
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
no, I just tried with RSD and Myth Tools
edit- I tried flashing with fastboot and it failed because the battery is too low
I ordered a factory cable and will report back when that gets here
I got my fastboot cable today. flashed 4.1.1 with RSD, no problems encountered
feels good having a working phone again
now I can add this fastboot cable to my collection of stuff I had to buy when I ****ed up big (my Galaxy S download mode jig comes to mind)
edit- so frustrating
the AOKP ROM I want to use is laggy in general use
the CM10.1 and PACman ROMs I tried are a lot smoother but aren't as customizable
buttwhole said:
I got my fastboot cable today. flashed 4.1.1 with RSD, no problems encountered
feels good having a working phone again
now I can add this fastboot cable to my collection of stuff I had to buy when I ****ed up big (my Galaxy S download mode jig comes to mind)
edit- so frustrating
the AOKP ROM I want to use is laggy in general use
the CM10.1 and PACman ROMs I tried are a lot smoother but aren't as customizable
Click to expand...
Click to collapse
Yea the CM10.1 skrillex night isn't bad, but the camcorder doesn't work, I personally am going to Mexico Retail and just wiping out a bunch of system apps and replacing the 4.1 apps with 4.2.
Silentwidow said:
Yea the CM10.1 skrillex night isn't bad, but the camcorder doesn't work, I personally am going to Mexico Retail and just wiping out a bunch of system apps and replacing the 4.1 apps with 4.2.
Click to expand...
Click to collapse
gl
buttwhole said:
gl
Click to expand...
Click to collapse
Wasn't too bad, I have it running right now, ended up using ATT retail instead, just because of the "LTE" on the 4g symbol(I know!), but I pretty much wiped out all Motorola apps and deodexed it, runs smooth without issue, and it's fast, but I really want the Tablet UI!
Search for Tablet UI...see below thread as well...
http://forum.xda-developers.com/showthread.php?p=38670671
Have a NAND backup before you use this...
If you end up doing this, please report your results and any issues you run into. I have tried some tablet ui stuff(roms that offer it) and haven't found a huge value in doing it...
Though, a full fledged tablet UI would be cool to try out. I'll probably end up trying it at some point, but if you take a first stab, any tips/tricks with what you did would be helpful.
thanks!
Maam.
Hi!
Device Info:
I have a rooted Kindle Fire HD 7" running CM11 with TWRP 2.7 running as a recovery. I have had the tablet for approximately a year and a half, so hardware issues from age wouldn't be overly unexpected, but not necessarily expected either.
Background Knowledge:
(Note: The following has happened before in CM10.2, but disappeared upon updating to CM11)
One week ago...
-Fully functioning tablet running CM11 with TWRP 2.7 recovery set up.
Four days ago...
-Device begins to randomly shut down about once an hour
-Later in the day it begins to shut down soon after I reboot it (as soon as 5 minutes)
Two days ago...
-Death
-Not really, but the device shut down a couple seconds after fully turning back on
My Response:
My first discovery upon looking into this problem was that fastboot was fully functioning and seemed to be unaffected by the shutdowns (I assume they were caused by maxed out RAM). I attempted to boot into recovery, only to find that it was unavailable, and booted into system instead. I then decided to flash TWRP again. I made the stupid mistake of deciding to use a brick-fix tool instead of just doing it myself. Unfortunately, I just opened the first file that looked right in my Android directory, which happened to be a tool designed for Kindle Fire HD 1st gen. I am not entirely sure what happened, but I assume it wiped everything it could get its hands on and put in an incorrect replacement.
The Actual Issue:
The kindle is now throwing a fit. Now,when I turn it on, it launches the stand Kindle Fire logo, shifts to the Fastboot logo, then turns off.. or at least the screen does. When I press the power button after this, nothing happens. I must hard shutdown in order to even activate the pathetic turn on and fade action. Next, I plugged it into the computer, planning to fall back on my amateur knowledge of fastboot, only to find that the fastboot logo means nothing (probably). When I plug the device into the computer, I head the plugged in chime, then exactly 3 seconds later, the disconnect chime. This is the only indication I have that anything is happening, as the screen is off. The fastboot logo either means nothing, or the three seconds is not long enough to establish a connection to the computer.
Help? Anyone?:
I apologize to come on here acting like a noob who panics the moment he feels discomfort and does no research of his own.
Before I posted I searched the best I could to find any issue similarish to my issue and come up with two, only one sounding similar at all:
http://forum.xda-developers.com/showthread.php?t=2729536 - Similar issue, but not really the same symptoms. The only real similarity is the device.
http://forum.xda-developers.com/showthread.php?t=2421487 - More similar, even kind of used my same description. The symptoms are not the same, the major problem is that I cannot establish fastboot connection. (And device is not the same)
Thanks for any help that can be offered!
I would save a "fastboot -i 0x1949 flash boot boot.img" and flash the boot.ing from the cm 11 zip, it should attempt to flash as soon as the kindle kicks into fastboot. If anything it might help fastboot from freaking out.
Sent from my LG-P769 using Tapatalk
Thanks, I'll try that. I'll update after I try it.
Update:
Thanks! That worked perfectly! It stops the device from fading, allowing me to flash a new ROM. To note to anyone else who might have this issue, the command will only send upon the initial boot. Any of the following connects/disconnects will not work.
Sent from my Nexus 5 using Tapatalk
Follow-Follow Up:
Flashing the boot img from CM11 works great at pausing the bootloop allowing me to communicate with fastboot. Unfortunately, upon flashing stock amazon system img and TWRP recovery, I am still unable to launch into either of them. Whenever the kindle reboots, the "extreme bootloop" begins again, forcing me to flash the boot img again.
Should I be trying to get a hold of the stock bootloader from Amazon? (And if so, would you have any suggestions as to where I can grab it? I have thus far been unable to find it)
Thanks for any help!
Sent from my Nexus 5 using Tapatalk
Its probably from the selinux xattribs left over on /data from cm 11, Amazon's kernel doesn't have selinux support and crashes/freaks out when it sees them. You would have to do a internal storage wipe to get rid of them if flashing back to amazon os.
Sent from my Amazon Tate using Tapatalk
Would erasing userdata/system effectively remove it?
(Sorry for my ignorance)
Sent from my Nexus 5 using Tapatalk
No need to wipe system, only user data hence why I said if twrp is still acessable to do a internal storage wipe, it wipes userdata.
Sent from my Amazon Tate using Tapatalk