I rooted my n1 from frg83 using manual method (rageagainstthecage etc.) I've downloaded Rom Manager and Titanium backup and have superuser permissions Debugging and unknown sources are checked.
When I try to use rom manager to back up the current rom the phone reboots, i get the x, then a triangle with exclamation mark and android. The phone just hangs and i have to pull the battery and reboot.
The same thing happens if I boot into recovery mode and and try a backup from there. I've seen some people who say backup takes a while but I've been waiting 15 min. before pulling the battery.
Anybody got some help to offer?
Hi,
Im using Cm7.2.0 RC1.
Every night during charge my OB reboots into the recovery mode. I didn't experience this problem with Zeus 4.02b or stock rom (shipped 2.2.0 and updated V20o).
It's a PITA, cause I use my phone as my alarm clock
Is there something like an error log? Does anybody already know a solution?
Tried google and this forum, no results
I had the same problem in an entirely different device but I know of some ways to possibly fix it. Check to see if you have the cyanogenmod tenkian kernel. Do this by opening up settings and scrolling down to the very bottom and hitting about phone. My other device randomly rebooted due to a problem with a kernel. What version of clockwork mod recovery do you have? Open up rom manager and update to the latest possible recovery by hitting "flash clockwork mod" at the top. If that doesn't fix it, boot into recovery and clear/wipe data (pain but usually fixes it) clear cache partition, and clear dalvik cache, then bootup and see. You can make a "logcat" file which gives details to devs about exactly what was happening when your device went wonky. I hope this helps
Sent from my LG-P970 using XDA, or something
vagubunt said:
Hi,
Im using Cm7.2.0 RC1.
Every night during charge my OB reboots into the recovery mode. I didn't experience this problem with Zeus 4.02b or stock rom (shipped 2.2.0 and updated V20o).
It's a PITA, cause I use my phone as my alarm clock
Is there something like an error log? Does anybody already know a solution?
Tried google and this forum, no results
Click to expand...
Click to collapse
reflash the file baby or the cm7 RC1 file babe
Help! I'm a newbie at this forum , but I just a droid 3 today , and while trying to get into recovery mode , I got stuck in a continueious boot loop. D:
I Installed the rom manager , got an ics rom , installed clockwork mod etc , then went to reboot into recovery , but it would just do a normal reboot,. I then found a safestrap .apk , which was I guess a modified version of HashCodes. But when I went to reboot , it just got stuck in a boot loop. Any Ideas? I'm trying Hashcodes SBH flash or whatever to reset it to factory settings , but unfortunatly its a 500mb download. So thats gonna be an hour. Any suggestions?
Was Clockworkmod uninstalled/removed before you added Safestrap?
Sent from my DROID3 using XDA
Boot with X+Power, then both volume keys, and wipe data from withing Android Recovery. I'm not a fan of ROM Manager on the D3, it only seems to cause headaches in terms of ROM flashing.
Okay , I'll try that in a second. As SOON as I got finished with the download , the phone died. ( left it in the fastboot mode thinking it was charging...apparently not...D: ) So I will post results in about 20mins. Also , is there any other way to install roms without it?
I've done alot of ROM flashing to windows devices and just older things...and I always liked the simple installers without any problems etc. Anything like that on the Droid 3?
And no , it was installed. Haha , but with the strap , I don't think it installed completely? It kept force closing the installer right before it got to 100% ( I thought it got to 100% ). I didn't know if that was normal , or what. I couldn't open the app after that...
Now , I;m having a different issue. The phone died , and I've had it on the charger for a good 20-30mins , and it won't even go into the bootloop now. It will turn on with a battery with a question mark in it , but it won't do anything else. Help? Haha
You're moving too fast lol
Once you get your battery charged, it'll probably be best to start with a fresh SBF flash (an SBF that is appropriate for your phone, of course).
Then root with one of the many tools mentioned in the development forum
Then install the safestrap app, then run it, and hit the install button. It will say in the safestrap app if the safestrap recovery has been installed (the first line in the app window, I believe)
If safestrap doesn't say that it installed (in that first line), you may have to separately install Busybox installer (its free in the android market). Then you can try to hit the install button in safestrap again.
With safestrap installed, you can restart phone.. you should see the safestrap splashscreen on bootup - hit Menu to go into safestrap recovery.
In safestrap recovery, it will be in non-safe mode (your phone's current stock rom).
Use the volup/voldown button to navigate, and power button to select.
Go to the safe menu, and hit toggle safe zone (or whatever its called)
It will move the necessary stuff and get you into the safe zone. Once that's done, there will be no rom on it yet, so you can then install a custom rom from zip.
Hope this helps
DreadCode said:
Now , I;m having a different issue. The phone died , and I've had it on the charger for a good 20-30mins , and it won't even go into the bootloop now. It will turn on with a battery with a question mark in it , but it won't do anything else. Help? Haha
Click to expand...
Click to collapse
The phone does not charge when it hasn't booted. You're gonna have to buy or jerry-rig a usb battery charger. You can take any old USB cable, strip the wires, and tape the black wire to the (-) terminal on the battery, and tape the red wire to the (+) terminal on the battery. Charge the battery for a maximum of 3 hours.
Sent from my DROID3 using XDA
Thank you Chatoic* I did that last night after I realized the battery didn't charge. Then flashed a new SBH etc. Rooting worked fine , and now I get to the menu just fine on bootup. But now I'm having another issue. I go to Rom Manager , and try to install my AOKP ICS from the SD card , but when It reboots and goes to the menu etc , I don't know what to do to install it. It makes a backup I think? But doesn't install the ROM. Sooo any Ideas? Am I missing a file or something on the sd card? And it says Error partitioning the SD card with a backup etc...
IMO, ROM Manager only causes way more headaches than it fixes, at least on the D3. I would recommend a folder simply called AAAZips (This is what I use, it keeps it at the top for less/no scrolling in Boot/SafeStrap) on your external SD card. Then install either SafeStrap or BootStrap, as you prefer, and reboot into recovery this way to backup/flash/wipe/etc.
Moral of this, IMO, ditch ROM Manager.
redsox985 said:
IMO, ROM Manager only causes way more headaches than it fixes, at least on the D3. I would recommend a folder simply called AAAZips (This is what I use, it keeps it at the top for less/no scrolling in Boot/SafeStrap) on your external SD card. Then install either SafeStrap or BootStrap, as you prefer, and reboot into recovery this way to backup/flash/wipe/etc.
Moral of this, IMO, ditch ROM Manager.
Click to expand...
Click to collapse
Lol. Mine is called Aisthefirstletter
Sent from my XT860 using xda premium
Then I just boot into recovery and do what to install the .zip?
And what do I put in the AAAzip folder?
Nevermind I think I got it working. WAY better then rom manager.....
I'm glad it's working. It may not be as nicely polished as ROM Manager, but flashing through CWM/SS from SD card seems to work better.
DreadCode said:
Help! I'm a newbie at this forum , but I just a droid 3 today , and while trying to get into recovery mode , I got stuck in a continueious boot loop. D:
I Installed the rom manager , got an ics rom , installed clockwork mod etc , then went to reboot into recovery , but it would just do a normal reboot,. I then found a safestrap .apk , which was I guess a modified version of HashCodes. But when I went to reboot , it just got stuck in a boot loop. Any Ideas? I'm trying Hashcodes SBH flash or whatever to reset it to factory settings , but unfortunatly its a 500mb download. So thats gonna be an hour. Any suggestions?
Click to expand...
Click to collapse
I'm noticing that the modded safestrap kicks me out of safe mode when flashing and then causes me to bootloop, maybe because of a problem w/the flash related to kicking me out of safe mode or something. Try hashcodes safestrap apk from his blog site and see if you have any more luck with that.
I have been using RemICS 1.3 with Semaphore kernel on my phone for a few months. I had a few problems with bootloop at first, which was solved completely after i flashed the Semaphore kernel and my phone has been running smoothly ever since.
However, today my phone started freezing and giving errors out of nowhere. I open a simple application like alarm clock and it says the application is stopped. I was only be able to open a few applications. So, I rebooted the phone thinking it would go back to normal. Unfortunately, rebooting revealed that my phone no longer can boot. It passes the kernel screen, goes to the RemICS animation and gets stuck there. Since I could go into Recovery Mode I have tried to restore from the backup I had from 10 days ago when my phone was running perfectly. Did not work. I had another backup from July, did not work, actually made things worse by stucking my phone at Samsung screen. Wiped cache, Wiped dalvik cache, did not work.. Made things worse by putting my phone into loop boot. I have tried flashing Devil kernel and another version of Semaphore kernel. Did not work.. Phone back into being stuck at RemICS logo.
Nothing I do seems to work. It just won't boot. I could try flashing a fresh firmware but I have some info on my memo application that i need to save as well as some text messages.
I really don't know how this happened out of nowhere. How can I save my data? Please help?
I've tried lots of ROMs, and been stuck in boot loops many times.
I've always got out of them by using Odin, and trying different kernels until one works, semaphore, devil, and an old GB one. Out of all the boot loops I've been stuck in there's never been a single time that one of those kernels hasn't worked...
Maybe I've just been lucky??
Edit: on reading again tho it looks to me that its your ROM that is the problem not the kernel.
I recommend using SMS Backup+ (free) from the play store next time
Sent from my GT-I9000 using Tapatalk 2
I would have never thought that I could brick my device without... doing something wrong. Here I come, completely helpless at this point.
Earlied today the phone had worked just fine until I turned 3G on, it wouldn't actually turn it on. I tried Aeroplane mode which didn't help, so I held power button and chose to reboot. This is when the problem starts. The phone booted itself successfully through its logo, then Devilkernel logo, and lastly showed the GamerzROM logo (which is actually the Nexus logo) and kept showing this flashing logo forever. Even after 30 minutes.
CWM works just fine.
I noticed that while booting it makes a single loop (Samsung logo -> Devil logo -> Samsung logo -> Devil logo -> Nexus logo).
I've wiped partition cache and dalvik, put the ROM and Gapps on external sd and flashed again. Nothing changed.
I am also worried about the battery - when I plug the charger the device turn on (the way mentioned above) and I have no idea whether it's charging or not, at the moment I am at 24% of battery so it's risky to flash without a charge.
Please, I need some advice to fix this, without loosing my data on the phone. I could flash another ROM, but that obviously means data/factory reset.
Thank you in advance!
EDIT: I've just checked in CMW and the phone is actually charging. Battery percentage rose up.
Have you tried to return to stock ROM ?
Sent from my GT-I9000 using xda app-developers app
I've made a nandroid backup to a external SD and wiped data. The phone "amazingly" works, although I've lost all my configuration and data (maybe I'll retrieve it somehow from the backup files).
Must have been corrupted files or something.
Hmmm im running gamerzrom too since first day and i didnt have anything like this.
Did you change/update kernel?
Sent from my GT-I9000 using xda app-developers app
Nope, I didn't touch anything. Just changed the DPI once I flashed the ROM.
Well I couldn't have said a bad word about GamerzROM until yesterday's incident.
Hope it never happens again.