mkay o i'm kind of new to android and tonight i wet my pants cause i thoughy i bricked the optimus. I wanted to install CM7 but something went horribly wrong.
After I rooted and installed ROM manager I copied CM7 to my SD and installed. After it was done the CM7 boot screen kept looping. No way the phone was doing anything more than that.
The only other thing it would do was to sho a 'waiting for update' screen. After a lot of searching I mangaged to get stock ROM back by using smartflash, praise be...
Now that I know I can rescue the phone I'd like to know what whent wrong..any clues? Did I use the wrong build of CM7? I just used the latest of the 4th of july.
I want to try again but maybe some insight would be helpful, thanks...
Did you remember to tick the wipe data box in ROM Manager?
Well it would not install from rom
Manager (installation canceled by itself and ennded up with fresh install of LG rom...) so after that i did it from recovery. cant remember if i got the option to wjpe in there...
So when i installed from ROM manager i did xheck the wipe boxes. Then started installing from SD. The installation stopped, i have seen some sort of warning exclamation but i could not read what was wrong the message disappeared too fast. I think the 'wipe' was sucssesful though because all my apps and settings for stock LG firmaware were back to factory.
Ah ha.
ROM Manager and the stock ROM don't get on too well. Boot to recovery, wipe and install from there.
Assume you are using CWM recovery? It has the option to wipe on there if you look carefully so you can wipe it manually before flashing.
I tried again and it seems GB is now running cause I can see the battery icon on a different angle but it keeps givin me LG installation error messages after boot which i may ' forrxe close' but basicly nothing happens. Did i forget to wipe somerhing or forget to do smth else?
What recovery are you using? If it's 4.0.0.5, you might want to update to the newest 4.0.0.5, as the original one I built had some problems formatting.
The error messagel all seem to refer to LG apps or services. Device wont go beyond these messages.
I know, if it's what I'm thinking, they will have been left behind during the CM install, which shouldn't happen.
Ok so what do you think i should do? thanks for the snappy replies rusty.
Fyi, behind the error messages i can see a black background. The top bar with battery indicator is present, it charging. Signal indicator is there but has no signal.
Change recovery and flash again, either to 3.2.0.0 or the newest 4.0.0.5
this is what it looks like now. When i switch off and do volume down+ power its says waiting for S/W upgrade.
First i need to re-install syock again i guess? Wont do much else..
If you're getting software upgrade, you're letting go of power to early, keep em both held.
Edit: Or use 'adb reboot recovery'
hmkay im in recovery now thanks for that. It says 3.0.2.8
Signarure check enabled
Signature check disabled
Script asserts eneabled
Im not quite sure what you want me to do now. Thanks for your patience
Oh, 3.0.2.8 shouldn't have had any problems then, annoying.
Still, pik the wipe data/cache option, then install CM7
Im there thanks so much Rusty.
Related
Everybody says this app is great but every time I try to do anything with it, it reboots my phone to a green progress bar but before it finished it switches to a picture of a phone with a red question mark on it....am I doing something wrong? I wrote the devs with no response
~ SykosouL~ d-_-b
SykosouL said:
Everybody says this app is great but every time I try to do anything with it, it reboots my phone to a green progress bar but before it finished it switches to a picture of a phone with a red question mark on it....am I doing something wrong? I wrote the devs with no response
~ SykosouL~ d-_-b
Click to expand...
Click to collapse
Have you flashed the engineering rom? You need to do that.
Oh ok....I didn't know you had to flash that for it to work thanx so much for the help...they should tell you that on the app
~ SykosouL~ d-_-b
SykosouL said:
Oh ok....I didn't know you had to flash that for it to work thanx so much for the help...they should tell you that on the app
~ SykosouL~ d-_-b
Click to expand...
Click to collapse
ROM Manager is for every device that can run clockworkmod recovery, not just the slide. The slide is the only one that can't get a recovery to stick as far as I am aware, so there's no reason for them to include a warning in an app used by tons of devices when only one of them has the issue.
True...didn't look at it that way
~ SykosouL~ d-_-b
I have a stupid ROM Manager question... I remember trying to use a while back and hit a snag. When you open it, it first wants you to install Clockwork Recovery, and of course we cant make ours stick. When I tried this a while back, I remember it breaking my recovery and took some fiddling to fix it. Should I let it run this option, so I can then use it to manage my ROMs?
fermunky said:
I have a stupid ROM Manager question... I remember trying to use a while back and hit a snag. When you open it, it first wants you to install Clockwork Recovery, and of course we cant make ours stick. When I tried this a while back, I remember it breaking my recovery and took some fiddling to fix it. Should I let it run this option, so I can then use it to manage my ROMs?
Click to expand...
Click to collapse
It now has a recovery for the slide and it works great. It is the only I use to get in recovery.
So to be clear, I can use the Install CWR option from ROM Manager? I cannot do anything else in ROM manager without it wanting to "install" it.
on mine it is the first option "Flash ClockworkMod Recovery", pop-up will show up and it only has the choice of "MyTouch Slide" after tapping that you are good-to-go for rebooting into recovery and flashing ROM's
Yeah I went ahead and did it. I get a lot of Superuser FCs still with it. I even hit the Fix Permissions, which says may fix FCs, and it FCs on me
that's odd I am running it on both of our phones without issue, didn't even have any issues running dumfuq's experimental dopio 960 oc kernel.
I see what happened. Cyans latest ROM comes with a different/newer SU app. When Rom Manager flashed recovery, it downgraded SU. I just grabbed the SU out of the latest CM6 ROM and pushed it to system in recovery and all is good. Running Fix Permissions now to see if it stops the FC I get on some uploader service upon each boot.
oh I forgot, unless you have already figured it out, the power button is NOT used for selecting in cwm anymore... volume still does "up" and "down", track-pad is now "select" and the back button works as "back page"
hopefully all is good.
So, Rom Manager can get you directly to Clockworkmod?
I just got a new Slide, rooted it, and immediately flashed the ENG build.
I then flashed MyFroYo6 with Rom Manager. No dice. What the hell am I doing wrong?
2 nights ago I thought I would have a go at installing ULTIMATE ROM 3.0. I have flashed many Roms on my Galaxy S before and not had a problem yet. I have ClockworkMod Recovery 2.5.1.0 installed.
However, this time- something went wrong. I don't think the installation completed properly. When I tried to reboot the system (to go back into my previous ROM) I wasn't able to. The Samsung logo appeared before the phone booted back into Recovery mode.
I tried to re-flash my previous working update.zip but had problems. I wasn't able to properly re-flash as the Installation would abort for various reasons. After doing cache clearing and data/factory reset I still had no luck. I resorted to reformatting the sdcard. Still didn't solve the flashing problem.
Throughout the whole time I was able to adb into the phone, browse the file system and I could push files on to it and take files off. But Kies wouldn't recognise the phone and Odin isn't able to complete a transfer to the phone (not sure why).
Today, I am able to successfully flash update.zip files (at least, that's what it looks like) but the phone ALWAYS boots into ClockwordMod recovery.
I am fast running out of ideas. Does anyone have any suggestion?
How can I tell if my ROMs are really 'there' but I can't access them because ClockworkMod is preventing them from booting?
hmmm... me too.. stuck in a loop, that keeps going back to the CWM recovery menu, and no matter what i do, keeps going back to it... cant even get to the download screen to flash (again).... here i was thinking no matter what happens when installing custom roms, i can always flash to my stable secure rom, but not this time... need some software that can perform surgical operations, any suggestions?
bradels said:
2 nights ago I thought I would have a go at installing ULTIMATE ROM 3.0. I have flashed many Roms on my Galaxy S before and not had a problem yet. I have ClockworkMod Recovery 2.5.1.0 installed.
However, this time- something went wrong. I don't think the installation completed properly. When I tried to reboot the system (to go back into my previous ROM) I wasn't able to. The Samsung logo appeared before the phone booted back into Recovery mode.
I tried to re-flash my previous working update.zip but had problems. I wasn't able to properly re-flash as the Installation would abort for various reasons. After doing cache clearing and data/factory reset I still had no luck. I resorted to reformatting the sdcard. Still didn't solve the flashing problem.
Throughout the whole time I was able to adb into the phone, browse the file system and I could push files on to it and take files off. But Kies wouldn't recognise the phone and Odin isn't able to complete a transfer to the phone (not sure why).
Today, I am able to successfully flash update.zip files (at least, that's what it looks like) but the phone ALWAYS boots into ClockwordMod recovery.
I am fast running out of ideas. Does anyone have any suggestion?
How can I tell if my ROMs are really 'there' but I can't access them because ClockworkMod is preventing them from booting?
Click to expand...
Click to collapse
myrobelle said:
hmmm... me too.. stuck in a loop, that keeps going back to the CWM recovery menu, and no matter what i do, keeps going back to it... cant even get to the download screen to flash (again).... here i was thinking no matter what happens when installing custom roms, i can always flash to my stable secure rom, but not this time... need some software that can perform surgical operations, any suggestions?
Click to expand...
Click to collapse
Thats too bad guys,and i m sorry to hear that news.I would like to havean answer but i dont...
The fact is that since most people in this forum use some custom roms,and all of us think the same,that we can always go back,so it would be great if you give some more details about what happened to you,and mybe why it went wrong,and it would be even better if one of the BIG guys would give some explanation about this...
I already thinking of not updating my rom anymore,dot want to end up in looping too,so lets see if someone will find something.Good luck guys..
By the way,i didnt get it right,CWM recovery cannot load your backup????
I just got an idea,but not sure if or how it would work or not.
Since you can push file with ADB,if soeone made a clean backup with his CWM (o e mail,contacts,setting saved) and send it to you,so that you log in with CWM recovery and flash that ???
Just an idea..maybe stupid dont know...
Its not very clear if youve tried this already but cant you just boot into recovery through adb? or does that not work either?
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.
Well, i wanted to change my rom, CM 7.2, with DjangoManouche 1.2 and used the rom below..i backed up, and when i started flashing, it said that"this is not a ROM"..i..kind of panicked and after a minute, when i seen "nothing moves" i removed the battery. When i tried to start the phone, it only shows the LG logo..but does not boot(i waited for just 1-2 minutes..). I hope someone could help me.
xdafileserver.nl/Files/LG/Optimus%202x%20(P990)/ROMS/DjangoManouche%20ROM/1.2/1.2ROMS/DjangoManouche1.2WipeEXT3Stock.zip
Mitzu' said:
Well, i wanted to change my rom, CM 7.2, with DjangoManouche 1.2 and used the rom below..i backed up, and when i started flashing, it said that"this is not a ROM"..i..kind of panicked and after a minute, when i seen "nothing moves" i removed the battery. When i tried to start the phone, it only shows the LG logo..but does not boot(i waited for just 1-2 minutes..). I hope someone could help me.
xdafileserver.nl/Files/LG/Optimus%202x%20(P990)/ROMS/DjangoManouche%20ROM/1.2/1.2ROMS/DjangoManouche1.2WipeEXT3Stock.zip
Click to expand...
Click to collapse
I recall reading something about using NVFlash to force the stock rom on and allowing to recover from a bricking.
I'll defer to someone with experience in fixing bricked phones though.
Thank you...now..it wont even start, even when i plug-in the charger..it had pretty low battery..i am pretty ducked..
You have to reflash it with KDZ recovery method. Look up google and you'll get it working. I did this the first time too (what a bad joke to say "this is not a ROM")...
I'm sure you can still enter Cwm if you hold down volume- while pressing power button until it the Cwm menu appears.
Sent from my Optimus 2X using xda premium
First of all, don't worry, O2X is pretty unbrickable...at least in the level you're messing with it!
If you have recovery installed, you should be able to reboot into recovery : press and hold vol down button, then power button until you see blue halo of LG. before that, download another ROM and put it in your external SDcard. Flash that ROM.
You can also download and flash the original firmware of LG by using smartflash. You can find those in ANDROID DEVELOPMENT section!
Also check KDZ recovery!!
Thank you..it worked with recovery mode..i had back-ups. I got a bit scared because when i pressed vol_dwn+ shut down button..after i release the 2nd button, it turned off...but i menaged to make it. Again, thank you for help.
====================
well, today i tried again to install a new rom(temasek's cm7 last build)..but i couldn't..after it is installed it get's into boot and stays like that..i tried to AOKP and it worked..my backup also worked...i just can't get it, why these roms won't work?
Mitzu' said:
well, today i tried again to install a new rom(temasek's cm7 last build)..but i couldn't..after it is installed it get's into boot and stays like that..i tried to AOKP and it worked..my backup also worked...i just can't get it, why these roms won't work?
Click to expand...
Click to collapse
The common mistake for new people is that they restore entire nandroid backup after flashing ROM. CWM doesn't have option to backup DATA only, so you have to restore DATA from nandroid backup using Titanium Backup etc.
Try this:
1. Restore into fully functioning ROM(+data) if you don't have already
2. Reboot to recovery
3. Format /system
4. Flash new ROM
5. Clear cache and dalvik cache
6. Check if phone successfully boots
7. Flash Gapps if needed.
8. DO NOT DO ANY RESTORES AFTER STEP 1!!
9. If it doesn't work out, try another ROM. There may be some error with the file!!
I've been looking all over this site but I can't find anything. I suppose that it's partly because I'm not sure about the problem myself.
A couple of months back (maybe more) I upgraded to the ICS infinitum rom (blue version) with midnight kernel. It was great - the phone worked fine. Well I'm exaggerating, it ****ed up every once in a while. Programs would automatically shut down and it would get really slow after a while. But all in all it wasn't bad, and it was stable enough for me most of the time....
Then, last Thursday everything seemed to go apart, every program on the phone was shutting down. So I thought I'll just restart and it will be fine. When I did, the phone did not come back on. the kernel would load and then it was stuck on the start-up animation in infinite loops.
Now, to be frank, this isn't the first time this has happened. So I didn't panic. Last time I just used the CMW recovery to re-install the kernel and the rom (I keep the files on the sd card). But this time, I wanted to try to avoid the factory wipe for as long as I could, and try finding a different option, knowing that if all else fails, I have something to revert back to.
Then I did the mistake of deleting the init.d file without re-installing anything. I wanted to, but accidentally clicked on the 'reboot now' option. And then all went to ****. The kernel didn't load. I went to recovery and it couldn't mount the sd card so I couldn't re-install it.
I tried flashing a new kernel using odin, and it did get me a bit better: my CWM recovery can read the sd. However, I still can't mount the system. Even worse, when I get to the infinitum zip roms and re-installing it brings up the status 7 error (which, after searching, seems to come up for different reasons for each person)
Despite installing a new kernel, when I reboot the phone now it doesn't load the kernel anymore, it just stays stuck on the welcome screen. I tried using the recovery to re-install a different kernel, it worked, but the phone still won't start - it now automatically skips to the recovery mode. I don't know if I should try flashing a rom through odin, and I'm too afraid to try anything at all now...
Can anyone help me? Is there any way to restore the init.d file or maybe that has nothing to do with my problem?
uvii said:
I've been looking all over this site but I can't find anything. I suppose that it's partly because I'm not sure about the problem myself.
A couple of months back (maybe more) I upgraded to the ICS infinitum rom (blue version) with midnight kernel. It was great - the phone worked fine. Well I'm exaggerating, it ****ed up every once in a while. Programs would automatically shut down and it would get really slow after a while. But all in all it wasn't bad, and it was stable enough for me most of the time....
Then, last Thursday everything seemed to go apart, every program on the phone was shutting down. So I thought I'll just restart and it will be fine. When I did, the phone did not come back on. the kernel would load and then it was stuck on the start-up animation in infinite loops.
Now, to be frank, this isn't the first time this has happened. So I didn't panic. Last time I just used the CMW recovery to re-install the kernel and the rom (I keep the files on the sd card). But this time, I wanted to try to avoid the factory wipe for as long as I could, and try finding a different option, knowing that if all else fails, I have something to revert back to.
Then I did the mistake of deleting the init.d file without re-installing anything. I wanted to, but accidentally clicked on the 'reboot now' option. And then all went to ****. The kernel didn't load. I went to recovery and it couldn't mount the sd card so I couldn't re-install it.
I tried flashing a new kernel using odin, and it did get me a bit better: my CWM recovery can read the sd. However, I still can't mount the system. Even worse, when I get to the infinitum zip roms and re-installing it brings up the status 7 error (which, after searching, seems to come up for different reasons for each person)
Despite installing a new kernel, when I reboot the phone now it doesn't load the kernel anymore, it just stays stuck on the welcome screen. I tried using the recovery to re-install a different kernel, it worked, but the phone still won't start - it now automatically skips to the recovery mode. I don't know if I should try flashing a rom through odin, and I'm too afraid to try anything at all now...
Can anyone help me? Is there any way to restore the init.d file or maybe that has nothing to do with my problem?
Click to expand...
Click to collapse
I suggest flash 3-file GB rom via odin with ticked re-partirion and phone bootloaderupdate.
First of all init.d has nothing to do with the boot of kernel and ROM itself. It's just like autostart in Windows, so if it's missing it shouldn't cause problems.
My solution is to flash a complete stock Gingerbread ROM using Odin. You can get them at sammobile.com. Then afterwards flash a custom kernel and then whatever you like.
If you need help,feel free to ask me
Sent from my Gameboy Color
Yes! Thank you! That worked!!
It happened again! just 10 days later.
Is the Infinidtum rom ****ed up in any way?
it's stuck on the loading part of the rom