Related
Hello, I've tried rooting my Nexus 7 (2013) with LTE for like 5 hours now...
I've done every single thing in every single thread, and I still can't do ****.
I've tried the WugFresh root toolkit, but that did not work at all for me, I uninstalled and remove what they told me to do... But nothing worked, when I followed the WugFresh toolkit I lost usb mass storage... N7 did not appear at all on my computer, which it did, before I tried to screw with it...
I've tried doing it the manual way too, downloading all the drivers, uninstalling the other onces first.. But nothing... I could not even get the device listed in adb! I tried the full driver installation thing + automatic check if everything worked out, but the tablet would NOT run the script to reboot it into fastboot, and when I tried to restart the tablet into fastboot, and then continue to run the toolkit, it would start TWRP, the popup on my computer told me to flash something "!flashready", but I could not find it in the sdcard...
I unlocked the n7 manually, holding the volume button and power button down.
I know that was very bad written, but I'm a bit in a hurry. Anything I could do?
Potetsjokolade said:
Hello, I've tried rooting my Nexus 7 (2013) with LTE for like 5 hours now...
I've done every single thing in every single thread, and I still can't do ****.
I've tried the WugFresh root toolkit, but that did not work at all for me, I uninstalled and remove what they told me to do... But nothing worked, when I followed the WugFresh toolkit I lost usb mass storage... N7 did not appear at all on my computer, which it did, before I tried to screw with it...
I've tried doing it the manual way too, downloading all the drivers, uninstalling the other onces first.. But nothing... I could not even get the device listed in adb! I tried the full driver installation thing + automatic check if everything worked out, but the tablet would NOT run the script to reboot it into fastboot, and when I tried to restart the tablet into fastboot, and then continue to run the toolkit, it would start TWRP, the popup on my computer told me to flash something "!flashready", but I could not find it in the sdcard...
I unlocked the n7 manually, holding the volume button and power button down.
I know that was very bad written, but I'm a bit in a hurry. Anything I could do?
Click to expand...
Click to collapse
So the current condition of your device is that ADB is nonfunctional but you are able to temporarily boot into TWRP with fastboot - is this correct?
Username invalid said:
So the current condition of your device is that ADB is nonfunctional but you are able to temporarily boot into TWRP with fastboot - is this correct?
Click to expand...
Click to collapse
Yes, that is correct, temporarily, with the toolkit I mentioned. But I do not find the files that the toolkit tells me to flash
Potetsjokolade said:
I've tried doing it the manual way too, downloading all the drivers, uninstalling the other onces first.. But nothing... I could not even get the device listed in adb! I tried the full driver installation thing + automatic check if everything worked out, but the tablet would NOT run the script to reboot it into fastboot, and when I tried to restart the tablet into fastboot, and then continue to run the toolkit, it would start TWRP, the popup on my computer told me to flash something "!flashready", but I could not find it in the sdcard...
I unlocked the n7 manually, holding the volume button and power button down.
Click to expand...
Click to collapse
I'm not sure what this means. If you're using a toolkit, you're not doing it manually. Have you tried ADB and fastboot alone, without a toolkit? Is TWRP on your phone now? If so, you're done; just flash from recovery 1) a ROM for a custom ROM or 2) SuperSU.zip for just root.
If you don't have TWRP, does your Google boot screen has a locked icon at the bottom? If so: for ADB to work you need to have debugging turned on in your phone's developer settings. You don't need ADB though; just reboot into the bootloader by holding power and volume-down. Then type "fastboot devices" and see if anything shows up.
If it's an unlocked icon, just flash a recovery.img from fastboot.
bananagranola said:
I'm not sure what this means. If you're using a toolkit, you're not doing it manually. Have you tried ADB and fastboot alone, without a toolkit? Is TWRP on your phone now? If so, you're done; just flash from recovery 1) a ROM for a custom ROM or 2) SuperSU.zip for just root.
If you don't have TWRP, does your Google boot screen has a locked icon at the bottom? If so: for ADB to work you need to have debugging turned on in your phone's developer settings. You don't need ADB though; just reboot into the bootloader by holding power and volume-down. Then type "fastboot devices" and see if anything shows up.
If it's an unlocked icon, just flash a recovery.img from fastboot.
Click to expand...
Click to collapse
Tried both manually with adb, and with WugFresh toolkit. I got WugFresh to run TWRP temporarily.
Potetsjokolade said:
Yes, that is correct, temporarily, with the toolkit I mentioned. But I do not find the files that the toolkit tells me to flash
Click to expand...
Click to collapse
The toolkit is using the command
Code:
fastboot boot openrecovery-twrp-2.6.3.0-deb.img
to temporarily boot it over the stock recovery. Since you unlocked your bootloader manually, you can replace the stock recovery manually too using
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img
Username invalid said:
The toolkit is using the command
Code:
fastboot boot openrecovery-twrp-2.6.3.0-deb.img
to temporarily boot it over the stock recovery. Since you unlocked your bootloader manually, you can replace the stock recovery manually too using
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img
Click to expand...
Click to collapse
How can I do that when my N7 does not show up on
adb devices
Click to expand...
Click to collapse
Getting "waiting for device"
Potetsjokolade said:
How can I do that when my N7 does not show up on
Click to expand...
Click to collapse
Fastboot is separate from ADB. Your fastboot is working if the toolkit is able to boot TWRP.
Code:
fastboot devices
is what you use while your device is in the bootloader.
Username invalid said:
Fastboot is separate from ADB. Your fastboot is working if the toolkit is able to boot TWRP.
Code:
fastboot devices
is what you use while your device is in the bootloader.
Click to expand...
Click to collapse
Great! I'll try that, just upoading openrecovery-twrp-2.6.3.0-flo.img to dropbox, just in case I'm able to flash it from download/
Potetsjokolade said:
Great! I'll try that, just upoading openrecovery-twrp-2.6.3.0-flo.img to dropbox, just in case I'm able to flash it from download/
Click to expand...
Click to collapse
openrecovery-twrp-2.6.3.0-flo.img is for the WiFi model. TWRP for the LTE model is openrecovery-twrp-2.6.3.0-deb.img.
Username invalid said:
The toolkit is using the command
Code:
fastboot boot openrecovery-twrp-2.6.3.0-deb.img
to temporarily boot it over the stock recovery. Since you unlocked your bootloader manually, you can replace the stock recovery manually too using
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img
Click to expand...
Click to collapse
Where in windows should I paste openrecovery-twrp-2.6.3.0-deb.img, so I can then flash it? It showed up in fastboot devices
EDIT: Nevermind that stupid question
Potetsjokolade said:
Where in windows should I paste openrecovery-twrp-2.6.3.0-deb.img, so I can then flash it? It showed up in fastboot devices
Click to expand...
Click to collapse
C:\Program Files\WugFresh Development
Then in toolkit > Advanced Utilities > Launch CMD Prompt > "fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img"
Username invalid said:
C:\Program Files\WugFresh Development
Then in toolkit > Advanced Utilities > Launch CMD Prompt > "fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img"
Click to expand...
Click to collapse
Flashed custom recovery + superSU
Thanks guys... Could you help me solve the problem where Nexus 7 wont show up on "my computer"? :laugh:
Potetsjokolade said:
Flashed custom recovery + superSU
Thanks guys... Could you help me solve the problem where Nexus 7 wont show up on "my computer"? :laugh:
Click to expand...
Click to collapse
What do you see if your computer Device Manager with USB Debugging on?
Username invalid said:
What do you see if your computer Device Manager with USB Debugging on?
Click to expand...
Click to collapse
It's connected as MTP, USB Debugging is on, and it does not show up on My Computer as Nexus 7
However, if I connect it as as PTP, it will show up.
Potetsjokolade said:
It's connected as MTP, USB Debugging is on, and it does not show up on My Computer as Nexus 7
However, if I connect it as as PTP, it will show up.
Click to expand...
Click to collapse
I've never had that problem so I can't speak from experience.
http://forum.xda-developers.com/showthread.php?t=2428061&highlight=mtp
http://forum.xda-developers.com/showthread.php?p=44219641#post44219641
Hi, i played around with my new OP3, and i wanted to root it. Since i'm noob at rooting, it went wrong. (i did it with twrp)
So first it just went in to bootloop, then i was still able to get to rcovery and stuff, but i followed a guide to fix bootloop, and that ****ed it even more up. The guide i followedet told me to use "OnePlus3_Unbrick_Tool"
After using "OnePlus3_Unbrick_Tool", i now cant even go into recovery anymore, the only thing i can do is go to bootloader, but when i'm in bootloader now, it wont connect proberly, so that i can use "flash twrp", so that i can use twrp recovery.
Also when i try to boot it, it because of "OnePlus3_Unbrick_Tool" goes into something, where it says "md5 checksum failed", and then restarts and does it again and again.....
I hope it's not bricked forever, pls help ))
have you tried re-flashing the stock or twrp recovery with adb sideload command?
if not give it a shot, it might work.
bonham1988 said:
have you tried re-flashing the stock or twrp recovery adb sideload command?
Click to expand...
Click to collapse
And how do you say I do that? I have tried using the "tool all in one", where you han flash both stock and twrp, but it doesnt seem to do anything, when i press them (and the device is in bootloader)
Godeske said:
And how do you say I do that? I have tried using the "tool all in one", where you han flash both stock and twrp, but it doesnt seem to do anything, when i press them (and the device is in bootloader)
Click to expand...
Click to collapse
Just boot into bootloader mode and through command prompt check if your phone is detected by typing fastboot devices. If its detected then you flash a new recovery again. Forget the toolkit, just look for instructions on how to install a custom recovery.
Sent from my OnePlus3 using XDA Labs
bonham1988 said:
Just boot into bootloader mode and through command prompt check if your phone is detected by typing fastboot devices. If its detected then you flash a new recovery again. Forget the toolkit, just look for instructions on how to install a custom recovery.
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Okay i've tried that now, and it wont allow me unlock my bootloader from command prompt, and i cant do the flash while it's locked.. what to do?
Godeske said:
Okay i've tried that now, and it wont allow me unlock my bootloader from command prompt, and i cant do the flash while it's locked.. what to do?
Click to expand...
Click to collapse
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
simthadim said:
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
Click to expand...
Click to collapse
When im in fastboot mode in the bootloader, i can only find it in "device manager" as "marshall london device -> marshall london bootloader interface"
Godeske said:
When im in fastboot mode in the bootloader, i can only find it in "device manager" as "marshall london device -> marshall london bootloader interface"
Click to expand...
Click to collapse
Might seem a silly question but what phone are you using? If it is a OnePlus3 have you installed the correct drivers?
ghostofcain said:
Might seem a silly question but what phone are you using? If it is a OnePlus3 have you installed the correct drivers?
Click to expand...
Click to collapse
Pretty sure i have, but i have booked a session with oneplus costumer service now, so that they do it for me live lololol
bonham1988 said:
have you tried re-flashing the stock or twrp recovery with adb sideload command?
if not give it a shot, it might work.
Click to expand...
Click to collapse
Hey bonham,
The same thing happened to me but when I try to sideload it says I need 1.0.32 or higher to sideload this device
What should I do?
gavintoronto2016 said:
Hey bonham,
The same thing happened to me but when I try to sideload it says I need 1.0.32 or higher to sideload this device
What should I do?
Click to expand...
Click to collapse
Adb version is outdated. Just download the latest ones.
Sent from my OnePlus3 using XDA Labs
Hey guys, if there are some of you, who knows a lot about this, would you like to answer this comment? Idk maybe we could use teamviewer to help me or something
simthadim said:
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
Click to expand...
Click to collapse
Ohh i think i understand your question. YEs in command prompt I am able to find the device, it is connected.
(do you know a lot about this, maybe you could teamview me to help?))
Godeske said:
Ohh i think i understand your question. YEs in command prompt I am able to find the device, it is connected.
(do you know a lot about this, maybe you could teamview me to help?))
Click to expand...
Click to collapse
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
simthadim said:
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
Click to expand...
Click to collapse
Thank you, but i have not enabled "allow oem unlocking" in the developer settings when the phone worked, so i get a error message "FAILED (remote: oem unloc is not allowed)
What to do to unlock it then?
Bro, download 3.2.4 oos rom zip file from official link. Its around 1.3 GB. Just connect ur OP3 to computer. It will detect as MTP device.Im my computer it was in the name of RAIN Transfer the zip file to internal storage. Wipe cache. And select install option in TWRP and select the zip file u pushed and flash it. Best of luck..
jaganmohans said:
Bro, download 3.2.4 oos rom zip file from official link. Its around 1.3 GB. Just connect ur OP3 to computer. It will detect as MTP device.Im my computer it was in the name of RAIN Transfer the zip file to internal storage. Wipe cache. And select install option in TWRP and select the zip file u pushed and flash it. Best of luck..
Click to expand...
Click to collapse
Bro, if just it were that simple, but it's not.. It doesn't find the phone in my computer...
simthadim said:
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
Click to expand...
Click to collapse
Hey i have the same problem but this fix does not work for me.
So I have the bootloader unlocked and I can enter the bootload and my computer detects my device which is nice.
when I flash twrp on my phone trough CMD it doesnt work, my PC tells me that everything is okay but my phone will not boot into twrp and instead it will give me weird errors.
---------- Post added at 03:31 PM ---------- Previous post was at 02:56 PM ----------
this fix worked for me,
On the screen when the phone failed to md5 checksum, you've got several partition failed right? in red text.
- download this : https://www.androidfilehost.com/?fid=24591000424942573
and then extract.
- download platform tools attached below. extract in the same folder with first file you've downloaded.
- Boot your phone to fastboot mode, plug your usb, make sure adb and fastboot driver are installed.
- on the folder, hold shift and right click, click open command here
- type fastboot devices
- make sure your serial number appear.
- now flash the img of the missing file according to the partition in red text on your ms5 checksum failed one by one.
- e.g. "fastboot flash boot_aging boot_aging.img.
- make sure you flash all the missing partition.
- type fastboot reboot.
this will boot you to oos 3.1.2.
unfortunately I couldn't extract the newest oos dat. data. but you could always take the OTA
goodluck mate. sorry for my english
Godeske said:
Bro, if just it were that simple, but it's not.. It doesn't find the phone in my computer...
Click to expand...
Click to collapse
Hmm bad try installing all op3 drivers and see whether phone is detected or not. I was in the same situation previously. Pushing zip through adp terminal is painful process. I got device offline first,after solving that i got service not recognized issue. For solving that usb debugging needs to be enabled i stuck in that step.
can you enter recovery trough fastboot mode? I.e. if you are in fastboot mode you van use the volume keys to select recovery.
100% sure you can't enter recovery?
you can try Fast and pro's option. let us know!
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.........
Guide updated!!!!!
If you wanna get back to stock ROM and relock bootloader + get OTAs working again, this is the right place!
DISCLAIMER: Relocking bootloader erases all your data/internal storage and (off course) remove TWRP/modules/root, so do a backup of all your data first. Also, I'm not responsible for any bricked devices (phones, SD Cards, etc). I tested it in my XT1955-1 and it worked fine, but we all know that errors might occur.
Finally, let's go to the steps.
Step 1 - Downloading necessary files
Download Android Platform Tools here and then extract it.
Install Motorola Drivers on your PC (download here).
Download the lastest firmware according to your variant/software channel here and extract it in the same folder you had extracted Android Platform Tools.
Download the "Lock Script" here, according to your android version and PC's OS.
For example: if your PC uses Windows as OS, and your phone is in android 10, download the "Lock-10q_windows.bat" file.
Or if you have a Linux distro on your PC and android 9 on your phone, download "Lock-9pie_linux.sh" file.
Place the file inside the platform-tools folder, where the ROM was extracted too.
Step 2 - Preparing your phone
Remove all your google account in device's settings and then go to Developer Options. Enable Android debugging and OEM unlocking (if you can't enable OEM unlocking, you may need to root your device first to get it avaible again (see Rooting thread)).
Power off your phone and put it fastboot mode. Connect it on PC using USB cable.
Step 3 - Installing Stock ROM and re-locking bootloader
Just double click on the Lock.bat/.sh file and it will reflash stock ROM and lock bootloader. Now all you have to do is wait till it finishes. This should take a few minutes to be done.
The phone will boot automatically after the last command is executed.
It seems to be a little hard, but it's easy. If you have any questions, let me know, I'll try to answer ASAP.
Very nice, it's really working! Thanks!
Works on xt1955-4 thanks very much, will the warranty still apply?
piotr1859 said:
Works on xt1955-4 thanks very much, will the warranty still apply?
Click to expand...
Click to collapse
run
Code:
fastboot getvar all
Will tell you if warranty is voided.
Sent from my ali using XDA Labs
piotr1859 said:
Works on xt1955-4 thanks very much, will the warranty still apply?
Click to expand...
Click to collapse
Yes, should work fine. Afaik, once you unlock your bootloader, your warranty is avoid, theoretically. But I guess you can send it to service center (if it's needed) with no problems. They don't always check if you have unlocked your bootloader or not.
Warning: Due to some changes in bootloader and people getting hard bricks in February security patch, i don't recommend to relock bootloader in that version, do it in December security patch instead!
Hello guys. I have Motorola Moto G7 Power (XT1955-4). I've tried to put in twrp and a rom, but when I rebooted my device it don't power on anymore. So I've searched many guides to repair. I've used "blankflash" and after many times I was finally power on my device and go in Fastboot Mode. But now there's another problem. When I connect with usb and open CMD and type "adb devices" appear:
LIST OF DEVICES ATTACHED
or
WAITING FOR DEVICES
I tried many things to fix it but nothing work. Now I've uninstalled everything on my pc, drivers too.
Maybe I've installed bad "blankflash"???
How can I fix my troubles?
DarkAngelNoctis said:
Hello guys. I have Motorola Moto G7 Power (XT1955-4). I've tried to put in twrp and a rom, but when I rebooted my device it don't power on anymore. So I've searched many guides to repair. I've used "blankflash" and after many times I was finally power on my device and go in Fastboot Mode. But now there's another problem. When I connect with usb and open CMD and type "adb devices" appear:
LIST OF DEVICES ATTACHED
or
WAITING FOR DEVICES
I tried many things to fix it but nothing work. Now I've uninstalled everything on my pc, drivers too.
Maybe I've installed bad "blankflash"???
How can I fix my troubles?
Click to expand...
Click to collapse
If the device is in fastboot mode only fastboot commands will work
Code:
fastboot getvar all
edit:grammer
Sent from my ali using XDA Labs
sd_shadow said:
If the device is in fastboot mode only fastboot commands work like
Click to expand...
Click to collapse
Ok. Thanks!
LuisLFSS said:
Warning: Due to some changes in bootloader and people getting hard bricks in February security patch, i don't recommend to relock bootloader in that version, do it in December security patch instead!
Click to expand...
Click to collapse
hey would it be safe to use this method on security patch version April1,2020? if not please point me in the right direction.
thanks
darko454 said:
hey would it be safe to use this method on security patch version April1,2020? if not please point me in the right direction.
thanks
Click to expand...
Click to collapse
Yes, it's safe. Now we have blankflash so it's safe
LuisLFSS said:
Yes, it's safe. Now we have blankflash so it's safe
Click to expand...
Click to collapse
ok thanks!
LuisLFSS said:
Yes, it's safe. Now we have blankflash so it's safe
Click to expand...
Click to collapse
Hi, can you send a link to blankflash for XT1955-1?
THANK YOU.
hawkdown77 said:
Hi, can you send a link to blankflash for XT1955-1?
THANK YOU.
Click to expand...
Click to collapse
Yes, join in my group: t.me/motog7brasil
LuisF201707 said:
If you wanna get back to stock ROM and relock bootloader + get OTAs working again, this is the right place!
DISCLAIMER: Relocking bootloader erases all your data/internal storage and (off course) remove TWRP/modules/root, so do a backup of all your data first. Also, I'm not responsible for any bricked devices (phones, SD Cards, etc). I tested it in my XT1955-1 and it worked fine, but we all know that errors might occur.
Finally, let's go to the steps.
Step 1 - Downloading necessary files
Download Android Platform Tools here and then extract it.
Install Motorola Drivers on your PC (download here).
Download the lastest firmware according to your variant/software channel here and extract it in the same folder you had extracted Android Platform Tools.
Step 2 - Preparing your phone
Remove all your google account in device's settings and then go to Developer Options. Enable Android debugging and OEM unlocking (if you can't enable OEM unlocking, you may need to root your device first to get it avaible again (see Rooting thread)).
Power off your phone and put it fastboot mode. Connect it on PC using USB cable.
Step 3 - Installing Stock ROM
If you're already in stock ROM with no modules and stuff installed on it, just skip this and jump to the next step. If you're not, then stay here.
Open CMD (command prompt) in the same folder you had extracted firmware and android platform tools.
Shift+right click and then "Open command window here" or just type CMD in the folder path bar at the top in windows explorer. Run this commands all at once in CMD:
Once it is done, DON'T power on your phone, just leave it as it is and let's go to the last step.
Step 4 - Relocking Bootoader
In cmd, run this commands all at once
Done! The phone will boot automatically after the last command is executed.
It seems to be a little hard, but it's easy. If you have any questions, let me know, I'll try to answer ASAP.
Click to expand...
Click to collapse
There is an bat file out to relsash stock rom with out trying all that stuff in manually
Help
I followed all the steps and managed to block the bootloader but when I turn on the phone I get "start up failed" can someone help me.
I did it in the April 1 patch
JPalomo1997 said:
I followed all the steps and managed to block the bootloader but when I turn on the phone I get "start up failed" can someone help me.
I did it in the April 1 patch
Click to expand...
Click to collapse
Which android version? There's april security patch for android 9 and 10...
roadkill42 said:
There is an bat file out to relsash stock rom with out trying all that stuff in manually
Click to expand...
Click to collapse
I know... I'll update the thread soon
chrisbchrisb85 said:
For step 4 relocking the bootloader what does "run these commands all at once" mean??? As soon as I lock the bootloader I can no longer flash anything else, therefore still stuck with a boot screen warning
Click to expand...
Click to collapse
"run these commands all at once" = copy all the commands and execute them in cmd...
And which android version did you install? because the commands to flash android 10 are different than android 9 ones
Guide updated!!!!!
I removed those annoying commands and put a link to download Scripts that already do everything automatically. Now the guide is simpler and easier
Hi there,
looks like the latest Update for my OnePlus 9 Pro did bricked my device.
It vibrates repidly at bootup, that stopes when I have the SIM Pin Screen. After I entered the Pins I should get the Finger Print Lock Screen but it just startes to vibrating rapidly again and I get the Line with emergency Call under it to enter the password (no finger print screen). No Keyboard to enter the PW and screen turns black after a while but keeps vibrating rapidly even for hours.
I can hold Power button and restart or shutdown.
So I think it is bricked and I have to try a Factory Reset.
I can enter the recovery menu with VolDown+Power (only reset device and no clear cache option) and the EDL Mode VolUp+VolDown+Power.
Is there any chance to Backup my files in one of that modes?
Haven't you rooted your OnePlus 9 Pro? If not, I think you had better contact a customer service center of OnePlus for help.
Sadly not rooted. The customer service say: factory reset which deletes all the files ...
Any recommendations for an App that restores Files on Android after Factory Reset? One that Restores ALL kind of Files, not only Pictures, Movies and Music.
I hope I could save some of my Chatlogs of Threema (I only have a Backup of the ID, not the Chatlog).
Search&Destroy said:
Sadly not rooted. The customer service say: factory reset which deletes all the files ...
Any recommendations for an App that restores Files on Android after Factory Reset? One that Restores ALL kind of Files, not only Pictures, Movies and Music.
I hope I could save some of my Chatlogs of Threema (I only have a Backup of the ID, not the Chatlog).
Click to expand...
Click to collapse
Normally ADB works in recovery mode, could do a pull command, if firmware is A11 you could temp boot TWRP for some options...
Just a thought.
I cant find any device in recovery or fastboot mode.
I also tested my OnePlus 6.
The OP6 will be found via ADB, when I boot it up to Android.
But not sure if there is a special Driver needed for ADB in recovery or fastboot mode.
Search&Destroy said:
I cant find any device in recovery or fastboot mode.
I also tested my OnePlus 6.
The OP6 will be found via ADB, when I boot it up to Android.
But not sure if there is a special Driver needed for ADB in recovery or fastboot mode.
Click to expand...
Click to collapse
Did you install the latest OP USB drivers?
Do you have a Google account? And we're you signed in?
TheGhost1951 said:
Did you install the latest OP USB drivers?
Click to expand...
Click to collapse
No, where can i get them?
TheGhost1951 said:
Do you have a Google account? And we're you signed in?
Click to expand...
Click to collapse
Yes I have and the Device is/was logged in.
Search&Destroy said:
No, where can i get them?
Yes I have and the Device is/was logged in.
Click to expand...
Click to collapse
Then you should be able to MSM back to stock and during setup log back in to Google and it will restore all apps with data..... But before doing that try from fast boot fastboot boot twrp, connect USB flash drive and while in twrp use TWRP file explorer to copy from SD card to USB flash drive for documents and photos... If SD card is not available in twrp, the only recovery option you have is apps and app data from Google restore
But I cant install TWRP as long as I cant find the device via ADB right?
Because I cant find the OnePlus 9 Pro, I can only find my older OnePlus 6.
And in Recovery Menu (v1.2) there are only 3 Options: Wipe data (no wipe cache option), Reboot and power off.
Have the latest Stock Android available for the OP9Pro installed
Search&Destroy said:
But I cant install TWRP as long as I cant find the device via ADB right?
Because I cant find the OnePlus 9 Pro, I can only find my older OnePlus 6.
Click to expand...
Click to collapse
Can you get to fastboot? Then if so, in CMD window type fastboot devices and see if you phone sends back the serial number
Ahh here it is.
The PowerShell shows me the same Serial number as my OP9Pro shows me in FastBoot Mode (still nothing with adb devices listed)
Well I downloaded TWRP and did try to send it via 'fastboot boot twrp.img' but its not possible, because my device is locked.
All I get is:
FAILED (remote: 'boot is not allowed in Lock State')
Your best bet would be to boot into TWRP if you are running Android 11
Search&Destroy said:
Ahh here it is.
The PowerShell shows me the same Serial number as my OP9Pro shows me in FastBoot Mode (still nothing with adb devices listed)
Click to expand...
Click to collapse
You are not booted up to home screen to be seen by ADB normally...in fastboot mode if you have TWRP downloaded, try fastboot boot name_of_twrp_img.img and see if TWRP boots up. Cd to directory where TWRP image is located.
twrp can only boot when the bootloader is unlocked , with locked bootloader you cant boot twrp
and the stock recovery have no adb enabled
ChrisFeiveel84 said:
twrp can only boot when the bootloader is unlocked , with locked bootloader you cant boot twrp
and the stock recovery have no adb enabled
Click to expand...
Click to collapse
My mistake...
Search&Destroy said:
Well I downloaded TWRP and did try to send it via 'fastboot boot twrp.img' but its not possible, because my device is locked.
All I get is:
FAILED (remote: 'boot is not allowed in Lock State'what firmware were you on before this happened? Glo, EU or which?
Click to expand...
Click to collapse
What Firmware were you on?
Search&Destroy said:
Well I downloaded TWRP and did try to send it via 'fastboot boot twrp.img' but its not possible, because my device is locked.
All I get is:
FAILED (remote: 'boot is not allowed in Lock State')
Click to expand...
Click to collapse
I believe you only have two options left. Try to flash all the firmware images while in fastboot. If that can't be done, only thing left is to use the MSM tool which I know will wipe everything. But when you go to setup you phone, logging into your Google account, Google will restore apps and apps data....but you will lose the data on internal storage. Sorry that I can't be more help.