Related
I tried pretty much everything on the internet before posting here.
My stock/no root phone started bootlooping. So I used Odin and root66.tar to get it back. Everything seemed to be good. After I got 3 updates:1) 30mb, 2) 60mb and 3) JB updated OTA. After 60Mb update my phone said Samsung and shows unlocked lock. After JB update my phone bootloops again.
I though it it was a bad update and reflashed stock no root 4.0.4 and OTA did the same thing.
I tried the gs3 tool to flash the recovery and it always fails.
I would appreciate any help.... I have been dealing with this non sense for the past 24h.
droidxrooting said:
I tried pretty much everything on the internet before posting here.
My stock/no root phone started bootlooping. So I used Odin and root66.tar to get it back. Everything seemed to be good. After I got 3 updates:1) 30mb, 2) 60mb and 3) JB updated OTA. After 60Mb update my phone said Samsung and shows unlocked lock. After JB update my phone bootloops again.
I though it it was a bad update and reflashed stock no root 4.0.4 and OTA did the same thing.
I tried the gs3 tool to flash the recovery and it always fails.
I would appreciate any help.... I have been dealing with this non sense for the past 24h.
Click to expand...
Click to collapse
Try to use Odin to flash back into stock not the root66 one as that is the rooted stock ROM.
jmxc23 said:
Try to use Odin to flash back into stock not the root66 one as that is the rooted stock ROM.
Click to expand...
Click to collapse
I did flash back to stock 4.0.4 and still get the same results. I was thinking If someone could provide the stock 4.1.1 update in a zip format. I wanted to flash it trough stock recovery to see the result.
I downloaded the JB 400mb update and installed it via recovery. Before I turned the phone on did factory reset and wiped the cache. I turned the phone on it boot loops. Does not make any sense at all. ICS works absolutely fine but JB fails to install properly.
This is a puzzle for me why it would do that.
Update: I was able to flash teamwin recovery though Ez-app from the play store. I still dont have luck with JB update. Update softbricked my phone 4 times now.
droidxrooting said:
I downloaded the JB 400mb update and installed it via recovery. Before I turned the phone on did factory reset and wiped the cache. I turned the phone on it boot loops. Does not make any sense at all. ICS works absolutely fine but JB fails to install properly.
This is a puzzle for me why it would do that.
Update: I was able to flash teamwin recovery though Ez-app from the play store. I still dont have luck with JB update. Update softbricked my phone 4 times now.
Click to expand...
Click to collapse
Are you flashing a custom recovery before the ota? If you run a custom recovery the ota wont take.
x714x said:
Are you flashing a custom recovery before the ota? If you run a custom recovery the ota wont take.
Click to expand...
Click to collapse
Everything was stock when I ran the OTA 2 times. The other 2 times I was rooted and still stock. Nothing I do works. I am not a noob. I have done some flashing in my life but this does not make sense at all.
droidxrooting said:
Everything was stock when I ran the OTA 2 times. The other 2 times I was rooted and still stock. Nothing I do works. I am not a noob. I have done some flashing in my life but this does not make sense at all.
Click to expand...
Click to collapse
What happens when you Odin flash the stock VRBLK3 tar?
SlimSnoopOS said:
What happens when you Odin flash the stock VRBLK3 tar?
Click to expand...
Click to collapse
Downloading COMBINATION_I535VRBLK3_I535VZWBLK3_381038_REV09_user_low_ship_NOWIPE_fixed.tar.md5 right now. I will flash it report it back.
Is there any reason that this file is 1.2GB?
droidxrooting said:
Downloading COMBINATION_I535VRBLK3_I535VZWBLK3_381038_REV09_user_low_ship_NOWIPE_fixed.tar.md5 right now. I will flash it report it back.
Is there any reason that this file is 1.2GB?
Click to expand...
Click to collapse
They're all large files due to TW. VRALG1 tar measures in at about 800 mb. The update from VRALHE to VRBLK3 was 400 mb so that's not unusual.
SlimSnoopOS said:
They're all large files due to TW. VRALG1 tar measures in at about 800 mb. The update from VRALHE to VRBLK3 was 400 mb so that's not unusual.
Click to expand...
Click to collapse
I tried the flash the VRBLK3 but it always fails not matter what I do. Any other suggestions?
Re: I am having a very strange problem with OTA [NOT A NOOB]
droidxrooting said:
I tried the flash the VRBLK3 but it always fails not matter what I do. Any other suggestions?
Click to expand...
Click to collapse
What error code do you get in Odin? What is the exact file name you're attempting to flash? Where are you downloading it from?
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
What error code do you get in Odin? What is the exact file name you're attempting to flash? Where are you downloading it from?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
name: COMBINATION_I535VRBLK3_I535VZWBLK3_381038_REV09_user_low_ship_NOWIPE_FIXED.tar.md5
downloaded from here : http://www.androidfilehost.com/?fid=9390214368362234406
code says failed and : <ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Erase...
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
droidxrooting said:
name: COMBINATION_I535VRBLK3_I535VZWBLK3_381038_REV09_user_low_ship_NOWIPE_FIXED.tar.md5
downloaded from here : http://www.androidfilehost.com/?fid=9390214368362234406
code says failed and : <ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Erase...
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Have you tried a different port? Also, is this with the OEM usb cable?
SlimSnoopOS said:
Have you tried a different port? Also, is this with the OEM usb cable?
Click to expand...
Click to collapse
Trying different port now. Yes the cable is OEM.
I was able to flash root66.tar with non oem cable just fine. Everything works but the phone does not like jelly bean update.
After I flashed CM10.1 the phone bootlooped again. I am restoring back to stock right now.
droidxrooting said:
Trying different port now. Yes the cable is OEM.
I was able to flash root66.tar with non oem cable just fine. Everything works but the phone does not like jelly bean update.
After I flashed CM10.1 the phone bootlooped again. I am restoring back to stock right now.
Click to expand...
Click to collapse
You unlocked the bootloader, flashed C10.1, and it bootlooped again? If you're back on rooted ics, you could try the VRBLK3 rooted rom by Beans. I'm having difficulty accepting the notion your phone will not run VRBLK3 but then again there was that thread where a few people were having issues with VRBLK3 bootlooping regardless of what they tried.
SlimSnoopOS said:
You unlocked the bootloader, flashed C10.1, and it bootlooped again? If you're back on rooted ics, you could try the VRBLK3 rooted rom by Beans. I'm having difficulty accepting the notion your phone will not run VRBLK3 but then again there was that thread where a few people were having issues with VRBLK3 bootlooping regardless of what they tried.
Click to expand...
Click to collapse
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas why it is failing? Do you think I can flash it trough cwm?
droidxrooting said:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas why it is failing? Do you think I can flash it trough cwm?
Click to expand...
Click to collapse
Well this one failed because its a rom that you flash in CWM or TWRP. Make sure you've unlocked the bootloader already.
Edit: You flash ".tar" or ".tar.md5" via Odin, .zip goes in recovery.
SlimSnoopOS said:
Well this one failed because its a rom that you flash in CWM or TWRP. Make sure you've unlocked the bootloader already.
Edit: You flash ".tar" or ".tar.md5" via Odin, .zip goes in recovery.
Click to expand...
Click to collapse
I think my phone is one of those which do not take jelly beam update. Now I have to send it to samsung to get it fixed. I did not buy it from verizon so I can not get it replaced.
I have tried pretty much everything that is on the internet. Nothing helps .... freaking ICS work just fine and every feature works on ICS.....
This does not make sense at all.
droidxrooting said:
I think my phone is one of those which do not take jelly beam update. Now I have to send it to samsung to get it fixed. I did not buy it from verizon so I can not get it replaced.
I have tried pretty much everything that is on the internet. Nothing helps .... freaking ICS work just fine and every feature works on ICS.....
This does not make sense at all.
Click to expand...
Click to collapse
It bootlooped again when flashing Beans custom rom via recovery?
SlimSnoopOS said:
It bootlooped again when flashing Beans custom rom via recovery?
Click to expand...
Click to collapse
Yes, nothing works but the stock ics. the root66.tar works and stock no root works. Other than that everything make the phone to boot loop. I have the other GS3 and that works absolutely fine. I can not under stand why in the hell this would not accept JB update.
Yes, I am a NOOB and yes I watched the video (very amusing by the way). I ran the Casual root method
http://forum.xda-developers.com/showthread.php?t=2332825
for my S3 and everything went fine. However, when I boot into recovery, there is no "backup/restore" option. Shouldn't I be able to do that if TWRP was installed at that time? Also, when I watched the youtube video showing that root method, Superuser was installed and on my phone a different superuser was installed. Rather than the pirate looking droid, I have a superman looking icon title SuperSU. I really want to flash the Cyanogenmod 10 on this phone. Thank you guys so much for your help on this!!
kcoop99 said:
Yes, I am a NOOB and yes I watched the video (very amusing by the way). I ran the Casual root method
http://forum.xda-developers.com/showthread.php?t=2332825
for my S3 and everything went fine. However, when I boot into recovery, there is no "backup/restore" option. Shouldn't I be able to do that if TWRP was installed at that time? Also, when I watched the youtube video showing that root method, Superuser was installed and on my phone a different superuser was installed. Rather than the pirate looking droid, I have a superman looking icon title SuperSU. I really want to flash the Cyanogenmod 10 on this phone. Thank you guys so much for your help on this!!
Click to expand...
Click to collapse
What does your recovery look like? Twrp looks blue, and the interface is touch optimized. The stock recovery is mostly black and has limited options.
The superman looking icon is SuperSU, the pirate looking icon is superuser, they both do the same thing and it indicates that you are rooted.
Download ez unlock 1.2 from a website and install it. Open it and check and make sure your Bootloader says unlocked. If it doesn't, unlock it.
Then, download ez recovery from the playstore. Download either twrp or CWM from the following thread and flash from the custom slot in the app.
http://forum.xda-developers.com/showthread.php?t=2096735
Now make a backup in the recovery and flash cm10, just follow the directions on the first page of the cm10 thread for installation and you're good to go.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
What does your recovery look like? Twrp looks blue, and the interface is touch optimized. The stock recovery is mostly black and has limited options.
The superman looking icon is SuperSU, the pirate looking icon is superuser, they both do the same thing and it indicates that you are rooted.
Download ez unlock 1.2 from a website and install it. Open it and check and make sure your Bootloader says unlocked. If it doesn't, unlock it.
Then, download ez recovery from the playstore. Download either twrp or CWM from the following thread and flash from the custom slot in the app.
http://forum.xda-developers.com/showthread.php?t=2096735
Now make a backup in the recovery and flash cm10, just follow the directions on the first page of the cm10 thread for installation and you're good to go.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
My recovery is apparently NOT TWRP then. In fact, after I wrote this, I installed ROM Manager from the play store. Now, when I try to boot into recovery, I just get the Samsung Custom with the unlock icon. If I want to boot into recovery, I have to do so through ROM Manager.
I downloaded CM10.1.2 from rom manager and also the gapps. Is it safe or advisable to just install it this way? I really appreciate the help as I am really trying to get a grasp on this stuff. My last phone was a droid x2 that I rooted with this site. Thanks!
kcoop99 said:
My recovery is apparently NOT TWRP then. In fact, after I wrote this, I installed ROM Manager from the play store. Now, when I try to boot into recovery, I just get the Samsung Custom with the unlock icon. If I want to boot into recovery, I have to do so through ROM Manager.
I downloaded CM10.1.2 from rom manager and also the gapps. Is it safe or advisable to just install it this way? I really appreciate the help as I am really trying to get a grasp on this stuff. My last phone was a droid x2 that I rooted with this site. Thanks!
Click to expand...
Click to collapse
Follow the directions I gave you. I think your Bootloader is still locked, but you should have CWM installed, just unlock the bootloader with ez unlock and then you can start flashing.
Sent from my SCH-I535 using Tapatalk 2
Not sure if it worked.
I am also very new to all of this. I wanted to use the GS3 toolkit to root my s3. It said to use the casual gs3 unlock tool. I downloaded and ran the program. I have no idea if it took. it said done, i have no idea if the insecure aboot took either. so i moved on. I was running the donate and updated version of the GS3Toolkit . It was going fine until Odin failed. I have no idea if i did anything at all or is everything the same before i ever started. Im on 4.4.2 with a build of rbmf1. How do i check if anything worked. Definitely not rooted. Please help ,thanks.
Odin displays the following fail:
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
BadUsername said:
Follow the directions I gave you. I think your Bootloader is still locked, but you should have CWM installed, just unlock the bootloader with ez unlock and then you can start flashing.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Worked great. Got it unlocked. When I downloaded that it said my phone status was unknown so I unlocked it. I downloaded the CWM also. Am I ready to go?
kcoop99 said:
Worked great. Got it unlocked. When I downloaded that it said my phone status was unknown so I unlocked it. I downloaded the CWM also. Am I ready to go?
Click to expand...
Click to collapse
Yes, you're all ready to go.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 01:11 PM ---------- Previous post was at 12:53 PM ----------
ranterbul said:
I am also very new to all of this. I wanted to use the GS3 toolkit to root my s3. It said to use the casual gs3 unlock tool. I downloaded and ran the program. I have no idea if it took. it said done, i have no idea if the insecure aboot took either. so i moved on. I was running the donate and updated version of the GS3Toolkit . It was going fine until Odin failed. I have no idea if i did anything at all or is everything the same before i ever started. Im on 4.4.2 with a build of rbmf1. How do i check if anything worked. Definitely not rooted. Please help ,thanks.
Odin displays the following fail:
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<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
I'm not sure if the toolkit will work on the updated version of jellybean. The only 2 methods I'm aware of that will root your phone are beans 1 click casual method located here; http://forum.xda-developers.com/showthread.php?t=2332825 or openyoureyes method located here: http://forum.xda-developers.com/showthread.php?t=2046439.
Once done, verify SuperSU is installed and you are rooted. Sometimes these methods don't successfully unlock your Bootloader, so make sure it's unlocked with ez unlock version 1.2.
Sent from my SCH-I535 using Tapatalk 2
When I use the ROM manager, I downloaded the cm10 and gapps to my SD card. When I boot in recovery and go to install the cm10 zip, it acts like it is working but then just boots back up as normal. Do I have to only download cm10 and gapps to my computer first and then to the phone? Guess the ROM manager just seems to easy.
Sent from my SCH-I535 using Tapatalk 2
kcoop99 said:
When I use the ROM manager, I downloaded the cm10 and gapps to my SD card. When I boot in recovery and go to install the cm10 zip, it acts like it is working but then just boots back up as normal. Do I have to only download cm10 and gapps to my computer first and then to the phone? Guess the ROM manager just seems to easy.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Now I'm just being a PITA. When I go to add CM10 from the zip, I get "failed to verify whole file signature" then it just reboots normally. I have allowed installation from unknown sources.
That's a script check in recovery causing it to fail. What version of recovery do you have, name and numbers please?
Lies, spewed poetically from galaxy S3!
---------- Post added at 02:59 AM ---------- Previous post was at 02:58 AM ----------
Also, are you doing the proper wipes first? Wipe cache dalvik cache and data?
Lies, spewed poetically from galaxy S3!
kcoop99 said:
Now I'm just being a PITA. When I go to add CM10 from the zip, I get "failed to verify whole file signature" then it just reboots normally. I have allowed installation from unknown sources.
Click to expand...
Click to collapse
Are you flashing in recovery? Unknown sources has nothing to do with rom installation.
Go to the original development thread and find cm10. Download that copy and the most recent gapps. Follow their directions exactly and it will work. You might have a bad copy.
Also it sounds like you're pulling something out of the zip, the entire zip file gets flashed, you shouldn't open it or pull anything out.
Sent from my SCH-I535 using Tapatalk 2
SUCESS!!! But I don't have data! I tried restoring and then reflashing cm10. The cm10 I downloaded was not a nightly. I downloaded a stable version. I download the most recent gapps. I tried searching this forum for answers but itn was getting late so any direction to a helpful thread wouldn be greatly appreciated.
Sent from my SCH-I535 using Tapatalk 2
kcoop99 said:
SUCESS!!! But I don't have data! I tried restoring and then reflashing cm10. The cm10 I downloaded was not a nightly. I downloaded a stable version. I download the most recent gapps. I tried searching this forum for answers but itn was getting late so any direction to a helpful thread wouldn be greatly appreciated.
Click to expand...
Click to collapse
Don't mess with the stable versions, just grab the latest nightly. Also make sure subscription is set to RUIM/SIM in mobile networks under settings and network mode is automatic.
We are getting closer!! I deleted the zips I had and redownloaded the latest nightly and reinstalled gapps. The phone boots up asks to select language and shows 4G at the top :good: BUT while it is waiting for the network and after the activation, it says I need to reboot to complete activation. It's a vicious circle......
So, how do I get it to actually take? Flash back and back to CM again??
**EDIT**
I just kept letting it reboot. After about the 6th time it was activated. All is good to go as of now! I really appreciate the help! This forum is great!!
kcoop99 said:
We are getting closer!! I deleted the zips I had and redownloaded the latest nightly and reinstalled gapps. The phone boots up asks to select language and shows 4G at the top :good: BUT while it is waiting for the network and after the activation, it says I need to reboot to complete activation. It's a vicious circle......
So, how do I get it to actually take? Flash back and back to CM again??
**EDIT**
I just kept letting it reboot. After about the 6th time it was activated. All is good to go as of now! I really appreciate the help! This forum is great!!
Click to expand...
Click to collapse
Spoke too soon!!! Cannot call or text........try a previous nightly??
Go to settings>about phone> and what baseband version number? Then look in status and make sure your imei matches the one under your battery in back of phone.
I've never used casual and the route you took but you did unlock your boot loader correct?
I'm sending you a PM.
Lies, spewed poetically from galaxy S3!
I rooted my phone the other day using this thread: http://forum.xda-developers.com/showthread.php?t=2046439. Then I tried to install MOAR rom and it didn't work, weird I thought. So I flashed my phone back to the recovery image I made before installing MOAR. However, my phone would start to randomly turn off. Well the screen would turn off and nothing would help to turn the phone back on unless I remove the battery and reboot. One of those time, it got stuck on the galaxy s3 screen and wouldn't go anywhere.
I tried reflashing a rom and it said that it couldn't mount my /system. So then I looked into this guide: http://www.androidauthority.com/galaxy-s3-i535-unbrick-soft-brick-125413/. Right now I'm trying to install the VRALEC bootloader and it gets stuck on the sbl2.mbn file. It's probably been like that for half an hour now. I've tried turning off odin and rebooting into download mode and trying different cables, but to no avail. Is there anything else that anyone can suggest me doing?
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRALEC.bootchain.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> rpm.mbn
<ID:0/007> sbl1.mbn
<ID:0/007> sbl2.mbn
This is the Odin log. I'm using Odin 3.07
My suggestion is to flash one of the rooted stock ROMs through Odin. There's a thread in android development that has rooted stock. Then when that's done boot up your phone. Then use Ez-Unlock 1.2 to unlock your bootloader. Make sure it's 1.2. Now use GooManager to flash TWRP. You are done! This is probably the easiest way to do this.
Thread: http://forum.xda-developers.com/showthread.php?p=33948598
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
My suggestion is to flash one of the rooted stock ROMs through Odin. There's a thread in android development that has rooted stock. Then when that's done boot up your phone. Then use Ez-Unlock 1.2 to unlock your bootloader. Make sure it's 1.2. Now use GooManager to flash TWRP. You are done! This is probably the easiest way to do this.
Thread: http://forum.xda-developers.com/showthread.php?p=33948598
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Thanks for the advice. I tried it and for whatever reason it gets to NAND WRITE START after sbl2.mbn and then doesn't do anything else. Any chance I've actually hard bricked my device? Or is that term only used for phones that cannot boot into download mode? And what is sbl2.mbn?
Check md5 it may be a bad download.
Sent from my SCH-I535 using Tapatalk
Okay I checked the md5, it checked out. I tried a different file from that thread and it still halts when it gets to sbl2.mbn. This is really frustrating..
Another question. If I installed the Sprint MOAR rom instead of the Verizon MOAR rom, is there any chance I would still be able to boot into download mode? Because I might have done that. I think I googled galaxy s3 moar rom and got to the sprint page, but I'm not completely sure. I deleted the files I used because I was running out of space on my hard drive so I can't check them.
nike t said:
Another question. If I installed the Sprint MOAR rom instead of the Verizon MOAR rom, is there any chance I would still be able to boot into download mode? Because I might have done that. I think I googled galaxy s3 moar rom and got to the sprint page, but I'm not completely sure. I deleted the files I used because I was running out of space on my hard drive so I can't check them.
Click to expand...
Click to collapse
You could check your browser history. Btw, it sounds like you may need to reflash a pit file to get around all your issues. Idk if that will definitively resolve your issues though.
Sent from my SCH-I535 using Tapatalk 4
Awesome, I think that would be good to try. Is this the pit file I need? http://forum.xda-developers.com/showthread.php?p=30547929 and then would I just use one of the ROM's from the thread that Sandman posted? Or would I be using the stock ROM from samsung-updates?
nike t said:
Awesome, I think that would be good to try. Is this the pit file I need? http://forum.xda-developers.com/showthread.php?p=30547929 and then would I just use one of the ROM's from the thread that Sandman posted? Or would I be using the stock ROM from samsung-updates?
Click to expand...
Click to collapse
Try using one from samsung-updates, it will wipe /sdcard though which is the internal storage. To clarify, our phone is SCH-i535 (or d2vzw) so do not flash anything in Odin unless it's meant for our device.
Okay so I got the vzw-i535vbrmf1-20130627174111.zip file and the sch-i535-16gb.pit file. I just put the zip file in the pda spot and then the pit file in the pit section and then check repartition and hit start right? I'm just trying not to screw this part up because I know I'll hard brick it if I do.
edit: I'm guessing I need to unzip it to get the tar out first
Update: I tried the pit and vbrmf file and it wouldn't go past nand write!!!!... Could this be a motherboard issue?
nike t said:
Okay so I got the vzw-i535vbrmf1-20130627174111.zip file and the sch-i535-16gb.pit file. I just put the zip file in the pda spot and then the pit file in the pit section and then check repartition and hit start right? I'm just trying not to screw this part up because I know I'll hard brick it if I do.
edit: I'm guessing I need to unzip it to get the tar out first
Update: I tried the pit and vbrmf file and it wouldn't go past nand write!!!!... Could this be a motherboard issue?
Click to expand...
Click to collapse
Hmm, why is it getting stuck at that same point? Are you using the Samsung OEM cable? Able to try a different port or try this on another computer? And to clarify, you are pressing "Start" correct?
I wish I could tell you why it always stops at the same spot :/.I am using the OEM cable and tried different ports on the ccomputer and multiple versions of Odin. I haven't tried another computer though. I'll try that soon. And yes I am pressing start. I don't know what's happening
nike t said:
I wish I could tell you why it always stops at the same spot :/.I am using the OEM cable and tried different ports on the ccomputer and multiple versions of Odin. I haven't tried another computer though. I'll try that soon. And yes I am pressing start. I don't know what's happening
Click to expand...
Click to collapse
Maybe uninstall the Samsung drivers, reboot the computer, then put your S3 into download mode and plug it into your computer to force install new drivers. Once it installs new drivers, boot the phone back into download mode and try again with Odin. If its a laptop, keep it plugged into the wall outlet.
So I tried what you just suggested (uninstalling the samsung drivers and then rebooting the computer) and then also tried writing the stock image from a different computer. I'm getting the same problem. It will not get past the "NAND Write Start!!" part..
Would trying the debrick image on an SD card work for me? Or is that mostly just to be able to get the phone into boot mode and then from there flash the regular image? I'm so extremely confused why this is happening to my phone
EDIT: http://forum.xda-developers.com/showthread.php?t=2345831. I'm now reading this thread. It says that if flashing a pit file fails my phone is dead, and the motherboard is screwed. True story? I also know this is for Samsung Galaxy S2, but I thought that the same would apply to the S3
EDIT2: http://forum.xda-developers.com/showthread.php?t=1457458. Now I'm reading this thread. Could I have a NAND corruption? Again I know this says Galaxy S2, I'm just trying to get as much information as I can
Sorry for the double post, but I found this thread and I'm beginning to think that "nand erase all" might help. I have the official rom from samsung-updates for the vbrmf1 firmware. If I flash that while having the nand erase all checkbox checked does anything think that this would help me solve my problem? I read this thread: http://forum.xda-developers.com/showthread.php?t=1976695. There's also this thread that suggest the nand erase all: http://forums.androidcentral.com/sa...ot-flash-really-really-stuck-please-help.html.
If I do use nand erase, it'll be like the guide for soft bricking, but without flashing the bootchains. How necessary is it to flash those boot chains? Would I be able to try flashing them after I try flashing the stock rom? Or must the order of the soft brick thread by Hero an absolute?
Another question. What happens if I flash just a pit file without anything in the PDA section?
Okay, well I was able to get my recovery back after trying to flash my pit with the stock firmware checking nand erase all and repartition. In the end it failed because it said there was no pit partition.
However, now I'm unable to do a factory reset because it cannot mount system or cache. It also asks for a password when I first boot up the recovery. Anyone know what's going on?
nike t said:
Okay, well I was able to get my recovery back after trying to flash my pit with the stock firmware checking nand erase all and repartition. In the end it failed because it said there was no pit partition.
However, now I'm unable to do a factory reset because it cannot mount system or cache. It also asks for a password when I first boot up the recovery. Anyone know what's going on?
Click to expand...
Click to collapse
I just had all the issues you described on the latest TWRP when flashing a 4.4 ROM. Try the latest CWR. Format system and data using CWR 6.0.3.1
Sent from my SCH-I535 using Tapatalk
I tried CWR 6.0.1.2 and I was able to flash it, but I wasn't able to do a factory reset. It said that there was an error mounting /sdcard/.android_secure and it also says E format_volume: make_extf4fs failed on /dev/block/mmcblk0p17.
nike t said:
I tried CWR 6.0.1.2 and I was able to flash it, but I wasn't able to do a factory reset. It said that there was an error mounting /sdcard/.android_secure and it also says E format_volume: make_extf4fs failed on /dev/block/mmcblk0p17.
Click to expand...
Click to collapse
Use the latest version!
Sent from my SCH-I535 using Tapatalk
Alrighty, tried 6.0.4.3, no go. Thanks for all the help. I think the phone's done. It's gotta be some kind of nand problem. I'll probably send it in for JTAG or maybe try to transplant a motherboard from a different phone..
Hey guys,
I've been trying to figure this out for about the last 8 hours and have been hitting brick wall after brick wall.
I accidentally deleted all my system files on my phone when trying to install a new rom. I can no longer access TRWP recovery. Whenever I do I get the firmware upgrade encountered an issue error. I have plugged the phone into my computer but Kies can't connect to it. I have tried to reinstall 5.0 and I get sw rev check fail aboot fused 2 binary 1 error. I am currently downloading 4.4.2 to hope that this will work but I'm not sure on what to do now. Any help would be greatly appreciated.
Forget about Kies, you need to Odin'd the [ODIN][TAR][5.0] SM-G900P OA6 (Official!) - Full Restore (ROM, Modem, Kernel). This will get you back on stock Lollipop. Once you get that done, post back and I can give you instructions on Odin'ing TWRP and installing a custom rom if you want to.
Ramer said:
Forget about Kies, you need to Odin'd the [ODIN][TAR][5.0] SM-G900P OA6 (Official!) - Full Restore (ROM, Modem, Kernel). This will get you back on stock Lollipop. Once you get that done, post back and I can give you instructions on Odin'ing TWRP and installing a custom rom if you want to.
Click to expand...
Click to collapse
Downloading it right now. Will let you know what happens when I try to install it
kevorski said:
Downloading it right now. Will let you know what happens when I try to install it
Click to expand...
Click to collapse
I know I shouldn't have to ask this, but being as it's happened once before, I'm making an assumption that since you posted on a Sprint forum, you are on the Sprint network?
Ramer said:
I know I shouldn't have to ask this, but being as it's happened once before, I'm making an assumption that since you posted on a Sprint forum, you are on the Sprint network?
Click to expand...
Click to collapse
Yeah I'm on Sprint. Funny that you would have to ask that question
Ramer said:
Forget about Kies, you need to Odin'd the [ODIN][TAR][5.0] SM-G900P OA6 (Official!) - Full Restore (ROM, Modem, Kernel). This will get you back on stock Lollipop. Once you get that done, post back and I can give you instructions on Odin'ing TWRP and installing a custom rom if you want to.
Click to expand...
Click to collapse
So I downloaded the image and tried to flash it.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_SPT_G900PVPU1BOA6_G900PSPT1BOA6_CL3859396_QB3804569_REV00_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
This is the error I get when trying to flash it. Any ideas?
kevorski said:
So I downloaded the image and tried to flash it.
This is the error I get when trying to flash it. Any ideas?
Click to expand...
Click to collapse
Which OS are you running on PC? Also, use an MD5 checker to confirm good download.
Ramer said:
Which OS are you running on PC? Also, use an MD5 checker to confirm good download.
Click to expand...
Click to collapse
Windows 7 64bit I ran a checksum and they match
kevorski said:
Windows 7 64bit I ran a checksum and they match
Click to expand...
Click to collapse
I suspect I left out an important step, you need to be on the OA6 firmware to to install a lollipop rom and you may have wiped yours out. Odin this file, it's the OA6 firmware and KT TWRP.
Before you do this, if you have an extSD, this is the link for MOAR, you can try any rom you want, but let's attempt to get you going on a rom I'm familiar with. You need to copy the rom to your extSD beforehand. Download link is about half way down to OP.
So, to recap:
1. Download and copy MOAR to extSD and put back in your phone.
2. Odin OA6 firmware with TWRP. (Turn off auto-reboot, as you don't have a system to boot into)
3. After it PASSES, unplug from PC and pull the battery. Wait a few seconds and put battery back in and go into recovery mode (Volume UP, Home and Power).
4. If all goes well, TWRP is loaded and you can now navigate to you extSD and flash MOAR. (Clean install etc and remember, first boot can take about 20 minutes.
Ramer said:
I suspect I left out an important step, you need to be on the OA6 firmware to to install a lollipop rom and you may have wiped yours out. Odin this file, it's the OA6 firmware and KT TWRP.
Before you do this, if you have an extSD, this is the link for MOAR, you can try any rom you want, but let's attempt to get you going on a rom I'm familiar with. You need to copy the rom to your extSD beforehand. Download link is about half way down to OP.
So, to recap:
1. Download and copy MOAR to extSD and put back in your phone.
2. Odin OA6 firmware with TWRP. (Turn off auto-reboot, as you don't have a system to boot into)
3. After it PASSES, unplug from PC and pull the battery. Wait a few seconds and put battery back in and go into recovery mode (Volume UP, Home and Power).
4. If all goes well, TWRP is loaded and you can now navigate to you extSD and flash MOAR. (Clean install etc and remember, first boot can take about 20 minutes.
Click to expand...
Click to collapse
I still get the same error as above.
kevorski said:
I still get the same error as above.
Click to expand...
Click to collapse
Shoot. Sorry I'm out of ideas Maybe someone else can help?
Some other thoughts, Try updating your Samsung drivers. Reboot your PC. (Actually, try that first) Try a different USB port and a different cable. Make sure you see the blue COM:ID button in Odin.
Ramer said:
Shoot. Sorry I'm out of ideas Maybe someone else can help?
Some other thoughts, Try updating your Samsung drivers. Reboot your PC. (Actually, try that first) Try a different USB port and a different cable. Make sure you see the blue COM:ID button in Odin.
Click to expand...
Click to collapse
Hey Ramer,
Just wanted to let you know that I took the device to someone that does this for a living and found out that I had fried my bootloader. Didn't know if you wanted to know about the status. I have it up and running now with it rooted and running lollipop. Thanks for all the help that you provided.
kevorski said:
Hey Ramer,
Just wanted to let you know that I took the device to someone that does this for a living and found out that I had fried my bootloader. Didn't know if you wanted to know about the status. I have it up and running now with it rooted and running lollipop. Thanks for all the help that you provided.
Click to expand...
Click to collapse
Good to hear, but slightly confused. The bootloader (firmware) can be odin'd and if you installed the full OD3 stock tar it would have been included. Regardless, glad you're up and running.
Well now after I did a backup of the stock rom the guy put on it is locked up...again.
So my galaxy amp prime(Cricket, SM-J320AZ) is stuck in a bootloop, and I have tried to research why, yet every reason seams plausible. So ill start at the beginning...
I used odin with a boot.tar in the ap slot so that kingroot could root my phone. it was successful at rooting my device but refused to switch with supersu me( I now know I needed kingroot 4.5) anyways kingroot deployed as a system app which in turn compromised my safetynet status. I couldn't use a number of apps and services, so I decided to flash the stock rom for my device (found here on xda) it was a little over 1gb and I followed directions. yet when odin successfully flashed it, the device rebooted and now is stuck in a bootloop. it loads the Samsung logo twice then reverts to the android recovery. I tried to wipe cache partition and reboot to no avail. I then tried to wide data/factory reset and reboot, but its still stuck in bootloop.
I originally made a backup with Samsung smart switch, but now it says the device is unsupported.
Is there anything I can do? ive read soft bricks and bootloops can be fixed, but I'm not finding much on my device. any help is greatly appreciated,
sorry if this is in the wrong area, I'm still new to xda
Rororoolz said:
So my galaxy amp prime(Cricket, SM-J320AZ) is stuck in a bootloop, and I have tried to research why, yet every reason seams plausible. So ill start at the beginning...
I used odin with a boot.tar in the ap slot so that kingroot could root my phone. it was successful at rooting my device but refused to switch with supersu me( I now know I needed kingroot 4.5) anyways kingroot deployed as a system app which in turn compromised my safetynet status. I couldn't use a number of apps and services, so I decided to flash the stock rom for my device (found here on xda) it was a little over 1gb and I followed directions. yet when odin successfully flashed it, the device rebooted and now is stuck in a bootloop. it loads the Samsung logo twice then reverts to the android recovery. I tried to wipe cache partition and reboot to no avail. I then tried to wide data/factory reset and reboot, but its still stuck in bootloop.
I originally made a backup with Samsung smart switch, but now it says the device is unsupported.
Is there anything I can do? ive read soft bricks and bootloops can be fixed, but I'm not finding much on my device. any help is greatly appreciated,
sorry if this is in the wrong area, I'm still new to xda
Click to expand...
Click to collapse
Point to the firmware you downloaded and also which version of odin you used.
ashyx said:
Point to the firmware you downloaded and also which version of odin you used.
Click to expand...
Click to collapse
I extracted this
AP_J320AUCS2AQA1_CL7663112_QB12351033_REV00_user_low_ship.tar
i believe is the firmware, and I'm using odin 3.11.1
I also asked in page 17 of the original thread
I'm just running out of options here lol
you actually posted right above me in that thread!
Rororoolz said:
I extracted this
AP_J320AUCS2AQA1_CL7663112_QB12351033_REV00_user_low_ship.tar
i believe is the firmware, and I'm using odin 3.11.1
I also asked in page 17 of the original thread
I'm just running out of options here lol
Click to expand...
Click to collapse
I suggest you flash the entire firmware not just AP.
ashyx said:
I suggest you flash the entire firmware not just AP.
Click to expand...
Click to collapse
Do u happen to know where i can find the rest?
Would i have to re partition it? Because im trying to research and learn, but i was under the impression that AP was the only spot to put firmware
I believe your proper firmware would be J320AZTUU1APC4
http://www.mediafire.com/file/skiapd1xqj3s7se/J320AZTUU1APC4_J320AZAIO1APC4_5.1.1_USA_4Files.zip
seaf0ur said:
I believe your proper firmware would be J320AZTUU1APC4
http://www.mediafire.com/file/skiapd1xqj3s7se/J320AZTUU1APC4_J320AZAIO1APC4_5.1.1_USA_4Files.zip
Click to expand...
Click to collapse
The files say md5 error, binary failed
I think im missing something here
You tried to flash only AP but for J320A, here you have full firmware for J320AZ: https://drive.google.com/file/d/0B5vkBxwCY_cCSkh0UHNZMmxmcVk/view
johnny.goldy said:
You tried to flash only AP but for J320A, here you have full firmware for J320AZ: https://drive.google.com/file/d/0B5vkBxwCY_cCSkh0UHNZMmxmcVk/view
Click to expand...
Click to collapse
Most these files worked, i checked auto reboot, re partition, and r reset. I set the pit file and all 4 others in correct spot. Yet it failed a few times. I unchecked the bl file and it succeeded. When i reboot it shows logo twice then shows android saying installing sys update.... then error... then goes back to recovery.
Essentially i flashed everything except the bl file. And when i try to flash it by itself it says
Initialization
Erase...
Set PIT file
DO NOT TURN OFF TARGET
get pit for mapping
Firmware update starting
Single download
Sboot.bin
NAND write start!
Fail!
Complete(write) operation fail
............
Im guessing the problem is with my BL file
When i go to boot phone it shows an android and says installing system update then says error very quickly and goes to recovery.
I feel like thats progress but why would only BL file be failing? The green bar in odin goes halfway then fails (with only bl file checked)
Rororoolz said:
Most these files worked, i checked auto reboot, re partition, and r reset. I set the pit file and all 4 others in correct spot. Yet it failed a few times. I unchecked the bl file and it succeeded. When i reboot it shows logo twice then shows android saying installing sys update.... then error... then goes back to recovery.
Essentially i flashed everything except the bl file. And when i try to flash it by itself it says
Initialization
Erase...
Set PIT file
DO NOT TURN OFF TARGET
get pit for mapping
Firmware update starting
Single download
Sboot.bin
NAND write start!
Fail!
Complete(write) operation fail
............
Im guessing the problem is with my BL file
When i go to boot phone it shows an android and says installing system update then says error very quickly and goes to recovery.
I feel like thats progress but why would only BL file be failing? The green bar in odin goes halfway then fails (with only bl file checked)
Click to expand...
Click to collapse
It WILL fail at the bootloader as it's not intended for your device. Just flash the correct firmware as advised.
ashyx said:
It WILL fail at the bootloader as it's not intended for your device. Just flash the correct firmware as advised.
Click to expand...
Click to collapse
Thats what i mean, i extracted all 5 files as advised(a few comments ago) it had
BL
AP
CP
CSC
PIT
I placed them in corresponding odin slot (even pit, with re partition) yet it fails at the BL slot)
I flash it all except bl its still in bootloop
Also Says dm-verity verification failed
Mind you, that i am flashing the right firmware now. I realize my original mistake by flashing the 320a. But these are the stock 320AZ files i am now speaking of...
Rororoolz said:
Thats what i mean, i extracted all 5 files as advised(a few comments ago) it had
BL
AP
CP
CSC
PIT
I placed them in corresponding odin slot (even pit, with re partition) yet it fails at the BL slot)
I flash it all except bl its still in bootloop
Also Says dm-verity verification failed
Mind you, that i am flashing the right firmware now. I realize my original mistake by flashing the 320a. But these are the stock 320AZ files i am now speaking of...
Click to expand...
Click to collapse
This probably means you had a newer firmware revision on your device.
ashyx said:
This probably means you had a newer firmware revision on your device.
Click to expand...
Click to collapse
So do i have any options left? Or should i just chuck it into the cornfield
Rororoolz said:
So do i have any options left? Or should i just chuck it into the cornfield
Click to expand...
Click to collapse
Of course you probably just need the revision 3 firmware. It's posted at the link below.
https://forum.xda-developers.com/galaxy-j3-2016/development/odin-j320a-j320az-links-t3631914
J320AZTUS3AQG1
Try this one: https://www.androidfilehost.com/?fid=817550096634792721
johnny.goldy said:
Try this one: https://www.androidfilehost.com/?fid=817550096634792721
Click to expand...
Click to collapse
IT WORKED! Omg IT wOrked!
ashyx said:
Of course you probably just need the revision 3 firmware. It's posted at the link below.
https://forum.xda-developers.com/galaxy-j3-2016/development/odin-j320a-j320az-links-t3631914
J320AZTUS3AQG1
Click to expand...
Click to collapse
It wasnt the firmware you said, but thank you so much for the help!
Rororoolz said:
It wasnt the firmware you said, but thank you so much for the help!
Click to expand...
Click to collapse
Doesn't matter it was still revision 3 firmware.
The one linked is the latest revision 3 firmware.