Database Develop

[Q] Flashing ROMs

Do I really need to flash to stock before I flash a ROM everytime? IT GETS SOO ANOYING.

I do, its not that big a deal. Place CWM update.zip in the root of your SD card, place desired ROM somewhere on the card. Odin to stock allow to fully boot, then restart into recovery. Flash CWM, then flash ROM from CWM. You don't need to root or use ROM manager.
Sent from my SAMSUNG-SGH-I897 using XDA App

quarlow said:
I do, its not that big a deal. Place CWM update.zip in the root of your SD card, place desired ROM somewhere on the card. Odin to stock allow to fully boot, then restart into recovery. Flash CWM, then flash ROM from CWM. You don't need to root or use ROM manager.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I do the same thing it's not that big of a deal to go back to stock. It eliminates any problems you might run into
Sent from my SAMSUNG-SGH-I897 using XDA App

I don't I have had my captivate since august and have only used odin three times. There are a lot of reasons why flashing stock is neccesary, but just switching from one rom to another is kind of a waste. One reason is 3e recovery. It is easier to flash stock 2.1 not 2.2 and then flash a new rom as the above post says just put the update.zip and newrom.zip on the root and install. Once you are on a custom rom with a custom kernal you can use the options in recovery to flash another rom. I just factory reset, wipe cache partition, wipe dalvik cache, and flash, if you really want to wipe everything you can go into mounts and storage and wipe everything, but the boot again. Then go to mount usb and copy over the rom from the computer, and then flash. The update script included in the new rom will wipe everything once again. If you have problems, like you got a bad flash, try flashing the same rom over again. Its kind of rare to get a bad flash. In short just flash over if you have problems then use odin.
Sent from my SGH-I897 using XDA Premium App

When switching kernels
I typically flash back to stock when I'm going from one kernel to another. If the ROM I'm on and the ROM I'm going to use the same kernel (or at least the same line, i.e. two different versions of SuckerPunch), I usually skip the back-to-stock step.

Some say that it is only worth doing if you run into problems with the Rom. I do it everyrime to avoid anything that might happen. Plus old habits die hard from my WM days where flashing stock was needed
Sent from the shadows

I do it everytime. It hardly takes 10 mins and I don't mind spending that 10 here than spend debugging later
Sent from my SAMSUNG-SGH-I897 using XDA App

I don't if I am going from froyo rom to froyo rom. Only time I have to is leaving 2.3.3
This is my Captivate. There are many like it but this one is mine

AndroidKaboom said:
Do I really need to flash to stock before I flash a ROM everytime? IT GETS SOO ANOYING.
Click to expand...
Click to collapse
About as annoying as seeing this question asked dozens of times when it can easily be answered by doing a search or just scanning the forum titles for a similar thread.

It is easy to do, but no real reason to do so unless on a 2.3.3 rom
MIUI

Thread closed

Abyss Red Recovery doesn't show downloaded ROMs. ..

.. Alright I am wearing luck on my sleeves ... I wanted to try staxx hybrid ROM every thing was ready I followed the time tested procedure of installation
1. Reboot to recovery
2. flash abyss red touch recovery and again reboot to recovery, all red red and touch touch!!
3. wipe data/factory reset
4. The other two wipes.
5 Went in to install menu on abyss
Now fun begins! The ROMs , Kernel that I had stored on my external sd card where not to be seen , they just vanished. I searched every where and nothing, it just can't be seen. I had earlier did a back up CWM or nandroid back up or what ever that was, after trying for some time and failing miserably to get the glimpse of the ROMs i downloaded I lost all hope, and decided to restore the back up . I restored the back up and my phone is back .
6. Again I rebooted into recovery , this time it was CWM recovery ,obviously, I could see my downloaded ROMs and Kernels.
7. I could see my downloaded ROMs and kernels through File manager.
My question is 1) Why i didn't see my ROMs on Abyss 4.2 Red touch recovery kernel? and how do I resolve this?
2) I used my back up and restored it. Do i have to back up again? or this back up will work again, & again. Assuming, of course, I don't want the post back up
changes to be reflected once i restore again.
I wil be grateful if anybody can help me with answers. Have fun and Happy Flashing!
Sent from my GT-N7000 using xda app-developers app

