Related
Hey guys. I've been an Android & XDA user for a while now, so this question shouldn't be about a nooby-sitiuation.
My friend bought an AT&T Samsung Galaxy SII (SGH-i777) this week. I've been trying to flash CM7 ever since. I got the rooting done, the properly recovery (with no signature / "abort" problems)
The rom seems to keep bricking the phone. Its simply unflashable. I seen tons of people on XDA who got it to work, with barely any serious problems. I troubleshooted the problem myself, and its simply just the CM7 roms. I would do a full wipe, and then install the rom like I would on my other Android phones, and the installation is successful. When it boots, it gets stuck on the Galaxy SII boot screen (not the splash/boot animation screen) and it would stay on it with a yellow warning triangle on the bottom.
I tried flashing other roms, like Cognition X2, and they worked. Its just CM7 on this phone... which is odd because CM7 is usually stable (nightlies aside.) Especially since the 7.1 stable version was recently released. Anyone can help me get the rom up and going? Would be highly appreciated.
did you try to wipe dalvick cashe as well when you wiped data?
I just flashed it tonight myself and all I did was reboot into CWM and did a Wipe data/factory reset and then Wipe cache partition. After doing that, I simply flashed the cm7 zip file that was loaded on my internal sd. Rebooted and no problems.
I didn't have ANH ISSUES installing it but I know I read that some.people bad to flash it twice initially. So flash it, then when it goes back to the recovery screen flash it a second time. I also remember users on the international SGS2 bad to do the same thing. Most have no issues but I think they found that it depends on what you used to root your phone (on the SGS2 internationals) and I THINK some had to do the same here. Try it and if it works just hit the thanks button.
Sent from My KickAss CM7 Galaxy S2
if you flash it and get stuck in a bootloop, just pull the battery, and 3-finger back into recovery to flash the rom again.
keep doing this until you get it up and running - took me a few times, including a couple of battery pulls.
How do you boot into recovery? I know On the SGH-i777 you have to hold the Vol down+back+power to get to the Download mode, but I tried everything to get to the recovery itself.
Boobie Watcher said:
did you try to wipe dalvick cashe as well when you wiped data?
Click to expand...
Click to collapse
Yes. I've flashed many roms before, this seems to be the only one I had ever seen a problem with.
mfpearson said:
if you flash it and get stuck in a bootloop, just pull the battery, and 3-finger back into recovery to flash the rom again.
keep doing this until you get it up and running - took me a few times, including a couple of battery pulls.
Click to expand...
Click to collapse
Word.
Edit: To boot into recovery vol up+vol down+power
Had the same problem. Read somewhere to install the ROM twice in a row in CWM without rebooting inbetween. Worked like a charm.
Thanks for the feedback guys. I'll try this in the morning once I get my hands on the phone again.
Saw this type of behaviour on occasion with cm7 on my aria. Sometimes caused by a bad download of the rom. Did you verify md5s ?
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Don't forget to do a master data clear /reset before trying to boot the new CM7 rom for the first time - clear out the old stuff. Works perfectly here.
Sent from my SGH-I777 using xda premium
I'm having the same issue. I'm getting signature errors when trying to flashCM7.1 stable. I've downloaded it two times now with the same problem. My question is, I'm trying to flash from on the phone itself, storing the zip in the download dir on the phone as I don't have an sd card. Will this even work? I've tried looking around and all I can find is flashing from an sd card. I can get one, I just haven't yet.
squigge said:
I'm having the same issue. I'm getting signature errors when trying to flashCM7.1 stable. I've downloaded it two times now with the same problem. My question is, I'm trying to flash from on the phone itself, storing the zip in the download dir on the phone as I don't have an sd card. Will this even work? I've tried looking around and all I can find is flashing from an sd card. I can get one, I just haven't yet.
Click to expand...
Click to collapse
That's the way I did it. Put the update in the same folder on the internal SD card. I can't even access my external SD card from CWM.
Sent from my SGH-I777 using xda premium
Hmm, I'm not sure what I'm doing wrong then. I did a factory reset, and wiped the cache and get the same thing. I know it wiped because now I have nothing setup on the phone when I boot normally. Suggestions?
Quit downloading the CM7 builds for the International Galaxy S II. They will NOT work. That is why it fails. Look for the Galaxys2ATT build.
Sent from my SGH-I777 using xda premium
I got the build by going to the cm7 website, looking by device, finding the galaxy s 2 and grabbing the stable one. So perhaps that is the incorrect one and I'll look closer for one that has att in it, whenever the site isn't going up and down. They seem to be having issues today.
Make sure you're installing the version located in this thread...
http://forum.xda-developers.com/showthread.php?t=1297568
Specifically this link
Double flash made it work. Thanks guys. + thanks for telling me how to boot into recovery lol. Great rom.
Sorry for the newb issues, it was the wrong version. I got the att version from the thread previously mentioned and that worked perfectly. Thanks!
I have used CWM 5.8.4.5 and 5.8.4.7 in both touch and regular variants, and I have not been able to once restore my nandroid backups successfully. It ALWAYS errors our with "Error while restoring /data!" I don't touch any of the backup files or folders. I have tried this on both ext and int sd cards.
Edit: Same thing happens on Team Epic recovery too.
I'm AT&T SGS3
Been trying all day and still not working.
Bump?
Try a newer variant... 5.8.4.9 works for us sprint users and is now working with rom manager.
Sent from my SPH-L710 using xda premium
That one doesn't work on AT&T ones. I have tried 5.8.4.7 and still doesn't work.
I have tried this too and having the same problem
Stokbroka said:
I have tried this too and having the same problem
Click to expand...
Click to collapse
Anyone have the same problem? Stokbroka what if you use open recovery twrp that just came out today?
Sent from my AT&T Samsung Galaxy S III
This is the situation and what ive tried to fix it. I was on cm9 and wanted to try jellybam so I flashed using cwm . It was successful but wouldn't boot so I tried to reinstall the rom still no luck so I tried going back to cm9 and it got stuck on the s2 logo screen ! I tried odin to flash a stock rom and it was successful but still stuck on the logo screen. Ive tried gb and ics ive tried to flash with and without bootloaders ive tried reparation but that only fails unless I use the pit file but still didn't fix it. If I flash the stock rooted ics rom and then flash cwm zip i can wipe system then flash cm9/10 but that only gets me to the cm animation . It will sit there till the end of time but wont boot! In cwm If I check the log I get this error I:can't partition unsafe device:/dev/block/mmcb1k1p1. It wont factory reset on stock or cwm it only freezes then bootloops. I hope this is enough info please help me! I love my s2 and even tho I have my s3 I miss my s2
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Did you factory reset? What do you mean you reset and it bootloops
Sent from my GS4 running CM11 Kandy Kane
122ninjas said:
Did you factory reset? What do you mean you reset and it bootloops
Sent from my GS4 running CM11 Kandy Kane
Click to expand...
Click to collapse
. yes I tried to factory reset but it just freezes then after 5 min. It try's to boot but gets stuck on the galaxy s2 logo screen. I checked the log in cwm and got the error I posted above. I've been flashing for years and never run into an issue I couldn't fix but this one has me stumped
troutslayermv said:
. yes I tried to factory reset but it just freezes then after 5 min. It try's to boot but gets stuck on the galaxy s2 logo screen. I checked the log in cwm and got the error I posted above. I've been flashing for years and never run into an issue I couldn't fix but this one has me stumped
Click to expand...
Click to collapse
Sorry if this sounds rude but have you googled that error?
Sent from my GS4 running CM11 Kandy Kane
Lol no that's not rude. I would ask the same question. ..I did and from what I've gathered its a corrupt sd card or part of the emmc brick bug. There are patched kernels to fix the same issue on the note but nothing for i777. All it says is factory reset and flash a new rom . Ive done that but still no boot. Roms flash fine and I can get into download mode and recovery but It wont factory reset or boot. Stock recovery says your ui is not prepared please factory reset and a bunch of can't mount data errors but it won't factory reset it just freezes then trys to reboot but gets stuck on the s2 logo then back to recovery. Here is the kicker tho. If I install a duel booting kernel I can install a second rom that boots but primary won't. ...I tried swapping primary and secondary roms but it froze....im just lost on this one and out of tricks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I'm not sure what partition that is. You've go a typo in it, but if the last three letters are correct "1p1", I don't remember seeing that as one of the system partitions. The kernel is in "mmcblk0p5" for instance. It should be "mmcblk1p1" I guess.
If you suspect memory damage to that partition, you can confirm that by trying to pull the data from that memory block with adb or terminal using the following command:
Code:
dd if=/dev/block/mmcblk1p1 of=/sdcard/testBLK
If the memory is damaged, you will get an error message. If the memory block is good, you will get no error message. I guess you could also look into "testBLK" to see what is in there, but of course it will be binary data most likely.
That's the error I got 1p1. Abd is something I haven't done yet. I've used terminal emulator back in the days of my cliq dext but im sure I can handle it...im pretty sure it is corrupt but if I do the test and confirm this how do I fix it? Is it just a matter of deleting or do I have to rewrite the path? Im confused on this
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Actually, this was bad advice. Since your phone is bootlooping, you can't use terminal, doh! If you can get into recovery, you might be able to use adb. Or you could use Red_81's adb portable. You could also try his adb batch file from download mode to see if you can boot it into recovery mode. I guess it will take a little study if you have no experience with it.
Oh, and if the memory is bad, its bad. This is just a way to find out, maybe.
So what your saying is it's dead?!!!
Noooooooo! Lol im looking into maybe getting another one or shipping this one to Samsung to have a new motherboard put in . Just trying to see if there is any hope of bringing her back to life...
sent from my stock galaxy s3
devices: g1 died
cliq/dext sold to developer on simply android
atrix 1 and 2 sold
s2 in a comma
nexus 7 stock
s3 stock
iphone 4 stock
troutslayermv said:
So what your saying is it's dead?!!!
Noooooooo!
Click to expand...
Click to collapse
Not saying that unless you verify for sure that the memory is bad. The only time I've actually heard of eMMC damage, and seen it verified, was in conjunction with the bad stock kernel on 4.0.4. There was also another case where a member sent his phone to Josh at Mobile Tech Videos for Jtag repair, and it was sent back unrepairable due to memory damage. I can't remember for sure, but I think that was due to the 4.0.4 stock kernel too.
You might talk to Josh at Mobile Tech Videos by phone to see what he thinks, before you send it to Samsung.
I tried contacting josh and couldn't reach anyone. I left a message and sent and email but haven't heard back. I tried using adb portable and as I did that I think that I didn't make the phone issues clear. I can get into recovery mode fine I can also get into download mode fine . I can flash roms fine but it won't go past the s2 logo screen . If I flash cyanogen it will go to the cyanogen boot screen but again won't boot. I am still trying to find a solution in my free time but nothing yet
sent from my stock galaxy s3
devices: g1 died
cliq/dext sold to developer on simply android
atrix 1 and 2 sold
s2 in a comma
nexus 7 stock
s3 stock
iphone 4 stock
troutslayermv said:
I tried contacting josh and couldn't reach anyone. I left a message and sent and email but haven't heard back. I tried using adb portable and as I did that I think that I didn't make the phone issues clear. I can get into recovery mode fine I can also get into download mode fine . I can flash roms fine but it won't go past the s2 logo screen . If I flash cyanogen it will go to the cyanogen boot screen but again won't boot. I am still trying to find a solution in my free time but nothing yet
sent from my stock galaxy s3
devices: g1 died
cliq/dext sold to developer on simply android
atrix 1 and 2 sold
s2 in a comma
nexus 7 stock
s3 stock
iphone 4 stock
Click to expand...
Click to collapse
I have run into something similar, my wife has the s2... I have the s3....
this is the steps I run to get the s2 working after it gets stuck...
1 - installed stock rom I777UCKH7 OCD Root No BL = self executable from windows.... brings you to stock with root..
forget this one, this is when I was first rooting... 2 - DooMLoRD_v4_ROOT-zergRush-busybox-su
3 - MobileODINLite-v3.57
4 - MobileODIN_FlashKernel_I777-v1.0
5 - flash kernal Siyah-v2.6.14-att.tar = installs recovery clockwork mod
6 - install any rom....
Download mode on S2 is volume up and down and power button....
I can't get it to boot up so I can't use mobile odin. I've tried one click and also tried every stock tar I could find . I even tried to reinstall the bootloaders. They all install successful but it wont boot past the s2 logo screen. Im not a noob , I've flashed hundreds of times. I've fixed a few bricks in my day but this has me stumped. ...if you install the stock rom there isn't any reason why it shouldn't boot. But it is just stuck. Nothing has worked. I think the only thing that may work is the re write the memory but im not that patient to do that lol
sent from my stock galaxy s3
devices: g1 died
cliq/dext sold to developer on simply android
atrix 1 and 2 sold
s2 in a comma
nexus 7 stock
s3 stock
iphone 4 stock
Have U tried threatening it? Just give it a little scare. It'll back dowin. Gotta keep thoz hoez in line.
Phalanx7621 said:
Have U tried threatening it? Just give it a little scare. It'll back dowin. Gotta keep thoz hoez in line.
Click to expand...
Click to collapse
ROFL
Sent from my SGH-I777 using xda premium
gireeshtty9 said:
ROFL
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Just curious if you unmounted and remounted the partitions?
or maybe formatted them individually?
Soft-bricked Galaxy 2 SGH-I777. Odin of no use
I bought a galaxy 3. I literally tried everything with this phone. Was able to root, went to install siyah kernel from zip and now I get the samsung logo. I can boot into CWM recovery, but none of the functions work--just hangs on the hat. Any ideas are greatly appreciated. Thanks.
keltaurn said:
...Any ideas are greatly appreciated...
Click to expand...
Click to collapse
Please don't re-post; your question has been answered in the thread you created. Please search for answers first; the solution to your problem is safely housed in a sticky in the General section.
Thanks but...
I can't flash anything so this would be a new thread. The poster above said he/she could flash toms. I CANNOT. Also, I've been looking on here for solutions for over a month. This is my first post.
Anyone have an idea why every time I install an aosp rom it glitches at the Samsung boot screen then just goes black and I have to pull the battery? I've installed clean, jelly beans and jedi Rom without issue. Any help is appreciated.
Update your twrp then try again. Make sure your doing full wipes and flashing gapps
Sent from my SCH-I605 using Tapatalk 2
hopesrequiem said:
Update your twrp then try again. Make sure your doing full wipes and flashing gapps
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Just updated my TWRP to 2.4 and did what you suggested with the wiping and same problem.
The Samsung Galaxy screen glitches to half way off the screen, then goes off, then comes back on then the whole thing goes black and nothing.
I'm going to try another rom and see if it still does it as well.
dudeicles said:
Just updated my TWRP to 2.4 and did what you suggested with the wiping and same problem.
The Samsung Galaxy screen glitches to half way off the screen, then goes off, then comes back on then the whole thing goes black and nothing.
I'm going to try another rom and see if it still does it as well.
Click to expand...
Click to collapse
Even with another ROM it doesn't seem to want to work. It's really weird, because any Touchwiz ROM works fine, it only does it on AOSP roms..... I'm hoping someone knows what the fix for this is.
dudeicles said:
Even with another ROM it doesn't seem to want to work. It's really weird, because any Touchwiz ROM works fine, it only does it on AOSP roms..... I'm hoping someone knows what the fix for this is.
Click to expand...
Click to collapse
Odin to stock then re unlock and try this all again? I'm not sure what else you can try. I flip between aosp and tw almost daily
Sent from my SCH-I605 using Tapatalk 2
The Note 2 that couldn't...
Sent from my SCH-I605 using Tapatalk 2
1ManWolfePack said:
The Note 2 that couldn't...
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Heh I think I can I think I can...I was thinken are you trying to flash the file that the post links to because thats not the right one you need to get the note 2 lte one tolte..just a though I downloaded the wrong one first but caught it
http://changelog.bbqdroid.org/#t0lte/cm10.1/next
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Acery said:
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Click to expand...
Click to collapse
Yeah it can't hurt even if they don't say that
Sent from my SCH-I605 using Tapatalk 2
Acery said:
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Click to expand...
Click to collapse
Would it help in any way to change to CWM when flashing my AOSP roms?
dudeicles said:
Would it help in any way to change to CWM when flashing my AOSP roms?
Click to expand...
Click to collapse
I would try cwm, I had a gs3 that couodnt flash anything with cwm but could with twrp, my note was the opposite, cwm was awful on it.
Just ran into something very interesting . When I installed Rom Manager and flashed the CWM recovery, I rebooted and my boot screen did the exact same thing it was doing installing AOSP roms. It would seem my problem may just be CWM.
dudeicles said:
Just ran into something very interesting . When I installed Rom Manager and flashed the CWM recovery, I rebooted and my boot screen did the exact same thing it was doing installing AOSP roms. It would seem my problem may just be CWM.
Click to expand...
Click to collapse
I've heard too many issues with cwm to even try it. Twrp has been flawless for me so why switch? If it ain't broke, don't fix it.
Sent from my SCH-I605 using Tapatalk 2
Ok, so update - Odin'd back to stock and re-rooted using the Casual method. I have the most recent TWRP installed and when i install the AOSP rom it does the exact same thing. I'm thinking about videotaping what the boot animation does and maybe someone can look at it and see what the cause may possibly be.
If anyone has any other suggestions i'm all ears. Again, any rom based on STOCK works without issue (Clean Rom, Jelly Beans and Jedi), but only AOSP roms (And CWM) crash the phone at "Samsung Galaxy Note II" screen on startup.
Thanks for the suggestions so far, just weird it's not working. I may have the single note 2 to never run AOSP roms. LOL
so... oddly enough i still have trouble installing AOSP roms. the only AOSP rom i have been able to install so far is Paranoid Droid. I am slowly trying each one just to see which one i can force to work. Am I the only person who can't just flash whichever rom I want whenever?
Anyone with other ideas on this? I was frequently flashing back and forth between TW and AOSP. The other day I tried to flash AOSP again and get a failed message in TWRP. Already using latest version of TWRP. I then restore a backup of TW. Download again, verify md5, get failed message again. And yes, I wiped everything...same thing I do everytime. Now I have tried to DL and flash multiple different AOSP roms and I get failed everytime. Decided to try CWM recovery and that just aborts. I have NO problems flashing TW roms though
Follow the advice to Odin back to stock and start over. Otherwise, get a replacement and tell them it's acting weird and slow haha.
Sent from my SCH-I605 using xda app-developers app
Same here!!
spydersilk said:
Anyone with other ideas on this? I was frequently flashing back and forth between TW and AOSP. The other day I tried to flash AOSP again and get a failed message in TWRP. Already using latest version of TWRP. I then restore a backup of TW. Download again, verify md5, get failed message again. And yes, I wiped everything...same thing I do everytime. Now I have tried to DL and flash multiple different AOSP roms and I get failed everytime. Decided to try CWM recovery and that just aborts. I have NO problems flashing TW roms though
Click to expand...
Click to collapse
I currently have a Tmobile Note 2. And i recently ran into the same issue. I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb. I also notice that it changed my device id to an SGH-i317, which is an ATT Note 2. The rom was a port from an ATT rom of course, but if it was for ATT, it wouldn't work on my device right? I installed GOOmanager, and flashed the OPEN INSTALL SCRIPT. Which it flashed the ATT version. Everything still worked. I flashed back to stock, and updated OTA. Still nothing. I've also noticed that, if i can open the zip file on my pc, it will work on my phone. For some reason, The AOSP files read invalid. While the Touchwiz roms open like a regular zip file.
Any help is appreciated. Hope some of this info helps.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
slinky42 said:
I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
Click to expand...
Click to collapse
This is standard on 4.2.2 ROMs. It is related to the multi-user implementation.
slinky42 said:
I currently have a Tmobile Note 2. And i recently ran into the same issue. I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb. I also notice that it changed my device id to an SGH-i317, which is an ATT Note 2. The rom was a port from an ATT rom of course, but if it was for ATT, it wouldn't work on my device right? I installed GOOmanager, and flashed the OPEN INSTALL SCRIPT. Which it flashed the ATT version. Everything still worked. I flashed back to stock, and updated OTA. Still nothing. I've also noticed that, if i can open the zip file on my pc, it will work on my phone. For some reason, The AOSP files read invalid. While the Touchwiz roms open like a regular zip file.
Any help is appreciated. Hope some of this info helps.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
Click to expand...
Click to collapse
Did you ever get your phone to install the AOSP Roms? Mine worked when l just let the phone sit. Now it works fine all the time.
Sent from my SCH-I605 using xda app-developers app
Dear members of XDA I kindly ask for your help after hours of searching for a valid solution.
After running on my Tab 10.1 for 3 years it got slower and slower, and I decided to install Cyanogenmod today. The tab is successfully rooted. I got the cm-10.1-20130811-NIGHTLY-p4wifi and gapps-jb-20130301-signed and uploaded them to the internal SD storage. I tried to make a backup from ClockworkMod Recovery v5.8.3.1 but it failed. I did a data&factory reset and installed CM and gapps.
The Samsung logo passes normally but the blue Cyanogen one lasts infinitely. Does anyone have a solution, or could anyone point me the mistake I probably omitted in the process? I should also add that I cannot enter the SD card from WIndows. If I missed a valid point, please point it out. Any help will be appreciated.
After 3 years of using it I do not want to throw it away yet, please help,
Thanks in advance,
Vecanoi
Vecanoi said:
Dear members of XDA I kindly ask for your help after hours of searching for a valid solution.
After running on my Tab 10.1 for 3 years it got slower and slower, and I decided to install Cyanogenmod today. The tab is successfully rooted. I got the cm-10.1-20130811-NIGHTLY-p4wifi and gapps-jb-20130301-signed and uploaded them to the internal SD storage. I tried to make a backup from ClockworkMod Recovery v5.8.3.1 but it failed. I did a data&factory reset and installed CM and gapps.
The Samsung logo passes normally but the blue Cyanogen one lasts infinitely. Does anyone have a solution, or could anyone point me the mistake I probably omitted in the process? I should also add that I cannot enter the SD card from WIndows. If I missed a valid point, please point it out. Any help will be appreciated.
After 3 years of using it I do not want to throw it away yet, please help,
Thanks in advance,
Vecanoi
Click to expand...
Click to collapse
Download the latest cwm recovery from http://droidbasement.com/db-blog/ and flash it. Your problem is that your current recovery can't handle the file system changes in 4.2.2.
Sent from my GT-P7500 using Tapatalk HD
Thanks for the insight. I have updated the Recovery to v6.0.3.4. Wiped Delvik, Factory Data Reset and Cache Partition, then installed the zips again. Still nothing. Could the problem be in gapps or in cm-10.1? Is there a way to put newer zips somehow on the device, or am I stuck with the ones I uploaded before the first reset?
Thanks in advance,
Vecanoi
Vecanoi said:
Thanks for the insight. I have updated the Recovery to v6.0.3.4. Wiped Delvik, Factory Data Reset and Cache Partition, then installed the zips again. Still nothing. Could the problem be in gapps or in cm-10.1? Is there a way to put newer zips somehow on the device, or am I stuck with the ones I uploaded before the first reset?
Thanks in advance,
Vecanoi
Click to expand...
Click to collapse
Then try flashing back to stock ICS first then flash cwm, then cm10.1 and gapps. There is nothing wrong with the way you put into your tab. If its there, its there.
Sent from my GT-P7500 using Tapatalk HD
Sorry, can you tell me where to find Stock ICS in the Recovery Mod, if it is there? My backup failed as I said.
Vecanoi said:
Sorry, can you tell me where to find Stock ICS in the Recovery Mod, if it is there? My backup failed as I said.
Click to expand...
Click to collapse
www.sammobile.com. You extract it, then flash the .tar.md5 file via Odin in download mode just like the recovery.
Sent from my GT-P7500 using Tapatalk HD
Thanks eushaun99, at least I'm back to normal ROM, but I'll try again, that's for sure.