hi, i recently broke my old gs2's screen but as i had an insurance i got a brand new phone. i was wondering wheter it would be possible to restore a CWM-backup of my old ROM to the new phone, which would safe me a lot of time, as opposed to restoring everything manually. I tried just putting the backup in the correct folder and tried to restore it from CWM recovery, but i've encountered an MD5-mismatch! error at the beginning of the proces.. so i was wondering of there is any way to work around this problem..
wootyv said:
hi, i recently broke my old gs2's screen but as i had an insurance and i got a brand new phone. i was wondering wheter it would be possible to restore a CWM-backup of my old ROM to the new phone, which would safe me a lot of time, as opposed to restoring everything manually. I tried just putting the backup in the correct folder and tried to restore it from CWM recovery, but i've encountered an MD5-mismatch! error at the beginning of the proces.. so i was wondering of there is any way to work around this problem..
Click to expand...
Click to collapse
make sure you are running the same kernel you used, when you created those backups on your new phone.
The restore process should work well after that.
For example, if you were running Siyah 3.2 when you created those backups then flash Siyah 3.2 on your new phone or at worst Siyah 3.x.
Swyped from my Samsung Galaxy SII
Jokesy said:
make sure you are running the same kernel you used, when you created those backups on your new phone.
The restore process should work well after that.
For example, if you were running Siyah 3.2 when you created those backups then flash Siyah 3.2 on your new phone or at worst Siyah 3.x.
Swyped from my Samsung Galaxy SII
Click to expand...
Click to collapse
i was at siyah kernel, but actually i dont really remember what version.. now i'm back at latest siyah kernel, but apparantly i wasn't on last version when i did the backup.. i'll try to install older versions of siyah and try again, thanks
actually, that doesnt really make sense to me.. the purpose of a nandroid is to restore your full rom when u messed up on something new.. so u won't be always on the same kernel, still it always worked for me.. any reason you would need to have the same kernel when it is another phone?
wootyv said:
actually, that doesnt really make sense to me.. the purpose of a nandroid is to restore your full rom when u messed up on something new.. so u won't be always on the same kernel, still it always worked for me.. any reason you would need to have the same kernel when it is another phone?
Click to expand...
Click to collapse
I suspect its to stop retards trying to restore incorrect device backup and also because of some kernels restoring/backup differently to others so its all to stop you bricking your device.
Just install correct kernel and you shouldnt have a prob. There is also a way to bypass the check afaik, but I wouldnt advise it.
ok sorry, sound quite logic indeed.. maybe i was a bit of a retard there (although i'd consider people who really restore backup from a totally different kind of phone far more retarded )
no luck on same kernel neither, tried even adding same rom but didn't work
ok, now i'm in big trouble, tried to restore my stock backup i made, error in restoring system, stuck at siyah boot logo and unable to enter recovery, what now?
was able to get into download mode, will try to flash stock rom through odin..
wootyv said:
ok, now i'm in big trouble, tried to restore my stock backup i made, error in restoring system, stuck at siyah boot logo and unable to enter recovery, what now?
Click to expand...
Click to collapse
Flash your firmware back via Odin.
Ps:
1.Something messy must have gone wrong during your restore.
2. I always makes a full set up device in my phone, then restore it on my friends' phones without issues.
Swyped from my Samsung Galaxy SII
well, i guess that since now also the stock restore has gone wrong it has something to do with my recovery.. so if i get my phone working again i'll try to start all over again..
wootyv said:
well, i guess that since now also the stock restore has gone wrong it has something to do with my recovery.. so if i get my phone working again i'll try to start all over again..
Click to expand...
Click to collapse
Are you sure you really restored the backup using the same kernel version?
Swyped from my Samsung Galaxy SII
pretty sure, is i used the zip i found in a backup of the memory of my old phone.. but got it working again, that's already a huge relief.. next try will be for tomorrow, thanks for your help anyway
oh yeah, as i have to start all over again, maybe you have an idea on how to root it without triggering custom counter? i somehow succeeded one time but since then only had problems... mainly the reason of all the error is already there..
wootyv said:
oh yeah, as i have to start all over again, maybe you have an idea on how to root it without triggering custom counter? i somehow succeeded one time but since then only had problems... mainly the reason of all the error is already there..
Click to expand...
Click to collapse
1. Root it with this method
2. Flash Siyah kernel using the Temporary recovery after successful rooting
this will not increase counter.
However, if you have in a way increased your counter, just use Triangle away App by chainfire to reset it. Root is needed for the App to function
thanks alot
unfortunatly, that's the method i used, so or something went wrong the first time, or the problem wasn't that part, leaving me in doubt where it might have taken place
and thanks for triangle away link, i knew it existed but i always thought it just removed the triangle but didn't really reset the counter.. now by clicking again on your link i read the description so now i know that there is another way then buying a jig, so maybe i'll just flash using odin, leaving the counter on 1, but having a way to reset it when i should ever need to..
Code:
su
mount -o remount rw /sdcard
cd /sdcard/clockworkmod/backup/xxxx-xx-xx.yy.yy.yy
rm nandroid.md5
md5sum *img > nandroid.md5
Also found that, and it worked, sent from my restored Galaxy sii, thanks guys, problem solved
wootyv said:
Also found that, and it worked, sent from my restored Galaxy sii, thanks guys, problem solved
Click to expand...
Click to collapse
Glad to hear that.
Can you add SOLVED to the thread title? That will be great
Swyped from my Samsung Galaxy SII
Jokesy said:
make sure you are running the same kernel you used, when you created those backups on your new phone.
The restore process should work well after that.
For example, if you were running Siyah 3.2 when you created those backups then flash Siyah 3.2 on your new phone or at worst Siyah 3.x.
Swyped from my Samsung Galaxy SII
Click to expand...
Click to collapse
Hey thanks you helped me. I just have one question. I'm into Android rooting/flashing/etc for almost two years now and I wondered, how do you know this stuff? I mean I read a lot about android but I would never have figured the kernel would be the problem.
Related
I still have a few questions before rooting my phone for the first time.
1) if i root 2.3.6 using the right kernel, Can i still install an ics custom rom like resurrection?
2) if i root stock 4.0.3 Poland version or argentinian version, final result of installing a new custom Rom is gonna be the same because it completely replace the first one?
3) what's the difference between nandroid backup and cwm way to backup custom rom? Do i need to keep my backup inside the phone in order to unbrick it tomorrow, or may i just store it on my notebook and delete it from the phone?
Thanks a lot!!
Sent from my GT-I9100 using Tapatalk 2
feden84 said:
I still have a few questions before rooting my phone for the first time.
1) if i root 2.3.6 using the right kernel, Can i still install an ics custom rom like resurrection?
2) if i root stock 4.0.3 Poland version or argentinian version, final result of installing a new custom Rom is gonna be the same because it completely replace the first one?
3) what's the difference between nandroid backup and cwm way to backup custom rom? Do i need to keep my backup inside the phone in order to unbrick it tomorrow, or may i just store it on my notebook and delete it from the phone?
Thanks a lot!!
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
1) Rooting is just to give you access to CWM.. ergo the ability to install custom ROMS so you can install ROMS after rooting
2) When you flash a new ROM (which is rooted) then you dont have to bother about what did you did before that..
3) If i'm not mistaken CWM only allows u to do a nandroid backup.. And if u want to restore to the backup ( in ur case unbrick :silly U need to have that in ur sd card :good:
Happy rooting.. Happy flashing..
1) Follow whatever instructions the rom you're wanting to use has to the letter.
2) If you install a custom rom, then yes, obviously it will replace any stock rom you flash it over the top of.
3) A CWM backup is a Nandroid backup. It's the same thing. You can store your backups wherever you want. I have my 4 most recent Nandroids on my phone, and I have every backup I've ever done on my phone stored on my PC (and another copy on an external drive I use for backups). So I guess the question you're asking is, can I take a Nandroid backup from ages ago stored on my PC, put it on my phone & restore it. Am I right ? If that's what you're asking, the answer is yes.
Thanks. Actually i was asking in case my phone bricks after installing a new rom. I guess i won't be able to come it back to life if i don t have the backup in the phone.
And one more thing. What is efs backup. Do I also need to do it?
Thanks
Sent from my GT-I9100 using Tapatalk 2
Yes. The 2nd thing you should do after your root your phone (first thing is do a Nandroid backup) is to get kTool from Google Play & backup your EFS. Before you install another rom or kernel do both of those.
Keep a copy on your external sdcard & keep another copy on your PC. Just in case you ever need it. We get quite a few people on here every week with IMEI/EFS details gone & most don't have EFS backups.
thanks!
I forgot to ask, is there any real risk at using triangle away app? So far, is it working on any kernel? thanks
feden84 said:
I forgot to ask, is there any real risk at using triangle away app? So far, is it working on any kernel? thanks
Click to expand...
Click to collapse
I've actually used that app a few times well (about 5) and haven't had any issues but once you get CWM installed and you flash kernels through it you won't get the yellow triangle.
Sent from my GT-I9100 using Tapatalk 2
feden84 said:
I forgot to ask, is there any real risk at using triangle away app? So far, is it working on any kernel? thanks
Click to expand...
Click to collapse
There will always be a risk when using anything that manupulates root access, but triangle away is quite safe, as for what kernel if works on, most kernel threads will say if it is compatiable or not, but only with ICS kernels, not GB kernels.
"...once you get CWM installed and you flash kernels through it you won't get the yellow triangle."
What do you mean by that? I actually don´t need to use the app, because triangle will dissapear anyway after flashing a Kernel?
feden84 said:
"...once you get CWM installed and you flash kernels through it you won't get the yellow triangle."
What do you mean by that? I actually don´t need to use the app, because triangle will dissapear anyway after flashing a Kernel?
Click to expand...
Click to collapse
You will still have the triangle after flashing a new rom or kernel, the best way to get rid of it is triagle away, this app will also reset your flash counter.
Once you get a working CWM, let's say you're using Cyanogenmod 9 and you want to flash over the stock kernel.
You'd put the kernel file on the memory of the device (sdcard) and boot in CWM recover and flash from there and you won't get the triangle.
The triangle won't go away now if you unless you use a USB jig or the triangle away app. So get rid of the triangle now and when you want to try a new kernel flash it through CWM and the triangle won't appear. Flash a kernel through download mode and you'll get the triangle.
Sent from my GT-I9100 using Tapatalk 2
After going through FAQ i succesfully rooted my s2 for the first time since im new to andorid and been an iphone user for 3 years.
I'm loving my s2 so far and want to flash custom rom can some one pls tell me how fixing permission works when flashing new rom is it the same on all custom roms for galaxy s2?
I want to flash the latest resurrection remix and want to know what to do when i get to the fixing permission section like how im gona be prmoted to enter the letters.....I read FAQ but need more pls
Thanks in advance
Force F said:
After going through FAQ i succesfully rooted my s2 for the first time since im new to andorid and been an iphone user for 3 years.
I'm loving my s2 so far and want to flash custom rom can some one pls tell me how fixing permission works when flashing new rom is it the same on all custom roms for galaxy s2?
I want to flash the latest resurrection remix and want to know what to do when i get to the fixing permission section like how im gona be prmoted to enter the letters.....I read FAQ but need more pls
Thanks in advance
Click to expand...
Click to collapse
Fixing permissions is automatic I believe in CWM recovery. It's an option in the recovery menu. Remember to wipe data and cache (dalvik too) when flashing a next rom or else you won't be able to boot.
Sent from my GT-I9100 using Tapatalk 2
Thanks for the info mate
By the way, you should really just buy a USB Jig off eBay for a few quid, it resets the custom binary counter (on old bootloaders) and can also force your phone into download mode after a bad flash. Handy to have around. Also, now that you have rooted your phone, download EFS Pro (found here on XDA) and back up your EFS folder before any flashing. Lose this folder and your in serious trouble!
Sent from my GT-I9100 using Tapatalk 2
Hi! When rooting or flashing a custom rom or kernel, do I lose internal sd card content?
Where is the EFS folder I need to backup?
Thanks!
Sorry for my newbie question, but is there any way to restore from a CWM backup via PC (using Odin or something else).
The reason is that whenever i go into CWM recovery, it crashes and reboots before i have a chance to even select the update.
< Background Story> I accidently updated my Samsung Galaxy S3 i9300 while it was rooted on Stock rom, it wouldnt turn on after that, but keeps rebooting at the "Samsung Galaxy S3 i9300" screen. i tried to install stock firmwares, i tried countless times with CWM to recover, but all failed. now my only option left is to Jtag or give it to the service centre.
So guys is there any way i might be able to install my backup from the CWM recovery i made earlier?
Guys PLEASE Help out a noob. I shall be very thankful.
have you tried reinstalling a stock firmware with Odin?
slaphead20 said:
have you tried reinstalling a stock firmware with Odin?
Click to expand...
Click to collapse
yes i did, multiple times. :/
AusafSal said:
yes i did, multiple times. :/
Click to expand...
Click to collapse
.....and what happens?
slaphead20 said:
.....and what happens?
Click to expand...
Click to collapse
It gives a Write fail or something. I've tried all sorts of firmwares. I've tried flashing the Recovery from CF Root but unfortunately it just restarts the phone after 2-3 seconds after being in it. So can't restore it from there
AusafSal said:
Sorry for my newbie question, but is there any way to restore from a CWM backup via PC (using Odin or something else).
The reason is that whenever i go into CWM recovery, it crashes and reboots before i have a chance to even select the update.
< Background Story> I accidently updated my Samsung Galaxy S3 i9300 while it was rooted on Stock rom, it wouldnt turn on after that, but keeps rebooting at the "Samsung Galaxy S3 i9300" screen. i tried to install stock firmwares, i tried countless times with CWM to recover, but all failed. now my only option left is to Jtag or give it to the service centre.
So guys is there any way i might be able to install my backup from the CWM recovery i made earlier?
Guys PLEASE Help out a noob. I shall be very thankful.
Click to expand...
Click to collapse
I'm another noob but I have been reading and just DL'd and installed the S3 Toolkit from http://forum.xda-developers.com/showthread.php?t=1703488 It looks to me like it will let you do all kinds of things from the PC. I haven't used it yet but there's a good list of options.
Good luck and let us know how it goes.
Journyman16 said:
I'm another noob but I have been reading and just DL'd and installed the S3 Toolkit from http://forum.xda-developers.com/showthread.php?t=1703488 It looks to me like it will let you do all kinds of things from the PC. I haven't used it yet but there's a good list of options.
Good luck and let us know how it goes.
Click to expand...
Click to collapse
You should try and wipe your data/restore factory defaults from the recovery menu itself.
can't promise, but it might help.
Good luck
Hi all,
I was running XWLPT and decided to try Chameleon 1.3. After flashing, it would not boot up. I've tried all kinds of things for the last 2 days, and read quite a bit. I've even tried the method in this thread http://forum.xda-developers.com/showthread.php?t=1457458
At the moment, I can get into recovery and I can get to download (power+vol down+middle button). But it's stuck at the Galaxs SII GT-I9100 very beginning boot up. Nothing seems to be working. I've tried several pit repartition and I know it's risky. But at this point, I have nothing to lose I guess.
Can anyone help?
sooby77 said:
Hi all,
I was running XWLPT and decided to try Chameleon 1.3. After flashing, it would not boot up. I've tried all kinds of things for the last 2 days, and read quite a bit. I've even tried the method in this thread http://forum.xda-developers.com/showthread.php?t=1457458
At the moment, I can get into recovery and I can get to download (power+vol down+middle button). But it's stuck at the Galaxs SII GT-I9100 very beginning boot up. Nothing seems to be working. I've tried several pit repartition and I know it's risky. But at this point, I have nothing to lose I guess.
Can anyone help?
Click to expand...
Click to collapse
Boot into recovery, wipe data (factory reset), wipe cache and try to flash the custom ROM again.
Good luck !
The issue is, I can't even wipe factory data. It will start and then just sits there, unable to complete the wipe. I'm so out of ideas.
sooby77 said:
The issue is, I can't even wipe factory data. It will start and then just sits there, unable to complete the wipe. I'm so out of ideas.
Click to expand...
Click to collapse
Have you tried upload stock rom to phone on download mode? I saw your checked link, maybe you should try with different stock roms like 2.3.5 and etc.. If you try that, what the say ODIN as error?
Flash a siyah kernel with odin.afther you have cwm...
Inviato dal mio GT-N7000 con Tapatalk 2
First of all stop doing things that you are not sure about...
If you can get into Recovery then your problem is simple.
1. Wipe Data/Factory Reset,
2. Wipe cache partition,
3. Advanced/Wipe Dalvik Cache,
4. Flash a new rom (from sdcars probably),
5. Wipe cache partition,
6. Advanced/Wipe Dalvik Cache.
Let me know if this helped.
Hey guys, I apreciate all the responses. panagiostis4te - I am unable to wipe data/factor reset. It just hangs trying to do that. I've let it sit and it never completes.
sinasi11 - ODIN never throws an error. Depending on what firmware I flash, it either get stuck at datafs or data. It just sits there. I've even left it overnight and nothing happens.
I was able to flash to completion a few or the 4.0.4 rom (XWLPF) and it would reboot, show the android logo with animated progress bar. Then it reboots and is then stuck at the Galaxy S2 very first boot screen. I'm so out of ideas.
sooby77 said:
Hi all,
I was running XWLPT and decided to try Chameleon 1.3. After flashing, it would not boot up. I've tried all kinds of things for the last 2 days, and read quite a bit. I've even tried the method in this thread http://forum.xda-developers.com/showthread.php?t=1457458
At the moment, I can get into recovery and I can get to download (power+vol down+middle button). But it's stuck at the Galaxs SII GT-I9100 very beginning boot up. Nothing seems to be working. I've tried several pit repartition and I know it's risky. But at this point, I have nothing to lose I guess.
Can anyone help?
Click to expand...
Click to collapse
Questions:
1 . Have you seen This Warning Thread before?
# I don't think so
2. Were you running a safe Custom kernel before flashing Chameleon?
# I don't think so.
Here are my conclusions
1.
You were affected by the infamous Brick bug.
# You should blame yourself for this, for apparently failing to read that sticky warning thread, or even ask questions before messing with your phone while running the Dreadful ICS 4.0.4 firmware!
2.
The reason why your phone is still partially coming on is because you have a partially insane emmc chip.
# If you were using a fully insane chip, your phone would just black out without any sign of life.
3.
Your Nand /Emmc chip is corrupt!
4.
You can try combinations of pit file and ICS bootloader (where suggested). Who knows, you might be lucky
# Visit here and try the suggested solution
## If it doesn't work, then you can try the combinations suggested here.
5.
Jtag service will probably not work for you.
6.
The only (probably) solution (if the suggestions in 4. doesn't work for you), will be for you to replace the motherboard of your phone.
# Changing motherboard costs between $120 to $200
7.
If your phone is still under a valid warranty, the best solution would be to send it to Samsung Service center. Repair if free.
Sorry about what happened to your phone, but you really must shoulder the blame!
jokesy - thanks for the suggestions. I accept the blame. I was running stock and I read the Chameleon 1.3 thread and didn't see any warnings. I thought everything was safe. I guess lesson learned the hard way!
sooby77 said:
jokesy - thanks for the suggestions. I accept the blame. I was running stock and I read the Chameleon 1.3 thread and didn't see any warnings. I thought everything was safe. I guess lesson learned the hard way!
Click to expand...
Click to collapse
have tried my suggestion 4 yet? any news?
It's a Monday and I've got lots of things I need to take care of I've tried some of the suggestions prior to starting this thread but I'm going to give it another shot. Meanwhile, I'm going to try and survive without a phone for a few days. I'm almost ready to give up. I'm going to work on it more tonight. Will post if I have questions. Thanks again jokesy!
jokesy - I want to report success. I tried several of the pit files and finally at
i9100_u1_02_20110310_emmc_EXT4--patched--brick-between-176-and-2323-MB--FACTORYFS-moved-by-2048-MiB.pit
I was able to get it to complete install and format with bootloaded. The device then booted up! I now have 9.5GB vs 11GB and that's OK. Thank you so much for your help. It's now not the perfect S2, but nevertheless, a usable one! I sincerely appreciated your help. Lesson learned truly the hard way!
sooby77 said:
jokesy - I want to report success. I tried several of the pit files and finally at
i9100_u1_02_20110310_emmc_EXT4--patched--brick-between-176-and-2323-MB--FACTORYFS-moved-by-2048-MiB.pit
I was able to get it to complete install and format with bootloaded. The device then booted up! I now have 9.5GB vs 11GB and that's OK. Thank you so much for your help. It's now not the perfect S2, but nevertheless, a usable one! I sincerely appreciated your help. Lesson learned truly the hard way!
Click to expand...
Click to collapse
Wow! that's a good news at least.
PS: Always try to go through all the sticky threads, they are made for some reasons. Also if you are not sure about something, search, if you can not find clear answers, then ask questions.
Enjoy your phone
Jokesy said:
Wow! that's a good news at least.
PS: Always try to go through all the sticky threads, they are made for some reasons. Also if you are not sure about something, search, if you can not find clear answers, then ask questions.
Enjoy your phone
Click to expand...
Click to collapse
A quick question. Now that the pit is different, I assume that the nandroid backup I made cannot be restored to the device anymore?
sooby77 said:
A quick question. Now that the pit is different, I assume that the nandroid backup I made cannot be restored to the device anymore?
Click to expand...
Click to collapse
I seriously don't know but if you have any important thing you want to extract from your backup, follow these steps:
1. Flash siyah kernel
2. boot to CWM recovery,
- dual boot options
- restore ROM to 2nd ROM (you need about 2.1 Gig free in your internal storage)
- done
3. Boot to your Second ROM
- Extract all info you need
4. Restore these info to your 1st ROM
5. you can delete the Second ROM when done, using the same dual boot menu in CWM recovery.
Thanks Jokesy. I did have 2 backups, Titanium and another backup app (name escape me at the moment). I think I'll restore app data and do it that way instead.
Just go back to original OS
sooby77 said:
Hi all,
I was running XWLPT and decided to try Chameleon 1.3. After flashing, it would not boot up. I've tried all kinds of things for the last 2 days, and read quite a bit. I've even tried the method in this thread http://forum.xda-developers.com/showthread.php?t=1457458
At the moment, I can get into recovery and I can get to download (power+vol down+middle button). But it's stuck at the Galaxs SII GT-I9100 very beginning boot up. Nothing seems to be working. I've tried several pit repartition and I know it's risky. But at this point, I have nothing to lose I guess.
Can anyone help?
Click to expand...
Click to collapse
You can go back to the original OS using Odin and a package found on many sites for the original Gingerbread that came on it... then go to Kies and update to the ICS and there you go. I have done this several times and unbricked mine after a mod. This was the best way for me.
Scott
sooby77 said:
A quick question. Now that the pit is different, I assume that the nandroid backup I made cannot be restored to the device anymore?
Click to expand...
Click to collapse
You said you have Titanium - it can restore elements out of a nandroid backup, almost everything, stright back into place. Much easier than second ROMs.
ScottsDesk said:
You can go back to the original OS using Odin and a package found on many sites for the original Gingerbread that came on it... then go to Kies and update to the ICS and there you go. I have done this several times and unbricked mine after a mod. This was the best way for me.
Scott
Click to expand...
Click to collapse
I've tried that and the flash would get stuck in Odin and never complete.
gyaku_zuki said:
You said you have Titanium - it can restore elements out of a nandroid backup, almost everything, stright back into place. Much easier than second ROMs.
Click to expand...
Click to collapse
Good to know. I am actually waiting for my microsd to sd adaptor to arrive. I accidentally formatted my microsd card with all my data in desperation of trying whatever method to format the device. I accidentally selected format emmc. Took out the card immediately, and am hoping to be able to unformat it in windows since it's using fat32. Fingers crossed!
i have my wifes att gs2. i rooted succesfully with official ics version. made a nandroid backup. attempted to flash an aokp rom (which is what i use on my lg phone). upon reboot it just stuck at samsung gs2 screen. couldnt get into recovery to restore the backup at first. now i am able to get into recovery but now it get and md5 mistmatch when tryin to restore the backup. when i rooted it changed the boot screen to i9100 when the phone is an i777. please help.
thanks
woodardbg said:
i have my wifes att gs2. i rooted succesfully with official ics version. made a nandroid backup. attempted to flash an aokp rom (which is what i use on my lg phone). upon reboot it just stuck at samsung gs2 screen. couldnt get into recovery to restore the backup at first. now i am able to get into recovery but now it get and md5 mistmatch when tryin to restore the backup. when i rooted it changed the boot screen to i9100 when the phone is an i777. please help.
thanks
Click to expand...
Click to collapse
You need to read a little more. The i9100 screen is because you have tripped the flash counter. Recovery is holding power and both volumes forever. Then you Factory reset.
Also maybe next time make the thread title something about the problem you're having. HELP isn't really telling much.
122ninjas said:
You need to read a little more. The i9100 screen is because you have tripped the flash counter. Recovery is holding power and both volumes forever. Then you Factory reset.
Click to expand...
Click to collapse
ive been trying to read up on it. unfortunatley there are different methods scattered everywhere and confusing. however when i do a factory reset its sticks at gs2 gti9100 screen. if you can point me to a thread that has a fix i'd appreciate it. coming from lg forums, these gs2 forums and fixes are a little confusing to me. i guess because of the different variants of the s2's.
thanks
Phalanx7621 said:
Also maybe next time make the thread title something about the problem you're having. HELP isn't really telling much.
Click to expand...
Click to collapse
Not to mention it is also useless for those who respect the forum by doing a search before posting.
woodardbg said:
ive been trying to read up on it. unfortunatley there are different methods scattered everywhere and confusing. however when i do a factory reset its sticks at gs2 gti9100 screen. if you can point me to a thread that has a fix i'd appreciate it. coming from lg forums, these gs2 forums and fixes are a little confusing to me. i guess because of the different variants of the s2's.
thanks
Click to expand...
Click to collapse
Factory reset then flash AOKP FOR OUR PHONE
122ninjas said:
Factory reset then flash AOKP FOR OUR PHONE
Click to expand...
Click to collapse
thanks for your help 122nijas.... ive tried a "supposedly" aokp rom for gs2 i777 but it doesnt come up after reboot. just hangs at the gs2 i9100 screen. i have tried a couple more but nothing seems to work to get a working driver. to me it seems like if i flash a compatible rom, it should work. i am able to get into cmw fine. on top of that, my backup that i did have that had md5 mismatch is no longer there. so when i connect to my pc and usb and navigate to clockwork mod folder it says file is corrupt. so now i have lost that initial bacup it seems.
so what course of action do you think i should try now?
again thanks for ur help
woodardbg said:
thanks for your help 122nijas.... ive tried a "supposedly" aokp rom for gs2 i777 but it doesnt come up after reboot. just hangs at the gs2 i9100 screen. i have tried a couple more but nothing seems to work to get a working driver. to me it seems like if i flash a compatible rom, it should work. i am able to get into cmw fine. on top of that, my backup that i did have that had md5 mismatch is no longer there. so when i connect to my pc and usb and navigate to clockwork mod folder it says file is corrupt. so now i have lost that initial bacup it seems.
so what course of action do you think i should try now?
again thanks for ur help
Click to expand...
Click to collapse
Where are you getting the rom from
Flash another rom ... and for the i9100 screen use this http://forum.xda-developers.com/showthread.php?t=1494114
Sent from my SAMSUNG-SGH-I777
I was trying to upgrade from 4.0.3 to 4.1.2 and I accidently flashed wrong CWM (v5) instead v6 and it got stuck at Samsung logo, reflashed 4.0.3 and now it gets stuck at the S logo (after start up sound).
Anyone know where I can get the multi-file old-style firmware so I can get this working again?
Thanks in advance!
Use Odin.... If You Already Usingtgen tell me Which file you tried to flash...
Sent from my iPhone using Tapatalk
otester said:
I was trying to upgrade from 4.0.3 to 4.1.2 and I accidently flashed wrong CWM (v5) instead v6 and it got stuck at Samsung logo, reflashed 4.0.3 and now it gets stuck at the S logo (after start up sound).
Anyone know where I can get the multi-file old-style firmware so I can get this working again?
Thanks in advance!
Click to expand...
Click to collapse
Here you got ICS ROMs & LS8.
That's for I9100, make sure you're packing the right model as well.
I managed to get it working again by VOLUP+Power+Menu and going into CWM and restoring from a backup.
But it is rather concerning that if I hadn't of had a backup I would be screwed right now, I use Odin and I was using the thread you posted above, however even after flashing those and even wiping user data, it still boot looped.
otester said:
I managed to get it working again by VOLUP+Power+Menu and going into CWM and restoring from a backup.
But it is rather concerning that if I hadn't of had a backup I would be screwed right now, I use Odin and I was using the thread you posted above, however even after flashing those and even wiping user data, it still boot looped.
Click to expand...
Click to collapse
hummm.........
If you can flash a back up you should be able to flash anything else. I mean, there's nothing wrong with your device.
Are you sure kies is all closed before flashing via Odin?
Try Mobile Odin to flash a stock ROM.
otester said:
I managed to get it working again by VOLUP+Power+Menu and going into CWM and restoring from a backup.
But it is rather concerning that if I hadn't of had a backup I would be screwed right now, I use Odin and I was using the thread you posted above, however even after flashing those and even wiping user data, it still boot looped.
Click to expand...
Click to collapse
Did you try follow the guide here: http://forum.xda-developers.com/showthread.php?t=1108499
It outlines what you did, only it suggests flashing a stock ROM through Odin instead of restoring a backup. Data stored on the internal memory will be lost during process, but it seems you have no way of retrieving it anyway! Give it a go with the stock ROM's link that gastonw linked you.
otester said:
I managed to get it working again by VOLUP+Power+Menu and going into CWM and restoring from a backup.
But it is rather concerning that if I hadn't of had a backup I would be screwed right now, I use Odin and I was using the thread you posted above, however even after flashing those and even wiping user data, it still boot looped.
Click to expand...
Click to collapse
Dude, your device was not "bricked" and it was of no concern. The problem was simply that you flashed a incompatible kernel.
To solve it all you needed to do was flash compatible kernel in download mode using ODIN and you would have then had correct cwm, root and rom would have booted no problem.