I was trying to flash the BAMF SoaB Sense 3.5 Rom and it kept rebooting randomly, even without making any personal changes (apps+data). I cleaned up my SD card and tried to flash the Infected Eternity Sence3.5 ROM, and I get an installation error (Status 7). This happens when ever I try to flash a new ROM, but the CM7.1 back ups that I made through ROM Manager, reload just fine.
Any ideas on what could be wrong?
Make sure you're using the latest version of CWM - 5.0.2.1, for the non-touch version, available here: http://www.clockworkmod.com/rommanager.
Older versions of CWM, well, don't work for "newer" ROMs.
Oh, and when flashing from AOSP <-> Sense, make sure you wipe everything (Cache, Dalvik, Data, and System).
You can flash the latest CWM from the BootLoader also:
http://forum.xda-developers.com/showthread.php?t=1179386
ByteSizeSln said:
Make sure you're using the latest version of CWM - 5.0.2.1, for the non-touch version, available here: http://www.clockworkmod.com/rommanager.
Older versions of CWM, well, don't work for "newer" ROMs.
Oh, and when flashing from AOSP <-> Sense, make sure you wipe everything (Cache, Dalvik, Data, and System).
You can flash the latest CWM from the BootLoader also:
http://forum.xda-developers.com/showthread.php?t=1179386
Click to expand...
Click to collapse
okay, I'll give this a shot and make sure everything is updated. Thanks!!
You could also try 4ext recovery. It has an option to wipe all except SD card which makes flashing easier.
Sent from my ADR6400L using Tapatalk
disconnecktie said:
You could also try 4ext recovery. It has an option to wipe all except SD card which makes flashing easier.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
4ext is not only a time saver, but you don't have to mash the buttons & its stable!
Sent from my ADR6400L
Related
I flashed the leaked ICS RUU, and I'm S-Off. I'm now running Energy's 2.1 ICS ROM, and I want to try different ICS ROMs. If I were to flash the Android Revolution ICS ROM, would I need to go back to stock ICS?
I know if I want to flash Energy's 2.2 ROM, I'd just flash it over my current 2.1 ROM.
I think you just need to flash super wipe script then flash the android ROM.
Oh okay, cool. Also, do I absolutely NEED 4EXT to flash this, or is Xboarder's 5.5.0.4 recovery okay?
4ext is needed, dont use CWM
or at least highly recommended
punkmetalska said:
Oh okay, cool. Also, do I absolutely NEED 4EXT to flash this, or is Xboarder's 5.5.0.4 recovery okay?
Click to expand...
Click to collapse
you need 4ext to flash mikes rom but xboarders recovery worked fine for energy and speedrun for me.
CWM CAN NOT FLASH KERNEL IN RECOVERY.
4ext takes care of it. You don't HAVE to buy the app. 4ext also has wipe menu with format all partitions (except sd card) option which works the same as superwipe.
Rule of thumb, its always best to backup and wipe whenever you switch between ROMs for a clean install (unless u are flashing an update of your existing ROM). It doesn't take more than 6 minutes to backup and wipe. It's always worth it and you can always advance restore /data from a backup if needed
Sent from my iced out HTC Ruby
Just curious about whether I am wiping and flashing correctly.
I currently have TWRP 2.2.2.0 installed.
I am presently on the Viper sense based rom for the HOX+. I assume I must be wiping and flashing correctly as the rom works!!
Wipe cache, wipe davlik cache, factory reset and system? Then flash rom?
Doing this, does it completely remove the previous rom, audio drivers etc so that I have a clean slate so to speak for flashing the new rom?
That's what I'm after, wiping the previous rom completely, drivers, everything so that I can flash an aosp based rom.
Thanks.
First off, I would advice you to flash the latest version of TWRP before doing anything. Now, having said that, yeah, essentially press all buttons in the wipe Menu (I frankly don't know if the "Format" button would be overkill). However, be aware that in doing so, you're going to wipe all the data in the partition, including any zip files you may want to flash afterwards. If you end up doing this, you're going to need to sideload the rom into your phone in order for you to be able to install it.
You only lose stuff in data by wiping data partition
Sent from my HTC One X+ using Tapatalk 2
If he is wanting to use the Viper rom it is best to flash the version that is on the Viper thread. This has some minor changes in it to allow the install of OTA's and zip files from the hub.
If he uses the latest version it may cause issues trying to install OTA's.
Lloir said:
You only lose stuff in data by wiping data partition
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Exactly, so long as he doesn't touch the data partition he should loose nothing. I did recommend the whole "Nuke it" approach because of the whole "Clean Slate" thing the OP wanted though...
Nuke it? Wipe everything, including data partition then sideload a rom?
Thanks.
maritimesbob said:
Nuke it? Wipe everything, including data partition then sideload a rom?
Thanks.
Click to expand...
Click to collapse
Yeah, although it's not necessary most of the times, at least that's what I personally do when I want a 100% clean install (Short of re-locking the bootloader and running a RUU of course).
maritimesbob said:
Nuke it? Wipe everything, including data partition then sideload a rom?
Thanks.
Click to expand...
Click to collapse
While installing Viper you can choose to wipe the phone for a clean installation. So basically it's not necessary to do anything than install recovery for Viper and then install Viper ROM and choose the correct option in AROMA installer...
Can someone confirm the order for flashing ROM, kernel, and Gapps? Do I perform all the factory reset/wipe/format steps prior to flashing anything, and do I need to reboot between any of the steps? Is it really necessary to perform multiple wipes (i.e. factory reset x3) and/or use the CleanWIPE script?
I'm used to a factory reset and a flash of just the ROM, but I'm reading through the CarbonROM thread and seeing the suggestions for custom kernel, separate Gapps, and "hoops" regarding data/GPS that have me second-guessing my noobish knowledge.
I am S-OFF and currently running Tachyon 1.1 with some minor problems. I attribute these to using CWM Touch recovery and not formatting internal SD/emmc prior to first (and only) 4.3 ROM. I plan to switch to TWRP 2.6.3 prior to flashing another ROM per all the high praise.
esmith818 said:
Can someone confirm the order for flashing ROM, kernel, and Gapps? Do I perform all the factory reset/wipe/format steps prior to flashing anything, and do I need to reboot between any of the steps? Is it really necessary to perform multiple wipes (i.e. factory reset x3) and/or use the CleanWIPE script?
I'm used to a factory reset and a flash of just the ROM, but I'm reading through the CarbonROM thread and seeing the suggestions for custom kernel, separate Gapps, and "hoops" regarding data/GPS that have me second-guessing my noobish knowledge.
I am S-OFF and currently running Tachyon 1.1 with some minor problems. I attribute these to using CWM Touch recovery and not formatting internal SD/emmc prior to first (and only) 4.3 ROM. I plan to switch to TWRP 2.6.3 prior to flashing another ROM per all the high praise.
Click to expand...
Click to collapse
If you are S-OFF, I would recommend this procedure (assuming TWRP 2.6.3.0 is installed)
1) Backup current ROM
2) Flash CleanWipe script of choice
2.5) [OPTIONAL] Format /boot partition (Some people say do this, others say never do. I do it everytime and never had any issues)
3) Flash ROM
4) Flash recommended Gapps (official full or unofficial Core as recommened by ROM dev)
5) Reboot
If you are going for a custom kernel that is not included in the ROM, make sure the ROM boots and comes up problem free BEFORE you flash it.
This is what I have been doing for some time, it always works... no extra steps or anything else. I have never had the internal storage problems or anything else. If you do have the internal storage issue, just format it in TWRP and you should be good to go.
acejavelin said:
2.5) [OPTIONAL] Format /boot partition (Some people say do this, others say never do. I do it everytime and never had any issues)
Click to expand...
Click to collapse
Where do you do this in TWRP 2.6.3.0? I do not see an option for /boot in Advanced Wipe.
esmith818 said:
Where do you do this in TWRP 2.6.3.0? I do not see an option for /boot in Advanced Wipe.
Click to expand...
Click to collapse
Hmm... Apparently its gone now, just skip that part I guess. The more I think about it, the more I am pretty sure I haven't done that since I used Amon Ra. Just Cleanwipe and flash.
Sent from my Nexus 4 using xda app-developers app
esmith818 said:
Where do you do this in TWRP 2.6.3.0? I do not see an option for /boot in Advanced Wipe.
Click to expand...
Click to collapse
If internal is acting funny and camera says it doesnt work after you flash the rom and everything you'll have to go into advanced settings and partition internal sd card and emmc...and also wipe it afterwards...also just to be safe format internal sd to defaults on pc afterwards
tetakpatak said:
Please quote my post and copy&paste whole text into some help thread for your phone, it is better idea as we are now getting off topic here. I'll try to help you there.
Format /system is done in recovery mode under "mount and storage" then after that you can restore your nandroid if it is done with the same recovery you use now. If you're on PhilZ 6, it usually can restore also CWM 6 backups.
Click to expand...
Click to collapse
What does format system do? And please help me load sentinel rom. That's the one I was gonna do.
Okay now for the question... I was running stock 4.1.2 with siyah kernel 6.0 b5. Then I decided to install philz kernel, but ended up in bootloop. Then I tried flashing dorimanx but still in bootloop. All the while I wiped everything before flashing.
Now im stuck as I can boot into recovery via any kernel but ultimately phone is stuck.
What to do?
And can anyone give me steps to install sentinel rom from this stage?
Sent from my Nexus 4 using xda app-developers app
AndroidReborn said:
What does format system do? And please help me load sentinel rom. That's the one I was gonna do.
Okay now for the question... I was running stock 4.1.2 with siyah kernel 6.0 b5. Then I decided to install philz kernel, but ended up in bootloop. Then I tried flashing dorimanx but still in bootloop. All the while I wiped everything before flashing.
Now im stuck as I can boot into recovery via any kernel but ultimately phone is stuck.
What to do?
And can anyone give me steps to install sentinel rom from this stage?
Click to expand...
Click to collapse
Mate, sorry for waiting, I was out of home. We will get your ROM back as soon as the phone boots again.
Don't worry, it doesn't sound serious so far. We have recovery and download mode (so topic name "nothing works" isn't really correct)
Formatting /system wipes all data from the system partition (so your system will be gone then) and it is important to do before installing new ROMs (essencially important for KitKat). It can't do any harm. As you have tried to install other kernels and didn't work we should check first what did you try to flash so far and it didn't boot? Is that what you wrote all what you have tried?
Now let me know please which recovery do you have now and is it the same version like when you have created your nandroid backup? If the recovery is the same, I would indeed try to restore nandroid backup right after wiping /system. Before you wipe the system just let me know: can you use ADB? If yes, check do you have ADB connection in the recovery mode?
tetakpatak said:
Mate, sorry for waiting, I was out of home. We will get your ROM back as soon as the phone boots again.
Don't worry, it doesn't sound serious so far. We have recovery and download mode (so topic name "nothing works" isn't really correct)
Formatting /system wipes all data from the system partition (so your system will be gone then) and it is important to do before installing new ROMs (essencially important for KitKat). It can't do any harm. As you have tried to install other kernels and didn't work we should check first what did you try to flash so far and it didn't boot? Is that what you wrote all what you have tried?
Now let me know please which recovery do you have now and is it the same version like when you have created your nandroid backup? If the recovery is the same, I would indeed try to restore nandroid backup right after wiping /system. Before you wipe the system just let me know: can you use ADB? If yes, check do you have ADB connection in the recovery mode?
Click to expand...
Click to collapse
Will it wipe the internal memory? Or the rom in the phone?
I have cwm based recovery v. 6.0.1.2. Yes I used it to make the backup.
Checking for adb.. How do I do it? .
Sent from my Nexus 4 using xda app-developers app
AndroidReborn said:
Will it wipe the internal memory? Or the rom in the phone?
I have cwm based recovery v. 6.0.1.2. Yes I used it to make the backup.
Checking for adb.. How do I do it?
Click to expand...
Click to collapse
Hi! Internal memory usually shouldn't get wiped by formatting /system, as it is "storage", not part of the system. I would give a try, wipe all: data/factory reset, cache, dalvik cache (advanced) and format /system (mounts and storage). Then back to the main menu --> backup & restore --> restore from (internal or external memory where your nandroid is saved) and choose your backup. It should reboot normally then.
tetakpatak said:
Hi! Internal memory usually shouldn't get wiped by formatting /system, as it is "storage", not part of the system. I would give a try, wipe all: data/factory reset, cache, dalvik cache (advanced) and format /system (mounts and storage). Then back to the main menu --> backup & restore --> restore from (internal or external memory where your nandroid is saved) and choose your backup. It should reboot normally then.
Click to expand...
Click to collapse
Thanks for helping, but I ended up downloading the stock rom and flashing it. Everything was normal. Then I installed cm10.2 so everything's great now. Thanks!
Sent from my Nexus 4 using xda app-developers app
Cool, @AndroidReborn! Now you can install your old ROM again and restore nandroid. Keep that stock FW saved on your PC, so if your phone gets ever again soft-bricked, no problem to revive it again.
I am wondering how nobody here responsed your help prompt, we have in i9000 help threads always handfull people of experience and skills who are ready to help in need. And there are double amount of the SGS2 units sold around the world.... strange.
tetakpatak said:
Cool, @AndroidReborn! Now you can install your old ROM again and restore nandroid. Keep that stock FW saved on your PC, so if your phone gets ever again soft-bricked, no problem to revive it again.
I am wondering how nobody here responsed your help prompt, we have in i9000 help threads always handfull people of experience and skills who are ready to help in need. And there are double amount of the SGS2 units sold around the world.... strange.
Click to expand...
Click to collapse
No idea. The people seem pretty 'busy'. Thanks for helping. Just one teeny tiny last question.. How do I install cm11 or any kitkat rom over this? Cwm is 6.0.4.5 so it's compatible...
Sent from my Nexus 4 using xda app-developers app
If you want to flash kitkat, the first thing you need to do is flash a kitkat compatible CWM (v6.0.4.7). If you try to flash KK with an 'older' CWM, you'll get 'installation aborted....error status 7' or something similar........
I'm currently running @infected_s KK build, and in the OP, you will find download links for the correct CWM, ROM and GApps files.......
Sent from my Infected KitKat bar.....
keithross39 said:
If you want to flash kitkat, the first thing you need to do is flash a kitkat compatible CWM (v6.0.4.7). If you try to flash KK with an 'older' CWM, you'll get 'installation aborted....error status 7' or something similar........
I'm currently running @infected_s KK build, and in the OP, you will find download links for the correct CWM, ROM and GApps files.......
Sent from my Infected KitKat bar.....
Click to expand...
Click to collapse
6.0.4.5 is compatible? I think so ......
Sent from my Nexus 4 using xda app-developers app
I've always read....not.....
In any case, probably best not to risk it......
6.0.4.7 is DEFINITELY KK compatible.... and it'd take a couple of seconds to flash.........
Sent from my Infected KitKat bar.....
AndroidReborn said:
No idea. The people seem pretty 'busy'. Thanks for helping. Just one teeny tiny last question.. How do I install cm11 or any kitkat rom over this? Cwm is 6.0.4.5 so it's compatible...
Click to expand...
Click to collapse
Yes, mate, CWM 6.0.4.5 is capable of flashing KitKat.
It is usually always the same:
download your ROM zip and compatible Gapps
check in the phone (or PC) if the zips are corrupted through download (if they open after clicking them, they are fine)
move the zips to the folder you will flash it from (if you use PC to flash zips with ADB sideload, put them in the sdk/platform-tools folder)
make nandroid backup of your presently used ROM
wipe data/factory reset
wipe cache
wipe dalvik cache (advanced)
format /system (under mount and storage)
flash ROM.zip
flash Gapps
reboot
It is in general always good to read in the development thread of the ROM you attend to flash in the opening post which Gapps are recommended, or if there is some unusual order of flashing (sometimes, developers recommend reboot system after flashing ROM, and after that going to recovery and flash Gapps zip.
Some KitKat ROMs struggle with root access by using Superuser, so SuperSU should be flashed. If SuperSU app from Play Store gives errors by updating binary, you should uninstall SuperSU app then, find in the Chainfire's thread the compatible UPDATE-SuperSu.zip (version for your phone), flash its zip in the recovery, install SuperSU app, update binary (either "normal" or "through CWM/TWRP")
So I finally took a shot at flashing a custom ROM ( from stock to unified 4.4 ROM). When I attempted to revert back to stock nandroid backup, everything went completely haywire. The radio was disabled and I got recurring process close errors. All I could do was battery pull and flash back to the ROM.
What do I need to make my nandroid recovery work correctly? I'm on CWM if that matters.
Sounds like you didn't wipe correctly..... wipe system ,data, cache and davlik
Sent from my SM-N900P using Xparent BlueTapatalk 2
Epix4G said:
Sounds like you didn't wipe correctly..... wipe system ,data, cache and davlik
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Tried it again, this time the radio is on, but otherwise, same result. Did all wipe options five times just to be sure.
Zhuge_Liang said:
Tried it again, this time the radio is on, but otherwise, same result. Did all wipe options five times just to be sure.
Click to expand...
Click to collapse
you didnt say what your trying to restore...... is it nab based or mj4 or aosp if its 4.2 mj4 and you were on aosp 4.4.2 you need to wipe internal sd as well. will cause issues. what recovery are you using twrp or philz?
kaos420 said:
you didnt say what your trying to restore...... is it nab based or mj4 or aosp if its 4.2 mj4 and you were on aosp 4.4.2 you need to wipe internal sd as well. will cause issues. what recovery are you using twrp or philz?
Click to expand...
Click to collapse
I was originally flashing a Pac-ROM 4.4.2, then tried to flash back to my stock nandroid. My recovery is CWM, not Philz. Unless I also needed to flash cache partition too? I thought the factory reset option took care of that as well? I'll try this again.
EDIT: Formatted internal SD as well, same result. Got the same process and gapps errors. I really have no clue as to what other options I have. Perhaps loading up a ROM just to use that Philz recovery?
Yep, PhilZ recovery was the difference maker. I guess I'm done with CWM for good.
Zhuge_Liang said:
Yep, PhilZ recovery was the difference maker. I guess I'm done with CWM for good.
Click to expand...
Click to collapse
What did you do different to clear the issue?
Tw1sted247 said:
What did you do different to clear the issue?
Click to expand...
Click to collapse
Honestly, that was really all it was. Using a different recovery made all the difference.