Related
thanky you to anyone ahead of time for reading this post. I really could use some help.
I have a Verizon galaxy s3 which I rooted 3 weeks ago when i got it. I know it was rooted as i had super user permissions, and deleted many bloatware apps. I waited until cm10 came out to flash a new rom and after doing so last night my phone now boots up with this message "System software not authorized by verizon wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
So I tried to boot it in to recovery mode but when I did, the same message came up, only this time it said "recovery booting" in small blue writing in the top left corner.
I followed the directions to a T from a page entitled "Jelly Bean for Verizon Galaxy S3: Unofficial CyanogenMod 10 (CM10) Nightlies Available for Flashing!
From what I understand, the bootloader was somehow never unlocked by kexec. because I cant get in to recovery mode, I was wondering if there was a way to disable the bootlock by installing kexec via odin.
Also, whether it was a good idea or not, I re flashed the stock rom via oden last, which was successful but, nothing has changed still the same response all boot ups. Download boot obviously works though as I have been able to mess with it in odin.
any insight on this would be graciously appreciated.
Lembro said:
thanky you to anyone ahead of time for reading this post. I really could use some help.
I have a Verizon galaxy s3 which I rooted 3 weeks ago when i got it. I know it was rooted as i had super user permissions, and deleted many bloatware apps. I waited until cm10 came out to flash a new rom and after doing so last night my phone now boots up with this message "System software not authorized by verizon wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
So I tried to boot it in to recovery mode but when I did, the same message came up, only this time it said "recovery booting" in small blue writing in the top left corner.
I followed the directions to a T from a page entitled "Jelly Bean for Verizon Galaxy S3: Unofficial CyanogenMod 10 (CM10) Nightlies Available for Flashing!
From what I understand, the bootloader was somehow never unlocked by kexec. because I cant get in to recovery mode, I was wondering if there was a way to disable the bootlock by installing kexec via odin.
Also, whether it was a good idea or not, I re flashed the stock rom via oden last, which was successful but, nothing has changed still the same response all boot ups. Download boot obviously works though as I have been able to mess with it in odin.
any insight on this would be graciously appreciated.
Click to expand...
Click to collapse
Okay, first, If you did follow the directions for that thread, i'm sure it would of worked, I'm pretty sure you are missing something here and i'm pretty sure from reading your post that I think you didn't unlock your bootloader. kexec was a workaround for the locked bootloader, it doesn't unlock it. I would follow droidstyle's guide to unlocking the bootloader, http://forum.xda-developers.com/showpost.php?p=28530409&postcount=2 after you unlocked it, i'm pretty sure you forgot that step. But the issue when flashing back to stock via odin and still showing up its a custom rom, I don't know why that would happen but I suggest reading section 2 of droidstyle's guide on flashing back to stock. http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
So first, I suggest to return to stock, then root, then unlock bootloader, and then install the rom of your choice, preferably without kexec, if you don't want the triple reboot.
RyanW114 said:
Okay, first, If you did follow the directions for that thread, i'm sure it would of worked, I'm pretty sure you are missing something here and i'm pretty sure from reading your post that I think you didn't unlock your bootloader. kexec was a workaround for the locked bootloader, it doesn't unlock it. I would follow droidstyle's guide to unlocking the bootloader, http://forum.xda-developers.com/showpost.php?p=28530409&postcount=2 after you unlocked it, i'm pretty sure you forgot that step. But the issue when flashing back to stock via odin and still showing up its a custom rom, I don't know why that would happen but I suggest reading section 2 of droidstyle's guide on flashing back to stock. http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
So first, I suggest to return to stock, then root, then unlock bootloader, and then install the rom of your choice, preferably without kexec, if you don't want the triple reboot.
Click to expand...
Click to collapse
Agreed! Op, do more reading and less flashing before you end up with a 600.00 paperweight!
Like he says above you have not unlocked your bootloader . Restore nandroid or recover to stock. Then unlock your bootloader and try again
Sent from my SCH-I535 using xda premium
Get rid of the Verizon screen of death
I got the same error msg after flashing a nightly of d2hacker's unofficial cm10, after I had flashed a few nightly's before of the same ROM w/ no problems. I had to
1. Flash a stock bloated unrooted ROM via odin (lemme know if you need a link to one)
2.boot into droid recovery and do a factory reset, and wipe the cache partition also.
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
I haven't re-rooted yet but I'll be trying the official cm10 now that it's up.
MDMoore313 said:
I got the same error msg after flashing a nightly of d2hacker's unofficial cm10, after I had flashed a few nightly's before of the same ROM w/ no problems. I had to
1. Flash a stock bloated unrooted ROM via odin (lemme know if you need a link to one)
2.boot into droid recovery and do a factory reset, and wipe the cache partition also.
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
I haven't re-rooted yet but I'll be trying the official cm10 now that it's up.
Click to expand...
Click to collapse
Refer to my last post
droidstyle said:
Refer to my last post
Click to expand...
Click to collapse
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
Incorrect. It actually means the opposite. The only way to tell if your bootloader is unlocked is to flash a custom rom/kernel and boot up. Please people, do some reading before you turn your phone into a paperweight. That unlocked lock/custom means you're running or were running custom software and it's been detected as such. One possible culprit is your "custom" recovery. If your bootloader is unlocked, you will not have that problem.
MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
refer to post #3 and read this link
http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13
Zalithian said:
Incorrect. It actually means the opposite. The only way to tell if your bootloader is unlocked is to flash a custom rom/kernel and boot up. Please people, do some reading before you turn your phone into a paperweight. That unlocked lock/custom means you're running or were running custom software and it's been detected as such. One possible culprit is your "custom" recovery. If your bootloader is unlocked, you will not have that problem.
Click to expand...
Click to collapse
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
MDMoore313 said:
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Click to expand...
Click to collapse
I think it has to do with the "degree" of customization. IE a custom ROM or Kernel will get you the verizon screen of death for sure if you're not unlocked. The custom/unlock icon seems more for minor things like a custom recovery, possibly different firmware or tweaking specific settings.
Zalithian said:
I think it has to do with the "degree" of customization. IE a custom ROM or Kernel will get you the verizon screen of death for sure if you're not unlocked. The custom/unlock icon seems more for minor things like a custom recovery, possibly different firmware or tweaking specific settings.
Click to expand...
Click to collapse
That makes more sense, as the nightlys progress and more modifications are being made, overnight the "switch is flipped" so to speak, and if you're not running a custom rom,
MDMoore313 said:
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
Click to expand...
Click to collapse
Could he Odin back to stock through download mode though? Or will the locked bootloader block download mode and recovery mode too when it detects tampering?
MDMoore313 said:
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Click to expand...
Click to collapse
The secure aboot.img only checks 3 of the 5 system images on boot. Since we can flash a custom recovery to the recovery partition, the secure aboot img lets it ride, but knows it there....hence why you see the custom lock screen, but device still boots. Kexec allowed the bootloader aka secure aboot.img to see the stock kernel(boot.img) and pass signature checks, then side loads the custom kernel. Thats why there was 3 reboots...now that the bootloader is unlocked, we ditch kexec because unsecure aboot is unlocked and not checking signatures.
However, if you flash a kernel thats non kexec and the bootloader is locked, you will get the verizon screen of death since the secure aboot.img is checking signatures. So never lock the bootloader unless your on stock rom/kernel or using kexec.
Deleted
Jesus. All of these people who don't read up on things before they flash something astounds me.
Lol, the exact same thing happen to me as Op, I was unlock (ezrecovery app) and rooted(casual-revision131) but when I flash unofficial CM10 KANG I was lock out by Verizon message.Thanks to DroidStyle awesome GUIDE i just Odin back to stock along with kernel.Thank you to all the cool people here at xda who help and evolve Android:thumbup:
Ezrecovery app must not have work properly even tho it said unlock, so I use Adam casual R131 flash Unsecure Aboot too.
Sent from my SCH-I535 using xda premium
EvoSideHustlAZ said:
Lol, the exact same thing happen to me as Op, I was unlock (ezrecovery app) and rooted(casual-revision131) but when I flash unofficial CM10 KANG I was lock out by Verizon message.Thanks to DroidStyle awesome GUIDE i just Odin back to stock along with kernel.Thank you to all the cool people here at xda who help and evolve Android:thumbup:
Ezrecovery app must not have work properly even tho it said unlock, so I use Adam casual R131 flash Unsecure Aboot too.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
ezrecovery to unlock? What?
MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
No, that just means that it normally has detected some changed files. If you WERE unlocked you would never see that icon.
TAPPED in on my (now unlocked bootloader) Verizon S3
strung said:
Could he Odin back to stock through download mode though? Or will the locked bootloader block download mode and recovery mode too when it detects tampering?
Click to expand...
Click to collapse
Well, step 1 is going Odin back to stock, but if a cache wipe and factory reset aren't done (like in Droidstyle's guide), then it will never completely boot, at least that's what I experienced after my phone sat at that screen for 10+ minutes. It doesn't run the user setup again.
Hello Everyone,
I'm fairly new to rooting phones and ROMs so if this question dosn't make sense please destroy my inner child I have a rooted sgs3 using odin and factory verizon build but the problem I am having is with ClockwordMod I think. The samsung update restarts the phone but ClockworkMod starts up right away and won't let the update go through. Is there a setting I need to change to allow all updates to bypass ClockworkMod or is there another way for me to get the update?
Any help is much appreciated.
Justin
Sounds to me like cwm just saved you from an auto ota update.
I use twrp so i dont know the answer to your question but if you're rooted, why would you want an ota?
Update
maniac2k said:
Sounds to me like cwm just saved you from an auto ota update.
I use twrp so i dont know the answer to your question but if you're rooted, why would you want an ota?
Click to expand...
Click to collapse
Hello and thank you for the reply. I'm not sure that I need/want it though it continues to ask me to update so it's either keep saying defer or just let it update.
Of you download and flash one of the latest and greatest roms, you wont get asked to update. There is a way you can stop the ota but i dont remember off the top of my head. Im sure google knows. I would just flash a newer rom that includes the update.
hmmmm
maniac2k said:
Of you download and flash one of the latest and greatest roms, you wont get asked to update. There is a way you can stop the ota but i dont remember off the top of my head. Im sure google knows. I would just flash a newer rom that includes the update.
Click to expand...
Click to collapse
What would you say is the latest and greatest ROM and can I use odin to flash it? Also, if I flash a new ROM I lose everything that is on my phone right??
ndjustin20 said:
What would you say is the latest and greatest ROM and can I use odin to flash it? Also, if I flash a new ROM I lose everything that is on my phone right??
Click to expand...
Click to collapse
Well I have beans 12 and woke up and my phone also was booted into recovery and stopped the update.
Sent from my SCH-I535 using Tapatalk 2
ndjustin20 said:
What would you say is the latest and greatest ROM and can I use odin to flash it? Also, if I flash a new ROM I lose everything that is on my phone right??
Click to expand...
Click to collapse
It is going to keep rebooting into CWM if you don't tell it to until you tell it to stop rebooting to recovery, which is an option in the menu system after flashing. If the OTA update installation is being intercepted by CWM's presence on your phone, then I'm not sure if there is a way around it other than flashing a ROM. Someone with more experience will have to chime in.
With that said, should you choose to install a new ROM, there are a plethora of ROM options on XDA, at least some of which have OTA updates disabled. See the following link for a guide (I'm assuming you are on Verizon):
http://forum.xda-developers.com/showthread.php?p=32079760#post32079760
You can flash the stock, rooted ROM back on with ODIN, and then download EZ-Recovery (which has CWM) and load a custom ROM that way.
I use aokp but jellywiz is a nice stock like rom. Just download a rom and flash in cwm.
ndjustin20 said:
Hello Everyone,
I'm fairly new to rooting phones and ROMs so if this question dosn't make sense please destroy my inner child I have a rooted sgs3 using odin and factory verizon build but the problem I am having is with ClockwordMod I think. The samsung update restarts the phone but ClockworkMod starts up right away and won't let the update go through. Is there a setting I need to change to allow all updates to bypass ClockworkMod or is there another way for me to get the update?
Any help is much appreciated.
Justin
Click to expand...
Click to collapse
If you want the update you should flash back to stock and restore the stock recovery. You can reroot and unlock the boot loader after you update.
Im having same issue. Verizion trying to force my phone to have less features. I was able to ignore it 2 weeks ago but now it keeps trying to force the update and I can keep delaying it. Any good tools you all know of to just block ota updates all together? Pretty happy with stock rom as is no need to fix it minus the copy and paste bug.
You can use Titanium Backup to freeze SDM 1.0 and the update will quit downloading. I'm not sure if freezing apps is supported in the free version but the paid version is well worth it of you plan on switching ROMs.
You could also flash Scotts stock rooted Rom with the latest update, then your phone status will say up to date. I flashed the zip right on my phone through cwm but I'm sure you can use Odin too
Sent from my SCH-I535 using xda app-developers app
I was in the exact same situation as you. The phone will not update with Clockwork Recovery installed. I simply flashed back to the stock ROM via ODIN (stock.vzw_root66 which a quick search should locate), accepted the OTA update, and then used the beginner's guide in the Android Development forum to get back root.
I use Titanium Backup to freeze SDM 1.0. Like JBO1018 wrote, the PRO version is well worth the price, if only to freeze bloatware. Everything else it offers is gravy.
Questions go in Q&A
Thread moved
Thanks
This is my first post ever here so I'm sorry if I'm breaking some rule (read the forum rules so I don't think I am) or if it's in the wrong subforum (although this does seem like a help & troubleshooting topic to me).
A little backstory is probably necessary.
I rooted my s3 (latest OTA update) via CASUAL (thread: http://forum.xda-developers.com/showthread.php?t=2332825) and it seemed like it worked for the most part, although it didn't boot into twrp like it should have and instead booted into normal recovery. I just assumed that it was because something went wrong with the recovery installation so I just thought "ok whatever."
Root access was there, and I assumed the bootloader was unlocked since I read several places that when it's unlocked, the initial samsung boot logo appears for about a second as opposed to several seconds when it's locked. So I just assumed all i needed was to reinstall a custom recovery and I was golden.
Installed ROM Manager, flashed CWM through the app, and rebooted the phone, and as it was booting into recovery I was greeted with the infamous "NO CUSTOM SOFTWARE ALLOWED PLEASE ALERT PAPA VERIZON IMMEDIATELY" warning.
I was about to flash back to stock through odin (which i regretted since I've had bad experiences in the past using it) when I figured out I could get the device to boot normally by clicking cancel in the download mode confirmation window. I guess it kept trying to reboot to recovery after every unsuccessful boot, which made it seem like it was softbricked to me.
Phone is operating normally now, and it should after another reboot as long as it doesn't try to go into recovery again (though I'm kind of afraid to even do that).
Is there any way without Odin I can fix my recovery and/or bootloader? I'm not sure what the problem is here and I don't think this sort of thing is a common searchable issue. Google/XDA search didn't bring up anything that sounded like someone had 100% the same problem I do.
Also on a semi-related note, does EZ-Unlock still work with this latest OTA? And if my bootloader is potentially unlocked already, would unlocking it again through EZ-Unlock break something?
Sleix said:
This is my first post ever here so I'm sorry if I'm breaking some rule (read the forum rules so I don't think I am) or if it's in the wrong subforum (although this does seem like a help & troubleshooting topic to me).
A little backstory is probably necessary.
I rooted my s3 (latest OTA update) via CASUAL (thread: http://forum.xda-developers.com/showthread.php?t=2332825) and it seemed like it worked for the most part, although it didn't boot into twrp like it should have and instead booted into normal recovery. I just assumed that it was because something went wrong with the recovery installation so I just thought "ok whatever."
Root access was there, and I assumed the bootloader was unlocked since I read several places that when it's unlocked, the initial samsung boot logo appears for about a second as opposed to several seconds when it's locked. So I just assumed all i needed was to reinstall a custom recovery and I was golden.
Installed ROM Manager, flashed CWM through the app, and rebooted the phone, and as it was booting into recovery I was greeted with the infamous "NO CUSTOM SOFTWARE ALLOWED PLEASE ALERT PAPA VERIZON IMMEDIATELY" warning.
I was about to flash back to stock through odin (which i regretted since I've had bad experiences in the past using it) when I figured out I could get the device to boot normally by clicking cancel in the download mode confirmation window, rebooting the phone normally. I guess it kept trying to reboot to recovery after every unsuccessful boot, which made it seem like it was softbricked to me.
Phone is operating normally now, and it should after another reboot as long as it doesn't try to go into recovery again (though I'm kind of afraid to even do that).
Is there any way without Odin I can fix my recovery and/or bootloader? I'm not sure what the problem is here and I don't think this sort of thing is a common searchable issue. Google/XDA search didn't bring up anything that sounded like someone had 100% the same problem I do.
Also on a semi-related note, does EZ-Unlock still work with this latest OTA? And if my bootloader is potentially unlocked already, would unlocking it again through EZ-Unlock break something?
Click to expand...
Click to collapse
That is really weird...
I was reading it and was going to suggest easy unlock v1.2,you will not break anything using that app.
If that still doesn't work, try to flash TWRP through goo manager and see if it somehow fixes your recovery issue.
It sounds to me that your Bootloader is unlocked though... But give it a shot.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
That is really weird...
I was reading it and was going to suggest easy unlock v1.2,you will not break anything using that app.
If that still doesn't work, try to flash TWRP through goo manager and see if it somehow fixes your recovery issue.
It sounds to me that your Bootloader is unlocked though... But give it a shot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick response.
That was going to be what I tried first, that's why I asked about it.
I'll wait for a little more input before trying it though if it's really that weird of an issue.
Sleix said:
Thanks for the quick response.
That was going to be what I tried first, that's why I asked about it.
I'll wait for a little more input before trying it though if it's really that weird of an issue.
Click to expand...
Click to collapse
It's just strange that you only get that message with recovery mode, it normally will not do that.
At the very worst, an odin back to stock is pretty easy. Just follow the same process, but use ez recovery instead of rom manager. It was made specifically for our phone, and never gives me any issues when installing recoveries.
I still think if you use ez unlock it'll probably fix the issue completely. Let me know if you figure it out. Good luck.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
It's just strange that you only get that message with recovery mode, it normally will not do that.
At the very worst, an odin back to stock is pretty easy. Just follow the same process, but use ez recovery instead of rom manager. It was made specifically for our phone, and never gives me any issues when installing recoveries.
I still think if you use ez unlock it'll probably fix the issue completely. Let me know if you figure it out. Good luck.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. Used ez unlock to unlock the bootloader. It was previously labeled as "Unknown".
Downloading ez recovery right now. Do you think I need to reinstall my recovery just to make sure?
Sleix said:
Thanks. Used ez unlock to unlock the bootloader. It was previously labeled as "Unknown".
Downloading ez recovery right now. Do you think I need to reinstall my recovery just to make sure?
Click to expand...
Click to collapse
No, but it wouldn't hurt.
Use 1.2 of ez unlock, versions 1.3 and 1.4 will give an unknown message. There have also been lots of reports saying that version 1.4 did not unlock their bootloader.
These are the most recent recoveries, download and flash in the ez recovery app if you need to.
http://forum.xda-developers.com/showthread.php?t=2096735
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
No, but it wouldn't hurt.
Use 1.2, versions 1.3 and 1.4 will give an unknown message. There have also been lots of reports saying that version 1.4 did not unlock their bootloader.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Reflashed CMW (I used the version provided by ez recovery, please let me know if that's a problem) just in case and it worked like a charm. Thanks!
Also I did use version 1.2. I actually had it sitting on my phone's home screen before I made this thread.
It still showed up as "Unknown". Maybe that indicated the problem?
Regardless, this problem seems to have been fixed. Now it's time to do some research on verizon s3 roms.
Also another semi-unrelated note, it seems I tripped a flash counter somewhere along the line.
Is Triangle Away one of those apps that is just "open and press a button"? I've been kind of wary of using it since it has that huge warning in app's description.
Sleix said:
Reflashed CMW (I used the version provided by ez recovery, please let me know if that's a problem) just in case and it worked like a charm. Thanks!
Also I did use version 1.2. I actually had it sitting on my phone's home screen before I made this thread.
It still showed up as "Unknown". Maybe that indicated the problem?
Regardless, this problem seems to have been fixed. Now it's time to do some research on verizon s3 roms.
Also another semi-unrelated note, it seems I tripped a flash counter somewhere along the line.
Is Triangle Away one of those apps that is just "open and press a button"? I've been kind of wary of using it since it has that huge warning in app's description.
Click to expand...
Click to collapse
Glad to hear it's working! Strange issue but looks like you ironed it out.
Triangle away is the app you would use. You tripped it using the rooting method injecting your recovery through odin, it's a big warning because it messes with your boot partition. If it fails and borks your boot partition, then you'd have to jtag your phone to fix it.
I personally wouldn't use it unless I was turning in my phone for service or replacement. But the app has great reviews and not many reports of bricks.
Before flashing anything, use a newer recovery image. The one provided by ez recovery is from last year, the newer versions are better written to prevent possible errors that come up with jellybean.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Glad to hear it's working! Strange issue but looks like you ironed it out.
Triangle away is the app you would use. You tripped it using the rooting method injecting your recovery through odin, it's a big warning because it messes with your boot partition. If it fails and borks your boot partition, then you'd have to jtag your phone to fix it.
I personally wouldn't use it unless I was turning in my phone for service or replacement. But the app has great reviews and not many reports of bricks.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'll keep that in mind, thanks again!
Any roms you'd recommend?
Sleix said:
I'll keep that in mind, thanks again!
Any roms you'd recommend?
Click to expand...
Click to collapse
Read through the op's and decide based on what you're looking for.
Mostly stock, very stable:
Clean rom, bonestock, darthstalker x1.
More modified stocks, more buggy but can run very well:
Hyperdrive, axis, goodness, moar
AOSP isn't my cup of tea, but they are fast and lag free.
Make sure you update your recovery image first, I edited my last post but think you missed it.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Read through the op's and decide based on what you're looking for.
Mostly stock, very stable:
Clean rom, bonestock, darthstalker x1.
More modified stocks, more buggy but can run very well:
Hyperdrive, axis, goodness, moar
AOSP isn't my cup of tea, but they are fast and lag free.
Make sure you update your recovery image first, I edited my last post but think you missed it.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Will do. Thanks for pointing that edit out.
Hi Guys,
I know this may be frustrating for some of you, but as a complete beginner in using Android, I was wondering whether someone could help me out here. I have tried searching various forums, but my knowledge of androids is limited. I used the tutorial from Rootwiki to successfully unlock my bootloader, install TWRP recovery and root my phone
Does this mean I am not using a stock rom?
Now I sort of regret deciding to do this and would like to return to stock so that I can get any OTA updates without further tampering with my phone. Unfortunately while following the above tutorial, I only made a backup after TWRP was installed and not before, so I need help in going back please.
I can see that there are a few people in my position, so I'm sure others will benefit from this as well.
My software details are:
Android version - 4.2.2.
Software number - 1.33.206.1
HTC SDK API level - 5.41
Network - o2 uk
Can I use any stock recovery file or does it have to be specific to the above?
Can you please provide a step by step guide with a list of files that I will need to download?
or can I simply just factory reset my phone, and everything goes back to normal? I don't mind having to re install apps etc?
Thank you all very much
i have a HTC One mini 4.3 and i am in the exact same situation. i like to get stock recovery but those ive tried hasent been working.
If you didint flash a rom after you installed your recovery, the back up you made is then of stock os
Maybe if you take the ota, it will cancel out ur root and five you stock recovery back, i havent browsed these forums.. Try searching for a RUU and stock recovery, the phone is fairly new, so can take time for someone to put something together
Sent from my HTC6500LVW using xda app-developers app
the stock recovery must match HBOOT /Main-Version....
wich HBOOT do you have?
epolus said:
the stock recovery must match HBOOT /Main-Version....
wich HBOOT do you have?
Click to expand...
Click to collapse
Thank you for your replies, my HBOOT is 2.19.0000
Ok guys, I got the notification for the OTA update today, I have downloaded it but haven't installed it. From a different thread, I found a link for a stock recovery which is about 9.5mb from androidfile host (/?fid=23252070760975668)
can I just flash this recovery and proceed with the update? or will there be compatibility issues with the version I have above?
Thanks
Anyone?
I am getting desperate to the point that I might actually pay HTC to repair it for me
Did u have any look for I'm looking for the same but have an unrooted mini
Sent from my HTC One mini using Tapatalk
nbbcj said:
Did u have any look for I'm looking for the same but have an unrooted mini
Sent from my HTC One mini using Tapatalk
Click to expand...
Click to collapse
not yet, but MirageBlader has been quite helpful and has said the following in a private message to me, which I have yet to try:
"Very easy mate, open your ota and flash the stock recovery from the ota. You can only install it with stock Rom, stock boot and stock recovery. Your bootloader musst be locked and your phone unrooted. s-off is not needed if you already got the ota"
drewkp said:
not yet, but MirageBlader has been quite helpful and has said the following in a private message to me, which I have yet to try:
"Very easy mate, open your ota and flash the stock recovery from the ota. You can only install it with stock Rom, stock boot and stock recovery. Your bootloader musst be locked and your phone unrooted. s-off is not needed if you already got the ota"
Click to expand...
Click to collapse
I'd be very interested to know the results of your attempt to go back to "stock".
Can I ask if you are doing this just to get the 4.3 update? Also, do you plan to root and customise your ROM after the update, or leave it stock?
Thanks, and good luck....
---------- Post added at 01:14 AM ---------- Previous post was at 01:10 AM ----------
nbbcj said:
Did u have any look for I'm looking for the same but have an unrooted mini
Sent from my HTC One mini using Tapatalk
Click to expand...
Click to collapse
If your phone isn't rooted, what exactly is the issue? Do you have a custom recovery installed, and is your bootloader unlocked? If you are looking to upgrade, did you get the OTA download on your phone?
Hi nelvinchi I am trying to get back to android ver 4.2, I have a stock mini it's not been rooted or mod'd in any way. Just had the 4.3 ota that was update automatically just woke up and my phone had updated looking at settings it was set to auto update and install when on charge Grr dam phone so many probs with this ota
Sent from my HTC One mini using Tapatalk
nelvinchi said:
I'd be very interested to know the results of your attempt to go back to "stock".
Can I ask if you are doing this just to get the 4.3 update? Also, do you plan to root and customise your ROM after the update, or leave it stock?
Thanks, and good luck....
---------- Post added at 01:14 AM ---------- Previous post was at 01:10 AM ----------
If your phone isn't rooted, what exactly is the issue? Do you have a custom recovery installed, and is your bootloader unlocked? If you are looking to upgrade, did you get the OTA download on your phone?
Click to expand...
Click to collapse
I haven't got round to trying this out yet, will update this thread once I do, just quite busy this month and can't afford to mess up my phone. Yep, just doing it for the update, I only rooted my phone in the first place to get rid of bloatware, which i realised is a lot more complicated than just rooting, and all the other benefits of rooting don't really appeal to me, or are too much hassle for a beginner such as myself.
Just need to figure out how to unroot and relock my bootloader before I can go ahead with this :s
Hey nelvinchi. You seem to be knowledgeable enough on the matter and have been looking for help with my device. I posted a separate thread yesterday. If you have time/think you can help, could you take a look? Would much appreciate it.
drewkp said:
I haven't got round to trying this out yet, will update this thread once I do, just quite busy this month and can't afford to mess up my phone. Yep, just doing it for the update, I only rooted my phone in the first place to get rid of bloatware, which i realised is a lot more complicated than just rooting, and all the other benefits of rooting don't really appeal to me, or are too much hassle for a beginner such as myself.
Just need to figure out how to unroot and relock my bootloader before I can go ahead with this :s
Click to expand...
Click to collapse
If you have SuperSU installed on your phone, the app has a settings option called "Full unroot" - this will get rid of root. Relocking your bootloader - there are various methods, you could try HTCDEV site (probably how you unlocked originally), or the revone option which will lock the bootloader and remove the "tampered" label. Try a search, but if you are unsure, jusk ask!
2664963463
Got everything sorted with the great help of Nelvin. I had previously gone to the twrp support IRC and after answering a few questions, they just stopped talking... Glad there are people out there still willing to help! He spent a good hour or so with me making sure everything was working.
nelvinchi said:
If you have SuperSU installed on your phone, the app has a settings option called "Full unroot" - this will get rid of root. Relocking your bootloader - there are various methods, you could try HTCDEV site (probably how you unlocked originally), or the revone option which will lock the bootloader and remove the "tampered" label. Try a search, but if you are unsure, jusk ask!
Click to expand...
Click to collapse
Thanks for your reply nelvinchi, can I just confirm whether the SuperSU app you're talking about it the one by Chainfire in the marketplace? And is it just a matter of installing this from the marketplace to unroot my device, or is it a bit more complicated than that?
I'll do some research on relocking my bootloader with revone.
Also do you reckon the above method of getting the stock recovery from my update file will work?
Thanks for your help
drewkp said:
Thanks for your reply nelvinchi, can I just confirm whether the SuperSU app you're talking about it the one by Chainfire in the marketplace? And is it just a matter of installing this from the marketplace to unroot my device, or is it a bit more complicated than that?
I'll do some research on relocking my bootloader with revone.
Also do you reckon the above method of getting the stock recovery from my update file will work?
Thanks for your help
Click to expand...
Click to collapse
If you are rooted then you more than likely have supersu already installed. Check your app drawer.I rooted using HTC DEV and supersu was flashed to the phone with twrp as part of the process
drewkp said:
Thanks for your reply nelvinchi, can I just confirm whether the SuperSU app you're talking about it the one by Chainfire in the marketplace? And is it just a matter of installing this from the marketplace to unroot my device, or is it a bit more complicated than that?
I'll do some research on relocking my bootloader with revone.
Also do you reckon the above method of getting the stock recovery from my update file will work?
Thanks for your help
Click to expand...
Click to collapse
Can I make a suggestion? Given where you are with your phone currently, It would be much simpler, and virtually risk free, to flash tr1gg3r's Stock Sense 5.5 4.3 rooted deodexed rom from the One Mini Android Development forum.
You will get the 4.3 update, and have a fast and very stable ROM. All future updates will be incorporated into a newer ROM version.
Returning to "stock" carries FAR more risk - and you'll never have true stock because it isn't possible. Soon as the bootloader is unlocked, your phone is tampered, and no tool or utility can change that (other than cosmetically!)
It's your choice obviously, but if I was you, I'd stay rooted and enjoy the benefits it brings!
If you still want to try to go back to stock, I'll help..... But I've now helped three members get out of a soft brick after they attempted to go stock.......
If you are using the Straight Talk Galaxy S4 with build number
JSS15J.S975LUDUANB1 and just want root and simple recovery
You can root using towelroot.
SuperSU will also deactivate Knox.
Safestrap version 3.72 works for getting a proper recovery installed with the option at boot for system or recovery. Note that it will say safestrap is disabled but will still allow your choice to boot into recovery.
Make a backup in recovery as soon as you can.
Or if you want awesomeness!! Do THIS!!
Here is the definitive guide for those wondering what to do that will work and be stable and AWESOME!
From the beginning:
1.Root with towelroot (search) AND install SuperSU from the play store.
2.Install the latest recovery from here using the DD method listed directions from the TWRP site. This is from T-Mobile and works! http://forum.xda-developers.com/showthread.php?t=2263001
MAKE A BACKUP!!! DO IT! No more messing around with Safestrap and the bitter warnings!
To get into recovery hold "home+volume up" during boot. Whoooo!!!!
3. Install the Lollipop gpe ROM from here: http://forum.xda-developers.com/showthread.php?t=2539361
This uses the aroma installer and works well.
You may, or may not have to input *#6463*# into dialpad to change settings to LTE etc.. This adjustment may alsobe in the ROM settings!
4. Optional - install the googy kernel
I like this kernel better though there isn't a huge difference from the hulk kernel. Make sure to install the GE edition 1.3.0. NOT TOUCHWHIZ! : http://forum.xda-developers.com/showthread.php?t=2741181
ENJOY!
sleekmason said:
Moderator, please move to relevant forum or incorporate into the general info thread if this isn't the right place.
If you are using the Straight Talk Galaxy S4 with build number
JSS15J.S975LUDUANB1,
You can root using towelroot.
SuperSU will also deactivate Knox.
Safestrap version 3.72 works for getting a proper recovery installed with the option at boot for system or recovery. Note that it will say safestrap is disabled but will still allow your choice to boot into recovery.
Make a backup in recovery as soon as you can.
The zip to allow tethering WILL NOT work, and you will be stuck on the Samsung logo.
Xposed works well, but do not use the option in gravity box to add the recovery option to your power menu or your device will freeze upon pressing the power button.
Greenify works well.
Advise against ROM installation, as well as initial upgrade. You will lose app to SD ability if you upgrade.
The boot loader is not unlocked, so no cool kernels here
Click to expand...
Click to collapse
I was able to use towelroot and my att s4 is running on the att towers with straight talk.
mrphotoman said:
I was able to use towelroot and my att s4 is running on the att towers with straight talk.
Click to expand...
Click to collapse
Have you downloaded safestrap? Or tried anything with Xposed?
sleekmason said:
Have you downloaded safestrap? Or tried anything with Xposed?
Click to expand...
Click to collapse
No not yet, I just got the phone so I haven't done a lot to it yet. I was able to get tethering working and it was pretty easy and I got a nice extended battery case for it yesterday that I love. Other than that I haven't had time to do a lot else to it.
mrphotoman said:
No not yet, I just got the phone so I haven't done a lot to it yet. I was able to get tethering working and it was pretty easy and I got a nice extended battery case for it yesterday that I love. Other than that I haven't had time to do a lot else to it.
Click to expand...
Click to collapse
Can you tell me what you did for tethering? I tried once but was unable to get it to work.
sleekmason said:
Can you tell me what you did for tethering? I tried once but was unable to get it to work.
Click to expand...
Click to collapse
sure, i have a how to vid but i am waiting on the mod to approve it so i can post it. it definately works on the newest updated att phone
mrphotoman said:
sure, i have a how to vid but i am waiting on the mod to approve it so i can post it. it definately works on the newest updated att phone
Click to expand...
Click to collapse
Excellent! Please post a link to it here as well when you get it uploaded
Updated
See first post
I used tmo twrp. Flashed tmo and att roms. I also have the Odin file. I am not sure but I am on the s975L which I thought was att not sure but pretty sure. However it also says i337 underbattery ...I've tried more tmo roms than anything. No safestrap but I might try that later. Seems we don't have locked bootloader. This is great. However unlock is next for me. Having a blast hacking the hell out of it. So far I have had no issues. Again I'm not new to this. Lol. It's an addiction. I have sprint note 4 as my DD. So this is my fix. Lmao.
Sent from my SM-N910P using XDA Free mobile app
Droid2drummer said:
I used tmo twrp. Flashed tmo and att roms. I also have the Odin file. I am not sure but I am on the s975L which I thought was att not sure but pretty sure. However it also says i337 underbattery ...I've tried more tmo roms than anything. No safestrap but I might try that later. Seems we don't have locked bootloader. This is great. However unlock is next for me. Having a blast hacking the hell out of it. So far I have had no issues. Again I'm not new to this. Lol. It's an addiction. I have sprint note 4 as my DD. So this is my fix. Lmao.
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
As far as I know, the bootloader IS locked, but can be bypassed using Loki to patch kernels for custom roms. Glad to see somebody else on this phone
sleekmason said:
As far as I know, the bootloader IS locked, but can be bypassed using Loki to patch kernels for custom roms. Glad to see somebody else on this phone
Click to expand...
Click to collapse
That's strange. If it was locked I wonder how I've used tmo twrp no loki or SS and flashed tons of roms so far...I just odined back from a modem issue. But rerooted now off to get some modems etc...boot and all. I'll keep reporting. Thank you bro. I maintain many devices and carriers and am about to start a channel on YouTube. I do music writing now with keyboard. Now I'm just getting a hand on s4 straight talk and will make a list of all working roms.
Sent from my SM-S975L using XDA Free mobile app
Droid2drummer said:
That's strange. If it was locked I wonder how I've used tmo twrp no loki or SS and flashed tons of roms so far...I just odined back from a modem issue. But rerooted now off to get some modems etc...boot and all. I'll keep reporting. Thank you bro. I maintain many devices and carriers and am about to start a channel on YouTube. I do music writing now with keyboard. Now I'm just getting a hand on s4 straight talk and will make a list of all working roms.
Sent from my SM-S975L using XDA Free mobile app
Click to expand...
Click to collapse
True.. I don't know as much about it as I like. I just wasn't able to use fastboot or "unlock" using fastboot.
If you are working with the modems let me know how that goes, and maybe you can help with an issue I'm having? My GPS won't work after trying a ROM with safestrap. What I've posted here is a result of trying to fix it. I consistently show NO satellites. I consulted the local phone fixers to no avail. I was wondering if it could be related to a modem issue? I think the ROM I first tried did something deep to my phone, though Phone Info showed at the time everything to be original concerning baseband etc.. And a factory reset didn't help.
I'm at the point now of thinking its hardware rather than software but the coincidence to trying the ROM was too high.
Hey everyone!
I am working with this phone and am trying to get a backup modem, can you please ,make a suggestion?
Also are there any ROMs that allow easy access to umts menu through servicemenu? I know the base firmware cripples this and I'm trying to get a work around!
thanks in advanced!