Greetings,
I recently rooted my Verizon 4.4.2 S3 using TowelRoot. (SCH-I535) Afterward I attempted to flash TWRP using ODIN. I kept getting an error message when flashing. I think tried TWRP Manager. I selected the proper IMG and flashed. It said flash successful. When I enter recovery I receive a LARGE yellow caution triangle with the message, "System Software not Authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest VW store for help."
I attempted to flash the factory recovery (Verizon-SCH-I535-StockRecovery.tar) using ODIN. It says the flash is successful but I still receive the same error message. My flash counter is at zero. Any idea how I can either get my factory Recovery back or get a functional recovery?
Thanks so much!
The bootloader is locked on 4.4.2 which makes having a custom recovery impossible. Try to flash the full NE1 image in ODIN. Here's the link:
http://forum.xda-developers.com/showthread.php?t=2795659
BattsNotIncld said:
The bootloader is locked on 4.4.2 which makes having a custom recovery impossible. Try to flash the full NE1 image in ODIN. Here's the link:
http://forum.xda-developers.com/showthread.php?t=2795659
Click to expand...
Click to collapse
Thanks. I ended up using the Verizon repair tool which actually did a pretty good job. It put 4.4.2 back on unfortunetly. After that it was Towel Root then TiBu restore. So is safe strap the only way around the locked bootloader? Can I JTAG?
lilbordr said:
Thanks. I ended up using the Verizon repair tool which actually did a pretty good job. It put 4.4.2 back on unfortunetly. After that it was Towel Root then TiBu restore. So is safe strap the only way around the locked bootloader? Can I JTAG?
Click to expand...
Click to collapse
Yes safestrap is the only way around. Unfortunately you can only flash NE1 based ROMs via safestrap and there aren't any custom ones out yet that I know of. I believe the devs need kernel source released before whipping up some updated ROMs with the new base.
Regarding JTAG the guys at mobiletechvideos apparently found a way to downgrade the s3 to the 4.1.2 firmware which would allow you to unlock your bootloader again. I have not heard of anyone on here that has tried that service, though.
So i have successfully rooted my droid razr m and unlocked the bootloader. i tried using safestrap to avail, i it didnt work at all. Then i tried clock work recovery flashed through with adb. It got flashed successfully. Then tried to get recovery open didnt work. I wanted to know if the unlocked bootloader message is the cause of both programs not working. or can you guys give me maybe better instructions to start flashing roms on phone on a rooted and unlocked bootloader. THANK YOU. I wanna put a rom on my device so my phones themes look cool.
I am also on 4.4.2 stock. and how do i get rid of the unlocked bootloader message.
shawnsingh said:
So i have successfully rooted my droid razr m and unlocked the bootloader. i tried using safestrap to avail, i it didnt work at all. Then i tried clock work recovery flashed through with adb. It got flashed successfully. Then tried to get recovery open didnt work. I wanted to know if the unlocked bootloader message is the cause of both programs not working. or can you guys give me maybe better instructions to start flashing roms on phone on a rooted and unlocked bootloader. THANK YOU. I wanna put a rom on my device so my phones themes look cool.
I am also on 4.4.2 stock. and how do i get rid of the unlocked bootloader message.
Click to expand...
Click to collapse
you don't need ss any more with an unlocked bl, although it should still work. however, the version you tried probably isnt compatible with kk.
as for cwm and twrp, make sure you have the correct version for kk, and after you install it you want to boot directly into it. do not let the phone boot the os the first time or it will wipe the recovery back to the stock one. also you should grab the su flashable zip and flash that when your in recovery the first time, so you have a properly working root.
after all that you can put a rom on your phone and flash it, but make sure you get one that is on kk base or it will just bootloop.
there is a method to remove the ul bl warning, check you forums general section for the post. i know there is one in the maxx/hd forum, but i don't know if they are cross compatible.
XT907
So is there any downloads i need. Can you be alittle bit more specific. I am stuck i can root i can flash 4.4.2 kk. Just need help with flash =ing custom roms and what i need for it. Thank
bwen diord said:
you don't need ss any more with an unlocked bl, although it should still work. However, the version you tried probably isnt compatible with kk.
As for cwm and twrp, make sure you have the correct version for kk, and after you install it you want to boot directly into it. Do not let the phone boot the os the first time or it will wipe the recovery back to the stock one. Also you should grab the su flashable zip and flash that when your in recovery the first time, so you have a properly working root.
After all that you can put a rom on your phone and flash it, but make sure you get one that is on kk base or it will just bootloop.
There is a method to remove the ul bl warning, check you forums general section for the post. I know there is one in the maxx/hd forum, but i don't know if they are cross compatible.
Click to expand...
Click to collapse
I used rom manager to install cwm. It said it was successful, but now i get the "Verizon has detected unauthorized software" when i try to boot into recovery. Can i safely install stock recovery. If so, what is the safest method?
ahiredgeek said:
I used rom manager to install cwm. It said it was successful, but now i get the "Verizon has detected unauthorized software" when i try to boot into recovery. Can i safely install stock recovery. If so, what is the safest method?
Click to expand...
Click to collapse
I think this is caused by bootloader, locked by 4.3 update. I do not know the answer to your question, however I have an additional one to whoever knows the answer: is there any custom recovery at all, which is known to properly work on 4.3+?
galets said:
I think this is caused by bootloader, locked by 4.3 update. I do not know the answer to your question, however I have an additional one to whoever knows the answer: is there any custom recovery at all, which is known to properly work on 4.3+?
Click to expand...
Click to collapse
If your on the locked bootloader 4.3 ML1 the only custom recovery option you have is safestrap, no cwm, twrp or philz
From my CM11 S3
but i actually used rom manager to flash the custom recovery and it said ti was a success. but when i try to enter recovery i get the Verizon error. i need to know if i can use safestrap or any other method to flash the native recovery back, so i can use the stock recovery.
or am i getting the Verizon error because i rooted my phone?
ahiredgeek said:
but i actually used rom manager to flash the custom recovery and it said ti was a success. but when i try to enter recovery i get the Verizon error. i need to know if i can use safestrap or any other method to flash the native recovery back, so i can use the stock recovery.
or am i getting the Verizon error because i rooted my phone?
Click to expand...
Click to collapse
If you have Odin installed on a Windows computer, flash the VRUDNE1 tar in the PDA slot. This should restore your phone to stock, VRUDNE1 4.4.2 stock firmware. You also will lose the data on the phone itself so choose your download wisely.
Download Odin from this post. Run Odin on your Windows PC, select PDA, then find the VRUDNE1 4.4.2 tar that you should have downloaded. Odin only flashes .tar or .tar.md5, it will not flash any files with anything else.
Help! I cannot flash a custom recovery onto my phone (Verizon/RAZR Maxx HD). I used to have SafeStrap installed and it worked fine. One day I took a OTA update and lost root. So I used RSD Lite to re-flash my stock partition so I could take advantage of Towelroot and Motopocolypse while they still worked and was successful in doing both. So my phone was unlocked and rooted again and I was so happy I just used it as is for a few months. Later on, on decided it was time to try a new ROM, at which point I attempted to flash CWM recovery and it failed. So then I tried flashing SafeStrap again, and now that also failed. Then, in the process of troubleshooting failure to flash a custom recovery I managed to unroot myself (thanks to someone's bad advice). ... And of course this happened after I already took the OTA update that patched the towelroot exploit. So now my phone is Unlocked but not rooted anymore. I still cannot flash CWM (which is what I'd like to do) and use a custom ROM. Any helpful advice or constructive feedback would be greatly appreciated... Thanks!
Currently on Android 4.4.2, System Version 183.46.15.xt926.Verizon.en.US
Are you sure you are unlocked? Boot into your fastboot screen and tell us what it says. If you are unlocked, it's easy to regain root. Flash a recovery (try TWRP since CWM seems to not work) and flash a SU zip.
Sent from my HTC6525LVW using Tapatalk
Same Issue
Apparently they slipped in a fix for towelroot because I losr root. Still have an unlocked bootloader thanks to motopokalyse. I actually jacked my stock recovery and am working on fixing now. I'll let you know if I get it fixed and can flash a recovery.
I got the Galaxy S6 yesterday and coming from Nexus 5, I wanted to remove the existing bloatware by flashing the XtrestoLite Deodexed ROM. This one here: http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/rom-xtrestolite-deodexed-mod-edition-1-3-t3119968
I'm haven't had much experience in rooting and it's my first time flashing a custom ROM. The phone was running on Android 5.1.1.
Apparently I failed. I started with CF-Root but I wasn't sure if it was done correctly. This was followed by TWRP 2.8.7.1 . Then I tried booting up the phone and the boot logo just loops. I tried to wipe the cache as well as the Delvik-cache through TWRP but it's still the same. Then I tried to flash the stock ROM that I found online but I got the error "Nand Write Start" followed by "Fail". I seem to have tried everything and now I just want to get the phone to work again. It shouldn't be so hard.
Someone help me please :crying:
Have you tried to flash the stock rom via Smart Switch software? There's an option in the top of the window where it says "More" called Emergency Recovery. When my S6 bricked nothing but that did the trick, you should give it a try.
Gallitho said:
Have you tried to flash the stock rom via Smart Switch software? There's an option in the top of the window where it says "More" called Emergency Recovery. When my S6 bricked nothing but that did the trick, you should give it a try.
Click to expand...
Click to collapse
How did you do it? I've installed the Smart Switch software but the device doesn't appear under the list in emergency software recovery, so I can't proceed.
Edit: I managed to do it through initialization. I'll update when it's done.
Edit 2: It worked! Thanks so much!
ztmj96 said:
How did you do it? I've installed the Smart Switch software but the device doesn't appear under the list in emergency software recovery, so I can't proceed.
Click to expand...
Click to collapse
Your PC is recognizing your phone? If not maybe you shall update your drivers first. My S6 is the same model number as yours and it does appears in the Emergency Recovery list.
Another solution could be trying to flash using another version of Odin; I saw a similar problem on another forum and it was solved using Odin 3.10 to reflash the stock firmware.
Also remember that you can't downgrade your firmware once that you are on 5.1.1, no 5.02 or so allowed.
ztmj96 said:
How did you do it? I've installed the Smart Switch software but the device doesn't appear under the list in emergency software recovery, so I can't proceed.
Click to expand...
Click to collapse
By the sounds of it you're able to boot into twrp? If so then simply boot into twrp, connect to your computer and copy a flashable rom to your phone and install it using twrp instead of odin
1qazwsx4 said:
By the sounds of it you're able to boot into twrp? If so then simply boot into twrp, connect to your computer and copy a flashable rom to your phone and install it using twrp instead of odin
Click to expand...
Click to collapse
How could I transfer the flashable ROM to the phone when I can't have it boot up to connect to my computer?
Gallitho said:
Your PC is recognizing your phone? If not maybe you shall update your drivers first. My S6 is the same model number as yours and it does appears in the Emergency Recovery list.
Another solution could be trying to flash using another version of Odin; I saw a similar problem on another forum and it was solved using Odin 3.10 to reflash the stock firmware.
Also remember that you can't downgrade your firmware once that you are on 5.1.1, no 5.02 or so allowed.
Click to expand...
Click to collapse
Since you're using the same model as mine, what are you running on your S6 right now? Are you able to root and flash a custom ROM like XtrestroLite onto Android 5.1.1?
Can you guys help me check if this post has the correct steps or is it missing anything like bootloader and root?
reddit.com/r/GalaxyS6/comments/39wwf6/should_i_install_xtrestolite_rom/cs7b7yq
ztmj96 said:
Since you're using the same model as mine, what are you running on your S6 right now? Are you able to root and flash a custom ROM like XtrestroLite onto Android 5.1.1?
Click to expand...
Click to collapse
Actually yeah. Earlier tonight I flashed XtreStoLite over stock 5.1.1, but I must confess it wasn't as easy as I thought, mainly because I didn't followed the steps in the right way and I ended up having to root my phone through installing UniKernel, which is pre-rooted and that did the trick for me, because I got stuck in the Samsung logo right after I tried to flash with CF-AutoRoot, needless to say I obviously couldn't root with that method and had to reflash stock 5.1.1 firmware to unbrick my phone, install UniKernel, and after that I was able to enter my phone config, uncheck the reactivation block under Find My Mobile settings (which was the reason for me to get stuck at the S-logo) and then flash through Odin XtreStoLite deodexed and Xposed FW too, so I can tell you for sure that SM-G920I can run XSL like a charm.
Gallitho said:
Actually yeah. Earlier tonight I flashed XtreStoLite over stock 5.1.1, but I must confess it wasn't as easy as I thought, mainly because I didn't followed the steps in the right way and I ended up having to root my phone through installing UniKernel, which is pre-rooted and that did the trick for me, because I got stuck in the Samsung logo right after I tried to flash with CF-AutoRoot, needless to say I obviously couldn't root with that method and had to reflash stock 5.1.1 firmware to unbrick my phone, install UniKernel, and after that I was able to enter my phone config, uncheck the reactivation block under Find My Mobile settings (which was the reason for me to get stuck at the S-logo) and then flash through Odin XtreStoLite deodexed and Xposed FW too, so I can tell you for sure that SM-G920I can run XSL like a charm.
Click to expand...
Click to collapse
1. So what is the correct order?
2. Did you have to manually unlock bootloader?
3. And is it a must to install uniKernel in order to root the device?
I have no idea how to proceed now.
This requires a lot more effort than I thought :fingers-crossed:
1. The correct order apparently WAS to flash 5.1.1 bootloader and modem over 5.0.2, then root, then TWRP, then flash XtreStoLite, or at least that was what I understood from Edgar's guide (as you can tell, I hurried myself too much and was to excited to flash XLS, so I didn't read properly).
Since I (and I think you did too) installed stock 5.1.1 first, there was no way to autoroot nor ping-pong root the device, that was the reason I got stuck in the Samsung logo screen after trying to autoroot, so I had to reflash stock 5.1.1 to regain access to the device settings/Find My Mobile as I explained before, after that I flashed UniKernel and that did the trick, no other steps were required to achieve root access beyond this point.
2. I didn't had to, but your carrier may have locked yours. My device is a SM-G920I (as yours) from Telcel carrier, so I can tell for sure.
3. There are several others way to root devices running over 5.0.2, but according to my personal research there aren't much options on 5.1.1 other than flash a pre-rooted kernel, but UniKernel isn't the only pre-rooted kernel, so you can choose whichever you like the most.
If I were you the first thing I'd try, as I said earlier, would be to switch to another Odin version or another firmware (as long as it is 5.1.1) and if that don't do the trick, then I'd update drivers and try via Smart Switch again.
Gallitho said:
1. The correct order apparently WAS to flash 5.1.1 bootloader and modem over 5.0.2, then root, then TWRP, then flash XtreStoLite, or at least that was what I understood from Edgar's guide (as you can tell, I hurried myself too much and was to excited to flash XLS, so I didn't read properly).
Since I (and I think you did too) installed stock 5.1.1 first, there was no way to autoroot nor ping-pong root the device, that was the reason I got stuck in the Samsung logo screen after trying to autoroot, so I had to reflash stock 5.1.1 to regain access to the device settings/Find My Mobile as I explained before, after that I flashed UniKernel and that did the trick, no other steps were required to achieve root access beyond this point.
2. I didn't had to, but your carrier may have locked yours. My device is a SM-G920I (as yours) from Telcel carrier, so I can tell for sure.
3. There are several others way to root devices running over 5.0.2, but according to my personal research there aren't much options on 5.1.1 other than flash a pre-rooted kernel, but UniKernel isn't the only pre-rooted kernel, so you can choose whichever you like the most.
If I were you the first thing I'd try, as I said earlier, would be to switch to another Odin version or another firmware (as long as it is 5.1.1) and if that don't do the trick, then I'd update drivers and try via Smart Switch again.
Click to expand...
Click to collapse
What did you use to root? May I ask for the link? I just tried flashing CF AutoRoot and now I think it's bricked again. (RECOVERY IS NOT SEANDROID ENFORCING) I'm thinking it might be due to incompatibility because I got it from here (https://autoroot.chainfire.eu/#odin) and the Android version states 5.0.2.
ztmj96 said:
What did you use to root? May I ask for the link? I just tried flashing CF AutoRoot and now I think it's bricked again. (RECOVERY IS NOT SEANDROID ENFORCING) I'm thinking it might be due to incompatibility because I got it from here (https://autoroot.chainfire.eu/#odin) and the Android version states 5.0.2.
Click to expand...
Click to collapse
Yep, that was the exact moment where mine got stuck too, as I stated before at that time I had to reflash stock firmware. The trouble is caused by CF-Autoroot, it won't work at all when you're on 5.1.1 (at least with SM-G920I) and if you try to root using this method, you'll get stuck with the message "RECOVERY IS NOT SEANDROID ENFORCING". You'll have to reflash to stock too, I'm affraid...
Flash UniKernel via Odin once you're on 5.1.1 stock again and see the magic happen. Once you have root access, gained by this kernel, you can install TWRP and flash XtreStoLite or any other rom you may want. Here is the direct link to the post: http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/kernel-stockmod-kernel-t3100395
Hope you get lucky.
Gallitho said:
Yep, that was the exact moment where mine got stuck too, as I stated before at that time I had to reflash stock firmware. The trouble is caused by CF-Autoroot, it won't work at all when you're on 5.1.1 (at least with SM-G920I) and if you try to root using this method, you'll get stuck with the message "RECOVERY IS NOT SEANDROID ENFORCING". You'll have to reflash to stock too, I'm affraid...
Flash UniKernel via Odin once you're on 5.1.1 stock again and see the magic happen. Once you have root access, gained by this kernel, you can install TWRP and flash XtreStoLite or any other rom you may want. Here is the direct link to the post: http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/kernel-stockmod-kernel-t3100395
Hope you get lucky.
Click to expand...
Click to collapse
I just did that before you suggested it and it worked! I was so elated! I love you bro (no homo). Our situations are identical. Now I have XtrestroLite running on the S6! Thank you so much!
Simply put:
1. Update bootloader and modem
2. Install TWRP without root via Odin
3. Install UniKernel via TWRP
4. Install ROMs!
ztmj96 said:
I just did that before you suggested it and it worked! I was so elated! I love you bro (no homo). Our situations are identical. Now I have XtrestroLite running on the S6! Thank you so much!
Simply put:
1. Update bootloader and modem
2. Install TWRP without root via Odin
3. Install UniKernel via TWRP
4. Install ROMs!
Click to expand...
Click to collapse
Glad to read that, dude!
Yep, our situations are identical and also happened at the same time haha.
Now's time to enjoy! :good: