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.
So, a month or 2 ago, I followed some instructions on here to unlock bootloader using ez-unlock, then just a few days ago, JB update came out and after a few days I decided to wipe my phone and start fresh, now I want to relock the boot loader as I don't plan on using any roms, I was just curious.
now, when i try to run ez-lock, it comes up to a white screen and won't load fully or locks up the phone
i need some help re-locking. any ideas?
Have you already flashed the JB update or taken the OTA update? I have you then your bootloader is already locked again. If you haven't flashed any of the updates, I would check and make sure that you still have working root access. If you don't you will need to re-root. If you have root you could try a different version of EZ-Unlock. 1.2 is usually the best, but you could try 1.3.
Bootloader
BigErnM said:
Have you already flashed the JB update or taken the OTA update? I have you then your bootloader is already locked again. If you haven't flashed any of the updates, I would check and make sure that you still have working root access. If you don't you will need to re-root. If you have root you could try a different version of EZ-Unlock. 1.2 is usually the best, but you could try 1.3.
Click to expand...
Click to collapse
I did update to JB when it came out. the reason i think it's still unlocked is redbox put out a new app, and apparently it's not working with rooted devices and it comes up on mine stating there is an error and the article says the error is due to unlocked bootloader.
i just tried 1.2 and same, either comes up to white screen or locks up my phone and I have to pull battery
How did you update to JB? If you took the OTA your bootloader is definitely locked. If you followed one of the guides in the development section it may or may not be locked. Since you want to start fresh you could just flash the factory JB image and that will wipe everything, remove root and lock the bootloader. See section 5 in this guide: http://forum.xda-developers.com/showthread.php?t=1762709.
BigErnM said:
How did you update to JB? If you took the OTA your bootloader is definitely locked. If you followed one of the guides in the development section it may or may not be locked. Since you want to start fresh you could just flash the factory JB image and that will wipe everything, remove root and lock the bootloader. See section 5 in this guide: http://forum.xda-developers.com/showthread.php?t=1762709.
Click to expand...
Click to collapse
When I reboot the phone, on the first screen it shows a lock and says "custom", what is that telling me?
And yes, it was OTA.
That is telling you that your bootloader is locked. If you were unlocked you wouldn't see the message. The app error you are seeing must be coming from something else. You could still try what I posted above to get a totally clean start or you could try doing a factory reset on your phone.
BigErnM said:
That is telling you that your bootloader is locked. If you were unlocked you wouldn't see the message. The app error you are seeing must be coming from something else. You could still try what I posted above to get a totally clean start or you could try doing a factory reset on your phone.
Click to expand...
Click to collapse
The icon shows it unlocked and did a factory reset yesterday.
The icon it shows has a picture of an unlocked lock, but trust me your bootloader is locked. An unlocked bootloader will not show the word custom or that icon. You also probably do not have root access anymore which is why EZ-unlock won't load. You should try flashing the factory image I linked to above. That will almost certainly fix your issue, unless it is just a problem with the app.
BigErnM said:
The icon it shows has a picture of an unlocked lock, but trust me your bootloader is locked. An unlocked bootloader will not show the words custom or that icon. You should try flashing the factory image I linked to above. That will almost certainly fix your issue, unless it is just a problem with the app.
Click to expand...
Click to collapse
Hmm.. ok
Please read forum rules before posting
Rule 15 tells you where to post if you are confused
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Well guys, I seem to have really done it this time. I was on 4.1.2 (9.16.6) on my HDMaxx and I was having problems gaining my root access. I used Voodoo to keep root and downgraded (while I was still on 4.1.1) back to 4.0.4 and gained root, then updated all the way back up. When I did the update to 4.1.2, I seemed to have some issues with root again. RootChecker said I have root, but all my root apps said otherwise, and I was unable to update SuperUser due to the fact that it was unable to get root access. I went through the post by Dan Rosenberg (http://www.droid-life.com/2013/04/0...r-hd-running-android-4-1-2-other-devices-too/) and it reported nothing but good news. Here's where the stupidity comes in: I didn't boot back up and test to see if the root was working. I was too excited by seeing that I could (finally) unlock my bootloader. I used the motopocalypse tool, and BAM! No recovery, no rom, no nothing. All I have is a screen that says "WARNING BOOTLOADER UNLOCKED" and if I want, I could get into AP Fastboot mode. All other options (recovery, wipe, etc.) just bring me back to the indefinite screen of the unlocked bootloader. Anyone by any chance know what I could have possibly done? Thank you in advance.
Action123 said:
Well guys, I seem to have really done it this time. I was on 4.1.2 (9.16.6) on my HDMaxx and I was having problems gaining my root access. I used Voodoo to keep root and downgraded (while I was still on 4.1.1) back to 4.0.4 and gained root, then updated all the way back up. When I did the update to 4.1.2, I seemed to have some issues with root again. RootChecker said I have root, but all my root apps said otherwise, and I was unable to update SuperUser due to the fact that it was unable to get root access. I went through the post by Dan Rosenberg (http://www.droid-life.com/2013/04/0...r-hd-running-android-4-1-2-other-devices-too/) and it reported nothing but good news. Here's where the stupidity comes in: I didn't boot back up and test to see if the root was working. I was too excited by seeing that I could (finally) unlock my bootloader. I used the motopocalypse tool, and BAM! No recovery, no rom, no nothing. All I have is a screen that says "WARNING BOOTLOADER UNLOCKED" and if I want, I could get into AP Fastboot mode. All other options (recovery, wipe, etc.) just bring me back to the indefinite screen of the unlocked bootloader. Anyone by any chance know what I could have possibly done? Thank you in advance.
Click to expand...
Click to collapse
Should probably be in the Q&A section -
But try this..
see if you can mount ADB and flash a custom recovery. You will need to google search or thread search for CWM ro TWRP for the xt926 (vanquish) and see if you can flash it through ADB.
that might get you recovery back and if you have a ROM or something on your SD try that.
Action123 said:
Well guys, I seem to have really done it this time. I was on 4.1.2 (9.16.6) on my HDMaxx and I was having problems gaining my root access. I used Voodoo to keep root and downgraded (while I was still on 4.1.1) back to 4.0.4 and gained root, then updated all the way back up. When I did the update to 4.1.2, I seemed to have some issues with root again. RootChecker said I have root, but all my root apps said otherwise, and I was unable to update SuperUser due to the fact that it was unable to get root access. I went through the post by Dan Rosenberg (http://www.droid-life.com/2013/04/0...r-hd-running-android-4-1-2-other-devices-too/) and it reported nothing but good news. Here's where the stupidity comes in: I didn't boot back up and test to see if the root was working. I was too excited by seeing that I could (finally) unlock my bootloader. I used the motopocalypse tool, and BAM! No recovery, no rom, no nothing. All I have is a screen that says "WARNING BOOTLOADER UNLOCKED" and if I want, I could get into AP Fastboot mode. All other options (recovery, wipe, etc.) just bring me back to the indefinite screen of the unlocked bootloader. Anyone by any chance know what I could have possibly done? Thank you in advance.
Click to expand...
Click to collapse
So go into ap fastboot and flash via rsd lite?
Sent from my XT926 using Tapatalk 2
Franzie3 said:
Should probably be in the Q&A section -
But try this..
see if you can mount ADB and flash a custom recovery. You will need to google search or thread search for CWM ro TWRP for the xt926 (vanquish) and see if you can flash it through ADB.
that might get you recovery back and if you have a ROM or something on your SD try that.
Click to expand...
Click to collapse
dark_mirage said:
So go into ap fastboot and flash via rsd lite?
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
ADB Keeps sending me messages saying "Command Restricted" and Remote Failure. RSD Lite gives me error messages. Very confusing.
Try DROID_RAZR_HD_Utility 1.1
See if this tool will recognize your XT926 & use the menu to go back to 4.0.4 (as last resort)..
itzik_man said:
See if this tool will recognize your XT926 & use the menu to go back to 4.0.4 (as last resort)..
Click to expand...
Click to collapse
Tried it. Same thing: FAILED (Remote Failure). Any ideas??
Action123 said:
Well guys, I seem to have really done it this time. I was on 4.1.2 (9.16.6) on my HDMaxx and I was having problems gaining my root access. I used Voodoo to keep root and downgraded (while I was still on 4.1.1) back to 4.0.4 and gained root, then updated all the way back up. When I did the update to 4.1.2, I seemed to have some issues with root again. RootChecker said I have root, but all my root apps said otherwise, and I was unable to update SuperUser due to the fact that it was unable to get root access. I went through the post by Dan Rosenberg (http://www.droid-life.com/2013/04/0...r-hd-running-android-4-1-2-other-devices-too/) and it reported nothing but good news. Here's where the stupidity comes in: I didn't boot back up and test to see if the root was working. I was too excited by seeing that I could (finally) unlock my bootloader. I used the motopocalypse tool, and BAM! No recovery, no rom, no nothing. All I have is a screen that says "WARNING BOOTLOADER UNLOCKED" and if I want, I could get into AP Fastboot mode. All other options (recovery, wipe, etc.) just bring me back to the indefinite screen of the unlocked bootloader. Anyone by any chance know what I could have possibly done? Thank you in advance.
Click to expand...
Click to collapse
Why are you trying to use voodoo to keep root and then downgrade/fastboot to stock? If you are downgrading and already had root on 4.1.1 you could downgrade without root, and even on 4.1.2 rooted and unlocked you just downgrade. You don't have to worry about root. Once the phone is back to stock upgrade to the latest 4.1.2 and then use the root and unlock bootloader if needed.
Is your bootloader already unlocked?
Even if your bootloader is locked you should have no problem rooting even on 4.1.2 with motochopper. And then unlock the bootloader with motopocalypse to be able to downgrade from 4.1.2.otherwose there is no downgrading. Motochopper must be used first if you don't have root or lost root on 4.1.2 in order to use motopocalypse .
Sent from my XT926 using Tapatalk 2
an21281 said:
Why are you trying to use voodoo to keep root and then downgrade/fastboot to stock? If you are downgrading and already had root on 4.1.1 you could downgrade without root, and even on 4.1.2 rooted and unlocked you just downgrade. You don't have to worry about root. Once the phone is back to stock upgrade to the latest 4.1.2 and then use the root and unlock bootloader if needed.
Is your bootloader already unlocked?
Even if your bootloader is locked you should have no problem rooting even on 4.1.2 with motochopper. And then unlock the bootloader with motopocalypse to be able to downgrade from 4.1.2.otherwose there is no downgrading. Motochopper must be used first if you don't have root or lost root on 4.1.2 in order to use motopocalypse .
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
I'm not having issues with that stuff anymore. What I am having issues with, Is that my phone is unlocked, no rom, no recovery, etc. All I get is a warning for the unlocked bootloader and AP Fastboot. Everything else in the boot menu doesn't work. I really need to get something figured out. Nothing seems to be working. Look at the above posts for more info on the situation.
Action123 said:
ADB Keeps sending me messages saying "Command Restricted" and Remote Failure. RSD Lite gives me error messages. Very confusing.
Click to expand...
Click to collapse
Are your drivers updated on your computer?
sent from my xt926 RAZR maxx hd
I understand your situation and I have read the posts. What I am trying to say is that you did something wrong, and that there is no need to try to preserve root when fastbooting or downgrading with any utility because you will loose root. Your first post is confusing. You say you were on 4.1. 2 then 4.1.1 and downgraded. Was your bootloader unlocked prior to all this? Once your bootloader is unlocked, you can root on any firmware and sbf to factory settings which should remove root also. You need to re root, and to with motochopper it's the easiest. If I were you I would just sbf using matts until 1.20, upgrade all the way to 4.1.2 then root with utility. I don't see how it's not working.
Or sbf 4.1.2 and just root like stated above...
In order to get into fb mode do a hard reset(hold over and vol - for 10secs then immediately hold power and vol+
Sent from my XT926 using Tapatalk 2
If you can get into fastboot and are status 3 unlocked just flash a custom recovery manually and be on your way. It's not hard...
Sent from my XT926 using Tapatalk 2
---------- Post added at 12:23 AM ---------- Previous post was at 12:20 AM ----------
Start at step 3...
http://www.droidrzr.com/index.php/topic/15583-twrp-installation-on-unlocked-bl-razr-hdmaxx/
Sent from my XT926 using Tapatalk 2
koftheworld said:
Are your drivers updated on your computer?
sent from my xt926 RAZR maxx hd
Click to expand...
Click to collapse
Everything is updated. I'm on OS X dual booting windows. Tried it from both OS's and still getting same problems.
an21281 said:
I understand your situation and I have read the posts. What I am trying to say is that you did something wrong, and that there is no need to try to preserve root when fastbooting or downgrading with any utility because you will loose root. Your first post is confusing. You say you were on 4.1. 2 then 4.1.1 and downgraded. Was your bootloader unlocked prior to all this? Once your bootloader is unlocked, you can root on any firmware and sbf to factory settings which should remove root also. You need to re root, and to with motochopper it's the easiest. If I were you I would just sbf using matts until 1.20, upgrade all the way to 4.1.2 then root with utility. I don't see how it's not working.
Or sbf 4.1.2 and just root like stated above...
In order to get into fb mode do a hard reset(hold over and vol - for 10secs then immediately hold power and vol+
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
I rooted a while back. Before the 4.1.2 update came out. I was on the latest update (4.1.1) but the only way to root an HDMaxx at that time with 4.1.1 was to go back to the original 4.0.4, root, keep root using voodoo, then upgrade back to 4.1.1 again. This worked fine on 4.1.1. Then, I upgraded to 4.1.2 and I lost root (even using voodoo correctly). I tried to unlock, then wipe the phone and try to do the process over again, but now I am without rom and recovery. Plus, for whatever reason, my phone isn't responding to adb or fastboot commands. It's probably an amateur user error, but it would help if someone could point me in the right direction. My apologies for a bad initial explanation. Again, thank you in advance.
arcanexvi said:
If you can get into fastboot and are status 3 unlocked just flash a custom recovery manually and be on your way. It's not hard...
Sent from my XT926 using Tapatalk 2
---------- Post added at 12:23 AM ---------- Previous post was at 12:20 AM ----------
Start at step 3...
http://www.droidrzr.com/index.php/topic/15583-twrp-installation-on-unlocked-bl-razr-hdmaxx/
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
Tried and this is what I got back. Battery was charging all freakin night. So I doubt it's actually low.
Kim-Jong-Il:~ Cooper$ fastboot flash recovery /usr/bin/twrp-2.5.0.0-recovery-vanquish.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (7428 KB)...
OKAY [ 0.629s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.750s
Just in case you overlooked the obvious, have you tried another USB port? My Mac only has one USB 2.0 when I boot it into Windows.
Another problem I have on occasion is that the USB cable just doesn't take for whatever reason. I have to unplug it and plug it back in and try again before anything can be flashed. The phone says its plugged but nothing transfers.
To repeat what's already been said, make sure you've gotten the updated Motorola drivers for Windows.
Make sure the Android SDK is installed and fastboot and adb are added to your PATH in Windows.
If still you have nothing, I only quickly read but I didn't notice that you'de attempted to flash a stock ROM for your carrier or not. It will wipe your data and internal SD, however it seems that whatever the problem is, that if you can get into recovery then something should work.
I'm really sorry that all I can offer is redundant and basic information but sometimes we overlook what's obvious or right in front of us, and good luck with it.
Edit: Sorry, I didn't see the battery low thing. Have you tried a simulated battery pull? Hold volume up and the power button for a bit. You're wanting to feel 10 quick vibrations.
PantsDownJedi said:
Just in case you overlooked the obvious, have you tried another USB port? My Mac only has one USB 2.0 when I boot it into Windows.
Another problem I have on occasion is that the USB cable just doesn't take for whatever reason. I have to unplug it and plug it back in and try again before anything can be flashed. The phone says its plugged but nothing transfers.
To repeat what's already been said, make sure you've gotten the updated Motorola drivers for Windows.
Make sure the Android SDK is installed and fastboot and adb are added to your PATH in Windows.
If still you have nothing, I only quickly read but I didn't notice that you'de attempted to flash a stock ROM for your carrier or not. It will wipe your data and internal SD, however it seems that whatever the problem is, that if you can get into recovery then something should work.
I'm really sorry that all I can offer is redundant and basic information but sometimes we overlook what's obvious or right in front of us, and good luck with it.
Edit: Sorry, I didn't see the battery low thing. Have you tried a simulated battery pull? Hold volume up and the power button for a bit. You're wanting to feel 10 quick vibrations.
Click to expand...
Click to collapse
I think I figured out the sad truth. I take back my previous statement about charging. Since my bootloader and recovery image are not functional, in addition to not having a rom, my device is therefore unable to "accept" the charge. I'm sitting down to solder together a factory cable (which forces the device to accept the charge, by going directly into the battery). I found it here: http://droidrazrroot.com/droid-razr-hacks/how-to-make-motorola-factory-cable/
Action123 said:
I think I figured out the sad truth. I take back my previous statement about charging. Since my bootloader and recovery image are not functional, in addition to not having a rom, my device is therefore unable to "accept" the charge. I'm sitting down to solder together a factory cable (which forces the device to accept the charge, by going directly into the battery). I found it here: http://droidrazrroot.com/droid-razr-hacks/how-to-make-motorola-factory-cable/
Click to expand...
Click to collapse
Just buy a factory cable from team Black hat everyone else does.
sent from my xt926 RAZR maxx hd
koftheworld said:
Just buy a factory cable from team Black hat everyone else does.
sent from my xt926 RAZR maxx hd
Click to expand...
Click to collapse
Soldered one together in about 10 mins. Worked as expected. I guess that was just the problem. I think I'll order a cable adapter from them. Thanks for the help
Action123 said:
Soldered one together in about 10 mins. Worked as expected. I guess that was just the problem. I think I'll order a cable adapter from them. Thanks for the help
Click to expand...
Click to collapse
Most people are not so adept nor have the tools readily available to do as you did and make their own factory cable.
That's why we went to the trouble of producing the factory cable adapters so average users could have a safe and inexpensive solution to this problem and never have to worry about it.
It's the best $10 investment you can make for your Motorola device.
Congrats on being resourceful and fixing your phone yourself!
cellzealot said:
Most people are not so adept nor have the tools readily available to do as you did and make their own factory cable.
That's why we went to the trouble of producing the factory cable adapters so average users could have a safe and inexpensive solution to this problem and never have to worry about it.
It's the best $10 investment you can make for your Motorola device.
Congrats on being resourceful and fixing your phone yourself!
Click to expand...
Click to collapse
Ordered my adapter from you guys this AM
Hi everyone,
First I want to thank to this awesome community for all their enthuisasm and work.
I have a T-Mobile HTC one S with stock rom, with the latest update from T-mobile. I was wondering if there is a way to root my device without unlocking the bootloader(I know how to do it first by unlocking the bootloader, which is very easy thanks to the all-in-one kit.)
I have found a method which used to work before: One-click root, but I couldn't make it work on my device.(It used to work on htc one S devices according to some other users).
Thanks for any help.
Short answer, no.
The best thing you can do is S-OFFing, so you can restore your LOCKED status in bootloader.
Thanks for the answer. I am not worried about the LOCKED status in bootloader, I just don't want to clear my storage and then reinstall everything.
When you say no, do you mean that there is no such method right now, or that it is not possible anymore?
Because it seems that it was possible last year.
AFAIK (and as you read yourself) that method isn't working anymore...
On the other side unlocking the bootloader will factory reset your phone...
Maybe the best thing you can do is backup your apps with Titanium backup, Carbon or something like that.
nor-ric said:
Short answer, no.
The best thing you can do is S-OFFing, so you can restore your LOCKED status in bootloader.
Click to expand...
Click to collapse
Btw if your s off and run a RUU the bootloader status will be Unlocked bit with no tampered sign . It won't shoe locked . Just done this process about 2 hours ago .no glory as bootloader status unlocked
Correct me if I am wrong, but I believe I cannot ise titanium backup without root. But I will check what I can do with Carbon.
Sent from my HTC VLE_U using xda app-developers app
With s-off you can reset your lock status flag, so that it will show LOCKED again. There's a guide about this , google for it.
Try to use Carbon (now renamed to helium), it's a very powerful app.
Can Ozan said:
Correct me if I am wrong, but I believe I cannot ise titanium backup without root. But I will check what I can do with Carbon.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
I used Helium without root, backed up almost all of my apps+user settings. Highly recommended.
Quick question, to receive OTA's again if I restore a Nandroid I need to relock the bootloader, correct?
MattDN93 said:
I used Helium without root, backed up almost all of my apps+user settings. Highly recommended.
Quick question, to receive OTA's again if I restore a Nandroid I need to relock the bootloader, correct?
Click to expand...
Click to collapse
Nope, no relocking needed. You need to have a ROM that can receive the OTAs (like Zen ROM) and official recovery for the OTAs to install correctly.
Sent from my One S
Hey all.
I don't want to open another thread so, I'll just ask here for a bit of help.
I've unlocked the bootloader for a One S of a friend of mine, following the steps on the website (HTC dev). In the final window it says that everything is OK, the phone starts fine. The only issue is that some how I can't boot the phone in FASTBOOT moede (power button + Vol Down) to move on the rooting process. The phone just starts in normal mode, no mater what am I keeping pressed.
Can anybody tell me what should I do in order to be able to enter the fastboot mode?
Thank you.
After rooting my device, unlocking the bootloader, and doing s-off, the Chase mobile app wouldn't let me use QuickDeposit. Whenever I clicked on "Take Picture," it'd send me back to the home screen of the app. I downloaded the RootCloak module thinking it was probably an issue with the Chase app not working properly on rooted devices, but that didn't do anything.
I decided to unroot my phone and lock my bootloader to see if that'd work, and well, now it works. If it works now, is there a reason the RootCloak module didn't do anything? Did the locked bootloader have anything to do with it possibly (something that maybe RootCloak can't hide to apps?).
Has anyone else had the same issue on their rooted device, and is there a solution to making QuickDeposit work on a rooted phone that I don't know about?
allthemalarkey19 said:
After rooting my device, unlocking the bootloader, and doing s-off, the Chase mobile app wouldn't let me use QuickDeposit. Whenever I clicked on "Take Picture," it'd send me back to the home screen of the app. I downloaded the RootCloak module thinking it was probably an issue with the Chase app not working properly on rooted devices, but that didn't do anything.
I decided to unroot my phone and lock my bootloader to see if that'd work, and well, now it works. If it works now, is there a reason the RootCloak module didn't do anything? Did the locked bootloader have anything to do with it possibly (something that maybe RootCloak can't hide to apps?).
Has anyone else had the same issue on their rooted device, and is there a solution to making QuickDeposit work on a rooted phone that I don't know about?
Click to expand...
Click to collapse
Hmmm...interesting....My Check/Mobile Deposit for PNC works on my M8 (S-Off, Unlocked and Rooted)....but I can certainly see a banking app running those checks to ensure the phone is secured as possible in order for it to be allowed to perform banking tasks.
Unfortunately I can't assist as I do not bank with Chase to verify the issue you are having.
allthemalarkey19 said:
After rooting my device, unlocking the bootloader, and doing s-off, the Chase mobile app wouldn't let me use QuickDeposit. Whenever I clicked on "Take Picture," it'd send me back to the home screen of the app. I downloaded the RootCloak module thinking it was probably an issue with the Chase app not working properly on rooted devices, but that didn't do anything.
I decided to unroot my phone and lock my bootloader to see if that'd work, and well, now it works. If it works now, is there a reason the RootCloak module didn't do anything? Did the locked bootloader have anything to do with it possibly (something that maybe RootCloak can't hide to apps?).
Has anyone else had the same issue on their rooted device, and is there a solution to making QuickDeposit work on a rooted phone that I don't know about?
Click to expand...
Click to collapse
I have Chase. It has to be something other than root/unlock/S-Off... or if it is because of that, it is specific to the M8.
I have had Chase with a rooted HTC Evo (S-off), Thunderbolt (S-Off), Razr Maxx (rooted only), Razr Maxx HD (and the HD got unlocked before I switched phones), Droid DNA (S-off I believe, definitely rooted), Galaxy S4 (rooted and unlocked, then just rooted when my original phone died and was stuck with a new phone with a locked boot loader), and currently using a Note 3 (rooted) and I have no issues doing a quick deposit (The Galaxy line had a bug but has since been fixed, unrelated to root). The M8 I had (and is now on the second line of my account) is rooted but I am unsure if a check deposit has been attempted on it.
So I am 100% sure it is not because of the root/unlock/S-Off, BUT, it might be something to do with a new check that HTC does. Sorry I cannot be more helpful.
meteron said:
I have Chase. It has to be something other than root/unlock/S-Off... or if it is because of that, it is specific to the M8.
I have had Chase with a rooted HTC Evo (S-off), Thunderbolt (S-Off), Razr Maxx (rooted only), Razr Maxx HD (and the HD got unlocked before I switched phones), Droid DNA (S-off I believe, definitely rooted), Galaxy S4 (rooted and unlocked, then just rooted when my original phone died and was stuck with a new phone with a locked boot loader), and currently using a Note 3 (rooted) and I have no issues doing a quick deposit (The Galaxy line had a bug but has since been fixed, unrelated to root). The M8 I had (and is now on the second line of my account) is rooted but I am unsure if a check deposit has been attempted on it.
So I am 100% sure it is not because of the root/unlock/S-Off, BUT, it might be something to do with a new check that HTC does. Sorry I cannot be more helpful.
Click to expand...
Click to collapse
Hmm interesting. Would there be any way you could try it on the M8 that's on the second line of your account? You don't even have to have a check to deposit, you just have to click the "Take Picture" button on the QuickDeposit screen and see what happens. I'm going to try re-rooting my phone in a little bit to see if maybe it'll work this time.
Root cloak xposed module. :good:
Sent from my HTC6525LVW using Tapatalk
allthemalarkey19 said:
Hmm interesting. Would there be any way you could try it on the M8 that's on the second line of your account? You don't even have to have a check to deposit, you just have to click the "Take Picture" button on the QuickDeposit screen and see what happens. I'm going to try re-rooting my phone in a little bit to see if maybe it'll work this time.
Click to expand...
Click to collapse
Are you on 1.55.605.2? I believe that is the latest OTA. (?)
meteron said:
Are you on 1.55.605.2? I believe that is the latest OTA. (?)
Click to expand...
Click to collapse
Yep, I just updated to that yesterday.
allthemalarkey19 said:
Yep, I just updated to that yesterday.
Click to expand...
Click to collapse
Well hmmmm. On the latest with the M8 here. Rooted. S-On. Picture taking works.
meteron said:
Well hmmmm. On the latest with the M8 here. Rooted. S-On. Picture taking works.
Click to expand...
Click to collapse
Hmm...for a second I thought it might've been S-Off that was causing it to not work for me, but it's working for me right now and I'm unrooted S-Off.
allthemalarkey19 said:
Hmm...for a second I thought it might've been S-Off that was causing it to not work for me, but it's working for me right now and I'm unrooted S-Off.
Click to expand...
Click to collapse
And when you re-root it stops working again??
On a side note, does anyone know how to unlock the bootloader again? I locked it to test all this out, when I go back to try to unlock the bootloader, the firewater script says "there isn't a helluva lot to do here" since I'm already S-Off. If I recall correctly, the firewater script was to do S-Off and to unlock the bootloader, correct?
allthemalarkey19 said:
On a side note, does anyone know how to unlock the bootloader again? I locked it to test all this out, when I go back to try to unlock the bootloader, the firewater script says "there isn't a helluva lot to do here" since I'm already S-Off. If I recall correctly, the firewater script was to do S-Off and to unlock the bootloader, correct?
Click to expand...
Click to collapse
That I cannot help with, as the owner of the phone does not want me to S-Off/unlock... so I can't be bad LOL.
meteron said:
And when you re-root it stops working again??
Click to expand...
Click to collapse
I'm using the WeakSauce temporary root for now, and it's still working. However, I'm still on a locked bootloader (I'm trying to figure out how to unlock it again since firewater says there's nothing to do). Once I get the unlocked bootloader back, I'm going to do a permanent root and try the Chase app again. If only I could figure out how to unlock the bootloader...
allthemalarkey19 said:
I'm using the WeakSauce temporary root for now, and it's still working. However, I'm still on a locked bootloader (I'm trying to figure out how to unlock it again since firewater says there's nothing to do). Once I get the unlocked bootloader back, I'm going to do a permanent root and try the Chase app again. If only I could figure out how to unlock the bootloader...
Click to expand...
Click to collapse
Step 13 of this link (http://forum.xda-developers.com/showthread.php?t=2708628) states this:
"When completely successfully, you now have S-OFF. Your phone's bootloader is also unlocked in the process; you do NOT need to perform any additional steps to unlock the bootloader. However, you do not have permanent root. The root that weaksuace provides goes away on reboot and must be reapplied again on startup."
Not sure if that helps or not.
meteron said:
Step 13 of this link (http://forum.xda-developers.com/showthread.php?t=2708628) states this:
"When completely successfully, you now have S-OFF. Your phone's bootloader is also unlocked in the process; you do NOT need to perform any additional steps to unlock the bootloader. However, you do not have permanent root. The root that weaksuace provides goes away on reboot and must be reapplied again on startup."
Not sure if that helps or not.
Click to expand...
Click to collapse
The problem is that I've already used the firewater script in the past to unlock my bootloader and to get S-OFF. But, I had to relock my bootloader earlier today as part of my process to try to fix my Chase app issue. My phone is still S-OFF but has a locked bootloader now, so when I try to run the firewater script again, it sees that my phone is S-OFF already and says there's nothing more to do, leaving me with my bootloader still locked. I used a command prompt earlier to lock my bootloader, but can't find the command script that'll unlock it again.
I have an m7 and ever since updating the app I don't have quick deposit working either. So I think it's a problem with the app not the phone.
Sent from my HTC One using xda app-developers app
Thanks for all the help guys. I figured out what the issue was. The SwipeBack module was the culprit. I uninstalled it and now it's working.
Sent from my HTC6525LVW using xda app-developers app