Related
Thanks to Hobby31 (http://forum.xda-developers.com/member.php?u=2360932) for figuring this out. I have taken his post, and rewritten for ease of reading. Tested and working on (at least) 2 phones so far.
How to restore a Nandroid or flash new ROM with CWM Touch
In CWM Touch Recovery
1. Go to mounts and storage and unmount cache.
2. Make a nandroid. (Going back to mounts and storage, you will see data is mounted and will not unmount.)
3. Go to "advanced" and select reboot recovery.
4. Once phone reboots into recovery, go back to mounts and storage and see that data is unmounted. You may now wipe data, system, and cache.
5. You may now restore a nandroid or flash a new rom.
Recommendation : As noted below, proper wiping matters when switching between roms, particularly from ICS to JB. Use superwipe from Mike (android revolution HD) when moving between roms. http://api.viglink.com/api/click?fo...="0" alt="">&jsonp=vglnk_jsonp_13416929577832
If this helped you, hit thanks. Also, thank hobby 31. Thread here. http://forum.xda-developers.com/showthread.php?t=1748049
EDIT 7-19-12 If you say "I've had no issues doing backups and restores with CWM," please ask yourself the following questions:
1. Are you using CWM Touch or non-touch? This is a Touch issue. If you are using the non-touch... you need not read further or report "I have no problems" because this is specifically related to Touch. (Please note I have not flashed the new 6.0 CWR Touch as some people are reporting problems with it also.)
2. Did you do multiple operations in the same recovery session? Meaning did you wipe data/factory reset, wipe cache, wipe delvik? Then did you try to flash a new ROM or restore a backup without restarting recovery? The reason this matters is because this issue of data not unmounting seems to happen in Touch CWM after a wipe is performed. You might be able to do one action per recovery session, but doing multiple actions that require data to be unmounted are what borks the operation and leaves some people hanging at the glowing X of "Oh crap I need to boot back into recovery."
Let me know if there are any problems, need for further clarification.
I flashed an older version of CWM (5.5.0.4) Non Touch version so I could flash JB but my SD card would not mount after I did a full wipe. Had to use the Toolkit to flash stock image. Do you know what would cause that to happen? People are saying to use the older version to flash JB and I want to try VanirBEAN ROM but don't want to run into the same SD mount issues.
I have not had any difficulty restoring cwm nandroid backups of other ROMs, or flashing other ROMs coming from V3. Have not had to resort to any of these steps. But I have seen a lot of threads about others having a lot of problems. Just curious if anyone has any theories about why this is?
Gallery69 said:
I flashed an older version of CWM (5.5.0.4) Non Touch version so I could flash JB but my SD card would not mount after I did a full wipe. Had to use the Toolkit to flash stock image. Do you know what would cause that to happen? People are saying to use the older version to flash JB and I want to try VanirBEAN ROM but don't want to run into the same SD mount issues.
Click to expand...
Click to collapse
I flashed the BAMF You Jelly Huh? ROM using the clockwork touch recovery and it worked flawlessly (I did wipe data though)
cam30era said:
I have not had any difficulty restoring cwm nandroid backups of other ROMs, or flashing other ROMs coming from V3. Have not had to resort to any of these steps. But I have seen a lot of threads about others having a lot of problems. Just curious if anyone has any theories about why this is?
Click to expand...
Click to collapse
After talking with others, I think my issue was after flashing the older CWM I did not reboot before moving forward with the wipe. Too chicken to try it again
I think it has to do with the coding in vicious and some of the initial releases of JB roms. Coupled with the data not unmounting at the proper time. A couple people also have mentioned that they didn't do as full of a wipe as is done with the super wipe script, hence why a lot of devs suggest using it to clean out old ics code.
Has nothing to do with Viscious. Same on JellyBelly 3.x Even when moving between JB roms, Data won't unmount when performing multiple operations.
I have flashed all three versions of Vicious' JB with CWM Touch and have not had a single problem. My process is as follows:
-Backup
-format /cache
-format /data
-format /system
-Wipe Dalvik cache
-Flash ROM
-Wipe Dalvik cache
-Reboot
-????????
-Profit
Team win recovery aka twrp. Everyone done says "use non touch recovery" it doesn't matter. Haven't had a single issue using twrp on this phone or any of my previous phones. It works great. Especially with super wipe scripts.
Sent from my Galaxy Nexus using Tapatalk 2
Omen87 said:
I have flashed all three versions of Vicious' JB with CWM Touch and have not had a single problem. My process is as follows:
-Backup
-format /cache
-format /data
-format /system
-Wipe Dalvik cache
-Flash ROM
-Wipe Dalvik cache
-Reboot
-????????
-Profit
Click to expand...
Click to collapse
Bingo. That's what superwipe does.
Added link to Mike's superwipe.
Sorry for the dumb question, but ive done a search and found conflicting answers. When you wipe data and cache do you want them to be mounted or unmounted?
Sent from my Transformer TF101 using Tapatalk 2
I have Touch CWM and I have no problems flashing back and forth between JB and ICS roms and nandroids.
You just have to flash a Super Wipe in between.
I just did this yesterday to test out my MHL adapter. Backed up my JB rom, super wiped, restored my ICS Liquid Rom, tested, super wiped, restored my JB rom.
I think super wipe is key in going between different rom builds. But I've had absolutely no problem using CWM at all. If Super wipe is the answer, then perhaps CWM's Factory Reset option isn't wiping as well as it should.
Flashing a SuperWipe is much easier then having to restart the phone a few times.
I think it may be related to Viscious old versions. Not Sure. Using Jelly Belly now. If you are not having problems, that's great. I used superwipe script. No problems. But, if people want the manual solution without getting errors, then at least we know the above method works. It might not be neccesary now with the newer releases, maybe data will unmount ok.
If anyone wants to test and see if they can restore old backups from ICS w/out doing the above steps (IE the rebooting) and report back, it'd be appreciated. I will be uber busy the next couple days or I'd take the time to backup to my computer before trying.
Would you mind sending me the super wipe script to flash? Or point me to the thread?
Sent from my Galaxy Nexus using xda premium
mikeacela said:
Would you mind sending me the super wipe script to flash? Or point me to the thread?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Link on Page 1... Sorry, I'm on my phone or I'd paste it for you.
player911 said:
I have Touch CWM and I have no problems flashing back and forth between JB and ICS roms and nandroids.
You just have to flash a Super Wipe in between.
I just did this yesterday to test out my MHL adapter. Backed up my JB rom, super wiped, restored my ICS Liquid Rom, tested, super wiped, restored my JB rom.
I think super wipe is key in going between different rom builds. But I've had absolutely no problem using CWM at all. If Super wipe is the answer, then perhaps CWM's Factory Reset option isn't wiping as well as it should.
Flashing a SuperWipe is much easier then having to restart the phone a few times.
Click to expand...
Click to collapse
I'm running CWMR 5.8.0.2 and I've restored my ICS roms over several JB roms without issue and no use of any sort of superwipe script.
nhizzat said:
I'm running CWMR 5.8.0.2 and I've restored my ICS roms over several JB roms without issue and no use of any sort of superwipe script.
Click to expand...
Click to collapse
This. ^^^^^^
Sent from my Galaxy Nexus using xda app-developers app
nickles96 said:
This. ^^^^^^
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Are you using Touch Based CWMR? Or Standard.
I can confirm even with Jelly 3.6, that after I wipe data, cache, and delvik that the data will then remain mounted and not unmount unless I restart recovery.
This can/does cause problems and messes up operations when people are doing multiple actions in recovery at the same time. You might be able to do one action, such as making a backup just fine. But if you are using CWMR Touch, you might have issues with doing multiple operations in the same recovery session, like, backup, wiping, then restoring if the action you are doing requires data to unmount.
So, if you say "I have no problems..." please confirm that you are using touch recovery... not just standard.
CWM Touch was updated to 6.0.0.5 this week, is this issue still present? I haven't experienced any problems yet using CWM Touch, I'm just curious.
My steps are 1. Backup 2. Wipe data/factory reset 3. Wipe cache partition 4. Wipe Dalvik cache 5. Flash ROM 6. Flash GApps if needed 7. Reboot
This is my first phone that doesn't have an external SD card and I'm not 100% sure how to properly perform a full wipe it
I know this is a noob question, but I just don't want to brick my phone.
What I Used to Do
Back in the day with my SGS Captivate or SGS2 I just put all my files on my external SD card, then via Android (Astro File Manager) I deleted every folder from the internal SD card, booted into CWM, performed a wipe/factory default, cleared cache, formatted system partition and then installed custom ROM and everything worked fine.
What I Need
I want to be sure that I don't brick it so I'm hoping that someone can give me a step-by-step walk-through of how to install CM 10.1 (or any other ROM i guess) on my phone after completely wiping it of anything on it.
What I've Tried
I used the Galaxy Nexus Toolkit to unlock, root and install CWM but unfortunately when I then installed CM 10.1 via CWM, some leftover files remained from the stock ROM.
Basically, my phone is ridiculously slow/lagging and I'm getting sick of it.
I've tried installing a custom kernel (Franco Kernel), I've set the CPU governor on Performance (1200MHz always) uninstalling any un-needed apps... but my phone is still un-usable.
Sometimes when I install the latest nightly of CM 10.1 I do an update and other times I tried doing a full install where I wipe the Dalvik; neither way helps I still get the ridiculous lag.
The definition of a full wipe:
-wipe data / factory reset
-wipe cache
-wipe dalvik cache
-(optional) format system
Then flash the rom/gapps/kernel.
Maybe you have a "bricked" phone. It has something to do with the emmc chip. How much free storage do you have?
Check it by downloading the app in the screenshot.
If you havent a bricked emmc version, then I suggest returning to stock again, and then root again. ( most clean process , as it restores all the partitions to the stock state.)
Hopefully this helps my friend!
PS: you posted in the wrong forum, don't do it in the future
Sent from my Nexus Prime
That's not related to development, read the rules next time.
Try the full wipe zip from Android Revolution HD Rom.
Use the pinned guide for fast boot. Use fast boot format/erase commands for all partitions, and for good measure flash to stock with fast boot also. This is the most surefire way and it hasn't failed me yet.
thegtfusion said:
The definition of a full wipe:
-wipe data / factory reset
-wipe cache
-wipe dalvik cache
-(optional) format system
Then flash the rom/gapps/kernel.
Maybe you have a "bricked" phone. It has something to do with the emmc chip. How much free storage do you have?
Check it by downloading the app in the screenshot.
If you havent a bricked emmc version, then I suggest returning to stock again, and then root again. ( most clean process , as it restores all the partitions to the stock state.)
Hopefully this helps my friend!
PS: you posted in the wrong forum, don't do it in the future
Sent from my Nexus Prime
Click to expand...
Click to collapse
Thanks for the info, I'll be more careful in the future where I post.
I have the 16GB model and 4GB free right now.
I installed the eMMC Brickbug Check app and it says that my chip is ok (sane).
My phone is definately rooted, so I'm not sure why this app says that root is required for the memory test (clicking it just launches wiki page on rooting).
https://www.dropbox.com/s/gzuzhn22n0f354w/Screenshot_2013-01-28-11-07-40.png
If you're on 4.2.1 you won't see any CWM backups so get ES File Explorer, give it root access and then go to /data/media/clockworkmod and see what's about. Or boot into CWM and delete some old backups
As for a full wipe, I use this before flashing a new ROM:
http://www.mediafire.com/download.php?lxpw84fwtm5cj6w
EddyOS said:
If you're on 4.2.1 you won't see any CWM backups so get ES File Explorer, give it root access and then go to /data/media/clockworkmod and see what's about. Or boot into CWM and delete some old backups
Click to expand...
Click to collapse
It totally forgot about the CWM backups
I'll delete those ASAP
There wasn't a lot in the backups folder but there is about 3.82 GB in the blobs folder in the clockworkmod folder; are those ok to delete?
Flash the newest version of CWM (6.0.2.3) as it doesn't use blobs any more. Delete all old backups and take a new one if you want. Also, check when I added to my last post
EddyOS said:
Flash the newest version of CWM (6.0.2.3) as it doesn't use blobs any more. Delete all old backups and take a new one if you want. Also, check when I added to my last post
Click to expand...
Click to collapse
Thanks a lot, I'll give that a shot tonight.
I'll update CWM to the latest, then run your super wipe zip followed by the latest CM 10.1.
Thanks a lot for the super wipe zip too.
After wiping and flashing go ahead and run fix permission too.
EddyOS said:
Flash the newest version of CWM (6.0.2.3) as it doesn't use blobs any more. Delete all old backups and take a new one if you want. Also, check when I added to my last post
Click to expand...
Click to collapse
WiredPirate said:
After wiping and flashing go ahead and run fix permission too.
Click to expand...
Click to collapse
Thanks guys, my phone is usable again
You guys are awesome.
What I Did
- installed the latest CWM using fastboot
- booted into recovery
- used adb to sideload your super wipe script, then the latest CM 10.1 nightly and then the latest gapps
- fixed permissions via CWM
- restarted my phone to get a very responsive phone again
With my last 2 phones I was spoiled having external SD cards so that i never had to sideload or use fastboot (I let Odin do that part).
My T-Mobile Galaxy s4 M919 will not boot after any custom ROM flashes. I tried 4 different ROMs with success messages. As soon as I reboot my phone after the ROM flash, it's stuck at the Samsung Galaxy S4 logo and would not enter the "phone desktop". I can easily enter download mode and recovery mode without any issue.
Background: I rooted with Odin successfully. (Used both CWM and OUDHS with the same no-boot results after flashing any custom ROMs). I can restore back to stock and phone boot up fine but tried root again and then with custom ROM and it would not boot. Any help would appreciate it.
After flashing a rom, go into recovery, and erase stuff. Like cache and dalvik cache. Possibly even data
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
After flashing a rom, go into recovery, and erase stuff. Like cache and dalvik cache. Possibly even data
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did that after each ROM flash. 1. Wipe data/factory reset, 2. wipe cache part, 3. wipe dalvik cache. Did not fix the problem. No good. Please clarify "possibly even data". I am not sure which wipe is that.
anothersaddream said:
I did that after each ROM flash. 1. Wipe data/factory reset, 2. wipe cache part, 3. wipe dalvik cache. Did not fix the problem. No good. Please clarify "possibly even data". I am not sure which wipe is that.
Click to expand...
Click to collapse
using CWM:
*wipe data/factory reset
*wipe cache
*wipe, dalvik cache
*wipe system
*wipe sdcard (only if you have the ROMs you plan on flashing on your external sdcard, this will erase internal sd)
now flash your ROM of choice. reboot (will take 1-2min on first boot)
use cwm touch. what ROMs have you tried so far?
I am thinking you are flashing something not specific to the TMo S4, so your not getting the right kernel installed. Try installing a TMo specific kernel immediately after flashing a rom and see what happens.
Yeah, what ROMs have you tried already? Have you tried TWRP 2.5 recovery?
Sometimes it'll take up to 10 minutes to boot up (I haven't experienced this yet with the GS4, but I have with other phones). How long did you wait before determining it was just stuck?
I switched to PhilZ Touch Recovery a couple of weeks ago and have not had Any issues as I did before.
TWRP 2.5.0.2 was issue free for months, until I started flashing ROMs with Aroma.
Nothing but issues re Samsung splash screen freezes, different solutions working sometimes and sometimes not, having to ODIN back to stock on many occasions, having to wipe INTERNAL SD on many occasions, etc., etc.
PhilZ was the solution.
This is coming from a hard core TWRP guy......
Check the link in Red in my sig for PhilZ and other good stuff
dynospectrum said:
using CWM:
*wipe data/factory reset
*wipe cache
*wipe, dalvik cache
*wipe system
*wipe sdcard (only if you have the ROMs you plan on flashing on your external sdcard, this will erase internal sd)
now flash your ROM of choice. reboot (will take 1-2min on first boot)
use cwm touch. what ROMs have you tried so far?
Click to expand...
Click to collapse
Where do you "wipe system"? I see a format /system inside Mounts and Storage Menu. Please confirm.
DKYang said:
Yeah, what ROMs have you tried already? Have you tried TWRP 2.5 recovery?
Sometimes it'll take up to 10 minutes to boot up (I haven't experienced this yet with the GS4, but I have with other phones). How long did you wait before determining it was just stuck?
Click to expand...
Click to collapse
I have not tried TWRP 2.5 recovery yet. I mostly use CWM. I have waited 20+ minutes after flashing a custom ROMs but to no success.
I have done the following ROMs:
Insanity v1
VirginROM
stevessvt said:
I am thinking you are flashing something not specific to the TMo S4, so your not getting the right kernel installed. Try installing a TMo specific kernel immediately after flashing a rom and see what happens.
Click to expand...
Click to collapse
I did try the InFamous ROM for Tmobile s4. This ROM also has a kernal. Same results, stuck at Samsung Galaxy s4 Logo screen. It would not go anywhere after that.
Really needing help here.
anothersaddream said:
I did try the InFamous ROM for Tmobile s4. This ROM also has a kernal. Same results, stuck at Samsung Galaxy s4 Logo screen. It would not go anywhere after that.
Really needing help here.
Click to expand...
Click to collapse
Okay let's start over from scratch.
First off can you restore the stock ROM using your nandroid backup?
Second, I don't think you are properly wiping everything prior to flashing the new ROM. You need to wipe system, data, dalvik, and cache in the CWM wipe menu prior to flashing the new ROM.
Wipe all 4 things. Wiping any less than all 4 things will cause the problems you are experiencing.
Once you've done that, then flash the ROM.zip and reboot and it should work just fine.
anothersaddream said:
Where do you "wipe system"? I see a format /system inside Mounts and Storage Menu. Please confirm.
Click to expand...
Click to collapse
wipe = format
yes, format system in mounts/storage.
Skipjacks said:
Okay let's start over from scratch.
First off can you restore the stock ROM using your nandroid backup?
Second, I don't think you are properly wiping everything prior to flashing the new ROM. You need to wipe system, data, dalvik, and cache in the CWM wipe menu prior to flashing the new ROM.
Wipe all 4 things. Wiping any less than all 4 things will cause the problems you are experiencing.
Once you've done that, then flash the ROM.zip and reboot and it should work just fine.
Click to expand...
Click to collapse
I did exactly what you stated. Restored to stock. Rooted successfully. Wiped all 4 things. ROM flash stated success. Still NO good. Stuck samsung S4 logo. You think there is something wrong with the hardware???? The s4 does randomly reboot on stock.
anothersaddream said:
I did exactly what you stated. Restored to stock. Rooted successfully. Wiped all 4 things. ROM flash stated success. Still NO good. Stuck samsung g4 logo. You think there is something wrong with the hardware???? The s4 does randomly reboot on stock.
Click to expand...
Click to collapse
When I was flashing ROMs w/Aroma using TWRP 2.5.0.2, I would sometimes get Samsung boot screen freezes. The only way I could resolve this was by wiping Internal SD, in addition to the other wipes mentioned, and flashing the ROM again.
find stock kernel, flash the roms you want and flash the stock kernel after and see if you boot
Biker1 said:
When I was flashing ROMs w/Aroma using TWRP 2.5.0.2, I would sometimes get Samsung boot screen freezes. The only way I could resolve this was by wiping Internal SD, in addition to the other wipes mentioned, and flashing the ROM again.
Click to expand...
Click to collapse
I also tried your suggestion exactly what you stated. Restored to stock. Rooted successfully. Wiped all 4 things + format /sdcard (internal SD). ROM flash stated success. Still NO good. Still Stuck Samsung S4 logo.
Is there any custom ROMs I can flash using odin?
anothersaddream said:
I also tried your suggestion exactly what you stated. Restored to stock. Rooted successfully. Wiped all 4 things + format /sdcard (internal SD). ROM flash stated success. Still NO good. Still Stuck Samsung S4 logo.
Is there any custom ROMs I can flash using odin?
Click to expand...
Click to collapse
ODIN Samsung Stock Firmware.
Boot.
ODIN Custom Recovery.
(I use PhilZ Touch Recovery. Flashes ROMs flawlessly )
Boot.
Flash custom ROM afterwards.
If ROM doesn't have Root, then Root with CF-AUTO-ROOT by Chainfire via ODIN prior to installing Custom Recovery.
Then flash custom ROM.
Biker1 said:
ODIN Samsung Stock Firmware.
Boot.
ODIN Custom Recovery.
(I use PhilZ Touch Recovery. Flashes ROMs flawlessly )
Boot.
Flash custom ROM afterwards.
If ROM doesn't have Root, then Root with CF-AUTO-ROOT by Chainfire via ODIN prior to installing Custom Recovery.
Then flash custom ROM.
Click to expand...
Click to collapse
I did as you stated. I love Philz Touch recovery UI. Very nice. Unfortunately, did not work as well. It stated successfully. I tried 2 rom, Infamous S4 v.2.5 and also the VirginROM v2.3.1. Both stated successful flashed but would not boot into the phone desktop. Stuck for over 10 minutes on black and white "Samsung Galaxy S4" logo.
I will send you a nice Starbucks gift card if anyone can fix this problem.
anothersaddream said:
I did as you stated. I love Philz Touch recovery UI. Very nice. Unfortunately, did not work as well. It stated successfully. I tried 2 rom, Infamous S4 v.2.5 and also the VirginROM v2.3.1. Both stated successful flashed but would not boot into the phone desktop. Stuck for over 10 minutes on black and white "Samsung Galaxy S4" logo.
I will send you a nice Starbucks gift card if anyone can fix this problem.
Click to expand...
Click to collapse
I have no idea why it ain't working for you.
On the plus side, I don't know everything
If you ODINd Stock.
ODINd Recovery.
Did a Md5 Checksum match between the ROM file and your Download.
Wiped Internal SD.
Flashed the ROM......
and you're still having issues.......
I'm at a loss....
Try again is my only suggestion, and insure the steps taken are correct, including ODINing the proper files for your device.
Check & Double check
Including making sure you have a good usb cable, which sometimes can work and sometimes not....
If you haven't, try flashing from internal sd card. Maybe remove th external sd card just in case.
since im new to xda i can not post on the main thread http://forum.xda-developers.com/showthread.php?t=2442977&page=12
so i had to create this one as a question, cause i have a problem installing this rom, i downloaded both the kernel and the rom from the main thread, i first flashed to stock rom with odin, then i followed every step to install the kernel and after the rom, but im stuck in boot loop and im kinda angry cause it seems like im the only one with that problem.
i tried to install the rom using white's 1.33 kernel instead of percy's kernel ( the one provided in the main thread) and then flashing the rom, and it kinda worked, because i didnt go in to boot loop, but neither wifi or bluetooth werent working.
pls help me!!! i really want to try this rom!
1.first flash stock ddlk2
2.download the rom and flash it after :
(i) formatting system,data and cache
(ii) mounting all partitions
When done flashing,wipe data and reboot
davithdeathrider said:
since im new to xda i can not post on the main thread http://forum.xda-developers.com/showthread.php?t=2442977&page=12
so i had to create this one as a question, cause i have a problem installing this rom, i downloaded both the kernel and the rom from the main thread, i first flashed to stock rom with odin, then i followed every step to install the kernel and after the rom, but im stuck in boot loop and im kinda angry cause it seems like im the only one with that problem.
i tried to install the rom using white's 1.33 kernel instead of percy's kernel ( the one provided in the main thread) and then flashing the rom, and it kinda worked, because i didnt go in to boot loop, but neither wifi or bluetooth werent working.
pls help me!!! i really want to try this rom!
Click to expand...
Click to collapse
Try this method
#1-Flash stock rom using odin
#2-Go to cwm
#3-Mount all partitions
#4-Install CyanogenMod#2 kernel
#5-Back and go to Advance then REBOOT RECOVERY
#6-You are on cwm now and the fonts are small
#7-Go to mounts and Format system,data,cache
#8-Dont press back -Mount all partitions
#9-Install zip from sd card-choose zip then choose The Rom
#10-When it is done flashing -Wipe Data - tHEN REBOOT
Do this.
1. Go to cwm recovery
2. Clear data and wipe cache
3. Go to advance :- wipe dalvik cache and battery states.
4. Go to mount & storage :- format system, data & cache.. dont format sd.
5. Then mount everything expect sd-ext.
6. Flash kernel.
7. Go to advance reboot recovery.
8. Again wipe data & cache.
9. go to advance and again wipe dalvik cache & battery states.
10. Mount everything expect sd-ext
This time you dont need to format system, data, or cache in mount.
11. Finally flash rom and reboot.
Hope it work.
Using optimus nexus me v5 on galaxy y
Hi,
For about a few days, I can't flash any touchwiz based rom, even the ones I could flash without any problem before. After I flash any touchwiz rom, my phone goes into a bootloop cycle. Though I can boot into recovery and download mode with key combinations. I don't know when this happened for the first time but as far as I can remember, it would be after I flashed some 4.4 AOSP rom (could be Omnirom, I'm not sure though)
What I did to recover from boot loop:
- Wipe cache, wipe dalvik cache and reboot, no joy.
- Wipe cache, wipe dalvik cache, wipe data, reboot, no joy.
- Wipe cache, wipe dalvik cache, wipe data, wipe data/media, reboot, no joy.
- Pulled out the battery between these steps too.
At first, I thought something was wrong about the aroma installer itself because the phone was getting frozen during aroma installer setup screen, then I came up that it was caused due to my older CWM version, so I updated the recovery and it didn't freze again during installation.
And by the way, I've lost my efs partition during these processes, thankfully I've had a nandroid backup from a couple of months before.
Now I'm stuck with AOSP roms and the only way I can use a touchwiz rom is to flash the stock rom via odin. But I want to use the new leaked version based Note3 featured roms.
I've seen similar topics at S4 section but I couldn't be sure if I can do the exact steps for an N7100 international device.
I'm pretty familiar with linux system and I can use adb so I can provide any kind of information you need to diagnose this issue. Thanks in advance. Best regards.
HOW I SOLVED THIS PROBLEM
- Wiped everything (system, data, sdcard, of course internal sdcard)
- Flashed n7100 16GB pit file via odin
- Flashed stock rom via odin
- During these steps, I realized that my CSC code had been changed, I've corrected it acording to my country code
- Rooted my phone again
- Flashed CWM 6.0.4.3 recovery
- Flashed DN3 V3.1 rom
- Bingo, I successifully booted into DN3 rom but had no WIFI
- Flashed MJ5 bootloader
- Rebooted, then WIFI worked without a problem
- Setup my phone and did some restore
It's all good now. Thanks for everything, I hope these steps can help someone facing the same problem.
Guys, I really need some help.. Any idea about what might the problem be?
Sent from my GT-N7100 using XDA Premium 4 mobile app
Download HD wipe script,flash the script zip via cwm/philz then try installing the rom of your choice.
I found the script from tamirda's phoenix rom thread and is very useful:http://d-h.st/fWr
Full wipe cache and reset in recovery menu, clear everything, you should be up and running.
akp.ajinkya said:
Download HD wipe script,flash the script zip via cwm/philz then try installing the rom of your choice.
I found the script from tamirda's phoenix rom thread and is very useful..
Click to expand...
Click to collapse
Thanks for the reply. I flashed this superwipe script, then flashed DN3 rom but still I got stuck at Samsung Galaxy Note II screen boot loop. I really don't understand this. What am I missing? What would happen if I wipe the entire internal memory block, I mean the whole things, even the root partition too.. I'm thinking that maybe there's some file inside the root partition that prevents me to flash touchwiz roms or perhaps something wrong about touchwiz based roms' bootloaders.. I'm truely pissed..
(InsertNameHere) said:
Full wipe cache and reset in recovery menu, clear everything, you should be up and running.
Click to expand...
Click to collapse
Have you read my first message? I remember that I've mentioned I've done already what you ask me to do.. Believe me I wouldn't shoot a new thread if I could've solved my problem with such easy steps. I've already done so many wipes, including internal SD and whatsoever.. I'm really confused and NEED help. Thanks anyway..
I think you can go for the method you mentioned.But also give a try to start fresh i.e pit file flashing...wiping everything n installing stock rom then rooting,flashing custom recovery n then installing any TW custom rom.
Also give other TW based roms a try too.
Im having the same problem but after flashing kernels (e.i. saber & perseus).
Im currently running on Tigra rom. Is this a compatibility issue or im just missing something here too?
I came across flashing bootimg but this thread http://forum.xda-developers.com/showthread.php?t=1752270
is for One S, im not sure if will work on Note 2 & haven't tried it yet.
Any suggestions? help pls...
akp.ajinkya said:
I think you can go for the method you mentioned.But also give a try to start fresh i.e pit file flashing...wiping everything n installing stock rom then rooting,flashing custom recovery n then installing any TW custom rom.
Also give other TW based roms a try too.
Click to expand...
Click to collapse
Well, the problem is gone.
What I did was the things you said.
- Wiped everything (system, data, sdcard, of course internal sdcard)
- Flashed n7100 16GB pit file via odin
- Flashed stock rom via odin
- During these steps, I realized that my CSC code had been changed, I've corrected it acording to my country code
- Rooted my phone again
- Flashed CWM 6.0.4.3 recovery
- Flashed DN3 V3.1 rom
- Bingo, I successifully booted into DN3 rom but had no WIFI
- Flashed MJ5 bootloader
- Rebooted, then WIFI worked without a problem
- Setup my phone and did some restore
It's all good now. Thanks for everything, I hope these steps can help someone facing the same problem.
Happy to help you bro