[Q] Upgrading to new ROM releases - G Tablet Q&A, Help & Troubleshooting

How much wiping do you need to do when you are upgrading to a new ROM release? I don't really want to have to go through all of the setup every time a ROM is updated. What does every generally do?
I'm running the G-Harmony ROM.

Use Titanium backup or the like to take a backup of everything if you are upgrading from one version of the rom to a new version. At first I wasn't backing up and spent hours getting everything back to the way it was. Now, in a matter of minutes I'm back running the same way I was before, but on a newer ROM.
Take the backup -> copy the backup folder to your micro sd card or computer -> follow the steps to install the ROM (do what is recommended such as the user data, dalvik, cache) -> once the rom is up and running, copy the backup folder back to your tablet -> download titanium backup, it will see the folder you copied over containing your backup-> restore data, apps, user settings from titanium backup.
I'm not sure how it works if going from ROM to ROM, probably want to search on it.

Cool, that's pretty much what I did. Unfortunately, I hadn't copied off the TitaniumBackup folder, and the new ROM version switched the emmc and SDCard mount locations, so I had to switch them back to be able to get at my backups. I didn't have an external micro SDCard reader with me, so I couldn't easily copy the folder from the internal card to the external. Ah, well. Going through the Titanium restores right now. I really should buy this software to prevent having to approve every restore

chadness,
One of the main things I try to help people here with is boot loops and I spend a
lot of time trying to figure out the cause so we can prevent it.
IT IS MY OPINION that one of the things causing the boot loops and making
people have to re-flash and re-partition -- is the stuff leftover in flash after
flash playing with their tablets.
I'm not sure the Android file system is all that good. I don't believe in tablet formats
because it doesn't work like a hard disk. You can delete a file and go back later and
the file is still there. You can nvflash the tablet and stuff is still let there.
When stuff gets left over it can conflict with the new stuff and BAM -- boot loops.
All of this is to say -- I SAY before every ROM burn you should nvflash to a solid
version -- bekit 1105 (2538) or 3588 -- the repartition to 2048 and 0, Fix Permissions,
Wipe Dalvik Cache, Wipe Cache and Wipe/Reset Factory Data.
I can't prove it yet -- but I bet if people would do that most of the boot loops would stop -- and probably some of the other little stuff too.
This is just my opinion -- but then I have only nvflashed either of my G-Tablets one time in five months now (involuntarily -- because of problems.)
Think about it.
Rev

Interesting! I've been flashing different ROMs this week and haven't run in to any problems as long as I've formatted system and data.

butchconner said:
. . .
All of this is to say -- I SAY before every ROM burn you should nvflash to a solid version -- bekit 1105 (2538) or 3588 -- then repartition to 2048 and 0, Fix Permissions, Wipe Dalvik Cache, Wipe Cache and Wipe/Reset Factory Data.
. . . . Rev
Click to expand...
Click to collapse
Rev, what is your opinion about using 'Calkukin's_Format_All.zip & wiping Dalvik Cache' vs all the above steps ?

Related

[Q] Ghost of ROMs past haunts my Vibrant

I've been stuck in a weird place for some time with my phone. After I installed clockwork mod, backed up, installed some flavour of FroYo, and made the mistake of trying to flash back my old back up without properly wiping things have been getting weird. I can use ODIN to flash fresh ROMs, but I always get a bunch of FCs at startup, and most apps don't work. I tried to do all kinds of tricks to completely wipe the internal SD, but there is always some remnants of old fun hanging about causing cascading errors and FCs. No matter what I try to do, MyBackupPro and Rommanager is always present, but not working.
How I can completely rid myself of anything not stock ROM?
I've finally gotten back to root ADB, after a long and hard battle. I believe this may hold the key to salvation for my Vibrant.
Any and all suggestions are much appreciated!
Things I've already tried:
EUGENE373_SamsungS_Froyo_PDA -> Stock 2.1 T959UVJFD
EUGENE373_SamsungS_Froyo_PDA -> battery pull -> Stock 2.1 T959UVJFD
Stock 2.1 T959UVJFD -> EUGENE373_SamsungS_Froyo_PDA
Bionix1.9.zip - would not install due to some error I can't recall right now. Will update.
Factory wipe - from Settings menu
Wipe in Clockworkmod menu
Wipe all in adb shell
The weird *2767*3855#* factory wipe
UPDATE:
Strangest thing happened: I flashed an old ROM back onto the phone with Odin 1.52, then the Updated Stock 2.1 also via Odin the usual FC-ing was still there. Then I rebooted into recovery, reinstalled the Clockworkmod recovery menu, installed the root-update.zip in order to have root shell access. Then I pushed VibrantDeodexed1_2.zip and Vibrantfroyo_R3.zip on to the sd card. I tried to apply the VibrantDeodexed1_2.zip, but it aborted due to some catalog not present. However, I did notice that the installation erased /system and deleted some files, and I had the notion to try and install the VibrantFroyo_R3.zip. The installation succeeded, and Lo and Behold!
the phone has returned to the land of the living! Wohoo!!
I do not fully understand how this can be, but there is no Force Closing of programs any longer. What a relief!
Thanks to everybody who contributed ideas!
If you're having problems, back up whatever data you want to keep to your computer. Go download eugenes 2.2 that doesn't brick. Flash that, do a battery pull once it's done (don't reboot). Then go get a stock eclair file, flash that with odin and check repartition. This solved every problem I had from flashing way too many roms.
Yea, when in doubt I thank the deities for Eugene and flash his "Froyo that doesn't brick" followed by the stock JFD firmware.
Sent from my SGH-T959 using XDA App
brnagndan said:
If you're having problems, back up whatever data you want to keep to your computer. Go download eugenes 2.2 that doesn't brick. Flash that, do a battery pull once it's done (don't reboot). Then go get a stock eclair file, flash that with odin and check repartition. This solved every problem I had from flashing way too many roms.
Click to expand...
Click to collapse
Sorry to say, that trying this solved nothing. Just the same as before.
ullrotta said:
Sorry to say, that trying this solved nothing. Just the same as before.
Click to expand...
Click to collapse
You clicked the "repartition" option? That should format your internal sd...
I7oobie said:
You clicked the "repartition" option? That should format your internal sd...
Click to expand...
Click to collapse
Yeah, that's the weird part.. It doesn't really delete anything. Files are still there, and so are the un-wanted system files, too.
Does anyone know if I can manually partition the sdcard?
Had a similar issue, and couldn't fully erase my files. Figured out how to completely erase everything, before you proceed, backup your files and be ready to Odin. In rom manager, enable advanced mode in settings, then use the flash alternate recovery option. That set my current cwm version to 2.5.1.2, now when I reboot to cwm i have a menu that says something similar to "sd and storage" and within that menu are options to completely format all of the internal storage. Be careful in there, you can delete everything, incl the sd ext, but I think this is what you are looking for.
Edited - I rebooted and checked the menus, mounts and storage in cwm is what you are looking for after flashing the alternate recovery, I can confirm this removes remnants that an Odin repartition or factory format still leaves behind, let me reiterate, backup your personal files, cause this does remove everything
After formatting, Odin away
Sent from my T959 running Bionix1.91 with Jacs OC/UV and Voodoo
same thing happened to me >.> I just formatted the SD card on the phone. then flashed whatever rom I wanted.
Br1cK'd said:
Had a similar issue, and couldn't fully erase my files. Figured out how to completely erase everything, before you proceed, backup your files and be ready to Odin. In rom manager, enable advanced mode in settings, then use the flash alternate recovery option. That set my current cwm version to 2.5.1.2, now when I reboot to cwm i have a menu that says something similar to "sd and storage" and within that menu are options to completely format all of the internal storage. Be careful in there, you can delete everything, incl the sd ext, but I think this is what you are looking for.
Edited - I rebooted and checked the menus, mounts and storage in cwm is what you are looking for after flashing the alternate recovery, I can confirm this removes remnants that an Odin repartition or factory format still leaves behind, let me reiterate, backup your personal files, cause this does remove everything
After formatting, Odin away
Sent from my T959 running Bionix1.91 with Jacs OC/UV and Voodoo
Click to expand...
Click to collapse
When I boot into recovery, I always have to reinstall packages to get to the CWM recovery menu. I tried to clear everything from the mounts and storage submenu; I cleared system, cache and data, then flashed stock eclair. STILL the same applications and files sit on the internal SD.
When performing the wiping, all looks normal. It does take a little time, and the system reports that all is going according to plan, yet no files are deleted.
What can possibly make the phone act this way? Are there no super secret samsung-technician codes that allow me to completely wipe clean the face of the sdcard?
When you get into the storage and mounts menu, I would format everything given what you're experiencing. Format boot, data, system, cache, and sdcard. Dont format the sd ext, thats the physical card. After formatting all of those your phone should be an odin ready blank slate, mine was. Hope this helps.
Sent from my T959 running Bionix1.9 with Jacs OC/UV and Voodoo
this has to be one of the most useful threads. just last night i was messing with rom manager and enabled advanced settings, BEEFORE reading this thread. I've done so much monkeying, but didn't keep a journal or log, so ive got **** from so many hacks and tweaks (mods and themes)...
thanks, im gonna wipe this ****er clean.
Good Info..but moved to Q&A
Br1cK'd said:
When you get into the storage and mounts menu, I would format everything given what you're experiencing. Format boot, data, system, cache, and sdcard. Dont format the sd ext, thats the physical card. After formatting all of those your phone should be an odin ready blank slate, mine was. Hope this helps.
Sent from my T959 running Bionix1.9 with Jacs OC/UV and Voodoo
Click to expand...
Click to collapse
This is exactly what I tried yesterday. I'll try it again a few times to see if I can find a way.
ullrotta said:
This is exactly what I tried yesterday. I'll try it again a few times to see if I can find a way.
Click to expand...
Click to collapse
I was hoping that would help you friend, that process wiped mine clean of all remnants. Good luck in getting her back into a functional state.
After reading som more, contacting Samsung Service, I've decided to send the phone in for service. [sigh]
I've learnt a lot about ADB, pushing and pulling files, rooting, unrooting, swapping ROMS and whatnot. Still, the phone is stuck in that weird place where I cannot delete files.
Hopefully the service team can fix this poor, misguided phone

[Q] All Gingerbread ROMs hang on reboot

