READ THE WHOLE THREAD BEFORE CONTINUING or FLASHING THE ZIP ! AS THIS ONLY WORKS DESCENT FOR G VERSION , I ONLY RECOMMEND TO DO SO ! USING IT ON A U-VERSION (B19/B25) MIGHT BRICK YOUR PHONE. ALSO TESTED & WORKING ON Project New World (Oreo) on G VERSION
I am not responsible for damaging/bricking your phone or other related stuff…DO MAKE A FULL BACKUP !
ONLY FOR A2017G & also on A2017G B32 Oreo PNW
DON'T USE ON B13 (MF5.0) BECAUSE IT DOES NOT WORK !!! Tested it myself.
Only to use whether flashed Universal B15 (or B32 on PNW) or Stock Bootloaders before.
Don't use on encrypted phones and remove security pattern before flash
Always backup your data. In case you have to format data you'll have a spare one to restore
EDIT : made a flashable zip : Remove Bootloader Unlock Warning on Axon 7G : https://androidfilehost.com/?fid=745849072291698596
As @Choose an username... asked to bring this to your attention again hereby a fairly easy and safe method to get rid of that annoying "unlocked bootloader" warning.
I did mentioned this before in the earlier days but perhaps its usefull to post it again. And if you're planning to stay a while on your rom this might help to have a clean boot.
I performed this steps often on my G and imo are safe to do.
So, take a look HERE
Prepare with necessary files (if you already haven't from before )
( Be on twrp 3.1.1.0 (3.2.1.0) )
Just perform steps 6 to 14 again (NOTE ! : If you get a permissions denied issue, try doing these steps while your device is in TWRP )
After that just type "fastboot reboot" and you should have a clean boot.
-------------------------------------------------
B) Unlock the bootloader
Q: Why do I need to unlock the bootloader?
A: With an unlocked bootloader, you can install custom ROMs.
1) Go to https://mega.nz/#F!rcFCQZ7C!vn457hU1zDwc0uVpvm5otw and download the aboot.img file from there (1024Kb). Put it in the same folder you used in the previous process
2) Download this file: https://www.androidfilehost.com/?fid=529152257862665656
3) Unzip the file and copy/cut the file called "fastboot_unlock.img"
4) Paste that file in the folder where "adb.exe", "axon7tool.exe", "recovery.img", "recovery.bin" and "aboot.img" are located
5) If there's none open, open a new command window in that folder again (Shift + right-click and "open command window here")
6) Type "adb push aboot.img /sdcard/" and hit enter
7) Type "adb push fastboot_unlock.img /sdcard/" and hit enter
8) Type "adb shell dd if=/dev/block/bootdevice/by-name/fbop of=/sdcard/fbop_lock.img" and hit enter
9) Type "adb shell dd if=/dev/block/bootdevice/by-name/aboot of=/sdcard/aboot_lock.img" and hit enter
10) Type "adb pull /sdcard/fbop_lock.img" and hit enter
11) Type "adb pull /sdcard/aboot_lock.img" and hit enter
12) Type "adb shell dd if=/sdcard/fastboot_unlock.img of=/dev/block/bootdevice/by-name/fbop" and hit enter
13) Type "adb shell dd if=/sdcard/aboot.img of=/dev/block/bootdevice/by-name/aboot" and hit enter
14) Type "Adb reboot bootloader" and hit enter to go to the bootloader
-------------------------------------------------
Thanks @Controllerboy
Can we not create flashable ZIPs for this to save Time? Something with AROMA to choose the Specific Device Files would be cool or nah? Let Me know if there is interest on this. I could help with the Scripts...
BR
Miustone said:
Can we not create flashable ZIPs for this to save Time? Something with AROMA to choose the Specific Device Files would be cool or nah? Let Me know if there is interest on this. I could help with the Scripts...
BR
Click to expand...
Click to collapse
Thnx for your reply.
But AFAIK this procedure might not work on the U version but not sure ( afaik no go on A2017). So therefore i just used the "known" familiar bootloader files.
But if it would work, so someone should test their specific files on U version, an AROMA zip would be interesting to make.
I can i you want but feel free to join in if A2017U and A2017 or good to go :good:
But then again we have to get some feedback on this.
raystef66 said:
Thnx for your reply.
But AFAIK this procedure might not work on the U version but not sure ( afaik no go on A2017). So therefore i just used the "known" familiar bootloader files.
But if it would work, so someone should test their specific files on U version, an AROMA zip would be interesting to make.
I can i you want but feel free to join in if A2017U and A2017 or good to go :good:
But then again we have to get some feedback on this.
Click to expand...
Click to collapse
First of all a happy new Year! :angel:
Think i will take a look on it in the next Days, would be cool if someone could test which Variants are supporting this. I see a flashable ZIP could be very useful for People who are switching the OS a lot of times (like i do). I own the G Version BTW.
BR
At the boot hold the Vol-Button and Power. And now you cant see the Bootloader-Message. Otherwise flash this zip: http://www120.zippyshare.com/v/xYBio6uW/file.html
I dont know if its work on the A2017U oder A2017 Devices. But it works definitely on the A2017G.
Miustone said:
First of all a happy new Year! :angel:
Think i will take a look on it in the next Days, would be cool if someone could test which Variants are supporting this. I see a flashable ZIP could be very useful for People who are switching the OS a lot of times (like i do). I own the G Version BTW.
BR
Click to expand...
Click to collapse
Happy new Year too and best wishes to all here on XDA !
Yeah such a zip for all variants should be handy. A A2017U user should test this method.
Anyway on G it works.
BaamAlex said:
At the boot hold the Vol-Button and Power. And now you cant see the Bootloader-Message. Otherwise flash this zip: http://www120.zippyshare.com/v/xYBio6uW/file.html
I dont know if its work on the A2017U oder A2017 Devices. But it works definitely on the A2017G.
Click to expand...
Click to collapse
This zip works on G version (not sure about other versions) but only when coming from Universal BL imo. When using the B13 bootstack f.e. like on Mifavor 5.0 this ZIP would not work imo. So be carefull flashing it. As said, when on Universal BL this should work.
Thanks !
BaamAlex said:
At the boot hold the Vol-Button and Power. And now you cant see the Bootloader-Message. Otherwise flash this zip: http://www120.zippyshare.com/v/xYBio6uW/file.html
I dont know if its work on the A2017U oder A2017 Devices. But it works definitely on the A2017G.
Click to expand...
Click to collapse
And if i have stock B08/B09 bootloader, not the universal BL?
I cant say that. It works under a2017g. But...you can test it. And say me if its work for the a2017u or a2017. But i cant guarantee for anything. Sry.
Okay then in another way: which bootloader was installed before you flashed your linked zip?
I messed up my phone completely one time with this "removal" from the first thread a few month ago.
So a wanna get sure this works with stock bootloader and not only the universal bootloader.
I also have the A2017G.
Spillunke said:
Okay then in another way: which bootloader was installed before you flashed your linked zip?
I messed up my phone completely one time with this "removal" from the first thread a few month ago.
So a wanna get sure this works with stock bootloader and not only the universal bootloader.
I also have the A2017G.
Click to expand...
Click to collapse
If you're not sure about the zip he provided, just don't use it
Do the above steps in 1st post and you'll be good to go. It takes only a minute or so, just copy paste in adb
Tip : just boot your phone in twrp before you do the steps. So you'll be sure about permissions
Spillunke said:
Okay then in another way: which bootloader was installed before you flashed your linked zip?
I messed up my phone completely one time with this "removal" from the first thread a few month ago.
So a wanna get sure this works with stock bootloader and not only the universal bootloader.
I also have the A2017G.
Click to expand...
Click to collapse
Better use @raystef66 method to remove the message.
Owning a A2017G isn't the only prerequisite to flash this file; like already said it depends on bootloader version, device encryption and probably much more ...
As you said, flashing this sort of stuff is too hasardous. Just take a look at the thread concerning this remover; lot of users "bricked" their devices with this stuff.
Pff
Spillunke said:
Hi all,
we need a person to test the tool, which removes the unlocked bootloader screen.
It do what it should do, but main problem is the question, if the adb.exe, which is included, is working in this case.
Axon 7 2017G on nougat with unlocked BL info-screen and a windows pc without ADB are the only requirements.
Download the file and give a feedback pls.
Click to expand...
Click to collapse
Why can't this be made via a flashable zip? It would be much easier to use and you wouldn't have to rely on Windows behaving.
The only thing needed would be to test if ro.product.model=ZTE A2017G, I don't know if you can read from build.prop with a flashable zip but if possible that would be the best approach. That would be to test if your phone is actually a G, minimize problems. Also, if you have the Universal Bootloader all this would do is restore fastboot; it wouldn't brick a G with univ bl (Someone made a flashable zip with an old aboot a while back actually. It was meant for getting fastboot back. I think it doesn't work though).
Choose an username... said:
Why can't this be made via a flashable zip? It would be much easier to use and you wouldn't have to rely on Windows behaving.
The only thing needed would be to test if ro.product.model=ZTE A2017G, I don't know if you can read from build.prop with a flashable zip but if possible that would be the best approach. That would be to test if your phone is actually a G, minimize problems. Also, if you have the Universal Bootloader all this would do is restore fastboot; it wouldn't brick a G with univ bl (Someone made a flashable zip with an old aboot a while back actually. It was meant for getting fastboot back. I think it doesn't work though).
Click to expand...
Click to collapse
It's indeed better to make an aroma zip for all devices. I'm actually looking into that right now. Hopefully with success. Come back to you when working on G in the first place.
A2017G & A2017U Remove Bootloader Unlock Warning
As the aboot and fastboot_unlock (from controllerboy thread) are the same in G & U (correct me if i'm wrong) this can be used on both models.
I've tested on my G and works flawless. Perhaps a U-user can test it out.
Remove Bootloader Unlock Warning on Axon 7G & U : https://androidfilehost.com/?fid=745849072291698596
it work but after reboot it dose not accept pattern password !
am2006 said:
it work but after reboot it dose not accept pattern password !
Click to expand...
Click to collapse
On my G it does. Pin, pattern.... No problem there.
Hmm, maybe coz am on LOS rom
am2006 said:
Hmm, maybe coz am on LOS rom
Click to expand...
Click to collapse
Don't think so because you used the universal B15 I suppose? Did those tests coming from that universal.
Can you not pattern afterwards?
Having a A2017U?
raystef66 said:
Don't think so because you used the universal B15 I suppose? Did those tests coming from that universal.
Can you not pattern afterwards?
Having a A2017U?
Click to expand...
Click to collapse
i use universal, my is A2017G, i do factory reset its work fine now
Related
Sorry about pulling the old post because of some problems.
Here is the latest update, I have modified the root.zip which may solve the flash_image problem.
Let's start!
What we need:
1. Nexus One with FRF72
2. The files I provide
3. Android SDK
4. Transcend Class 6 4gig(High recommend but not a must)
5. A brain!!!
Click to expand...
Click to collapse
YOU MUST FOLLOW ALL STEPS, OTHERWISE YOU LOSE!
Step 0:
- Install the SDK
- Make sure there is no "update.zip" in SD card
- Connect your phone with the USB
- Extract all files I provided to your <SDK>/tools
Step 1:
Enable Debugging in Setting->Development
Then, shut down your phone
Step 2:
Booting into bootloader by holding vol- and press Power
Use vol- button to highlight "Recovery"
Step 3:
Open CMD, and cd to the <SDK>/tools
Run "loop"
Step 4:
Press Power to enter Recovery now, you will see the triangle and <!>
Hold Power and vol+ to show the menu
Step 4a:
If your CMD shows you the devices is in recovery, press control + c to stop the "loop"
Step 4b:
If there is nothing, reboot your phone and repeat step 2-4 until it shows up.
(This is 99% caused by the sd card, faster card make it easier to show up)
Step 5:
Select "Apply update.zip", and it will show failed(IMPORTANT!!!!)
Step 6:
Run "adb push ota.zip /sdcard/update.zip"
Run "adb push busybox /sdcard/busybox"
Step 7:
Type but not run "adb push root.zip /sdcard/update.zip"
Step 8:
Select "Apply update.zip" again and run the step-7-code half a second later.
IF IT SHOWS ERROR STATUS 6, DOWNLOAD THE NEW ZIP I UPLOADED
Step 8a:
If it works, it will print ""Nexus One Rooting modified by Booker from Hong Kong"
Step 8b:
If it failed, repeat step 6-8
Step 9:
Finished the process, you can now immediately flash_image.
Step 10:
If you do flash a new recovery image, you may need to remove "/system/etc/install-recovery.sh" and "/system/recovery-from-boot.p"
This prevent the system automatically re-flash your recovery image to the stock one.
Click to expand...
Click to collapse
Have fun to flash great roms from devs.
Hope you can buy me some candies if you do like my work.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=3CDK8GTKMZGWJ
requirements. for this method
Hey..your post says you require frf72 for this to work
But that requires me to root my n1...(epe54b)...which means bootloader unlocking.
Will your method then remove the padlock?
There is not much reason to root the t-mo n1 since they can flash frf50 anyway (tethering included )
So based on the last statement, I'm assuming after doing this I'm not able to flash the stock updates without loosing my root? Just wanted to make sure I understood you correctly. Also the flash_image file. After it's uploaded to the phone I have to run this using a terminal or from a adb shell, correct?
actuallly you can get the official version, put it on your sd card and install it without being rooted. That is what they want you to do.
You see those of us who were rooted had to wait for a repacked version of the FRF72 update or we had to revert to stock with a stock recovery to get it to install. So sir, this is a valid method and you will keep your warranty intact!
O_O this is a really big deal NO?
anangphatak said:
Hey..your post says you require frf72 for this to work
But that requires me to root my n1...(epe54b)...which means bootloader unlocking.
Will your method then remove the padlock?
There is not much reason to root the t-mo n1 since they can flash frf50 anyway (tethering included )
Click to expand...
Click to collapse
you can flash the stock frf72 and don't need to root. just grab an official non-root build, place on sdcard and flash via any recovery u have installed
Looks interesting to say the least!
Just curious, why no frf83? Is it too new or just not possible?
madj42 said:
So based on the last statement, I'm assuming after doing this I'm not able to flash the stock updates without loosing my root? Just wanted to make sure I understood you correctly. Also the flash_image file. After it's uploaded to the phone I have to run this using a terminal or from a adb shell, correct?
Click to expand...
Click to collapse
No it will not remove the padlock. There is no way to relock the phone as of now.
I really wish this was a week ago..I had gotten a new phone, and decided not to wait to root it.
artcarney said:
Looks interesting to say the least!
Just curious, why no frf83? Is it too new or just not possible?
Click to expand...
Click to collapse
I was asking myself the same thing. The other thing is, wouldn't we have to flash a new radio too? Coming from 2.1 update1 this is a must afair.
jroid said:
you can flash the stock frf72 and don't need to root. just grab an official non-root build, place on sdcard and flash via any recovery u have installed
Click to expand...
Click to collapse
Really? I have been looking for this file for EPE54B for days!
all i have found was FRF50 from EPE27, FRF72 from FRF50, FRF83 from FRF50...
can you please advise us where we could find the one for EPE54B please?
Zapo said:
I was asking myself the same thing. The other thing is, wouldn't we have to flash a new radio too? Coming from 2.1 update1 this is a must afair.
Click to expand...
Click to collapse
i still haven't got a confirmation from anyone that updating radio requires unlocked bootloader....
but i understand everyone's concern as flashing radio is pretty much the only way to brick you phone therefore no one has the guts to be the 1st one flashing Froyo and the new radio with a rooted phone w/o an unlocked bootloader, right?
Rayman0625 said:
No it will not remove the padlock. There is no way to relock the phone as of now.
I really wish this was a week ago..I had gotten a new phone, and decided not to wait to root it.
Click to expand...
Click to collapse
Let me rephrase my statement above. I have not rooted my phone using the fastboot method. No padlock is shown on the boot screen. I'm asking if after doing this, am I stuck to using the modified builds (one's with root) or can I still use the official builds directly from Google? I'm assuming based on what has been said that if I use the official builds after using this process, that I'll loose the root access. Correct me if I'm wrong.
Thanks in advance. I apologize for being such a newb with all these questions.
kaiser_tytnii said:
can you please advise us where we could find the one for EPE54B please?
Click to expand...
Click to collapse
Have a look here brother: http://forum.xda-developers.com/showthread.php?t=654869
Second thread in this forum.
christiankk said:
Have a look here brother: http://forum.xda-developers.com/showthread.php?t=654869
Second thread in this forum.
Click to expand...
Click to collapse
my apologizes, i did not see any Froyo ROM there.
madj42 said:
Let me rephrase my statement above. I have not rooted my phone using the fastboot method. No padlock is shown on the boot screen. I'm asking if after doing this, am I stuck to using the modified builds (one's with root) or can I still use the official builds directly from Google? I'm assuming based on what has been said that if I use the official builds after using this process, that I'll loose the root access. Correct me if I'm wrong.
Thanks in advance. I apologize for being such a newb with all these questions.
Click to expand...
Click to collapse
if you stay with stock recovery and ROM, you will receive OTA from Google.
You can still flash Stock ROM with Custom Recovery but will not be able to install OTA from Google.
hope this help.
Booker-T said:
Sorry about pulling the old post because of some problems.
Here is the latest update, I have modified the root.zip which may solve the flash_image problem.
Let's start!
Have fun to flash great roms from devs.
Hope you can buy me some candies if you do like my work.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=3CDK8GTKMZGWJ
Click to expand...
Click to collapse
proud of you Konger!
Is there any way this can work on FRF83?
or
Is there a way to revert back to FRF72?
You can revert. Just need to grab the passimg.zip for the phone and flash from bootloader. Good job with tut a little clearer then mine. Didn't check files to see if the same but worked for me. Not reading the memory card was the obstacle which putting card in after detected in recovery was the only way I was able to get it to work.
M9x3mos said:
You can revert. Just need to grab the passimg.zip for the phone and flash from bootloader. Good job with tut a little clearer then mine. Didn't check files to see if the same but worked for me. Not reading the memory card was the obstacle which putting card in after detected in recovery was the only way I was able to get it to work.
Click to expand...
Click to collapse
Do you think you could give me a link to the passimg.zip that I can use without having to unlock the bootloader? I've been searching for hours.
PS: there is no busybox in the "Nexus_One_Full_Root.zip" from the original post.
Just a quick advice for everybody.... If someone (like me) is still stuck with the 2.1 Update 1, before update to 2.2 FRF52 test on your phone the point between 2 and 4.b. Once you will have your phone recognized by ADB then you can update to 2.2 FRF52.
For now my 4 microSD (1 * Class 6 Sandisk / 1 * Class 4 Kingston / 1 * Class 6 Transcend and 1 * Class 2 Samsung) doesn't work at all....
Hope this help
Hello! I've upgraded to 5.1 and have lost my root. I have tried using kingo and towelroot but neither have worked. I have tried downgrading to 4.3 re-rooting and then upgrading to 5.1 only to lose root again. Any help as to fix this would be awesome and highly appreciated!
Use TWRP
Milkteabubbles said:
Hello! I've upgraded to 5.1 and have lost my root. I have tried using kingo and towelroot but neither have worked. I have tried downgrading to 4.3 re-rooting and then upgrading to 5.1 only to lose root again. Any help as to fix this would be awesome and highly appreciated!
Click to expand...
Click to collapse
You can flash twrp to root, then install superusersu. There's a zip file that's been posted in the forums recently by ArkAngel 06 that has everything you should need and a step by step guide to do it. Hope this helps
This question has been asked and answered. Do you guys read the other threads at all?
To get root and TWRP.
Credit to Foltz61.
1. Boot to bootloader.
2. Fastboot boot TWRP-L.img
3. Install supersu-2.49.zip (even though I didn't lose root)
4. Reboot back to system.
5. Reboot back to bootloader.
6. fastboot flash recovery TWRP-L.img.
7. fastboot reboot.
8. Boot to recovery and had TWRP
Thanks
Thank you both for your help! I saw this posted in the other threads but there's been a lot of activity since the release of 5.1 and it was all getting confusing
to get su 2.49 .zip do a Google search u will find it after twrp just flash su 2.49.zip and ur all set .
I tried n its working fine
Would be best at this time to not flash twrp. Instead fastboot boot twrp.img then install the beta.SuperSU v2.49.
Sent from my MT2L03 using XDA Free mobile app
Re-rooting your LOLLIPOP HAM2
Milkteabubbles said:
Hello! I've upgraded to 5.1 and have lost my root. I have tried using kingo and towelroot but neither have worked. I have tried downgrading to 4.3 re-rooting and then upgrading to 5.1 only to lose root again. Any help as to fix this would be awesome and highly appreciated!
Click to expand...
Click to collapse
If your Bootloader is still unlocked, skip to step 5
UNLOCKING YOUR BOOTLOADER
1) Request your 16 digit Bootloader Unlock Code from [email protected] (you'll need to give them your phone's IMEI and SERIAL numbers)
2) Download the HW-QmOneKeyTool to your PC from here: http://www.mediafire.com/download/um5sqbwp094r2x4/HW-QmOneKeyTool.rar
3) Connect your phone to your PC, open the HW-QmOneKeyTool and enter your 16 digit unlock code into the text box in the first tab of that tool, then click 'ROOT' {This button should actually read 'UNLOCK'}
4) Now that your phone's Bootloader is unlocked, flash TWRP as follows:
INSTALLING TWRP
4a) Download TWRP Recovery from the following site: http://forum.xda-developers.com/asc.../2014-09-22-teamwin-recovery-project-t2885144
4b) Rename TWRP_MT2-L03_RECOVERY.img to TWRP.img
4c) Move TWRP.img to hard drive C, folder: adb
4d) Connect you phone to your PC, open Command Prompt and type: cd C:\adb
4e) After the adb prompt, type: adb devices
4f) With your device serial showing in the Command Prompt, type: fastboot flash recovery c:\adb\TWRP.img
4g) The Command Prompt should now say "waiting for device"
4h) Unplug your phone and reboot into bootloader (power + volume down)
4i) Once in the bootloader make sure it says unlocked then plug your phone in.
4j) The command prompt should say done after 2 seconds and your phone will stay the same.
4k) Unplug your phone and reboot.
INSTALLING SUPERUSER
5) Download BETA-SuperSU-v2.49 to your root: http://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
6) Boot into TWRP and Flash BETA-SuperSU-v2.49
7) download the TWRP App from Google Play, and let it install BusyBox, then run the SD fix if needed
7) Now you can grant Superuser status to Apps that need root
Is there a backup of the mt02 emui 3.1 boot loader before I go to the twrp?
omnithesis said:
5) Download BETA-SuperSU-v2.49 to your root: http://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
6) Boot into TWRP and Flash BETA-SuperSU-v2.49
7) download the TWRP App from Google Play, and let it install BusyBox, then run the SD fix if needed
7) Now you can grant Superuser status to Apps that need root
Click to expand...
Click to collapse
Step 7 is required if you don't have an SD card issue?
For anyone that knows, if you root your device, will this cause issues getting OTA updates from Huawei? I registered my IMEI after converting to OEM and loading Lollipop so I would like to ensure I get these updates and can install without issue.
No one?
No
Moody66 said:
No
Click to expand...
Click to collapse
What sort of response is this on a community forum where people try to help each other? Or I thought people helped each other?
I don't get a couple of you members here on the Huawei forums.
Trying to figure out if root causes an issue with OTA updates I believe is a valid question. Thanks for nothing though Moody. You're awesome. :good:
What phone because only a few phones are rooted on lollipop and they have to have unlocked bootloaders.
Sent from my SM-N910V using XDA Free mobile app
TheIgster said:
What sort of response is this on a community forum where people try to help each other? Or I thought people helped each other?
I don't get a couple of you members here on the Huawei forums.
Trying to figure out if root causes an issue with OTA updates I believe is a valid question. Thanks for nothing though Moody. You're awesome. :good:
Click to expand...
Click to collapse
The question was did root affect OTA. The answer is NO. What more do you want.
Moody66 said:
The question was did root affect OTA. The answer is NO. What more do you want.
Click to expand...
Click to collapse
Well, your simple one worded response was misinterpreted. How about that...
And yes, it does effect OTA. I just received B20 and it clearly said to make sure your phone was NOT rooted before upgrading, so obviously it causes an issue with the OTA updates.
Root does not affect OTA. Only if you change system files. Stock recovery and stock system files will not. At worst you will loose root and have to reroot.
---------- Post added at 02:19 PM ---------- Previous post was at 02:14 PM ----------
does root affect OTA....type that into Google. Thousands of posts will tell you the same thing.
Was simply reporting what the update to B20 said. It stated ensure your device is NOT rooted before updating. Perhaps it is just them being careful and ensuring that bugs that may appear on a rooted device would be tougher to diagnose.
Personally I don't see a big need for root with no ROM's available for the HAM.
Because you can't make some changes without root. LCD etc.
Moody66 said:
Because you can't make some changes without root. LCD etc.
Click to expand...
Click to collapse
Yeah, that's true, but to date, I have been pretty happy with the HAM stock. The LP update made this phone a whole new phone. The UI is very nice for an older phone with older specs. Coming from and LG G3 (yes, some would think the HAM is a downgrade), I love the HAM over the G3. The colors are amazing, the screen size is awesome and the new UI for LP is way better than stock LG.
Have a look at a G4. Shame they are expensive
Worth it. But expensive.
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?
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 !!!
Trying to root Nougat (Android 7)? Then read the comments at the bottom please...
I will first state I do NOT own a Moto G4, I own the G3 and the X Pure which are both 3rd Gen devices, but I was requested to write this tutorial by a few users here due to lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto G3/4, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread. Remember, I do not own this device although the methods used are the same as similar devices.
Prerequisites:
0) Be running Marshmallow (Android 6.x) stock ROM, at this time Nougat (Android 7.x) is not working via any method.
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: As of 7/18/2016, Amazon ad-subsidised Moto G 4th Gen devices cannot be bootloader unlocked, therefore they cannot be rooted. Sorry, Lollipop and newer Android security changes pretty much put an end to that.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See TWRP's Moto G 2016 page
3) You need a copy of the latest stable SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device. SR1-SuperSU-v2.78-SR1-20160915123031.zip is the lastest version verified to work with this method.
Note: Do NOT use any 2.77 version, it was a beta intended specifically for the SG Note 7 and will not work, it does not harm but fails to root.
4) Reboot and start TWRP recovery, and PERFORM A COMPLETE BACKUP IN TWRP (Nandroid)!!!
How to do it:
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
EDIT: Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
Notes on Nougat/Android 7... At this time this method of rooting does not work properly on the official Nougat ROM for this device, it causes WiFi issues and interface problems (settings crashes, etc) and with no complete factory image there is no work fix other than to restore your Nandroid backup to pre-root status. If you wish to play with this method and try it, your on your own, I will try to assist but as I stated earlier I do not own this device. To my knowledge as of this posting, there is no working root on stock Android 7 on this device.
I can confirm this worked on my formerly-amazon XT1625 16GB G4. You will get an error about not being able to mount /data, but it proceeds and works anyway.
This is exactly what was missing! I rooted as normal with the latest SuperSU expecting it to just work like on other phones/tablets, but yeah. Before specifying systemless, it hung on boot. After following your instructions it booted right up. Thanks!
Also if you setup adaptable storage with your SDcard, so it works like internal storage, TWRP can't find any files on the SDcard. You will need to revert to non-adaptable storage for TWRP to find the supersu ZIP file.
And make sure you're using the latest SuperSU-- I accidentally tried a very old version which did not work!
Scared Noobie
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Appreciate this. I miss the old days where it was all simple. Everything was flashable. Never had to flash back to something or re flash.
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
Very rare...all you need is read, read, read and follow the instructions. Good luck
Very nice and just what I needed. Worked perfectly on my Amazon Moto G4 with ads. I got no errors or messages but booted fine-got caught in a boot loop once as the SuperSU file explains after it installs. Boots in less then a minute first time.
Marty
acejavelin said:
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Tomsgt said:
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Click to expand...
Click to collapse
cheers mate
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
zipjay said:
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
Click to expand...
Click to collapse
Your welcome... Just give click thanks on the first post, but if you feel absolutely compelled to buy me dinner, there is the Donate button.
Sent from my MotoG3 using Tapatalk
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
mikeruss said:
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
Click to expand...
Click to collapse
Can't you just use MTP mode of TWRP to copy the latest SuperSU to internal storage then flash after creating the config file?
Sent from my MotoG3 using Tapatalk
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
mikeruss said:
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
Click to expand...
Click to collapse
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
acejavelin said:
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
Click to expand...
Click to collapse
32 bit
Sent from my Moto G (4) using Tapatalk
thanks, xposed works fine
Well, I was planning on joining all of you with your Moto G4's soon, or possibly the G4 Plus... but since the Amazon version can't be unlocked anymore I got cold feet, and today Best Buy was running a special on the Moto X Pure 32GB edition for $249 (My Best Buy Elite members only), I pulled the trigger on that one instead. No change in helping though, I didn't have the device to begin with so I will continue to assist with this thread as I can.