[Q] Flashing ROM and Kernel question - myTouch 4G Q&A, Help & Troubleshooting

So when I root my phone using this method: http://forum.xda-developers.com/showthread.php?t=858996 (TRUE PermaRoot and the ULTIMATE S=Off) and then comes time to install the ROM and with that the Kernel... in this case: "MIUI 1.6.24 demonSPEED v1.1" it is recommended that I also update the kernel to "demonSPEED INSANITY v2.0"
So I wiped everything and then flashed the ROM and then shutdown the phone and then booted into recovery and then wiped everything and then flashed the kernel.
My question is: Did I do this correctly or should I have done something different.
Here is my hboot info after I rooted my phone:
GLACIER PVT SHIP S-OFF
HBOOT-0.85.2007
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Sep 27 2010, 11:12:59

Your results posted only show that your phone has root and s=off. When flashing a rom wipe everything (wipe data/factory reset, wipe cache partition, advanced then wipe dalvike cache, then flash rom. After flashing the rom wipe cache partition and dalvik cache again then install custom kernel. Eveything can be done in recovery.
Sent from my Acer Iconia Tab A500 using XDA Premium App

I do understand that everything can be done in recovery.
I guess my question is that after I flashed the ROM (after wiping everything of course)... should I shutdown the phone and then start back into the recovery right away and then wipe everything and then flash the kernel or should I let the phone start up normally after the ROM wipe and then shutdown and reboot into recovery followed by wiping everything and then flashing the kernel?
Or can I do both (ROM and Kernel) like this:
1) Boot into recovery.
2) Wipe Everything
3) Flash ROM
4) While still in recovery wipe everything
6) Flash Kernel
7) Reboot.

aybe said:
I do understand that everything can be done in recovery.
I guess my question is that after I flashed the ROM (after wiping everything of course)... should I shutdown the phone and then start back into the recovery right away and then wipe everything and then flash the kernel or should I let the phone start up normally after the ROM wipe and then shutdown and reboot into recovery followed by wiping everything and then flashing the kernel?
Or can I do both (ROM and Kernel) like this:
1) Boot into recovery.
2) Wipe Everything
3) Flash ROM
4) While still in recovery wipe cache partition and dalvik cache (in advanced)
6) Flash Kernel
7) Reboot.
Click to expand...
Click to collapse
See minor change in step 4...After reboot I would open ROM manager and select fix permissions and reboot then u will be set....other than that you got it
Sent from my Acer Iconia Tab A500 using XDA Premium App

aybe said:
I guess my question is that after I flashed the ROM (after wiping everything of course)... should I shutdown the phone and then start back into the recovery right away and then wipe everything and then flash the kernel or should I let the phone start up normally after the ROM wipe and then shutdown and reboot into recovery followed by wiping everything and then flashing the kernel?
Click to expand...
Click to collapse
It sounds to me that the problem is you're wiping "everything" before flashing the kernel. If you do a full data wipe, you're wiping the phone clean including the freshly flashed ROM. Try following this procedure: wipe everything, flash ROM, let it boot/reboot, wipe only cache and Dalvik-Cache, flash kernel, boot again, fix permissions, reboot. That's the standard procedure for flashing a custom kernel other than the kernel that comes with the ROM.

TeeJay3800 said:
It sounds to me that the problem is you're wiping "everything" before flashing the kernel. If you do a full data wipe, you're wiping the phone clean including the freshly flashed ROM. Try following this procedure: wipe everything, flash ROM, let it boot/reboot, wipe only cache and Dalvik-Cache, flash kernel, boot again, fix permissions, reboot. That's the standard procedure for flashing a custom kernel other than the kernel that comes with the ROM.
Click to expand...
Click to collapse
I actually haven't had a problem yet. Just wanted to make sure if what I did was the correct way to do things or not. Since there haven't been any problems and everything is working correctly so far, would you recommend that I reflash both the ROM and the kernel using the method you provided or should I just leave it be?
Thanks.

