Current setup - stock - 4.0.4 - I have not made any modifications to this phone so far other than upgrading it from GB OTA. It is the standard unlocked SIM free UK/Irelend edition.
PDA: I9100XWLPT
PHONE: I9100XXLQ6
CSC: I9100XEULPA
I am interested in trying the stock leaked version of 4.1.2 - actually I'm fed up with waiting for the official release which always seems to be "coming in the very near future" but never arrives.
I have read around extensively on this site and others about how to do this, but still have some questions that I would be grateful if someone could answer.
1. Brick bug - I have run eMMC check and it reports that it reports: NO. Sane chip. Does this mean that I have nothing to fear regarding factory resets/data wiping on 4.0.4?
2. Some mention that USB debugging should be checked - others make not mention of it at all. Should USB debugging be checked in this case when going up to 4.1.2 or back down to 4.0.4?
3. Should the SIM card be removed before flashing with odin or is it alright to leave it in?
4. When the phone reboots after flashing 4.1.2 with odin, some tutorials do nothing and let the phone reboot - others suggest removing the battery as it begins to reboot and then booting into stock recovery mode and doing a factory reset, wipe cache. Some even say also wipe dalvik cache. Is this battery removal step necessary? Or should the phone be left to attempt to boot and if the process hangs enter recovery and reset/wipe cache?
5. I have read in a couple of cases that the SIM lock has been activated after this flashing procedure on a previously unlocked phone. I have found an unlock apk on this forum that can resolve this issue. But why does it happen? How common is this problem?
6. In my 4.1.2 download from Sammobile there are 2 files that are not mentioned in the articles I have read. emmc_EXT4_16GB.pit and emmc_EXT4_32GB.pit - what are these for? Are they needed for this procedure?
7. How long should the reboot process take after the flashing is complete? - or after how long should I start to get worried if it seems to be stuck?
8. If I wish to return to stock 4.0.4 (here the brick bug is the problem yes?)- is the procedure the same as flashing 4.1.2? And if I do go back to 4.0.4 stock will the phone work with KIES again?
9. I have odin 3.07 - is this version appropriate for this procedure?
dimbo33 said:
Current setup - stock - 4.0.4 - I have not made any modifications to this phone so far other than upgrading it from GB OTA. It is the standard unlocked SIM free UK/Irelend edition.
PDA: I9100XWLPT
PHONE: I9100XXLQ6
CSC: I9100XEULPA
I am interested in trying the stock leaked version of 4.1.2 - actually I'm fed up with waiting for the official release which always seems to be "coming in the very near future" but never arrives.
I have read around extensively on this site and others about how to do this, but still have some questions that I would be grateful if someone could answer.
1. Brick bug - I have run eMMC check and it reports that it reports: NO. Sane chip. Does this mean that I have nothing to fear regarding factory resets/data wiping on 4.0.4?
Yes. If you have the sane/safe chip no need to worry.
2. Some mention that USB debugging should be checked - others make not mention of it at all. Should USB debugging be checked in this case when going up to 4.1.2 or back down to 4.0.4?
Doesn't matter whether it is on or off. It's just for debugging. I usually keep it on since you don't know when it might be useful. There is no harm in keeping it ticked.
3. Should the SIM card be removed before flashing with odin or is it alright to leave it in?
No need to remove sim card.
4. When the phone reboots after flashing 4.1.2 with odin, some tutorials do nothing and let the phone reboot - others suggest removing the battery as it begins to reboot and then booting into stock recovery mode and doing a factory reset, wipe cache. Some even say also wipe dalvik cache. Is this battery removal step necessary? Or should the phone be left to attempt to boot and if the process hangs enter recovery and reset/wipe cache?
After flashing, your phone will restart. If it doesn't go past the samsung logo, you'll need to pull out the battery, reinsert it, boot into recovery and perform a factory reset. Wiping cache and dalvik isn't necessary. However, if you do boot into recovery (which most certainly you'll have to, to do the data wipe), it takes less than 15 seconds to wipe the cache and dalvik.
5. I have read in a couple of cases that the SIM lock has been activated after this flashing procedure on a previously unlocked phone. I have found an unlock apk on this forum that can resolve this issue. But why does it happen? How common is this problem?
I believe it's designed to be that way. However, I am not sure about this one. Sorry.
6. In my 4.1.2 download from Sammobile there are 2 files that are not mentioned in the articles I have read. emmc_EXT4_16GB.pit and emmc_EXT4_32GB.pit - what are these for? Are they needed for this procedure?
No need for the .pit files. Better avoid them at all costs.
7. How long should the reboot process take after the flashing is complete? - or after how long should I start to get worried if it seems to be stuck?
Don't worry. You'll know when to worry ... Taking upto 5 minutes is perhaps normal. After that, update here if you think there is a problem.
8. If I wish to return to stock 4.0.4 (here the brick bug is the problem yes?)- is the procedure the same as flashing 4.1.2? And if I do go back to 4.0.4 stock will the phone work with KIES again?
Yes, and yes.
9. I have odin 3.07 - is this version appropriate for this procedure?
Better use v1.83 or v1.85. I've read a complaint against the latest one. Old is gold in some cases
Click to expand...
Click to collapse
I've replied under every question. Didn't want to quote the whole thing then write my answers, or scroll up and down continuously. Good luck and don't worry
Sent from my GT-I9100 using Tapatalk 2
Spiralzz said:
I've replied under every question. Didn't want to quote the whole thing then write my answers, or scroll up and down continuously. Good luck and don't worry
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your answers. I appreciate it. I've done this kind of thing loads of times on other types of device, but I'm always nervous as hell when it's the first time and don't want any holes in my understanding of the process.
dimbo33 said:
Current setup - stock - 4.0.4 - I have not made any modifications to this phone so far other than upgrading it from GB OTA. It is the standard unlocked SIM free UK/Irelend edition.
PDA: I9100XWLPT
PHONE: I9100XXLQ6
CSC: I9100XEULPA
I am interested in trying the stock leaked version of 4.1.2 - actually I'm fed up with waiting for the official release which always seems to be "coming in the very near future" but never arrives.
I have read around extensively on this site and others about how to do this, but still have some questions that I would be grateful if someone could answer.
1. Brick bug - I have run eMMC check and it reports that it reports: NO. Sane chip. Does this mean that I have nothing to fear regarding factory resets/data wiping on 4.0.4?
2. Some mention that USB debugging should be checked - others make not mention of it at all. Should USB debugging be checked in this case when going up to 4.1.2 or back down to 4.0.4?
3. Should the SIM card be removed before flashing with odin or is it alright to leave it in?
4. When the phone reboots after flashing 4.1.2 with odin, some tutorials do nothing and let the phone reboot - others suggest removing the battery as it begins to reboot and then booting into stock recovery mode and doing a factory reset, wipe cache. Some even say also wipe dalvik cache. Is this battery removal step necessary? Or should the phone be left to attempt to boot and if the process hangs enter recovery and reset/wipe cache?
5. I have read in a couple of cases that the SIM lock has been activated after this flashing procedure on a previously unlocked phone. I have found an unlock apk on this forum that can resolve this issue. But why does it happen? How common is this problem?
6. In my 4.1.2 download from Sammobile there are 2 files that are not mentioned in the articles I have read. emmc_EXT4_16GB.pit and emmc_EXT4_32GB.pit - what are these for? Are they needed for this procedure?
7. How long should the reboot process take after the flashing is complete? - or after how long should I start to get worried if it seems to be stuck?
8. If I wish to return to stock 4.0.4 (here the brick bug is the problem yes?)- is the procedure the same as flashing 4.1.2? And if I do go back to 4.0.4 stock will the phone work with KIES again?
9. I have odin 3.07 - is this version appropriate for this procedure?
Click to expand...
Click to collapse
Firstly,
Idk exactly about USB debugging but what i do know is that...
"USB Debugging is intended for development purposes only. It can be used to copy data between your computer and your device, install applications on your device without notification, and read log data." A few apps use it, like the aforementioned PdaNet app. USB Debugging can also be used with ADB when issuing commands from a command line on your computer to your Android handset or tablet. One-Click root apps often require USB Debugging to be enabled to deliver the exploit that roots your device.
SIM card wouldn't affect anything, so it doesn't matter if you leave it in the phone..
After Flashing the JB, first check whether the phone goes into boot loop or anything like that....if you experience any problems then do the factory reset, wipe cache...though its usually recommended to factory reset anyways..
I don't think we need to flash the "emmc_EXT4_16GB.pit" or the other pit file..
The reboot process shouldn't take more than 5-10 minutes max..
Well i have gone from custom ROM 4.1.2 XXLSJ back to the stock 4.0.4 using the usual flashing steps of ODIN....I didn't experience any problems..
If its anything above Odin3v1.85 it shouldn't be a problem...
Press thanx if i helped..
Is there any need to do any factory reset/cache wiping from recovery before flashing 4.1.2?
I guess that when I flashed jb leak I had all those questions, and maybe a couple of more.
Then I read about Mobile Odin, flashed & rooted my device in half a smoke (3 mins). All I had to do was select the 3 tar files.
The flash did network lock my device. Galaxysim Unlock solved it for me.
good luck and happy flashing.
dimbo33 said:
Is there any need to do any factory reset/cache wiping from recovery before flashing 4.1.2?
Click to expand...
Click to collapse
Only once. Either before flashing the ROM, or after. Order doesn't matter.
Sent from my GT-I9100 using Tapatalk 2
Spiralzz said:
Only once. Either before flashing the ROM, or after. Order doesn't matter.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
I would imagine then it's better to do it whilst on 4.0.4 prior to flashing (since I have the sane chip) so that you don't get the possible failed boot after flashing 4.1.2 with odin.
So after doing the wipes in recovery prior to flashing, is the phone turned off by a long press of the power button?
dimbo33 said:
I would imagine then it's better to do it prior to flashing so that you don't get the possible failed boot after flashing 4.1.2 with odin.
So after doing the wipes in recovery prior to flashing, is the phone turned off by a long press of the power button?
Click to expand...
Click to collapse
No, I don't think so. Come to think of it, I've never tried that A battery pull works though
Sent from my GT-I9100 using Tapatalk 2
Spiralzz said:
No, I don't think so. Come to think of it, I've never tried that A battery pull works though
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Do you mean it's not better to factory reset before flashing or the long press doesn't turn off the phone from recovery (in which case best to pull the battery out)?
dimbo33 said:
I would imagine then it's better to do it whilst on 4.0.4 prior to flashing (since I have the sane chip) so that you don't get the possible failed boot after flashing 4.1.2 with odin.
So after doing the wipes in recovery prior to flashing, is the phone turned off by a long press of the power button?
Click to expand...
Click to collapse
Well since your flashing 4.0.4 its pretty much a must to also install custom kernel to avoid possible silly bricks by wiping data.
So simply flash rom via odin and then do same for custom kernel like Siyah and then reboot into kernel and wipe data/factory reset and you're off
TheATHEiST said:
Well since your flashing 4.0.4 its pretty much a must to also install custom kernel to avoid possible silly bricks by wiping data.
So simply flash rom via odin and then do same for custom kernel like Siyah and then reboot into kernel and wipe data/factory reset and you're off
Click to expand...
Click to collapse
Sane chip, he's already off.
gastonw said:
Sane chip, he's already off.
Click to expand...
Click to collapse
Yeah didnt notice OP was on sane chip. Was speaking more in general though anyway.
TheATHEiST said:
Yeah didnt notice OP was on sane chip. Was speaking more in general though anyway.
Click to expand...
Click to collapse
Sometimes I dream my phone is bricked or scracthed. This Q&A thing might be messing with my head.
gastonw said:
Sometimes I dream my phone is bricked or scracthed. This Q&A thing might be messing with my head.
Click to expand...
Click to collapse
:laugh:
gastonw said:
Sometimes I dream my phone is bricked or scracthed. This Q&A thing might be messing with my head.
Click to expand...
Click to collapse
I know what you mean. I haven't even done this procedure yet and I'm dreaming of bricked phones/ corrupted IMEIs etc.
Probably a bit melodramatic I know.
It did occur to me that instead of flashing stock 4.1.2 from stock 4.0.4, it may be better to flash the Siyah kernel to my current 4.0.4. This way I can back up efs, do a nandroid and titanium - before embarking on fully fledged ROM flashing etc.
What do you think?
dimbo33 said:
I know what you mean. I haven't even done this procedure yet and I'm dreaming of bricked phones/ corrupted IMEIs etc.
Probably a bit melodramatic I know.
It did occur to me that instead of flashing stock 4.1.2 from stock 4.0.4, it may be better to flash the Siyah kernel to my current 4.0.4. This way I can back up efs, do a nandroid and titanium - before embarking on fully fledged ROM flashing etc.
What do you think?
Click to expand...
Click to collapse
Well...the beauty of flashing is that you can do both Stock & Custom. You can also Dual Boot if you want.
My advice is this:
1) Always Back up EFS folder (HC-ktool is a good app for that).
2) Get Titanium Back up Pro.
3) Flash CMW or Flash siyah, it can't never hurt (well, if you go JB leak, might wanna try usin stock kernel first and the flash a custom kernel)
4) Get mobile odin Pro (so you can flash as many stock ROMs as you like, with the chance of getting bricked or soft bricked close to none + you'll always be rooted)
5) Read about ROMs features. You are the only person in the world that knows what ROM will fit your needs.
6) Start flashing.
7) If you are scared about bricks, read the bricked device's threads. That way you will know what NOT to do.
In my experience, I went jb and never came back.
Now, you really dream about IMEI, lol, that's something
I haven't flashed 4.1.2 yet. I was going to do it last night but realised I had forgotten my GPS active and the battery went flat. I took this as an omen and aborted the mission.
I've been reading around the subject for days. There seem to be so many people that encounter problems that it is difficult to have any perspective. The myriad of users that flash stuff via odin without any trouble obviously don't post that it went well - so you read 10 problem posts and never see the other thousand flashes that went without a hitch.
I also have read on xda that the leaked JB 4.1.2 is somewhat buggy. I'm not sure how buggy, but the lock screen freeze would be annoying in practice.
Again the carrot of official jb has been dangled before us - supposedly in February now.......Given that this will probably be the last official release for the S2 I might hang on and wait for it - then embark on the routing/custom ROM journey.
dimbo33 said:
I haven't flashed 4.1.2 yet. I was going to do it last night but realised I had forgotten my GPS active and the battery went flat. I took this as an omen and aborted the mission.
I've been reading around the subject for days. There seem to be so many people that encounter problems that it is difficult to have any perspective. The myriad of users that flash stuff via odin without any trouble obviously don't post that it went well - so you read 10 problem posts and never see the other thousand flashes that went without a hitch.
I also have read on xda that the leaked JB 4.1.2 is somewhat buggy. I'm not sure how buggy, but the lock screen freeze would be annoying in practice.
Again the carrot of official jb has been dangled before us - supposedly in February now.......Given that this will probably be the last official release for the S2 I might hang on and wait for it - then embark on the routing/custom ROM journey.
Click to expand...
Click to collapse
Well, you read 10 problems while flashing, right now we got 50.000 users going thru these threads, here, at XDA.
Jb is buggy, it's a leak, but too buggy? don't think so.
As for the bugs, we got plenty of people coming up with work arounds & fixes every day. In my case, I only have the lockscreen issue (let's face it, it doesn't always happens, like maybe 1 time a day and it's only for 3 seconds till the capacitive buttons light up. If you lock the screen and re unlock it with the power button, you're off. For me, it's not even an issue). I don't even remember when was the last time I had this issue, maybe 3 days ago now that I think about it.
Where's flashing, there's risk. TRUE. That's why I layed the Mobile Odin Pro option for you, that could be the best way to lose you flashing's fright.
BTW: we are getting the lime pie update, SII Plus was released just now
gastonw said:
Where's flashing, there's risk. TRUE. That's why I layed the Mobile Odin Pro option for you, that could be the best way to lose you flashing's fright.
Click to expand...
Click to collapse
I have had a look at mobile Odin Pro and I like the look of it. Thanks for the tip. To use it I need to root the S2.
I have seen this guide http://forum.xda-developers.com/showthread.php?t=1501719 - this seems simple. I could also flash the Siyah kernel via Odin. Which root method would you recommend? The first method seems to avoid the triangle issue - although this is not a big deal.
With a routed device I can backup efs etc before flashing anything else. Does the efs folder contain the simlock status?
Also, as you know I have been looking at the leaked jb, but perhaps it might be worth looking at neatrom 4.1.2 (or similar) instead?
I seem to get the impression that mobile Odin Pro is a safe method. Is it safer than using PC Odin?
Related
I got a brand new BELL SGS2HDLTE yesterday model SGH757 and flashed CWM, everything was ok. This morning I decided I wanted to flash a samsung based ICS rom specifically this on here (http://forum.xda-developers.com/showthread.php?t=1569686). I booted into CWM Recovery, wipe/factory reset wiped cache and dalvik cache and installed the ROM. The setup show up and eventually said complete please reboot. I pressed reboot and the phone turned off and refuses to turn on anymore. The battery was at 44% when I was flashing, even if I plug the phone in via usb nothing happens. I've tried taking out the battery for a few second and putting it back in but nothing happens. I can't boot into CWM or DL mode either, its as if the phone is completely dead... Can someone tell me whats going on here??? I never had an issue like this on my old SGS.. Thanks in advance!
I'm guessing the infamous brick bug is responsible.
What was your configuration before flashing the new ROM?
What ROM and kernel?
Sent from a GT-I9100 having a mind of its own
TechnicallyImpaired said:
I got a brand new BELL SGS2HDLTE yesterday model SGH757 and flashed CWM, everything was ok. This morning I decided I wanted to flash a samsung based ICS rom specifically this on here (http://forum.xda-developers.com/showthread.php?t=1569686). I booted into CWM Recovery, wipe/factory reset wiped cache and dalvik cache and installed the ROM. The setup show up and eventually said complete please reboot. I pressed reboot and the phone turned off and refuses to turn on anymore. The battery was at 44% when I was flashing, even if I plug the phone in via usb nothing happens. I've tried taking out the battery for a few second and putting it back in but nothing happens. I can't boot into CWM or DL mode either, its as if the phone is completely dead... Can someone tell me whats going on here??? I never had an issue like this on my old SGS.. Thanks in advance!
Click to expand...
Click to collapse
I'm sorry bro but you might have suffered from the infamous super brick bug and your inability to read.
Solution:
Package the phone and send it to Samsung repair center
Swyped from Samsung Galaxy SII
TechnicallyImpaired said:
I got a brand new BELL SGS2HDLTE yesterday model SGH757 and flashed CWM, everything was ok. This morning I decided I wanted to flash a samsung based ICS rom specifically this on here (http://forum.xda-developers.com/showthread.php?t=1569686). I booted into CWM Recovery, wipe/factory reset wiped cache and dalvik cache and installed the ROM. The setup show up and eventually said complete please reboot. I pressed reboot and the phone turned off and refuses to turn on anymore. The battery was at 44% when I was flashing, even if I plug the phone in via usb nothing happens. I've tried taking out the battery for a few second and putting it back in but nothing happens. I can't boot into CWM or DL mode either, its as if the phone is completely dead... Can someone tell me whats going on here??? I never had an issue like this on my old SGS.. Thanks in advance!
Click to expand...
Click to collapse
No offense to the two responders above me, but you can ignore them.
The problem is that you attempted to flash a firmware not meant for your phone.
You yourself said you have an SGH-I757. Well, that ICS ROM you linked that you tried to flash is for the GT-i9100. The two models have different hardware, so firmwares, kernels, and ROMs are NOT compatible between them.
This probably screwed up the bootloader. Your only course of action at this point will probably be either JTag repair, or sending it to Samsung for repair.
ctomgee said:
No offense to the two responders above me, but you can ignore them.
The problem is that you attempted to flash a firmware not meant for your phone.
You yourself said you have an SGH-I757. Well, that ICS ROM you linked that you tried to flash is for the GT-i9100. The two models have different hardware, so firmwares, kernels, and ROMs are NOT compatible between them.
This probably screwed up the bootloader. Your only course of action at this point will probably be either JTag repair, or sending it to Samsung for repair.
Click to expand...
Click to collapse
Thanks for not being a douche bag in your response, much appreciated. Thanks for the info BTW, I just got myself a new one and I'll be more careful now. My biggest annoyance with native ICS on this phone is one is looks like gingerbread and two it comes with a tonne of bloatware that you can't remove without rooting ect. At this point should I flash CWM again since it installed successfully last time, root, and use that as a method to remove the unwanted bloatware. I'm so hesitant to flash this phone now, it seems it was much ease on my SGS1.
TechnicallyImpaired said:
Thanks for not being a douche bag in your response, much appreciated. Thanks for the info BTW, I just got myself a new one and I'll be more careful now. My biggest annoyance with native ICS on this phone is one is looks like gingerbread and two it comes with a tonne of bloatware that you can't remove without rooting ect. At this point should I flash CWM again since it installed successfully last time, root, and use that as a method to remove the unwanted bloatware. I'm so hesitant to flash this phone now, it seems it was much ease on my SGS1.
Click to expand...
Click to collapse
Just make sure you stick to flashing things meant for your model. Those things compatible with your device will be clearly labeled with the model number.
Problem is the SGH-i757 doesn't have its own forum, so stuff for it gets posted in here.
ctomgee said:
Just make sure you stick to flashing things meant for your model. Those things compatible with your device will be clearly labeled with the model number.
Problem is the SGH-i757 doesn't have its own forum, so stuff for it gets posted in here.
Click to expand...
Click to collapse
Yup, I've found a few but I also have a few questions maybe you can help me with. According to this thread ( http://forum.xda-developers.com/showthread.php?t=1756242) only stock ICS v 4.0.4 is effected by this superbrick. The SGS2 I hardbricked earlier today was updated to this version via keys to 4.0.4 before installing the custom ROM. So provided I stick to ROMS such as lets say the one here (http://forum.xda-developers.com/showthread.php?t=1740188) and avoid upgrading to 4.0.4 I should be able to CWM + Flash + Root correct? I should also be able to do the standard factory reset / wipe cache / wipe dalvik? I also used the eMMC Brickbug Check app in the first post I liked under how to AVOID the superbrick and it came up saying my chip was sane. Thanks in advance and also I pressed the thank you button
TechnicallyImpaired said:
Yup, I've found a few but I also have a few questions maybe you can help me with. According to this thread ( http://forum.xda-developers.com/showthread.php?t=1756242) only stock ICS v 4.0.4 is effected by this superbrick. The SGS2 I hardbricked earlier today was updated to this version via keys to 4.0.4 before installing the custom ROM. So provided I stick to ROMS such as lets say the one here (http://forum.xda-developers.com/showthread.php?t=1740188) and avoid upgrading to 4.0.4 I should be able to CWM + Flash + Root correct? I should also be able to do the standard factory reset / wipe cache / wipe dalvik? I also used the eMMC Brickbug Check app in the first post I liked under how to AVOID the superbrick and it came up saying my chip was sane. Thanks in advance and also I pressed the thank you button
Click to expand...
Click to collapse
The brick bug may not affect you at all. The most common Galaxy S2 affected is the i9100, which we have established is NOT your device. And you already used the app that said your chip is "sane", so it's confirmed you don't have to worry about it.
Again, you bricked the device by flashing a ROM meant for a different device. Had nothing to do with the brick bug.
ctomgee said:
The brick bug may not affect you at all. The most common Galaxy S2 affected is the i9100, which we have established is NOT your device. And you already used the app that said your chip is "sane", so it's confirmed you don't have to worry about it.
Again, you bricked the device by flashing a ROM meant for a different device. Had nothing to do with the brick bug.
Click to expand...
Click to collapse
Thanks, I wasn't aware flashing a rom not meant for your device can cause a hard brick to the point where you cant turn anything on and no buttons are responsive ect. Thanks for the help.
New here. (also apologies for probable duplicate topic)
I've rooted a phone in the past with no problem. This time round was with an S2, and I flashed an insecure kernel on it, got a green pass on Odin however it's now stuck on the boot screen with the yellow triangle.
I can access recovery mode and download mode but it will never boot properly, always stuck on the yellow triangle. What's the best course of action from here?
Need a lot of help with this guys as I'd rather not have a bricked phone ><
ikradex said:
New here. (also apologies for probable duplicate topic)
I've rooted a phone in the past with no problem. This time round was with an S2, and I flashed an insecure kernel on it, got a green pass on Odin however it's now stuck on the boot screen with the yellow triangle.
I can access recovery mode and download mode but it will never boot properly, always stuck on the yellow triangle. What's the best course of action from here?
Need a lot of help with this guys as I'd rather not have a bricked phone ><
Click to expand...
Click to collapse
Seriously dude? Use some common sense please and give relevant information on what you have. What model/variant do you have, rom are you on, what kernel have you flashed?
How do you expect anybody to be able to help you if you dont give such basic info???
Are you sure the kernel supports the rom/version you have installed?
ikradex said:
New here. (also apologies for probable duplicate topic)
I've rooted a phone in the past with no problem. This time round was with an S2, and I flashed an insecure kernel on it, got a green pass on Odin however it's now stuck on the boot screen with the yellow triangle.
I can access recovery mode and download mode but it will never boot properly, always stuck on the yellow triangle. What's the best course of action from here?
Need a lot of help with this guys as I'd rather not have a bricked phone ><
Click to expand...
Click to collapse
Maybe because you wiped all data....so...there's no ROM to boot up to.
Try flashing one via Odin
gastonw said:
Maybe because you wiped all data....so...there's no ROM to boot up to.
Try flashing one via Odin
Click to expand...
Click to collapse
Wiping data doesnt wipe rom , It just wipes appdata, ie settings etc. All that happens is a factory reset so when you next boot its back to default. For example you would need to re-enter google account and re-install apss either manually or from a backup.
You can only wipe rom by formatting system partition.
TheATHEiST said:
Wiping data doesnt wipe rom , It just wipes appdata, ie settings etc. All that happens is a factory reset so when you next boot its back to default. For example you would need to re-enter google account and re-install apss either manually or from a backup.
You can only wipe rom by formatting system partition.
Click to expand...
Click to collapse
Thought you had me in ignore.
So there's no way you can wipe your OS via recovery? Good to know that, it's like ROM over ROM then. The new one clears the old one.
gastonw said:
Thought you had me in ignore.
So there's no way you can wipe your OS via recovery? Good to know that, it's like ROM over ROM then. The new one clears the old one.
Click to expand...
Click to collapse
I did have you on ignore but I still see little boxes saying this comment has been ignored etc which was actually more annoying so I removed ignore.
Yes you can wipe OS via recovery but only by formatting system/deleting partition etc. All the "wipe" options do is remove files that have been created by rom like app settings/cache etc.
Your confusion was probably also the reason why you made a big thing in a previous topic about you trying to avoid wiping data, because you thought it wiped rom? :silly:
Wiping data/factory reset in cwm is one of the best ways to get rid of system issues, Its basically like doing a clean install of Windows on a PC. After you have wiped you can simply restore your needed apps from a backup using Titanium Backup. Other things like sms/mms etc can be also backed up easily and contacts will be synced via Google account.
TheATHEiST said:
I did have you on ignore but I still see little boxes saying this comment has been ignored etc which was actually more annoying so I removed ignore.
Yes you can wipe OS via recovery but only by formatting system/deleting partition etc. All the "wipe" options do is remove files that have been created by rom like app settings/cache etc.
Your confusion was probably also the reason why you made a big thing in a previous topic about you trying to avoid wiping data, because you thought it wiped rom? :silly:
Wiping data/factory reset in cwm is one of the best ways to get rid of system issues, Its basically like doing a clean install of Windows on a PC. After you have wiped you can simply restore your needed apps from a backup using Titanium Backup. Other things like sms/mms etc can be also backed up easily and contacts will be synced via Google account.
Click to expand...
Click to collapse
hum...okay.
I actually know what Factory Reset does, I mean..."factory"..."reset", kinda......gives it away.
And yes, it made sense to me that you could wipe the ROM you are on before installing a new one, just like the format c:/s days in win98.
You learn something every day, speaking of which, how come no one recommends noobs to root their device with exynos abuse? It's because they're noobs and wouldn't be able to handle/understand the exploit?
I still don't do factory resets because I don't need to, and I avoid needing to perform it.
TheATHEiST said:
Seriously dude? Use some common sense please and give relevant information on what you have. What model/variant do you have, rom are you on, what kernel have you flashed?
How do you expect anybody to be able to help you if you dont give such basic info???
Are you sure the kernel supports the rom/version you have installed?
Click to expand...
Click to collapse
Thanks for the reply Figured if someone was willing to help me I'd give them the information they wanted.
Have Samsung Galaxy S II (GT-I9100) (couldn't tell you what "variant" it is). I was following this guide. It told me to get an insecure kernel from here. The guide said it didn't really matter which kernel I picked so I picked the first one (GT-I9100_BGKF5_insecure) and used Odin to flash it. Got a green pass and the phone began reboot but it's now stuck on the yellow triangle (the warning message that you've flashed an insecure kernel).
I couldn't tell whether there would be compatibility issues as the thread just seems to be one big list of kernels and nothing else. AFAIK the phone was running ICS.
Looking at the replies, I keep seeing factory reset. Is that a liable option to restore my phone back to its original state. I don't care as long the phone works again. If not can someone run through how to fix my predicament I heard if I can access download and recovery mode I should be able to fix it.
ikradex said:
Thanks for the reply Figured if someone was willing to help me I'd give them the information they wanted.
Have Samsung Galaxy S II (GT-I9100) (couldn't tell you what "variant" it is). I was following this guide. It told me to get an insecure kernel from here. The guide said it didn't really matter which kernel I picked so I picked the first one (GT-I9100_BGKF5_insecure) and used Odin to flash it. Got a green pass and the phone began reboot but it's now stuck on the yellow triangle (the warning message that you've flashed an insecure kernel).
I couldn't tell whether there would be compatibility issues as the thread just seems to be one big list of kernels and nothing else. AFAIK the phone was running ICS.
Looking at the replies, I keep seeing factory reset. Is that a liable option to restore my phone back to its original state. I don't care as long the phone works again. If not can someone run through how to fix my predicament I heard if I can access download and recovery mode I should be able to fix it.
Click to expand...
Click to collapse
Of course, you're not bricked yet.
Before trying your back up, why don't you flash a stock ROM via odin and take a long breath?
This is JB leak.
These are ICS, look for 4.0.3 unbranded.
gastonw said:
Of course, you're not bricked yet.
Before trying your back up, why don't you flash a stock ROM via odin and take a long breath?
This is JB leak.
These are ICS, look for 4.0.3 unbranded.
Click to expand...
Click to collapse
I know this is leading onto another thread but my phone now is having trouble connecting to my computer. Keep getting "USB not recognized" error. Installed/Uninstalled kies & drivers then installed drivers again alone and still won't recognize it
Tried another usb port? another pc/laptop? sure kies is not running in background? reinstalled kies?
Don't worry, your pc WILL see your device.
Sent from the little guy
Hello first time rooting this phone. Its a SGH-I777. I used the guide from galaxys2root.com/. At first it didnt work because my computer didnt recongnize my phone. I tried a different computer and it seemed successful until it rebooted. When the phone rebooted it did nothing but stay on the first screen. I still have the ability to get into Odin mode(download mode), but that is it. When i put the phone in download mode and use Odin it allows me to download the "zimage" but after rebooting it is the same exact thing. I have tried the one click root, one click factory restore. Tried restoring it on Kies. and nothing work took it to a store and the guy said he tried but it would stop in the middle of the download the only option i had with him was purchasing a new mother board for $80. Does anyone have a solution that can help me fix my phone.
Before i attempted to root it, it had OS 2.3.6 with kernal 2.6.35.7.
Go to the development section and read the stickies. There you will find stock rooted packages you can flash with Odin.
Sent from my SGH-I777 using xda premium
@jmula,
Enter recovery and perform a wipe data/factory reset. That may clear the failure to boot. If not you'll need to flash back to stock and start over.
The yellow trangle is a result of flashing a custom kernel using Odin or Heimdall, and is expected. You are not the first person having problems with the tools provided by GalaxyS2Root. In the future, I would recommend you avoid his site.
And... as suggested, read and study till you understand the basics. Then if you have questions, feel free to ask.
creepyncrawly said:
@jmula,
Enter recovery and perform a wipe data/factory reset. That may clear the failure to boot. If not you'll need to flash back to stock and start over.
The yellow trangle is a result of flashing a custom kernel using Odin or Heimdall, and is expected. You are not the first person having problems with the tools provided by GalaxyS2Root. In the future, I would recommend you avoid his site.
And... as suggested, read and study till you understand the basics. Then if you have questions, feel free to ask.
Click to expand...
Click to collapse
the only option that i have is to put the phone in download mode. when i try to download any kernel it reboots and does not go past the booting screen with the triangle.
jmula said:
the only option that i have is to put the phone in download mode. when i try to download any kernel it reboots and does not go past the booting screen with the triangle.
Click to expand...
Click to collapse
You should be able to enter recovery. Hold down all three buttons, vol+ vol- and pwr, continuously until the phone boots into recovery. It could take 10 or 15 seconds or more. If that is unsuccessful, then since you can enter download mode, you will need to flash back to stock, or stock plus root. That is not just a kernel, but the entire package. Please see the links in my sig for instructions.
The dropbox links in the download repository are temporarily suspended until probably Monday night or Tuesday as someone abused and over-downloaded. But the hotfile links still work.
creepyncrawly said:
You should be able to enter recovery. Hold down all three buttons, vol+ vol- and pwr, continuously until the phone boots into recovery. It could take 10 or 15 seconds or more. If that is unsuccessful, then since you can enter download mode, you will need to flash back to stock, or stock plus root. That is not just a kernel, but the entire package. Please see the links in my sig for instructions.
The dropbox links in the download repository are temporarily suspended until probably Monday night or Tuesday as someone abused and over-downloaded. But the hotfile links still work.
Click to expand...
Click to collapse
i Downloaded ''UCLE5 Stock ICS plus Root'' . i placed the phone in download mode started Odin and placed file in PDA. It starts but gets stuck at cache.img
jmula said:
i Downloaded ''UCLE5 Stock ICS plus Root'' . i placed the phone in download mode started Odin and placed file in PDA. It starts but gets stuck at cache.img
Click to expand...
Click to collapse
The next thing I would suggest is to try and flash the UCKH7 full stock package with bootloaders. However, as the dropbox links in the download repository are currently suspended, you will have to download it from SamFirmware. To be able to download, you will need to register for free if you havn't already. Search sgh-i777 in the upper right hand corner of the page, then download the I777UCKH7 version. Let us know if that will flash.
Ok it finally wokred after countless times of changing usb ports. I used the one click recovery. It restroed my phone to 2.3.4 i had 2.3.6. I tried to update by kies to 4.01 and it didnt work. Kies froze. The queestion is how do i safltey root the phone?
jmula said:
Ok it finally wokred after countless times of changing usb ports. I used the one click recovery. It restroed my phone to 2.3.4 i had 2.3.6. I tried to update by kies to 4.01 and it didnt work. Kies froze. The queestion is how do i safltey root the phone?
Click to expand...
Click to collapse
Flash a .tar version of a custom kernel with Odin. I always use an old siyah.tar, but that's just me. There are other methods floating around but that's the quickest and easiest for me. I think there's an old entropy dd.tar around somewhere too. But just flash it through Odin and you're good to go, assuming you flashed one for your version of android. If you just want to get into recovery to flash something this works as well.
There may be links to tar versions of the kernels in creepy's sig I don't remember offhand.
Ok since i do not want to brick my phone again where it is just stuck at the boot loop. I tried looking for ways to root and when i tried some of them my phone went back to the problem it had it the beginning. Should i just call it quits or do you guys have a guide?
jmula said:
Ok since i do not want to brick my phone again where it is just stuck at the boot loop. I tried looking for ways to root and when i tried some of them my phone went back to the problem it had it the beginning. Should i just call it quits or do you guys have a guide?
Click to expand...
Click to collapse
Give up???
I personally don't think flashing a kernel with odin is the best way to root. It increments the flash counter, for one thing, though I'm not sure how many people care about that anymore. I would suggest that you use the stock plus root package to root the phone with odin. See the links in my sig.
Guide... did someone say guide?
Feeling the pain....
creepyncrawly said:
@jmula,
Enter recovery and perform a wipe data/factory reset. That may clear the failure to boot. If not you'll need to flash back to stock and start over.
The yellow trangle is a result of flashing a custom kernel using Odin or Heimdall, and is expected. You are not the first person having problems with the tools provided by GalaxyS2Root. In the future, I would recommend you avoid his site.
And... as suggested, read and study till you understand the basics. Then if you have questions, feel free to ask.
Click to expand...
Click to collapse
First, to Creepy....you've been a great resource here and I read a lot of what you post and you got me out of the very jam being discussed here. I made the mistake of trying to root via the galaxys2root.com site (actually, I thought it was a different site...was redirected), got the i9100 screen and a boot loop...couldn't go anywhere. I came back here and found resources eventually unrooting my phone all the way back to 2.3.4, then moved to 2.3.6, then the stock android 4.0.3 which updated to 4.0.4.
But I still want to root (4.0.4 shuts itself down A LOT...more than 4.0.3) and I have a Galaxy note 10.1 with JB 4.1.2 and I LOVE IT! I feel on a mission to get rooted and try out some of the JB roms I see talked about here, but can't seem to find the best way to root. I've heard exynosabuse referenced here (no links to it though) and I don't want to use the wrong one and mess up my phone. I've been reading for weeks here and there's obviously a lot of great material, but I'm not sure which material is critical to understand, and which is "nice to know" but might not even apply, and which material isn't even right. Very frustrating.
Judi
judib said:
First, to Creepy....you've been a great resource here and I read a lot of what you post and you got me out of the very jam being discussed here. I made the mistake of trying to root via the galaxys2root.com site (actually, I thought it was a different site...was redirected), got the i9100 screen and a boot loop...couldn't go anywhere. I came back here and found resources eventually unrooting my phone all the way back to 2.3.4, then moved to 2.3.6, then the stock android 4.0.3 which updated to 4.0.4.
But I still want to root (4.0.4 shuts itself down A LOT...more than 4.0.3) and I have a Galaxy note 10.1 with JB 4.1.2 and I LOVE IT! I feel on a mission to get rooted and try out some of the JB roms I see talked about here, but can't seem to find the best way to root. I've heard exynosabuse referenced here (no links to it though) and I don't want to use the wrong one and mess up my phone. I've been reading for weeks here and there's obviously a lot of great material, but I'm not sure which material is critical to understand, and which is "nice to know" but might not even apply, and which material isn't even right. Very frustrating.
Judi
Click to expand...
Click to collapse
The ExynosAbuse application is the only practical way to root 4.0.4 without changing base. You can download it as an attachment in the OP of the developer's thread, but read through the thread first to understand its limitations and risks.
Alternatively, you could flash 4.0.3 plus root from the development forum. If you choose that route, please read the thread to understand how to install a custom kernel, which is recommended whether you plan to install a custom firmware or not. The custom kernel will contain ClockworkMod Recovery so you can flash the firmware of your choice if you wish.
There are really several routes you could choose. All of them work. Another would be to flash back to stock Gingerbread plus root. For that see my guide How to Flash Custom Binaries Without Ever Incrementing the Flash counter!! (link in sig)
Hmmmmm..
Well, I see that their are many, more experienced than me following this thread and my following comment is not meant to jump on the knowledge train here, but............... I had the same event happen as the orig poster earlier today. I had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII, What I did was go into recovery ,cleared the Dalvik cache and that is all I cleared. Then I re-installed the RR Rom .rar, which I keep on my SD, over everything and rebooted, it came back as it was 4 mins before . All I did after, was do a system restore(only) using Titanium BU. So when I see all the "clear and restore this and that" I started to doubt some of the more experienced than I. My 2 cents is, that, if one does not know EXACTLY ,how to correct an issue,leave it for our more knowledgeable brothers and sisters.
If I am wrong ,please except my appology.
b0bb said:
Well, I see that their are many, more experienced than me following this thread and my following comment is not meant to jump on the knowledge train here, but............... I had the same event happen as the orig poster earlier today. I had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII, What I did was go into recovery ,cleared the Dalvik cache and that is all I cleared. Then I re-installed the RR Rom .rar, which I keep on my SD, over everything and rebooted, it came back as it was 4 mins before . All I did after, was do a system restore(only) using Titanium BU. So when I see all the "clear and restore this and that" I started to doubt some of the more experienced than I. My 2 cents is, that, if one does not know EXACTLY ,how to correct an issue,leave it for our more knowledgeable brothers and sisters.
If I am wrong ,please except my appology.
Click to expand...
Click to collapse
I don't know what you're trying to get across here. Yes, restoring a backup nandroid works. Yes, you can try wiping cache and dalvik to see if it fixes an issue. Yes you can restore apps via titanium backup. All these things are indeed true.
Phalanx7621 said:
I don't know what you're trying to get across here. Yes, restoring a backup nandroid works. Yes, you can try wiping cache and dalvik to see if it fixes an issue. Yes you can restore apps via titanium backup. All these things are indeed true.
Click to expand...
Click to collapse
Well if you did not fully grasp what I was trying to get across,you seemed to get it correct with your statement.
b0bb said:
Well if you did not fully grasp what I was trying to get across,you seemed to get it correct with your statement.
Click to expand...
Click to collapse
And yet you say, "All I did after, was do a system restore(only) using Titanium BU." This may have worked for you, but this is an absolute recipe for disaster, and should not be given as a recommendation.
And further, from what you say, you did not have the "same event happen as the orig poster." Instead you "had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII." This is by far not the same as trying to root with a tool from GalaxyS2Root.
creepyncrawly said:
And yet you say, "All I did after, was do a system restore(only) using Titanium BU." This may have worked for you, but this is an absolute recipe for disaster, and should not be given as a recommendation.
And further, from what you say, you did not have the "same event happen as the orig poster." Instead you "had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII." This is by far not the same as trying to root with a tool from GalaxyS2Root.
Click to expand...
Click to collapse
Hey Bro, I think you think that I am challenging you, trust me I am not and I thank you for correcting me and putting me in my place, which is a bit phone techie challenged, I'll stick to building submarines. Thanks for what you do here.
b0bb said:
Hey Bro, I think you think that I am challenging you, trust me I am not and I thank you for correcting me and putting me in my place, which is a bit phone techie challenged, I'll stick to building submarines. Thanks for what you do here.
Click to expand...
Click to collapse
Not at all. I want people to help others here. I want you to help other here as well. But it is important to post only accurate information. Inaccurate information can cause someone to do the wrong action. So I always correct misinformation.
Wow! I need some help. I've acquired a Samsung Galaxy Note (i717, I believe) that shows all the signs of being healthy (appearance, touch screen, etc.) but persistently slows down at the ATT opening splash screen, begins to load Android, dies and reboots. Whatever variant rooted ROM I received it with (sluggish and unreliable) I have written over and now I can't get any farther than the Android settings screen. Therefore I do not know the exact version nor can I begin to set it up (wifi, etc.).
That's the 'presenting problem', so let me explain what I've done to this point (about 25 hrs. worth!). I have reloaded latest version of CWM (runs great) and then Padawan JB . . . same symptoms. I have loaded the ATT JB and ICS via the latest Odin successfully . . . with same symptoms. I have loaded TWRP (touch screen is snappy and works as it should) and Padawan JB again . . . with same symptoms. I have wiped caches before, after, and in between till I'm blue in the face, each time with the same symptoms. Most recently I have done a hard reset to native/factory settings . . . with no change! I've tried to scour the XDA (and any other sites) trouble shooting articles and seem to have come to a dead end.
Here's a couple things that I'm wondering: because I can't get deep enough into Android to check out the model number, could the phone be something other than an ATT model? At the top of the front face it simply says 'Samsung', not ATT at top and Samsung at bottom like my previous ATT Note. Right after boot I persistently get an ATT splash screen which would lead me to believe that it is ATT. Is there some other way to find model, say in TWRP? Do I need a phone specific version of Android? Second, everything seems to be working fine physically (i.e., no hardware problems). Could this thing have gotten a virus in an earlier life that's preventing the ROM from working right? I've not been able to get far enough to register it with my cell provider (second party, not ATT). Must you be up and running with the cell service to correctly load and use the ROM (wouldn't think so)? And if so, how without Android working? I've been using and playing with computers for 25 years, but I'm fairly new to the Android system (but learning fast!) Any help would sure be appreciated. I'd really like to resurrect this baby. I loved my first Note (till it fell off the car and disappeared).
pstrulm said:
Wow! I need some help. I've acquired a Samsung Galaxy Note (i717, I believe) that shows all the signs of being healthy (appearance, touch screen, etc.) but persistently slows down at the ATT opening splash screen, begins to load Android, dies and reboots. Whatever variant rooted ROM I received it with (sluggish and unreliable) I have written over and now I can't get any farther than the Android settings screen. Therefore I do not know the exact version nor can I begin to set it up (wifi, etc.).
That's the 'presenting problem', so let me explain what I've done to this point (about 25 hrs. worth!). I have reloaded latest version of CWM (runs great) and then Padawan JB . . . same symptoms. I have loaded the ATT JB and ICS via the latest Odin successfully . . . with same symptoms. I have loaded TWRP (touch screen is snappy and works as it should) and Padawan JB again . . . with same symptoms. I have wiped caches before, after, and in between till I'm blue in the face, each time with the same symptoms. Most recently I have done a hard reset to native/factory settings . . . with no change! I've tried to scour the XDA (and any other sites) trouble shooting articles and seem to have come to a dead end.
Here's a couple things that I'm wondering: because I can't get deep enough into Android to check out the model number, could the phone be something other than an ATT model? At the top of the front face it simply says 'Samsung', not ATT at top and Samsung at bottom like my previous ATT Note. Right after boot I persistently get an ATT splash screen which would lead me to believe that it is ATT. Is there some other way to find model, say in TWRP? Do I need a phone specific version of Android? Second, everything seems to be working fine physically (i.e., no hardware problems). Could this thing have gotten a virus in an earlier life that's preventing the ROM from working right? I've not been able to get far enough to register it with my cell provider (second party, not ATT). Must you be up and running with the cell service to correctly load and use the ROM (wouldn't think so)? And if so, how without Android working? I've been using and playing with computers for 25 years, but I'm fairly new to the Android system (but learning fast!) Any help would sure be appreciated. I'd really like to resurrect this baby. I loved my first Note (till it fell off the car and disappeared).
Click to expand...
Click to collapse
Well, if you keep flashing an AT&T based rom, then yes, you will get an AT&T boot animation simply because it's part of the rom you are flashing.
You said "you think" you have an I717, did you take the battery off and physically look at the sticker beneath it to see the model?
Try TWRP, go to WIPE, and WIPE everything, which means checking every checkbox. Then flash a stock rom with a fresh phone (no data, nothing at all)
You said you did CWM->Padawan.. these are two totally different roms, so you should always do a factory reset whenever flashing two totally different roms.
You can't just rely on the Android->settings to see the info since roms overwrite these stuff in build.prop so if you flash a wrong rom, wrong info will show up.
Here's my advice:
1. Flash TWRP
2. Wipe in TWRP, check every checkbox
3. Flash a stock i717 rom
4. Reboot
If that doesn't work, either hardware is bad or your phone isn't for the I717 roms.
Edit:
Question, have you ever come to a point that the phone boots successfuly at all? You did mention CM works great. But you can't go from CWM->TW Based rom without factory reset in between.
fbauto1 said:
Well, if you keep flashing an AT&T based rom, then yes, you will get an AT&T boot animation simply because it's part of the rom you are flashing.
You said "you think" you have an I717, did you take the battery off and physically look at the sticker beneath it to see the model?
Try TWRP, go to WIPE, and WIPE everything, which means checking every checkbox. Then flash a stock rom with a fresh phone (no data, nothing at all)
You said you did CWM->Padawan.. these are two totally different roms, so you should always do a factory reset whenever flashing two totally different roms.
You can't just rely on the Android->settings to see the info since roms overwrite these stuff in build.prop so if you flash a wrong rom, wrong info will show up.
Here's my advice:
1. Flash TWRP
2. Wipe in TWRP, check every checkbox
3. Flash a stock i717 rom
4. Reboot
If that doesn't work, either hardware is bad or your phone isn't for the I717 roms.
Edit:
Question, have you ever come to a point that the phone boots successfuly at all? You did mention CM works great. But you can't go from CWM->TW Based rom without factory
I would reflash cwm thru odin after that I would flash the latest TWRP 2.5. Then you can flash whatever. If padawan is givin u problems try something else like AOSP or AOKP. Padawan is TW based. JaimeD builds are pretty sweet.
sent from my GalaxySuperNote running OC Padawan JB
Click to expand...
Click to collapse
androidmechanic said:
fbauto1 said:
Well, if you keep flashing an AT&T based rom, then yes, you will get an AT&T boot animation simply because it's part of the rom you are flashing.
You said "you think" you have an I717, did you take the battery off and physically look at the sticker beneath it to see the model?
Try TWRP, go to WIPE, and WIPE everything, which means checking every checkbox. Then flash a stock rom with a fresh phone (no data, nothing at all)
You said you did CWM->Padawan.. these are two totally different roms, so you should always do a factory reset whenever flashing two totally different roms.
You can't just rely on the Android->settings to see the info since roms overwrite these stuff in build.prop so if you flash a wrong rom, wrong info will show up.
Here's my advice:
1. Flash TWRP
2. Wipe in TWRP, check every checkbox
3. Flash a stock i717 rom
4. Reboot
If that doesn't work, either hardware is bad or your phone isn't for the I717 roms.
Edit:
Question, have you ever come to a point that the phone boots successfuly at all? You did mention CM works great. But you can't go from CWM->TW Based rom without factory
I would reflash cwm thru odin after that I would flash the latest TWRP 2.5. Then you can flash whatever. If padawan is givin u problems try something else like AOSP or AOKP. Padawan is TW based. JaimeD builds are pretty sweet.
sent from my GalaxySuperNote running OC Padawan JB
Click to expand...
Click to collapse
If you want TWRP, flash TWRP. No need to flash CWM
Click to expand...
Click to collapse
AT&T Phones have a [logo}AT&T] on the top-center!!
But if you are in doubt, use kies to do a full recovery-restore [WILL ERASE EVERYTHING ON YOUR DEVICE].
See post #4 on this thread.
fbauto1 said:
androidmechanic said:
If you want TWRP, flash TWRP. No need to flash CWM
Click to expand...
Click to collapse
If you go thru Odin you would have cwm first. With the problems talked about, I would go back factory stock then re-root with Odin. Then thru cwm, flash twrp or whatever floats your boat.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
androidmechanic said:
If you go thru Odin you would have cwm first. With the problems talked about, I would go back factory stock then re-root with Odin. Then thru cwm, flash twrp or whatever floats your boat.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Nope. If you want TWRP, then flash TWRP via Odin. No need to go through CWM first. You can flash TWRP via Odin, you know that, right?
fbauto1 said:
Nope. If you want TWRP, then flash TWRP via Odin. No need to go through CWM first. You can flash TWRP via Odin, you know that, right?
Click to expand...
Click to collapse
No I didn't know that. All of the Odin programs that I dealt with flash cwm. Than for the Intel tho. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
fbauto1 said:
Nope. If you want TWRP, then flash TWRP via Odin. No need to go through CWM first. You can flash TWRP via Odin, you know that, right?
Click to expand...
Click to collapse
androidmechanic said:
No I didn't know that. All of the Odin programs that I dealt with flash cwm. Than for the Intel tho. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
you are both actually correct, however, I am looking at PSTRULM's stats. if he is anything like me when I started, the more simple and less complication involved in the process, the more he may understand.
ANDROIDMECHANIC is stating the most basic and beginner way to do this and understand simply. after doing this a few times as I did, the basic mechanics of the process will become more fluent.
then he can make his own decisions as to methods which might be easier for him, without confusing.
I am sure you both are a huge help to everyone and I thank members such as yourself for your efforts. ME, I prefer baby steps, cause I know I can really EFF things up if I get confused
androidmechanic said:
No I didn't know that. All of the Odin programs that I dealt with flash cwm. Than for the Intel tho. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Just a reminder.. when flashing through Odin, make sure it's an ODIN-flashable tarball, i.e., you can't flash a recovery-type zip through Odin and vice versa.
Hello.
My SGS2 is softbricked. It hangs during boot, but I can boot into download mode and I can boot into recovery mode.
My phone has only been flashed with OTA method and firmware. Never rooted, never flashed manually.
It starts up showing the animation with some ray of lights surrounding "Samsung Galaxy S2 I9100" logo, then it goes into the centered "SAMSUNG" logo with the corona slightly flashing and here it just continues with this slightly corona-blinking (normally it would here do that a few seconds and then show the home screen). The phone gets quite hot (but not burning hot) after a few seconds and I can turn it of by holding the power button for about 5 seconds (no need to take out the battery).
The situation started by the phone shutting down due to low battery. Then I connected usb (which I though was connected in the other end, but it was not) for charging and I powered up the phone immediately. Not noticing that the usb cable had no power I actually booted the phone with very low battery and no power in the usb cable. Shortly after the home screen showed up with a battery low-message. The phone went off (the hard way I think).
After that I of course ensured to charge the phone for a while before I booted it again, but at that time when booting it hung (as described above)
I believe Iread somewhere, that most likely the system filesystem has been corrupted, so just overwriting it (that is flashing like an OS upgrade) I could restore the device just like the phone has just been upgraded. And during normal upgrade my phone is not wiped, so that is what I am expecting would be possible.
From
http://forum.xda-developers.com/showthread.php?t=1973233
and
http://forum.xda-developers.com/showthread.php?t=1188615
it sounds like I can flash withour loosing data as long as the new ROM is same (or newer) as the one already on the phone.
So I have downloaded I9100XWLSS_I9100OXXLS9_NEE.zip for my phone it contains a I9100XWLSS_I9100OXXLS9_I9100XXMS2_HOME.tar.md5 file which contains
boot.bin
cache.img
factoryfs.img
hidden.img
modem.bin
param.lfs
Sbl.bin
zImage
From http://forum.xda-developers.com/showthread.php?t=1456532 I get the impression that if I flash a .tar.md5 file that contains hidden.img and/or cache.img it will wipe all my data.
So I was wondering if it was possible to just create a tar file without hidden.img and cache.img and flash that, so my data is not wiped.
Any input is appreciated.
jarl-dk said:
My SGS2 is softbricked. It hangs during boot, but I can boot into download mode and I can boot into recovery mode.
From
http://forum.xda-developers.com/showthread.php?t=1973233
and
http://forum.xda-developers.com/showthread.php?t=1188615
it sounds like I can flash withour loosing data as long as the new ROM is same (or newer) as the one already on the phone.
So I have downloaded I9100XWLSS_I9100OXXLS9_NEE.zip for my phone it contains a I9100XWLSS_I9100OXXLS9_I9100XXMS2_HOME.tar.md5 file which contains
boot.bin
cache.img
factoryfs.img
hidden.img
modem.bin
param.lfs
Sbl.bin
zImage
From http://forum.xda-developers.com/showthread.php?t=1456532 I get the impression that if I flash a .tar.md5 file that contains hidden.img and/or cache.img it will wipe all my data.
So I was wondering if it was possible to just create a tar file without hidden.img and cache.img and flash that, so my data is not wiped.
Any input is appreciated.
Click to expand...
Click to collapse
Good to see someone who has actually read something!! :good:
I suggest you avoid messing with the firmwares for now. Is your phone rooted? How did the bootloop start?
There is no way to avoid factory reset.The only way to solve bootloop is by wiping data.No other way.You can flash a new ROM/firmware,but you will still have to do a factory reset because of old bootloop and new ROM.Sorry.
GamingDj said:
There is no way to avoid factory reset.The only way to solve bootloop is by wiping data.No other way.You can flash a new ROM/firmware,but you will still have to do a factory reset because of old bootloop and new ROM.Sorry.
Click to expand...
Click to collapse
I'm afraid I must agree.
@OP: But what you can do is make a nandroid backup before wiping. :good:
immortalneo said:
I'm afraid I must agree.
@OP: But what you can do is make a nandroid backup before wiping. :good:
Click to expand...
Click to collapse
good idea neo...and he can extract contacts or notes from nandroid...heard that people did this
immortalneo said:
I'm afraid I must agree.
@OP: But what you can do is make a nandroid backup before wiping. :good:
Click to expand...
Click to collapse
Can you give a short summary of how to do this (from the situation I am in),and some usefull links...
Jarl
much uirstaby
immortalneo said:
Good to see someone who has actually read something!! :good:
I suggest you avoid messing with the firmwares for now. Is your phone rooted? How did the bootloop start?
Click to expand...
Click to collapse
Thanks.
I must emphasize it is not a boot loop. It starts up showing the animation with some ray of lights surrounding "Samsung Galaxy S2 I9100" logo, then it goes into the centered "SAMSUNG" logo with the shadow slightly flashing and here it just continues with this slightly shadow-blinking (normally it would here do that a few seconds and then show the home screen). The phone gets quite hot after a efw seconds and I can turn it of by holding the power button for about 5 seconds (no need to take out the battery).
The situation started by the phone shutting down due to low battery. Then I connected usb (which I though was connected in the other end, but it was not) for charging and I powered up the phone immediately. Not noticing that the usb cable had no power I actually booted the phone with very low battery and no power in the usb cable. Shortly after the home screen showed up with a battery low-message. The phone went off (the hard way I think).
After that I of course ensured to charge the phone for a while before I booted it again, but at that time when booting it hung (as described above)
I believe Iread somewhere, that most likely the system filesystem has been corrupted, so just overwriting it (that is flashing like an OS upgrade) I could restore the device just like the phone has just been upgraded. And during normal upgrade my phone is not wiped, so that is what I am expecting would be possible.
Jarl
What firmware were you on? As in 4.1.2, 4.0.3, 4.0.4?
Basically what you need to do is flash a custom kernel via Odin in download mode. Let's take Siyah kernel for example (v5 for ICS. Pick which one is correct for your version, you can download them from gokhanmoral.com). If you're on JB, I suggest philz or apolo kernel. More on that in a sec.
Flash that kernel in Odin. Then, you can back up in CWM recovery. If you're on ICS, then you can factory reset and hopefully boot up. Once you've got your backup & booting, then you can extract data from the backup using titanium backup or CWM recovery.
If you're on JB, then you need to backup the /preload folder. Apolo does it automatically, in philz you need to tick the option before backing up. Same deal once you've backed up, factory reset then boot.
I hope that makes sense to you, I gave you all the info in one big hit. As you've done a lot of reading and attempted to help yourself before posting, I imagine you can make sense of that
Any issues, post up here, but for now, give that a go!
Sent from a galaxy far, far away
Hi.
Thank you for your time.
Hopper8 said:
What firmware were you on? As in 4.1.2, 4.0.3, 4.0.4?
Basically what you need to do is flash a custom kernel via Odin in download mode. Let's take Siyah kernel for example (v5 for ICS. Pick which one is correct for your version, you can download them from gokhanmoral.com). If you're on JB, I suggest philz or apolo kernel. More on that in a sec.
Click to expand...
Click to collapse
OK. I think I need help in two steps:
take a backup
make the phone usable again.
I am not sure exactly what firmware it had reached before the softbrick. It was definitely above 4.0, maybe even 4.1.x Does it matter a lot.
Lets focus on step 1 (taking a backup). I think that is what you are guiding me towards above, right?
So what shall I do when I am not 100% sure of the current firmware version on the phone?
Jarl
jarl-dk said:
Hi.
Thank you for your time.
OK. I think I need help in two steps:
take a backup
make the phone usable again.
I am not sure exactly what firmware it had reached before the softbrick. It was definitely above 4.0, maybe even 4.1.x Does it matter a lot.
Lets focus on step 1 (taking a backup). I think that is what you are guiding me towards above, right?
So what shall I do when I am not 100% sure of the current firmware version on the phone?
Jarl
Click to expand...
Click to collapse
Correct, if you want to keep the data then you need to make a backup. Unfortunately, if you don't know which firmware you were on previously, it's not easy. What I would suggest you do is to go onto YouTube, and look at videos of i9100's (that is what you have right?). You want a video of one with 4.0.3, one of 4.0.4, and one of 4.1.2. They all do look different, although 4.0.4 and 4.0.3 are reasonably similar.
Basically, if you can tell if you were on 4.0.x or 4.1.2 then we can go somewhere Until then, I'm not comfortable to tell you to flash.
Edit: and don't stress. Making the phone useable again is not hard to keep your data as well as make it useable again will take some effort on your part though.
Hopper8 said:
Correct, if you want to keep the data then you need to make a backup. Unfortunately, if you don't know which firmware you were on previously, it's not easy. What I would suggest you do is to go onto YouTube, and look at videos of i9100's (that is what you have right?). You want a video of one with 4.0.3, one of 4.0.4, and one of 4.1.2. They all do look different, although 4.0.4 and 4.0.3 are reasonably similar.
Basically, if you can tell if you were on 4.0.x or 4.1.2 then we can go somewhere Until then, I'm not comfortable to tell you to flash.
Edit: and don't stress. Making the phone useable again is not hard to keep your data as well as make it useable again will take some effort on your part though.
Click to expand...
Click to collapse
I will take a look at YouTube... However I do understand booting an incorrect version of Android can be dangerous to my data. However if I make 100% sure that I never boot the flashed android and only boot up in recovery mode to make a nandroid backup. Then it probably doesn't matter which (most likely incorrect) version of android is installed because will not boot it, I will only boot in recovery mode. After having made a nandroid backup I will go to step 2 (make it usable again) and making sure I don't boot up the incorrect android version along the path.
Would that be possible?
Jarl
GamingDj said:
There is no way to avoid factory reset.The only way to solve bootloop is by wiping data.No other way.You can flash a new ROM/firmware,but you will still have to do a factory reset because of old bootloop and new ROM.Sorry.
Click to expand...
Click to collapse
I just made an experiement with my Samsung Galaxy S 5.0 Tablet (YP-G70):
I flashed it with zImage and factoryfs.rfs (using Heimdall and making sure that repartition is not ticked)
In this situation there was no data loss (behaved like a standard OTA update), all contacts and apps still installed.
Why would this not be possible on GT-I9100 without wipe/factory reset. By just flashing the zImage and factoryfs.img from I9100XWLSS_OXXLS9_NEE_Nordic_Android_4.1.2.zip ? Notice I am not in a boot loop situation.
jarl-dk said:
I will take a look at YouTube... However I do understand booting an incorrect version of Android can be dangerous to my data. However if I make 100% sure that I never boot the flashed android and only boot up in recovery mode to make a nandroid backup. Then it probably doesn't matter which (most likely incorrect) version of android is installed because will not boot it, I will only boot in recovery mode. After having made a nandroid backup I will go to step 2 (make it usable again) and making sure I don't boot up the incorrect android version along the path.
Would that be possible?
Jarl
Click to expand...
Click to collapse
You are correct in saying that if you don't boot it, but only flash the kernel & immediately flash stock then you're OK. The thing I am unsure of, is making a nandroid whilst using an incompatible kernel.. I really don't know if it will work. My guess says it won't, but I don't know for sure. Can someone come in here? @MistahBungle @andrewwright @immortalneo @gastonw @keithross39
I still think you should try to figure out which version you were on before this, just so that you can have a safe bet of which kernel to flash.
---------- Post added at 09:59 PM ---------- Previous post was at 09:55 PM ----------
jarl-dk said:
I just made an experiemtn with my Samsungs Galaxy S 5.0 Tablet (YP-G70):
I flashed it with zImage and factoryfs.rfs (using Heimdall and making sure that repartition is not ticked)
In this situation there was no data loss (behaved like a standard OTA update), all contacts and apps still installed.
Why would this not be possible on GT-I9100 without wipe/factory reset. By just flashing the zImage and factoryfs.img from I9100XWLSS_OXXLS9_NEE_Nordic_Android_4.1.2.zip ? Notice I am not in a boot loop situation.
Click to expand...
Click to collapse
Good thinking. The thing is, on your tablet currently, it boots fine. It's not in the bootlooping scenario. Hence, doing an update which does not wipe will only update to a new version which won't be wiped, and hence will still be bootlooping. Of course you still could flash them (using Heimdall/ Odin, but I've never tried Heimdall personally) but I doubt that you'll boot up by that. It'll likely still get stuck at the boot logo.
Hopper8 said:
You are correct in saying that if you don't boot it, but only flash the kernel & immediately flash stock then you're OK. The thing I am unsure of, is making a nandroid whilst using an incompatible kernel.. I really don't know if it will work. My guess says it won't, but I don't know for sure. Can someone come in here? @MistahBungle @andrewwright @immortalneo @gastonw @keithross39
I still think you should try to figure out which version you were on before this, just so that you can have a safe bet of which kernel to flash.
---------- Post added at 09:59 PM ---------- Previous post was at 09:55 PM ----------
Good thinking. The thing is, on your tablet currently, it boots fine. It's not in the bootlooping scenario. Hence, doing an update which does not wipe will only update to a new version which won't be wiped, and hence will still be bootlooping. Of course you still could flash them (using Heimdall/ Odin, but I've never tried Heimdall personally) but I doubt that you'll boot up by that. It'll likely still get stuck at the boot logo.
Click to expand...
Click to collapse
OK, so what you are saying is that: I might just flash some of the files (all except cache.img and hidden.img) that will not wipe my phone, but as I understand you, it most likely wont solve my boot problem...
In that case can someone confirm that that flashing the files
boot.bin
factoryfs.img
modem.bin
param.lfs
Sbl.bin
zImage
without
cache.img
hidden.img
will not wipe my phone? Or are there more files that need to go down to the dangerous list?
Jarl
Hopper8 said:
The thing I am unsure of, is making a nandroid whilst using an incompatible kernel.. I really don't know if it will work. My guess says it won't, but I don't know for sure. Can someone come in here?
Click to expand...
Click to collapse
AFAIK, the nandroid backup will go just fine. If the kernel is incompatible, the nandroid would contain the incompatible kernel and would still bootloop after restoring. But since the OP isn't planning to restore the entire nandroid backup, I guess it doesn't matter.
I still suggest flashing the correct kernel to install CWM, just to be safe. Or if he is not on 4.0.4, he could use Philz temporary CWM (which can be flashed in stock recovery). :good:
immortalneo said:
AFAIK, the nandroid backup will go just fine. If the kernel is incompatible, the nandroid would contain the incompatible kernel and would still bootloop after restoring. But since the OP isn't planning to restore the entire nandroid backup, I guess it doesn't matter.
I still suggest flashing the correct kernel to install CWM, just to be safe. Or if he is not on 4.0.4, he could use Philz temporary CWM (which can be flashed in stock recovery). :good:
Click to expand...
Click to collapse
Ahh, the thing being that OP doesn't know what version he was previously on before all this :/
Hopper8 said:
Ahh, the thing being that OP doesn't know what version he was previously on before all this :/
Click to expand...
Click to collapse
I noticed that..
@OP: tried checking out some screenshots and videos and remembering how your firmware looked like?
A friend of mine gave me his S2 which was bootlooping. I showed him screenshots of the notification tray (and toggle buttons), and he was able to identify it as being GB. The tricky part was finding which version it was. He was sure it was fully stock and bought from Saudi Arabia. So what I did was to look up sammobile.com to see which version of GB was available in Saudi Arabia. And I found out it was 2.3.5! Problem solved. :good:
Hopper8 said:
Correct, if you want to keep the data then you need to make a backup. Unfortunately, if you don't know which firmware you were on previously, it's not easy. What I would suggest you do is to go onto YouTube, and look at videos of i9100's (that is what you have right?). You want a video of one with 4.0.3, one of 4.0.4, and one of 4.1.2. They all do look different, although 4.0.4 and 4.0.3 are reasonably similar.
Basically, if you can tell if you were on 4.0.x or 4.1.2 then we can go somewhere Until then, I'm not comfortable to tell you to flash.
Edit: and don't stress. Making the phone useable again is not hard to keep your data as well as make it useable again will take some effort on your part though.
Click to expand...
Click to collapse
OK. I am now pretty confident that I had/has android 4.1.2, because I remember I had features like SmartStay (which is new in 4.1 AFAIK). I also remember that I had the "Mobile Data" toggle button along the other quick state buttons like "GPS", "Sound", "WIFI", "Screen rotate". The "Mobile Data" state button was also new, but I cannot verify that is was nwe in 4.1.2 (maybe it was already in 4.0.x). Do you know of any other features that are nwe in 4.1.2 that can help me verify that is was a 4.1.2?
So from here I am going to install CWM, and reading http://forum.xda-developers.com/wiki/ClockworkMod_Recovery
I have several options to create a CWM for my phone:
Building according to http://forum.xda-developers.com/showthread.php?t=1866545 and http://wiki.cyanogenmod.org/w/Build_for_i9100 I run into a dead end "Extract proprietary blobs " (http://wiki.cyanogenmod.org/w/Build_for_i9100#Extract_proprietary_blobs). I cannot do this because it requires a working phone.
Method 1A is a dead end because it requires a working phone.
Method 1B I am not 100% sure of. Where should I get this update.zip from?
Method 2 is not applicable
And finally:
For Samsung Galaxy S phones: From stock it is easiest to get CWM by flashing a kernel with CWM built-in by using Odin3 1.7 flashing utility. Only some kernels come in a Odin compatible package (.tar file).
So I need to get a kernel with CWM since I could not build one and you are suggesting SiyahKernel S2-v5.0.1 (http://www.gokhanmoral.com/?p=1536), right?
So as I understand it, I flash this kernel and then when entering recovery menu, I will get advanced options like adb shell and nandroid backup.
Correct?
jarl-dk said:
OK. I am now pretty confident that I had/has android 4.1.2, because I remember I had features like SmartStay (which is new in 4.1 AFAIK). I also remember that I had the "Mobile Data" toggle button along the other quick state buttons like "GPS", "Sound", "WIFI", "Screen rotate". The "Mobile Data" state button was also new, but I cannot verify that is was nwe in 4.1.2 (maybe it was already in 4.0.x). Do you know of any other features that are nwe in 4.1.2 that can help me verify that is was a 4.1.2?
So from here I am going to install CWM, and reading http://forum.xda-developers.com/wiki/ClockworkMod_Recovery
I have several options to create a CWM for my phone:
Building according to http://forum.xda-developers.com/showthread.php?t=1866545 and http://wiki.cyanogenmod.org/w/Build_for_i777 I run into a dead end "Extract proprietary blobs " (http://wiki.cyanogenmod.org/w/Build_for_i777#Extract_proprietary_blobs). I cannot do this because it requires a working phone.
Method 1A is a dead end because it requires a working phone.
Method 1B I am not 100% sure of. Where should I get this update.zip from?
Method 2 is not applicable
And finally:
For Samsung Galaxy S phones: From stock it is easiest to get CWM by flashing a kernel with CWM built-in by using Odin3 1.7 flashing utility. Only some kernels come in a Odin compatible package (.tar file).
So I need to get a kernel with CWM since I could not build one and you are suggesting SiyahKernel S2-v5.0.1 (http://www.gokhanmoral.com/?p=1536), right?
So as I understand it, I flash this kernel and then when entering recovery menu, I will get advanced options like adb shell and nandroid backup.
Correct?
Click to expand...
Click to collapse
Aha! Now we're getting somewhere To clarify though, you do have an i9100?? Not an i777? You posted links for i777 that's all. If you have something other than i9100 don't flash Siyah.
If you're on 4.1.2 (yes smart stay is 4.1.2, so if you had that, we should be good) then nope, you want Siyah v6.0 beta4 or beta 5, not Siyah v5. Download them from the same place. To flash it in Odin, flash it in the PDA section of Odin, don't check repartition or unplug your phone till it passes (or fails), with no exceptions! If you need more info, google, or click my signature & look at that. Or, go to Q&A and look at the stickied guide there, plenty of options
Yep, once you flash the kernel and get CWM recovery, then you want to backup (nandroid). Then you can factory reset from CWM, and hopefully boot up! Once you're booting then you can set about restoring the data from your backup.
See how you go as always, read up (good job continuing to do that) and post up if you can't find a solution to something. As my signature says, 'reading is easy, fixing is not', so read up then flash away!
Hopper8 said:
Aha! Now we're getting somewhere To clarify though, you do have an i9100?? Not an i777? You posted links for i777 that's all. If you have something other than i9100 don't flash Siyah.
Click to expand...
Click to collapse
Thanks for enlightening me... Yes it is a GT-I9100. I must have picked the wrong variant in the device page. Links are fixed. Thanks.
I can download a zip version of the Siyah kernel, which brings me back to another question. Regarding Method 1B:
Method 1B: you can find and download the update.zip by yourself, place it on the phone in /sdcard/ and boot into recovery using the 3 button method, choose the option "re-install package" TWO TIMES to load into CWM. Once again the update.zip needs to remain on the phone. DO NOT DELETE!
It sounds to me like I can put the Siyah kernel (update.zip) on an external SD card and boot directly from the SD card (without flashing) and then make a nandroid backup which in that case also will also include my original kernel which is currently installed.
Do I understand that method correct?
Otherwise I understand it the way that I cannot expect to get a backup of my current kernel. However I will be able to restore it during "Make the phone useable again" step which include wipe and factory reset, and several system upgrades.