I'm on the Koodo Optimus One (P500h)
Method used was:
1. Kdz updater 2.2.1 -> 2.2 (telus firmware) [Success]
2. Z4root -> Permanent [Success]
3. Installed the Desirelle recovery [Success]
4. Made a nand .secure recovery [Success]
5. Flash Rom ->CM7 and gapps ported from Mik_os [Success]
I initially had CM7 running perfectly fine, but then I decided to go back to stock 2.2.
Now I want to go back to CM7 due to the performance... so I proceed to..
6. Wiped Data/Cache
7. Flashed CM7 + Gapps
8. Booted into LG logo..stuck
9. typed in the instructions per mik_os "mount /system"adb shell rm -rf ..." rebooted, and still nothing...
10. Tried wiping data + cache and flashing CM7 + gapps again, but still can't boot in!
Someone please help!
Fixed... the system didn't clear the data/cache so I flashed the zip file the mik_os provided for boot loop issues.
Kinda shocked nobody helped you, but glad you got it fixed by yourself
Related
I'm working with my new (from woot) Viewsonic G Tablet.
I managed to flash clockwork recovery (v .8) with little to no trouble. However, I am having some difficulty flashing a custom ROM. I have tried several different versions, including many of the ones posted on this forum.
Whenever I try, clockwork says that the install completed, but when I reboot it hangs at the Viewsonic bird-logo screen. After about 25 minutes I give up, reboot. It happens again. I reboot into clockwork and restore to stock and it works fine. I don't think I'm missing a step, but I'm pleading for help.
From clockworkmod -- Wipe Data, Cache, and Dalvik Cache. Repartition sdcard to 2048 and 0. The repartition will format your user partition, so back up any data to an external source that you don't want to lose.
Re-flash ROM of choice, hopefully boot all the way, if not then try wiping data again after flash and then fix permissions from clockworkmod.
I'll give it a shot!
Sent from my HTC Vision using XDA App
No luck.
My steps:
1) Shut down
2) Boot into recovery (hold the vol+ and power)
3) Wipe data/factory reset
4) Wipe cache
5) advanced, wipe Dalvik
6) advanced, partition sdcard 2048, 0
7) mount usb, copy rom & gapps over (both from xda with reports of success)
8) install zip from sd (CorwinCM7RC4Beta.zip)
9) install zip from sd ( gapps-gb-20110307-signed.zip)
10) re-wipe data
11) rewipe cache
12) rewipe dalvik
13) fix permissions
14) boot & freezes at the birds
Sent from my HTC Vision using XDA App
Can you flash a stock rom like 3588 and see if that boots?
Stock roms are here:
http://forum.xda-developers.com/showthread.php?t=842000
They have to be flashed with stock recovery, not clockworkmod.
I would probably use nvflash to get a working stock image on it first. This thread for those instructions:
http://forum.xda-developers.com/showthread.php?t=861950
Nvflash bekit's images then flash 3588 through the stock recovery, and you'll be back to latest stock image. Then you might have success with the custom ROM again.
Some tabs had a slightly different partition structure, mine was one of them. I nvflashed bekit's originals and it straightened out some things for me back in December.
It seems like a lot to do, but you may only need it once. I've only needed to use it twice since owning the Gtab, and the second time was by choice.
Having similar issue on the batch recieved from woot. Stock and Vegan 5.1x works but everything else gets stuck at the viewsonic birds screen.
I have no idea why. I'm going to try to do the old nvflash push method of installing cw .8 bekit today, since on the two I had in my possession this weekend got stuck and I used the install via recovery on cw .8 on them.
(btw. My original tab loads any rom(g-tablet) i want to throw at it, I used nvflash in december so it's the only thing i can think of)
Model on the tabs from woot is upc300-2.2 so yeah I am baffled (unless it turns out the way cw .8 installs....)
Hi,
Currently using latest firmware KI3 with root.
I'm able to use CWM, backup, install zips, everything.
However, if i install a ROM trough a ZIP, i get a boot loop.
Only way to get back the phone, it's to install via ODIN with latest KI3.
Even tried with Litening Rom, and got the boot loop.
Any ideas ?
I was very keen to return to CM7.
Tx in advance.
Did you exactly what's mentioned here?
Install via ClockworkMod (do not use ROMManager for initial install):
Make sure you're running a rooted device.
Root your device and install ClockworkMod Recovery (http://forum.xda-developers.com/show....php?t=1118693)
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition) - do it for real.
Install the ROM from internal sdcard using ClockworkMod Recovery.
Do not reboot! We mean it - do nothing except choose zip and continue next step (if you come back to us with permission issues in install, we will know you did not read the directions and will call you an idiot). If it just plain hangs, reboot directly back into ClockworkMod recovery and continue at the next step.
Install the ROM from internal sdcard using ClockworkMod Recovery, again (due to a bug in the install).
Reboot
Install the Google Addon through ROMManager which is easiest, but you can
download the gapps.zip and install via ClockworkMod recovery instead.
Click to expand...
Click to collapse
Did you try flashing a old stock ROM like KH3, root it then try from this base?
I went from Villain ROM 2.3.5 to CyanogenMOD without any problems.
It's essential that you flash CyanogenMOD !TWICE! in a row when you're coming from a stock ROM.
Thanks.
Gonna check, as soon as i'm @ 127.0.0.1
Same behaviour, back to boot loop.
Tanx anyway!
I had a similar problem so here goes my help.
Cf root kernel uses a modified version of CWM that isn't compatible with CM7 or something like that. So what I did was flash this kernel http://forum.xda-developers.com/showthread.php?t=1118693. Get the kernel with CWM 5.x.y.z With that I got a compatible version of CWM and from there I flashed CM7. It is important that you do a full wipe, wipe cache, wipe dalvik cache, format \system, everything so you don't get any trouble. THen you flash the CM7 zip file, when tha t is done, flash the zip again for a second time (don't reboot just do it after the first flash). After that reboot. That worked for me at least.
A tip: If you can't reboot your phone and you have no ROM zip file to flash via CWM you can mount usb storage from CWM for putting the ROM in sd card and flash with CWM. That way you don't have to use ODIN to recover.
Tanx Tomas.
Tried with CWM 5.x.y.z and upon "WIPE" always got an error for mounting partitions.
Could't mount CACHE, SDCARD .....
Tx anyway.
Back to ODIN, back to stock 2.3.5
PS : I have to get a JIG to reset ...
Hi guys, I was on cherry blur for a long while before finally decide to update.
I use the ROMRACER's Recovery from here:
http://forum.xda-developers.com/showthread.php?t=1204500
I update w/ the following manner:
1. Factory Reset/Wipe
2. Cache Partition Wipe
3. Dalvik Wipe
4. Install the ROM
ROMS i Tried:
Darkside 2.2
PureBlur 1.1
CherrynCrust .8
w/ DarkSide things freeze at M logo after reboot never got pass
w/ PureBlur the phone freeze up at random then reboot.
w/ CherrynCrust the phone freeze up at random then reboot.
I am not sure if there is anything else I should try, plz provide input if you have any experience. Thank you.
Update: I think i may have solve the problem
It seem that the phone does not like faux kernel and it seem to be the root of all the issue.
1. Fastboot -w
2. Fastboot reboot
3. Recovery > Factory Reset > Wipe Cache > Wipe Dalvik
4. Install PureBlur v1.1
5. Install PureBlur v1.2
6. Install ATT Stock Kernel
7. Reboot
---seem to work ok for an hour so far w/out crashing finger cross
I had problems when I used custom launchers, though I was on stock 2.2 atm, maybe that is your problem too?
Yeah i tried multiple launcher all produce the same thing, I thought it could be the overclocking so I use setcpu to set it back to 1ghz and still the same
Try wiping with fastboot -w and then flashing your ROM.
I think i may have solved my problem - updated my post
About a month ago I wanted to try out CM7 and see what it's worth.
I went to this thread: http://forum.xda-developers.com/showthread.php?t=1176411
I was using a stock GB ROM and rooted with CF-root kernel.
I downloaded the stable build and followed these instructions:
Install via ClockworkMod (do not use ROMManager for initial install):
1.Make sure you're running a rooted device.
2.Root your device and install ClockworkMod Recovery (http://forum.xda-developers.com/show....php?t=1118693)
3.Do a Nandroid backup!
4.WIPE (wipe data/factory reset + wipe cache partition) - do it for real.
5.Install the ROM from internal sdcard using ClockworkMod Recovery.
6.Do not reboot! We mean it - do nothing except choose zip and continue next step (if you come back to us with permission issues in install, we will know you did not read the directions and will call you an idiot). If it just plain hangs, reboot directly back into ClockworkMod recovery and continue at the next step.
7.Install the ROM from internal sdcard using ClockworkMod Recovery, again (due to a bug in the install).
8.Reboot
9.Install the Google Addon through ROMManager which is easiest, but you can
download the gapps.zip and install via ClockworkMod recovery instead.
Click to expand...
Click to collapse
When My phone booted it got into a bootloop.
I could not boot into recovery, I could only boot into download mode.
I searched the web and on one forum website I saw that someone encountered the same problem and after he encountered the bootloop he booted into download mode and flashed Siyah Kernel via Odin and his phone booted successfully.
I followed what he did and my phone booted into CM7.
After that I went on to other ROMs.
Two days ago I was running CM9 and I wanted to flash to CM7, so I downloaded CM7 nightly build #115 and did the following:
1) My phone was rooted with CWM. (CM9)
2) Wiped data, cache and dalvik.
3) Flashed the ROM twice.
4) Flashed GAPPS.
5) Rebooted.
6) "Samsung Galaxy S II with !" Screen.
7) "Kernel Panic" screen.
8) Took battery out.
*Tried booting into CWM with no success.
9) Booted.
10) Stages 6, 7 & 8.
11) Booted into download mode.
12) Flashed siyah kernel via odin.
13) CM7 working!
So there is my story!
I have also seen other people with the same problem, so it is not just me.
And here are my questions:
1) Why did these problems happen (kernel panic or bootloop)?
2) Why does Siyah Kernel fix these problems?
3) How can I prevent the bootloop/kernel panic from happening in the future (without flashing Siyah)?
Seconding the question as well as noting that it also occurs with Arif-Ali's nightly compiles.
did you wipe cache and dalvik cache after flashing cm7?
golcheck said:
did you wipe cache and dalvik cache after flashing cm7?
Click to expand...
Click to collapse
No, you dont need.
golcheck said:
did you wipe cache and dalvik cache after flashing cm7?
Click to expand...
Click to collapse
I did. I tried "messing" with CWM any which way and even flashed a stock rom in odin (and appropriate CF root). Nothing short of flashing Siyah (and probably any other kernel that supports CM7 except the one in the update zip) lets CM7 boot.
Net.silb said:
About a month ago I wanted to try out CM7 and see what it's worth.
I went to this thread: http://forum.xda-developers.com/showthread.php?t=1176411
I was using a stock GB ROM and rooted with CF-root kernel.
I downloaded the stable build and followed these instructions:
When My phone booted it got into a bootloop.
I could not boot into recovery, I could only boot into download mode.
I searched the web and on one forum website I saw that someone encountered the same problem and after he encountered the bootloop he booted into download mode and flashed Siyah Kernel via Odin and his phone booted successfully.
I followed what he did and my phone booted into CM7.
After that I went on to other ROMs.
Two days ago I was running CM9 and I wanted to flash to CM7, so I downloaded CM7 nightly build #115 and did the following:
1) My phone was rooted with CWM. (CM9)
2) Wiped data, cache and dalvik.
3) Flashed the ROM twice.
4) Flashed GAPPS.
5) Rebooted.
6) "Samsung Galaxy S II with !" Screen.
7) "Kernel Panic" screen.
8) Took battery out.
*Tried booting into CWM with no success.
9) Booted.
10) Stages 6, 7 & 8.
11) Booted into download mode.
12) Flashed siyah kernel via odin.
13) CM7 working!
So there is my story!
I have also seen other people with the same problem, so it is not just me.
And here are my questions:
1) Why did these problems happen (kernel panic or bootloop)?
2) Why does Siyah Kernel fix these problems?
3) How can I prevent the bootloop/kernel panic from happening in the future (without flashing Siyah)?
Click to expand...
Click to collapse
I fixed it.
This is how:
1. Make a CWM Backup.
2. Use Odin to flash I9100XXKI3, including the PIT (re-partition)
3. Flash this kernel (PDA section) and the old Bootloader (Bootloader section) with Odin.
4. Boot into CWM recovery and flash cm7+gapps.
5. Use Advance Restore in CWM to restore your /data partition if you want to.
I'm 90% certain that the problem was ICS's partition layout (PIT file).
This i9100g doesn't belong to me. It belongs to a friend..
Here's what he told me he did:
1)Did an OTA update to the GB stock ROM
2)Phone restarted and got stuck at the logo. (It was that way when I got the phone from him)
What I did to try and fix it:
1) Flashed a ClockWorkMod Recovery kernel (GT-I9100G_ICS_ClockworkMod-Recovery_6.0.1.2.tar) using ODIN
2) Data wipe .. Cache wipe .. Wipe /system /cache /data...Wipe Dalvik
3) Flashed CM10 (cm-10.0.0-i9100g)
4) Reboot System. It didn't work.
So again,
2) Data wipe .. Cache wipe .. Wipe /system /cache /data...Wipe Dalvik
3) Flashed CM9 (cm-9.1.0-i9100g.zip)
4) Reboot System. Things don't work out yet again.
Here's what happens:
Phone shows the exclaimation mark at boot along with the initial logo and goes directly into CWM recovery
I think this is because I am on a GB bootloader. How do I get an ICS bootloader? Is it safe to flash the stock ICS Rom over CM10 i.e., to follow this guide without messing things up (http://forum.xda-developers.com/showthread.php?t=1619571). Is there something that can be done apart from this to get CM10 working?