I took the OTA MJ7 4.3 update and then tried doing the M1I root technique and soft bricked my phone. I know some have tried that and others have just had issues where their phone won't boot after taking the OTA. I will share the steps I did that fixed my phone!
1. Place the update.zip from this thread (http://forum.xda-developers.com/showthread.php?t=2502591) on an SD card. You may have to put it in another phone or into an SD card reader.
2. Press and hold volume up + home button for a couple of seconds
3. While still holding those buttons press and hold the power key until the phone vibrates, then release the power key only
4. Your phone should boot into Android System Recovery. Go to Apply update from external sd card.
5. Select update.zip and apply it
6. It will reboot your phone, it will still not boot properly. Remove the battery and follow steps 2-3 again.
7. This time, select Wipe data/factory reset.
8. Once complete reboot your phone, it will boot this time!
I'm so excited my S4 works again!! Hope this helps you guys!
antisomnic said:
I took the OTA MJ7 4.3 update and then tried doing the M1I root technique and soft bricked my phone. I know some have tried that and others have just had issues where their phone won't boot after taking the OTA. I will share the steps I did that fixed my phone!
1. Place the update.zip from this thread (http://forum.xda-developers.com/showthread.php?t=2502591) on an SD card. You may have to put it in another phone or into an SD card reader.
2. Press and hold volume up + home button for a couple of seconds
3. While still holding those buttons press and hold the power key until the phone vibrates, then release the power key only
4. Your phone should boot into Android System Recovery. Go to Apply update from external sd card.
5. Select update.zip and apply it
6. It will reboot your phone, it will still not boot properly. Remove the battery and follow steps 2-3 again.
7. This time, select Wipe data/factory reset.
8. Once complete reboot your phone, it will boot this time!
I'm so excited my S4 works again!! Hope this helps you guys!
Click to expand...
Click to collapse
Cool! Glad you are up and running.
The MI1 root method flashed a MI1 ROM, so if you are on MJ7, you create a soft brick by trying to root.
Don't do that!!!!
Right. I figured that out the hard way. At least there is a solution
Sent from my SCH-I545 using xda app-developers app
Were you able to boot into android recovery while soft bricked? I experienced the same issue and booted into recovery (volume up, center button, and power button while power is off) and simply did a factory reset. I was able to keep root and fix whatever had gone wrong.
Nevermind, read wrong.
Can be deleted.
tried this.
instead of recovery i get : firmware upgrade encountered an issue. please select recovery mode in kies
slackwaresupport said:
tried this.
instead of recovery i get : firmware upgrade encountered an issue. please select recovery mode in kies
Click to expand...
Click to collapse
I had this happen too. I had to use ODIN to restore to factory MI1 then did OTA to MJ7.
teinwhite said:
I had this happen too. I had to use ODIN to restore to factory MI1 then did OTA to MJ7.
Click to expand...
Click to collapse
just tried to flash ml1.. failed on system.img.ext4
slackwaresupport said:
just tried to flash ml1.. failed on system.img.ext4
Click to expand...
Click to collapse
Did you take the MJ7 update and then try to go back to Ml1? I thought that is the error you get if you do try to go back.
-Lawless said:
Did you take the MJ7 update and then try to go back to Ml1? I thought that is the error you get if you do try to go back.
Click to expand...
Click to collapse
I was in that boat. Took the OTA and foolishly tried Root de la Vega. Couldn't flash back to MI1 (failed as described) but the new no-wipe MJ7 Odin file saved the day. Good as new (but still unrooted).
http://forum.xda-developers.com/showthread.php?t=2507217
I got root with this post: http://forum.xda-developers.com/showpost.php?p=47187227&postcount=84
As other say, it seems to be bad.
I cleared this post and if you wish, you can check the first line and open the post to see how it goes.
TheJumpingBean said:
You will prolly get banned for this! LOL Either way, it does work. I did it on mine, and all of that is true.
Click to expand...
Click to collapse
Why would i get banned ? Did i do something wrong by sharing the knowledge? I have not taken credit for this and also added the link to the post so it can be verified ;
OK, i removed the link and whoever needs it, can use Google to find it.
Trak-X said:
Why would i get banned ? Did i do something wrong by sharing the knowledge? I have not taken credit for this and also added the link to the post so it can be verified ;
OK, i removed the link and whoever needs it, can use Google to find it.
Click to expand...
Click to collapse
No there were some xda admins or w/e that said the links 2 this root arent allowed on XDA ne more. Not sure why... I used it and it worked perfectly. oh well. Sowwy
Moderator @Naddict posted this one post prior in that thread. Read up and learn about the risk you are exposing yourself to.
Be aware that as of this moment XDA has deemed the Kingo root method and Vroot method are not allowed on XDA. There are concerns with the information which is collected during the root method by the exploit. It is not about a continuous malware which may affect your device but about important information shared about your device, serial numbers etc during the root process which could be huge securities issues. You have all been warned.
Click to expand...
Click to collapse
This post, courtesy of open1your1eyes, provides some detail from the bright guys that keep us rooted and happy.
We finally have some details on these root methods:
https://twitter.com/TeamAndIRC/status/397767301811802112
TLDR: Uses "Romaster" root method
Click to expand...
Click to collapse
I would take their caution to heart if I was in your position.
--OctOS Powered VZW GS4 Dev Edition
Nice to see the wheels turning here guys. Thumbs up
I dont know what to think of this. I did the root the first day, and haven't had any problems. I have talked to a few devs and Android engineers who have checked it out and don't think its a threat. I did manage to update mine to SuperSU from the chinese superuser, just in case...
So, I dont know enough to tell you if it is or isnt dangerous, but I can tell u that Im on like day 5 with no issues. I went ahead the first day and installed DroidWall. DroidWall doesnt have any records of su or the chinese superuser trying to access anything, and netstat doesnt show that the su or superuser apps are listening for connections.
I kinda wish we could get some closure on whats happening...
teinwhite said:
I had this happen too. I had to use ODIN to restore to factory MI1 then did OTA to MJ7.
Click to expand...
Click to collapse
Im go the problem where it says Firmware upgrade encountered an issue. how do i fix this? and can u provide a link for the stock firmwares please the mi1 and mj7.
TheJumpingBean said:
I dont know what to think of this. I did the root the first day, and haven't had any problems. I have talked to a few devs and Android engineers who have checked it out and don't think its a threat. I did manage to update mine to SuperSU from the chinese superuser, just in case...
So, I dont know enough to tell you if it is or isnt dangerous, but I can tell u that Im on like day 5 with no issues. I went ahead the first day and installed DroidWall. DroidWall doesnt have any records of su or the chinese superuser trying to access anything, and netstat doesnt show that the su or superuser apps are listening for connections.
I kinda wish we could get some closure on whats happening...
Click to expand...
Click to collapse
How'd you get supersu to work and remove Chinese superuser?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Hey all, I got a Verizon Galaxy S4 16 gigs. I did the 4.3 OTA, then tried to go back to 4.2.2. I guess that soft bricked it. So do I have to use the MJ7 firmware to make my phone usable again? And if that works, is there any way to go back to 4.2.2? What do I do if it doesn't work?
Update: This worked beautifully, I'm now back to 4.3.
Related
I changed from an iPhone 4 in May to the Samsung Note. On my iPhone I would immediately jailbreak and install MyWi. In my research to do the same on the note I ran across a rooting tutorial for my device and followed the instructions http://www.androidauthority.com/galaxy-note-att-i717-root-without-increasing-flash-counter-61325/ (I am not positive, but I feel confident this is the one I followed). I installed Superuser and Titanium Backup, did a backup of ATT connection manager, then removed it. Tethering worked like a charm. This has worked and I had no issues until Friday June 14th.
On Friday, everytime I opened an app on my phone I would get a Force Close. I restarted the phone and watched as it repeatedly happened after every cycle. Believing that installing Droid VNC Server was the issue, the last app I had installed, I removed it successfully and included others I didn’t use. Upon reboot, I noticed the notification of App Updates and a missed call. Checked the application list and noticed that all of the apps I had just removed were still there. I have a ton of pics and videos and thought that I should back them up immediately before I deleted them, prepared for the worst. I was able to do that. I deleted them all, nothing in the gallery. When the phone crapped out again and rebooted, all apps and all pictures back.
I formatted the USB Storage, seemed to delete nothing and also showed the same amount of used space as before.
Time for a restore. I know now that the recovery partition is gone and so a Wipe/reset is fruitless. No problem. I know how to flash the rom. I used this method with Odin. http://forum.xda-developers.com/showthread.php?t=1506330
Everything seemed to work successfully, but upon reboot I get the same app updates notification and the same missed call notification. The same frozen state my phone was in when the issue started on Friday. WTH!
I have everything backed up. How do I get back to stock? I could care less about the counter. I just want my phone to be usable again.
ryantaylor16 said:
I changed from an iPhone 4 in May to the Samsung Note. On my iPhone I would immediately jailbreak and install MyWi. In my research to do the same on the note I ran across a rooting tutorial for my device and followed the instructions http://www.androidauthority.com/galaxy-note-att-i717-root-without-increasing-flash-counter-61325/ (I am not positive, but I feel confident this is the one I followed). I installed Superuser and Titanium Backup, did a backup of ATT connection manager, then removed it. Tethering worked like a charm. This has worked and I had no issues until Friday June 14th.
On Friday, everytime I opened an app on my phone I would get a Force Close. I restarted the phone and watched as it repeatedly happened after every cycle. Believing that installing Droid VNC Server was the issue, the last app I had installed, I removed it successfully and included others I didn’t use. Upon reboot, I noticed the notification of App Updates and a missed call. Checked the application list and noticed that all of the apps I had just removed were still there. I have a ton of pics and videos and thought that I should back them up immediately before I deleted them, prepared for the worst. I was able to do that. I deleted them all, nothing in the gallery. When the phone crapped out again and rebooted, all apps and all pictures back.
I formatted the USB Storage, seemed to delete nothing and also showed the same amount of used space as before.
Time for a restore. I know now that the recovery partition is gone and so a Wipe/reset is fruitless. No problem. I know how to flash the rom. I used this method with Odin. http://forum.xda-developers.com/showthread.php?t=1506330
Everything seemed to work successfully, but upon reboot I get the same app updates notification and the same missed call notification. The same frozen state my phone was in when the issue started on Friday. WTH!
I have everything backed up. How do I get back to stock? I could care less about the counter. I just want my phone to be usable again.
Click to expand...
Click to collapse
did you try wiping Catche and Dav?
Wipe Catch > Wife Davlik > Fix Permision, then reboot ..
see what happens ..
Not a noob, but here is where i am lost
I booted in to recovery, chose to Wipe/Erase . I see no option to Wipe Davlik except for in SuperUser and there it is a paid option, not sure where to find Fix Permission and then reboot?
I am assuming these are all options for CWM. I attempted to put CWM on an SD card last night and install from ZIP, but Recovery does not seem to see the SD card.
Are these options that are available for CWM, if so I will push through until I get it to work, but I have had no luck to this point.
UltimateEnd said:
did you try wiping Catche and Dav?
Wipe Catch > Wife Davlik > Fix Permision, then reboot ..
see what happens ..
Click to expand...
Click to collapse
ryantaylor16 said:
I booted in to recovery, chose to Wipe/Erase . I see no option to Wipe Davlik except for in SuperUser and there it is a paid option, not sure where to find Fix Permission and then reboot?
I am assuming these are all options for CWM. I attempted to put CWM on an SD card last night and install from ZIP, but Recovery does not seem to see the SD card.
Are these options that are available for CWM, if so I will push through until I get it to work, but I have had no luck to this point.
Click to expand...
Click to collapse
no need to go back to stock .
try reflashing whichever ROM you desire...
its always wise to follow every little STEP given by the DEV .
to wipe dav you go to advance and it should be there..
Sorry, still need assist
UltimateEnd said:
no need to go back to stock .
try reflashing whichever ROM you desire...
its always wise to follow every little STEP given by the DEV .
to wipe dav you go to advance and it should be there..
Click to expand...
Click to collapse
I have attempted to Flash ROMs I don't desire just to move forward. They all flash and pass in Odin but on reboot I still have my default screen. Unfortunately, I want to go back to stock. I have done plenty of research and need something more to push on to the next thing. I am looking at phone and there is not an Advanced option in recovery. I have read there are options in CWM but I am looking at what I believe is the stock recovery options.
ryantaylor16 said:
I have attempted to Flash ROMs I don't desire just to move forward. They all flash and pass in Odin but on reboot I still have my default screen. Unfortunately, I want to go back to stock. I have done plenty of research and need something more to push on to the next thing. I am looking at phone and there is not an Advanced option in recovery. I have read there are options in CWM but I am looking at what I believe is the stock recovery options.
Click to expand...
Click to collapse
after you are rooted ,
you should have nothing to do with Odin.
and also, if you were stuck on your phone trying to boot up, chances are you keep downloading a bad ROM..
happen to me before..a ROM that was suposed to be 192MB,
would finish on 158MB
someone else may be able to help you get back to stock ROM..i havent had the chance to ever wanna go back to stock so i wouldnt know for sure.
sorry and good luck .
Still Worried. Still Stuck
ryantaylor16 said:
Time for a restore. I know now that the recovery partition is gone and so a Wipe/reset is fruitless. No problem. I know how to flash the rom. I used this method with Odin to undo root. http://forum.xda-developers.com/showthread.php?t=1506330
Everything seemed to work successfully, but upon reboot I get the same app updates notification and the same missed call notification. The same frozen state my phone was in when the issue started on Friday. WTH!
I have everything backed up. How do I get back to stock? I could care less about the counter. I just want my phone to be usable again.
Click to expand...
Click to collapse
OK, I am still stuck and so I will wait for someone else to reply. Thanks for your help though
ryantaylor16 said:
OK, I am still stuck and so I will wait for someone else to reply. Thanks for your help though
Click to expand...
Click to collapse
U need to do what he said he is every well known on xda...install cwm to ur internel memory not sd card and ur phone has to see it!
Btw if u want to get back to bare bone stock look for att b4 tar file if u cant find it let me know ill link it
cm9
Use this?
JB calhoun said:
U need to do what he said he is every well known on xda...install cwm to ur internel memory not sd card and ur phone has to see it!
Btw if u want to get back to bare bone stock look for att b4 tar file if u cant find it let me know ill link it
cm9
Click to expand...
Click to collapse
Would you say this is a good tutorial to follow?
http://rootgalaxynote.com/galaxy-no...-on-att-galaxy-note-sgh-i717-belltelusrogers/
So, maybe I am a newb. I have followed the instructions to install CWM on my device and it even says it was successful. I am doing it from ODIN. See the file I downloaded here. Says it was successful but holding the volume up and then power button. NO CWM.
I am truly frustrated but I want my phone back. Can someone link me to the stupid people posts so I can get my phone working again?
bump
CWM Problems
Hi,
Have you looked at these posts? Sounds like you may be using the
wrong key combo to start CWM?
http://forum.xda-developers.com/showthread.php?t=1586223
http://forum.xda-developers.com/showthread.php?t=1483113
Are you confident that your uSD card hasn't been corrupted?
Peter
ryantaylor16 said:
So, maybe I am a newb. I have followed the instructions to install CWM on my device and it even says it was successful. I am doing it from ODIN. See the file I downloaded here. Says it was successful but holding the volume up and then power button. NO CWM.
I am truly frustrated but I want my phone back. Can someone link me to the stupid people posts so I can get my phone working again?
Click to expand...
Click to collapse
ryantaylor16 said:
bump
Click to expand...
Click to collapse
You now have a custom recovery(according to Odin). The problem is, you're doing the wrong key combo as stated above. You can also go to the market and grab FJ's power tool. You can boot into recovery directly from the app. Good luck.
Certainly I am not this dumb..... am I
froidroid said:
You now have a custom recovery(according to Odin). The problem is, you're doing the wrong key combo as stated above. You can also go to the market and grab FJ's power tool. You can boot into recovery directly from the app. Good luck.
Click to expand...
Click to collapse
Still having issues. Here is the deal.
I have the phone in Download mode
https://www.dropbox.com/s/dnk6ekjqp9vddev/2012-06-19 19.40.01.jpg
I load the CWM Recovery in the PDA box. Start the flash, get a pass. All looks good to me.
https://www.dropbox.com/s/5q4hayf35mm26wr/odin-success.PNG
I immediately attempt to access CWM Recovery by holding the power, vol+ and vol- and still get the default recovery
https://www.dropbox.com/s/d176blydonlvrlu/2012-06-19 20.13.42.jpg
I am so confused as to what I am doing wrong.
Unfortunately those pics aren't loading for me. Try again with the pic of recovery and the file you're flashing. Thanks. If you still have stock recovery then maybe that's what you're flashing in error.
Try volume up + down and power button. When phone vibrates, release power button but keep holding volume buttons until you are in cwm.
I would use Odin to flash cwm touch recovery from pda, then load a rom via cwm. Using that method you don't even need to root because it's all done at bootloader level and root is built in to the custom rom you flash
SGH-i717 mesosphere-remix
The user lordazoroth originally posted this method here in the T-Mobile SGSIII forum. However, I have confirmed that it works with the Note 3 (at least with the Verizon variant) with one small difference. Feel free to give us both a "THANKS" if this helped you out.
You can disable the OTA Update notification by following the steps below. Just be aware that there is a small change in STEP #3.
Solution:
Step 1. Delete the update located in /cache/fota/ (may be /data/fota) and then click the update notification prompt to install it, it will instantly fail and the notification will disappear. (My phone rebooted and tried to install the update - this is the point where my Note 3 gave the update failed notification. I just rebooted the phone and went to STEP #2.)
Step 2. Disable otacerts.zip located in /etc/security by renaming it to otacerts.zip.bak
Step 3. Disable FotaClient.apk and FWUpgrade.apk by renaming with .bak extensions located in /system/app/
Step 4. Reboot
(NOTE: The difference in STEP #3 for the Galaxy Note 3 is that the [FotaClient.apk] is named [LocalFotaClient.apk] instead of just [FotaClient.apk]. All of the other steps are the same.
Continue running JB 4.3 and enjoy your Note 3 without that nagging update notification!
But the kitkat update is awesome... so you might want to reconsider doing this
Sent from my Note 3 using Tapatalk Pro
Wouldn't just freezing the "SDM" app do the trick? And possibly "FWUpgrade", although i heard that just SDM works
lmike6453 said:
Wouldn't just freezing the "SDM" app do the trick? And possibly "FWUpgrade", although i heard that just SDM works
Click to expand...
Click to collapse
You're right. Freezing just sdm would do the trick lol
Sent from my SM-N900V using Tapatalk
Grompy said:
You're right. Freezing just sdm would do the trick lol
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Say I'm not using TiBu. Can I use root explore to change something with sdm or should I just do what was originally posted?
Sent from my SM-N900V using Tapatalk
TMFGO45 said:
Say I'm not using TiBu. Can I use root explore to change something with sdm or should I just do what was originally posted?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
I personally use ROM Toolbox to do it
I got the annoying OTA update today... I DON'T WANT TO UPDATE!!! Why can't they give us an option instead of forcing it down our throats?
Is there any way to disable the update WITHOUT ROOTING? I read everywhere you need ROOT ACCESS to delete the SDM.apk FILE and such. I can't delete it without root.
How can I get rid of the annoying update WITHOUT ROOTING or what is the easiest way to gain root without wiping out everything and starting over?
As of this morning...Verizon seems to be trying to "ram the update" onto your note 3
I was rooted and safestrapped on MJE and when I unplugged my phone from the charger this morning...I had a notice that the update failed to install.
I had previously downloaded, but removed the download.
Sent from my Note 3 via Tapatalk
boamuro said:
I got the annoying OTA update today... I DON'T WANT TO UPDATE!!! Why can't they give us an option instead of forcing it down our throats?
Is there any way to disable the update WITHOUT ROOTING? I read everywhere you need ROOT ACCESS to delete the SDM.apk FILE and such. I can't delete it without root.
How can I get rid of the annoying update WITHOUT ROOTING or what is the easiest way to gain root without wiping out everything and starting over?
Click to expand...
Click to collapse
rooting (with jb roms, for us vzw n3 owners) does not wipe anything at all. Kingo is easy. There's how-to threads and vids.
Edit: This is what I recommend. ..
http://forum.xda-developers.com/showthread.php?t=2543386
Edit 2: no way to disable the ota update notification w/o root.
LeftyGR said:
rooting (with jb roms, for us vzw n3 owners) does not wipe anything at all. Kingo is easy. There's how-to threads and vids.
Edit: This is what I recommend. ..
http://forum.xda-developers.com/showthread.php?t=2543386
Edit 2: no way to disable the ota update notification w/o root.
Click to expand...
Click to collapse
OMG!! I was able too root easily, but the stupid OTA update popped up and I accidentally hit the UPDATE button. Now it rebooted on its own and went into this RECOVERY MODE and it's trying to update... I removed the battery out right away... HOW CAN I CANCEL IT?! OMG! Somone help me please. It was going so well and I can't believe the stupid popup got me...
---------- Post added at 06:23 PM ---------- Previous post was at 06:19 PM ----------
Am I doomed??? OMG I hate you Verizon
boamuro said:
OMG!! I was able too root easily, but the stupid OTA update popped up and I accidentally hit the UPDATE button. Now it rebooted on its own and went into this RECOVERY MODE and it's trying to update... I removed the battery out right away... HOW CAN I CANCEL IT?! OMG! Somone help me please. It was going so well and I can't believe the stupid popup got me...
---------- Post added at 06:23 PM ---------- Previous post was at 06:19 PM ----------
Am I doomed??? OMG I hate you Verizon
Click to expand...
Click to collapse
No way of knowing how far it got. If it was able to get the bootloader nailed in...yes. Screwed. Welcome to kk. If not, whatever you do will wipe at this point.
Safest bet to try and see if you can retain jb is with odin...if it lets you. If it does, great. If it doesn't, you still need odin because you just interrupted a firmware update and probably just soft bricked your phone. So you'll need odin to put kk on your phone.
--
If niether of these things look good, they aren't. So try this first. Try booting to recovery. If you can, it's possible you just saved yourself from learning to use odin. Do a factory reset and reboot. See if it boots to jb. If it does, root asap. If not (it just hangs forever or loops), you're bricked. Try to odin jb. If it keeps failing, you're stuck with kk and you need to odin kk.
If you can't get to recovery and just hangs or loops, odin jb or kk. Whichever it lets you.
If it doesn't let you boot to recovery because it continues to upgrade, at this point let it. This is the ONLY possible scenario that you will keep anything.
Mind you, everything I just covered will never touch any files on external sd memory.
This is a lot to process. So take your time. Good luck!
Odin tutorials are in the general section.
<Note3>
LeftyGR said:
No way of knowing how far it got. If it was able to get the bootloader nailed in...yes. Screwed. Welcome to kk. If not, whatever you do will wipe at this point.
Safest bet to try and see if you can retain jb is with odin...if it lets you. If it does, great. If it doesn't, you still need odin because you just interrupted a firmware update and probably just soft bricked your phone. So you'll need odin to put kk on your phone.
--
If niether of these things look good, they aren't. So try this first. Try booting to recovery. If you can, it's possible you just saved yourself from learning to use odin. Do a factory reset and reboot. See if it boots to jb. If it does, root asap. If not (it just hangs forever or loops), you're bricked. Try to odin jb. If it keeps failing, you're stuck with kk and you need to odin kk.
If you can't get to recovery and just hangs or loops, odin jb or kk. Whichever it lets you.
If it doesn't let you boot to recovery because it continues to upgrade, at this point let it. This is the ONLY possible scenario that you will keep anything.
Mind you, everything I just covered will never touch any files on external sd memory.
This is a lot to process. So take your time. Good luck!
Odin tutorials are in the general section.
<Note3>
Click to expand...
Click to collapse
GRRR it installed Kitkat successfully. I'm SO MAD.. I should have set the annoying OTA notification for a different time so that it wouldn't constantly pop up every second... I would have been home free rooted on Jellybean if it weren't for the STUPID UPDATE.
So can I still DOWNGRADE to Jellybean and be rooted? or did Verizon LOCK or restrict stuff with the update? Can I go back to Jellybean keeping all my files?
boamuro said:
GRRR it installed Kitkat successfully. I'm SO MAD.. I should have set the annoying OTA notification for a different time so that it wouldn't constantly pop up every second... I would have been home free rooted on Jellybean if it weren't for the STUPID UPDATE.
So can I still DOWNGRADE to Jellybean and be rooted? or did Verizon LOCK or restrict stuff with the update? Can I go back to Jellybean keeping all my files?
Click to expand...
Click to collapse
I heard once you take the verizon ota update for now your locked down.
Sent from my SM-N900V using xda premium
Hulk0069 said:
I heard once you take the verizon ota update for now your locked down.
Sent from my SM-N900V using xda premium
Click to expand...
Click to collapse
I read that too... I can't believe one simple tap mistake ruined my whole first time rooting adventure... Using KINGO was so easy and right when I WAS ABOUT TO DELETE THE STUPID SDM file in the system folder, the update popup came up and accidentally hit the UPDATE And it just rebooted instantly!! I hate how they don't even allow you to cancel or anything... like totally forcing it in your face!!
I still have SuperSU but no longer functions it says "There isn o SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!"
So there's no way to have root access now?? I can't flash back to Jellybean??? Verizon/Samsung really screwed us here. There must be a way to have root access in Jellybean... I don't care for custom roms... I just want root access!!
boamuro said:
I read that too... I can't believe one simple tap mistake ruined my whole first time rooting adventure... Using KINGO was so easy and right when I WAS ABOUT TO DELETE THE STUPID SDM file in the system folder, the update popup came up and accidentally hit the UPDATE And it just rebooted instantly!! I hate how they don't even allow you to cancel or anything... like totally forcing it in your face!!
I still have SuperSU but no longer functions it says "There isn o SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!"
So there's no way to have root access now?? I can't flash back to Jellybean??? Verizon/Samsung really screwed us here. There must be a way to have root access in Jellybean... I don't care for custom roms... I just want root access!!
Click to expand...
Click to collapse
It's verizon not Sammy who did this
Sent from my SM-N900V using xda premium
Hulk0069 said:
It's verizon not Sammy who did this
Sent from my SM-N900V using xda premium
Click to expand...
Click to collapse
AH EVIL VERIZON... freaking Verizon...
There seriously is no way to flash back to Jellybean and be rooted??? or be rooted in Kitkat?? This is SO RIDICULOUS..
I'm at least glad FoxFi fixed a way to still work with KitKat... if they didn't, I'd be really pissed to have no hotspot and stuck with KitKat... screw you VERIZON.
boamuro said:
AH EVIL VERIZON... freaking Verizon...
There seriously is no way to flash back to Jellybean and be rooted??? or be rooted in Kitkat?? This is SO RIDICULOUS..
I'm at least glad FoxFi fixed a way to still work with KitKat... if they didn't, I'd be really pissed to have no hotspot and stuck with KitKat... screw you VERIZON.
Click to expand...
Click to collapse
As it has been warned now many, many, many times.... There is NO GOING BACK if you take the NC4 update. Also, as of now, there also NO root method for it. You're stuck on it.
Sent From The Darkside of My N3
mwshows said:
As it has been warned now many, many, many times.... There is NO GOING BACK if you take the NC4 update. Also, as of now, there also NO root method for it. You're stuck on it.
Sent From The Darkside of My N3
Click to expand...
Click to collapse
So it would be pointless for me to try to use Odin to flash back to stock Jellybean and then KINGO? It won't even flash back?
I did successfully root before OTA installed Kitkat on mine... does that make any difference?
boamuro said:
So it would be pointless for me to try to use Odin to flash back to stock Jellybean and then KINGO? It won't even flash back?
I did successfully root before OTA installed Kitkat on mine... does that make any difference?
Click to expand...
Click to collapse
Unfortunately no. Once you have nc4 loaded you cannot go backwards.
<Note3>
bummer
I just received a Android update in my notification menu. I am rooted and running a custom recovery (twrp). I know I cannot accept the update but I can't swipe it away. Anyone know how I can get the update removed from my notification menu?
Have you tried long pressing on the notification and disabling notifications?
I froze system update in ti backup I didn't have a pending update but I would try that
Is that file under. Com in tb?
jreink01 said:
Is that file under. Com in tb?
Click to expand...
Click to collapse
Here you go
kennwoodkenn said:
Here you go
Click to expand...
Click to collapse
Thanks for the thumbnail. I did find it in TB and froze it but I'm still getting the update notification in my notification pull down.
Did you restart the phone after
that may work
Don't know if this will work or not, but on the Galaxy S3 the way to stop getting nagged about an OTA was to edit build.prop and replace all references to the old ROM with the new one. So you could try making a backup of build.prop, then edit all references to ZV4 and change them to ZV6. Save the file, make sure permissions are set to rw-, r--, r-- (0644), and reboot.
I would strongly suggest making a nandroid backup first.
Here's how I have been doing it:
1. Download Autorun Manager
2. In settings under advanced enable view services
3. Go to Google Services Framework and disable update...see below.
At your own risk if you decide to try it, of course.
Sent from my LGLS990 using XDA Free mobile app
This is the recommended way. http://forum.xda-developers.com/showthread.php?p=57182591
If the update has already downloaded. Disabling the OTA still wont get rid the the notification. Easy way to get rid of it is long press it and go to app info. This will take you to Google Play Services. Simply uncheck show notifications and the system update in the pull down notifications will go away.
Just a temporary fix to get it out of the way. I reccommend just downloading a ZV6 rooted rom.
engine95 said:
This is the recommended way. http://forum.xda-developers.com/showthread.php?p=57182591
Click to expand...
Click to collapse
guys I mistakenly installed this update and now my phone is stuck in twrp where can I go to delete it or am I s.o.l please help
You will need to use LG Flash tool if you are stuck in TWRP.
LG Flash Tool How to Thread
A youtube video that might help
https://www.youtube.com/watch?v=1WgXuxDbmbc
im0rtalz said:
You will need to use LG Flash tool if you are stuck in TWRP.
LG Flash Tool How to Thread
A youtube video that might help
https://www.youtube.com/watch?v=1WgXuxDbmbc
Click to expand...
Click to collapse
thanks for this I'll have to wait until I'm near a computer or back home right now I'm vacationing in Florida
Try this first before doing the LG Flash
[Fix] Stuck in Custom Recovery
Thanks to acparker posts
randyrampage609 said:
thanks for this I'll have to wait until I'm near a computer or back home right now I'm vacationing in Florida
Click to expand...
Click to collapse
Downside: No Phone.
Upside: Nice weather!
From folks here in Chicago - no sympathy! :silly:
Good luck with the phone!
FractalSphere said:
Downside: No Phone.
Upside: Nice weather!
From folks here in Chicago - no sympathy! :silly:
Good luck with the phone!
Click to expand...
Click to collapse
Alls good now used a two command terminal combo from another thread that I'm trying to find
Sent from my LGLS990 using Tapatalk
---------- Post added at 11:15 PM ---------- Previous post was at 11:12 PM ----------
randyrampage609 said:
Alls good now used a two command terminal combo from another thread that I'm trying to find
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2916085
Without having to use a computer and lg flash tool
Sent from my LGLS990 using Tapatalk
Lucky you. Good find. Glad you got it sorted. Now you can relax.
I have a question that I wanted to ask before I go any further. I bought a G3 last week, rooted it and installed twrp recovery, and have done multiple backups.. Had a hardware defect so I had to exchange my phone for another new one. I received a system update just now so I was going to accept the OTA update since its not rooted, completely stock. My questions are will I be able to root and instally twrp after this update and once I install all my apps, and if rooting and installing twrp is successful, can I restore my backup that I did on my other phone, even though its a different phone? Its from the same carrier and same model phone. Thanks for your feedback.
jreink01 said:
I have a question that I wanted to ask before I go any further. I bought a G3 last week, rooted it and installed twrp recovery, and have done multiple backups.. Had a hardware defect so I had to exchange my phone for another new one. I received a system update just now so I was going to accept the OTA update since its not rooted, completely stock. My questions are will I be able to root and instally twrp after this update and once I install all my apps, and if rooting and installing twrp is successful, can I restore my backup that I did on my other phone, even though its a different phone? Its from the same carrier and same model phone. Thanks for your feedback.
Click to expand...
Click to collapse
Don't take OTA. Root it and TWRP it. Then flash STOCK ROM ZV6 Deodexed or Odexed, then you'll be up to date and keep root with TWRP.
My work colleague is an idiot - Despite warnings from his S3 that phone memory was low he continued taking videos and pictures and he has no sd card in the phone. Now the phone boots up but the pattern unlock screen is unresponsive. I offered to try to help him as he said "The last 2 years photos of my life are on there" so clearly a factory reset will lose them all so that's not an option.
So I installed Kies, thinking I'll just grab them to my PC for him - but alas no. MTP USB driver installation fails every time and yes I've googled my socks off, tried all the regedit fixes, even tried installing Win 7 32 bit on a spare hard drive.
I've checked that the ribbon connector for the screen is attached, tried linux boot disks that don't see the phone and now I'm all out of ideas. Any help would be vastly appreciated :fingers-crossed:
Hello,
Welcome to XDA.
Most of the time the screen being locked wont let PC interact with the device. There are many different models of S3, give me your model number and I'll guide you to where you can find answers.
You may can flash a custom recovery or a temporary recovery(not sure because I don't know what is available for the model you're working with and what isn't), if you can get one of those recoveries then you may can use the factory reset in recovery(it wont wipe his photos) or adb to get the phone working.
Remember to create an XDA account so you can post and reply in the forums.
Droidriven said:
Hello,
Welcome to XDA.
Most of the time the screen being locked wont let PC interact with the device. There are many different models of S3, give me your model number and I'll guide you to where you can find answers.
Click to expand...
Click to collapse
Hi there and many thanks for the welcome. The model number is GT-19300 :fingers-crossed:
Azarameus said:
Hi there and many thanks for the welcome. The model number is GT-19300 :fingers-crossed:
Click to expand...
Click to collapse
Your issue is unusual because of how it got that way, I'm not certain exactly which subforum or thread you need but I will link you to the GT I9300 Main Forum linked below:
http://forum.xda-developers.com/galaxy-s3
You can check through the subforums there for anything you think applies, the Q&A and the 2 development subforums are most likely where you will find help, this thread will be moved to the GT I9300 Q&A forum linked below:
http://forum.xda-developers.com/galaxy-s3/help
If you get replies you can check them and respond there, you might want to find some off topic threads to post in until you have at least 10 posts so that you can post in the development forums there if you need to, there is a 10 post minimum before you can post there. Good luck.
Droidriven said:
Your issue is unusual because of how it got that way, I'm not certain exactly which subforum or thread you need but I will link you to the GT I9300 Main Forum linked below:
http://forum.xda-developers.com/galaxy-s3
You can check through the subforums there for anything you think applies, the Q&A and the 2 development subforums are most likely where you will find help, this thread will be moved to the GT I9300 Q&A forum linked below:
http://forum.xda-developers.com/galaxy-s3/help
If you get replies you can check them and respond there, you might want to find some off topic threads to post in until you have at least 10 posts so that you can post in the development forums there if you need to, there is a 10 post minimum before you can post there. Good luck.
Click to expand...
Click to collapse
Ok thanks again. I can get it into Recovery mode but all I've tried so far is clearing the cache, as I don't want to do anything that might lose his pictures.
Azarameus said:
Ok thanks again. I can get it into Recovery mode but all I've tried so far is clearing the cache, as I don't want to do anything that might lose his pictures.
Click to expand...
Click to collapse
If it is stock recovery then I believe if you can get to download mode then you can flash a custom recovery and flash the superSU zip to root the device then factory reset/wipe data, wipe cache and wipe dalvik cache, this will clear the lockscreen but won't erase his pictures, music, etc., it may let him back into his phone, he will just have to be careful because the device will be rooted and he could make things worse if he doesn't know what he's doing. If that works and he gets back in his phone but isn't comfortable with the risk of having a rooted device without understanding its usage then the device can be un rooted by going into the superSU settings and choosing the unroot and uninstall option. He'd still have custom recovery though. You might even be able to just flash the recovery to do the wipes and not have to root, I'm not sure about that though because I've never used recovery without root so I can't speak from personal experience.
I've never owned the i9300 so I'm not sure if you can do that or not safely from the state you are in so you may want to verify in this forum before you try it, but I don't see an issue with you doing it, its commonly used to root the S3 variants and doesn't wipe any important data or factory reset the device
Sent from my SCH-I535 using Tapatalk
Droidriven said:
If it is stock recovery then I believe if you can get to download mode then you can flash a custom recovery and flash the superSU zip to root the device then factory reset/wipe data, wipe cache and wipe dalvik cache, this will clear the lockscreen but won't erase his pictures, music, etc., it may let him back into his phone, he will just have to be careful because the device will be rooted and he could make things worse if he doesn't know what he's doing. If that works and he gets back in his phone but isn't comfortable with the risk of having a rooted device without understanding its usage then the device can be un rooted by going into the superSU settings and choosing the unroot and uninstall option. He'd still have custom recovery though. You might even be able to just flash the recovery to do the wipes and not have to root, I'm not sure about that though because I've never used recovery without root so I can't speak from personal experience.
I've never owned the i9300 so I'm not sure if you can do that or not safely from the state you are in so you may want to verify in this forum before you try it, but I don't see an issue with you doing it, its commonly used to root the S3 variants and doesn't wipe any important data or factory reset the device
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Whew, most of that went right over my head lol. An idiot's guide please? Bearing in mind that my PC can't currently connect to the phone I'm guessing that I need to put the custom recovery file (where to find one?) on an SD card via a PC card reader and try it from there in download mode? I think he'll be delighted just to get his pictures and videos back even if the phone never works again, so it being rooted won't be an issue.
Azarameus said:
Whew, most of that went right over my head lol. An idiot's guide please? Bearing in mind that my PC can't currently connect to the phone I'm guessing that I need to put the custom recovery file (where to find one?) on an SD card via a PC card reader and try it from there in download mode? I think he'll be delighted just to get his pictures and videos back even if the phone never works again, so it being rooted won't be an issue.
Click to expand...
Click to collapse
No, to get to download mode you need to have the phone off, then press and hold the volume down+home+power button, when you see the caution screen you press up, if you can get to this mode you may can flash a TWRP recovery through Odin from PC to phone.
But first, before we get to Odin, do you or he know what android version he had before this happened, Kit Kat? Lollipop? I need to see if there are locked bootloaders on your device builds and which ones they are and which are safe to flash TWRP, if the i9300 is like some of the other Samsung devices with certain locked bootloaders that can't be unlocked or downgraded then flashing TWRP could and probably would brick the device. I need some info so I can check for you.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
No, to get to download mode you need to have the phone off, then press and hold the volume down+home+power button, when you see the caution screen you press up, if you can get to this mode you may can flash a TWRP recovery through Odin from PC to phone.
But first, before we get to Odin, do you or he know what android version he had before this happened, Kit Kat? Lollipop? I need to see if there are locked bootloaders on your device builds and which ones they are and which are safe to flash TWRP, if the i9300 is like some of the other Samsung devices with certain locked bootloaders that can't be unlocked or downgraded then flashing TWRP could and probably would brick the device. I need some info so I can check for you.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I honestly have no idea which android build it is running on, as I can't get into the settings page or anything else and I very much doubt if my friend knows as he is pretty much clueless on such things, hence the problem. All I know is that its a few years old and when it starts up there is a three.co.uk white screen icon before it gets to the unresponsive lockscreen. I am also almost as clueless with android devices (I'm only a PC guy) - so far my only experience has been to set up kodi with addons for TV viewing which is why I came here to ask you expert guys
Methinks I won't try to get into download mode just yet in case it makes things worse
All your help is much appreciated, thank you!
Azarameus said:
I honestly have no idea which android build it is running on, as I can't get into the settings page or anything else and I very much doubt if my friend knows as he is pretty much clueless on such things, hence the problem. All I know is that its a few years old and when it starts up there is a three.co.uk white screen icon before it gets to the unresponsive lockscreen. I am also almost as clueless with android devices (I'm only a PC guy) - so far my only experience has been to set up kodi with addons for TV viewing which is why I came here to ask you expert guys
Methinks I won't try to get into download mode just yet in case it makes things worse
All your help is much appreciated, thank you!
Click to expand...
Click to collapse
The device was never updated, it never had stock upgrades? If not then I can narrow down what was on it, when was the device bought?
If you can boot to download mode and if it is recognized in Odin then you've got a chance, at the moment your PC isn't recognizing the phone but if it successfully connects to Odin then you've got a chance, otherwise I'm not sure what success you'll have.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
The device was never updated, it never had stock upgrades? If not then I can narrow down what was on it, when was the device bought?
If you can boot to download mode and if it is recognized in Odin then you've got a chance, at the moment your PC isn't recognizing the phone but if it successfully connects to Odin then you've got a chance, otherwise I'm not sure what success you'll have.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I would put a spare miniSD card in, flash TWRP recovery in odin, access the storage from there and copy the files to the SD card. Easy as pie.
The international version of the S3 (GT-i9300) already has an unlocked bootloader. So no problem there.
Important to note is that if the device is not rooted the TWRP recovery won't "stick" when the device is allowed to reboot automatically after the odin flash. So in odin you have to UNTICK(!) the reboot option and after flash reboot directly to recovery via holding Vol UP + Home + Power for about 7 sec.
Droidriven said:
The device was never updated, it never had stock upgrades? If not then I can narrow down what was on it, when was the device bought?
If you can boot to download mode and if it is recognized in Odin then you've got a chance, at the moment your PC isn't recognizing the phone but if it successfully connects to Odin then you've got a chance, otherwise I'm not sure what success you'll have.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I showed him this thread at work earlier and although he growled somewhat at being called an idiot in my OP, he had to agree he was lol. It turns out he bought his partner the same phone around the same time so I checked and it has Automatic upgrades ticked and is on build 4.3 so we can hopefully assume the problematic one is on the same version. When I mentioned the possibility of bricking to him he became unsure as to whether I should proceed with flashing. If he was to send the phone to Samsung themselves would they be able to retrieve his data safely, albeit with some cost and waiting?
Thanks again for your input
Hawaiihemd said:
I would put a spare miniSD card in, flash TWRP recovery in odin, access the storage from there and copy the files to the SD card. Easy as pie.
The international version of the S3 (GT-i9300) already has an unlocked bootloader. So no problem there.
Important to note is that if the device is not rooted the TWRP recovery won't "stick" when the device is allowed to reboot automatically after the odin flash. So in odin you have to UNTICK(!) the reboot option and after flash reboot directly to recovery via holding Vol UP + Home + Power for about 7 sec.
Click to expand...
Click to collapse
That sounds good - all he wants is his files back safely. It certainly isn't rooted. So once that is done and I'm back in recovery mode how do I get out of there, just reboot it from there?
Thanks for the help, it is much appreciated
Azarameus said:
That sounds good - all he wants is his files back safely. It certainly isn't rooted. So once that is done and I'm back in recovery mode how do I get out of there, just reboot it from there?
Thanks for the help, it is much appreciated
Click to expand...
Click to collapse
Yes, after you copied the files via the "File Manager" in TWRP you simply choose "reboot system". Rebooting to system will automatically restore the original recovery you are used to. Or you can choose to shutdown in TWRP, remove the SDcard "safely" first and then reboot.
Even more: After you copied all the photos/videos from internal storage (which should be under /storage/sdcard0/DCIM/camera) to SDcard you could simply delete a few of those.
If them taking up too much space is the problem for the lockscreen not working, deleting a few would of course free up some space again, which would then most likely make the lockscreen work again.
But let me make one thing clear: Flashing anything always brings with it the slight(!) possibility something could go wrong, because you are writing to the EMMC of the phone. BUT I can't imagine a samsung staff member doing anything different. He/she would also need to gain access somehow...
After all it's your choice but hundreds of people (including me) have used odin and twrp on different devices for years now without any problem whatsoever. :good:
--- Edit ---
Ah one more thing. I would definitely make a full backup (System/Data, EFS and bootloader) while I'm at it! You just choose "backup" in twrp, then the "MicroSD card" under "storage" and go from there. Pretty self explanatory. Never hurts to have a backup!
Hawaiihemd said:
Yes, after you copied the files via the "File Manager" in TWRP you simply choose "reboot system". Rebooting to system will automatically restore the original recovery you are used to. Or you can choose to shutdown in TWRP, remove the SDcard "safely" first and then reboot.
Even more: After you copied all the photos/videos from internal storage (which should be under /storage/sdcard0/DCIM/camera) to SDcard you could simply delete a few of those.
If them taking up too much space is the problem for the lockscreen not working, deleting a few would of course free up some space again, which would then most likely make the lockscreen work again.
But let me make one thing clear: Flashing anything always brings with it the slight(!) possibility something could go wrong, because you are writing to the EMMC of the phone. BUT I can't imagine a samsung staff member doing anything different. He/she would also need to gain access somehow...
After all it's your choice but hundreds of people (including me) have used odin and twrp on different devices for years now without any problem whatsoever. :good:
--- Edit ---
Ah one more thing. I would definitely make a full backup (System/Data, EFS and bootloader) while I'm at it! You just choose "backup" in twrp, then the "MicroSD card" under "storage" and go from there. Pretty self explanatory. Never hurts to have a backup!
Click to expand...
Click to collapse
Ok thanks again. I am going to attempt this tonight, will update on any progress
Azarameus said:
Ok thanks again. I am going to attempt this tonight, will update on any progress
Click to expand...
Click to collapse
Well, that worked! My idiot friend is happy now. Thanks a million for the help - you guys ROCK!
Azarameus said:
Well, that worked! My idiot friend is happy now. Thanks a million for the help - you guys ROCK!
Click to expand...
Click to collapse
Nice! And were you able to get the lockscreen working again?
Hawaiihemd said:
Nice! And were you able to get the lockscreen working again?
Click to expand...
Click to collapse
Yes indeed, all is working now as it should. The village idiot actually danced off to his car when I returned his phone - he has strict orders from me to move all his stuff to the SD card and make regular backups to his PC!
Thanks again - would never have done it without you guys
I got this device used and it had been updated to the newest firmware. It would not work with Kingroot, Framaroot, SRS, or Kingo. The only option was to attempt to downgrade to an older firmware with unpatched exploits. The Verizon J1 has a locked bootloader so it cannot flash full firmware packages with older bootloaders. Luckily it can be downgraded to older firmware of the same android version with older kernel. I just had to unpack the firmware and remove the bootloader and repack. I tried to make a rooted stock firmware but can't seem to repack the system.img.ext4 properly after mounting it.
Now let's get down to business
1. Download Odin 3.09
2. Download modified (by me) rootable firmware. Do not rename file it might mess up md5sum.
3. Boot phone to download mode. Hold power+vol down+ home.
4. Start Odin and connect phone with original factory sync cable.
5. Click on the AP button and select the firmware downloaded above. It will check the md5sum automatically when it finishes and passes then press the start button. Once the flash finishes it will reboot.
6. Enable usb debugging.
7. Download Kingoroot for PC (google) and let it run. The apk will not work to root. It should install drivers automatically.
8. Profit!!
I'm testing a method to reliably switch to Supersu but having trouble updating binary 100% of the time. I've tried to flash exposed but Flashfire doesn't seem to work properly with this device. If anyone can suggest a workaround please share.
OP, is it okay if I don't have original factory sync cable in hands?
volibyro said:
OP, is it okay if I don't have original factory sync cable in hands?
Click to expand...
Click to collapse
Yeah its ok you just run into less issues with original cable.
**Working on updating links I have a slow upload speed though.
HideTheCookies said:
I got this device used and it had been updated to the newest firmware. It would not work with Kingroot, Framaroot, SRS, or Kingo. The only option was to attempt to downgrade to an older firmware with unpatched exploits. The Verizon J1 has a locked bootloader so it cannot flash full firmware packages with older bootloaders. Luckily it can be downgraded to older firmware of the same android version with older kernel. I just had to unpack the firmware and remove the bootloader and repack. I tried to make a rooted stock firmware but can't seem to repack the system.img.ext4 properly after mounting it.
Now let's get down to business
1. Download Odin 3.09
2. Download modified (by me) rootable firmware. Do not rename file it might mess up md5sum.
3. Boot phone to download mode. Hold power+vol down+ home.
4. Start Odin and connect phone with original factory sync cable.
5. Click on the AP button and select the firmware downloaded above. It will check the md5sum automatically when it finishes and passes then press the start button. Once the flash finishes it will reboot.
6. Enable usb debugging.
7. Download Kingoroot for PC (google) and let it run. The apk will not work to root. It should install drivers automatically.
8. Profit!!
I'm testing a method to reliably switch to Supersu but having trouble updating binary 100% of the time. I've tried to flash exposed but Flashfire doesn't seem to work properly with this device. If anyone can suggest a workaround please share.
Click to expand...
Click to collapse
If u want to switch to SuperSu from KingoROOT, the best and easiest method would be backing up ur phone and performing a soft reset. Afterwards simply install SuperSu, the superuser binary is already installed from kingroot - no worries, just update it normally via SuperSU and disable KNOX after the update is complete.
That switch idea of yours might get you bricked
Confirmed it works now we need a recovery so we can just flash su
SuperSUme works really really well lol, this phone is 32bit only any1 wanna try 4 a recovery?
Thxx bro
I've tried porting a few times from the j100h twrp and keep getting a return to Verizon dealer screen. So I'd assume the bootloader is still locked. Im going to try the old safestrap and see if i can't get that working. But im kinda a noob so I'll do my best.
p.s. Don't try flashing any recovery until you backup your current one with rashr or flashify.BE SAFE.btw I've yet to see supersume actually work but hey it could happen. I'd much rather just flash the su from a recovery.
gravyd316 said:
I've tried porting a few times from the j100h twrp and keep getting a return to Verizon dealer screen. So I'd assume the bootloader is still locked. Im going to try the old safestrap and see if i can't get that working. But im kinda a noob so I'll do my best.
p.s. Don't try flashing any recovery until you backup your current one with rashr or flashify.BE SAFE.btw I've yet to see supersume actually work but hey it could happen. I'd much rather just flash the su from a recovery.
Click to expand...
Click to collapse
Agreed about flashing the recovery, but you need to be rooted with KingOroot to get SuperSUme to work, & it helps to just keep the screen timeout turned off thru this process , after it says "complete" I downloaded SuperSU & installed, updated, "disabled" knox, & I can also use flashfire although its pretty worthless for anything other than backups, as the little AROMA shell emulator thingy does run after the verizon logo is showing, which indicates to me yea its locked down pretty solid lol.
I tried Safestrap & it gave me a /SS folder in my /etc so I looked into that but I can't manage to figure out how I should go placing the files to make it work lol. But i do know this thing is 32bit ONLY, so compiling the j100H twrp for instance will NOT flash no matter what we do to the bootloader, it will bootloop since the architecture is for a 64bit SoC, we need someone to compile the j100H twrp in a 32bit only compatible architecture, & then you can easily flash it like cake, & TWRP should do the rest like all other Samsung phones O.O
its gotten to the point these are all the apps I have when i restore haha, if you wanna PM me about working together to get this thing a little more flexible I'm always open to ideas . I only use this thing as a hotspot but would totally like to see a recovery at least make it over & from there I could definitely start the ROM bringup
Will I get bricked by doing this with Verizon
Weegee1 said:
Will I get bricked by doing this with Verizon
Click to expand...
Click to collapse
you cant hard brick this device, restore with ODIN start over.
LilAnt530 said:
you cant hard brick this device, restore with ODIN start over.
Click to expand...
Click to collapse
I did it. I keep getting a notification that SE for Android has been turned off. What do I do
Weegee1 said:
I did it. I keep getting a notification that SE for Android has been turned off. What do I do
Click to expand...
Click to collapse
Download any terminal app & type in 'su' then 'setenforce 1'
---------- Post added at 12:42 AM ---------- Previous post was at 12:41 AM ----------
Weegee1 said:
I did it. I keep getting a notification that SE for Android has been turned off. What do I do
Click to expand...
Click to collapse
Download any terminal app & type in 'su' then 'setenforce 1' and you should be good.
LilAnt530 said:
Download any terminal app & type in 'su' then 'setenforce 1'
---------- Post added at 12:42 AM ---------- Previous post was at 12:41 AM ----------
Download any terminal app & type in 'su' then 'setenforce 1' and you should be good.
Click to expand...
Click to collapse
THANKS! sorry last noob question, will I lose root if I turn my phone off
Weegee1 said:
THANKS! sorry last noob question, will I lose root if I turn my phone off
Click to expand...
Click to collapse
Haha believe it or not that's a pretty reasonable question! xD, you shouldn't, i cannot see why, if you have problems just restore i will help ya through it again, & if you want xposed ONLY use the material installer from xda
LilAnt530 said:
Haha believe it or not that's a pretty reasonable question! xD, you shouldn't, i cannot see why, if you have problems just restore i will help ya through it again, & if you want xposed ONLY use the material installer from xda
Click to expand...
Click to collapse
I'll get Xposed another time. I turned off my phone a couple times but the root stayed so that's a plus :victory:
Weegee1 said:
I'll get Xposed another time. I turned off my phone a couple times but the root stayed so that's a plus :victory:
Click to expand...
Click to collapse
If you havent used SUPERSUme to transfer it over to SuperSU, google the app, can't find the free one on play store anymore i guess.
LilAnt530 said:
If you havent used SUPERSUme to transfer it over to SuperSU, google the app, can't find the free one on play store anymore i guess.
Click to expand...
Click to collapse
And with SuperSU, is that one more stable