Related
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
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.
Sent from my HTC One_M8 using XDA Free mobile app
KitKat and SD card issue, if you are stock and rooted - use this http://goo.gl/UfqPKb
Thanks for your reply. My m8 is stock...n I am not planning to root my phone yet as I am new to android. Is there a fix for stock m8
Sent from my HTC One_M8 using XDA Free mobile app
beastyricky said:
Thanks for your reply. My m8 is stock...n I am not planning to root my phone yet as I am new to android. Is there a fix for stock m8
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Nope, no way.
You have to switch to the dark side (root) of android users only ;D
Hahaha...I will try it out then...hope my phone won't get bricked...
Sent from my HTC One_M8 using XDA Free mobile app
You won't brick your phone rooting it. HTC even provide the tools to help achieve it by unlocking the boot loader. All you need do then is install twrp recovery and it will do the rest.
Don't even need to install/flash TWRP to get it rooted, can just boot TWRP and still flash SuperSU to get root, which is what I have done. Benefit - You get to keep stock recovery for future OTA's (Even though you can flash it later on, I know... =oP )
BerndM14 said:
Don't even need to install/flash TWRP to get it rooted, can just boot TWRP and still flash SuperSU to get root, which is what I have done. Benefit - You get to keep stock recovery for future OTA's (Even though you can flash it later on, I know... =oP )
Click to expand...
Click to collapse
good to hear HTC let you do this again!!! I thought they stopped doing this on the first hboot update on m7, great stuff!!! :good:
BerndM14 said:
Don't even need to install/flash TWRP to get it rooted, can just boot TWRP and still flash SuperSU to get root, which is what I have done. Benefit - You get to keep stock recovery for future OTA's (Even though you can flash it later on, I know... =oP )
Click to expand...
Click to collapse
cool, how do I just boot TWRP without actually installing it so I can retain my regular stock recovery to take OTA's? I thought I had to install it? I have not rooted M8 yet, but I did my EVO 4G LTE - was just hanging back to make sure the initial OTA's were all out before rooting - but if I can just boot TWRP to install supersu that would make life so much easier.
tommy_riley said:
cool, how do I just boot TWRP without actually installing it so I can retain my regular stock recovery to take OTA's? I thought I had to install it? I have not rooted M8 yet, but I did my EVO 4G LTE - was just hanging back to make sure the initial OTA's were all out before rooting - but if I can just boot TWRP to install supersu that would make life so much easier.
Click to expand...
Click to collapse
Boot into bootloader, connect phone to PC, open command prompt, change directory to adb.exe / fastboot.exe folder. Type fastboot devices to make sure your device gets picked up, should show you serial number of the phone. Then type fastboot boot name_of_recovery.img. Just make sure you have the custom recovery(TWRP) extracted(not in .zip form) in the fastboot/adb folder as well.
Done, that's it :good:
Edit: Of course I'm sure you know the bootloader needs to be unlocked as well.
BerndM14 said:
Boot into bootloader, connect phone to PC, open command prompt, change directory to adb.exe / fastboot.exe folder. Type fastboot devices to make sure your device gets picked up, should show you serial number of the phone. Then type fastboot boot name_of_recovery.img. Just make sure you have the custom recovery(TWRP) extracted(not in .zip form) in the fastboot/adb folder as well.
Done, that's it :good:
Edit: Of course I'm sure you know the bootloader needs to be unlocked as well.
Click to expand...
Click to collapse
excellent, thanks for the quick reply and also not saying "go search for it" - yeah, very familiar with the bootloader unlocking method via htc website - I don't know a lot but have spent some time with unlocking
I also feel proud to be one of the few who knows how to get adb/flashing to work via my windows 8.1 USB3.0 only system - but that's another story.
thanks again for the response - going to go do this later today.
Hello everyone, im really mew to rooting.
I have the T Mob M8 with 5.0.1, i was planning on rooting but will I be able to update nprmally wjen 5.1 comes out? If so how?
Also whats tje easiest method to root this phone? Ive seen apks like framaroot that root the phone extremely quick and easy...is there something similar for this phone?
Thanks in advance
Sent from my HTC One_M8 using XDA Free mobile app
Root by unlocking the bootloader via HTCDev.com and then just install custom recovery and flash current (2.56) SuperSU zip.
One click root solutions won't work with a locked bootloader. Unlocking the bootloader is really the key.
Once rooted, you can OTA. But you need to have stock ROM (nothing altered in /system partition) and you need to re-install stock recovery. Root is okay (although you will likely lose root) and unlocked bootloader is okay to OTA. To root again after an OTA, just install custom recovery and flash SuperSU again.
Thanks a lot. I will unlock the bootloader and can you link me to a good tutorial or guide on how to install custom recovery and supersu?
Thanks again
Sent from my HTC One_M8 using XDA Free mobile app
Red_Gh0st said:
Thanks a lot. I will unlock the bootloader and can you link me to a good tutorial or guide on how to install custom recovery and supersu?
Click to expand...
Click to collapse
The following guide is a pretty good one: http://forum.xda-developers.com/showthread.php?t=2799796
Although some links are outdated:
1) Installing HTCSync should be fine to get the HTC drivers on your computer; or you can search XDA for more recent HTC drivers. The HTC drivers linked in the guide are really old.
2) Get the latest SuperSU zip here: http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3) And if you need an easy adb/fastboot installer, just use the XDA seach function with the phrase "simple adb" and you will get a few results for beginner adb guides and installers.
4) Get the latest version of TWRP here: http://techerrata.com/browse/twrp2/m8
redpoint73 said:
The following guide is a pretty good one: http://forum.xda-developers.com/showthread.php?t=2799796
Although some links are outdated:
1) Installing HTCSync should be fine to get the HTC drivers on your computer; or you can search XDA for more recent HTC drivers. The HTC drivers linked in the guide are really old.
2) Get the latest SuperSU zip here: http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3) And if you need an easy adb/fastboot installer, just use the XDA seach function with the phrase "simple adb" and you will get a few results for beginner adb guides and installers.
4) Get the latest version of TWRP here: http://techerrata.com/browse/twrp2/m8
Click to expand...
Click to collapse
hello I saw your post Im planning also to root my m8 but I dont want to flash the custom recovery someone told me it is possible
just download the custom recovery
then type "fastboot boot recovery.img" = this will boot my m8 to custom recovery but not flash so I can flash the supersu in that custom recovery then reboot after that stock recovery is still intact
imfuzzyyy said:
hello I saw your post Im planning also to root my m8 but I dont want to flash the custom recovery someone told me it is possible
just download the custom recovery
then type "fastboot boot recovery.img" = this will boot my m8 to custom recovery but not flash so I can flash the supersu in that custom recovery then reboot after that stock recovery is still intact
Click to expand...
Click to collapse
That's true, you can boot TWRP remotely with fastboot, without actually flashing it (installing to the phone).
Although its slightly irrelevant; you can always flash back to stock recovery back to the phone (over-write TWRP). You can either find your stock recovery posted in the collection; or back it up your self using the fastboot TWRP trick (fastboot boot TWRP, and use TWRP to backup stock recovery). In that instance, the fastboot boot TWRP trick is very useful.
Having TWRP installed after root is very useful. Reason being, it gives you a lot more recovery options if things go south. And also, for a lot of mods done under root, you will want to backup your stock setup anyway (just in case the mod goes wrong, and you need to revert). Stock recovery is close to useless for anything but installing OTA updates.
redpoint73 said:
That's true, you can boot TWRP remotely with fastboot, without actually flashing it (installing to the phone).
Although its slightly irrelevant; you can always flash back to stock recovery back to the phone (over-write TWRP). You can either find your stock recovery posted in the collection; or back it up your self using the fastboot TWRP trick (fastboot boot TWRP, and use TWRP to backup stock recovery). In that instance, the fastboot boot TWRP trick is very useful.
Having TWRP installed after root is very useful. Reason being, it gives you a lot more recovery options if things go south. And also, for a lot of mods done under root, you will want to backup your stock setup anyway (just in case the mod goes wrong, and you need to revert). Stock recovery is close to useless for anything but installing OTA updates.
Click to expand...
Click to collapse
woah didnt know that I can back up the stock recovery by fastboot boot in TWRP BTW if I'm using this phone I will probably use a TWRP but its my gf who uses it so she just need the root access for xmod app because she is an coc adik haha and she doesnt know about modding its system, thanks for this wonderful information
---------- Post added at 01:33 AM ---------- Previous post was at 01:13 AM ----------
hello I need your help this m8 is previously rooted have supersu installed then take OTA before now it is not rooted but the supersu still intact on my apps, I fastboot boot twrp.img then went smoothly flash the supersu.zip but Im still unrooted any suggestion? it say on root checker the root access is not properly installed
update: sorry got root now I flashed the 1.94.zip which is very outdated didnt notice it flashed the latest 2.46.zip now its rooted thank you so much!
Hello I finally started downloading everything to get started. I start the process to unlock the bootloader but when i get to the part i need to type "fastoboom oem....." On cmd I get an error saying Adbwinapi.dll is missing try reinstalling the program.
What can I do to fix this?
Sent from my HTC One_M8 using XDA Free mobile app
Red_Gh0st said:
On cmd I get an error saying Adbwinapi.dll is missing try reinstalling the program.
Click to expand...
Click to collapse
Is HTC Sync installed? If so, re-install it.
Reinstalled but it still says tht file is missing from my conputer
Sent from my HTC One_M8 using XDA Free mobile app
Red_Gh0st said:
Reinstalled but it still says tht file is missing from my conputer
Click to expand...
Click to collapse
Try a different adb installer.
Thanks a lot I unlocked my bootloader and rooted my phone
I'm trying to root my ZE551ML (WW-2.20.40.198) and install Xposed, but I can't get any of the scripts I've found here to work. I've installed ADB & Fastboot and this driver. MTP works and adb works when I'm in recovery mode, so I'm not sure why the scripts can't contact the device. None of the scripts recognize the device. Also, "adb devices" shows that no device is found.
It seems that all these scripts are using some variation of CWM to do it anyway. So if I could just install CWM in some other way, I guess I could just get root and xposed through CWM. I have used this official ASUS app to unlock the bootloader. So, I wonder if I could just flash a recovery.img of CWM using the command "fastboot flash recovery recovery.img"? Is that all it would take to get CWM installed? And then I could use CWM to get root, etc?
If yes, which recovery.img file should I use and where can I get it?
I think I can get fastboot to work when the device is in the bootloader, so that's what I'm thinking. Also, I can use OS X or Ubuntu then, so I don't have to worry about the Windows scripts.
Fiksdal said:
I'm trying to root my ZE551ML (WW-2.20.40.198) and install Xposed, but I can't get any of the scripts I've found here to work. I've installed ADB & Fastboot and this driver. MTP works and adb works when I'm in recovery mode, so I'm not sure why the scripts can't contact the device. None of the scripts recognize the device. Also, "adb devices" shows that no device is found.
It seems that all these scripts are using some variation of CWM to do it anyway. So if I could just install CWM in some other way, I guess I could just get root and xposed through CWM. I have used this official ASUS app to unlock the bootloader. So, I wonder if I could just flash a recovery.img of CWM using the command "fastboot flash recovery recovery.img"? Is that all it would take to get CWM installed? And then I could use CWM to get root, etc?
If yes, which recovery.img file should I use and where can I get it?
I think I can get fastboot to work when the device is in the bootloader, so that's what I'm thinking. Also, I can use OS X or Ubuntu then, so I don't have to worry about the Windows scripts.
Click to expand...
Click to collapse
Worth checking general section
http://forum.xda-developers.com/zenfone2/general/index-asus-zenfone-2-wip-t3149748
http://forum.xda-developers.com/zenfone2/development/z00az008-zenfone-2-t3265236
Hmmm.. Nevermind, I did it through TWRP. Followed this tutorial. Root works
Fiksdal said:
Hmmm.. Nevermind, I did it through TWRP. Followed this tutorial. Root works
Click to expand...
Click to collapse
Tip
It is always worth googling
and put an XDA on the end
timbernot said:
Tip
It is always worth googling
and put an XDA on the end
Click to expand...
Click to collapse
Haha, you know, I had been struggling with this problem for like 2 days. So many hours on the computer and Google trying to figure it out. I was trying to get the scripts to work, then CWM, then TWRP. I was just really confused and didn't know how to do it since most guides on Google said I had to use the scripts for Windows. Then finally I realized that it was as simple as using fastboot from OS X Anyway, sorry to bother you guys. But Everything is working now, root, Xposed and permanent TWRP. Awesome
Good stuff
There was a script at the beginning in earlier fw versions I think when boot loader was first being hacked.
Remember , if you upgrade to M , unlock boot loader again at .134 with modder tool in general section before updating to .144 and then to .184.
another tip
timbernot said:
Good stuff
There was a script at the beginning in earlier fw versions I think when boot loader was first being hacked.
Remember , if you upgrade to M , unlock boot loader again at .134 with modder tool in general section before updating to .144 and then to .184.
another tip
Click to expand...
Click to collapse
Yeah, I've tried Marshmallow already, but my favorite Xposed modules didn't work, so I've downgraded to Lollipop again
Fiksdal said:
Yeah, I've tried Marshmallow already, but my favorite Xposed modules didn't work, so I've downgraded to Lollipop again
Click to expand...
Click to collapse
You are doing great now :victory: