Related
DO NOT UNDER AND CIRCUMSTANCE USE THESE RECOVERIES
CWM TOUCH
There is something wrong with the original CWM touch and the way it handles partitions.
THESE WILL CORRUPT YOUR /DATA & /EMMC PARTITIONS AND YOUR PHONE WILL NEVER BOOT AGAIN
There are tons of posts about this problem
http://forum.xda-developers.com/showthread.php?t=1504808
http://forum.xda-developers.com/showthread.php?p=22794885
+ any thread with brick in the title -
Read these threads all you want, the common problem is touch recovery screwing up /data and /emmc. NOT EVEN A TAR W/ PIT IN ODIN WILL WORK
BEWARE.
Once you get it all screwed up and try to fix it with odin, you'll get stuck here. (image below) I have tried odin 1.82/1.83/1.85 & Heimdall with the .pit and re-partition option enabled, Still doesn't work.
Really?!?!?! have used touch recovery like 20 times and had no problems except for 1 soft brick
Sent from my SPH-D710 using XDA App
*GalaxyDev* said:
Really?!?!?! have used touch recovery like 20 times and had no problems except for 1 soft brick
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Seems to be happening when you do a factory wipe from inside the touch recoveries.
Sent from my SPH-D710 using XDA App
I'll keep this in mind I actually have to think if I've done a factory wipe with the touch recovery yet not sure I have. But outside of that I've not had any problems with the touch recovery.
No offense, but I feel that people who use touch recovery are not acting as smart as they really are.... You can accidentally wipe your phone completely without an issue....
I'm sure if there was really an issue the downloads would have been pulled by the devs.
I don't think the issue is in the recovery but rather User Error. I used Touch Recovery about 100 times to test my theme before Rogue Recovery came out for FB15. I no longer use it but I never wiped with it, I knew it was temporary and those who treated it as an all out Recovery are those who probably got bricked. I don't like it when people brick phones and I do feel bad for those who are bricked.
URGENT The beer is bad! Nobody drink the beer!
I hafta agree with ssconcepts.
Sent from my SPH-D710 using XDA App
If i save 1 phone its worth it.
With folks trying out ICS, many will want to return to GB, and may try and wipe with Touch Recovery. This will corrupt the /data and /emmc partitions.
Can't fix my phone no matter what I attempt.
I'm just saying with all the other recoveries there was no real wrong move.
Hit a wrong button in touch and its over.
Don't wipe/format anything with a touch recovery to be safe. I just want to help others I'm not trying to scare people away.
BTW - Check Out
http://forum.xda-developers.com/showthread.php?t=1504808
Look at how many views there are.
We should start a check-in.
I have the Rogue Hitman kernel & recovery on my now-obsolete GB nandroid and I never had problems with it...Then again I never factory wiped. I always used Calkulin's wipeall .zip thing.
This is from someone else but it is very close to what i did:
I just couldn't help myself and I flashed shabbys ICS test build this morning. Well the more I started reading in the thread about guys having issues restoring there backups I tried it. Flashed the cwm touch recovery....did a full wipe and then went to restore my nand of Blend. Booted up and gets stuck at the Samsung boot screen. I let it sit there for about 10 minutes. Then from there I pressed volume up and power to see if i could get back into cwm. I was able to and had rogue recovery. I then went to do a full wipe again. The data wipe took about 2 minutes....which was strange...then wiped cache and dalvik. Then went to flash Blend(not the nand backup) and again stuck at the samsung boot screen.
So I then went into odin mode and attempted to odin back to stock using the D710USEL29_20120105.stock from qb777's you tube vid. All went good....got the pass and once again stuck at the Samsung boot screen. Then from there I went back into odin download mode and attempted to odin the stock rooted file(not the file to keep your data file) and it got stuck at "Data.img" in odin.
Good lookin out posting this here glass. I'm not confident enough to put it ALL on touch recovery. I've used touch before plenty of times with zero issues, with this phone and the HTC Thunderbolt.
BUT one person I trust as I believe we all do is sfhub. If you read thru the "stuck at data.img" thread it sounds as if he is leaning toward the touch recovery being the issue. I'm not speaking for him tho.
As for the person earlier stating user error....I did exactly what was stated to do in an ICS op. The only thing I used the touch recovery for was wiping and restoring a backup and all went to sh#t from there.
Obviously ya'll do what you want, I just got my replacement phone today and I'm staying the hell away from touch recovery. I think now the risks far out way the advantage of just touching your screen instead of using volume buttons. Maybe just take a few minutes to read thru these "bricked threads" and decide for yourself.
I wonder if there's a way to safely run an Android virtual machine on a PC and try to recreate this without sacrificing a phone.
I didn't think we were supposed to wipe when recovering a Nand. Perhaps I'm wrong but might this be the problem?
Sent from my SPH-D710 using XDA App
I don't think it was necessarily the touch recovery that bricked my phone. I think it was the way the touch recovery is handled because it's temporary and the way ICS is handled.
I used the permanent touch recovery on EL29 and only soft bricked once. Other than that it worked fine.
The permabrick happened after I had been using FB17 flawlessly for just under 24 hours. I wanted to check out the ICS 4 ICS theme. So I loaded up the temp touch recovery and flash the deodex fb17 rom. Worked fine. Reflashed temp touch again. Flashed theme. Worked fine. Noticed rom was laggy.
This is where things went south. I flashed the temp recovery. Because I wanted a clean install I figured I'd do a factory reset and wipe everything a couple times. It froze in the middle of the factory reset while wiping data. I think it was at this point that the partition got borked.
I think if I had odin'd everything instead of using the temp touch recovery I would have been fine. This is of course my own fault. There were bricks prior to mine and I didn't do my homework.
However, I do agree with a warning for everyone that this has been happening.
Sent from my SPH-D710 using Tapatalk
may i ask why is this in the Q&A? Its not a question.. and its not the answer to everyone problem since 50% is saying it is the recovery and then 50% say its just the user.... but half of the people who use it and restored from ICS got this error..so someone with a bad ESN phone need to test both methods and see whats up
dgn_sandibalz said:
I don't think it was necessarily the touch recovery that bricked my phone. I think it was the way the touch recovery is handled because it's temporary and the way ICS is handled.
I used the permanent touch recovery on EL29 and only soft bricked once. Other than that it worked fine.
The permabrick happened after I had been using FB17 flawlessly for just under 24 hours. I wanted to check out the ICS 4 ICS theme. So I loaded up the temp touch recovery and flash the deodex fb17 rom. Worked fine. Reflashed temp touch again. Flashed theme. Worked fine. Noticed rom was laggy.
This is where things went south. I flashed the temp recovery. Because I wanted a clean install I figured I'd do a factory reset and wipe everything a couple times. It froze in the middle of the factory reset while wiping data. I think it was at this point that the partition got borked.
I think if I had odin'd everything instead of using the temp touch recovery I would have been fine. This is of course my own fault. There were bricks prior to mine and I didn't do my homework.
However, I do agree with a warning for everyone that this has been happening.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
That sucks. Maybe the OP should edit the title of his post to"don't fake flash and/or wipe with temp cwm touch" and leave hitman out of this.
Sent from my SPH-D710 using XDA App
Sfhub just posted what he thinks is happening in the stuck at data.img thread. Makes sense.......even to a dumba#s like myself.
Its not tje actual touch recovery. Its when u use it as a temp flash recovery. I did the same thing by wiping data. I tried for three hours flashing everything created for this phone and nothing. Data and emmc gone!!!
Sent from my Nexus S 4G using xda premium
So I have discovered a hardware issue with my device. It's been rooted and flashed with a custom rom. Before I take it to ATT for warranty I want to restore it to full stock. Are there any good guides out there for this?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Stock images are here...flash through Odin.
http://forum.xda-developers.com/showthread.php?t=1968625
Sent from my SGH-I747 using xda premium
Don't forget to factory reset to avoid a possible bootloop
Before doing any of that, check the Triangle Away app to reset your flash counter. Not sure if you tripped it? It will tell you that too. If i were doing it, i would:
Back everything up and sync everything with google
Pull everything i wanted to keep off the internal card
Check/run triangle away
Odin to stock LG1
Perform factory reset, from settings menu (this will wipe and reformat your internal card)
Let ota update you to LH9
You are now 100% stock, no tripped flash counter, and ready for warranty return.
HI all
so i rooted my phone and been using custom rom, but didn't like the instability of them. so now I am trying to go back to stock firmware but with root access.
so i went to samsung official website and downloaded the firmware
http://www.sammobile.com/firmwares/1/?model=SGH-I747M&pcode=0#firmware
then I use odin and flash that .tar file on my phone. every thing went smoothly, the flahsing was complete.
but after my phone was rebooted. it stopped at the boosting animation ( the one with big word "samsung" and purple like going at behind)
what is happening? any help would be appreciated thank you
Boot into Samsung stock recovery
Wipe cache data etc and you should be good to go!
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Did you wrote cache and dalvik?
Sent from my SGH-I747 using Tapatalk 4 Beta
I have a galaxy s3 t999 rooted with team win recovery v2.6.0.0
No matter what rom i use, wether it be debloated stock or custom rom, after a couple hours my phone goes into a boot loop and the only thing that brings it back is a restore to when i rooted and installed the recovery.
Baseband- t999UVDMD5
Ive tried
universeS4 v3
Stockoroma
z999 UVDMD5 (Modified) Stock TouchWiz
[STOCK] T999UVDMD5 | 4.1.2 | Deodexed
all of them after 2-3 hours bootloop.
Can anyone help me with this? ive looked everywhere to see if anyone is having the same issue as me but no luck....
Have you factory reset after flashing and tried letting it run clean without installing any apps?
If all else fails, Odin flash back to stock and try again. Odin flash the root66 firmware to have the phone rooted.
Sent from my SGH-T999L using XDA Premium 4 mobile app
DocHoliday77 said:
Have you factory reset after flashing and tried letting it run clean without installing any apps?
If all else fails, Odin flash back to stock and try again. Odin flash the root66 firmware to have the phone rooted.
Sent from my SGH-T999L using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I factory reset before i flash. Am i suppose to factory reset after flash as well? sorry if thats a noob question. ive been flashin roms for a few years now and never had this problem.
If you're going to factory reset, I generally suggest doing so after the flash. Its not unheard of for someone to factory reset, then reboot normally, then go and flash the rom. By rebooting they rebuild the data which was wiped to begin with. Then when they flash the rom wonder why it won't boot till factory resetting again.
If you don't reboot, it shouldn't really matter if you do so before or after flashing.
I also usually do so before, but suggest the other way for that reason.
Sent from my SGH-T999L using XDA Premium 4 mobile app
DocHoliday77 said:
If you're going to factory reset, I generally suggest doing so after the flash. Its not unheard of for someone to factory reset, then reboot normally, then go and flash the rom. By rebooting they rebuild the data which was wiped to begin with. Then when they flash the rom wonder why it won't boot till factory resetting again.
If you don't reboot, it shouldn't really matter if you do so before or after flashing.
I also usually do so before, but suggest the other way for that reason.
Sent from my SGH-T999L using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I figured as much. I just reflashed the firmware only, factory reset, wiped cache and del, flashed universeS4, factory reset again, let phone boot fully, restarted phone and am gonna see where the phones at in the am when i wake up. If it still does it ill return to stock/odin with root66 and see if that will fix. if not im stuck on stock which sucks.
if anyone else has any suggestions let me know.
Thanks doc
UPDATE*
so i flashed back to stock with odin. then flashed root66. wiped cache and del, factory reset, wiped cache and del again, flashed universeS4 factory reset.
Its been 7 hours so far and no bootloop. Putting my simcard in it now and hoping for the best. Thank you again.
Cool man! :fingers-crossed:
Sent from my SGH-T999L using XDA Premium 4 mobile app
DocHoliday77 said:
Cool man! :fingers-crossed:
Sent from my SGH-T999L using XDA Premium 4 mobile app
Click to expand...
Click to collapse
*2nd UPDATE*
Wake up this morning to the phone boot looping. This sucks. Does anyone have any idea what i can do to fix this?
Noooooooooo!!!!!
That definitely sucks man. My best advice is to odin flash official stock firmware (root66 ok) and try the same thing. If it continues then I would check if its still under warranty as its probably hardware related. Aside from that I'm not really sure what else to suggest...
Sent from my SGH-T999L using XDA Premium 4 mobile app
Alright, im not completely new to rooting but I have encountered a new problem.
I rooted my phone through odin (galaxy s3 T999), had some hiccups with that so I ended up downloading the stock rom tar and reflashed using that, problem solved good to go still rooted. awesome.
So, I attempted to flash the cyanogen rom using clockwork mod. it wouldn't come past the load screen, went into clockwork mod to recover my backup but for some reason it wouldn't let me access the SD card to get it. next thought was to go back to odin and flash the same file I used previously to get back to where I was, for some reason this is not working, I can get to download, use odin to flash it, says success and all that, then upoon rebooting it stays at the Samsung loading screen.
So from there I went and downloaded the GS3 toolkit and tried all of their recovery files, all having the same issue. about 18 flashes later I tried reformatting from the phone itself, same issue with the samsung logo being stuck. And now, I am currently baffled, anyone wanna help me out? I have a feeling it has something to do with the .pit option on odin, but I am not that advanced and its just a hunch. so...thanks in advance guys!
So I understand not to touch pit, roger, reading other posts makes that clear, but still cant find a fix, the top right of my download says
ODIN MODE
Product Name SGH-T999
Custom Binary yes: 19 counts
Current Binary Samsung Offical
System Status Custom
Qualcomm secureboot Enable
Okay, what is the current state of the device?
Whst do you see when you boot into recovery ( take battery out of phone the put it back in and do the following: hold volume up, home button and power button, let go of all buttons when you feel the phone vibrate and blue text flashes in the upper left corner of the screen)?
Sent from my SGH-T999 using XDA Premium 4 mobile app
I just tried to send a rom over that had CWM 6.0.2.3 and it installed that, but still stuck on logo. going into recovery I am in CWM 6.0.2.3
have the standard options wipe/factory, install from zip etc.
You flashed a rom that had cwm 6.0.2.3 or did you flash a rom while on 6.0.2.3?
Sent from my SGH-T999 using XDA Premium 4 mobile app
I'd say about 98% of the time, when it hangs like that you just need to factory reset.
Sent from my SGH-T999L using XDA Premium 4 mobile app
Flashed a rom that had 6.0.2.3. I do not have any roms on my ZIP, been doing everything through ODIN. Very confused as to why it suddenly stopped working.
DocHoliday77 said:
I'd say about 98% of the time, when it hangs like that you just need to factory reset.
Sent from my SGH-T999L using XDA Premium 4 mobile app
Click to expand...
Click to collapse
tried to factory reset and it does the same logo stuck business. That was the last thing i tried after attempting to back up and reflash numerous times. tried flashing again recently, it will install CWM if it is attached to the rom but still gets stuck on the logo. tried re installing odin as well, it is working as usual, starts, restarts the phone, sits awhile, success. then i restart the phone and never get past logo.
I would do what Doc said.
If it still doesnt work, download a rom of your choice (in the t-999 section) and do a full wipe before flashing the rom you picked.
Sent from my SGH-T999 using XDA Premium 4 mobile app
Da Kine said:
I would do what Doc said.
If it still doesnt work, download a rom of your choice (in the t-999 section) and do a full wipe before flashing the rom you picked.
Sent from my SGH-T999 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
what do you mean by full wipe, factory reset? or something else?
connorjiy said:
what do you mean by full wipe, factory reset? or something else?
Click to expand...
Click to collapse
When flashing a new rom, you have to do a full wipe or youll run into problems like you are currently having.
If you dont know what a full wipe is, then stop what you are doing and put your phone down. Just about every rom thread here on xda explains what a full wipe is, it will be in the first post of the thread.
Like I said, find a rom you like in the t-999 section and flash it after doing a full wipe.
Sent from my SGH-T999 using XDA Premium 4 mobile app
Da Kine said:
When flashing a new rom, you have to do a full wipe or youll run into problems like you are currently having.
If you dont know what a full wipe is, then stop what you are doing and put your phone down. Just about every rom thread here on xda explains what a full wipe is, it will be in the first post of the thread.
Like I said, find a rom you like in the t-999 section and flash it after doing a full wipe.
Sent from my SGH-T999 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Looked it up, that is what I do by default, didn't know thats what was considered a full wipe, just tried it with similar results, didn't know about the dalvik cache though. im on a work computer so I cannot currently DL a new rom from the site, I hope thats what the issue is, but I still cannot see why my other ones would suddenly not work.
connorjiy said:
tried to factory reset and it does the same logo stuck business. That was the last thing i tried after attempting to back up and reflash numerous times. tried flashing again recently, it will install CWM if it is attached to the rom but still gets stuck on the logo. tried re installing odin as well, it is working as usual, starts, restarts the phone, sits awhile, success. then i restart the phone and never get past logo.
Click to expand...
Click to collapse
I'm just not sure what you mean by it installing CWM attached to a Rom? Recoveries shouldn't be included with a Rom.
Odin flash the root66 firmware, then reboot to STOCK recovery and factory reset. This will wipe all user data, including your internal sd card. Then try rebooting again.
Sent from my SGH-T999L using XDA Premium 4 mobile app