For some reason i am unable to flash a stock ota or factory image to phone boots up and gets stuck at login screen on phone (bootloader) Erasing active slot "_a"
FAILED (remote: Partition table doesn't exist
Push. I have the exact same problem. Has anyone found a solution?
Are your android tools up-to-date?
pe7er said:
Push. I have the exact same problem. Has anyone found a solution?
Click to expand...
Click to collapse
Try locking and unlocking the bootloader then rebooting twice
Sent from my Pixel using XDA-Developers mobile app
bacon612 said:
Try locking and unlocking the bootloader then rebooting twice
Sent from my Pixel using XDA-Developers mobile app
Click to expand...
Click to collapse
I still get "(bootloader) Flashing active slot "_a" Failed (remote: partition [boota] doesn't exist)" error message.
Adb and fastboot are the newest versions.
Are you doing this?
https://developers.google.com/android/images
ne0ns4l4m4nder said:
For some reason i am unable to flash a stock ota or factory image to phone boots up and gets stuck at login screen on phone (bootloader) Erasing active slot "_a"
FAILED (remote: Partition table doesn't exist
Click to expand...
Click to collapse
Sorry I cant find where I got this PDF. Just download https://developers.google.com/android/ota <----the one for your phone then do below.
I had the same problem. I did below and its all back to normal. For ME to apply OTA I had to fastboot then press up volume till it said recovery. Press power then hold power down press up voluem once and there you see where you want to me. SIDELOAD. Then you can do the OTA img
4. Boot the Pixel into Fastboot Mode. This can be done by first powering off the Pixel, then pressing and holding both Power and Volume Down simultaneously. You should see a green android on his back and Start in green with an arrow pointing toward the Power button. 5. At this point do a test to see if drivers are properly installed in the PC. Attach the USB cable between the PC and the Pixel. Device Manager should now show an entry of Android Phone with a sub-entry of Android Bootloader Interface. 6. In the command prompt on the PC from step 2, enter the command fastboot devices. If you see a response with the serial number of your Pixel, then all is good and proceed. If the results for step 5 or 6 are not as expected, then further work is required in the PC to get the required drivers installed, so do not proceed further and ask for assistance. 7. Remove the USB cable between the PC and the Pixel. 8. Tap Volume Down until you see “Recovery Mode” in the arrow, then tap Power once to select it. 9. After a few seconds you will see the Google logo followed by a green android on his back with “No command” underneath. Press and hold Power, then tap Volume Up once, then release Power. NOTE: If your device starts rebooting at this point, your only recourse is to contact your place of purchase about a warranty replacement or repair. 10. You are now on the Android Recovery screen. On the third line at the top of the screen you will see something that looks like this: 7.1 / NDE63V / 3389651 The middle one is your current Build Number. Make note of this as the Rescue OTA you need corresponds to this one or a more recent one. (NOTE: You cannot install an older one than your current Build Number.) 11. Tap Volume Down until the entry “Apply Update from ADB” is highlighted, then tap Power to select it. You Pixel is now waiting to receive the OTA file. 12. Attach the USB cable between the PC and the Pixel. Device Manager should now show an entry of Android Phone with a sub-entry of Android ADB Interface.
13. In the command prompt on the PC from step 2, enter the command adb devices. If you see a response with the serial number of your Pixel, then all is good and proceed. If you do not see this then further work is required in the PC to get the required drivers installed, so do not proceed further and ask for assistance. On a Windows 10 PC: 14. On your PC, create the folder c:\MyPixel 15. Download the OTA for the current Build Number of your Pixel from here. Note: There are currently three release streams for Pixel phones. Please ensure you pick the correct one based on your situation: Release Global North America Verizon Oct 2016 NDE63H NDE63L NDE63P Nov 2016 NDE63U NDE63V NDE63X
16. When the download finishes, click on “Open Folder” at the bottom of the browser window. This will open Windows File Explorer. Right click on the highlighted file that was just downloaded, click Cut, then select the folder c:\MyPixel, right click again and click Paste to move the OTA zip file into c:\MyPixel.
17. If the Pixel Apply Update from ADB timed out (step 12), then re-initiate it. 18. Enter a command similar to the following (this example is for non-Verizon, North American customers), but the highlighted filename will be the one you pasted into c:\MyPixel in step 16 (don’t forget the .zip extension in the command): For a Pixel: adb sideload c:\MyPixel\sailfish-ota-nde63u-f1c2a8f5.zip For a Pixel XL: adb sideload c:\MyPixel\marlin-ota-nde63v-272853b5.zip 19. Progress messages should now appear on both the PC and the Pixel. Be patient as there can be several minutes before any progress messages appear. If there are any errors, do not proceed further and ask for assistance. On the Pixel: 20. When the update finishes the line “Reboot system now” should be highlighted. Tap power once to initiate a reboot. 21. After the reboot, your Pixel should be back in operation.
jayfried said:
Are you doing this?
https://developers.google.com/android/images
Click to expand...
Click to collapse
Been flashing ROMS since the G1. I was doing exactly this, yes. With the december images everything went back to normal.
Update platform tools?
ne0ns4l4m4nder said:
For some reason i am unable to flash a stock ota or factory image to phone boots up and gets stuck at login screen on phone (bootloader) Erasing active slot "_a"
FAILED (remote: Partition table doesn't exist
Click to expand...
Click to collapse
pe7er said:
Push. I have the exact same problem. Has anyone found a solution?
Click to expand...
Click to collapse
Have you updated your platform tools (adb/fastboot)? That fixed this exact issue for me.
Can you try fastboot continue? That might boot up your device properly although I think it is not the same issue as I had here
http://forum.xda-developers.com/pixel/help/accomplished-hardbricked-pixel-d-t3516717
I have the same issue... I flashed 8.1 and kept getting a google play services error. I tried formatting via recovery and it hung wiping /data... Now I get this error trying to flash an OS... Help!
This happened to me before. I fixed it by downloading the factory image that has the same bootloader version and not flashing the bootloader.
Related
I am trying to root my Nexus S. Actually, I'm trying to play around with the ADP developer terminal but I can't seem to get my drivers working. I even called Samsung but they told me they're supposed to not be installed (sigh).
It says that the drivers for Nexus S are missing
it also says the drivers for Android 1.0 are missing
I tried to install the Android 1.0 drivers manually through device manager (I am using Windows 7 64). I have the latest version of the android SDK installed along with the Google USB Driver package, revision 4
I navigate to C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver but windows just says,
"Windows was unable to install your Android 1.0
Windows could not find driver software for your device.
If you know the manufacturer of your device, you can visit its website and check the support section for driver software."
I checked the directory myself and it has a few files in it
android_winusb.inf
androidwinusb86.cat
androidwinusba64.cat
source.properties
Does anyone know what is going on and how I fix this?
Never mind, it just worked.
I right clicked the item in device manager and went to "scan for hardware changes" and then went to properties and navigated to the driver tab and went update driver and put in the directory again except this time with a trailing backslash and it worked.
I also rebooted the phone into regular mode instead of the power button + volume up boot loader.
I'm not sure which of those things made it work since I know I did the scan for hardware changes and properties / update driver thing several times without it working before.
*shrugs*
Thanks
WAIT!!
I spoke too soon. Apparently, when I boot it back into the bootloader (power button + volume up) it changes back to Android 1.0 and says it is missing drivers. Once again it will not let me install the drivers no matter what I try.
Even though I successfully installed the driver in regular mode, now it says the driver can't be found and there's nothing I can do about it.
Please help!
Aro2220 said:
WAIT!!
I spoke too soon. Apparently, when I boot it back into the bootloader (power button + volume up) it changes back to Android 1.0 and says it is missing drivers. Once again it will not let me install the drivers no matter what I try.
Even though I successfully installed the driver in regular mode, now it says the driver can't be found and there's nothing I can do about it.
Please help!
Click to expand...
Click to collapse
uninstall what you installed, then go to PDAnets' website http://junefabrics.com/android/ download the free installer. then start the program, follow the on-screen instructions, and let it install the drivers for you.
"Install to phone failed
Installer fail to open device"
When I go into windows device manager it shows up as Android ADB Interface on my computer...even when in the boot loader.
But if I try adb devices it doesn't list it as a connected device.
Aro2220 said:
Install to phone failed
Installer fail to open device
Click to expand...
Click to collapse
did you go to the phones main settings, applications, development.. and enable usb/android debugging?
Yes, I did that originally before I started having any of these problems.
When the phone is booted normally I can adb devices and it shows up. I can connect to it as well with adb shell and see all my files.
Then, I power down my phone and boot it back up holding the volume up and power button.
Now I am on the FASTBOOT MODE screen:
Code:
FASTBOOT MODE
PRODUCT NAME - HERRING
HW VERSION - REV 11
BOOTLOADER VERSION - I9020XXKA3
BASEBAND VERSION - I9020XXKF1
CARRIER INFO - TMB
SERIAL NUMBER - 12345ETC
LOCK STATE - LOCKED
SELECT - VOL UP or VOL DOWN
EXECUTE - POWER
REBOOT BOOTLOADER
REBOOT
RECOVERY
POWER OFF
USB Control Init
USB Control Init End
STANDARD_SET_CONFIGURATION
Now I adb devices and nothing is there.
Aro2220 said:
Yes, I did that originally before I started having any of these problems.
When the phone is booted normally I can adb devices and it shows up. I can connect to it as well with adb shell and see all my files.
Then, I power down my phone and boot it back up holding the volume up and power button.
Now I am on the FASTBOOT MODE screen:
Code:
FASTBOOT MODE
PRODUCT NAME - HERRING
HW VERSION - REV 11
BOOTLOADER VERSION - I9020XXKA3
BASEBAND VERSION - I9020XXKF1
CARRIER INFO - TMB
SERIAL NUMBER - 12345ETC
LOCK STATE - LOCKED
SELECT - VOL UP or VOL DOWN
EXECUTE - POWER
REBOOT BOOTLOADER
REBOOT
RECOVERY
POWER OFF
USB Control Init
USB Control Init End
STANDARD_SET_CONFIGURATION
Now I adb devices and nothing is there.
Click to expand...
Click to collapse
do a fastboot devices
Might be because you can't use adb in fastboot.
Sent from my Nexus S MV from the XDA Premium app.
Fastboot devices found my device. I was able to unlock it and follow the instructions on http://forum.xda-developers.com/showthread.php?t=895545
But I run into a problem whenever I enter the recovery mode. It just gives me the android with the exclamation mark in a triangle symbolizing that something went wrong.
EDIT: I think I didn't know how to use the recovery module. If you press volume up then power then let go of power or something like that it shows you some command options at the top of the screen.
But I realized that wasn't clockwork and after doing some reading I think when I rebooted the phone it auto-flashed the recovery module back to the default one.
So I flashed clockwork recovery.img again using the same steps except this time I went straight into the recovery option instead of rebooting my phone and then I saw clockwork.
I followed the rest of the steps from that work and everything seems to be working.
Thanks again ;-)
Aro2220 said:
Fastboot devices found my device. I was able to unlock it and follow the instructions on http://forum.xda-developers.com/showthread.php?t=895545
But I run into a problem whenever I enter the recovery mode. It just gives me the android with the exclamation mark in a triangle symbolizing that something went wrong.
Any ideas?
Click to expand...
Click to collapse
fastboot a custom recovery like clockwork or twrp. then flash whatever rooted rom(and gapps) you plan on flashing.
Go To The Link From Your PC and Click the Box Within The YouTube video. Watch the video and in description should be a download link named NexusRootNew
http://m.youtube.com/#/watch?deskto...e.com/watch?v=xwe4sWH67dk&v=xwe4sWH67dk&gl=US
Download it
Extract it
Place into C Drive
Within the file are the drivers, Recovery and superuser
Just follow the Video and u should be ok
Sent from my Nexus S using xda premium
I'm on Android 5.0.1. I changed my PIN screen lock of my xperia and 20 minutes later I forgot it out of lots of things happening at once. I try to guess it 120 times (5.0 doesn't have "Enter google password" after x tries) without any progress (I was still at school at this point). I tried to boot to recovery and wipe it, but because I had Cyanogenmod recovery it didn't work. (it doesn't work at all, when I try to wipe it, it just displays the Android and flashes a few times and that's it.). At home, I tried to use Android Device Manager to erase it, but it just rebooted into Android. I tried to unlock the screen with the lock feature, but it didn't work at all, nothing happened (if I put something in the text field it allowed me to call owner. Pressing back or home puts me back in the lock screen "swipe up to unlock" state. I tried reflashing it with flashtool, but I couldn't even connect my device through ADB, it only said
Code:
04/034/2015 18:34:13 - INFO - Device connected with USB debugging off
04/034/2015 18:34:13 - INFO - For 2011 devices line, be sure you are not in MTP mode
even though USB debugging was on, even the notification said so. ADB just doesn't find it at all. When I plug my device in my computer the window that pops up says "This folder is empty". Am I really screwed? I guess my only chance is to keep guessing the password... I don't remember the first number or how many numbers were in it... help?
pefu19 said:
I'm on Android 5.0.1. I changed my PIN screen lock of my xperia and 20 minutes later I forgot it out of lots of things happening at once. I try to guess it 120 times (5.0 doesn't have "Enter google password" after x tries) without any progress (I was still at school at this point). I tried to boot to recovery and wipe it, but because I had Cyanogenmod recovery it didn't work. (it doesn't work at all, when I try to wipe it, it just displays the Android and flashes a few times and that's it.). At home, I tried to use Android Device Manager to erase it, but it just rebooted into Android. I tried to unlock the screen with the lock feature, but it didn't work at all, nothing happened (if I put something in the text field it allowed me to call owner. Pressing back or home puts me back in the lock screen "swipe up to unlock" state. I tried reflashing it with flashtool, but I couldn't even connect my device through ADB, it only said
Code:
04/034/2015 18:34:13 - INFO - Device connected with USB debugging off
04/034/2015 18:34:13 - INFO - For 2011 devices line, be sure you are not in MTP mode
even though USB debugging was on, even the notification said so. ADB just doesn't find it at all. When I plug my device in my computer the window that pops up says "This folder is empty". Am I really screwed? I guess my only chance is to keep guessing the password... I don't remember the first number or how many numbers were in it... help?
Click to expand...
Click to collapse
Hi bro.
Download this file Here.
Extract it on your desktop.
Now this file will install the cwm recovery.
Open a command window in the folder you have extracted.
Type
fastboot flash boot boot.IMG
Now before pressing enter you just need to power off your phone connecting it to the computer while holding volume + key .
Now you can press enter.
After you flash the recovery boot to recovery and make a factory reset.
Note: after this process the WiFi may not work you just need to install this app http://forum.xda-developers.com/xperia-l/development/app-recoveries-recovery-installer-t3187915 and give root and install TWRP.
And don't worry windows won't show the internal or the external memory because your phone is locked it's kind of protecting your files .
Don't forget to hit thanks
n78 shadow said:
Hi bro.
Download this file Here.
Extract it on your desktop.
Now this file will install the cwm recovery.
Open a command window in the folder you have extracted.
Type
fastboot flash boot boot.IMG
Now before pressing enter you just need to power off your phone connecting it to the computer while holding volume + key .
Now you can press enter.
After you flash the recovery boot to recovery and make a factory reset.
Note: after this process the WiFi may not work you just need to install this app http://forum.xda-developers.com/xperia-l/development/app-recoveries-recovery-installer-t3187915 and give root and install TWRP.
And don't worry windows won't show the internal or the external memory because your phone is locked it's kind of protecting your files .
Don't forget to hit thanks
Click to expand...
Click to collapse
I did what you told me to do, and it says < waiting for device > in the console. The device displays a blue LED after I volume+ and plug the USB in. I then enter the command and it's just stuck at < waiting for device >.
pefu19 said:
I did what you told me to do
Click to expand...
Click to collapse
Did you have fastboot driver installed?
If not go to flashtool folder then to drivers there you will see a exe file ,open it and install fastboot drivers and xperia l derivers.
Edit: and I think it should be installed automatically by windows just wait for it.
n78 shadow said:
Did you have fastboot driver installed?
If not go to flashtool folder then to drivers there you will see a exe file ,open it and install fastboot drivers and xperia l derivers.
Edit: and I think it should be installed automatically by windows just wait for it.
Click to expand...
Click to collapse
I think I have them installed, but when I go to the flashtool drivers folder and install those drivers, I select xperia L drivers and the 2 on top, it says Install Failed for all of them
What windows do you use???
If 8 I think it won't work , you should try it on another one
n78 shadow said:
What windows do you use???
If 8 I think it won't work , you should try it on another one
Click to expand...
Click to collapse
I have Windows 10 x64
pefu19 said:
I have Windows 10 x64
Click to expand...
Click to collapse
Sorry bro that won't work try it on another computer with 7 or lower.
Don't forget to hit thanks if I hleped you
pefu19 said:
I have Windows 10 x64
Click to expand...
Click to collapse
windows 10 has a special 3rd party driver protection... you must disable it and install fastboot driver... AND you need a USB2.0 because 3.0 has known issues
Sent from my Xperia T using XDA Free mobile app
In Window 10 go to setting>update&security>Recovery>Advanced startup and restart pc >then choose troubleshoot>Advanced Option>Startup Setting and restart>and it will ask option choose Disable Driver signature enforcement and done......
if you have any problem ask...:laugh:
Hello everybody,
I managed to brick my mate 8 as per the title, honestly thinking why did i even bother, that whole saying "If it ain't broke, don't fix it." applies here 100%.
So i have been in the NXT-L29C636B180 which i put with the dload method (original was C636B103) and since then everything was good, all except the video camera that is.
So i wanted to try to get to the nougat update (561?) but i read that you need the 211 first. As i couldn't find it i used the android app: firmware finder, and using the proxy method i told basically the system that a new update is up and download it - so this is the update option in the settings..
So after it downloaded NXT-L29C636B211 then it restarted, starting unpacking, and the installation stopped at around 5% when it restarted by it self. And that was it...
I am in a screen where i cannot use the touch, but only the buttons on the side and have the options
"Reboot system now"
"Wipe data/ factory reset"
"Wipe cache partition"
Tried the cache and rebooting, didn't do anything.
Tried wiping, and reboot, then i go in another page
"Huawei eRecovery" where it asks to connect to the wifi and download but then throws an error message "Getting package info failed"
That is pretty much it, i tried putting the update.app in the dload folder in the sd card and tried to use that method but it wouldnt boot that (used the volume + and - and power buttons) but it took me back to one of the above.
Am i out of hope? Is there anything i can do to restore it?
I really appreciate the help.
same problem!
kaelthuzad said:
Hello everybody,
I managed to brick my mate 8 as per the title, honestly thinking why did i even bother, that whole saying "If it ain't broke, don't fix it." applies here 100%.
So i have been in the NXT-L29C636B180 which i put with the dload method (original was C636B103) and since then everything was good, all except the video camera that is.
So i wanted to try to get to the nougat update (561?) but i read that you need the 211 first. As i couldn't find it i used the android app: firmware finder, and using the proxy method i told basically the system that a new update is up and download it - so this is the update option in the settings..
So after it downloaded NXT-L29C636B211 then it restarted, starting unpacking, and the installation stopped at around 5% when it restarted by it self. And that was it...
I am in a screen where i cannot use the touch, but only the buttons on the side and have the options
"Reboot system now"
"Wipe data/ factory reset"
"Wipe cache partition"
Tried the cache and rebooting, didn't do anything.
Tried wiping, and reboot, then i go in another page
"Huawei eRecovery" where it asks to connect to the wifi and download but then throws an error message "Getting package info failed"
That is pretty much it, i tried putting the update.app in the dload folder in the sd card and tried to use that method but it wouldnt boot that (used the volume + and - and power buttons) but it took me back to one of the above.
Am i out of hope? Is there anything i can do to restore it?
I really appreciate the help.
Click to expand...
Click to collapse
That happened to me too. you will still be able to enter fastboot. plug your phone to your pc and and press and hold the power and volume down. that should take you to the fastboot screen.
find the appropriate twrp recovery for your phone and use the command
fastboot flash recovery "recovery name".img. wait till its done.
press and hold the power and volume down button till the phone reboots. that will takeyou to twrp recovery. there you could either flash b210 or the beta b521 -- which i am on.
crazynitro said:
That happened to me too. you will still be able to enter fastboot. plug your phone to your pc and and press and hold the power and volume down. that should take you to the fastboot screen.
find the appropriate twrp recovery for your phone and use the command
fastboot flash recovery "recovery name".img. wait till its done.
press and hold the power and volume down button till the phone reboots. that will takeyou to twrp recovery. there you could either flash b210 or the beta b521 -- which i am on.
Click to expand...
Click to collapse
Thank you for the response. I will give it a try today after work i am a complete noob so its the first time for me to see what fastboot is, never heard of TWRP, i was always stock so never needed to mess with my phones.
If i recall doing power and volume down while plugged it was taking me to the page i mentioned to wipe the data, reboot or wipe the cache.
I managed to go to the fastboot page on the phone by pressing volume - and then plugging the phone to the pc. Now in the white page on the phone it shows, Phone unlocked in red. Does this mean just it is carrier unlocked?
So do i need to have the bootloader unlocked to do anything here? How do i do that? I cannot buy the code i suppose now since my phone is bricked i will have to go the Huawei way? And how do i do that, i saw a site to create a HUawei ID but in the registration page it didn't mention UK anywhere (where i live), mentioned Hong Kong and other Asian territories. I bought the phone from Wonda mobile, and being the 636 i would think its the asian model anyway.
Regarding TWRP, i didnt install it from before the phone was bricked will i still be able to do what you mentioned? And for the image i need to use, do i need to go to the firmware i was in before (636B180) or the one i tried to go to (636B211)? I can't seem to find the 180 anymore anywhere.
Sorry for the mass amount of questions, trying to sort it i have the phone for less than a year and i am gutted for messing it up like that.
kaelthuzad said:
Thank you for the response. I will give it a try today after work i am a complete noob so its the first time for me to see what fastboot is, never heard of TWRP, i was always stock so never needed to mess with my phones.
If i recall doing power and volume down while plugged it was taking me to the page i mentioned to wipe the data, reboot or wipe the cache.
I managed to go to the fastboot page on the phone by pressing volume - and then plugging the phone to the pc. Now in the white page on the phone it shows, Phone unlocked in red. Does this mean just it is carrier unlocked?
So do i need to have the bootloader unlocked to do anything here? How do i do that? I cannot buy the code i suppose now since my phone is bricked i will have to go the Huawei way? And how do i do that, i saw a site to create a HUawei ID but in the registration page it didn't mention UK anywhere (where i live), mentioned Hong Kong and other Asian territories. I bought the phone from Wonda mobile, and being the 636 i would think its the asian model anyway.
Regarding TWRP, i didnt install it from before the phone was bricked will i still be able to do what you mentioned? And for the image i need to use, do i need to go to the firmware i was in before (636B180) or the one i tried to go to (636B211)? I can't seem to find the 180 anymore anywhere.
Sorry for the mass amount of questions, trying to sort it i have the phone for less than a year and i am gutted for messing it up like that.
Click to expand...
Click to collapse
did u solve it plz i have same problem
first download NXT-L29C636B170 here: https://goo.gl/dHk8r8 , download Huawei extractor here: https://forum.xda-developers.com/showthread.php?t=2433454 ,unzip update.zip from B170 firmware downloaded, go to huawei extractor and choose UPDATE.APP (from B170 firmware extracted), and extract only recovery.img, download ADB Command here: https://goo.gl/05Rx06 unrar and copy recovery.img into ADB Command folder, put your phone in fastboot mode, turn off your device, then hold volume - and fast plug your phone into PC, now you are in fastboot mode,go to ADB Command folder and hold shift, holding shift key do click right with the mouse,and click on: open command window, now write: fastboot devices, enter, and you can see your device are connect, now write: fastboot flash recovery recovery.img, enter, when it finished write: fastboot reboot, and enter, then the system reboot, turn off your phone, now put UPDATE.APP (from B170 firmware) into dload folder in sdcard, with your phone off hold volume +, volume -, and power at the same time, then you can update by dload method,wait it finish and the phone reboot, now you're running NXT-L29C636B170, and if you want update to NXT-L29C636B211 you can find here: https://forum.xda-developers.com/mate-8/general/huawei-mate-8-stock-firmware-official-t3391727/amp/ unzip the update.zip and put UPDATE.APP (from B211) into dload folder in sdcard (obviously you need delete the UPDATE.APP from B170), now go to dialler and press *#*#2846579#*#* and project menu open, choose Software upgrade>SDCard Upgrate and yes, the system reboot , wait it finish and reboot, and you're now running NXT-L29C636B211. if you have any problem just tell me.
sorry for my bad english.
I have a pixel 4a with stock rom and recovery that is boot looping after an update. The device has a couple pictures I would like to recover and I was hoping I could use adb to pull those files from the device. The device does have a passcode that I know and and I am able to boot into resuce mode and run "abd devices", and it shows the device in rescue.
When I try to run, "adb shell ls, I get "error:closed"
I tried abd pull "/sdcard/DCIM" and received, "adb: error: connect failed: closed"
Any help is greatly appreciated!
This might be an obvious question, but have you tried booting up in safe mode?
JohnC said:
This might be an obvious question, but have you tried booting up in safe mode?
Click to expand...
Click to collapse
I read holding the power button and tapping the logo was the shortcut but that did not do anything. How do you boot it in safemode?
I think these are the steps:
When your phone is off
- Press your phone's power button.
- When the animation starts, press and hold your phone's volume down button. Keep holding it until theanimation ends and your phone starts in safe mode.
- You'll see "Safe mode" at the bottom of your screen.
Edit: Important: Safe mode removes some Home screen widgets.
JohnC said:
I think these are the steps:
When your phone is off
- Press your phone's power button.
- When the animation starts, press and hold your phone's volume down button. Keep holding it until theanimation ends and your phone starts in safe mode.
- You'll see "Safe mode" at the bottom of your screen.
Click to expand...
Click to collapse
I found that as well and just tried it a dozen times and I never get any safe mode idication at the bottom the screen. I only get a Google logo with a progress bar that never finishes.
What version of android did the phone have, and what type of update did it try to do? (And OS Upgrade, or a security update)
JohnC said:
What version of android did the phone have, and what type of update did it try to do? (And OS Upgrade, or a security update)
Click to expand...
Click to collapse
Its running Android 11
It shows 11/RQ2A.210305.006/7119741 in recovery mode. It would have been up update pushed just before 4/4/21. I think it was security updates but I do not know how to verify that. My other Pixel 4a phone updated last around that same time and shows 11/RQ2A.210405.210305.005
This unfortunately is now outside of my experience, so I would be just guessing at this point.
So I was able to get into fast boot and use the flash utility provided by Google and Google chrome to detect the device, but when I try to flash it with sunfish i get an error about "oem unlocking" but I will have to dig further tomorrow. Hoping that I can get it to do something.
That error might be because your bootloader is locked, so it can't flash a new boot image to it.
The only way I know to unlock it is from the developer options in the settings, but that would require the phone to be able to bootup.
Adb sideload the stock OTA in recovery
Glad to hear that
I tried to downgrade from Android 11 to Android 10 a few months ago. Back then I had no knowledge about everything related to Bootloader Unlocking and other things.
I followed a tutorial. But my phone got bricked. So I followed an unbrick guide a few months later. I got it back to a state where I have basic Fastboot access.
But when I try to start the phone, is says Red State, Your device has failed verification. Incorrect Signature. Please download Image with correct signature or disable secure boot.
Now I don't have the Bootloader unlocked. I also can't do that with Fastboot. Results in the error that I am not permitted to do that. I also tried flashing TWRP but it says:
'download for partition 'recovery' is not allowed'.
Is there a way to get it working again? I would really need this phone again.
I have not made any backups. Also It says in Fastboot that my device is called: 0123456789ABCDEF. I dont think that is good because other phones I used fastboot on had a normal name.
J_029 said:
I tried to downgrade from Android 11 to Android 10 a few months ago. Back then I had no knowledge about everything related to Bootloader Unlocking and other things.
I followed a tutorial. But my phone got bricked. So I followed an unbrick guide a few months later. I got it back to a state where I have basic Fastboot access.
But when I try to start the phone, is says Red State, Your device has failed verification. Incorrect Signature. Please download Image with correct signature or disable secure boot.
Now I don't have the Bootloader unlocked. I also can't do that with Fastboot. Results in the error that I am not permitted to do that. I also tried flashing TWRP but it says:
'download for partition 'recovery' is not allowed'.
Is there a way to get it working again? I would really need this phone again.
I have not made any backups. Also It says in Fastboot that my device is called: 0123456789ABCDEF. I dont think that is good because other phones I used fastboot on had a normal name.
Click to expand...
Click to collapse
I'm dealing with that issue right now and my device won't even charge or turn on. Let me know if you find a fix. Did you try mtkclient already?
I have found a solution to fix red state. I also unlocked the bootloader afterwards and rooted the device.
The solution to fix red state is as following:
1. Go to: https://androidfilehost.com/?fid=2188818919693749336 and download the firmware (Its from FIH-Firmware.HikariCalyx.com Tutorial how to unlock bootloader)
2. Open SP Flash tool and load the firmware using the scatter file called MT6761_Android_scatter.txt
3. Select Format + Download and klick the download button
4. Now take your phone (Make sure to have it connected to a charger for over an hour bevore doing this, even tho the charging symbol might not show up) and hold down the volume buttons and while holding them, connect the phone to the pc using usb cable.
5. Wait for it to finish downloading.
6. When complete you should be able to start into fastboot. That can take up to one minute. Try putting the battery back in if it doesnt start after holding buttons over a minute.
7. When in fastboot, make sure the drivers are loaded. For this go into Device Manager. If there is an unknown device called Android, select update Driver > Search on my Computer > Select from a list. Then scroll down to TCL and then select Android ADB Interface. The device manager might tell you that it might not be the correct driver, but just continue.
8. Type into ADB and Fastboot window:
fastboot reboot recovery
9. When you see android laying on its back, hold power button and press volume up button (sometimes you have to press it 6 times), then the recovery menu should open up. Now select Wipe Data Factory reset. Select Yes and let it reset. After that start the phone again.
10. Your phone should start normal now. The startup can take up to 10 minutes. if it hasnt started after 30 minutes, repeat the procedure to reset it.
11. To get IMEI back, you have to unlock the bootloader and root the device. If you want to do that tell me. Its a bit complicated but i can tell you.
Make sure to follow the steps exactly
Thanks for the response, my device is a mt8163 and I have mtkclient if I can find the proper firmware what command would I use to flash the file