Related
This is a TWRP backup of the stock firmware for V510 GPE GPAD 8.3. They have already been updated. It is completely stock no mods, no root, no busybox. This should ensure that you are able to take future OTAs without issue. Many GPE users have been having problems with the OTAs. The reason is that the OTA does a system verification and any type of modification causes it to fail.
How to flash this:
1. Reboot into bootloader
2. Flash TWRP if you don't already have it. Current version is 2.8.1.0 fastboot flash recovery xxxxxxxxxxxxx.img (where xxxxx is the filename)
3. Reboot System
4. Copy the entire contents of the zip file to your TWRP/BACKUPS/LG0000XXXXXXXX folder. Make sure you copy the folder 2014-11-30--23-35-25 LRX21P.L004 or 2014-06-26--18-41-18 KTU84P.L002. If you don't have a backups folder, create one in TWRP by choosing Backup, then backup something like the boot partition.
5. Reboot to Recovery Vol Dwn+Pwr or adb reboot recovery.
6. Choose Restore and select 2014-11-30--23-35-25 LRX21P.L004 or 2014-06-26--18-41-18 KTU84P.L002
7. Once finished Reboot System.
8. Upon boot you should be greeted with the usual Setup screens.
9. Reboot into bootloader
10. (Optional for Kit Kat) Flash stock recovery: fastboot flash recovery 17-recovery.img
11. Reboot into system
.
Flashing the stock recovery is optional however if you want a completely stock experience and ensure future OTAs, you probably want to do so. Also note that you must unroot to take any future OTAs.
To reroot flash latest version of TWRP.
Download Links:
LMY47O.L008 with Stock Recovery
TWRP Backup 5.1 LMY47O.L005 with Stock Recovery
TWRP Backup 5.1 LMY47O Thanks @rocket321 for providing the image.
TWRP BACKUP 5.0 LRX21P.L004
TWRP BACKUP 4.4.4 KTU84P.L002
KK Stock Recovery
You did an excellent job on this thread. Thanks for doing this for our small community.
BTW: regarding recovery for our device, the latest (and in fact only) that I see is TWRP 2.7.0.1 in the Original Android Development section.
Agreed. I wasn't able to flash 4.4.4 any other way. Tried everything, kept getting errors. This finally worked!
cam30era said:
You did an excellent job on this thread. Thanks for doing this for our small community.
BTW: regarding recovery for our device, the latest (and in fact only) that I see is TWRP 2.7.0.1 in the Original Android Development section.
Click to expand...
Click to collapse
Figured it will come in handy to have this online for everyone in the future...when I bought the device when it was announced thought there would be more dev on it...but that hasn't been the case. Luckily we at least have twrp.
No partitions selected for restore.
djkinetic said:
This is a TWRP backup of the stock firmware for V510 GPE GPAD 8.3. It has already been updated to 4.4.4. It is completely stock no mods, no root, no busybox. This should ensure that you are able to take future OTAs without issue. Many GPE users have been having problems with the OTA for 4.4.4 The reason is that the OTA does a system verification and any type of modification causes it to fail.
How to flash this:
1. Reboot into bootloader
2. Flash TWRP if you don't already have it. Current version is 2.7.0.1 fastboot flash recovery xxxxxxxxxxxxx.img (where xxxxx is the filename)
3. Reboot System
4. Copy the entire contents of the zip file to your TWRP/BACKUPS/LG0000XXXXXXXX folder. Make sure you copy the folder 2014-06-26--18-41-18 KTU84P.L002. If you don't have a backups folder, create one in TWRP by choosing Backup, then backup something like the boot partition.
5. Reboot to Recovery Vol Dwn+Pwr or adb reboot recovery.
6. Choose Restore and select 2014-06-26--18-41-18 KTU84P.L002
7. Once finished Reboot System.
8. Upon boot you should be greeted with the usual Setup screens.
9. Reboot into bootloader
10. (Optional) Flash stock recovery: fastboot flash recovery 17-recovery.img
11. Reboot into system
.
Flashing the stock recovery is optional however if you want a completely stock experience and ensure future OTAs, you probably want to do so. Also note that you must unroot to take any future OTAs.
Download Links:
TWRP BACKUP 4.4.4 KTU84P.L002
Stock Recovery
Click to expand...
Click to collapse
When I flash this in twrp it fails to flash and i get an error message: No partitions selected for restore. Have twrp 2.7.0.1 installed. Thank you.
Do I unzip the folder before I move it to the backup folder?
1barlog17 said:
Do I unzip the folder before I move it to the backup folder?
Click to expand...
Click to collapse
Delete
Figured out what was going on. finally got it to flash in TWRP. Works great. Thank you for this.
Thanks for this image - was the only way I was able to update.
Sent from my LG-V510 using Tapatalk
I was not able to update using your image and I don't know why. Everything was done correctly as far as I know. I downloaded and unpacked the zip and placed it in the back apps folder of TWRP and rebooted into recovery and tried restore with no success during the system restore it stops halfway through and says failed.
I tried downloading the file twice, installing the file from my computer, changing my SD card, deleting everything and trying, deleting just dalvik cache a,updating the partition separately, and was able to update the boot partition but not system and data. I honestly don't know what the trouble is as I was able to restore my own back up several times.if anybody has any insight into what is happening here please tell me. I would really like to install the update! I don't know why it is not allowing me to.
sleekmason said:
I was not able to update using your image and I don't know why. Everything was done correctly as far as I know. I downloaded and unpacked the zip and placed it in the back apps folder of TWRP and rebooted into recovery and tried restore with no success during the system restore it stops halfway through and says failed.
I tried downloading the file twice, installing the file from my computer, changing my SD card, deleting everything and trying, deleting just dalvik cache a,updating the partition separately, and was able to update the boot partition but not system and data. I honestly don't know what the trouble is as I was able to restore my own back up several times.if anybody has any insight into what is happening here please tell me. I would really like to install the update! I don't know why it is not allowing me to.
Click to expand...
Click to collapse
First off, I use solid explorer, dual pane. Very easy to navigate for me.
I only copied system. I didn't even wipe. All my data and settings were intact. As close to an OTA I could get. The system backup was 790.95mb
It sounds like you did everything right to me. I included a screen shot of what it looked like after i clicked the backup.zip and moved the unzipped backup to the TWRP backup folder.
Sent from my LG-V510 using XDA Premium 4 mobile app
sleekmason said:
I was not able to update using your image and I don't know why. Everything was done correctly as far as I know. I downloaded and unpacked the zip and placed it in the back apps folder of TWRP and rebooted into recovery and tried restore with no success during the system restore it stops halfway through and says failed.
I tried downloading the file twice, installing the file from my computer, changing my SD card, deleting everything and trying, deleting just dalvik cache a,updating the partition separately, and was able to update the boot partition but not system and data. I honestly don't know what the trouble is as I was able to restore my own back up several times.if anybody has any insight into what is happening here please tell me. I would really like to install the update! I don't know why it is not allowing me to.
Click to expand...
Click to collapse
im not sure if this would work
did u try restoring from the internal sd instead of external. as far as I know the backup file should have no issues.
djkinetic said:
im not sure if this would work
did u try restoring from the internal sd instead of external. as far as I know the backup file should have no issues.
Click to expand...
Click to collapse
That was it!! Thank you!
Do I need to uninstall Xposed Framework, unroot, restore the stock kernel, etc., before restoring this system back up TWRP? I assume the answer is no, though I'll need to reinstall those afterward, but I figured I'd check first!
UPDATE: Never mind. I just went ahead and restored it successfully and am in the process of restoring my apps from TiBu now. Thanks again for providing this for those of us who couldn't upgrade to 4.4.4 any other way!
Hey guys,
first off thank you for posting this tutorial, I was able to perform the backup0 and am currently on 4.4.4.
I did, however, run into a slight hiccup when I was trying to flash the stock recovery. I kept getting messages about partitions and so forth. I entered in the following commands from beginning to end:
adb devices
adb reboot bootloader
fastboot flash recovery 17-recovery.img
but as I said I can't get the job done lol.
Any ideas?
ephayzee said:
Hey guys,
first off thank you for posting this tutorial, I was able to perform the backup0 and am currently on 4.4.4.
I did, however, run into a slight hiccup when I was trying to flash the stock recovery. I kept getting messages about partitions and so forth. I entered in the following commands from beginning to end:
adb devices
adb reboot bootloader
fastboot flash recovery 17-recovery.img
but as I said I can't get the job done lol.
Any ideas?
Click to expand...
Click to collapse
A few things to check:
you need to have usb debugging checked on phone
you need the recovery image in same folder as your fastboot.exe/adb files
you need to cd to that directory/folder
TWRP source
Hi,
Can you please tell me where to find TWRP 2.7.x for the V510. I currently have 2.6.3.0, I believe?
Thanks
techinv said:
Hi,
Can you please tell me where to find TWRP 2.7.x for the V510. I currently have 2.6.3.0, I believe?
Thanks
Click to expand...
Click to collapse
It worked fine for me with TWRP 2.6
techinv said:
Hi,
Can you please tell me where to find TWRP 2.7.x for the V510. I currently have 2.6.3.0, I believe?
Thanks
Click to expand...
Click to collapse
Here > http://forum.xda-developers.com/showthread.php?t=2682606
However, download link in OP is currently broken. I PMed the OP about it.
Has anyone gotten the error "E: No partitions selected for restore." when trying to flash the recovery?
Like other curious 6P users, I flashed the "full ota" zip to check out Nougat. Then I tried to restore my nandroid for Dirty Unicorns, and apparently TWRP 3.0.2-1 had a fatal flaw that borked the EFS backup. I tried literally everything I could think of, until I saw the process @be_vigilant did to revive his phone. I'm going to be using his process as the base for the guide, as well as linking you to my nandroid that has now helped two other people revive their device.
What you need:
*MMB29P factory image (although MTC20F also worked for someone).
Direct download link: https://dl.google.com/dl/android/aosp/angler-mmb29m-factory-616cf265.zip
*My nandroid backup (its stock MMB29P, decrypted and rooted)
https://www.androidfilehost.com/?fid=24686679545612465
*TWRP recovery image (3.0.2-0 or one of the newer builds that fixed the EFS stuff)
https://dl.twrp.me/angler/
*Android SDK or at least platform-tools (for fastboot, adb, etc)
The Process:
1. Extract the factory image into the location where you have fastboot.exe (mine is C:\Android\sdk\platform-tools)
2. Extract the nandroid backup - doesn't matter where, I'll explain later
3. Make sure you are in bootloader mode, and run flash-all.bat from the factory image
4. Flash TWRP (fastboot flash recovery twrprecovery.img)
5. Boot into TWRP, and make a new nandroid backup. This step is just to create the TWRP backup folder on your device
6. Now go to wipe, advanced wipe, click on each partition one at a time, choose "Repair or Change File System", then select "Repair File System" - do this for dalvik/art, system, data, internal storage, and cache. It may not work for all of them, but its ok.
***you must mount data again in TWRP after doing this, or you will not be able to see anything***
7. Copy & paste my nandroid onto your device in the correct location (sdcard/TWRP/BACKUPS/XXXXXX)
8. Restore my nandroid and try to boot.
9. If it still does not boot at this point, then you need to run these adb commands (while in TWRP) that @bogomil4e kindly reported to wipe the EFS partitions
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384 -and-
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
Now you should be able to boot up and do anything you want again. Please do not mirror my nandroid or take advantage of it - I am making it available only for people to utilize as a way to unbrick their phone!
Thanks Train, I would been lost. I replied to you gplus posting. Really appreciative for your work on this post. Thanks dude.
Ash
Bump
Sent from my Nexus 6P using Tapatalk
Double Bump
Sent from my SGP621 using XDA-Developers mobile app
This needs to be pinned!
Sent from my Nexus 6 using XDA Labs
I just used this and was able to get my Nexus 6P back up with your nandroid. I should not be able to use fastboot flash correct to get a full google stock?
pctechdroid said:
I just used this and was able to get my Nexus 6P back up with your nandroid. I should not be able to use fastboot flash correct to get a full google stock?
Click to expand...
Click to collapse
Yes you should be able to... Or just unroot so that the OTA will work.
Sent from my Nexus 6P using Tapatalk
Train88 said:
Like other curious 6P users, I flashed the "full ota" zip to check out Nougat. Then I tried to restore my nandroid for Dirty Unicorns, and apparently TWRP 3.0.2-1 had a fatal flaw that borked the EFS backup. I tried literally everything I could think of, until I saw the process @be_vigilant did to revive his phone. I'm going to be using his process as the base for the guide, as well as linking you to my nandroid that has now helped two other people revive their device.
What you need:
*MMB29P factory image (although MTC20F also worked for someone).
Direct download link: https://dl.google.com/dl/android/aosp/angler-mmb29m-factory-616cf265.zip
*My nandroid backup (its stock MMB29P, decrypted and rooted)
https://www.androidfilehost.com/?fid=24686679545612465
*TWRP recovery image (3.0.2-0 or one of the newer builds that fixed the EFS stuff)
https://dl.twrp.me/angler/
*Android SDK or at least platform-tools (for fastboot, adb, etc)
The Process:
1. Extract the factory image into the location where you have fastboot.exe (mine is C:\Android\sdk\platform-tools)
2. Extract the nandroid backup - doesn't matter where, I'll explain later
3. Make sure you are in bootloader mode, and run flash-all.bat from the factory image
4. Flash TWRP (fastboot flash recovery twrprecovery.img)
5. Boot into TWRP, and make a new nandroid backup. This step is just to create the TWRP backup folder on your device
6. Now go to wipe, advanced wipe, click on each partition one at a time, choose "Repair or Change File System", then select "Repair File System" - do this for dalvik/art, system, data, internal storage, and cache. It may not work for all of them, but its ok.
***you must mount data again in TWRP after doing this, or you will not be able to see anything***
7. Copy & paste my nandroid onto your device in the correct location (sdcard/TWRP/BACKUPS/XXXXXX)
8. Restore my nandroid and try to boot.
9. If it still does not boot at this point, then you need to run these adb commands (while in TWRP) that @bogomil4e kindly reported to wipe the EFS partitions
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384 -and-
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
Now you should be able to boot up and do anything you want again. Please do not mirror my nandroid or take advantage of it - I am making it available only for people to utilize as a way to unbrick their phone!
Click to expand...
Click to collapse
Dude. I don't know what to say. I really thought I lost my nexus 6p. But your tutorial worked like a charm. Thank you so much for sharing your nandroid and writing up an amazing tutorial!!! This seriously needs to get pinned!!????✌?
Sent from my ONE A2003 using Tapatalk
---------- Post added at 05:22 PM ---------- Previous post was at 05:17 PM ----------
BTW, I also was on MTC20F. Your nandroid booted the device. But I had to clean install MTC20F again so that the WiFi and sim started to work. Might come handy for some people... ??
Sent from my ONE A2003 using Tapatalk
im_Zak said:
Dude. I don't know what to say. I really thought I lost my nexus 6p. But your tutorial worked like a charm. Thank you so much for sharing your nandroid and writing up an amazing tutorial!!! This seriously needs to get pinned!!????✌?
Sent from my ONE A2003 using Tapatalk
---------- Post added at 05:22 PM ---------- Previous post was at 05:17 PM ----------
BTW, I also was on MTC20F. Your nandroid booted the device. But I had to clean install MTC20F again so that the WiFi and sim started to work. Might come handy for some people... ??
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
I'm glad I could help! Thanks for the extra info! ?
Sent from my Nexus 6P using Tapatalk
I have a similar issue, any advice on this... Updated to PureNexus Nougat fine, but even before that I had realized that my phone was not being detected through USB, no fastboot, recovery, nothing. So I flashed through TWRP to the current PureNexus Nougat build. All went good, except I now realized that the version of TWRP I have must be one with bugs on Nougat. Booting into recovery it just sits at the TWRP loading screen forever.
I can't get ADB through USB, can't get into Recovery, and Fastboot wont connect on USB. I can boot into the ROM just fine (not rooted) and can do ADB w/ wifi when booted up in Android.
Any ideas on how to fix my recovery and/or flash anything at all at this point? I am almost feeling like there must be something wrong with the actual usb-c port, but charging works fine, just no data connection at all (tried any different cables, Windows, Mac, different usb ports).
Is debugging on in your developer options.
Sent from my ONE A2003 using Tapatalk
Lacrosse200760 said:
I have a similar issue, any advice on this... Updated to PureNexus Nougat fine, but even before that I had realized that my phone was not being detected through USB, no fastboot, recovery, nothing. So I flashed through TWRP to the current PureNexus Nougat build. All went good, except I now realized that the version of TWRP I have must be one with bugs on Nougat. Booting into recovery it just sits at the TWRP loading screen forever.
I can't get ADB through USB, can't get into Recovery, and Fastboot wont connect on USB. I can boot into the ROM just fine (not rooted) and can do ADB w/ wifi when booted up in Android.
Any ideas on how to fix my recovery and/or flash anything at all at this point? I am almost feeling like there must be something wrong with the actual usb-c port, but charging works fine, just no data connection at all (tried any different cables, Windows, Mac, different usb ports).
Click to expand...
Click to collapse
What Zak said - you are not even in the same boat as the people that need this guide. You can get it to boot. I could not do anything besides go to fastboot(download mode) when I made this
Sent from my Nexus 6P using Tapatalk
Lacrosse200760 said:
I have a similar issue, any advice on this... Updated to PureNexus Nougat fine, but even before that I had realized that my phone was not being detected through USB, no fastboot, recovery, nothing. So I flashed through TWRP to the current PureNexus Nougat build. All went good, except I now realized that the version of TWRP I have must be one with bugs on Nougat. Booting into recovery it just sits at the TWRP loading screen forever.
I can't get ADB through USB, can't get into Recovery, and Fastboot wont connect on USB. I can boot into the ROM just fine (not rooted) and can do ADB w/ wifi when booted up in Android.
Any ideas on how to fix my recovery and/or flash anything at all at this point? I am almost feeling like there must be something wrong with the actual usb-c port, but charging works fine, just no data connection at all (tried any different cables, Windows, Mac, different usb ports).
Click to expand...
Click to collapse
You can flash recovery from phone terminal, Google the commands. You need root though, install super su from playstore. Otherwise you'll need to fix that adb issue.
djdarkknight96 said:
You can flash recovery from phone terminal, Google the commands. You need root though, install super su from playstore. Otherwise you'll need to fix that adb issue.
Click to expand...
Click to collapse
Installing SuperSU from playstore wont actually give me Root though. I like the idea though, maybe there is something that can be done around this.
Lacrosse200760 said:
Installing SuperSU from playstore wont actually give me Root though. I like the idea though, maybe there is something that can be done around this.
Click to expand...
Click to collapse
Flash recovery through adb or android terminal, download the superSU zip, flash the zip in recovery. If you're having trouble getting recovery to stick, you need to flash the superSU zip immediately after you flash recovery. If you boot before doing that, android will try overwrite the custom recovery on boot
Sent from my Nexus 6P using Tapatalk
Train88 said:
Flash recovery through adb or android terminal, download the superSU zip, flash the zip in recovery. If you're having trouble getting recovery to stick, you need to flash the superSU zip immediately after you flash recovery. If you boot before doing that, android will try overwrite the custom recovery on boot
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Doesn't flashing recovery through adb require root? (only have adb wifi access when phone is booted into ROM)
Lacrosse200760 said:
Doesn't flashing recovery through adb require root? (only have adb wifi access when phone is booted into ROM)
Click to expand...
Click to collapse
No you don't need root to flash in adb. Just an unlocked bootloader
Sent from my Nexus 6P using Tapatalk
Lacrosse200760 said:
Doesn't flashing recovery through adb require root? (only have adb wifi access when phone is booted into ROM)
Click to expand...
Click to collapse
Train88 said:
No you don't need root to flash in adb. Just an unlocked bootloader
Click to expand...
Click to collapse
I have been very lucky to not have to remember but Train is correct. You should be able to push recovery via adb Wi-Fi. I forget root isn't needed to replace it, like Train said. "Kinda talking to myself as a reminder lol"
Train88 said:
Like other curious 6P users, I flashed the "full ota" zip to check out Nougat. Then I tried to restore my nandroid for Dirty Unicorns, and apparently TWRP 3.0.2-1 had a fatal flaw that borked the EFS backup. I tried literally everything I could think of, until I saw the process @be_vigilant did to revive his phone. I'm going to be using his process as the base for the guide, as well as linking you to my nandroid that has now helped two other people revive their device.
What you need:
*MMB29P factory image (although MTC20F also worked for someone).
Direct download link: https://dl.google.com/dl/android/aosp/angler-mmb29m-factory-616cf265.zip
*My nandroid backup (its stock MMB29P, decrypted and rooted)
https://www.androidfilehost.com/?fid=24686679545612465
*TWRP recovery image (3.0.2-0 or one of the newer builds that fixed the EFS stuff)
https://dl.twrp.me/angler/
*Android SDK or at least platform-tools (for fastboot, adb, etc)
The Process:
1. Extract the factory image into the location where you have fastboot.exe (mine is C:\Android\sdk\platform-tools)
2. Extract the nandroid backup - doesn't matter where, I'll explain later
3. Make sure you are in bootloader mode, and run flash-all.bat from the factory image
4. Flash TWRP (fastboot flash recovery twrprecovery.img)
5. Boot into TWRP, and make a new nandroid backup. This step is just to create the TWRP backup folder on your device
6. Now go to wipe, advanced wipe, click on each partition one at a time, choose "Repair or Change File System", then select "Repair File System" - do this for dalvik/art, system, data, internal storage, and cache. It may not work for all of them, but its ok.
***you must mount data again in TWRP after doing this, or you will not be able to see anything***
7. Copy & paste my nandroid onto your device in the correct location (sdcard/TWRP/BACKUPS/XXXXXX)
8. Restore my nandroid and try to boot.
9. If it still does not boot at this point, then you need to run these adb commands (while in TWRP) that @bogomil4e kindly reported to wipe the EFS partitions
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384 -and-
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
Now you should be able to boot up and do anything you want again. Please do not mirror my nandroid or take advantage of it - I am making it available only for people to utilize as a way to unbrick their phone!
Click to expand...
Click to collapse
Followed Your guide
at first, I couldn't repair the data partition. Then I formatted the whole device again and was able to repair data partition. But when I go to restore your backup, boot flashes fine but when it says flashing data, TWRP hangs and it reboots into the google splash logo screen.
TJ_bab said:
Followed Your guide
at first, I couldn't repair the data partition. Then I formatted the whole device again and was able to repair data partition. But when I go to restore your backup, boot flashes fine but when it says flashing data, TWRP hangs and it reboots into the google splash logo screen.
Click to expand...
Click to collapse
It could be due to the storage option my 6P has (128 GB)... Try restoring everything but data. But essentially, it's the efs backup that you need if your issue was created by a bad backup from TWRP 3.0.2-1.
Sent from my Nexus 6P using Tapatalk
Hi to all. I'm new in Honor world and I've stopped my Android experience with KitKat so I'm a little bit confused ...
I've read several guides (on XDA too) that that three steps to obtain root are unlock bootloader, flash TWRP via ADB and then install Magisk or SuperSU via TWRP. But in the thread on TWRP is clearly written that to install Magisk decryption is needed and to have decryption we must flash a kernel with encryption disabled in fstab. But no guide says anything about this step. Can someone explain me how encryption/decryption work doing a standard installation of TWRP ? Is needed a flash of a modified kernel ? And where find it ?
And another question (if it's not too much ). Since I don't need to install custom rom (I want root only to use some apps like Titanium) how can I make a backup of stock rom, boot.img, efs partition and all that can be useful to restore phone to the starting point if, by chance, I need Huawei warranty ?
Thanks a lot
Hi, apparently there's a way to get root on an encrypted system. Follow the rebrand guide and then flash supersu in TWRP via ADB sideload. It worked for me and a few others, there is no comment from the developers as of right now.
So basically in short follow this guide until you are finished with the TWRP section:
https://forum.xda-developers.com/honor-9/how-to/one-guide-recovery-os-roms-t3661829
Then
- enter twrp
- adb sideload supersu
Afterwards follow the "rooting!" section with point 2
Thank for your answer... I'd like to try to install Magisk instead of SuperSU. In several places is written that this should be right. I'll try....
unvisigoth said:
Thank for your answer... I'd like to try to install Magisk instead of SuperSU. In several places is written that this should be right. I'll try....
Click to expand...
Click to collapse
The method is also working fine with Magisk. Let me know if you need help
zxz0O0 said:
The method is also working fine with Magisk. Let me know if you need help
Click to expand...
Click to collapse
Finally done with a couple of hours of panic. This is the story if can be useful to someone...
Unlock bootloader....done TWRP install... done. Copy magisk (apk and zip) on phone than install apk without opening it. Reboot to recovery wipe all, factory reset. Trying to boot.....BOOTLOOP But I don't have installed Magisk zip. Only apk without opening it.
Nothing to do. Bootloop and then erecovery. I try to restore the backups previously done with TWRP. I restore boot and system partition. All wipes ...no luck. I don't know what has happened. While downloading full firmware to try to reinstall it I try to install magisk.zip. Install via TWRP. All wipes and then magically (it's such a case ) phone boots. Powered off and on several times no problem. Root (verified with root checker) ok.
I habe b100 release but I don't think to update to b130. I wait for Oreo...
The only two things that I can say are these: first TWRP even after flashing magisk gave an error (unable to mount system). Two while installing magisk it seems that magisk itself has patched something.
If someone has an explanation is welcome...
unvisigoth said:
Finally done with a couple of hours of panic. This is the story if can be useful to someone...
Unlock bootloader....done TWRP install... done. Copy magisk (apk and zip) on phone than install apk without opening it. Reboot to recovery wipe all, factory reset. Trying to boot.....BOOTLOOP But I don't have installed Magisk zip. Only apk without opening it.
Nothing to do. Bootloop and then erecovery. I try to restore the backups previously done with TWRP. I restore boot and system partition. All wipes ...no luck. I don't know what has happened. While downloading full firmware to try to reinstall it I try to install magisk.zip. Install via TWRP. All wipes and then magically (it's such a case ) phone boots. Powered off and on several times no problem. Root (verified with root checker) ok.
I habe b100 release but I don't think to update to b130. I wait for Oreo...
The only two things that I can say are these: first TWRP even after flashing magisk gave an error (unable to mount system). Two while installing magisk it seems that magisk itself has patched something.
If someone has an explanation is welcome...
Click to expand...
Click to collapse
So do you have some step-by-step instructions for someone who wants to unlock and root the phone with magisk?
shiboby said:
So do you have some step-by-step instructions for someone who wants to unlock and root the phone with magisk?
Click to expand...
Click to collapse
Here what I have done:
Unlock bootloader
install adb drivers (find something that is right for your PC. For example minimal ADB found on XDA weren't suitable for me. Google adb drivers...). Open a command windows (shift+right click). If typing "adb devices" your phone is found that's ok
Enable usb debugging and oem unlock (or in other words disable FRP, factory reset protection)
Put the phone in fastboot mode ("adb reboot bootloader"). If all ok typing "fastboot devices" your phone is found
Type "fastboot oem unlock xxxxxxxx" (xxxxxxxx is the code provided by Huawey)
Bootloader unlocked
Flash TWRP
Download TWRP recovery for Honor 9 (link found on other thread on this forum)
Put the phone in fastboot mode
Type "fastboot flash recovery xxxxx.img" (where xxxx.img is the recovery downloaded)
Reboot phone directly in Recovery to avoid erecovery overwrite TWRP. Booting on TWRP let TWRP patch to avoid erecovery booting
Now here I've had some issues as said (read previous post). My tip is the following:
after rebooting in TWRP make all wipes then reboot again in TWRP
Install Magisk.zip (for me download here https://geekaxe.com/root-honor-9-twrp-bootloader-unlocking/)
Reboot recovery
All wipes
Reboot to system
If it's all OK you can install magisk.apk and you are rooted
I suggest after flashing TWRP to make backup of all partitions on external SD (for some reasons, maybe encryption, backup on internal storage gives error). Again I suggest to copy all files that you need (i.e. magisk files) on external sd before starting all.
Pay attention that if you update firmware after this procedure I think that you must repeat all. For me I remain on original firmware found on phone (B100). B130 seems to have some bugs, B120 doesn't seem improve much. Moreover all releases are 7.0 based. I wait for Oreo, hopefully in some custom rom!
To add to this, a bootloop or two might be normal. Let it sit for a few minutes before considering re-flashing everything.
Thanks for your guide!
Zuzler said:
To add to this, a bootloop or two might be normal. Let it sit for a few minutes before considering re-flashing everything.
Thanks for your guide!
Click to expand...
Click to collapse
You're right. But after 20 minutes of bootlops I've chosen another way....:laugh::laugh:
unvisigoth said:
You're right. But after 20 minutes of bootlops I've chosen another way....:laugh::laugh:
Click to expand...
Click to collapse
So is it fixed?
Sent from my Honor 8 Pro using XDA Labs
adriansticoid said:
So is it fixed?
Sent from my Honor 8 Pro using XDA Labs
Click to expand...
Click to collapse
Yes sure. As said previously installation of magisk.zip fixed the bootloop problem. I think (but I could be wrong) that installation of TWRP corrupted the boot partition and magisk fixed it. But it's only an hypothesis...
unvisigoth said:
Yes sure. As said previously installation of magisk.zip fixed the bootloop problem. I think (but I could be wrong) that installation of TWRP corrupted the boot partition and magisk fixed it. But it's only an hypothesis...
Click to expand...
Click to collapse
Observe and be careful man.
Sent from my Honor 8 Pro using XDA Labs
unvisigoth said:
Yes sure. As said previously installation of magisk.zip fixed the bootloop problem. I think (but I could be wrong) that installation of TWRP corrupted the boot partition and magisk fixed it. But it's only an hypothesis...
Click to expand...
Click to collapse
Which TWRP version did you use?
I had a similar problem after formatting all data with the OpenKirin TWRP 3.1.1 Perhaps its an issue with this TWRP release?
I was able to recover in similar circumstances by flashing a stock boot.img over fastboot. Based on this, it's looking like Magisk is really the way to go for rooting atm. Making sure to pull my twrp backup with adb this time though.
If I'm lucky enough to install magisk and not get a bootloop the safetynet always fails. Anyone got a valid method of actually getting magisk working fully?
Unofficial TWRP for Moto G5S Plus (Sanders)
Additional Features over Official TWRP:
Supports flashing of both 32bit and 64bit ROMs and Kernels.
OREO Images/ROMs support.
Decryption and Encryption support.
No SuperSU by default.
No TWRP app.
No HTC Dumlock cruft.
Updated pigz compressor (slightly faster and more tolerant of corruption).
NTFS support(Both Read and Write).
Covers more partitions for nandroid backup (OEM, FSG and FSC).
Experimental support for SD cards that are partitioned for partial adopted storage and partial removable storage.
Faster I/O performance.
Fixed Gapps/aroma freeze issues.
IMPORTANT!!! : READ INSTRUCTIONS CAREFULLY BEFORE PROCEEDING TO FLASHING PROCESS..!!
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either Magisk or flash any of the verity disabler zips available on xda.
Force encryption is enabled by default in stock OS and twrp will successfully decrypt /data at first boot if all goes well
If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to wipe data once via twrp wipe options and reboot back to twrp for functioning of /data
Flashing Instructions:
Using Existing TWRP:
Reboot to recovery > Click on Install > Install Image > recovery > select recovery image and flash > reboot to recovery
Other Methods(Fastboot) :
Make sure you have unlocked bootloader
Reboot to bootloader
Enter following command in terminal: fastboot flash recovery twrp-****.img (if you want permanent flash) or fastboot boot twrp-****.img (if you want temporary boot)
Incase your device is encrypted (while coming from stock rom), Follow these steps to decrypt:
Reboot to recovery > cancel the password prompt > mount all partitions > Format Data/Userdata (on f2fs) > Reboot Recovery > Mount all partitions again > Flash Magisk > Reboot
Now you are free to use Stock ROM (Decrypted) or Flash any custom rom you want.
Download Links: https://www.androidfilehost.com/?w=files&flid=216298
TWRP Themes: Check 3rd post
Known Issues: None || Report if you find any.
XDA:DevDB Information
[RECOVERY][UNOFFICIAL][Sanders] TWRP-3.2.1-r20 (64bit Supported!), Tool/Utility for the Moto G5S Plus
Contributors
CheckYourScreen
Source Code: https://github.com/CheckYourScreen/twrp_device_motorola_sanders
Version Information
Status: Stable
Current Stable Version: r20
Stable Release Date: 2018-04-04
Created 2017-10-26
Last Updated 2018-04-04
|| Changelog ||
r20:
Fixed Encryption support on custom roms.
Updated kernel
Updated build fingerprint for latest bootloader support.
Reverted pigz changes.
Switched back to original twrp themes. (TWRP Themes can be found in 3rd post )
Various bug fixes and improvements.
r16:
Fixed compatibility with New Bootloader (C2.07-December patch)
Merged october patches in kernel.
Various twrp upstream patches and fixes.
Fixed remote wipe process (Earlier remote wipe issued from play account wasnt processed due to twrp)
r15:
Added 64bit Support (You can flash both 32bit/64bit roms or kernels with it).
Fixed Encryption Support! (No need to format data to decrypt and mount).
Updated to 3.2.1 upstream changes with full oreo support.
Remove android reboot during password check on multiple wrong inputs.
r9:
Fixed F2FS mount issues(You can flash magisk modules or SuperSu now).
Enabled NTFS Write Support (You can make backups on sdcard/pendrives formatted on NTFS).
Fixed size of various partitions.
Switched to LZMA compression to decrease size.
r7: Initial Public Release
|| Themes ||
Here are some of the twrp themes:
Preview images: https://photos.app.goo.gl/DLrfDseGzfxE8Uq93
Download link: https://androidfilehost.com/?w=files&flid=233551
:good:
Only one that has actually be working for me ever since I got the phone. Thank you for your efforts.
this seems to suffer from the same thing the stock rom/kernel suffers from, the weird f2fs bug that makes certain mounts fail. geneticengineer has shared a kernel that fixes this in stock rom , maybe you could get in touch with him about how he updated f2fs
Thank you for your work, this seems to work well on my device. If you would like to swap the kernel, I posted a newer firmware NPS26.116-45 here:https://forum.xda-developers.com/showpost.php?p=74325160&postcount=33
revengineer said:
Thank you for your work, this seems to work well on my device. If you would like to swap the kernel, I posted a newer firmware NPS26.116-45 here:https://forum.xda-developers.com/showpost.php?p=74325160&postcount=33
Click to expand...
Click to collapse
But its for xt1806 only i think. Not real help. The most user here are outside usa.
Schrotty35 said:
But its for xt1806 only i think. Not real help. The most user here are outside usa.
Click to expand...
Click to collapse
Well my guess is that the kernel in the present twrp is from the -26 firmware posted in the other thread. That firmware was US Retail also. The OP in the other thread states in can be used on other models. But I am not going to tell you that because I do not know. I have not found any other firmware for the sanders model.
Ae3NerdGod said:
this seems to suffer from the same thing the stock rom/kernel suffers from, the weird f2fs bug that makes certain mounts fail. geneticengineer has shared a kernel that fixes this in stock rom , maybe you could get in touch with him about how he updated f2fs
Click to expand...
Click to collapse
Afaik it doesnt affect TWRP, you just need to be on a custom kernel if you are running stock rom.
Twrp has nothing to do with it.
If you face any problem flashing anything then post a screenshot or log.
revengineer said:
Thank you for your work, this seems to work well on my device. If you would like to swap the kernel, I posted a newer firmware NPS26.116-45 here:https://forum.xda-developers.com/showpost.php?p=74325160&postcount=33
Click to expand...
Click to collapse
Schrotty35 said:
But its for xt1806 only i think. Not real help. The most user here are outside usa.
Click to expand...
Click to collapse
Stock kernel is same in both the firmwares.
-45 is just for US variant, i dont recommend you to even flash that firmware on other variants.
CheckYourScreen said:
Afaik it doesnt affect TWRP, you just need to be on a custom kernel if you are running stock rom.
Twrp has nothing to do with it.
If you face any problem flashing anything then post a screenshot or log.
Click to expand...
Click to collapse
but i have a custom stock kernel, and things that fail in TWRP work in flashfire or magiskmanager
its mostly magisk modules im having problems with, ill reproduce an error when i get the chance
Ae3NerdGod said:
but i have a custom stock kernel, and things that fail in TWRP work in flashfire or magiskmanager
its mostly magisk modules im having problems with, ill reproduce an error when i get the chance
Click to expand...
Click to collapse
Flash the magisk module via twrp > take screenshot when flashing completes > go to advance section of twrp and take recovery log > reboot system > send that screenshot and recovery log here.
CheckYourScreen said:
Flash the magisk module via twrp > take screenshot when flashing completes > go to advance section of twrp and take recovery log > reboot system > send that screenshot and recovery log here.
Click to expand...
Click to collapse
will do, it happens with every magisk package i try. they used to fail in stock too till i used geneticengineers kernel from telegram now they work
didnt know you could screenshot in recovery, i assume its the same buttons
Ae3NerdGod said:
will do, it happens with every magisk package i try. they used to fail in stock too till i used geneticengineers kernel from telegram now they work
didnt know you could screenshot in recovery, i assume its the same buttons
Click to expand...
Click to collapse
Yes, same buttons to take a screenshot in TWRP
TWRP backup is frozen at 13% completed. The progress bar is still showing its animation.
I unlocked the bootloader, and then rebooted. Android came up with the language selection screen. I powered off, connected the phone to the PC, and booted into TWRP (not flashed yet):
Code:
fastboot boot twrp-3.1.1-sanders-r7.img
I did not let TWRP format /data.
Then I started a backup, selecting all partitions, so that I could always go back after flashing TWRP and Magisk.
Does anyone know why backup is stuck at 13%? Last log line says "Backing up System..."
I tapped "Cancel" after two hours. That stopped the progress bar animation, but not the backup itself.
BTW: I used TWRP from this thread, the one in another thread freezes at the TWRP boot logo.
Edit: after two hours I killed the backup by powering down (the only way it seemed). On retry it froze at 21%.
Edit 2: Retried, this time backing up everything except system. No problem. I then tried to backup system. Frozen at 1%. What is the problem here?
Edit 3: Finally, a complete backup of system! Only one to go: system_image. But unfortunately that froze at 0%. Every subsequent try freezes at 1666MB (40%). The card has over 30GB free. I tried backup to USB-OTG, but that also froze.
gewe said:
TWRP backup is frozen at 13% completed. The progress bar is still showing its animation.
I unlocked the bootloader, and then rebooted. Android came up with the language selection screen. I powered off, connected the phone to the PC, and booted into TWRP (not flashed yet):
Code:
fastboot boot twrp-3.1.1-sanders-r7.img
I did not let TWRP format /data.
Then I started a backup, selecting all partitions, so that I could always go back after flashing TWRP and Magisk.
Does anyone know why backup is stuck at 13%? Last log line says "Backing up System..."
I tapped "Cancel" after two hours. That stopped the progress bar animation, but not the backup itself.
BTW: I used TWRP from this thread, the one in another thread freezes at the TWRP boot logo.
Edit: after two hours I killed the backup by powering down (the only way it seemed). On retry it froze at 21%.
Edit 2: Retried, this time backing up everything except system. No problem. I then tried to backup system. Frozen at 1%. What is the problem here?
Edit 3: Finally, a complete backup of system! Only one to go: system_image. But unfortunately that froze at 0%. Every subsequent try freezes at 1666MB (40%). The card has over 30GB free. I tried backup to USB-OTG, but that also froze.
Click to expand...
Click to collapse
Might be due to data partition being encrypted, you cant write anything in it without decrypting it first.
Format data and reboot recovery, then make the backup. You can flash magisk after taking the backup.
Btw r9 new release on its way with some really important changes
CheckYourScreen said:
Might be due to data partition being encrypted, you cant write anything in it without decrypting it first.
Format data and reboot recovery, then make the backup. You can flash magisk after taking the backup.
Btw r9 new release on its way with some really important changes
Click to expand...
Click to collapse
I was not trying to write the backup to the data partition, but to external SD card (tried OTG-USB as well without success).
I have flashed TWRP, formatted the data partition, and flashed Magisk. I have not tried to create a new backup yet. First I want to find out why Magisk does not pass the Safetynet check.
Can't wait to see what r9 brings. Thanks for your efforts. :good:
gewe said:
I was not trying to write the backup to the data partition, but to external SD card (tried OTG-USB as well without success).
I have flashed TWRP, formatted the data partition, and flashed Magisk. I have not tried to create a new backup yet. First I want to find out why Magisk does not pass the Safetynet check.
Can't wait to see what r9 brings. Thanks for your efforts. :good:
Click to expand...
Click to collapse
Magisk won't pass safety net with stock boot.img (kernel). Here is a modified kernel.
https://forum.xda-developers.com/showthread.php?p=73930507
After flashing new kernel Magisk passes no problem.
Sent by way of magic
lilcdroid said:
Magisk won't pass safety net with stock boot.img (kernel). Here is a modified kernel.
https://forum.xda-developers.com/showthread.php?p=73930507
After flashing new kernel Magisk passes no problem.
Sent by way of magic
Click to expand...
Click to collapse
When I flash this my WiFi stops working completely. I'm running aosp extended rom. I'm not sure if I can achieve battery life as good as I can on the stock ROM as I can on this one so im not sure what I should do about that..
Brycearuuni said:
When I flash this my WiFi stops working completely. I'm running aosp extended rom. I'm not sure if I can achieve battery life as good as I can on the stock ROM as I can on this one so im not sure what I should do about that..
Click to expand...
Click to collapse
Sorry I wasn't aware you weren't still on stock. That kernel will only work on stock. I would verify with the maintainer of AOSP extended ROM that the kernel is patched to work with Magisk.
Sent by way of magic
MTP does not work in TWRP on the Pixel 3 and will not work until we have time to update the TWRP MTP implementation. You may still use adb to push and pull files.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, you will need to reflash root.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
3.2.3-0: Initial release for the Pixel 3 devices
Pixel 3:
https://twrp.me/google/googlepixel3.html
https://dl.twrp.me/blueline/
Pixel 3 XL:
https://twrp.me/google/googlepixel3xl.html
https://dl.twrp.me/crosshatch/
Reserved.
You are the man! Cant believe we have TWRP this early! Just in time for the next OTA!
Thank you for this! Great work, it feels like an early Christmas!
All set up with TWRP and rooted again,,even made a back up,,,awesome job to the dev!
Thanks you!
Is anyone having the touchscreen not work after a reboot?
Archangel said:
All set up with TWRP and rooted again,,even made a back up,,,awesome job to the dev!
Click to expand...
Click to collapse
I got twrp up and running on my Pixel 3, but when try to install magisk 17.3 via twrp it says it completes but just bootloops. And I have to restore again. How did you go about it?
code_311 said:
Is anyone having the touchscreen not work after a reboot?
Click to expand...
Click to collapse
On the Pixel 2 XL touch was broken unless you used a custom kernel. I guess it's the same on 3. If you boot TWRP using fastboot it should allow touchscreen.
You would think after buying the Pixel 1, 2 and 3 I would have this whole A/B slot thing down pat but I dont LOL. That did the same thing for me too. I just rebooted into recovery and flashed TWRP again and it has been fine since. I think sometimes it switches slots and that causes the bootloop. I messed around with changing slots and I think I am on slot A and all if fine for me.
Mrnicgeuy633 said:
I got twrp up and running on my Pixel 3, but when try to install magisk 17.3 via twrp it says it completes but just bootloops. And I have to restore again. How did you go about it?
Click to expand...
Click to collapse
---------- Post added at 02:53 PM ---------- Previous post was at 02:52 PM ----------
I had that happen I think once and I just rebooted back into TWRP and it was fine.
code_311 said:
Is anyone having the touchscreen not work after a reboot?
Click to expand...
Click to collapse
Hey guys - I'm a pixel noob and have a quick question about TWRP/Magisk.
I was rooted before TWRP came out so I flashed the stock boot images back to slots A and B. Then I followed steps 2-12 of the following article to install both Magisk and TWRP using temp TWRP. https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
My question is... when I was temp booted into TWRP, and installed the Magisk zip file, it only said that it installed to slot A. But when I was rooted before TWRP released I remember I had to flash the patched boot image to both slots. So using the process I followed, do I have one slot rooted and the other not? If so, is that a problem? Phone seems to work perfectly and root is working.
Sorry if this is a dumb question. I've always been a HTC guy but I'm trying
ktdt00 said:
Hey guys - I'm a pixel noob and have a quick question about TWRP/Magisk.
I was rooted before TWRP came out so I flashed the stock boot images back to slots A and B. Then I followed steps 2-12 of the following article to install both Magisk and TWRP using temp TWRP. https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
My question is... when I was temp booted into TWRP, and installed the Magisk zip file, it only said that it installed to slot A. But when I was rooted before TWRP released I remember I had to flash the patched boot image to both slots. So using the process I followed, do I have one slot rooted and the other not? If so, is that a problem? Phone seems to work perfectly and root is working.
Sorry if this is a dumb question. I've always been a HTC guy but I'm trying
Click to expand...
Click to collapse
No, only the current slot needs to be rooted.
Hello,
I apparently have one of these Pixel 3's that are not working with the current version of TWRP (twrp-3.2.3-0-blueline.img). Yes, I have a 3, not a 3XL. I have done these a hundred times before so I am fairly confident I am not doing anything wrong either. I get the file to load through ADB but on the reboot, it just hangs on the Google screen forever. I have left it for an hour. I have tried everything I can think of. Does anyone have any advice or is in the same situation? I just got my Pixel 3 in the mail on Friday so it's as fresh as they come. I was thinking of fully flashing the TWRP image, but I really don't think it's going to make any difference and I don't want the extra hassle of tracking down the official boot.img from the repo. I guess I will just have to wait until someone who really knows how to debug these comes across one like mine. Clearly, something has changed in what Google is sending out.
For reference:
Android security patch level: September 5,2018
Baseband version: g845-00023-180815-B-4956438
Kernel Version: 4.9.96-g340a9aaf92bc-ab4959234 #0 Thu Aug 16 23:24:20 UTC 2018
Build number: PD1A.180720.031
Much appreciated! $50 donation to anyone who can get me past this and rooted. I'm an old-time Verizon unlimited data planner and I need that tether check disabled.
Is root
To Pixel 3 owners that succesfully rooted, can you share the build.prop here? /system/build.prop
when i booted in to twrp it was encrypted! but i didnt have a PW.... so for everyone to whom that happens, boot up normally and disable your pin ! then you can see your storage in twrp!
i almost flipped this morning hahahaha
Carmenlove said:
Hello,
I apparently have one of these Pixel 3's that are not working with the current version of TWRP (twrp-3.2.3-0-blueline.img). Yes, I have a 3, not a 3XL. I have done these a hundred times before so I am fairly confident I am not doing anything wrong either. I get the file to load through ADB but on the reboot, it just hangs on the Google screen forever. I have left it for an hour. I have tried everything I can think of. Does anyone have any advice or is in the same situation? I just got my Pixel 3 in the mail on Friday so it's as fresh as they come. I was thinking of fully flashing the TWRP image, but I really don't think it's going to make any difference and I don't want the extra hassle of tracking down the official boot.img from the repo. I guess I will just have to wait until someone who really knows how to debug these comes across one like mine. Clearly, something has changed in what Google is sending out.
For reference:
Android security patch level: September 5,2018
Baseband version: g845-00023-180815-B-4956438
Kernel Version: 4.9.96-g340a9aaf92bc-ab4959234 #0 Thu Aug 16 23:24:20 UTC 2018
Build number: PD1A.180720.031
Much appreciated! $50 donation to anyone who can get me past this and rooted. I'm an old-time Verizon unlimited data planner and I need that tether check disabled.
Click to expand...
Click to collapse
Flash the stock boot image. Then try to fastboot boot "path to TWRP". If it still hangs, redownload TWRP and try again. Here's the stock boot for Pixel 3... https://drive.google.com/file/d/1EMkcRkH7n-1bGlVbbzcEJKKPJeE4l9mB/view?usp=drivesdk
jsauder2 said:
Flash the stock boot image. Then try to fastboot boot "path to TWRP". If it still hangs, redownload TWRP and try again. Here's the stock boot for Pixel 3... https://drive.google.com/file/d/1EMkcRkH7n-1bGlVbbzcEJKKPJeE4l9mB/view?usp=drivesdk
Click to expand...
Click to collapse
Thanks! I will give it a try this morning after some coffee. I learned a cool trick last night to get my hotspot to work un-rooted, so I am less desperate than I was last night.
Carm
freebordjunky said:
when i booted in to twrp it was encrypted! but i didnt have a PW.... so for everyone to whom that happens, boot up normally and disable your pin ! then you can see your storage in twrp!
i almost flipped this morning hahahaha
Click to expand...
Click to collapse
Just enter your PIN at the TWRP prompt and it will work.
Mrnicgeuy633 said:
I got twrp up and running on my Pixel 3, but when try to install magisk 17.3 via twrp it says it completes but just bootloops. And I have to restore again. How did you go about it?
Click to expand...
Click to collapse
I have a similar problem. After installing twrp, I can boot to the OS, but Magisk isn't installed and I don't have root. After going back to Twrp and flashing the magisk zip, i can't get past the bootloader screen with a error saying something about failed to load boot.img.
Re-fastboot flashing the patched boot img to both slots brings me back to a rooted state with all magisk modules loaded and applied, but no more twrp. I technically don't need twrp for anything except for nandroid backups, but I guess i could just backup using the adb backup commands and get similar results, right?
Either way, I'm open to suggestions for how to get twrp and magisk working at the same time.