[Q] VZW Samsung Fascinate won't root - Fascinate Q&A, Help & Troubleshooting

This phone is on the latest software release, EH03 (Gingerbread 2.3.5), and I'm using the Fascinate_Root_V2. The device is listed as connected, so I know the drivers are fine. But, for some reason, rage.bin does not push, though everything else does. After that, the phone boots twice, but Superuser is nowhere to be found. Sometimes after it boots twice, it says it's complete, other times it says device not found. It ultimately fails to work either way.

Not sure what method you are trying but you will have a lot better luck if you use droidstyles guide in the fascinate general section. It has everything you need...trust me.
Sent from my SCH-I500 using Tapatalk

I figured it out. Turns out it was much easier to use Odin3 to flash CWM, then flash the Superuser/Root package from recovery. Worked like a charm.
Instructions here.
More details here.

UndeadSquirrel said:
I figured it out. Turns out it was much easier to use Odin3 to flash CWM, then flash the Superuser/Root package from recovery. Worked like a charm.
Instructions here.
More details here.
Click to expand...
Click to collapse
I was about to say use Oden lol. I'm on eh03 as well!

Related

[Q] anyone nice enough to help a newbie fix a phone that he just bricked?

ok heres my problem:
i was trying to disable the ryanza oclf alpha 1 build with the unlagfixme batch file that came in the .zip in anticipation of the update. in the process as it was copying the files from ext2 to rcf or somethign like that, my phone rang. instead of just letting it go, i freaked and tied to reject the call. this caused my superuser permission to force close. tried to run a couple more times, but the superuser would not recognize anything. i rebooted the phone expecting the worst, and got it. now it wont boot past the galaxy s screen. i would like to just get back to stock, just like it was when it came out of the box, so i can receive the tmobile ji6 update, but admittedly don't know what i am doing. anyone with the patience to explain to me how to fix it? you can even ridicule me all you want. thanks.
The short answer, you will need to setup odin and flash the stock rom. All the needed links are in the ' vibrant directory (bible)' thread under the development section.
1) install the windows drivers for the vibrant on your computer.
2) download odin and the stock rom.
3) run odin
4) enter download mode on you phone
5) flash the stock rom
6) smile because you fixed a brick
Follow the links in the bible thread for more specific details, as I don't want to rewrite what has been written.
Hope this helps.
Sent from my SGH-T959 using XDA App
thanks, but now it seems i am having trouble getting into download mode as well. when i ran the root update.zip i got to it a million times no problem. could this be because in the middle of freaking out, i got it into recovery mode and reloaded the packages?
also if i have kies, i should already have the drivers correct?
if you are at the Gal S screen, ADB should be able to read the phone.
just run adb reboot download
ADB starts to see the phone while still on the vibrant screen for me
lol...i realize i am not sounding any smarter but where do i get adb?
ok so i got the sdk, and adb was included in that. but when i go to run the adb application, it opens and closes what looks like the command window immediately? pretty confused right now. like i said, i am definitely new at all this.
malaise said:
lol...i realize i am not sounding any smarter but where do i get adb?
Click to expand...
Click to collapse
you load it through the cmd prompt.
so start>run>cmd> path to sdk/tools> adb reboot download
ok in dl mode, got the true stock 2.1 rom selected in odin, but whats this about a .tar file?
"and for the T959UVJFD.tar just use PDA click repartition and start"
holy ****. you guys are awesome. back to stock, and working perfectly!!! and now i know how to use adb and odin. if i could i'd buy yall a beer.
malaise said:
ok in dl mode, got the true stock 2.1 rom selected in odin, but whats this about a .tar file?
"and for the T959UVJFD.tar just use PDA click repartition and start"
Click to expand...
Click to collapse
There are directions on how to use Odin in the Bible thread in the developer section. Google works too.
nm..op got it fixed

Help with SuperOneClick or GalaxyS2RootNew