aybe said:
I actually haven't had a problem yet. Just wanted to make sure if what I did was the correct way to do things or not. Since there haven't been any problems and everything is working correctly so far, would you recommend that I reflash both the ROM and the kernel using the method you provided or should I just leave it be?
Click to expand...
Click to collapse
If you have the ROM and kernel you want loaded, and it's running smooth and stable, I would say leave it as is. Just refer to the steps I detailed the next time you flash a ROM followed by a third-party kernel.

Related

Why cant I boot into Recovery?

I can reboot into Bootloader, but when I try to boot into Recovery it kicks me back into bootloader. Im using Rom Manager and Clockworks. Any suggestions? Thanks for the help.
Use amon-ra its 10 times better than clockwordmod just download this http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=PC36IMG.zip
drag it to sd card and go to into bootloader thern fastboot and it should say update
Step one, get rid of Rom Manager.
Step Two, flash Amon Ra.
Fixed....
That did it. Thanks guys. Follow up question..do I do a full wipe or Delvick- Cache wipe when flashing Roms? Im used to letting ROM Manager do everything for me that im not 100% sure.
Do a full wipe User Data/Factory reset, then wipe each sub-category, EXCEPT SD Card.
Heck, I re-wipe Cache and Dalvik Cache twice.
jrvjr said:
That did it. Thanks guys. Follow up question..do I do a full wipe or Delvick- Cache wipe when flashing Roms? Im used to letting ROM Manager do everything for me that im not 100% sure.
Click to expand...
Click to collapse
No sweat any time bro

[Q] Motorola Defy on CM7 stucked on boot screen! Urgent!

