Currently stuck in bootloop and would like to return back to stock rom.
These are the steps I've taken:
1) NVFlash full restore using bekit's original image
2) Bootloader update (1.1 to 1.2) with CWM
3) installed gtabcombover 3.4.2, slow response rom
4) formatted sdcard to 2048/0
5) Ran TeamDRH 350 Prep to install TeamDRH ICS
6) Installed TeamDRH-ICS-Beta-1.3 (included TeamDRH recovery)
7) Software was unstable so I went through step 2 again.
8) Boot loop at Tap n Tap splash
9) Ran bekit's NVFlash, still stuck at bootloop.
Are there any links that I can be guided to that will help correct this?
Will need to look at logs to find out precisely why you're stuck in a boot loop, but, try one of these to wipe all data (except ROM) on the tablet. That usually fixes boot-looping.
1. If you have CWM recovery, then a) format cache and b) repartition the internal SD card.
2. If you have stock recovery, then see this thread.
Did you delete dalvik and do a factory reset? I would try that.
Sent from my VEGAn-TAB using xda app-developers app
striker59 said:
Did you delete dalvik and do a factory reset? I would try that.
Click to expand...
Click to collapse
An FYI: A factory reset in recovery mode, and in the ROM (when it works!), will clear the dalvik cache.
And, a factory reset is functionally what's being done in both steps in my post #2.
I had the same issue. Resolved it by following the instruction here: http://forum.xda-developers.com/showpost.php?p=14603562&postcount=21
tariq_niazi said:
I had the same issue. Resolved it by following the instruction here: http://forum.xda-developers.com/showpost.php?p=14603562&postcount=21
Click to expand...
Click to collapse
Don't need all those steps--only step 4. is needed here. In this case, the user's problems are most likely caused by not repartitioning the SD card/wiping cache between installing different ROMs.
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....)
Howdy,
Yesterday my Gtab started booting up only into ClockWorkMod recovery mode. I know of no changes beforehand.
I have:
1) Cleared cache
2) Cleared Dalivck Cache
3) Reflashed my rom (BL1.2 CyanogenMod7.2.0-RC0 BUILD98 REPACK 2.3.7 GWK74)
4) Reflashed the kernel (pershoot)
5) Reflashed CWM
6) Verified the Volume Up button isnt stuck
I have not done a full wipe yet.
Any ideas outside of trying to wipe the whole thing?
Coldfirex said:
Any ideas outside of trying to wipe the whole thing?
Click to expand...
Click to collapse
See this thread.
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).
Hi,
I am currently running CM9 Alpha2 ICS.
I thought of upgrading to CherryKang 0.9.2, I followed the steps below, but after install CherryKang would not come up.. I see the dual boot menu and when the cyanogen mod menu item is selected it blanks out and then reboots again and I see the dual boot menu again.
I did full wipe, Factory reset, Advanced-Dalvik Cache and also under Mounts and Storage System wipe, and lastly Wipe Cache. After install i did Factory Reset again and Wiped Cache again. Rebooted Touchpad and nothing comes up.
I also tried unsintall thru ACMEUnInstaller and then put CherryKang 0.9.2 in the cminstall directory and the install process did not install the CherryKang 0.9.2
What am I missing?
Thanks
TOO1BEE said:
Hi,
I am currently running CM9 Alpha2 ICS.
I thought of upgrading to CherryKang 0.9.2, I followed the steps below, but after install CherryKang would not come up.. I see the dual boot menu and when the cyanogen mod menu item is selected it blanks out and then reboots again and I see the dual boot menu again.
I did full wipe, Factory reset, Advanced-Dalvik Cache and also under Mounts and Storage System wipe, and lastly Wipe Cache. After install i did Factory Reset again and Wiped Cache again. Rebooted Touchpad and nothing comes up.
I also tried unsintall thru ACMEUnInstaller and then put CherryKang 0.9.2 in the cminstall directory and the install process did not install the CherryKang 0.9.2
What am I missing?
Thanks
Click to expand...
Click to collapse
0. 9.3 is out now, so you might as well install that.
Wipe /delete factory reset, wipe dalvik cache and install.
Make sure you have a good download (check md5).
No need to wipe /format anything after you install (I don't).
It should work.......
Don't forget to have a good backup in case things don't work.
I tried to use 0.9.3 but goes into a boot loop as before. Is it because I am also doing a "system format" under Mount and Storage?
I don't think cherry will install from cminstall since it doesn't start with update... or gapps...
I've always had to install it via CWM. I had to run the boot image cleaner and wipe everything before installing.
Sent from my MB860 using XDA
I did the update thru CWM. It did not work and goes into boot loop.
What else can I do
Are you still formatting system every time? Try skipping that. Just wipe caches and install ROM then gapps.
Sent from my MB860 using XDA
Hi Guys
Im having some problems trying to install a custom rom into my new Galaxy SIII I9300.
The rom in question is OmegaRom V35
After roooting and all, yesterday i tryed installing the rom with mobile odin, following all the instructions.
The result was the phone rebooted after the instalation seemed to be ok, but got stuck on the booting animation, and never got out of there.
I Had then to inject cwm with odin desktop, wiped data, cache anda dalvik, and then proceed to install the stock rom with desktop odin. All went well and the phone worked great.
I thought that maybe the problem was with mobile odin pro. So today, i went and proceeded to install Omega V35 via CWM. I again put the file on internal sd card, wiped data, cache and dalvik, and the rom started flashing. It all started good but, with no warning, at the mniddle of the installation, when applications were being installed, the phone went automatically and wuickly back to CWM!
Of course the installation wasnt finished, so i was stuck with cwm on reboot. Again made wipe data, cache and Dalvik, tried again to flash Omega V35, and again, the same problem...
In the end, i had to flash the stock rom again.
I searched the forum, but i cant seem to find the problem for this. I followed all the instructions, and had no error messages besides CWM skiping the format of the card, and some message (that i've seen in videos as normal), when wiping Dalvik!
Any clue to what's happening?
A clue read the instructions for the rom .
<b>Installation:Install CWM Recovery with Odin - Get CWM Recovery here
Boot to CWM Recovery using volume up, power button and home key
Backup your device and make sure to keep a copy of the backup to your pc!
Wipe data / factory reset (Not needed if you already have Omega)
Install Omega
(Wipe cache will be done automatically during installation so you can skip this step
Wipe dalvik cache will be done automatically during installation so you can skip this step)</b>
JJEgan said:
A clue read the instructions for the rom .
<b>Installation:Install CWM Recovery with Odin - Get CWM Recovery here
Boot to CWM Recovery using volume up, power button and home key
Backup your device and make sure to keep a copy of the backup to your pc!
Wipe data / factory reset (Not needed if you already have Omega)
Install Omega
(Wipe cache will be done automatically during installation so you can skip this step
Wipe dalvik cache will be done automatically during installation so you can skip this step)</b>
Click to expand...
Click to collapse
Maybe i didn't expressed myself correctly, but today i followed those instructions twice, and, at each of these tries the
same thing happened. When the flashing was running apparently problemless it simply stoped and went to CWM without rebooting.
rebentador said:
Maybe i didn't expressed myself correctly, but today i followed those instructions twice, and, at each of these tries the
same thing happened. When the flashing was running apparently problemless it simply stoped and went to CWM without rebooting.
Click to expand...
Click to collapse
Maybe The File Is Damaged Try To Download Again, Check MD5 Before Flashing
THE.W!ZARD said:
Maybe The File Is Damaged Try To Download Again, Check MD5 Before Flashing
Click to expand...
Click to collapse
I had already checked the md5, and the file is ok...
When you try to flash it through cwm recovery what error do you get while flashing?
Sent from my GT-I9300 using xda premium
Amritttt said:
When you try to flash it through cwm recovery what error do you get while flashing?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
None whatsoever. The flashing process seems to be running ok, It starts, i select default instalation, after i can see the apps being installed and suddenly, it all stops and goes into cwm without any message or warning...