Related
Phone happily running 7.0.0 (NBD90Z, Oct 2016)
Running system less super su SR3 and Franco #57
Downloaded and fast boot flashed the latest November update from PC.
Only flashed updated bootloader and system image from 7.0.0 (NBD91P, Nov 2016)
Restarted Phone and it loops at boot animation, left for twenty minutes, no progress, so rebooted back to recovery and tried wiping, cache, dalvik and art cache, and restarted again still no difference, looped at boot animation again for twenty minutes.
So rebooted to recovery and restored October backup.
Was anyone else and to fast boot flash latest factory system image and boot their phone without any issues?
Is a full wipe really necessary?
Any one?
Sent from my Shamu using Tapatalk
ben_pyett said:
Phone happily running 7.0.0 (NBD90Z, Oct 2016)
Running system less super su SR3 and Franco #57
Downloaded and fast boot flashed the latest November update from PC.
Only flashed updated bootloader and system image from 7.0.0 (NBD91P, Nov 2016)
Restarted Phone and it loops at boot animation, left for twenty minutes, no progress, so rebooted back to recovery and tried wiping, cache, dalvik and art cache, and restarted again still no difference, looped at boot animation again for twenty minutes.
So rebooted to recovery and restored October backup.
Was anyone else and to fast boot flash latest factory system image and boot their phone without any issues?
Is a full wipe really necessary?
Any one?
Sent from my Shamu using Tapatalk
Click to expand...
Click to collapse
I flashed NBD91P without a full wipe and my phone booted without any issues. However I have not been able to get su SR2 or su SR3 to work with either NBD90Z or NBD91P. SR1 works without any issues.
I flashed bootloader, boot and system without a problem. Also using FK, but have magisk+phh root.
I've seen a few people mentioning having problems with SuperSU 2.78 SR2 and SR3 and the latest update (NBD91P)
"Only flashed updated bootloader and system image"
I'm genuinely puzzled as to why people aren't using the OTA sideload method, which is incredibly simple and leaves your data and settings totally intact.
The quote above makes me think "You did half a job and now wonder why your phone won't work...?"
dahawthorne said:
I'm genuinely puzzled as to why people aren't using the OTA sideload method, which is incredibly simple and leaves your data and settings totally intact.
The quote above makes me think "You did half a job and now wonder why your phone won't work...?"
Click to expand...
Click to collapse
You didn't read the post completely, as my phone is working as I always make the precaution of taking a backup and simply restored to it.
I didn't think ota method was possible if you had custom recovery?
Using the method I've described also leaves data and settings in tact.
I didn't run the flash all scripts.
Thanks
Sent from my Shamu using Tapatalk
No offence intended. I have never (touch wood) had any serious problems with my many upgrades on many devices. As you did, I always have a backup in case it goes wrong. In fact I even have multiple backups on my laptop in case the latest one doesn't work.
I've use the OTA sideload method a dozen times now on all my rooted Nexus devices. All of them as standard have TWRP & root (either doitright's or Chainfire's), and the OTA just slides right in there regardless. No problems at all. When it's installed (which takes about five minutes) I have to reroot - I can't remember if I've had to reinstall TWRP, though on a number of occasions I've just reinstalled it anyway without bothering to check if it was already still there.
So in summary the OTA sideload works for rooted/TWRPed devices, doesn't lose anything, and is far simpler and safer than running separate partition flashes. Give it a go and I guarantee you'll never do it the old way again.
dahawthorne said:
No offence intended. I have never (touch wood) had any serious problems with my many upgrades on many devices. As you did, I always have a backup in case it goes wrong. In fact I even have multiple backups on my laptop in case the latest one doesn't work.
I've use the OTA sideload method a dozen times now on all my rooted Nexus devices. All of them as standard have TWRP & root (either doitright's or Chainfire's), and the OTA just slides right in there regardless. No problems at all. When it's installed (which takes about five minutes) I have to reroot - I can't remember if I've had to reinstall TWRP, though on a number of occasions I've just reinstalled it anyway without bothering to check if it was already still there.
So in summary the OTA sideload works for rooted/TWRPed devices, doesn't lose anything, and is far simpler and safer than running separate partition flashes. Give it a go and I guarantee you'll never do it the old way again.
Click to expand...
Click to collapse
Do you change, or alter you system partition, ie remove application or add some.
I'm asking if an ota will apply over the top of an altered system?
If so I'll try it once I've finished work.
Although will also rule out the version of super su first.
Sent from my Shamu using Tapatalk
I change nothing. My N6 is rooted and TWRPed and I just connect to the computer and use ADB to sideload the OTA. It says "flashing unconditionally" so I'm guessing (I'm just an end-user, not a dev) that the OTA just wipes the old ROM and overwrites it, but doesn't touch the data partition. Since the system partition is replaced, root disappears with it, but I'm not sure if it touches TWRP - as I said, I just reinstall it anyway each time and then use it to flash SuperSU.
Give it a go - you'll like it...
P.S. I understand that the OTA has some sort of internal checksum to verify the package integrity, but I always double-check my download with Checksum Utility:
https://raylin.wordpress.com/downloads/md5-sha-1-checksum-utility/
dahawthorne said:
I change nothing. My N6 is rooted and TWRPed and I just connect to the computer and use ADB to sideload the OTA. It says "flashing unconditionally" so I'm guessing (I'm just an end-user, not a dev) that the OTA just wipes the old ROM and overwrites it, but doesn't touch the data partition. Since the system partition is replaced, root disappears with it, but I'm not sure if it touches TWRP - as I said, I just reinstall it anyway each time and then use it to flash SuperSU.
Give it a go - you'll like it...
P.S. I understand that the OTA has some sort of internal checksum to verify the package integrity, but I always double-check my download with Checksum Utility:
https://raylin.wordpress.com/downloads/md5-sha-1-checksum-utility/
Click to expand...
Click to collapse
So flashed, ota through flash fire, worked as described.
As expected phone booted, with stock kernel, recovery and no root.
So rebooted to bootloader and had to re fast boot flash twrp recovery.
But then flashed systemless super su and Franco kernel, phone no longer boots.
Restored backup as ran out of time.
Will try again tonight with our systemless, which root version and methods are you using?
I'll try just kernel and then just root to see which it is that's causing the problem
Progress.
Although to be honest, I'm still of the opinion that flashing just system partition is a far simpler, process then ota.
This is the first time in a a good few years and multiple nexus/android versions, where I've ever had an issue with this process. (And I've had N4, N5 and N6)
Anyone?
Thanks
Sent from my Shamu using Tapatalk
Maybe you're trying too much all at once? I installed the OTA, TWRP and SuperSU 2.78 R3 with no problems - I have tried a couple of custom kernels but saw no appreciable difference, so decided that I'd avoid the risk of tinkering with stuff I don't understand.
Maybe there's some incompatibility with the Franco kernel? I know that SuperSU performs some processing on the kernel - it shows in the installation dialogue.
The more Google locks down android the harder it will be so people need to make a choice and live with it. Either you want the pointless OTA or you are gonna use a custom set up. Not flashing an update properly and then posting a thread about it only makes developers laugh.
zelendel said:
The more Google locks down android the harder it will be so people need to make a choice and live with it. Either you want the pointless OTA or you are gonna use a custom set up. Not flashing an update properly and then posting a thread about it only makes developers laugh.
Click to expand...
Click to collapse
Why do you say he didn't flash the update properly? I thought the only difference between NBD90Z and NBD91P was the bootloader and system images. There was no new recovery, radio, etc... included in that release. So what's the harm in only updating the bootloader/system partitions?
If you did it the "right way" I guess that would be running the flash-all.bat file in the folder. All that does is flash all the partitions (which is dumb because you're overwriting the same partitions which is completely unnecessary if you already have them) and wipe userdata. With his method userdata would've stayed intact.
Please note I never do this method, I'm a custom ROM man thru and thru. Whether it's Dirty Unicorns, AOSiP, OctOS, etc... I never run factory system images because even though with GravityBox you can get a lot of customization, I still prefer CMTE over Substratum/OMS. No way to get CMTE in stock firmware.
dahawthorne said:
Maybe you're trying too much all at once? I installed the OTA, TWRP and SuperSU 2.78 R3 with no problems - I have tried a couple of custom kernels but saw no appreciable difference, so decided that I'd avoid the risk of tinkering with stuff I don't understand.
Maybe there's some incompatibility with the Franco kernel? I know that SuperSU performs some processing on the kernel - it shows in the installation dialogue.
Click to expand...
Click to collapse
Finally managed it.
Fastboot Flashed system
Fastboot Flashed stock boot
Went in to recovery
Flashed Franco
Booted rom
Went back to recovery
Flashed update-unSU (unsure is this stage is needed, but was taking no chances)
Flashed super su
Was finally able to boot rom
Seems combination of super su and Franco wouldn't work in single flash for me. Needed clean reboot between each.
Although I still believe that fast boot flash system is easiest method rather than ota, as doesn't affect recovery or boot partitions and you stay in control, each to their own.
This is the first time I've encountered any issues with this method.
Comments suggesting I didn't do it properly without highlighting what, if anything I did wrong or without adding any positive feedback are worthless.
Thanks for input and suggestions.
Sent from my Nexus 6 using Tapatalk
I had very similar issues. I've been updating this phone monthly since day 1 without issue but with the NBD91P update, I got the same boot loop even with the stock kernel. My device is also encrypted.
After I booted back to the bootloader I noticed that TWRP was gone. I found that very odd. It was like the system image was trying to write over it. Not sure though, but I do know that I had to re-flash TWRP (I've had the same version, which is also the latest one, for months) after every boot loop.
I kept re-flashing and trying different versions of the systemless versions of SuperSU but none of them worked. Got stuck in the same boot loop everytime.
I finally re-flashed everything except for SuperSU and stock NBD91P booted up fine without root.
I'm also having the same issue. I can't even flash SR1. Any update on this?
I can't not boot the NBD91P factory image if I have any layers installed. Removing that overlay folder via TWRP is the only way to make it boot again.
LordDeath said:
I can't not boot the NBD91P factory image if I have any layers installed. Removing that overlay folder via TWRP is the only way to make it boot again.
Click to expand...
Click to collapse
There is a bug in this update which causes a bootloop if the system is themed. Restore to NBD90Z.
msaitta said:
I had very similar issues. I've been updating this phone monthly since day 1 without issue but with the NBD91P update, I got the same boot loop even with the stock kernel. My device is also encrypted.
After I booted back to the bootloader I noticed that TWRP was gone. I found that very odd. It was like the system image was trying to write over it. Not sure though, but I do know that I had to re-flash TWRP (I've had the same version, which is also the latest one, for months) after every boot loop.
I kept re-flashing and trying different versions of the systemless versions of SuperSU but none of them worked. Got stuck in the same boot loop everytime.
I finally re-flashed everything except for SuperSU and stock NBD91P booted up fine without root.
Click to expand...
Click to collapse
collinjames said:
I'm also having the same issue. I can't even flash SR1. Any update on this?
Click to expand...
Click to collapse
LordDeath said:
I can't not boot the NBD91P factory image if I have any layers installed. Removing that overlay folder via TWRP is the only way to make it boot again.
Click to expand...
Click to collapse
I was able to get over my own original problem using the process listed a few posts above, in my previous comment.
Even though it took several attempts to determine a working sequence. Did you try the process which worked for me on your devices?
Strephon Alkhalikoi said:
There is a bug in this update which causes a bootloop if the system is themed. Restore to NBD90Z.
Click to expand...
Click to collapse
Can't comment as my system wasn't themed.
Does the boot loop occur, if you, remove your themes then upgrade to latest image, reboot it and finally reapply your layers?
Sent from my Nexus 6 using Tapatalk
Dopamin3 said:
Why do you say he didn't flash the update properly? I thought the only difference between NBD90Z and NBD91P was the bootloader and system images. There was no new recovery, radio, etc... included in that release. So what's the harm in only updating the bootloader/system partitions?
Click to expand...
Click to collapse
He said, quote:
Only flashed updated bootloader and system image from 7.0.0 (NBD91P, Nov 2016)
Click to expand...
Click to collapse
Unless you have the diffs from the Android git, you can't decide if flashing boot necessary or not. And even then you can decide wrong.
The whole package is: bootloader, radio, boot, system, (vendor in case of the 6P), recovery, and the clutter.
You should skip data, and shouldn't bother with the cache partition, but it's a good idea clearing it after flashing a new system. You can always check if the bootloader and radio have changed, you can diff them if you don't believe the version numbers.
That leaves boot and system, you should always flash both, even if it goes by the nuisance of re-rooting.
Also if you're unencypted, as I am, then after flashing boot, you should not reboot without flashing a root that deals with it.
(But making an unencrypted and verity-less boot is five minutes tops, by the way)
Strephon Alkhalikoi said:
There is a bug in this update which causes a bootloop if the system is themed. Restore to NBD90Z.
Click to expand...
Click to collapse
Having the lastest security fixes is more important than themes.
I've been sitting around on post-surgery "bedrest" and for whatever reason decided to install a different 7.x ROM using trusty TWRP to try something new. However, I'm stumped as to why no matter what ROM I use I get a successful installation message, but infinite boot animation.
I was running AOKP 7.x and it was stable and happy, and that installation went uneventful.
I've run down a list of possible remedies, like clearing cache, installing GAPPs in order first (no good), after LOS ROM .zip (no good), tried reinstalling AOKP (no good)....
I did make a backup of my phone via TWRP in case of an issue, but even reinstalling the backup did no good. It would load successfully, but upon restart... constant boot animation.
I wiped the SSD clean and tried a fresh install, and according to TWRP it was a success, but I've been watching the LOS boot animation for two hours now.
cRDroid sat in the boot loop all night... a full charge... no joke.
So what are my next steps for getting a working phone? I don't care what ROM I use really... I liked AOKP and just wanted to try something new.
Charlie207 said:
I've been sitting around on post-surgery "bedrest" and for whatever reason decided to install a different 7.x ROM using trusty TWRP to try something new. However, I'm stumped as to why no matter what ROM I use I get a successful installation message, but infinite boot animation.
I was running AOKP 7.x and it was stable and happy, and that installation went uneventful.
I've run down a list of possible remedies, like clearing cache, installing GAPPs in order first (no good), after LOS ROM .zip (no good), tried reinstalling AOKP (no good)....
I did make a backup of my phone via TWRP in case of an issue, but even reinstalling the backup did no good. It would load successfully, but upon restart... constant boot animation.
I wiped the SSD clean and tried a fresh install, and according to TWRP it was a success, but I've been watching the LOS boot animation for two hours now.
cRDroid sat in the boot loop all night... a full charge... no joke.
So what are my next steps for getting a working phone? I don't care what ROM I use really... I liked AOKP and just wanted to try something new.
Click to expand...
Click to collapse
What version TWRP are you using?
The latest custom ROMs require the latest modded TWRP from @bhb27.
Next step would b be to install ROM bare, no GAPPs or anything else. Let it boot successfully. You can always install all the other stuff later.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
What version TWRP are you using?
The latest custom ROMs require the latest modded TWRP from @bhb27.
Next step would b be to install ROM bare, no GAPPs or anything else. Let it boot successfully. You can always install all the other stuff later.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
Phone is on TWRP 3.0.2-0_MOD-04
I notice now that v3.2xxxx is out now. Can I use my current TWRP to install the newest .img file to the phone?
I didn't mention that I also attempted to flash the ROM.zip bare a few times for each of the different ROMs I tried to get working. (Both versions of LOS, AOKP , and cRDroid)
Charlie207 said:
Phone is on TWRP 3.0.2-0_MOD-04
I notice now that v3.2xxxx is out now. Can I use my current TWRP to install the newest .img file to the phone?
I didn't mention that I also attempted to flash the ROM.zip bare a few times for each of the different ROMs I tried to get working. (Both versions of LOS, AOKP , and cRDroid)
Click to expand...
Click to collapse
Go to the TWRP thread and get the latest MODDED TWRP. Do NOT use the TWRP from the official site.
I can post a link later if you can't find it, but it's the Quark TWRP thread in the same forum you got some of the other ROMs.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
Go to the TWRP thread and get the latest MODDED TWRP. Do NOT use the TWRP from the official site.
I can post a link later if you can't find it, but it's the Quark TWRP thread in the same forum you got some of the other ROMs.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
OK, I'll take a look.
Can I upgrade TWRP within TWRP?
Charlie207 said:
OK, I'll take a look.
Can I upgrade TWRP within TWRP?
Click to expand...
Click to collapse
Yes.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
Yes.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
OK.
Successfully upgraded TWRP, and the install of LOS seemed to go smoothly. Now it's back to the waiting game with the install/boot animation. I'll check back in a bit if nothing good has happened.
So after trying to install fresh versions of AOKP and LOS with the most recent version of TWRP I'm still stuck.
Now AOKP (which installs without a hiccup) simply lights up the boot image, and basically shuts off after 20-30 seconds.
Can I get a hint on the best way to completely wipe the phone with TWRP, and trying a different method?
Charlie207 said:
So after trying to install fresh versions of AOKP and LOS with the most recent version of TWRP I'm still stuck.
Now AOKP (which installs without a hiccup) simply lights up the boot image, and basically shuts off after 20-30 seconds.
Can I get a hint on the best way to completely wipe the phone with TWRP, and trying a different method?
Click to expand...
Click to collapse
You can try a truly clean install...
Boot your phone to TWRP, plug into PC, test file transfer. Drag something from PC to Download folder and make sure it's there...
Then, if successful, gather everything you want to install -- ROM, GAPPS, SuperSu, etc. -- onto your PC.
Next save off anything you could not stand to lose or do not have backed up already. Pictures in the DCIM folder, and such.
Now while still in TWRP, format everything on the phone. Including internal storage. You will be completely wiping the phone. You will lose everything on the phone.
Do NOT reboot!
After wiping the phone, while still in TWRP, drag over all the install files you gathered earlier. Install the ROM first and reboot. If successful, go back to TWRP and install GAPPS and whatever else you want.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
You can try a truly clean install...
Boot your phone to TWRP, plug into PC, test file transfer. Drag something from PC to Download folder and make sure it's there...
Then, if successful, gather everything you want to install -- ROM, GAPPS, SuperSu, etc. -- onto your PC.
Next save off anything you could not stand to lose or do not have backed up already. Pictures in the DCIM folder, and such.
Now while still in TWRP, format everything on the phone. Including internal storage. You will be completely wiping the phone. You will lose everything on the phone.
Do NOT reboot!
After wiping the phone, while still in TWRP, drag over all the install files you gathered earlier. Install the ROM first and reboot. If successful, go back to TWRP and install GAPPS and whatever else you want.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
I've done this several times as you describe it. Each time (no matter which ROM) it installs a-ok and then hangs up on the first boot animation.
If TWRP isn't going to work, is there another way to install a .zip? I seem to remember doing it via ADB a few years ago.
Charlie207 said:
I've done this several times as you describe it. Each time (no matter which ROM) it installs a-ok and then hangs up on the first boot animation.
If TWRP isn't going to work, is there another way to install a .zip? I seem to remember doing it via ADB a few years ago.
Click to expand...
Click to collapse
There's ways to push over files via ADB, as this was necessary before TWRP could handle drag and drop. I don't know of any way to flash (install) zipped files via ADB.
Maybe someone else has some ideas?
I know you want latest custom ROM. But as an experiment have you tried flashing back to stock Marshmallow? Pure stock Marshmallow? If that works, then you can try to upgrade back to custom ROMs.
ChazzMatt said:
There's ways to push over files via ADB, as this was necessary before TWRP could handle drag and drop. I don't know of any way to flash (install) zipped files via ADB.
Maybe someone else has some ideas?
I know you want latest custom ROM. But as an experiment have you tried flashing back to stock Marshmallow? Pure stock Marshmallow? If that works, then you can try to upgrade back to custom ROMs.
Click to expand...
Click to collapse
I haven't tried flashing a pure stock MM ROM yet, but will surely give that a try. Do you have a link to a recommended MM ROM?
And, I assume I'd be attempting the install just like I did previously.... e.g. wipe everything, DO NOT reboot, drag .zip from laptop to phone via USB cable, install, (then profit?).
Not that it should matter from a hardware point of view, but I'm using a 2011 MacBook Pro 15" running the latest beta version of OS 10.13.whatever. It sends files to the phone via the Android File Transfer app. I think that's the only way to physically send files from a Mac to Android.
Looking back at some past post of mine, I had a similar issue with cRDroid, which installed it's own recovery software, and wouldn't work with TWRP. I did end up (through serious trial and error headbanging) succeeding in using ADB commands via Terminal to get the phone wiped clean and installed TWRP. After that I was able to load custom ROMs via TWRP and had no problems swapping between different ROMs until just the other day.
I found this ROM, and will attempt to flash it via TWRP: https://forum.xda-developers.com/droid-turbo/development/rom-mpg24-107-70-2-brazilian-6-0-1-t3426234
Charlie207 said:
I found this ROM, and will attempt to flash it via TWRP: https://forum.xda-developers.com/droid-turbo/development/rom-mpg24-107-70-2-brazilian-6-0-1-t3426234
Click to expand...
Click to collapse
Well **** me running....
That worked. I followed the identical wipe+install procedure for the "stock" MM 6.0.1 ROM as I had for three other 7.x ROMs, and it installed with no issues this time. I'm staring at the Welcome screen, and pretty frustrated that this was the only way to get the phone working again. I'll do a basic setup, and then see if I can flash a 7.x ROM
Thanks for your help in solving this riddle up to now. I'll see what happens....
EDIT: Now that I think of it, the only thing I did different was that, after downloading the ROM to my laptop, I edited the file name from that long name to MM6.0.1.zip so I could simply recognize it faster when clicking between windows and stuff. Other than that I followed the same installation process as noted before.
I'm going to edit/shorten the filename of the LOS ROM and see if removing unneeded characters does anything.
Nothing is working. The Brazilian stock MM ROM works, in a basic sense, but doesn't allow calls or WiFi, so that's kind of a moot point.
Back to the drawing board.
The Brazilian MM ROM was junk for my purposes, but the other MM ROM worked.. Phone is setting up now. WiFi and LTE work on it, so I guess I'll be stuck with 6.x for a while until I feel like messing around with a 7.x ROM.
Charlie207 said:
Nothing is working. The Brazilian stock MM ROM works, in a basic sense, but doesn't allow calls or WiFi, so that's kind of a moot point.
Back to the drawing board.
Click to expand...
Click to collapse
The Brazilian ROM needs your own modem. You would need to flash that in TWRP separately.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
The Brazilian ROM needs your own modem. You would need to flash that in TWRP separately.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
Yeah... I realized my mistake, and flashed the other MM ROM. That one works normally.
I'm stumped why all of a sudden 7.x ROMs refuse to install on my phone. I had prevously installed crDroid, AOKP, and RR 7.x ROMs just fine via TWRP.
ChazzMatt said:
There's ways to push over files via ADB, as this was necessary before TWRP could handle drag and drop. I don't know of any way to flash (install) zipped files via ADB.
Maybe someone else has some ideas?...
Click to expand...
Click to collapse
I'm not sure if all TWRP versions for different devices are the same, but with my Pixel C (TWRP 3.2.1) there is an "adb sideload" option in recovery to install zip files via adb from a computer.
I think the command is: adb sideload filenamegoeshere.zip
Sorry for reviving this thread, but I have exact same issue. Stock Lollipop and MM roms work, but any custom rom just hangs on boot animation forever did you manage to sort it out? @Charlie207
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
heya people! my razer 2 is screwed. I had trinity kernel originally, and i saw arter's was updated to april and trinity was march so i flashed arter's, someone else did it with no issue.
K so i flash arter, go to system, reboot, someone in tg group told me arter is sketchy and known to brick phones, so i wanted to go back to trinity, before tho, someone said i should clean flash my stock, so i tried. The thing is, the file comes from razer, and is a flash_all.bat the only problem was i couldnt use fastboot, so after talking to them i tried to just flash the boot.img to boot slot in twrp. Big mistake. Twrp no longer is a thing, fastboot doesnt work, cant go into download mode, when i boot up my phone it tells me my phone is corrupted and may not function, after that it takes me to default android recovery screen.
if i hit apply via adb, i get sys errors and **** and according to nfs group, my partition is completely corrupted (device not found) or something like that
so i called a repair place and explained it to him and he said hed have to look at it, so im gonna probably have to drive down there for him to tell me its screwed.
I tried applying via sd card, but when i insert the sdcard to my pc and try to write files, it says its write protected, and i dont see anything in properties about making it r/w so im really at a loss.
Is there ANYTHING i can do or am i gonna have to pray that this guy knows something?
dont thikn i can send to razer since i broke my warranty unlocking bootloader and rooting.
anything would help guys, i dont wanna have to go back to my razer 1 ;_;
ok well i didnt get any replies so i took it to a repair place, he said his tech guy wasnt in but he'd call me with updates as to whats happening. Shouldnt cost more than $75 so thats great.
if you have any ideas on what could be wrong id love to hear, maybe i can learn from my mistakes and be able to recover next time.
I'm not sure about the comments in the telegram group, but I don't think it was necessary to flash all the stock stuffs. Factory images may contain stuffs that you should never flash on a device that has already left factory and packaged. Usually you should only be flashing boot, system and vendor (plus userdata, if you want to wipe existing data as well). You may also consider flashing modem, dsp, bluetooth if baseband/firmware update on certain parts are needed.
Recovery is now part of the kernel image, so flashing stock kernel means you have stock recovery. Stock recovery is only useful if you accidentally issued Factory Reset from system, or pressed "Wipe user data" from bootloader (which happened when I was preparing the device for unlock/rooting for the first time), and got into an endless loop after that (since TWRP may not properly handle /misc stuffs).
Again, **NEVER** use Factory Reset from system, or Wipe user data from bootloader, if you use TWRP. Always wipe data from TWRP if you intend to do so.
At one point (r13) arter97's kernel had some issues which is supposed to have been fixed in r14. I haven't updated my kernel yet since last Trinity nightly (it's working great even after flashing MR3 vendor stuffs).
LSS4181 said:
I'm not sure about the comments in the telegram group, but I don't think it was necessary to flash all the stock stuffs. Factory images may contain stuffs that you should never flash on a device that has already left factory and packaged. Usually you should only be flashing boot, system and vendor (plus userdata, if you want to wipe existing data as well). You may also consider flashing modem, dsp, bluetooth if baseband/firmware update on certain parts are needed.
Recovery is now part of the kernel image, so flashing stock kernel means you have stock recovery. Stock recovery is only useful if you accidentally issued Factory Reset from system, or pressed "Wipe user data" from bootloader (which happened when I was preparing the device for unlock/rooting for the first time), and got into an endless loop after that (since TWRP may not properly handle /misc stuffs).
Again, **NEVER** use Factory Reset from system, or Wipe user data from bootloader, if you use TWRP. Always wipe data from TWRP if you intend to do so.
At one point (r13) arter97's kernel had some issues which is supposed to have been fixed in r14. I haven't updated my kernel yet since last Trinity nightly (it's working great even after flashing MR3 vendor stuffs).
Click to expand...
Click to collapse
hmm, im not understanding how flashing stock boot.img to boot partition would make recovery part of the kernel image? boot.img is the literal only thing i got to flash in twrp before it just died.
Like i said fastboot didnt work, and oddly enough, it doesnt work on my old razer 1 either, i tried rooting it the other day and it wont go to fastboot
Edit: according to an admin in magnetar group, dm-verity could be the reason, and he said i should've flashed something called "lazy flasher" after flashing the boot img. Never heard of it and never used it.
hadtosignuptoreply said:
hmm, im not understanding how flashing stock boot.img to boot partition would make recovery part of the kernel image? boot.img is the literal only thing i got to flash in twrp before it just died.
Like i said fastboot didnt work, and oddly enough, it doesnt work on my old razer 1 either, i tried rooting it the other day and it wont go to fastboot
Edit: according to an admin in magnetar group, dm-verity could be the reason, and he said i should've flashed something called "lazy flasher" after flashing the boot img. Never heard of it and never used it.
Click to expand...
Click to collapse
Recovery is built into the kernel (which is common for recent devices). arter97 (or Trinity) kernel image includes TWRP in place of the stock recovery, so you get TWRP when you flashed the kernel. Stock boot.img comes with stock recovery, so if you flash stock kernel you lose TWRP.
Also, keep track of your reboot count and your current active slot. If your system fails to boot multiple times in a row, the bootloader may consider it damaged and switching to another slot (which usually contains the previous version of system/vendor/modem etc.) and may cause some issues if you're unlocked (or you were previously on a GSI).
As for fastboot issues, I once had a time that I could only conduct flash commands within a very tiny time window right after the phone booted to bootloader, although the problem has been lessened after reboot and I could now flash properly again. It's unknown when the problem would resurface that I'd need another reboot (given the distro I use, Manjaro, is constantly updating, I'd just update the system and reboot anyway if that happens).
Some fastboot versions may be buggy, or maybe USB interactions under Linux can be problematic in general (especially in handling plugs and unplugs). This is more apparent if a system is running constantly for a long time and a lot of devices has been properly (or improperly) plugged or unplugged over the course of its uptime. Maybe it's better if one conducts fastboot using rear USB ports (as front USB ports tend to have less voltage).
I never bothered with dm-verity and hardly ever had problems with it.
vnb
LSS4181 said:
Recovery is built into the kernel (which is common for recent devices). arter97 (or Trinity) kernel image includes TWRP in place of the stock recovery, so you get TWRP when you flashed the kernel. Stock boot.img comes with stock recovery, so if you flash stock kernel you lose TWRP.
Also, keep track of your reboot count and your current active slot. If your system fails to boot multiple times in a row, the bootloader may consider it damaged and switching to another slot (which usually contains the previous version of system/vendor/modem etc.) and may cause some issues if you're unlocked (or you were previously on a GSI).
As for fastboot issues, I once had a time that I could only conduct flash commands within a very tiny time window right after the phone booted to bootloader, although the problem has been lessened after reboot and I could now flash properly again. It's unknown when the problem would resurface that I'd need another reboot (given the distro I use, Manjaro, is constantly updating, I'd just update the system and reboot anyway if that happens).
Some fastboot versions may be buggy, or maybe USB interactions under Linux can be problematic in general (especially in handling plugs and unplugs). This is more apparent if a system is running constantly for a long time and a lot of devices has been properly (or improperly) plugged or unplugged over the course of its uptime. Maybe it's better if one conducts fastboot using rear USB ports (as front USB ports tend to have less voltage).
I never bothered with dm-verity and hardly ever had problems with it.
Click to expand...
Click to collapse
ah ok. Well the repair guy called and said they didnt know what was wrong or how to fix it, i know i can at least get to bootloader, and to root my razer 1 again, i went to bootloader and fastboot worked. Before work tomorrow im gonna get that phone from the place and hope that i can flash what i need to get it working again. Assuming it will actually be able to read the device. Thanks for your input
Long story short: I tried to install a GSI so I installed TWRP and flashed some necessary zips (vbmeta, mutidisabler, ...) from different sources and the GSI, but maybe it was a bad idea to follow multiple sources, because the phone was bootlooping when I tried to reboot into system. I then wiped everything and reflashed everything but that didn't fix it. After meddlilng around for a while, I was able to get into the download mode, so I thought of flashing the factory firmware with Heimdall. I used samloader and downloaded the supposedlly correct firmware (M215FXXU2BUH6/M215FODM2BUI1/M215FDDU2BUH1/M215FXXU2BUH6, region is BKD). When I was adding the files, I found out that I was missing the following files:
md5.img (MD5HDR)
efs.img (EFS)
sec_efs.img (SEC_EFS)
nad_fw.bin (NAD_FW)
param.bin (PARAM)
steady.bin (STEADY)
uhuh.bin (UHCFG)
blcmd.bin (BLCMD)
spu.img (SPU)
ul_key.bin (UL_KEYS)
nad_refer.bin (NAD_REFER)
dqmdbg.img (DQMDBG)
There were other partitions, but no files were listed for them, so I think they are not supposed to be flashed. There were also two different "fota.zip" files, but I didn't know what to do with them. Anyway, I flashed the other files, but the phone started bootlooping with the bootloader unlocked warning screen. I locked the bootloader from the download mode and tried again but no luck. I tried reflashing everything again, but the flashing stopped halfway with the message "super.img blocked by OEM" or something like that. I performed a force reboot with volume down + power and it rebooted into the "Emergency Recovery Function" screen. I reflashed everything again, but this time, without super.img, and it flashed fine, but the same bootloop problem remained. Looking up on the internet, it seems that efs.img has something to do with the IMEIs. I don't have any backup of it. I also don't know how to get the rest of the files (if all of them are even necessary), or what they even do/mean.
Basically, I'm trying to get it back to the factory software, or salvage it in any other way. Does somebody have any idea how to fix it?
Naah... Stuff like this happens to me all the time.
Download this ODIN first: https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
Then download this firmware: https://samfw.com/firmware/SM-M215F/BKD/M215FXXU2BUG2
Now first a few things:
1. You probably downloaded a engineer firmware that isnt allowed as of now.
2. Heimdall is mostly dead, last I checked. It isnt very wise to use it.
3. LOCKING THE BOOTLOADER IN A UNSTABLE STATE IS FOOLISHNESS. I do not mean to offend anyone, but pls dont do this.
4. I think you are using ErfanGSI/ some other port. These will NOT work. Only phhusson's GSI's have worked for me so far.
So coming back to the topic, Just open up the ODIN and connect up your phone. It will get recognized. If it is not in emergency/ download modes, just hold vol down + power, then press both vol buttons and connect to pc immediately - it will boot into dl mode.
Select the BL, AP, CP and HOME_CSC. Flash these.
It should reboot right back up into stock.
Also, are you using my vbmeta zip from ItsMeKande's thread?
Chill
GuruPrasadAH
Thanks for the fast response. I followed your instructions and was able to recover the device. It was actually bootlooping after flashing the firmware. I had to lock the bootloader to be able to successfully boot into the system. I was kind of worried, because I was running Odin in VirtualBox since Odin is Windows-exclusive and I don't use Windows. I'm glad everything worked out well in the end. I used to be into Android modding years ago, but my last Android device was Android 5 based and I stopped modding it once it got to my "perfect state". I haven't kept up with the modding scene since then. Things seems to have gotten a lot more complicated with newer Android versions.
GuruPrasadAH said:
Also, are you using my vbmeta zip from ItsMeKande's thread?
Click to expand...
Click to collapse
Yes.
Since you seem to know about this stuff, can you recommend a GSI that's customizable, lightweight, and doesn't have GApps or microG?
newt23 said:
Thanks for the fast response. I followed your instructions and was able to recover the device. It was actually bootlooping after flashing the firmware. I had to lock the bootloader to be able to successfully boot into the system. I was kind of worried, because I was running Odin in VirtualBox since Odin is Windows-exclusive and I don't use Windows. I'm glad everything worked out well in the end. I used to be into Android modding years ago, but my last Android device was Android 5 based and I stopped modding it once it got to my "perfect state". I haven't kept up with the modding scene since then. Things seems to have gotten a lot more complicated with newer Android versions.
Yes.
Since you seem to know about this stuff, can you recommend a GSI that's customizable, lightweight, and doesn't have GApps or microG?
Click to expand...
Click to collapse
My to-go answer is always crdroid. Its lightweight, customizable, and comes in variants with gapps, foss and vanilla. The one you're looking for is vanilla. Here's the post where u can find the link
Any official or unofficial lineage OS for Samsung galaxy M21
Hello everyone so I have a Samsung galaxy M21 with One UI 3.1 core. Are there any lineage OS official or unofficial builds for Android 11? If you know please reply to this, thank you in advance!!! 🙏🏾🙏🏾🙏🏾
forum.xda-developers.com
Hmm, it didn't work. I get bootloops...
Did you follow all the instructions given in that thread?
Only if you flash vbmeta, Multidisabler it will boot.
Then too magisk is recommended. The zips are in that thread.
Follow the instructions and let me know. On guy OldNoobOne also successfully flashed and booted a gsi
Let me know if it works
Chill
GuruPrasadAH
For Multidisabler just do a google search one for samsung devices will appear
Here's what I did (stock firmware, unlocked bootloader):
1. Boot into dl mode
2. Flash TWRP and boot into it
3. Wipe > Format data > "yes"
4. Reboot > Recovery
5. Advanced > Terminal
6. "cd external_sd/flash"
7. "super mount system"
8. "super flash system crdrom-v313-210921-arm64-bvZ-lite.img"
9. Install > vbmeta.zip, multidisabler-samsung-3.1.zip"
10. Reboot into system
And I get bootloops. Multidisabler detects Android 10, doesn't find the stock recovery and fails to mount /system. Maybe that's the problem? I'm using this one.
Also try flashing magisk... I dont really understand what is happening to you.
Maybe you set the system as read only? Really not sure.
Also, a ROM might be coming soon
Chill
GuruPrasadAH
Yes, that did the trick! I'm able to boot into crDroid now. I was wondering if I needed to flash something to fix the corners, but seems like a simple reboot fixed it.
Anyway, thanks a lot for your help!
newt23 said:
Yes, that did the trick! I'm able to boot into crDroid now. I was wondering if I needed to flash something to fix the corners, but seems like a simple reboot fixed it.
Anyway, thanks a lot for your help!
Click to expand...
Click to collapse
Use Overlay-Fix by dev Yillie. It had worked for me on crd too. You will find Yillie on telegram 'Galaxy M21 Updates' group, download from there.