GS II i9100
Note: Warranty is already expired
Before I write anything further, I have been trying to get the most I can out of this thread: http://forum.xda-developers.com/showthread.php?t=1457458
Sadly, I can't seem to wrap my head around this problem, so here goes:
Yesterday I've found out, that the new CM11 came out. Of course I went off to download it, put it in my phone and started to install it through recovery (I had siyah at that time). Well, it failed, must've been corrupt or something, since I got the error status 7. Anyways, while exiting the install screen, siyah asked me, if I want to repair something, because something may have gotten corrupt (Sorry, can't remember the exact thing). Being the sloppy person I am, I clicked yes.
Five minutes later, after going back to stock firmware, because apparently during the install something did go corrupt, and the phone wouldn't boot, only play the boot sound, I've read, that I need the newest CWM for CM11 to work.
Another five minutes later I'm staring at this:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.07.9-i9100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
I've tried changing computers, kicking KIES out through the window, using different USB slots and cables, but to no avail. It just keeps throwing this error at me every time I try to install anything through Odin. The strangest part is, though, that the phone is working perfectly fine.
What could be the problem, and if it is possible, how do I fix it?
Another quick note would be my counter in the download screen of my SII. It's 12 (yeah, I know, I kept forgetting about it, but now, since I'm unable to install anything through Odin, I can't even root the phone and reset the damn thing)
Don't flash nothing to this phone. Be happy it works or get rid of it while it does still works. Seen this before and this is the first stage of mb failure. Trust me don't flash nothing to this phone and get rid of it. If not start reading about the pit file
andrewwright said:
Don't flash nothing to this phone. Be happy it works or get rid of it while it does still works. Seen this before and this is the first stage of mb failure. Trust me don't flash nothing to this phone and get rid of it. If not start reading about the pit file
Click to expand...
Click to collapse
And apparently, this is now happening:
Baseband version - XXMS2
Build - XWLSS
I think I may have messed it up a little...
Please close the thread
This thread can be closed.
Should anyone need this:
After losing patience spending hours on the phone I have decided to JTAG it... Ant it worked. The phone is running like a charm now.
Related
I was using the MIUI rom and I sold the phone. To deliver to the buyer I decided to go back to the stock rom but forgot to wipe and now I have the following situation:
- I can only get into download mode
- Odin recognizes the phone
- I tried to repartition the Odin reported successful operation (my model is 16gb)
- Tried to put other roms on the phone including those downloaded from the site sammobile, selecting only auto-reboot and f.reset.time
- With these steps could only get stuck in "nand write start ..."
- Tried installing kies but do not believe it can be something with the drivers because the odin recognizes the phone.
I read many posts but after two days decedi post to see if anyone would help me solve this issue
I'll be waiting for directions on how to proceed without worsening the scenario.
Odin log:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300UBBLG2_I9300VILG1_I9300ZVVBLG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> modem.bin
<ID:0/006> NAND Write Start!!
have you tried restarting your computer or using another computer? or even a different usb port or cable?
ages ago I had a similar problem - never moved beyond the start point - simple restart solved it for me...no idea if that's the same situation as you.
Just throwing out ideas here; otherwise I'm not sure.
Sent from my GT-I9300 using Tapatalk 2
Tried to do this, but still stucked at nand write start...
One thing I noticed is that the progress bar on the phone at the "downloading mode screen" runs quickly, and then it stops at nand write start.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300UBBLG2_I9300VILG1_I9300ZVVBLG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> modem.bin
<ID:0/005> NAND Write Start!!
At least I'm not alone
I have the exact same problem you have. Intl i9300, cannot enter recovery, only download mode. Flashing 16gb pit file works ok, however attempting to flash Stock rom gets stuck at Nand Write Start. Not sure what to do now, I guess I'll wait for responses here as well.
RePartition .
Fail Nand write .
Assuming you have read and are following the basics re an Odin flash ( if not go and read them ) .
This sounds in both cases like a damaged Nand >>> service centre job .
jje
I've not done much to my S3. Trouble started when I decided to install an OTA of Foxhound 1.8. Installation completed successfully but during the application upgrade (...you know the first boot message of 'Android is updating x of 365 apps). It froze and stuck there for like 15min so I decided to reboot it and all hell broke loose.
Started with 'Foxhound cannot mount recovery command..' etc. Which made me decide to flash my 16gb pit file, and since then all attempts to flash back to stock stall at 'Nand write start'.
I have backups of everything, even my efs. Problem is I can't even get to recovery to restore anything.
I'll keep trying I guess, worst case I'll just return it back to Samsung.
pull usb devices except s3 and be sure to have correct drivers then try again. you may even try it on another pc of course with installing drivers. if none of them works try flashing a kernel or recovery if it flashes then try to flash stock rom.if stucks again at nand write there may be a problem at emmc sect. but dont worry just do what i said if it fails there should be a solution
if you can enter the recovery mode u should be happy
to kamau can u send me the pit file you flashed thanks
zhjackss said:
to kamau can u send me the pit file you flashed thanks
Click to expand...
Click to collapse
There it is. I"m now working on resetting the flash counter from odin since I obviously can't install triangle away in preparation of returning it to samsung.
Hello
For a couple of weeks now, i've been trying to fix this phone for a friend who studies as an artist. She wanted the Galaxy Beam for presentations and bought one used as they seemingly ain't to be found in the stores any longer.
Originally, the firmware ends at 2.3.6 on this brand, but this one was rooted to be fit with 4.1.2.
The phone bugged and hung in weird ways, so i thought to follow the steps into downgrading it to stock rom for her and see if that would help.
I am no expert, but since i have successfully rooted several phones and tablets earlier with no issues (its pretty straight forward when it works, right), i felt up for the tast.
I have spent a lot of time googling the last couple weeks, and reading a lot of solutions here on these forums, but i can't seem to find this ecact problem, so here goes.
Samsung Galaxy Beam GT.I8530
Odin3 v3.07
Windows 7 and 8 fully updated (tried both)
No matter which Android version i chose, it ends up at the same spot. Stuck at logo screen after first boot.
I have tried both with and without a PIT file, same result.
This last try was with a PIT and Android 4.1.2. (i understand that PIT is not nessessary, as it should be baked within the PDA if it's a single file, but what won't you try eventually, right?)
Load Odin, admin rights
Boot phone in download mode
Insert USB
-->
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8530DXLJ1_I8530OLBLJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.img.md5
<ID:0/003> NAND Write Start!!
<ID:0/003> hidden.img.md5
<ID:0/003> kernel.bin.md5
<ID:0/003> modem.bin.md5
<ID:0/003> system.img.md5
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
- here, the phone reboots and loads to logo screen *
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
- from here the phone wont nudge from the logo screen. can reboot, nothing new happens.
No other functions work, other than:
- volume down+home+power (download mode)
- power (boots to logo screen)
Thanks for reading! Hope someone feels up for the task
Edit: It might be vital information that the phone will uncharge the battery at logo screen eventually, even when connected to a computer. (5v output) But i believe this is common somehow.
Also, if i try and shut down the phone, it will reboot into a frozen "star icon".
Bump*
What makes this issue differ from others i've read on these forums, is this:
Akiiras said:
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
Any theories?
As much as i hate bumping, i'm feeling kind of responsible to try and fix it. Hope someone got a clue on what might be wrong. Thanks
"I bet you 10 buck you'll get your answer here within a couple days" -a friend said, well, in norwegian though.
I guess a week later and no response means that i've at least earned 10 buck! ^^
Guess i can give it one more shot here before i send it to a repair guy.
*bump*
Akiiras said:
Guess i can give it one more shot here before i send it to a repair guy.
*bump*
Click to expand...
Click to collapse
Are you sure about the right region when choosing a firmware? Did you also try Odin 1.85? Have you tried flash a custom recovery via Odin and flash a rom manually?
LS.xD said:
Are you sure about the right region when choosing a firmware? Did you also try Odin 1.85? Have you tried flash a custom recovery via Odin and flash a rom manually?
Click to expand...
Click to collapse
Hi, and thanks for the reply!
I am pretty sure i got the right firmware region. At least, the only region that covered my location (norway) that i could find, was nordic.
I have not tried Odin v1.85 or manually. I guess i can find a guide on how to do it manually here somewhere, but i'll go for a shot with the older version of Odin right away.
Thanks!
Akiiras said:
Hi, and thanks for the reply!
I am pretty sure i got the right firmware region. At least, the only region that covered my location (norway) that i could find, was nordic.
I have not tried Odin v1.85 or manually. I guess i can find a guide on how to do it manually here somewhere, but i'll go for a shot with the older version of Odin right away.
Thanks!
Click to expand...
Click to collapse
BTW there are 4 different versions for nodric countries --> LINK
Odin3 v1.85 didn't work. Well, in the sense that it probably does a job well done and says everything went well, but the phone wont nudge past boot screen.
I'll see if i can learn how to do it manually and come back with the result.
Edit:
LS.xD said:
BTW there are 4 different versions for nodric countries --> LINK
Click to expand...
Click to collapse
Oh, thanks! I couldnt find it at sammobile myself, so i found it somewhere else. This could be it!
any developments?
I Have the Same Problem
I Have the same problem please anyone help me!!!!!
SOLUTION
Akiiras said:
Hello
For a couple of weeks now, i've been trying to fix this phone for a friend who studies as an artist. She wanted the Galaxy Beam for presentations and bought one used as they seemingly ain't to be found in the stores any longer.
Originally, the firmware ends at 2.3.6 on this brand, but this one was rooted to be fit with 4.1.2.
The phone bugged and hung in weird ways, so i thought to follow the steps into downgrading it to stock rom for her and see if that would help.
I am no expert, but since i have successfully rooted several phones and tablets earlier with no issues (its pretty straight forward when it works, right), i felt up for the tast.
I have spent a lot of time googling the last couple weeks, and reading a lot of solutions here on these forums, but i can't seem to find this ecact problem, so here goes.
Samsung Galaxy Beam GT.I8530
Odin3 v3.07
Windows 7 and 8 fully updated (tried both)
No matter which Android version i chose, it ends up at the same spot. Stuck at logo screen after first boot.
I have tried both with and without a PIT file, same result.
This last try was with a PIT and Android 4.1.2. (i understand that PIT is not nessessary, as it should be baked within the PDA if it's a single file, but what won't you try eventually, right?)
Load Odin, admin rights
Boot phone in download mode
Insert USB
-->
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8530DXLJ1_I8530OLBLJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.img.md5
<ID:0/003> NAND Write Start!!
<ID:0/003> hidden.img.md5
<ID:0/003> kernel.bin.md5
<ID:0/003> modem.bin.md5
<ID:0/003> system.img.md5
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
- here, the phone reboots and loads to logo screen *
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
- from here the phone wont nudge from the logo screen. can reboot, nothing new happens.
No other functions work, other than:
- volume down+home+power (download mode)
- power (boots to logo screen)
Thanks for reading! Hope someone feels up for the task
Edit: It might be vital information that the phone will uncharge the battery at logo screen eventually, even when connected to a computer. (5v output) But i believe this is common somehow.
Also, if i try and shut down the phone, it will reboot into a frozen "star icon".
Click to expand...
Click to collapse
I have The solution For that remove your battery and charge battery by use of another working mobile or battery charger box
after charging you do the flashing using android 4.1.2
it successfully works on my mobile
the problem is battery is low so that at the time of flashing it turned off ....so fill the battery and use......
Hi everyone,
My head is spinning from what's just happened. My phone mysteriously decided to crash on me after being a little slow and unresponsive recently. I'm running CM11 M5 on my phone, I found this is the most stable of the roms for me. The unusual thing about this crash was that it rebooted with a fuzzy, static-like screen, so I tried to reboot into the Cyanogen bootloader thingy and it just brings up the crash screen. I tried to reboot into Odin Mode, hooked up the phone to my computer and tried to reinstall a new ROM. First I tried with Odin 3.07 with a ROM I loaded onto it last month (I9300XXUGNA5_I9300AUTGNA1_I9300XXUGMK6_HOME.tar.md5), but the Odin program on the computer crashes each time. I also tried with an updated version of Odin, v1.85 and also Odin Auto. I had an issue last month, looked around and fixed it by downloading this ROM just mentioned, but this time, no joy. I've tried with another that I just downloaded (root66_TMO_T999UVDLJA.tar.md5) and the same thing happens. At one point, I received a message on different attempts where the Odin program would spit back at me this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDLJA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1
So, how do I proceed from this point? I don't know enough to understand what the problem is with this, maybe something to do with the PIT mapping? I feel like I've covered every possible avenue that I can see posted online, I'm really not sure if there is anyone else with this problem, where the Odin program is so volatile. Your thoughts would be greatly appreciated, I suffer without my phone.
Stuart
blackbeardtwenty said:
Hi everyone,
My head is spinning from what's just happened. My phone mysteriously decided to crash on me after being a little slow and unresponsive recently. I'm running CM11 M5 on my phone, I found this is the most stable of the roms for me. The unusual thing about this crash was that it rebooted with a fuzzy, static-like screen, so I tried to reboot into the Cyanogen bootloader thingy and it just brings up the crash screen. I tried to reboot into Odin Mode, hooked up the phone to my computer and tried to reinstall a new ROM. First I tried with Odin 3.07 with a ROM I loaded onto it last month (I9300XXUGNA5_I9300AUTGNA1_I9300XXUGMK6_HOME.tar.md5), but the Odin program on the computer crashes each time. I also tried with an updated version of Odin, v1.85 and also Odin Auto. I had an issue last month, looked around and fixed it by downloading this ROM just mentioned, but this time, no joy. I've tried with another that I just downloaded (root66_TMO_T999UVDLJA.tar.md5) and the same thing happens. At one point, I received a message on different attempts where the Odin program would spit back at me this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDLJA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1
So, how do I proceed from this point? I don't know enough to understand what the problem is with this, maybe something to do with the PIT mapping? I feel like I've covered every possible avenue that I can see posted online, I'm really not sure if there is anyone else with this problem, where the Odin program is so volatile. Your thoughts would be greatly appreciated, I suffer without my phone.
Stuart
Click to expand...
Click to collapse
Use this if it fails it needs service repair >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 <<
blackbeardtwenty said:
Hi everyone,
My head is spinning from what's just happened. My phone mysteriously decided to crash on me after being a little slow and unresponsive recently. I'm running CM11 M5 on my phone, I found this is the most stable of the roms for me. The unusual thing about this crash was that it rebooted with a fuzzy, static-like screen, so I tried to reboot into the Cyanogen bootloader thingy and it just brings up the crash screen. I tried to reboot into Odin Mode, hooked up the phone to my computer and tried to reinstall a new ROM. First I tried with Odin 3.07 with a ROM I loaded onto it last month (I9300XXUGNA5_I9300AUTGNA1_I9300XXUGMK6_HOME.tar.md5), but the Odin program on the computer crashes each time. I also tried with an updated version of Odin, v1.85 and also Odin Auto. I had an issue last month, looked around and fixed it by downloading this ROM just mentioned, but this time, no joy. I've tried with another that I just downloaded (root66_TMO_T999UVDLJA.tar.md5) and the same thing happens. At one point, I received a message on different attempts where the Odin program would spit back at me this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDLJA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1
So, how do I proceed from this point? I don't know enough to understand what the problem is with this, maybe something to do with the PIT mapping? I feel like I've covered every possible avenue that I can see posted online, I'm really not sure if there is anyone else with this problem, where the Odin program is so volatile. Your thoughts would be greatly appreciated, I suffer without my phone.
Stuart
Click to expand...
Click to collapse
Happened the same too me and i have CM11 too... If you get a fix contact me please
emnt said:
Happened the same too me and i have CM11 too... If you get a fix contact me please
Click to expand...
Click to collapse
Try the above rescue firmware as suggested above make sure you know what you are doing before flashing.. Exactly same advice if that doesn't work service required partition corrupt..Also I noticed the op above also flashed wrong root file for I9300 which didn't help.
blackbeardtwenty said:
The unusual thing about this crash was that it rebooted with a fuzzy, static-like screen,
Click to expand...
Click to collapse
Hardware issue, either damaged or corrupt emmc chip.
tallman43 said:
.Also I noticed the op above also flashed wrong root file for I9300 which didn't help.
Click to expand...
Click to collapse
Yeah, that was a desperate attempt at trying another root file which was recommended in another post. I initially used:
I9300XXUGNA5_I9300AUTGNA1_I9300XXUGMK6_HOME.tar.md5
and this worked fine last month, but now I'm back to square one again. Any ideas on other PIT files or root files I can download which might do the trick?
Thanks for your comments so far, you're all a bunch of wizards...
I've managed to screw the pooch and got the Yellow Triangle of Death for my efforts. This is a VZW Note 2 sch-i605 that had(has?) a rooted 4.4.2. I tried to get TWRP installed and... yellow triangle. OK, the bootloader's locked up tight.
How do I get back to 4.3? Odin works - that is, it sees the phone, tries to do a NAND write and... party over.
Would trying to get an AOSP ROM loaded help? Can I get Odin to do that? I have the SDK but I guess sideloading is a loss without recovery.
This is what a failure looks like on Odin 3.10.7:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
No matter what rev. of Odin, TWRP, CWM, or even I605VRUAND3_I605VZWAND3_I605VRUAND3_HOME.tar.md5 I use... FAIL. And it's always that NAND write.
What options do I have?
I'm happy to say I beat this problem with a stick. The process was brutally ugly but it worked out. It starts with this video from Root Junky: https://www.youtube.com/watch?v=4qtbEevn1VA. But things didn't quite work out. At the very end, the process tanked with, on the phone, a message saying "bad magic string". The good news is I didn't get the VZW Yellow Triangle of Death. I got the Kies or some Samsung utilities Yellow Triangle of Death. Out of simple desperation, I tried the same process seen in the video but... I used the ND7 file instead of the MC3 file. I kept the 16G.pit file (maybe I didn't need to repartition, maybe I did). And the who process passed, front to back. Even more amazing, my data is intact and so are the home screens. I did, however, lose root. I know how to root under ND7, so I'll do that next. And...
Root Checker gave me a scare and said the phone wasn't rooted. I had to install SuperSU first. The only thing this particular rooting process still doesn't do is install SuperSU and BusyBox. I can install them via Play Store, so it's not a real problem.
The procedure used to root at the end:
Originally Posted by NetworkingPro (*)
Everyone, please use this .zip from now on. Please test, and let me know how it goes. I have simplifed the root be a single click root method.
Steps:
Download and unzip file.
Connect phone, ensure usb debugging is on, and device is authorized.
Double click GhettoRoot.bat
Download - Attachment 2922670
In full disclosure I have no idea where the source for this came from, I just made it pretty, and tried to make it super easy. Credit goes to 25yvdgpo06 for finding it. This root very well may work any many other devices, including other Samsung devices. Looking at the source I dont see anything that should hurt another device. Worst case scenario it simply doesn't root it. Please let us know if you try another device with success.
Click to expand...
Click to collapse
Hey guys.
So. As of now, my phone is ****ed. I mean, not completely to the point where it's not working, but to a point that it still affects me. Let me explain my full situation though.
Essentially what started this off, is that I had no internet connection to the play store, and any of the apps associated with it, or downloaded from it. Tried a few things, but no cigar. Since my S6 is rooted, I figured something had went wrong (Note: There is no distinct cause of the connection issues, and I wasn't messing around with root stuff at the time of it happening). I factory reset my phone, and attempted booting it back up again.
From there, it seemed to be fine, until it wanted me to sign into a network. I logged into my router fine, but it could not complete the "Test Connection" stage, or whatever it is called exactly. It also cannot use the play store whatsoever now, and comes up with a "Cannot establish reliable server connection" message. Browser however, works fine. I dont know what to do from here, or to go about solving these issues.
If some way someone out there can guide me through this, I would be eternally grateful. Thank you so much.
-Fraser Nagle
I would start with reloading the original firmware via Odin, especially since you have already factory reset and don't need to worry about losing any data at this stage. Always best to get a fresh start and go from there. I would also reset the phone again after reloading.
es0tericcha0s said:
I would start with reloading the original firmware via Odin, especially since you have already factory reset and don't need to worry about losing any data at this stage. Always best to get a fresh start and go from there. I would also reset the phone again after reloading.
Click to expand...
Click to collapse
I tried flashing the firmware with Odin3 3.11, but it continues to fail. I have tried two computers now, as well as other USB ports and such. I have confirmed that I have the right .tar.md5 file for my phone. This is the log that shows up when I start the process:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1101)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Hope you can help me out. Thanks
-Fraser
That doesn't sound good. Could be bad internal memory. I found some info here http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096 but your phone might be different. The guys there might be able to provide more details on what to do.
es0tericcha0s said:
That doesn't sound good. Could be bad internal memory. I found some info here http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096 but your phone might be different. The guys there might be able to provide more details on what to do.
Click to expand...
Click to collapse
alright thanks, ill take a look.
es0tericcha0s said:
That doesn't sound good. Could be bad internal memory. I found some info here http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096 but your phone might be different. The guys there might be able to provide more details on what to do.
Click to expand...
Click to collapse
I took a look through that thread... I have no idea where to start. Although I a computer savy, Android and mobile devices is an entire new field to me. Is there any other indications that the NAND is the problem? Because besides the play store, everything else works fine.. Could it be the tar file? or something to do with the PIT? Let me know.
-Fraser
Edit: Never mind, its the same. I'm dumb.