Axon 7 A2017G from Lineage OS go back to Stock and Lock Bootloader without Problems - ZTE Axon 7 Questions & Answers

1.) You must have a full ZIP from ZTE
2.) Flash back the Original Recovery from the Original ZIP e.g. B08 B10 with ADB Fastboot command ( You must ticked OEM unlock on and USB debugging on in Developer Setting ) in Lineage.
2.1) push Power and tick restart in Bootloader.
2.2) go to Minimal ADB and Fastboot and type fastboot flash recovery recovery.img.
2.3) After this push with the Volume down recovery ,tick power.
OK! You can see the ORIGINALRecovery from ZTE.
3.) You must put a SD Card in Phone with the Original Update.zip
4.) Go in recovery and tick Update from SD card. Search the Update.zip and press Power.
5.) Wait until the Flash Process is finished.
6.) Tick Factory reset with Volume up/down push Power wait.
7.) Tick format Cache with Volume up / down push Power wait.
8.) Push Power to start your Phone with the Original Stock.
9.) After this you go to Settings / Build Number and Tick that seven Times to activate Developer Options, go back to setting and tick Developer Options ,here you must tick the OEM unlocking and USB debugging.
10.) Open Command window on PC and type "fastboot reboot bootloader" the phone shut down and restart in bootloader mode.
11.) in the Comand window you type" Fastboot oem lock" the Phone reboot and the bootloaer is locked. All your Data is lost in this Process!!![COLOR="Red"][/COLOR]
Voila all is done!! Original AXON 7 with Stock Rom .
I have test this with my Axon 7 Model A2017G and i have no Problem.
Sorry for my bad English.

Thanks for writing this out. Will be useful in case I need to switch back in the future
Where do you get the stock rom zip file though? zteusa.com somewhere?

spacemanvt said:
Thanks for writing this out. Will be useful in case I need to switch back in the future
Where do you get the stock rom zip file though? zteusa.com somewhere?
Click to expand...
Click to collapse
There is a global site where you can get the file. http://www.ztedevice.com/support/detail?id=C3BAC27838C4497C80C05EE008527885
Sent from my ZTE A2017G using XDA-Developers Legacy app

Hello,
I recovered my old stock recovery and when trying to apply update from sd card, it gives me this error: "Couldn´t mount /sdcard. installation aborted"
What can I do?
Edit: Solved by formatting the SD card

What is the ADB fastboot command to flash stock recovery?

JP_93 said:
What is the ADB fastboot command to flash stock recovery?
Click to expand...
Click to collapse
fastboot flash recovery "stock Recovery"

Flash the Original recovery.img from your Update.zip!!
JP_93 said:
What is the ADB fastboot command to flash stock recovery?
Click to expand...
Click to collapse
open Update.zip with e.g Winrar and unpacking recovery.img to the ADB directory. OK?!
Then open a Command Window and Type : fatboot flash recovery recovery.img . Wait.
Shutdown your Phone . Restart Phone wit push Power and Volume up.
tick with the Volume down botem update from SD card.

julk13 said:
fastboot flash recovery "stock Recovery"
Click to expand...
Click to collapse
Thanks!
tester2017 said:
open Update.zip with e.g Winrar and unpacking recovery.img to the ADB directory. OK?!
Then open a Command Window and Type : fatboot flash recovery recovery.img . Wait.
Shutdown your Phone . Restart Phone wit push Power and Volume up.
tick with the Volume down botem update from SD card.
Click to expand...
Click to collapse
Thanks for the help, I will try now

10.) Open Command window on PC and type "fastboot reboot bootloader" the phone shut down and restart in bootloader mode.
Click to expand...
Click to collapse
You made a mistake there as you have to enter "adb reboot bootloader" instead of fastboot. Other than that, it works perfectly. Thank you.

I can't get my bootloader locked. Under dev options, "OEM Unlocking" it grayed out.

idigg said:
I can't get my bootloader locked. Under dev options, "OEM Unlocking" it grayed out.
Click to expand...
Click to collapse
Did you find a solution to this? I'm running into the same problem with OEM unlocking being grayed out. I returned to stock just fine, but my problem is booting into the bootloader. Every time I try, it just goes to the "your device cannot be checked for corruption and will reboot in 5 seconds" screen. During this screen and during the screen that comes up you press the volume keys for the options menu, the fastboot oem lock command does not seem to work. Fastboot devices doesn't show any devices listed either

spearman792 said:
Did you find a solution to this? I'm running into the same problem with OEM unlocking being grayed out. I returned to stock just fine, but my problem is booting into the bootloader. Every time I try, it just goes to the "your device cannot be checked for corruption and will reboot in 5 seconds" screen. During this screen and during the screen that comes up you press the volume keys for the options menu, the fastboot oem lock command does not seem to work. Fastboot devices doesn't show any devices listed either
Click to expand...
Click to collapse
Seconded, I'm having the very same problem. Strange thing is, I cannot boot into booloader. I can boot into recovery, I can boot to system but whan I try to boot into bootloader via adb reboot bootloader, the phone just boots into system. If I try Power/Vol-Down, I will eventually land in FTM mode.
Anybody any clue?
SOLVED: After using the Windows based Axon7Toolkit which used Miflash to restore fastboot, I was able to boot into bootloader and also re-lock it.

robertaramar said:
Seconded, I'm having the very same problem. Strange thing is, I cannot boot into booloader. I can boot into recovery, I can boot to system but whan I try to boot into bootloader via adb reboot bootloader, the phone just boots into system. If I try Power/Vol-Down, I will eventually land in FTM mode.
Anybody any clue?
SOLVED: After using the Windows based Axon7Toolkit which used Miflash to restore fastboot, I was able to boot into bootloader and also re-lock it.
Click to expand...
Click to collapse
You couldn't boot into bootloader because there was no bootloader mode. As soon as you update to a recent Nougat build (or an upcoming one) via official zips, your aboot.img will be changed and you won't have bootloader mode anymore. Axon7toolkit relies on fastboot, so it flashes a package through MiFlash that gets you fastboot support.
Jus sayin

Thanks for the clarification.
Is there an aboot.img I can flash e.g. via axon7tool so I can enable fastboot again?
Would that be counted as a warranty void by ZTE?

robertaramar said:
Thanks for the clarification.
Is there an aboot.img I can flash e.g. via axon7tool so I can enable fastboot again?
Would that be counted as a warranty void by ZTE?
Click to expand...
Click to collapse
You can use the A2017U_FASTBOOT_UNLOCK_EDL from 4pda guys with MiFlash. Doesn't matter if you have a G, use this one
Actually axon7toolkit seems to flash that every time it does something related to fastboot. And after you lock it, you can install an official update zip (the latest one for example) and you'll get your phone totally stock, bootloader mode will be blocked.

Related

Unable to Flash Custom Recovery

Hi guys,
Im on the cm12s, and unlocked bootloader but im unable to get into custom recovery, it keeps reverting to Cynogen recovery.
I tried toolkit also, it flashes and then it shows waiting for device, i manually boot into recovery its just a blank screen.
Please help i need root and ROMS
varun.gid said:
Hi guys,
Im on the cm12s, and unlocked bootloader but im unable to get into custom recovery, it keeps reverting to Cynogen recovery.
I tried toolkit also, it flashes and then it shows waiting for device, i manually boot into recovery its just a blank screen.
Please help i need root and ROMS
Click to expand...
Click to collapse
how did you unlock bootloader ?
may be using adb drivers right ?
so if you are using adb drivers then follow this procedure ....
copy this recovery file in your adb folder LINK
now go to adb folder
now press and hold shift button and right click on empty space there you will see open cmd , click on it cmd will open
now copy below code (this is for CM12 only)
Code:
fastboot -i 0x1ebf flash recovery recovery_twrp.img
anow right click in cmd and click on paste.
hit enter and after a while you will se 'Okay ' message at the end.
bingo you have flasher recovery :highfive: :good:
ashish_zarekar said:
how did you unlock bootloader ?
may be using adb drivers right ?
so if you are using adb drivers then follow this procedure ....
copy this recovery file in your adb folder LINK
now go to adb folder
now press and hold shift button and right click on empty space there you will see open cmd , click on it cmd will open
now copy below code (this is for CM12 only)
Code:
fastboot -i 0x1ebf flash recovery recovery_twrp.img
anow right click in cmd and click on paste.
hit enter and after a while you will se 'Okay ' message at the end.
bingo you have flasher recovery :highfive: :good:
Click to expand...
Click to collapse
I tried this method.. but it always reverts to stock recovery. and when i boot into recovery directly from fastboot i get a blank screen. Please help.
varun.gid said:
I tried this method.. but it always reverts to stock recovery. and when i boot into recovery directly from fastboot i get a blank screen. Please help.
Click to expand...
Click to collapse
have you tried with this recovery which i provided in link ?
first try using this recovery.
earlier i also face this.
now go to this thread download software from this thread only. there are two thread for this tool but i prefer you to go to this one.
GUIDE
now unlock bootloader.
and go for step 4(which flash twrp recovery)
now flash the recovery which is provided by me using code.
and now go can go into recovery
****************************************************************************************************
i suggest you this guide this method do for me
Disable update CM recovery option in developer options... Then flash custom recovery.... it will work.
once flashing twrp recovery, you will need to use
Code:
fastboot -i 0x1ebf reboot
command.
remove battery after install recovery before restarting phone
then insert battery and start in custom recovery
install Custom Recovery
1) enable developer options
2)enable advance reboot and usb debugging
3)disable Update CM recovery option
4)reboot to bootloader and flash recovery
" fastboot -i 0x1ebf flash recovery recovery_twrpyulolli.img "
5) directly disconnect phone (phone displaying FASTBOOT MODE)
6) remove battery and start phone in recovery mode using volume UP+DOWN and power key
7) And YOUR are IN TWRP RECOVERY ......
THIS method work for me perfectly .....i m also having same problem of flashing custom recovery and again showing CM RECOVERY
:laugh::laugh:
Thank You...!
Which is best for yureka cwm or twrp recovery
I'm facing the same problem but this trick didn't work for me.