Hi guys!
I have just rooted my Motorola Defy and installed CM7 (7.0.2) into it using the instructions provided by CM wiki. I decided to use ClockworkMod and bootmenu, since I'm on Mac OS X.
Well, everything went fine until I tried to open the Market app, which was not working. Searching the web, I found that the solution could be wiping user data and caché through the recovery mode. As I could not figure out how to start the bootmenu (which I learned later), I did it through the stock recovery mode (using power + volume down)... and since that I can't boot my phone anymore!
I have already tried wiping everything again and installing CM7, but I'm still facing this problem.
Please, anyone have any ideas? I'm almost desperate.
gfreh said:
Hi guys!
I have just rooted my Motorola Defy and installed CM7 (7.0.2) into it using the instructions provided by CM wiki. I decided to use ClockworkMod and bootmenu, since I'm on Mac OS X.
Well, everything went fine until I tried to open the Market app, which was not working. Searching the web, I found that the solution could be wiping user data and caché through the recovery mode. As I could not figure out how to start the bootmenu (which I learned later), I did it through the stock recovery mode (using power + volume down)... and since that I can't boot my phone anymore!
I have already tried wiping everything again and installing CM7, but I'm still facing this problem.
Please, anyone have any ideas? I'm almost desperate.
Click to expand...
Click to collapse
So after doing a factory reset from stock recovery, you say you're trying to install CM7...
Are you installing this from CWM recovery?
Did you wipe Dalvik cache?
Are you using an MB525 Defy or an MB526 Defy+, and is the CM7 zip you're flashing a Defy or a Defy+ build?
>
You've probably not wiped Dalvik it seems.
In CWM recovery, go to Advanced and under that select Wipe Dalvik Cache.
Do yhis and a normal cache wipe every time you flash a ROM update. If you flash a totally new rom like CM10, wipe data also.
krushnam said:
So after doing a factory reset from stock recovery, you say you're trying to install CM7...
Are you installing this from CWM recovery?
Did you wipe Dalvik cache?
Are you using an MB525 Defy or an MB526 Defy+, and is the CM7 zip you're flashing a Defy or a Defy+ build?
>
You've probably not wiped Dalvik it seems.
In CWM recovery, go to Advanced and under that select Wipe Dalvik Cache.
Do yhis and a normal cache wipe every time you flash a ROM update. If you flash a totally new rom like CM10, wipe data also.
Click to expand...
Click to collapse
Hi! Thanks for the reply, and sorry for my English.
Actually, I have already installed CM7 and it worked fine, except for the Market app. Trying to solve this, I have done a factory reset from stock recovery and, since that, CM7 is locked to the boot screen.
And yes, I have installed CM7 through CWM recovery, and I'm using a MB525 Defy.
Well, I have just tried wiping Dalvik Cache, but it seem as if nothing happens when I select this.
Ya wiping Dalvik is very fast, but it will make a lot of difference. Every time you update your ROM, wipe both cache and dalvik.
>
If this didn't solve your problem, try wiping market data and uninstalling market updates. They will reinstall on their own.
>
If even that doesn't work, reflash the GAPPS zip.
BTW, shouldn't you be on CM7.2? That's the latest CM7 as far as I know.
CM7.2:
WhiteRabbit 1.8: http://forum.xda-developers.com/showthread.php?t=1510063
Maniac's builds: https://github.com/maniac103/android_device_motorola_jordan-common/downloads
Quarx's builds: http://quarx2k.ru/cm7-nightly-defy/
krushnam said:
Ya wiping Dalvik is very fast, but it will make a lot of difference. Every time you update your ROM, wipe both cache and dalvik.
>
If this didn't solve your problem, try wiping market data and uninstalling market updates. They will reinstall on their own.
>
If even that doesn't work, reflash the GAPPS zip.
BTW, shouldn't you be on CM7.2? That's the latest CM7 as far as I know.
CM7.2:
WhiteRabbit 1.8: http://forum.xda-developers.com/showthread.php?t=1510063
Maniac's builds: https://github.com/maniac103/android_device_motorola_jordan-common/downloads
Quarx's builds: http://quarx2k.ru/cm7-nightly-defy/
Click to expand...
Click to collapse
How can I wipe market data? It is not an option from CWM...
gfreh said:
How can I wipe market data? It is not an option from CWM...
Click to expand...
Click to collapse
You can only wipe data from an app trough the Apps Manager inside CM7 (that means you have to boot up your phone).
Try flashing the newest CM7.2 and the newest GAPPS for CM7.2.
If the problem persists, return your phone to the old .sbf and start all over again.
thiagoelg said:
You can only wipe data from an app trough the Apps Manager inside CM7 (that means you have to boot up your phone).
Try flashing the newest CM7.2 and the newest GAPPS for CM7.2.
If the problem persists, return your phone to the old .sbf and start all over again.
Click to expand...
Click to collapse
Well, I really can't boot my phone. I just can access bootloader and both recovery modes from stock and CWM (bootmenu).
Do you know how can I flash a .sbf on OS X? I know a lot of programs for Windows, and I also have found a script (sbf_flash.sh) that should work on Mac, but it seems that a lot of people are having problems in OS X (including myself).
gfreh said:
Well, I really can't boot my phone. I just can access bootloader and both recovery modes from stock and CWM (bootmenu).
Do you know how can I flash a .sbf on OS X? I know a lot of programs for Windows, and I also have found a script (sbf_flash.sh) that should work on Mac, but it seems that a lot of people are having problems in OS X (including myself).
Click to expand...
Click to collapse
OK. Go to CWM recovery. Wipe data. Wipe cache. Wipe dalvik.
Now install WhiteRabbit 1.8 or Maniac's CM7.2.
Flash the GAPPS packages linked in the respective threads.
Now AGAIN wipe cache and dalvik.
You should boot normally.
>
As long as you can access CWM, there's no need to reflash the SBF.
krushnam said:
OK. Go to CWM recovery. Wipe data. Wipe cache. Wipe dalvik.
Now install WhiteRabbit 1.8 or Maniac's CM7.2.
Flash the GAPPS packages linked in the respective threads.
Now AGAIN wipe cache and dalvik.
You should boot normally.
>
As long as you can access CWM, there's no need to reflash the SBF.
Click to expand...
Click to collapse
Hi,
I have just reflashed a retailer version using RSD on a friend's computer and it is now back to life... now I'm figuring out what is the best path to follow.
Thanks for the help!
Factory resetting from stock recovery messes up custom Rom!! If You are on custom rom, you have to use CWM for doing wipe etc...
Sent from my Defy green lense using xda-developers app
sa3e1 said:
Factory resetting from stock recovery messes up custom Rom!! If You are on custom rom, you have to use CWM for doing wipe etc...
Sent from my Defy green lense using xda-developers app
Click to expand...
Click to collapse
Yeah... I know that. I just wanted to rollback everything and have the phone back. I'm now studying which is the best ROM for me to install again, but meanwhile, I have my phone working.

