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.
Related
Hi,
I just bought an AT&T SGS2. I began by rooting it, flashing cwm and trying to flash MIUI. But the phone would not boot up. So I downloaded ODIN one click back to stock and flashed that, but the phone still does not boot past the AT&T screen. I've tried flashing different roms from cwm none of which boot up.
Please point me in the right direction to get the phone to boot.
Thanks
Can you get into cwm? Id bet you didn't wipe before you flashed
smknutson said:
Can you get into cwm? Id bet you didn't wipe before you flashed
Click to expand...
Click to collapse
+1 this.
boot into cwm>factory wipe data/factory>delete cache partition>delete dalvik cache> install zip from sdcard>pick your ROM...
Thanks guys wiping the all the caches did the trick. I didn't know it was a requirement for this phone. I came from a Captivate where is wasn't required to wipe everything.
Sent from my SGH-I777 using XDA App
smknutson said:
Can you get into cwm? Id bet you didn't wipe before you flashed
Click to expand...
Click to collapse
He doesn't have CWM if he used the one-click back to stock, unless it failed and didn't flash a kernel. Stock kernel has 3e recovery.
kperajis said:
Thanks guys wiping the all the caches did the trick. I didn't know it was a requirement for this phone. I came from a Captivate where is wasn't required to wipe everything.
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
Even on the Captivate, you had to wipe whenever flashing a new ROM. Returning to stock is, effectively, flashing a new ROM (the stock one).
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
Just bought a used phone off Swappa. It has TWRP and had Cyanogenmod installed.
I wanted to try a TouchWiz ROM so I downloaded one. Booted into recovery, made a backup to external SD Card and then flashed the ROM. It said it flashed
successfully but when rebooted, it just stayed at the Samsung Galaxy S4 Boot
screen.
I tried restoring the backup, but it failed!
I thought I might have had a bad download so I downloaded Cyanogenmod nightly and LiquidSmooth on my laptop, transfered to the SD card, popped it into the S4, boot into recovery, and tried flashing each, and both just boot to the boot screen and freeze.
What are my best options now? I saw some guides for flashing back to stock via Odin, but requires that I know if I am on VRUAME7 or VRUAMDK and I don't know. Could I have been on ME7 and running Cyanogenmod? Doesn't seem possible, no?
Me7 ota doesnt have the ability to flash custom recovery or rom, so no you werent on that beforehand. Whenever you flash a rom you need to do a wipe/factory reset and wipe caches, unless op states you can dirty flash. Doing some reading will only help you out, generally every post outlines the installation process. Boot to recovery do your wipes then try booting again. If your still in a bootloop then you will need to flash mdk via odin then start the rooting and romming process over.
Sent from my SCH-I545 using Tapatalk 2
Man, I thought I did everything right.
First, did a backup.
Then full wipe with TWRP full wipe, including cache.
Then flash ROM
I'll have to get familiar with Odin and find the MDK images.
Sometimes that happens. Could have been a bad download then it happens more often then you would think. If theres an md5 hash posted its a good idea to verify the download is good. In the dev section theres no wipe mdk images posted so you wont lose your already installed apps and data.
Sent from my SCH-I545 using Tapatalk 2
So I downloaded the factory image and flashed via Odin, but accidentally flashed via bootloader rather than PDA. It wouldn't start - still hung at the boot screen, so I re-flashed via PDA and it is still hanging at the boot screen.
Now I don't know if it is just the same problem as before, or if I messed something up with flashing through bootloader. Can I reflash something via the bootloader section of Odin to restore it?
What version of twrp? And try to go back into recovery and wipe cache and dalvik.
That worked for me on the buggy version of twrp when it wouldn't booy
Sent from my SCH-I545 using Tapatalk 2
twiz0r said:
What version of twrp? And try to go back into recovery and wipe cache and dalvik.
That worked for me on the buggy version of twrp when it wouldn't booy
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Not sure what version it was because it's now back to factory recovery. I did go back into it and did a factory wipe and it booted!
Hi, all!
I have that annoying problem with all the 4.3 ROM I've tried with no exception. Everything is fine until the first reboot. Then it's stuck on the first Galaxy SIII boot logo. I'm using TWRP - the latest version if it matters.
I always wipe everything first.
Please give more details on how you flash it.
Enviado do meu GT-I9305 utilizando o Tapatalk now Free
nikolav75 said:
Hi, all!
I have that annoying problem with all the 4.3 ROM I've tried with no exception. Everything is fine until the first reboot. Then it's stuck on the first Galaxy SIII boot logo. I'm using TWRP - the latest version if it matters.
I always wipe everything first.
Click to expand...
Click to collapse
!!ALL QUESTIONS GO IN THE Q&A FORUM!! OR THEY MAY BE DELETED!!
nikolav75 said:
Hi, all!
I have that annoying problem with all the 4.3 ROM I've tried with no exception. Everything is fine until the first reboot. Then it's stuck on the first Galaxy SIII boot logo. I'm using TWRP - the latest version if it matters.
I always wipe everything first.
Click to expand...
Click to collapse
If you did all required wipes and followed the instructions did you try a different recovery? I read in the SB thread for example of people having issues with TWRP
Sent from my Nexus 7 (2013)
I am sorry for the wrong section. May I ask some to move it to Q&A?
I always wipe data, cash, dalvik cash, system. Then install the ROM and gapps...
After the restart I set up the google account and etc. And after the first restart the phone freezes. That's all.
I'll try with different recovery.
PS. I've just tried CWM recovery 6.0.3.3. and Omega AOSP v9. Still the same.
Try cwm 6.0.3.6 and after you install the rom and after its set up go to recovery and factory reset
nikolav75 said:
I am sorry for the wrong section. May I ask some to move it to Q&A?
I always wipe data, cash, dalvik cash, system. Then install the ROM and gapps...
After the restart I set up the google account and etc. And after the first restart the phone freezes. That's all.
I'll try with different recovery.
PS. I've just tried CWM recovery 6.0.3.3. and Omega AOSP v9. Still the same.
Click to expand...
Click to collapse
That's strange, I run Philz recovery and every 4.3 flash till now went through without issue.
Sent from my GT-I9300 using xda app-developers app
I tried all the recoveries I could find. Including Philz. Still the same.
And something else strange. I installed CWM, CWM, touch and Philz and with them I made backups. After restoration of the backup the phone freezes. I also tried to install Omega 49 and the installation goes OK, but freezes before the first start-up.
The only solution was to install manually TWRP (Odin) to restore some of my old backups. I'm beginning to think that there is something wrong with my phone. It's black if it is important.
Suggest total wipe of phone install your stock rom and test
Hi,
I just want to say I'm also having the same problem.
Started using TWRP with full wipe, same issue on 4.3 and no issues on 4.2.
On latest CWM same problem and 4.2 wont even pass the first boot on Samsung logo.
Also had to use Odin to get back on TWRP and flash a 4.2 rom again.
Anyway there is one more thing I would like to try but haven't had the chance to do so, is installing the latest modem and ril. But I'm kind skeptic about that currently because there is also some risks and my S3 is my daily driver.
Don't change the ril on any custom as you stand a big chance of breaking the calls and Tex's. Modem yes but not ril. Do change to cwm and retry.
andrewwright said:
Don't change the ril on any custom as you stand a big chance of breaking the calls and Tex's. Modem yes but not ril. Do change to cwm and retry.
Click to expand...
Click to collapse
Thanks for the info, I was planning to read more about it before I would make an attempt. BTW already tried CWM that only made things worse, couldn't flash any rom without getting stuck on samsung screen.
bla166 said:
Thanks for the info, I was planning to read more about it before I would make an attempt. BTW already tried CWM that only made things worse, couldn't flash any rom without getting stuck on samsung screen.
Click to expand...
Click to collapse
You are doing a full wipe?. System and data is the main thing to wipe not just factory reset. So go into mounts and storage and format data,system and cache there then flash the rom /gapps.
andrewwright said:
You are doing a full wipe?. System and data is the main thing to wipe not just factory reset. So go into mounts and storage and format data,system and cache there then flash the rom /gapps.
Click to expand...
Click to collapse
yes tried that, also used the mega wipe zip thing
Start fresh and flash stock with Odin then try again after you root and install cwm.
andrewwright said:
Start fresh and flash stock with Odin then try again after you root and install cwm.
Click to expand...
Click to collapse
Tried to go stock and flashed a 4.3 rom again that fixed my problem. =)
Thanks! :good:
I'll try it too. And one stupid question. Where do I find a stock ROM? I never did it before
nikolav75 said:
I'll try it too. And one stupid question. Where do I find a stock ROM? I never did it before
Click to expand...
Click to collapse
http://www.sammobile.com/
Thank you!
But nothing helped. I flashed a stock ROM, with Odin. First I tried with TWRP, and the second time (again after flashing stock) with CWM recovery. I tried two 4.3 ROMs. They both can't boot after the first reboot.
nikolav75 said:
Thank you!
But nothing helped. I flashed a stock ROM, with Odin. First I tried with TWRP, and the second time (again after flashing stock) with CWM recovery. I tried two 4.3 ROMs. They both can't boot after the first reboot.
Click to expand...
Click to collapse
Hi, I think I did the following steps to get it working on my device.
1. Flash stock with odin
2. Hard reset
3. Boot up and finish first run menus
4. Flash twrp with odin
5. Format data with twrp
6. Flash 4.3 rom
I followed the procedures accurately I believe:
upgraded to 4.4.2 rooted with SS 3.72
wiped dalvik, system, cache
flashed ROM
flashed supersu and nc5 module (found here http://www.androidfilehost.com/?fid=23486521113837640)
rebooted.
Stuck on samsung custom screen. I did it twice, thinking I did something wrong first time...
I do know how to odin back, but I would like to be able to figure out why hyperdrive isn't installing, and get it working.
any help is appreciated!
Dave
biikman said:
I followed the procedures accurately I believe:
upgraded to 4.4.2 rooted with SS 3.72
wiped dalvik, system, cache
flashed ROM
flashed supersu and nc5 module (found here http://www.androidfilehost.com/?fid=23486521113837640)
rebooted.
Stuck on samsung custom screen. I did it twice, thinking I did something wrong first time...
I do know how to odin back, but I would like to be able to figure out why hyperdrive isn't installing, and get it working.
any help is appreciated!
Dave
Click to expand...
Click to collapse
Perhaps I put this in the wrong place, if so can a MOD move to correct category?
biikman said:
I followed the procedures accurately I believe:
upgraded to 4.4.2 rooted with SS 3.72
wiped dalvik, system, cache
flashed ROM
flashed supersu and nc5 module (found here http://www.androidfilehost.com/?fid=23486521113837640)
rebooted.
Stuck on samsung custom screen. I did it twice, thinking I did something wrong first time...
I do know how to odin back, but I would like to be able to figure out why hyperdrive isn't installing, and get it working.
any help is appreciated!
Dave
Click to expand...
Click to collapse
Does the safe strap flash screen come up..did you install to stock slot?
Sent from my GT-I9505 using Tapatalk
decaturbob said:
Does the safe strap flash screen come up..did you install to stock slot?
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
thanks for the reply...I did install it on the stock slot, and no, I do not get to the SS flash screen. It stays Stuck on samsung custom screen, with the open padlock.
biikman said:
thanks for the reply...I did install it on the stock slot, and no, I do not get to the SS flash screen. It stays Stuck on samsung custom screen, with the open padlock.
Click to expand...
Click to collapse
You probably need to full wipe nc5 odin and start over.
Sent from my GT-I9505 using Tapatalk
decaturbob said:
You probably need to full wipe nc5 odin and start over.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
that was my thought...I have done it 3 times with the same result
biikman said:
that was my thought...I have done it 3 times with the same result
Click to expand...
Click to collapse
Download all files to pc and verify md5 s before moving hd zip to phone
sent by safestrap powered echo v26
decaturbob said:
Download all files to pc and verify md5 s before moving hd zip to phone
sent by safestrap powered echo v26
Click to expand...
Click to collapse
ok, redownloaded hyperdrive and verified the MD5.
before I try again for #4, when I wipe dalvik, system, cache, I should do it through safestrap correct? I did see an option in the hyperdrive install for a full system wipe..
thanks!
Dave
biikman said:
ok, redownloaded hyperdrive and verified the MD5.
before I try again for #4, when I wipe dalvik, system, cache, I should do it through safestrap correct? I did see an option in the hyperdrive install for a full system wipe..
thanks!
Dave
Click to expand...
Click to collapse
I'd say do it before that, in recovery. Then do it again in SS if you can. That way you can be sure you got the right one, and the other one won't matter.
decaturbob said:
Download all files to pc and verify md5 s before moving hd zip to phone
sent by safestrap powered echo v26
Click to expand...
Click to collapse
It looks like this did the trick. redoloaded the files and went smoothly. thanks much!