Related
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
I have tried several different Rom Managers without a problem on my G Tablet. Have been using TNT lite. Recently I switched to Vegan Gingerbread edition, but when I went to backup my old Rom (TNT Lite) the backup hangs on backing up the cache. I tried wiping the cache and formatting the cache, but it always hangs indefinitely.
I installed Vegan Gingerbread anyway and it appears to work perfectly, yet I still cannot backup the rom with Clockworkmod (always hangs on the cache). If I try to look at the cache partition in filemanager, it shows empty, though I am not sure it is actually recognized. I can't seem to do anything with the cache at all.
I am, by no means an expert, but have had no problems with this before. Backup did work before the recent problem.
Since everything is working with my G Tablet now, I am not sure there is an actual problem with the cache, except that I can't backup the Rom without it hanging on the cache. This may limit my ability to load other Roms in the future.
Please help.
I have the exact same problem. I've had no issues backing up and restoring ROMs myself, but now I'm having issues with my tablet not being able to format or restore cache. I can install a ROM, but it takes a long time to actually load up - it can sit on the first splash screen for easily 5 minutes before it boots into the ROM, wher as before it took around 1 minute or less. Are you having this slow boot problem as well, or are your problems strictly with the cache? I'm going to continue to look into it (currently looking into using nvflash to do a restore and see if that irons things out), so I'll let you know if I come across any solutions. And please, let me know if you do as well.
hey guys i had the exact same problem before but nvflash fix what ever the problem was and the newly installed cwm work as it should. are you getting "ANDROID" screen right before it goes into cwm?
I am not getting the Android screen before ClockworkMod, but I generally boot with the power/vol + combo. I also have not changed Rom's recently, so I am not sure if this would be a problem or not. I do not have any boot problems that I am aware of, nor can I see and performance problems resulting from my inability to format the cache. The only problem is I can't wipe the cache, backup the rom, or format the cache as it stops on formatting cache partition and therefore can't continue the backup process. Other than incomplete backups I am not sure what problems this actually causes. Do you know.
I haven't used NVFlash yet, but I guess I will have to give it a try. Am I simply restoring the ROM to factory state and starting over or is there some other process I am looking for? Unfortunately, I did not get a proper backup of my original factory rom, so I will have to rely on downloads. Any tips on NVFlash would be greatly appreciated.
It's Fixed! Thanks for the tips.
Here is how I did it:
Ran NVFLASH - it was much easier that expected. It fully restored the original stock Rom, but I still had trouble with clockworkmod. Mostly it would not boot into recover mode. I then re-rooted the tablet using the Update.zip method, Then everything worked fine including backup and cache format.
I continued to restore my tablet and tried the backup each step of they way.
I installed Vegan Gingerbread - Worked flawlessly
I reinstalled MyBackupsPro and all my apps and Data - Also, worked flawlessly
I reinstalled Rom Manager - also worked flawlessly.
I used Rom Manager to upgrade ClockworkMod to 2.5.1.8 - then the backup/ format cache problem reappeared.
I then ran Rom Manager again and selected flash alternate ClockworkMod. It restored version 2.5.1.1. Then the backup and format cache worked again.
It appears that my Gtab does not work properly with Clockworkmod ver 2.5.1.8 and that was the entire problem.
Since Version 2.5.1.1 works great, I see no reason to upgrade this again and consider my problem fixed. I hope this info helps others
Hi - first time trying to root. I successfully rooted, installed Entropy's Kernel, and I thought successfully installed TurkbeyRom (I don't think this is a question specific to this rom, so I"m posting here...).
After booting back up, I get this message: " The process com.android.phone has stopped unexpectedly". This takes out my wireless signal, and keeps popping up with the error even when clear that screen out.
I realized that I didn't do any sort of data wipe before installing this rom...could that be the issue? I was under the impression that when installing them, it asked if you would like to wipe data, and it didn't.
My question is - if I wipe the data now, how much will I lose? Obviously I don't care about apps/contacts/etc..I'm wondering how far it'll set me back in the rooting process. Meaning if I wipe, will it completely wipe out my kernel...etc.
Thanks!
Boot into cwm and wipe data factory reset...then see if it fixes the issue. It wont go backwards in the root process
Sent from my SGH-I777 using xda premium
Please read before posting. Check the FAQ question [21].
- ROM install doesn't ask you to wipe, you have to do it yourself. (FAQ [21] has steps how to do it in CWM. For that, it is assumed that you followed this guide all the way through.
- any type of wipe will NOT remove your kernel. Wiping will remove stuff like your apps/contacts/etc
Wipe data/factory reset will remove any user installed applications and personal settings that have been set since the flash. It will not make any changes to the kernel or system partition, so the rom will be just like if you wiped first and then flashed the rom. That should solve any issues, but if there are still problems after the wipe, then try flashing the rom again.
Most roms here don't do an automatic wipe, afaik. You must do the wipe first, usually from ClockworkMod Recovery. It is always recommended to wipe when changing from one rom to another, from stock to any rom, etc. You can usually get by without a wipe when doing a minor upgrade of the same rom, assuming there is not change of base within the rom.
Thanks guys. It works perfectly now after wiping.
Sorry about not seeing that in the FAQs. I did look there, but I must have had a different "question" in mind than "[21] Install Custom ROM from CWM" and glanced past that one.
I don't know exactly what caused the issue. Maybe some recent apps since that was all that I had installed. I was running the latest AOKP ICS 4-28-12 and Siyah 3.1x. I forget the exact kernal number but it wasn't the version that I read about phone bricking (R6?).
So I wake up this morning and unlock my screen and there are popups for everything force closing. Not just foreground running apps but everything including background running apps. Every time an app autorestarts in the background the force close error msg pops up again. It was running fine just 6 hours prior since I was using it before bed.
Reboot. Same issue. CMW Recovery. Wipe cache/dalvik. Reflash AOKP and GApps. Reboot. Same force closing issue. WTF. Attach USB to comp and try to move a different ROM to my Internal SD but no dice. Comp isnt recognizing phone now. [email protected]#K! Reboot into download mode. All the ROMS I downloaded are ZIP format instead of TAR format. So this time my dumb self uses Odin to reflash the TAR file I used to root my phone. After this I realize "that TAR doesn't have a ROM attached to it."
So now I can only boot into download mode. Can't load CMW. Sadly I had to leave for work and I'm without my phone until I get home at midnight. I FEEL SO DISCONNECTED! ='(
Will a simple file conversion program be sufficient to convert ZIP to TAR so I can use ODIN to flash them later? Or will I have to follow the unbrick instructions to return to stock and then start over? And after reading about that one version of Siyah bricking phones I think I'm going to leave the NEAK kernal that comes with AOKP.
Thanks for your assistance!
No, you can't build a tar from a zip.
I don't and have never used aokp or cm9 or miui, but in my experience, when you start getting massive force closes, and if a fix permissions in recovery doesn't fix it, then you're best off starting over from scratch. If you have a working nandroid backup, use that. Otherwise, flash back to stock, wipe data/factory reset, and reinstall your rom from scratch.
There are plenty of tar and one-click downloaders available. See links in my signature.
I found this on the i9100 forums, instructive. Instead of installing a stock samsung firmware and kernel, just download a rooted package (maybe go back to Gingerbread for i777) then go from there.
http://forum.xda-developers.com/showthread.php?t=1457458
I'm interested to know how this recovery works for you, keep us posted! Best luck!
Any idea what would randomly cause the issue of mass force closures so I can prevent this from occuring again?
Did you do a Full Wipe when you first installed AOKP? I have ran into issues before with Rom Control by just wiping cache and dalvik and under the OP of AOKP Task even states coming from aokp or cm9 you Should be good but more likely than not, I would do a complete wipe *Factory Reset under CWM*. And when you restore your data with TiBu just restore missing apps and their data. Do not restore system data as that will be a major cause of mass FC... So first things first, I would use Odin to go back to UCKH7 *hopefully with CWM and Root* and than go back to Aokp since in my opinion is the best rom for our phones now.
HTH,
Charlie
dmnall said:
Did you do a Full Wipe when you first installed AOKP? I have ran into issues before with Rom Control by just wiping cache and dalvik and under the OP of AOKP Task even states coming from aokp or cm9 you Should be good but more likely than not, I would do a complete wipe *Factory Reset under CWM*. And when you restore your data with TiBu just restore missing apps and their data. Do not restore system data as that will be a major cause of mass FC... So first things first, I would use Odin to go back to UCKH7 *hopefully with CWM and Root* and than go back to Aokp since in my opinion is the best rom for our phones now.
HTH,
Charlie
Click to expand...
Click to collapse
I didn't do a factory wipe. I'm thinking I'll just do a factory wipe for any new rom installs. It's a little more work but if it helps prevent this sort of error I'll do it. And after reading about the bricking with that one version of Siyah I'm going to wait a couple weeks before any new installs to make sure other people have tested it first.
creepyncrawly said:
No, you can't build a tar from a zip.
I don't and have never used aokp or cm9 or miui, but in my experience, when you start getting massive force closes, and if a fix permissions in recovery doesn't fix it, then you're best off starting over from scratch. If you have a working nandroid backup, use that. Otherwise, flash back to stock, wipe data/factory reset, and reinstall your rom from scratch.
There are plenty of tar and one-click downloaders available. See links in my signature.
Click to expand...
Click to collapse
Well the first attempt didnt work using kernel + rooted UCKH7. Odin did everything it was supposed to but the phone locks at the initial Galaxy S II I-9100 ! screen. =(
Second attempt using I777_UCKH7_OCD_Root_No_BL and I'm able to get past the Galaxy S II I-9100 screen and the original AT&T boot animation shows but after the boot animation it just continuously reboots. ='(
Third attempt I tried Kernel + cache + rooted UCKK6 and after the reboot it actually rebooted into recovery mode. I thought that was a good sign so I reboot the phone normally and same issue as above. I try to reboot into recovery mode (Vol + - and pwr) again but it doesn't come up now. ='(
Forth attempt I tried Kernel + cache + rooted UCKK6 again. It reboots into recovery mode and I select the Factory Wipe option and reboot. There's a long delay after the AT&T boot animation and finally my phone starts up as if it was stock.
What a freakin nightmare! I was so worried my phone was a goner. None of the other ROMs I tried gave the option of booting into recovery mode which would have saved me so much time. Only the stock one did. The factory wipe was the key. So I'm definitely saving that file for safe keeping.
Thank you all for your suggestions and assistance. It's much appreciated.
This entire thread could have been avoided. By wiping completely. What is a complete wipe? Well, its the /system , /cache, /data, and /dalvik partition. Each of which are easily wiped in cwm in under 30 seconds. Flashing the kernel cleaning script doesn't hurt. Keep in mind these are your phones people it wouldn't hurt to do some research.
Sent from my SGH-I777 using Tapatalk 2
Anyone else have problems flashing to a 4.3 ROM? (I know some people do because I've searched.)
No matter what ROM it is, if it is 4.3 it will always fail to reboot a second time after it has been flashed.
Currently on CleanROM ACE 4.9 (4.1.2) with TWRP 2.6.0.1
I've tried to go to CM10.2 and it would reboot initially but then hang on the Note II logo if I tried to reboot.
I've tried to go to Paranoid Android.. same thing.
I've tried to go to PAC-man.. same thing.
I've tried flashing from the stock 4.1.2 ROM and the same thing happens.
I've followed every instruction I could find including this: http://forum.xda-developers.com/showthread.php?t=2423057
I do a factory reset, format data, flash ROM, wipe caches, flash gapps, wipe caches, reboot. It will boot fine from TWRP and load everything normally. Then, if I reboot or power off the device, it will hang on the Note II screen and I have to nandroid back to my previous ROM.
Any insight as to why this is happening? I haven't been able to find anything besides some random instructions for wiping/flashing (which I've linked). These ROMs look great and I'd really like to move to 4.3, but I cannot figure out what the problem is.
BigBoy275 said:
Anyone else have problems flashing to a 4.3 ROM? (I know some people do because I've searched.)
No matter what ROM it is, if it is 4.3 it will always fail to reboot a second time after it has been flashed.
Currently on CleanROM ACE 4.9 (4.1.2) with TWRP 2.6.0.1
I've tried to go to CM10.2 and it would reboot initially but then hang on the Note II logo if I tried to reboot.
I've tried to go to Paranoid Android.. same thing.
I've tried to go to PAC-man.. same thing.
I've tried flashing from the stock 4.1.2 ROM and the same thing happens.
I've followed every instruction I could find including this: http://forum.xda-developers.com/showthread.php?t=2423057
I do a factory reset, format data, flash ROM, wipe caches, flash gapps, wipe caches, reboot. It will boot fine from TWRP and load everything normally. Then, if I reboot or power off the device, it will hang on the Note II screen and I have to nandroid back to my previous ROM.
Any insight as to why this is happening? I haven't been able to find anything besides some random instructions for wiping/flashing (which I've linked). These ROMs look great and I'd really like to move to 4.3, but I cannot figure out what the problem is.
Click to expand...
Click to collapse
First time installing CyanogenMod 10.2 to your Galaxy Note 2 I605, or coming from another ROM:
- Read known issues ans FAQs
- Flash the latest official ClockworkMod-Recovery
- Copy GApps and CM10.2 ZIPs to your SDCard
- Boot into Recovery
- Flash CM10.2 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
read the OP for CM 10.2 next time....
First - clockworkmod not twrp for 4.3 usually fixes things
Second - do a factory reset AFTER installing
Third - Dont restore apps with TiBu going to 4.3
Next time be truthful when you say you read and searched.