I have been searching for a while, but does anyone have issues installing Miui 1.7.8? I can get to CM7 and install GAPPS for it no problem. On CWM 4.0 I have been trying to install Miui from SD card after wiping data and both caches. When it tries to load Miui I get a boot loop with the exclamation mark and quickly written words that I can't decipher quickly. I read earlier about pulling battery in this instance, but that didn't help. I want to test out the phone.apk, but I'm having some issues.
fsuagentsmith said:
I have been searching for a while, but does anyone have issues installing Miui 1.7.8? I can get to CM7 and install GAPPS for it no problem. On CWM 4.0 I have been trying to install Miui from SD card after wiping data and both caches. When it tries to load Miui I get a boot loop with the exclamation mark and quickly written words that I can't decipher quickly. I read earlier about pulling battery in this instance, but that didn't help. I want to test out the phone.apk, but I'm having some issues.
Click to expand...
Click to collapse
For future use, if anyone is having issues like this...
1. Booted using volume controls to recovery 3.0 posted by JT in CM7.
2. Used the ext4 formatter_all from navenrob
3. Used the CM7 install from JT
4. Booted CM7
5. ReBooted recovery from CM7
6. Wiped Cache from CWM 4.0
7. Installed current verison of Miui from CWM 4.0
Thought I would post how I figured it out.
fsuagentsmith said:
I have been searching for a while, but does anyone have issues installing Miui 1.7.8? I can get to CM7 and install GAPPS for it no problem. On CWM 4.0 I have been trying to install Miui from SD card after wiping data and both caches. When it tries to load Miui I get a boot loop with the exclamation mark and quickly written words that I can't decipher quickly. I read earlier about pulling battery in this instance, but that didn't help. I want to test out the phone.apk, but I'm having some issues.
Click to expand...
Click to collapse
I was having problems flashing 1.7.8 too. I downloaded 1.7.1.3 from goo inside me. The site where you download the rom. I flashed that with no issues on red CWM. Then i booted and went to orange recovery from the power menu. Flashed 1.7.8 perfectly. Don't really know if this would solve the problem but its worth a shot.
I had to odin eb01 with atlas 2.2, odin cm recovery fix for cm7, flash cm7signed in red recovery, rebooted into orange recovery, reflash cm7signed, reboot into rom, reboot recovery, wipe, flash cm7 0704, reboot, wipe, flash miui. finally worked after much trial and error
Related
To begin with, I am a complete noob with any and all phone mods. I'll run down what I've done and whats happening when I do it.
I used the adb method to root my tbolt. Once that was done, I installed Superuser, and Rom Manager and flashed with the latest CWR, after clearing the download manager and turning on the erase option in settings. I have done this (flash cwr) before each attempt to flash a rom.
I have tried 3 roms: Das Bamf 1.3.2 themed (tried twice), The Perfect Storm 1.2 and VirusROM RC1b3. I used identical steps to flash them:
1. Booted to CWR
2. made a nandroid backup
3. wiped data
4. wiped cache
5. wiped Davlik (sp?)
6. wiped battery
7. install zip from sd, choose zip from sd
8. after installation, reboot
When I reboot, the white boot screen with green htc logo appears, disappears, appears, disappears, and so on. I assume this is what people are referring to as a boot loop. It happened with both Roms, and luckily I am still able to get back to recovery and restore the stock rooted rom.
I've asked for help in the android forums, and a couple of people there have been trying to help, but the only real suggestion I've received is bad dl's. I haven't been able to find the md5's for the .zips to compare to what I generate, but I can't believe 3 straight dl's are corrupt.
Anyone have any suggestions as to what I'm doing wrong? Any help is greatly appreciated.
hootinani said:
To begin with, I am a complete noob with any and all phone mods. I'll run down what I've done and whats happening when I do it.
I used the adb method to root my tbolt. Once that was done, I installed Superuser, and Rom Manager and flashed with the latest CWR, after clearing the download manager and turning on the erase option in settings. I have done this (flash cwr) before each attempt to flash a rom.
I have tried 3 roms: Das Bamf 1.3.2 themed (tried twice), The Perfect Storm 1.2 and VirusROM RC1b3. I used identical steps to flash them:
1. Booted to CWR
2. made a nandroid backup
3. wiped data
4. wiped cache
5. wiped Davlik (sp?)
6. wiped battery
7. install zip from sd, choose zip from sd
8. after installation, reboot
When I reboot, the white boot screen with green htc logo appears, disappears, appears, disappears, and so on. I assume this is what people are referring to as a boot loop. It happened with both Roms, and luckily I am still able to get back to recovery and restore the stock rooted rom.
I've asked for help in the android forums, and a couple of people there have been trying to help, but the only real suggestion I've received is bad dl's. I haven't been able to find the md5's for the .zips to compare to what I generate, but I can't believe 3 straight dl's are corrupt.
Anyone have any suggestions as to what I'm doing wrong? Any help is greatly appreciated.
Click to expand...
Click to collapse
Did you try hitting install ROM from SD card in ROM manager and just flashing it through the app? Not sure that will change your result but it flashes it for you and you can choose the options to make a backup and wipe. Can't hurt to try it.
I did try it with Das Bamf, but got the same result. Thats when I read that using rom manager to install the roms could cause problems and started doing it manually.
After uninstalling/reinstalling rom manager and flashing cwr again, I got TPS 1.1 to flash, and its working great. I then tried to flash 1.2 thru cwr, both with a data wipe and without, but both times it boot looped.
I've dl'd TPS 1.2 from a different source, and I'll try to install it when I get home. But any other suggestions are very appreciated. I'm just glad I finally got something to flash.
I'm stumped. I tried new dl's of TPS 1.2 and Das Bamf 1.3.2te, and both of them failed. I even tried turning off my antivirus while dl'ing and moving the file to my sdcard, but it didn't make a difference.
So...I can't install either of the two CM based ROM's I've downloaded. However, on the first try, I installed VEGan, and then tonight TNT Lite, with no issues. Any CM ROM I try to install just sits on the loading screen, regardless of how long I wait. Is there something special that needs to be done to install them, different than what I do for other ROM's? (Clear data/cache, flash the ROM, clear data/cache again, reboot.)
sfreemanoh said:
So...I can't install either of the two CM based ROM's I've downloaded. However, on the first try, I installed VEGan, and then tonight TNT Lite, with no issues. Any CM ROM I try to install just sits on the loading screen, regardless of how long I wait. Is there something special that needs to be done to install them, different than what I do for other ROM's? (Clear data/cache, flash the ROM, clear data/cache again, reboot.)
Click to expand...
Click to collapse
I believe you have ClockworkMod 0.8 recovery, since you were able to flash Vegan Rom.
In general, before you flash the different rom
1. Back up your current rom
2. wipe data (factory reset)
3. wipe cache
4. flash the rom
5, flash gapps
6. reboot
Hope this helps
There have also been some reports of G-Tablets coming out of the box with incorrect partitions.
Using NVFlash has cured those issues. You should then be able to flash CM7 Roms through CWM like everyone else.
I repartitioned with 2048/0, shouldn't that rule out any partitioning problems?
I'm trying it again right now with flashing the rom then gapps.zip, waiting for it to boot...or just stay on the boot screen.
Format system and data, then follow those steps again. I ran in to similar issues when I hadn't formatted.
Also, do the three wipes again after installing the ROM and gapps.
Holy crap! I see the CM boot screen now! Thanks for the help guys. Now, do I still need to do the market fix (http://forum.xda-developers.com/showthread.php?t=865245)? It looks like from their changelogs that the latest version of Flash is cooked into the ROM so I shouldn't have to do that part from the guide, but I'm wondering about the market.
Well, the market seems to have everything, including an app (power control plus) that none of the other rom's let me see, so I seem to be good to go! Thanks again guys!
Thanks for the suggestion - and I'll readily admit I'm WAY out of my comfort zone with Android.
When I format the /system /data do I have to mount first?
What order do the steps run in? Do I partition and then format /system /data?
cannot install cm based roms
I was trying to reset from factory rest but failed when my gtablet stucked and apparently did something wrong along the way. Now when I turn it on, I get the 3 birds screen, followed by G-Tabdevs screen, then dead. I do have clockwork mod installed on it.
1 when I clicked factory rest, it just return to the manue and said cannot find the file.
2 when I did a back up, it went through boot image,recovery image,system and then taskbar stopped in the half at settings.apk and then dead.
3 when I tried to followed this link http://forum.xda-developers.com/showthread.php?t=865245
to use the external tf card to flash, Gtablet doesnot recogonize the external card, while I can read all the files in gtablet. I can copya single small file but cannot paste a recovery and update.zip on gtablet. Each time I copied a file from gtablet, then it is dead. I have to return on by pressing power and volume+.
4 I tried adb to push update.zip to gatblet,also failed. I feel my gtablet can only allows me to read it and refuse me to do anything on it.
Any ways to reboot my gatblet brick?
Please help! I've been reading forums all weeks trying to figure out how to fix it and am not having any luck!
Appreciate any suggestions
Hello all,
I need some advice. I originally followed this page http://wiki.cyanogenmod.com/wiki/Sam...l_Update_Guide to flash and everything was fine for 3 or 4 days and then the fc's came. So i odin'd to stock and when getting ready to reflash i see that you need to be on 2.2 to use his guide. So another member kwkslvr (who has been very helpful and patient btw) told me his method for flashing CM7 so i attempted to straight from 2.1 with no root to the following...
(kwkslvr's method) You definitely don't need to be on Froyo. You don't need root either. What has worked best for me is to Odin to 2.1, reboot into stock recovery and flash update.zip. Since you've flashed before, update.zip will probably already be in your internal sdcard unless you removed it. You'll have to flash it twice in a row without rebooting and that will load ClockworkMod Recovery.
Once you're in CMW Recovery (probably green recovery), wipe data/factory reset then format/system. These two steps are CRUCIAL! Flash your CM7 Nightly twice. The first time you flash it, it installs blue recovery. The second time it installs CM7. After that, again without rebooting, install gapps.
From that point, wipe data/factory reset again and reboot into the OS.
So i tried that and got to where the phone restarts after the flash and it has galaxy and cyanogen below it for a few seconds and then immediately script with font like from recovery mode races down the screen for a few seconds, then back to galaxy/cyanogen in a loop. So i odin'd again and as of now am stock 2.1 with the options of kies n it to 2.2 and then follow cyan page again or trying kwkslvr's method again. I did notice he mentioned nightlies but i am attempting to flash the stable on page 1 of this thread but don't think that would make much difference. I love the way this ROM looks and performed before it went off the tracks. Any suggestions are welcomed. Thanks alot
EDIT: At the boot loop sequence i 3 buttoned to recovery and reflashed and it seems to have worked. I notice the battery gauge no longer has the # %. And the horizontal line next to it is gone too. On my market page under "not installed" i have adobe flash showcase (Reads this item is not available at top), google search which just has a open tab (Already is installed), magic 8 ball by dennis bond (Reads this not available in your country?? it was the first time i installed it) Any ideas on how to get these 3 items off the not installed section. It's mainly a minor annoyance. I have cleared cache in market with no luck. Thanks.
I've been shuffling through threads for the past 2 days trying to find a fix a no luck yet so i'm making my own noob post.
yesterday after flashing CM7 to my atrix, I was trying to install the Gapps package and after that install my phone wont boot past the logo screen.
Im still able to access fastboot and get into android recovery. I've tried to wipe everything and reinstall cm7 but still nothing.
i read that some people were able to get this issue resolved using command prompt and fastboot commands, but im totally lost when it comes to command prompt and couldn't get working correctly.
any suggestions or fixes would be greatly appreciated
DThimself said:
I've been shuffling through threads for the past 2 days trying to find a fix a no luck yet so i'm making my own noob post.
yesterday after flashing CM7 to my atrix, I was trying to install the Gapps package and after that install my phone wont boot past the logo screen.
Im still able to access fastboot and get into android recovery. I've tried to wipe everything and reinstall cm7 but still nothing.
i read that some people were able to get this issue resolved using command prompt and fastboot commands, but im totally lost when it comes to command prompt and couldn't get working correctly.
any suggestions or fixes would be greatly appreciated
Click to expand...
Click to collapse
Just to be clear:
1. You successfully booted into CM7 after installing it? Then you went to install gapps and couldn't get past the boot logo?
2. Or were you trying to install gapps right after flashing CM7 (i.e. stayed in recovery and did not boot into OS)?
i Successfully booted into cm7 then went back into recovery to install the gapps package and after that install it wouldnt boot past the logo
DThimself said:
i Successfully booted into cm7 then went back into recovery to install the gapps package and after that install it wouldnt boot past the logo
Click to expand...
Click to collapse
Hmm, well that definitely rules out an outdated recovery, which is what usually causes people to get stuck at the bootlogo. If you can't even re-install after wiping, then I would just restore a backup and start over.
Maybe try getting a fresh download of the gapps package. You may have possibly had a corrupted download?
Are you running CWM recovery or Rom Racer's? I had a problem where I was stuck at the boot logo while using CWM (latest one) but when I switched to Rom Racer's recovery and flashed everything worked.
I ended up having to use an older CWM recovery and wiping the phone and SD card with a lot of help from a friend of mine whos knows more about this than i do
DThimself said:
i Successfully booted into cm7 then went back into recovery to install the gapps package and after that install it wouldnt boot past the logo
Click to expand...
Click to collapse
How did you prep for the CM7 and GAPPS flash? If you did not wipe correctly, there was a first indication you might have problems.
How long did you wait after the phone first booted into CM7? If you rebooted as soon as the OS was up, that's more than likely your issue. You need to wait 10 minutes to let the phone build system files after flashing.
Also, an older CWM would have, if anything, caused more problems. If you had the latest ROM Manager or Romracer CWM then that was definitely not your problem, so your friend using an "older" CWM wasn't helping any.
DThimself said:
I've been shuffling through threads for the past 2 days trying to find a fix a no luck yet so i'm making my own noob post.
yesterday after flashing CM7 to my atrix, I was trying to install the Gapps package and after that install my phone wont boot past the logo screen.
Im still able to access fastboot and get into android recovery. I've tried to wipe everything and reinstall cm7 but still nothing.
i read that some people were able to get this issue resolved using command prompt and fastboot commands, but im totally lost when it comes to command prompt and couldn't get working correctly.
any suggestions or fixes would be greatly appreciated
Click to expand...
Click to collapse
I have run into this issue before when flashing any apps that update an app that is already there. I have found that a Dalvik wipe is needed before the flash. It is good practice to wipe Dalvik at least when flashing anything that changes the System Files. I also wipe the cache Partition before any flashes just to help mitigate issues like this.
I have a sch-i500 that is rooted with cwm working.
I am very interested in running liquid smooth v 2.9 found here: http://forum.xda-developers.com/showthread.php?t=2245120
so I did a format, wiped the cache and davlik. when I installed the zip from external sd card the phone immediately gave me a screen for CWM v 6.0.3.3.
I can still navigate and restore old back ups but the phone does not go past the Samsung logo on the boot screen. Any advice is appreciated.
I was previously running stock 2.3.5 E09 if that helps
http://forum.xda-developers.com/showthread.php?t=1026746
seems to be the best way for me to recover from this (looks like I flashed a non voodoo rom without removing voodoo) but I am unable to get the phone into download mode with or without the battery in the phone.
please help......(update) Alright, I am a moron. needed to have a powered usb port. on my way to recovery. thanks for having all this great info in one place.
aircooledbusses said:
so I did a format, wiped the cache and davlik. when I installed the zip from external sd card the phone immediately gave me a screen for CWM v 6.0.3.3.
I can still navigate and restore old back ups but the phone does not go past the Samsung logo on the boot screen. Any advice is appreciated.
I was previously running stock 2.3.5 E09 if that helps
Click to expand...
Click to collapse
Oh so close.
When coming from 2.3.x ROM you will need to flash the rom (liquid: or other 4.2.x) you will need to flash 2 more times...
The 1st flash get you into the new recovery only,,, as you found out.
2nd flash will pop up with an error message about incompatible partition and telling you to re-flash again,,,
So 3rd flash actually installs your new ROM
Then install a current/compatible Google gapps
.
Enjoy
.
Thank you, I am getting closer.
still on the second and third flash of the rom I get a satus 7 error which I think is a bootloader issue.
I have flashed the GBbootloader.tar through odid to no avail and am following Section:4 How to flash any ICS 4.0.x & 4.x.x JellyBean based rom
http://forum.xda-developers.com/showthread.php?t=1238070
anythoughts?
aircooledbusses said:
Thank you, I am getting closer.
still on the second and third flash of the rom I get a satus 7 error which I think is a bootloader issue.
I have flashed the GBbootloader.tar through odid to no avail and am following Section:4 How to flash any ICS 4.0.x & 4.x.x JellyBean based rom
http://forum.xda-developers.com/showthread.php?t=1238070
anythoughts?
Click to expand...
Click to collapse
what does the error say besides status 7?
did you odin the CWM4 fixed for cm7 then install the ROM 3 times?
can you get a pic up for us to see?
just to be sure......using odin, I repartitioned with the pit, and flashed a E03 rom. rebooted the phone fine.
flashed the CWM4 fix for 7 and redid the GB bootloaders as well.
went into recovery and factory reset, wiped cache, and dalvik.
installed liquid-JB-v2.7-Official-fascinatemtd.zip this time first time took me directly to clockwork where I flashed again. prompted with install from sdcard complete. repeated and got same message.
factory reset, wipe, wipe and flashed gapps. Everything seems to have worked this time with the v2.7Official instead of 2.9. I will play with this for just a bit and probably try it again tonight with a fresh downloaded copy of v2.9. I really do appreciate your assistance and help and I would not have gotten this far without the forum.
update:
flawless installation of v2.9 since 2.7 was already installed. (installed via cloclwork mod recovery)
It was most likely an operator error that prevented me from installing 2.9 after E03. But I don't see the benefit of going back to recreate why it didn't work. Thanks again all is good and right.