So, I rooted last night using Pete's Motorola Root Tools. Worked perfectly, I had root, and was enjoying drocap2 and a few other root apps.
Well, I downloaded Rom Manager (already had Premium) and downloaded Cyanogen Mod 7.1, the only stable release listed for my phone. I downloaded it, and went to install it, and that's when it got stuck at the Motorola logo screen.
I backed up everything - so that shouldn't be a problem. But the phone won't turn on at all. No matter how long I hold down the power button. If I charge the phone the Motorola logo comes on, but it stays on even when I unplug the phone, and then I have to pull the battery.
Any ideas on what I can do?
simply use the available sbf to recover back to working state.
do not use rom manager, it is not fully compatible with d2g. read in the forums how to get CM working on your phone, not all of it works though..
Sent from my BlackBerry Runtime for Android Apps using Tapatalk
If you haven't SBFed, look at my thread and do steps 9-11 first and see if it fixes the problem.
http://forum.xda-developers.com/showthread.php?t=1060694
Related
(Well, this is embarrassing.)
(yes, I read older threads before making this.)
I recently rooted my admire; I decided to install rom manager and Busybox, however, when rom manager was installed (I figured that I could get flashed roms) When I begun to install CWM recovery 7.0.3 from rom manager, i chose "other". It installed, and it told me to reboot. So, i turned it off and was going to turn it back on. Nothing. Recovery mode, Download mode. Nothing. Phone stays off, never turns back on, as if it was dead. I'm not sure if it did enter DL mode, because I heard that it would still be in download mode, even if the screen was off. My battery still charges(?) when i plug it in. (The battery heats up, no charging screen, or boot.) Any fix?
To recap; Samsung admire. Rooted recently. Root manager installed. Cwm recovery 7.0.3 downloaded. Installed. Tried to reboot. Hard brick.
Biffalothethird said:
(Well, this is embarrassing.)
(yes, I read older threads before making this.)
I recently rooted my admire; I decided to install rom manager and Busybox, however, when rom manager was installed (I figured that I could get flashed roms) When I begun to install CWM recovery 7.0.3 from rom manager, i chose "other". It installed, and it told me to reboot. So, i turned it off and was going to turn it back on. Nothing. Recovery mode, Download mode. Nothing. Phone stays off, never turns back on, as if it was dead. I'm not sure if it did enter DL mode, because I heard that it would still be in download mode, even if the screen was off. My battery still charges(?) when i plug it in. (The battery heats up, no charging screen, or boot.) Any fix?
To recap; Samsung admire. Rooted recently. Root manager installed. Cwm recovery 7.0.3 downloaded. Installed. Tried to reboot. Hard brick.
Click to expand...
Click to collapse
dude i did the same exact thing except when i tried to upload a rom from my sd card,cwm rebooted my admire and it never cut bak on, im been up all nigh
t tryin to unbrick still havent got it to unbrick,but it still charge so dats a plus.
I pulled my vortex out of storage the other day to tinker. It was rooted but fully updated stock 2.2.2
When I booted it up, it stayed on the boot animation 20+ minutes, until the battery ran out. I've tried booting it up again but it keeps bootlooping.
I figured I'd just flash a new ROM onto it, but I never put a custom recovery onto it and the only Vortex Recovery I found was this;
http://androidforums.com/getitnowmarketing/330813-all-one-recovery-thread.html
However, it says I need to do on-device commands and stuff to get it working, which obviously isn't an option.
Is there any other way you guys could think to resurrect my old Vortex? My Droid Charge is my phone now, this thing doesn't get much use anymore, but I'd still like to get it back in a usable form.
EDIT: FYI, already tried everything relevant in this thread: http://forum.xda-developers.com/showthread.php?t=1031596
If you flashed stock rom. Try hard reset.
Home+vol down / vol up+ power.
thank you! that button trick did the job!
EDIT:
well, it worked once, but the phone had been uncharged for a while so the battery died, and now i can't get the trick to work again >_<
is there a way to re-flash stock without a custom recovery?
I have the nexus s 4g flashed to boost mobile. it has ran great for over a year now. i have flashed many roms and kernals to it and it has worked like a charm with only the occational hickup. but a few weeks ago when i would power it down and change may battery it would start to get stuck on the google screen. i could pull the battery a few times and it would eventually take off and work fine for a few day and then do it again. this last time it done it i cant get it to go past the google screen for nothing. i can get into the fast boot mode and also into clockworkmod touch recovery but when i go into flash zip from sd it say error loading sd, when i plug it into my computer it conects when in fastboot but i cannot access my sd memory at all. i tried the pdanet but it wont work due to no access to the sd. i downloaded the program wugs nexus tool kit and tried to flash stock and unroot with option bootloop / soft-brick in my boot loader. the program seems like it is working, it takes control of my phone restarts bootloader a few times then says restarting your now stock phone, but my phone just sits in bootloader. i have tried to manually reboot system and it just goes to the google screen and stops. when i power on my phone the google logo comes up, flashes away for a split second then pops back up with the leds at the bottom of my phone on this time but thats all i can get. please help i dont know what to try next. let me know if any of you have had this problem before and what you did to get it fixed. Please help i miss my Nexus...
** UPDATE *** Well i havnt really given up on my Nexus but i gave in and bought a new Galaxy S II so i could have a working smart phone again. Ill still be working on the Nexus in my spare time so ill update if i have any luck.
Sent from my SPH-D710 Galaxy S II running Crossbones JB ROM with matrix using xda app-developers app
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
addamT989 said:
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
Click to expand...
Click to collapse
Try flash a stock firmware by using flashtool, it will work 100%:angel:
revernwe therefore
addamT989 said:
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
Click to expand...
Click to collapse
hi,
can 'be that your device has some residual old. Do as you have advised. install a stock rom and firmware, so it becomes a new cell phone. After odin starts TWRP (much better) and root.
I would flash a complete bone stock Rom using Odin and start over. Also rom manager was highly discouraged on the AT&T version of the s2 so I don't know what the stance is on T-Mobile's version
Sent from my CLEAN Note ll
brandonarev said:
I would flash a complete bone stock Rom using Odin and start over. Also rom manager was highly discouraged on the AT&T version of the s2 so I don't know what the stance is on T-Mobile's version
Sent from my CLEAN Note ll
Click to expand...
Click to collapse
Thanks for the advice! Should i flash it back to ICS then try to root again via Odin before i upgrade back to JB? I'm guessing there's something that isn't getting wiped. Since i can run CWM and Root with Odin without a hitch. it's the initial reboot after all that is done that I go into the boot loop.
tainiun rioters
pierm said:
hi,
can 'be that your device has some residual old. Do as you have advised. install a stock rom and firmware, so it becomes a new cell phone. After odin starts TWRP (much better) and root.
Click to expand...
Click to collapse
Sorry for my ignorrance, what exactly is TWRP, and is it now on there because i used Odin and it installed it automaticly? And do i want to use this vice CWM?
One more question...before i try all this, can i backup everything on Kies just like i would be able to with CWM and reinstall if my root fails again? I've only used Kies for firmware upgrade, never to reinstall a backed up copy of my phone.
Thanks!
addamT989 said:
Sorry for my ignorrance, what exactly is TWRP, and is it now on there because i used Odin and it installed it automaticly? And do i want to use this vice CWM?
Click to expand...
Click to collapse
addamT989 said:
One more question...before i try all this, can i backup everything on Kies just like i would be able to with CWM and reinstall if my root fails again? I've only used Kies for firmware upgrade, never to reinstall a backed up copy of my phone.
Thanks!
Click to expand...
Click to collapse
Hi
TWRP and the 'one touch recovery, better than CWM.
The backup kies can not recover from CWM
steps:
install odin, after recovery, nandroid backup, ROM, and root.
hi
Flash the stock firmware using odin!!..it will work!
Sent from my GT-N7100 using xda premium
freezes then booted
Hello I have this problem with my galaxy s2 i9100. After reboot the phone wasn't booting something like "boot loop" so I re flashed the firmware and now the phone boots up but after the boot it freezes immediately. So I decided to install clock work mod recovery and install cyanogen mode 11 with cyanogen mode the phone boots up and are able to be used again until the screen goes to sleep mode or the power button is pressed then the screen goes black and doesn't turn on after long pressing the power button it reboots. So I don't know what else to do I have tried kernels, operating systems re flashing reseting and nothing helps. No need to tel me to do resettings. Also my galaxy s2 i9100 chip has insane chip bug but I don't know if it has to do something with my problem.
Phone: Sony xperia j st26i
Firmware version: 11.2.A.0.33
Okay heres the deal, i recently rooted my phone, i installed rom manager pro. busy box, supersu pro,
after i installed those, i decided to get a clock work mod for my phone to, so i did of course.
after i got the CWM, i went to rom manager and installed a font called loco, and then my phone restarted and
wont turn back on, i have tried every thing possbile, im not stupid.
I wan wondering if you guys could help? because i am out of options. and i am stuck here.
the phone will turn on, show me the charging screen (even when its not charging) and turn off in like 2 seconds.
And please no common sence questions. ive already tried,
taking out sd card, removing battery, charging for hours, holding power button
etc...
KingLegionnare said:
Phone: Sony xperia j st26i
Firmware version: 11.2.A.0.33
Okay heres the deal, i recently rooted my phone, i installed rom manager pro. busy box, supersu pro,
after i installed those, i decided to get a clock work mod for my phone to, so i did of course.
after i got the CWM, i went to rom manager and installed a font called loco, and then my phone restarted and
wont turn back on, i have tried every thing possbile, im not stupid.
I wan wondering if you guys could help? because i am out of options. and i am stuck here.
the phone will turn on, show me the charging screen (even when its not charging) and turn off in like 2 seconds.
And please no common sence questions. ive already tried,
taking out sd card, removing battery, charging for hours, holding power button
etc...
Click to expand...
Click to collapse
Your Phone is possibly bricked... Download xperia flash tool and custom rom of your device and flash it....
Just download from goo.gl / 4De1UL ( Ive just left some spaces as xda wont allow me... )