Related
So i'm going to consolidate and give everyone a brief recap on how I fixed my phone since it required the use of SEVERAL posts. I figured someone will eventually get caught in the same situation I was.
This is by no means the best way, or the correct way to fix any phone, do this at your own pace and liability. I am, and no one mentioned in this thread is liable for your phone.
Please excuse any of my grammar mistakes, this is spewing out as I type.
History: Stock DI01 update w/ JT's Voodoo .2 OC Kernel.
Flashed JT's Super Clean ROM V.4 & Remix Incognito Theme.
** Market would no longer work. I had this issue before updating to the 2.2 market after the DI01 update, so I uninstalled and worked again, however, that option wasn't available with the ROM Flash.
I couldn't find a single fix that would work to get the market to work, even ADB pushing older market apk's to the system wouldn't fix it. I decided to do a flash of JT's Super Clean ROM V.2, that didn't fix the issue either.
**I was clearing data and wiping dalvik after each flash**
With nothing seeming to work, I decided to try Deodexe's Zinc ROM, and this is where **** hit the fan. After doing this, I sent my phone into FC boot loop hell. I was getting the process.acore FC everytime I pressed a key. I rebooted back into Clockwork, tried to recover from an old ROM I had backed up the previous day, notta. Damage was done. I was getting FC bootloop hell with a very crappy performance.
I decided it was time to Odin restore and start over. These aren't the exact steps I took, but if I had to do it over again, this is how I would do it. If at any point you're getting a process.media FC, remove your SD Card, and leave it out until you need it for CWM.
STEP ONE:
If you installed Voodoo (at any point, removed or not, do this step)
Thanks to adrynalyne
http://forum.xda-developers.com/showthread.php?t=804784
This was the main culprit behind my phone not working correctly after a complete restore. I moved this to the top of the list, because after that, it's downhill.
STEP TWO:
Completely Restore with Odin Restore Files
Thanks to fallingup
http://forum.xda-developers.com/showthread.php?t=782204
The instructions are a little un-clear, but do this. First, Only use the PDA option, and flash each backup one at a time along with the PIT file. You're not out of the clear yet. Read on.
STEP THREE:
Flash CWM Recovery (read my notes below)
Thanks to fallingup
http://forum.xda-developers.com/showthread.php?t=788099
After you've flashed CWM. Boot into CWM Recovery, Boot back in Stock Recovery and wipe data and cache. Boot back to CWM (select sd:update.zip) and do the exact same thing there. Reboot phone.
STEP FOUR:
Do a data factory reset
Even though you have just restored the **** out of your phone, you're still not there. Get through all the account setup fields and go to Settings > Privacy > Factory Data Reset.
After a reboot, you should be on your way to a completely 100% stock fixed phone. At this point, I would suggest making a ROM back up of this point before moving ahead with flashing again.
LAST STEP (for me anyway):
Restore apps via Titanium Backup
This restored most my apps and settings that I had already saved, including LauncherPro and the backups I had for that. If you haven't used Ti, then use whatever app backup app you do have, if you do indeed have one.
I decided to re-flash JT's Super Clean ROM V.4 found here. Thanks to JT
http://forum.xda-developers.com/showthread.php?t=796171
I am also running the Remix Incognito Theme here: Thanks to frostman89
http://forum.xda-developers.com/showthread.php?t=801867
Right now I'm mixed on updating a new Voodoo Kernel, I haven't decided if I want to do that again or wait for something else.
Thanks again for all the DEV support, hopefully someone searching will find this thread useful.
Pretty much my standard routine when trying new kernels.
I have a nandroid with my basic rooted setup (apps and data intact), so this doesn't set me back by a huge amount.
Just a few differences...
I use:
Odin (System, then kernel) (step only needed if things are *really* messed up...won't boot)
Boot into Recovery
flash update.zip to get into CWM
Wipe Data/Cache/Davlik
Reboot into recovery
run jt's voodoo_uninstall (flashes stock.zip and replaces mbr with stock mbr)
reboot into recovery
restore nandroid image.
This has yet to fail me and usually takes under 10 minutes. The nandroid image is key. Most of the time, I can skip the Odin step completely if I am not seeing anything truly, staggeringly horrific going on.
Again, jt's voodoo-uninstall seems to solve a lot more than just voodoo issues. This thing should get it's own topic/forum/entry in ROM Manager/zip code/nobel award...you get the picture.
PhoenixPath said:
Again, jt's voodoo-uninstall seems to solve a lot more than just voodoo issues. This thing should get it's own topic/forum/entry in ROM Manager/zip code/nobel award...you get the picture.
Click to expand...
Click to collapse
+1 I agree
Nice write up! I'm sure this will help many people.
Thanks
This along with several other threads allowed me to recover from my own mental retardation.
Gotta remember to remove voodoo before doing stuff. I should know better.
Thanks again.
This is not working for me. I removed voodoo (using the uninstaller). I then did odin and my phone boots but I cant do anything past the unlock bc of all the fcs I get. I wiped the cache and data. CWM is not working, when I try to do the update.zip I get a "failed to verify whole-file signiture". - I deleted the voodoo folder from the sd-card after uninstalling voodoo, dont know if that contributed to the problem. Any ideas?
Ke1evraTi said:
This is not working for me. I removed voodoo (using the uninstaller). I then did odin and my phone boots but I cant do anything past the unlock bc of all the fcs I get. I wiped the cache and data. CWM is not working, when I try to do the update.zip I get a "failed to verify whole-file signiture". - I deleted the voodoo folder from the sd-card after uninstalling voodoo, dont know if that contributed to the problem. Any ideas?
Click to expand...
Click to collapse
Sounds like you need to re-flash ClockworkMod through Odin. I'm guessing it got wiped out when you went back to stock.
hey guys, been here since the launch of evo. rooting, flashing, everything.
today i wanted to switch roms. so i went about my normal process...
d/l new ROM
backup current ROM
backup apps
wipe cache and dalvic
flash new ROM
i got stuck on the last step. i went to flash the new ROM (nocturnal 1.3)
it said something along the lines of blah blah is already unmounted. i didnt pay too much attention to it because i was going to restart and try again. long story short, it will only boot to htc white screen and nothing else.
can anyone help me out?
p.s. im on clockwork recovery
PLEASE CLOSE
did you not wipe system and data? I am not super skilled, but maybe it tried to stick the entire ROM into the left over space of the last ROM that is still on there?
It won't boot to recovery? It should boot to recovery
weezymagic said:
hey guys, been here since the launch of evo. rooting, flashing, everything.
today i wanted to switch roms. so i went about my normal process...
d/l new ROM
backup current ROM
backup apps
wipe cache and dalvic
flash new ROM
i got stuck on the last step. i went to flash the new ROM (nocturnal 1.3)
it said something along the lines of blah blah is already unmounted. i didnt pay too much attention to it because i was going to restart and try again. long story short, it will only boot to htc white screen and nothing else.
can anyone help me out?
p.s. im on clockwork recovery
Click to expand...
Click to collapse
The error message you received is going to be the key to understanding the issue that occured. When it says unmounted, it is referring to a specific partition, either /data or /system most likely.
For starters, when it hangs on the htc white screen, this is usually either a kernel or ramdisk issue. If the kernel is known to be good, then it is probably a ramdisk issue. most ramdisk issues relate to a mismatch/incompatibility between the loaded kernel and the ROM.
First suggestion would be to reflash the ROM, clearing /cache and /data.
Second suggestion would be to restore a backup. This will confirm there is nothing wrong with your device hardware wise and you'll know it is a specific issue with the ROM you wanted to load.
Third suggestion, find the exact error, word for word, which occured in recovery and post up in the ROM thread asking if other users of that ROM also encountered, how they handled. Also feel free to post back up here.
When writing the programming behind a custom recovery, the error messages are added in there to help allow users and developers better knowledge of the exact issue so they can work to resolve them. Without the exact error message, it is similar to going to a car shop and saying, some light came on my dash, but I don't know what it was and now the car doesn't work. Fix it? Another words, it is very vague.
Hope the suggestions and tips help! Good luck!
my first instinct was to reflash the backup or new rom again but it wont boot to any rom, recovery or bootloader. it just hangs on the htc white screen
idk what happened but i got into the bootloader through battery pull, power+vol down. i know ive tried that in the past but this time it worked. now im restoring a nandroid from yesterday
weezymagic said:
idk what happened but i got into the bootloader through battery pull, power+vol down. i know ive tried that in the past but this time it worked. now im restoring a nandroid from yesterday
Click to expand...
Click to collapse
are you on twrp 1.0.x ? There is s charging issue where it won't restart right because it thinks It's already in recovery
sent from my EVO 3D via XDA app
weezymagic said:
hey guys, been here since the launch of evo. rooting, flashing, everything.
today i wanted to switch roms. so i went about my normal process...
d/l new ROM
backup current ROM
backup apps
wipe cache and dalvic
flash new ROM
i got stuck on the last step. i went to flash the new ROM (nocturnal 1.3)
it said something along the lines of blah blah is already unmounted. i didnt pay too much attention to it because i was going to restart and try again. long story short, it will only boot to htc white screen and nothing else.
can anyone help me out?
p.s. im on clockwork recovery
PLEASE CLOSE
Click to expand...
Click to collapse
You missed a step. After you wipe dalvik and cache, you ALWAYS need to wipe /system and /data, do a factory reset to make sure, or download a superwipe tool. The ONLY time you don't need to wipe completely is when you're updating your ROM, but even then it is recommended to wipe everything.
Twolazyg said:
You missed a step. After you wipe dalvik and cache, you ALWAYS need to wipe /system and /data, do a factory reset to make sure, or download a superwipe tool. The ONLY time you don't need to wipe completely is when you're updating your ROM, but even then it is recommended to wipe everything.
Click to expand...
Click to collapse
Agreed^^^^^
Hello all! Long-time prowler, 1st time poster.
Finally got my hands on a GS2. Very pleased with it. I've always been interested in custom roms and kernels, as I've spent dozens of hours researching how-to's and don't-do's, but I've been hesitant to take the plunge due to the risk and 1st-time unfamiliarity.
That is, until now. I was following the rooting instructions here: http://forum.xda-developers.com/showthread.php?t=1311081
Specifically, point 2c using Entropy's root method (phone had the OTA UCKK6 update) to revert back to UCKH7 2.3.4. Everything went as expected, root was achieved (2.3.4, kernel 2.6.35.7, superuser, etc.), but wifi is DOA. It appears that everything else is working fine, but when I attempt to turn on wifi, it starts scanning for a few seconds and then shuts itself off.
I've searched both XDA and Google on the topic, and while it seems to be a common occurrence, there is very little information in the way of solutions. The closest I've come to has been this thread: http://forum.xda-developers.com/showthread.php?t=1364039&highlight=wifi+broke
Appears that a full un-root is necessary? I just wanted to double-check that there isn't some silly little thing I'm missing or a more streamlined solution.
Again, noob here. Any advice or input is greatly appreciated. Looking forward to trying out some roms and kernels and learning more from the community!
I've got the same problem ... kinda...I followed the same steps to root, WiFi was fine after that, but when I flashed CWM-recovery, WiFi was borked. This is where I usually shhot myself in the foot ( as I appear to have done again). After more reading and research, I found that the ROM I was planning to flash (UnNamed) did its own kernel update so I figured that it may patch my WiFi problem.
Sadly it did not and now I have NO radio at all. (Cellular, data or WiFi). I get FC's from com.android.phone. (over and over... every 5-7 seconds.)
Hmmmmmm...
Flash stock again just to make sure it got everything
Sent from my páhhōniē
That had crossed my mind, so I went through the root flashing process again, Odin3 gave it a "PASS," but the problem remains.
OK... Should I wipe before flashing stock? Thats the one thing that I didn't do. I wasn't sure which wipe to do so I didn't. (oops???)
Do a wipe data/factory reset now and you should have wi-fi again. I had the same problem and it worked after I did the wipe data/factory reset.
ehhhhh.... somethings up here. I did a wipe/factory reset, then flashed back to my virgin ROM with CWM-recovery on board. My cellular/ data is back but WiFi is still borked.
---------- Post added at 07:46 PM ---------- Previous post was at 07:45 PM ----------
wreckit72 said:
Do a wipe data/factory reset now and you should have wi-fi again. I had the same problem and it worked after I did the wipe data/factory reset.
Click to expand...
Click to collapse
Or did you mean that I should have did the wipe on the UnNamed ROM?
Trying to do a CWM backup through the Rom Manager App so I can do a data wipe/reset (through the factory-reset option, or through CWM, just to clarify?), but every time I try to make a backup CWM gives me this:
E: Failed to verify whole-file signature.
Any idea what would cause this?
McMash said:
Trying to do a CWM backup through the Rom Manager App so I can do a data wipe/reset (through the factory-reset option, or through CWM, just to clarify?), but every time I try to make a backup CWM gives me this:
E: Failed to verify whole-file signature.
Any idea what would cause this?
Click to expand...
Click to collapse
It is posted prominently in several places in the I777 forums, do not use ROM Manager app.
Starting with UCKK6, then flashing UCKH7 plus root package is known to bork wifi. A wipe data/factory reset will clear it if you wish to stay on UCKH7. Doing OTA update to UCKK6 without a wipe also reportedly clears the wifi problem, and will retain root.
To use ClockworkMod Recovery, you must first install a CWM enabled kernel.
ya...
McMash said:
Trying to do a CWM backup through the Rom Manager App so I can do a data wipe/reset (through the factory-reset option, or through CWM, just to clarify?), but every time I try to make a backup CWM gives me this:
E: Failed to verify whole-file signature.
Any idea what would cause this?
Click to expand...
Click to collapse
Yuppers... ROM manager is incompatable with the SGSII. I just learned that yesterday. Its a P.I.T.A.
You gotta delete it then flash the CWM-R kernel to get the nandroid backup. Yes you are now backing up a modded kernel but otherwise you are pulling a raw (and virgin) FS image.
@SeniorGato
I can't interpret from your post. If you restored a previous backup from ClockworkMod Recovery, then you probably reintroduced the wifi problem.
Anyway, you want to be on UnNamed. You should do a wipe data/factory reset before you flash UnNamed. Then for good measure, it couldn't hurt to do another one after.
creepyncrawly said:
@SeniorGato
I can't interpret from your post. If you restored a previous backup from ClockworkMod Recovery, then you probably reintroduced the wifi problem.
Anyway, you want to be on UnNamed. You should do a wipe data/factory reset before you flash UnNamed. Then for good measure, it couldn't hurt to do another one after.
Click to expand...
Click to collapse
I did in fact go back to CWM.
From the recovery screen of UnNamed, I kernel flashed back to CWM, then did the factory wipe, then flashed the backup I made. The WiFi did work when I was on that ROM prior to flashing UnNamed. Now... not so much.
Anyway... Off to look for that stock kernel, then start over.
So do a wipe before each flash then?
Just finished re-installing the OTA update back to UCKK6. Root is still good and the wifi seems to be working. Thank you Creepy and Gato for being so helpful and gracious. There's a huge amount of information on here that I'm trying to sift through and thus a bit of a learning curve, but thanks for helping me through the first hurdles!
Yes, you must wipe before changing from one rom to another, ie stock UCKK6 to UCKH7, or UCKH7 to UnNamed, etc.
You can usually get by without a wipe when flashing the same ROM, ie UnNamed 2.0.0 to 2.0.1
Hmmmm...
So I've wiped, flashed UnNamed then re-wiped. Now I have no modem at all (again).
Looking in the about phone I see some interesting things...
model number: SPH-D710
Baseband: unknown
Kernel version:
2.6.35.7-sph-d710.el13-cl806482
build number: UnNamed v2.0.1
hardware version : unknown
And strange behavior (aside from the no modem thing): when the screen turns off, I have to restart the phone all over again.
I downloaded the ROM through the developement forum under the I-777 so I THINK its the right one, but this descrepancy in the model number has me concerned. Is it normal for custom ROMs to display incorrect data like this or have I completely hosed this?
This is totally *not* normal.
SPH-D710 is Epic 4G Touch.
The kernel belongs to the epic.
It looks like the phone won't even recognise the sprint modem.
I'm surprised your phone will even boot.
Your phone is the AT&T Samsung Galaxy S II I777, right?
If so, you need to re-download the UnNamed install file. The latest version number is 2.2.1 (not 2.0.1) from here. The file you want is update-unnamed-v2.2.1-full.zip.
I don't have enough experience to tell you how to proceed, but here is what I think will work.
If the kernel currently on your phone has ClockworkMod Recovery, and if you can boot into recovery, you might try flashing UnNamed from there. Do a wipe first.
Or, flash back to stock plus root, install a CWM kernel, and then flash UnNamed.
Edit: Yes, gtg released an UnNamed for Epic 4G Touch, which is currently on version 2.0.1. Somehow, you have downloaded and flashed the wrong package, but knowing gtg, it almost certainly does not contain bootloaders or param.lfs, so you should be able to recover. The kernel contains CWM recovery based on 5.0.2.7, the same version we have in Entropy's DD kernel, so you might try flashing the correct UnNamed directly from that recovery. Since you could go SGS II --> Epic 4G, you should be able to go back the other way. If that doesn't work, then flash the stock plus root using Odin or the Odin One-click package.
Well that does explain...
Weird part is that I DID use the I-777 forum's download. Anyway, I'm redownloading now.
*fingers Crossed*
So this begs the question, how are the sprint galaxy s2 roms looking, and how hard would it be to build a 'hellraising' package for them? If a straight flash managed to boot, kernel and all, might open even more possibilities for us.
Sent from my páhhōniē
Siyah Kernel 2.6.6 Troubleshooting
Hello again!
I thought I'd give flashing a kernel a go. I've been following Creepy's guide to installing a kernel via Mobile Odin (bought the pro version; easier and helps out the devs!). Got it installed on the phone and put the zImage for Siyah in the internal SD-card root and flashed from there.
It rebooted and showed that CWM had successfully installed, but the kernel is still the 2.6.35.14 as it was before. Not only that, but wifi is also non-functional again. Tried to flash it again; same result. Cleared the cache/dalvik and also ran the kernel cleaning script, then gave it another go. Still no Siyah kernel, still no wifi.
Great start to my XDA career, I know. Any help would be awesome!
If you're sure you have root and can boot to CWMrecovery, you may try mounting the phones internal USB memory (not the removeable SD card) on your computer, move the entire zip into it and flash thru CWM recovery. Once I had the right ROM *sheepish grin* it worked immediately and perfectly. My wifi is back and everything!
A thousand thanks for all the help!
Edit: I just reread your post. First check what recovery you are booting to. 3e or CWM?
Sent from my SAMSUNG-SGH-I777 using XDA App
In short, I have a US Galaxy 4.0 Player, and have been enjoying it immensely, I've messed around with a few roms and kernels, and thought I'd try out the newest version of Han's Ethereal rom, version 2.1, with the TerraSilent 1.3.5 kernel. I heard it would take a long time to boot the first time, between 10 and 15 minutes, and that it would appear like it's bootlooping when it actually is not. Unfortunately, it ha been doing this for close to an hour now, making me think there actually is a problem. Has anyone ever experienced this huge amount of boot up time before?
(Also, I changed the filesystem to EXT4, as per Han's instructions, but I heard going back into CWM under the TerraSilent 1.3.5 messes with that, would it have anything to do with it?)
The filesystem mix up could definitely be the issue. You're best just flashing and booting. If possible, just stick to RFS. I think EXT4 just makes things too messy.
Your not alone on this one. I didn't change the file system, installed the same rom w/ the same kernel, and it's still looping
Nnn Noob said:
Your not alone on this one. I didn't change the file system, installed the same rom w/ the same kernel, and it's still looping
Click to expand...
Click to collapse
I have put a new version (2.2) that should fix the bootlooping issues (or at least help them). How many apps to each of you have? Sometimes you have to pull the battery to get it to finish booting up properly. The EXT4 filesystem should have nothing to do with it bootlooping on the bootlogo, if that was an issue, it should be looping on the bootloader (the splash screen you see before it starts booting).
Interesting, because once I went back to stock with the RFS filesystem and reflashed the same rom, it went just fine, booted in just over a minute. When I was trying to boot before, I had perhaps a couple dozen apps, so I thought that was unlikely to be the cause. But yeah, did the whole deal with the battery pull/reboot a couple times and still no luck. But once I went back to stock before I flashed it was no problem. I'm going to be flashing 2.2 soon, when I didn't mess with the filesystem, if everything goes smoothly, then I think that might be our culprit.
silentdoh said:
Interesting, because once I went back to stock with the RFS filesystem and reflashed the same rom, it went just fine, booted in just over a minute. When I was trying to boot before, I had perhaps a couple dozen apps, so I thought that was unlikely to be the cause. But yeah, did the whole deal with the battery pull/reboot a couple times and still no luck. But once I went back to stock before I flashed it was no problem. I'm going to be flashing 2.2 soon, when I didn't mess with the filesystem, if everything goes smoothly, then I think that might be our culprit.
Click to expand...
Click to collapse
I have found out that if you wipe cache/dalvik, sometimes it will get stuck in a bootloop. If you head into recovery after that happens, and wipe cache/dalvik from there (again if need be), then hit fix permissions (might be necessary), it should boot just fine. I would also hold off until 1.3, as I am releasing it today, and it is finally stable.
Am I bootlooping?
hanthesolo said:
I have found out that if you wipe cache/dalvik, sometimes it will get stuck in a bootloop. If you head into recovery after that happens, and wipe cache/dalvik from there (again if need be), then hit fix permissions (might be necessary), it should boot just fine. I would also hold off until 1.3, as I am releasing it today, and it is finally stable.
Click to expand...
Click to collapse
I downloaded the latest (v2.4) Ethereal ROM and flashed it, and I think I may have gotten myself into a boot loop. Either that or I'm just impatient.
I'm currently running Klin's Klassic R5, rooted. Never messed with the file system.
Here's what I did:
1) Reboot to Recovery. Wipe cache and Dalvik.
2) Reboot to Download, flash the tar file with Odin. (Did not check PIT). All threads completed.
3) Device rebooted, I get Samsung logo (with Steve's Kernel icon at the bottom), then it displays "ANDROID" and the screen sleeps, and occasionally comes back on for a few seconds. This continues for close to an hour.
4) I found this thread. Pulled battery, wiped cache and Dalvik again, fixed permissions, rebooted.
5) Same results as #3.
I did make a nandroid backup before starting this. Should I restore it and re-flash?
Thanks,
Scott
Fixed?
thirdeye73 said:
I downloaded the latest (v2.4) Ethereal ROM and flashed it, and I think I may have gotten myself into a boot loop. Either that or I'm just impatient.
I'm currently running Klin's Klassic R5, rooted. Never messed with the file system.
Here's what I did:
1) Reboot to Recovery. Wipe cache and Dalvik.
2) Reboot to Download, flash the tar file with Odin. (Did not check PIT). All threads completed.
3) Device rebooted, I get Samsung logo (with Steve's Kernel icon at the bottom), then it displays "ANDROID" and the screen sleeps, and occasionally comes back on for a few seconds. This continues for close to an hour.
4) I found this thread. Pulled battery, wiped cache and Dalvik again, fixed permissions, rebooted.
5) Same results as #3.
I did make a nandroid backup before starting this. Should I restore it and re-flash?
Thanks,
Scott
Click to expand...
Click to collapse
I am back up and running. Flashed TerraSilent kernel and got my device back up. I tried restoring from my nandroid backup and that made my bootloop worse--left me in a samsung logo bootloop. I'd love to know why the nandroid restore didn't work, if anyone has any ideas what I might've done wrong.
Tried flashing Ethereal again, no problems this time. Only weird thing is Holo Launcher kept force closing, had to uninstall it.
I recently had an issue with my Note 2 when I went to flash (yet another) ROM. I tried to run the "Wipe Data/Factory reset" from within CWMR (Touch), and it would lock up/freeze during the format /data portion of the wipe. It would eventually just reboot itself back into recovery mode.
I eventually got to a point where I tried flashing a TW4.3 (rooted) stock ROM, but it was flaking out because obviously the data partition never did get properly wiped (lots of FC's, etc after it finished booting). I tried to do a factory wipe from WITHIN the booted OS. This took me a the android with the spinning blue "heart" and pseudo-progress bar. It then just stayed on this screen for 3-5 minutes and then rebooted back to the screen over and over.
I eventually gave up and ODIN'ed it back to the a stock, unrooted state (but I chose NOT to go to the latest 4.3 release so I could still possibly unlock again).
For some reason, the stock recovery doesn't have any issues formatting the /data partition now. I actually went back to stock thinking I might have to file a warranty claim on the phone (and I could right now, since it appears to be fully stock in all the various places you might look for tampering).
I am still concerned, however, that there is a corruption present in the /data partition and I would like to know if there is a way to test for it. Do I need to re-root just to test it?
spiff72 said:
I recently had an issue with my Note 2 when I went to flash (yet another) ROM. I tried to run the "Wipe Data/Factory reset" from within CWMR (Touch), and it would lock up/freeze during the format /data portion of the wipe. It would eventually just reboot itself back into recovery mode.
I eventually got to a point where I tried flashing a TW4.3 (rooted) stock ROM, but it was flaking out because obviously the data partition never did get properly wiped (lots of FC's, etc after it finished booting). I tried to do a factory wipe from WITHIN the booted OS. This took me a the android with the spinning blue "heart" and pseudo-progress bar. It then just stayed on this screen for 3-5 minutes and then rebooted back to the screen over and over.
I eventually gave up and ODIN'ed it back to the a stock, unrooted state (but I chose NOT to go to the latest 4.3 release so I could still possibly unlock again).
For some reason, the stock recovery doesn't have any issues formatting the /data partition now. I actually went back to stock thinking I might have to file a warranty claim on the phone (and I could right now, since it appears to be fully stock in all the various places you might look for tampering).
I am still concerned, however, that there is a corruption present in the /data partition and I would like to know if there is a way to test for it. Do I need to re-root just to test it?
Click to expand...
Click to collapse
I had this issue as well at one point, my phone actually soft bricked. What you need to do is use the pit file thru odin, flash any firmware in odin EXCEPT THE NEW OTA. Then you need to unlock again using the proper version of CASUAL for the base in which you relocked.
Sent from my Galaxy Note II
icedventimocha said:
I had this issue as well at one point, my phone actually soft bricked. What you need to do is use the pit file thru odin, flash any firmware in odin EXCEPT THE NEW OTA. Then you need to unlock again using the proper version of CASUAL for the base in which you relocked.
Sent from my Galaxy Note II
Click to expand...
Click to collapse
Thanks...
I actually went through the whole revert to stock with ODIN (but I used the PDA button/file). Was this the wrong approach? It sounds like I ended up at the same point as you...
And of course I couldn't leave it alone last night and unlocked and rooted with Casual last night. So far no issues with recovery data wipes.
I would like to understand what the problem was! Is it hardware, or a flash gone wrong?