Related
Hi i've had CM9 in my phone for a half year now without any issues, however two days ago i woke up and went to check my phone, it froze and after that i haven't been able to boot it up, it just hungs at the samsung logo with the triangle and all that, so i've been trying to sort out this for two days straight now and i'm getting really sick of this, what i've done so far is:
* tried to flash alot of rom's and such with no success, stucks at: NAND Write Start!!
* tried to flash on a different computer
* tried to flash with different usb ports
Oh and i can't get into the recovery mode, only the download mode.
This is the files i've tried to flash and such to get my phone working again:
Kernel_I9100XXLPH
I9100XXLPQ_I9100HTSLP3_HTS
I9100XWLPG_I9100XXLPX_I9100NEELP4_NEE
I9100XWLPG_I9100XXLPX_I9100NEELP4_HOME.tar
I9100XWLPG_I9100NEELP4_NEE
GT-I9100_Kernel_Gingerbread-supercurio-3
GT-I9100_ICS_ClockworkMod-Recovery_5.5.0.4
cm-10-20120927-EXPERIMENTAL-i9100-jb_mali-changmin
cm-10-20120926-NIGHTLY-i9100
cm-9-20120330-ODIN-galaxys2.tar
CF-Root-SGS2_XW_NEE_LPG-v5.5-CWM5
CF-Root-SGS2_XX_OXA_KP8-v5.2-CWM5
GT-I9100_NEE_I9100XWLPD_I9100XXLPW_I9100NEELP4
Please, can anyone try to help me? I can't explain how tired i am of this, i really need and want my phone to work again! Thanks
Emperia said:
Hi i've had CM9 in my phone for a half year now without any issues, however two days ago i woke up and went to check my phone, it froze and after that i haven't been able to boot it up, it just hungs at the samsung logo with the triangle and all that, so i've been trying to sort out this for two days straight now and i'm getting really sick of this, what i've done so far is:
* tried to flash alot of rom's and such with no success, stucks at: NAND Write Start!!
* tried to flash on a different computer
* tried to flash with different usb ports
Oh and i can't get into the recovery mode, only the download mode.
This is the files i've tried to flash and such to get my phone working again:
Kernel_I9100XXLPH
I9100XXLPQ_I9100HTSLP3_HTS
I9100XWLPG_I9100XXLPX_I9100NEELP4_NEE
I9100XWLPG_I9100XXLPX_I9100NEELP4_HOME.tar
I9100XWLPG_I9100NEELP4_NEE
GT-I9100_Kernel_Gingerbread-supercurio-3
GT-I9100_ICS_ClockworkMod-Recovery_5.5.0.4
cm-10-20120927-EXPERIMENTAL-i9100-jb_mali-changmin
cm-10-20120926-NIGHTLY-i9100
cm-9-20120330-ODIN-galaxys2.tar
CF-Root-SGS2_XW_NEE_LPG-v5.5-CWM5
CF-Root-SGS2_XX_OXA_KP8-v5.2-CWM5
GT-I9100_NEE_I9100XWLPD_I9100XXLPW_I9100NEELP4
Please, can anyone try to help me? I can't explain how tired i am of this, i really need and want my phone to work again! Thanks
Click to expand...
Click to collapse
try flashing a stockfirmware which comes with a .pit file and see
Sun90 said:
try flashing a stockfirmware which comes with a .pit file and see
Click to expand...
Click to collapse
Could you please help me out, i'm not really sure where i can find that.
Edit: I live in Sweden, Europe so i need a nordic firmware.
Emperia said:
Could you please help me out, i'm not really sure where i can find that.
Edit: I live in Sweden, Europe so i need a nordic firmware.
Click to expand...
Click to collapse
check the link below read the main post(#1) of that thread and proceed carefully to revive back ur phone
http://forum.xda-developers.com/showthread.php?t=1457458
Sun90 said:
check the link below read the main post(#1) of that thread and proceed carefully to revive back ur phone
http://forum.xda-developers.com/showthread.php?t=1457458
Click to expand...
Click to collapse
Thanks, i've read that guide earlier and tried a few steps with no luck.
Is this what i should do?
"WARNING : FLASHING A BOOTLOADER IS DANGEROUS. FLASH WITH EXTREME CAUTION.
8) Download the Bootloader. Flash it as PDA or Bootloader in ODIN. Without ticking Re-Partitioning
9) Flash the Kernel, as in step 5
10) Flash the recovery package, like in steps 1-4 And that will fix any of your issues "
Emperia said:
Thanks, i've read that guide earlier and tried a few steps with no luck.
Is this what i should do?
"WARNING : FLASHING A BOOTLOADER IS DANGEROUS. FLASH WITH EXTREME CAUTION.
8) Download the Bootloader. Flash it as PDA or Bootloader in ODIN. Without ticking Re-Partitioning
9) Flash the Kernel, as in step 5
10) Flash the recovery package, like in steps 1-4 And that will fix any of your issues "
Click to expand...
Click to collapse
no dont mess with that 'Bootloader' one ma8, there is one on how to use pit file look into that
look for this in that thread
Recovering a soft bricked phone
1) Grab the Recovery Package, and you'll see a bunch of .tar files. Take a look at the names. You'll see CODE, MODEM, CSC and .PIT. Put each one in its place.
2) Turn off your phone. Enter Download mode by presing Volume Down + Home + Power button.
3) Plug in your phone. It will show you, in a yellow box in ODIN, ID:COMx (x being the number displayed, sometimes displays 7, sometimes displays 9)
Now here, take a breath
First try flashing WITHOUT the .PIT and re-partition. And only if it DOESN'T WORK OR FIX then you flash with the .PIT and Re-Partition ticked.
4) Once ready and done all your prayers, press Start. Wait patiently. It usually takes 5 minutes to flash.
Have you done everything correctly until now? Then...
Congratulations on recovering your phone!
Sun90 said:
no dont mess with that 'Bootloader' one ma8, there is one on how to use pit file look into that
Click to expand...
Click to collapse
Hmm, well the only files i got when i downloaded the recovery package via that thread is:
MODEM_I9100XXLPH_REV_02_CL1104396.tar
I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar
I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar
GT-I9100-MULTI-CSC-OXALPH.tar
thanks for trying to help me, it's appreciated!
Emperia said:
Hmm, well the only files i got when i downloaded the recovery package via that thread is:
MODEM_I9100XXLPH_REV_02_CL1104396.tar
I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar
I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar
GT-I9100-MULTI-CSC-OXALPH.tar
thanks for trying to help me, it's appreciated!
Click to expand...
Click to collapse
did u dwnld'd that file under Gingerbread or ICS?
Sun90 said:
did u dwnld'd that file under Gingerbread or ICS?
Click to expand...
Click to collapse
The ICS one, is that wrong?
Emperia said:
The ICS one, is that wrong?
Click to expand...
Click to collapse
yes its correct, The ICS one is the right one for u
now follow the instruction over that thread for where to put those files in ODIN and flash the same
Sun90 said:
yes its correct, The ICS one is the right one for u
now follow the instruction over that thread for where to put those files in ODIN and flash the same
Click to expand...
Click to collapse
Alright, we'll see what happens, there is no pit file thought, correct?
Emperia said:
Alright, we'll see what happens, there is no pit file thought, correct?
Click to expand...
Click to collapse
its only needed in the worst case scenerio
Sun90 said:
its only needed in the worst case scenerio
Click to expand...
Click to collapse
Ah alright, so i should put all those files even the bootloader in odin and try to flash? Just making sure!
Emperia said:
Ah alright, so i should put all those files even the bootloader in odin and try to flash? Just making sure!
Click to expand...
Click to collapse
yes
ps- and remember that u r doing all this thing at ur own risk, do not complain in the Future if something goes wrong there
Sun90 said:
yes
Click to expand...
Click to collapse
This is what happens:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXLPH_REV_02_CL1104396.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXALPH.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> boot.bin
<ID:0/006> NAND Write Start!!
Emperia said:
This is what happens:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXLPH_REV_02_CL1104396.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXALPH.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> boot.bin
<ID:0/006> NAND Write Start!!
Click to expand...
Click to collapse
do u see a red 'fail' message in the big rectangle box in odin
Sun90 said:
do u see a red 'fail' message in the big rectangle box in odin
Click to expand...
Click to collapse
Nope, it just seems like it's stuck, this is what always happens, i never get fail messages or such.
Emperia said:
Nope, it just seems like it's stuck, this is what always happens, i never get fail messages or such.
Click to expand...
Click to collapse
which version of windows ur using is it XP or 7
Sun90 said:
which version of windows ur using is it XP or 7
Click to expand...
Click to collapse
Windows 7, i've tried to flash on windows xp as well, and it gets stuck too, no fail error.
Emperia said:
Windows 7, i've tried to flash on windows xp as well, and it gets stuck too, no fail error.
Click to expand...
Click to collapse
try to reflash using the PIT file att below, extract the file put it in the pit section on odin along with the other files in there respective section also check the re-partition and see
Hey guys, I know this is a topic that's gone over and over again, but I didn't want to hijack someone else's thread. First off, I don't know much about rooting phones, ODIN, ROMs, or any of that, so bear with me.
I rooted my Note II awhile back with ODIN (couldn't give you the specifics unless you want me to find the guide that led me through it). Everything worked fine up until I plugged my phone into my laptop and VZW upgrader decided to update my phone without my permission, and now it's stuck on the bootloop where all you see is the black screen with the Samsung logo popping up every second or so. I can access the custom ROM download screen though, so hopefully it can be fixed.
If possible, I would love to be able to keep all data on the phone (ironically enough, I was hooking it up to my PC to back it up when this happened).
Thank you in advance, and please be as noob-friendly as you can. Links to step-by-steps and pictures are appreciated.
Can you be a little more elaborate... Which rom you were having and what file you used in odin.... Which rom for installed on your mobile by verizon etc
Thanks,
Nikhil Dhand
Email : [email protected]
nikhil.kdhand said:
Can you be a little more elaborate... Which rom you were having and what file you used in odin.... Which rom for installed on your mobile by verizon etc
Thanks,
Nikhil Dhand
Email : [email protected]
Click to expand...
Click to collapse
How do I check? I can't remember exact details. I'll try to find the guide I used to root it.
I'm pretty sure it's stock ROM, though.
Go into download mode and see if you are able to find knox word anywhere.... What is the filename you used for casual
Thanks,
Nikhil Dhand
Email : [email protected]
nikhil.kdhand said:
Go into download mode and see if you are able to find knox word anywhere.... What is the filename you used for casual
Thanks,
Nikhil Dhand
Email : [email protected]
Click to expand...
Click to collapse
"NoYouVerizon-GalaxyNote2-CASUAL R515" I hope that's what you're looking for.
Please go into the download/odin mode and search for the word called knox.... Let me know if you are able to find it or not
Thanks,
Nikhil Dhand
Email : [email protected]
nikhil.kdhand said:
Please go into the download/odin mode and search for the word called knox.... Let me know if you are able to find it or not
Thanks,
Nikhil Dhand
Email : [email protected]
Click to expand...
Click to collapse
Okay, it says "KNOX WARRANTY VOID: 0"
The whole text on the download screen reads:
ODIN MODE
PRODUCT NAME: SCH-1605
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 0
RP SWREV: A2
The Verizon update was the latest. I'm not sure on details. I just plugged it in and VZW Software Upgrade Assistant started auto-upgrading.
Then you need to install stock 4.3 rom only and not any custom rom.... You may download the same and install it via odin
Thanks,
Nikhil Dhand
Email : [email protected]
nikhil.kdhand said:
Then you need to install stock 4.3 rom only and not any custom rom.... You may download the same and install it via odin
Thanks,
Nikhil Dhand
Email : [email protected]
Click to expand...
Click to collapse
Where can I download the 4.3 ROM and how do I install? I'm sorry. I wish I knew more about rooting and ROMs and such, but I'm a total noob when it comes to this. I greatly appreciate your help.
EDIT: I know I'm asking a lot of questions, but I just don't want to end up with an expensive paperweight. Any details are very appreciated.
Go to sammobile and download from firmware option.... Give your model number there.... Select the 4.3 rom from the list.... Download pit file and odin too....
Thanks,
Nikhil Dhand
Email : [email protected]
Here is a brief how-to:
1. download the Stock rom and odin.
2. Restart your phone. Before the phone has a chance to start hold the volume down key + home key + power key all at once. This takes you into download mode. Download screen opens press volume up key to get into download mode.
3. Open Odin and in the PDA slot: locate your Stock rom you downloaded and select it. Odin will verify it and you should see in left pain it saying it succeeded
4. Make sure only the checkboxes (on the left side) “Auto Reboot” and “F. Reset Time” are checked
5. click Start
This will install the stock rom. Phone will reboot and go into recovery mode then reboot again I believe, trying to recall that from memory.
If your phone gets into the Logo screen loop and wont load phone, Try this:
1. Download the Pit file for the phone – do a search on XDA and youll find it.
2. Put phone into download mode like stated above,
3. Open Odin
4. In the Pit slot locate your downloaded Pit file and select it.
5. Make sure “Auto Reboot” and “F. Reset Time” and “Re Partition” are checked
6. Click Start
Using the Pit file is used in rare cases and as a Last resort as it can cause your phone to Brick if it fails in the Flash process.
I assume no responsibility for you trying this and using this method I have mentioned. It has worked for me but may not for you.
I hope this helps
nikhil.kdhand said:
Go to sammobile and download from firmware option.... Give your model number there.... Select the 4.3 rom from the list.... Download pit file and odin too....
Thanks,
Nikhil Dhand
Email : [email protected]
Click to expand...
Click to collapse
Okay so I got the md5 file and tried to flash it, but it failed. I put it in the PDA section, let it load, checked the box, and clicked start, but it failed. So I tried again and now it's stuck on:
"<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUEMJ9_I605VZWEMJ9_I605VRUEMJ9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection.."
I restarted everything and tried again, but it still failed. Here's the log:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUEMJ9_I605VZWEMJ9_I605VRUEMJ9_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> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Werkshop712 said:
I restarted everything and tried again, but it still failed. Here's the log:
Click to expand...
Click to collapse
Make sure you are using the usb cable that came with the phone as alot of aftermarket cords dont work well for this type of procedure, if not available try another cord. Do this before flashing the pit file.
Download the Pit file, and run the pit file first. See if that works. You may also want to let the phone try and load and see if it works before doing the Rom flash.
If the pit file flashes then run Odin again and flash with the Rom image.
Success!!! The re-partition fixed it! I'm so happy to not have bricked my phone. Thank you to everyone who helped.
I think I'm gonna stay safe with stock phones for awhile, haha.
Oh, should I still flash the ROM? It seems to be working just fine after the re-partition. Could anything go wrong?
Werkshop712 said:
Oh, should I still flash the ROM? It seems to be working just fine after the re-partition. Could anything go wrong?
Click to expand...
Click to collapse
Awesome, I am glad you got it to work with the PIT file. In my experience as long as you can get the phone back up and running with the PIT file you are good to go. If you notice down the road that some instability issues occur you could flash back to rom, but at this point your good.
have a Great Holiday
---------- Post added at 06:04 AM ---------- Previous post was at 05:50 AM ----------
Oh I thought Id mention incase you hadnt noticed, you most likely lost root, not sure what you your needs of root are but if you do need root check the forums for rooting the new 4.3.
I did mine using a program that I never used before (wasnt from XDA) but it worked.
Big draw back in 4.3 is Wifi tethering now gets checked by verizon so it blocks third party widgets from working around it. There is a mod for that if you get 4.3 rooted but, I havent found the thread for mod yet on here, but it exists.
Amigahd said:
Here is a brief how-to:
1. download the Stock rom and odin.
2. Restart your phone. Before the phone has a chance to start hold the volume down key + home key + power key all at once. This takes you into download mode. Download screen opens press volume up key to get into download mode.
3. Open Odin and in the PDA slot: locate your Stock rom you downloaded and select it. Odin will verify it and you should see in left pain it saying it succeeded
4. Make sure only the checkboxes (on the left side) “Auto Reboot” and “F. Reset Time” are checked
5. click Start
This will install the stock rom. Phone will reboot and go into recovery mode then reboot again I believe, trying to recall that from memory.
If your phone gets into the Logo screen loop and wont load phone, Try this:
1. Download the Pit file for the phone – do a search on XDA and youll find it.
2. Put phone into download mode like stated above,
3. Open Odin
4. In the Pit slot locate your downloaded Pit file and select it.
5. Make sure “Auto Reboot” and “F. Reset Time” and “Re Partition” are checked
6. Click Start
Using the Pit file is used in rare cases and as a Last resort as it can cause your phone to Brick if it fails in the Flash process.
I assume no responsibility for you trying this and using this method I have mentioned. It has worked for me but may not for you.
I hope this helps
Click to expand...
Click to collapse
Dude, I can not thank you enough my phone has been like this for hours! Flashing the PIT fixed it! Thanks again.
Root Didn't Take But Showing Knox Trip & "Custom" Status [Sprint version 4.3 / MJ4]
Hello Experts! I am trying to root my phone but it seems rooting may only have 1/2 worked. First the details of my device:
Sprint Note 3 N900P
Android 4.3
Software N900PVPUBMJ4
I have used qbking77's tar.md5 [for Sprint] file in Odin but my phone isn't actually rooting. (this thread: http://forum.xda-developers.com/showthread.php?t=2474222)
Odin said pass; here's the report:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hltespr-hltespr-smn900p.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
After this, the phone gets stuck on the 'Recovery Booting / Recovery is not seandoroid enforcing / Set Warranty Bit Recovery' screen. Since I know patience is a virtue, I left it there (about 16 minutes) but it never went to the rooting screen. (the red android guy with the eye patch in his video)... I tried rebooting but all it would do is loop. I pulled the battery and then the volume down + home + power start and choose to boot normal so I am working, just not rooted.
I have tripped Knox and my device status is "custom." I have confirmed with Titanium Backup there is no root access.
If you must know, I'm rooting because I do NOT want KitKat and it seems rooting is the only way to avoid it.
How do I successfully complete the root?
Velocity_Yellow said:
Hello Experts! I am trying to root my phone but it seems rooting may only have 1/2 worked. First the details of my device:
Sprint Note 3 N900P
Android 4.3
Software N900PVPUBMJ4
I have used qbking77's tar.md5 [for Sprint] file in Odin but my phone isn't actually rooting. (this thread: http://forum.xda-developers.com/showthread.php?t=2474222)
Odin said pass; here's the report:
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
CF-Auto-Root-hltespr-hltespr-smn900p.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Added!!
Odin v.3 engine (ID:3)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
recovery.img
NAND Write Start!!
cache.img.ext4
RQT_CLOSE !!
RES OK !!
Removed!!
Remain Port .... 0
All threads completed. (succeed 1 / failed 0)
After this, the phone gets stuck on the 'Recovery Booting / Recovery is not seandoroid enforcing / Set Warranty Bit Recovery' screen. Since I know patience is a virtue, I left it there (about 16 minutes) but it never went to the rooting screen. (the red android guy with the eye patch in his video)... I tried rebooting but all it would do is loop. I pulled the battery and then the volume down + home + power start and choose to boot normal so I am working, just not rooted.
I have tripped Knox and my device status is "custom." I have confirmed with Titanium Backup there is no root access.
If you must know, I'm rooting because I do NOT want KitKat and it seems rooting is the only way to avoid it.
How do I successfully complete the root?
Click to expand...
Click to collapse
What version of Odin are you using? Some versions are hit and miss, try version 3.09 and see if that helps. Also, try from complete power off and then start into download mode and then plug into computer.
Sent from my SM-N900P using Tapatalk
tonyevo52 said:
What version of Odin are you using? Some versions are hit and miss, try version 3.09 and see if that helps. Also, try from complete power off and then start into download mode and then plug into computer.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
tonyevo52, we used Odin v. 3.07. We also powered off then booted into download mode, then plugged into the PC for our process. I read somewhere that Odin 3.09 didn't always play well with the Note3 so we were hesitant to try. Can anyone confirm/deny this? Any suggestions welcome and appreciated.
Anyone have any other suggestions? Or is this just a real stumper?
Velocity_Yellow said:
tonyevo52, we used Odin v. 3.07. We also powered off then booted into download mode, then plugged into the PC for our process. I read somewhere that Odin 3.09 didn't always play well with the Note3 so we were hesitant to try. Can anyone confirm/deny this? Any suggestions welcome and appreciated.
Click to expand...
Click to collapse
It's hit and miss, 3.07 didn't work for me and then I did all the same steps with 3.09 and worked like a charm.
Sent from my SM-N900P using Tapatalk
tonyevo52 said:
It's hit and miss, 3.07 didn't work for me and then I did all the same steps with 3.09 and worked like a charm.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
im having the same issue. 3.07 didnt work. 3.09 doesnt have pda but i selected the second option and still the same error
...............................................................................................
seem to work for me after i upgraded to KK
I'm still unsuccessful. I have tried these three things:
(1) Odin 3.09 -- still the same issue of bootloop.
(2) Odin 3.09 with Auto Reboot unchecked. Once Odin passed tried to force it into reboot manually... still won't go into recovery mode even with volume up + power + home... it goes into the the same bootloop "Recovery Booting / Recovery is not seandoroid enforcing / Set Warranty Bit Recovery" screen and NOT the manual recovery screen I've seen pictures of.
(2) Odin 3.09 with a newly downloaded tar file from chainfire [figuring maybe the original one was somehow corrupted]. Also had the phone set into to Airplane mode. Odin took ONE HOUR AND 20 MINUTES to pass, and STILL went into the "Recovery Booting / Recovery is not seandoroid enforcing / Set Warranty Bit Recovery" bootloop.
Also note: it seems every time we flash with Odin it takes at least double the amount of time as the previous flash. From everything we've read of Odin, there is no way it should be taking more than a few minutes... not over an hour. Why is this?
Long story short -- still not rooted.
Velocity_Yellow said:
I'm still unsuccessful. I have tried these three things:
(1) Odin 3.09 -- still the same issue of bootloop.
(2) Odin 3.09 with Auto Reboot unchecked. Once Odin passed tried to force it into reboot manually... still won't go into recovery mode even with volume up + power + home... it goes into the the same bootloop "Recovery Booting / Recovery is not seandoroid enforcing / Set Warranty Bit Recovery" screen and NOT the manual recovery screen I've seen pictures of.
(2) Odin 3.09 with a newly downloaded tar file from chainfire [figuring maybe the original one was somehow corrupted]. Also had the phone set into to Airplane mode. Odin took ONE HOUR AND 20 MINUTES to pass, and STILL went into the "Recovery Booting / Recovery is not seandoroid enforcing / Set Warranty Bit Recovery" bootloop.
Also note: it seems every time we flash with Odin it takes at least double the amount of time as the previous flash. From everything we've read of Odin, there is no way it should be taking more than a few minutes... not over an hour. Why is this?
Long story short -- still not rooted.
Click to expand...
Click to collapse
I have been also helping this person on this issue. The main issue seems the recovery file being installed is not working for this phone and bootloops when try to access recovery mode. After researching this issue it seems possible issues from phone using a older version of 4.3 and conflicts with Chainfire's latest CF-Root files (found in other postings and also by Chainfire himself on the parent CF-Root post). I have checked to see if there is historic archived older CF-Root file we could try but only find his newest. Does anyone have older version or another workaround. Thanks.
wolfnails said:
I have been also helping this person on this issue. The main issue seems the recovery file being installed is not working for this phone and bootloops when try to access recovery mode. After researching this issue it seems possible issues from phone using a older version of 4.3 and conflicts with Chainfire's latest CF-Root files (found in other postings and also by Chainfire himself on the parent CF-Root post). I have checked to see if there is historic archived older CF-Root file we could try but only find his newest. Does anyone have older version or another workaround. Thanks.
Click to expand...
Click to collapse
Here ya go boss.
All of these are at the Chainfire index site.
This is the one I used for MJ4.
https://www.dropbox.com/s/ktva4y3eevz6psd/CF-Auto-Root-hltespr-hltespr-smn900p.tar.md5
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
Here ya go boss.
All of these are at the Chainfire index site.
This is the one I used for MJ4.
https://www.dropbox.com/s/ktva4y3eevz6psd/CF-Auto-Root-hltespr-hltespr-smn900p.tar.md5
Click to expand...
Click to collapse
micmars, thank a bunch for the file; I have not tried it yet because i have an additional question... Anyone know why Odin seems to take so long? The timeframe seems to double with each use. The last [unsuccessful] attempt took 1 hour and 20 minutes. I'm worried another flash with your file will take much longer. Anyone have thoughts? Instead of 3.09, maybe try 3.07 again? Or....???
[Edited to add: As an FYI it's during the 'cache' part of the Odin process that seems to take the longest and where it hangs the longest.]
Hey guys. I've run into an issue with my GT-i9300 International version just yesterday at it's racking my brains up.
Here's the lowdown about the device
It's the international GTi9300 (3G version)
It runs ArchiDroid v2.1.4 ROM
This rom was installed a year ago and gave no issues what so ever.
Just yesterday the device did not boot up. i Managed to get it into philz recovery to see whats the problem. i get the error message that it couldnt mount /data, /system & etc.
I have posted the screenshots. I've tried backing up, mounting and even factory wiping but it does not work
I have a feeling the eMMC flash storage has failed and therefore i have a hardware failure :crying:
I hope this is not the case since i have lots of important data on this phone (it's my secondary phone)
Have a look at the screens. lemme know the fate of my S3, whether it is possible to recover this device or not
p.s: I've checked all over the net. i've only come across the /efs not mounting issue. not what im going through
Naweed Reza said:
Hey guys. I've run into an issue with my GT-i9300 International version just yesterday at it's racking my brains up.
Here's the lowdown about the device
It's the international GTi9300 (3G version)
It runs ArchiDroid v2.1.4 ROM
This rom was installed a year ago and gave no issues what so ever.
Just yesterday the device did not boot up. i Managed to get it into philz recovery to see whats the problem. i get the error message that it couldnt mount /data, /system & etc.
I have posted the screenshots. I've tried backing up, mounting and even factory wiping but it does not work
I have a feeling the eMMC flash storage has failed and therefore i have a hardware failure :crying:
I hope this is not the case since i have lots of important data on this phone (it's my secondary phone)
Have a look at the screens. lemme know the fate of my S3, whether it is possible to recover this device or not
p.s: I've checked all over the net. i've only come across the /efs not mounting issue. not what im going through
Click to expand...
Click to collapse
Have you flashed stock firmware with Odin yet? This is the first thing you need to do to see if Odin works or gives errors....don't forget to factory reset after flashing. I'm afraid you may have to live with losing your data if you can't back it up in recovery.
tallman43 said:
Have you flashed stock firmware with Odin yet? This is the first thing you need to do to see if Odin works or gives errors....don't forget to factory reset after flashing. I'm afraid you may have to live with losing your data if you can't back it up in recovery.
Click to expand...
Click to collapse
i'll try flashing the stock rom via odin
Yeah, now i gave up on caring about the data. i really need the phone to work tho
i'll get back on the progress
@tallman43
Status report.
I tried flashing a stock rom which is on 4.3
It says NAND write failure. screenshot uploaded.
So i'm guessing my eMMC is corrupt or has failed :crying:
I did more research and found out that i could repartition it using a .pit file
This thread shows the relevant pit files
http://forum.xda-developers.com/showthread.php?p=30547929#post30547929
GT-I9300_mx_20120220.pit is for the 16 gb s3.
i'll flash with with the ROM
Lemme know if this is alright :good:
Naweed Reza said:
@tallman43
Status report.
I tried flashing a stock rom which is on 4.3
It says NAND write failure. screenshot uploaded.
So i'm guessing my eMMC is corrupt or has failed :crying:
I did more research and found out that i could repartition it using a .pit file
This thread shows the relevant pit files
http://forum.xda-developers.com/showthread.php?p=30547929#post30547929
GT-I9300_mx_20120220.pit is for the 16 gb s3.
i'll flash with with the ROM
Lemme know if this is alright :good:
Click to expand...
Click to collapse
Be careful the thread is for verizon you can't flash any pit files from there be 100% sure the pit file is for S3 international try looking here this is the rescue firmware >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << there is a pit file in the 4.1.2 download but you need to flash the 4.3 in the link to stop efs issues. But to be honest it doesn't look too good if this fails I recommend a service repair.
tallman43 said:
Have you flashed stock firmware with Odin yet? This is the first thing you need to do to see if Odin works or gives errors....don't forget to factory reset after flashing. I'm afraid you may have to live with losing your data if you can't back it up in recovery.
Click to expand...
Click to collapse
Tried flashing the pit. I got the following error messages on odin
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGMK6_I9300OXAGMK6_I9300XXUGMK6_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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
tallman43 said:
Be careful the thread is for verizon you can't flash any pit files from there be 100% sure the pit file is for S3 international try looking here this is the rescue firmware >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << there is a pit file in the 4.1.2 download but you need to flash the 4.3 in the link to stop efs issues. But to be honest it doesn't look too good if this fails I recommend a service repair.
Click to expand...
Click to collapse
I had downloaded the pit from another site. it was the international one
But i'll try your link. i just saw your reply
I'm downloading the 4.3 GT-I9300XXUGMJ9_KOR_MULTI_FACTORY package
Naweed Reza said:
Tried flashing the pit. I got the following error messages on odin
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGMK6_I9300OXAGMK6_I9300XXUGMK6_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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You need to flash everything at once pit file and rom look at the link I sent you but it looks like you need a new motherboard:crying:
tallman43 said:
You need to flash everything at once pit file and rom look at the link I sent you but it looks like you need a new motherboard:crying:
Click to expand...
Click to collapse
Oh maan
Last resort is the link you gave. i'm downloading the 4.3 package. will put everything and flash at once. if this doest work. rip i guess :/
I never did anything. I installed the custom rom a year ago and let the phone be. didnt bother tweaking or adding to the custom rom
Then all of a sudden it doesnt boot
Naweed Reza said:
@tallman43
Status report.
I tried flashing a stock rom which is on 4.3
It says NAND write failure. screenshot uploaded.
So i'm guessing my eMMC is corrupt or has failed :crying:
I did more research and found out that i could repartition it using a .pit file
This thread shows the relevant pit files
http://forum.xda-developers.com/showthread.php?p=30547929#post30547929
GT-I9300_mx_20120220.pit is for the 16 gb s3.
i'll flash with with the ROM
Lemme know if this is alright :good:
Click to expand...
Click to collapse
I have a feeling the eMMC flash storage has failed and therefore i have a hardware failure
This is true
So flashing all 4 stock files (including pit) via odin turned out to be a Fail
I guess the eMMC is not functional resulting in a hardware failure
Thanks for the help @tallman43
If anyone else has suggestions, feel free to post them here
Dz-Horse said:
I have a feeling the eMMC flash storage has failed and therefore i have a hardware failure
This is true
Click to expand...
Click to collapse
Has this happened to your S3?
I havent tinkered with anything and this happens
I just installed a ROm and left it for a year
Oh well
Yes it happened to me same problem
Looks like the rollout today came in 2 updates. I downloaded the first and installed with no problem but the 2nd which actually puts in lolipop can't install. It says error 402, google/the Verizon forums doesn't have any info on it.
I have the same issue. I have tried Wifi and the Verizon Software Assistant download, and neither works. I am on the hunt for any suggestions as to how to get past this. Since I have just Factory Reset my phone, I will try pretty much anything.
I had 402 error. I downloaded I545VRUFNK1_I545VZWFNK1_I545VRUFNK1_HOME.tar from here:
http://forum.xda-developers.com/gal...-to-root-i545vrufnk1-4-4-2-12-1-2014-t2959613
Extract the .tar file
Install with Odin v3.09+ (put the .tar file in AP slot) and put phone in download mode
It will keep all data.
After reboot install both updates again.
do_9999 said:
I had 402 error. I downloaded I545VRUFNK1_I545VZWFNK1_I545VRUFNK1_HOME.tar from here:
http://forum.xda-developers.com/gal...-to-root-i545vrufnk1-4-4-2-12-1-2014-t2959613
Extract the .tar file
Install with Odin v3.09+ (put the .tar file in AP slot) and put phone in download mode
It will keep all data.
After reboot install both updates again.
Click to expand...
Click to collapse
were you able to root after the updates?
meazz1 said:
were you able to root after the updates?
Click to expand...
Click to collapse
Negative. But I knew that before.
If you're having trouble with the Odin portion of this, check to see if you're using USB 2.0 or USB 3.0 port. My issues seemed to be directly related to using 3.0. No idea why, or whether or not this is a known thing but I'm Odin-ing successfully right now. I'm leaving the "struggle" report in case it might help somebody who has gone through the same process unsuccessfully. Cheers
Followed the Odin instructions. Get a Fail. Using original cable. Here's the log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNK1_I545VZWFNK1_I545VRUFNK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
I made it to NK4 on the OTAs so maybe flashing NK1 won't work? Gonna try the NG6 and NK1 FULL WIPE Odin file. (found here: https://www.androidfilehost.com/?fid=95916177934540736)
The good news is that I can still get into download mode after a battery pull so I'm just going to try and find another Odin file.
Tried using a Pit file given there's no partition. Didn't work. Looks like I've got a morning of thread crawling to look forward to.
As crazy as this might sound, I found the answer for me on Verizon's actual forums from a Verizon customer service rep! That NEVER happens. I almost entirely dismissed it. He told someone asking about this problem, "If that doesn't work, the manufacturer has another way to install the update." I thought that sounding interesting. The link took me to Samsung Kies (an app for the PC) and there you have a choice to install either Kies or Kies3. For some reason it suggests we need Kies, but Kies3 is actually what we need as our S4's have been updated beyond when this site was created.
After installing that, the app TRIES to suggest that we're better off with Smart-something or other, but that's just for transferring contacts and such between two phones. Ignore that and just connect your phone via cable to the PC and Kies will see it and tell you there's an update. It then installed the update without a hitch!
What's amazing is that I also own a Samsung Galaxy Note Pro (the 12.2 inch tablet) that had some issues. However, it would never say there was any sort of update and I could never find one mentioned online. Kies said there was one and installed it. Now the tablet's snappier and better than ever. What a surprise find....
Agrajag27 - OMG, thank you very much! That worked, simple update, and I am on lollipop! Great find!