I had a SGS2 several months ago and was able to root it just fine. I am now having issues w/ my computer identifying the device (A different SGS2), while connected and using either SOC or GalaxyS2RootNew. I removed the usb drivers I had installed (for Captivare) and while I can mount the phone and read internal and external drives on the phone, when I plug phone in and run either SOC or GS2Root it just says "waiting for device"
Wait, so are you obtaining root through Odin? And are you on 2.3.6?
jaguars34 said:
Wait, so are you obtaining root through Odin? And are you on 2.3.6?
Click to expand...
Click to collapse
Well I could do that (Odin) however I have read quite a bit that SOC and GalaxyS2RootNew are much safer. No, phone is on 2.3.4
Oh, I got you. Well, I just used the one click Odin flasher for 2.3.6, and it worked for me like a charm. If you can't get the one click root to work, read up on Odin. If you know what your doing it isn't dangerous at all. Look on entropy's guide or creepyncrawly's to flash for root in Odin
jaguars34 said:
Oh, I got you. Well, I just used the one click Odin flasher for 2.3.6, and it worked for me like a charm. If you can't get the one click root to work, read up on Odin. If you know what your doing it isn't dangerous at all. Look on entropy's guide or creepyncrawly's to flash for root in Odin
Click to expand...
Click to collapse
Been flashing for a couple years and I was here when Entropy started. I have a mega post on sgs2 but got away from it a month ago. I am familiar with ways to do it< just wanted to make the newer, safer ways a try.
Could simply be the USB ports. That happened to me. If all fails try using another computer/operating system (hint: linux). Did you get root?
I am having bad issues as well i have flashed back to 2.3.4 using odin, rerooted and now i can't seem to do anything evertime i try and install a Rom like phonebricker i get stuck on the boot screen......please help i realize im a total noob! Im also apply root before trying to do anything but i must be missing some step im sure.
Sent from my SAMSUNG-SGH-I717 using xda premium

Odin doesn't work after root!

