Related
Welcome everyone!
This thread has been created for extreme newbies/noobs and for their benefit. Not only noobs, but everyone is free to post questions and also give answers to those questions. Any type of question is allowed as long as it is related about the device. No off-topic discussions are allowed!
Hit Thanks if I Helped You!!!
Regards,
PoseidonKing
Honor 4x hanged (in some Indian kitkat version, not rooted) and after restart it is in bootloop. Honor logo appears then blue light starts to appear then restart.
Recovery mode and dload update not working.
After unlocking bootloader tried fastboot -w, still in bootloop.
Extracted Lollipop, Marshmallow, Kitkat - B161, B126 and flashed in fastboot. Possible to flash only recovery, boot, userdata & system. For others - failed : remote command not allowed. After flashing no change, still in bootloop.
Tried to boot to recovery from fastboot boot
- for lollipop and marshmallow recoveries it says "dtb not found"
- others including twrp, cm it is in bootloop.
Out of warranty.
Need help.
oppili said:
Honor 4x hanged (in some Indian kitkat version, not rooted) and after restart it is in bootloop. Honor logo appears then blue light starts to appear then restart.
Recovery mode and dload update not working.
After unlocking bootloader tried fastboot -w, still in bootloop.
Extracted Lollipop, Marshmallow, Kitkat - B161, B126 and flashed in fastboot. Possible to flash only recovery, boot, userdata & system. For others - failed : remote command not allowed. After flashing no change, still in bootloop.
Tried to boot to recovery from fastboot boot
- for lollipop and marshmallow recoveries it says "dtb not found"
- others including twrp, cm it is in bootloop.
Out of warranty.
Need help.
Click to expand...
Click to collapse
Oh ****, that seems like a frustrating situation. What made the device mess up so much? Have you gone to service centres?
Regards,
PoseidonKing
Not tried to flash or root. It just hanged while using.
Service centre said board gone (as always). MTK devices have a factory mode through which we can check working of all board parts. I did not find any way for this.
oppili said:
Not tried to flash or root. It just hanged while using.
Service centre said board gone (as always). MTK devices have a factory mode through which we can check working of all board parts. I did not find any way for this.
Click to expand...
Click to collapse
Sorry bro, can't help you out over here in this situation.... Best of Luck regarding your device. I would suggest pm'ing a forum moderator for your issue
Hit Thanks if I Helped You!!!
Regards,
PoseidonKing
HELP.!!Back to Stock Rom ????
I am struggling like anything to go back to stock rom. I am using Honor 4x Che1-L04 snapdragon. Pls send a link where can i find the instructions to do this. Or Better U expain.
EDIT:
Roll back to EMUI 4.0 success. Used the Hauwei update extractor and used CMD. Anyhow THANKS
NEW Problem:
How to enable ADOPTED STORAGE in honor 4x che1-L04 snapdragon edition.
In Xda they mentioned only about the kirin processor version.
Help!!!!!!!!!!
balongc52b311 after failing kangvip 6.7.1
hey there. will tell you my experience with failing to flashing kangvip 6.7.1 due to wiping problem
i wiped my cache, data, system even internal storage and yet failed to flashing kangvip 6.7.1 4 custom rom due to "cust" folder unable to mount giving me this:
error 1 can't mount /cust (Invalid argument)
so after failing to mount that folder and even deleting it by mistake,i got a new error:
error 1 can't mount cust no such file or directory
i lost hope and let my my honor 4x normally boot but it took too long and i was determined its stuck on bootloop :cyclops:
i woke up today finding it on 5% battery and giving me that first time setup as if all i did was a factory format BUT all in chinese. checked the build number and it was balongc52b311.
i tried mounting "cust" folder to r/w and rebooted into bootloader but it gave me the same first error. i tried deleting the folder and then rebooting into recovery and it gave me the 2nd error. created the folder "/cast" and then rebooted into recovery and it gave me the same first problem that the folder can't mount EVENTHO it was mounted successfully right before i rebooted into recovery (did this 3 times to make sure)
did some researching and found a solution for honor 4c http://forum.xda-developers.com/honor-4x/help/huawei-honor-4x-balong-hi6210sft-fixed-t3324335 or two BUT both for lolllipop and i'm marshmallow.
i'm already halfway at the method i mentioned above but i stopped after i realized it was for lollipop. i rooted my mobile and changed my build number to "Che2-L11C636B330". worth to mention that my model number remained already the same "Che2-L11".
the cust folder error is still there whenever i go to the bootloader
now i have no idea what to do, what firmware to download and if i have to downgrade first to lollipop and then upgrade to marshmallow again...
my marshmallow version was the middle east final version before this balong happened: Che2-L11C185B561 and i would like to go back to it again.. thank you in advance ( :
###*UPDATED BELOW*
fixed my problem trying the method here http://forum.xda-developers.com/honor-8/help/honor-8-rooted-twrp-modaco-rom-unable-t3462039/page2
>>>>worth to mention that i flashed my oeminfo for my UPDATE.APK REGION before flashing the extracted files from UPDATE.APP "wasn't mentioned in that method"
now i'm back to my original marshmallow version "middle east". good luck people.
abdurrahmanzaki said:
hey there. will tell you my experience with failing to flashing kangvip 6.7.1 due to wiping problem
i wiped my cache, data, system even internal storage and yet failed to flashing kangvip 6.7.1 4 custom rom due to "cust" folder unable to mount giving me this:
error 1 can't mount /cust (Invalid argument)
so after failing to mount that folder and even deleting it by mistake,i got a new error:
error 1 can't mount cust no such file or directory
i lost hope and let my my honor 4x normally boot but it took too long and i was determined its stuck on bootloop :cyclops:
i woke up today finding it on 5% battery and giving me that first time setup as if all i did was a factory format BUT all in chinese. checked the build number and it was balongc52b311.
i tried mounting "cust" folder to r/w and rebooted into bootloader but it gave me the same first error. i tried deleting the folder and then rebooting into recovery and it gave me the 2nd error. created the folder "/cast" and then rebooted into recovery and it gave me the same first problem that the folder can't mount EVENTHO it was mounted successfully right before i rebooted into recovery (did this 3 times to make sure)
did some researching and found a solution for honor 4c http://forum.xda-developers.com/honor-4x/help/huawei-honor-4x-balong-hi6210sft-fixed-t3324335 or two BUT both for lolllipop and i'm marshmallow.
i'm already halfway at the method i mentioned above but i stopped after i realized it was for lollipop. i rooted my mobile and changed my build number to "Che2-L11C636B330". worth to mention that my model number remained already the same "Che2-L11".
the cust folder error is still there whenever i go to the bootloader
now i have no idea what to do, what firmware to download and if i have to downgrade first to lollipop and then upgrade to marshmallow again...
my marshmallow version was the middle east final version before this balong happened: Che2-L11C185B561 and i would like to go back to it again.. thank you in advance ( :
###*UPDATED BELOW*
fixed my problem trying the method here http://forum.xda-developers.com/honor-8/help/honor-8-rooted-twrp-modaco-rom-unable-t3462039/page2
>>>>worth to mention that i flashed my oeminfo for my UPDATE.APK REGION before flashing the extracted files from UPDATE.APP "wasn't mentioned in that method"
now i'm back to my original marshmallow version "middle east". good luck people.
Click to expand...
Click to collapse
Thanks on the update about your success on restoring your phone. Surely some poor soul will get along the same problem and your post will help him out. Sorry for the late reply btw.
Hit Thanks if I Helped You!!!
Regards,
PoseidonKing
How to Root my honor 4x Che2-L11?
Hi everyone, I'm noob, so I need a step to step guide if there's such a thing
my android version is 6.0 and EMUI 4.0
I have bootloader code for unlocking the phone, thanks in advance guys, also happy new year :good:
Phone Honor 4x (che1-L04) Stuck in fastboot mode
My phone is stuck in fastboot mode. Couldn't get the bootloader unlock key online as it requires the product id which can be obtained by dialing a number which isn't possible. I have requested directly from the customer care number and the official chat portal as well but its been more than a week and still they are asking for 24 working hours. Is there any alternative method of getting the key or atleast the Product ID?
Model name :Che1-L04
Stuck in Fastboot & Rescue mode with the bootloader locked.
I got unlock key after 12 days. Honor 4x hanged after restart it is in bootloop.
3 button sd card update not working ?
oppili said:
I got unlock key after 12 days. Honor 4x hanged after restart it is in bootloop.
3 button sd card update not working ?
Click to expand...
Click to collapse
No the update.app isnt working I guess because I have already flashed the CM13 recovery image with the bootloader locked. However, I recieved the bootloader key yesterday from the email but when I tried unlocking by the fastboot command it said it is an invalid or wrong key. Is there any other way to take my phone back to stock condition atleast without actually unlocking the Bootloader?
Princeshubh said:
No the update.app isnt working I guess because I have already flashed the CM13 recovery image with the bootloader locked. However, I recieved the bootloader key yesterday from the email but when I tried unlocking by the fastboot command it said it is an invalid or wrong key. Is there any other way to take my phone back to stock condition atleast without actually unlocking the Bootloader?
Click to expand...
Click to collapse
1. Try "fastboot continue" it will directly boot without going to recovery.
2. If fastboot flash works flash recovery of the firmware installed in phone before bootloop.
3. If still not works flash boot, system, recovery (in this order) of firmware installed before bootloop.
Confirm unlock key with customer care if it is still locked.
I wanna know is there any other method to install xposed framework since the normal installation is not working for me.
Using Honor 4x Che1-l04 running on (stock ROM) Android marshmallow 6.0.1, have TWRP custom recovery and is rooted.
SumitGupta2442 said:
I wanna know is there any other method to install xposed framework since the normal installation is not working for me.
Using Honor 4x Che1-l04 running on (stock ROM) Android marshmallow 6.0.1, have TWRP custom recovery and is rooted.
Click to expand...
Click to collapse
no other way, unfortunatly.. one way or the other, you have to flash the zip...
ps: if you are on emui, first boot after flashing xposed will take a really long time.. mine took around 25 minutes to boot.. so dont consider it a boot loop, wait untill 30 minutes and you will be profitted
Mine was in boot screen for around 3 minutes and then rebooted into recovery. Same thing was happening again and again. So at last did the restore process from TWRP.
oppili said:
1. Try "fastboot continue" it will directly boot without going to recovery.
2. If fastboot flash works flash recovery of the firmware installed in phone before bootloop.
3. If still not works flash boot, system, recovery (in this order) of firmware installed before bootloop.
Confirm unlock key with customer care if it is still locked.
Click to expand...
Click to collapse
Its not working. Please help me I am still stuck....any way of installing the stock ROM back via fastboot mode with the phone showing 'Phone Locked'
Restoring TOO MUCH with twrp?
Can restoring too much with TWRP damage my phone?
jwalker9715 said:
Can restoring too much with TWRP damage my phone?
Click to expand...
Click to collapse
not really..
Hi all,
I am new to the BLU R1 HD scene. Just got my phone this week. It's a amazon prime variant with firmware v7.4.2 (or v7.2.4?).
I got twrp installed and wiped everything through TWRP, including the internal storage - which removed my only NANDroid backup image.
My phone would freeze at the startup BLU logo now. But I could still enter recovery mode (TWRP). And I could still see the TWRP folder from my Ubuntu (which shows as a internal storage drive)
What should I do? Is there a way to flash it back to stock ROM? Where can I download a stock rom?
I am in panic mode now. Any help would be greatly appreciated!!
jimmythefung said:
Hi all,
I am new to the BLU R1 HD scene. Just got my phone this week. It's a amazon prime variant with firmware v7.4.2 (or v7.2.4?).
I got twrp installed and wiped everything through TWRP, including the internal storage - which removed my only NANDroid backup image.
My phone would freeze at the startup BLU logo now. But I could still enter recovery mode (TWRP). And I could still see the TWRP folder from my Ubuntu (which shows as a internal storage drive)
What should I do? Is there a way to flash it back to stock ROM? Where can I download a stock rom?
I am in panic mode now. Any help would be greatly appreciated!!
Click to expand...
Click to collapse
take it easy . sounds like you wiped /system too. but that is ok since you still have access to twrp
take a rom from here
https://forum.xda-developers.com/r1-hd/development/modified-8-3-stock-rom-t3602672
copy it to the phone (internal storage) as seen from your ubuntu.
boot to twrp and select install, browse to the zip file copied to internal
mrmazak said:
take it easy . sounds like you wiped /system too. but that is ok since you still have access to twrp
take a rom from here
https://forum.xda-developers.com/r1-hd/development/modified-8-3-stock-rom-t3602672
copy it to the phone (internal storage) as seen from your ubuntu.
boot to twrp and select install, browse to the zip file copied to internal
Click to expand...
Click to collapse
Oh my god that's good to hear! (especially from someone who knows his stuff!)
I was just looking at that other thread you posted.
Okay I give that a try. Thanks much!
It fixed my phone just as you said! The v8.4 rom is even better with higher level security update. Thanks!
Once you have twrp installed, you can recover from most things that go wrong.
One exception is when people do a "wipe all" and erase the phone's MEID unique identification. When that happens, the phone can boot and work but can no longer be connected to a phone service provider's network.
And the more common problem with this phone is people who accept an over-the-air update that disables SP Flash Tool and then want to get root or flash their phones. They are out of luck at that point.
Hi, I think i've kinda bricked my honor 5C (nem-l51), and I really need help :
A few years ago I rooted my phone to make otg work.
It worked a little while, but then a system update came up, could not update because of the twrp, so I tried to unroot it (from supersu) to do the update, and the twrp stayed after the unroot.
I stayed with the phone like this, twrp installed and update pending (still trying to install the update from time to time) and then I had to use OTG again and tried to re-root my phone.
I tried to flash the supersu files I used the first time, but, even when the flashing worked, I couldn't see the supersu app on the phone, still unrooted.
Then I tried to change the twrp (via fastboot) and I realised that I couldn't : I get the "command not allowed" failure when the recovery should get written. I tried with numerous twrp versions, and stock recovery.
So my twrp right now is the twrp-3.1.1-0-venus "OpenKirin edition" one.
The phone says it's unlocked and the frp is locked, but I can't remember if it was already the case or not when I first rooted.
I unfortunately don't have anymore the bootloader unlock code that huawai gave me originally. I have no idea how to get it again, to try to re-lock/unlock the bootloader.
Back then when I first rooted my phone, I made a back up, so I tried to restore that back up. It failed, first with "cannot wipe the cust partition". Then I tried to restore without restoring the cust partition, and I got "extracttarfork() process ended with error 255" while the system was restoring.
After that, the phone wouldn't boot into android anymore. It would be stuck at the unlocked bootloader warning message and then reboot after a few minutes.
So, lastly, I tried to install the unofficial lineageOS port from here : https://forum.xda-developers.com/honor-5c/development/rom-lineageos-14-1-honor-5c-t3713911 with my twrp.
The installation went well, but the phone is stuck while first booting in lineageOS (I let it overnight, restarted it, re-installed it, tried with the first release, nothing).
TL;DR: My phone isn't booting and I can't flash any new recovery.
Please, help me to get my phone working again
Give me the
old build number on emui
Update build you received..
Twrp working?
Fastboot?
Erecovery?
I got access to erecovery, even if the "download latest version and recovery" doesn't work. (erecovery connects to wifi, and the first thing it tries to check/download fails)
I can boot into fastboot but can't flash recovery from there because of the command not allowed problem.
I can boot into twrp, but the back up I tried to restore and the lineageos rom I tried to install both failed, so maybe the twrp has a problem?
I'm sorry I'm not sure about the build number, I'm pretty sure I was on EMUI 5.0 and android 7.x, and I think I remember comparing current build number vs the update, and it was something like B350 or B351 for the current, and B355 or B375 for the update.
I've found this in my backup file 'recovery.log' ro.omni.version=6.0.1-20160703-nemo-HOMEMADE and ro.build.id=MOB30M . So, that mean that I had android 6.x when I did the backup, way back at the beginning.
I thought the update never got installed because each time the phone would reboot to complete installation, it would reboot into twrp. But I've still updated from android 6 to android 7 somehow ?
NEM-L51C432 or NEM-L51C10 ?
NEM-L51C432 and I'm sure of that ^^
Zhyrclew said:
NEM-L51C432 and I'm sure of that ^^
Click to expand...
Click to collapse
Flash this via twrp
http://update.hicloud.com:8180/TDS/...-L51_hw_eu/update_data_full_NEM-L51_hw_eu.zip
Once done, boot to twrp and flash this
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1581/g104/v82938/f1/full/update.zip
Reboot.
If you are unable to flash the 2nd link then just use the dload method to flash this. If you are not aware of dload method, link is given in my signature.
Note, this 2nd firmware will replace your twrp with stock recovery. You should boot to b350 version and it will be full stock. Reason for flashing data file first is it doesn't replace the recovery to stock but just flashes your data, settings, apps. And 2nd link is main full firmware which will replace your boot, recovery, vendor everything and should boot.
Good luck
I flashed the first one, no error.
The second one had multiple errors :
"[...]
write radio image...
32k crc checked failure
E:unknown command [errno]
update_huawai_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/update.zip'
Updating partition details...
...done
"
So I tried the dload method, and the installation started and ended at 5% with this error :
"Software install failed!
Incompatibility with current version.
Please download the correct update package."
I guess it's because I couldn't tell you the exact build number, I'm sorry for not taking note of it.
If there is a way for me to get the build number despite the status of the phone, i'm ready to do it.
If not, I'm ready to try as many versions as it takes to find the good one.
PS: I've still access to the twrp, thank god ! That was my biggest fear, because I can't flash any recovery in the current state.
Zhyrclew said:
I flashed the first one, no error.
The second one had multiple errors :
"[...]
write radio image...
32k crc checked failure
E:unknown command [errno]
update_huawai_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/update.zip'
Updating partition details...
...done
"
So I tried the dload method, and the installation started and ended at 5% with this error :
"Software install failed!
Incompatibility with current version.
Please download the correct update package."
I guess it's because I couldn't tell you the exact build number, I'm sorry for not taking note of it.
If there is a way for me to get the build number despite the status of the phone, i'm ready to do it.
If not, I'm ready to try as many versions as it takes to find the good one.
PS: I've still access to the twrp, thank god ! That was my biggest fear, because I can't flash any recovery in the current state.
Click to expand...
Click to collapse
You may try other higher versions like 360, 370 etc and see your luck. Twrp will be replaced only if the installation os successful for the main firmware. Its just a trial and error for you now but I am 99% sure you should be able to revive the phone via dload method
Thank you, it's reassuring. I will not give up until I test all the versions ^^
Could you help me a little bit to find other versions, please ? The only place I know where there is update packages for my phone is there : https://forum.xda-developers.com/ho...lota-upgrade-packages-models-nem-l51-t3473110 and there is only two versions.
Zhyrclew said:
Thank you, it's reassuring. I will not give up until I test all the versions ^^
Could you help me a little bit to find other versions, please ? The only place I know where there is update packages for my phone is there : https://forum.xda-developers.com/ho...lota-upgrade-packages-models-nem-l51-t3473110 and there is only two versions.
Click to expand...
Click to collapse
Firmware finder website
Wow, thank you, I downloaded the firmware finder software, it has everything.
Should I flash the firmware in two steps like you first made me, or should I just try with only the dload method with the fullOTA firmware ?
Zhyrclew said:
Wow, thank you, I downloaded the firmware finder software, it has everything.
Should I flash the firmware in two steps like you first made me, or should I just try with only the dload method with the fullOTA firmware ?
Click to expand...
Click to collapse
Check dload guide in my signature. You can follow that now. Good luck
I tried b355, b361, b375, b377, nothing changes, same error.
I noticed that I have something related to an update in my sd card AND internal storage->HwOUC->140783->( update.zip[1.32GB], update_data_full_public.zip[344MB], update_full_NEM-L51_hw_eu.zip[412MB] )
I don't know whether these files were there before I did all these attempted updates.
Could it be that my phone is not trying to install the files I put in sdcard->dload, because he finds these files in the internal memory first, and each time try to install these ?
Should I delete them, move them, unzip them in dload folder ?
Zhyrclew said:
I tried b355, b361, b375, b377, nothing changes, same error.
I noticed that I have something related to an update in my sd card AND internal storage->HwOUC->140783->( update.zip[1.32GB], update_data_full_public.zip[344MB], update_full_NEM-L51_hw_eu.zip[412MB] )
I don't know whether these files were there before I did all these attempted updates.
Could it be that my phone is not trying to install the files I put in sdcard->dload, because he finds these files in the internal memory first, and each time try to install these ?
Should I delete them, move them, unzip them in dload folder ?
Click to expand...
Click to collapse
Copy them on PC and then try dload of files you downloaded from Firmware finder website.
These are files your phone downloaded for OTA update but as you were on twrp, they never installed it amd stays there
I copied the updates my phone downloaded on PC and then deleted them both on internal storage and sd card.
Then I tried dload method with b355,b375&b377 from firmware finder, and also with the update.zip I found in the updates my phone downloaded.
Nothing worked, all of them got the error "Incompatibility with current version. Please download the correct update package."
Should I try even more firmware versions, or should I try something else ?
Btw, I noticed my phone, when connected to my PC, is labeled as huawei-P9-lite, and I don't think it was always like that, but it's probably just because the twrp-3.1.1-0-venus.img is originally for the P9 lite.
I came accross this thread, where somebody recommends to flash stuff from fastboot.
I have not tried it yet, I only tried to flash recovery from fastboot, and it is failing with the "command not allowed". But maybe I could try to flash some other things ? Any advice ?
For now, despite all my attempts to install stock OTA via dload method, the phone is still trying to boot into lineageOS, and failing.
I came across the "current" firmware version with a check with DC-unlocker : "NEM-L51C432B120"
So I downloaded full OTA firmware b120 on firmware finder software, and the dload method worked !
The installation went well, and after a few minutes of the first boot, I got into phone configuration.
I have one last problem, though : the phone configuration is looping.
There is only 4 languages to choose, so I have to choose english(US), then there is a weird list of countries, none in the EU, where I feel i have to choose united states, then after some steps I have to register to huawei ID thing.
If I try to skip it, it loops to the language selection.
If I try to log in to my original account, it says "device not supported for your location" and then loops to languages. (my original account is in french/France)
If I try to create a new account with new address mail, it works but then at the end says again that "device not supported for your location" and then loops to languages.
I tried with other countries it still loops.
The other languages seems to be Chinese and Japanese, but the configuration is looping too if I choose them.
I tried with/without sim, with/without wifi connected...
Dload the next firmware now and see if it works. Then set the phone
I downloaded and installed with dload method (by removing sd card and copying directly on it the files, because I don't know how to have access to the phone internal & external memory now) the next firmware (b130 version)
The phone booted, it launched a "system optimization" that was a few minutes long, and then the EMUI configuration poped up and looped through language selection, region(country), wifi connection (successful), terms and conditions, and WLAN+(switch between wlan and mobile data automatically).
I feel like the phone is working, the notification led is even blinking when I receive sms, but I have access to nothing because of this damned configuration.
Note: the connection to huawei ID isn't prompted again in the loop once I log in, from the original or the new account. In order to be prompted again to log in to the huawei ID, I have to go to erecovery and reset to factory the phone.
I'm coming to the g6 from an older Samsung. I figured that rooting this one would be just as simple, but was I ever wrong. I've gone through the guides available here, as well as guides on other sites, but no joy. I've probably restored my phone to the original system now 5 or 6 times. I'm hoping that someone can point me in the correct direction here.
The last couple of times I tried, here's what I did and what went wrong. I found a guide over at https://www.androidinfotech.com/root-moto-g6-and-g6-plus-pie/ that was fairly straight forward.
The first time I followed the instructions, booting to twrp failed but I figured that was because it never included flashing twrp to the phone. So I flashed it and used fastboot to boot the phone to the image. I then wiped the phone, flashed magisk and then did the same thing with no-verity-opt and rebooted.
On the reboot, the phone cycled through a couple of attempts and then was successful on the third try. But some things were broken. The battery indicator said I had 0% charge, and the phone refused to connect to wi fi. It also didn't recognize my network. And best of all, I've never achieved root. When I boot back into the bootloader, it comes up with the standard motorola file; not twrp.
Just FYI, I'm running pie.
Can anyone point me in the correct direction here? any help will be very much appreciated.
jmalmberg said:
I'm coming to the g6 from an older Samsung. I figured that rooting this one would be just as simple, but was I ever wrong. I've gone through the guides available here, as well as guides on other sites, but no joy. I've probably restored my phone to the original system now 5 or 6 times. I'm hoping that someone can point me in the correct direction here.
The last couple of times I tried, here's what I did and what went wrong. I found a guide over at https://www.androidinfotech.com/root-moto-g6-and-g6-plus-pie/ that was fairly straight forward.
The first time I followed the instructions, booting to twrp failed but I figured that was because it never included flashing twrp to the phone. So I flashed it and used fastboot to boot the phone to the image. I then wiped the phone, flashed magisk and then did the same thing with no-verity-opt and rebooted.
On the reboot, the phone cycled through a couple of attempts and then was successful on the third try. But some things were broken. The battery indicator said I had 0% charge, and the phone refused to connect to wi fi. It also didn't recognize my network. And best of all, I've never achieved root. When I boot back into the bootloader, it comes up with the standard motorola file; not twrp.
Just FYI, I'm running pie.
Can anyone point me in the correct direction here? any help will be very much appreciated.
Click to expand...
Click to collapse
Need a bit more info
What model G6 ? Software channel?
What build number of Pie are you trying to root?
You say "restored my phone to the original system now 5 or 6 times" what version and build number is that and how are you restoring it?
kc6wke said:
Need a bit more info
What model G6 ? Software channel?
What build number of Pie are you trying to root?
You say "restored my phone to the original system now 5 or 6 times" what version and build number is that and how are you restoring it?
Click to expand...
Click to collapse
Model is xt1925-6
Android version is ALI_RETAIL_9.0_PPS29.118-11-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
I'm restoring it using Minimal ADB and Fastboot, and flashing the files over.
A couple of other things I should probably say too.
1. The phone was originally running Oreo. About two weeks ago, Motorola pushed out PIE to me and I installed it. That caused a tone of problems... the biggest one was that you couldn't hear the phone anymore. Couldn't hear callers, ringing, notifications, etc... It might has well have been a doorstop. I tried to roll the phone back to Oreo doing a factory reset, but that didn't work either. Wiped out my IMEI and carrier. So I did a little research and found out that some other people had the same issue. They couldn't roll back so I figured I was stuck with Pie.
2. At that point, I unlocked the bootloader and downloaded the version above from a link in one of the forums and flashed it to the phone. For whatever reason, that cured the IMEI, carrier and sound issues. Since I've come this far and the phone doesn't have anything on it, I'd like to root what I have and get some of the capability that I had on the Samsung.
Thanks for your assistance on this.
jmalmberg said:
Model is xt1925-6
Android version is ALI_RETAIL_9.0_PPS29.118-11-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
I'm restoring it using Minimal ADB and Fastboot, and flashing the files over.
A couple of other things I should probably say too.
1. The phone was originally running Oreo. About two weeks ago, Motorola pushed out PIE to me and I installed it. That caused a tone of problems... the biggest one was that you couldn't hear the phone anymore. Couldn't hear callers, ringing, notifications, etc... It might has well have been a doorstop. I tried to roll the phone back to Oreo doing a factory reset, but that didn't work either. Wiped out my IMEI and carrier. So I did a little research and found out that some other people had the same issue. They couldn't roll back so I figured I was stuck with Pie.
2. At that point, I unlocked the bootloader and downloaded the version above from a link in one of the forums and flashed it to the phone. For whatever reason, that cured the IMEI, carrier and sound issues. Since I've come this far and the phone doesn't have anything on it, I'd like to root what I have and get some of the capability that I had on the Samsung.
Thanks for your assistance on this.
Click to expand...
Click to collapse
PPS29.118-11-1 has a lot of issues. downgrading doesn't seem possible. I thought we had it solved today but ran into the same issue with calls
Follow This thread for rooting
kc6wke said:
PPS29.118-11-1 has a lot of issues. downgrading doesn't seem possible. I thought we had it solved today but ran into the same issue with calls
Follow This thread for rooting
Click to expand...
Click to collapse
Oh, interesting, That's the thread I started with but couldn't get to work for me. That's when I went out and found the guide that I linked to in my original posting. Let me walk through the steps I used here to see if you can tell me where I went wrong.
1. Unlocked my bootloader.
2. Installed Minimal ADB & Fastboot.
3. Placed TWRP, in the Minimal ADB director on my PC and loaded Magisk, DM Verity, Magisk Manager apk to the SD card on my phone. (NOTE: the SD card isn't installed in the phone yet. I'll do that after doing the wipe. Just putting the software on it.)
4. Flashed TWRP to the phone and used Fastboot to load it.
5. Wiped the phone. Used advanced wipe and deleted the cache and data then rebooted to TWRP and did it again. At this point, I installed the SD card.
6. Rebooted the phone into TWRP and then selected install for DM Verity and again for Magisk.
7. Reboot and check for root using Rootcheck. I'm being told that I don't have root access.
What am I missing here?
Again, thank you for the assistance.
jmalmberg said:
Oh, interesting, That's the thread I started with but couldn't get to work for me. That's when I went out and found the guide that I linked to in my original posting. Let me walk through the steps I used here to see if you can tell me where I went wrong.
1. Unlocked my bootloader.
2. Installed Minimal ADB & Fastboot.
3. Placed TWRP, in the Minimal ADB director on my PC and loaded Magisk, DM Verity, Magisk Manager apk to the SD card on my phone. (NOTE: the SD card isn't installed in the phone yet. I'll do that after doing the wipe. Just putting the software on it.)
4. Flashed TWRP to the phone and used Fastboot to load it.
5. Wiped the phone. Used advanced wipe and deleted the cache and data then rebooted to TWRP and did it again. At this point, I installed the SD card.
6. Rebooted the phone into TWRP and then selected install for DM Verity and again for Magisk.
7. Reboot and check for root using Rootcheck. I'm being told that I don't have root access.
What am I missing here?
Again, thank you for the assistance.
Click to expand...
Click to collapse
You need to format data (type yes) In twrp
kc6wke said:
You need to format data (type yes) In twrp
Click to expand...
Click to collapse
That worked! Thank you very much!!! I really appreciate it!!!!
jmalmberg said:
3. Placed TWRP, in the Minimal ADB director on my PC and loaded Magisk, DM Verity, Magisk Manager apk to the SD card on my phone. (NOTE: the SD card isn't installed in the phone yet. I'll do that after doing the wipe. Just putting the software on it.)
.
Click to expand...
Click to collapse
What ver TWRP did you use?
Apparently there is an official version and a modified version to mount vendor-specific mount points?
Thanks,
Tigger31337 said:
What ver TWRP did you use?
Apparently there is an official version and a modified version to mount vendor-specific mount points?
Thanks,
Click to expand...
Click to collapse
I renamed the TWRP file I flashed "recovery.img" and I don't remember the original file name. When I boot to recovery mode it says 3.3.0-0. Hope that helps
jmalmberg said:
I renamed the TWRP file I flashed "recovery.img" and I don't remember the original file name. When I boot to recovery mode it says 3.3.0-0. Hope that helps
Click to expand...
Click to collapse
Yup, I solved it. Thanks. I ended up using 3.2.3.official.
Rooting; ending in bootloop help
Sorry if I am hijacking this thread; thought to discuss here as the title "Trouble rooting my g6" still applies.
I have:
XT1925-13 (Moto G6 ALI) running stock Android Pie with build ppss29.55-34.
I have issues when I tried to root. I followed these steps:
I downloaded the factory image “ALI_RETAIL_9.0_PPS29.55-34_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip” and flashed it first. The mobile restarted and went to the first screen to select a language.
I rebooted it into bootloader, ran the TWRP as a temp by command “fastboot boot twrp-3.3.0-0-Ali.img,” which asked for the password.
I pressed cancel, and then I wiped cache and data.
Via ADB I transferred “adb push Magisk-v20.0.zip /sdcard” and “adb push no-verity-opt-encrypt-6.1.zip /sdcard”.
Then from TWRP, I installed Magisk. Then when installing no-verity, it gave an error “updater process ended with an error: 1 error installing zip file ‘no-verity-opt-encrypt-6.1.zip’.
Rebooted the device with hope and ended in a boot loop.
I also tried to use Magisk-v19.4.zip in the above steps and also tried to skip no-verity-opt-encrypt-6.1.zip. All ended in boot loop.
Any idea why? Are there any guides for the combination XT1925-13 (Moto G6 ALI) running ppss29.55-34?
Many thanks for your time.
Here is a solution
Flash original boot in fastboot followed by TWRP and reboot in recovery.
Install Magisk 19.4 in TWRP (3.3.x Android 9 OK) and reboot
You can update to 20 in Magisk Manager later
The saga starts with a successful rooting of my MI 8. After the Android Q update, the rooting was wiped out. I tried to repeat the root using the previous procedure but the TWRP could not read the file system. I tried a sideload of Magisk. This gave no errors but ended badly with no OS bootable. I could use TWRP to choose to restore the factory image. After the restore and OTA updates, everything looked ok but phone calls had an echo of my voice and the other party could not hear anything. I found a version of TWRP that could read the file system and decided to try an install of Havoc OS. After a wipe of recommended partitions, TWRP could no longer read the file system. I suspect that a format (no option to avoid) wiped out the ability to read the file system. I have now no OS, TWRP can not read the file system, and MiFlash gave no errors but does not load an OS. MiFlash was tried to install a factory ROM, only takes one second, gives a success result, but no go and the phone only has a boot loop now. I have an OTG adapter on order. I suspect I may need a different TWRP specific to Android Q. Any better options?
Update: Success! After finding a post highlighting a better version of TWRP I was able to format the encrypted folders which destroyed the data but allowed a successful install of Havoc OS. Phone is working again. Now on to troubleshooting voice issues. Below is the relevant post.
https://forum.xda-developers.com/mi...3-2-3-1110-t3869729/post78221593#post78221593
Udopia said:
The saga starts with a successful rooting of my MI 8. After the Android Q update, the rooting was wiped out. I tried to repeat the root using the previous procedure but the TWRP could not read the file system. I tried a sideload of Magisk. This gave no errors but ended badly with no OS bootable. I could use TWRP to choose to restore the factory image. After the restore and OTA updates, everything looked ok but phone calls had an echo of my voice and the other party could not hear anything. I found a version of TWRP that could read the file system and decided to try an install of Havoc OS. After a wipe of recommended partitions, TWRP could no longer read the file system. I suspect that a format (no option to avoid) wiped out the ability to read the file system. I have now no OS, TWRP can not read the file system, and MiFlash gave no errors but does not load an OS. MiFlash was tried to install a factory ROM, only takes one second, gives a success result, but no go and the phone only has a boot loop now. I have an OTG adapter on order. I suspect I may need a different TWRP specific to Android Q. Any better options?
Update: Success! After finding a post highlighting a better version of TWRP I was able to format the encrypted folders which destroyed the data but allowed a successful install of Havoc OS. Phone is working again. Now on to troubleshooting voice issues. Below is the relevant post.
https://forum.xda-developers.com/mi...3-2-3-1110-t3869729/post78221593#post78221593
Click to expand...
Click to collapse
When using Android 10 , the best method for rooting is using the patchboot method, and usually it does not require formatting your data.
tsongming said:
When using Android 10 , the best method for rooting is using the patchboot method, and usually it does not require formatting your data.
Click to expand...
Click to collapse
Thanks for the intro to the new technique. I am rooted again through TWRP but I will keep this in mind for the future.