[HELP NEEDED] HTC One M8 won't update Android 4.4.2

So I've bought this phone a year ago and I've found out recently that its rooted.
I was trying to update to 4.4.3 and stuck at (entering recovery now)..
I even tried factory reset several times and stuck at the same screen, and as a result I can't hear in-call sound and I don't know what to do anymore.
At the boot loader screen it says
*Tampered*
*unlocked*
And S-on
Any chance I can get it updated and working?? :angel:
Sam087 said:
So I've bought this phone a year ago and I've found out recently that its rooted.
I was trying to update to 4.4.3 and stuck at (entering recovery now)..
I even tried factory reset several times and stuck at the same screen, and as a result I can't hear in-call sound and I don't know what to do anymore.
At the boot loader screen it says
*Tampered*
*unlocked*
And S-on
Any chance I can get it updated and working?? :angel:
Click to expand...
Click to collapse
Flash stock recovery and try again only stock recovery can flash update not twrp,philz,cmw
sayad1 said:
Flash stock recovery and try again only stock recovery can flash update not twrp,philz,cmw
Click to expand...
Click to collapse
and how to flash stock recovery? I'm all new to this.. thanks in advance.
Sam087 said:
and how to flash stock recovery? I'm all new to this.. thanks in advance.
Click to expand...
Click to collapse
Which veriant of you mean at&t,Verizon,sprint or other ??
Do you have done setting up and&fastboot already on your desktop or laptop??
sayad1 said:
Which veriant of you mean at&t,Verizon,sprint or other ??
Do you have done setting up and&fastboot already on your desktop or laptop??
Click to expand...
Click to collapse
I have zain netwok on Unlocked HTC m8.
and yes I have adb fastboot already on my laptop
Sam087 said:
I have zain netwok on Unlocked HTC m8.
and yes I have adb fastboot already on my laptop
Click to expand...
Click to collapse
1.Put the recovery file (*. img) into a fastboot / adb folder, and open Windows Command prompt (CMD) from there.
2.Make sure the M8 drivers already installed on your computer.
3.Connect the phone into computer via USB.
Now put your phone into fastboot mode, by turning it off first, then press and hold Volume down and power button. After that, choose Fastboot mode.
5.Run the following command to CMD window:
fastboot flash recovery FileName.img
You should change the “FileName” to match with your own.
6.Now reboot system.
fastboot reboot
7.Once fully boots up, your HTC One M8 should have stock recovery, now take an OTA then apply it.
https://mega.nz/#!aAxWWTCY!TLjZ-Q9NQVGFj0GQ7AHCSxtKG-9yS5LtKsvvbS3ExBM
sayad1 said:
1.Put the recovery file (*. img) into a fastboot / adb folder, and open Windows Command prompt (CMD) from there.
2.Make sure the M8 drivers already installed on your computer.
3.Connect the phone into computer via USB.
Now put your phone into fastboot mode, by turning it off first, then press and hold Volume down and power button. After that, choose Fastboot mode.
5.Run the following command to CMD window:
fastboot flash recovery FileName.img
You should change the “FileName” to match with your own.
6.Now reboot system.
fastboot reboot
7.Once fully boots up, your HTC One M8 should have stock recovery, now take an OTA then apply it.
https://mega.nz/#!aAxWWTCY!TLjZ-Q9NQVGFj0GQ7AHCSxtKG-9yS5LtKsvvbS3ExBM
Click to expand...
Click to collapse
Thanks it worked just fine.. updating to marshmallow now

Need help, bricked my 3s

Was supposed to flash CM13 Rom. I did a full wipe including system via TWRP.
Before flashing I decided to reboot into recovery, but it didn't. Only gets stuck in the MI logo now. Can't boot into recovery anymore.
I can go into Fastboot mode. Tried flashing twrp via ADB but whenever i type 'adb devices' in command prompt it says device is offline.
Tried to enter EDL via ADB in fastboot mode, it gets stuck at 'waiting for device'.
When plugged in PC, it gets detected as USB ADB interface
Bootloader was unlocked prior, was on xioami.eu ROM before this. I have TWRP system backup of last ROM installed.
Hoping someone can point me in the right direction on what to do next. Very much appreciated, thank you.
Hi Supdow,
I was facing with the same issue and I also thought I bricked my phone... No worries. To solve it is very easy, just unlock your bootloader again with Mi UnlockTool. Than you have access to your recovery again.
Good luck!
Boesila said:
Hi Supdow,
I was facing with the same issue and I also thought I bricked my phone... No worries. To solve it is very easy, just unlock your bootloader again with Mi UnlockTool. Than you have access to your recovery again.
Good luck!
Click to expand...
Click to collapse
Do I have to apply to unlock the bootloader again like the first time?
Boesila said:
Hi Supdow,
I was facing with the same issue and I also thought I bricked my phone... No worries. To solve it is very easy, just unlock your bootloader again with Mi UnlockTool. Than you have access to your recovery again.
Good luck!
Click to expand...
Click to collapse
Was able to unlock bootloader again, but I still can't access recovery. I may have forgotten how to exactly do this since the last time I did it. What do i have to do after unlocking bootloader? I tried flashing TWRP via fastboot but it only gives me an error.
So you have a few options
1. Hold volume+ & - and power (if you have twrp)
2. Take fedosis twrp 3.1 and installer, put twrp 3.1 into extracted installer folder, then shift+right click on installer folder, open cmd, then type
fastboot flash recovery twrp_name.img
fastboot boot twrp_name.img (or do step 1)
3. Just flash dev/stable with miflash (recommendation: go into fastboot, then like step 2 go into cmd and type fastboot oem edl then flash mi rom)
Hope this helps
bekcicandrej said:
So you have a few options
1. Hold volume+ & - and power (if you have twrp)
2. Take fedosis twrp 3.1 and installer, put twrp 3.1 into extracted installer folder, then shift+right click on installer folder, open cmd, then type
fastboot flash recovery twrp_name.img
fastboot boot twrp_name.img (or do step 1)
3. Just flash dev/stable with miflash (recommendation: go into fastboot, then like step 2 go into cmd and type fastboot oem edl then flash mi rom)
Hope this helps
Click to expand...
Click to collapse
Thank you, finally on CM13 fedosis!

Boot loop after Android O DP2 update

I installed Android O DP2 update via OTA yesterday. The phone updated, rebooted to the new build and restarted abruptly and since then has been stuck in a boot loop. The Google logo shows up, goes to the android animation step and then Google logo appears again.
I don't have bootloader unlocked, don't have TWRP and have done OTA updates. I am able to get into the stock recovery mode.
How do I fix this, i.e. make it work in any way without erasing the user data? I don't mind extreme steps (without erasing user data) because I was planning to reflash 7 with unlocking & rooting today.
Try to wipe cache from recovery - in recovery hold volume-down and select "Wipe cache partition". Should do the trick
I tried, didn't work. Had to factory reset in the end. Also opted out of beta
I just read that some people that took the update from certain builds had boot loops due to the update only replacing part of the OS but leaving the 7.x.x system in place causing it to boot loop. I think it was like on android authority or something like that.
Sent from my Nexus 6P using XDA-Developers Legacy app
I have similar problem. Phone became stuck at Google logo and bootloop. I didn't have OEM unlock and debugged enable when phone was working. Now I'm stuck because It cannot flash with any factory image rom. Anyone with solution, please help. Thanks
citifone said:
I have similar problem. Phone became stuck at Google logo and bootloop. I didn't have OEM unlock and debugged enable when phone was working. Now I'm stuck because It cannot flash with any factory image rom. Anyone with solution, please help. Thanks
Click to expand...
Click to collapse
You can unlock your bootloader to flash a stock ROM. Do you need the steps?
---------- Post added at 09:54 AM ---------- Previous post was at 09:38 AM ----------
citifone said:
I have similar problem. Phone became stuck at Google logo and bootloop. I didn't have OEM unlock and debugged enable when phone was working. Now I'm stuck because It cannot flash with any factory image rom. Anyone with solution, please help. Thanks
Click to expand...
Click to collapse
To flash a system image:
Download the latest system image for your Nexus 6p, then unzip it to a safe directory.
https://dl.google.com/dl/android/aosp/angler-n2g47o-factory-dc258043.zip
or Download any of your choice from here
https://developers.google.com/android/images
Connect your device to your computer over USB.
Start the device in fastboot mode with one of the following methods:
adb tool
http://developer.android.com/tools/help/adb.html
Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device.
POWER BUTTON + VOLUME DOWN BUTTON
Click to expand...
Click to collapse
If necessary, unlock the device's bootloader using one of the following methods:
Code:
fastboot flashing unlock
If you are updating an older device, run this command:
Code:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
Open a terminal and navigate to the unzipped system image directory or Open a command prompt from within your System image folder (navigate to where you have flash-all.bat located on your PC, shift + right click anywhere within that folder, select open command prompt here
Execute the flash-all script.
Code:
fastboot flash-all.bat
This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
Code:
fastboot flashing lock
or, for older devices, run:
Code:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Mavelos said:
You can unlock your bootloader to flash a stock ROM. Do you need the steps?
---------- Post added at 09:54 AM ---------- Previous post was at 09:38 AM ----------
To flash a system image:
Download the latest system image for your Nexus 6p, then unzip it to a safe directory.
https://dl.google.com/dl/android/aosp/angler-n2g47o-factory-dc258043.zip
or Download any of your choice from here
https://developers.google.com/android/images
Connect your device to your computer over USB.
Start the device in fastboot mode with one of the following methods:
adb tool
http://developer.android.com/tools/help/adb.html
Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device.
If necessary, unlock the device's bootloader using one of the following methods:
Code:
fastboot flashing unlock
If you are updating an older device, run this command:
Code:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
Open a terminal and navigate to the unzipped system image directory or Open a command prompt from within your System image folder (navigate to where you have flash-all.bat located on your PC, shift + right click anywhere within that folder, select open command prompt here
Execute the flash-all script.
Code:
fastboot flash-all.bat
This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
Code:
fastboot flashing lock
or, for older devices, run:
Code:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Click to expand...
Click to collapse
Thanks for your reply..But you can only do this only if you have an unlocked bootloader and debugged mode on. I didn't have either so it won't allow to flash with locked bootloader.
citifone said:
Thanks for your reply..But you can only do this only if you have an unlocked bootloader and debugged mode on. I didn't have either so it won't allow to flash with locked bootloader.
Click to expand...
Click to collapse
Exactly why i posted that. You can unlock your bootloader without turning USB debugging ON. Just Boot up with the POWER + VOLUME down Combination and use the bootloader unlock command in my previous post.
FAILED (remote: OEM unlock is not allowed)
Mavelos said:
Exactly why i posted that. You can unlock your bootloader without turning USB debugging ON. Just Boot up with the POWER + VOLUME down Combination and use the bootloader unlock command in my previous post.
Click to expand...
Click to collapse
What I think he is telling you and the same problem I have, when We try the unlock command we are getting this error :
FAILED (remote: OEM unlock is not allowed)
any suggestions ?
Regards.
Lord Aguacate said:
What I think he is telling you and the same problem I have, when We try the unlock command we are getting this error :
FAILED (remote: OEM unlock is not allowed)
any suggestions ?
Regards.
Click to expand...
Click to collapse
Yes, I got the same error. Again, it's because of bootloader locked and debug is off. Any other ways to unlock or flash this phone?
citifone said:
Yes, I got the same error. Again, it's because of bootloader locked and debug is off. Any other ways to unlock or flash this phone?
Click to expand...
Click to collapse
To unlock you first need to have ticked the allow OEM unlock from developer menu within the OS. It won't work otherwise.
Lord Aguacate said:
What I think he is telling you and the same problem I have, when We try the unlock command we are getting this error :
FAILED (remote: OEM unlock is not allowed)
any suggestions ?
Regards.
Click to expand...
Click to collapse
You'll have to use a Rescue OTA
Download the latest Nexus 6P OTA from here https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
STEPS TO FOLLOW
To apply an OTA update image:
Download the appropriate update image for your device below.
https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
Boot into your recovery from fastboot
use the key combination for your device
Code:
POWER + VOLUME DOWN
and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command on your PC:
Code:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
Code:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.
Mavelos said:
You'll have to use a Rescue OTA
Download the latest Nexus 6P OTA from here [="https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip"]https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
STEPS TO FOLLOW
To apply an OTA update image:
Download the appropriate update image for your device below.
="https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip"]https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
Boot into your recovery from fastboot
use the key combination for your device
Code:
POWER + VOLUME DOWN
and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command on your PC:
Code:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
Code:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.
Click to expand...
Click to collapse
Dear Mavelos,
I already tried that and the installation was successful, but my first problem still there, when I installed the Android O Beta, the touch of my screen stop working after the 2nd day of installation.
Now I don't know if this is a problem with Android O or just a coincidence and the hardware its broken.
I went to a lot of forums but nobody its talking about that (Touch Screen not working)
Did You guys hear anything about it?
Mavelos said:
You'll have to use a Rescue OTA
Download the latest Nexus 6P OTA from here https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
STEPS TO FOLLOW
To apply an OTA update image:
Download the appropriate update image for your device below.
https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
Boot into your recovery from fastboot
use the key combination for your device
Code:
POWER + VOLUME DOWN
and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command on your PC:
Code:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
Code:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.
Click to expand...
Click to collapse
I have the same problem as others, stuck in a bootloop and had not enabled unlock in dev options. I can get to bootloader but not recovery mode (bootloops when I select this). I would love to try this OTA side load, but I can't see my device in adb. I can see it however in fastboot. Not sure how to get it up in adb....
Any help would be much appreciated.
scorneil said:
I have the same problem as others, stuck in a bootloop and had not enabled unlock in dev options. I can get to bootloader but not recovery mode (bootloops when I select this). I would love to try this OTA side load, but I can't see my device in adb. I can see it however in fastboot. Not sure how to get it up in adb....
Any help would be much appreciated.
Click to expand...
Click to collapse
If you get a bootloop when selecting recovery, try rebooting to recovery with fastboot
Code:
fastboot reboot recovery
if that doesn't work, then i think your device is bricked.
---------- Post added at 06:19 AM ---------- Previous post was at 06:16 AM ----------
Lord Aguacate said:
Dear Mavelos,
I already tried that and the installation was successful, but my first problem still there, when I installed the Android O Beta, the touch of my screen stop working after the 2nd day of installation.
Now I don't know if this is a problem with Android O or just a coincidence and the hardware its broken.
I went to a lot of forums but nobody its talking about that (Touch Screen not working)
Did You guys hear anything about it?
Click to expand...
Click to collapse
If your touch screen isn't working, it might be related to the Android O Beta you flashed. Can you boot the phone up? If you have an OTG cable, connect a mouse to your phone. Turn on OEM unlocking in developer options. Do a factory reset.
i have the same problem with this, and i cannot unlock it too, is there anyway to unlock this phone?
OTG works Perfect! But.....
Mavelos said:
If you get a bootloop when selecting recovery, try rebooting to recovery with fastboot
Code:
fastboot reboot recovery
if that doesn't work, then i think your device is bricked.
---------- Post added at 06:19 AM ---------- Previous post was at 06:16 AM ----------
If your touch screen isn't working, it might be related to the Android O Beta you flashed. Can you boot the phone up? If you have an OTG cable, connect a mouse to your phone. Turn on OEM unlocking in developer options. Do a factory reset.
Click to expand...
Click to collapse
So I Follow your suggestion and I bought the OTG adapter, works perfectly I unlocked the bootloader from the developers options, did a factory restore with a previous image, etc.... Touch still not working, I'm starting to believe this a hardware problem with the screen.... Bad Luck maybe, I don't know! ..... I will have to buy that expensive screen ($140).
Anyway thanks for the help...
Regards
Lord Aguacate said:
So I Follow your suggestion and I bought the OTG adapter, works perfectly I unlocked the bootloader from the developers options, did a factory restore with a previous image, etc.... Touch still not working, I'm starting to believe this a hardware problem with the screen.... Bad Luck maybe, I don't know! ..... I will have to buy that expensive screen ($140).
Anyway thanks for the help...
Regards
Click to expand...
Click to collapse
You're welcome. Get your phone fixed and return to the flashing community.
last night i my phone inside my freezer hehehe and this morning i tried to turn it on, and it pass the google logo boot normally but it only lasted for a few minute and then turn off and bootloop again. so i guess my 6p has a hardware faulty

Help please can't see my phone in adb

I've had my Essential two weeks i was on 8.1 beta.Today i unlocked the boot loader.Then installed twrp while in twrp i side loaded magisk.I went back to fastboot then hit start .The phone just went into a bootloop.I Was able to go back to twrp 2 times but now i can't get back to any type of recovery.I Can get back to fastboot mode ishow all the info and secure boot says yes and device state unlocked.My pc see essential phone fastboot in the device manager but i can't get adb to see it .Can anyone help me ?
forgot something
looks like i skipped this part . Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.Is there anything i can do?
videodave1 said:
I've had my Essential two weeks i was on 8.1 beta.Today i unlocked the boot loader.Then installed twrp while in twrp i side loaded magisk.I went back to fastboot then hit start .The phone just went into a bootloop.I Was able to go back to twrp 2 times but now i can't get back to any type of recovery.I Can get back to fastboot mode ishow all the info and secure boot says yes and device state unlocked.My pc see essential phone fastboot in the device manager but i can't get adb to see it .Can anyone help me ?
Click to expand...
Click to collapse
adb only works while phone is booted into system so nothing wrong there. If you're in the bootloader menu where you see that the status of your device is unlocked then you're already in fastboot mode. Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too. Go into install and press flash image file and find the stock boot image and then go into install again and change to flash .zip and flash magisk. After that, reboot into system.
WOW thank you so much'
Arju said:
adb only works while phone is booted into system so nothing wrong there. If you're in the bootloader menu where you see that the status of your device is unlocked then you're already in fastboot mode. Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too. Go into install and press flash image file and find the stock boot image and then go into install again and change to flash .zip and flash magisk. After that, reboot into system.
Click to expand...
Click to collapse
I was able to flash twrp i'll try the rest when i get home from work
sideloading stock img
videodave1 said:
I was able to flash twrp i'll try the rest when i get home from work
Click to expand...
Click to collapse
Do i need it to be zipped I've tried it as image that i downloaded from xda and I've tried a zip i got from Essential neither are working?
zip file
videodave1 said:
Do i need it to be zipped I've tried it as image that i downloaded from xda and I've tried a zip i got from Essential neither are working?
Click to expand...
Click to collapse
When i try i get invalid file format. This is using a zip i got from Essential.
Stuck twrp says no os installed . But i did learn how to push files.
just trying to get back to stock now 
videodave1 said:
just trying to get back to stock now 
Click to expand...
Click to collapse
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
thanks been there tried the Oreo beta that is what i was on when i started and tried the 1st build before the betas i get an error on both i'll try to download them on another pc my phone does show up when i type fastboot devices now just need an os now .
Okay got back to 8.1 bootloader still unlocked twrp not install and i don't have root.I may just wait until P comes out.I'll try and learn more about adb. Thanks for your help Arju.
thanks everyone.
videodave1 said:
Okay got back to 8.1 bootloader still unlocked twrp not install and i don't have root.I may just wait until P comes out.I'll try and learn more about adb. Thanks for your help Arju.
Click to expand...
Click to collapse
No problem. Thank you very much for the donation, that was really kind of you. Hey I'm sure you'll get the hang of it before android P drops. you did figure out what went wrong all by yourself so get a hold of the right boot.img and the rest is exactly as how you did it in the first place but flash the boot.img before magisk. Let me know if you want to give it a dive again.
I'm on 8.1 boot loader unlocked and ready to try to root again .Thanks for the help
This is the closest thread i could find to what is happening to my PH-1.
Like videodave1 I 'was' running the latest stock 8.1 and have my bootloader unlocked. In trying to root the phone I did this:
flash boot flash boot twrp.img
adb shell twrp sideload
adb sideload magisk.zip
All installations went well, but when trying to reboot from twrp it forced me to install the app. After that the phone went into boot loop.
* Note how I didn't sideloaded the Oreo 8.1 image before magisk.
By pressing all 3 buttons I can get the phone to reboot and releasing the volume up I can get to Fastboot. Just volume down and power doesn't work.
The problem now is that adb and fastboot no longer recognise the phone. adb devices just gives an empty list and fastboot only shows < waiting for device >
Trying to go into Recovery mode doesn't work either. Power off doesn't work and Restart bootloader, well, restarts the bootloader.
It might be relevant to mention that I'm running adb and fastboot from Terminal in a Mac and that this is my very first and frustrated attempt to root any phone.
For reference this is what the FastBoot Mode brings:
PRODUCT_NAME - Mata
VARIANT - OPENUS
BOOTLOADER VERSION - mata-aad8ac4
BASEBAND VERSION - 2.0.C4-M1.3.1
SECURE BOOT - yes
DEVICE STATE - unlocked
I might have to just resign myself to the ordinary land of unlocked full stock phones
Thanks very much
avocom said:
This is the closest thread i could find to what is happening to my PH-1.
Like videodave1 I 'was' running the latest stock 8.1 and have my bootloader unlocked. In trying to root the phone I did this:
flash boot flash boot twrp.img
adb shell twrp sideload
adb sideload magisk.zip
All installations went well, but when trying to reboot from twrp it forced me to install the app. After that the phone went into boot loop.
* Note how I didn't sideloaded the Oreo 8.1 image before magisk.
By pressing all 3 buttons I can get the phone to reboot and releasing the volume up I can get to Fastboot. Just volume down and power doesn't work.
The problem now is that adb and fastboot no longer recognise the phone. adb devices just gives an empty list and fastboot only shows < waiting for device >
Trying to go into Recovery mode doesn't work either. Power off doesn't work and Restart bootloader, well, restarts the bootloader.
It might be relevant to mention that I'm running adb and fastboot from Terminal in a Mac and that this is my very first and frustrated attempt to root any phone.
For reference this is what the FastBoot Mode brings:
PRODUCT_NAME - Mata
VARIANT - OPENUS
BOOTLOADER VERSION - mata-aad8ac4
BASEBAND VERSION - 2.0.C4-M1.3.1
SECURE BOOT - yes
DEVICE STATE - unlocked
I might have to just resign myself to the ordinary land of unlocked full stock phones
Thanks very much
Click to expand...
Click to collapse
Even though your phone does not show up its there wipe everything.Fallow what Arju said in his post.I got back to stock then took the 8.1 update i'm not rooted but my bootloader is still unlocked.Oh make sure you unlock critical
videodave1 said:
Fallow what Arju said in his post.
Click to expand...
Click to collapse
Thanks for coming back to me. I really appreciate it.
Arju said:
Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too.
Click to expand...
Click to collapse
I might be missing something hopefully obvious here. How can I flash twrp again if I my computer can't see the phone. With the USB phone plugged in and in the FastBoot screen I enter into Terminal:
fastboot flash boot twrp.img
and I get:
< waiting for any device >
How do I flash it from the FastBoot screen? BTW, going to Recovery mode just hangs at the Essential logo.
Thanks
avocom said:
Thanks for coming back to me. I really appreciate it.
I might be missing something hopefully obvious here. How can I flash twrp again if I my computer can't see the phone. With the USB phone plugged in and in the FastBoot screen I enter into Terminal:
fastboot flash boot twrp.img
and I get:
< waiting for any device >
How do I flash it from the FastBoot screen? BTW, going to Recovery mode just hangs at the Essential logo.
Thanks
Click to expand...
Click to collapse
are you able to get to the bootloader menu? where it says start on the top.
Arju said:
are you able to get to the bootloader menu? where it says start on the top.
Click to expand...
Click to collapse
Thanks Arju. If you are referring to the FastBoot menu where you can use the up and down volume keys to select Start, Restart Bootloader, Recovery mode and Power off Yes, but not much else unfortunately.
If I select Recovery mode I don't go to the screen with the blue buttons from twrp.
Thanks
avocom said:
Thanks Arju. If you are referring to the FastBoot menu where you can use the up and down volume keys to select Start, Restart Bootloader, Recovery mode and Power off Yes, but not much else unfortunately.
If I select Recovery mode I don't go to the screen with the blue buttons from twrp.
Thanks
Click to expand...
Click to collapse
What you need to understand is that twrp will not stick after you flash it. This device does not have a recovery partition and that's why you replace the boot partition with twrp and while you're in twrp you need to flash the boot.img back and whatever mods on top of that such as kernel etc.. If you flash a rom then it will replace the twrp with the boot.img found in the rom zip.
So now we need the computer to recognize you device. Could you unplug the cable and change the usb port on you computer. connect your phone while you're in the bootloader menu where it says start on the top.
The use use fastboot command: fastboot devices
See if the computer recognizes you device.

Categories

Resources