Vishal_Pratap singh said:
.. Alright I am wearing luck on my sleeves ... I wanted to try staxx hybrid ROM every thing was ready I followed the time tested procedure of installation
1. Reboot to recovery
2. flash abyss red touch recovery and again reboot to recovery, all red red and touch touch!!
3. wipe data/factory reset
4. The other two wipes.
5 Went in to install menu on abyss
Now fun begins! The ROMs , Kernel that I had stored on my external sd card where not to be seen , they just vanished. I searched every where and nothing, it just can't be seen. I had earlier did a back up CWM or nandroid back up or what ever that was, after trying for some time and failing miserably to get the glimpse of the ROMs i downloaded I lost all hope, and decided to restore the back up . I restored the back up and my phone is back .
6. Again I rebooted into recovery , this time it was CWM recovery ,obviously, I could see my downloaded ROMs and Kernels.
7. I could see my downloaded ROMs and kernels through File manager.
My question is 1) Why i didn't see my ROMs on Abyss 4.2 Red touch recovery kernel? and how do I resolve this?
2) I used my back up and restored it. Do i have to back up again? or this back up will work again, & again. Assuming, of course, I don't want the post back up
changes to be reflected once i restore again.
I wil be grateful if anybody can help me with answers. Have fun and Happy Flashing!
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Not sure why you couldn't see it. DId you put ROM in root of Internal SD? Try putting it in Root of both Internal and Exernal.
Don't backup again. Do 1-4 and you should see your ROM when you choose install ZIP from INternal or External.
And not knowing about your ROM is it a CWM ROM- maybe you need Mobile ODIN?

Vishal_Pratap singh said:
.. Alright I am wearing luck on my sleeves ... I wanted to try staxx hybrid ROM every thing was ready I followed the time tested procedure of installation
1. Reboot to recovery
2. flash abyss red touch recovery and again reboot to recovery, all red red and touch touch!!
3. wipe data/factory reset
4. The other two wipes.
5 Went in to install menu on abyss
Now fun begins! The ROMs , Kernel that I had stored on my external sd card where not to be seen , they just vanished. I searched every where and nothing, it just can't be seen. I had earlier did a back up CWM or nandroid back up or what ever that was, after trying for some time and failing miserably to get the glimpse of the ROMs i downloaded I lost all hope, and decided to restore the back up . I restored the back up and my phone is back .
6. Again I rebooted into recovery , this time it was CWM recovery ,obviously, I could see my downloaded ROMs and Kernels.
7. I could see my downloaded ROMs and kernels through File manager.
My question is 1) Why i didn't see my ROMs on Abyss 4.2 Red touch recovery kernel? and how do I resolve this?
2) I used my back up and restored it. Do i have to back up again? or this back up will work again, & again. Assuming, of course, I don't want the post back up
changes to be reflected once i restore again.
I wil be grateful if anybody can help me with answers. Have fun and Happy Flashing!
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Your kernel and rom is in tar files so it did not register.
Or put your custom rom and kernel in internal and external sd i think you will not miss it.

I was on criskelo v9, CF 5.6 LRG kernel. All the files were in zip format so perfectly flashable on abyss. I was trying to flash Staxx paranoid hybrid Rom. I just saved it on my external SD card not in a folder on a extsd card. Can that be the reason? Very weird problem,Albeit very dangerous imagine you wiped all and ready to install the ROM and there is no ROM what will you do. Luckily I had a backup what if I didn't had a backup I would have struck on abyss recovery! !
Sent from my GT-N7000 using xda app-developers app

Vishal_Pratap singh said:
I was on criskelo v9, CF 5.6 LRG kernel. All the files were in zip format so perfectly flashable on abyss. I was trying to flash Staxx paranoid hybrid Rom. I just saved it on my external SD card not in a folder on a extsd card. Can that be the reason? Very weird problem,Albeit very dangerous imagine you wiped all and ready to install the ROM and there is no ROM what will you do. Luckily I had a backup what if I didn't had a backup I would have struck on abyss recovery! !
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
I think that is your answer - save on both internal and external just in case. HTH

