My USB connector is broken on my nexus. Amazon has sent me a replacement, which I have at hand. I would like to lock my boot loader on my nexus with the broken USB connector before sending it back to amazon.
Any thoughts as to how I may accomplish this?
If not, can you at the least convince me amazon won't care that my boot loader is unlocked?
EDIT: Never mind, it seems the awesome developers have figured out ways to relock the bootloader.
https://play.google.com/store/apps/details?id=aperture.ezekeel.gladoscontrol
Potentially.
MAYBE.
Just Maybe you can re-lock with this.
I'm not sure if it requires SU or not.
And I haven't given anyone this advice yet, so you'll be the first.
But as the above poster said...
Mobile Odin first.
mt6272 said:
My USB connector is broken on my nexus. Amazon has sent me a replacement, which I have at hand. I would like to lock my boot loader on my nexus with the broken USB connector before sending it back to amazon.
Any thoughts as to how I may accomplish this?
If not, can you at the least convince me amazon won't care that my boot loader is unlocked?
Click to expand...
Click to collapse
Not sure if Amazon will even care if it is locked or not.
Thanks to AdamOutler and a few others, you can re-lock the bootloader without being plugging into a computer, but root (and busybox) is required.
Download the attachment from this post, and extract the files to the root of /sdcard. Then open a terminal emulator on your device and type the following commands:
su
dd if=/sdcard/param.lock of=dev/block/platform/omap/omap_hsmmc.0/by-name/param
That should re-lock your bootloader.
Now you need to make sure you are running a stock ROM and stock recovery.
Once that is done, you can then remove busybox, and finally, you can delete /system/app/Superuser.apk and su.
EDIT: For those that are curious, to unlock your bootloader without wiping, replace the command above with this:
su
dd if=/sdcard/param.unlock of=dev/block/platform/omap/omap_hsmmc.0/by-name/param
efrant said:
Not sure if Amazon will even care if it is locked or not.
Thanks to AdamOutler and a few others, you can re-lock the bootloader without being plugging into a computer, but root (and busybox) is required.
Download the attachment from this post, and extract the files to the root of /sdcard. Then open a terminal emulator on your device and type the following commands:
su
dd if=/sdcard/param.lock of=dev/block/platform/omap/omap_hsmmc.0/by-name/param
That should re-lock your bootloader.
Now you need to make sure you are running a stock ROM and stock recovery.
Once that is done, you can then remove busybox, and finally, you can delete /system/app/Superuser.apk and su.
Click to expand...
Click to collapse
Awesome efrant, thank you.
I'll reference to this later if need be.
efrant said:
Not sure if Amazon will even care if it is locked or not.
Thanks to AdamOutler and a few others, you can re-lock the bootloader without being plugging into a computer, but root (and busybox) is required.
Download the attachment from this post, and extract the files to the root of /sdcard. Then open a terminal emulator on your device and type the following commands:
su
dd if=/sdcard/param.lock of=dev/block/platform/omap/omap_hsmmc.0/by-name/param
That should re-lock your bootloader.
Now you need to make sure you are running a stock ROM and stock recovery.
Once that is done, you can then remove busybox, and finally, you can delete /system/app/Superuser.apk and su.
Click to expand...
Click to collapse
couldnt you take it a step further?
doesnt mobile odin work properly even if the bootloader is locked?
Zepius said:
couldnt you take it a step further?
doesnt mobile odin work properly even if the bootloader is locked?
Click to expand...
Click to collapse
Yeah, he could use mobile odin to flash to stock (and thus, no need to remove custom recovery, root, etc.), but mobile odin will not re-lock his bootloader.
efrant said:
Yeah, he could use mobile odin to flash to stock (and thus, no need to remove custom recovery, root, etc.), but mobile odin will not re-lock his bootloader.
Click to expand...
Click to collapse
ah i figured you could still use mobile odin to restore to stock with the bootloader already locked when you first run it.
ive never used it so i guess i didnt understand completely what it did.
Zepius said:
ah i figured you could still use mobile odin to restore to stock with the bootloader already locked when you first run it.
ive never used it so i guess i didnt understand completely what it did.
Click to expand...
Click to collapse
No, you're right. You CAN use mobile odin with a bootloader already locked. However, you need root to use it.
efrant said:
No, you're right. You CAN use mobile odin with a bootloader already locked. However, you need root to use it.
Click to expand...
Click to collapse
so you could then change the param file, which locks the bootloader, then use mobile odin to go back to 100% stock and still have a locked bootloader.
Zepius said:
so you could then change the param file, which locks the bootloader, then use mobile odin to go back to 100% stock and still have a locked bootloader.
Click to expand...
Click to collapse
Yes. That's what I was trying to say in my earlier post, but I guess it wasn't clear. Mobile Odin will not change the lock state of the bootloader, but will work in either a locked state or an unlocked state, assuming you have root.
More details on my phone: It is rooted, running aokp m5 & franco m3. It sounds like there is a solution to my problem contained within this thread - however, things are a bit hazy to me when it comes to what order to perform these operations and which apps to use when.
My thanks to the first person who compiles a step-by-step (albeit brief and concise) guide to unrooting, re-locking the bootloader, and restoring to stock WITHOUT being connected to the computer!
I don't know how you have broken USB, but my friend had it broken - it didn't want to charge longer than few seconds, connection to PC was extremely inconsistent...
Samsung told him that it happens on SGNs sometimes and that it is caused by oxidation of USB. It isn't covered by warranty.
But he solved it very simply - you can clean the USB by soft toothbrush and it works like a charm again. Hope this helps you.
mt6272 said:
More details on my phone: It is rooted, running aokp m5 & franco m3. It sounds like there is a solution to my problem contained within this thread - however, things are a bit hazy to me when it comes to what order to perform these operations and which apps to use when.
My thanks to the first person who compiles a step-by-step (albeit brief and concise) guide to unrooting, re-locking the bootloader, and restoring to stock WITHOUT being connected to the computer!
Click to expand...
Click to collapse
It is not that difficult, and I'm sure you do not need a step by step.
I haven't tried this on my device, as I don't really feel like wiping, but:
1) Lock your bootloader as per my post above. EDIT: I just looked at Mobile Odin, and it seems that Chainfire has implemented flashing the param partition as well in his app, so you can skip this step and go straight to step two.
2) Download the param file from the same post mentioned in step 1, and extract it to the root of your /sdcard.
3) Rename the param.lock file to param.img
4) Download version of the stock ROM for your device from here, e.g., if you have a GSM device, download the maguro factory image, if you have a Verizon device, download the toro factory image.
5) Extract the system, boot, userdata and recovery images from within and place them on the root of your /sdcard.
6) Buy Mobile Odin Pro from the Play Store. [You can use get the free version from the XDA thread here, but it needs setting up, and I'm not going to guide you through that.]
7) Run Mobile Odin Pro and follow the instructions here. It should be pretty obvious what you need to do.
I'm running AOKP 4.2, their latest release. I, too, have a failed USB connection. I downloaded the latest recovery from the link for my Verizon Toro. When I used the paid version of Mobile Odin, it says "partition could not be found in file". I tried the older, ICS image, but it just factory reset my AOKP install, not reflash to stock. So far, I've locked the boot loader, but I can't get rid of AOKP. I think it is because Mobile Odin doesn't reflash the bootloader, which I learned after my attempt, and I attempted to Odin back to factory ICS, which is a different bootloader. My other thought was to get into TWRP and flash an older AOKP ICS build, which flashes the older bootloader(right??), and try again, but I have no recovery, stock or otherwise after my Mobile Odin attempt. Any advice at this point? Should I just send it to Verizon as-is and let the chips fall where they may?
Quick update: I used Goomanager from the market to instantly flash TWRP. BAM! Recovery restored! I just finished flashing AOKP Jellybean Milestone 1, which is 4.1.2. I also figured out my JRO030 issue. It was a bad .tar file. When I browsed it with Winrar, it containted another file with the same name and no extension. I found another .tar file with the entire file structure inside. I'm currently booting into AOKP M1 as I type. I'll attempt to Mobile Odin with the JRO030 factory image (4.1.1) over 4.1.2 and then update this thread again. I hope I can save others some heartache.
The JRO030 update said something about "unable to extract update script". So I gave up on Jelly Bean and went futher back. I found an old AOKP ICS build, Milestone 6, flashed to that and used the monster 470 mb 4.0.2 update file that was linked to in a galaxynexusforums post with Mobile Odin. TADA! It worked like a charm. No root. Stock software. The only downside is that recovery is broken. It shows an Android guy with a red exclamation point over his belly. Whatever. I'm on 4.0.2 stock VZW software. That's all I care about. Let me know if anyone needs help with this.
scubamike said:
Snip
The only downside is that recovery is broken. It shows an Android guy with a red exclamation point over his belly. Whatever. I'm on 4.0.2 stock VZW software. That's all I care about. Let me know if anyone needs help with this.
Click to expand...
Click to collapse
That IS the stock recovery.
Sent from my Nexus 4 using Tapatalk 2
efrant said:
That IS the stock recovery.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I thought it was too, but, just for the heck of it, I tried taking the OTA. It rebooted and stuck on the android guy with the red exclamation. I had to pull the battery.
It is the stock recovery and no, you did not have to pull the battery. The Android with the red triangle is the main screen of the stock recovery . To access the menu from the main screen, hold power and press volume up. This is covered in at least 2 of the stickies in the General section.
Sent from my Nexus 4 using Tapatalk 2
Related
So I'm running the stock OS and now it won't install the OTA update. I'm unlocked and rooted and the update downloads, then the phone reboots. I see the install starts and runs for about 3 seconds and then it stops with the red triangle exclamation point.
What's going on, anyone else having this issue?
How many times per day does this thread need to be made?
You're either going to have to flash just the update via fastboot on your own, or unroot and accept the OTA normally.
Well I appreciate the answer, sorry to be a bother...
Anyway, is this the way it's always going to be since I'm rooted and unlocked? Where will I be able to download the OTA updates so I can flash manually with fastboot?
It won't work if you have ClockworkMod's recovery, you need the stock recovery.
Sent from my Galaxy Nexus using XDA App
105437 said:
So I'm running the stock OS and now it won't install the OTA update. I'm unlocked and rooted and the update downloads, then the phone reboots. I see the install starts and runs for about 3 seconds and then it stops with the red triangle exclamation point.
What's going on, anyone else having this issue?
Click to expand...
Click to collapse
Dowload from http://code.google.com/android/nexus/images.html. It needs 7Zip to uncompress the file. Once decompressed it has a file with no extension, decrompress that again and you will have the several file.
The just power the phone off and power back on with the volume up and down pressed. Same as when you rooted it.
Then run these commands:
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
sleep 5
fastboot update image-yakju-icl53f.zip
This will not wipe your phone!
You will need to root it again.
This is what I just did and works prefectly!
Root and unlocked bootloader shouldn't prevent you from installing if you still have stock recovery. If you have ClockworkMod recovery instead, you can use that to flash it manually. If your phone downloaded the update zip, it should be located in /cache.
You'll probably have to re-root after applying the update, regardless of how you install it.
Thanks for the replies guys! I guess I'd like to stay unlocked & rooted and be able to get OTA updates. Is there any risk in doing this? If not, how do I uninstall CWM?
Thanks again!
105437 said:
Thanks for the replies guys! I guess I'd like to stay unlocked & rooted and be able to get OTA updates. Is there any risk in doing this? If not, how do I uninstall CWM?
Thanks again!
Click to expand...
Click to collapse
I believe that in rom manager you should be able to set the recovery back to the default.
Bad Liar said:
I believe that in rom manager you should be able to set the recovery back to the default.
Click to expand...
Click to collapse
ROM Manager only has the option to flash ClockworkMod, not stock recovery. But the stock recovery can be extracted from the Google factory images and flashed with fastboot.
I have same problem like yours, how can i solved it? my device is SE WT19i
Happened to me as well - but I also ran into problems initially trying to do the image upgrades, because I had ended up changing a couple values in the build.prop file (wifi scan time, and disabling the boot animation). I'm assuming changes like that would cause the OTA update to fail, if doing it manually fails as well?
Also remember when trying to resolve my issue, reading through other people who went through similar sequences.
Had unlocked/rooted. Tried OTA - got the red warning symbol.
Tried installing the zip from sdcard through CWM but ran into various warnings/errors because of minor tweaks that either they had done, or something that had been installed had done.
Try mskip's GNex Toolkit. Super easy to use and everything explained in the thread. The guy's a genius!
http://forum.xda-developers.com/showthread.php?t=1392310
Think option 10 will reflash stock recovery.
Dark Tapatalk (GSM Galaxy Nexus)
+1. GNex Toolkit made my life worth living, I got the OTA 4.0.4 update (IMM76I), and I'm rooted and unlocked.
I also highly recommend GNex Toolkit. It has an option to restore the factory recovery and also helps you to get root again after update.
Voodoo OTA Root Keeper only helps partially.
ceribaen said:
Happened to me as well - but I also ran into problems initially trying to do the image upgrades, because I had ended up changing a couple values in the build.prop file (wifi scan time, and disabling the boot animation). I'm assuming changes like that would cause the OTA update to fail, if doing it manually fails as well?
Also remember when trying to resolve my issue, reading through other people who went through similar sequences.
Had unlocked/rooted. Tried OTA - got the red warning symbol.
Tried installing the zip from sdcard through CWM but ran into various warnings/errors because of minor tweaks that either they had done, or something that had been installed had done.
Click to expand...
Click to collapse
Each if those warnings that you are getting is because something is not stock. You will need to download the appropriate stock file for each of those warnings. I have already posted the stock build.prop and boot image in the main IMM76I update thread. If you need others, instructions can be found in the update link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
philipdeane said:
Try mskip's GNex Toolkit. Super easy to use and everything explained in the thread. The guy's a genius!
http://forum.xda-developers.com/showthread.php?t=1392310
Think option 10 will reflash stock recovery.
Dark Tapatalk (GSM Galaxy Nexus)
Click to expand...
Click to collapse
bingefister said:
+1. GNex Toolkit made my life worth living, I got the OTA 4.0.4 update (IMM76I), and I'm rooted and unlocked.
Click to expand...
Click to collapse
toxaris said:
I also highly recommend GNex Toolkit. It has an option to restore the factory recovery and also helps you to get root again after update.
Voodoo OTA Root Keeper only helps partially.
Click to expand...
Click to collapse
All of you guys recommending using a toolkit: do you even understand the OP's issue? I don't think so, otherwise you would know that a toolkit won't do what he needs done.
My opinion:
On an unrelated note: you need to figure out how to do things manually before you start using toolkits, otherwise you will never learn anything. There is a reason they teach you long division in school before letting you use a calculator...
Sent from my Galaxy Nexus using Tapatalk 2
My usb port on my phone is not working anymore and I need to return to stock for warranty. I have locked the bootloader using the app but still have TWRP and root. Is there a way to remove TWRP and unroot it without USB?
Thanks in advance!
m57 said:
My usb port on my phone is not working anymore and I need to return to stock for warranty. I have locked the bootloader using the app but still have TWRP and root. Is there a way to remove TWRP and unroot it without USB?
Thanks in advance!
Click to expand...
Click to collapse
I think once you root it, your warranty is void regardless if you go back or not.
If you open the super su app it has an option to fully unroot. I've never tried it. Not sure about getting boot loader back
Sent from my Galaxy Nexus using Tapatalk 2
I just need to return Recovery to stock and unroot. I'll check out the super su unroot option when I get home.
I've also been trying to install the OTA to 4.2.2 as this will restore stock ecovery but I'm getting a error (assert failed apply_patch_check( /system/lib/hw) I did have franco kernel and have returned back to stock and put a copy of power.tuna.so but that did not fix it.
Did you search first? I believe I've seen a post by franco about that issue. Also, there is this thread, among others: http://forum.xda-developers.com/showthread.php?t=2160790. I'd like to see if this would work for the recovery[before unrooting]: http://forum.xda-developers.com/showpost.php?p=38486011&postcount=8
bodh said:
Did you search first? I believe I've seen a post by franco about that issue. Also, there is this thread, among others: http://forum.xda-developers.com/showthread.php?t=2160790. I'd like to see if this would work for the recovery[before unrooting]: http://forum.xda-developers.com/showpost.php?p=38486011&postcount=8
Click to expand...
Click to collapse
I did do a bit of searching. I downloaded a power.tuna.so file from this thread http://forum.xda-developers.com/showthread.php?t=2031985 but the OTA still did not flash.
Im not quite sure how deeply you've modded your device. If you fix this, will it then give another error is what i'm saying.. You're going to be looking for a system.img flash, whether it be via .zip or mobile odin. Did you verify the permissions and ownership on the replacement power.tuna.so, should be 644 root.root. Did you wipe caches after replacing it?
m57 said:
My usb port on my phone is not working anymore and I need to return to stock for warranty. I have locked the bootloader using the app but still have TWRP and root. Is there a way to remove TWRP and unroot it without USB?
Thanks in advance!
Click to expand...
Click to collapse
What about using ADB over network? I noticed that under Developer Options is that choice,so this could be the possible replacement of damaged USB port.
Well looks like I screwed something up when I tried to restore some of the hw files and now the phone gets stuck at the X loading screen. It does have a locked bootloader but still has TWRP installed so I guess my only option is to send it back for warranty and hope they don't notice the custom recovery.
I have an idea that may work... (IT worked like a charm for me)
1)find a flashable recovery zip. it can be a cwm.zip
2)replace the recovery.img file inside a package with the stock one.
3) upload modified to a server, then download to your phone.
4)flash it with twrp
5)reboot recovery
I don't think you're gonna mess up anything more. It worked for me.
Or If you are on yakju/takju 4.2.2 jdq39 you may try my zip I attached below.
So if anybody's been reading the news, you may know that the bootloader for the Razr M has finally been unlocked!
So here's a how-to on unlocking and flashing a custom recovery.
A couple notes:
This essentially makes the phone behave like an unlocked dev edition. You can flash any firmware, recovery, etc that you want. Be careful, don't flash stuff for other devices, etc etc...
FOLLOW THE INSTRUCTIONS...
Future OTAs may (will) disable this exploit. Do it while it can be done! Also, beware OTAs! They could disable this, or do bad things... Don't update unless you know it won't disable the bootloader exploit
You need to be rooted, have the motorola drivers installed (link here - sorry, it's device manager, but they do have all the drivers in a nice package...)
First, root if you haven't already...
Next, download Motopocalypse.zip by Dan Rosenberg from here: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
extract the zip and run
Run through the entire process, until it tells you you have a bootloader unlock.
Make sure that AP Fastboot indicates "Unlocked, status code 3"
Also, when you reboot, you will get a warning screen about an unlocked bootloader.
Next, choose your recovery. There are 2 options, TWRP (Touch Win Recovery Project) and CWM (ClockworkMod)
either works, and each has benefits and downsides, choose whichever one you want.
Follow the instructions for your flavor of recovery:
CWM:
Download the .img file here: http://goo.im/devs/Hashcode/scorpion_mini/cwm-recovery--scorpion_mini.img
Move it to the same place you extracted the .zip above.
Open a command prompt/terminal/command interpreter at that location (Windows short-cut: shift-right click, command window here)
type the following (filename is the name of the file you downloaded, probably "cwm-recovery--scorpion_mini.img" unless you renamed it): fastboot flash recovery filename
and press Enter. Let it flash, then reboot.
The first time you use CWM, it will ask you if you want to disable something that would cause CWM to stop working. You do want to, so say "yes". Othewise, you'll have to reflash CWM every time you want to use it
TWRP:
Download the .img file here: http://d-h.st/QGe
Move it to the same place you extracted the .zip above.
Open a command prompt/terminal/command interpreter at that location (Windows short-cut: shift-right click, command window here)
type the following (filename is the name of the file you downloaded, probably "twrp2.4-recovery-scorpion_mini.img" unless you renamed it):
fastboot flash recovery filename
and press Enter. Let it flash, then reboot.
Now, you need to disable the automatic re-flashing of stock recovery.
Reboot directly into recovery, and allow TWRP to disable the re-flashing.
Now, you have TWRP running on your Razr M
Please consider donating to Dan Rosenberg here for all the work he's done for our phones!
Congrats! You now have a custom recovery on your Razr M
Reboot into recovery, and you're done!
----IMPORTANT NOTE:----
IF you are on the latest OTA and have NOT unlocked, it is impossible at this time to unlock. It may be possible in the future if someone finds another exploit, but not likely. Basically, if you updated without researching (that's why you shouldn't do that) or got a new one after the OTA, you're SOL for right npw
sloosecannon said:
So if anybody's been reading the news, you may know that the bootloader for the Razr M has finally been unlocked!
So here's a how-to on unlocking and flashing a custom recovery.
A couple notes:
This essentially makes the phone behave like an unlocked dev edition. You can flash any firmware, recovery, etc that you want. Be careful, don't flash stuff for other devices, etc etc...
FOLLOW THE INSTRUCTIONS...
Future OTAs may (will) disable this exploit. Do it while it can be done! Also, beware OTAs! They could disable this, or do bad things... Don't update unless you know it won't disable the bootloader exploit
You need to be rooted, have the motorola drivers installed (link here - sorry, it's device manager, but they do have all the drivers in a nice package...)
First, root if you haven't already...
Next, download Motopocalypse.zip by Dan Rosenberg from here: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
extract the zip and run
Run through the entire process, until it tells you you have a bootloader unlock.
Make sure that AP Fastboot indicates "Unlocked, status code 3"
Also, when you reboot, you will get a warning screen about an unlocked bootloader.
Next, choose your recovery. There are 2 options, TWRP (Touch Win Recovery Project) and CWM (ClockworkMod)
either works, and each has benefits and downsides, choose whichever one you want.
Follow the instructions for your flavor of recovery:
CWM:
Download the .img file here: http://goo.im/devs/Hashcode/scorpion_mini/cwm-recovery--scorpion_mini.img
Move it to the same place you extracted the .zip above.
Open a command prompt/terminal/command interpreter at that location (Windows short-cut: shift-right click, command window here)
type the following (filename is the name of the file you downloaded, probably "cwm-recovery--scorpion_mini.img" unless you renamed it): fastboot flash recovery filename
and press Enter. Let it flash, then reboot.
The first time you use CWM, it will ask you if you want to disable something that would cause CWM to stop working. You do want to, so say "yes". Othewise, you'll have to reflash CWM every time you want to use it
TWRP:
Download the .img file here: http://goo.im/devs/Hashcode/scorpion_mini/twrp2.4-recovery-scorpion_mini.img
Move it to the same place you extracted the .zip above.
Open a command prompt/terminal/command interpreter at that location (Windows short-cut: shift-right click, command window here)
type the following (filename is the name of the file you downloaded, probably "twrp2.4-recovery-scorpion_mini.img" unless you renamed it):
fastboot flash recovery filename
and press Enter. Let it flash, then reboot.
Now, you need to disable the automatic re-flashing of stock recovery.
Run adb shell from the same info and run the following commands (you can copy-paste and press enter):
su
mount -o remount,rw /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mount -o remount,ro /system
Now, you have TWRP running on your Razr M
Please consider donating to Dan Rosenberg here for all the work he's done for our phones!
Congrats! You now have a custom recovery on your Razr M
Reboot into recovery, and you're done!
Click to expand...
Click to collapse
I followed the instructions, ran the .bat, but my Razr M is still being shown as locked 1. Am on 4.1.1 stock rom. Do I need to uninstall SafeStrap?
Edit- Found my answer, the phone needed to be unlocked so it could ask me for SU permissions. Hope this helps someone else so I don't feel like the only idiot.
As long as we do this first, future OTAs can't relock our bootloaders, can they?
Awesome!!!! Hopefully this will spark up some dev activity. I know this is huge I just hope its not too little too late.
BoredKender said:
I followed the instructions, ran the .bat, but my Razr M is still being shown as locked 1. Am on 4.1.1 stock rom. Do I need to uninstall SafeStrap?
Edit- Found my answer, the phone needed to be unlocked so it could ask me for SU permissions. Hope this helps someone else so I don't feel like the only idiot.
Click to expand...
Click to collapse
Nope, don't need to uninstall safestrap, and yep, you do need SU.
sujaanj said:
As long as we do this first, future OTAs can't relock our bootloaders, can they?
Click to expand...
Click to collapse
That's really not known... advise you steer clear of OTAs for the time being... until we can determine if it will actually relock or not...
sloosecannon said:
That's really not known... advise you steer clear of OTAs for the time being... until we can determine if it will actually relock or not...
Click to expand...
Click to collapse
Well, from what I read from Dan's explanation on his website, we are essentially blowing a fuse that can not be reset. So I'm leaning towards rejecting OTAs from now on but according to my limited understanding, we will be safe.
trouble installing recovery
Thanks! I successfully unlocked the bootloader following the awesome instructions AP Fastboot indicated "Unlocked, status code 3"
I then let the device reboot.
I'm trying to install CWM following the instructions and I get <waiting for device>
This makes me think i need to not have the phone booted into the OS
What am I doing wrong.
Please excuse my newbness
Regards,
Darryl
dnoren said:
Thanks! I successfully unlocked the bootloader following the awesome instructions AP Fastboot indicated "Unlocked, status code 3"
I then let the device reboot.
I'm trying to install CWM following the instructions and I get <waiting for device>
This makes me think i need to not have the phone booted into the OS
What am I doing wrong.
Please excuse my newbness
Regards,
Darryl
Click to expand...
Click to collapse
You need to be in fast boot mode for it to flash recovery.
Turn off your device, hold Power + Vol Up + Vol down then select fast boot and plug your phone into your computer.
Sent from my XT907 using xda premium
new roms
Thanks for the write up, worked flawlessly. So I did this with safestrap installed, can I just wipe the phone and install a rom made for safestrap like you normally would with CWM?
CaptainElwood said:
Thanks for the write up, worked flawlessly. So I did this with safestrap installed, can I just wipe the phone and install a rom made for safestrap like you normally would with CWM?
Click to expand...
Click to collapse
Yes, as long as you mount your /system first. Found that out the hard way too...
Does this wipe our phone
Sent from my XT907 using xda app-developers app
Nope
ifrankie10 said:
Does this wipe our phone
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
No, everything is the same except I get a warning every boot that my phones bootloader is unlocked
Has anyone flashed a dev edition rom yet? If so what one, I wanted to try but the cm10 thread has broken links. Can I get that somewhere else?
Also say my screen cracks and I call Motorola and they say send it out and they see that it is unlocked does that mean they will not repair it
Sent from my XT907 using xda app-developers app
---------- Post added at 03:11 AM ---------- Previous post was at 03:07 AM ----------
and can we rsd back to stock if we can't get into the recovery but into fastboot
Sent from my XT907 using xda app-developers app
I'm trying to help unlock my friends razr m, but his device was updated to 4.1.1 in the Verizon store by one of the sales associates. Does the root method (required for bootloader unlock) work on 4.1.1?
Sent from my SCH-I535 using Tapatalk 2
mindflayyer said:
I'm trying to help unlock my friends razr m, but his device was updated to 4.1.1 in the Verizon store by one of the sales associates. Does the root method (required for bootloader unlock) work on 4.1.1?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
If I recall correctly, 4.1.1 is fine, just use the JB root method. 4.1.2 is an issue, but that has not been pushed yet (on Verizon that is).
Floundering with recovery
I've tried both methods cwm and twrp it says writing recovery, okay, and finished but when i try to go into recovery I just get the Green robot
Any ideas on what I'm doing wrong?
Thanks
Cant get this to work and I can't get safestrap off my phone
Sent from my cm_tenderloin using Tapatalk HD
Hmm..
Also say my screen cracks and I call Motorola and they say send it out and they see that it is unlocked does that mean they will not repair it
Click to expand...
Click to collapse
If they are able to discover that the phones system files have been tampered with in anyway, including unlocking, rooting, installing custom recoveries, roms, modems etc.. most likely they will not fix your phone. Quoted off the Motorola website "Unlocking your DEVELOPER EDITION's bootloader voids all warranties" (Naturally this goes for retail edition even more so). I have however hear of people getting unlocked phones repaired under warranty, just make sure that you RSD back to stock, unrooted before you send it.
pjf626 said:
Cant get this to work and I can't get safestrap off my phone
Sent from my cm_tenderloin using Tapatalk HD
Click to expand...
Click to collapse
Gonna need a tad more detail.. Are you sure that you're rooted? If not, that would cause both of your problems. You also need to uninstall safestrap through the safestap app, and then remove the app.
sujaanj said:
Well, from what I read from Dan's explanation on his website, we are essentially blowing a fuse that can not be reset. So I'm leaning towards rejecting OTAs from now on but according to my limited understanding, we will be safe.
Click to expand...
Click to collapse
Yes unlocking is blowing a fuse but that's beside the point, there is a separate piece of software that looks at that fuse and decides whether to allow the system to boot an unsigned system or not. If the OTA changes this piece of software to use another fuse instead (there might be many of them) then your device will be locked again and we will be back at square one, no fuse need to actually be reset for this to happen.
ok, I got stock 4.4.4 but with root, bootloader is locked..
I wanna be able to receive the OTA update what do I need to do in order to be able to receive that?
or do I need to unlock the bootloader, install a recovery and flash lollipop threw that?
If you have stock system, kernel, and recovery, (no altered system files, either) being rooted won't keep you from getting the OTA. Locked/unlocked bootloader doesn't matter. If you rooted with SuperSu, just use its settings to uninstall root (you'll lose it anyway). However, I think you have to unlock bootloader to reroot, which, of course, will wipe your device. The OTA zip is now available for adb sideload if you're interested.
nvm got stock recovery back on, lol still learning, is it better to side load or can i use flash stock + unroot on the nexus root toolkit v1.9.3 to do the same?
Cobra11Murderer said:
nvm got stock recovery back on, lol still learning, is it better to side load or can i use flash stock + unroot on the nexus root toolkit v1.9.3 to do the same?
Click to expand...
Click to collapse
OTA won't wipe regardless of how you get it--over the air or sideloaded. Wug's will wipe unless you tell it not to (Options>Flash Stock>Enable no wipe). He also has the LRX21P build available. IMO, one way isn't better than another.
ok, I just tried to sideload and looks like i got a driver issue :\ lol followed the steps in the installation guide and did the test.. it works great up till i go into stock recovery and hit sideload lol then it disconnects and tells me no driver found...
i might just try flash stock + unroot and choosing LRX21P, that wont lock my bootloader correct? and should I be a little worried that the driver cant be found for that specific thing? thanks for all the help btw!
You probably already did all this, but you have to specifically send command to lock boot loader. I don't get how your device wasn't recognized through stock recovery but is on NRT, but it doesn't matter. Just use the kit which is what you probably did.
What you should do is back up what you need and want, then unlock the bootloader. You're not gonna get root without it on Android L since it requires a custom kernel.
Cobra11Murderer said:
ok, I just tried to sideload and looks like i got a driver issue :\ lol followed the steps in the installation guide and did the test.. it works great up till i go into stock recovery and hit sideload lol then it disconnects and tells me no driver found...
i might just try flash stock + unroot and choosing LRX21P, that wont lock my bootloader correct? and should I be a little worried that the driver cant be found for that specific thing? thanks for all the help btw!
Click to expand...
Click to collapse
Based on this, I assumed you unlocked your bootloader since first posting. NRT recognizes the device, right? Have you gotten it all sorted out yet.
idk why adb sideloading would kick the connection out, then the pc would say nexus 7 but wrong driver?, anyways i just went ahead and flashed the factory image using flash stock + unroot since I had it all backed up anyways, and that went great now I got lollipop on it, and should be able to root no probs now
thanks everyone, I hope i dont have a issue with adb again, im not sure if it was the samsung cord or what but it kept disconnecting at that part asking for a driver.. funny thing everything from bootloader, fastboot and all worked great with the driver that I installed using the steps in the toolkit..
Glad it's all good. Root with the toolkit. Just for the heck of it, you may want to try running CMD from wug's ADB folder. I've experienced just the opposite with older versions of the kit. NRT wouldn't recognize device. I'd go to CMD and device recognized. Return to NRT, all good again.
alrighty will do!, thanks for all your help
My knox was not tripped.
Highly recommend to have a odin firmware!
Tested on 5.1.1
Recommend to update to PB2, BACK UP BACK UP BACK UP may delete everything.
http://www.mediafire.com/download/kuvw79x83zrdpc9/N920AUCU2APB2_User_Binary.zip
A not much has been said in the thread, yes after Odin flashing the ENG kernel for our device and flashing a root script we can use rooted apps. @metalcated*posted a script that does push SuperSU into system/. This was originally posted in the AT&T GS6 forum. It's a potentially complicated process and if your phone shuts off, battery dies or you hard reboot you will be stuck in a bootloop, hotbooting works fine for Xposed. Will this method be practical for everyone probably not, but considering we were told the device was unrootable........
Read thru his thread, then read it again, seriously do this. And if you still want to try, backup everything you can just in case you need to reflash via Odin to recover from a bootloop. Here were my steps.
1. Yes this needs to be flashed before the process begins, the script wont run with the stock kernel.*
Here's a link to the eng kernel. Download and extract. Yes flash via ODIN, add the kernel file to the AP slot.*
http://www.mediafire.com/?2i5aeu6pr0ms7io
2. The only file I downloaded and used was this one:
http://www.mediafire.com/?m0b639pfnavjmha
(G920a5.1.1.root.metalcated-v4.zip)
3.Save it and extract it on your PC
4. Verify Samsung drivers and adb are installed
5.***ENABLE USB DEBUGGING*** this is an important step.*
6. Plug device into PC open file and run root script. It'll prompt you to press enter a couple of times and reboot the phone. Just follow the on-screen instructions.
7. After it reboots you have root access.
Root apps that work for me: Titanium backup/root explorer/build.prop editor/no frills.
I was able to delete all Knox apps and debloat the heck of the stock ROM. At no point did my device freeze, reboot on its own.
Let's work on bootloader unlock so we can flash custom rom, kernel and recoverys.
Thanks to Michael3214 for finding the method.
Thanks to Metalcateds for scripts.
Has anyone tried to push a script to make SELinux permissive on boot? We might be able to unteather the root.
http://forum.xda-developers.com/ver...ipt-permissive-selinux-stock-kernels-t2854364
KillKount said:
Has anyone tried to push a script to make SELinux permissive on boot? We might be able to unteather the root.
http://forum.xda-developers.com/ver...ipt-permissive-selinux-stock-kernels-t2854364
Click to expand...
Click to collapse
I have tried this with no luck. It seams to be something in the kernel that's preventing untethered reboots so far. We can use this root to unlock bootloader with someone who is good enough.
TechNyne66 said:
I have tried this with no luck. It seams to be something in the kernel that's preventing untethered reboots so far. We can use this root to unlock bootloader with someone who is good enough.
Click to expand...
Click to collapse
There are some people looking into this but haven't had much luck as of yet. It also requires a lot of time which I haven't had much of lately. Hope someone else can jump in here as well. [emoji6]
metalcated said:
There are some people looking into this but haven't had much luck as of yet. It also requires a lot of time which I haven't had much of lately. Hope someone else can jump in here as well. [emoji6]
Click to expand...
Click to collapse
Im not sure where to start. If you want to point me in the right direction i could posably help. Flashify does write recovery and kernel just gets blocked by bootloader.
do we have a xposed we can use?
TechNyne66 said:
Im not sure where to start. If you want to point me in the right direction i could posably help. Flashify does write recovery and kernel just gets blocked by bootloader.
Click to expand...
Click to collapse
There is an eng BL out there which allows flashing a recovery img but the signature checks fail so that doesn't work anyhow. Your welcome to try it. I can send you a link for it.
does anyone know whee to get the stock kernel?
This is confirmed working. I rooted, debloated, and unrooted and can now reboot with no worries and no bloat.
bmatney said:
This is confirmed working. I rooted, debloated, and unrooted and can now reboot with no worries and no bloat.
Click to expand...
Click to collapse
how did you unoot?
blane3298 said:
how did you unoot?
Click to expand...
Click to collapse
One of the last options in the settings of supersu is to fully unroot.
do you know if we can unroot and flash the stock kernel and be good to go? My phone was laggy with the eng kernel
metalcated said:
There is an eng BL out there which allows flashing a recovery img but the signature checks fail so that doesn't work anyhow. Your welcome to try it. I can send you a link for it.
Click to expand...
Click to collapse
I would be willing to try bootloader if it will work on OGG firmware.
Has anyone tried this on PB2 ?
Sent from my SGH-M919 using XDA Free mobile app
dpwguenther said:
Has anyone tried this on PB2 ?
Sent from my SGH-M919 using XDA Free mobile app
Click to expand...
Click to collapse
Yes the kernel required to root other builds is the PB2 ENG
Can I use this on my s6 active? Thanks in advance.
blane3298 said:
do you know if we can unroot and flash the stock kernel and be good to go? My phone was laggy with the eng kernel
Click to expand...
Click to collapse
I performed the root. At the beginning yes it was laggy but i went ahead download (NO-frills CPU) base level has been 1.2GHZ max 1.5GHZ. Power-save mode ON and ZENUI launcher. AND my friends have been happy every since. NO lag at all.
TechNyne66 said:
My knox was not tripped.
Highly recommend to have a odin firmware!
Tested on 5.1.1
A not much has been said in the thread, yes after Odin flashing the ENG kernel for our device and flashing a root script we can use rooted apps. @metalcated*posted a script that does push SuperSU into system/. This was originally posted in the atat GS6 forum. It's a potentially complicated process and if your phone shuts off, battery dies or you hard reboot you will be stuck in a bootloop, hotbooting works fine for Xposed. Will this method be practical for everyone probably not, but considering we were told the device was unrootable........
Read thru his thread, then read it again, seriously do this. And if you still want to try, backup everything you can just in case you need to reflash via Odin to recover from a bootloop. Here were my steps.
1. Yes this needs to be flashed before the process begins, the script wont run with the stock kernel.*
Here's a link to the eng kernel. Download and extract. Yes flash via ODIN, add the kernel file to the AP slot.*
Link 1 https://mega.nz/#!lZhwxB4Q!pdBsM51Do...d4l8ANPqTKVc9E
Link 2 http://www.mediafire.com/?2i5aeu6pr0ms7io
2.Metalcateds thread is here:
http://forum.xda-developers.com/att-...-snag-t3334546
3. The only file I downloaded and used was this one:
https://www.androidfilehost.com/?fid=24438995911977129
(G920a5.1.1.root.metalcated-v4.zip)
4.Save it and extract it on your PC
5. Verify Samsung drivers and adb are installed
6.***ENABLE USB DEBUGGING*** this is an important step.*
7. Plug device into PC open file and run root script. It'll prompt you to press enter a couple of times and reboot the phone. Just follow the on-screen instructions.*
8. After it reboots you have root access.*
Root apps that work for me: Titanium backup/root explorer/build.prop editor/no frills.
I was able to delete all Knox apps and debloat the heck of the stock ROM. At no point did my device freeze, reboot on its own.
Let's work on bootloader unlock so we can flash custom rom, kernel and recoverys.
Thanks to Michael3214 for finding the method.
Thanks to Metalcateds for scripts.
Click to expand...
Click to collapse
Fix your links.
First, link 1. goes to an encrypted file on Mega.
Second this link https://www.androidfilehost.com/?fid=24438995911977129 doesn't link to the Root script but links out to metalcated's debloated system image for the S6.
Edit: Well that was quick to brick my phone haha. Script finished, phone rebooted to AT&T logo, script failed and now its soft bricked XD haha.
Guess it's time to ODIN.
TechNyne66 said:
My knox was not tripped.
Highly recommend to have a odin firmware!
Tested on 5.1.1
A not much has been said in the thread, yes after Odin flashing the ENG kernel for our device and flashing a root script we can use rooted apps. @metalcated*posted a script that does push SuperSU into system/. This was originally posted in the atat GS6 forum. It's a potentially complicated process and if your phone shuts off, battery dies or you hard reboot you will be stuck in a bootloop, hotbooting works fine for Xposed. Will this method be practical for everyone probably not, but considering we were told the device was unrootable........
Read thru his thread, then read it again, seriously do this. And if you still want to try, backup everything you can just in case you need to reflash via Odin to recover from a bootloop. Here were my steps.
1. Yes this needs to be flashed before the process begins, the script wont run with the stock kernel.*
Here's a link to the eng kernel. Download and extract. Yes flash via ODIN, add the kernel file to the AP slot.*
Link 1 https://mega.nz/#!lZhwxB4Q!pdBsM51Do...d4l8ANPqTKVc9E
Link 2 http://www.mediafire.com/?2i5aeu6pr0ms7io
2.Metalcateds thread is here:
http://forum.xda-developers.com/att-...-snag-t3334546
3. The only file I downloaded and used was this one:
https://www.androidfilehost.com/?fid=24438995911977129
(G920a5.1.1.root.metalcated-v4.zip)
4.Save it and extract it on your PC
5. Verify Samsung drivers and adb are installed
6.***ENABLE USB DEBUGGING*** this is an important step.*
7. Plug device into PC open file and run root script. It'll prompt you to press enter a couple of times and reboot the phone. Just follow the on-screen instructions.*
8. After it reboots you have root access.*
Root apps that work for me: Titanium backup/root explorer/build.prop editor/no frills.
I was able to delete all Knox apps and debloat the heck of the stock ROM. At no point did my device freeze, reboot on its own.
Let's work on bootloader unlock so we can flash custom rom, kernel and recoverys.
Thanks to Michael3214 for finding the method.
Thanks to Metalcateds for scripts.
Click to expand...
Click to collapse
i believe THIS >>> https://mega.nz/#!lZhwxB4Q!pdBsM51DoMOvgaQ4j4saZKRCezTWFd4l8ANPqTKVc9E <<< was the link you where looking for for the ENG. Kernel..... N920A.7z i have the root script also downloaded
i will post all in an index file with a site to follow
JeSTeRH4CK3D said:
i believe THIS >>> https://mega.nz/#!lZhwxB4Q!pdBsM51DoMOvgaQ4j4saZKRCezTWFd4l8ANPqTKVc9E <<< was the link you where looking for for the ENG. Kernel..... N920A.7z i have the root script also downloaded
i will post all in an index file with a site to follow
Click to expand...
Click to collapse
Will fix in a bit just making my family dinner.