Google pixel in qdloader-9008 after removing aboot - Google Pixel Questions & Answers

Hi all, I accidentally cleared the aboot partition, after that the phone is detected as QDloader-9008. How can I overwrite the aboot partition to get the phone to start again?
Thanks in advance for your help

Related

Help please I think I bricked my Motorola Droid Maxx Dev Edition.

I think I bricked my phone but im not sure if its a soft or hard brick. I got the phone and it had Droid 4.2.2 on it and then unlocked the bootloader. I then installed all of the updates to it and then rooted it with TWRP and SU. I got a stock image for my phone for 4.2.2 then I flashed the system image and all was ok when I rebooted the phone It just hung there so I then tried to go into recovery and that worked and I then tried to do a factory reset and it just got stuck in a bootloader loop it would turn on and then the bootloader warning came up and then it would be blank screen and then the bootloader warning would come up again and repeat. I am able to still go into fastboot and TWRP but I did not back up the image. Any ideas...Im a noob and I dont want a 650 dollar paperweight.
Knight71 said:
I think I bricked my phone but im not sure if its a soft or hard brick. I got the phone and it had Droid 4.2.2 on it and then unlocked the bootloader. I then installed all of the updates to it and then rooted it with TWRP and SU. I got a stock image for my phone for 4.2.2 then I flashed the system image and all was ok when I rebooted the phone It just hung there so I then tried to go into recovery and that worked and I then tried to do a factory reset and it just got stuck in a bootloader loop it would turn on and then the bootloader warning came up and then it would be blank screen and then the bootloader warning would come up again and repeat. I am able to still go into fastboot and TWRP but I did not back up the image. Any ideas...Im a noob and I dont want a 650 dollar paperweight.
Click to expand...
Click to collapse
Don't worry. There is no such thing as a soft brick. It's either bricked or its not. If a phone is bricked, it does nothing at all. In your case download the factory images to your pc again to make sure you have a clean download and fastboot flash them onto your device. I'd flash the files individually and restart the bootloader between each file. Then clear the cache and reboot.
Lokke9191 said:
Don't worry. There is no such thing as a soft brick. It's either bricked or its not. If a phone is bricked, it does nothing at all. In your case download the factory images to your pc again to make sure you have a clean download and fastboot flash them onto your device. I'd flash the files individually and restart the bootloader between each file. Then clear the cache and reboot.
Click to expand...
Click to collapse
Ok...I got my phone up and running again. If I told you what I did to get into this situation you would just laugh. So I redone everything typed out the code and 2 items failed...I dont know if this is good or bad but my phone is up and running sort of....
OK..........fastboot oem fb_mode_set
FAILED....fastboot flash partition gpt.bin
FAILED....fastboot flash motoboot motoboot.img
OK..........fastboot flash logo logo.bin
OK..........fastboot flash boot boot.img
OK..........fastboot flash recovery recovery.img
OK.......mfastboot flash system system.img
OK..........fastboot flash modem NON-HLOS.bin
OK..........fastboot erase modemst1
OK..........fastboot erase modemst2
OK..........fastboot flash fsg fsg.mbn
OK..........fastboot erase cache
OK..........fastboot erase userdata
OK..........fastboot erase customize
OK..........fastboot erase clogo
OK..........fastboot oem config carrier vzw
OK..........fastboot oem fb_mode_clear
I then rebooted the phone and went threw the whole set up new phone process. I then unlocked developer mode did the google playstore updates. Meanwhile the phone is downloading OTA update. I did not want to install that update because I am now on 4.2.2 - 12.15.15 because I want to use FoxFi to teather my phone to my laptop using Wifi and KitKat turns off Wifi. I am having some problems with that app because now I have to set a pin password to lock the phone instead of swipe. And the other problem is that when I went back in fastboot and setup TWRP in the recover partition it just keeps rebooting into that partition like a loop not the system partition like it should. So now I dont know how im going to root my phone so I can freeze my OTA update with Titanium Backup. unless there is another way of doing it to get rid of the OTA. But I still want to be rooted im just not sure how to do it now.

Solved - FRP Locked, Phone not booting

Hi All,
Need help.
I was flashing 320 on L29C185 and things went wrong. I was on Kangvip and dirty flashed it.
Now the phone not booting and in fastboot it shows remote command not allowed. It shows BL and FRP locked.
Now I have the BL code but how to unlock the FRP as I am unable to boot into the ROM even after installing the update from stock recovery. The installation of update completes and after reboot, shows the huawei logo on the first screen and then just goes blank.
Any help would be appreciated.
Solved: Step by step guide below:
1. Download DC-Unlocker Phoenix software from there website.
2. Boot your phone in Fastboot mode using Vol - key and Power key pressed together and USB cable plugged to computer and phone.
3. Launch Phoenix and click OK on the first warning.
4. Enter your DC-Unlocker account ID and Password which you get when you purchase credits from the website.
5. If you want to read the tutorial about the Phoenix usage, select Yes otherwise continue pressing No.
6. Make sure that You seect Fastboot mode and App file in the options on the home screen and select the Update.App that you want to flash using the three dots.
7. Phoenix will extract the update.app in the folder and will list the files for you in the tool.
8. Click Select All and click update.
9. On the left hand side you will see the progress of flash.
10. Once it says firmware flashed OK, remove your phone from USB and reboot.
11. After booting, do a DLOAD flash by placing the update.app in the DLOAD folder in the root of SDCARD and pressing Vol +-and power key at the same time.
This should fix your phone unless you messed up real bad like I did and below is what I did to recover it.
USING THIS METHOD REMOVES IMEI AND OTHER NO. FROM YOUR PHONE SO YOU WILL HAVE TO RESTORE THEM USING HCU CLIENT WHICH AGAIN NEEDS 8 CREDITS FROM DC-UNLOCKER.
1. After the above steps, my phone was still not working. So I from the phoenix software click on the Enter Support Area.
2. Download the Factory image for your device (unfortunately only AL10 is available for Mate 8, no L29).
3. In Phoenix, select IMG file instead of the App files.
4. Select the factory image downloaded from the support area by selecting the three button menu.
5. Connect your phone in fastboot mode.
6. Select update and wait for the process to complete.
7. After process ins complete, remove your phone and reboot.
8. After reboot, you can DLOAD you relevant firmware using SD Card dload method.
9. Once the process is complete, you will have to restore your IMEI using HCU Client which will again use DC-Unlocker credits.
10. Launch HCU and put in your ID and password and connect. It will show how many credits you have in your account. You should atleast have 8.
11. Go to project menu of your phone by dialling *#*#2846579#*#* and selecting ProjectMenu -> 2.USB ports setting -> Select Manufacture mode
12. Connect phone to laptop and select read phone info.
13. Go to the tab Repair UMTS and select the IMEI and Sub IMEI and enter your 1st and 2nd IMEI in them respectively.
14. If you want to change the MAC of bluetooth and Wifi, you can do that otherwise leas=ve it as it is.
15. Click on repair and it will rewrite your IMEI nos. and reboot and factory reset the phone.
Doing these steps should give you your phone in 100% working conditions. Atleast I got my Mate back by following the exact same steps.
In twrp wipe cache, then fastboot flash system, recovery, cust and recovery. You should be on stock then, in Developer Options you can unlock FRP
13im6b said:
In twrp wipe cache, then fastboot flash system, recovery, cust and recovery. You should be on stock then, in Developer Options you can unlock FRP
Click to expand...
Click to collapse
I no longer have twrp which is the problem. I got stock recovery now. Tried wiping data and cache in that but to no avail. Still fastboot not accepting any commands saying remote commands not allowed. So can not flash TWRP as well.
I just used DC Unlocker Phoenix to recover using the 320 stock update.app. It completed the process successfully on the tool but then also after the reboot, the screen remains black and do not boot up.
Any help??
Current version: NextL09C185B100EMUI41
Extracting partitions
Cannot create extract directory: C:\Users\Ravinder\Desktop\DC_Phoenix_v22\tmp\20161108_173125_UPDATE\
Extract files to directory: C:\Users\Ravinder\Desktop\DC_Phoenix_v22\
Extracting partition: XLOADER OK
Extracting partition: FW_LPM3 OK
Extracting partition: FASTBOOT OK
Extracting partition: MODEMNVM_UPDATE OK
Extracting partition: TEEOS OK
Extracting partition: TRUSTFIRMWARE OK
Extracting partition: SENSORHUB OK
Extracting partition: FW_HIFI OK
Extracting partition: BOOT OK
Extracting partition: RECOVERY OK
Extracting partition: RECOVERY2 OK
Extracting partition: DTS OK
Extracting partition: MODEM OK
Extracting partition: MODEM_DSP OK
Extracting partition: 3RDMODEM OK
Extracting partition: SYSTEM OK
Extracting partition: CUST OK
Extracting partition: MODEM_DTB OK
Device found: 23Q7N16226004380
IMEI: 868407023861691
Build number: :KangVIP Slim
Product model: HUAWEI NXT-L29
Writing XLOADER partition with file C:\Users\Ravinder\Desktop\DC_Phoenix_v22\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file C:\Users\Ravinder\Desktop\DC_Phoenix_v22\XLOADER.img
XLOADER partition UPDATE ...OK
Writing FW_LPM3 partition with file C:\Users\Ravinder\Desktop\DC_Phoenix_v22\FW_LPM3.img
FW_LPM3 partition UPDATE ...OK
Writing FASTBOOT partition with file C:\Users\Ravinder\Desktop\DC_Phoenix_v22\FASTBOOT.img
FASTBOOT partition UPDATE ...OK
Writing MODEMNVM_UPDATE partition with file C:\Users\Ravinder\Desktop\DC_Phoenix_v22\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...OK
Writing TEEOS partition with file C:\Users\Ravinder\Desktop\DC_Phoenix_v22\TEEOS.img
TEEOS partition UPDATE ...OK
Writing TRUSTFIRMWARE partition with file C:\Users\Ravinder\Desktop\DC_Phoenix_v22\TRUSTFIRMWARE.img
TRUSTFIRMWARE partition UPDATE ...OK
Writing SENSORHUB partition with file C:\Users\Ravinder\Desktop\DC_Phoenix_v22\SENSORHUB.img
SENSORHUB partition UPDATE ...OK
Writing FW_HIFI partition with file C:\Users\Ravinder\Desktop\DC_Phoenix_v22\FW_HIFI.img
FW_HIFI partition UPDATE ...OK
Writing BOOT partition with file C:\Users\Ravinder\Desktop\DC_Phoenix_v22\BOOT.img
BOOT partition UPDATE ...OK
Writing RECOVERY partition with file C:\Users\Ravinder\Desktop\DC_Phoenix_v22\RECOVERY.img
RECOVERY partition UPDATE ...OK
Writing RECOVERY2 partition with file C:\Users\Ravinder\Desktop\DC_Phoenix_v22\RECOVERY2.img
RECOVERY2 partition UPDATE ...OK
Writing DTS partition with file C:\Users\Ravinder\Desktop\DC_Phoenix_v22\DTS.img
DTS partition UPDATE ...OK
Writing MODEM partition with file C:\Users\Ravinder\Desktop\DC_Phoenix_v22\MODEM.img
MODEM partition UPDATE ...OK
Writing MODEM_DSP partition with file C:\Users\Ravinder\Desktop\DC_Phoenix_v22\MODEM_DSP.img
MODEM_DSP partition UPDATE ...OK
Writing 3RDMODEM partition with file C:\Users\Ravinder\Desktop\DC_Phoenix_v22\3RDMODEM.img
3RDMODEM partition UPDATE ...OK
Writing SYSTEM partition with file C:\Users\Ravinder\Desktop\DC_Phoenix_v22\SYSTEM.img
SYSTEM partition UPDATE ...OK
Erasing CUST partition
Partition CUST erased
Writing CUST partition with file C:\Users\Ravinder\Desktop\DC_Phoenix_v22\CUST.img
CUST partition UPDATE ...OK
Writing MODEM_DTB partition with file C:\Users\Ravinder\Desktop\DC_Phoenix_v22\MODEM_DTB.img
MODEM_DTB partition UPDATE ...OK
Software written
08-Nov-16 5:38:29 PM Writing device finished OK
Still getting the black screen on reboot.
Black Screen is a cache problem when you switch between roms. You need to wipe cache.
13im6b said:
Black Screen is a cache problem when you switch between roms. You need to wipe cache.
Click to expand...
Click to collapse
I did it many a times but from stock recovery as FRP lock is preventing me from flashing TWRP.
But clearing it from stock is doing nothing. I have done the dload update from SD Card for atleast 8-10 tomes by now in hope that it might boot but to no avail.
Any other way around to unlock FRP or to flash TWRP?
Factory Reset?
letschky said:
Factory Reset?
Click to expand...
Click to collapse
Done multiple times from stock recovery. Tried flashing 320 as well as 200 but both fail to boot as after the splash screen of Huawei, the bot animation never shows and it just stays black.
I have L29 but should I try the second method of DC Phoenix tool to recover using the factory image of AL10 maybe??
Have anybody tried it till now?
Push the B320 UPDATE.APP in dload Folder in SD Card Press all three Buttons at same Time (Power Button,Volume+ and Volume-)
and waiting to finish the Update
Flashed 320 via dload as mentioned by you around 8 times already as mentioned above posts.
Also flashed 200 as well. Not booting.
Sent from my A0001 using Tapatalk
I told you guys not to flash this nougat. It looks like a dead loop... bricked?
danterape said:
I told you guys not to flash this nougat. It looks like a dead loop... bricked?
Click to expand...
Click to collapse
So, any way to bypass it or no hope??
Sent from my A0001 using Tapatalk
I have the same number model like you and the same problem three month ago, I tryed everything, contact a lot of members xda, try many solutions and many flash, no one do comeback my phone... Now a have my mate 8 bricked phone and my other mate 8 buyed after test everything
hi
i have same problem
I was flashing 320 on L29C185 and things went wrong.
Now the phone not booting and in fastboot it shows remote command not allowed. It shows BL and FRP locked.
Now I have the BL code but how to unlock the FRP as I am unable to boot into the ROM even after installing the update from stock recovery. The installation of update completes and after reboot, shows the huawei logo on the first screen and then just goes blank.
maybe here you will find something?
https://www.dc-unlocker.com/huawei-android-phone-frp-unlock
i dunno, i hadnt read it. i can recomend them for unlocking bootloader but i dont know if they can help you
This solution does not work as this is only if your phone boots up.
Sent from my A0001 using Tapatalk
Ok. Restless guys.
Follow this simple procedure.
In SD card, dload your original firmware unzipped.
Put it in the tray and slide in.
Power on your mate 8 by holding volume-up and power and when u see screen that it's booting, leave the phone and go for a long loo
Don't leave the keys till you see Device Booting....
After about 8-10min, it will start flashing the dload firmware.
Then factory reset once done and reboot.
sozofriend1234 said:
This solution does not work as this is only if your phone boots up.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
stop getting panicked
FRP doesn't stop you from booting up system. but locked bootloader can create problems.
contact me through private message,
i can help you
bluheart said:
Ok. Restless guys.
Follow this simple procedure.
In SD card, dload your original firmware unzipped.
Put it in the tray and slide in.
Power on your mate 8 by holding volume-up and power and when u see screen that it's booting, leave the phone and go for a long loo
Don't leave the keys till you see Device Booting....
After about 8-10min, it will start flashing the dload firmware.
Then factory reset once done and reboot.
Click to expand...
Click to collapse
Volume up + Power means leaving the phone in the stock recovery which I did multiple times but it just switches off itself after couple of minutes. Not sure if this is right..
Some hope seen right now when after trying to flash the stock rom again and again, got the bootloader unlocked and the first screen has came back with orange text.
However, the system is still not booting. After the warning screen, it just sits on the black screen again and FRP is still shown as locked and not allowing any fastboot command to run so TWRP flashing is not possible.
Any help??

How to erase CACHE PARTITION ?

I ran into a problem today when I tried to repair my Z5 Dual, I unplugged my phone in the beginning (NOT EVEN 5 Seconds). Then my phone started showing SOFTWARE UPDATE FAILED PLEASE CONNECT YOUR PHONE TO YOUR COMPUTER. I have a lot of important data in my phone which I need. I thought of just erasing the cache partition. But when I try via fastboot it says that REMOTE: COMMAND NOT ALLOWED HERE. Is there any other way to erase the cache partition? is there any other tool for erasing the cache partition alone? If the above doesn't work us there any way to recover the files in the internal storage. I have also encrypted some files using galleryvault that's why I prefer wiping cache and trying to boot up instead of flashing a new ROM with USERDATA box unchecked. Any help would really be appreciated.
Wipe it in twrp if you have it.
L33Tgod said:
Wipe it in twrp if you have it.
Click to expand...
Click to collapse
I haven't unlocked the bootloader.. No modifications to my phone. Is there any other way?
ajithpoison said:
I haven't unlocked the bootloader.. No modifications to my phone. Is there any other way?
Click to expand...
Click to collapse
Then just flash .ftf using flashtool without wiping anything

Oneplus6t Resize partition help

I need some help, I tried this on my 6t & it failed it wouldnt mount storage so i used msm tool & now im stuck in a bootloop. This means i cannot unlock my bootloader what can i possibly do? I was having issues booting system_a i tried to erase the partition and that didnt work so i formated system_a & still unable to boot into twrp on slot a. Any Ideas?

Nexus 5 deleted data partition

Hi there,
So I wanted to resize the system partition so I could install GApps. I accidentally deleted the data partition somehow (deleted not corrupted). I can go into bootloader and recovery, my bootloader is unlocked so I can flash any recovery I need to but I can't boot Android. Any ways to redo the partition table or manually add the userdata partition?
Thanks in advance.
Edit: I was able to fix the partition by creating a partition called "userdata" with parted, but now my phone is constantly rebooting and it cant be the power button because when powered off or in bootloader, it doesnt automatically turn on. Any help?
KevinKraze said:
Hi there,
So I wanted to resize the system partition so I could install GApps. I accidentally deleted the data partition somehow (deleted not corrupted). I can go into bootloader and recovery, my bootloader is unlocked so I can flash any recovery I need to but I can't boot Android. Any ways to redo the partition table or manually add the userdata partition?
Thanks in advance.
Click to expand...
Click to collapse
I would start fresh and flash the last factory image using fastboot
Then follow this guide for repartitioning... https://forum.xda-developers.com/t/recovery-unofficial-twrp-hh-for-nexus-5-hammerhead.4047653/
Lughnasadh said:
I would start fresh and flash the last factory image using fastboot
Then follow this guide for repartitioning... https://forum.xda-developers.com/t/recovery-unofficial-twrp-hh-for-nexus-5-hammerhead.4047653/
Click to expand...
Click to collapse
I have tried to flash the factory image, but as I said, the data partition is deleted so nothing works
I got it to work by manually creating a partition with parted and called it "userdata" After I just flashed the userdata.img file and everything seemed to work!

Categories

Resources