Requirements:
[ROOT REQUIRED]
[OEM Unlocking must be allowed under the developer options before flashing this file AND stay activated
as long as you want the device to stay unlocked (OnePlus implemented security features which locks the device on reboot with the switch off)]
* I am not responsible for bricked devices, thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about this method before using it!
* YOU are choosing to make these modifications.
* And if you point the finger at me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
WARNING: THESE FILES ARE BASED ON THE OXYGEN OS 2.1.1 FIRMWARE, PLEASE ANALYZE YOUR DEVINFO IF THE VERSION IS DIFFERENT TO MAKE SURE NOT BRICKING SOMETHING!
I have not upgraded my device to 2.1.2 yet because there have been some issues with the newest firmware.
Tested and confirmed working on:
OxygenOS 2.2.0 - thanks to @pryggi
OxygenOS 2.1.1
Hydrogen OS 1.2.0 - thanks to @fareed_xtreme
I looked at this thread, thanks to Naman Bhalla for this great work.
and found out that the file attached to this post is the answer to my problem, described in another thread.
After the whole day of work analyzing and dumping and saving via adb from my device to the pc and the other way around i finally did it.
On the frist screenshot is my situation before flashing the new devinfo, on the second after flashing the devinfo from the thread mentioned above.
By changing the bits with a Hex Editor of your choice, or by flashing the files below via dd:
Code:
dd bs=4096 of=/dev/block/bootdevice/by-name/devinfo if=/sdcard/oneplus2-devinfo-factory.img
The output should look like the following:
Code:
0+1 records in
0+1 records out
1024 bytes transferred in 0.005 secs (204800 bytes/sec)
You can restore your OnePlus 2 to a factory state while still having root or unlock your phone again without having to wipe it! :highfive:
Credits:
Naman Bhalla
Also to segv11 who already managed this in the OnePlus One and Nexus devices
wow nice job m8
sent from rooted phone
Modified the same location using a HEX Editor (root) whilst on the Hydrogen OS 1.2.0 and I must say it works.
Screenshot Attached. Good Find @thedropdead
Thank you and thanks for testing it out on Hydrogen OS @fareed_xtreme
It is not a Revolution like CM13 on the 1+2, but its helpful for people like me who use their developer devices as daily drivers and still want to lock and unlock the device because of security reasons without wiping the whole device.
fareed_xtreme said:
Modified the same location using a HEX Editor (root) whilst on the Hydrogen OS 1.2.0 and I must say it works.
Screenshot Attached. Good Find @thedropdead
Click to expand...
Click to collapse
thedropdead said:
Thank you and thanks for testing it out on Hydrogen OS @fareed_xtreme
It is not a Revolution like CM13 on the 1+2, but its helpful for people like me who use their developer devices as daily drivers and still want to lock and unlock the device because of security reasons without wiping the whole device.
Click to expand...
Click to collapse
I needed it for resetting the tamper flag. I have certain issues with my phone and might have to return it in the near future and hence this was important. So thanks again.
fareed_xtreme said:
I needed it for resetting the tamper flag. I have certain issues with my phone and might have to return it in the near future and hence this was important. So thanks again.
Click to expand...
Click to collapse
Thats another good thing to do with it
It was a pleasure to help you out mate
Thanks, I was waiting for this for securing my OPT. Has anyone tested, if it works also on OOS 2.2.0?
Just to clarify, the dd command should be executed in TWRP console?
Would be cool if someone could make an app for this like the Nexus devices have:
https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
pryggi said:
Thanks, I was waiting for this for securing my OPT. Has anyone tested, if it works also on OOS 2.2.0?
Just to clarify, the dd command should be executed in TWRP console?
Would be cool if someone could make an app for this like the Nexus devices have:
https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
Click to expand...
Click to collapse
Hello pryggi,
It should also work on OOS 2.2.0, you could check that by dumping the partition (by reversing the dd command) like this:
Code:
dd bs=4096 if=/dev/block/bootdevice/by-name/devinfo of=/sdcard/oneplus2-devinfo-oos220.img
And looking at the file in the hex editor for differences or by posting it here and i can check it for you.
I have executed the dd command from ADB Shell with the Phone connected via wireless ADB.
You can also execute dd in the Android Terminal Emulator App.
Thanks for your reply. My device is already unlocked. As I don't have a computer with ADB/drivers at hand right now, I managed to run the dd command in Terminal Emulator app after elevating with su. Result is attached. Viewing it in hex seems to confirm, that at least the locking bit seems to be in the same position.
pryggi said:
Thanks for your reply. My device is already unlocked. As I don't have a computer with ADB/drivers at hand right now, I managed to run the dd command in Terminal Emulator app after elevating with su. Result is attached. Viewing it in hex seems to confirm, that at least the locking bit seems to be in the same position.
Click to expand...
Click to collapse
Thank you for the Dump, i can confirm that the bit is at the same position and the unlock bit is the same.
I compared the file attached at my first post with yours and they are identical ( see attachment, sorry its german, meaning is they are identical).
So by flashing the factory.img from my first post or unchecking OEM Unlock allowed in the developer Settings your device should be locked again and can be unlocked by flashing the unlock.img via dd in ADB or the Android Terminal Emulator within the Phone.
Thanks for the further explanation. I was just wondering about this OEM Unlocking switch in dev options. What would happen, if one would use dd and the factory image file to lock the bootloader and leave the OEM Unlocking switch still unlocked...
I also am interested if this type of locking-unlocking can be done in TWRP... If it can be done there, then it does not offer any benefits in security, if my logic is correct. Although, I might be drifting off topic here.
pryggi said:
Thanks for the further explanation. I was just wondering about this OEM Unlocking switch in dev options. What would happen, if one would use dd and the factory image file to lock the bootloader and leave the OEM Unlocking switch still unlocked...
I also am interested if this type of locking-unlocking can be done in TWRP... If it can be done there, then it does not offer any benefits in security, if my logic is correct. Although, I might be drifting off topic here.
Click to expand...
Click to collapse
As i can remember i tried that too, by flashing the factory image partition via dd and leaving the switch on, the switch gets toggled off when rebooting, because the switch is just the representation of the unlocking bit in the partition. So when it is turned off, the software will set the bit to zero, means the device will get locked on reboot. Turning the switch on will not override the bit and the device can boot unlocked and the switch will stay on.
It is hard to explain
Your Idea about doing the same thing in TWRP since the ADB is available there is interesting.
I think the problem here is, that once you onlock and flash a custom recovery via fastboot, and relock the device, you already tampered with it, and twrp does provide much more options than the stock recovery image (ADB commands, ...).
So the problem here lies in flashing twrp.
I solved this problem by keeping the stock recovery and locking the device via the image file.
Once i want to use twrp, i unlock the phone by using the unlock.img and use "fastboot boot twrp.img" to boot twrp to backup my device or some other action.
I know that this means if my device gets bricked in this locked state with stock recovery i will have to unlock it normally, but before making any important changes to my software i always unlock my device first in case something goes wrong and with the stock recovery i could not even flash anything so making huge software changes requires me to unlock my device and boot twrp
Hope that this post helps somehow
FYI: The HEX hack must work on almost all OPT OS Releases.Kinda universal
fareed_xtreme said:
FYI: The HEX hack must work on almost all OPT OS Releases.Kinda universal
Click to expand...
Click to collapse
That is right, i just included the notice in the first post so nobody can tell me i have not told them
It is also possible that OnePlus changes the layout of that partition in one of the upcoming updates/releases and that is why it is still mentioned in the first post, thank you anyway.
@thedropdead I've a question: I should use the "modified" devinfo.img AFTER I go back to stock, if I want to unlock my phone without wiping data, right ? So I go back to stock, flash in fastboot or in terminal emulator the .img, and that's good ? I'me unlocked without data wiped ?
casual_kikoo said:
@thedropdead I've a question: I should use the "modified" devinfo.img AFTER I go back to stock, if I want to unlock my phone without wiping data, right ? So I go back to stock, flash in fastboot or in terminal emulator the .img, and that's good ? I'me unlocked without data wiped ?
Click to expand...
Click to collapse
That should be the plan if i have understood everything right.
So you are on the custom ROM, want to go back to the stock ROM?
If that is the case i do not see why you should want to flash any image.
You can use TWRP to wipe and then flash the stock ROM, your phone should still be unlocked right?
Please someone correct me if i am wrong.
It would be great if you could tell me what you are trying to achieve.
The unlock image had the purpose to help someone unlock their device if they have a rooted device but have locked it after flashing everything for security reasons.
thedropdead said:
That should be the plan if i have understood everything right.
So you are on the custom ROM, want to go back to the stock ROM?
If that is the case i do not see why you should want to flash any image.
You can use TWRP to wipe and then flash the stock ROM, your phone should still be unlocked right?
Please someone correct me if i am wrong.
It would be great if you could tell me what you are trying to achieve.
The unlock image had the purpose to help someone unlock their device if they have a rooted device but have locked it after flashing everything for security reasons.
Click to expand...
Click to collapse
Well, for now I'm under CM13, and, yeah, I know I could wipe and flash stock in TWRP, I just want to know in case .
casual_kikoo said:
Well, for now I'm under CM13, and, yeah, I know I could wipe and flash stock in TWRP, I just want to know in case .
Click to expand...
Click to collapse
Okay thanks for the clarification.
In the Case of using some unbrick Tool and thus resetting everything including recovery to stock your phone should lock on the first stock boot.
Once it is locked and you do not have root, which would be the case, you have no possibility to flash the img via fastboot or the emulator.
so in conclusion you are better off with wiping and flashing via twrp so you can still flash something if anything goes wrong
It works on OxygenOS 3.0.2 too. I edit the same location using a HEX Editor. And everything is fine.
Hey guys, sounds like this is exactly what I've been looking for. Thanks for figuring this out.
But, I'm a bit of a noob, so can you break it down into like a hundred very clear steps?
Related
hi
i have problem in my wifi
i trued to flash Rogers rom by fastboot and when its start its flashed the boot.img and recovery.img only and stop to flash the system.img
after that my WIFI starting give me error and i cant swith it on
so please any one can upload the boot.img for AT&T version so i can able to reflash it again
is that how its called? boot.img?
i can't seem to find such a file (in root explorer)
do you know where can i find it?
Here you go...
I extracted these from the PG09IMG_Puccini_LTE_Cingular_US_1.17.502.3_Radio_1.04.550I.15v2_30.60.550I.10_release_210183_signed ROM file... hope it helps.
boot.img
wifi_htc_bcmMFG248_ag_tx_rx_swap.img
yes you can use it from footballs topic. or the puccini leak topic. extract from the zip file. btw. I cannot flash that whole zip anyhow.
Thanks i have done from the boot. mg from PG09IMG_Puccini_LTE_Cingular_US
I dont know why we cannot download an official RUU for ATT devices. WHY? it will makes thing easier. If your device went wrong, you can easily flash it back to factory state.
Hi, I got this wifi error now,
Is the solution and correct conditions and commend as described in below steps: -
boot into fastboot
connnect USB and it shows the USB word behind fastboot.
then from dos prompt enter commend
fastboot flash wifi_htc_bcmMFG248_ag_tx_rx_swap.img
done?
end?
Thanks.
cx5 said:
Hi, I got this wifi error now,
Is the solution and correct conditions and commend as described in below steps: -
boot into fastboot
connnect USB and it shows the USB word behind fastboot.
then from dos prompt enter commend
fastboot flash wifi_htc_bcmMFG248_ag_tx_rx_swap.img
done?
end?
Thanks.
Click to expand...
Click to collapse
When using fastboot flash you have to specify a partition to flash, so that command will not work. The correct command is:
Code:
fastboot flash boot wifi_htc_bcmMFG248_ag_tx_rx_swap.img
I am not guaranteeing that it will solve your problem, only that it will actually flash your boot partition. The best outcome is that it fixes your problem. The worst outcome is that your tablet will no longer boot due to mismatched /boot and /system partitions.
If the latter occurs then I recommend that you install a custom ROM. Let us know if it comes to that and someone will guide you.
Don't forget to backup what you have on the tablet before you do anything.
Thanks finniest, I have performed…Fastboot flash boot boot_signed.img
And solved temporarily. Got wifi not to say error. Allows me to turn on, but then immediately shuts off and display error again.
On another note, i also relocked bootloader. Run RUU, but error 155, means I can't restock.
Currently has TWRP, root, SU, all OK. Able to change custom rom anytime. But wifi error. CWrecovery flashed doomlord's wifi fix but not working.
The wifi.img hasn't been tried yet. feels strange to flash wifi.img going into the boot partition. Am I just being paranoia?
Sent from my GT-P1000 using xda app-developers app
cx5 said:
The wifi.img hasn't been tried yet. feels strange to flash wifi.img going into the boot partition. Am I just being paranoia?
Click to expand...
Click to collapse
I would give it a try. Beyond wasting five minutes of your time I don't see a downside. You can always flash another /boot image if it doesn't work.
It is good to know that you are familiar with unlocking bootloaders and have a custom recovery. That gives us a lot more options to solve this.
As far as I know the wifi module paired with the kernel by DooMLoRD is incompatible with all other kernels. So if you aren't using that kernel then you will have to use whatever bcm4329.ko file is included with the ROM that you are using. It is easy to forget that his custom wifi module is still in your /system/lib/modules directory when you flash a new kernel.
I suggest trying El-Diablo ROM and the boot.img that comes with it. This is a known working kernel and ROM pair. If you install them then first make certain to format /boot, /system and /data in whatever ways TWRP allows you to.
You should also consider that there might be something wrong with your wifi hardware. This is most likely if you have gotten your tablet wet and/or dropped it.
Hi finniest, you're right about not loosing too much time, I will give it a try now, and if it doesn't work, god bless it's OK I will read up more here, do more homework, then ask again, hahahah. Thanks !!!!!!!
finniest said:
I would give it a try. Beyond wasting five minutes of your time I don't see a downside. You can always flash another /boot image if it doesn't work.
Click to expand...
Click to collapse
Done, but not because I dare the above.
After realizing kernel + wifi (must be paired), knowing I am no OSIMOND's lightest rom, then I went back to CAREFULLY read his instructions specifically asking for doomlord's kernel v1 then flash the wifi correction ZIP via CWM. Hence I FASTBOOT FLASH BOOT kernelname.img then CWM recovery flash doomlord's wifi ZIP correction, then done. All my own fault for not reading carefully. Thanks still finniest and so many others who replied to various thread.
Where to read step by step?
cx5 said:
Hi finniest, you're right about not loosing too much time, I will give it a try now, and if it doesn't work, god bless it's OK I will read up more here, do more homework, then ask again, hahahah. Thanks !!!!!!!
Done, but not because I dare the above.
After realizing kernel + wifi (must be paired), knowing I am no OSIMOND's lightest rom, then I went back to CAREFULLY read his instructions specifically asking for doomlord's kernel v1 then flash the wifi correction ZIP via CWM. Hence I FASTBOOT FLASH BOOT kernelname.img then CWM recovery flash doomlord's wifi ZIP correction, then done. All my own fault for not reading carefully. Thanks still finniest and so many others who replied to various thread.
Click to expand...
Click to collapse
---
Kernel (ZIP) or Kernel as an Kernel Folder (organized like Linux kernel release 2.6.xx). I do not know how to use this last one
BTW, I am stuck whit my WiFi since a few weeks... Accidentally I wiped the System(Original) and other stuff, and happily installed the Diablo Version make my Jetstream to come alive. but never never can make the wifi work again.
I read a lot of Android and lear a bit about it, but I can't find the way to make WiFi works again. So Please... A jetstream whitout WiFi is like a die tablet... I need some help.
I need those links where they say how to, and the link to dowload IMG or ZIP. or a page teaching step by step how to install this Kernel (Organized like folders in a Linux like). thank in advance.
try downloading this:
https://dl.dropboxusercontent.com/u/5952907/Stock_wifi_modules.zip
and flash it thru the recovery
It said FAIL...
guru_shastri said:
try downloading this:
https://dl.dropboxusercontent.com/u/5952907/Stock_wifi_modules.zip
and flash it thru the recovery
Click to expand...
Click to collapse
Thanks for Helping.
I reboot into recovery using TWRP and tried to install it from Install Options. it said [FAIL]
Surely I'm just learnig about Android, I should use a commad from bootloader like this?
<fastboot flash recovery Stock_wifi_modules.zip> or
<fastboot flash boot Stock_wifi_modules.zip>
or something like this?
or perhaps use another tool instead TWRP...
flashing thru recovery should have worked. maybe the file is corrupted, I can't really tell
I downloaded and visually inspected the contents of the archive that @guru_shastri provided and everything looks okay. If you want to revert to revert to the stock WiFi module then this appears to be what you need.
Be aware that I have frequently witnessed instances where transfers to internal_sdcard via USB mount caused the file(s) to be corrupted. You should verify that a transfer worked by using MD5, cmp or (at least) a visual inspection.
WiFI OK!, SIM, not!
finniest said:
When using fastboot flash you have to specify a partition to flash, so that command will not work. The correct command is:
Code:
fastboot flash boot wifi_htc_bcmMFG248_ag_tx_rx_swap.img
I am not guaranteeing that it will solve your problem, only that it will actually flash your boot partition. The best outcome is that it fixes your problem. The worst outcome is that your tablet will no longer boot due to mismatched /boot and /system partitions.
If the latter occurs then I recommend that you install a custom ROM. Let us know if it comes to that and someone will guide you.
Don't forget to backup what you have on the tablet before you do anything.
Click to expand...
Click to collapse
Finally.. WiFI Works!... but not exactly with described... I had to read pretty much about all the things that concerns to adb/bootloader/flashing/installig>img>zip/ partition of each thing and so on before being succesfull with WiFi...
Not totally Sure, but the process that worked was:
WIPE all but recovery (using TWRP toosl)...
INSTALL el Diablo (zip) ROM Posted into the forums...(do not reboot)
INSTALL Stock_wifi_modules.zip
reboot into system...
Using USB debbuging reboot into bootloader.
Flash boot_signed.img >[fastboot flash root boot_signed.img]
(in this point the prompt said <waiting for device>, so I reboot into bootloader using Volume and Power buttons...)
Once flashed, reboot...
Now WiFi is working. Happily!
----
BTW... My SIM is not reconigzed (why???)... I saw it working the first time I istalled "El Diablo", but now... nothing happens.
I mean, the Sim Card appear to be reconigzed bye the system, but I don't get signal from the Phone Network (Like if it was from an unreconized carrier.. and my phone is Unlocked). I tried the sim in other phones and works well. What Can I Do at this point?
----- Soon I gonna move to another country, where I gonna use another SIM, with another carrier... --- Will the SIM work??
Adolyep said:
My SIM is not reconigzed (why???)... I saw it working the first time I istalled "El Diablo", but now... nothing happens.
Click to expand...
Click to collapse
Are you sure that you are carrier unlocked and not just bootloader unlocked? The former involves submitting your IMEI and paying a small sum of money, so it is usually easy to remember. They are completely different animals.
Make sure that you have checked Wireless & networks-->Mobile network [x]. If it is enabled then check Mobile networks for information. The SIM Toolkit app can also be a source of information.
Strangely, the lock screen is a source of information for your SIM card, so make sure you have it enabled. It is the only gateway (that I am aware of) to submitting your unlock code.
Adolyep said:
Soon I gonna move to another country, where I gonna use another SIM, with another carrier... --- Will the SIM work??
Click to expand...
Click to collapse
If your Jetstream is carrier unlocked then probably. The answer is probably because the Jetstream radio does not support every provider available.
Silly me! I did not realize look at this!
finniest said:
Are you sure that you are carrier unlocked and not just bootloader unlocked? The former involves submitting your IMEI and paying a small sum of money, so it is usually easy to remember. They are completely different animals.
Make sure that you have checked Wireless & networks-->Mobile network [x]. If it is enabled then check Mobile networks for information. The SIM Toolkit app can also be a source of information.
Strangely, the lock screen is a source of information for your SIM card, so make sure you have it enabled. It is the only gateway (that I am aware of) to submitting your unlock code.
If your Jetstream is carrier unlocked then probably. The answer is probably because the Jetstream radio does not support every provider available.
Click to expand...
Click to collapse
I just read your answer y I realized that I should carried out this simple step. look for networks in the area. This command "activate" the SIM to perform usual commands like Call or sending codes with * or # and numbers.
At this point my Jetstream is pretty much like it eas before wiping the system. but I can not fix the issue: <<Connection Problem or Invalid MMI Code>> every time that I send an command code (*111#) that is the network commad to access a few services. To perform those commads I have to take the SIM CARD and install it in another phone, Perform the network command, and return the SIM to my JETSTREAM. it is annoying. (but works)
Why in this world the network commands can not be performed by the Jetstream! (any advice?)
Adolyep said:
I just read your answer y I realized that I should carried out this simple step. look for networks in the area. This command "activate" the SIM to perform usual commands like Call or sending codes with * or # and numbers.
At this point my Jetstream is pretty much like it eas before wiping the system. but I can not fix the issue: <<Connection Problem or Invalid MMI Code>> every time that I send an command code (*111#) that is the network commad to access a few services. To perform those commads I have to take the SIM CARD and install it in another phone, Perform the network command, and return the SIM to my JETSTREAM. it is annoying. (but works)
Why in this world the network commands can not be performed by the Jetstream! (any advice?)
Click to expand...
Click to collapse
You will need to enable the MMI Code setting in the build.prop using root explorer. Without that MMI Codes do not work.
Here are instructions on how to unlock and root your htc desire 610. These work for both models, but the files are for the AT&T version.
BEFORE WE BEGIN, SOME TERMINOLOGY:
Unlocked Bootloader: HTCDev website will help us do this. It's free. It allows you to flash a recovery and signed boot image, which we have. It does not allow you to flash unsigned images.
S-On: Security on. This is how our phones come stock. Htc will not allow us to flash unsigned images because of this.
S-off: once someone achieves this for us, it will allow us to modify anything and everything, signed or not. We can flash new boot image and radios without worry of version number or signature.
Root: Allows you "administrative access" to your device, to move files and do certain things. However, our phone also has...
System Write Protection: HTC included this in the kernel, and it basically means that unless you have a kernel or boot image that gets around it, any changes you make to the system partition (aside from flashing in recovery) won't stick through a reboot. Essentially they will be temporary in an effort to preserve the phone. We don't like this.
Now then, with that out of the way...
1) HTCDev Bootloader Unlock: Under "Select Your Device", scroll ALL THE WAY TO THE BOTTOM, and choose "All Other Supported Models". I know it works, because I just did it. IT WILL WIPE YOUR DEVICE DATA. If you want the data backed up beforehand, turn on USB Debugging and use this command through adb to make a backup:
Code:
adb backup -apk -shared -all -f C:\desirebackup.ab
2)Download ClearD's Root Tool V3(USE VERSION 2.1 BELOW, VERSION 3 DOESN'T WORK FOR MOST PEOPLE): After you have drivers installed for your desire (install htc sync, plug in your phone, then let them load, then uninstall htc sync), fastboot turned off in the battery options in settings, and USB debugging turned on through the hidden developers menu, read the disclaimer in red below, and download and run this exe on your Windows machine with your phone plugged in. It'll install twrp recovery 2.8.0.1, install the engineering boot image, install SuperSU and root, and then install jmz's system-unlocked kernel to make root work like it should. I'm still working out kinks, so if it doesn't work right the first time, run it a second time! Thanks go to jmz, deez_troy, AdriVelazquez, and chainfire for the pieces to make this work.
DISCLAIMER: ONCE YOU USE THIS TOOL, YOUR DEVICE WILL HAVE THE ROOTED ENGINEERING BOOT IMAGE, WHICH CANNOT BE REVERSED. THERE ARE NO SIDE EFFECTS TO THIS IMAGE EXCEPT THAT IT SHOWS A DISCLAIMER ON YOUR SPLASH SCREEN WHEN YOU BOOT THE PHONE. THIS CANNOT BE CHANGED UNTIL WE GAIN S-OFF, WHICH HAS BEEN ACCOMPLISHED, BUT IS NOT YET PUBLICLY AVAILABLE. IF YOU ARE OK WITH THIS, PROCEED.
IF V3 DOESN'T WORK, HERE IS VERSION 2.1: Download ClearD's Root Tool V2.1. THIS VERSION INSTALLS ENGINEERING BOOT IMAGE AND JMZ KERNEL.
Return to Stock (AT&T ONLY) :http://dl3.htc.com/application/RUU_...16_10.20.4187.00L_release_392486_signed_2.exe
This ruu will bring you back to complete stock, version 1.50.502.7. It has to be run through Windows, and you have to have a locked bootloader to run it. If you're unlocked, you can relock it in fastboot with the command:
Code:
fastboot oem lock
. Feel free to unlock it again after updating through the RUU. You can use your original unlock token or get it again through htcdev.
Older root tool version 1:
Download ClearD's Desire 610 Root Tool V1. This version does not contain the engineering boot image, and needs it to work fully, thus is buggy and probably won't root you with one click. It will fail to adb remount, which will fail to auto install the zip files in recovery. If you've already flashed the engineering boot image, then it will work properly without issue. Otherwise, it'll place the root zip files on your phone, but you'll have to flash them manually in recovery.
Click to expand...
Click to collapse
Old manual method:
2) Recovery: After you're unlocked, download TWRP recovery from this thread, rename the image file to "recovery.img", and flash through fastboot with the command:
Code:
fastboot flash recovery recovery.img
This will give you the official Team Win Recovery Project recovery for our device, which will allow you to root.
3) Insecure Boot Image and Root: Once you have recovery installed, the rest is easy. In recovery, if you try to reboot back into the rom, it will ask you if you wish to root. Select yes. It will do the rest I believe, and install SuperSU when you boot back into the rom. You'll also want to download and flash JMZ's insecure kernel, which unlocks the system file lock that htc places on their newer devices. Once flashed, you can then change system files and the changes will stick through reboots.
Click to expand...
Click to collapse
HTC Engineering Boot Image:
Once unlocked, download the root zip provided in this thread, then open it. We can't just flash the zip file because most of us have an updated rom version than the one it was intended for, and I'm not sure how to fix that. But no bother. Pull out the boot image file, and place it somewhere you can find it. I put it right in my MiniADB/Fastboot folder for easy access. Then, you need to flash it. Here's how:
Code:
fastboot flash boot boot_root.img
You'll then have an insecure boot image, and it will say so on your splash screen. Trust me, the words are pretty ominous.
To restore your backup you made before unlocking, use this in adb:
Code:
adb restore C:\desirebackup.ab
Click to expand...
Click to collapse
A few superstars are currently working on s-off, and this will be updated once that occurs.
Special thanks to:
-JMZ (Recovery and Kernel)
-Deez_Troy (officiating recovery)
-AdriVelazquez (Insecure boot image)
-Chainfire (SuperSu)
Also, to save this spot and before I forget it going to sleep tonight, I'm actually not sure if firewater or sunshine will work or not yet because I haven't gotten app root yet for them to function. I'll have to get that, then we'll try one or the other of those. /end thought
Edit: I do believe we will need the wp_mod to disable system write protection and allow su to stick before we continue. That'll allow us full root. Or, we could continue with a twrp build or a Clockworkmod build if someone can assist.
ClearD said:
Edit: I do believe we will need the wp_mod to disable system write protection and allow su to stick before we continue. That'll allow us full root. Or, we could continue with a twrp build or a Clockworkmod build if someone can assist.
Click to expand...
Click to collapse
I could help with that, but you will have to build, I currently don't have a cyanogenmod source around. I need outputs of:
cat /proc/emmc
mount
cat /system/build.prop #<-- root maybe required
and I need your stock recovery.img, try getting it from an ota, or using dd.
The kernel source for this phone is released, you don't need to use the wp_mod.
It is? Where did you find it released? And how would we go about getting system writable without wp_mod? I'm still trying to work out all the kinks and have never built from source.
The outputs you need should be in my dev info thread except for the build prop, but I can remount and pull that.
ClearD said:
It is? Where did you find it released? And how would we go about getting system writable without wp_mod? I'm still trying to work out all the kinks and have never built from source.
The outputs you need should be in my dev info thread except for the build prop, but I can remount and pull that.
Click to expand...
Click to collapse
? never built from source? You are RD!
http://www.htcdev.com/devcenter/downloads Filter device desire 610.
About the system write protection: https://github.com/dummie999/android_kernel_htc_z4u/commit/19626f6c38b56b715dcc0b005ec8b82ce8ca264a
Should work
Well, build.prop then,
Edit: I need your stock recovery. You can get this with:
Code:
dd if=/dev/block/mmcblk0p41 of=/path/to/file/recovery.img
But you'll need busybox installed.
Edit2: You play subwaysurf! :highfive:
dummie999 said:
? never built from source? You are RD!
http://www.htcdev.com/devcenter/downloads Filter device desire 610.
About the system write protection: https://github.com/dummie999/android_kernel_htc_z4u/commit/19626f6c38b56b715dcc0b005ec8b82ce8ca264a
Should work
Well, build.prop then,
Edit: I need your stock recovery. You can get this with:
Code:
dd if=/dev/block/mmcblk0p41 of=/path/to/file/recovery.img
But you'll need busybox installed.
Edit2: You play subwaysurf! :highfive:
Click to expand...
Click to collapse
I'll add this hear also since I was adding it to the rooted forum. But dummie999 is right.
AdriVelazquez said:
That logic is sound; however slight differences in the model maybe.
Currently in the M8 this file is located in block/blk-core.c, which has the following.
Code:
#ifdef CONFIG_MMC_MUST_PREVENT_WP_VIOLATION
sprintf(wp_ptn, "mmcblk0p%d", get_partition_num_by_name("system"));
if (!strcmp(bdevname(bio->bi_bdev, b), wp_ptn) && !board_mfg_mode() &&
(get_tamper_sf() == 1) && (bio->bi_rw & WRITE)) {
pr_info("blk-core: Attempt to write protected partition %s block %Lu \n",
bdevname(bio->bi_bdev, b), (unsigned long long)bio->bi_sector);
err = 0;
goto wp_end_io;
} else if (atomic_read(&emmc_reboot) && (bio->bi_rw & WRITE)) {
pr_info("%s: Attempt to write eMMC, %s block %Lu \n", current->comm,
bdevname(bio->bi_bdev, b), (unsigned long long)bio->bi_sector);
err = -EROFS;
goto wp_end_io;
}
#endif
That line of code will need to be intercepted at boot to allow permanent root.
I haven't checked recently, but is the source for desire 610 posted?
Click to expand...
Click to collapse
Also, you'll need to build from source for this.
Also, you can just create modules to intercept the data on boot, which would be easier.
AdriVelazquez said:
Also, you can just create modules to intercept the data on boot, which would be easier.
Click to expand...
Click to collapse
Lol, no I couldn't get that working , compiling from source was a lot easier, at least for my d500
Edit:
My company has actually done a lot of work with the desire 610 and HTC, unfortunately some proprietary. But other's aren't.
Click to expand...
Click to collapse
Just curious, where do you work?
I usually build from pre built stock, then change what I want through decompiling and recompiling, also do gui things and script things and theme things. This is new territory, but nothing I'm not uncomfortable doing by any means. I'll work on it tonight.
Also, those outputs were not from my device, but from an unlocked and s-off device of a friend lol. I noticed that also, but was too lazy to remove it.
ClearD said:
I usually build from pre built stock, then change what I want through decompiling and recompiling, also do gui things and script things and theme things. This is new territory, but nothing I'm not uncomfortable doing by any means. I'll work on it tonight.
Click to expand...
Click to collapse
Well, then I hope you have a linux pc/laptop somewhere around
Good luck!
dummie999 said:
Well, then I hope you have a linux pc/laptop somewhere around
Good luck!
Click to expand...
Click to collapse
One of each. we'll see what happens lol.
dummie999 said:
Lol, no I couldn't get that working , compiling from source was a lot easier, at least for my d500
Edit:
Just curious, where do you work?
Click to expand...
Click to collapse
Yonder Music. It's a new music streaming app.
ClearD said:
One of each. we'll see what happens lol.
Click to expand...
Click to collapse
http://xda-university.com/as-a-developer/getting-started-building-a-kernel-from-source before I forget. There is also a readme included with your download.
AdriVelazquez said:
Yonder Music. It's a new music streaming app.
Click to expand...
Click to collapse
Why do you make your devices S-off? (the thread in general)
dummie999 said:
http://xda-university.com/as-a-developer/getting-started-building-a-kernel-from-source before I forget. There is also a readme included with your download.
Why do you make your devices S-off? (the thread in general)
Click to expand...
Click to collapse
Instead of you paying a subscription fee every month, Yonder Music sells the app bundled with the phone which you have free streaming music for the lifetime of the device.
S-off let's us do all of that.
The only source code currently offered by HTC is:
Device Carrier Region Type Kernel Android Size Description
Desire 610
Vodafone
UK
CRC
3.4.0
v4.4.2 152 MB
1.29.161.2
Desire 610
Vodafone
CH GER
CRC
3.4.0
v4.4.2 155 MB
1.29.166.2
Any idea if either of those would work? :/
ClearD said:
The only source code currently offered by HTC is:
Device Carrier Region Type Kernel Android Size Description
Desire 610
Vodafone
UK
CRC
3.4.0
v4.4.2 152 MB
1.29.161.2
Desire 610
Vodafone
CH GER
CRC
3.4.0
v4.4.2 155 MB
1.29.166.2
Any idea if either of those would work? :/
Click to expand...
Click to collapse
They usually work, you just have to be sure that your software version (1.29.sth) matches. For example, if you are on 1.29.401.3, it should work. I'm not sure, but I think this usually is only a problem on high end smartphones (one m7&m8), because the carriers there modify the kernels of those devices.
Mine (and I assume others) are on 1.30.x.x
ClearD said:
Mine (and I assume others) are on 1.30.x.x
Click to expand...
Click to collapse
Try it anyway, it might work. For example:
On my phone, the kernel for 1.20 runs fine on 1.13 1.10 1.16, but it doesn't run on 1.26 1.32 1.34. You can't know if it works before you try it.
Root achieved thanks to jmz (confirmed on my unit after his) , s-off is being worked on (by pros, not by me). Jmz built us a twrp recovery that allows for an easy root. Hopefully it'll be released to the masses soon!
first post
Does this image works with At&t devices because I am running firmware 1.19.502.4 not sure if it would stop me from booting...I have attained root by using TWRP however nothing sticks whenever i restart my phone so I was hoping this would be a solution
Shattariff said:
Does this image works with At&t devices because I am running firmware 1.19.502.4 not sure if it would stop me from booting...I have attained root by using TWRP however nothing sticks whenever i restart my phone so I was hoping this would be a solution
Click to expand...
Click to collapse
Nope that wont fix it. I am working on a kernel that will solve that problem
Hey guys, Kyuubi10 here again.
Recently I had an issue with my nexus 9, which is becoming increasingly common.
Where one can permanently soft-brick their nexus, for lack of ticking the "Enable OEM unlock" button, then bootlooping their device while locking their bootloader, thus making it impossible to reflash a system image through fastboot.
If you're lucky enough to still be able to access your custom recovery your device is still salvageable, but if as me you were performing a factory reimage when you locked your bootloader chances are that you have gone back to stock recovery, and only after realised that your OS was bootlooping.
From reading about it, I found out that it was virtually unrecoverable, unless you managed to keep your custom recovery, by either flashing a new system or if your recovery refuses to flash new system you can use this: http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539.
But in all of these cases you still need a custom recovery.
At the end most people gave up and either bought another device or used their warranty to replace their device (Which I am trying to attempt, if my warranty isn't completely voided.)
So, finally reaching the important point of this thread, I have had a couple ideas which could work to solve this issue but since I don't have enough knowledge I am unable to actually test the idea.
For the device to recognize the lock status of the device even without an OS present means that there must be a flag the bootloader reads. By reading further I found this. http://newandroidbook.com/Articles/Nexus9.html
This basecally explains that Nexus 9 has a partition called PST (Persist) whose only job is to provide the value of this flag. I was wondering whether it is possible by using Linux could get a more direct access to the partition and change its binary value to enable the "enable OEM unlock" variable (Described by fastboot as "Ability is 0").
I had this idea because one day when I bootlooped another device and ADB on windows failed to recognize the device I booted linux and used ADB from there. And the phone was reconized.
This works because Linux can view partitions with different filesystems, where as windowns can only see partitions which have been formatted into "Windows" partitions (e.g. FAT32, NTFS).
So in theory using a Linux OS to access the different partitions in Android should show up much more information, and give you better access. But apart from this I don't know much more. I will be testing this theory out in more detail. But I am challenging the more experienced contributors out there to help out in overcoming this issue!
Please, this is a real issue which is limiting newer nexus devices. If anyone has any new ideas please share by commenting, and lets help each other out to find a solution to this problem.
..
cam30era said:
@Kyuubi10
Have you seen this thread > http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
Click to expand...
Click to collapse
Yes, in fact I have the same exact link in the OP.
But unfortunately as I have described my case is quite unique in which I don't have a custom recovery. This in turn means I have no access to ADB because no partitions are mounted.... I'm stuck with using fastboot for now.
Kyuubi10 said:
Yes, in fact I have the same exact link in the OP.
But unfortunately as I have described my case is quite unique in which I don't have a custom recovery. This in turn means I have no access to ADB because no partitions are mounted.... I'm stuck with using fastboot for now.
Click to expand...
Click to collapse
The March 25, 2016 Android N Beta should be able to save you: https://developer.android.com/preview/download-ota.html
It can be pushed via adb to a stock Nexus 9 even with a locked bootloader.
Halleyscomet said:
The March 25, 2016 Android N Beta should be able to save you: https://developer.android.com/preview/download-ota.html
It can be pushed via adb to a stock Nexus 9 even with a locked bootloader.
Click to expand...
Click to collapse
@Halleyscomet is very right, the N preview saved me from this problem, allowing me to enable OEM unlock and then go back to stock marshmallow.
Halleyscomet said:
The March 25, 2016 Android N Beta should be able to save you: https://developer.android.com/preview/download-ota.html
It can be pushed via adb to a stock Nexus 9 even with a locked bootloader.
Click to expand...
Click to collapse
defmetal96 said:
@Halleyscomet is very right, the N preview saved me from this problem, allowing me to enable OEM unlock and then go back to stock marshmallow.
Click to expand...
Click to collapse
Thank you guys for your reply!!
Unfortunately as described in my signature my N9 was stolen.
But I'll change the title of this thread to [SOLVED] so that others know where to find an answer.
Halleyscomet said:
The March 25, 2016 Android N Beta should be able to save you: https://developer.android.com/preview/download-ota.html
It can be pushed via adb to a stock Nexus 9 even with a locked bootloader.
Click to expand...
Click to collapse
Seriously, you are a lifesaver.
The simple fact that you can sideoad the preview and that it flashes system unconditionally saved my Nexus 9.
This infomation should be stickied because it is the only solution if you are stuck in between versions. I was on LMY48T and adb sideload of the correspondig OTA showed "unexpected content" (Error 7).
This allowed me to boot, and unlock OEM & bootloader.
Huge thanks!
angerized said:
Seriously, you are a lifesaver.
The simple fact that you can sideoad the preview and that it flashes system unconditionally saved my Nexus 9.
This infomation should be stickied because it is the only solution if you are stuck in between versions. I was on LMY48T and adb sideload of the correspondig OTA showed "unexpected content" (Error 7).
This allowed me to boot, and unlock OEM & bootloader.
Huge thanks!
Click to expand...
Click to collapse
For that a Moderator needs to be made aware ) Let's try do that!
angerized said:
Seriously, you are a lifesaver.
The simple fact that you can sideoad the preview and that it flashes system unconditionally saved my Nexus 9.
This infomation should be stickied because it is the only solution if you are stuck in between versions. I was on LMY48T and adb sideload of the correspondig OTA showed "unexpected content" (Error 7).
This allowed me to boot, and unlock OEM & bootloader.
Huge thanks!
Click to expand...
Click to collapse
Any chance you still have this file? Doesn't seem to exist on the internet anymore.Having same issue.
joeish said:
Any chance you still have this file? Doesn't seem to exist on the internet anymore.Having same issue.
Click to expand...
Click to collapse
Hello,
I don't have this specific file anymore, but I think you can sideload the latest OTA from here:
Images OTA complètes pour les appareils Nexus et Pixel | Google Play services | Google for Developers
developers.google.com
This is just a mirror to my original thread on superSU
Make sure you have adb installed either via the sdk or adb minimal
Here is a guide for anyone running android wear 6.0.1 on rooting
(from PC)
1.Unlock the bootloader if not already unlocked
(Make sure to boot to system and set up device after unlocking bootloader otherwise broken kernel! )
Code:
adb reboot bootloader
fastboot oem unlock
2.flash THIS TWRP onto the watch MAKE SURE TO USE THIS ONE!(current official cannot mount squashfs system)
Code:
fastboot flash recovery recoveryname.img
3.Download special SuperSU here with busybox YDS included HERE and move it to watch with adb push to /sdcard while TWRP is booted and then install as normal zip
Code:
adb push nameofzip.zip /sdcard/
4.Boot watch to system (ignore TWRP message of no OS installed) Now your root apps from 5.1 should work perfect
REMEMBER squashfs is read only even with root so don't bother trying to modify system files like the build.prop
If you would like to change pixel density perform this command in either adb shell or a terminal emulator:
Code:
wm density <dpi>
Please leave thanks if it helped!
New Update!
updated to superSU 2.79
reverted to previous busybox due to incompatibility
Xmaster24 said:
Feel free to submit links to twrp for squashfs watch with model name, codename and original developer's name
Will add them to this post
I DID NOT CREATE ANY OF THESE BUILDS!
LG G Watch dory(courtesy of @rbox): http://www.mediafire.com/download/apwtscp0tn0y8qd/twrp-3.0.0-0-dory+squashfs.img
Click to expand...
Click to collapse
I read in your other thread that you have your own version of TWRP? The 3.0.0.0 version I got from twrp.me doesn't seem to flash your supersu zip properly. Or at least I don't have a busybox app installed on my watch after flashing the zip.
b1g.p0ppa said:
I read in your other thread that you have your own version of TWRP? The 3.0.0.0 version I got from twrp.me doesn't seem to flash your supersu zip properly. Or at least I don't have a busybox app installed on my watch after flashing the zip.
Click to expand...
Click to collapse
yes see step 2 download the one from post below ie. the one you quoted. The one from twrp.me is outdated and cannot mount the system as it is squashfs. the one in that post can
oh sorry! the way it was situated in your post made me think it was a signature, so I didn't even read it. Thanks!
b1g.p0ppa said:
oh sorry! the way it was situated in your post made me think it was a signature, so I didn't even read it. Thanks!
Click to expand...
Click to collapse
Yes thanks for pointing that out, I have made it more obvious now.
Non-relatedid you notice xda updated this evening? notifications are broken now have to check things manually
I followed the instructions to a T and when I went to reboot in TWRP I have no OS installed what the **** happend?
EDIT: I saved myself when because I used the rootjunky tool to restore 5.1.1 then flahsed twrp on that and then flashed the update 6.0.1 zip from another thread on here. Hopefully I can figure this out. I'm good with android phone... first time messing with android wear.
EDIT: Second time is the charm I guess. Thanks for nobody screaming at me and calling me a nub!
codyedmonson said:
I followed the instructions to a T and when I went to reboot in TWRP I have no OS installed what the **** happend?
EDIT: I saved myself when because I used the rootjunky tool to restore 5.1.1 then flahsed twrp on that and then flashed the update 6.0.1 zip from another thread on here. Hopefully I can figure this out. I'm good with android phone... first time messing with android wear.
EDIT: Second time is the charm I guess. Thanks for nobody screaming at me and calling me a nub!
Click to expand...
Click to collapse
Um probably should have told people but TWRP would say that but you should just ignore it cause your system is there
Xmaster24 said:
Um probably should have told people but TWRP would say that but you should just ignore it cause your system is there
Click to expand...
Click to collapse
Yeahhh I figured that out after a while. My knowledge with rooting android wear is very limited at the moment. I've read as much as I could in one night lol. After figuring everything out with twrp/rooting I know have root and everything is going smoothly. Thanks for the tut!
okay, i used ur tutorial... fastboot flashed the twrp and pushed the supersu via adb to the sd... installed the zip via twrp... on leaving twrp it says "no os installed"... when i try to reboot the system it always just boots straight into twrp
/edit
okay! please add to your tutorial that you have to reboot and pair your watch first, after unlocking the bootloader! thx
cYraXx said:
okay, i used ur tutorial... fastboot flashed the twrp and pushed the supersu via adb to the sd... installed the zip via twrp... on leaving twrp it says "no os installed"... when i try to reboot the system it always just boots straight into twrp
/edit
okay! please add to your tutorial that you have to reboot and pair your watch first, after unlocking the bootloader! thx
Click to expand...
Click to collapse
Thanks was not aware that was a requirement strange that that happens
his thread gets a tad confussing ..is there a clear guide on doing 6.0.1 ? please..
Eggman72 said:
his thread gets a tad confussing ..is there a clear guide on doing 6.0.1 ? please..
Click to expand...
Click to collapse
What's confusing you? It's almost the same as rooting a phone flash twrp install supersu zip
Posters saying this is missing etc...im unsure whether posted tools etc are all there...rooted plenty of phones etc..just never a smartwatch..dont want to end up with a nice paperweight (I know its always a risk) seems some people have had a couple of issues Os missing etc..
Eggman72 said:
Posters saying this is missing etc...im unsure whether posted tools etc are all there...rooted plenty of phones etc..just never a smartwatch..dont want to end up with a nice paperweight (I know its always a risk) seems some people have had a couple of issues Os missing etc..
Click to expand...
Click to collapse
OS missing is just fault of twrp not me besides it's meaningless error it simply cannot write to system so it assumes it those not exist. Everything you need is there apart from adb but just get adb minimal from XDA. With my method there is no risk of a paperweight it only touches recovery and kernel which both can be easily replaced. The only thing that can really kill a phone is a messed up bootloader update/mod. I have taken everything posters said into account and updated accordingly. Originally I just wrote what worked for me but now I updated it for universal use
Thanks for the reply & clarificartion.. you say 1.Unlock the bootloader if not already unlocked
(Make sure to set up device after unlocking bootloader otherwise no boot!) does that mean after unlock it will reboot into OS and you perform language setup & pairing ? or after its done the unlock it go's straight into os for setup ?
Eggman72 said:
Thanks for the reply & clarificartion.. you say 1.Unlock the bootloader if not already unlocked
(Make sure to set up device after unlocking bootloader otherwise no boot!) does that mean after unlock it will reboot into OS and you perform language setup & pairing ? or after its done the unlock it go's straight into os for setup ?
Click to expand...
Click to collapse
After unlocking go straight to OS and setup because rooting with an empty data partition breaks the kernel
Do you reboot or does just go straight in ?
Eggman72 said:
Do you reboot or does just go straight in ?
Click to expand...
Click to collapse
I'm not sure I think it does yes just try it if it thosen't its simple as clicking start on the watch bootloader screen
bootloader unlocked fine..twrp installed fine..pushed files install and i get this error..any clues guys ?busy box installs but no super user... help !!!
I'm trying to root a friend's Metro LG Aristo MS210 7.0, what method works for rooting this phone?
Msjoannalynn said:
I'm trying to root a friend's Metro LG Aristo MS210 7.0, what method works for rooting this phone?
Click to expand...
Click to collapse
https://androidforums.com/threads/recovery-twrp-v3-for-lg-aristo-metropc-t-mobile.1117942/
Messi got you covered.
Personally I would recommend against rooting right now. There isn't much to be done with the Aristo at this point in time except to make backups of your system. Most you'll end up doing is learning a few things about why mixing system based and systemless mods can lead to pretty unpredictable results.
ninjasinabag said:
There isn't much to be done with the Aristo at this point in time except to make backups of your system.
Click to expand...
Click to collapse
This is exactly what I've wanted to do - preferably by having direct rw access to the flash, like I did on my old phone. Unfortunately the only viable custom recovery procedure right now (messi2050's) involves wiping the userdata partition (unless you somehow happen to have an unlocked bootloader). To make matters worse the userdata partition is encrypted AFAIK. Surely the keys are stored on the phone somewhere but there wouldn't be a way to get them without some exploit, and I don't know if this phone is popular enough for someone to bother researching and publishing an exploit.
There was some progress here (github.com/Lekensteyn/lglaf) on reversing and exploiting LG's LAF protocol in their recovery OS, but it hasn't been updated for more than a year now. If anyone wants to play around with that code, be sure to read this issue (github.com/Lekensteyn/lglaf/issues/7) which has ongoing attempts at reversing LAF's current auth methods. I don't have the time right now to dive into this unfortunately.
messi2050 said:
https://androidforums.com/threads/recovery-twrp-v3-for-lg-aristo-metropc-t-mobile.1117942/
Click to expand...
Click to collapse
reboot into fastboot [ adb reboot bootloader ]
- fastboot oem unlock [ this is going to wipe your data ]
how do i do this any one got any video tutorial for all of this ?
@Messi help
1118niranjan said:
reboot into fastboot [ adb reboot bootloader ]
- fastboot oem unlock [ this is going to wipe your data ]
how do i do this any one got any video tutorial for all of this ?
@Messi help
Click to expand...
Click to collapse
You need to do some search yourself
messi2050 said:
You need to do some search yourself
Click to expand...
Click to collapse
i saw your post in android form they've said u are the best guy to help any link if u can ?
1118niranjan said:
i saw your post in android form they've said u are the best guy to help any link if u can ?
Click to expand...
Click to collapse
Power your phone off.
Hold VOL DOWN WHILE PLUGGING DEVICE INTO COMPUTER WITH USB - this will bring it to the fastboot screen. If you have all drivers installed then you can simply open a cmd window and type "fastboot oem unlock" - which should unlock the bootloader - if all drivers are installed. Then continue with the tutorial as usual.
Is root worth it
So, I have an LG ms210 (Lg Aristo) that I've own for a little over 3 months now, but i have been experiencing this issue since about 1 week into ownership. The phone seams to have a RAM leak or something similar as about every hour it slows down substantially, usually to the point of freezing, or crashing all together and restarting on its own, even if not being touched since I power it on. Ive been thinking about rooting it to debloat, but im not sure if it will help, or if i should just invest in a new handset. I have since factory reset it, deleting more high-resource apps, and leaving it bare-bones system apps and nothing else, but the problem still persists. The carrier i MetroPCS if thats a factor, but i dont see why it would be. Any thoughts?
Rooted mine! Thanks to the modified twrp. I couldn't get into it for alost a week, then had a system update that rebooted me right to it, still had the super su zip in sd card so i flashed it and the no verity zip THANKS OP!!??
captnbluebeard said:
Rooted mine! Thanks to the modified twrp. I couldn't get into it for alost a week, then had a system update that rebooted me right to it, still had the super su zip in sd card so i flashed it and the no verity zip THANKS OP!!
Click to expand...
Click to collapse
If you still have trouble reaching recovery after this, either download an advanced shutdown prompt from the market. (There's one literally called advanced reboot) or you can download a terminal emulator app and use the reboot recovery command with root.
su
reboot recovery
ninjasinabag said:
If you still have trouble reaching recovery after this, either download an advanced shutdown prompt from the market. (There's one literally called advanced reboot) or you can download a terminal emulator app and use the reboot recovery command with root.
su
reboot recovery
Click to expand...
Click to collapse
I did that already, im trying to get xposed up and running but my model #lvl3 doesnt match what is in the terminal in twrp. I still get a weird error ph4u
Most likely shows as the lg stylo 2 plus as I guess your using the lineage backup. So just use the model of the lg stylo 2 in terminal? Guessing as I don't use xposed. What do you use xposed for?
To get it running on the aristo is to either edit build prop values to match the ms210 model, or remove the device requirements from xposed's update binary.
failed remote cannot flash this partition in unlocked state.
Anyone?
can some walk me thru this idk what im doing wrong but i go into adb i reboot bootloader and when i try to fastboot oem unlock it says device not found what am i doing wrong?
question
does this root works for lg ms210 security patch level jan 1 2018?
I believe the root is just twrp so it should work fine. Just update first then follow the steps for flashing twrp and the most recent magisk and probably dm verity thing. If something fails it can be eaily reflashed with the original firmware with correct software and the firmware image/kdz.
Edit: try to reinstall the lg drivers? Also a try a tool called minimal adb and fastboot here
Help. It just staus on "" waiting for device " with oem unlock step
Before rooting your phone , it is necessary to backup data for your phone .