I currently have cwm .8 and vegan 5.1.1 running without issue and backed up.
I have tried several different gingerbread roms and all of them get stuck on the static image screen before the boot animation.
I have made sure to wipe boot, system, data, dalvik, and cache as well as running Calkulin's Format.zip all prior to rebooting. I also have tried installing the ROMs with or without the Google apps addition. All with the same results.
Internal SDcard partitioned to 2048/0
Is there anything else I can try?
Are you sure they are all hanging at the boot screen? Most of the roms first boot takes a awhile for the cache to get filled with the data it needs to perform.
After the first few boots everything usually goes smooth from then on.
Roxxas049 said:
Are you sure they are all hanging at the boot screen? Most of the roms first boot takes a awhile for the cache to get filled with the data it needs to perform.
After the first few boots everything usually goes smooth from then on.
Click to expand...
Click to collapse
I am a patient fellow. I waited 20min at minimum for each ROM and none have ever made it to the animated boot screen.
I'm having the same issue with mine.. vegantab 5.1 works fine..
none of the gingerbread based roms get passed the viewsonic logo for me.
Same problem here.
All of the GB roms freeze at the android screen.
I have tried everything, I am a serial flasher on my D1 and on the gtab with the froyo builds and consider myself very familiar with the process and it still confuses me...
These are all new gTabs right? Have any of you repartitioned the internal sdcard yet? That option is in CWM recovery. There is a thread on it somewhere too. Basically it wipes the /SDCARD space and repartitions it. The FAQ thread has information on partition sizes too: http://forum.xda-developers.com/showthread.php?t=874258
ramerco said:
These are all new gTabs right? Have any of you repartitioned the internal sdcard yet? That option is in CWM recovery. There is a thread on it somewhere too. Basically it wipes the /SDCARD space and repartitions it. The FAQ thread has information on partition sizes too: http://forum.xda-developers.com/showthread.php?t=874258
Click to expand...
Click to collapse
I have been using the highly recommended 2048/0 as I did not see any details in the threads for the GB ROMs detailing otherwise. Sorry I forgot to mention that in my OP.
-edit-
Repartitioned to 2048/0 and also tried 4096/256. Issue persists
TNT lite 4.40 works Great.
bambamishere said:
TNT lite 4.40 works Great.
Click to expand...
Click to collapse
still a 2.2 ROM
Some progress! Following these steps will erase EVERYTHING from your device including the internal SD. Backup everything before you start.
After doing another restore to stock using nvflash
wipe everything via cwm (boot, system, data, cache, dalvik)
repartition sd to 4096/256
copy vegan ginger edition over to internal sd
it installed and booted up!
-edit-
and then I tried to install gapps and it won't boot again
Ran out of battery power to fully test but finally got it to boot after gapps install. Here are the steps I had to take:
wipe everything via cwm (boot, system, data, cache, dalvik)
repartition sd to 4096/256
Restore to stock using nvflash
did not let it boot into stock
reinstall .8 cwm from external sdcard
in cwm copy vegan ginger edition.zip and gapps.zip over to internal sd
Installed ROM then gapps
reboot
(note: after returning to stock I did not wipe anything with cwm)
genei.09 said:
Ran out of battery power to fully test but finally got it to boot after gapps install. Here are the steps I had to take:
wipe everything via cwm (boot, system, data, cache, dalvik)
repartition sd to 4096/256
Restore to stock using nvflash
did not let it boot into stock
reinstall .8 cwm from external sdcard
in cwm copy vegan ginger edition.zip and gapps.zip over to internal sd
Installed ROM then gapps
reboot
(note: after returning to stock I did not wipe anything with cwm)
Click to expand...
Click to collapse
Good work, quick question, you said you reinstalled cwm from external sdcard, does that mean you used the "cwmod_microsd.zip" from the "[STICKY][GUIDE] Install ClockworkMod, a ROM, Flash Player, and the Market Fix" post?
I have always used the internal one and was wondering if that made a difference.
wadsface said:
Good work, quick question, you said you reinstalled cwm from external sdcard, does that mean you used the "cwmod_microsd.zip" from the "[STICKY][GUIDE] Install ClockworkMod, a ROM, Flash Player, and the Market Fix" post?
I have always used the internal one and was wondering if that made a difference.
Click to expand...
Click to collapse
Yes that should be the same file. Looks like it was recently renamed as I had it labeled external rather than microsd. It isn't really a different cwm I used it so I wouldn't have to let the stock OS boot up and I kept it on the external sdcard so when I repartitioned the internal card I wouldn't loose it. I reloaded to stock many, many, many times trying to get this to work.
I'm currently using the experimental VEGAN Ginger Edition. It has some nice features but the videos for Dungeon Defenders don't play, and the keyboard is a little strange.
genei.09 said:
Ran out of battery power to fully test but finally got it to boot after gapps install. Here are the steps I had to take:
wipe everything via cwm (boot, system, data, cache, dalvik)
repartition sd to 4096/256
Restore to stock using nvflash
did not let it boot into stock
reinstall .8 cwm from external sdcard
in cwm copy vegan ginger edition.zip and gapps.zip over to internal sd
Installed ROM then gapps
reboot
(note: after returning to stock I did not wipe anything with cwm)
Click to expand...
Click to collapse
This work for anyone else? These Woot batches are introducing some issues.
I've had my tablet since early Feb. and I had issues with GB roms when I started trying them too. I found that the steps that worked best for me were pretty much the same as above. Mine are assuming that the tab is coming from something other than stock...
Wipe data,cache,dalvik and Battery Stats... (not sure the battery stats wipe matters)
NV Flash back to stock
Load CWM .08
Repeat Wipe
Load GB Rom
Repeat Wipe
Load rom devs recommended gapps version
Reboot
This USUALLY results in success. I still have mixed results getting gapps installed with some GB roms...once in a while I have to change up the steps and reboot PRIOR to gapps.
I've only had to repartition a few times, but the 2/0 option is the norm for me...and I usually only have to do this after I've made a big mistake, or things start to act "off" with the tablet.....
I think I read in one of the posts over on the dev side that most of the roms are written with the stock bootloader in mind and that it's just good policy to learn NVFlash and use it if you have any issues going from one rom to another.
I've been spending A LOT of time on this site since I got my gtab, too much probably. Usually, about 6 pages into a rom post, the answers to whatever issues we have with install are answered. It seems like mostly page 1 - 4 are people excited to flash...or saying thanks... pages 4 to like 10 are full of the answers to the questions "Why can't, Why didn't, how come..."...and then 10 - 10000 are just plain fun to read. ;-)
Good luck, this Tab is a ton of fon. I was super excited when the woot sale went down. I figure if even 4 or 5 more programmer types ordered one....that could mean 4 or 5 new roms for us to play with!
pceasar said:
This work for anyone else? These Woot batches are introducing some issues.
Click to expand...
Click to collapse
Worked for me last night. Using external sd CW.... Did not work from internal....
*shrug*
so far
3 tablets - internal memory cw install --- only vegan / tnt lite
2 tablets - 1 install of asop (gingerbread) 1 install of vegan GB experementals - one with clymson kernal one with pershot....
I'm just saying...
akodoreign said:
Worked for me last night. Using external sd CW.... Did not work from internal....
*shrug*
so far
3 tablets - internal memory cw install --- only vegan / tnt lite
2 tablets - 1 install of asop (gingerbread) 1 install of vegan GB experementals - one with clymson kernal one with pershot....
I'm just saying...
Click to expand...
Click to collapse
What process did you follow is it the same as tdg2100
Edit: I follow the same process as TDG2100 and it works w00t!! I think this should be included in a sticky somewhere people are going to struggle with this if they don't know how to get out of it.
Also question. Does this mean EVERY ginger ROM I have to flash has to go back via the NVFlash ROM route or can I just upgrade? Just curious, though at this point CM7 w/TT I doubt I'll be changing soon.
tdg2100 said:
I've had my tablet since early Feb. and I had issues with GB roms when I started trying them too. I found that the steps that worked best for me were pretty much the same as above. Mine are assuming that the tab is coming from something other than stock...
Wipe data,cache,dalvik and Battery Stats... (not sure the battery stats wipe matters)
NV Flash back to stock
Load CWM .08
Repeat Wipe
Load GB Rom
Repeat Wipe
Load rom devs recommended gapps version
Reboot
This USUALLY results in success. I still have mixed results getting gapps installed with some GB roms...once in a while I have to change up the steps and reboot PRIOR to gapps.
I've only had to repartition a few times, but the 2/0 option is the norm for me...and I usually only have to do this after I've made a big mistake, or things start to act "off" with the tablet.....
I think I read in one of the posts over on the dev side that most of the roms are written with the stock bootloader in mind and that it's just good policy to learn NVFlash and use it if you have any issues going from one rom to another.
I've been spending A LOT of time on this site since I got my gtab, too much probably. Usually, about 6 pages into a rom post, the answers to whatever issues we have with install are answered. It seems like mostly page 1 - 4 are people excited to flash...or saying thanks... pages 4 to like 10 are full of the answers to the questions "Why can't, Why didn't, how come..."...and then 10 - 10000 are just plain fun to read. ;-)
Good luck, this Tab is a ton of fon. I was super excited when the woot sale went down. I figure if even 4 or 5 more programmer types ordered one....that could mean 4 or 5 new roms for us to play with!
Click to expand...
Click to collapse
Worked for me also.
Matt
I had the same issue and I fixed it by:
1) Boot to clockwork
2) Go to mounts and storage and click "format system"
3) Then wipe data/factory reset
4) After that clear the cache
5) Then go to advanced and wipe dalvik cache
6) Install cm7
7) Install gapps
8) Reboot
Now everything is working for me.
Hi XDA !
I also am stuck at the ViewSonic Birds window - I know how to install CWM etc but I cannot get this to be recognized on a PC via USB. Its almost like the USB isnt started on the GTablet. How do I reboot this thing? Holding down the Power and + button has no effect...

