I have followed these instructions but I get stuck in a bootloop at 3:50 https://www.youtube.com/watch?v=k2oOvf5tOCY
Can anyone help me get past that?
KingKobra813 said:
I have followed these instructions but I get stuck in a bootloop at 3:50 https://www.youtube.com/watch?v=k2oOvf5tOCY
Can anyone help me get past that?
Click to expand...
Click to collapse
Yes wipe your storage n youll. Be good to go
pbedard said:
Yes wipe your storage n youll. Be good to go
Click to expand...
Click to collapse
I wiped my internal storage and I'm still getting stuck in at the same part. Do I need to wipe my external storage as well?
Bad download or wrong file? I think you should start over with fresh downloads, downloaded from your PC, not phone. Verify md5 checksum on the stock tar. Check your Samsung driver version as well.
http://forum.xda-developers.com/showthread.php?p=56853325
Download the CF Auto-Root specific to your device as well.
If you think your sdcard is suspect, just remove it or format it. Follow the usual advice: try another USB cable on the rear of PC (USB 2.0). The original Note 4 USB cable works for me.
BTW, if you're trying to get to lollipop, don't root until you take the OTA update.
samep said:
Bad download or wrong file? I think you should start over with fresh downloads, downloaded from your PC, not phone. Verify md5 checksum on the stock tar. Check your Samsung driver version as well.
http://forum.xda-developers.com/showthread.php?p=56853325
Download the CF Auto-Root specific to your device as well.
If you think your sdcard is suspect, just remove it or format it. Follow the usual advice: try another USB cable on the rear of PC (USB 2.0). The original Note 4 USB cable works for me.
BTW, if you're trying to get to lollipop, don't root until you take the OTA update.
Click to expand...
Click to collapse
Thank you. I will try that.
KingKobra813 said:
Thank you. I will try that.
Click to expand...
Click to collapse
Forgot to mention that Flashify has become a trusted source, to me and maybe others here. You can find it on Google Play and it will download TWRP, I recommend the non-zip latest one. Flashify will also automatically prompt you to install it from where it just downloaded it and checks its integrity. Since TWRP updates frequently, could be a manual step saver.
samep said:
Bad download or wrong file? I think you should start over with fresh downloads, downloaded from your PC, not phone. Verify md5 checksum on the stock tar. Check your Samsung driver version as well.
http://forum.xda-developers.com/showthread.php?p=56853325
Download the CF Auto-Root specific to your device as well.
If you think your sdcard is suspect, just remove it or format it. Follow the usual advice: try another USB cable on the rear of PC (USB 2.0). The original Note 4 USB cable works for me.
BTW, if you're trying to get to lollipop, don't root until you take the OTA update.
Click to expand...
Click to collapse
So I used a totally different computer and new cable and I'm still getting stuck at the exact same place. Everything on ODIN said it worked but my phone just bootloops.
1) Could you tell me what is your goal, please? Example: root stock, flash custom touchwiz or CM12 ROM. If touchwiz, are you referring to NIE, NK2, OB7?
2) Are you starting with a factory reset then stock tar?
There are alternate methods but knowing your goal could simplify the process or warrant starting over with NIE stock tar. For example, you could simply Odin TWRP recovery and then flash a rooted ROM zip or SuperSU zip in recovery. Another example: I and at least one other user trying to get to the OTA for 5.0.1 (OB7), had to Odin NIE stock tar and take two OTA updates to get lollipop.
http://download.chainfire.eu/supersu
This is a recovery flash that uses custom recovery to root; same developer, different approach. (For rooting stock. If a different ROM is your goal, it most likely includes this zip in its flash zip in a folder labeled supersu.)
Using the alternative methods, you'd skip Odin if CF Auto Root but still have to Odin latest TWRP.
http://www.techerrata.com/file/twrp2/trltespr/openrecovery-twrp-2.8.5.0-trltespr.img.tar
samep said:
1) Could you tell me what is your goal, please? Example: root stock, flash custom touchwiz or CM12 ROM. If touchwiz, are you referring to NIE, NK2, OB7?
2) Are you starting with a factory reset then stock tar?
There are alternate methods but knowing your goal could simplify the process or warrant starting over with NIE stock tar. For example, you could simply Odin TWRP recovery and then flash a rooted ROM zip or SuperSU zip in recovery. Another example: I and at least one other user trying to get to the OTA for 5.0.1 (OB7), had to Odin NIE stock tar and take two OTA updates to get lollipop.
http://download.chainfire.eu/supersu
This is a recovery flash that uses custom recovery to root; same developer, different approach. (For rooting stock. If a different ROM is your goal, it most likely includes this zip in its flash zip in a folder labeled supersu.)
Using the alternative methods, you'd skip Odin if CF Auto Root but still have to Odin latest TWRP.
http://www.techerrata.com/file/twrp2/trltespr/openrecovery-twrp-2.8.5.0-trltespr.img.tar
Click to expand...
Click to collapse
1)My goal is to just root stock
2) I'm starting with a factory reset. I don't really know what you mean by stock tar.
What I tried was. I followed the instructions to root my phone. It got stuck in a bootloop. I did a factory reset. Set up my phone. Tried to root again using ODIN. Still getting stuck in bootloop. Then I did another factory reset and I'm just stock but the strange thing is I have Super SU installed and all the bloatware I originally removed is gone but rootchecker says I don't have root. And strangely my WiFi won't work.
KingKobra813 said:
1)My goal is to just root stock
2) I'm starting with a factory reset. I don't really know what you mean by stock tar.
What I tried was. I followed the instructions to root my phone. It got stuck in a bootloop. I did a factory reset. Set up my phone. Tried to root again using ODIN. Still getting stuck in bootloop. Then I did another factory reset and I'm just stock but the strange thing is I have Super SU installed and all the bloatware I originally removed is gone but rootchecker says I don't have root. And strangely my WiFi won't work.
Click to expand...
Click to collapse
Root stock helps me some with your goal. The alternative method of Odin TWRP them flash the zip file in the previous post would be an option.
The time that you actually root is key to your goal and suggesting steps. If you want rooted lollipop, currently the only option is take OB7 OTA (over the air) update.
Furthermore, you're having Wi-Fi issues and can't root is an indication you need to flash stock firmware in Odin rather than just root. It's always a good idea to do this if you start having problems with booting after a flash or something is not working.
There's already a thread on getting to lollipop with OTA and rooting.
http://forum.xda-developers.com/showthread.php?p=59235259
You could follow that but I'd suggest adding an extra OTA and starting over at NIE stock tar since NK2 is giving you problems. The three alpha-numeric designations for firmware I gave indicate the original stock tar starting at NIE and then NK2 (both are KitKat ROMs). The initial lollipop ROM is OB7. The stock tars available are NIE and NK2 found below.
http://forum.xda-developers.com/showthread.php?p=56853325
samep said:
Root stock helps me some with your goal. The alternative method of Odin TWRP them flash the zip file in the previous post would be an option.
The time that you actually root is key to your goal and suggesting steps. If you want rooted lollipop, currently the only option is take OB7 OTA (over the air) update.
Furthermore, you're having Wi-Fi issues and can't root is an indication you need to flash stock firmware in Odin rather than just root. It's always a good idea to do this if you start having problems with booting after a flash or something is not working.
There's already a thread on getting to lollipop with OTA and rooting.
http://forum.xda-developers.com/showthread.php?p=59235259
You could follow that but I'd suggest adding an extra OTA and starting over at NIE stock tar since NK2 is giving you problems. The three alpha-numeric designations for firmware I gave indicate the original stock tar starting at NIE and then NK2 (both are KitKat ROMs). The initial lollipop ROM is OB7. The stock tars available are NIE and NK2 found below.
http://forum.xda-developers.com/showthread.php?p=56853325
Click to expand...
Click to collapse
I would lIke to stay on kitkat. What steps would you recommend for me to root my phone?
KingKobra813 said:
I would lIke to stay on kitkat. What steps would you recommend for me to root my phone?
Click to expand...
Click to collapse
1)Download the stock tar NK2, TWRP tar for Odin and supersu zip.
2)Factory reset.
3)Power down. Battery pull is an option. Go to download mode.
4)Odin stock tar; be patient waiting for COM and tar to verify before start (one minute or 2).
5)Boot and setup.
6)Power down.
7)Odin TWRP recovery tar
8)In recovery, flash the supersu zip.
9)On first boot, follow any prompts to update su binary that SuperSu prompts you for but do not select TRWP as the option but "Normal" when asked.
10)You should be rooted.
Of course you could also follow the instructions in the stock tar thread I pointed you too. The above is the alternative method.
samep said:
1)Download the stock tar NK2, TWRP tar for Odin and supersu zip.
2)Factory reset.
3)Power down. Battery pull is an option. Go to download mode.
4)Odin stock tar; be patient waiting for COM and tar to verify before start (one minute or 2).
5)Boot and setup.
6)Power down.
7)Odin TWRP recovery tar
8)In recovery, flash the supersu zip.
9)On first boot, follow any prompts to update su binary that SuperSu prompts you for but do not select TRWP as the option but "Normal" when asked.
10)You should be rooted.
Of course you could also follow the instructions in the stock tar thread I pointed you too. The above is the alternative method.
Click to expand...
Click to collapse
I'll give that a try.
Is this the correct stock tar nk2 - https://www.androidfilehost.com/?fid=95853297432265112
KingKobra813 said:
I'll give that a try.
Is this the correct stock tar nk2 - https://www.androidfilehost.com/?fid=95853297432265112
Click to expand...
Click to collapse
Correct.
Refer to post 8 for the links to alternate rooting method files if you don't already have them.
Best wishes for success. No luck to it.
Related
so i downgraded from 4.1.2 to 4.1.1, i sim unlocked my phome and i installed the root thing, both with odin.
now i want to upgrade to 4.1.2, so i have this link to a 4.1.2 zip file, not the same as the other odin files which were like md5 or something that i used with PDA with odin, here is this link.
http://forum.xda-developers.com/showthread.php?t=2387423
specific download link
http://www.androidfilehost.com/?fid=23060877489997375
it is on the first post of that forum, it says
update412.zip
now my question is how to i use the zip file to update, it says something about mobile odin but there are no real instructions to update from 4.1.1 to 4.1.2
also will i loose my downloaded files and my root?
also how to update to 4.3 after i update to 4.1.2
thanks for all your help!!!!
cnile said:
so i downgraded from 4.1.2 to 4.1.1, i sim unlocked my phome and i installed the root thing, both with odin.
now i want to upgrade to 4.1.2, so i have this link to a 4.1.2 zip file, not the same as the other odin files which were like md5 or something that i used with PDA with odin, here is this link.
http://forum.xda-developers.com/showthread.php?t=2387423
specific download link
http://www.androidfilehost.com/?fid=23060877489997375
it is on the first post of that forum, it says
update412.zip
now my question is how to i use the zip file to update, it says something about mobile odin but there are no real instructions to update from 4.1.1 to 4.1.2
also will i loose my downloaded files and my root?
also how to update to 4.3 after i update to 4.1.2
thanks for all your help!!!!
Click to expand...
Click to collapse
You don't have to update to 4.1.2 to update to 4.3.
If you go with a custom ROM, you will keep root. Although, if you flash stock ROM with Odin, you will lose it.
Mobile Odin can be used to flash (don't interrupt it), if you wish to go that route. No special instructions.
You can also flash using Odin (PC version), once again, don't interrupt it. You'll have to unzip and use the PDA file.
Finally, if you wanna flash a custom ROM, you can install TWRP, which you can get from GooManager on the Play Store (menu then install recovery). That will let you flash a custom ROM in recovery.
Now before you do any of that, please take the time to read and fully understand what you are doing, w/e option you choose to go with.
GL!
BWolf56 said:
You don't have to update to 4.1.2 to update to 4.3.
If you go with a custom ROM, you will keep root. Although, if you flash stock ROM with Odin, you will lose it.
Mobile Odin can be used to flash (don't interrupt it), if you wish to go that route. No special instructions.
You can also flash using Odin (PC version), once again, don't interrupt it. You'll have to unzip and use the PDA file.
Finally, if you wanna flash a custom ROM, you can install TWRP, which you can get from GooManager on the Play Store (menu then install recovery). That will let you flash a custom ROM in recovery.
Now before you do any of that, please take the time to read and fully understand what you are doing, w/e option you choose to go with.
GL!
Click to expand...
Click to collapse
Well I would want stock 4.3 the thing is I cannot find download for it. Do you know where to get it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
cnile said:
Well I would want stock 4.3 the thing is I cannot find download for it. Do you know where to get it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Did you look in the stickied?
http://forum.xda-developers.com/showthread.php?p=33570269#post33570269
cnile said:
so i downgraded from 4.1.2 to 4.1.1, i sim unlocked my phome and i installed the root thing, both with odin.
now i want to upgrade to 4.1.2, so i have this link to a 4.1.2 zip file, not the same as the other odin files which were like md5 or something that i used with PDA with odin, here is this link.
http://forum.xda-developers.com/showthread.php?t=2387423
specific download link
http://www.androidfilehost.com/?fid=23060877489997375
it is on the first post of that forum, it says
update412.zip
now my question is how to i use the zip file to update, it says something about mobile odin but there are no real instructions to update from 4.1.1 to 4.1.2
also will i loose my downloaded files and my root?
also how to update to 4.3 after i update to 4.1.2
thanks for all your help!!!!
Click to expand...
Click to collapse
You can only flash the zips via recovery. Download both zip files to your PC and copy to a good quality micro SD card. Place the card in your phone and boot your phone to recovery mode. First you flash the 4.1.2 zip, then reboot to recovery again and repeat the process with the 4.3 zip.
Yes, you will lose root and you may lose your downloaded files which is why you need to do a back-up before updating. Once you have updated to 4.3, you can re-root your phone.
Rooted/Flashed my phone a long time. Constant bugs and errors. I really don't remember what all I did but I think I almost have it completely unrooted and back to stock. However, I can't update OTA. I've reflashed using this file, http://forum.xda-developers.com/showthread.php?t=2658486. Fixed just about all my issues and I actually have a lot of space on my phone. When I try to do the OTA Update, it doesn't install the update. Once it boots into recovery mode to install the update it gives an error. Can someone help my to 100% fully get my phone back to stock and be able to install OTA updates? I'm clueless.
First, did the 4.4.2 ota fail after a certain percentage? If so you may actually be partially updated already. If so, flashing MJB firmware/bootloader will hard brick.
Install and open Terminal Emulator and enter this:
getprop ro.bootloader
If it says MJB, you are still on 4.3 and can refresh that. If it says NE4, do not flash MJB!
If you can still flash MJB, there is a thread in General (I think that's where) that has the Odin flashable firmware package. Flash that with Odin and factory reset. Then try the OTA.
Factory resetting with stock recovery installed will wipe internal sd card, so back up first!
There are also a few threads in General that can help you update if the OTA continues to fail.
I'm unrooted. At least im pretty sure of that. I cant run superu anumore and root checker says im not rooted. Can I still access the terminal without being rooted. I know I had clockeork mod recovery. I also had used cyanogen mod at one point. Now I have the stock recovery but when I boot into recovery I get an error. I will post the error and install percentage as soon as the ota update downloads.
Yes, you can still run getprop w/o root. Just install terminal emulator by jackpal from the play store.
Yeah it said I747UCUEMJB. Like I said my recovery gives me an error. When I try flashing at all with odin it fails. Trying to install the ota update now. After it fails ill give the error recovery gives me. OTA update fails at 24%
Ok, booting into Android system recovery gives me a no command error than it shows the list of options. When I go to reboot system now, it gives me a no command error as well. Download mode used to give me an error, might only show up when attempting to flash something. However, these are the details of my ODIN Mode right now.
Product Name: SGH-I747
Custom Binary Download: Yes (1 Counts)
Current Binary Custom
System Status: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER RP SWREV: 2
When you try to flash the firmware with Odin, what does it say in the message box?
Have you tried flashing TWRP via Odin?
A lot of people seem to be having issues with the OTA failing at 20-something percent. No idea why though. I know some found that their firmware was partially updated afterwards though, which is why they couldn't flash with Odin. Need to know what odin says about the failure to know for sure though.
You might need to factory reset btw.
I've already did a factory reset when I flashed this latest rom from that thread I posted.
Point me in the right direction of the firmware I need. I've got AT&T btw.
Try MJB firmware again. Im assuming that's what you tried to flash with odin earlier right? When/if it fails again, copy the text from the message box and paste it here.
So you want me to try flashing using Odin with that firmware I provided in that link? Like I said, ODIN on the pc gives me an error. I'll provide the error later when I get off work. Before I just put the firmware on my sd card, went into refovery mode and installed it from there.
From what I can see that is for flashing in recovery only. Of in only flashes .tar and .tar.md5 files.
This is the stock MJB firmware you can use in Odin:
http://www.androidfilehost.com/?fid=23329332407590581
Its from enewman17 in his how to update thread here (step 4):
http://forum.xda-developers.com/showthread.php?p=53563776
If you still want to update to 4.4.2, that thread has had a pretty good success rate from what I've seen.
Let me know if you have any ither questions about this.
I'll try ut as soon as I get home from work and posy my results. Thanks for the help so far!
Wow I think one of the reasons I couldn't use ODIN after trying to unroot, is because I never had turned on USB Debugging mode. You wanted me to just go through Step 4 for right now right? Just to get back to stock 4.3 AT&T S3 like right out the box?
Thanks so much Doc. After following step 4 on that thread I was able to Ota update!
DocHoliday77 said:
From what I can see that is for flashing in recovery only. Of in only flashes .tar and .tar.md5 files.
This is the stock MJB firmware you can use in Odin:
http://www.androidfilehost.com/?fid=23329332407590581
Its from enewman17 in his how to update thread here (step 4):
http://forum.xda-developers.com/showthread.php?p=53563776
If you still want to update to 4.4.2, that thread has had a pretty good success rate from what I've seen.
Let me know if you have any ither questions about this.
Click to expand...
Click to collapse
Been using my newly updated S3 and now the Touchwiz Home stops on startup and resets my default app settings repeatedly. Not sure what's the deal, tried suggestions on diff sites and am trying a factory restore, wipe date, and wipe cache partition. Any clue how to fix this?
PS: Seen in Android System Recovery it says KOT49H.I747UFNE4. Should that be I747UCEMJB since that's what mine is and recovery still gives me no command when I start it up?
You said you had updated with the OTA so NE4 would be correct.
As for recovery, if you want to keep stock recovery, enewman17 has it available in one of his threads (in development section I think). Redland that by itself and it ought to be good to go.
Otherwise, use Odin to flash TWRP recovery.
Factory reset should take care of the launcher/home issue you mentioned. You may not be able to though since it sounds like recovery is corrupted. Fix recovery as I said above and then try the reset.
If you factory reset with stock recovery installed, it will wipe your internal sd card. With custom recovery it will not.
You could also try clearing data for Touchwiz Home in application management.
I am having issues updating OTA too. It gets to 100% and then says my phone will reboot in 5 seconds, then it reboots and some at&t logo with a % counter comes up, that gets to 100% then it reboots into Android and it still says 4.3...what am I doing wrong? Anyone have any advice? Many thanks if so.
Thats a new one for me...how exactly are you going about updating? Are you using one of the threads here? Have you recently modified anything?
DocHoliday77 said:
Thats a new one for me...how exactly are you going about updating? Are you using one of the threads here? Have you recently modified anything?
Click to expand...
Click to collapse
I am trying to update by going to settings --> more --> about device --> software update. Not using a thread, no. I was rooted and uninstalled google books and newsstand then unrooted and did a factory reset in stock recovery because I found out that if you are rooted the OTA update won't take. I am 100% bone stock now except for the 2 bloatware apps I uninstalled. I have since reinstalled them via the play store , but I hear they need to be system apps?
They do, but they also need to be the same versions that were originally included. If you get them from the store they'll be updated and will cause the ota to fail.
The development for the AT&T I747 has been discontinued by the developer. Thank you for your support.
WARNING: YOU COULD BRICK YOUR PHONE
UCUFNJ1 4.4.2 incremental update contains firmware.... bootloaders and modem baseband.
MUST BE ON UCUFNE4 FIRMWARE TO CONTINUE!!! Guide can be found here. http://forum.xda-developers.com/gal...are-update-t2808654/post53984772#post53984772
This is the perfect time to use this update to return your S3 to stock for resale or whatever. Download and save these files for when you are ready to return your phone to stock.
*This is a rooted NE4 system.img, stock recovery.img and boot.img. The install script will format system and factory data reset. /media is safe.*
1. Flash restore zip in a custom recovery. CWM, TWRP, Philz. https://www.androidfilehost.com/?fid=95784891001611561
2. Boot your phone and go through setup.
3. Use triangle away and clear your counter. http://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114
4. *Optional* If you want a clean un-rooted phone for the update do this now! , Go into SuperSu >settings>full unroot.
5. Reboot your phone.
6. Search for the OTA in the about settings, download and let the phone update.
Or download this and place in the root of your phones internal storage. Reboot into recovery and select the update from update.zip https://www.androidfilehost.com/?fid=95784891001611091
Advanced users.
The original OTA cfg file. https://www.androidfilehost.com/?fid=95784891001611092
.cfg file goes in root/cache/fota
Rename the .cfg extension to .zip and you can rename it update.zip yourself or you can actually flash it in a custom recovery once renamed. if you choose not to use the stock recovery to update.
*You will loose root during the update* But the bootloader is not locked so you can still Odin your favorite recovery and flash SuperSU.
TWRP 2.8.1.0 Odin tar. http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.8.1.0-d2att.tar
SuperSU http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip?retrieve_file=1
Once you flash your favorite recovery via Odin, you need to be ready to hold the Volume Up, Power and Home button combo when Odin reboots your phone. If you don't catch it, once the OS boots it will replace recovery with the stock version. Once SuperSU is installed your recovery will stick.
Flashable Rooted NJ1 system.img and boot.img
MD5: 6df80e42df56ddf90512f4162e645cb3
Download: https://www.androidfilehost.com/?fid=95784891001613266
Flashable NJ1 Bootloaders and modem. *Must be on NE4 bootloaders prior to flashing.*
Download: https://www.androidfilehost.com/?fid=95832962473396872
Thanks enewman for writing this up.
Doing Vice Versa Method?
Just to be clear, what if my galaxy s3 is on UCUFNJ1 and I want to go back to UCUFNE4, I can still ODIN the custom recovery and flash SuperSU?
Galaxy S3 I747
Baseband: I747UCUFNJ1
For the advanced users, should we be able to install the update without any issues? I saw in another thread that someone had installed but now their phone will not boot past the Samsung logo to anything other than a black screen.
Also, do we know what this update contains yet? Other than new bootloaders, removal of root, etc.
mattsternc said:
For the advanced users, should we be able to install the update without any issues? I saw in another thread that someone had installed but now their phone will not boot past the Samsung logo to anything other than a black screen.
Also, do we know what this update contains yet? Other than new bootloaders, removal of root, etc.
Click to expand...
Click to collapse
You know if your not wanting to return your phone to stock I really wouldn't mess with this update. Far as the user who couldn't boot... Idk I wasn't there to watch them update. This whole mess with the S3 is exhausting. We haven't got a real Odin release so I'm woking with what I can extract from my phone after updating. The system.img in ne4 zip is 100% stock except for root. So I know the update worked because I did it. Also not sure what was updated either... The kernel yes... Firmware yes, all the system apps get patched so without decompiling ne4 and nj1 apps and comparing them afraid I have no idea what the update fixes or improves.
Thanks for all you do for us S3 owners, enewman17.
If we upgrade to the new NJ1 firmware, and then flash your latest SRX Rom, I assume we cannot then use your "restore.zip" to once again go back to NE4 stock since we would be on NJ1 bootloader? If so, is there a way to go back to NJ1 stock if we later want to sell our phone?
OKAstro said:
Thanks for all you do for us S3 owners, enewman17.
If we upgrade to the new NJ1 firmware, and then flash your latest SRX Rom, I assume we cannot then use your "restore.zip" to once again go back to NE4 stock since we would be on NJ1 bootloader? If so, is there a way to go back to NJ1 stock if we later want to sell our phone?
Click to expand...
Click to collapse
I have the nj1 system dump, I'll get it uploaded so anyone who updates can restore back to stock.
enewman17 said:
I have the nj1 system dump, I'll get it uploaded so anyone who updates can restore back to stock.
Click to expand...
Click to collapse
Thanks again my man.
Towelroot no longer works after the NJ1 update. Can the CF-AutoRoot still be used? The only version at http://autoroot.chainfire.eu/ says it's for 4.0.4.
Ark42 said:
Towelroot no longer works after the NJ1 update. Can the CF-AutoRoot still be used? The only version at http://autoroot.chainfire.eu/ says it's for 4.0.4.
Click to expand...
Click to collapse
Not sure if it still works but read the op you can Odin a custom recovery then flash super su.
enewman17 said:
Not sure if it still works but read the op you can Odin a custom recovery then flash super su.
Click to expand...
Click to collapse
Yeah, I saw that, but I never had a custom recovery before, that I know of at least, and I suspect a lot of other people finding this thread in the coming days are going to be in the same boat as me. They just want SuperSU so their favorite 1 or 2 apps that require SU can continue to work.
Has anybody tried CF-AutoRoot yet on the NJ1 4.4.2?
Ark42 said:
Yeah, I saw that, but I never had a custom recovery before, that I know of at least, and I suspect a lot of other people finding this thread in the coming days are going to be in the same boat as me. They just want SuperSU so their favorite 1 or 2 apps that require SU can continue to work.
Has anybody tried CF-AutoRoot yet on the NJ1 4.4.2?
Click to expand...
Click to collapse
Agreed! I'm the same boat as you.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Ark42 said:
Yeah, I saw that, but I never had a custom recovery before, that I know of at least, and I suspect a lot of other people finding this thread in the coming days are going to be in the same boat as me. They just want SuperSU so their favorite 1 or 2 apps that require SU can continue to work.
Has anybody tried CF-AutoRoot yet on the NJ1 4.4.2?
Click to expand...
Click to collapse
Tell you what, when I get home from work I will try cfauto root and see if it works.
enewman17 said:
Not sure if it still works but read the op you can Odin a custom recovery then flash super su.
Click to expand...
Click to collapse
I can confirm this as a root method for NJ1. You were exactly right regarding immediately booting into recovery after installing TWRP thru Odin. The files provided in your links (TWRP 2.8.1.0 Odin tar. http://techerrata.com/file/twrp2/d2a....1.0-d2att.tar and
SuperSU http://download.chainfire.eu/589/Sup...etrieve_file=1)
worked exactly as stated.
A BIG thanks to you. I can't live without AdAway, TiBackup and Xposed anymore! The few days without root left me a little grumpy.
And regarding the NJ1 update as a whole...I THINK the baseband upgrade IS an actual upgrade. Since NE4, I always thought Wifi operated was somewhat choppy/throttled. THIS looks to have been improved back to ICS "standards". Re: voice, I've had a handful of dropped calls, broken up calls, and choppy data in low signal areas over the past few months on with NE4. Initial observations (albeit a tad premature) lead me to believe that this has improved as well based on a weeks worth of data use and a few calls in a "controlled" environment (the area and physical structure of my work office complex is not cellular signal friendly to begin with) I have also noticed that boot-up time has improved a bit as well. Thanks again for your efforts with the ATT GS3!
I flashed CF-Auto ROOT via Odin without success, unable to gain root access. Followed your instructions via TWRP and flashed SuperSu 2.16, my SGS3-i747 is properly rooted and functioning perfectly on UCUFNJ1. As always, thank you very kindly for all your valuable time, effort, hard work and guidance. Be well, sir!
mwrobe1 said:
I can confirm this as a root method for NJ1. You were exactly right regarding immediately booting into recovery after installing TWRP thru Odin. The files provided in your links (TWRP 2.8.1.0 Odin tar. http://techerrata.com/file/twrp2/d2a....1.0-d2att.tar and
SuperSU http://download.chainfire.eu/589/Sup...etrieve_file=1)
worked exactly as stated.
Click to expand...
Click to collapse
What version of Odin do we need to flash that TWRP, or do you have a link handy?
I've seen quite a lot of different Odins out there and don't want to brick my phone by using the wrong one.
Any pitfalls to watch out for if using TWRP for the first time? I'm sure there is going to be a bunch of people having to do this now that both CF-AutoRoot and TowelRoot doesn't work anymore.
For me, personally, I just use root for AdFree and to edit the font fallback order to properly support Japanese instead of Chinese glyphs on shared Han-unified Unicode codepoints.
Ark42 said:
What version of Odin do we need to flash that TWRP, or do you have a link handy?
I've seen quite a lot of different Odins out there and don't want to brick my phone by using the wrong one.
Any pitfalls to watch out for if using TWRP for the first time? I'm sure there is going to be a bunch of people having to do this now that both CF-AutoRoot and TowelRoot doesn't work anymore.
For me, personally, I just use root for AdFree and to edit the font fallback order to properly support Japanese instead of Chinese glyphs on shared Han-unified Unicode codepoints.
Click to expand...
Click to collapse
Use Odin 3.0.7
Not really any pitfalls to TWRP. It has an easy clean user interface and it works.
Once you have flash Super Su, in my how to ne4 update there is a flashable stock recovery. You just flash it with TWRP and once you reboot, stock recovery will be back on you phone.
Hi enewman17,
Thanks for your posts and work. I'm hoping you can help me get the new NJ1 update installed and rooted.
Here's where I'm at: AT&T SGS3 on rooted stock NE4, installed using your guides from back in June this year.
The OTA NJ1 update downloaded but failed to install (as did the NE4 OTA back then, I assume because I was rooted).
My phone still has the TWRP recovery from the previous update, so I was hoping I could install using the original OTA cfg file download from the "advanced" section in your OP so as to avoid factory reset, etc.
I downloaded the file, renamed to update.zip, and copied to my SD card. However, when I boot into TWRP and try to install it, I get an error after the system check, something like "assert failed ro.secure==1". I guess I'm doing something wrong, maybe I'm mistaken about how the original OTA is supposed to work?
Again, I'm trying to end up with a stock, but rooted, NJ1 firmware but hopefully without having to reset/lose data and settings on the phone. I don't really care right now about resale or making it look like I haven't messed with it.
Thanks for any help you can provide! Let me know if I can provide any additional details.
I am actually looking to do the exact same thing. Currently rooted, with a lot of the AT&T apps frozen via Titanium Backup.
Hope there is some way to accomplish this without returning to stock!
Thanks in advance!
Bob2014 said:
Hi enewman17,
Thanks for your posts and work. I'm hoping you can help me get the new NJ1 update installed and rooted.
Here's where I'm at: AT&T SGS3 on rooted stock NE4, installed using your guides from back in June this year.
The OTA NJ1 update downloaded but failed to install (as did the NE4 OTA back then, I assume because I was rooted).
My phone still has the TWRP recovery from the previous update, so I was hoping I could install using the original OTA cfg file download from the "advanced" section in your OP so as to avoid factory reset, etc.
I downloaded the file, renamed to update.zip, and copied to my SD card. However, when I boot into TWRP and try to install it, I get an error after the system check, something like "assert failed ro.secure==1". I guess I'm doing something wrong, maybe I'm mistaken about how the original OTA is supposed to work?
Again, I'm trying to end up with a stock, but rooted, NJ1 firmware but hopefully without having to reset/lose data and settings on the phone. I don't really care right now about resale or making it look like I haven't messed with it.
Thanks for any help you can provide! Let me know if I can provide any additional details.
Click to expand...
Click to collapse
Bob2014 said:
Hi enewman17,
Thanks for your posts and work. I'm hoping you can help me get the new NJ1 update installed and rooted.
Here's where I'm at: AT&T SGS3 on rooted stock NE4, installed using your guides from back in June this year.
The OTA NJ1 update downloaded but failed to install (as did the NE4 OTA back then, I assume because I was rooted).
My phone still has the TWRP recovery from the previous update, so I was hoping I could install using the original OTA cfg file download from the "advanced" section in your OP so as to avoid factory reset, etc.
I downloaded the file, renamed to update.zip, and copied to my SD card. However, when I boot into TWRP and try to install it, I get an error after the system check, something like "assert failed ro.secure==1". I guess I'm doing something wrong, maybe I'm mistaken about how the original OTA is supposed to work?
Again, I'm trying to end up with a stock, but rooted, NJ1 firmware but hopefully without having to reset/lose data and settings on the phone. I don't really care right now about resale or making it look like I haven't messed with it.
Thanks for any help you can provide! Let me know if I can provide any additional details.
Click to expand...
Click to collapse
I'll get my stock rooted system dump up later so you can flash in TWRP or CWM.
Do you guys want it packaged with the stock recovery?
mattsternc said:
I am actually looking to do the exact same thing. Currently rooted, with a lot of the AT&T apps frozen via Titanium Backup.
Hope there is some way to accomplish this without returning to stock!
Thanks in advance!
Click to expand...
Click to collapse
These files will restore stock recovery and cache for those who have rooted with CF Auto Root, so that you can return those partitions to factory status for an OTA. Remember that any changes to /system in Lollipop nullifies OTA capability so you also need to undo any changes you've made, restore any bloat, unroot from within SuperSU, etc. For those who used CF and have done minimal mods or changes, this is merely a faster (both in terms of download time and flash time) way of restoring recovery and cache (which are modified when you flash CF Auto Root) than flashing the full stock tar. If you've deleted a whole bunch of bloat, installed Xposed, flashed mods in recovery, etc. then you probably just wanna use the full tar
Flash via Odin PDA/AP slot.
OC9:
OCF:
https://www.androidfilehost.com/?fid=24052804347756900
OE2:
https://www.androidfilehost.com/?fid=24052804347756938
Sweeet!!! DO you know of anywhere else to get the full stock TARs (particularly OE2)?? Or do you know anywhere to get full data wipe TARs? Thanks!
JoeFCaputo113 said:
Sweeet!!! DO you know of anywhere else to get the full stock TARs (particularly OE2)?? Or do you know anywhere to get full data wipe TARs? Thanks!
Click to expand...
Click to collapse
Well where do you think I pulled the recovery and cache from haha? I'll have an AFH mirror up later today
iBowToAndroid said:
Well where do you think I pulled the recovery and cache from haha? I'll have an AFH mirror up later today
Click to expand...
Click to collapse
AHHHH!! You are a God! Thanks so much :good:
I flashed the stock rom downloaded directly from Sammobile and it still didn't allow OTA. It said that my phone had been modified... Not sure if I missed something because it stuck in a bootloop with the stock ROM after TWRP unless I flash Unikernel. Maybe the newest 5.1.1 doesn't allow OTA. I tried it with the OFE ROM completely stock.
Johnrob011045 said:
I flashed the stock rom downloaded directly from Sammobile and it still didn't allow OTA. It said that my phone had been modified... Not sure if I missed something because it stuck in a bootloop with the stock ROM after TWRP unless I flash Unikernel. Maybe the newest 5.1.1 doesn't allow OTA. I tried it with the OFE ROM completely stock.
Click to expand...
Click to collapse
If you install a non-stock recovery (like TWRP) you cannot take OTA updates. Any version, doesn't matter.
Follow the guide posted at http://forum.xda-developers.com/sprint-galaxy-s6/general/how-to-to-100-stock-root-t3075448 and you will have the latest version with custom recovery and root.
Or, if OTA updates are crucial to you, Odin the TAR file and stop there.
Mine wasn't working after I flashed the stock rom from Sammobile before I flashed twrp, since it wouldn't update I figured I needed twrp to stay up to date from now on but I'm not trying to post bad information to anyone, it wasn't working for me but maybe these caches can bring back OTA. I wish there was a way to get Samsung pay working.
i've samsung note 4 sm-n910p
was working fine ,tried to install firmware but got bricked
i've tried downloading many firmwares all fail
need someone to send the right firmware for my device
attached the error i get
thanks
And here we go again...... What version software was installed before trying to update? Were you rooted?
zjor2000 said:
i've samsung note 4 sm-n910p
was working fine ,tried to install firmware but got bricked
i've tried downloading many firmwares all fail
thanks
Click to expand...
Click to collapse
Try Flashing CF Auto Root through Odin and reboot your phone and report back please.
w7excursion said:
And here we go again...... What version software was installed before trying to update? Were you rooted?
Click to expand...
Click to collapse
Lol, ikr....
done so ,,but nothing keeps restarting ,,,,loop
it needs a new firmware .. OS
zjor2000 said:
done so ,,but nothing keeps restarting ,,,,loop
it needs a new firmware .. OS
Click to expand...
Click to collapse
Were you on the OG5 OTA and tried to root your phone?
rooted thru odin
now i can't get to OS ,just show samsung sign and loops
Flash whatever firmware u was on in odin
zjor2000 said:
rooted thru odin
now i can't get to OS ,just show samsung sign and loops
Click to expand...
Click to collapse
In Odin, Flash the TWRP recovery
Download notarized,cm12 or sacs and put it on your SD card, and reboot to recovery and install your choice of Rom downloaded.
Reboot and relax.
tried to do thru sd card ,but i get :
dm-verity verification failed
can i just go back to 5.1 lollipop with an official stock rom via odin ?
zjor2000 said:
can i just go back to 5.1 lollipop with an official stock rom via odin ?
Click to expand...
Click to collapse
There is no official rom
any firmware can get me back to lollipop with odin !!!
zjor2000 said:
any firmware can get me back to lollipop with odin !!!
Click to expand...
Click to collapse
Here's what I understand as far as recovering with Odin by build:
All these builds NIE, NK2 (KitKat) and first Lollipop (OB7) were downgradeable; you were free to flash in Odin within these builds. Or KIES but not downgrade.
OE1 didn't have a tar, it also locked out the older ones but was compatible with OF5 to flash Odin or KIES to upgrade. Can only go back to OE1 with nandroid backup from OF5. OE1 introduced reactivation lock to prevent flashing over user locked phone as well as preventing the downgrade to escape the feature. Seems dine could recover from a bit loop by flashing CF Auto Root in Odin.
OF5 was released with a supporting tar eventually but it's the same story as OE1. But I'm not sure if CF Auto Root worked to recover boot when looped.
OG5 locks it further. If you don't have a nandroid, recovering from boot loop options may include flashing CWM recovery or a compatible flash that takes you away from OG5 almost entirely. Sacs, Notarized, and CM12 are reportedly working. Reportedly, can't go back to OF5 with Odin and not sure about nandroid, maybe not.
Depending on certain exceptions unclear, Odin and KIES have been reported to work together, flashing stock OB7 ROM, parts of stock tar with Odin with a flash result that won't boot but connecting KIES in recovery and using the emergency recovery method. If KIES doesn't see your phone on recovery, you may try this fix on your Windows PC:
http://forum.xda-developers.com/showpost.php?p=34864154&postcount=14
I'll add this too: flashing L Speed Mod may fix adb with ADB Insecure in booted mode; ADB Insecure wouldn't be needed in recovery anyway so it works without it. I can report this does work for me with the above MTP fix on OB7.
Sent from my SM-N910P using Tapatalk
samep said:
Here's what I understand as far as recovering with Odin by build:
All these builds NIE, NK2 (KitKat) and first Lollipop (OB7) were downgradeable; you were free to flash in Odin within these builds. Or KIES but not downgrade.
OE1 didn't have a tar, it also locked out the older ones but was compatible with OF5 to flash Odin or KIES to upgrade. Can only go back to OE1 with nandroid backup from OF5. OE1 introduced reactivation lock to prevent flashing over user locked phone as well as preventing the downgrade to escape the feature. Seems dine could recover from a bit loop by flashing CF Auto Root in Odin.
OF5 was released with a supporting tar eventually but it's the same story as OE1. But I'm not sure if CF Auto Root worked to recover boot when looped.
OF5 locks it further. If you don't have a nandroid, recovering from boot loop options may include flashing CWM recovery or a compatible flash that takes you away from OG5 almost entirely. Sacs, Notarized, and CM12 are reportedly working. Reportedly, can't go back to OF5 with Odin and not sure about nandroid, maybe not.
Depending on certain exceptions unclear, Odin and KIES have been reported to work together, flashing parts of stock tar with Odin and connecting KIES using the emergency recovery method. If KIES doesn't see your phone on recovery, you may try this fix on your Windows PC:
http://forum.xda-developers.com/showpost.php?p=34864154&postcount=14
I'll add this too: flashing L Speed Mod may fix adb with ADB Insecure in booted mode; ADB Insecure wouldn't be needed in recovery anyway so it works without it. I can report this does work for me with the above MTP fix on OB7.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Was i incorrect in my method of getting him back on his feet? I should suggest CWM instead of TWRP? Now im confused.
The last thing i want to do is tell someone the wrong procedure, only causing more frustration. I thought i read 'Twrp, Install and Viola!' from many users in the other thread.
xxSTARBUCKSxx said:
Was i incorrect in my method of getting him back on his feet? I should suggest CWM instead of TWRP? Now im confused.
The last thing i want to do is tell someone the wrong procedure, only causing more frustration. I thought i read 'Twrp, Install and Viola!' from many users in the other thread.
Click to expand...
Click to collapse
I think your suggestion is consistent with what we're learning as you gave it. It seems to be evolving with trial and error. The CWM suggestion came from a single experience shared.
http://forum.xda-developers.com/showthread.php?p=62196189
The OP was asking for another solution and it wasn't clear where he started from to correctly recovery so tried to answer including all the options for each build. I added some things that may help depending on his situation.
Sent from my SM-N910P using Tapatalk
i managed to find the right fW ,,,if anyone has same problem u can do it your self
https://1fichier.com/dir/IOjXgJUa
and download this file : N910PVPU3BOF5_SPT3BOF5_SPR_Sprint_USA_5.0.1.zip