Hi All,
This is my first post. So, I apologize now if I don't do it correctly per forum requirements.
I have a U.S. T-Mobile Samsung Galaxy S3, which I've rooted. I updated to T999UVDMD5 via the method described here - http://forum.xda-developers.com/showthread.php?t=2282603. I'm running Android 4.3.1. I just updated to Cyanogenmod 10.2.1.
Everything is great operationally. However, after using this setup for several months, I just realized that my internal storage has decreased from 32GB to 12GB. I'm now getting insufficient storage messages. I don't know if this happened from the method referenced above or when I first rooted the phone as I haven't hit a wall with storage until now.
I've looked into this issue on the forum and think I might need to update my PIT file, but I'm not sure. I don't feel confident enough in this route to do it. So, I'm hoping someone can assist me with figuring out what is going on.
Please help. Thank you in advance for your time and assistance.
Internal memory may reduce due to several reasons. Pit files is just one of them.
The UVDMD5 Thread you posted is for Bootloader only. In order to clear up your issue, Please fhash Root66 via Odin. Follow this thread for details. Make sure to choose UVDMD5 version alone.
Once that's completed, flash latest recovery of your choice (either CWM or TWRP). Then flash CM version again.
Perseus71 said:
Internal memory may reduce due to several reasons. Pit files is just one of them.
The UVDMD5 Thread you posted is for Bootloader only. In order to clear up your issue, Please fhash Root66 via Odin. Follow this thread for details. Make sure to choose UVDMD5 version alone.
Once that's completed, flash latest recovery of your choice (either CWM or TWRP). Then flash CM version again.
Click to expand...
Click to collapse
Thank you for the prompt response. I've done as you said. However, Odin is hanging on aboot.mbn. I haven't touched it, but it's been like this for about five minutes. The phone still reads, "Downloading... Do not turn off target!!" What do you advise I do? Thanks again.
Keep the phone in downloading mode. Make sure your download of Root66 is valid. Follow the instructions from the thread I linked. Reboot computer and try another cable.
Perseus71 said:
Keep the phone in downloading mode. Make sure your download of Root66 is valid. Follow the instructions from the thread I linked. Reboot computer and try another cable.
Click to expand...
Click to collapse
Thank you Perseus71. I'll give this a shot tomorrow and get back to you. I appreciate your help.
Perseus71 said:
Keep the phone in downloading mode. Make sure your download of Root66 is valid. Follow the instructions from the thread I linked. Reboot computer and try another cable.
Click to expand...
Click to collapse
I went ahead and gave it a shot. I plugged the micro usb into a USB 3.0 port on the back of the machine instead of using one of the auxiliary ports on the front of my computer. That seemed to fixed the problem. I guess a direct connection with the motherboard makes a different. It flashed and I'm back up and running with the stock rom.
Quick question - I created a backup of my phone today. If I flash cyanogenmod back onto it, can I restore the phone from that backup? Or, is it no good now since I flashed it with root66?
Thank you so much!
Perseus71 said:
Keep the phone in downloading mode. Make sure your download of Root66 is valid. Follow the instructions from the thread I linked. Reboot computer and try another cable.
Click to expand...
Click to collapse
Update: I just checked and unfortunately I still have the 12gb of space. What do you recommend I do from here? Sorry. I hate to continue to bug you with this. Thank you.
If you took a Nandroid after the Root66 flash today, you can restore it anytime. As to the Space, its probably taken up by Samsung Bloat. Go ahead and flash CM. Make sure to do factory Reset, wipe Dalvik + Cache before and after the flash.
Check the space usage immediately after flash. Post a screen of Storage settings at the end.
Perseus71 said:
If you took a Nandroid after the Root66 flash today, you can restore it anytime. As to the Space, its probably taken up by Samsung Bloat. Go ahead and flash CM. Make sure to do factory Reset, wipe Dalvik + Cache before and after the flash.
Check the space usage immediately after flash. Post a screen of Storage settings at the end.
Click to expand...
Click to collapse
I know the term, but I'm not 100% confident in what you mean by Nandroid. So I will just explain what I did. Prior to flashing root66, I used CWM Recovery to create a backup file on my SD card.
I downloaded ROM Manager and re-installed CWM Recovery. I then rebooted into recovery and wipe all data, wiped the cache partition, and wiped the Dalvik Cache. Then, I restored the backup I created before I flashed root66.
Next, I rebooted the phone. It's still telling me I have 12 GB of internal memory. One thing that is different from before is I have about 9GB of free space now versus roughly 1GB of free space before. I've attached a screenshot of this.
Another issue I am having, which I had before is I'm getting an insufficient storage message when I try to install certain apps. What's weird is the error doesn't come up with all apps, only certain ones. I've attached a screenshot of this error message as well. Lastly, I put a screenshot of part of my partition table in case you are able to see something I'm not, in there.
If you have any other thoughts on what might be going on, I would greatly appreciate your insight. Thank you.
What you did in CWM is the Nandroid. I didn't want you to restore anything before flashing Root66. So please can you wipe everything again and then flash Root66 ? This time don't flash CWM after Root66. Just check the Spaces.
P.S. - Continue using the phone in that fashion (Just Root66 nothing custom). For now at least.
Perseus71 said:
What you did in CWM is the Nandroid. I didn't want you to restore anything before flashing Root66. So please can you wipe everything again and then flash Root66 ? This time don't flash CWM after Root66. Just check the Spaces.
P.S. - Continue using the phone in that fashion (Just Root66 nothing custom). For now at least.
Click to expand...
Click to collapse
Sorry, I may have miscommunicated. I restored the Nandroid after I flashed root66. I did check the internal memory space before I restored the Nandroid and it hadn't changed. I'll flash root66 again and get back to you. Please standby. Thank you.
If it still continues to be the case, this post has correct .PIT file. You use Odin to flash it. I think you know that already.
Perseus71 said:
If it still continues to be the case, this post has correct .PIT file. You use Odin to flash it. I think you know that already.
Click to expand...
Click to collapse
Thanks Perseus71! I'm on a new computer today. So I'm downloading root66 again so I can flash it. If the issue remains, I'll flash the PIT file. I downloaded the file at the link you sent me.
Do you by chance know of a good tutorial on flashing the PIT. I presume it's the same process with flashing anything and I use the PIT button on Odin. However, I'm paranoid that I'll brick my phone and prefer to be over cautious than presumptuous. Thank you sir!
And the saga continues... man this is frustrating!
I flashed root66 and checked the storage in settings. It's still at 12GB.
So, I did some digging on flashing the PIT file. Everything I read said to accompany the PIT file with the ROM. So, I rebooted into download mode, then plugged in the micro-USB, and Odin recognized the device. I unzipped the PIT file on my computer. I then clicked the PIT button on Odin and selected the PIT file on my machine. Next, I added the root66 ROM via the PDA button on Odin. Then, I clicked the Re-Partition checkbox so that the Auto-Reboot, Re-Partition, and F. Reset Time checkboxes were all checked. I hit start and then Odin failed on me.
Here's what Odin said:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDMD5.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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> __Xmit Write fail
<ID:0/004> Removed!!
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Am I doing something wrong here? Please help. Thank you again for your time and assistance.
Perseus71 said:
If it still continues to be the case, this post has correct .PIT file. You use Odin to flash it. I think you know that already.
Click to expand...
Click to collapse
I think I may have really screwed up. Ever since Odin failed on the re-partition, it is no longer recognizing my device. When I go into "Devices and Printers" in Windows 8, it's no longer displaying SGH-T999. Now it's displaying "Qualcomm HS-USB QDLoader 9008 (COM7)"
I'm afraid I just bricked my phone. I hope you have better news for than this. Please help when you can. Thank you.
Do All of the same above but do not hit Re-partition. Here's a good Guide. Make sure you have latest Odin ( v3.09) and its running as Admin on Windows.
Perseus71 said:
Do All of the same above but do not hit Re-partition. Here's a good Guide. Make sure you have latest Odin ( v3.09) and its running as Admin on Windows.
Click to expand...
Click to collapse
Ok. Good news. I was afraid to reboot the phone from the Download mode after Odin failed (for fear that I might not be able to get back into Download mode). However, I did reboot it, and the phone rebooted fine into Touchwiz (courtesy of root66). My computer then recognized the device as SGH-T999 once again. (Thank you Jesus!)
So, I have now rebooted back into download mode. I've download Odin v3.09 as you suggested (was using v3.07 before). I've selected the PIT file and root66 (via Odin's rebranded AP button). However, when I select the PIT file, Odin automatically checks the Re-Partition checkbox. You told me not to check that this time. Stupid question but should I just uncheck it?
I haven't done anything yet as I'm now terrified after the last experience of venturing out on my own. Waiting on your guidance. Thank you again.
Perseus71 said:
Do All of the same above but do not hit Re-partition. Here's a good Guide. Make sure you have latest Odin ( v3.09) and its running as Admin on Windows.
Click to expand...
Click to collapse
Update: I figured it was relatively low risk to uncheck Re-Partition so I went ahead and un-checked it and flashed the PIT and ROM. It succeeded. The phone booted normally. I reboot into recovery, did a factory wipe and wiped the cache partition; then reboot.
Total space is still reading 11.95GB. Although, apps do appear to be installing fine. So that issue is resolved.
I discovered an interesting piece of information. I downloaded the app Partition Table and was able to get a picture of the internal memory card (see "mmcblk0"). It says it's "unmounted." See the attached screen shot.
Any ideas on where to go from here?
If you are up to it, get a Root Explorer such as ES File Explorer. Make sure to turn on its Root Features. (That requires granting Root Access to it.)
Now go to /Proc folder. You will see 2 files. Mounts and Partitions. Post them here please.
Also see if you CWM can mount all partitions.
Perseus71 said:
If you are up to it, get a Root Explorer such as ES File Explorer. Make sure to turn on its Root Features. (That requires granting Root Access to it.)
Now go to /Proc folder. You will see 2 files. Mounts and Partitions. Post them here please.
Also see if you CWM can mount all partitions.
Click to expand...
Click to collapse
Thanks man. I'm on it, but I'll have to get back to you tomorrow. I really appreciate your continued guidance. Talk to you soon.
Related
Hi All,
I've searched through the forums for answers to my particular problem but haven't found anything that's worked bla bla bla... you guys go through a lot of this every day, don't you? I honestly have been scouring the web, looking for answers to my problem (I'm a member on other, unrelated forums and I know how annoying lazy noobs can be) but I only found a single response in a single thread that might be helpful (but I'll get back to that at the end).
Here's a brief history of my failure, followed by my problem:
1. Tried rooting with motochopper, it installed Superuser but SU didn't work properly (kept going off about updating binary but would always shoot back errors when I tried to update) and Rootchecker said phone wasn't rooted.
2. Tried rooting via Odin, I don't remember exactly what happened (it's been hours since this happened) but I ended up with a failure notice halfway through the download, I read somewhere to pull the battery so I did. Waited a minute, plugged it back in, now the phone won't boot (I get a "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" error), and it gives me the same error message if I try to boot to recovery mode, but I can still boot to download mode.
3. At this point, I figured I'd screwed the pooch and should flash the original, stock Samsung ROM back on to the phone and start from scratch. (I don't have a backup file but I've only had the phone for two days, I don't care if I lose personal data).
4. Downloaded the 1.6 GB stock ROM zip file.
5. Deleted temporary files, restarted computer, booted phone into download mode, opened Odin, loaded the ROM .tar file into the PDA slot of Odin (left all the Odin settings as they were).
6. Connected phone to computer, blue light from Odin (this means it added the device if I understand correctly).
7. Started Odin, download failed. Here's the transcript from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
I hit start again, another failure. Transcript:
<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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
So do I need to flash a new PIT partition? The one relevant thread (http://forum.xda-developers.com/showthread.php?t=2320066&highlight=partition+file) says that the PIT information is imbedded in the tar file, why isn't Odin reading it correctly?
I'm very new to the realm of Android and Linux, I've been trying to learn the basics about rooting, kernels, ROMs, etc. over the last few days to better understand how to fix these problems on my own. But I haven't found anything that will fix this. Thanks to anyone and everyone who answers, I'll make you cookies.
I'm not joking, if you live in or around the San Francisco bay area and you help me fix this, I'll deliver cookies, donuts, brownies, etc.
Read my second post on that thread. PIT information is stored in the Odin file. Get the download from Sammobile.com
Sent from my SGH-M919 using Tapatalk 2
re: pit file
WetbehindEars said:
Hi All,
I've searched through the forums for answers to my particular problem but haven't found anything that's worked bla bla bla... you guys go through a lot of this every day, don't you? I honestly have been scouring the web, looking for answers to my problem (I'm a member on other, unrelated forums and I know how annoying lazy noobs can be) but I only found a single response in a single thread that might be helpful (but I'll get back to that at the end).
Here's a brief history of my failure, followed by my problem:
1. Tried rooting with motochopper, it installed Superuser but SU didn't work properly (kept going off about updating binary but would always shoot back errors when I tried to update) and Rootchecker said phone wasn't rooted.
2. Tried rooting via Odin, I don't remember exactly what happened (it's been hours since this happened) but I ended up with a failure notice halfway through the download, I read somewhere to pull the battery so I did. Waited a minute, plugged it back in, now the phone won't boot (I get a "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" error), and it gives me the same error message if I try to boot to recovery mode, but I can still boot to download mode.
3. At this point, I figured I'd screwed the pooch and should flash the original, stock Samsung ROM back on to the phone and start from scratch. (I don't have a backup file but I've only had the phone for two days, I don't care if I lose personal data).
4. Downloaded the 1.6 GB stock ROM zip file.
5. Deleted temporary files, restarted computer, booted phone into download mode, opened Odin, loaded the ROM .tar file into the PDA slot of Odin (left all the Odin settings as they were).
6. Connected phone to computer, blue light from Odin (this means it added the device if I understand correctly).
7. Started Odin, download failed. Here's the transcript from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
I hit start again, another failure. Transcript:
<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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
So do I need to flash a new PIT partition? The one relevant thread (http://forum.xda-developers.com/showthread.php?t=2320066&highlight=partition+file) says that the PIT information is imbedded in the tar file, why isn't Odin reading it correctly?
I'm very new to the realm of Android and Linux, I've been trying to learn the basics about rooting, kernels, ROMs, etc. over the last few days to better understand how to fix these problems on my own. But I haven't found anything that will fix this. Thanks to anyone and everyone who answers, I'll make you cookies.
I'm not joking, if you live in or around the San Francisco bay area and you help me fix this, I'll deliver cookies, donuts, brownies, etc.
Click to expand...
Click to collapse
Never flash a .pit file, it contains the partition information for your phone.
It is also a sure way to end up with a shiny brick.
You wrote an lot of specifics but you forgot to say if your phone can get into cwm or twrp recovery?
Do you have a cwm/twrp flashable custom rom zip file on your sdcard in your phone?
An other question have you recently flashed any AOSP/AOKP/CM/MIUI roms?
If you don't, download the wicked v3 custom rom from this forum for your M919 Tmobile S4 phone.
What happens if you do a full wipe in cwm/twrp recovery and afterwards flash a cwm/twrp flashable zip file custom rom?
Be sure to do a full wipe which includes Factory Reset, Wipe System, Wipe Cache and Wipe Dalvik Cache before flashing.
If you do all these things there is a good chance your phone will work properly and then afterwards if you still want to
Odin flash the stock un-rooted firmware which you were trying to flash it most likely will be successful.
Good luck!
Misterjunky said:
Never flash a .pit file, it contains the partition information for your phone.
It is also a sure way to end up with a shiny brick.
You wrote an lot of specifics but you forgot to say if your phone can get into cwm or twrp recovery?
Do you have a cwm/twrp flashable custom rom zip file on your sdcard in your phone?
An other question have you recently flashed any AOSP/AOKP/CM/MIUI roms?
If you don't, download the wicked v3 custom rom from this forum for your M919 Tmobile S4 phone.
What happens if you do a full wipe in cwm/twrp recovery and afterwards flash a cwm/twrp flashable zip file custom rom?
Be sure to do a full wipe which includes Factory Reset, Wipe System, Wipe Cache and Wipe Dalvik Cache before flashing.
If you do all these things there is a good chance your phone will work properly and then afterwards if you still want to
Odin flash the stock un-rooted firmware which you were trying to flash it most likely will be successful.
Good luck!
Click to expand...
Click to collapse
Sorry, I should have mentioned all of that...
As far as I know, I cannot enter into any type of recovery... the only thing that's working right now is download mode, no other button combinations work (volume up+home+on gives me the "Firmware upgrade encountered an issue" story, same with volume up+volume down+power). So I have no way of doing a wipe, unless there's something else I can do. Is there a way I can wipe the phone remotely, from my computer?
A couple other specifics that I should have mentioned in OP:
This phone is only five days old and has not be rooted or modded at all up until yesterday.
I've never put an SD card into the phone (though I have one handy, if there's something I need to do that requires one).
elesbb said:
Read my second post on that thread. PIT information is stored in the Odin file. Get the download from Sammobile.com
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Vielen Dank, elesbb... I went to sammobile.com and started the download, but when I clicked through to the download server, it was the exact same file (from the exact same server) that I had just downloaded... So I have the sammobile file, I think the issue is that I need to wipe the phone before I flash it but I have no way of wiping it (that I am aware of).
Thank you both for your time and energy!
Restart your phone and computer. Try a different USB cable or usb port and see if odin will work. I've seen so many times problems because of a usb cable. And no, I wouldn't use a PIT file. Just the PDA tar.
Then you can use CF-Auto-Root to root or follow these instructions to root the MDL build.
Atmazzz said:
Restart your phone and computer. Try a different USB cable or usb port and see if odin will work. I've seen so many times problems because of a usb cable. And no, I wouldn't use a PIT file. Just the PDA tar.
Then you can use CF-Auto-Root to root or follow these instructions to root the MDL build.
Click to expand...
Click to collapse
Thanks, I haven't tried a different usb port... I'll try that when I get home. The USB cable I'm using is the brand new Samsung cable that came with the phone, I don't think it's the problem but I'll give it a try anyway.
Thanks!
Edit:
After some more digging, I think I might have NAND rw corruption issues (since I can boot into download mode but not into any kind of recovery/bootloader mode). I get this notion from reading http://forum.xda-developers.com/showthread.php?t=1457458, which isn't for the GS4 but I figure it's probably a good diagnostic tool for both. In the thread, Phistachio says that reflashing the kernel (and if that fails, the bootloader) will fix the problem. Will this fix the problem for the GS4 as well?
At this point, I will try a different USB port and/or cable and if that fails, I'll try reflashing the kernel.
Does that sound good?
WetbehindEars said:
Vielen Dank, elesbb... I went to sammobile.com and started the download, but when I clicked through to the download server, it was the exact same file (from the exact same server) that I had just downloaded... So I have the sammobile file, I think the issue is that I need to wipe the phone before I flash it but I have no way of wiping it (that I am aware of).
Thank you both for your time and energy!
Click to expand...
Click to collapse
You make sure it wasn't a bad download? Check md5. I've had failed Odin's before. Just had to keep trying. I also unchecked "f reset time" when I flash. Also, try "wipe nand" option. I'd Google that first though.
Sent from my SGH-M919 using Tapatalk 2
elesbb said:
You make sure it wasn't a bad download? Check md5. I've had failed Odin's before. Just had to keep trying. I also unchecked "f reset time" when I flash. Also, try "wipe nand" option. I'd Google that first though.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
This might be revealing my noobness a bit too much, but I'm not sure how to check md5 :/
I'll research the "wipe nand" option, might be worth a shot...
Is there anywhere I can download the stock SGH-M919 kernel?
Thanks again for all the help!
re: cable, usb port, drivers
WetbehindEars said:
This might be revealing my noobness a bit too much, but I'm not sure how to check md5 :/
I'll research the "wipe nand" option, might be worth a shot...
Is there anywhere I can download the stock SGH-M919 kernel?
Thanks again for all the help!
Click to expand...
Click to collapse
Why would you want to download the kernel?
The kernel is in the TAR file which you were trying to odin flash.
Best bet, try different cable, different usb port and it might even be a good idea if you go to the
Samsung USA website and download the latest usb drivers too.
If you do download the drivers, be sure to uninstall ALL samsung drivers, kies or any other Samsung
utility you have installed before installing the new samsung usb drivers.
I can tell you this for sure, if you cannot flash the stock firmware using Odin with your phone
you will need to take it to a Tmobile store and get it exchanged.
You should have no problem exchanging it since it's only 5 days old and you have not even
rooted it or flashed any custom firmwares to it.
Good luck!
Misterjunky said:
Why would you want to download the kernel?
The kernel is in the TAR file which you were trying to odin flash.
Best bet, try different cable, different usb port and it might even be a good idea if you go to the
Samsung USA website and download the latest usb drivers too.
If you do download the drivers, be sure to uninstall ALL samsung drivers, kies or any other Samsung
utility you have installed before installing the new samsung usb drivers.
I can tell you this for sure, if you cannot flash the stock firmware using Odin with your phone
you will need to take it to a Tmobile store and get it exchanged.
You should have no problem exchanging it since it's only 5 days old and you have not even
rooted it or flashed any custom firmwares to it.
Good luck!
Click to expand...
Click to collapse
Why would I want to download the kernel, you ask? I'll tell you why! Because I'm an Android infant and I have no idea what I'm doing!
It was because I was reading on an un-soft-brick how-to for a different phone and it mentioned flashing the kernel. But as you mentioned, it was completely unnecessary.
Last night, I made sure I was straight on the driver front (updated drivers, no Kies, etc.) and double checked the tar file I downloaded... the one thing I didn't do that I should have was plug my phone directly into my laptop; I only have one functioning USB port at the moment and it's occupied by a cooling fan. But the cooling fan has a USB port in it that I run my mouse through and it works fine, that's what I've had my phone plugged into during this whole process. Just plugged it directly into PC, ran Odin, worked flawlessly. I feel like an idiot for going through the fan, but the relief that came from seeing my S4 boot properly made up for it.
Thanks everyone for your help and attention, I know it's annoying getting inundated by greenhorns who need direction and I appreciate that you would be willing to help us get on our feet.
Thanks!
WetbehindEars said:
Why would I want to download the kernel, you ask? I'll tell you why! Because I'm an Android infant and I have no idea what I'm doing!
It was because I was reading on an un-soft-brick how-to for a different phone and it mentioned flashing the kernel. But as you mentioned, it was completely unnecessary.
Last night, I made sure I was straight on the driver front (updated drivers, no Kies, etc.) and double checked the tar file I downloaded... the one thing I didn't do that I should have was plug my phone directly into my laptop; I only have one functioning USB port at the moment and it's occupied by a cooling fan. But the cooling fan has a USB port in it that I run my mouse through and it works fine, that's what I've had my phone plugged into during this whole process. Just plugged it directly into PC, ran Odin, worked flawlessly. I feel like an idiot for going through the fan, but the relief that came from seeing my S4 boot properly made up for it.
Thanks everyone for your help and attention, I know it's annoying getting inundated by greenhorns who need direction and I appreciate that you would be willing to help us get on our feet.
Thanks!
Click to expand...
Click to collapse
Glad everything is working great! It was probably just a bad flash through odin. They happen from time to time. I am also wondering now if the USB on the cooling fan didn't have enough juice to fully power the whole process?
elesbb said:
Glad everything is working great! It was probably just a bad flash through odin. They happen from time to time. I am also wondering now if the USB on the cooling fan didn't have enough juice to fully power the whole process?
Click to expand...
Click to collapse
Yeah, the USB was probably already busy powering the fan and didn't want any of my Odin nonsense.
Thanks again for all the help!
(noob).....So i was running TWRP with paranoid android3 on my sprint s3 an accidentally flashed the wrong Google app zip with goo manager an ended up formatting my rom , internal storage and right now i have no OS installed....the only thing that's running is team win recovery project & pretty much don't know where to go from there. Also i can access my phone still thro the external sd card still. A little insight would be nice so i know what my next move should be.
SoReckless said:
(noob).....So i was running TWRP with paranoid android3 on my sprint s3 an accidentally flashed the wrong Google app zip with goo manager an ended up formatting my rom , internal storage and right now i have no OS installed....the only thing that's running is team win recovery project & pretty much don't know where to go from there. Also i can access my phone still thro the external sd card still. A little insight would be nice so i know what my next move should be.
Click to expand...
Click to collapse
Download new rom, Toss on extrnal SD, Flash in TWRP, and your alive and kicking once more. (TWRP has mount SD option so you can add to SD card from there) You'll be up and running in no time.
Only bad thing is all the pics and what nots (If not previously backed up) are gone. So it's a good thing to make a backup in TWRP after flashing and getting setup Just in case (Save to External SD)
milky1112 said:
Download new rom, Toss on extrnal SD, Flash in TWRP, and your alive and kicking once more. (TWRP has mount SD option so you can add to SD card from there) You'll be up and running in no time.
Only bad thing is all the pics and what nots (If not previously backed up) are gone. So it's a good thing to make a backup in TWRP after flashing and getting setup Just in case (Save to External SD)
Click to expand...
Click to collapse
You beat me to it. I was gonna say this.
Just a heads up, I invested in aa 16 gig sdcard and I love it. Every few weeks I will transfer what I need from internal over and completely wipe it so it doesn't take too much space. Keep everything on SD card and if needed, a computer.
Sorry if you lost your stuff. but at least you can recover. This has happened to me before too, trust me.
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!
Whiplashh said:
You beat me to it. I was gonna say this.
Just a heads up, I invested in aa 16 gig sdcard and I love it. Every few weeks I will transfer what I need from internal over and completely wipe it so it doesn't take too much space. Keep everything on SD card and if needed, a computer.
Sorry if you lost your stuff. but at least you can recover. This has happened to me before too, trust me.
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!
Click to expand...
Click to collapse
It's all good. Just wanna ensure folks are getting help. And OP we can't stress the important of a good backup on standby keep on your SD, Your computer, Wherever you want. just for reasons like this. It's always good to have one if you don't like what you flashed after.. Quick and easy to get it back to normal on the fly!
milky1112 said:
Download new rom, Toss on extrnal SD, Flash in TWRP, and your alive and kicking once more. (TWRP has mount SD option so you can add to SD card from there) You'll be up and running in no time.
Only bad thing is all the pics and what nots (If not previously backed up) are gone. So it's a good thing to make a backup in TWRP after flashing and getting setup Just in case (Save to External SD)
Click to expand...
Click to collapse
So I did what you said & the only thing that happens is TWRP resets & that it i put cm-10.1-20130728-NIGHTLY-d2spr on my ex sd card & tried to flash but thats all that happens
SoReckless said:
So I did what you said & the only thing that happens is TWRP resets & that it i put cm-10.1-20130728-NIGHTLY-d2spr on my ex sd card & tried to flash but thats all that happens
Click to expand...
Click to collapse
So it's just rebooting back to TWRP after rom finishes flashing? May just try to odin back to stock and start over again if you can't get it to play nice. Typically just doing factory wipe, clearing caches, flashing new rom will boot it back up, Unless the flash failed.
milky1112 said:
So it's just rebooting back to TWRP after rom finishes flashing? May just try to odin back to stock and start over again if you can't get it to play nice. Typically just doing factory wipe, clearing caches, flashing new rom will boot it back up, Unless the flash failed.
Click to expand...
Click to collapse
So Ive come to a conclusion last night. I have soft brick myself & now TWRP isnt coming up anymore. So my question is how do i reset the flash counts without an os?
SoReckless said:
So Ive come to a conclusion last night. I have soft brick myself & now TWRP isnt coming up anymore. So my question is how do i reset the flash counts without an os?
Click to expand...
Click to collapse
Odin back to stock and start from Square one. (Provided you can get into download mode) This won't reset the flash counter, but will get you going again to re root and flash something new =)
milky1112 said:
Odin back to stock and start from Square one. (Provided you can get into download mode) This won't reset the flash counter, but will get you going again to re root and flash something new =)
Click to expand...
Click to collapse
Ive researched & came across this
http://forum.xda-developers.com/showthread.php?t=1840030 ([HOW-TO] Unbrick your soft bricked Galaxy S III (+ bootloader brick)
I follow the instruction to the "T" but when i try to flash the VRALEC bootchain in the PDA i get this log
<ID:0/005> Added!!
<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> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
SoReckless said:
Ive researched & came across this
http://forum.xda-developers.com/showthread.php?t=1840030 ([HOW-TO] Unbrick your soft bricked Galaxy S III (+ bootloader brick)
I follow the instruction to the "T" but when i try to flash the VRALEC bootchain in the PDA i get this log
<ID:0/005> Added!!
<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> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try flashing a 100% stock rom see if it will take. 9 out of 10 times.. It'll work (Don't believe it's soft bricked with it not going to recovery.. which is a good thing. Giver a shot and lemme know.
milky1112 said:
Try flashing a 100% stock rom see if it will take. 9 out of 10 times.. It'll work (Don't believe it's soft bricked with it not going to recovery.. which is a good thing. Giver a shot and lemme know.
Click to expand...
Click to collapse
So I found out that hyperlink was for Verizon & not sprint. But also found this video that QBKing did with (unroot / unbrick) method the s3 a an hours ago. Downloading the tar. file now hopefully I can flash back to stock that way but if not ill pm to see if it anything else I can do
Disk Digger is a handy tool I've used to recover deleted photos after I flash a new rom. It totally works with overwhelming results but you just have to make sure you HAVE NOT TAKEN any new pictures since you erased your important ones.
Help sir!!!
Whiplashh said:
You beat me to it. I was gonna say this.
Just a heads up, I invested in aa 16 gig sdcard and I love it. Every few weeks I will transfer what I need from internal over and completely wipe it so it doesn't take too much space. Keep everything on SD card and if needed, a computer.
Sorry if you lost your stuff. but at least you can recover. This has happened to me before too, trust me.
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!
Click to expand...
Click to collapse
SIR!
What am I gonna do if I have the same problem with no available External SD.
My Device is a Google Nexus 7 (2012) ver Wifi Only
Thank you for the help
ironxsloth said:
SIR!
What am I gonna do if I have the same problem with no available External SD.
My Device is a Google Nexus 7 (2012) ver Wifi Only
Thank you for the help
Click to expand...
Click to collapse
Try going to the nexus 7 forum.
internal sd
milky1112 said:
Download new rom, Toss on extrnal SD, Flash in TWRP, and your alive and kicking once more. (TWRP has mount SD option so you can add to SD card from there) You'll be up and running in no time.
Only bad thing is all the pics and what nots (If not previously backed up) are gone. So it's a good thing to make a backup in TWRP after flashing and getting setup Just in case (Save to External SD)
Click to expand...
Click to collapse
i have an internal sd card in xperia s plz help
(noob).....So i was running TWRP with paranoid android3 on my sprint s4 mini an accidentally flashed the wrong Google app zip with goo manager an ended up formatting my rom , internal storage and right now i have no OS installed....the only thing that's running is team win recovery project & pretty much don't know where to go from there. Also i can access my phone still thro the external sd card still. A little insight would be nice so i know what my next move should b
ive done the exact same thing deleted internal storage and have no OS installed i have a Ascend P7 L10 where can i get the recommended firmware and stuff i need (noob here also) it runs android 4.4.2 with emui 2.3
JAA FEEEL said:
ive done the exact same thing deleted internal storage and have no OS installed i have a Ascend P7 L10 where can i get the recommended firmware and stuff i need (noob here also) it runs android 4.4.2 with emui 2.3
Click to expand...
Click to collapse
can flashing a zip file of the exact firmware work?
I havent got an SD card as I'm using the Samsung Galaxy S3 32gig device. I wiped system and have no OS installed and because of that my PC does not want to install driver. I cannot access my device through my PC but it is visible though. I have downloaded android software for my device and do not know how to copy it over to my S3. Can someone please help me? I have given up.
Hey, I also deleted my operating system and am stuck on TWRP, and I have an external SD card as well. I installed the exact ROM that's meant for my device (It's supposed to run on 4.4.2 Kitkat and it is an LG Tribute 1) and imported it to my external SD card. Problem is, when I try to flash the ROM onto the Lg Tribute, it does tell me that it is "installed successful" but when I reboot, it prompts me with a "Your device does not appear to be rooted, install SuperSU now? This will root your device." it gives me an option to "Do not install." But when I press the "Do not install." Button, nothing happens, so I am basically forced to install the SuperSU, which I normally don't mind, (since I actually already rooted my device before the OS was destroyed, which is probably why it got deleted in the first place.) but the thing is, after this happens, it reboots, then goes straight to TWRP, which is not supposed to happen. So I suspect the fact that I am installing SuperSU every time I reboot is what is causing my OS not to install. So I would really appreciate help. Thanks.
Please please can someone help?
I'll start at the beginning; I have a galaxy note 2 (n7100) in the UK, unlocked for use on any network. I have had this phone from new.
I rooted the phone about a year ago and installed twrp recovery I also installed a script that would allow me to swap the internal memory with the external memory.
Everything has been fine for about 8 months and then the other day I went to switch on my phone and it froze on the screen where I put my pin number in, I didn’t think much about it and turned the phone off & on, but now it just sits at the “Samsung galaxy note 2” screen.
I have booted into twrp and that is telling me there is “No Operating system installed”, it also will not allow me to browse the external SD card.
I have tried to reflash the stock rom using ODIN and everything appears to work and I get the “PASS” sign up, but the phone refuses to boot!!
Also when I boot into twrp it asks me to enter a password, I have never set a password so I'm baffled as to what this is?
And one last thing is that when I plug the phone into the charger with the phone switched off, the battery symbol appears on the screen but it just has a little circle in the battery and doesn’t show the battery charging animation.
I have just tried to flash a PIT file and now can no longer get into TWRP recovery, it seems to be going from bad to worse.
Please can someone help?
Pete
peter7769 said:
Please please can someone help?
I'll start at the beginning; I have a galaxy note 2 (n7100) in the UK, unlocked for use on any network. I have had this phone from new.
I rooted the phone about a year ago and installed twrp recovery I also installed a script that would allow me to swap the internal memory with the external memory.
Everything has been fine for about 8 months and then the other day I went to switch on my phone and it froze on the screen where I put my pin number in, I didn’t think much about it and turned the phone off & on, but now it just sits at the “Samsung galaxy note 2” screen.
I have booted into twrp and that is telling me there is “No Operating system installed”, it also will not allow me to browse the external SD card.
I have tried to reflash the stock rom using ODIN and everything appears to work and I get the “PASS” sign up, but the phone refuses to boot!!
Also when I boot into twrp it asks me to enter a password, I have never set a password so I'm baffled as to what this is?
And one last thing is that when I plug the phone into the charger with the phone switched off, the battery symbol appears on the screen but it just has a little circle in the battery and doesn’t show the battery charging animation.
I have just tried to flash a PIT file and now can no longer get into TWRP recovery, it seems to be going from bad to worse.
Please can someone help?
Pete
Click to expand...
Click to collapse
why did you use a pit file? anyway. if you flashed stock with odin there souldn't have been remained any TWRP.
reflash without pit file. after that boot in stock recovery and wipw data/factory reset. phone should boot up.
if all fails, (jope not) use this http://forum.xda-developers.com/showthread.php?t=2088809
mariosraptor said:
why did you use a pit file? anyway. if you flashed stock with odin there souldn't have been remained any TWRP.
reflash without pit file. after that boot in stock recovery and wipw data/factory reset. phone should boot up.
if all fails, (jope not) use this http://forum.xda-developers.com/showthread.php?t=2088809
Click to expand...
Click to collapse
i used pit file as last resort, i have tried everything else, i was thinking the same as you in that if i flashed custom rom then it should be custom recovery, ODIN says passed when its finished but something is obviously going wrong somewhere.
Thanks
Pete
i have tried the link you suggested but the phone wont connect with Kies, i have all the drivers installed but still wont connect
Well even though ODIN says its flashing and passed its not working, i have just tried for the 3rd time flashing a stock ROM, it said it had passed but its still booting into TWRP, and i cant do anything from within TWRP, firstly it ask for my password, if i press cancel then it goes to the main screen, but that's it.
if i look in the log file it just keeps saying
E: unable to find partition size for boot
E: unable to find partition size for recovery
etc
also
Unable to mount /efs
Unable to mount /cache
Unable to mount /system
etc
peter7769 said:
Well even though ODIN says its flashing and passed its not working, i have just tried for the 3rd time flashing a stock ROM, it said it had passed but its still booting into TWRP, and i cant do anything from within TWRP, firstly it ask for my password, if i press cancel then it goes to the main screen, but that's it.
if i look in the log file it just keeps saying
E: unable to find partition size for boot
E: unable to find partition size for recovery
etc
also
Unable to mount /efs
Unable to mount /cache
Unable to mount /system
etc
Click to expand...
Click to collapse
try this rescue firmware. also close all kies running apps from task manager prior to opening ODIN
http://forum.xda-developers.com/showpost.php?p=32273406&postcount=5
mariosraptor said:
try this rescue firmware. also close all kies running apps from task manager prior to opening ODIN
http://forum.xda-developers.com/showpost.php?p=32273406&postcount=5
Click to expand...
Click to collapse
Thanks, but the hotfile links are dead
i managed to find a link further on, d/l and tried it but still no joy im afraid, ODIN said it had all passed but nothing was written to the phone!!
peter7769 said:
Thanks, but the hotfile links are dead
Click to expand...
Click to collapse
https://www.4shared.com/zip/814t0y9A/N7100XXDLJ2_OXA_FACTORY.html
mariosraptor said:
https://www.4shared.com/zip/814t0y9A/N7100XXDLJ2_OXA_FACTORY.html
Click to expand...
Click to collapse
Thanks, but as you can see from my post above it didn't work :crying:
what do you mean? this is from 4shared not hotfile
mariosraptor said:
what do you mean? this is from 4shared not hotfile
Click to expand...
Click to collapse
no we are getting crossed wires, your original link sent me to download a rescue package from Hotfile, this no longer works.
but i managed to find another link further in the post that did work, i downloaded that and tried it but still had no success.
i have now downloaded your file from 4shared, and when i try and add all the various parts into Odin and click start, i get a message saying "Failed", this happens almost instantly.
any suggestions?
Pete
peter7769 said:
no we are getting crossed wires, your original link sent me to download a rescue package from Hotfile, this no longer works.
but i managed to find another link further in the post that did work, i downloaded that and tried it but still had no success.
i have now downloaded your file from 4shared, and when i try and add all the various parts into Odin and click start, i get a message saying "Failed", this happens almost instantly.
any suggestions?
Pete
Click to expand...
Click to collapse
first, are you closing any Kies remaining tasks from task manager?
second. what does it say when you are in donload mode? write all here
mariosraptor said:
first, are you closing any Kies remaining tasks from task manager?
second. what does it say when you are in donload mode? write all here
Click to expand...
Click to collapse
Hi
i have unistalled KIES as the phone wouldnt connect, no matter what usb port i tried, but i have kept the samsung drivers.
When i go into download mode i get this..
ODIN MODE
PRODUCT NAME - GT-N7100
CUSTOM BINARY DOWNLOAD: YES (2 COUNTS)
CURRENT BINARY:CUSTOM
SYSTEM STATUS:CUSTOM
like i said before it seems like nothing is being written to the phone, i even tried to flash the latest version of TWRP to the phone via ODIN, it passed but when i booted into recovery it still showed the old version number within TWRP
Pete
peter7769 said:
Hi
i have unistalled KIES as the phone wouldnt connect, no matter what usb port i tried, but i have kept the samsung drivers.
When i go into download mode i get this..
ODIN MODE
PRODUCT NAME - GT-N7100
CUSTOM BINARY DOWNLOAD: YES (2 COUNTS)
CURRENT BINARY:CUSTOM
SYSTEM STATUS:CUSTOM
like i said before it seems like nothing is being written to the phone, i even tried to flash the latest version of TWRP to the phone via ODIN, it passed but when i booted into recovery it still showed the old version number within TWRP
Pete
Click to expand...
Click to collapse
1. Try to flash the stock firmware.
2. If it bootloops, try to access recovery.
3. If didn't work, try to flash custom recovery such as philz touch
4. Try factory reset, wipe cache and dalvik cache.
Let us know if it works
iamjerbergerber said:
1. Try to flash the stock firmware.
2. If it bootloops, try to access recovery.
3. If didn't work, try to flash custom recovery such as philz touch
4. Try factory reset, wipe cache and dalvik cache.
Let us know if it works
Click to expand...
Click to collapse
Have you even read what he wrote? He did all those things but despite Odin reporting success, nothing in the phone was altered.
@peter7769 - what Odin version are you using? Is it started as Administrator? What is the driver version that is reported in Device Manager when you connect the phone? Can you uninstall Kies and try again to flash Samsung firmware (not custom one)?
mat9v said:
Have you even read what he wrote? He did all those things but despite Odin reporting success, nothing in the phone was altered.
@peter7769 - what Odin version are you using? Is it started as Administrator? What is the driver version that is reported in Device Manager when you connect the phone? Can you uninstall Kies and try again to flash Samsung firmware (not custom one)?
Click to expand...
Click to collapse
Thanks, like you said i have tried everything that iamjerbergerber suggested and nothing works,
i have tried using ODIN 3.07 & 3.09 as admin, what am are looking for in the device manager?, i can only see SAMSUNG Mobile USB CDC Composite Device listed under USB controllers, and SAMSUNG Mobile USB Modem listed under modems.
i have already tried the stock firmware which i got from SAMmobile but still no joy, i have been reading up that people said something has happened to the read/write permissions and that is why nothing is being flashed to the phone, though i cant understand why ODIN reports a PASS, as soon as i flash and go into TWRP is firstly asks for my password (never set one!) and then tells me no operating system installed.
Pete
Also i do get failed messages on ODIN when i try to flash anything but the PDA & PIT File Boxes.
Just trying to give you as much info as i can.
Pete
Just flashed stock firmware, all passed but same result
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDMB2_N7100OXXDMB2_N7100XXDLK7_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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> tz.img
<ID:0/003> system.img
<ID:0/003> boot.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> recovery.img
<ID:0/003> modem.bin
<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)
peter7769 said:
Thanks, like you said i have tried everything that iamjerbergerber suggested and nothing works,
i have tried using ODIN 3.07 & 3.09 as admin, what am are looking for in the device manager?, i can only see SAMSUNG Mobile USB CDC Composite Device listed under USB controllers, and SAMSUNG Mobile USB Modem listed under modems.
i have already tried the stock firmware which i got from SAMmobile but still no joy, i have been reading up that people said something has happened to the read/write permissions and that is why nothing is being flashed to the phone, though i cant understand why ODIN reports a PASS, as soon as i flash and go into TWRP is firstly asks for my password (never set one!) and then tells me no operating system installed.
Pete
Click to expand...
Click to collapse
What driver version are you using? This one (look at included screenshot)?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
From the listing you provided, the Odin behaves well. What happens after it reboots the system (Auto reboot and F.reset time are enabled, yes?)
Does the first window at the top print PASS! on green color with time underneath?
As I understand you tried to flash recovery with Odin? Could you try Philz recovery flashable from Odin, can be downloaded from HERE
You know, this message from TWRP stating that it can't locate partitions may mean you flashed an invalid PIT file...
Attached is a PIT file I have used in times of 4.1.2 firmware flash when I hosed my system.
Also PIT can be flashed ONLY with full system flash or you may loose EFS (along with IMEI) and that would be a disaster without correct backup.
mat9v said:
What driver version are you using? This one (look at included screenshot)?
View attachment 2601488
From the listing you provided, the Odin behaves well. What happens after it reboots the system (Auto reboot and F.reset time are enabled, yes?)
Does the first window at the top print PASS! on green color with time underneath?
As I understand you tried to flash recovery with Odin? Could you try Philz recovery flashable from Odin, can be downloaded from HERE
You know, this message from TWRP stating that it can't locate partitions may mean you flashed an invalid PIT file...
Attached is a PIT file I have used in times of 4.1.2 firmware flash when I hosed my system.
Also PIT can be flashed ONLY with full system flash or you may loose EFS (along with IMEI) and that would be a disaster without correct backup.
Click to expand...
Click to collapse
Thanks again for the help so far, firstly yes auto reboot is enabled and the other one, when the phone reboots it just sticks on the Samsung GT-N7100 screen and doesn't move, yes the window is green with PASS on it, although i cant recall seeing a time.
as for the driver it says driver date 02/01/2014 and version 2.11.7.0
i will try the pit file and philz recovery in a while as im just updating some stuff on the pc.
i will report back with the results.
Pete
Hi
one question i forgot to ask, when i flash the pit file do i have a tick in the Re-partition box, or should i leave it blank?
Thanks again
Pete
I had a relatively good OmniROM on my Samsung Galaxy Note 2 SGH-I317M for a while. I was in the middle of listening to some music that my phone crashed and rebooted and it got stuck at the OmniROM logo. I waited but then as I noticed it's not getting anywhere, I rebooted the phone. Then it got stuck at the Samsung GN2 logo.
I can go to download mode and I do have TWRP 2.6.3.1 as recovery mode and it's working. The weird thing is that, when I go to TWRP it asks for a password which I'm sure I've never set up in first place! Using File Manager of TWRP, I can browse but all critical folders are empty (system, data, etc, ...). Even if I insert my external SD card, the sdcard1 folder doesn't show anything! Worse than all, I can't wipe, backup, restore, install or mount or pretty much any of the functionalities in TWRP as folders are empty and external microSD card is not mounted. I can confirm all folders exist but are empty as I said. Apparently, it is unable to mount any folder!!!
In download mode, I tried to flash the stock ROM for 4.1.1 and 4.3 but it always fails with NAND Write started Operation fail error. And just to make sure I have tried different versions of Odin, different cables and 2 computers, all same error. I appreciate if someone can help me. This phone is new.
Another symptom is that when I power off the phone and charge it by plugging it in, the battery logo shows up but it's always show empty. I know the battery is being charged because when in TWRP, it shows percentage on top of screen, say 83%. Please help.
I can even adb from my PC to the phone.
Here is what Odin shows:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317MVLUCMK5_I317MOYACMK5_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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
idoit said:
I had a relatively good OmniROM on my Samsung Galaxy Note 2 SGH-I317M for a while. I was in the middle of listening to some music that my phone crashed and rebooted and it got stuck at the OmniROM logo. I waited but then as I noticed it's not getting anywhere, I rebooted the phone. Then it got stuck at the Samsung GN2 logo.
I can go to download mode and I do have TWRP 2.6.3.1 as recovery mode and it's working. The weird thing is that, when I go to TWRP it asks for a password which I'm sure I've never set up in first place! Using File Manager of TWRP, I can browse but all critical folders are empty (system, data, etc, ...). Even if I insert my external SD card, the sdcard1 folder doesn't show anything! Worse than all, I can't wipe, backup, restore, install or mount or pretty much any of the functionalities in TWRP as folders are empty and external microSD card is not mounted. I can confirm all folders exist but are empty as I said. Apparently, it is unable to mount any folder!!!
In download mode, I tried to flash the stock ROM for 4.1.1 and 4.3 but it always fails with NAND Write started Operation fail error. And just to make sure I have tried different versions of Odin, different cables and 2 computers, all same error. I appreciate if someone can help me. This phone is new.
Another symptom is that when I power off the phone and charge it by plugging it in, the battery logo shows up but it's always show empty. I know the battery is being charged because when in TWRP, it shows percentage on top of screen, say 83%. Please help.
I can even adb from my PC to the phone.
Here is what Odin shows:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317MVLUCMK5_I317MOYACMK5_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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You're only kinda hosed....
You need to find an ODIN package WITHOUT the sboot.bin. That's the bootloader that is not flashing....
dicksteele said:
You're only kinda hosed....
You need to find an ODIN package WITHOUT the sboot.bin. That's the bootloader that is not flashing....
Click to expand...
Click to collapse
By reading around, I was getting the impression that I need to flash .pit file along with the stock ROM but as I don't want to get things worse I was reluctant to do it. My searches for odin package without sboot.bin takes me no where. Not that I am a super Android toddler but any help is certainly more than appreciated. Well Ok, I'm noob. admit it. :good:
Edit: I found out about N7100UBALJ2_N7100TCEALJ1_TCE ROM from http://forum.xda-developers.com/showthread.php?t=2523366 but not sure if that solves the problem or that's relevant as it's for N7100 and mine is SGH-i317m... same family but who knows maybe different ROMs! ?
Can you connect to your pc and transfer rom files?
If not, in download mode you can use adb.exe and "adb push / mnt/sd card rom name" if you can't transfer.
Don't use a pit file. That partitions all of your phone.
rangercaptain said:
Can you connect to your pc and transfer rom files?
If not, in download mode you can use adb.exe and "adb push / mnt/sd card rom name" if you can't transfer.
Click to expand...
Click to collapse
Update: I uploaded the recovery.log file from TWRP by accessing with adb in recovery mode.
Nothing happens when I connect it to PC in normal mode... I mean just connecting it as it is. (NOT in recovery mode or download mode).
Right now, I am in Windows and when I connect it in download mode, I try to adb but it says device not found. In recovery mode, I can adb but as I said in first post, I can't read or write. MicroSD is not recognized, so I can't put stock ROM there either. Is there any hope to get my phone back?
Don't use a pit file. That partitions all of your phone.
Click to expand...
Click to collapse
Well, I did try to flash a pit file from here, but it fails with same NAND Write error!
I have a good news.
So I went to /dev/block folder when ADBing and noticed mmcblk0 device. I manually mounted mmcblk0p1 and yoohoo it is mounted. It means now i can put my TWRP backup files there and run TWRP restore. Is that a good idea?! Does it make sense at all? I mean I am desperate for any way to get this thing back, a shadow of hope is huge for me too now.
Update: Ahhh damn it! I mount the MicroSD from adb to /external_sdcard (this is the folder where it used to mount my external microSD) in TWRP. Using File Manager provided by TWRP, I confirm the folder is there. But when I go to Restore section, it doesn't show any partition and it doesn't let me choose external memory. It's like this:
- Internal Memory (0MB)
- External Memory (0MB)
- USB OTG (0MB)
Any thoughts? I feel I am so close but not there yet.
The reason adb doesn't work is you need a setting checked in developer options. I wish that was a default setting.
You're not bricked if there's any lifesigns.
Have you used the Kies website? I generally don't recommend Kies, but when your operating system is borked, Kies has an emergency firmware recovery option.
Before you go to Kies, copy down the information on the sticker under your battery, and it will be case sensitive when Kies asks for that info.
rangercaptain said:
Before you go to Kies, copy down the information on the sticker under your battery, and it will be case sensitive when Kies asks for that info.
Click to expand...
Click to collapse
Alright, done.
The reason adb doesn't work is you need a setting checked in developer options. I wish that was a default setting.
You're not bricked if there's any lifesigns.
Have you used the Kies website? I generally don't recommend Kies, but when your operating system is borked, Kies has an emergency firmware recovery option.
Click to expand...
Click to collapse
When in Kies, it can't connect to my device. tried all usb cables and all 3 modes: Normal, download and recovery. Always says connecting... spinning forever. I suppose I should work in download mode anyways, right? Anyway, I went to Tools > firmware emergency recovery and entered the serial number. It finishes to 100% but it the end prompts with this error:
<Firmware emergency recovery stopped due to error. If the problem persists, please contact the Samsung service center.>
Now to report back the result from Kies FER:
I follow the instructions word by word. As the screenshot shows, Kies tells me to put phone into "Recovery mode"by pressing on power button. Well, either Samsung doesn't know what recovery mode is or ... Anyways, I take battery out and etc and boot to normal phone by pressing on power button... and "Free Upgrade"button is still grayed out. I go to Recovery mode (Power + Home + Volume Up) and it is still grayed out. (first screenshot attached below)
It's only in Odin Download mode (Power + Home + Volume Down and then Volume Up) that it becomes available.
After some time, the following error appears. I have done it a couple of times now and I restarted my Windows too. but no dice.
(second screenshot attached below)
idoit said:
Alright, done.
When in Kies, it can't connect to my device. tried all usb cables and all 3 modes: Normal, download and recovery. Always says connecting... spinning forever. I suppose I should work in download mode anyways, right? Anyway, I went to Tools > firmware emergency recovery and entered the serial number. It finishes to 100% but it the end prompts with this error:
<Firmware emergency recovery stopped due to error. If the problem persists, please contact the Samsung service center.>
Click to expand...
Click to collapse
And you're on an i317M on ATT?
Was this an original Rogers or Bell phone???
dicksteele said:
And you're on an i317M on ATT?
Was this an original Rogers or Bell phone???
Click to expand...
Click to collapse
I have i317M and it was originally for Bell. I got rid of stock ROM and then installed OmniROM until this happened.
Kies is not helping the poor smartphone either (well now it is dumbphone ). Keeps giving that error too.
idoit said:
I have i317M and it was originally for Bell. I got rid of stock ROM and then installed OmniROM until this happened.
Kies is not helping the poor smartphone either (well now it is dumbphone ). Keeps giving that error too.
Click to expand...
Click to collapse
Cool.... So where did you get this
I317MVLUCMK5_I317MOYACMK5_HOME.tar.md5
The ODIN file that's blowing up on the bootloader?
dicksteele said:
Cool.... So where did you get this
I317MVLUCMK5_I317MOYACMK5_HOME.tar.md5
The ODIN file that's blowing up on the bootloader?
Click to expand...
Click to collapse
I have to say this: When my phone was alive, in order to unlock the carrier from Bell, I had to flash a 4.1.1 modem and I flashed one from Rogers to unlock. So my under setting in my Phone was showing Rogers brand. Now with this in mind:
I downloaded that file from here under heading I317MVLUCMK5 4.3 Stock Firmware. I noticed it is for Rogers. (where for Bell was available too but I downloaded Rogers one.
I have tried some other original i317m stock roms (from sammobile.com), 4.1.1 for Bell but no luck same NAND error. I simply guess ODIN can't write anything, and the eMMC is corrupted! ?
idoit said:
I have to say this: When my phone was alive, in order to unlock the carrier from Bell, I had to flash a 4.1.1 modem and I flashed one from Rogers to unlock. So my under setting in my Phone was showing Rogers brand. Now with this in mind:
I downloaded that file from here under heading I317MVLUCMK5 4.3 Stock Firmware. I noticed it is for Rogers. (where for Bell was available too but I downloaded Rogers one.
I have tried some other original i317m stock roms, 4.1.1 for Bell but no luck same NAND error. I simply guess ODIN can't write anything, and the eMMC is corrupted! ?
Click to expand...
Click to collapse
It's trying write the sboot.bin file which is the bootloader.
The 4.3 bootloader slaps down any attempts to overwrite it. That's why you're seeing the fail.
I'm downloading a 4.1.2 to see if sboot.bin is in there
---------- Post added at 08:58 PM ---------- Previous post was at 08:23 PM ----------
Good news the I317M_RWC_I317MVLBMA3_I317MOYABMA3_Original.zip from the
Rogers – 4.3 Jelly Bean RWC_I317MVLBMA3_I317MOYABMA3_I317MVLBMA3 download does not have the sboot.bin.
That should bring you back.. Or at least get past the ODIN flash fail
---------- Post added at 09:02 PM ---------- Previous post was at 08:58 PM ----------
idoit said:
I have to say this: When my phone was alive, in order to unlock the carrier from Bell, I had to flash a 4.1.1 modem and I flashed one from Rogers to unlock. So my under setting in my Phone was showing Rogers brand. Now with this in mind:
I downloaded that file from here under heading I317MVLUCMK5 4.3 Stock Firmware. I noticed it is for Rogers. (where for Bell was available too but I downloaded Rogers one.
I have tried some other original i317m stock roms (from sammobile.com), 4.1.1 for Bell but no luck same NAND error. I simply guess ODIN can't write anything, and the eMMC is corrupted! ?
Click to expand...
Click to collapse
Awesome on the firmware site BTW !
dicksteele said:
It's trying write the sboot.bin file which is the bootloader.
The 4.3 bootloader slaps down any attempts to overwrite it. That's why you're seeing the fail.
I'm downloading a 4.1.2 to see if sboot.bin is in there
---------- Post added at 08:58 PM ---------- Previous post was at 08:23 PM ----------
Good news the I317M_RWC_I317MVLBMA3_I317MOYABMA3_Original.zip from the
Rogers – 4.3 Jelly Bean RWC_I317MVLBMA3_I317MOYABMA3_I317MVLBMA3 download does not have the sboot.bin.
That should bring you back.. Or at least get past the ODIN flash fail
---------- Post added at 09:02 PM ---------- Previous post was at 08:58 PM ----------
Awesome on the firmware site BTW !
Click to expand...
Click to collapse
Thank you very much dicksteele! I'm downloading it too and it will take 8 hours I believe, so I'll report back later. Now, here is the thing: Reading some comments from that page makes me be careful though.
Specifically, talking about the following comments:
Hi Guy, my problem is that my phone lost baseband version and IMEI number. I download the stock rom: TLS_I317MVLBMA3_I317MOYABMA3_I317MVLBMA3; The rom did not fix the issue. After I install it, the baseband version and IMEI number still shown Null. Could you please help me? Thousands thanks!
Click to expand...
Click to collapse
This was posted long before the 4.1.2 came around, but you have all the guts there when trying to roll back to 4.1.1 not even aware that there might be a new bootloader added on 4.1.2 I317MVLBMA3 update and returning back to 4.1.1 is quite risky
If you did not touch your device before using rooted kernels and/or custom. I suggests that you must stay on 4.1.2.
Click to expand...
Click to collapse
Now, what should I do now to make sure I will be able to make calls, assuming (hopefully) I'll get this sucker back to life?
Oh boy, will I ever again install OmniROM on it? Hell NOOO!
You won't lose your baseband or IEMI. What you are doing is returning your phone to 100% factory stock (except for the 4.3 bootloader). You can deal with any other issues as they arise/if they arise from a working phone easier than you can from a borked phone.
Why eight hours to download?
idoit said:
Thank you very much dicksteele! I'm downloading it too and it will take 8 hours I believe, so I'll report back later. Now, here is the thing: Reading some comments from that page makes me be careful though.
Specifically, talking about the following comments:
Now, what should I do now to make sure I will be able to make calls, assuming (hopefully) I'll get this sucker back to life?
Oh boy, will I ever again install OmniROM on it? Hell NOOO!
Click to expand...
Click to collapse
The losing the IMEI was because of a different issue I believe.... The /efs partition holds all the important cel info. As long as that's not hosed you're fine...
OMNIROM should not have touched that.
Backing up your /efs can be done a couple of ways.
http://www.xda-developers.com/android/backup-your-efs-partition-with-easy-to-use-app/
So I downloaded that file and it took almost 8 hours. But it still has sboot.bin and boot.img file inside! Obviously flashing with Odin gave same error. @dicksteele: Can you please share with me the link I can download? I downloaded this file (http://rg.to/file/c036fd8b51b8836bf0a399eee83ee680/%20I317M_RWC_I317MVLBMA3_I317MOYABMA3_Original.zip.html) from http://androidromupdate.com/2012/11...-sgh-i317m-canada-original-stock-romfirmware/ under I317MVLBMA3 4.1.2 Stock Firmware, Rogers – 4.3 Jelly Bean RWC_I317MVLBMA3_I317MOYABMA3_I317MVLBMA3
P.S. I opened the tar.md5 file with 7-zip.
@rangercaptain: My internet speed is good, it should have been because of the download link above (from rapidgator) which made it so slow. Where do you guys download from that's faster?!
Thanks everyone.
idoit said:
So I downloaded that file and it took almost 8 hours. But it still has sboot.bin and boot.img file inside! Obviously flashing with Odin gave same error. @dicksteele: Can you please share with me the link I can download? I downloaded this file (http://rg.to/file/c036fd8b51b8836bf0a399eee83ee680/%20I317M_RWC_I317MVLBMA3_I317MOYABMA3_Original.zip.html) from http://androidromupdate.com/2012/11...-sgh-i317m-canada-original-stock-romfirmware/ under I317MVLBMA3 4.1.2 Stock Firmware, Rogers – 4.3 Jelly Bean RWC_I317MVLBMA3_I317MOYABMA3_I317MVLBMA3
P.S. I opened the tar.md5 file with 7-zip.
@rangercaptain: My internet speed is good, it should have been because of the download link above (from rapidgator) which made it so slow. Where do you guys download from that's faster?!
Thanks everyone.
Click to expand...
Click to collapse
I'm a dumbass It was
I317M_RWC_I317MVLALJ2_I317MOYAALJ2_Original
And you're right it was rapidget that was slow.... I have a download manager that I use and it pulls it down quick.
Another location is here
http://www.sammobile.com/firmwares/3/?download=8176
I know I know RC.
You need a login to download, registration is free.
I'm trying to upload the one I downloaded but upload dies 3 MB into it.
If you have probs with the sammobile one, I'll try and get the other one downloaded so you don't have to waste another 8 hours because I'm a dumbass.
And 7zip to verify was good, that's what I did.
dicksteele said:
I'm a dumbass It was
I317M_RWC_I317MVLALJ2_I317MOYAALJ2_Original
And you're right it was rapidget that was slow.... I have a download manager that I use and it pulls it down quick.
Another location is here
http://www.sammobile.com/firmwares/3/?download=8176
I know I know RC.
You need a login to download, registration is free.
I'm trying to upload the one I downloaded but upload dies 3 MB into it.
If you have probs with the sammobile one, I'll try and get the other one downloaded so you don't have to waste another 8 hours because I'm a dumbass.
And 7zip to verify was good, that's what I did.
Click to expand...
Click to collapse
This is being downloaded quickly. Until that download is finished, I knew yesterday I downloaded I317M_BWC_I317MVLALJ2_I317MOYAALJ2_Original (Similar to the one you just said to download but for Bell). You're right, this one doesn't have sboot.bin but it does have boot.img. Anyways, I tried to flash it with Odin3 v3.04, and it fails on me!
Firmware update start...
boot.img
NAND Write Start!
Complete(Write) operation failed.
Now, I have no idea what to do next! Wow, phones and even products from big companies like Samsung are so fragile.
[Off-topic]
Boy, these last 3 days had been hectic. First this happened to my Phone. Then today, when I was in Windows (which I rarely use, I went on Disk Management and made my C partition active). Stupid Windows, wiped all my partition table!!! And now my laptop is a piece of brick too. Oh boy, you know, when it rains it pours!
Samsung Galaxy s3 T-mobile SGH-T999 4.3 jellybean
I have been trying for a few days to flash my phone but no luck. All I want is to get cyangenmod but I encounter errors everywhere I go. I have tried the simple method provided by cyanogenmod themselves but at the end of the process it boots me up into recovery mode telling me that I might lose root and asking that if I want to fix it. No matter what I choose it decides to boot up into regular touchwiz with no apparent changes. I have tried the mobile odin method but it comes up with an error and boots up yet again. It came up with an error but the screen turned off before I could read any further. I have tried flashing the rom via rom manager but everytime I do it boots me up into recovery mode with an error and eventually asks me that same question regarding root just before returning me back to touchwiz. I have even tried using odin307(which I used to root my phone) but it no longer recognizes my phone. I have no idea what to do. My phone still works fine although I get more errors concerning google application after a factory reset but I can still use it no problem. Also, whenever I try to boot up into recovery mode it just shows up with that cyanogenmod icon and then it dissapears just before having it boot up normally so i can no longer boot up into recovery mode. I have downloaded clockworkmod recovery but no luck. I have done so many things that I wouldn't be surprised if my phone turned out to be broken now. whenever I boot up into download mode it now tells me that everything is custom. I have heard of problems concerning knox but when I rooted my phone it didn't it didn't seem to get rid of it. This is really driving me nuts and I now hate samsung for having it made so hard to tweak anything in this phone. Does anyone know of a way get passed all of this stuff and flashing the rom? is my phone broken now? Any help would be greatly appreciated.
It helps a lot if you included exactly what errors you saw. A recovery log, what exactly you're trying to flash, and any other related details goes a long way.
If odin doesn't see your phone its probably a driver issue. What does it say in device manager?
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
It helps a lot if you included exactly what errors you saw. A recovery log, what exactly you're trying to flash, and any other related details goes a long way.
If odin doesn't see your phone its probably a driver issue. What does it say in device manager?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
As you can see, I am a complete noob when it comes to this stuff so I apologize in advance if I don't answer your questions in the correct manner.
If you are talking about the phone drivers, I had already installed them some time ago. I have even installed kies and kies3. Odin recognized my phone before I did all of this since it was what I used to root my phone. I am still able to access the phone's files through my computer.
when I used rom manager it would give me an error right after the whole backup process and show me recovery mode. I would try to look up the same rom via the recovery directory but it would give me the same error message. If i clicked on the reboot option, it would boot me up to stock. If I clicked on the **go back** option a couple of times it would give me this message.
Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE
1. YES fix root (/system/xbin/su)
2. NO do not fix
*Go back*
no matter what I clicked on, it would boot me up into stock yet again.
I tried doing this again just now and it turned off. it then showed that small strip of blue at the top left that it usually shows before booting up into recovery mode and the screen turned off shortly after. at this point I was unable to turn on the phone even with the charger on. I was only able to turn it on after booting it up into download mode.
This same root message appeared when I tried to flash using the cyanogenmod website method. the only difference was that it only showed this message and not the whole recovery menu.
The device manager reads it as "Samsung device"
Ok, first thing you should do is uninstall kies. Odin usually wont work if its installed. If it still fails to see it in odin, uninstall your drivers through device manager, then install the stand alone driver pkg from my sig. (Use the second or third newest to start, the latest should work, but its had a lot more changes for the S5 and Note3.)
Once you get Odin working, download TWRP and flash. (Put the file in PDA if using Odin v3.07, or put it in AP if v3.09). See my sig for everything you need. (Get the .tar or .tar.md5 file for flashing in Odin btw.)
Next boot recovery and flash your rom. A factory reset would probably a good idea at this point, but you can try without first if you want.
If you have any questions or problems feel free to ask. Most of us dont mind helping at all, so long as you are willing to make an effort to help yourself first.
Good luck!
Sent from my SGH-T999 using Tapatalk
---------- Post added at 02:16 AM ---------- Previous post was at 02:15 AM ----------
Oh, and Sammys devices wont turn on when plugged in. This is perfectly normal.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Ok, first thing you should do is uninstall kies. Odin usually wont work if its installed. If it still fails to see it in odin, uninstall your drivers through device manager, then install the stand alone driver pkg from my sig. (Use the second or third newest to start, the latest should work, but its had a lot more changes for the S5 and Note3.)
Once you get Odin working, download TWRP and flash. (Put the file in PDA if using Odin v3.07, or put it in AP if v3.09). See my sig for everything you need. (Get the .tar or .tar.md5 file for flashing in Odin btw.)
Next boot recovery and flash your rom. A factory reset would probably a good idea at this point, but you can try without first if you want.
If you have any questions or problems feel free to ask. Most of us dont mind helping at all, so long as you are willing to make an effort to help yourself first.
Good luck!
Sent from my SGH-T999 using Tapatalk
---------- Post added at 02:16 AM ---------- Previous post was at 02:15 AM ----------
Oh, and Sammys devices wont turn on when plugged in. This is perfectly normal.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thank you for the timely and thorough responses.
Okay so odin is now reading my device. It just isn't reading my device while on download mode though.
I tried the .tar version first and this is what came up:
C:\Users\Jerry\Desktop\openrecovery-twrp-2.4.0.0-d2tmo.tar
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I attempted this four times and they all ended with "fail" at the top
I then attempted the .tar.md5 and I received this.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> openrecovery-twrp-2.3.1.0-d2tmo.tar.md5 is invalid.
<OSM> End...
It seems like it is not even reading this file. This came up before even connecting my device. I tried a couple versions of this but they all had the same result.
My phone then asked to update clockworkmodrecovery and I did.( I actually installed the rom installer version) After doing so, I decided to try my luck and boot up into recovery mode. This time I was successful in booting up into recovery mode although it still showed me that cyanogenmod icon right before getting there. I then went on to install a zip from sd card only to receive the same message I have been receiving since the very beginning:
Installing: /sdcard/0/cm-11-20140217-NIGHTLY-d2tmo.zip
Finding update package...
Finding update package...
Opening update package...
Installing update...
assert failed: THEN A BUNCH OF THESE getprop(" ro.bootloader") =="T999VVLUVUBMK4" (WITH VARIATIONS AFTER T999)
E: Error in /data/media/0/cm-11-20140217-NIGHTLY-d2tmo.zip
(status 7)
Installation aborted.
After error I clicked on the "reboot now" option, only to come up with this message again:
Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE
1. YES fix root (/system/xbin/su)
2. NO do not fix
This message is what seems(at least to me) to be the main problem. It has appeared after a successful cyanogenmod standard installation (the one from their website) only to restore everything to default after I click on it. Instead of rebooting normally like cyanogenmod said, it would bring me up to this screen. so it seems that even if i were to have a successful installation, this would keep it from going through
I also tried mobile odin but, once again, showed an error that disappeared before I could remember anything.
Thanks your help is really appreciated.
If odin isnt seeing it in download mode try reinstalling your drivers, maybe a different version. Also, check what version of odin you are using. If 3.07, try 3.09. If using 3.09, try 3.07.
Another thing I noticed is the twrp you were trying to use is quite old. Try 2.7.0.0. If you still cant do this from Odin, use the Goo Manager app from the store. (Press menu, then install openrecovery script)
Also, install Terminal Emulator, and enter this:
getprop ro.bootloader
Tell me what it returns. Finally, if you want, open the rom zip file and find the updater script. Open with Notepad++ and delete the assert lines at the top. Save then delete the sig files from the rom, rezip and flash. (There are 3 signature files, cert, manifest, and another. If found, delete, if not, ignore)
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
If odin isnt seeing it in download mode try reinstalling your drivers, maybe a different version. Also, check what version of odin you are using. If 3.07, try 3.09. If using 3.09, try 3.07.
Another thing I noticed is the twrp you were trying to use is quite old. Try 2.7.0.0. If you still cant do this from Odin, use the Goo Manager app from the store. (Press menu, then install openrecovery script)
Also, install Terminal Emulator, and enter this:
getprop ro.bootloader
Tell me what it returns. Finally, if you want, open the rom zip file and find the updater script. Open with Notepad++ and delete the assert lines at the top. Save then delete the sig files from the rom, rezip and flash. (There are 3 signature files, cert, manifest, and another. If found, delete, if not, ignore)
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Hey man I was finally able to flash my rom! I updated both the drivers and odin and was able to successfully install the recovery file. It still did not install cyanogenmod reading an md5 error and "error executing updater binary in zip" though. anyway I installed AOKP instead and it finally worked. I think the cyanogenmod files that I downloaded were just incompatible with my device or faulty (even though i tried like 10. maybe something wrong with my phone?). Anyway I am really grateful for all of your help. I was so happy after I was finally getting it. It seriously frustrated the heck out of me. I no longer hate my samsung and am quite liking this new rom. Thanks again!
Glad I could help and that you seem to be happy with it so far!
Sent from my SGH-T999 using Tapatalk