Nandroid Advanced Restore (User Data Only) + navenedrob's format utility

Yeah, I just flashed from EB01 SC 292 to ED01 MIUIWiz after full Data, Cache, Dalvik, and voltage double wipes, and restored all my old EB01 user Data and apps over MIUIWiz, all in under 17 minutes.
Edit: adding navenedrob's utility method has cut this down to under 10 minutes, plus navigation and reboot time. See post #5
How? Just followed what the Devs have taught us, plus Nandroid Advanced Restore in CWM.
I have been doing this for every ROM I have flashed since I discovered what a Nandroid backup was.
But this is not just a Nandroid Backup. This is a partial restoration called “Restore data” under “Advanced Restore.” All in CWM recovery.
Here is the method I use:
Charge to 100% (At this point, I started the timer)
Boot to Recovery
Wipe Cache and Dalvik (and Voltage for MIUIWiz) x2
Make a Nandroid backup
Wipe Data x2
Flash the new ROM (of your choice) in CWM
Let it boot
Boot to Recovery
Select “backup and restore”
Select “Advanced Restore”
Select the Nandroid Backup file you wish to restore from (probably your latest one)
Here is where it gets cool, and less scary…
There is yet another page, with options:
Restore boot
Restore system
Restore data
Restore cache
Restore sd-ext
+++++Go Back+++++
So no sweat yet
Select “Restore Data”
Reboot completely
Turn off phone (here is where I stopped the timer at 16.5 minutes)
Charge to 100%
Boot and enjoy.
BAM! All the old data is back. On top of the new ROM. Except for stuff that no longer applies, like maybe in-ROM launchers that no longer exist.
My ROM flashing evolution path has been:
Stock
Odin DXC DB/DO tar
EC01 DB/D0 (zip i think, can't remember)
Full ED01 (Adrynalyne method, not OTA)
ComROM 1.0 zip
Evil Fascination, all variants in sequence. Zip
EB01 SC 2.9.2 zip (Why? To see if it would work. Because it means restoring ED01 Nandroid data over an EB01 ROM. Without compromising the ROM. (Thanks for the assistance with this, Lttlwing16.)
ED01 MIUIWiz
Seems to work flawlessly so far. No forced closes, no hiccups, just sweet functionality. Every time so far. And so quick, I sometimes actually have time to use my phone between flashes.
As I said, I have been doing this for just about as long as I have been flashing through CWM. Your backup may overwrite some ROM theme elements, so that is something to think about.
Any other drawbacks? Not that I have found, but…Not completely sure yet, So… You know the drill…
DO NOT TRY THIS UNLESS YOU ACCEPT FULL RESPONSIBILITY AND ARE PREPARED TO DEAL WITH THE CONSEQUENCES!! YOU MAY LOSE DATA OR FUNCTIONALITY!! YOU MAY EVEN MANAGE TO BRICK THIS THING!
But you just made a complete clean-wiped Nandroid Backup, right? So you can always restore the whole thing. Or worst case, do the Odin recovery method. (or even worse case, Heimdall).
I suspect that there is some reason that this method has not been widely promoted already. It seems unlikely that it has not been experimented with, so maybe someone can help show a newbie the error of his ways. Or we may need someone with a thorough knowledge of Fascinate ROMs to add some warnings, caveats, or guidance around potential problems, etc. But it does seem to work just fine for me, and all of the ROMs I have worked with seem smooth and stable. All my apps always work, and update properly. Unless I get stupid and screw something up.
It does seem that Android should be able to pull this off if sufficient attention is given to file structure and dependencies, and if everything data can be kept where a data only restore would look for files. I suspect that I have been having success because of the good work of all the great ROM builders and developers working to fix the Fascinate, and make our experience all that it is. So if this works for you, they are the ones that really deserve the credit and the thanks. They made it work. I just followed instructions, got curious about Nandroid Advanced Restore, and pushed the right buttons. Oh, and wrote it all down.
Wiping data and dalvik cache is kinda pointless because it gets overwritten and replaced by the restore anyway. Dalvik cache is located in the data partition, not the cache partition, ironically.
Sent from my SCH-I500 using XDA App
Well, I am expecting to learn something from posting this. So thanks. However, it raises more questions for me.
Does it mean that I never have actually needed to wipe data? I could have flashed all those ROMs without wiping data and without issues?
My understanding was that at least the cache would be re-written as needed by the new ROM, rather than trying to work with data created by the old one.
It sounds like it means that if bringing back the old data works, keeping the old data would have worked, too. So even Dalvik could have been left every time?
My thinking was that cleaning the cache and Dalvik before making the backup would mean that when restoring, they would come back blank, and not confuse the new ROM. I was under the impression that something was more likely to go wrong if all that stuff was left in there, and it was safer to bring it in later, after the ROM boots up, and give the new ROM a chance to properly recognize and deal with it.
Is there any logic in that logic? Just asking, because I really don't know. It sounds good.
If not, this thread is for educational purposes only.
But dang, either the Devs are even more awesome than we thought, or I must get lucky a lot. Because I have flashed quite a few ROMs without issues, force closes, etc.
Interested in more feedback on this process.
OK, I did have a couple of FCs of Gmail this last time flashing MIUIWiz, going from EB01 to ED01. It seemed to fix itself after I closed it twice, but I updated Gmail anyway. No repeats.
I have a new preferred method of backing up, cleaning the files, flashing new ROMs and restoring my data. Flashed MIUIWiz 111 over EF 360, the whole process taking about 10 minutes altogether plus navigation and boot time.
(Always create a clean Nandroid Backup (with wiped cache and Dalvik, possibly voltage) 4-5 minute process, not included. This should ensure that the new ROM will create its own compatible cache data after the restore.)
1. Run navenedrob's reformat utility [UTILITY]EXT4/RFS Formatter (CWM3 recovery packages) - xda-developers as a CWM zip from sd card <1 minute process.
2. Flash the new ROM in CWM <1 minute process.
3. Flash new Kernel if needed (before allowing ROM to boot) in CWM <0.5 minute process
4. Allow ROM to boot (3-4 minute process)
5. Nandroid Advanced Restore in CWM (Data only) (3 minute process)(Restores all User Data and apps)
From navenedrob: “Understand that this [format utility] will completely wipe your system, data, datadata (dbdata), and cache. This is a "full" wipe of the device.” But it also puts things back in order if they have gotten screwed up. This could be the solution to issues you are having. Thanks, navenedrob! Very cool.
If there are particularly desirable user setups in the flashed ROM, be advised they may get lost in the restore.
The only issue I seem to have is the need to update/install Gmail. Then all is smooth.
Works for me, but you may totally bork yours. You are responsible for what you decide to do.
times_infinity said:
Wiping data and dalvik cache is kinda pointless because it gets overwritten and replaced by the restore anyway. Dalvik cache is located in the data partition, not the cache partition, ironically.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I think that means wiping data also wipes Dalvik. So Dalvik wipe is redundant when wiping data. Good to know about the partition info. Seems to support the idea that wiping Dalvik before making the backup would ensure that when the restored data is brought back, it brings no Dalvik data with it, avoiding potential issues with the new ROM.

Non-booting SII with CM 7.1

As of yesterday, my CM7.1 phone won't boot - it gets stuck at the "rotating arrow" blue Android for ever. It's a Samsung Galaxy S II GT-9100.
I have been running CM 7.1.0 for several happy months now, and haven't tried to install or upgrade my ROM. The last action I took before this happened is that I made a full system backup (using CWM 5.0.2.6).
That backup is present on the internal memory. I can boot into recovery, mount drives and access devices using adb shell. So I do have an opportunity to fix what's broken, if I can work out what it is.
Given that the last thing I did was a backup, I checked to see if any of the partitions were full, but none are. (None is more than 42% full according to df; although strangely, df does not show any partition mounted on /.) I tried making another backup, watching carefully - that worked fine. I tried restoring the first backup - no improvement.
I've also tried wiping everything Recovery allows me to that's non data-destructive - cache, Dalvik cache etc. It hasn't helped.
How do I work out what's wrong? Is there a boot log file anywhere which might give me a clue as to what is wrong? I've searched for "*.log" but can't find anything obvious.
I don't want to do a factory wipe if I can avoid it, because obviously that will lose all my data. If I do a factory wipe and restore just the data partition, does that put me pretty much back where I was? If so, how do I restore just the data partition? The Restore option in CWM Recovery seems to do full backups only, and only from a particular directory.
The original CM and Google Apps zips are still on the internal SD (same versions as are currently not working). Would it be worth trying to reinstall those, without wiping? Or would that be data-destructive?
Any other ideas?
Thanks!
Gerv
SOLVED - remove 0-byte data/system/profiles.xml
I tried doing a full factory reset from Recovery. This got the phone booting again, but without any of my data . Fortunately, ClockWorkMod has a "partial backup restore" function. I restored the data partition... and the phone stopped booting again.
So this is progress. I now had some idea where the problem lay. I finally found it using a laborious 5-minutes-per-cycle manual bisection technique. Delete half the stuff on the data partition, reboot, if it still fails, delete more, reboot... once you get it to boot, restore the data partition, narrow it down further. Once you find a top-level directory, repeat the process inside it.
The result: the existence of a single 0-byte file stopped my phone from booting entirely. The file was: data/system/profiles.xml.
I have no idea what that file does (there are only a few references online), how a 0-byte version of it got created, or why having it existent but empty breaks things but if it's not present everything works fine. I have no idea if anyone else will ever see this problem, or if they will ever find this forum post. But still, here's my Wisdom of the Ancients (google the phrase for the relevant XKCD comic).

Upgrade ROM "SGT7+CM10+Cherry Picks,By meghd00t"?

hi,
this ROM works very nice for me, thanks all the deveopers!
i have few questions:
(1) since this ROM has OTA updater (it seems, from the changelog), next time when the new version is realeased, can i just update the ROM via OTA updater?
(2) i dont really understand what “Wipe cache/dalvik” and “Wipe data / factory reset” really do. my guess is that “Wipe data / factory reset” repartitions the internal flash memory of the original memory, so we can use all the memory for our purpose. (not like original Nook Tablet, in which they dedicate only 1GB for personal usage)
if i understand all these correctly, this means next time if i flash the new ROM and want to keep the old data, i should not do "Wipe data / factory reset", but only need to do "Wipe cache/dalvik"? is this correct?
thanks so much,
Jun
junkoi said:
hi,
this ROM works very nice for me, thanks all the deveopers!
i have few questions:
(1) since this ROM has OTA updater (it seems, from the changelog), next time when the new version is realeased, can i just update the ROM via OTA updater?
(2) i dont really understand what “Wipe cache/dalvik” and “Wipe data / factory reset” really do. my guess is that “Wipe data / factory reset” repartitions the internal flash memory of the original memory, so we can use all the memory for our purpose. (not like original Nook Tablet, in which they dedicate only 1GB for personal usage)
if i understand all these correctly, this means next time if i flash the new ROM and want to keep the old data, i should not do "Wipe data / factory reset", but only need to do "Wipe cache/dalvik"? is this correct?
thanks so much,
Jun
Click to expand...
Click to collapse
Wipe data/factory reset is an option in CWM Recovery. Really all it does (from the screen messages) is format both /data and /cache.
Assuming you have CWM Recovery (though I imagine that there are similar entries in TWRP, I've just never used it), to wipe both of the caches you will first need to go to the entry "Wipe Cache Partition", which I believe is directly below Wipe Data/Factory Reset. Do that 3x (that's always been the recommendation, anyway) then go to Advanced and click on Wipe Dalvik Cache (again, 3x).
Again, assuming CWM Recovery, when you're in the recovery Vol Up/Down goes up and down in the list, the 'n' key is for Enter, and the Pwr button goes back.
I don't know about the OTA Updater. I always download and install ROMs (on both my phone and my NT) via Recovery.
Since this is a CM10 based rom you probably don't want to do the ota updater since that is a Cyanogenmod feature. This rom is optimized for the Nook from the CM10 Source I would presume. I personally tried the ota uldater since i get the notifications all the time but i get an error message something like "can't verify the source with a string of numbers". Stick to the recovery based flash installation.
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 10:48 AM ---------- Previous post was at 10:10 AM ----------
I agree with liquidzoo that you should probably do the wipe cache, wipe dalvik cache and factory reset 3times seems like overkill but you can never be too safe. Also i use twrp recovery and click the system button and wipe system a few times as well.
Sent from my SPH-L710 using xda app-developers app
kobhomye said:
I agree with liquidzoo that you should probably do the wipe cache, wipe dalvik cache and factory reset 3times seems like overkill but you can never be too safe. Also i use twrp recovery and click the system button and wipe system a few times as well.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I wipe /system 3x as well (under Mounts in CWM Recovery) when I'm installing a new ROM.
liquidzoo said:
I wipe /system 3x as well (under Mounts in CWM Recovery) when I'm installing a new ROM.
Click to expand...
Click to collapse
I'm not picking on you personally, but deleting and/or wiping partitions (in the case of /system) or directories (dalvik-cache) three times as opposed to once is completely unnecessary. You'll gain nothing by running the command three times over running it once, assuming you received no errors the first time.
When wiping the dalvik cache, both CM recovery and TWRP perform an "rm -rf /data/dalvik-cache" command using the shell. It's not Windows, and is unlikely to fail when passed the "-f (force)" option along with the "-r (recursive)" option.
In the case of wiping the /system partition, again both CM and TWRP write out zeros to clear the data on the partition. I would be suprised if CWM acted differently from CM and TWRP when wiping dalvik-cache and /system.
The only reason I bothered to look into what these commands actually do is to prevent a user from thinking there's a corellation between a failure to wipe 3x versus a problem they're having. If a 3x wipe "fixes" something for you, whatever the problem was, it's very unlikely that the second or third wipe was what fixed it but instead it was more likely a result of a clean install of the ROM.
References from source:
TWRP Wipe Dalvik - https://github.com/TeamWin/Team-Win...548de276b62c0e9af8661e/extra-functions.c#L986
TWRP Wipe/Format System - https://github.com/TeamWin/Team-Win...8de276b62c0e9af8661e/mtdutils/mtdutils.c#L498
CM Wipe Dalvik - https://github.com/CyanogenMod/andr...aa7ff3d06d5dd115b16c/extendedcommands.c#L1292
CM Wipe/Format System - https://github.com/CyanogenMod/andr...aa7ff3d06d5dd115b16c/mtdutils/mtdutils.c#L498
Have fun modding!
No worries, it's just something I've always done as it's been recommended to me in the past (there are some ROM developers that recommend 5x, actually). I'm not saying that 3x over 1x is any better, but I've never had issues. YMMV, but it doesn't take much more time and I like being thorough.
liquidzoo said:
Wipe data/factory reset is an option in CWM Recovery. Really all it does (from the screen messages) is format both /data and /cache.
Assuming you have CWM Recovery (though I imagine that there are similar entries in TWRP, I've just never used it), to wipe both of the caches you will first need to go to the entry "Wipe Cache Partition", which I believe is directly below Wipe Data/Factory Reset. Do that 3x (that's always been the recommendation, anyway) then go to Advanced and click on Wipe Dalvik Cache (again, 3x).
Click to expand...
Click to collapse
sorry, but can you confirm that when i upgrade to the new ROM (from the same author), it is really necessary to Wipe cache &Dalvik cache?
i am confused because somebody told me that i can just flash the ROM by installing the ZIP file (containing the ROM), and reboot the Nook without having to wipe or clean anything.
thanks,
JK
Flashing a ROM
junkoi said:
sorry, but can you confirm that when i upgrade to the new ROM (from the same author), it is really necessary to Wipe cache &Dalvik cache?
i am confused because somebody told me that i can just flash the ROM by installing the ZIP file (containing the ROM), and reboot the Nook without having to wipe or clean anything.
thanks,
JK
Click to expand...
Click to collapse
I don't know if I am doing it right or wrong but I have flashed numerous ROMs and lately have flashed every version of SGT7+CM10+Cherry Picks,By meghd00t. from 24/09 thru my current installation of 08/10 with only one glitch and that was when I flashed enhancements v2 on top of v1.
I have never had any other issues with the above mentioned ROMs except when I flashed 04/10 with enhancement v2. I didn't have the tablet option.
The way I do it is as follows:
1. format /system
2. format /data
3. Flash ROM
4. Flash CWM emmc
5. Flash GAPPs
6. Reset Factory/format data
7. Remove CWM SD card put in data SD Card with Flash Player (no longer avail on Google Play)
8. Boot from CWM menu
Takes awhile to boot this first time. When booted up I bypass the setup screens.
9. Manually set up wireless (need to access auth web site at work and need wireless to be working to accomplish that)
10. Browse to a web site and get redirected to auth page.
11. Auth
12. Set up Google account and other settings, especially under Security <Install from other locations>
13. Download apps I want from Google.
At this first boot SD card is not mounted.
14. Shut down and do a cold boot.
Now I can see SD Card.
15. Install Flash Player from External SD Card.
16. Install Crackle from Play Store.
Now I check Pandora for Audio, Crackle for Video, other apps I use, utilities, keyboards, launchers, games, etc.
So far since Version 24/09 everything has worked for me with the two exceptions above, tablet mode with 04/10 with enhancement v2 and when I flashed enhancement v2 over enhancement v1.
I am now running 08/10 and am very happy with the performance, battery drain is more than CM7 but that is to be expected from a fairly new ROM but not so bad that it is unacceptable, to me at least.
I have never had a black screen or arbitrary reboot (knock on wood). However I do turn my tablet off when I am finished using it, so don't know about deep sleep. I'm using OnDemand, and three launchers without one being the default....Apex, Nova and Trebucket.
All I can say is these developers really ROCK, way to go guys!
--------------------------------------------------------------------------------
MojoGB said:
The way I do it is as follows:
1. format /system
2. format /data
3. Flash ROM
4. Flash CWM emmc
5. Flash GAPPs
6. Reset Factory/format data
7. Remove CWM SD card put in data SD Card with Flash Player (no longer avail on Google Play)
8. Boot from CWM menu
Click to expand...
Click to collapse
You don't need to re-flash CWM every time you flash a ROM. Also, it doesn't make sense to me why you would do a factory reset/format after flashing the new ROM, I would think it would be done prior to flashing the ROM but maybe it doesn't make a difference, I don't know.
I've got TWRP installed to the emmc so I just download the new ROM to the SD with GooManager, reboot into recovery, do a backup, factory reset, flash new ROM & GApps and reboot. Only takes a few minutes.
Reflash ROM
LifeWOutMilk said:
You don't need to re-flash CWM every time you flash a ROM. Also, it doesn't make sense to me why you would do a factory reset/format after flashing the new ROM, I would think it would be done prior to flashing the ROM but maybe it doesn't make a difference, I don't know.
I've got TWRP installed to the emmc so I just download the new ROM to the SD with GooManager, reboot into recovery, do a backup, factory reset, flash new ROM & GApps and reboot. Only takes a few minutes.
Click to expand...
Click to collapse
Tried it as you mentioned, doing a factory reset before flashing the ROM and got a black screen and wouldn't boot. May have been a fluke but the way I mentioned above gives me a good image and alway boots. Don't know why, but if it works for me, I will continue to do it this way as long as it works for me. I have flashed numerous other ROMs the same way with good results each time.
junkoi said:
sorry, but can you confirm that when i upgrade to the new ROM (from the same author), it is really necessary to Wipe cache &Dalvik cache?
i am confused because somebody told me that i can just flash the ROM by installing the ZIP file (containing the ROM), and reboot the Nook without having to wipe or clean anything.
thanks,
JK
Click to expand...
Click to collapse
For an update, yes it is recommended to clear both caches. To be clear, this is only for an update. If it is a new ROM, or if the author recommends it, you should also wipe /data and /system first.
You can just flash without clearing them, but you might run into unexpected issues, so it's not recommended.
MojoGB said:
Tried it as you mentioned, doing a factory reset before flashing the ROM and got a black screen and wouldn't boot. May have been a fluke but the way I mentioned above gives me a good image and alway boots. Don't know why, but if it works for me, I will continue to do it this way as long as it works for me. I have flashed numerous other ROMs the same way with good results each time.
Click to expand...
Click to collapse
I get a black screen for a while on first boot too, but it only last a couple minutes at the most and if you shine a bright light at the screen you can see the CM logo spinning. Are you sure it was hung?
Sent from my Barnes & Noble Nook Tablet using xda premium
When you clear the Dalvik cache, it clears out data stored in your applications. When you turn on your Nook after clearing the Dalvik, the first thing it does is it rebuilds the Dalvik cache, that's why it seemed like it hung on startup. I believe the long black screen in the beginning is when it rebuilds Dalvik for core Android apps and then when it says "Optimizing Apps", that's for the rest of your applications. The more apps you have, the longer it will take to build the Dalvik. No need to freak out, just a little patience is all you need. Correct me if I'm wrong, however, as I'm still pretty much a noob at this... :laugh:
Flash a Rom
topdawg7793 said:
When you clear the Dalvik cache, it cleares out data stored in your applications. When you turn on your Nook after clearing the Dalvik, the first thing it does is it rebuilds the Dalvik cache, that's why it seemed like it hung on startup. I believe the long black screen in the beginning is when it rebuilds dalvik for core Android apps and then when it says "Optimizing Apps", that's for the rest of your applications. The more apps you have, the longer it will take to build the dalvik. No need to freak out, just a little patience is all you need. Correct me if I'm wrong, however, as I'm still pretty much a noob at this... :laugh:
Click to expand...
Click to collapse
Well fhe screen was black, no light at all and I waited for over five minutes for the Flash Screen to come up and it never did. Yes I know when you are waiting time drags. But due to the ROMS always taking awhile to boot up the first time I actually pay attention to how long it takes. No more then 2 minutes in my experience. I had to hold the power button in for a long time until it finally booted in B&N Recovery. Used my sequence mentioned in earlier post to flash the ROM again and everything worked as it should, GREAT. The number of APPs shouldn't be an issue as these ROMS only have the very basic apps.
I have read this forum and see the various and asundry errors some are getting, so far I have never gotten a major error, except for when I forgot to do the Wipe Data/Factory Reset after flashing.
I also got the "No Tablet Mode Option" with 04/10 with enhancement v2.
But I consider these minor issues and currently am running 08/10 with no issues, works smoother then any version of Microsoft Windows I have dealt with.
These developers are exceptional.
MojoGB said:
I don't know if I am doing it right or wrong but I have flashed numerous ROMs and lately have flashed every version of SGT7+CM10+Cherry Picks,By meghd00t. from 24/09 thru my current installation of 08/10 with only one glitch and that was when I flashed enhancements v2 on top of v1.
I have never had any other issues with the above mentioned ROMs except when I flashed 04/10 with enhancement v2. I didn't have the tablet option.
The way I do it is as follows:
1. format /system
2. format /data
3. Flash ROM
4. Flash CWM emmc
5. Flash GAPPs
6. Reset Factory/format data
7. Remove CWM SD card put in data SD Card with Flash Player (no longer avail on Google Play)
8. Boot from CWM menu
--------------------------------------------------------------------------------
Click to expand...
Click to collapse
oh, so you always reset factory every time you upgrade the ROM? that way will delete all the old data/apps you installed, so you need to install all the apps again?
this is my concern, because i dont want to reinstall apps, or lose my data. so i think i just need flash the new ROM, then Wipe cache/Dalvik cache, and hopefully all the old apps and data are still intact.
thanks.
MojoGB said:
I don't know if I am doing it right or wrong but I have flashed numerous ROMs and lately have flashed every version of SGT7+CM10+Cherry Picks,By meghd00t. from 24/09 thru my current installation of 08/10 with only one glitch and that was when I flashed enhancements v2 on top of v1.
--------------------------------------------------------------------------------
Click to expand...
Click to collapse
i have some questions on the "Enhancements":
(1) the correct way to install them is to flash version 1 first, then immediately flash version 2 right after version 1 (without having to reboot first)?
(2) i am not sure what i will get with this "enhancements". they will make video/audio playing more smoothly? is the quality improvement really noticable? anything else, like they make the battery last longer, for example?
thanks,
Jun
If you're running 08/10, the enhancements are not needed. That's my understanding at least. I had problems with V2 so I decided to not install them while on 04/10.
Sent from my Barnes & Noble Nook Tablet using xda premium
Flash Rom
junkoi said:
i have some questions on the "Enhancements":
(1) the correct way to install them is to flash version 1 first, then immediately flash version 2 right after version 1 (without having to reboot first)?
(2) i am not sure what i will get with this "enhancements". they will make video/audio playing more smoothly? is the quality improvement really noticable? anything else, like they make the battery last longer, for example?
thanks,
Jun
Click to expand...
Click to collapse
If you flash enhancement v2 on top of version 1 you will have problems, UI will stop. If you only flash v2 you will not have the Tablet Mode Option. So my understanding is that you can use either v1 or v2 but not both.
ROM 08/10 does not need either enhancement as indicated by the developer. ROM 08/10 works great by itself is my experience.
If I'm installing a ROM, backup the existing ROM and wipe everything.
If I'm installing a .zip package like GApps or an enhancement, backup the existing ROM, wipe Data/Dalvik.
Folks, these are development ROMS. Thar be bugs in thet thar code. It's going to take you longer than the time you think you're going to save by doing a dirty flash, and then having to restore the thing to stock (worse case) only to start all over.
Don't ask how I know.
wellersl said:
If I'm installing a ROM, backup the existing ROM and wipe everything.
Click to expand...
Click to collapse
so it is possible to back up the existing data/apps, then restore them back after the new ROM is flashed? could you please confirm this?
if so, how & what is the right steps to do the backup? can we still use CWM, or use ROM Manager, or other tools?
thanks

Categories

Resources