Related
I decided to go to Android 5.0.1 from CM10.2 on my Nexus 4. I guess I did not think it though that well and relied on some crappy guides too much.
I have CWM Recovery 6.4.3 installed, so I thought I just place the factory image on the phone and install it via CWM. So:
1) Copied occam-....tgz on the phone;
2) Rebooted into CWM recovery;
3) Did wipe cache/format system/wipe dalvik;
4) Went to install .zip menu... and figured out that the file is no longer on my phone.
I thought OK, I do it via ADB and cable, so installed ADB, drivers etc. and connected my phone to my computer. However, adb does not see it most of the time (when at logo, bootloader, recovery) and only once adb managed to see it (*some number* device unauthorized) while the phone was at Google logo. And I realized I forgot to set up the USB debug option. What are my options now? I can go into CWM recovery, but ADB does not see the device, as I forgot to set up recovery before flashing. Help, please?
The computer sees the phone as MLP, but I still cannot see its storage in Explorer, so I cannot copy the .zip file.
Update
I managed to make adb recognize the phone, but consistently says that it is not authorized, which makes sense. And there is not way I can mount it as an external storage .
first of all, you have a serious lack of knowledge. not activating USB debugging in android settings has no effect whatsoever on ADB usage ability when you are in recovery mode. Secondly, installing factory images is not done through recovery (the downloaded factory image zip is not even flashable so it would work not in recovery), as factory images also contain RADIO and BOOTLOADER images that are flashable through fastboot (not the recovery). The only thing from factory image that you could flash via recovery is a zip file named - in case of 5.0.1 factory image - image-occam-lrx22c.zip (you can find it if you unpack the downloaded factory image on your PC). And this zip file is a classic ROM (system,userdata,boot,cache,recovery partitions). However, even if you were to flash the correct zip (rather than the zip containing entire factory image complete with ROM, RADIO and BOOTLOADER) Android 5.0 (or 5.0.1) comes with updated RADIO (maybe bootloader aswell, i did not check), so you are supposed to update that aswell prior to switching to 5.0/5.0.1
now here is what you should do:
1. download 5.0.1 factory image from gooogle
2. make sure you have ADB and drivers for Nexus4 correctly set up (in order to check wheter it works go see point 3 of this instruction set)
3. boot to fastboot mode (vol down+power) and check if 'fastboot devices' gives you back device id (you should open command prompt in platform-tools folder, where both adb.exe and fastboot.exe are present)
4. proceed with this instruction, start at step 8 http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/ (in step 11, name of zip file is the one that is INSIDE downloaded factiory image file (image-occam-lrx22c.zip) and you either do the single zip flash or flashing each of .img files separately (system,boot,userdata,cache,recovery)
ps. 1st android 5.0.1 boot after flashing will take up to 15 minutes. (it took 10 in my case)
Update 2
Thanks dzumagos! Sure, I do not claim to be a specialist by any means. I managed to successfully install Cyanogenmod many times, so thought I would give this one a go as well.
I read your post after I fixed the issue. Basically I did exactly what you suggested, but following another guide and it worked fine, also took it around 15 minutes to load the first time. I noticed I do miss a few tricks from Cyanogenmod
Hi,
I did search, but I didn't find any solution to the issue. I got the Nexus 6P 64 GB.
I unlocked my bootloader using the 6p Multitool. Thereafter I used my normal method of fastboot (Minimal ADB) to flash the boot.img from this thread http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344.
After that I flashed TWRP. Basically I followed the instructions here: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928.
But my phone is not booting up.
It gives me this error:
Your device software cannot be checked for corruption. Please lock the bootloader."
But I tried that and it doesn't work. I tried from fastboot restoring to factory, but get the same message.
Please help me!
Did you check the enable oem unlocking in developer settings?
Sent from my Nexus 6P using Tapatalk
Yes. As I said, I achieved the unlock. Now I just can't get back into my phone or recovery or anything other than fastboot (where it says unlock)
isn't "Your device software cannot be checked for corruption. Please lock the bootloader." the new msg on boot when you are unlocked, and you have to wait ~10 secs before it startup ?
After that, I'm stuck on the Google screen. It just goes on and on. Left it for over 20 minutes at one point and it didn't get past it.
Edit: The multicolored animated google screen. The animation just keeps going and going.
Del.
Your issue might be due to the encryption of the phone. Take a look at this thread: http://forum.xda-developers.com/nex...recovery-twrp-2-8-7-0-touch-recovery-t3234976
From this thread:
NOTE: Decrypting data is not supported yet. The Nexus 6P will normally attempt to encrypt the device automatically on first boot. To use TWRP as you normally would, you will have to format data and install a slightly modified boot image with forceencrypt disabled. My Nexus 6P should arrive tomorrow and I will start working on decrypt once I get my hands on it.
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Read through that thread. Part of the issue is that I don't know which variant (MDA89D & MDB08K) I have, or how to find that out seeing as I can't boot into the phone.
If I have the variant I may be able to fix this through the unified toolkit (though I'm not sure of that)
Did you ever fix this?
Try flashing the factory image and starting from scratch. You must have messed up somewhere. Re-download the boot.img from Chainfire's thread, maybe that was corrupt or something.
1. Download the MDB08K factory image (it's not a variant, it's a Marshmallow update) and unzip it.
2. Download the MDB08K boot.zip from Chainfire's modified boot.img thread
3. Download latest SuperSU beta zip
Wipe phone in TWRP, to include format data.
In bootloader, fastboot flash MDB08K
fastboot flash modified boot.img (from zip)
In TWRP, ADB sideload SuperSU
Reboot and it should perform normally.
kibmikey1 said:
1. Download the MDB08K factory image (it's not a variant, it's a Marshmallow update) and unzip it.
2. Download the MDB08K boot.zip from Chainfire's modified boot.img thread
3. Download latest SuperSU beta zip
Wipe phone in TWRP, to include format data.
In bootloader, fastboot flash MDB08K
fastboot flash modified boot.img (from zip)
In TWRP, ADB sideload SuperSU
Reboot and it should perform normally.
Click to expand...
Click to collapse
Thank you for your reply, but I can't get into TWRP either!! Any way for me to restore to factory or do the repairs from in flashboot without the restore?
I ran into the same issue last night trying to install TWRP. I'm still not sure how to get around it but I did get my phone back. you should be able to get to the bootloader (hold the power button until phone turns off, then hold vol up+vol down+power) once there use ADB fastboot to go back to stock.
this link will walk you through what you need. follow step 7.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
here it is as well:
How To Flash The Factory Images (And Return To Stock)
Prerequisites: unlocked bootloader (section 1).
Download the appropriate factory images for your model here.
Unzip the angler-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\angler\).
Once unzipped you should have a folder named angler-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\angler\images\:
bootloader-angler-angler-01.31.img
radio-angler-angler-01.29.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\angler\angler-xxxxxx\ you'll see another zip archive named image-angler-xxxxxx, unzip the contents of that zip into the C:\angler\images\ folder we created before. Now within C:\angler\images\ you should have the following files:
android-info.txt
boot.img
bootloader-angler-angler-01.31.img
cache.img
radio-angler-angler-01.29.img
recovery.img
system.img
userdata.img
vendor.img
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-01.31.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-m8994f-2.6.28.0.65.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash userdata C:\angler\images\userdata.img
fastboot flash vendor C:\angler\images\vendor.img
Thank you. I was eventually able to do tysonwald's suggestion. First I didn't know what my version was, so I couldn't.
At some point I was able to get into the phone with constant gapp errors, check it.
Now my phone is unlocked and rooted. But when I go to settings to security (and when I tried to set up my fingerprint) settings crashes. Any ideas?
There was still some issue. I wiped the phone with the above method again, did NOT set up twrp/root, and everything works. It was something about the custom boot image I guess. Any advice if I want to try to set it up again?
Problem solved. Needed to update to newer image before doing everything. Issue resolve from Heisenberg's thread. Thank you all!
I had the same damn issue last night. Thise bootleg instructions had me flashing build k boot.img on build D. Maybe i wasnt paying attention lol!
I have a very similar problem, I flashed the k boot img. and now I'm stuck in an endless bootloop any idea?
TeriusPR said:
I have a very similar problem, I flashed the k boot img. and now I'm stuck in an endless bootloop any idea?
Click to expand...
Click to collapse
Read thru this guide and follow the instructions to the T. http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I had a similar issue just now where my phone got stuck at the TWRP logo. Selecting the reboot option in download mode refused to remove it. I had to follow step 10 to get my phone back to stock. I'm afraid to try this again now
Is there anyway to know which version do i need to download? i bought the phone already bricked and i am trying to bring it back to life
Hi all im new to this forum. I am having a problem with my N7 im trying to unbrick it with nexus tool kit but at the flashing stage its says FAILED write failed unknown error for all partitions and when I try to flash a rom in twrp it hangs on patching system unconditionally. Has any one come across this problem before.
Update I have no software on my device without a way to flash it all tools including fastboot via comand prompt can't see it in bootloader mode please I really need help
gavster26 said:
Update I have no software on my device without a way to flash it all tools including fastboot via comand prompt can't see it in bootloader mode please I really need help
Click to expand...
Click to collapse
so you can boot to recovery or bootloader?
try nexus root toolkit - there is an option to unbrick. Wipe everything and try to unbrick.
how windows detects your N7? maybe try different usb cable - if not genuine, then cut a lil bit of plastic, so it goes all the way to the usb port
give some photos of what errors do you have in recovery
yaro666 said:
so you can boot to recovery or bootloader?
try nexus root toolkit - there is an option to unbrick. Wipe everything and try to unbrick.
how windows detects your N7? maybe try different usb cable - if not genuine, then cut a lil bit of plastic, so it goes all the way to the usb port
give some photos of what errors do you have in recovery
Click to expand...
Click to collapse
I can boot to bootloader and thats it that tool can't write to any partitions thats what I tried in the first place it erased the partitions but then could not write to them so im left with no system no kernel or recovery
Download drivers from here
Open cmd as admin and type fastboot devices, it should detect your n7 with some numbers and letters.
If you have grouper (wifi) n7 then download recovery here
Go to bootloader, connect n7 with pc and type:
fastboot flash recovery twrp.img
Where twrp.img is the name of recovery file you downloaded.
Then type: fastboot reboot
In cmd you probably have to go to proper folder just use cd.. to go up a folder and cd name of the folder to go to proper folder. I use C:\adb as drivers install right there
yaro666 said:
Download drivers from here
Open cmd as admin and type fastboot devices, it should detect your n7 with some numbers and letters.
If you have grouper (wifi) n7 then download recovery here
Go to bootloader, connect n7 with pc and type:
fastboot flash recovery twrp.img
Where twrp.img is the name of recovery file you downloaded.
Then type: fastboot reboot
In cmd you probably have to go to proper folder just use cd.. to go up a folder and cd name of the folder to go to proper folder. I use C:\adb as drivers install right there
Click to expand...
Click to collapse
Ok thanks I've got twrp to boot and I fastbooted aosp mm system and kernel but it won't boot up and twrp cant mount storage data or cache where to go from here it wont fastboot any stock img
Hi,
I have a problem. I tried to flash stock rom, but I forgot about hifi image.
There's a photo of my phone.
imgur.com/aVUBTRD
I have unlocked bootloader, but I can't flash hifi. "Command not allowed."
I tried method with put microsd card with update.app in dload into smartphone and I when I pressed power button
and VOLUME UP and VOLUME DOWN nothing happened.
I tried just flash all partitions separately, with huawei update extractor, again nothing.
I saw the same problem in this site, but I don't know how he solwed this.
Please help me :crying:
Flash a Huawei recovery, a old one b584 or something, then download b596 DS or b597 SS i don't know your device, extract update.app and copy to sd card dload folder, try to flash it!
persona78 said:
Flash a Huawei recovery, a old one b584 or something, then download b596 DS or b597 SS i don't know your device, extract update.app and copy to sd card dload folder, try to flash it!
Click to expand...
Click to collapse
I flashed recovery and nothing happened, I can't get into recovery mode, only fastboot.
I have the same phone.
adamektv said:
I flashed recovery and nothing happened, I can't get into recovery mode, only fastboot.
I have the same phone.
Click to expand...
Click to collapse
You flashed the recovery and everything say okay, right?
Now flash a rom with dload and the 3 keys, do you know how?
.
persona78 said:
You flashed the recovery and everything say okay, right?
Now flash a rom with dload and the 3 keys, do you know how?
.
Click to expand...
Click to collapse
I don't know, when I pressed three buttons I didn't enter to recovery mode, but to rescue mode, as if recovery wasn't flashed.
adamektv said:
I don't know, when I pressed three buttons I didn't enter to recovery mode, but to rescue mode, as if recovery wasn't flashed.
Click to expand...
Click to collapse
Do you have a dload folder with update.app inside, in sd card?
With that and pressing vol +, vol - and power at same time you enter in flash mode and start to flash the rom
persona78 said:
Do you have a dload folder with update.app inside, in sd card?
With that and pressing vol +, vol - and power at same time you enter in flash mode and start to flash the rom
Click to expand...
Click to collapse
Yes, I have, and it's still not working
I can't charge battery, so i don't think it's software.
Maybe it's motherboard
adamektv said:
Yes, I have, and it's still not working
I can't charge battery, so i don't think it's software.
Maybe it's motherboard
Click to expand...
Click to collapse
How da start it???
adamektv said:
Yes, I have, and it's still not working
I can't charge battery, so i don't think it's software.
Maybe it's motherboard
Click to expand...
Click to collapse
Try opening the phone and disconnecting the battery .. do it if u only gave up with other methods someone said it worked
adamektv said:
Hi,
I have a problem. I tried to flash stock rom, but I forgot about hifi image.
There's a photo of my phone.
imgur.com/aVUBTRD
I have unlocked bootloader, but I can't flash hifi. "Command not allowed."
I tried method with put microsd card with update.app in dload into smartphone and I when I pressed power button
and VOLUME UP and VOLUME DOWN nothing happened.
I tried just flash all partitions separately, with huawei update extractor, again nothing.
I saw the same problem in this site, but I don't know how he solwed this.
Please help me :crying:
Click to expand...
Click to collapse
Hi Have got succeeded or not, if not follow the guide.
Is your phone being detected by PC if yes then you have chances of recovering your phone.
1. Download 15 Seconds ADB and Fastboot Drivers. Visit the official XDA forum for download and installation instructions.
2. Install Huawei HiSuite which will install drivers .
3. If HiSuite doesn't install Install drivers then install universal drivers for your device .
Now connect your device to pc and open HiSuite and click on system recovery it will show options for recovery if it is success then you are fine if not then proceed to this method.
Connect your phone to PC.
Open Command Prompt in the directory where you have extracted the ADB files by holding Shift and Right Mouse Button and finally click Open Command Prompt window here in the context menu.
Completely power off your device.
While holding Volume Down button, connect your device to PC via USB cable to boot to Fastboot Mode.
1. Type the following command in ADB :
Code:
adb devices
If your device is being detected and it shows list of devices attached and its serial number.
2.Now download the firmware of the phone before your phone got bootlooped extract the update using the file here
3.Now copy the following files ( boot.img, recovery.img and system.img ,cust.img ) from the extracted files to the ADB files directory.
4.Now Execute these commands one at a time using the command prompt.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot
5.Now Perform a Factory Reset if your phone got recovered.
If not then download the stock recovery of your Device and try steps 2,3,4.
Even if it doesn't get succeeded then try this option .
If your device got bootlooped while on Lollipop or Marshmallow then you have one more way to recover .
6.Now download the latest TWRP from here and boot into TWRP recovery if you cant enter TWRP recovery for this version then try the previous TWRP versions like 2.8.7 ,
7.Use the following command to flash the TWRP recovery
Code:
fastboot flash recovery twrp.img
8.Then download any of the custom ROMs or ask any of the XDA members for TWRP backup for your device and flash them through Recovery.
Then Reboot your Device.
You would most probably recover your device from any of the above methods . I too had the same problem and My device was use less for almost 6 months but after several trial and error methods my device got recovered.
Credits:
1.https://forum.xda-developers.com/honor-4c/how-to/huawei-honor-4c-index-troubleshooting-t3293110
2.https://forum.xda-developers.com/showthread.php?t=2433454
miststudent2011 said:
Hi Have got succeeded or not, if not follow the guide.
Is your phone being detected by PC if yes then you have chances of recovering your phone.
1. Download 15 Seconds ADB and Fastboot Drivers. Visit the official XDA forum for download and installation instructions.
2. Install Huawei HiSuite which will install drivers .
3. If HiSuite doesn't install Install drivers then install universal drivers for your device .
Now connect your device to pc and open HiSuite and click on system recovery it will show options for recovery if it is success then you are fine if not then proceed to this method.
Connect your phone to PC.
Open Command Prompt in the directory where you have extracted the ADB files by holding Shift and Right Mouse Button and finally click Open Command Prompt window here in the context menu.
Completely power off your device.
While holding Volume Down button, connect your device to PC via USB cable to boot to Fastboot Mode.
1. Type the following command in ADB :
Code:
adb devices
If your device is being detected and it shows list of devices attached and its serial number.
2.Now download the firmware of the phone before your phone got bootlooped extract the update using the file here
3.Now copy the following files ( boot.img, recovery.img and system.img ,cust.img ) from the extracted files to the ADB files directory.
4.Now Execute these commands one at a time using the command prompt.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot
5.Now Perform a Factory Reset if your phone got recovered.
If not then download the stock recovery of your Device and try steps 2,3,4.
Even if it doesn't get succeeded then try this option .
If your device got bootlooped while on Lollipop or Marshmallow then you have one more way to recover .
6.Now download the latest TWRP from here and boot into TWRP recovery if you cant enter TWRP recovery for this version then try the previous TWRP versions like 2.8.7 ,
7.Use the following command to flash the TWRP recovery
Code:
fastboot flash recovery twrp.img
8.Then download any of the custom ROMs or ask any of the XDA members for TWRP backup for your device and flash them through Recovery.
Then Reboot your Device.
You would most probably recover your device from any of the above methods . I too had the same problem and My device was use less for almost 6 months but after several trial and error methods my device got recovered.
Credits:
1.https://forum.xda-developers.com/honor-4c/how-to/huawei-honor-4c-index-troubleshooting-t3293110
2.https://forum.xda-developers.com/showthread.php?t=2433454
Click to expand...
Click to collapse
I have already done this and still stuck in rescue
adamektv said:
I have already done this and still stuck in rescue
Click to expand...
Click to collapse
Did you try flashing different variant ROM ie different builds?
Actually I too got the same problem bootlooped on LP but cant flash the LP ROM back so I flashed different Region ROM.
Give a try to TWRP Method It should give you success.
Imp:
Try the previous ROM where you got Bootloop, or the version earlier to it.If it doesn't succeed try the rom which you got initially on your mobile.
PS: If your phone is being detected by your PC you have good chances of recovering your phone.
Via Magisk Manager:
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode
REQUIREMENTS -
1 - Setup adb and fastboot on your PC.
2- Stock boot image (boot.img) of your device (extract file from factory image android P)
3 - Last Magisk Manager (v 5.8.3)
4 - Active Internet connection
5 - Active mind and patience.
6 - Devices must is unlock bl.
This Boot-Image is for boot android P PPR1.180610.009:
https://drive.google.com/open?id=166pE9aMk-jqns3JM74enFhsaDY6-c3yJ
Magisk Manager
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
==================================================
Step 1: Patching the stock boot.img
1- Copy the stock boot.img of your device to your phone's internal storage.
2- Install the latest Magisk Manager
3- Launch Magisk Manager app
4- If prompted to install Magisk, select NO THANKS
5- If you're planning to flash the patched boot image,For normal users leave it as the default .img
6-Press Setting>Update Channel>Beta
7- Press Install > Install > Patch Boot Image File, and select your stock boot image file
Navigate to the location of the stock boot.img you copied earlier on, then Select it
8- Magisk Manager should begin downloading the magisk zip file used for patching
9- Once download is complete, MagiskManager will automatically patch the boot file and store it under SDcard/MagiskManager/patched_boot.img
Step 2: Flashing the patched boot.img
1- Copy the patched_boot.img from your phone's internal storage to folder adb or platform-tools on PC (directory>SDcard/MagiskManager/patched_boot.img)
2- You could also use Fastboot to flash the patched_boot.img or boot.img (if you've renamed then the command must reflect the file name) as outlined below
How to Flash patched_boot.img using Fastboot
1- Setup adb and fastboot on your PC.
2- Unlock the phone's Bootloader (if its not unlocked)
3-Re-enable USB debugging on the phone
4- Connect the phone to the PC via USB cord
5- Boot into fastboot mode.
code
-adb reboot bootloader
6- Flash the patched_boot and reboot by typing in the commands below into adb CMD prompt window and hitting Enter after each line -
Quote:
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
-Verify root using Root Checker
Try at your own Risk
CREDITS
@topjohnwu (Magisk)
Sadly goes into a bootloop for me - no idea why though
This worked for me. I had magisk installed and took the pie update. No more root. D/l the factory image and extracted the boot image to the files folder...pissmeoff they changed the name of the icon... and magisk patched the image and saved it in its folder. Found the file, moved it to the laptop then flashed it.
reawo said:
Sadly goes into a bootloop for me - no idea why though
Click to expand...
Click to collapse
I think you made a mistake.
I always did that method pre Pie and it always worked but now I end up in a bootloop and I did everything according to guide
reawo said:
I always did that method pre Pie and it always worked but now I end up in a bootloop and I did everything according to guide
Click to expand...
Click to collapse
I think you use my file(boot.img) for patch_boot.img from magisk manager.
I think you must check your build number devices.
You must use file boot.img from your factory image for root.
9.0.0 (PPR1.180610.009, Aug 2018) >This is version for my devices
9.0.0 (PPR1.180610.011, Aug 2018, Telstra) >?
hey mate thanks for the input, I got a normal non testra (whatever that is) taimen - tried your boot.img and before that I tried the one from the factory image, both result in a boot loop.
I went through all stages of the Android p beta and in the end, to try solve this, I also non wipe flashed the factory image all to get the same result
could you sent me a drive Link to the patched version of yours or something?
reawo said:
hey mate thanks for the input, I got a normal non testra (whatever that is) taimen - tried your boot.img and before that I tried the one from the factory image, both result in a boot loop.
I went through all stages of the Android p beta and in the end, to try solve this, I also non wipe flashed the factory image all to get the same result
could you sent me a drive Link to the patched version of yours or something?
Click to expand...
Click to collapse
This is file patch_boot.img from my devices.
https://drive.google.com/open?id=1nVEpoGam-VY1YT3GBbG6HNfhnT2NqRin
newyesor said:
This is file patch_boot.img from my devices.
https://drive.google.com/open?id=1nVEpoGam-VY1YT3GBbG6HNfhnT2NqRin
Click to expand...
Click to collapse
Also doesnt work, i thought so - didnt do anything different than when it worked - no idea why it doesn't though
Is there a way to see or read out any protocols regarding this?
I receive also a bootloop and I didnt make any mistake. I also used this method pre Pie, I read that alot of users have problems with rooting Pie atm, even with TWRP
reawo said:
Also doesnt work, i thought so - didnt do anything different than when it worked - no idea why it doesn't though
Is there a way to see or read out any protocols regarding this?
Click to expand...
Click to collapse
You use adb last version for flash patch_boot.img ?
I think you should flash factory image new again and factory reset your devices.
You are use stock kernel or other kernel on your devices.
newyesor said:
You use adb last version for flash patch_boot.img ?
I think you should flash factory image new again and factory reset your devices.
You are use stock kernel or other kernel on your devices.
Click to expand...
Click to collapse
I downloaded all the latest adb and fastboot. Never touched kernel or did custom recovery, always used the magisk method since i am on a pixel device. i also got the issue that my pc doesnt recognize my pixel from time to time, you think i should do a complete wipe?
I don't sure.
You are use platfrom-tool from sdk lastversion?(for flash via fastboot mode)
@reawo
I think you should flash factory image new again and factory reset your devices.
Step 1: Patching the stock boot.img
1- Copy the stock boot.img of your device to your phone's internal storage.
2- Install the latest Magisk Manager
3- Launch Magisk Manager app
4- If prompted to install Magisk, select NO THANKS
5- If you're planning to flash the patched boot image,For normal users leave it as the default .img
6-Press Setting>Update Channel>Beta ,and close this app.****
7- Open app again and Press Install > Install > Patch Boot Image File, and select your stock boot image file
Navigate to the location of the stock boot.img you copied earlier on, then Select it
8- Magisk Manager should begin downloading the magisk zip file used for patching (This process is not failed)***
9- Once download is complete, MagiskManager will automatically patch the boot file and store it under SDcard/MagiskManager/patched_boot.img
Step 2: Flashing the patched boot.img
1- Copy the patched_boot.img from your phone's internal storage to folder adb or platform-tools on PC (directory>SDcard/MagiskManager/patched_boot.img)
2- You could also use Fastboot to flash the patched_boot.img or boot.img (if you've renamed then the command must reflect the file name) as outlined below
How to Flash patched_boot.img using Fastboot
1- Setup adb and fastboot on your PC.
2- Unlock the phone's Bootloader (if its not unlocked)
3-Re-enable USB debugging on the phone
4- Connect the phone to the PC via USB cord
5- Boot into fastboot mode.
code
-adb reboot bootloader
6- Flash the patched_boot and reboot by typing in the commands below into adb CMD prompt window and hitting Enter after each line -
Quote:
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
-Verify root using Root Checker
Try at your own Risk
Will work on the verizon variant (bootloader locked)?
sabi95190 said:
Will work on the verizon variant (bootloader locked)?
Click to expand...
Click to collapse
Nope. If it were that easy for bootloader locked Verizon phones, it would have been done months ago.
What happens if you lock the bootloader after all of this?
DarkSilentSC said:
What happens if you lock the bootloader after all of this?
Click to expand...
Click to collapse
You'll wipe the phone, lose root, and be stock.
DarkSilentSC said:
What happens if you lock the bootloader after all of this?
Click to expand...
Click to collapse
When still rooted and modified? You might very well brick it. Relocking while modified is borderline insanity.
TonikJDK said:
When still rooted and modified? You might very well brick it. Relocking while modified is borderline insanity.
Click to expand...
Click to collapse
"Borderline"???? More like certifiably insane! ?