4.3 flashing and bootlooping problem

Hi there
I seem to have a problem flashing 4.3 roms, actually any rom that isn't stock in general.
Right now I am running syzmel's 20E with 1.3ghz overclock version 3.09.
Back to the problem: this is the steps I take to upgrade to any rom: 1. Download (slimbean, vanir asop) 2. flash v20D (unmodded) 3. Root it using Framaroot 4. Install CWM using L7CWM.zip (extracted, then clicked on flash bootloader, flash recovery, and then booted into recovery) 5. Boot into CWM 6. Click on factory reset and reset 7. Go into mounts and storage and format /system 8. Go to advanced and wipe dalvik cache. 9. Flash either 4.3 version slimbean or Vanir ASOP (tell me which is better) 9. Flash gapps (Slimbean: Slim AIO minimal Gapps, Vanir: 4.3 minimal Gapps which is found in the Vanir ASOP page) 10. Factory reset again 11. Wipe dalvik 12. Reboot
Now as soon as I reboot, either it stays rebooting, or boots once and when you reboot it stays at the boot loading page (slimbean logo, or android logo) (In other words, once you go black, you never go back. Not being racist, just saying once it blacks out it doesn't work no more). So i retry. And then I give up and stick on v20E.
So please suggestions?
Also ignore my signature
AsianFoodRules said:
Also ignore my signature
Click to expand...
Click to collapse
Are you sure it wipes made ​​correctly?
Danm, yes I'm sure.
Why you dont format cache and data & data/media ?
Did you try boot without gapps... Sometimes bad gapps cause a lot of problems
Sent from my LG-E610 using Tapatalk
When you factory reset it clears cache automatically. I'll try without Gapps.
wipe data,wipe cache wipe dalvic cache
AsianFoodRules said:
When you factory reset it clears cache automatically. I'll try without Gapps.
Click to expand...
Click to collapse
How do you factory reset? Factory Reset is NOT only wipe data
raul338 said:
How do you factory reset? Factory Reset is NOT only wipe data
Click to expand...
Click to collapse
Factory reset in CWM clears cache automatically.
....Anyway, I finally fixed it. Turns out I had to wipe EVERYTHING. Including /data and /data media. Thanks anyway guys.
LG Optimus L5 E610 - CWM Bootlooping
Basically I inserted a pre-rooted firware into my lg phone using 20d+root + cwm.kdz, everything was fine including the flashing, I some how got the the CWM recovery and done everything such as wiping cache, etc, but the problem was before and after the wiping, etc, is that everytime i press power button it turn off and on and back on to the CWM recovery screen not home screen with apps, etc.
I am really fustrated, please Help!:crying:

everything I try goes to bootloop or blank screen

Hi All, I can flash a rom using RSD lite and then root using super one Click, then install 2nd init. I can access the custom recovery to install new roms. I do a factory reset/wipe cache, wipe dalvik and then install a rom. After install, I do a second wipe then reboot. Everything I try goes to a bootloop or does not work. When I am in a newer recovery, I wipe the /system folder too before installing a rom. and still no dice.
Any Ideas.
fleagalbaum said:
Hi All, I can flash a rom using RSD lite and then root using super one Click, then install 2nd init. I can access the custom recovery to install new roms. I do a factory reset/wipe cache, wipe dalvik and then install a rom. After install, I do a second wipe then reboot. Everything I try goes to a bootloop or does not work. When I am in a newer recovery, I wipe the /system folder too before installing a rom. and still no dice.
Any Ideas.
Click to expand...
Click to collapse
Use defy full wiper or aroma wiper to wipe everything and then flash. Then immediately reboot after flashing, no wipes required.
Sent from my Nexus 7 using Tapatalk
I tried the aroma wiper but still does not boot properly Thanks for the link though, I will try to use it more and see what if I can get something to stick.
fleagalbaum said:
I tried the aroma wiper but still does not boot properly Thanks for the link though, I will try to use it more and see what if I can get something to stick.
Click to expand...
Click to collapse
Don't wipe after installing the ROM.
Sent from my Nexus 7 using Tapatalk

[Q] Flashing various TW Lollipop fw over existing CM12 fails

Hello,
actually I'm using a SGS4 I9505 with cm-12-20150304-NIGHTLY-jfltexx and CWM 6.0.5.1.
I've tried to flash several TW Lollipop firmware wich i found in the I9505 forum:
1. Kushan+Touchwiz+Lollipop+Lite+Rom+v.1.2
2. S4_Echoev42_EchoePop2_020315
3. OA7-2.1F
4. XXUHA07-v2.01
Before flashing any oft this firmwares i made a factory reset, wiped both caches and installed the modem Firmware via Odin.
After flashing firmware # 1 and 2 my phone was stuc in a bootloop (only Samsung Galaxy S4 Logo appears).
Flashing firmware #3 and 4 fails and cwm reports error 7.
Flashing cm12 afterwards isn't a problem and runs fine.
I think the wipe fails or doesn't work properly. Is it enougth to select factory reset in cwm and wipe the dalvik cache manualy?
What can I do?
With besteht regard
Mirko (NemesisMF)
What if it is a recovery problem?
Thought about that too.
Should i try twrp or philz?
I switched to Philz Recovery and flashed S4 Echoe Rom v42 without any Problems.
CWM seems to have a problem to falsh TW Lollipop images ower an existing CM12 an the I9505.
You need to do full wipe not just cache.
ranger4740 said:
You need to do full wipe not just cache.
Click to expand...
Click to collapse
As I wrote above I did a factory reset before flashing and wiped the caches with cwm. If that is not enougth it would be nice to explain what else I have to wipe or post a link.
While using philz recovery the factory reset for clean system is enougth and the new System is working fine.
Factory wipe is not full wipe, you need to do a full wipe as in format to install new rom, phillz recovery has this feature can't remember exactly where, I think its under advanced.
Just have a look in the sub menus.
Just to explain it better when you do a full wipe it deletes every part of the existing
Rom including the system, data and cache and some other stuff completely removing the android operating system, so unless the rom you install does a wipe before install parts of the existing system will remain and can cause boot issues. For example as you've already discovered you are trying to install a tw rom over an existing cyanogenmod 12 installation which Will cause it to hang on boot.
NemesisMF said:
As I wrote above I did a factory reset before flashing and wiped the caches with cwm. If that is not enougth it would be nice to explain what else I have to wipe or post a link.
While using philz recovery the factory reset for clean system is enougth and the new System is working fine.
Click to expand...
Click to collapse
Do you mean a factory reset from within Android itself? If so, then that's a complete obsolete step. When before flashing a rom you should perform a factory reset, then they always mean a full wipe from the recovery. You need to do a full wipe from the recovery. That means the /system partition is being wiped. You will see it in the screen during the wipe if it wipes /system.
But it also could have been a problem of CWM. I don't think it is being updated anymore, so better use TWRP or Philz.

Resources