Hi, what ever you had in ext sd card will be there only. i think you are not correctly accessing your ext sd card.

No dude.... I checked it 10 times, in fact I had no other option other then looking for them! finally I gave up, and was wondering what to do then it struck to me to restore back up and I did that and rest as they say is history
I did get few answers like
1. Abyss is a GB kernel and I flashed it on ICS things went wrong.
2.I didn't put them in a folder.
Not sure what exactly the issue was.... Now I won't flash abyss but still I am not sure which are safe ICS kernel to perform wipe data?
Sent from my GT-N7000 using xda app-developers app

Vishal_Pratap singh said:
No dude.... I checked it 10 times, in fact I had no other option other then looking for them! finally I gave up, and was wondering what to do then it struck to me to restore back up and I did that and rest as they say is history
I did get few answers like
1. Abyss is a GB kernel and I flashed it on ICS things went wrong.
2.I didn't put them in a folder.
Not sure what exactly the issue was.... Now I won't flash abyss but still I am not sure which are safe ICS kernel to perform wipe data?
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Custom kernels are safe to wipe like speedmod, cm9 etc
Stock ics roms are unsafe.
Sent from my GT-N7000 using XDA Premium App

Vishal_Pratap singh said:
No dude.... I checked it 10 times, in fact I had no other option other then looking for them! finally I gave up, and was wondering what to do then it struck to me to restore back up and I did that and rest as they say is history
I did get few answers like
1. Abyss is a GB kernel and I flashed it on ICS things went wrong.
2.I didn't put them in a folder.
Not sure what exactly the issue was.... Now I won't flash abyss but still I am not sure which are safe ICS kernel to perform wipe data?
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Only booting a ICS ROM with a GB kernel will cause havoc. But then you can install Abyss kernel for wiping data safely. Your procedure is also correct. My hunch is that at some place super-user permissions must have hindered the process.

If I have to check again what went wrong I have to flash abyss, wipe all 3 and then if I could not find the ROM again I will have to restore the back up. I want to do it but... Wondering is it worth the risk!
Sent from my GT-N7000 using xda app-developers app

Today I checked it again when I was moving from criskelo to liquid black. I flashed abyss and I realized that it doesn't show external sd card. So ext sd card mount problem I guess but not sure why ? And now I am on Franco r3 kernel this kernel should be safe to move to cm10 in future or should I go back to GB all together .
Sent from my GT-N7000 using xda app-developers app

Vishal_Pratap singh said:
Today I checked it again when I was moving from criskelo to liquid black. I flashed abyss and I realized that it doesn't show external sd card. So ext sd card mount problem I guess but not sure why ? And now I am on Franco r3 kernel this kernel should be safe to move to cm10 in future or should I go back to GB all together .
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Franco kernel has the emmc bug disabled so all together it is safe. Guess you can start working safely.

My Abyss Red reverses the two SD cards, so the Internal appears External and vice versa. This is well documented.
I've had no trouble using Abyss, so I think you just need to do a little more homework.

[Q] bootloop, unrooted stock phone, how do I recover?

Ok first off, I am pretty green newbie, please help me understand this stuff.
This is my girlfriend's phone, she was using it and it reset itself and now it seems to be stuck in a boot loop.
We'd like to try and recover the original system back to normal without having to use the built in system reset. I've heard I can do that by wiping the dalvk cache?
It is not rooted, and I'm driving myself crazy trying to figure it out. There's ways to root it but I can't get into the system to run things like zergrush or the other options.
I tried to flash clockwork mod, but since the built in recovery tool only sees the INTERNAL SD contents, I only have access to the EXTERNAL SD card to put ZIPs in. I tried to use ADB to push the zip onto the internal SD Card but it says access denied (because it's unrooted?) Now what?
So short of system resetting it and loosing all the system settings or trying to see if we can send it into samsung for a replacement, how do I do this?
Thank you for any help in advance. Please be gentle.

Put cwm on the phone via Odin, on a question asked yesterday almost exact problem I posted a link with instructions how to do this, MAKE SURE it is a t679 not t759! Otherwise you will brick your device
Sent from my SGH-T679 using xda app-developers app

Unrooted, your only real options are factory reset or use Odin.
Sent from my SGH-T679 using xda app-developers app

That is not true, if he gets cwm on it via Odin he can flash to stock through cwm, doing so would bring the phone back to out of the box condition with 2.3.6. Also it will save ALOT of time doing cwm through Odin rather than return to stock via odin
Sent from my SGH-T679 using xda app-developers app

It is a T679, yes.
OK according to the wiki page for the phone, I see how to use Odin to bring the phone back to stock, which is great, but I just want to be able to root it to wipe the dalvik cache in hopes of stopping the boot loop. Hopefully this would get the phone working like normal again without deleting the old system, right?
With the Odin program, how would I use it to force the CWM.zip to root it and give me access to the recovery menu to wipe the cache? Or am I missing something?
Again, sorry for not quite getting this stuff. Thank you for helping.

Check here:
http://forum.xda-developers.com/showpost.php?p=26860509&postcount=4
Down near the bottom.

http://forum.xda-developers.com/showthread.php?t=1686384
Sent from my SGH-T679 using xda app-developers app

tazmaniondvl said:
That is not true, if he gets cwm on it via Odin he can flash to stock through cwm, doing so would bring the phone back to out of the box condition with 2.3.6. Also it will save ALOT of time doing cwm through Odin rather than return to stock via odin
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
My bad, I forgot there was a cwm for Odin on this phone. I got mine after the 2.3.6 update and you could flash it thru stock recovery. Plus I've only used Odin once and that was to root my Gtab 2.
Sent from my GT-P3113 using xda app-developers app

OK thank you guys, using Odin did manage to get CWM recovery pushed into the phone.
The current problem is that wiping cache/dalvik is not fixing the boot looping.
I tried wiping battery stats, fixing permissions, wiping cache/dalvik, etc. and while it does cause the phone to sit on the "SAMSUNG" opening for about 2 mins, it still bootloops after that.
now, because I want to try and somehow preserve the old stock system (she has a lot of settings and programs that she needs to get access to) I can't just wipe everything and start over fresh.
Now, again, I am a newbie, but if I'm not mistaken, can I do a nandbackup onto the external SD card and this will allow me to just wipe to original stock, get it fully working again, then do an ADVANCED RESTORE of only the /system to get it back to the way it was before?
Again thanks for the help (and putting up with newbies) :3

Wilford Brimley said:
.
now, because I want to try and somehow preserve the old stock system (she has a lot of settings and programs that she needs to get access to) I can't just wipe everything and start over fresh.
Now, again, I am a newbie, but if I'm not mistaken, can I do a nandbackup onto the external SD card and this will allow me to just wipe to original stock, get it fully working again, then do an ADVANCED RESTORE of only the /system to get it back to the way it was before?
Click to expand...
Click to collapse
If you go back to stock and then advanced restore system you will probably be right back where you are now. Do another backup before trying that.
P.S. Make sure you have a way to keep track of the backups. Write it down or something.

Sorry bro if it is sticking on the Samsung logo, your phone does not have a rom
Sent from my SGH-T679 using xda app-developers app

Phone broke, Help!

Hi, I recently tried to root my Galaxy Exhibit, but now it's broken, nothing will load, it all force closes. My home, menu and search buttons do not work, I tried to restore it by using factory reset, but that just messed it up more. I plunged it into Samsung Kies, but it won't recognize the device. How can I restore the phone back, unroot, to factory settings.
This is what I did, first I downloaded TWO custom kernel (or roms, idk the difference.) The first one worked like a charm it was the root stock 1.8 but it was too stock, I wanted ICS so, I restored and I put a different rom/kernel in and booted it up, and boom everything is messed up, my kernel version has not changed, I tried using cwm recovery, but it didn't do anything.
Thanks
Sent from my LG-E970 using xda app-developers app

Well easy fix, in cwm wipe system or ROM 3 times wipe cache/dalvic cache. Then you can flash ICS and gapps, be advised there is no further development for ICS so I would suggest any 4.1 ROMs or even the 4.2 ROMs. Make sure you flash gapps
Sent from my SGH-T679 using xda app-developers app

this is why people need to do research. if you dont know the difference between roms and kernels dont flash

Amen lol
Sent from my SGH-T679 using xda app-developers app

[Q] bootloops after flashing rom

I just got a nexus one for $35 that i plan on using mostly as an mp3 player. I rooted it using the one click method but it's still S-on. Part of my issue is that booting into recovery using CWM only works maybe 25% of the time. Not sure why that is. A couple times I've been able to flash a rom via recovery but after seeing the X screen, the phone bootloops on the next splash screen. This has happened on two GB roms - MIUI and CM 7.2.
Any guess on why this happens? One reason I want to flash a rom is that the camera doesn't work so I'm curious if it would work in a different rom.

nvillamob said:
I just got a nexus one for $35 that i plan on using mostly as an mp3 player. I rooted it using the one click method but it's still S-on. Part of my issue is that booting into recovery using CWM only works maybe 25% of the time. Not sure why that is. A couple times I've been able to flash a rom via recovery but after seeing the X screen, the phone bootloops on the next splash screen. This has happened on two GB roms - MIUI and CM 7.2.
Any guess on why this happens? One reason I want to flash a rom is that the camera doesn't work so I'm curious if it would work in a different rom.
Click to expand...
Click to collapse
Before flashing a ROM, clear cache/ dalvik-cache from recovery. If you don't do these, then you will see bootloops.

I had been doing that through rom manager but just did it through recovery. still bootlooping.
I wiped cache but did not factory reset
Sent from my Nexus 4 using xda app-developers app

nvillamob said:
I had been doing that through rom manager but just did it through recovery. still bootlooping.
I wiped cache but did not factory reset
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
If you are changing ROMs, its always advisable to do a factory reset in addition to clearing cache and dalvik. Try it
Sent from my Nexus One

Best advice is to skip ROM manager and always do everything manually in recovery, this has never been a problem for me
And just because, I would suggest using 4ext recovery as in my opinion it is by far the most superior recovery... Just saying
Sent from my Nexus 4 using xda premium

Unfortunately, I've tried flashing manually via recovery too...still bootloops

Check md5sum of ROM (maybe bad download)
Make sure you wipe fully (manually in recovery or with fastboot)
Make sure you meet requirements of ROM in op (as in you flashed gapps if needed or you have a large enough system partition etc)
Sent from my Nexus 4 using xda premium

yeah, i haven't checked the md5's but it's odd that it's happened with both official miui and cyanogenmod. i did wipe cache and dalvik. i think i'm just going to give up. i'd do a factory restore but don't want to do that because then i'd have to root my phone again. i rooted the phone using a Vista computer but now I'm back home and my computer runs windows 8. from what I can tell, installing the android SDK is kinda complicated on W8.

Factory reset is needed and will not mean you have to reroot your phone, this is something that would be done before each flash, in fact the cleaner the wipe the less chance of an issue.
Also there is no need for the SDK to root (but its easy to get for windows 8 anyway and tools such as fastboot and adb are very handy... Also there are other ways to get these tools without the SDK) but all that besides the point, these are your steps
Nandroid backup
Wipe everything as clean as possible
Flash ROM and anything else needed (gapps etc)
Reboot
This is the procedure you should follow for any ROM flash for any android and never a need to reroot in between
Best of luck
Sent from my Nexus 4 using xda premium

I really appreciate the help. the reason I mention the SDK is that my computer doesn't recognize my phone unless I install the SDK and the associated drivers. So I'd hate the wipe my phone so that I can flash a rom, but then be unable to flash a rom because I'm not rooted!
But you feel confident that if I factory reset, I won't loose root?

I factory reset daily! You'll be just fine, when you factory reset and wipe all partitions you are following the proper procedure to change roms. When you flash the new one you are sure to still have root access
Sent from my Nexus 4 using xda premium

well, did a factory reset last night but i'm still having the same problem. I'm at a loss.