Database Develop

LG optimus 2x bootloop after failed cyanogen mod

Hello!
Today, i decided to install cyanogemmod on my 2x. So i downloaded ROM manager and downloaded cyanogenmod. everything went fine until i was going to boot for the first time. I got into a bootloop. so i tried taking out the battery and all that stuff but it still would't work. So i tried to recover the phone. I recovered it to a month old backup (I could not find the one i made in ROM manager before i installed cyanogenmod) The recovery went fine. But, when i rebooted it got into a loop on the lg logo! (the one without the loading bar) it would just load the lg logo, be there for like 10sec, then it would do the same. I tried recovering one more time, but it didn't work. The same thing happend. What should i do? :S Should i wipe data/factory reset?
EDIT: My phone was on android 2.3.4 before i download cyanogenmod.
BTW before i installed cyanogenmod, i forgot to clear cache and data. I was in a hurry so i did't notice the screen popping up, I automatically pressed "ok" without selecting anything.
Thanks for the help
- Kashif

Different partitions... Look for something called backtoext3 in the dev section (or somewhere else) The problem is that when you flash a custom rom like CM you convert your filesystem to EXT4, while stock is EXT3.
So basically what you have to do is:
1) Reboot into recovery
2) Wipe everything
3) Flash Backtoext3 zip
4) Restore Nandroid.
This should work. this will take you back to stock.

So i have to restart the phone, Choose wipe data/factory reset, then flash backtoext3 (how do i do it? lol) then restore nandroid (the backup i just tried to restore twice?)

kashi169 said:
So i have to restart the phone, Choose wipe data/factory reset, then flash backtoext3 (how do i do it? lol) then restore nandroid (the backup i just tried to restore twice?)
Click to expand...
Click to collapse
Yes
Flashing backtoext3 is just flashing the zip file you put on the sd card. (and then install zip from SD ) an then restore your nandroid stock backup and you're back on stock.
But you said you wanted to try CM right? In that case, wipe everything (factory reset/data + cache + dalvik) and then flash the CM7 rom and you have CM! Don't worry about backtoext3, your partitions are already on EXT4, because of your prior CM flash.

Ohh! Thanks Can you send the files for cm (2.3.4)? I've found some, but im not sure if my phone is compitable with them :S im really afraid to mess something up again

