Related
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
This ISN'T Resolved. I get errors when attempting to fastboot the stock image
~/Desktop/adb-fastboot/adb reboot bootloader
brings about the following error
"error: device not found"
I was already in bootloader and tried:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
I get:
error: cannot load '/Users/grnmons/Desktop/adb-fastboot/boot.img'
If anybody has any ideas please let me know, I really don't know what to do at this point.
grnmons said:
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
If anybody has any ideas please let me know, I really don't know what to do at this point. Plan B is to use a PC which I can only access later in the week. If you know someone, or have a link I would really appreciate it. Also ask me anything if it can help make this clearer.
Thanks
Click to expand...
Click to collapse
Okay your bootloader is unlocked which is good, but your MAC doesn't see your phone in bootloader mode?
grnmons said:
Plan B is to use a PC which I can only access later in the week.
Click to expand...
Click to collapse
Can you bootcamp or use a virtual machine?
grnmons said:
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
If anybody has any ideas please let me know, I really don't know what to do at this point. Plan B is to use a PC which I can only access later in the week. If you know someone, or have a link I would really appreciate it. Also ask me anything if it can help make this clearer.
Thanks
Click to expand...
Click to collapse
Wrong section..but
I would def use a PC and use Odin ! Make your life easier...it takes like 3-5 Mins..takes it to stock!
Sent from my Galaxy Nexus using xda premium
All you have to do is fastboot flash those stock images of 4.0.2 google gave us. There's not even any need for Odin. You can do this right on your Mac.
Sent from my Galaxy Nexus using Tapatalk
Please uninstall and reinstall your phones drivers. Your just soft bricked is all. Once your computer sees the device you should be good.
sent from the Almighty One himself....
borgey said:
All you have to do is fastboot flash those stock images of 4.0.2 google gave us. There's not even any need for Odin. You can do this right on your Mac.
Click to expand...
Click to collapse
I can't seem to figure out how to do that. Seems like that's what got me here in the first place, the mac version might be missing files I'm missing the steps to actually do that.
Can't find any forum/site/guide that tells me how to do that. Does anybody have this?
grnmons said:
I can't seem to figure out how to do that. Seems like that's what got me here in the first place, the mac version might be missing files I'm missing the steps to actually do that.
Can't find any forum/site/guide that tells me how to do that. Does anybody have this?
Click to expand...
Click to collapse
fastboot flash (google on how to use these)
you do them when you're in bootloader mode. you need to have a ADB/Fastboot environment set up (look at root guides and do step one of it..... verifying the part of getting the environment, ignore drivers)
stock images are here: http://code.google.com/android/nexus/images.html
zephiK said:
fastboot flash (google on how to use these)
you do them when you're in bootloader mode. you need to have a ADB/Fastboot environment set up (look at root guides and do step one of it..... verifying the part of getting the environment, ignore drivers)
stock images are here: http://code.google.com/android/nexus/images.html
Click to expand...
Click to collapse
Thanks. Can you confirm that these are the steps?
1) Download the latest stock image( i will leave finding that image to you since this post can become outdated)
2) Unzip the files, and place the images into the adb-fastboot folder you created on your desktop above.
3) Open a terminal and use the following commands:
Code:
~/Desktop/adb-fastboot/adb reboot bootloader
4) Wait for bootloader to reboot on phone.
5) Then, in terminal use the following commands:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
~/Desktop/adb-fastboot/fastboot flash system ~/Desktop/adb-fastboot/system.img
~/Desktop/adb-fastboot/fastboot flash recovery ~/Desktop/adb-fastboot/recovery.img
~/Desktop/adb-fastboot/fastboot flash userdata ~/Desktop/adb-fastboot/userdata.img
~/Desktop/adb-fastboot/fastboot erase cache
~/Desktop/adb-fastboot/fastboot oem lock
6) Reboot to System, and you should be returned to Stock and Unrooted
~/Desktop/adb-fastboot/adb reboot bootloader
brings about the following error
"error: device not found"
I was already in bootloader and tried:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
I get:
error: cannot load '/Users/grnmons/Desktop/adb-fastboot/boot.img'
anybody have any other suggestions to this? or a follow up?
It should be easy to fix. You do not seem to have the correct driver installed.
Sent from my Galaxy Nexus using xda premium
Understood, I think I definitely did a few things wrong here. But my problem requires some kind of steps to solve. I don't mean to sound lazy but I've been running around the forums for awhile and I'm in way over my head, I was hoping someone could just list a few steps, links, SOMETHING. I'm looking for solvency here.
grnmons said:
Understood, I think I definitely did a few things wrong here. But my problem requires some kind of steps to solve. I don't mean to sound lazy but I've been running around the forums for awhile and I'm in way over my head, I was hoping someone could just list a few steps, links, SOMETHING. I'm looking for solvency here.
Click to expand...
Click to collapse
reinstall the android sdk from here that will get your drivers in order so your computer can see your phone
then fastboot flash recovery
then manually flash su (attached)
ogdobber said:
reinstall the android sdk from here that will get your drivers in order so your computer can see your phone
then fastboot flash recovery
then manually flash su (attached)
Click to expand...
Click to collapse
Thanks muchly, I feel like I'm getting closer but could you elaborate on the manual flash su step? My **** is all over the place now, my desktop is littered with files, should I be in recovery for this or still fastboot? and what is the command if you have?
grnmons said:
Thanks muchly, I feel like I'm getting closer but could you elaborate on the manual flash su step? My **** is all over the place now, my desktop is littered with files, should I be in recovery for this or still fastboot? and what is the command if you have?
Click to expand...
Click to collapse
download the gnex-su.zip and put in in the root of your sd card. then in recovery select "-install zip from sdcard" then "-choose zip from sdcard" then select the gnex-su.zip. this will give you root and install the superuser app
not to get ahead (previous post), but after your computer recognizes the phone you need to flash clockwork recovery
you need to open a terminal in the platform-tools folder of the sdk (also put the recovery.img there) and then
Code:
fastboot flash recovery name-of-recovery.img
Thanks for your help ogdobber, I'm incredibly frustrated and you must be too trying to help me, but I must have done something wrong as after I flash recovery, i still cannot access it - it continues to hang out in the Google screen.
Let me go through my steps with you and you tell me what I might have done wrong. So with my bricked phone, 1. I clicked your link and updated my SDK.
There's no indication that I did anything right here, it just shows that everything is installed and that's all I think I need here.
2. Opened up terminal fastboot flash boot (in this case) bootloader-toro-primekk15.img DONE!
3. Fastboot flash recovery (in this case) recovery-clockwork-5.0.2.0-crespo.img
DONE!
Then... nothing. Recovery doesn't load for me. Just get a boot loop. Anything I might have done wrong prior or inbetween these steps? Also, besides flashing and running commands off terminal - i assume this is considered computer recognizes my phone. Could the problem be there?
Just got your last post, I'm unfamiliar with SDK but I've since put the recovery file in there, not sure how to flash recovery. I have tried flashing recovery through terminal and surprisingly it says "-bash: fastboot: command not found"
grnmons said:
Thanks for your help ogdobber, I'm incredibly frustrated and you must be too trying to help me, but I must have done something wrong as after I flash recovery, i still cannot access it - it continues to hang out in the Google screen.
Let me go through my steps with you and you tell me what I might have done wrong. So with my bricked phone, 1. I clicked your link and updated my SDK.
There's no indication that I did anything right here, it just shows that everything is installed and that's all I think I need here.
2. Opened up terminal fastboot flash boot (in this case) bootloader-toro-primekk15.img DONE!
3. Fastboot flash recovery (in this case) recovery-clockwork-5.0.2.0-crespo.img
DONE!
Then... nothing. Recovery doesn't load for me. Just get a boot loop. Anything I might have done wrong prior or inbetween these steps? Also, besides flashing and running commands off terminal - i assume this is considered computer recognizes my phone. Could the problem be there?
Click to expand...
Click to collapse
that is for the nexus s
check your pm
ogdobber said:
that is for the nexus s
check your pm
Click to expand...
Click to collapse
If you are still having problems ...like I said before ...use Odin......since the simple process of fastboot is not working properly for you.Odin makes things so Much easier
Sent from my Galaxy Nexus using xda premium
Hi guys,
I have already read dozens of pages regarding the procedure to root my new Htc M8 but I am still a bit confused.
In the picture attached you can see the status of my phone, I think the previous owner has already unlocked it .
What I am kindly ask you is to help me to find the next step to root the phone. I suppose that I have to download a TWRP file, copy it to the internal memory of the phone and then chose "Recovery" but I'm not sure and I don't want to make a disaster !!!
Can U help me? I'm on Mac.
thanks
ciao
fausto
now flash any custom recovery and then flash supersu.zip from recovery to make your handset root
fcasini said:
I suppose that I have to download a TWRP file, copy it to the internal memory of the phone and then chose "Recovery"
Click to expand...
Click to collapse
That is not the proper way to install TWRP, and I don't know how you got that notion.
The proper way to install TWRP is described on the TWRP website (see under "Fastboot Install Method"): https://twrp.me/devices/htconem8gsm.html
fcasini said:
Hi guys,
I have already read dozens of pages regarding the procedure to root my new Htc M8 but I am still a bit confused.
In the picture attached you can see the status of my phone, I think the previous owner has already unlocked it .
What I am kindly ask you is to help me to find the next step to root the phone. I suppose that I have to download a TWRP file, copy it to the internal memory of the phone and then chose "Recovery" but I'm not sure and I don't want to make a disaster !!!
Can U help me? I'm on Mac.
thanks
ciao
your lucky to have s-off already phone lol, install TWRP via fastboot command then flash supersu in TWRP
Click to expand...
Click to collapse
ok, thanks to all,
now I have downloaded the TWRP.IMG, adb and Fastboot files and I am approaching to connect my phone to mac, open terminal and then
./adb reboot bootloader
./fastboot twrp.img
SuperSU is already installed on the phone, so I think I don't need to download and install again.
Is it right?
Once Flashed the twrp image, phone will be wiped?
Thank you again, you help and patience is very appreciated
ciao
fausto
fcasini said:
SuperSU is already installed on the phone, so I think I don't need to download and install again.
Is it right?
Click to expand...
Click to collapse
Did you check to see if the phone was still rooted? It was clearly modded by the previous owner, so may still be rooted. You can check with one of the root checker apps; or simply any app that requires root (such as Titanium Backup).
Although its also possible they unrooted and left the SuperSU app still installed. Just having the app installed does not in itself give you root, the binary also has to be installed. So if that is the case (no root) then UES you will still need to download the current version SuperSU and flash in TWRP in order to gain root.
fcasini said:
Once Flashed the twrp image, phone will be wiped?
Click to expand...
Click to collapse
Nope, TWRP just overwrites the recovery partition. Completely separate partition from user data, ROM, etc.
Regardless, I still highly recommend you backup any personal data that is important to you (preferably backup to an off-phone location) before doing any mods, just in case something goes wrong.
Hi Redpoint73, thanks for the useful info.
I am pretty sure that it is unrooted. I unsuccessfully tried to install Titanium Backup and also the SuperSu application don't start because of the missing of root permission.
Then If I have understood your suggestions:
1) connect the phone with debug Usb ON
2) type ./fastboot twrp.img
3) Phone off
4) Power+Vol-
5) Fastboot menu
6) Recovery+Power
Is it right?
And then? What's happen after? The phone will reboot himself?
thanks
ciao
My comments below in red font:
fcasini said:
Then If I have understood your suggestions:
1) connect the phone with debug Usb ON Doesn't matter if Debugging is on, this only enables adb commands. Fastboot commands work regardless of debugging on or not. But Debugging on is good to have in other situations (so I usually leave it on).
2) type ./fastboot twrp.img Don't know where you got this syntax from. Its not correct. The command given on the link I gave previously (Post #3) states: fastboot flash recovery twrp.img
If the syntax is not exactly right, the command will fail or perform the wrong action. Also note that the TWRP img filename in the command needs to match the actual TWRP file you with to flash. You will notice when you download the TWRP file, the file name is actually much longer than just "twrp.img". So you can either type that whole filename exactly, or change the name of the file to actually be "twrp.img" (with no quotes)
3) Phone off
4) Power+Vol-
5) Fastboot menu
6) Recovery+Power
Click to expand...
Click to collapse
At some point before Step 6, you need to put the SuperSU zip on the phone. You can download it direct to your phone from here: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
After step 6 (boot into TWRP) select "Install" from the main menu. Navigate to the SuperSU zip, then select it. Once its flashed, reboot. You should be rooted and good to go.
redpoint73 said:
My comments below in red font:
fastboot flash recovery twrp.img.
Click to expand...
Click to collapse
redpoint73, I need your precious help
I have connected my phone to the Mac but with the command "./fastboot flash recovery twrp.img" I get the message "Permission denied".
Even with other command like ./reboot or ./adb devices...
What is going wrong? Maybe I've missed something?
I followed also the instruction here https://www.youtube.com/watch?v=WOW38u-02I0 but without luck...
Help!!!
ciao
fausto
fcasini said:
redpoint73, I need your precious help
I have connected my phone to the Mac but with the command "./fastboot flash recovery twrp.img" I get the message "Permission denied".
Even with other command like ./reboot or ./adb devices...
What is going wrong? Maybe I've missed something?
Click to expand...
Click to collapse
I don't know anything about Mac's, so I probably will be of limited help in that regard.
Did you install the Android SDK, or other Mac friendly adb-fastboot environment?
it is really strange...
I have installed both Adb and fastboot but whenever I try to flash the image file I get the same error: Permission denied.
With Mac there is no need of driver to work and I don't know ho to proceed.
Thank you redpoint73, your help has been very appreciated, I will search again on the net to solve the problem.
Have a nice day
ciao
fausto
fcasini said:
it is really strange...
I have installed both Adb and fastboot but whenever I try to flash the image file I get the same error: Permission denied.
Click to expand...
Click to collapse
Make sure you are running fastboot command while the phone is in bootloader-fastboot mode. Run adb command while booted into OS (and Debugging needs to be enabled in Settings).
You are in the correct directory (where your fastboot and adb executables are located) when running the commands?
Try finding a thread specific to running adb/fastboot on a Mac (probably doesn't need to be M8 specific) and reading up or post a link to this thread. This may be some Mac-specific nuance that I am not knowledgeable in.
thanks again dear redpoint73,
I checked again and It seems to be all right but it doesn't work.
I have just one doubt yet. Perhaps I have to flash a root file like this http://www.androidrevolution.org/do...le=Android_Revolution_HD_Root_and_BusyBox.zip and then supersu.img through recovery menu?
Could it be the way to gain the permission?
thanks
ciao
Hi Guy!
It's been a while since I've posted on here, last time was the HTC HD2 days, Remember that?!
Anyways I've started unlocking my LG G4 H815 after 2 years, 2nd motherboard and new screen. I've used the official route through LG and got to the TWRP installation and hit an issue.
I'm running the command prompt in adb installation path, using the latest version of TWRP which was renamed like the guide said. Using Windows 10 which gives all the drivers needed to allow the phone to be recognised when I type in "reboot bootloader".
Issue is when trying to install TWRP through command prompt "fastboot flash recovery twrp-3.1.0.0-h815.img"
I get "invalid destination or file cannot be found" I've tried different files, checked I'm booting from the right place, IMG file is in ADB/fastboot folder also. Debugging and what not all enabled.
So I'm out of idea? Help
Dingo
You need a microsd card installed on the phone and a copy of twrp image on the microsd card - you can also add a copy of supersu zipfile if you want to install root
fastboot boot twrp-2.8.7.1-h811.img (phone itself boots TWRP)
from phone itself:
In TWRP hit Install > Images... (bottom right corner) > select TWRP.img on ext sdcard > select "recovery" > swipe for permanent install of twrp
for root: Hit the Home button > Install > select SuperSU zip on external sdcard > swipe
Reboot into Android. (if TWRP asks if you want to install SU, HIT NO!!!)
if you do not have an external sdcard to save SuperSU and the TWRP.img onto.. you will need to skip saving the files to sdcard until AFTER you fastboot OEM unlock and boot into TWRP. After fastboot booting TWRP you can use adb push to put SuperSU and TWRP.img onto the internal sdcard to install with TWRP. Or you can use the MTP mount option in TWRP and drag n' drop the files from the computer to the phone. You cannot store the files on the internal sdcard before the OEM unlock because OEM unlock wipes all your data.
These are for h811 g4 but should work fine for you, instructions can be found here:
https://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Dingo88 said:
Hi Guy!
It's been a while since I've posted on here, last time was the HTC HD2 days, Remember that?!
Anyways I've started unlocking my LG G4 H815 after 2 years, 2nd motherboard and new screen. I've used the official route through LG and got to the TWRP installation and hit an issue.
I'm running the command prompt in adb installation path, using the latest version of TWRP which was renamed like the guide said. Using Windows 10 which gives all the drivers needed to allow the phone to be recognised when I type in "reboot bootloader".
Issue is when trying to install TWRP through command prompt "fastboot flash recovery twrp-3.1.0.0-h815.img"
I get "invalid destination or file cannot be found" I've tried different files, checked I'm booting from the right place, IMG file is in ADB/fastboot folder also. Debugging and what not all enabled.
So I'm out of idea? Help
Dingo
Click to expand...
Click to collapse
You are using an abandoned version please use the latest beta in the official TWRP thread
.
Sent from my LG-H815 using XDA Labs
Dingo88 said:
Hi Guy!
It's been a while since I've posted on here, last time was the HTC HD2 days, Remember that?!
Anyways I've started unlocking my LG G4 H815 after 2 years, 2nd motherboard and new screen. I've used the official route through LG and got to the TWRP installation and hit an issue.
I'm running the command prompt in adb installation path, using the latest version of TWRP which was renamed like the guide said. Using Windows 10 which gives all the drivers needed to allow the phone to be recognised when I type in "reboot bootloader".
Issue is when trying to install TWRP through command prompt "fastboot flash recovery twrp-3.1.0.0-h815.img"
I get "invalid destination or file cannot be found" I've tried different files, checked I'm booting from the right place, IMG file is in ADB/fastboot folder also. Debugging and what not all enabled.
So I'm out of idea? Help
Dingo
Click to expand...
Click to collapse
i beleive win 10 gives problems and must use USB 2.0
Hi Cheers for replys,
Had an issue on Win7 where I couldn't make "android" drivers work, both LG usb and Google driver update failed miserably.
On the TWRP I've used the latest version and a previous version. Placed it within the ADB folder and on the SD card both came out saying , "invalid file destination or something like that" am I missing a command prompt for the phone to access the SD card?
Thanks Dingo88
Dingo88 said:
Hi Cheers for replys,
Had an issue on Win7 where I couldn't make "android" drivers work, both LG usb and Google driver update failed miserably.
On the TWRP I've used the latest version and a previous version. Placed it within the ADB folder and on the SD card both came out saying , "invalid file destination or something like that" am I missing a command prompt for the phone to access the SD card?
Thanks Dingo88
Click to expand...
Click to collapse
It seems you really miss something. Read carefully. Fastboot flash will not work!
You just need to reboot into bootloader then using
fastboot boot twrp.img
Then you should see TWRP. Then you would flash TWRP from within TWRP. That's all described in the official install guide.
Btw: Exactly because of your problems with drivers etc I created FWUL ( https://tinyurl.com/FWULatXDA )..
The latest TWRP beta is 3.1.1 btw.
.
Sent from my LG-H815 using XDA Labs
Hi Steadfaster, cheers for the reply.
Im definitely doing something wrong, im still at a loss.
I've unlocked the boot loader, followed by "adb reboot bootloader" which takes me into the bootloader.
Then with the lgg4-twrp.img placed in both the SD and ADB location I type "fastboot boot lgg4-twrp.img. I get no luck!
Pic attached! Apologies if your screaming at your screen!
Dingo88 said:
Hi Steadfaster, cheers for the reply.
Im definitely doing something wrong, im still at a loss.
I've unlocked the boot loader, followed by "adb reboot bootloader" which takes me into the bootloader.
Then with the lgg4-twrp.img placed in both the SD and ADB location I type "fastboot boot lgg4-twrp.img. I get no luck!
Pic attached! Apologies if your screaming at your screen!
Click to expand...
Click to collapse
Rename the downloaded twrp to twrp.img no dashes. and it has to be in the same folder where your adb exe is.
.
Sent from my LG-H815 using XDA Labs
Dingo88 said:
Hi Steadfaster, cheers for the reply.
Im definitely doing something wrong, im still at a loss.
I've unlocked the boot loader, followed by "adb reboot bootloader" which takes me into the bootloader.
Then with the lgg4-twrp.img placed in both the SD and ADB location I type "fastboot boot lgg4-twrp.img. I get no luck!
Pic attached! Apologies if your screaming at your screen!
Click to expand...
Click to collapse
could be corrupted download verify md5 with latest 3.1.1 as named and downloaded using 61ed0c81afb750535bdb71dfb0298149 md5 key
then simplify things, rename file to twrp.img to avoid typing errors
I have a stock Pixel 2xl running android 10. Can't root it, no matter what i try. Any help would be greatly appreciated. Thanks
grunt0300 said:
I have a stock Pixel 2xl running android 10. Can't root it, no matter what i try. Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Is your bootloader unlocked?
Badger50 said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Yes it is.
grunt0300 said:
Yes it is.
Click to expand...
Click to collapse
Ok. So you've installed the latest platform-tools on your pc?
Downloaded the factory image that coincides with your current build?
Extracted the factory image, then extracted the image.zip, and moved the boot.img to your phones internal storage?
Magisk manager is installed on your phone. Then you patched the boot.img, and then moved it to your pc platform-tools?
Put your phone into bootloader mode, opened a command prompt on you platform-tools folder, typed in "fastboot devices" to make sure your pc recognizes your phone?
Then fastbooted your patched boot.img to both slots with...
fastboot flash boot magisk_patched.img --slot=all
And then booted up with root?
What happens when you run the fastboot command "fastboot flashing unlock"?
Badger50 said:
Ok. So you've installed the latest platform-tools on your pc?
Downloaded the factory image that coincides with your current build?
Extracted the factory image, then extracted the image.zip, and moved the boot.img to your phones internal storage?
Magisk manager is installed on your phone. Then you patched the boot.img, and then moved it to your pc platform-tools?
Put your phone into bootloader mode, opened a command prompt on you platform-tools folder, typed in "fastboot devices" to make sure your pc recognizes your phone?
Then fastbooted your patched boot.img to both slots with...
fastboot flash boot magisk_patched.img --slot=all
And then booted up with root?
Click to expand...
Click to collapse
Sorry, i've been trying to root this phone all afternoon and i'm burnt out. Maybe tomorrow. Thanks
OK, i tried to root it again, and this is what i got....Your device is corrupt. It can't be trusted and may not work properly. The phone is not recognized by my pc. I can get into "bootloader mode", but can't do a thing with it. I could sure use some help. In the meantime, i'll pop the sim card into my trusty nexus 6, and wait to hear from one of you nice people. Thanks.
grunt0300 said:
OK, i tried to root it again, and this is what i got....Your device is corrupt. It can't be trusted and may not work properly. The phone is not recognized by my pc. I can get into "bootloader mode", but can't do a thing with it. I could sure use some help. In the meantime, i'll pop the sim card into my trusty nexus 6, and wait to hear from one of you nice people. Thanks.
Click to expand...
Click to collapse
Go to the guide in my signature, follow the step by step instructions there.
Make sure you have done the following:
-SDK tools are up to date,
-the proper platform folders are unzipped (there are two),
-you have a couple different USB cables handy.
Az Biker said:
Go to the guide in my signature, follow the step by step instructions there.
Make sure you have done the following:
-SDK tools are up to date,
-the proper platform folders are unzipped (there are two),
-you have a couple different USB cables handy.
Click to expand...
Click to collapse
I just put the sim card back into the pixel 2xl, and it booted up as if it was brand new. Plugged it into pc, got into bootloader mode, typed in command "adb devices", and it recognized the phone. I have all those files downloaded onto my desktop, so what's my next move?
grunt0300 said:
I just put the sim card back into the pixel 2xl, and it booted up as if it was brand new. Plugged it into pc, got into bootloader mode, typed in command "adb devices", and it recognized the phone. I have all those files downloaded onto my desktop, so what's my next move?
Click to expand...
Click to collapse
Like @Az Biker said, follow the guide in his signature :good:
Badger50 said:
Like @Az Biker said, follow the guide in his signature :good:
Click to expand...
Click to collapse
Doesn't work. I can't "fastboot" into anything. When i try, the pc stops recognizing the phone.
grunt0300 said:
Doesn't work. I can't "fastboot" into anything. When i try, the pc stops recognizing the phone.
Click to expand...
Click to collapse
Did you try a different usb cable? And you activated "developer options" and turned on usb debugging?
Also, try typing CMD in the url line from within the same platform tool folder where the platform tools application is located.
Az Biker said:
Did you try a different usb cable? And you activated "developer options" and turned on usb debugging?
Also, try typing CMD in the url line from within the same platform tool folder where the platform tools application is located.
Click to expand...
Click to collapse
OK, after waiting an hour, i tried typing into that command line that popped up within the platform tools folder. I tried adb devices, and my phone was recognized. Now, my phone is not in fastboot mode, and i don't have the sim card in it. What's my next move, please.
grunt0300 said:
OK, after waiting an hour, i tried typing into that command line that popped up within the platform tools folder. I tried adb devices, and my phone was recognized. Now, my phone is not in fastboot mode, and i don't have the sim card in it. What's my next move, please.
Click to expand...
Click to collapse
Have you patched the boot.img with magisk yet? If you look a few posts ago, I gave you exact instructions on how to patch and flash the modified boot.img
Also, adb devices is a command while your in your OS. You need to power off the phone, then enter bootloader mode manually by holding the power + volume down button until you enter the bootloader screen.
Then plug your phone in, open the command prompt on your platform-tools folder, and type in "fastboot devices". If you see your phone's ID number, then you have a good interface. Then you can fastboot the patched boot.img :good:
https://forum.xda-developers.com/pixel-2-xl/help/rooting-pixel-2xl-t4033453/post81455679
Badger50 said:
Have you patched the boot.img with magisk yet? If you look a few posts ago, I gave you exact instructions on how to patch and flash the modified boot.img
Also, adb devices is a command while your in your OS. You need to power off the phone, then enter bootloader mode manually by holding the power + volume down button until you enter the bootloader screen.
Then plug your phone in, open the command prompt on your platform-tools folder, and type in "fastboot devices". If you see your phone's ID number, then you have a good interface. Then you can fastboot the patched boot.img :good:
https://forum.xda-developers.com/pixel-2-xl/help/rooting-pixel-2xl-t4033453/post81455679
Click to expand...
Click to collapse
Can't get into "recovery mode". I have all the files in the file mgr on the phone. Do i have to put the sim card back into the phone in order for this to work?
grunt0300 said:
Can't get into "recovery mode". I have all the files in the file mgr on the phone. Do i have to put the sim card back into the phone in order for this to work?
Click to expand...
Click to collapse
Recovery mode? You need to be in bootloader mode. What files exactly do you have on your phone that your talking about? Just curious, but have you read through any of the directions that myself and @Az Biker have given you? Things seem to be getting lost in translation.
Badger50 said:
Recovery mode? You need to be in bootloader mode. What files exactly do you have on your phone that your talking about? Just curious, but have you read through any of the directions that myself and @Az Biker have given you? Things seem to be getting lost in translation.
Click to expand...
Click to collapse
Right now, i'm so confused that i don't know what day it is. I've got files all over my desktop. If i can get this phone up and running, i'll sell it and use the money towards a Note 9(USA version). I still have my rooted Nexus 6, and i NEVER had this trouble rooting it. Anyway, i'm done with this for now. If you want, i'll send you the Pixel 2xl, and when you get it working send it back to me, and we'll figure out the compensation. Thanks for trying.
grunt0300 said:
Right now, i'm so confused that i don't know what day it is. I've got files all over my desktop. If i can get this phone up and running, i'll sell it and use the money towards a Note 9(USA version). I still have my rooted Nexus 6, and i NEVER had this trouble rooting it. Anyway, i'm done with this for now. If you want, i'll send you the Pixel 2xl, and when you get it working send it back to me, and we'll figure out the compensation. Thanks for trying.
Click to expand...
Click to collapse
Please follow the step by step guide in my sig.
It explains EVERYTHING from step one all the way through the final reboot.
If your SDK tools are up to date (link provided), and your have multiple USB cables (trust me it's a known, unexplained issue) and you've unzipped the platform tools folder AND unzipped the second platform tool folder (this is the one where you type CMD in the url line) and then follow each step as written, you should have NO problem at all.
If you skip steps or go ahead using your own or another process there's no guarantee, but if you follow the steps in the guide, you should have no problems at all. This guide has been followed by myself and many others with ZERO issues, so I know the written process works.
Az Biker said:
Please follow the step by step guide in my sig.
It explains EVERYTHING from step one all the way through the final reboot.
If your SDK tools are up to date (link provided), and your have multiple USB cables (trust me it's a known, unexplained issue) and you've unzipped the platform tools folder AND unzipped the second platform tool folder (this is the one where you type CMD in the url line) and then follow each step as written, you should have NO problem at all.
If you skip steps or go ahead using your own or another process there's no guarantee, but if you follow the steps in the guide, you should have no problems at all. This guide has been followed by myself and many others with ZERO issues, so I know the written process works.
Click to expand...
Click to collapse
Did i mention that i already have android 10 on the phone?
grunt0300 said:
Did i mention that i already have android 10 on the phone?
Click to expand...
Click to collapse
The guide process works the same for 9x and Android 10.
In the guide, it is stated:
NOTE: On Android 10, when flashing TWRP Installer, kernels, magisk , etc. in TWRP, ignore the warning "FAILED TO MOUNT '/system' (invalid argument) this is a known issue with TWRP + 10 but affects nothing
Once you verify 'fastboot devices' on command prompt
Type flash-all to install factory image (allow it to install, and boot into system)
Hold vol down and power button to boot into bootloader
Fastboot into twrp 3.3.0-0.IMG
Flash the twrp installer 3.3.0-0.ZIP,
Flash Cust Kernel (I use Flash -not supported after 3.19 Nov 2018 or Sultan Kernel or Elemental X (EX) kernel) BE SURE TO SELECT THE CORRECT 9X OR ANDROID 10 KERNEL
Let the system boot up to verify.
Reboot back into twrp and flash latest magisk
Reboot to system
Profit
I guess I'm confused as to why you are simply not just following the guide from step one.........
Hi all,
Have looked around the guides and such on these threads for the Oneplus 8 Pro and haven't found a full comprehensive guide outlining all parts of the bootloader unlocking and root process, so thought I'd put together my experience for anyone found in the same position, this is simply what I did, i'm sure there are other guides out there which offer different methods but I can confirm that this 100% works
NOTE* This guide is intended for all OnePlus 8 devices but the boot image files are for the EU version of the Oneplus 8 Pro on the most current firmware at the time of writing please don't use these files unless you meet the pre-requisites to the guide stated below
It is possible to extract the boot IMG from any firmware using the payload extractor tool which can be found online, then change the commands to reflect the files you obtain, for the sake of clarity I'll be using 10.5.12
Hope this helps.
Pre-requisites
A European variant of the Oneplus 8 Pro: IN2023
Running the following firmware: 10.5.12 IN11BA
ADB Access to your phone
A decent amount of charge, eg: 80%
A Windows 10 based computer
The cable that came with your phone
Obtaining ADB access to your device using your computer
1. Connect your phone to your computer using the cable that you charge it with
2. Allow it to see the device, if it automatically installs the driver (which it should) then you're good to go, if not then install the driver you can obtain from the drive which will appear on screen within "This PC" (i won't detail this as it's pretty self explanatory)
3. On your phone Open settings and navigate to "About phone"
4. Click "Build number" several times (5) then enter your PIN, this will enable "Developer Options"
5. Back out, then click "System"
6. Scroll down to "Developer Options" and open it.
7. Scroll down to "USB Debugging" and turn it on (if at this point you are prompted with a dialogue box asking for authorization then please check the box and allow it, also turn on) also turn on "OEM Unlocking" in the same section and agree to any prompts.
8. On your computer Download this folder https://drive.google.com/drive/folders/1S-yNzdvOvdZzPuxhYuEuwnelzfdEd0K2?usp=sharing
This is adb and fastboot so you can talk to your phone via your PC.
9. Move it to the root of the C: drive, so it looks like this in the filepath
C:\Android
10. Navigate to the folder and perform the following:
i) Hold shift and right click an empty space within the folder
ii) Click "Open Powershell Window here" or "Open a Command prompt Windows here"
iii) A black or blue window will appear with some text
11. In the window type the following command
adb devices
press enter
If you are now prompted with an authorization dialogue on your phone, please check the box and allow it.
You should see a readout of a device followed by a code, you now have ADB access and can continue.
Unlocking the bootloader
NOTE* THIS WILL WIPE YOUR ENTIRE DEVICE, IT'S UP TO YOU IF YOU WANT TO BACK UP OR NOT. I WOULD RECOMMEND DOING SO
1. Connect your phone to your computer
2. On your computer Navigate to C:\Android
i) Hold shift and right click an empty space within the folder
ii) Click "Open Powershell Window here" or "Open a Command prompt Windows here"
iii) A black or blue window will appear with some text
3. Type the following command into the window
adb reboot bootloader
press enter
On your phone
i) Your phone will reboot and show you a screen with 3 language choices, Choose "English" then "Advanced" and finally "Reboot to fastboot" and "Reboot to fastboot"
ii) You'll see a screen appear on your phone with some text, at the top you'll see the word "START" in green, you're now in Fastboot
4. On your computer Type the following command into the window
fastboot oem unlock
press enter
NOTE* THIS IS THE PART THAT WIPES YOUR PHONE IF YOU WANT TO BACK OUT, NOW IS THE TIME TO DO SO, ONCE STARTED DO NOT DISCONNECT THE CABLE OR FORCE A SHUTDOWN FOR ANY REASON THIS COULD RESULT IN A BRICKED DEVICE
5. Your phone will warn you and go through a set of screens, please agree and move forward until the device reboots
You have just unlocked the bootloader to your phone
Once the device has booted, set it up again and then follow the steps to unlock "developer options" and "USB Debugging" once more.
Installing Magisk Manager and obtaining Root access
Before you begin, please follow these two steps to install the magisk manager
Magisk manager
i) On your computer download this folder https://drive.google.com/drive/folders/1VH_2Ql6L5580rVYvRZ5l8t7cX2XENEAG?usp=sharing and move the file inside to your internal storage on your phone, the file is called "MagiskManager-v7.5.1.apk"
ii) On your phone using a file manager navigate to where you moved the file and open it, this will install the Magisk Manager used to manage root access, open the Magisk Manager once, you'll see it does not have root access.
Rooting
1. On your computer Go here https://drive.google.com/drive/folders/189DlZH1NSMrgVF996S7y3q5_IG9RAFIr?usp=sharing and download the folder
2. Copy the file inside the folder which is called "magisk_patched.img" to C:\Android
3. Navigate to C:\Android
i) Hold shift and right click an empty space within the folder
ii) Click "Open Powershell Window here" or "Open a Command prompt Windows here"
iii) A black or blue window will appear with some text
4. Type the following into the window
adb reboot fastboot
press enter
On your phone
i) Your phone will reboot and show you a screen with 3 language choices, Choose "English" then "Advanced" and finally "Reboot to fastboot" and "Reboot to fastboot"
ii) You'll see a screen appear on your phone with some text, at the top you'll see the word "START" in green, you're now in Fastboot
On your computer
5. There are two options for rooting, the first is to boot it first, this is safer as it is not permanent and a reboot will rejoice the booted image, the second is to flash it, this is a one step option but if the image isn't right then you could end up in a bootloop so id recommend the first.
Type the following into the window
To boot:
Fastboot boot magisk_patched.img
(Your phone will reboot automatically)
To flash:
fastboot flash boot_a magisk_patched.img
press enter
then
fastboot flash boot_b magisk_patched.img
press enter
then
NOTE* THIS WILL FLASH THE PATCHED BOOT IMG TO BOTH SLOTS, THIS IS WHAT I DID, I HAVEN'T EXPLORED IF ONE SLOT IS ADEQUATE OR NOT, IT MAY BE POSSIBLE TO ONLY FLASH THE BOOT.IMG TO ONE SLOT BUT AS I HAVEN'T I CAN'T ADVISE.
6.. Once complete, type in the following command
fastboot reboot
press enter, your device will reboot
7. On your phone open up "Magisk Manager" you should now have two green ticks signifying that you now have root access.
NOTE* If you booted the image then simply click the top install option then go to install directly, this will make root permanent.
That's it, you've now unlocked your bootloader and rooted using the most current boot img at the time of writing.
------------------------------------------------------------------------------------------------------------------------------------
Please don't quote the entire thread!!!!!
If i've missed anything out or anyone notices a mistake please let me know and i'll amend accordingly.
Alternate second guide here on post #55 thanks to @flushell
https://forum.xda-developers.com/showpost.php?p=83534273&postcount=55
dladz said:
Hi all,
Have looked around the guides and such on these threads for the Oneplus 8 Pro and haven't found a full comprehensive guide outlining all parts of the root process, so thought I'd put together my experience for anyone found in the same position, this is simply what I did, i'm sure there are other guides out there which offer different methods.
NOTE* This guide is intended for the EU version of the Oneplus 8 Pro on the most current firmware at the time of writing please don't use these files unless you meet the pre-requisites to the guide stated below
Hope this helps..
Click to expand...
Click to collapse
If you dont have 10.5.12 installed in both slots then I dont see any reason to flash patched image to A and B..I just fastboot flash boot magisk_patched.img and that worked fine. Ive been rooted for quite awhile though
pyry666 said:
If you dont have 10.5.12 installed in both slots then I dont see any reason to flash patched image to A and B..I just fastboot flash boot magisk_patched.img and that worked fine. Ive been rooted for quite awhile though
Click to expand...
Click to collapse
Ok so by not specifying a slot you are flashing to both afaik
I know that the way i've written this it works perfectly, if another slot is required then it can be used when the time comes.
dladz said:
Ok so by not specifying a slot you are flashing to both.
I know that the way i've written this it works perfectly, if another slot is required then it can be used when the time comes.
Also please don't quote the entire guide it makes reading threads awful, edit your post please.
Click to expand...
Click to collapse
Sorry about that, post edited.Afaik if you dont specify slot it flashes it to current slot being used. Or you could just boot twrp (not install) and flash magisk from there. That also works. Ive tried that too
pyry666 said:
Sorry about that, post edited.Afaik if you dont specify slot it flashes it to current slot being used. Or you could just boot twrp (not install) and flash magisk from there. That also works. Ive tried that too
Click to expand...
Click to collapse
Ah ok nice, and no worries, thanks for editing.
Im aware of TWRP but for the purpose of just getting rooted this has worked for me and there wasn't a fool proof place where all the guides were so i wanted to make sure everything to get rooted was in one place and was easy to understand.
I'll edit it for TWRP and maybe some other bits once i've got to use them, but for now, this is enough to get people onto Magisk ROM's at least.
Have read different things about the slots, when i didn't specify the slot, it didn't work, so i had to specify, but had no idea which slot to choose so i chose both, it then worked so didn't want to break it i kept it, hasn't broken anything.
How are you identifying which slot is actually in use?
dladz said:
Ah ok nice, and no worries, thanks for editing.
Im aware of TWRP but for the purpose of just getting rooted this has worked for me and there wasn't a fool proof place where all the guides were so i wanted to make sure everything to get rooted was in one place and was easy to understand.
I'll edit it for TWRP and maybe some other bits once i've got to use them, but for now, this is enough to get people onto Magisk ROM's at least.
Have read different things about the slots, when i didn't specify the slot, it didn't work, so i had to specify, but had no idea which slot to choose so i chose both, it then worked so didn't want to break it i kept it, hasn't broken anything.
How are you identifying which slot is actually in use?
Click to expand...
Click to collapse
In twrp it reads clearly. And there is a fastboot command to check witch slot you are currently on and you can change that also in fastboot but I have to admit that I cant remember those commands from the top of my head right now
pyry666 said:
In twrp it reads clearly. And there is a fastboot command to check witch slot you are currently on and you can change that also in fastboot but I have to admit that I cant remember those commands from the top of my head right now
Click to expand...
Click to collapse
Nah it's cool, perhaps there's an app which does the same. Seeing as this is a pretty integral part of the system I would imagine that there would be.
Will have a look, appreciate you helping. Couldn't find much on the subject myself. Will edit the guide to reflect it.
I haven't actually installed twrp. Not yet anyway
dladz said:
Nah it's cool, perhaps there's an app which does the same. Seeing as this is a pretty integral part of the system I would imagine that there would be.
Will have a look, appreciate you helping. Couldn't find much on the subject myself. Will edit the guide to reflect it.
I haven't actually installed twrp. Not yet anyway
Click to expand...
Click to collapse
Me neither, just booted it couple times. Btw its safer to patch boot.img yourself rather than use pre patched image. Just because then you now what magisk version was used to patch it in first place. Wrong magisk version can cause issues
pyry666 said:
Me neither, just booted it couple times. Btw its safer to patch boot.img yourself rather than use pre patched image. Just because then you now what magisk version was used to patch it in first place. Wrong magisk version can cause issues
Click to expand...
Click to collapse
Or just follow the above guide if you meet the requirements
Command for swapping slot is
fastboot --set-active=a
Or b
Thanks for the guide, but I'm using IN2020 and I'm on 10.5.13.IN11AA.
anyone can point me to the correct topic or guide to root/ unlock bootloader etc?
N'ash said:
Thanks for the guide, but I'm using IN2020 and I'm on 10.5.13.IN11AA.
anyone can point me to the correct topic or guide to root/ unlock bootloader etc?
Click to expand...
Click to collapse
Bootloader unlock works same no matter what model you are using. You can just boot twrp and flash magisk from there
N'ash said:
Thanks for the guide, but I'm using IN2020 and I'm on 10.5.13.IN11AA.
anyone can point me to the correct topic or guide to root/ unlock bootloader etc?
Click to expand...
Click to collapse
Guides the same but the files would not be.
You can use payload dumper to extract the boot.img, then patch using magisk, then extract and follow the guide.
This guide was made for the EU version of the phone, i couldn't comment further on your device and i would not recommend continuing with the files i've uploaded if you don't meet the pre-requisites.
dladz said:
Guides the same but the files would not be.
You can use payload dumper to extract the boot.img, then patch using magisk, then extract and follow the guide.
This guide was made for the EU version of the phone, i couldn't comment further on your device and i would not recommend continuing with the files i've uploaded if you don't meet the pre-requisites.
Click to expand...
Click to collapse
So I have to download the official rom for IN2020 10.5.13 then extract the boot.img, patch with magisk and flash the patched boot.img right?
N'ash said:
So I have to download the official rom for IN2020 10.5.13 then extract the boot.img, patch with magisk and flash the patched boot.img right?
Click to expand...
Click to collapse
So in order.
1 Download the full ROM for your device and region.
2 Open it in on a computer and extract the bin file called payload, it'll be about 2.4GB.
3 Then copy it to the payload dumper input folder and run the exe
4 You'll get the boot image as well as some other files, copy the boot image to your phone and patch it using magisk.
5 Then pull the output magisk patched.img to your adb folder and flash to slot A or B or both. I did both
N'ash said:
So I have to download the official rom for IN2020 10.5.13 then extract the boot.img, patch with magisk and flash the patched boot.img right?
Click to expand...
Click to collapse
So how did it go?? All good?
dladz said:
So how did it go?? All good?
Click to expand...
Click to collapse
Yeah I did as instructed and everything is good. I wish I could get rid of the bootscreen security error message though!
I was not thinking and did this on 10.5.7 global and now I'm in a boot loop; EDIT: Just restored 10.5.5 with unbrick tool and used the downgrade 10.5.7 global from here https://forum.xda-developers.com/oneplus-8-pro/how-to/oneplus-8-pro-repo-oxygen-os-builds-t4084315 --then, I made my own patched magisk from the boot.img I extracted. Here is that 10.5.7 magisk patched img for global if anyone needs: http://www.mediafire.com/file/xcrm53shf5km8jz/magisk_patched.img/file
A.Priori said:
I was not thinking and did this on 10.5.7 global and now I'm in a boot loop; EDIT: Just restored 10.5.5 with unbrick tool and used the downgrade 10.5.7 global from here https://forum.xda-developers.com/oneplus-8-pro/how-to/oneplus-8-pro-repo-oxygen-os-builds-t4084315 --then, I made my own patched magisk from the boot.img I extracted. Here is that 10.5.7 magisk patched img for global if anyone needs: http://www.mediafire.com/file/xcrm53shf5km8jz/magisk_patched.img/file
Click to expand...
Click to collapse
Well done, always good to come back from the dead
N'ash said:
Yeah I did as instructed and everything is good. I wish I could get rid of the bootscreen security error message though!
Click to expand...
Click to collapse
Yea that annoys me too.
There will be a way I'd imagine, but you wouldn't want to get that script wrong..
Might look into getting that gone, HTC had this too as do a few devices.
Possible a precious guide for an older device may work but using it to test would be a risk..
After doing this, is it still possible to install official OS builds from OnePlus whenever a new build comes out? Either via a zip or OTA?
For instance when 10.5.13.IN11BA comes out or whatever?