Related
I started to root my phone this morning. I did the HTVDev unlock, flashed twrp, then tried to flash viperboy's disable RW system protect. This caused my phone to just hang at the HTC screen. I let my phone die and was able to get into my bootloader and fastboot. I tried to push the rom via adb but I kept getting the error of no device connected. Then i tried to flash the stock boot.img though fastboot. This brought me back to the HTC screen but now when I plug it in to my computer it shows up for everything and it installs drivers but the HTC MTP Device fails. Now I cant send commands to reboot through fastboot or adb. Im currently waiting for it to die again to get back to twrp or the bootloader. Any advice on how to proceed?
Thanks,
Paris6906
Paris6906 said:
I started to root my phone this morning. I did the HTVDev unlock, flashed twrp, then tried to flash viperboy's disable RW system protect. This caused my phone to just hang at the HTC screen. I let my phone die and was able to get into my bootloader and fastboot. I tried to push the rom via adb but I kept getting the error of no device connected. Then i tried to flash the stock boot.img though fastboot. This brought me back to the HTC screen but now when I plug it in to my computer it shows up for everything and it installs drivers but the HTC MTP Device fails. Now I cant send commands to reboot through fastboot or adb. Im currently waiting for it to die again to get back to twrp or the bootloader. Any advice on how to proceed?
Thanks,
Paris6906
Click to expand...
Click to collapse
Likely no need to let it die -- a hard reset (hold the power and vol down for a very long time) should bring you back to the bootloader (hopefully). It'll seem like a good long while -- keep pressing.
From there, select 'fastboot' and press the power button, then plug in to your computer (USB). That'll show USB on the fastboot line.
Then, on your computer, open a command window (presuming you're using Windows) in the SDK platform-tools directory and type:
fastboot devices
If that gives back your device ID, you're at least at a reasonable fastboot. I'd flash a good recovery (I use PhilZ, and while it might be foreign to you (CWM style), it lets you load a ROM via OTG cable over USB if you have such a cable -- if not, hopefully sideload works for you in TWRP if you stick with that) -- just to be sure you have a good recovery.
Then, reboot into recovery.
Your kernel (boot.img) apparently is garbage, so hopefully you can either put a ROM on USB and flash from that (OTG) or adb sideload it. All the ROMs normally have a good kernel so would flash your boot.img properly during install. Were me me, I'd flash O.M.J's stock rooted ROM just so you at least get back to some place of sanity).
If that all fails, you might have to RUU and start over.
Let us know and we'll help out.
If that gives back your device ID, you're at least at a reasonable fastboot. I'd flash a good recovery (I use PhilZ, and while it might be foreign to you (CWM style), it lets you load a ROM via OTG cable over USB if you have such a cable -- if not, hopefully sideload works for you in TWRP if you stick with that) -- just to be sure you have a good recovery.
ok. can you use adb push in fastboot? also i noticed that my captive buttons blink when i tried to turn off my phone. don't know if that means anything.
OMG it worked! Thank you so much. I uber appreciate it. Today I learned a ton about how android works and how to use adb and fastboot. While the processed about gave me a heart attack i did learn a lot. I can not believe how great of a resource xda is. The knowledge of everyone on here is incredible. I cant thank you enough.
Thanks all,
Paris6906
Hoping somebody can help me figure out what is going on with my phone. Sorry for the long post, but hoping folks with custom rom and flashing experience will read on to help.
I have the Verizon Developer Edition. I have unlocked the bootloader, installed TWRP 2.7, and rooted the phone. I have never installed any custom ROMs on the phone. I had done custom ROMs on my GS3, but I just wanted this phone rooted, and maybe mess around with a few ROMs down the road.
I followed this video from RootJunky when I originally installed TWRP.
So a few weeks ago I kept getting the OTA message to upgrade to the latest kitkat. I decided to flash back to the original recovery so I could do the upgrade. I contacted RootJunky on his youtube channel and he provided a link to the stock recovery and I flashed it using the same video and his linked file.
After flashing the stock recovery, when I was in bootloader mode, I scrolled down to "recovery" and selected it. It would not go into recovery. It just stays in a bootloop. I went back and forth with RootJunky a few times trying to resolve this, but I got no response to my last few comments.
I can get the phone back into bootloader mode by holding the volume up/dwn and power buttons, if I time it correctly during the bootloop. When in bootloader mode, I can select "Normal Powerup" option and the phone will boot up and function properly. But, if I shut the phone down, I can't turn the device on with the power button, otherwise it will just bootloop. I have to get into bootloader mode, then select "Normal Powerup" to get the phone to work.
Once back in the phone, my USB debugging option is unchecked. I can recheck it, open a command prompt, and do a "adb devices" and it shows it connected. But if I do a "adb reboot bootloader" from the command prompt it will bootloop.
When I get into bootloader mode manually, when I connect it to the computer, and do a "adb devices", it doesn't show as connected, as I think the USB debugging option is getting toggled off somehow, so I can't connect or flash anything to the phone at this point.
One thing I see, in the video @ 4:50, he says you need to be at "status code 1" to flash recoveries. I am/was at status code 3. Not sure if that is why I am having this issue, or how to get this changed.
Any help would be greatly appreciated. I can use the phone just fine, but at this point, I would just like to be able to do a full restore to stock, upgrade to 4.4.4, keep the unlocked bootloader, and root the phone. No custom ROM.
THANKS!
08G8V8 said:
Hoping somebody can help me figure out what is going on with my phone. Sorry for the long post, but hoping folks with custom rom and flashing experience will read on to help.
I have the Verizon Developer Edition. I have unlocked the bootloader, installed TWRP 2.7, and rooted the phone. I have never installed any custom ROMs on the phone. I had done custom ROMs on my GS3, but I just wanted this phone rooted, and maybe mess around with a few ROMs down the road.
I followed this video from RootJunky when I originally installed TWRP.
So a few weeks ago I kept getting the OTA message to upgrade to the latest kitkat. I decided to flash back to the original recovery so I could do the upgrade. I contacted RootJunky on his youtube channel and he provided a link to the stock recovery and I flashed it using the same video and his linked file.
After flashing the stock recovery, when I was in bootloader mode, I scrolled down to "recovery" and selected it. It would not go into recovery. It just stays in a bootloop. I went back and forth with RootJunky a few times trying to resolve this, but I got no response to my last few comments.
I can get the phone back into bootloader mode by holding the volume up/dwn and power buttons, if I time it correctly during the bootloop. When in bootloader mode, I can select "Normal Powerup" option and the phone will boot up and function properly. But, if I shut the phone down, I can't turn the device on with the power button, otherwise it will just bootloop. I have to get into bootloader mode, then select "Normal Powerup" to get the phone to work.
Once back in the phone, my USB debugging option is unchecked. I can recheck it, open a command prompt, and do a "adb devices" and it shows it connected. But if I do a "adb reboot bootloader" from the command prompt it will bootloop.
When I get into bootloader mode manually, when I connect it to the computer, and do a "adb devices", it doesn't show as connected, as I think the USB debugging option is getting toggled off somehow, so I can't connect or flash anything to the phone at this point.
One thing I see, in the video @ 4:50, he says you need to be at "status code 1" to flash recoveries. I am/was at status code 3. Not sure if that is why I am having this issue, or how to get this changed.
Any help would be greatly appreciated. I can use the phone just fine, but at this point, I would just like to be able to do a full restore to stock, upgrade to 4.4.4, keep the unlocked bootloader, and root the phone. No custom ROM.
THANKS!
Click to expand...
Click to collapse
First, Status code 3 is normal - that indicates an unlocked bootloader.
You should be able to use the 4.4.4 FXZ to flash back to 100% stock. Afterwards, you can flash TWRP, and re-root. Use the latest TWRP from here: http://techerrata.com/browse/twrp2/ghost
The important thing about TWRP is that immediately after flashing it, you have to "fastboot reboot-bootloader" and immediately boot into recovery - otherwise it doesn't 'stick'. We don't know why, but as long as you do it that way, you will be fine.
Here is the link for the 4.4.4 FXZ: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
If you follow the instructions, you will be on stock, rooted 4.4.4 in less than 20 minutes.
Good Luck, and let me know if you need additional assistance :good:
Also, please remember to post your questions to Q&A - not General. Don't worry as I have already requested that the Mods move it to the appropriate sub-forum.
EDIT: The problem I see with "rootjunky"s video is that first, he advises that "Status code 1" is required to flash recovery -- this is incorrect. Status code 3 works fine for custom recovery.
Additionally, he did not "fastboot reboot-bootloader" before booting into recovery. This is necessary. I'm not sure why he left that step out....likely he already had custom recovery flashed when he made the video.
Thanks for the quick response. Sorry about posting in the wrong section. I should have known better.....
I will look at this, but probably won't do it until after work tomorrow. I will post back tomorrow, hopefully with success.
Thanks!
I saw your edit to your post. I did the reboot boot loader step when I originally flashed twrp. I can't remember where I saw it, but I remember reading it and doing it.
The phone was running fine with twrp installed for a few months. The problem I am having now happened after flashing the stock recovery back onto the phone.
Do you recommend the RSD Flasher or House of Moto method to flash this FXZ?
08G8V8 said:
I saw your edit to your post. I did the reboot boot loader step when I originally flashed twrp. I can't remember where I saw it, but I remember reading it and doing it.
The phone was running fine with twrp installed for a few months. The problem I am having now happened after flashing the stock recovery back onto the phone.
Do you recommend the RSD Flasher or House of Moto method to flash this FXZ?
Click to expand...
Click to collapse
Either will work fine. If you don't care about keeping your data, you can use RSD Lite (will wipe everything). If you use one of the tools in the thread I linked you to, make absolutely sure you follow the instructions -- you can't have any spaces in any folder-names. If you use RSD Lite, you just select the zip file and flash (no worries about directory structure).
Ok, I just assumed those were the methods to flash it. I will look into the RSD Lite method, as if don't mind wiping the data.
I just watched a quick video on YouTube about using RSD Lite, and they state you must reboot the boot loader and do the flash in fastboot. I can't reboot into the bootloader from the command prompt, as it goes into the boot loop. I can get into fastboot manually, but when connecting to the computer it doesn't recognize it since the USB debugging option keeps getting reset on me.
Am I missing something? I don't see how I can flash this.
08G8V8 said:
I just watched a quick video on YouTube about using RSD Lite, and they state you must reboot the boot loader and do the flash in fastboot. I can't reboot into the bootloader from the command prompt, as it goes into the boot loop. I can get into fastboot manually, but when connecting to the computer it doesn't recognize it since the USB debugging option keeps getting reset on me.
Am I missing something? I don't see how I can flash this.
Click to expand...
Click to collapse
So you are telling me that when you type "adb reboot bootloader" (if usb debugging is enabled) or "fastboot reboot-bootloader" (if usb debugging is not enabled) it doesn't take you to the "AP Fastboot Mode" screen?
samwathegreat said:
So you are telling me that when you type "adb reboot bootloader" (if usb debugging is enabled) or "fastboot reboot-bootloader" (if usb debugging is not enabled) it doesn't take you to the "AP Fastboot Mode" screen?
Click to expand...
Click to collapse
Sorry, the "adb reboot bootloader" sends me into the bootloop.
I hadn't tried the "fastboot reboot bootloader" or "fastboot reboot-bootloader". Now when I try that, with USB debugging checked I just get "<waiting for device>" It does nothing.
What about turning off the device. Then holding power button and volume down at the same time. Does it take you to the bootloader screen like it should?
It sounds to me like when you were attempting you flash your stock recovery back, you flashed it to the wrong partition. I've seen another member do this....
He accidentally typed "fastboot flash bootloader stockrecoveryfile.img"
That would cause the issues you are describing... I might have a way to fix it if you are currently still rooted and able to access adb...
Travisdroidx2 said:
What about turning off the device. Then holding power button and volume down at the same time. Does it take you to the bootloader screen like it should?
Click to expand...
Click to collapse
Yes, I can manually get into bootloader, but it keeps toggling my USB debugging option, so when I connect it to the computer, it doesn't see it.
08G8V8 said:
Yes, I can manually get into bootloader, but it keeps toggling my USB debugging option, so when I connect it to the computer, it doesn't see it.
Click to expand...
Click to collapse
USB debugging isn't used in the bootloader, and adb isn't used for fastboot mode... I'm very confused by what you are saying...
Once you are in the boot loader screen does "fastboot devices" recognize your device?
samwathegreat said:
It sounds to me like when you were attempting you flash your stock recovery back, you flashed it to the wrong partition. I've seen another member do this....
He accidentally typed "fastboot flash bootloader stockrecoveryfile.img"
That would cause the issues you are describing... I might have a way to fix it if you are currently still rooted and able to access adb...
Click to expand...
Click to collapse
No, I typed "fastboot flash recovery stockrecoveryfile.img"
I did just like originally when flashing TWRP, just replaced the file in the command line.
I am still rooted.
samwathegreat said:
USB debugging isn't used in the bootloader, and adb isn't used for fastboot mode... I'm very confused by what you are saying...
Click to expand...
Click to collapse
I can get into fastboot with the phone powered off, holding the volume UP/DWN and PWR. But when connected to the computer it isn't recognized.
Sorry, but I am confused as well. I am just going off what I have seen in RootJunky's videos. In this video, https://www.youtube.com/watch?v=1LkuLb8hV6Q#t=285 at 4:44, after he does the "adb reboot bootloader" he says the device is now in "bootloader mode" which is what I am talking about, but I guess is actually Fastboot Mode. This is the same mode I am talking about getting into from the device powered off holding the volume UP/DWN and PWR buttons, but going in this way doesn't get recognized by the computer.
Travisdroidx2 said:
Once you are in the boot loader screen does "fastboot devices" recognize your device?
Click to expand...
Click to collapse
YES it does! Thanks. I kept trying "adb devices", and when it wasn't recognizing it, I figured it wasn't connected. I wasn't doing "fastboot devices". But, my USB debugging still was getting unchecked after getting back into the phone.
So with it recognizing my device in fastboot mode I should be able to go ahead with the RSD Lite flashing?
08G8V8 said:
No, I typed "fastboot flash recovery stockrecoveryfile.img"
I did just like originally when flashing TWRP, just replaced the file in the command line.
I am still rooted.
I can get into fastboot with the phone powered off, holding the volume UP/DWN and PWR. But when connected to the computer it isn't recognized.
Sorry, but I am confused as well. I am just going off what I have seen in RootJunky's videos. In this video, https://www.youtube.com/watch?v=1LkuLb8hV6Q#t=285 at 4:44, after he does the "adb reboot bootloader" he says the device is now in "bootloader mode" which is what I am talking about, but I guess is actually Fastboot Mode. This is the same mode I am talking about getting into from the device powered off holding the volume UP/DWN and PWR buttons, but going in this way doesn't get recognized by the computer.
Click to expand...
Click to collapse
OK, glad you didn't flash to bootloader. That is tricky to fix...but I've dealt with people who have done it before.
Try another PC...or re-install the drivers. Also, DO NOT use a usb 3.0 port, always use 2.0.
Bootloader = AP fastboot mode. They are one and the same. Try to get it recognized with "fastboot devices", on any PC. If you can get to that point, you can flash back to stock and recover everything. The FXZ can actually FIX a corrupted or damaged filesystem. It replaces all the relevant partitions.
Remember you do NOT use adb or usb debugging. They have nothing to do with fastboot.
---------- Post added at 09:10 PM ---------- Previous post was at 09:09 PM ----------
08G8V8 said:
YES it does! Thanks. I kept trying "adb devices", and when it wasn't recognizing it, I figured it wasn't connected. I wasn't doing "fastboot devices". But, my USB debugging still was getting unchecked after getting back into the phone.
So with it recognizing my device in fastboot mode I should be able to go ahead with the RSD Lite flashing?
Click to expand...
Click to collapse
YES!!!!
It seems you were confusing adb and fastboot. As long as "fastboot devices" recognizes your device, SO WILL RSD LITE!!!
Now follow my initial instrucitons, and you will be up and running in no time...
Thanks guys! I am going to do this tomorrow, but I feel pretty good that it is going to work.
Yes, I got VERY confused, and definitely need to go study up some more. I thought I had it, but obviously not.
Will report back tomorrow.
Happy to help
Absolutely get the Dev Edition for the same price. While Safestrap is out for other Galaxy devices with locked bootloaders (not sure if the S5 got SS yet) it allows customs Roms....but not kernel changes. With a Dev edition, there may be less development, but I'm sure there will still be some development out there.
Hi,
I looked all over the place but could not find a way to unlock the bootloader of the latest version of my device. Currently running Android 6.0 H81120p and rooting this version as well!
hammy88 said:
Hi,
I looked all over the place but could not find a way to unlock the bootloader of the latest version of my device. Currently running Android 6.0 H81120p and rooting this version as well!
Click to expand...
Click to collapse
i recommend for you to KDZ 20p refurbished..
and heres the instruccions same as 20i
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
i tried but its not working as i get stuck on waiting for device after i type the command to reboot to bootloader, installed google usb drivers , lg drivers and all but nothing seemed to be fixing the issue
hammy88 said:
i tried but its not working as i get stuck on waiting for device after i type the command to reboot to bootloader, installed google usb drivers , lg drivers and all but nothing seemed to be fixing the issue
Click to expand...
Click to collapse
did you click on screen when you gave the command to go into fastboot it shows some sort of numbers and leters and asks you if you want to allow phone .??/ did you
Yes I did allow the computer to have access to the phone, when i typed the command to reboot to bootloader it did, but then when i type the command to fastboot oem unlock it gets stuck on waiting for any device. I tried doing it again just to check, after i get to bootloader, i typed adb devices it doesn't show any device thats connected
hammy88 said:
Yes I did allow the computer to have access to the phone, when i typed the command to reboot to bootloader it did, but then when i type the command to fastboot oem unlock it gets stuck on waiting for any device. I tried doing it again just to check, after i get to bootloader, i typed adb devices it doesn't show any device thats connected
Click to expand...
Click to collapse
adb reboot bootloader (phone reboots to bootloader)
fastboot oem unlock (this wipes ALL data!!)
debugging tick and unlock oen in dev options.?
raptorddd said:
adb reboot bootloader (phone reboots to bootloader)
fastboot oem unlock (this wipes ALL data!!)
debugging tick and unlock oen in dev options.?
Click to expand...
Click to collapse
I checked the oem unlock, and the USB debugging thing is checked as well. Developers Options is on but same issue. I installed the latest USB drivers, installed Google USB drivers. I went to device Manger and I can't see that my device is even connected!
hammy88 said:
I checked the oem unlock, and the USB debugging thing is checked as well. Developers Options is on but same issue. I installed the latest USB drivers, installed Google USB drivers. I went to device Manger and I can't see that my device is even connected!
Click to expand...
Click to collapse
can try another computer maybe. i use the drivers from LGUP..
am afraid i do not know how to proceed from here. am pretty sure you are not alonei gave read someting similar but.. i didnt pay attention
I tried 3 other computers , did not help resolve the issue
hammy88 said:
I tried 3 other computers , did not help resolve the issue
Click to expand...
Click to collapse
i came across this try it.
http://forum.xda-developers.com/showpost.php?p=69339003&postcount=2
Use Linux dude, also try different cables. My stock g4 came with a bad cable that only charged.
I've had exactly the same problem as hammy88. Is what is referred to as "fastboot mode" the same as download mode? I know it's relatively easy to get into download mode. But "adb reboot bootloader" doesn't work for me.
Fastboot mode ≠ Download mode
If you did tick "Enable OEM unlock" , and adb reboot bootloader doesn't work, then I guess is BL is locked now.
I tried the method , i found that Android Bootloader does not have a green light, so i went to device manager to try to update the driver but it wasn't even there, clicked on view to show the hidden items or whatever then found android device, when i clicked update the driver i could not find the Google fastboot thing to update it with, all i got was either LG usb or ADB interface even thoough i downloader google fastboot usb drivers few days ago
hammy88 said:
I tried the method , i found that Android Bootloader does not have a green light, so i went to device manager to try to update the driver but it wasn't even there, clicked on view to show the hidden items or whatever then found android device, when i clicked update the driver i could not find the Google fastboot thing to update it with, all i got was either LG usb or ADB interface even thoough i downloader google fastboot usb drivers few days ago
Click to expand...
Click to collapse
Brother, be calm. Find the fastboot drivers. And update.
You will figure it out. Just do it.
So I just got my shiny new Nokia 8 and it seems to be updated to the latest version of Pie. Reading through all the root forums/threads, I'm noticing a couple issues with my phone that I'm not seeing mentioned:
-In Dev settings, OEM unlocking is off and grayed out, I can't toggle it.
-When I try to access download mode/bootloader (volume down/plug in cable from pc) my screen does a little flashy thing and then goes straight to the battery percentage.
-I can ADB devices just fine and see the phone, when I ADB reboot bootloader, the phone gets stuck on a screen showing "powered by android'', with "download mode" in the upper left corner, and any fastboot commands return absolutely nothing.
Any tips or suggestions?
Many thanks
jgro1976 said:
So I just got my shiny new Nokia 8 and it seems to be updated to the latest version of Pie. Reading through all the root forums/threads, I'm noticing a couple issues with my phone that I'm not seeing mentioned:
-In Dev settings, OEM unlocking is off and grayed out, I can't toggle it.
-When I try to access download mode/bootloader (volume down/plug in cable from pc) my screen does a little flashy thing and then goes straight to the battery percentage.
-I can ADB devices just fine and see the phone, when I ADB reboot bootloader, the phone gets stuck on a screen showing "powered by android'', with "download mode" in the upper left corner, and any fastboot commands return absolutely nothing.
Any tips or suggestions?
Many thanks
Click to expand...
Click to collapse
- you cant toggle it because you have not unlocked the bootloader. Sometimes even after you unlock it it will be greyed out, which isnt of importance. To unlock the bootloader downgrade to Oreo November update by sideloading the relevant ROM, then follow the the official HMD instructions.
- Make sure USB debugging is turned on under developer options.
- Are you attempting to boot into the OS or recovery here? Abd reboot is enough to boot into your system. To boot into recovery use adb reboot recovery. Or do it manually using the keys.
Ok, everything I've read so far says to make sure OEM unlock is enabled before you do anything else, so you've confused me now. And none of the guides talk about sideloading the ROM, so you've thrown a new twist with that as well.
USB debugging is enabled, and my computer sees the device via adb devices, but if I try adb reboot recovery, all I get is the little android icon with the red triangle over him, and if I try adb reboot bootloader, basically nothing happens. And I wasn't trying to boot into the OS or recovery, I'm not a noob but maybe this phone is just different enough from what I'm used to I guess.
So basically I'm stuck right now, can't boot into recovery, can't sideload a ROM, can't boot into the bootloader/download mode either.
MDV106 said:
- you cant toggle it because you have not unlocked the bootloader. Sometimes even after you unlock it it will be greyed out, which isnt of importance. To unlock the bootloader downgrade to Oreo November update by sideloading the relevant ROM, then follow the the official HMD instructions.
- Make sure USB debugging is turned on under developer options.
- Are you attempting to boot into the OS or recovery here? Abd reboot is enough to boot into your system. To boot into recovery use adb reboot recovery. Or do it manually using the keys.
Click to expand...
Click to collapse
Actually, thank you, you got me thinking and I was able to get downgraded to the Oreo, got my code from Nokia and unlock.key, now the only thing I'm still having a hard time with is my computer won't detect my phone in fastboot mode. Works just fine in normal ADB commands, but no fastboot...
You'd think my drivers are all fine and that since ADB sees the device, but maybe not?
jgro1976 said:
Ok, everything I've read so far says to make sure OEM unlock is enabled before you do anything else, so you've confused me now. And none of the guides talk about sideloading the ROM, so you've thrown a new twist with that as well.
USB debugging is enabled, and my computer sees the device via adb devices, but if I try adb reboot recovery, all I get is the little android icon with the red triangle over him, and if I try adb reboot bootloader, basically nothing happens. And I wasn't trying to boot into the OS or recovery, I'm not a noob but maybe this phone is just different enough from what I'm used to I guess.
So basically I'm stuck right now, can't boot into recovery, can't sideload a ROM, can't boot into the bootloader/download mode either.
Click to expand...
Click to collapse
Bootloader, unlocked! Now if I can get the rest of my home wireless **** to work this well/easily, thank you for getting me pointed in the right direction, all good here (I hope).
jgro1976 said:
Actually, thank you, you got me thinking and I was able to get downgraded to the Oreo, got my code from Nokia and unlock.key, now the only thing I'm still having a hard time with is my computer won't detect my phone in fastboot mode. Works just fine in normal ADB commands, but no fastboot...
You'd think my drivers are all fine and that since ADB sees the device, but maybe not?
Click to expand...
Click to collapse
jgro1976 said:
Bootloader, unlocked! Now if I can get the rest of my home wireless **** to work this well/easily, thank you for getting me pointed in the right direction, all good here (I hope).
Click to expand...
Click to collapse
Im guessing you finally realised they after getting the android icon with the red triangle u have to press volume up and hold it then tap the power key to enter the recovery. Good to know you managed to unlock the bootloader eventually.
A lot of people have been having issues with fastboot, especially on Windows machines . Try restarting the shell or use a different USB port on your computer?also maybe try a different driver version and see if it helps.
Hi, Im kinda new to this bootloader thingy. What happen is, i updated the razer phone 2 to Pie, but notice wifi and sim card cant be detect. Even factory reset fails. So i thought of flashing new image on it. KINDA easy on my oneplus, but im not sure where I gone wrong on this razer phone 2, i accidentally unlock the bootloader. NOW the problem is HOW to relock it back? i been follow all youtube and guides all over the place but still fails.
The state of device atm, cannot be boot into Download Mode. Everytime I plug in usb c from Windows, it will boot into unlock bootloader warning page, and continue boot into the homescreen. testing the adbtools, fastboot also to no avail. Can anyone help and guide me how to relocking it back? Maybe i type wrongly on cmd or maybe other android steps not similar to razer one etc....:crying:help much appreciated.
Hold volume down while turning on. Then fastboot flashing lock.
the stock usb doesnt send things correctly in BL mode, https://www.amazon.com/Blackweb-3-Foot-Charge-Cable-Connector/dp/B07SG7P3KZ/ worked for me. with the correct usb cable you should be able to perform the lock commands correctly. can you give us more detail of what you tried on this phone so we know if we need to provide you additional information?
https://developer.razer.com/razer-phone-dev-tools/general-instructions/
"Locking the Bootloader
Locking the bootloader is recommended for security reasons. Some applications will not work with an unlocked bootloader.
Start the Phone in Download Mode with one of the following methods:
Using the adb tool: With the Phone powered on, execute: adb reboot bootloader Enter Download Mode:
Plug in a USB cable to connect your Razer Phone to your computer, Power Off the Phone, then turn it on and immediately press and hold the Volume Down button until “Download Mode” appears on screen.
Lock the critical partitions of the Bootloader first by running this command: fastboot flashing lock_critical
Your Razer Phone will show you a confirmation screen. Use the Volume Up/Volume Down buttons for navigation, and press the Power button to select. Your Phone will reboot."
I can't seem to enter download mode. All I have is fastboot mode and the option to either reboot, close the phone or enter recovery mode. I would really like to lock the bootloader, but I can't seem to be able to detect my phone on my PC even though I installed the fastboot driver.
The_Vinlander said:
I can't seem to enter download mode. All I have is fastboot mode and the option to either reboot, close the phone or enter recovery mode. I would really like to lock the bootloader, but I can't seem to be able to detect my phone on my PC even though I installed the fastboot driver.
Click to expand...
Click to collapse
You must use a USB 2.0 port. The RP2 isn't detected by fastboot when connected to a 3/3.1 port.
Reznor7 said:
You must use a USB 2.0 port. The RP2 isn't detected by fastboot when connected to a 3/3.1 port.
Click to expand...
Click to collapse
I tried this, but to no avail. I tried with 2 cables I had and it keeps telling me < waiting for device > when I enter this command; fastboot flashing lock_critical
The_Vinlander said:
I tried this, but to no avail. I tried with 2 cables I had and it keeps telling me < waiting for device > when I enter this command; fastboot flashing lock_critical
Click to expand...
Click to collapse
You need to go into your device manager and select [ android bootloader interface ] while in fastboot