Okay, I have a 16 gig us moto g with a unlocked 4.4 boot loader, cmw recovery, and root. The other day I was going to flash the unofficial beanstalk rom, so I did the usual data wipe and what the installation guide said on the thread. I got stuck in a bootloop so held down the power button to try and reset the phone and get it to the bootloader menu but my screen went black. It has been black ever since, no matter what combination of button I press I can't get the screen to do anything, I have never had this problem before on any android device. Do you guys think if I contact Motorola they'll give me a replacement even though the bootloader is unlocked. Any help is appreciated.
Edit: fixed! I read on a faq that you sometimes have to hold power button for as long as 30 seconds so that's what I did and it worked
Related
Hi to all,
I been trying to upgrade to JF 1.14 rc33 and haven't been able to get to the recovery mode to process the update.zip file. Im not a noob but also not and expert i rooted my my phone so i know basics. When i try to hold the home butoon and power button the g1 logo keeps reappearing for as long as i hold it from 10 seconds to 2 minutes. any ideas of what im doing wrong, i dont care if i have to wipe i just want rc33. Thanks.
I currently have Fimware 1.0
Build #:1.0 TC-4 RC30
Custom Theme: Windows beta 7
Just to make sure, with the phone off you press and hold the home button and then press and hold (while still holding the home button) the power button. It should take ~20 seconds for the recovery mode screen to come up.
Dharkaron said:
Just to make sure, with the phone off you press and hold the home button and then press and hold (while still holding the home button) the power button. It should take ~20 seconds for the recovery mode screen to come up.
Click to expand...
Click to collapse
i tried and did not work
natienn said:
Hi to all,
I been trying to upgrade to JF 1.14 rc33 and haven't been able to get to the recovery mode to process the update.zip file. Im not a noob but also not and expert i rooted my my phone so i know basics. When i try to hold the home butoon and power button the g1 logo keeps reappearing for as long as i hold it from 10 seconds to 2 minutes. any ideas of what im doing wrong, i dont care if i have to wipe i just want rc33. Thanks.
I currently have Fimware 1.0
Build #:1.0 TC-4 RC30
Custom Theme: Windows beta 7
Click to expand...
Click to collapse
Flash back to the original G1 theme, then try the update. Your theme may be preventing you from upgrading.
andonnguyen said:
Flash back to the original G1 theme, then try the update. Your theme may be preventing you from upgrading.
Click to expand...
Click to collapse
how do you flash to the original theme? do you know of any links? thanks
Start holding the Home button before you press the Power button.
jashsu said:
Start holding the Home button before you press the Power button.
Click to expand...
Click to collapse
i tried that in different time lentghs from 10 seconds holdin both to 2 minutes, of course pressing the home key 1 sec before the power and holding both
Same problem
Need to bump this thread as I'm having the same issue. Have a HTC Dream with CyanogenMod-5.0.7-DS, trying to go to 5.0.8, but cannot get into Recovery Mode.
Yes, I am completely powering the phone off, holding Home just prior to pressing & holding Power. I keep both depressed for a few minutes and no joy, just sits at the G1 splash screen. I can remove the battery and press Power to bring the phone up normally. Have even dropped to the console, switched to root and issued "reboot recovery". The phone restarts and sits at the G1 splash screen as well.
Can anyone offer advice on how to restore my Recovery Mode? Many thanks...
You can try to reflash (or flash another) recovery with adb, fastboot or in terminal. Btw this thread is in wrong section. It should be in Q & A section.
You could even flash a recovery image from within your rom...you said you could boot the phone normally correct?
So drop into terminal and flash it if you don't want to mess with adb.
The Amon Ra 1.7 Recovery thread has the commands you need to flash through terminal...
These people apparently are no help. If you hold down the home key and it stays at the G1, try fastboot by holding down the camera button on the side while you power it on. You only need to hold the home key until it vibrates. It should instantly boot into fast boot, if you're holding down camera when powering on.
... if you can get into fastboot, you might need to unroot your phone and reroot it.
... if you can't get into fastboot or recovery mode, then you probably bricked your G1 and you'll need a jtag or scrap it. Or if it's under insurance, tell them you updated and your phone is stuck on the G1 screen....
You could also try taking out your battery then powering it on into fastboot/recovery but odds are that wont help at all.
Hope this was some help.
yutsoku said:
These people apparently are no help. If you hold down the home key and it stays at the G1, try fastboot by holding down the camera button on the side while you power it on. You only need to hold the home key until it vibrates. It should instantly boot into fast boot, if you're holding down camera when powering on.
... if you can get into fastboot, you might need to unroot your phone and reroot it.
... if you can't get into fastboot or recovery mode, then you probably bricked your G1 and you'll need a jtag or scrap it. Or if it's under insurance, tell them you updated and your phone is stuck on the G1 screen....
You could also try taking out your battery then powering it on into fastboot/recovery but odds are that wont help at all.
Hope this was some help.
Click to expand...
Click to collapse
Why would you need to reroot it, just flash a new recovery through fastboot.
fastboot flash recovery <name>.img
misread, yeah he could do that too but it would be easier to reroot if he knows how to do that... instead of learning a whole new method.
You're right though, that would be better.
Update
I am able to fastboot by holding the camera button in and powering on. It sounds like I just need to do the Amon Ra Recovery procedure in order to restore my recovery partition. I assume that I'll need to re-root, but I'm sure there are instructions there for that as well.
Thanks for all the quick replies!
So here's what I found....
I had the exact same problem, but first a little history then how I fixed it.
I purchased an 8GB MicroSD card so I could use Apps2SD and was quite pleased with the ability to do so. Until my battery life dropped to 5mins. It was already down from when I bought it last year.
The battery was severely screwed on my. If I used ANYTHING for more than 5 mins, it would die and would NOT boot up. Oh I could pres the power button and it would try to boot but then die somewhere in the boot process. That is until I plugged it into some charger (car or wall) and then it would boot, showing anywhere from 70 to 90% battery life.
After much research I found that it was the battery and so ordered a replacement off eBay from Hong Kong. $3.96 shipped to my door. Works great, and I am incredibly thankful for that.
So just prior to getting the battery I had done an upgrade to 5.0.8 with the vain hopes that it might help limp along but to no avail. The battery was gone.
Ok, so in comes the new battery. Great! I'll just reflash the ROM to make sure there are no lingering issues and we'll be good to go! Little did I realize that I did an 'upgrade' from CM Updater and when I booted into Recovery I flashed th zip file that was there....which was 5.0.7. DOH! No biggie, everything was working so I didn't worry too much.
Then I installed Clockwork's ROM Manager 1.8.x. A few days later there was an update, so I updated to 2.0.1.3. So I updated that. It went fine.
Few days later, and a few more apps re-installed, the system was running slow.
Apps2SD was greyed out. Huh?
Checked the card....Ubuntu was only mounting it Read Only. And the old swap partition, which I thought I had deleted, was still there. Dammt. But this s a side story I think.
So I wanted to reflash but there was no way I could do it because I could not get into Recovery mode. Ugh.
ROM manager had an update to 2.0.1.4. Ok, maybe that'll work. Nope. It said it updated fine but stuck at G1 logo like many others.
Doing some googling around I saw that it was a ROM Manager issue and that you should flash back down to 1.4.x. Well, since I knew it was working at 1.8.x I decided to reflash to 2.0.0.3. I could get into recovery mode now!
While this kinda solves one issue....I'll have to go into another thread to figure out the Read Only problem so I can re-partition my card again.
Thread closed. Please post questions in the Questions and Answers forums and not in the development forum.
hello frnds,
i am from india (duh) ...my friend bought a galaxy nexus s two days ago..
she had it up an running and it was working as it should.. but yesterday when she woke up..what she saw was that the phone won't boot up and a it shows a lock sign on the boot screen below google and that it was heating up badly... even the pc is not detecting it..i have the phone right now and i promised her that i'll fix it...
what should i do to keep up my promise!
bootloader is locked, phone won't boot
Hello,
The lock simply means that the bootloader of the phone is currently locked (as it is from the factory).
If it won't boot past the Google screen, try removing the battery of the phone for 10 seconds, then trying again.
If this fails, remove the battery again, replace the battery, hold down the UP volume button while pressing power until you see a green android screen. If you can see this screen, then use One Click Root 5.1 in the Development Thread for Nexus S or Nexus S 4G.
hmmm..
thank for the relpy,
well i have tried all that stuff i.e removing the battery for 10 sec..(didn't work)...
wen't to recovery mode(the green android thingi...) and tried recovery option won't work..
do you mean i should flash the firmware again by using one click?
thanks in advance!!:angel:
The lock sign means that the bootloader is UNLOCKED. If you didn't see the lock it would mean that the bootloader is locked (stock). The recovery option won't work because you haven't flash any custom recovery. In fastboot mode (volume up+ power button) it should say: LOCK STATE - UNLOCKED. This means that bootloader is unlocked. Use the toolkit (found in nexus s android development) to flash stock image.
Someone tried to do stuff to the phone and messed up.
thanks
i will try this let you know.:fingers-crossed:
thanks for the help:good:
What causes this though? I have codename jb And cwm 6 on my device and it randomly gets stuck on the boot screen through out the day
Hey guys, I need a bit of help. I had CM11 installed on my one x with 4.4.2, i decided id like to update it to cm12. So i read the instructions. I was S-off and supercid already .so i went to ruu 3.18. Got success in cmd line, reboot into bootloader. saw it worked. went to update to 5.18 at&t firmware as per the cm 12 instructions, i got success. but when i hit reboot, the htc logo just appears, and then it shuts off. It will not go into fastboot, bootloader, or recovery.
Is the phone bricked? or is there a way to fix this. This isn't my main device so i'm not too worried about it, just want to get it working if possible.
Arkalos13 said:
Hey guys, I need a bit of help. I had CM11 installed on my one x with 4.4.2, i decided id like to update it to cm12. So i read the instructions. I was S-off and supercid already .so i went to ruu 3.18. Got success in cmd line, reboot into bootloader. saw it worked. went to update to 5.18 at&t firmware as per the cm 12 instructions, i got success. but when i hit reboot, the htc logo just appears, and then it shuts off. It will not go into fastboot, bootloader, or recovery.
Is the phone bricked? or is there a way to fix this. This isn't my main device so i'm not too worried about it, just want to get it working if possible.
Click to expand...
Click to collapse
Wrong forum mate go in the right forum
Arkalos13 said:
Hey guys, I need a bit of help. I had CM11 installed on my one x with 4.4.2, i decided id like to update it to cm12. So i read the instructions. I was S-off and supercid already .so i went to ruu 3.18. Got success in cmd line, reboot into bootloader. saw it worked. went to update to 5.18 at&t firmware as per the cm 12 instructions, i got success. but when i hit reboot, the htc logo just appears, and then it shuts off. It will not go into fastboot, bootloader, or recovery.
Is the phone bricked? or is there a way to fix this. This isn't my main device so i'm not too worried about it, just want to get it working if possible.
Click to expand...
Click to collapse
It isn't bricked, if it powers on at all it isn't a brick. Not being able to get to the bootloader is almost always a case of user error. To boot into the bootloader there are two methods.
With phone powered on
Hold the volume down button, then hold the power button (so you're holding both buttons together), the button lights will start to flash, they will stop flashing and the screen will go blank, after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
With phone powered off
Hold the volume down button, then hold the power button (so you're holding both buttons together), after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
Please post the first five lines.
Transmitted via Bacon
You are correct, thanks for the help. I guess I wasn't doing the right technique to get into boot loader. (Volume down+power button) I was doing vol up.
Thanks again, all is well and running cm12 now.
Sent from my LG-D850 using XDA Free mobile app
No probs, glad to help.
Transmitted via Bacon
My moto g was attempting to install lollipop on my rooted 4.4 and i idiotically wiped all my data through TWRP (?) and rebooted my phone with no OS even when i was warned By a warning screen. Now my phone is stuck on the white unlocked bootloader screen and when i hold down the power button and the volume down button, it just goes back to the unlocked bootloader screen. Can i do anything? Idc about any data on it but id love just my stock phone working. Thanks for any help.
takemyname45 said:
My moto g was attempting to install lollipop on my rooted 4.4 and i idiotically wiped all my data through TWRP (?) and rebooted my phone with no OS even when i was warned By a warning screen. Now my phone is stuck on the white unlocked bootloader screen and when i hold down the power button and the volume down button, it just goes back to the unlocked bootloader screen. Can i do anything? Idc about any data on it but id love just my stock phone working. Thanks for any help.
Click to expand...
Click to collapse
If you are still facing the problem, press & hold power + vol down button. It will turn your phone off briefly for 2-3 seconds & immediately again press & hold power + vol down button for about 5 seconds. Release it & this should take you to bootloader. And since you flashed twrp you might be familiar with pushing & flashing a rom from recovery.
I'm going to try to keep this as simple as possible as I don't really know what I did wrong or how I ended up where I am now.
I have a Samsung Galaxy 8+ and I decided to root it. I decided to follow this guy's instructions on how to do it: youtube.com/watch?v=eh-I4uxAmUY.
I follow his steps and am bought to the "Unmodified System Partition" menu after having gone through the process of factory resetting, wiping my data and using Odin to flash twrp-3.1.0-r1_dreamlteks.
The problem is that now the touch screen is unresponsive. It does literally nothing.
I am stuck at the screen that says "Keep System Read only?" where I have to "Swipe to Unlock Modifications", but find myself unable to do so because my touch screen doesn't let me swipe!
So now I'm panicking:
Firstly, I can't get the phone to shut down. Holding the power button does nothing, even if I hold it for a full minute.
Secondly, I can't boot the phone into anything except this unresponsive TWRP thing.
Thirdly, my computer no longer recognizes my phone when I try to connect it via USB (might be unrelated?).
How ****ed am I?
Is my phone just bricked now?
Can I save this rooting attempt in any way, or at least revert to the stock?
Will bringing the phone to a retailer help me in any way, or have I already broken the warranty?
Please guys I am desperate for some assistance here.
ViRALiC said:
I'm going to try to keep this as simple as possible as I don't really know what I did wrong or how I ended up where I am now.
I have a Samsung Galaxy 8+ and I decided to root it. I decided to follow this guy's instructions on how to do it: youtube.com/watch?v=eh-I4uxAmUY.
I follow his steps and am bought to the "Unmodified System Partition" menu after having gone through the process of factory resetting, wiping my data and using Odin to flash twrp-3.1.0-r1_dreamlteks.
The problem is that now the touch screen is unresponsive. It does literally nothing.
I am stuck at the screen that says "Keep System Read only?" where I have to "Swipe to Unlock Modifications", but find myself unable to do so because my touch screen doesn't let me swipe!
So now I'm panicking:
Firstly, I can't get the phone to shut down. Holding the power button does nothing, even if I hold it for a full minute.
Secondly, I can't boot the phone into anything except this unresponsive TWRP thing.
Thirdly, my computer no longer recognizes my phone when I try to connect it via USB (might be unrelated?).
How ****ed am I?
Is my phone just bricked now?
Can I save this rooting attempt in any way, or at least revert to the stock?
Will bringing the phone to a retailer help me in any way, or have I already broken the warranty?
Please guys I am desperate for some assistance here.
Click to expand...
Click to collapse
You have voided your warranty so you can't take it down to the shop and get it replaced.
It isn't fully bricked because you can still boot into an "os" that isn't fully functional. It ain't recognised because you have to swipe past this and hop into the ADB sideload interface. Btw, try holding your home button, power button and volume up (or down) and report results.
If I was you, I would wait till the battery drains and shuts off and then let it be off for the rest of the night or something and then try again.
RAZERZDAHACKER said:
You have voided your warranty so you can't take it down to the shop and get it replaced.
It isn't fully bricked because you can still boot into an "os" that isn't fully functional. It ain't recognised because you have to swipe past this and hop into the ADB sideload interface. Btw, try holding your home button, power button and volume up (or down) and report results.
If I was you, I would wait till the battery drains and shuts off and then let it be off for the rest of the night or something and then try again.
Click to expand...
Click to collapse
Alright, I'll give it until it passes out from battery loss and then get back on when things change. Thanks for the reply!