Okay, I want to start by saying I am truly sorry if this has already been looked at. I truly spent 20 minutes searching and could not find anything that address this problem.
Im going to give you the long story because, I am actually really in need of help.
My friends owns a droid x2, ?.?.5 (sorry I cant honestly remember but, its the gingerbread ending in .5)
Her husband decided to root her phone for her, and it was in Chinese and only had a partial root. Frustrated she brought it to me because, well I have a working knowledge of google, this forum, and have flashed and rooted many phones.
I managed to change the language, and root the phone (using DX2_batchroot), I installed a custom recovery (its an apk ), I also think I installed the Recovery BSR (that will make sense in a second)
I booted into custom recovery, I made a backup. Then I went about wiping caches so I could install a custom rom. I wiped all the caches, I formatted the internal memory, and then I accidentally hit "boot now".
The phone gets the the "M" and says "Failed to boot 1"
If I try holding the power and down button it just flips off completly.
I cant scroll thru the menu, I cant get the computer to acknowledge its on.
It has been plugged in the hole time.
So what do I do, and what DID I do, so I never do it again.
Thank yo
Update
Since this happened I have left it on the wall charger and checked it out occasionally.
Well it still won't boot into recovery but... It is now willing to play ball when I press volume down and then plug in to the computer. Sadly it then tells me that the battery is too low.
Now, I *guess* it could be, except after rooting and before rebooting into recovery to make my first backup I had the phone off andplugg ed into a wall charger for 2 hours.
Again, any help you can offer
Often if ROM won't boot, charging does not work either.
Will need a charged battery, or a TBH factory cable adaptor.
See my low battery options in my list.
sd_shadow's (themib) [Collection] of Links for Droid X2
Sent from my Amazon Kindle Fire using Tapatalk
Related
I really suck at installing custom ROMs.
I hard bricked because of low battery while flashing (I think, screen won't turn on, green light only comes on when plugged into a computer with no battery in, and a couple of posts I read made it sound like I'm screwed). So I'm going to AT&T tomorrow and hopefully getting a new phone. My main question is...
Can someone point me in the direction of a very comprehensive guide to installing a custom ROM on a stock Atrix brand new from the store?
I have poured over these forums for five days obsessively trying to figure out why I am so stupid and can't make it work, and have probably tried ten different methods of everything to get it to work, hoping that one of them had whatever I was missing already taken care of.
I rooted and unlocked my bootloader just fine. Even installed the Gingerblur rom (but that's a P-ROM right?). I think my problem is the custom recovery. Yes I deleted the recovery_install file. I tried flashing tenfar's CWM (the newest one I think, I sideloaded a different one to get Gingerblur) with fastboot but it said something like "flash:recovery is not a known command." (Sorry I don't remember completely, this was very early this morning before I went to sleep) I thought at the time that once you unlocked the bootloader you didn't have to do it again, but I read a thread an hour ago that said you just have to flash the unlock image after an RSD reset. So I was going to try to re-unlock, then try and flash with fastboot. Unfortunately I never got to try.
I am sorry for my obnoxiously long post, but I figured the more info I gave the higher chance there would be that someone could point at the obvious for me.
Thanks for your time.
when you plug the phone to wall-charger...wt happens?..do you see anything on the screen..
No. Also nothing happens when I press the power button. The green light ONLY comes on when I plug it into my computer with no battery, not when I plug it into an outlet.
Not entirely the right person to give advice but I guess it's worth a shot trying.
I'm a bit confused as to what you actually did. You're rooted and unlocked (100% sure on this?) Had gingerblur installed (guessing you were unlocked on 1.8.3?) and then wanted to install CMW, correct?
From the error you got you probably didn't cd (folder fastboot is in) flash fastboot recovery (path of recovery-en-goapk.img). Deleting the stock Android recovery folder most likely left you without any recovery. (Someone correct me if I'm wrong )
Entirely sure NOTHING happens while being plugged in into a computer? Can you get into fastboot at all? When connected via USB, does RSD show your device?
xscottishx27 said:
Not entirely the right person to give advice but I guess it's worth a shot trying.
I'm a bit confused as to what you actually did. You're rooted and unlocked (100% sure on this?) Had gingerblur installed (guessing you were unlocked on 1.8.3?) and then wanted to install CMW, correct?
From the error you got you probably didn't cd (folder fastboot is in) flash fastboot recovery (path of recovery-en-goapk.img). Deleting the stock Android recovery folder most likely left you without any recovery. (Someone correct me if I'm wrong )
Entirely sure NOTHING happens while being plugged in into a computer? Can you get into fastboot at all? When connected via USB, does RSD show your device?
Click to expand...
Click to collapse
The screen will not turn on. Nothing, no moto symbol, nothing. I did cd, I got an interface, fastboot said it was going to install a recovery, but then it failed, and that is the message the phone gave me. I was rooted, because I had superuser. I WAS unlocked,, because it had said unlocked on boot, though not at the time of fastboot, but then I used rsd after I was stuck in boot after trying to install a custom rom. After that it didn't say unlocked, so I unlocked again, and while doing so it said I was already unlocked. I failed to install a custom rom again with the same result, so I rsd'ed again back to 1.2. I never unlocked after that because I figured I didn't need to. I tried to install a custom rom many times with pretty much the same result after trying several different things, including flashing CWM with fastboot. Then I read that I had to re unlock after RSDing, so I was in the process of that when my screen shut off in the middle of it. I assume it didn't have enough charge and died (or that is what it sounds like according to what I have read)
mediocrepiracy said:
The screen will not turn on. Nothing, no moto symbol, nothing. I did cd, I got an interface, fastboot said it was going to install a recovery, but then it failed, and that is the message the phone gave me. I was rooted, because I had superuser. I WAS unlocked,, because it had said unlocked on boot, though not at the time of fastboot, but then I used rsd after I was stuck in boot after trying to install a custom rom. After that it didn't say unlocked, so I unlocked again, and while doing so it said I was already unlocked. I failed to install a custom rom again with the same result, so I rsd'ed again back to 1.2. I never unlocked after that because I figured I didn't need to. I tried to install a custom rom many times with pretty much the same result after trying several different things, including flashing CWM with fastboot. Then I read that I had to re unlock after RSDing, so I was in the process of that when my screen shut off in the middle of it. I assume it didn't have enough charge and died (or that is what it sounds like according to what I have read)
Click to expand...
Click to collapse
sounds like hard brick bro...
You need to find a way to charge your battery. It sounds like your battery is dead. Try to find a someone with the same phone as you.
Sent from my MB860 using XDA Premium App
To charge your battery,
Take ANY USB cable and cut one end of it off.
Strip the outer layer and strip the Black and red wires exposing the wire itself.
Starting with the black wire, tape that end to the NEGATIVE sign on the battery
Then take the red wire and tape it to the POSITIVE side of the battery.
Make sure you check it every few minutes so it does not over heat because it WILL get hot due to no regulations
I would charge it for approximately 30 min or so then put the battery back into your phone and boot it up
AND NO YOU DID NOT HARDBRICK BECAUSE YOU DID NOT HAVE HAVE THE RIGHT CWM IN ORDER TO FLASH THE OTA THAT WOULD CAUSE YOU TO HARDBRICK IF GOING BACKWARDS
ClearFire said:
To charge your battery,
Take ANY USB cable and cut one end of it off.
Strip the outer layer and strip the Black and red wires exposing the wire itself.
Starting with the black wire, tape that end to the NEGATIVE sign on the battery
Then take the red wire and tape it to the POSITIVE side of the battery.
Make sure you check it every few minutes so it does not over heat because it WILL get hot due to no regulations
I would charge it for approximately 30 min or so then put the battery back into your phone and boot it up
AND NO YOU DID NOT HARDBRICK BECAUSE YOU DID NOT HAVE HAVE THE RIGHT CWM IN ORDER TO FLASH THE OTA THAT WOULD CAUSE YOU TO HARDBRICK IF GOING BACKWARDS
Click to expand...
Click to collapse
If this works I will give you many thanks, and my firstborn child.
It didn't work. Walked into an AT&T store and said "It broke, I don't know what to do" and they gave me a new one under manufacturers warranty. I am going to try again, but if someone could point me towards a comprehensive guide that may be able to solve my problems, I would be appreciative.
I figured out my issue with not being able to install custom recovery, it was the fact that I hadn't unlocked again after flashing an sbf. I am now running Aura ROM, and so far I've been geeking out nonstop. Thanks everyone who tried to help me.
I received a G Tablet which had been used for development work for a few months. The person giving it to me (not the dev who has left) said the tablet was working fine, but had just become frozen at a reboot after he had tried to erase personal data from the tablet. I asked him if he had erased the sd card and he said "maybe" but that he couldn't remember. I powered the tablet on and sure enough it displayed two lines on a black background, one of which said something like loading kernel.
Now, these tablets were all rooted, and had Android 2.3 on them, via one of the ROMs discussed here. I don't know which one however.
So, I tried using NVflash to flash the tablet back to a stock ROM. Tablet then got stuck in a boot loop; I would see the Viewsonic logo, then the G Tablet logo, and then this would go on forever.
So I shut it down and tried again. This time Nvflash failed almost at the last step after having written most of the image.
And so here I am now, with a totally dead tablet. I cannot power it on. No combination of power or volume up/down buttons work. The only sign of life is when I plug it into its charger, and see the charging light come on.
I confirmed again with the person who gave me the tablet that the device was working just fine before it froze at a reboot after his erasing attempts.
Is there a way out of this? I hope so. Please help!
Thanks very much
Paul
texnote said:
I received a G Tablet which had been used for development work for a few months. The person giving it to me (not the dev who has left) said the tablet was working fine, but had just become frozen at a reboot after he had tried to erase personal data from the tablet. I asked him if he had erased the sd card and he said "maybe" but that he couldn't remember. I powered the tablet on and sure enough it displayed two lines on a black background, one of which said something like loading kernel.
Now, these tablets were all rooted, and had Android 2.3 on them, via one of the ROMs discussed here. I don't know which one however.
So, I tried using NVflash to flash the tablet back to a stock ROM. Tablet then got stuck in a boot loop; I would see the Viewsonic logo, then the G Tablet logo, and then this would go on forever.
So I shut it down and tried again. This time Nvflash failed almost at the last step after having written most of the image.
And so here I am now, with a totally dead tablet. I cannot power it on. No combination of power or volume up/down buttons work. The only sign of life is when I plug it into its charger, and see the charging light come on.
I confirmed again with the person who gave me the tablet that the device was working just fine before it froze at a reboot after his erasing attempts.
Is there a way out of this? I hope so. Please help!
Thanks very much
Paul
Click to expand...
Click to collapse
I would try popping it open and unplugging the internal battery then plugging it back in. Also hit the internal reset button while you're in there. It's pretty hard to actually kill one of these tablets. PM me if you need any other help.
help
Started my own thread, didnt mean to hijack. =)
Thanks, I will try removing the battery and let you know.
As for NVflash, I believe the latest version is here:
http://www.slatedroid.com/topic/171...-using-either-11-or-12-based-images-g-tablet/
However in my case I have no idea whether I have 1.1 or 1.2 and there is no way to determine this. Which one should I choose?
Paul
Doesn't matter for NVFlash, just download all of the flash files again because it might be that you have a bad download. Also make sure you have the right drivers installed since the drivers that automatically install when you plug it in sometimes don't work.
I'm pretty sure that if it boots past the birds, the hardware is working okay, so you should run the FORMAT version for NVFlash and then I'd run just a CWM flash setup and see if you can get into CWM and delete the partitions from within that.
The best thing to flash as far as ROMs would be Bekit's 1105 which is stock OTB with a few key changes. If you can't get the 1105 to play nice, you might really have some hardware problems.
I would go with the 1.2 BL, it will give you access to the newer roms as it appears that dev for the 1.1 BL seems to be dwindeling. I upgraded mine to 1.2 the other day and it worked great.
Good afternoon folks,
I had a "situation" where I found myself missing some apparently critical "bloatware" on my phone. Came up with lots of errors and a lot of functions no longer, well, functioned. Got too carried away I guess.
I had done a system backup with Titanium Backup. I initially tried just restoring some of the apps. Problem was, it just sat there saying restore. Just stuck. So I thought, hey, I have it backed up, I will do a factory reset. I did this, only then to find out that my backup was located on the INTERNAL sdcard not sdcard-ext, so all of a sudden I have no backups.
I do have access to another Electrify, if it would help. What I then decided to do was try downloading a factory rom for my phone. I downloaded "1FF-sunfire-user-2.3.5-4.5.1A_SUN_USC_19.0-19-release-keys-signed-USC-US.rar" off of the teamuscellular.com page. I booted the phone in RSD mode, restored it (three times now actually), and every step seemed to go fine (RSD even says it finished fine). But on the last step when RSD says it is rebooting the phone, at the very end, it comes up with an error :
"Failed to boot 4
starting in rsd mode"
I have read elsewhere where people say it is related to the battery. I had a 60% charge for the first two times I did this process, the last time I used the battery from the other phone which was at 95% plus. So far I have not been able to get past this.
Another post suggested that I should pop out the battery, pop it back in, hold the vol down and power buttons, and then do a factory wipe of the /data partition. This is fine, but I cannot get it to go past the Moto screen unless I let go of the buttons.
In case this might help figure out the issue, here are some details from the phone :
System version - 45.1.190.MB853.USC.en.US
Model number - Motorola Electrify
Android version - 2.3.5
Also worth noting, I did not see anything on the screen ever indicating I was "unlocked".
What I want when this is done and over with is to get the phone back and working stock, root, and make barnicle wifi work. Any advice would be most helpful, I am really kind of freaking out here.
H-E-L-P!
Thanks,
ledoktre said:
Good afternoon folks,
I had a "situation" where I found myself missing some apparently critical "bloatware" on my phone. Came up with lots of errors and a lot of functions no longer, well, functioned. Got too carried away I guess.
I had done a system backup with Titanium Backup. I initially tried just restoring some of the apps. Problem was, it just sat there saying restore. Just stuck. So I thought, hey, I have it backed up, I will do a factory reset. I did this, only then to find out that my backup was located on the INTERNAL sdcard not sdcard-ext, so all of a sudden I have no backups.
I do have access to another Electrify, if it would help. What I then decided to do was try downloading a factory rom for my phone. I downloaded "1FF-sunfire-user-2.3.5-4.5.1A_SUN_USC_19.0-19-release-keys-signed-USC-US.rar" off of the teamuscellular.com page. I booted the phone in RSD mode, restored it (three times now actually), and every step seemed to go fine (RSD even says it finished fine). But on the last step when RSD says it is rebooting the phone, at the very end, it comes up with an error :
"Failed to boot 4
starting in rsd mode"
I have read elsewhere where people say it is related to the battery. I had a 60% charge for the first two times I did this process, the last time I used the battery from the other phone which was at 95% plus. So far I have not been able to get past this.
Another post suggested that I should pop out the battery, pop it back in, hold the vol down and power buttons, and then do a factory wipe of the /data partition. This is fine, but I cannot get it to go past the Moto screen unless I let go of the buttons.
In case this might help figure out the issue, here are some details from the phone :
System version - 45.1.190.MB853.USC.en.US
Model number - Motorola Electrify
Android version - 2.3.5
Also worth noting, I did not see anything on the screen ever indicating I was "unlocked".
What I want when this is done and over with is to get the phone back and working stock, root, and make barnicle wifi work. Any advice would be most helpful, I am really kind of freaking out here.
H-E-L-P!
Thanks,
Click to expand...
Click to collapse
did you install the moto drivers? if you're unlocked be sure to flash 2.3.4 not 2.3.5
Good afternoon,
I have installed the moto drivers. I am on Windows 7 64 bit (dual boot with Linux Mint Debian 64). I installed "MotoHelper_2.1.40_Driver_5.5.0.exe", and was using RSDLite5.6.
As far as I know, the phone was locked. Rooted, but locked. Some say it will actually say on the screen 'unlocked', mine does not say anything like that.
Thanks,
Just to make sure it's not a battery issue, there is free battery swap if you can run by a USCC store. But I think you're right, it's probably not that. Wish I could help you more, but it stumps me.
ledoktre said:
Another post suggested that I should pop out the battery, pop it back in, hold the vol down and power buttons, and then do a factory wipe of the /data partition. This is fine, but I cannot get it to go past the Moto screen unless I let go of the buttons.
Click to expand...
Click to collapse
From the phone completely off, hold vol-down and power. When the screen lights up, release power ONLY. Keep holding vol-down until some text shows up then release. Click vol-down to scroll through options until Recovery shows up. Click vol-up to select. Once recovery starts, navigate using vol-up/vol-down and power to select. /data will be wiped if you do a factory reset.
Hope this helps.
My friend is having some problems charging his Atrix. Basically, the phone will not charge or recognize a charger at all except for under certain circumstances.
Some background info: I helped him unlock his bootloader and install 4.5.91 way back when it came out. No problems there, it went well. All was fine until the 4.5.141 OTA update came around. He got the OTA notification and clicked update because he didn't know anything bad would happen. Luckily it didn't brick him like it did a lot of people, but he said it gave him an error message during the install and it would not boot after that, stuck at the Motorola dual core screen. I took a look at it and managed to get into recovery and flash back to 4.5.91. All was fine until it was time to charge the phone. It wouldn't recognize any charger. I tried flashing to tons of different roms, wiping everything, even restored a full nandroid recovery from my working Atrix on it. His phone will charge and will be recognized by a computer immediately after we flash a new rom, and will continue to charge for as long as we leave it plugged in, but if we unplug it then after a short time (like under 30 mins) it will not recognize a charger if we plug it in again. Wiping data alone will not make it start charging again, only actually installing a new rom will. Deleting battery stats does nothing. The closest we have gotten to fixing it was when I made a nandroid on my Atrix and then restored it on his (my backup was from Joker's CM9); after the restore, it would charge for a while, and we unplugged it and waited to see if it would do the same thing as it always did and stop recognizing a charger after a few minutes. About 30 minutes later it stopped recognizing the charger as usual. We played with the USB debugging setting (enable, plug in, see if it recognized the charger, disable, plug in, see if it recognized it, etc) and after messing with that setting a lot it recognized the charger once, but then when we unplugged it the phone wouldn't recognize the charger again. We could not reproduce this again.
To summarize what we have tried and found to work:
-flashing a rom will let the phone charge/let a computer recognize it for as long as we leave it plugged in after the first boot (we have tried every rom under the sun, they all do the same thing)
-restoring from a nandroid backup will have the same effect as flashing a rom
What we have tried that didn't work:
-different cords; have tried them all, both OEM cord and third party, this is not the problem
-wiping all data/factory reset doesn't do anything
-cache wipe doesn't do anything
-wiping battery stats doesn't do anything
I have also tried fastboot flashing back to 4.5.91, CWMing back to 4.5.91, using the unbrick scripts and stock restore scripts people have made, nothing will fix it.
If anyone has any suggestions or can refer me to anywhere with more info on this I would appreciate it, I have searched high and low and can't find anyone with a problem quite like this one. I don't even know if it's a hardware or software problem, if you guys know a way to determine this it would be helpful.
Have you tried a wall charger?
Yeah, both the stock one and a different one I have, neither work.
No one has any advice or ideas on this? Does anyone know if Moto does repairs in this type of situation with a voided warranty because of an unlocked bootloader, or does anyone know who may be able to fix this if I can't get any help from the forums or figure it out on my own?
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
elead1 said:
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
Click to expand...
Click to collapse
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
VeNuM said:
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
Click to expand...
Click to collapse
I will post back with results. Not like I've got much else to do with it right now, eh? :laugh:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
Damn. Well I've been there done that too...
send it to htc.
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
i had the same problem but my situation was that i downgraded the radio while s-on. I was in the same situation that you are right now. i did everything i could but nothing worked so my last hope was sending it to HTC and say that i lefted updating the software while sleeping and when i woke up it was like that. i sended they didnt even ask, i got it back like new . :laugh: