Related
So I just got the new 7.1.1 beta and installed on nexus 6p, during the reboot the phone froze on "google" screen. After 30 mins i rebooted the device and got the message it is corrupted. I tried following the instructions here https://developers.google.com/android/images and I cannot run "fastboot flashing unlock" is there any workaround for it. I have also tried Nexus Root toolkit. Please help.
tennyson24 said:
So I just got the new 7.1.1 beta and installed on nexus 6p, during the reboot the phone froze on "google" screen. After 30 mins i rebooted the device and got the message it is corrupted. I tried following the instructions here https://developers.google.com/android/images and I cannot run "fastboot flashing unlock" is there any workaround for it. I have also tried Nexus Root toolkit. Please help.
Click to expand...
Click to collapse
Hello... Was it a Google pushed OTA or you tried to update with ADB sideload? Maybe try to sideload 7.1.2 beta 2...
Good luck...
tennyson24 said:
So I just got the new 7.1.1 beta and installed on nexus 6p, during the reboot the phone froze on "google" screen. After 30 mins i rebooted the device and got the message it is corrupted. I tried following the instructions here https://developers.google.com/android/images and I cannot run "fastboot flashing unlock" is there any workaround for it. I have also tried Nexus Root toolkit. Please help.
Click to expand...
Click to collapse
A little more information could be really helpful. Though why are you not able to run "fastboot flashing unlock" command?
DJBhardwaj said:
A little more information could be really helpful. Though why are you not able to run "fastboot flashing unlock" command?
Click to expand...
Click to collapse
From my understanding the fastboot flashing unlock" command does not work because I did not Enable OEM Unlock in the Developer Options menu.
5.1 said:
Hello... Was it a Google pushed OTA or you tried to update with ADB sideload? Maybe try to sideload 7.1.2 beta 2...
Good luck...
Click to expand...
Click to collapse
It was an OTA update. I will try to sideload it.
tennyson24 said:
From my understanding the fastboot flashing unlock" command does not work because I did not Enable OEM Unlock in the Developer Options menu.
Click to expand...
Click to collapse
Okay. So did you try wiping data partition/factory reset option in the recovery?
DJBhardwaj said:
Okay. So did you try wiping data partition/factory reset option in the recovery?
Click to expand...
Click to collapse
When I go to recovery it goes back to fastboot mode.
tennyson24 said:
When I go to recovery it goes back to fastboot mode.
Click to expand...
Click to collapse
It doesn't show an Android bot on the screen when you choose recovery mode from bootloader?
tennyson24 said:
So I just got the new 7.1.1 beta and installed on nexus 6p, during the reboot the phone froze on "google" screen. After 30 mins i rebooted the device and got the message it is corrupted. I tried following the instructions here https://developers.google.com/android/images and I cannot run "fastboot flashing unlock" is there any workaround for it. I have also tried Nexus Root toolkit. Please help.
Click to expand...
Click to collapse
No workaround. Unfortunately if you don't have access to recovery mode you can't sideload anything either because ADB won't work in fastboot mode. If you are locked, no recovery mode and bootlooping, the device is pretty much toast. Sorry. Hopefully you have some kind of warranty you can look into.
Hi,
I have TWRP but I want to use the default bootloader. Is there a way to restore it back to stock without losing my apps and settings?
I downloaded (A2017UV1.1.B35 (Nougat) (Post # 2 or Click Here)) from here:
https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
https://androidfilehost.com/?w=file...c9cf15e47b9a9c4af6f1239b585792c06c0520ebc3480
I extracted the recovery.img
then I followed this:
https://www.theandroidsoul.com/how-to-install-twrp-recovery-via-fastboot/
But after I type this:
adb reboot bootloader
I am in the booting black screen for 5 seconds, as the loading screen tells me, before it reboots. Either way when I call this command right after:
fastboot flash recovery recovery.img
I am getting "waiting for device" print and it never finishes. Before that ADB sees my device. What do I need to do so I can fix this?
Thanks in advance.
lachdanan said:
Hi,
I have TWRP but I want to use the default bootloader. Is there a way to restore it back to stock without losing my apps and settings?
I downloaded (A2017UV1.1.B35 (Nougat) (Post # 2 or Click Here)) from here:
https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
https://androidfilehost.com/?w=file...c9cf15e47b9a9c4af6f1239b585792c06c0520ebc3480
I extracted the recovery.img
then I followed this:
https://www.theandroidsoul.com/how-to-install-twrp-recovery-via-fastboot/
But after I type this:
adb reboot bootloader
I am in the booting black screen for 5 seconds, as the loading screen tells me, before it reboots. Either way when I call this command right after:
fastboot flash recovery recovery.img
I am getting "waiting for device" print and it never finishes. Before that ADB sees my device. What do I need to do so I can fix this?
Thanks in advance.
Click to expand...
Click to collapse
First of all it would be a good start to actually get fastboot mode :laugh: You should actually follow a guide instead of trying to do this by your own. Find a guide for the U (assuming that you have an U). You'll have to install fastboot via miflash or whatever
Thanks the guides I found online all advise to use that fastboot command. That's why I couldn't figure it out. I have A2017U yes. Do you know any guide for this?
I will google more using your miflash keyword. Thanks again
The toolkit can do this for you. Make sure you are 100% stock bootstack, recovery, and system, with everything working, before you attempt to lock your bootloader. Lots of people ignore that warning and brick their phones. I'm not sure if your apps and data survive a lock.
I tried to lock mine via adb and bricked it. Luckily, the RMA people believed me that it was a failed software update and fixed it for me. I wouldn't try to do that again ^^
lachdanan said:
Thanks the guides I found online all advise to use that fastboot command. That's why I couldn't figure it out. I have A2017U yes. Do you know any guide for this?
I will google more using your miflash keyword. Thanks again
Click to expand...
Click to collapse
Were the guides that you found online for the Axon 7? Because I meant HERE AT XDA...
Hi guys. Few days ago I unlocked the bootloader of my Moto G4 plus, install twrp recovery and root the phone. Then I made the mistake of trying to install an update from OTA and since that day it is impossible to start the phone normally. It always starts in recovery mode, then I must go to restart to start in fastboot mode and next, select start to be able to use it. I reinstall the latest version of the recovery twrp and the ROM of LineageOS but nothing changes. Can someone tell me if there is any console command I can execute in the phone to start normally?
Thanks for your time...
Eduadc said:
Hi guys. Few days ago I unlocked the bootloader of my Moto G4 plus, install twrp recovery and root the phone. Then I made the mistake of trying to install an update from OTA and since that day it is impossible to start the phone normally. It always starts in recovery mode, then I must go to restart to start in fastboot mode and next, select start to be able to use it. I reinstall the latest version of the recovery twrp and the ROM of LineageOS but nothing changes. Can someone tell me if there is any console command I can execute in the phone to start normally?
Thanks for your time...
Click to expand...
Click to collapse
Please refer here, you bricked your device by taking ota while on custom recovery https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
strongst said:
Please refer here, you bricked your device by taking ota while on custom recovery https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Click to expand...
Click to collapse
Thanks for your answer. I don't understand the reference. I can flash any firmware without problem.
I looking for a commands to repair the boot because I have a boot loop with recovery mode.
I can use the phone but only across: recovery > restart > bootloader this restart in fastboot mode, next I select "start" And the phone boot with Android....
I whant to start in Android directly... I whant (if exists) any console command or any solution to fix the boot problem.
Eduadc said:
Thanks for your answer. I don't understand the reference. I can flash any firmware without problem.
I looking for a commands to repair the boot because I have a boot loop with recovery mode.
I can use the phone but only across: recovery > restart > bootloader this restart in fastboot mode, next I select "start" And the phone boot with Android....
I whant to start in Android directly... I whant (if exists) any console command or any solution to fix the boot problem.
Click to expand...
Click to collapse
Oh, then you can try using these commands through fastboot:
mfastboot oem fb_mode_set
mfastboot oem fb_mode_clear
strongst said:
Oh, then you can try using these commands through fastboot:
mfastboot oem fb_mode_set
mfastboot oem fb_mode_clear
Click to expand...
Click to collapse
Thanks for your reply again. I tried the commands but nothing changes....
Eduadc said:
Thanks for your reply again. I tried the commands but nothing changes....
Click to expand...
Click to collapse
If your Issue resolved..then tell me ...how you did it....i am also stuck on that bootloop on recovery mode
I'm trying to install TWRP recovery on my essential phone. this is the guide i am using, though pretty much every guide i found follows the same commands:
https://android.gadgethacks.com/how-to/install-twrp-recovery-essential-ph-1-0187660/
The command to determine my current slot returned that i am on slot_b, and when i try to flash the twrp img to slot_a, it sits trying to write. it never crashes but doesn't get anywhere. nothing is happening either in the command prompt window or on the phone screen.
I'm not sure what the issue is. I've updated the android sdk to the newest version and confirmed that I'm using that version of fastboot. I've also updated essential's windows drivers for the device, and rebooted the bootloader several times.
EDIT: I have noticed that on the phone screen when in the bootloader, it says "SECURE BOOT - yes". i don't know if this is important, but when i ran "fastboot oem device-info" it said true for unlocked and unlocked-critical.
Ricx94 said:
I'm trying to install TWRP recovery on my essential phone. this is the guide i am using, though pretty much every guide i found follows the same commands:
https://android.gadgethacks.com/how-to/install-twrp-recovery-essential-ph-1-0187660/
The command to determine my current slot returned that i am on slot_b, and when i try to flash the twrp img to slot_a, it sits trying to write. it never crashes but doesn't get anywhere. nothing is happening either in the command prompt window or on the phone screen.
I'm not sure what the issue is. I've updated the android sdk to the newest version and confirmed that I'm using that version of fastboot. I've also updated essential's windows drivers for the device, and rebooted the bootloader several times.
EDIT: I have noticed that on the phone screen when in the bootloader, it says "SECURE BOOT - yes". i don't know if this is important, but when i ran "fastboot oem device-info" it said true for unlocked and unlocked-critical.
Click to expand...
Click to collapse
Have you the latest twrp.img from the twrp.me site?
Do you have a type c to USB connector thing? Bluetooth keyboard?
If yes, fastboot flash boot twrp.img.
You might need the Bluetooth keyboard in case of not having touch response.
dirtyreturn said:
Have you the latest twrp.img from the twrp.me site?
Do you have a type c to USB connector thing? Bluetooth keyboard?
If yes, fastboot flash boot twrp.img.
You might need the Bluetooth keyboard in case of not having touch response.
Click to expand...
Click to collapse
i do have the newest file. i even tried redownloading it thinking the file might have been corrupted.
i haven't gotten to the part where i would need a usb otg keyboard yet, though i have one for when i make it that far.
I would check out the PH1 Development Telegram Channel as if your on stock they have boot images with TWRP and root already added and then all you have to do is fastboot flash the patched image and you will have TWRP with working touch and root as well. Here is the link to the channel if your interested https://t.me/EssentialPH1DEV
dirtyreturn said:
Have you the latest twrp.img from the twrp.me site?
Do you have a type c to USB connector thing? Bluetooth keyboard?
If yes, fastboot flash boot twrp.img.
You might need the Bluetooth keyboard in case of not having touch response.
Click to expand...
Click to collapse
robertbarber said:
I would check out the PH1 Development Telegram Channel as if your on stock they have boot images with TWRP and root already added and then all you have to do is fastboot flash the patched image and you will have TWRP with working touch and root as well. Here is the link to the channel if your interested https://t.me/EssentialPH1DEV
Click to expand...
Click to collapse
I'm not having issues with touch yet. haven't even made it far enough to know if I'm having an issue with touch in twrp...
I can't flash anything for some reason.
I'm stuck at "Sending 'boot_b' (48712 KB)" and nothing happens. every post I've seen says this should take less than 2 seconds but I've waited up to 10 minutes some tries and nothing happens. i need to restart the bootloader after trying this each time before it will let me try again.
Ricx94 said:
I'm not having issues with touch yet. haven't even made it far enough to know if I'm having an issue with touch in twrp...
I can't flash anything for some reason.
I'm stuck at "Sending 'boot_b' (48712 KB)" and nothing happens. every post I've seen says this should take less than 2 seconds but I've waited up to 10 minutes some tries and nothing happens. i need to restart the bootloader after trying this each time before it will let me try again.
Click to expand...
Click to collapse
Did you do the two unlock commands via fastboot? Firstly.?(not intending to dumb you down or anything)
Did you try with just - fastboot flash boot twrp.img ?
P.S. !! Definitely check out the posted telegram channel! Super helpful group of people.
dirtyreturn said:
Did you do the two unlock commands via fastboot? Firstly.?(not intending to dumb you down or anything)
Did you try with just - fastboot flash boot twrp.img ?
P.S. !! Definitely check out the posted telegram channel! Super helpful group of people.
Click to expand...
Click to collapse
I did fastboot flashing unlock and unlock_critical. Those seemed to work it shows up as being unlocked and factory reset.
To try to flash twrp I ran fastboot flash boot_a (also tried boot_b and boot) twrp.img and it tried to send but just sits trying and isn't getting anywhere.
Ricx94 said:
I did fastboot flashing unlock and unlock_critical. Those seemed to work it shows up as being unlocked and factory reset.
To try to flash twrp I ran fastboot flash boot_a (also tried boot_b and boot) twrp.img and it tried to send but just sits trying and isn't getting anywhere.
Click to expand...
Click to collapse
https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
Ricx94 said:
I did fastboot flashing unlock and unlock_critical. Those seemed to work it shows up as being unlocked and factory reset.
To try to flash twrp I ran fastboot flash boot_a (also tried boot_b and boot) twrp.img and it tried to send but just sits trying and isn't getting anywhere.
Click to expand...
Click to collapse
Are you using cmd or power shell for Windows. What ports are you using,2.0 or 3.0 and which type of cord. A-c or c-c
Sent from my PH-1 using Tapatalk
dazeone said:
Are you using cmd or power shell for Windows. What ports are you using,2.0 or 3.0 and which type of cord. A-c or c-c
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I've tried both CMD and Powershell
my computer only has USB 3.0 and 3.1 ports, all type A, so I'm using USB A-C cables. the cables are both only USB 2.0.
so I'm not sure why i tried this but it seemed to work...
I sent the flash command and when it got to the part it normally freezes at, i restarted the bootloader using volume and power keys on the phone. then while it was restarting i sent the command again, and as soon as it got to the bootloader the command activated and worked instantly. now I'm toying around with this newfound knowledge and i think i have twrp working. just wiped phone again and installed AOSIP so here we go
Ricx94 said:
so I'm not sure why i tried this but it seemed to work...
I sent the flash command and when it got to the part it normally freezes at, i restarted the bootloader using volume and power keys on the phone. then while it was restarting i sent the command again, and as soon as it got to the bootloader the command activated and worked instantly. now I'm toying around with this newfound knowledge and i think i have twrp working. just wiped phone again and installed AOSIP so here we go
Click to expand...
Click to collapse
Sorry... I didn't read...
When you are stuck at waiting for device .. if you unplug... Run the command... And then plug in... It will sometimes take...
Why... I don't know
Sent from my PH-1 using Tapatalk
Ricx94 said:
so I'm not sure why i tried this but it seemed to work...
I sent the flash command and when it got to the part it normally freezes at, i restarted the bootloader using volume and power keys on the phone. then while it was restarting i sent the command again, and as soon as it got to the bootloader the command activated and worked instantly. now I'm toying around with this newfound knowledge and i think i have twrp working. just wiped phone again and installed AOSIP so here we go
Click to expand...
Click to collapse
Nice to hear! Be sure to have the twrpinstaller.zip handy to flash after the ROM!! This preserves twrp.
rignfool said:
Sorry... I didn't read...
When you are stuck at waiting for device .. if you unplug... Run the command... And then plug in... It will sometimes take...
Why... I don't know
Click to expand...
Click to collapse
I need to send the command while the bootloader is restarting. It works consistently for me. Unplugging and repluging won't do it; only restarting bootloader. I honestly can't explain it but it's working great.
Ricx94 said:
I need to send the command while the bootloader is restarting. It works consistently for me. Unplugging and repluging won't do it; only restarting bootloader. I honestly can't explain it but it's working great.
Click to expand...
Click to collapse
HOLY CRAP THANK YOU
I've been going insane and this worked for whatever reason. You are awesome!
Zach Alt said:
HOLY CRAP THANK YOU
I've been going insane and this worked for whatever reason. You are awesome!
Click to expand...
Click to collapse
Glad i could be of service
I got my 6P bootloader locked (ofcourse by accident) and now it has become a paperweight. is there any solution for this issue? I can boot into bootloader, but cannot flash anything. No recovery is installed and No OS is installed too...
Shabbirkt said:
I got my 6P bootloader locked (ofcourse by accident) and now it has become a paperweight. is there any solution for this issue? I can boot into bootloader, but cannot flash anything. No recovery is installed and No OS is installed too...
Click to expand...
Click to collapse
If the device can be seen by a computer, reflash the factory image. If not, no idea.
Dear friend if you have no OS installed and the Bootloader blocked the only thing you can try is using an OTG cable and a flash memory to download the latest version of the factory image but OTA and copy it to the flash memory and try to flash it from the stock recovery
felixpaz1992 said:
Dear friend if you have no OS installed and the Bootloader blocked the only thing you can try is using an OTG cable and a flash memory to download the latest version of the factory image but OTA and copy it to the flash memory and try to flash it from the stock recovery
Click to expand...
Click to collapse
i cannot do that. how can i access OTG ? booting into recovery reboots phone in endless loop of booting into Google written screen and Screen turns off...
Can you boot to bootloader? (With the device powered off, hold Volume Down + Power)
Then run
Code:
fastboot devices
If you see your mobile then you should be able to flash the factory ROM.
See section 10 in https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
ghost shell said:
Can you boot to bootloader? (With the device powered off, hold Volume Down + Power)
Then run
If you see your mobile then you should be able to flash the factory ROM.
See section 10 in https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
yup... fastboot devices detects the phone...
but when i try to flash factory image it says cannot flash as bootloader is locked.
Shabbirkt said:
yup... fastboot devices detects the phone...
but when i try to flash factory image it says cannot flash as bootloader is locked.
Click to expand...
Click to collapse
Code:
fastboot flashing unlock
Note that it will delete all your data.
Please let me know if after that you're able to flash the factory image.
ghost shell said:
Note that it will delete all your data.
Please let me know if after that you're able to flash the factory image.
Click to expand...
Click to collapse
i tried that brother... it says 'oem unlock is not allowed'.
Shabbirkt said:
yup... fastboot devices detects the phone...
but when i try to flash factory image it says cannot flash as bootloader is locked.
Click to expand...
Click to collapse
Shabbirkt said:
i tried that brother... it says 'oem unlock is not allowed'.
Click to expand...
Click to collapse
I don't know if this will help you but
Code:
fastboot boot twrp.img
Maybe you're able to unlock it or flash from there?
ghost shell said:
I don't know if this will help you but
Maybe you're able to unlock it or flash from there?
Click to expand...
Click to collapse
i appreciate your effort brother...
but i already tried that and no luck...
Shabbirkt said:
yup... fastboot devices detects the phone...
but when i try to flash factory image it says cannot flash as bootloader is locked.
Click to expand...
Click to collapse
Shabbirkt said:
i appreciate your effort brother...
but i already tried that and no luck...
Click to expand...
Click to collapse
No worries. Normally I wouldn't dig into it... but who knows, next time could be me in the same spot.
If you can boot using twrp then you can get adb shell with root, right?
Code:
adb shell getprop | grep -i unlock
I'm getting
[ro.oem_unlock_supported]: [1]
[sys.oem_unlock_allowed]: [1]
Click to expand...
Click to collapse
I'm wondering if you set those props to 1 maybe you'll be able to flash images again.
Code:
adb -d shell setprop ro.oem_unlock_supported 1
adb -d shell setprop sys.oem_unlock_allowed 1
...
Spending way more time than I should lol...
If the above doesn't work check these
https://old.reddit.com/r/AndroidQue...astboot_oem_unlock_without_enable_oem_unlock/
https://gist.github.com/zhuowei/79b6fbcd9ba9f1726163
https://forum.xda-developers.com/nexus-6p/general/to-unlock-phone-twrp-flashed-t3334083
https://forum.xda-developers.com/android/software/frp-destroyer-flashable-zip-t3920067
Wait Brother...
My phone just mysteriously booted up... I dun know how this happend or what made it do so... And Thanks a lot for your assistance...
Another thing is my phone has booted into FRP lock, and i kinda dun know the Email associated with it. Is there any way to bypass it?
Shabbirkt said:
Wait Brother...
My phone just mysteriously booted up... I dun know how this happend or what made it do so... And Thanks a lot for your assistance...
Another thing is my phone has booted into FRP lock, and i kinda dun know the Email associated with it. Is there any way to bypass it?
Click to expand...
Click to collapse
How don't you know the email associated with it ?