So I rooted my Note a few weeks back using the non-counter advancing rooting method via odin. Worked flawlessly, and I'm rooted without issue. Tired of waiting for stock ICS to come out so I want to start flashing ROM's. Trying to install the newest CWM through Odin....well Odin doesn't recognize when the phone is connected. Tried 2 different windows 7 VM's and one W7 machine. I flashed via one of the VM's and it worked fine. It's not working on any machine that I have. I also have a mac book pro, but no idea if there is a apple Odin. What do I do? Don't have the android APK and really don't wanna go that route through ADB.
Can I just reboot into recovery and 'install via sd' or whatever the selection is, navigate to CWM touch recovery zip and install? or will that potentially do some serious damage?
Also if it's available on the CWM website as a DL why isn't it an option through the app to install? Would make my life WORLDS easier at this point.
A rooted phone would not interfere with Odin, completely unrelated. Perhaps your cable is bad, or you are installing the wrong drivers.
That said, once you have CWM on your phone, there should be no reason to use odin again. The updates for CWM are flashable via CWM. Most every single ROM is flashable via CWM. I can't really tell from your description if you were successful installing a custom recovery yet.
jpeg42 said:
A rooted phone would not interfere with Odin, completely unrelated. Perhaps your cable is bad, or you are installing the wrong drivers.
That said, once you have CWM on your phone, there should be no reason to use odin again. The updates for CWM are flashable via CWM. Most every single ROM is flashable via CWM. I can't really tell from your description if you were successful installing a custom recovery yet.
Click to expand...
Click to collapse
Trying to install a custom recovery. Sorry may not have made that clear in my rant. I've tried a couple different cables, and same luck. I DLed the CWM app from the Google Play, but have not installed a custom recovery. Trying to get CWM touch installed. Galaxy Note isn't an option when I try and install a custom recovery(CWM Touch Recovery...or hell any CWM recovery Note isn't an avialable model) via CWM.
So the options I've found so far are: Install custom recovery(CWM) via Odin, or install via ADB using android APK.
Are there other options to installing CWM recovery?
Sorry kind of a newb to all of this. I had a Dell Streak before this as my first android and it was a PITA to install Custom ROM's and root that I didn't mess with it much. Did root it and managed to soft brick my phone and bring her back to life. lol Then figured it was too much a pain to deal with.
ROM manager does not support our phone. I wouldn't use that app for now. So you're booting into download mode and Odin doesn't see your phone? I'm assuming you're in download mode?
froidroid said:
ROM manager does not support our phone. I wouldn't use that app for now. So you're booting into download mode and Odin doesn't see your phone? I'm assuming you're in download mode?
Click to expand...
Click to collapse
This...if not restart everything from scratch. Uninstall the drivers and re-install them again and restart Odin. Also make sure you are using the latest version of Odin.
froidroid said:
ROM manager does not support our phone. I wouldn't use that app for now. So you're booting into download mode and Odin doesn't see your phone? I'm assuming you're in download mode?
Click to expand...
Click to collapse
Correct isn't recognized in DL mode. The phone is recognized just fine when I plug it in regularly. Can transfer back and forth all day long.
The ICS ROM I wanna try uses CWM recovery to install. So trying to get everything to line up as to not end up with a brick. lol
babymatteo said:
This...if not restart everything from scratch. Uninstall the drivers and re-install them again and restart Odin. Also make sure you are using the latest version of Odin.
Click to expand...
Click to collapse
Believe I've done that before, but will try again. Latest version of Odin higher than 1.8.5 or something like that? If so that's what I'm using.
ROM manager does not support our phone. I wouldn't use that app for now. So you're booting into download mode and Odin doesn't see your phone? I'm assuming you're in download mode?
darkion2411 said:
ROM manager does not support our phone. I wouldn't use that app for now. So you're booting into download mode and Odin doesn't see your phone? I'm assuming you're in download mode?
Click to expand...
Click to collapse
Not sure what's going on with XDA, but my reply didn't post. So here goes: Yes that is correct I would boot into DL mode and odin didn't see my phone.
So I opened one of my VM's( the one previously used to root) uninstalled/reinstalled the drivers and voila odin sees my phone again. CWM touch recovery installed. Now off to flash Team Perfections ICS. Only chose them as they have a step by step video of installation and it seems stupid easy. Also seems to be the most stable from reading. Could be wrong. I'll try it out and wait for official CM9.
Have you tried using a different PC. I remeber my desktop wouldnt let me odin all the sudden one day. I tried my laptop worked no problem. using a VM sounds sketchy id be afraid there were too many facets or some risk of data corruption on its way. That may be incorrect but data > virtual hardware > hardware > phone. just too much for me -_-
Wing_Zero_Custom said:
Have you tried using a different PC. I remeber my desktop wouldnt let me odin all the sudden one day. I tried my laptop worked no problem. using a VM sounds sketchy id be afraid there were too many facets or some risk of data corruption on its way. That may be incorrect but data > virtual hardware > hardware > phone. just too much for me -_-
Click to expand...
Click to collapse
I tried my physical windows machine and it wouldn't even install the drivers. Failed every time regardless what I did.
I got the VM to work fine. CWM recovery touch is installed now.
sukemecuke said:
Not sure what's going on with XDA, but my reply didn't post. So here goes: Yes that is correct I would boot into DL mode and odin didn't see my phone.
So I opened one of my VM's( the one previously used to root) uninstalled/reinstalled the drivers and voila odin sees my phone again. CWM touch recovery installed. Now off to flash Team Perfections ICS. Only chose them as they have a step by step video of installation and it seems stupid easy. Also seems to be the most stable from reading. Could be wrong. I'll try it out and wait for official CM9.
Click to expand...
Click to collapse
All roms are that easy to flash once you have cwm, it's just booting into recovery, wiping, and flashing.
Try em all and see which one works best fir you
studacris said:
All roms are that easy to flash once you have cwm, it's just booting into recovery, wiping, and flashing.
Try em all and see which one works best fir you
Click to expand...
Click to collapse
I hear ya. Just when I start reading about some ROM's they say: oh and you need to flash this, this and this or else your phone will blow up and likely kill your whole family.
Being somewhat new to the flashing business just flashing ONE zip file is enough for me. Yet alone a bunch of other things. Just starts to confuse me with the multiple flashes......do I install all the same( as far as "flashing" goes)? Just boot into recovery navigate to file...double click and it'll do it's thing? If so I suppose that's not all that difficult. I like the one and done approach though. lol
Yup.
If there are multiple zips, flash them all like the main ROM.
Sweet! Flashed the Objection ICS. Like it so far. Seems like the modem is kinda all over the map for lte speeds.
Sent from my SAMSUNG-SGH-I717 using XDA

Help- I messed up my phone bad (stuck on exclamation mark)

So I decided to root my Samsung S2 i7777. Had years of experience flashing HTC hero and Hp touchpad. Thought this might be straightforward as well. Proceeded to get ODIN and ATTGalaxyS2RootStockZedomaxKernel.tar. Flashed it and got pass. Phone proceeded to reboot and was stuck on the Exclamation mark. Tried restarting but no luck same thing. Initially had CWM coming in when I tried the Volume and Power button trick but could not do anything beyond that.
Then I decided that maybe my flash was not proper with that file so I took the siyah kernel and flashed that. This was a pass as well and then back to...the exclamation mark. Now, I cannot get CWM and retarating the phone with the USB connected lets me get into the Downloading window, but I cannot do anything beyond it.
What can I do? Do I need to flash a ROM- is that why I am stuck? How should I flash the ROM from ODIN- if I do get CWM back, can I put the ROM on the SD card and flash it using CWM?
Please help- I am getting stressed out and if I do recover from this, I am going to take a break from rooting :laugh:
g.kupster said:
So I decided to root my Samsung S2 i7777. Had years of experience flashing HTC hero and Hp touchpad. Thought this might be straightforward as well. Proceeded to get ODIN and ATTGalaxyS2RootStockZedomaxKernel.tar. Flashed it and got pass. Phone proceeded to reboot and was stuck on the Exclamation mark. Tried restarting but no luck same thing. Initially had CWM coming in when I tried the Volume and Power button trick but could not do anything beyond that.
Then I decided that maybe my flash was not proper with that file so I took the siyah kernel and flashed that. This was a pass as well and then back to...the exclamation mark. Now, I cannot get CWM and retarating the phone with the USB connected lets me get into the Downloading window, but I cannot do anything beyond it.
What can I do? Do I need to flash a ROM- is that why I am stuck? How should I flash the ROM from ODIN- if I do get CWM back, can I put the ROM on the SD card and flash it using CWM?
Please help- I am getting stressed out and if I do recover from this, I am going to take a break from rooting :laugh:
Click to expand...
Click to collapse
I think you should head over to the stickies and look for creepyncrawly's thread. It sounds like you should also be able to flash firmware through download mode if kernels are working. Also, stay away from galaxys2root and zedomax in the future
Sent from my SGH-I777 using Tapatalk 2
g.kupster said:
So I decided to root my Samsung S2 i7777. Had years of experience flashing HTC hero and Hp touchpad. Thought this might be straightforward as well. Proceeded to get ODIN and ATTGalaxyS2RootStockZedomaxKernel.tar. Flashed it and got pass. Phone proceeded to reboot and was stuck on the Exclamation mark. Tried restarting but no luck same thing. Initially had CWM coming in when I tried the Volume and Power button trick but could not do anything beyond that.
Then I decided that maybe my flash was not proper with that file so I took the siyah kernel and flashed that. This was a pass as well and then back to...the exclamation mark. Now, I cannot get CWM and retarating the phone with the USB connected lets me get into the Downloading window, but I cannot do anything beyond it.
What can I do? Do I need to flash a ROM- is that why I am stuck? How should I flash the ROM from ODIN- if I do get CWM back, can I put the ROM on the SD card and flash it using CWM?
Please help- I am getting stressed out and if I do recover from this, I am going to take a break from rooting :laugh:
Click to expand...
Click to collapse
You shouldn't take a break from rooting. You are just one of a very large group of people that have been blindsided by the galaxys2root website and its rogue developer zedomax. The firmware tools from that site have caused untold problems for people, similar to your problem.
To recover your phone, you need to first flash back to stock. Since you want to root the phone, and ultimately install custom firmware, you should first flash UCKH7 stock plus root package using the one-click downloader which you can get from the guide about how to flash custom binaries without incrementing the flash counter. The link for the guide is in my signature. Read the guide and follow it's directions. That should get you going again. If for some reason you have any trouble, post back here and we'll try to help you out.
Nick281051 said:
I think you should head over to the stickies and look for creepyncrawly's thread. It sounds like you should also be able to flash firmware through download mode if kernels are working. Also, stay away from galaxys2root and zedomax in the future
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Thanks I checked it out..seems like putting the Stock back on might help me. Just so that I understand this better before I do it, am I installing the UCLE5_Stock_Rooted.tar using ODIN and that is enough to get me through.
Thanks
creepyncrawly said:
You shouldn't take a break from rooting. You are just one of a very large group of people that have been blindsided by the galaxys2root website and its rogue developer zedomax. The firmware tools from that site have caused untold problems for people, similar to your problem.
To recover your phone, you need to first flash back to stock. Since you want to root the phone, and ultimately install custom firmware, you should first flash UCKH7 stock plus root package using the one-click downloader which you can get from the guide about how to flash custom binaries without incrementing the flash counter. The link for the guide is in my signature. Read the guide and follow it's directions. That should get you going again. If for some reason you have any trouble, post back here and we'll try to help you out.
Click to expand...
Click to collapse
Thanks for stopping by. I did not see your post when I posted my reply to the previous poster..I am so worried that I might screw it up more that I wanted to be doubly sure about this. from what I read, I am doing Step 2c as indicated below. Am I correct?
Thanks
2c.) How to root by flashing Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package with Modem using Odin3 One-Click Downloader (Windows)
UPDATE: I did download the "Odin3 One-Click Downloader Stock I-777 UCKH7 with Root no BL" package and extracted the file. Double clicked on it with the phone connected and all I see are the words I777- UCKH7 with Root with a lot of empty boxes below. Went to Odin and I see the phone connected (Com has yellow box) but nothing else is ticked off. Clicking Start does not do anything at all.
At my wits end- will not get any sleep tonite if I don't fix it.
Thanks in advance
I had a similar thing happen after trying to make a backup of the stock rom with Rom Manager (Yes, I know now, thanks much.)
If you keep trying new kernels/roms and it never clears up, you're pretty much stuck with wiping data. It won't wipe your sdcard, but more and more apps are sticking their data in the phone's memory rather than on the sdcard, so if you can get a backup at all, you really should.
Source: Was up until 2:30 the other night trying to make my phone work again. The above is a GUESS - it's probable I missed something that creepyncrawly wouldn't.
Ok more progress..turned off the phone and started 'I777UCKH7 OCD With Root.exe". Got the same window with lot of empty boxes. Had turned off the phone by this time and disconnected it. Now, I connected the phone and pressed the volume buttons. Phone goes into Download mode. Now, the Odin3 window has a Com port for the phone. Now I press start and it goes through a bunch of things before it declares "FAIL" in red. What do I do?
Evidently, the zedomax product you originally flashed, or perhaps the siyah kernel that you flashed second, has made some undesired modification. I'd like to know exactly which package you flashed for each one of these first before I suggest which way to start correcting the problem. Can you please post working links for each of the two downloads that you used? You should still be fine, and will be able to recover the phone.
creepyncrawly said:
Evidently, the zedomax product you originally flashed, or perhaps the siyah kernel that you flashed second, has made some undesired modification. I'd like to know exactly which package you flashed for each one of these first before I suggest which way to start correcting the problem. Can you please post working links for each of the two downloads that you used? You should still be fine, and will be able to recover the phone.
Click to expand...
Click to collapse
This stuff makes me so sad seeing these threads............ Thanx for helping him Creepy, ALWAYZ with 100% accurate info!!! Looks like this is the page he got the tar from in the zip on step 3 http://galaxys2root.com/galaxy-s2-root/how-to-root-att-galaxy-s2-sgh-i777/ Much respect Creepy.....
creepyncrawly said:
Evidently, the zedomax product you originally flashed, or perhaps the siyah kernel that you flashed second, has made some undesired modification. I'd like to know exactly which package you flashed for each one of these first before I suggest which way to start correcting the problem. Can you please post working links for each of the two downloads that you used? You should still be fine, and will be able to recover the phone.
Click to expand...
Click to collapse
The first one was http://galaxys2root.com/galaxy-s2-root/how-to-root-att-galaxy-s2-sgh-i777/
The second one was http://galaxys2root.com/galaxy-s2-root/how-to-root-ics-on-att-galaxy-s2-sgh-i777/
Now I know I need to stay away from galaxy2root. Thanks for looking at this. The status of the phone is I can go into Download mode by pressing volume buttons and connected to USB. ODIN can see the phone (COM is yellow with number). Nothing happens beyond that..
g.kupster said:
The first one was http://galaxys2root.com/galaxy-s2-root/how-to-root-att-galaxy-s2-sgh-i777/
The second one was http://galaxys2root.com/galaxy-s2-root/how-to-root-ics-on-att-galaxy-s2-sgh-i777/
Now I know I need to stay away from galaxy2root. Thanks for looking at this. The status of the phone is I can go into Download mode by pressing volume buttons and connected to USB. ODIN can see the phone (COM is yellow with number). Nothing happens beyond that..
Click to expand...
Click to collapse
The zedomax rooting kernel you flashed first is for Gingerbread version UCKH7, and was posted last October, shortly after the phone was released. If you had UCKH7 on the phone before you flashed that, it should have booted up fine. Most people I have heard about are able to use that rooting kernel successfully. So I need more information in order to be able to trouble shoot your situation.
First, are you sure your phone is SGH-I777, and not SGH-I727?
What firmware was installed on the phone before you flashed the zedomax kernel?
Has any other modification been done on the phone since or even before you had it?
The second kernel you flashed, the Siyah kernel, is an ICS kernel, version 3.4.2. The phone will not boot if the kernel and the system have different versions installed. So I need as much detailed information as possible so know what to do next.
creepyncrawly said:
The zedomax rooting kernel you flashed first is for Gingerbread version UCKH7, and was posted last October, shortly after the phone was released. If you had UCKH7 on the phone before you flashed that, it should have booted up fine. Most people I have heard about are able to use that rooting kernel successfully. So I need more information in order to be able to trouble shoot your situation.
First, are you sure your phone is SGH-I777, and not SGH-I727?
What firmware was installed on the phone before you flashed the zedomax kernel?
Has any other modification been done on the phone since or even before you had it?
The second kernel you flashed, the Siyah kernel, is an ICS kernel, version 3.4.2. The phone will not boot if the kernel and the system have different versions installed. So I need as much detailed information as possible so know what to do next.
Click to expand...
Click to collapse
The phone is SGH-I777 from AT&T. (I'll check the phone when I get home and reconfirm) The phone had the ICS installed (through the Kies update) before I (stupidly) tried the Zedomax Kernel. I just bought the phone new so no other modification had been done. After I had installed the Zedomax I had been able to see CWM if I did the power Volume trick but I cannot do it now since I installed the Siyah.
Hope that helps. Let me know if you need more info.
g.kupster said:
The phone is SGH-I777 from AT&T. (I'll check the phone when I get home and reconfirm) The phone had the ICS installed (through the Kies update) before I (stupidly) tried the Zedomax Kernel. I just bought the phone new so no other modification had been done. After I had installed the Zedomax I had been able to see CWM if I did the power Volume trick but I cannot do it now since I installed the Siyah.
Hope that helps. Let me know if you need more info.
Click to expand...
Click to collapse
OK. The phone was new, and most likely came with Gingerbread 2.3.6 UCKK6 installed. You updated it using kies to ICS 4.0.3 UCLE5. Just asking for your confirmation here.
Then you tried to root with zedomax kernel, which is a Gingerbread 2.3.4 UCKH7 kernel, which explains why it flashed successfully, but failed to boot, since you can't have a Gingerbread kernel and an ICS system together. You were able to boot into ClockworkMod Recovery in the kernel though. We can't blame this problem on zedomax. That kernel usually works ok. You started modifying your phone before you were familiar enough with the phone and it's firmware. The error of flashing a Gingerbread kernel onto an ICS system was yours.
Next you flashed the Siyah v3.4.2 ICS kernel. This kernel should be compatible with the UCLE5 system files that are on the phone. It seems to me that the phone should now boot, and I'm not really sure from this sequence what might have been altered that prevented the phone from booting and also prevented the Odin flash back to stock from succeeding. The only thing you have flashed so far is two kernels. No other partitions should have been touched.
What kind of error message do you get when you try to boot into recovery mode using vol+ vol- Pwr?
creepyncrawly said:
OK. The phone was new, and most likely came with Gingerbread 2.3.6 UCKK6 installed. You updated it using kies to ICS 4.0.3 UCLE5. Just asking for your confirmation here.
Then you tried to root with zedomax kernel, which is a Gingerbread 2.3.4 UCKH7 kernel, which explains why it flashed successfully, but failed to boot, since you can't have a Gingerbread kernel and an ICS system together. You were able to boot into ClockworkMod Recovery in the kernel though. We can't blame this problem on zedomax. That kernel usually works ok. You started modifying your phone before you were familiar enough with the phone and it's firmware. The error of flashing a Gingerbread kernel onto an ICS system was yours.
Next you flashed the Siyah v3.4.2 ICS kernel. This kernel should be compatible with the UCLE5 system files that are on the phone. It seems to me that the phone should now boot, and I'm not really sure from this sequence what might have been altered that prevented the phone from booting and also prevented the Odin flash back to stock from succeeding. The only thing you have flashed so far is two kernels. No other partitions should have been touched.
What kind of error message do you get when you try to boot into recovery mode using vol+ vol- Pwr?
Click to expand...
Click to collapse
That seems correct (with regards to the sequence of events of the phone).
The error message is just the words "SAMSUNG GALAXY SII GT1900"..with a huge exclamation at the bottom. It stays like that until I do a battery pull.
g.kupster said:
That seems correct (with regards to the sequence of events of the phone).
The error message is just the words "SAMSUNG GALAXY SII GT1900"..with a huge exclamation at the bottom. It stays like that until I do a battery pull.
Click to expand...
Click to collapse
Please verify this - the screen says "Samsung Galaxy SII GT-I9100" assuming yours was a typo. Yellow triangle with exclamation mark?
This is what you get when you try to boot the phone normally, and also when you try to enter recovery mode using the three button method, vol+ vol- and power?
creepyncrawly said:
Please verify this - the screen says "Samsung Galaxy SII GT-I9100" assuming yours was a typo. Yellow triangle with exclamation mark?
This is what you get when you try to boot the phone normally, and also when you try to enter recovery mode using the three button method, vol+ vol- and power?
Click to expand...
Click to collapse
Yes, that is correct. It was a typo. I get the exclamation mark when I do the normal boot. I am going to confirm this evening if I get the same error with the 3 button method.
g.kupster said:
Yes, that is correct. It was a typo. I get the exclamation mark when I do the normal boot. I am going to confirm this evening if I get the same error with the 3 button method.
Click to expand...
Click to collapse
Post the answer when you have your phone in hand and I'll suggest something to try.
creepyncrawly said:
Post the answer when you have your phone in hand and I'll suggest something to try.
Click to expand...
Click to collapse
Ok, I tried that just now and I got a message 'Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again'. There is an image of a cell phone and computer with an exclamation mark between them
g.kupster said:
Ok, I tried that just now and I got a message 'Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again'. There is an image of a cell phone and computer with an exclamation mark between them
Click to expand...
Click to collapse
I'm not working from first hand experience, but I'm fairly good at correlating information and making deductions. Something in the sequence of events doesn't add up to me. You're sure you have the I777? You pulled the battery and looked at the label?
At this point any suggestions that I can offer are based on educated speculation. The first thing to try would be to flash an ICS kernel using Odin, but you have already done that. I would suggest that you try that again, but discard the tar you already have and download the tar again, from here. That may be the same place you downloaded it before, not sure. Be sure to use the original USB cable that came with the phone.

I717: Unable to flash ANY ROM'S (TWRP 2.6)

Hello, Iv'e looked at all the threads pertaining to this issue but haven't found any solution.
I use a rooted I717, running Padawan V2 ROM. Recovery is TWRP 2.6, the latest one. All the other issues that look like mine either use CWM or an older version of TWRP.
Issue: I'm unable to flash absolutely anything.Tried Stock ROM's, AOSP, AOKP ROM's. Tried downgrading TWRP to see if it works, but of course it doesn't flash.
Tried flashing using Odin, but that doesn't work either. Its never able to set up a connection. The only thing that does work is installing the same ROM all over again.
Hope someone can help me.
Illumin4tion said:
Hello, Iv'e looked at all the threads pertaining to this issue but haven't found any solution.
I use a rooted I717, running Padawan V2 ROM. Recovery is TWRP 2.6, the latest one. All the other issues that look like mine either use CWM or an older version of TWRP.
Issue: I'm unable to flash absolutely anything.Tried Stock ROM's, AOSP, AOKP ROM's. Tried downgrading TWRP to see if it works, but of course it doesn't flash.
Tried flashing using Odin, but that doesn't work either. Its never able to set up a connection. The only thing that does work is installing the same ROM all over again.
Hope someone can help me.
Click to expand...
Click to collapse
never able to set up connection?
connecting what to what?
all of it sounds odd, but this caught my eye. makes me think could this be a good starting point.
Odin > Phone
captemo said:
never able to set up connection?
connecting what to what?
all of it sounds odd, but this caught my eye. makes me think could this be a good starting point.
Click to expand...
Click to collapse
Odin (v3.07) to my phone. When flashing a stock ROM or anything for that matter, even though my phone is connected and in USB mode, it never gets past the 'Setting up connection...' step in Odin. I have a feeling this is a problem with the ROM, because transferring data to the SD card is a painful process. Most of the time the device 'stops responding' and I have to use Airdroid.
But of course this is a smaller part of the main issue.
In order to use Odin you need to be in download mode. When you're in download mode you're not using a rom so a rom can't be the problem. Try using Odin version 1.85 in download mode and flash twrp .tar file.
440bro said:
In order to use Odin you need to be in download mode. When you're in download mode you're not using a rom so a rom can't be the problem. Try using Odin version 1.85 in download mode and flash twrp .tar file.
Click to expand...
Click to collapse
Right! I totally forgot about that. Jeez
My apologies. Ill get back if the overall issue is or isn't solved.
Also, I already have TWRP 2.6, unless you're suggesting something else.
Thanks for reminding me about Odin mode. I got that working, flashed to stock, flashed TWRP 2.6.
Then followed proper procedures for PACman ROM and now it finally works.
Many thanks to both of you. Apologies for overseeing this simple process.
:good:
Illumin4tion said:
Thanks for reminding me about Odin mode. I got that working, flashed to stock, flashed TWRP 2.6.
Then followed proper procedures for PACman ROM and now it finally works.
Many thanks to both of you. Apologies for overseeing this simple process.
:good:
Click to expand...
Click to collapse
Good choice flashing PAC first. Padawan is nice, but it lags on my Note like mad
Padawan actually works like a charm for me. Super stable. Did you try changing things using the trickster mod?
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app

Categories

Resources