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!
Related
Followed root guide http://forum.xda-developers.com/showthread.php?t=1657056 to the letter.
Odin loads and installs the downloaded recovery file. When I boot into recovery, it loads the stock android recovery instead of CWM.
I have downloaded the files several times, made sure the drivers are updated and installed and I still get the same result.
When in download mode, it says Custom Binary Download: Yes (10 counts)
Any help would be appreciated. Thanks!
Try the updated CWM recovery in my guide.
No joy! Downloaded your CWM recovery on a different pc and after flashing with Odin, I still can only boot to the stock android recovery.
My counter went up one more time. Pure frustration at this point!
I'm having the same problem on my 3113. I tried several times, odin says everything is good, count goes up and still Android recovery.
sent from my Samsung Galaxy Tab 2 7.0
i have same proglem on GT-P5100.. what should i do.. :crying:
I can't guarantee this will fix it, buy you should try restoring to stock 4.0.3.
Rolled back to 4.03 and everything works great! Big thanks for your help!
How to rollback to 4.0.3?
I see folks talking about rollback to 4.0.3, yet no one explains how to do it or where to get the firmware image from! As far as I can tell, I have to have root access before I can flash anything. My device is reporting that it is not properly rooted. What do I do next? I've successfully rooted my EVO and my Galaxy Nexus, but the GTab2 has me stumped.
Widedomain said:
Rolled back to 4.03 and everything works great! Big thanks for your help!
Click to expand...
Click to collapse
Same but with Heimdall. Well at least it is awesome Windows users experience the same troubles. This improves chances that somebody has enough rating here to post to the ClockworkMod recovery thread.
Widedomain said:
Followed root guide http://forum.xda-developers.com/showthread.php?t=1657056 to the letter.
Odin loads and installs the downloaded recovery file. When I boot into recovery, it loads the stock android recovery instead of CWM.
I have downloaded the files several times, made sure the drivers are updated and installed and I still get the same result.
When in download mode, it says Custom Binary Download: Yes (10 counts)
Any help would be appreciated. Thanks!
Click to expand...
Click to collapse
Look in the general thread. Links to 5110 and 5100 are in a guide thread that includes returning to stock in the title. The 5113 is in a different thread titled something like 5113 stock firmware
Sent from my XT860 using xda premium
Widedomain said:
Rolled back to 4.03 and everything works great! Big thanks for your help!
Click to expand...
Click to collapse
4.0.3 - no joy
Endoroid said:
Look in the general thread. Links to 5110 and 5100 are in a guide thread that includes returning to stock in the title. The 5113 is in a different thread titled something like 5113 stock firmware
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
The problem appears to be that Samsung has gotten cute and restores stock recovery during the boot.
This isn't very nice -- they did the same thing with a recent update on their SGS-II phones as well, and I don't remember how I got around it.
Genesis3 said:
The problem appears to be that Samsung has gotten cute and restores stock recovery during the boot.
This isn't very nice -- they did the same thing with a recent update on their SGS-II phones as well, and I don't remember how I got around it.
Click to expand...
Click to collapse
I noticed this first on my Thrive tablet, then noticed it again on the 4.0.4 update. Once you are rooted, you can rename (If memory serves) /system/etc/install-recovery.sh to something like /system/etc/install-recovery.bak
Then go back into download mode and reflash cwm recovery.
I incremented my flash count by about 5 before I remembered about this.
If you do not rename that script, by the time you see your boot animation, the stock recovery will have already overwritten your custom recovery..
MultipleMonomials said:
Try the updated CWM recovery in my guide.
Click to expand...
Click to collapse
I was going to follow your guide, which is well organized, but the firmware download for my p5113 is no longer supported by that site.
Widedomain said:
(...)
Odin loads and installs the downloaded recovery file. When I boot into recovery, it loads the stock android recovery instead of CWM.
(...)
Click to expand...
Click to collapse
That´s the trick:
Uncheck "Auto-Reboot" in Odin.
If Odin finished flashing: wait one minute.
Now DIRECTLY boot from Downloadmode into Recovery - don´t reboot into System!
Now enjoy CWM - no need to do this again
Hello everybody, new member here. I have recently rooted and installed CyanogenMod 10 on my Samsung galaxy s blaze 4g to test it out and I just feel weird with it. Is there anyway to return back to stock android Gingerbread? I've tried everything but it keeps returning me to CyanogenMod. Please and thank you.
Neekoh said:
Hello everybody, new member here. I have recently rooted and installed CyanogenMod 10 on my Samsung galaxy s blaze 4g to test it out and I just feel weird with it. Is there anyway to return back to stock android Gingerbread? I've tried everything but it keeps returning me to CyanogenMod. Please and thank you.
Click to expand...
Click to collapse
For samsung official (no root) go to this thread and download the file: http://forum.xda-developers.com/showthread.php?t=1917570
download Odin (look for k0nane's post in the dev thread). flash the tar.md5 file from the first thread. click on phone and navigate to where you downloaded it. UNCHECK REPARTITION. if you dont, you'll brick your phone... boot into download mode, and then flash it. you'll be stock.
for the future, you can get a long way by using the search feature...
im new here and ned some help
jparnell8839 said:
For samsung official (no root) go to this thread and download the file: http://forum.xda-developers.com/showthread.php?t=1917570
download Odin (look for k0nane's post in the dev thread). flash the tar.md5 file from the first thread. click on phone and navigate to where you downloaded it. UNCHECK REPARTITION. if you dont, you'll brick your phone... boot into download mode, and then flash it. you'll be stock.
for the future, you can get a long way by using the search feature...
Click to expand...
Click to collapse
i did everything in this thread and worked, but now i cant go pass the setup screen just keep showing errors saying everything stoped working any ideas
jparnell8839 said:
For samsung official (no root) go to this thread and download the file: http://forum.xda-developers.com/showthread.php?t=1917570
download Odin (look for k0nane's post in the dev thread). flash the tar.md5 file from the first thread. click on phone and navigate to where you downloaded it. UNCHECK REPARTITION. if you dont, you'll brick your phone... boot into download mode, and then flash it. you'll be stock.
for the future, you can get a long way by using the search feature...
Click to expand...
Click to collapse
You probably dirty flashed, install cwm for the stock firmware you flashed via odin. Once installed go into cwm and wipe everything; data/factory reset, wipe cache, dalvik cache, and fix permissions. Try that and it should be able to workagain. Also you might have the wrong baseband installed.
Sent from my SGH-T769 using xda app-developers app
I have an unlocked CDMA/GSM Galaxy S7 rooted using the guide at https://forum.xda-developers.com/ve...to-notes-root-install-xposed-unroot-t3411039/ and I'm trying to download TWRP for it. I've tried using the official TWRP app to try to flash twrp-3.1.0-0-heroqltechn to recovery and first I flashed the one that wasn't a tar because I thought it was the one that was a tar, but apparently the ones that are a tar simply don't show up when you attempt to select a file so I can't use them. That and I forgot to unlock OEM. Of course that caused it to get stuck at the boot failure screen so I just reflashed the rooted boot it was using and it worked fine again. Then I tried to install manually using Odin3.12 and when I try, it failed and the log says
1: Added!!
2: Odin engine v(ID:3.1203)
3: File analysis..
4:SetupConnection..
5: Initialzation..
6: Get PIT for mapping..
7: Firmware update start..
8: SingleDownload.
9: recovery.img
10: RQT_CLOSE !!
11: (nothing)
12: Complete(Write) operation failed.
<OSM> All Threads Completed. (succeed 0 / failed 1)
Then I try flashify to flash the tar to recovery and it says File could not be loaded.
I'm pretty much at an impasse here, so I'm posting here. By the way if anyone has any solid guides on how to pass safetynet for pokemon go with root that would be great too, thanks.
Pretty sure the U variant have locked bootloader dispite being carrier unlocked.
Colonel Kernel said:
I have an unlocked CDMA/GSM Galaxy S7 rooted using the guide at https://forum.xda-developers.com/ve...to-notes-root-install-xposed-unroot-t3411039/ and I'm trying to download TWRP for it. I've tried using the official TWRP app to try to flash twrp-3.1.0-0-heroqltechn to recovery and first I flashed the one that wasn't a tar because I thought it was the one that was a tar, but apparently the ones that are a tar simply don't show up when you attempt to select a file so I can't use them. That and I forgot to unlock OEM. Of course that caused it to get stuck at the boot failure screen so I just reflashed the rooted boot it was using and it worked fine again. Then I tried to install manually using Odin3.12 and when I try, it failed and the log says
s.
Click to expand...
Click to collapse
Eric1084 said:
Pretty sure the U variant have locked bootloader dispite being carrier unlocked.
Click to expand...
Click to collapse
Hi +1 Eric1084
Bootloader is locked impossible to get TWRP in the USA version
On Chinese Snapdragons is possible...
https://forum.xda-developers.com/ga...gon/recovery-official-twrp-galaxy-s7-t3458579
MAX 404 said:
Hi +1 Eric1084
Bootloader is locked impossible to get TWRP in the USA version
On Chinese Snapdragons is possible...
https://forum.xda-developers.com/ga...gon/recovery-official-twrp-galaxy-s7-t3458579
Click to expand...
Click to collapse
Well thats just groovy. Everytime I try to reboot it goes into recovery boot failure. Any way to fix?
I'm going to try to flash the stock firmware for this phone from sammobile, G930UOYM4APL2_XAA and pray it fixes the recovery boot. If that doesn't work I might try to hard reset the phone, but I'm not sure if that will damage it in any way so I'm a little reluctant. If neither work I have a specialist man who usually knows what he's doing, so I'll take it to him after that. Any advice would be greatly appreciated
Looks like flashing the stock firmware worked. Unrooted and everything, no bootloop or anything anymore. Shame though, wish I could have root and pass safetynet
According to the Verizon Galaxy S5 Update Page:
Android® security patches and bug fixes.
Resolved a ring-back tone issue on calls to non-Verizon phones.
Fixed an issue where some users reported difficulty making calls to non-Verizon customers.
Click to expand...
Click to collapse
The security patch included is (most likely) the July one, since Samsung also just released a new software update to international models which includes the July security patch and Verizon has been updating the "Galaxy S" series phones with the July update over the past few weeks.
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQF2_G900VVZW2DQF2_G900VVRU2DQF2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQF2_G900VVZW2DQF2_G900VVRU2DQF2_HOME_No_Aboot.tar.md5.zip
Appreciate that, but how do you get the Odin firmware file out of curiosity?
drewcu said:
Appreciate that, but how do you get the Odin firmware file out of curiosity?
Click to expand...
Click to collapse
Updato is one way; this shows the list for the Verizon S5 with the most recent at the top; they haven't gotten the new update up yet though.
I think that another way would be for someone to dig through the update.zip file which would be on the phone of someone who got the OTA update downloaded but had not yet installed it yet.
To confirm, the only thing that's different between the dev-friendly version (when it comes out) and the stock is the missing aboot? Thanks again.
drewcu said:
To confirm, the only thing that's different between the dev-friendly version (when it comes out) and the stock is the missing aboot? Thanks again.
Click to expand...
Click to collapse
Yes and the firmware just came out today so I'm currently in the process of uploading both versions.
Dudash said:
Yes and the firmware just came out today so I'm currently in the process of uploading both versions.
Click to expand...
Click to collapse
Is this flashable with Odin only or possibly need to already be on a specific kernal? I have tried on two S5900V's through TWRP and both result in a failure message. Both are on jkruse de-bloated MM rom at the moment.
Kaliaila said:
Updato is one way; this shows the list for the Verizon S5 with the most recent at the top; they haven't gotten the new update up yet though.
I think that another way would be for someone to dig through the update.zip file which would be on the phone of someone who got the OTA update downloaded but had not yet installed it yet.
Click to expand...
Click to collapse
The link for the update zip is not working when you tap or click on it
Sent from my SM-G900V using Tapatalk
---------- Post added at 11:25 AM ---------- Previous post was at 11:16 AM ----------
No one believe update.zip files anymore ? i need one badley
Sent from my SM-G900V using Tapatalk
Kastro1784 said:
The link for the update zip is not working when you tap or click on it
Sent from my SM-G900V using Tapatalk
---------- Post added at 11:25 AM ---------- Previous post was at 11:16 AM ----------
No one believe update.zip files anymore ? i need one badley
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
Odd. It works for me.
Sent from my SM-G900V using Tapatalk
Since no one wanted to chime in and help me out in my post, you need to unzip the file and load the md5 into Odin's AP slot and flash it. Then let the phone do its thing and flash the latest TWRP with odin after. Then go back into TWRP and flash supersu to gain root again. Trying to flash right within TWRP is not an option, not sure why its not explained.
So this update wont "factory reset" my device?
AWESOME1092387456 said:
So this update wont "factory reset" my device?
Click to expand...
Click to collapse
I dirty flashed two S5's last night with Odin, no factory reset and both phones kept their bootloaders un touched since unlocked. :good:
stuck on Verizon boot screen
After the update via OTA, my aunt's phone has been stuck on Verizon boot screen. Tried booting into safe mode, with same result. Any ideas on how not to lose all her data? Thanks!
This sucks I wanna download this so bad but my computer is down smdh is it possible someone can make and ota update zip file for me so can flash this through stock recovery on my phone ?
Sent from my SM-G900V using Tapatalk
I guess no one knows how to do it huh smdh
Sent from my SM-G900V using Tapatalk
Rumsfield said:
I dirty flashed two S5's last night with Odin, no factory reset and both phones kept their bootloaders un touched since unlocked. :good:
Click to expand...
Click to collapse
Did you loose root?
I dirty flashed and lost root, was unable to get it back.
Reloaded TWRP via Odin and then flashed SuperSU, nothing. Wiped and restore backup all good. ..
mastertech007 said:
Did you loose root?
I dirty flashed and lost root, was unable to get it back.
Reloaded TWRP via Odin and then flashed SuperSU, nothing. Wiped and restore backup all good. ..
Click to expand...
Click to collapse
I always flash super su and whatever else I need in recovery after I've flashed the rom so I cant give you a definitive answer. Both phones did upgrade without data loss and now advanced calling/wifi calling actually work now which is why I flashed in the first place.
Working?
Is this working? Ive tried everything and i have the Toshiba chip. Emmc 11. It soft bricks if i try to downgraded to stock builds.
JasonD1180 said:
Is this working? Ive tried everything and i have the Toshiba chip. Emmc 11. It soft bricks if i try to downgraded to stock builds.
Click to expand...
Click to collapse
The new file seemed to unlock boot loader. Couldnt get odin to flash twrp......
JasonD1180 said:
The new file seemed to unlock boot loader. Couldnt get odin to flash twrp......
Click to expand...
Click to collapse
If you flash the dev boot loader friendly version it wont screw with your bootloader whatsoever. Before you restart go back in TWRP and flash supersu to get root again. Saying it "unlocked boot loader" may cause confusion to people because it does not, you need to manually go from locked to DEV status via a few of the methods posted in here.
Rumsfield said:
If you flash the dev boot loader friendly version it wont screw with your bootloader whatsoever. Before you restart go back in TWRP and flash supersu to get root again. Saying it "unlocked boot loader" may cause confusion to people because it does not, you need to manually go from locked to DEV status via a few of the methods posted in here.
Click to expand...
Click to collapse
Ive not had twrp or root on this device but it went from saying vzw official binary to samsung original. Will i be able to root as long as twrp flashes?
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.