My. Signature. (CM7 temasek's KANG = the best CM7 at the moment )

I did everything and i got into a bootloop at the skating andriod screen again

OK, restored my phone back... Now it wont connect to the network and the battery has a question mark inside it. It also says the battery level is 999% heelp

Nvm, got my phone back to normal still dont understand why cm wont work...

You need cwm5 to flash cm.

I have a G2x, which is basically the same phone. But anyway, I would recommend nvflashing CWM and not getting it from ROM Manager.

CWM 5.0.2.0 will do just fine, but it is indeed old...
Anyway, are you sure you waited long enough on the CM boot screen? The first boot might take a couple of minutes. (4 or 5)

[Q] How to get to Recovery

So i bought this rooted int'l note off of craigslist and it had a darkynote rom on it. I tried the power+home+vol down but it just goes to download mode even if its not connected to the pc. I went into Rom Manager and hit reboot into recovery and it worked and i was able to flash the RoMow ICS rom and now it wont let me boot into recovery from there. I tried market apps to boot, but it says that my phone is not rooted. I gave Super user permissions and everything. Last thing i tried was rooting again using the method outlined in the development thread, but it got stuck and i figure that it is because i am running ICS and not gingerbread.
Can anyone give me some help on if i am trying to boot into recovery the right way or if you have a solution?
Thanks alot

Try power button, home and volume up.
Sent from my GT-N7000 using xda premium

Or use the Terminal application and type;
reboot recovery
Or, plug it into a PC with the SDK installed and type;
adb reboot recovery
Or, what Stoney said.

Thanks! The vol up+Home+Power worked.
Now im having another issue though:
I tried backing up and it got stuck when it was almost done,
same with flashing any roms and restoring from a backup... Any ideas, or should post a new thread?

Look, stop doing anything else with your RoMow ICS, because you didn't install it properly, and have a partial root as a consequence. This is a known issue: you have a semi-functional rom right now, and doing a backup of it is of no use to you.
Do the following:
1. download AbyssNote 3.9 kernel from HERE | MIRROR. It's a flashable zip.
2. put this zip on your SD Card (take out your SD card and paste the zip from your PC via a card reader if no other option is possible)
3. power off your phone
4. boot into recovery (Volume up + Home + Power)
5. chose 'install zip from SD Card'
6. navigate to your Abyss kernel zip and flash it
7. go back to the Recovery start menu
8. go to advanced/reboot recovery <--- this will reboot the phone directly to recovery
9. you will discover that you now have Hyperdroid Redpill Recovery - it comes with the Abyss kernel - it's pretty much the same thing as CWMR
10. wipe cache, dalvik, do your factory reset
11. flash any GB rom you fancy or do a GB restore if you have one

thanks so much fro your help. I had no idea that i had a partial root. I will try this when i get home. Will i have to do this with every rom i flash (flash rom then kernal) or is it just this rom?

Alright so i followed the steps and i got the red recovery and flashed the romow rom again. I went back to recovery to flash the mms fix and it went back to the blue clockworkmod recovery and once again it wont let me flash anything

kkg720 said:
Alright so i followed the steps and i got the red recovery and flashed the romow rom again. I went back to recovery to flash the mms fix and it went back to the blue clockworkmod recovery and once again it wont let me flash anything
Click to expand...
Click to collapse
I think said
11. flash any GB rom you fancy or do a GB restore if you have one
didn't I? Emphasis was on GB rom, as in Gingerbread, not ICS.
Every time you want to flash your first ICS rom, you must start from a gingerbread one.
It's no good trying to flash ICS over a botched ICS, it will get you nowhere.

chasmodo said:
I think said
11. flash any GB rom you fancy or do a GB restore if you have one
didn't I? Emphasis was on GB rom, as in Gingerbread, not ICS.
Every time you want to flash your first ICS rom, you must start from a gingerbread one.
It's no good trying to flash ICS over a botched ICS, it will get you nowhere.
Click to expand...
Click to collapse
Thanks alot. I reread the post last night and flash the darkynote rom, but the same thing happened with the recovery switching back.
Sent from my GT-N7000 using Tapatalk

kkg720 said:
Thanks alot. I reread the post last night and flash the darkynote rom, but the same thing happened with the recovery switching back.
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
obviously, there are steps you are not following quite well. the instructions above were quite very specific.
if i were you, i'd reinstall abyss 3.9, and reinstall a stock, rootable rom and start from scratch. or stick with stock.

Trying to upgrade from cyanogen 9 to cyanogen 10 now missing phone and camera apps.

I have the GT-i9000M
I did not put Cyanogen 9 on myself, the phone was given to me with it on it. I wanted to upgrade to cyanogen 10 so I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=1778526 .
"- Upgrading from CM7/CM9?
Do a Nandroid Backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon"
Did my nandroid backup obviously, wiped everything, then I went to "install zip from sdcard" picked "cm-10-20120726-UNOFFICIAL-galaxysmtd.zip" then my phone went into a reboot loop of just failing. So I went back into recover with 3 button combo and wiped everything again and restored from my nandroid backup, then when I booted back up I had no lockscreen and my phone and camera apps were gone.
What did I do wrong and how do I get those back and/or upgrade to cyanogen 10 properly?
Keep in mind this is my first time doing anything like this to my android, I was given it with cyanogen 9 on it.
Edit: Now when I try restoring from my nandroid backup and reboot all I see the is the cyanogen (mod) 9 animation boot screen forever, it never boots.

fastfreddy101 said:
Edit: Now when I try restoring from my nandroid backup and reboot all I see the is the cyanogen (mod) 9 animation boot screen forever, it never boots.
Click to expand...
Click to collapse
First i9000M is not same as I9000 http://forum.xda-developers.com/showthread.php?t=886158
so you need to check for compatibility problems
This procedure is for i9000
1. Using CWM, make sure to wipe data/factory reset, then wipe cache, and then go into advanced, and wipe the Dalvik cache too.
2. From there, flash the ROM
3. Afterwards, repeat the wipe step (step #1).
4. Continuing on, go into advanced and fix permissions.
5. Finally, reboot the device.

Thanks for the reply!
I finally got it by wiping everything and the dalvik cache, and reinstalling the zip from the SD card, got everything working now.

[Q] (Yet Another) Boot Loop Problem in Installing CM7 on GalaxyS I9000 [SOLVED]

YABLP (Yet Another Boot Loop Problem)
Hi,
I'm having a devil of a time installing CM7 on my GalaxyS I9000. Description of my procedure and problem below.
I've been beating my head against a wall for a week so any help GREATLY appreciated.
-John
Phone: Galaxy S "I9000"
Trying to Flash: CM7.2.0 using CWM Recovery
What I did:
Flash stock ROM w/ODIN v1.85 - OK
Wipe Data/Wipe Cache
Flash ChainFire (CF-Root-XX_OVA_JVU_2.3.6-v4.3-XWM3RFS.tar) w/ODIN v1.85
Wipe Data/Wipe Cache
Phone now rooted OK
Boot to CWM Recovery
Install zip from sdcard
Select update on SDCard (cm-7.2.0-galaxysmtd.zip from CM site)
Flash completes in just a few seconds - much too quick!
Phone reboots automatically
Now stuck in boot loop
Screens in boot loop:
1. GalaxyS/GTI9000/Samsung
2. GalaxyS/Cyanogen(mod)
3. CWM menu scrolls by too quickly to read
Back to 1.
Tried Heimdall but complained about missing XML file
Tried installing "Datafix". Would not install (says not compatible with device)
Tried STFW: many reports of same problem but no solutions seemed relevant & appropriate
Clues:
After CF flash, disk use as follows
/system: used 27.3M, free 9.4M (97%) (seems pretty full)
/data: used 47M, free 1916M (2%) (seems pretty empty)
Me thinks maybe /system is too small/full to accept update?
This is the 3rd I9000 I've flashed. First 2 went Ok but this time it failed although identical files/procedures used (I think).
HELP!

I've seen a similar problem on my I9000 - I think the CWM scroll complains about "can't mount /data".
I'm in a similar position, I can't get anything to flash and boot though : http://forum.xda-developers.com/showthread.php?t=1967982

This happens pretty much every time you flash any kind of CM rom from stock. All you need to do is flash CM7, it will go in to bootloop with various text scrolling through thats too fast to read. You just pull battery while in the bootloop. Then replace battery, three button combo to recovery and flash the same CM7 zip again. This time the install will take a while longer. Afterwards flash gapps and reboot and you should be good to go.

I tried this - but same result, just spins round on the CM boot screen
Where do the wipe data and wipe cache commands fit in to this? Before/after both installs?
I don't normally bother with gapps - just trying to get it loaded. Does that make a difference?
Also, no SIM card in at all during all this...

IT WORKED!
Bless you BandiBp!
I'll be sending my first-born by return mail (please don't tell my wife

Yeah that happens because its flashes a kernel with a new partition system. Dunno why only a few roms warn people about this.
Sent from my GT-I9000 using xda premium

You're welcome mate, yeah the reasons are the new partition changes on different roms. I agree that rom flashers should be warned in advance about this. Would reduce problems A LOT. My general rule is if a Rom installs in under 5 secs, then you should always flash again.
Anyways have fun.

[Q] Razr i - no possibility to flash custom rom or stock - bricked?

Hallo together,
I seem to have done something wrong while trying to flash the rom "RazRi_JB_X-2014-Jul-16".
Here is what i did:
- Unlocked to bootloader using official Motorola homepage
- Flashed CWM (non-touch) recovery using "Recovery Flasher by LeBobo v1.7", USB-Debugging was on
- Rebooted into bootloader and flashed "RAZRiRoot2" to prevent Stock-ROM from overwriting the recovery
- Tried to install the Custom ROM using CWM, but it fails to wipe cache (stuck on line "Formatting /cache")
Because it didn't work, i tried to reset everything as it was before to be able to try again - flashed stock-recovery using the Recovery Flasher by LeBobo, booted into bootloader and selected "Factory". The cell is now just showing the "Warning bootloader unlocked" warning and nothing else happens.
When i try to select the recovery in the bootloader menu, an image of a Android laying on its back with an opened hatch and a red warning symbol showing a "!" appears and nothing else happens.
I seem to have bricked my device, because i cant't really do anything now - is there any solution?
I read through different topics but could not find a real solution to this particular problem...
Thank you so much in advance for your help!

It's not bricked
At the moment u enter stock recovery with that android and red warning sy,bol, u need to press bot volume up + downp. Than it will enter stock recovery mode.
Those are the following things u can do to get custom rom,
1. Flash another recovery, cwm touch, cwm non-touch, twrp. They all work a little different.
2. Flash the custom rom and wipe everything, The wip can take some time. sometimes it will be seconds, sometimes it will take a couple of minutes. Every recovery behaves different, and every flash/wipe too.
3. enjoy
If u really want to go back to stock, flash your stock JB firmware by RSD-Lite.

Thank you very much for your answer. I restored the stock rom using RSD Lite and did a clean install of TWRP.
Then I did a Factory Reset and started to install the custom ROM.
The TWRP is now stuck at "Flashing File 1 of 1 /external_sd/RazRi_JB_X-2014-Jul-16.zip".
Is it normal that it takes more than five minutes or is something going wrong here? Is there something i forgot?

StarGeneral said:
Thank you very much for your answer. I restored the stock rom using RSD Lite and did a clean install of TWRP.
Then I did a Factory Reset and started to install the custom ROM.
The TWRP is now stuck at "Flashing File 1 of 1 /external_sd/RazRi_JB_X-2014-Jul-16.zip".
Is it normal that it takes more than five minutes or is something going wrong here? Is there something i forgot?
Click to expand...
Click to collapse
5 minutes is a bit too much. But that's the problem with this device. Every device behaves different and we haven't found out a solution too it.
At the moment i can't do much for you. I can only say try to wipe the partitions mannualy. Wipe system, data and cache. and mount system. And then try to install it. Maybe if that doesnt do the trick try again another recovery.
This from KTR-ROM
Code:
- Enter in TWRP or CWM
- Wipes required: data, system, cache y dalvik
*In CWM mount system must format before (Mount and storage -> Mount system)

Thanks again - that was it.
For some reason, TWRP did not automatically wipe the system-partition. It had to be mounted + wiped manually.
Not the custom ROM is up and running well. Installation took 35 minutes for some reason though...
Thank you so much for your help!

StarGeneral said:
Thanks again - that was it.
For some reason, TWRP did not automatically wipe the system-partition. It had to be mounted + wiped manually.
Not the custom ROM is up and running well. Installation took 35 minutes for some reason though...
Thank you so much for your help!
Click to expand...
Click to collapse
nice, glad that it worked