Related
Hi guys,
I've had an S2 for a few months now, and although I've managed to root the phone I'm still pretty green and need help.
I've had an OTA update from Gingerbread to ICS which I only installed as it popped up when I was using the phone.
The battery died earlier than expected and now it's stuck in a bootloop.
I don't want to have to ROM it as frankly I'm still in the "full theory" stage. I've heard of Odin and SamMobile.com, I've seen hours of vids on Youtube but I'm hoping there's another way to get around it. My confidence levels are improving but not there yet.
I have a Titanium backup on the phone from 2.3.4, if I wipe the phone from recovery will it work? Is there anything I can do apart from a new ROM?
If you had my lack of experience with this, what would you do? Thanks.
Can you get into download mode?
If so, you may have to bite the bullet and use Odin to flash the original firmware. You will be able to find it on these forums.
Don't sweat it, just download the Orange ICS ROM and put it in PDA on Odin and flash it, it'll take just a couple of minutes and you are done.
Thanks guys. It sounds so simple when you don't have a bootlocked phone to panic about.
FourQ said:
Thanks guys. It sounds so simple when you don't have a bootlocked phone to panic about.
Click to expand...
Click to collapse
Thats because it is simple! Ive never rooted because it looks confusing. But I've used odin many times to flash stock firmwares.
Sent from my GT-I9100 using XDA
Warren.D said:
Thats because it is simple! Ive never rooted because it looks confusing. But I've used odin many times to flash stock firmwares.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Nothing confusing about rooting either.
Download one of chainfires cfroot kernels or siyah kernel and flash via Odin.
That's it you're rooted.
----------------------
GTI9100
Hydra H2O 1.2.1
fluxi xx.01_rc5
if ya have a look around the forum, theres plenty of pre-rooted roms to flash via odin that wont increase ya binary counter, nothing hard about that.
Read the links in my signature
Sent from my GT-I9100 using XDA
I'm still reletively new to it
and I've had a couple of bootloops. A bit of a panic and then I figured out what I'd done wrong. As long as you follow instructions to the letter you'll be fine.
Edit: *Relatively, damn it.
Rooting it was easy enough. I went to unlockroot.com and a download later I was rooted. It's the ROMs that terrify me.
FourQ said:
Rooting it was easy enough. I went to unlockroot.com and a download later I was rooted. It's the ROMs that terrify me.
Click to expand...
Click to collapse
getting a custom rom isn't something you should be afraid of
getting a custom rom (or kernel) can improve your battery life (some of them).. but just be sure that getting a custom rom, it should be for whatever you're running (Gingerbread or ICS) usually, roms are flashable via CWM
take a leap, when you get into bootloop or get some problems along the process, just flash a stock firmware with odin..
@saywhatt
A mate (who's been doing this for years) has installed CWM7. It's odd how the things I liked about Gingerbread were added by Samsung, not Google.
I suspect I'll run with CWM7 for a week or so and decide then. First impressions aren't always correct (especially if you saw my face!) but after a week I should have a pretty good impression of the new ROM. I'm hesitant about ICS as the official version killed the phone but ultimately I may end up there.
It's good to watch the Youtube vids on how to flash stock ROMs with Odin. It's something I may try next week if CWM7 falls from favour.
Ultimately I'm sort of glad it happened. It's given me new confidence to try these things as I know there's a good chance it can all be recovered.
Q
I've never been too afraid of rooting or flashing. My first android device was a cheap piece of rubbish (an LG GTsomething i think), so I built up confidence in rooting and flashing because I didn't care if i damaged my phone.
I would recommend anyone who's not too confident to go out and get a cheap phone, it's a pretty significant investment but if your unsure about what your doing and just want to experiment, it's definitely worth the peace of mind.
...
I'm hesitant about ICS as the official version killed the phone
Click to expand...
Click to collapse
no m8 it didn't, your battery dying while you were updating killed your phone
It had finished a while before that. I was selecting a new font when it died.
You can't stuff up your phone anymore - its already in bootloop, what do you have to lose?
Odin is indeed very easy. Just make sure F.Partition is unchecked. Put the ROM in PDA and flash! Of course, after your phone has been put into download mode and connected to pc via usb and one of the Odin blocks have turned yellow.
Your phone is already rooted? If you made a backup in CWM (NOT Titanium Backup, this won't help you right now, as it's only for apps) you should restore that in CWM. A wipe and factory reset wouldn't help you right bow.
I understand you are a bit skeptic of ICS stock ROM right now, but remember you probably got pushed an early version,.the latest versions are very stable! Though Custom ROM's are the way to go eventually. Try the latest stable Cyanogen ROM.
Sent from my GT-I9100 using Tapatalk 2
@FreeStanler
Good point.
The stock ICS ROM was 4.0.3 if memory serves. It wasn't there for long but I was curious to see which version I'd been upgraded to.
I'm planning to see how this CWM7 ROM sits with me. If I can find out which app is causing this: http://t.co/9GfdXmD I'll probably be happy with it. I need to have a good play about with it to give it a fair chance. May end up with ICS/Stock ICS but for now we'll see how it goes.
Why on earth would you use Cm7 when Cm9 is far better, plus to flash a fw & then root with SuperOneClickRoot, or use the cf root kernel. The whole process takes 5 mins. Honestly M8 there's nothing to worry about. One thing I will say tho, Google Nandroid back up & once you know how to use etc, use it & make it your best friend coz that's the only thing that will fix the bootloop in the future
Sent from my GT-I9100 using xda premium
@blade30p
I didn't. A friend who's been doing this for years did it for me. I was hoping to get something resembling the stock Gingerbread on the phone, instead I got CWM7.
If anyone has the time i would like some help on how to flash my Note without bricking the phone. Reason i ask, is because i have already bricked it!! Sent it off to mobiletechvideos.com who unbricked it so now i'm back! I love the phone alot just hate stock rom and how slow it is. I would like to use a rom that is able to overclock? I've read about the sauron rom but i can't tell if it's out dated or if there is something better now?
I'm not a noob when it comes to rom's, Htc aria, samsung captivate, inspire, then the htc one x - i've all rom'd them but now i'm stump'd. The first go around, i flashed the rom and everything went thru fine. When i booted up the phone - Nothing changed!? so i find another rom, flashed it and the phone bricked. Tried jig everything else and to no avail. So 65$ later i'm back with the stock rom and it's rooted. Anyhow, here is the info i'm sure you guys are wanting to give me a hand!
Model Number
SAMSUNG-SGH-I717
Andriod Version
2.3.6
Baseband Version
I717UCLF6
Kernel Version
2.6.35.11
Build Number
GINGERBREAD.UCLA1
Cliff Notes -- Hard bricked trying to flash rom, Main goal want to overclock, battery life not issue. Please help flashing :angel:
do you have a custom recovery ? like cwm or the other one ( ive only had my note a week)
i would start with that..
If I were you (and I fully understand that I am not nor anyone else on here...) I would:
1. Install Samsung Kies and drivers to my laptop.
2. Start Samsung Kies and plug in the phone via USB cable.
3. Update the phone's OS via Kies to ICS. You won't brick it that way.
4. Give stock ICS a chance and if you still feel it's too slow for you (rolling eyes), flash a custom ROM/kernel.
nutpants said:
do you have a custom recovery ? like cwm or the other one ( ive only had my note a week)
i would start with that..
Click to expand...
Click to collapse
Yep, already have clockwork mod, That's no big deal.
BlackZenith said:
If I were you (and I fully understand that I am not nor anyone else on here...) I would:
1. Install Samsung Kies and drivers to my laptop.
2. Start Samsung Kies and plug in the phone via USB cable.
3. Update the phone's OS via Kies to ICS. You won't brick it that way.
4. Give stock ICS a chance and if you still feel it's too slow for you (rolling eyes), flash a custom ROM/kernel.
Click to expand...
Click to collapse
Sounds good sir i will give it a try - Meanwhile Anyone want to take a stab at walking me thru a rom that would work on my phone?
not that i have any idea what i am doing...
0 MAKE VERY SURE THE ROM YOU ARE FLASHING IS FOR YOUR PHONE... FORGET THE WORDS "note" or "galaxy" or anything else..
its the i717d or i 7100 or i 7000 that matters.. if in doubt dont do it..
1 download your cwm compatible rom (like blackstar or others) ( try to pick a recent rom no older than 2 months unless all the developers have jumped ship for the new phone)
( usually ends with a .zip) to your sd card)
2 use "android file verifier " ( from the market) to make sure your md5 hash of the download is prefect
( there SHOULD be a md5 someplace to verify the file download)
then by following info like whats found here.... http://forum.xda-developers.com/showthread.php?t=1584250 ( and that i copied and pasted)
boot into recovery by pressing volume up down,and power button at same time ( when your phone is turned off)
Select wipe data/factory reset and confirm
Select wipe cache partition and confirm
Select advanced - wipe dalvik cache and confirm
Select install zip from SD card
Select from internal SD card or wherever you placed it.
Select the ROM file and confirm.
rom will install
then AGAIN
Select wipe data/factory reset and confirm
Select wipe cache partition and confirm
Select advanced - wipe dalvik cache and confirm
boot up wait 5mins for it to boot.. dont touch it for 10 minutes after it boots
then
have fun..
dont forget to wonder if you bricked it during the first boot... that one takes the longest..
i have followed these directions drunk and sober when flashing over 20 times my new note i717d i got last week and im not bricked yet.
its the same system i used with my sgs2 i9100 for over a year and it still works..
but then dont think anything i have said here is right.
i could just be stupid and very lucky that i dont brick everything i touch but will not admit it.
READ A LOT, then READ more.. then ONE MORE TIME READ.. then flash.
BlackZenith said:
If I were you (and I fully understand that I am not nor anyone else on here...) I would:
1. Install Samsung Kies and drivers to my laptop.
2. Start Samsung Kies and plug in the phone via USB cable.
3. Update the phone's OS via Kies to ICS. You won't brick it that way.
4. Give stock ICS a chance and if you still feel it's too slow for you (rolling eyes), flash a custom ROM/kernel.
Click to expand...
Click to collapse
So after about 2 hours off and on, using different cables and google. No avail, UGH!
Samsung kies
Your device is not supported to update via samsung kies. Walked thru a few xda threads and they are saying update thru odin. Hell if i'm jumping ship to odin again, mine as well do a rom. I'm giving this 1 more shot, if it bricks i'll sell it lol!!
Mobiletechvideos most have had to do something extreme to repair your device, or they gave you one that.... never mind. Well, looks like you need to flash CWM and find a zip aligned ROM on here.
BlackZenith said:
Mobiletechvideos most have had to do something extreme to repair your device, or they gave you one that.... never mind. Well, looks like you need to flash CWM and find a zip aligned ROM on here.
Click to expand...
Click to collapse
LOL, no they did exactly what was promised. Even people who haven't bricked their device have ran into this issue!
Okay - After reading up and then watching a video on how to flash roms. Which looked exactly like what i had done before time and time again. I'm proud to say i'm ROM'D! I'm now running the blackstar rom and it's very zippy love it to death. Would like to have tried ICS 4.0.4 but took the plunge and happy with the turn out.
I've always came to this site for help but never made an account and you guys are too nice! Hopefully i can/could help someone else out down the road. Until then i'm going to enjoy not being so slow! Thanks!:good:
Its because you have a LF6 modem. Its not the modem that GB had. The Kies upgrade only works if your phone is stock.
You can use the kies emergancy firmware upgrade option.
Is not black star 4.04?
nutpants said:
Is not black star 4.04?
Click to expand...
Click to collapse
1st post says GB.
rangercaptain said:
1st post says GB.
Click to expand...
Click to collapse
First post here or first post of black star ?
written in your mud with my stick
Your first post.
The latest black star is based on the ics 4.0.4 firmware from Singapore
studacris said:
Your first post.
The latest black star is based on the ics 4.0.4 firmware from Singapore
Click to expand...
Click to collapse
The original Tom I started with was 2.3.6 since lies wouldn't let me update to ice 4.0.4 I jumped the gun and flashed blackstar. While it is a great rom. I'm thinking of trying more while I got my feet wet.
1Note said:
The original Tom I started with was 2.3.6 since lies wouldn't let me update to ice 4.0.4 I jumped the gun and flashed blackstar. While it is a great rom. I'm thinking of trying more while I got my feet wet.
Click to expand...
Click to collapse
I've been flashing two roms a day looking for something that supports total recall and underclocking, with a network mode menu that has lte on it.
I think I am out of luck.and I have forgotten some roms so I may flash everything again and keep notes...
It's research not an addiction.
written in your mud with my stick
Stage 1 of acceptance is denial
studacris said:
Stage 1 of acceptance is denial
Click to expand...
Click to collapse
LOL ...
And of course my favorite ....
"Trying is the first step toward failure ".....(Homer Simpson )...(grin )
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.
First of all, I am not new to flashing, rooting and etc. I have helped many of my friends with custom roms and etc so flashing and Odin is not something I know nothing about.
However, I was asked by my friend that his S2 was running slow and wanted me to put a custom rom on there. So I did the usual thing of using the ZergRush method to give him root access and I tested Superuser with Root Checker and everything was fine. So I went to install a custom recovery (Phil's CWM) via Odin and using the latest tar file from Phil's website but this is where things didn't go according to plan.
When I hit the Start button in Odin, it did the normal thing of writing to the NAND but instead of taking the usual 8-10 seconds, it took a lot longer. I actually waited 20 minutes and nothing was happening. There was no indication on the S2 that anything was happening and Odin was still stuck on the NAND Writing with all the buttone grayed out. So I waited a bit longer and after 30 min I decided to close Odin and try again, but when I try to get into Download Mode, I got the message 'Software Update Fail'. I tried to flash the custom recovery again but when it gets to the NAND Write, it instantly goes to 'Fail'.
Out of the 8 Samsung phones I have rooted and put a custom rom on, this is the first time this has happened. I searched the forum but most of it point to a bricked phone. I know at this point is is pretty critical that I do not try any random thing and asking you guys for any advice. I have tried flashing with a different version of Odin and also on different computers but gave me the same result. So any help would be much appriciated.
Hopper8's 'Odin troubleshooting' guide; search for it. You need to try everything in that thread over & over & over, only way you're fixing it is if you get a successful Odin flash away. In particular flashing the 3 part firmware might fix it.
Given the alternative - motherboard replacement or new phone - keep trying stuff, these cases are sometimes fixed by persevering (for whatever reason the first 8 stock rom flashes you try don't work but the 9th does, etc)
Thanks for the information MistahBungle, I have tried most of what has been said but I have not tried the leaked rom for the i9100. I will definately give this a shot.
No worries The rationale with flashing the 3 part is it will wipe the phone & hopefully remove any 'remnants' of what was previously on the phone which might be causing issues. If that doesn't work, download a bunch of stock roms from Samfirmware (carrier/country doesn't matter, just make sure you DL I9100 firmwares) & start flashing, this sometimes solves problems like this as I mentioned in my PP. Good luck.
MistahBungle said:
No worries The rationale with flashing the 3 part is it will wipe the phone & hopefully remove any 'remnants' of what was previously on the phone which might be causing issues. If that doesn't work, download a bunch of stock roms from Samfirmware (carrier/country doesn't matter, just make sure you DL I9100 firmwares) & start flashing, this sometimes solves problems like this as I mentioned in my PP. Good luck.
Click to expand...
Click to collapse
Just giving you an update. The 3 part leaked rom did the trick! I been flashing for a few years now but never ever had Odin go wrong so this is a new experience for me. I really appricate your help with this, was so worried I stuffed up a friends phone.
Good news then No worries, glad you got it sorted (& you've still got a friend ). Yeah, that's a handy trick the 3 part, it's bailed a few people out. Don't forget to thank Hopper's OP in his thread.
Z-Blade said:
Just giving you an update. The 3 part leaked rom did the trick! I been flashing for a few years now but never ever had Odin go wrong so this is a new experience for me. I really appricate your help with this, was so worried I stuffed up a friends phone.
Click to expand...
Click to collapse
Good to see you got it working, always like hearing of people getting their (or not their own in your case) phone back to life
MistahBungle said:
Good news then No worries, glad you got it sorted (& you've still got a friend ). Yeah, that's a handy trick the 3 part, it's bailed a few people out. Don't forget to thank Hopper's OP in his thread.
Click to expand...
Click to collapse
Thanks for keeping on referring my thread, the more people it can help the better I'm working 6 days a week for now so haven't much time to go on Q&A and help out. Also thanks for before, I think you know what I'm referring to. Much appreciated. :good: