Bricked ZUK Z1 ? - Zuk Z1 Q&A, Help & Troubleshooting

Was able to wipe OS on my phone, now only ZUK Recovery menu is available. Boot stops showing white ZUK logo on screen.
ADB does not recognize the device.
Is it totally bricked now? or does there exist a solution?

I think you can still flash a factory image with the recovery, but I don't know how. By the way, how do you acces the fasboot menu ? Because I think it is still present on my bricked Z1 but I tried nearly every button combination to acces it, but never succeed...

I get to the ZUK Recovery menu by holding down both volume + and - for 10 sec at the moment phone vibrates at startup.
Hopefully there is a way to flash a recovery image. In the ZUK recovery menu there is an option to install update.zip, but I can't find a way to push the file to the device.

nordream said:
I get to the ZUK Recovery menu by holding down both volume + and - for 10 sec at the moment phone vibrates at startup.
Hopefully there is a way to flash a recovery image. In the ZUK recovery menu there is an option to install update.zip, but I can't find a way to push the file to the device.
Click to expand...
Click to collapse
Download qpst and the zui rom file and flash it and you should be good to go
qpst
https://mega.nz/#!4tom3DqL!4a-rRcLef1yS6HJSrBfne_-r9atg6yF3kI_HW8lDaPY
password: bbs.zuk.cn
zui rom file
https://mega.nz/#!chQkEAwR!IHeYRxWx38QdML6VxjPdVz08BgbZD-Z-xVuSG150qPU
Z1 usb driver (can be troublesome if doing this in windows 10 so try and use a win7 machine)
https://mega.nz/#!l8pVHIpT!UkcW3Jg4B7YilDjZatvLqGBi_R4vVUYVdkrsUL_Ve9k
If you dont know how to flash then ill try and guide you
After you installed qpst, you will get a bunch of programs, start QFIL from the qpst folder
Click browse on the programmer path row and select "prog_emmc_firehose_8974.mbn" and then click browse on the search path row and select the xml file + the other patch file which comes after it.
When thats done, make sure phone is off and then hold vol+ while you are inserting usb cable into phone and QFIL should then detect phone, you may need to select port and be quick with it, took me a few tries before I got it right so just take out the cable and turn off and try again if you fail to make them connect.
Not only you need to select comport, you also need to press the download button aswell as soon as possible or else phone will continue booting as normal
If everything went alrite then you soon got ZUI flashed on your phone and can install recovery etc
Good luck!

tndb said:
Download qpst and the zui rom file and flash it and you should be good to go
qpst
https://mega.nz/#!4tom3DqL!4a-rRcLef1yS6HJSrBfne_-r9atg6yF3kI_HW8lDaPY
zui rom file
uploading, will update as soon as the file is done
Z1 usb driver (can be troublesome if doing this in windows 10 so try and use a win7 machine)
https://mega.nz/#!l8pVHIpT!UkcW3Jg4B7YilDjZatvLqGBi_R4vVUYVdkrsUL_Ve9k
If you dont know how to flash then ill try and guide you
After you installed qpst, you will get a bunch of programs, start QFIL from the qpst folder
Click browse on the programmer path row and select "prog_emmc_firehose_8974.mbn" and then click browse on the search path row and select the xml file + the other patch file which comes after it.
When thats done, make sure phone is off and then hold vol+ while you are inserting usb cable into phone and QFIL should then detect phone, you may need to select port and be quick with it, took me a few tries before I got it right so just take out the cable and turn off and try again if you fail to make them connect.
Not only you need to select comport, you also need to press the download button aswell as soon as possible or else phone will continue booting as normal
If everything went alrite then you soon got ZUI flashed on your phone and can install recovery etc
Good luck!
Click to expand...
Click to collapse
Thanks very much for this guidance and files, so this will be a serial communucation, and I will not need the MTP USB to work? I have trouble with that driver, tried two windows 7 computers without luck.
I will try asap, phone is a christmas present so I'm in a kind off hurry. Plan was to flash ZUI to CM12.1...

nordream said:
Thanks very much for this guidance and files, so this will be a serial communucation, and I will not need the MTP USB to work? I have trouble with that driver, tried two windows 7 computers without luck.
I will try asap, phone is a christmas present so I'm in a kind off hurry. Plan was to flash ZUI to CM12.1...
Click to expand...
Click to collapse
Nah no need for MTP
As soon as you got zui into phone, you can convert back to cyanogen if you prefer that one. Look at modacos guide for example http://www.modaco.com/forums/topic/375804-convert-z1-from-zukui-to-cyanogen-os/
When you got zui loaded onto phone again, its in chinese. On the first screen you are met with just press the button in the bottom (on screen), then press cogwheel (which is the settings), scroll down to yet another cogwheel in here which should be below a lock icon, then press second option in here and then the top option to change language to english incase you cant make out the chinese

tndb said:
Nah no need for MTP
As soon as you got zui into phone, you can convert back to cyanogen if you prefer that one. Look at modacos guide for example http://www.modaco.com/forums/topic/375804-convert-z1-from-zukui-to-cyanogen-os/
Click to expand...
Click to collapse
Christmas is saved ! I'm back in business Thanks to tndb !
But last problem is to flash to CM. These steps below are unclear for me, tried "Wipe Data" and then "install using adb" but the sideload command fails with error "no device"
Select the option to wipe the device (important!)
Select the install update / from USB option
Type 'adb sideload z1.cyanogen.convert.signed.zip'
There are several Wipe options data or partitions?
Don't get any update / from USB option in the recovery menu. Only install using adb, but it fails

nordream said:
Christmas is saved ! I'm back in business Thanks to tndb !
But last problem is to flash to CM. These steps below are unclear for me, tried "Wipe Data" and then "install using adb" but the sideload command fails with error "no device"
Select the option to wipe the device (important!)
Select the install update / from USB option
Type 'adb sideload z1.cyanogen.convert.signed.zip'
There are several Wipe options data or partitions?
Don't get any update / from USB option in the recovery menu. Only install using adb, but it fails
Click to expand...
Click to collapse
Not sure where you got stuck?
If you already are as far as in cyanogen recovery, then its prob that your phone isnt detected in device manager as it may be detected as yet another device. Install driver again and then run the "adb sideload z1.cyanogen.convert.signed.zip" command (make sure the zip is in the same folder as your adb working folder)
otherwise read below
Did you manage to get into bootloader mode by typing "adb reboot bootloader"?
If you are already in bootloader mode, have you checked device manager if phone is detected here?
Have you made sure bootloader is unlocked aswell? Check with "fastboot -i 0x2b4c oem device-info" and if its still locked then type "fastboot -i 0x2b4c oem unlock"
and then "fastboot -i 0x2b4c boot z1.recovery.testkeys.img" to load cyanogen recovery.
Let me know if you still cant get it working, if you got google hangouts just pm me with details and ill help you from there

tndb said:
Not sure where you got stuck?
If you already are as far as in cyanogen recovery, then its prob that your phone isnt detected in device manager as it may be detected as yet another device. Install driver again and then run the "adb sideload z1.cyanogen.convert.signed.zip" command (make sure the zip is in the same folder as your adb working folder)
Click to expand...
Click to collapse
Thanks tndb, you put me in the right direction again, did a "adb kill-server" before adb sideload command and voila the sideload command connected and soon I'm ready to wrap the christmas present.
Merry Christmas ! and thanks

nordream said:
Thanks tndb, you put me in the right direction again, did a "adb kill-server" before adb sideload command and voila the sideload command connected and soon I'm ready to wrap the christmas present.
Merry Christmas ! and thanks
Click to expand...
Click to collapse
Aaah awesome!
Merry xmas to you too and have a happy new year!

hi
I have the same problem. When i try to falsh, by pressing download, i get this error:
Download Fail:Switch To EDL FailSystem.Exception: FireHose Fail
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
at QFIL.Tech.DownloadTech.SwitchToEDL()
Finish Download
Any thoughts?
How can i flash anything? i can acces fastboot, recovery menu.

nordream said:
I get to the ZUK Recovery menu by holding down both volume + and - for 10 sec at the moment phone vibrates at startup.
Hopefully there is a way to flash a recovery image. In the ZUK recovery menu there is an option to install update.zip, but I can't find a way to push the file to the device.
Click to expand...
Click to collapse
if you find a way, please tell me, i m in the same boat

Extentho said:
I have the same problem. When i try to falsh, by pressing download, i get this error:
Download Fail:Switch To EDL FailSystem.Exception: FireHose Fail
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
at QFIL.Tech.DownloadTech.SwitchToEDL()
Finish Download
Any thoughts?
How can i flash anything? i can acces fastboot, recovery menu.
Click to expand...
Click to collapse
If you can boot in fasboot mode and you are able to connect to your device from your pc you can just download the fastboot flashable stock image from Cyanogen Inc. Unzip it and flash it with fastboot. There are a a lot of guides how to do that on xda.

Planet X said:
If you can boot in favor mode and you are able to connect to your device from your pc you can just download the fastboot flashable stock image from Canon Inc. Unzip it and flash it with fastboot. There are a a lot of guides how to do that on xda.
Click to expand...
Click to collapse
Can you give me some links please? thank you very much. Qufil seems not to work for me. What is Canon inc, and where i can donwload the fastboot flashable stock image for lenovo zuk z1? And most important, how do i do that?

Extentho said:
Can you give me some links please? thank you very much. Qufil seems not to work for me. What is Canon inc, and where i can donwload the fastboot flashable stock image for lenovo zuk z1? And most important, how do i do that?
Click to expand...
Click to collapse
Download the fast signed image of COS 12.1 here http://builds.cyngn.com/factory/ham/...d-fastboot.zip
Unzip it
Open cmd or terminal
Go to the unzipped folder
Execute this step by step:
fastboot -i 0x2b4c flash aboot emmc_appsboot.mbn
fastboot -i 0x2b4c flash modem NON-HLOS.bin
fastboot -i 0x2b4c flash rpm rpm.mbn
fastboot -i 0x2b4c flash sbl1 sbl1.mbn
fastboot -i 0x2b4c flash dbi sdi.mbn
fastboot -i 0x2b4c flash splash splash.img
fastboot -i 0x2b4c flash tz tz.mbn
fastboot -i 0x2b4c flash persist persist.img
This will restore your bootloader to stock Cyanogen OS. It will remain unlocked. You can add cache.img, system.img and userdata yourself I guess. Otherwise Google for flash fastboot nexus. That should give you an idea how to flash with fastboot.

Planet X said:
Download the fast signed image of COS 12.1 here http://builds.cyngn.com/factory/ham/...d-fastboot.zip
Unzip it
Open cmd or terminal
Go to the unzipped folder
Execute this step by step:
fastboot -i 0x2b4c flash aboot emmc_appsboot.mbn
fastboot -i 0x2b4c flash modem NON-HLOS.bin
fastboot -i 0x2b4c flash rpm rpm.mbn
fastboot -i 0x2b4c flash sbl1 sbl1.mbn
fastboot -i 0x2b4c flash dbi sdi.mbn
fastboot -i 0x2b4c flash splash splash.img
fastboot -i 0x2b4c flash tz tz.mbn
fastboot -i 0x2b4c flash persist persist.img
This will restore your bootloader to stock Cyanogen OS. It will remain unlocked. You can add cache.img, system.img and userdata yourself I guess. Otherwise Google for flash fastboot nexus. That should give you an idea how to flash with fastboot.
Click to expand...
Click to collapse
Tried the first command and i got this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think the computer doesn t see the phone, because when i try command adb reboot bootloader in cmd i get device not found.
I have in installed the universal adb driver for android, but still doesn t work.

Extentho said:
Tried the first command and i got this:
I think the computer doesn t see the phone, because when i try command adb reboot bootloader in cmd i get device not found.
I have in installed the universal adb driver for android, but still doesn t work.
Click to expand...
Click to collapse
You have had an answer from the phone. So there was a connection. You can always test beforehand with the command fastboot -i 0x4b2c devices. It should then let you see the serial number of your phone.
But your answer was device is locked. That means you still have an locked bootloader. For to be able to use adb you have to add 0x4b2c to your usb_adb.ini file. Please look a bit more to the solutions that already have been given in the other threads. To unlock your bootloader you need to use the toolkit. You will find that in the development thread. The toolkit: http://forum.xda-developers.com/zuk-z1/development/win-zuk-z1-toolkit-0-1-alpha-t3235964
You will than have the possibility to flash a TWRP recovery too. With that you could also just flash the full rom as a zip.

Planet X said:
You have had an answer from the phone. So there was a connection. You can always test beforehand with the command fastboot -i 0x4b2c devices. It should then let you see the serial number of your phone.
But your answer was device is locked. That means you still have an locked bootloader. For to be able to use adb you have to add 0x4b2c to your usb_adb.ini file. Please look a bit more to the solutions that already have been given in the other threads. To unlock your bootloader you need to use the toolkit. You will find that in the development thread. The toolkit: http://forum.xda-developers.com/zuk-z1/development/win-zuk-z1-toolkit-0-1-alpha-t3235964
You will than have the possibility to flash a TWRP recovery too. With that you could also just flash the full rom as a zip.
Click to expand...
Click to collapse
I have played a while with this tool, and now the phone boots only into zuk logo(not the cyanogen anymore), also now i have access only to recovery and fastboot. Think i ve messed it up. Tried to sideload the stock rom and worked up to 47% with this tool, then gave me error on the phone. So, there is a working connection between phone and pc but i don t know what i can do. However i can t unlock the bootloader , when i try, it shows press any key and nothing happens. When i check the devices connected to the pc in adb tool, it shows me nothing. The only connection i was able to put up, was only sideload update.
None of the other commands is working. I can t install twrp recovery, i can, t unlock bootloader. I can t do anything.
I was able to use some fastboot commands in fastboot mode however. I managed to reboot phone in android using command in zuk tool from pc. When tried to flash stock rom in fastboot with the command from the tool, i got the same error : DEVICE IS LOCKED . CANNOT FLASH IMAGES

Extentho said:
I have played a while with this tool, and now the phone boots only into zuk logo(not the cyanogen anymore), also now i have access only to recovery and fastboot. Think i ve messed it up. Tried to sideload the stock rom and worked up to 47% with this tool, then gave me error on the phone. So, there is a working connection between phone and pc but i don t know what i can do. However i can t unlock the bootloader , when i try, it shows press any key and nothing happens. When i check the devices connected to the pc in adb tool, it shows me nothing. The only connection i was able to put up, was only sideload update.
None of the other commands is working. I can t install twrp recovery, i can, t unlock bootloader. I can t do anything.
I was able to use some fastboot commands in fastboot mode however. I managed to reboot phone in android using command in zuk tool from pc.
Click to expand...
Click to collapse
Thank you for the information. You should be able to flash the stock Cyanogen recovery with fastboot. Than you could do a factory reset in that recovery. That's all you need to have a working phone again. But with that recovery you could also flash the signed zip from Cyanogen.

Planet X said:
Thank you for the information. You should be able to flash the stock Cyanogen recovery with fastboot. Than you could do a factory reset in that recovery. That's all you need to have a working phone again. But with that recovery you could also flash the signed zip from Cyanogen.
Click to expand...
Click to collapse
I CANNOT flash the stock rom using fastboot. I have tried, many times. Also, the USB debugging was not activate befor the bricking. The only option i can use to flash something seems to be sideload. Also, where can i find the stock recovery?? I acces the fastboot mode from stock recovery. Isn t this enough?
That is what i recieve when i try to install a recovery using the tool. I can wait all day long.
Also, wehn i try to use the command [FASTBOOT]REBOOT INTO ANY CUSTOM RECOVERY WITHOU INSTALL i recieve this:
When i use the command [FASTBOOT] REFLASH THE STOCK USING MANUALLY DOWNLOADED FACTORY IMAGE i get this. (i donwloaded the official signed fastboot rom and followed the instructions)
And that is what i get when i try to sideload the cm signed rom with the [ADB]SIDELOAD A ZIP FILE command

Related

Stuck in RESCUE MODE screen, please HELP ME!!

Hi all!!!
I'm screwed!! :crying::crying::crying:
I think I bricked the phone!
Please help!!
Backups files I already have
A-WRP is correctly installed and I made a full nandroid backup.
B-I have a full partitions backups made with Partitions Backup and Restore App (Root access required). I backup all the partitions, all of them in raw mode. All the files are *.img ready to flash with fastboot.
C-I have a full B132 ALE-L21 stock ROM that was working perfectly before.
The problem
1-adb is not recognizing the device
2-fastboot is not recognizing the device
3-I cannot enter TWRP
4-Huawei EMUI 3 buttons (volume up + volume down + on/off button) function doesn't start neither (I'm trying to force the update to B132 ROM)
5-The phone enters directly to Rescue Mode and says:
error! Func NO : 8 (hifi image) Error NO : 1 (Security verify faild!)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So the phone is still working and I got this RESCUE MODE screen but I can't do anything when this screen is displayed.
Any idea? What can I try?
Please, I really need your help, anything you can imagine to try please, let me know!!!
Thanks in advance!!!
Update:
Finally I was able to enter in FASTBOOT & RESCUE MODE following this procedure:
1-Turn off the phone
2-Connect USB cable to computer but NOT to the phone
3-Press the volume down button and hold It
4-Connect the USB cable to the phone
5-Ready, the phone will turn on automatically in this mode (DO NOT press the power button)
So, now I have fastboot but I CANNOT flash the f.....ing HIFI partition
I tried:
-fastboot flash hifi hifi.img --> command not allowed
-fastboot flash radio hifi.img --> command not allowed
-fastboot flashing unlock --> command not allowed
-I tried to enter recovery mode. I have TWRP installed, I can also flash It again with fastboot, everything good but can't access It after that!!!!
-ADB is not working
-I flash a B052 ROM, then put B132 Update.app file in SD Card root\dload and try to force update by pressing volume up + volume down + power, nothing
-I flash the B132 ROM again , then put B170 Update.zip file in SD Card root\dload and try to force update by pressing volume up + volume down + power, nothing
-I try fastboot update update.zip but It says no android-info.txt nor android-product.txt
-I try to create a flashable .zip file for fastboot but It requires .sig files for the boot, recovery and system partitions
-HiSuite open ups automatically on the computer but can't connect to phone, the phone is not recognize by HiSuite but in windows says Marshall London Bootloader Interface. I can change that to Huwaei HDB Interface, Android ADB Interface, etc. etc. in device manager. A couple of times in the phone screen refreshes saying "Rescue mode enter.." but no way, HiSuite can't connect.
I tried lastest HiSuite version v2.3.55.1 and v1.8.2.206, nothing.
So, I have fastboot, what else can I do? Can somebody help me build a .zip file flashable with fastboot?
Is there any other fastboot or tool (I tried mfastboot too) that may allow me to flash HIFI partition?
With the phone like this, which USB device shows up? (HardwareID)
Try to put phone in manual download mode.
Alferboy said:
With the phone like this, which USB device shows up? (HardwareID)
Try to put phone in manual download mode.
Click to expand...
Click to collapse
Trying to do that I get FASTBOOT & RESCUE MODE but I can't do anything. How I may enter to download mode?
loredata said:
Trying to do that I get FASTBOOT & RESCUE MODE but I can't do anything. How I may enter to download mode?
Click to expand...
Click to collapse
Fastboot should be enough.
Alferboy said:
Fastboot should be enough.
Click to expand...
Click to collapse
No way, can't flash HIFI partition.
Device is detected as Android Sooner Single ADB Interface.
I tried:
fastboot flash HIFI HIFI.img
fastboot flash hifi HIFI.img
fastboot flash HIFI hifi.img
Always the same error: FAILED <remote: command not allowed>
1.Download b052 unzip/unRAR it
2.Extract from unzipped update.app through huawei update extractor :
boot, cust, recovery, system, userdata
to the folder where u have adb
3.Start cmd in that ADB folder
4.Flash via fastboot those 5 img files
5.After flashing those files use command fastboot reboot
6. Boot phone
7. Update to latest ROM version via ota
Wysłane z mojego ALE-L21 przy użyciu Tapatalka
I have the same problem and it doesnt work... Some many line is failed in the command...
iznogoud69 said:
I have the same problem and it doesnt work... Some many line is failed in the command...
Click to expand...
Click to collapse
Try these commands:
chdir C:\adb
fastboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
PD: What the f**ck is HIFI?
Had the same problem and solved it. What I did:
1) Disconnect and power off.
2) Put a stock rom (UPDATE.APP) on SD card in folder dload and put it in the phone.
3) Connect as described above to enter FASTBOOT & RESCUE MODE
4) fastboot flash cust cust.img
5) fastboot flash recovery recovery.img
6) fastboot flash boot boot.img
7) Disconnect and power off.
8) Hold down Volume+ AND Volume- AND Power until the phone enters EMUI system update mode and stars update from the SD card.
After a few minutes: Up and running.
I cant fix my phone
Geladk said:
Had the same problem and solved it. What I did:
1) Disconnect and power off.
2) Put a stock rom (UPDATE.APP) on SD card in folder dload and put it in the phone.
3) Connect as described above to enter FASTBOOT & RESCUE MODE
4) fastboot flash cust cust.img
5) fastboot flash recovery recovery.img
6) fastboot flash boot boot.img
7) Disconnect and power off.
8) Hold down Volume+ AND Volume- AND Power until the phone enters EMUI system update mode and stars update from the SD card.
After a few minutes: Up and running.
Click to expand...
Click to collapse
I follow your steps and i cant fix my phone, at the moment of enter in EMUI system update with de 3 keys, It can't update... I only see the screen of Rescue mode
loredata said:
Hi all!!!
I'm screwed!! :crying::crying::crying:
I think I bricked the phone!
Please help!!
Click to expand...
Click to collapse
Did you solved the problem?
Geladk said:
Had the same problem and solved it. What I did:
1) Disconnect and power off.
2) Put a stock rom (UPDATE.APP) on SD card in folder dload and put it in the phone.
3) Connect as described above to enter FASTBOOT & RESCUE MODE
4) fastboot flash cust cust.img
5) fastboot flash recovery recovery.img
6) fastboot flash boot boot.img
7) Disconnect and power off.
8) Hold down Volume+ AND Volume- AND Power until the phone enters EMUI system update mode and stars update from the SD card.
After a few minutes: Up and running.
Click to expand...
Click to collapse
I have the exactly same problem.
I got 'remote: Command not allowed' when I flash the 3 .img files.
But it says that PHONE unlocked.
Could you let me know how to fix it?
sbihero said:
I have the exactly same problem.
I got 'remote: Command not allowed' when I flash the 3 .img files.
But it says that PHONE unlocked.
Could you let me know how to fix it?
Click to expand...
Click to collapse
You can try this method via HiSuite
greatslon said:
You can try this method via HiSuite
Click to expand...
Click to collapse
seriously? chinese?
I HAVE THE SAME PROBLEM AND ICAN NOT SOLVE IT
IHAVE ROOTED MY PHONE BEFORE THAT IS THE guarantee IS STEEL WORKING ?
guarantee
Use this tutorial is in spanish but it worked for me
http://www.htcmania.com/showthread.php?t=1112055
Need to have unlocked bootloader.
Put your phone in fastboot mode.
Use the unziped file you just downloaded.
Run it, it does all for you, instructions are in spanish, but you can figure it out.
Regards
Unlock bootloader
HUSSENISAM said:
I HAVE THE SAME PROBLEM AND ICAN NOT SOLVE IT
IHAVE ROOTED MY PHONE BEFORE THAT IS THE guarantee IS STEEL WORKING ?
guarantee
Click to expand...
Click to collapse
rubentkato77 said:
Use this tutorial is in spanish but it worked for me
http://www.htcmania.com/showthread.php?t=1112055
Need to have unlocked bootloader.
Put your phone in fastboot mode.
Use the unziped file you just downloaded.
Run it, it does all for you, instructions are in spanish, but you can figure it out.
Regards
Click to expand...
Click to collapse
Hi,
Do as rubentkato77 told, unlock bootloader eve if it tells you that is already unlocked. Be sure you have it unlocked by you, then follow the procedure as rubentkato77 told you. It is working like a charm. I have done this already for quiet some time.
Cheers.
My Huawei P8 GRA-UL00 Stuck in RESCUE MODE screen, please HELP ME!!
CristiMCI said:
Hi,
Do as rubentkato77 told, unlock bootloader eve if it tells you that is already unlocked. Be sure you have it unlocked by you, then follow the procedure as rubentkato77 told you. It is working like a charm. I have done this already for quiet some time.
Cheers.
Click to expand...
Click to collapse
awais awais said:
Click to expand...
Click to collapse
awais awais said:
Click to expand...
Click to collapse
First and foremost, this is P8 Lite section of the forum.
Did you followed unlocking bootloader procedure for P8? Be sure you have unlocked bootloader, otherwise do it again and retry to flash those 4 files extracted with "Huawei Update Extractor" from FULL APP ROM image specific for your P8 GRA-UL00.
BTW, I have used Fedora Linux v23 to make all the Android moves, never Windows because it fails big time. +1 for Linux :good:
Sorry mate, I don't own a P8, but a P8 Lite. Cheers.
I have the same error How can i fix it?

UrgenT pls help! Huawei p8 lite stuck in logo scr. Phone is new and its locked by net

The phone is brad new i tried to return to them they recejeted saying that he was droped in water but it diddnt..i tried to fastboot and rescue but phone locked cant do a thing..someone pls help so i can prove they dont know how to fix it
You need to try to go to fastboot.
Plugin your phone to your pc.
Best way to try is to first hard reset your phone. "vol up + vol down + power button" for 10 seconds or longer (until its restart)
Then try to go into fastboot by holding down the "vol down + power button" for 10 seconds or longer (until in fastboot)
When you are in fastboot you need to unlock first your bootloader and then you can flash stock firmware.
olrak said:
You need to try to go to fastboot.
Plugin your phone to your pc.
Best way to try is to first hard reset your phone. "vol up + vol down + power button" for 10 seconds or longer (until its restart)
Then try to go into fastboot by holding down the "vol down + power button" for 10 seconds or longer (until in fastboot)
When you are in fastboot you need to unlock first your bootloader and then you can flash stock firmware.
Click to expand...
Click to collapse
I dont know how to unlock it when i cant turn the phone on,and hi suite cant recogize phone too..and if i stay phone on it just keep restarting..
try to enter in recovery mod by press and hold power button and volume up at the same time,in recovery wipe data factory reset(it will delete your phone memory)and wait till is done,now wipe cache,wen is done restart to system
cristi.blidariu said:
try to enter in recovery mod by press and hold power button and volume up at the same time,in recovery wipe data factory reset(it will delete your phone memory)and wait till is done,now wipe cache,wen is done restart to system
Click to expand...
Click to collapse
Cant tried all that..said Phone locked..thats a problem dont know how to unlock recovery and boot mode
what version you have on your phone?
cristi.blidariu said:
what version you have on your phone?
Click to expand...
Click to collapse
I had regular not rooted 5.1 Lollipop..And just stucked on logo scr and keep restarting
is say phone locked only if you are in fastboot/rescue mod,in that case just press and hold volume up button until your phone restart,and to enter in recovery press and hold volume up and power button,to unlock your bootloader watch this tutorial https://www.youtube.com/watch?v=63L7FBuWFrc
I cant get product ID number becouse i need keyboard on phone..oMG..can someone tell me some other way to get product ID?
Listen up ppl i managed to unlock it now..good job!!! And thnks but problem is i cant manage to reinstaled becouse i cant connect him to PC with pc suite..is there any other way so i can somehow reinstal system:!
i tried with vol + vol - and power And just wont start instaling update..and folder named dload like iy should right?! any sugestions?
Now you can flash files with adb,so first try to flash boot and see if is work,if not you need to flash all files starting with boot,recovery,cust and system
cristi.blidariu said:
Now you can flash files with adb,so first try to flash boot and see if is work,if not you need to flash all files starting with boot,recovery,cust and system
Click to expand...
Click to collapse
Where can i find that img. files for my huawei p8 lite..can u link me pls man im going to flash something wrong i feel it
Tatharon said:
Where can i find that img. files for my huawei p8 lite..can u link me pls man im going to flash something wrong i feel it
Click to expand...
Click to collapse
first you need to download HuaweiUpdateExtractor,with this app you will be able to extract files form update.app,extract in adb folder,and use this commands:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is adb and fastboot,download and extract you will find a folder named adb
https://mega.nz/#!Pc9zjDYB!X0wTeiFdY-ca70K9tI-b5fYf40LpcVExIEim0Xk9v14
and this is huawei update extractor
https://mega.nz/#!OI8kWahZ!6KSgIyz3a-Dp318qflV5J5VlrC8ZGu7fWFlQyYVq-m0
good luck
cristi.blidariu said:
first you need to download HuaweiUpdateExtractor,with this app you will be able to extract files form update.app,extract in adb folder,and use this commands:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
View attachment 3701298
View attachment 3701299
View attachment 3701300
this is adb and fastboot,download and extract you will find a folder named adb
https://mega.nz/#!Pc9zjDYB!X0wTeiFdY-ca70K9tI-b5fYf40LpcVExIEim0Xk9v14
and this is huawei update extractor
https://mega.nz/#!OI8kWahZ!6KSgIyz3a-Dp318qflV5J5VlrC8ZGu7fWFlQyYVq-m0
good luck
Click to expand...
Click to collapse
Done all that mate thnks buy problem is adb wont find img. file to boot it
question is where should i put a img. files so adb can find them..i tried to find that android folder but i dont hawe it on my pc
Just download from the link and extract to desktop,you will find a folder adb,so in that folder put the files:boot,cust,recovery and system,now open adb folder,press and hold shift an right click,search for option open command window here,wen window open conect your phone via pc an run the commands:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
olrak said:
You need to try to go to fastboot.
Plugin your phone to your pc.
Best way to try is to first hard reset your phone. "vol up + vol down + power button" for 10 seconds or longer (until its restart)
Then try to go into fastboot by holding down the "vol down + power button" for 10 seconds or longer (until in fastboot)
When you are in fastboot you need to unlock first your bootloader and then you can flash stock firmware.
Click to expand...
Click to collapse
my huawei p8 lite stuck at boot logo, but i can twrp recovery, fastboot etc, i guess had flashed it all along with internal memory.. plz guide me how to flash a rom.
---------- Post added at 03:37 AM ---------- Previous post was at 03:35 AM ----------
my huawei p8 lite stuck at boot logo, but i can access twrp recovery, fastboot etc, i guess had flashed it all along with internal memory.. plz guide me how to flash a rom.
Everyone, I made this to go from the start. Follow this guide (also in txt form)
It's gotten to this. You've tinkered with your phone and it's got into a bootloop, also known as a softbrick. Have no fear though, for software problems are much easier to solve than hardware issues. If you have the latter, pray and get in touch with the place you bought your phone from or Huawei themselves. Let's start booting.
Yeah, you could use the numerous scripts in XDA to automate some stuff, but you won't learn much that way. I've found that a) adb and fastboot are really easy programs that Google has provided us with to solve issues/develop and b) their knowledge helps with problemsolving for Android in general. It's good to know your phone. That's the open nature that iOS cannot achieve.
1. Getting the SDK Platform Tools (adb, fastboot e.t.c.)
You can always get the latest SDK Platform Tools .zip by clicking on the link for your OS: Windows, Mac, Linux.
Extract the .zip's contents in a folder. (I trust you know how, even phones can do it nowadays... Anyhow, you can get 7-Zip for Windows, as the built in zip manager is limited)
2. Using the SDK Platform Tools
You give commands to adb and fastboot though a command window.
You have 2 choices. You can either:
a) work from the folder you extracted the sdk tools in (I have them in D:\Portable\platform-tools).
You'll have to do [Shift] + (Right click) > "Open command (or PowerShell) window here"
or
b) edit your PATH environment variable, so you can open a command (or PowerShell) window anywhere you want.
Call the program by name to give commands (e.g. adb <command>)
3. Getting into fastboot/bootloader mode
You can do that in 3 ways:
a) Shut down the phone. While holding VOL- (down), connect a USB cable that is plugged to a power source (usually your PC, since you are planning to use the fastboot program).
b) We'll use the adb utility.
You need to enable USB debugging for this. After that you can refer to "chapter" 2.
Type
adb reboot bootloader
Click to expand...
Click to collapse
and press [Enter].
c) Reboot into a custom recovery like TWRP and go to Reboot > Bootloader
4. Flashing the stock images
Here's the part we care most about, to get out of the bootloop.
If you are truly in fastboot mode, with the green android dude (his name is Andy) and the white background then the command
fastboot devices
Click to expand...
Click to collapse
should return your device's serial number. Then you can go ahead and flash the 4 needed partions from the stock ROM with fastboot.
First of all, you need the 4 .img files for boot, recovery, cust and system.
You can get these as follows:
This page lists all the Huawei Firmware for the ALE model, aka our P8 Lite (Thanks @persona78 for the link, see here). You can translate to English with the Google Translate toolbar on the top. Find a firmware package of type FullOTA and click on the update link to download the zip update file. Inside that zip is the UPDATE.APP file we need, so extract it somewhere.
Use Huawei Update Extractor to extract boot, recovery, cust, and system as .img files.
Open a command window in the folder with the files and rename them accodingly if you wish (e.g. 06.boot.img -> boot.img)
Then you can flash them in fastboot mode by executing these commands 1 by 1. They're pretty self-explanatory.
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
Click to expand...
Click to collapse
That last one may take a bit. Then you can do
fastboot reboot
Click to expand...
Click to collapse
@JpegXguy
fastboot mode, remote command not allowed, I cant start on system to enable USB debugging, fastboot edl doesn't work, so what can I do?

Fix bootloop in redmi note 3 (no recovery ,no edl mode)

After trying to flash the latest 7.1.1 cm 14 ropms many people ended up in bootloop where your phone switch on ,shows mi logo and rebbot again. Many where not able to enter recovey mode also.. Now i come up with a perfect soluton for you all on how to fix these issues in your phone..Lets Get started..
If anything goes wrong iam not responsible.Do it At your Own Risk.
Requirements
------------------
1. Enter edl .rar (attached below)
2.Miui Stock Rom (FastBoot). Download it from(only use this version) here
3.Phone Must have Charge of 50% or more.
4.Unlock Boot loader.zip (Attched Below)
6.MIPhone Tools and install it .Get it from here
6.Extract all the file
7. PDA Net.(Optional,but installing will be useful). Get it from here
Once you have all of the file we can move on
Steps
------
1. Put Your Phone into fastboot mode by pressing Vol Down and power button at same time.
2.Connect your Phone With Your PC
3.Run EDL Mode.exe from the zip Enter edl.. Now your phone must be in edl mode. You can see a light blinking at the top of your phone.
4. From the Unlock Boot Loader folder copy "emmc_appsboot.mbn" to the rom folder ie)
kenzo_global_images_V7.1.8.0.LHOMICL_20160129.0000.14_5.1_global--> images--> paste it there (replace/overwrite if existing)
5. Once the above step is done, Open MIFlash tool as administrator. Browse the folder
kenzo_global_images_V7.1.8.0.LHOMICL_20160129.0000.14_5.1_global and select it..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
6.From the drop Down Menu Select Advanced.
7.Set Fastboot Script As Flash_ALL.Bat.
8.Set Flash Programmer As prog_emmc_firehose_8976_ddr.mbn from images folder.
9. Set RAW Xml File as rawprogram*.xml from images folder
10. Set Patch XML File as patch*.xml from images folder.
11. Video Help HERE.... Watch from 2.40 (Ignore the other portion,We dont need that Part)
Special [email protected] for the video.. I didn't made that video..
12. Once The Above step is done. Click REFRESH OPTION,and you will see Phone detected By The Name COMXX.(XX will be a number)
13.Click Flash and Wait for some time and allow the phone to reboot.
14.Once all the step is done your phone will be good to use..:fingers-crossed: :fingers-crossed:
UNLOCKING BOOT LOADER AND INSTALLING TWRP AGAIN
-------------------------------------------------------------------------
1.Once Your Phone Reboots successfully enable USB Debugginf From Developer Option.
2.Connect Your phone to your PC and Open CMD as administrator.
3.Type in "adb devices".
4. Cmd will show a random number and Device (Everyone will be knowing this,but for info only iam writing it here)
5.Type "adb reboot bootloader". Now your phone will boot into fastboot mode.
6.Type "fastboot oem device-info" to get device status.
7.Type "fastboot oem unlock-go" to unlock bootloader.
8.Again type "fastboot oem device-info" to check to find if device is unlocked.(Do not reboot YET)
9. Now Downlaod TWRP from HERE
10. Now Got to the folder containig TWRP . By holding the Shift Key Of key Board ,right click the mouse and select OPEN COMMAND WINDOW HERE.
11. Type "fastboot flash recovery recovery_filename.img"
12.Type "fastboot reboot".
You Phone will be good to go. If anything goes wrong or you have any doubt Comment Below do not pm me..i will not reply..
If this thread helpef you thumbs up and do comment and shre this post
So i do not need to unlock the boot loader before using MiTool to flash phone via EDL
ahh988 said:
So i do not need to unlock the boot loader before using MiTool to flash phone via EDL
Click to expand...
Click to collapse
Nope if phone is bricked enter fastboot mode and run enter edl.exe to enter edl,flash ROM using mi flash tool
adithyan25 said:
Nope if phone is bricked enter fastboot mode and run enter edl.exe to enter edl,flash ROM using mi flash tool
Click to expand...
Click to collapse
I did that but phone is still stuck . I'm getting infinite boot animation ?
ahh988 said:
I did that but phone is still stuck . I'm getting infinite boot animation ?
Click to expand...
Click to collapse
Boot animation or simply mi logo and then vibrating and again rebooting???
If mi flash tool shows successfully done without any errors then
Try this
Roeboot to fast boot and type
fastboot oem unlock-go
I guess it will be fixed
adithyan25 said:
Boot animation or simply mi logo and then vibrating and again rebooting???
If mi flash tool shows successfully done without any errors then
Try this
Roeboot to fast boot and type
fastboot oem unlock-go
I guess it will be fixed
Click to expand...
Click to collapse
I am stuck at boot animation with the three white dots spinning for ever ? will try to do as you said
I tried fastboot oem unlock-go but i get response: token verification failed and device still stuck on bootanimation
well, i think this caused by relocking bootloader after we flash a new firmware. if that happens, just go in fastboot mode by hold power button + volume down, then unlock it again using mi unlock. reboot it..your twrp is back.
no need to enter edl mode & install twrp again, btw thanks..this is helpful
nitephoenix said:
well, i think this caused by relocking bootloader after we flash a new firmware. if that happens, just go in fastboot mode by hold power button + volume down, then unlock it again using mi unlock. reboot it..your twrp is back.
no need to enter edl mode & install twrp again, btw thanks..this is helpful
Click to expand...
Click to collapse
always my pleasure
For some mi unlock stucks at 50%.. I was one of them...every time I try fails...so I found this was the only way for those who can't access it using mi unlock
tips to avoid relocking bootloader, when u want to flash a new firmware..just delete emmc apsbot.mbn file inside the firmware using winrar or etc, or u can use psy-man firmware because the emmc file has been deleted
nitephoenix said:
tips to avoid relocking bootloader, when u want to flash a new firmware..just delete emmc apsbot.mbn file inside the firmware using winrar or etc, or u can use psy-man firmware because the emmc file has been deleted
Click to expand...
Click to collapse
Yeah...I know that...but it does not support volte. .only abhisheks fw sprt volte
nitephoenix said:
tips to avoid relocking bootloader, when u want to flash a new firmware..just delete emmc apsbot.mbn file inside the firmware using winrar or etc, or u can use psy-man firmware because the emmc file has been deleted
Click to expand...
Click to collapse
@nitephoenix
Can we then flash update marshmallow global firmware this way? (Just delete emmc apsbot.mbn file inside the firmware). Thanks
Pleroma said:
@nitephoenix
Can we then flash update marshmallow global firmware this way? (Just delete emmc apsbot.mbn file inside the firmware). Thanks
Click to expand...
Click to collapse
don't flash official miui from twrp (you better do it in edl mode), but yes you can flash custom miui like miui eu, miuipro, multirom, epic miui etc from twrp. and..after u delete the emmc file inside the firmware which is included on every miui rom, your bootloader will be safe
nitephoenix said:
don't flash official miui from twrp (you better do it in edl mode), but yes you can flash custom miui like miui eu, miuipro, multirom, epic miui etc from twrp. and..after u delete the emmc file inside the firmware which is included on every miui rom, your bootloader will be safe
Click to expand...
Click to collapse
I used to flash it via twrp ..(by deleting bootllader file) followed by flashing lazyflasher...I didn't faced any prblm yet
Mine behaves different
I tried restoring the backup it started to back up and completed sucessfully but when i reboot there comes Mi logo and again it boots to TWRP Recovery .... Same case with any ROM ... Kindly tell me what to do.
ZCX recovery i have.
sarabeshsab said:
I tried restoring the backup it started to back up and completed sucessfully but when i reboot there comes Mi logo and again it boots to TWRP Recovery .... Same case with any ROM ... Kindly tell me what to do.
ZCX recovery i have.
Click to expand...
Click to collapse
Probably the problem with bootloader file
not a whole lot of talk anywhere else so i'll try here. i just got my kenzo few days ago, jumped the gun and started trying to get twrp on it. i'm assuming the bootloader was locked. As of right now it wont boot up, its in edl mode maybe... red led flashes and i can upgrade driver to 9008. sometimes its recognized by miflash and when it is and i try to flash stock fastboot it gives me an error. i know thats a lot to take in but i'm trying to cover all my bases. the phone came from overseas so sending it back isnt really an option. any help is appreciated.
Jjleininger said:
not a whole lot of talk anywhere else so i'll try here. i just got my kenzo few days ago, jumped the gun and started trying to get twrp on it. i'm assuming the bootloader was locked. As of right now it wont boot up, its in edl mode maybe... red led flashes and i can upgrade driver to 9008. sometimes its recognized by miflash and when it is and i try to flash stock fastboot it gives me an error. i know thats a lot to take in but i'm trying to cover all my bases. the phone came from overseas so sending it back isnt really an option. any help is appreciated.
Click to expand...
Click to collapse
Download eiter China based ROM or ROM from post.
Mi flash tool have many prolems.
Some tips:-
Make sure driver enforcement is disabled in PC.
All drivers including PDA net is installed.
Copy paste the unlocked bootloade file inside images folder and replace original one. Even after tryig this method it fails try my other method unbrick viafasrboot
uhm, this does not work for some reason...
i did everything as you said but in the end it just says cathasrophic error and something
After flashing i get Mi logo, vibration and reboot, please help

(Solved) Yureka Plus YU5510A - Rooted/TWRP 2.8.7.0

DWYOR
After a long time of googling I got a solution for yu5510a full access.
You need
Adb + fastboot
Twrp 2.8.7.0 tomato
SuperSU.zip
Coolpad drivers
Cyanogen ROM V1 from firmwarefile.com
Any Custom Rom, I am using aosp extended.
Gapps
Memory card
Install all drivers , adb & fastboot.
First flash Cyanogen ROM using YGDP tool
Use version 3.98 in other versions I got problems.
After ROM installation enable developer option.
Enable android debugging, fast reboot and check update cyanogen recovery
Now connect phone with PC
Goto adb folder
Copy twrp.img in adb folder
Shift + Right click select open command window here
Type adb devices
Device should be shown if not showing try to install adb drivers
Now after that
Type Command adb reboot-bootloader
Device will be rebooted in bootloader
Type command fastboot -i 0x1ebf oem device-info to verify device in fastboot mode and your bootloader is unlocked or not.
If bootloader showing unlocked then follow next process if not then unlock it
Type command fastboot -i 0x1ebf oem unlock
Boot loader unlocked now.
Remove data cable and remove battery from phone for 30 secs and reinsert again.
Press volume + key and hold
Attach phone with PC ( it shows fastboot mode)
After that type command
fastboot -i 0x1ebf flash recovery twrp.img
When done remove data cable & battery
After 30 secs reinsert battery
Press Volume + , Volume - & Power key
When yu logo appears release power key and keep pressing both volume keys
You will be goto twrp
Now wipe everything also format data/don't delete mmc
Restart twrp to recovery
Your internal and external storage are mounted.
Install any custom ROM for yureka/yureka plus
Flash gapps ( not required in miui & quarkos)
Flash SuperSU.zip
Reboot
It takes 10-15 minutes for first boot .
Done
Flash Latest NON-HLOS.bin before flashing any volte ROM.
Flash through fastboot
File link
https://drive.google.com/file/d/0B8Vodzmhc0GlXzdtOUFjb29EOFU/view
Extract .zip
Copy NON-HLOS.bin in adb folder
Open command prompt here
Connect phone into fastboot mode
Type command
fastboot -i 0x1ebf flash modem NON-HLOS.bin
Wait till process done.
Disconnect phone
Remove battery and insert again
Goto twrp recovery.
Install any volte enabled ROM.
Enjoy.:good:
OEM unlock command not found
hi,
I am trying to root my yu yureka plus( YU5510A white color) running android 5.1.1 , build number is 5.1.111.P0.160314.YU5510A , i am able to connect the phone to my PC running adb,
"adb devices" lists the phone , "adb reboot bootloader" puts the phone in fastboot ( screeen doesnt show fastboot instead it shows do not disconnect usb cable and non secure phone). When i run the command fastboot -i 0x1ebf oem unlock , im getting the error as command not found. same error im getting when i run the command fastboot -i 0x1ebf oem device-info
what could be the reason.
Any help in this regard is appreciated.
nischait said:
DWYOR
After a long time of googling I got a solution for yu5510a full access.
You need
Adb + fastboot
Twrp 2.8.7.0 tomato
SuperSU.zip
Coolpad drivers
Cyanogen ROM V1 from firmwarefile.com
Any Custom Rom, I am using aosp extended.
Gapps
Memory card
Install all drivers , adb & fastboot.
First flash Cyanogen ROM using YGDP tool
Use version 3.98 in other versions I got problems.
After ROM installation enable developer option.
Enable android debugging, fast reboot and check update cyanogen recovery
Now connect phone with PC
Goto adb folder
Copy twrp.img in adb folder
Shift + Right click select open command window here
Type adb devices
Device should be shown if not showing try to install adb drivers
Now after that
Type Command adb reboot-bootloader
Device will be rebooted in bootloader
Type command fastboot -i 0x1ebf oem device-info to verify device in fastboot mode and your bootloader is unlocked or not.
If bootloader showing unlocked then follow next process if not then unlock it
Type command fastboot -i 0x1ebf oem unlock
Boot loader unlocked now.
Remove data cable and remove battery from phone for 30 secs and reinsert again.
Press volume + key and hold
Attach phone with PC ( it shows fastboot mode)
After that type command
fastboot -i 0x1ebf flash recovery twrp.img
When done remove data cable & battery
After 30 secs reinsert battery
Press Volume + , Volume - & Power key
When yu logo appears release power key and keep pressing both volume keys
You will be goto twrp
Now wipe everything also format data/don't delete mmc
Restart twrp to recovery
Your internal and external storage are mounted.
Install any custom ROM for yureka/yureka plus
Flash gapps ( not required in miui & quarkos)
Flash SuperSU.zip
Reboot
It takes 10-15 minutes for first boot .
Done
Click to expand...
Click to collapse
nithin1664 said:
hi,
I am trying to root my yu yureka plus( YU5510A white color) running android 5.1.1 , build number is 5.1.111.P0.160314.YU5510A , i am able to connect the phone to my PC running adb,
"adb devices" lists the phone , "adb reboot bootloader" puts the phone in fastboot ( screeen doesnt show fastboot instead it shows do not disconnect usb cable and non secure phone). When i run the command fastboot -i 0x1ebf oem unlock , im getting the error as command not found. same error im getting when i run the command fastboot -i 0x1ebf oem device-info
what could be the reason.
Any help in this regard is appreciated.
Click to expand...
Click to collapse
Try without using 0x1ebf and report.
nischait said:
Try without using 0x1ebf and report.
Click to expand...
Click to collapse
I tried without -i 0x1ebf also but it does not show in fastboot. With -i 0x1ebf it shows "xyznumbers fastboot" . The problem now is , I flashed through YGDP tool and now it shows aboot failed image, and does not boot at all.
Why doe my phone show non secure phone ?
Please help.
Yogesh1969 said:
I tried without -i 0x1ebf also but it does not show in fastboot. With -i 0x1ebf it shows "xyznumbers fastboot" . The problem now is , I flashed through YGDP tool and now it shows aboot failed image, and does not boot at all.
Why doe my phone show non secure phone ?
Please help.
Click to expand...
Click to collapse
Download cyanogen ROM and flash it with ygdp
1st ever rom uploaded in AFH.
Your device should be boot up.
Then try with command prompt.
May be new device having different device ID.
nischait said:
Try without using 0x1ebf and report.
Click to expand...
Click to collapse
Hi...
I too face the same problem, I tried fastboot adb and YU yureka drivers reinstalling and connected device to PC it gets charger when connection in on, when connected in fastboot mode on device it shows fastboot but when check in PC for device info, it dosen't show any connected device. I followed many tutorials for this to install TWRP but its impossible to install without establishing a proper connection. I also tried to install TWRP without PC, for this i need to root my device and flash TWRP img, so I started trying root I had used kingroot, kingoroot, towelroot and some more but failed to root, I am still trying to install TWRP can anyone help me in either of the process to install TWRP.
nischait said:
Download cyanogen ROM and flash it with ygdp
1st ever rom uploaded in AFH.
Your device should be boot up.
Then try with command prompt.
May be new device having different device ID.
Click to expand...
Click to collapse
I couldnt find the ygdp version of Cynogen, any way I found a way from youtube which solved my problems.
Link : https://www.youtube.com/watch?v=2Gpz65r2pNM
---------- Post added at 05:21 PM ---------- Previous post was at 05:18 PM ----------
vijaykumarbabu079 said:
Hi...
I too face the same problem, I tried fastboot adb and YU yureka drivers reinstalling and connected device to PC it gets charger when connection in on, when connected in fastboot mode on device it shows fastboot but when check in PC for device info, it dosen't show any connected device. I followed many tutorials for this to install TWRP but its impossible to install without establishing a proper connection. I also tried to install TWRP without PC, for this i need to root my device and flash TWRP img, so I started trying root I had used kingroot, kingoroot, towelroot and some more but failed to root, I am still trying to install TWRP can anyone help me in either of the process to install TWRP.
Click to expand...
Click to collapse
For drivers problem install pdanet. And you can refer to the youtube video link (above post) if you want for all needs.
vijaykumarbabu079 said:
Hi...
I too face the same problem, I tried fastboot adb and YU yureka drivers reinstalling and connected device to PC it gets charger when connection in on, when connected in fastboot mode on device it shows fastboot but when check in PC for device info, it dosen't show any connected device. I followed many tutorials for this to install TWRP but its impossible to install without establishing a proper connection. I also tried to install TWRP without PC, for this i need to root my device and flash TWRP img, so I started trying root I had used kingroot, kingoroot, towelroot and some more but failed to root, I am still trying to install TWRP can anyone help me in either of the process to install TWRP.
Click to expand...
Click to collapse
Getting your device connected is a very important stage, whether it is system,recovery or fastboot. From what I read , you can connsct through fasatboot, since you flashed cyanogen. Just flash TWRP 3.2.1 or so which is the latest, through fastboot:
fastboot flash recovery twrp.3.2.1 .img ( Remember the spaces, the name twrp.xxx.img should be same as you downloaded. If flash is successful, you can see twrp when you boot to recovery. Then flash supersu file and/or whichever rom you want.
Sorry for late answers.
I was lil busy and sorry for wrong address also.
You could get it from firmwarefile.com
I can't post link here but select yu yureka plus variant and download oldest CBP

How To Guide [GUIDE][HowTo] Unlock and root Nothing Phone (1)

ANNOUNCEMENT: I'M STOPPING THE FOLLOW UP AND UPDATE OF THIS TOPIC TODAY, IF SOMEONE WANTS TO TAKE OVER, CONTACT THE MODERATOR IN THIS LINK.
THE TOPIC REMAINS AS IT IS AND WILL NOT BE UPDATED ANYMORE (BY ME ANYWAY!)
GOOD CONTINUATION TO ALL​
Hey everyone,
It's been a few days since the Phone(1) went on sale. And already, Nothing is doing things right by making the Phone(1) Kernel available. The next step was to unlock the bootloader and root it. Both are already available and ready to use.
So don't deprive yourself and here is the process of the two operations.
You've already unlocked the bootloader and rooted a carrierless variant of either a Google Pixel or OnePlus, you should have no problem unlocking your Nothing Phone (1) and installing Magisk. For those of you with a memory lapse, here is a tutorial to guide you through the process.
- Disclaimer: I don't take any responsibility for anything you do to your tablet, which is to transform it into brick, break, or transform it into coffee machine - ​
Click to expand...
Click to collapse
How to bootloader unlock and root the Nothing Phone 1​After unlocking the bootloader, you can use Magisk to root the device.
You must first unlock the bootloader in order to be able to start third-party software. Here's how to do it:
Step 1: Unlock the Nothing Phone 1’s bootloader​
Open the Settings app on your Nothing Phone 1.
Tap on About phone.
Locate the section named Software info and tap on it.
On the next screen, tap on the Build number 7 times until it says you’re now a developer.
Go back to the main Settings page, tap on System, and near the bottom of the list, you should see Developer options. Tap on it.
You should see an OEM unlocking option. Enable it. For security purposes, it may ask you to input your lock screen PIN/password if you have one set.
Scroll down a bit until you see USB debugging. Enable it as well.
Plug in your Nothing Phone 1 into your PC/Mac/Chromebook. Make sure you have the Latest version of ADB and Fastboot (33.0.3) binaries installed.
Now open up a terminal window/Command Prompt instance and enter the following command: adb devices
If you see your device’s serial number and it says “authorized,” then you’re good to go. If this is your first time setting up ADB for this device, then you may see a prompt on your phone to enable USB Debugging for your PC. Grant it permission.
If you’re having trouble getting your Windows PC to recognize your device, try installing the latest Android USB Drivers.
Now, reboot to the bootloader menu. You can either do this by holding the power and volume down buttons while booting up, or by entering the following ADB command: adb reboot bootloader
Once you’re on the bootloader menu, you’ll now have to switch to using fastboot command to communicate with your device. To unlock the Nothing Phone 1’s bootloader, enter the following command: fastboot flashing unlock
In case you need to flash low-level firmware partitions like the bootloader images, you will have to execute another command afterwards: fastboot flashing unlock_critical
[NOT A MANDATORY TO UNLOCK CRITICAL, IT'S FOR ME BETTER TO NOT USE THIS COMMAND, THIS COMMAND COULD BE THE REASON SOME PEOPLE HAVE BRICK OR NOT WHEN GO BACK STOCK NOS]
You should now see text on screen warning you about the potential risks of unlocking the bootloader. On the screen next to the power and volume buttons, you should see some text. Press the volume up key until it says “unlock the bootloader.” Once it says this, press the power button.
The phone will unlock the bootloader and reboot back to the bootloader menu. This time, the bootloader will show a red warning icon and “unlocked” text.
Now, reboot your phone back to the Android OS. You can do this by sending the following fastboot command: fastboot reboot
Congratulations, your Nothing Phone 1 now has an unlocked bootloader!
You’ll see a warning message that your phone’s bootloader is unlocked on every boot, but don’t worry about that as it doesn’t affect your day-to-day use.
Step 2 - Rooting your Nothing Phone 1 with Magisk​With an unlocked bootloader, you can now boot modified boot images. For Magisk to work, you’ll need to patch the Nothing Phone 1’s stock boot image.
Since your device has been wiped earlier, you’ll need to go back and re-enable Developer Options and then re-enable USB Debugging. Make sure your Nothing Phone 1 is still recognized by your PC.
Download the full OTA package corresponding to the installed software version on the Nothing Phone 1.
Depending of your model, you have Global or EEA (European) firmware availables.
You can download the latest full OTA firmware package here.
Extract the stock boot image from the OTA package. For more information, take a look the “You have access to the recovery-flashable ZIP file” section our “How to Install Magisk on your Android Phone” tutorial.
In case you don’t want to download the whole OTA file, you can separately download the boot image just to the post #2 or from this post. However, to avoid version mismatch and other unforeseen errors, it is always advised to extract the boot image yourself.
Now that we have the stock boot image to patch, push it to your device with this command: adb push <path_to_file> /sdcard/Download
Download and install the Magisk app on the Nothing Phone 1.
Open the Magisk app and tap on the Install button.
Choose Select and Patch a File. A file manager will pop up.
Select the boot image that you pushed earlier and let Magisk patch it.
Pull it off your phone with this command: adb pull /sdcard/Download/magisk_patched_[random_strings].img
Reboot the Phone 1 into the bootloader: adb reboot bootloader
Flash the patched boot image: fastboot flash boot /path/to/magisk_patched_boot.img
Reboot the phone: fastboot reboot
Open the Magisk app and your Nothing Phone 1 should be rooted.
Keep in mind that unlocking the bootloader and rooting your Nothing Phone 1 will impact how you take advantage of updates. You'll have to learn to manually load monthly security patch updates. But don't worry, it's easy enough to do.​
-=o#0#o=-​
WARNING: I wrote this step to allow you to re-lock your bootloader, but it seems that for this step, there are some problems. So after this warning, if you continue on this path, I could not be held responsible for what you will have as a result: soft-bricked, bootloop, etc.​
Spoiler: Relock the bootloader of your Phone(1)
menu. You can either do this by holding the power and volume down buttons while booting up, or by entering the following ADB command: adb reboot bootloader
[*]Once you’re on the bootloader menu, you’ll now have to switch to using fastboot command to communicate with your device. To unlock the Nothing Phone 1’s bootloader, enter the following command: fastboot flashing lock
[*]Reboot your phone back to the Android OS. You can do this by sending the following fastboot command: fastboot reboot
Many thanks to Skanda Hazarika for his tutorial which you can read on the xda news page.
And thanks to Qiyue_ for the 1st Boot Magisk Patched for the Phone1
#root #nothingphone
Unbricking Nothing phone 1: Flash Stock Firmware with Fastboot
- Disclaimer: I don't take any responsibility for anything you do to your tablet, which is to transform it into brick, break, or transform it into coffee machine -​
Click to expand...
Click to collapse
Warning : The process below will erase all the data on your device. So, I invite you to make a full backup of the device beforehand.
Unfortunately, as I don't own the Phone(1) yet, I am unable to take screenshots with the Phone(1) at the moment. As soon as I can, I will put them online to finalize the tutorial. Thank you for your understanding
STEP 1: What you need and read before the process.
It’s really important for a process without problems
Install Android SDK and the Platform-tools folder
Download the Nothing OS version you need (see this post)
Extract the "payload bin" file from the rom
Extract the Firmware Stock "boot.img" from the rom (see this tutorial)
Unlock the bootloader of your Phone(1) (see this tutorial)
STEP 2: Boot the bricked phone 1 into Fastboot mode
Very often, a soft-bricked or boot-looped device may already be in Fastboot mode. However, if you are stuck in a boot-loop, long press the Power key to turn it off.
Then press and hold the Power and Volume Down keys (or Power and Volume Up keys on some devices) simultaneously to boot your device into Fastboot mode.
In case you are unable to turn off your device, let the battery discharge. Once it is drained, connect it to the charger. Then, as soon as it is about to start, use the Power and Volume Up/Down keys and it will start directly in Fastboot mode.
STEP 3: Format the device via Fastboot
1.Go to the platform-tools folder where the extracted ROM is located.
2.Then go to its address bar, type CMD in its address, and press Enter. This will launch the CMD window.
3.Now run the following command to perform a factory reset (optional but recommended)
Code:
fastboot -w
STEP 4: Flash the Nothing Phone 1 firmware via the Fastboot commands
Run the commands below in the CMD window [which is open in the platform-tools folder] to flash the partition file.
Very Important: Only run one command at a time. If you get an error, however, do not exit the process halfway, but go on to the next flashing command instead.
Don't forget to check your command line before validating it, because often a small error blocks you!
Spoiler: Command Lines
Code:
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash devcfg devcfg.img
flash fastboot dsp dsp.img
flash fastboot dtbo dtbo.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img fastboot
fastboot flash product product.img
fastboot flash qupfw qupfw.img
flash fastboot shrm shrm.img
flash fastboot system system.img
flash fastboot system_ext system_ext.img
flash fastboot tz tz.img
flash fastboot uefisecapp uefisecapp.img
flash fastboot vbmeta vbmeta.img
flash fastboot vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot flash vendor_boot vendor_boot.img
flash fastboot xbl xbl.img
fastboot flash xbl_config xbl_config.img
Step 5: If you have not had any errors, then you can run the command below to boot your device onto the operating system.
Code:
fastboot reboot
Well done , you have just debricked your Nothing Phone 1 by flashing the stock firmware via the fastboot commands.
I hope this tutorial has helped you find your Phone(1).
Thanks
Reserved
FILES FOR NOTHING OS - (stock-boot, etc. )
UPDATE 15/12/2022
Stock_Boot for Nothing OS here
Be carefull, be sure to select the good Stock Boot "Global" or "EEA" for your device.​
Extract Payload.bin via Payload Dumper Go
To start, download the payload-dumper-go 1.0.0 from Github [Credits: XDA Member @ssssut].
Then extract it to any convenient location on your PC. The file name will be something like payload-dumper-go_1.0.0_windows_amd64.
Rename it to payload-dumper-go.
Next, download the liblzma-5.dll file and transfer it to the same folder where the payload-dumper-go.exe file is located.
After that, transfer the payload.bin file to this folder as well.
So, from now on, you should have the 3 files payload-dumper-go.exe, payload.bin and liblzma-5.dll in one folder.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now go to the address bar of that folder, type "cmd" and press Enter. This will launch the command prompt window.
Type the command below to extract the payload.bin file:
Code:
payload-dumper-go payload.bin
The extraction process will now begin and will only take a few seconds.
Once this is done, all extracted files will be placed in a folder named extract_date_time which is created in this directory like this name : extracted_20220731_145751
The process is very simple and very fast. Anyone can do it. So don't hesitate, you have everything you need to do this yourself.
it's up to you now
If this has helped you, and if you appreciate my help.
Thanks
Is it possible to relock the bootloader?
Is it possible to relock the bootloader on an third party ROM?
@Sib64 does the device keep Widevine L1 when the bootloader has been unlocked?
Krullendhaar said:
Is it possible to relock the bootloader?
Click to expand...
Click to collapse
Yes.
Krullendhaar said:
Is it possible to relock the bootloader on an third party ROM?
Click to expand...
Click to collapse
No.
Could you also do a tutorial on how to update the OS when you're rooted?
I hope to find an EDL QPST full rom... better to stay safe and restore It in any case...
Mod is coming...
I tried this with the latest 1.1.0 ROM (got the ROM from https://www.xda-developers.com/nothing-phone-1-nothing-os-1-1-0-update/) but after relocking the bootloader the phone says that it's corrupt and can't get to boot Android.
ErChisus said:
I tried this with the latest 1.1.0 ROM (got the ROM from https://www.xda-developers.com/nothing-phone-1-nothing-os-1-1-0-update/) but after relocking the bootloader the phone says that it's corrupt and can't get to boot Android.
Click to expand...
Click to collapse
Is rooting success with 1.1.0 Rom?
Naveenakash said:
Is rooting success with 1.1.0 Rom?
Click to expand...
Click to collapse
I didn't try it with an actual app, but it was showing properly in Magisk. But bootloader needs to stay unlocked.
ErChisus said:
I tried this with the latest 1.1.0 ROM (got the ROM from https://www.xda-developers.com/nothing-phone-1-nothing-os-1-1-0-update/) but after relocking the bootloader the phone says that it's corrupt and can't get to boot Android.
Click to expand...
Click to collapse
Did you fix that issue?
Naveenakash said:
Did you fix that issue?
Click to expand...
Click to collapse
I didn't. I'm trying to factory reset the phone, but I can't seem to flash the ROM from bootloader.
ErChisus said:
I tried this with the latest 1.1.0 ROM (got the ROM from https://www.xda-developers.com/nothing-phone-1-nothing-os-1-1-0-update/) but after relocking the bootloader the phone says that it's corrupt and can't get to boot Android.
Click to expand...
Click to collapse
Hi! I don't know what the best solution would be, but I would definitely try it if I access the fastboot mode from recovery, reunlock the previously modded and closed bootloader, that is currently on the phone. Ater restarting the phone and its boots up, i would put back the one corresponding to the original software's in recovery fastboot mode and then close it. if the phone started, I do the next sw ota update, restart it and patch its bootloader with magic, then open again the new sw's bootloader from fastboot then flash the magisk patched one. But with thiese solution, you will lose all of your data and application from the phone, same like after you first unlocked the bootloader. ( like factory reset ). I hope it's understandable, unfortunately my English is not very good.
No matter from which partition (A/B)
lba810701 said:
Hi! I don't know what the best solution would be, but I would definitely try it if I access the fastboot mode from recovery, reunlock the previously modded and closed bootloader, that is currently on the phone. Ater restarting the phone and its boots up, i would put back the one corresponding to the original software's in recovery fastboot mode and then close it. if the phone started, I do the next sw ota update, restart it and patch its bootloader with magic, then open again the new sw's bootloader from fastboot then flash the magisk patched one. But with thiese solution, you will lose all of your data and application from the phone, same like after you first unlocked the bootloader. ( like factory reset ). I hope it's understandable, unfortunately my English is not very good.
Click to expand...
Click to collapse
I'm just testing the phone (driving another one yet) so I have no issues with losing data. But the only thing that worked for me was to unlock again the bootloader and then change the active partition (from B to A) within fastboot. After that I could boot the system and do a factory reset.
My issue now is that I'm still with an unlocked bootloader and whether I lock it with one partition marked as active or the other I can't boot to system.
ErChisus said:
No matter from which partition (A/B)
I'm just testing the phone (driving another one yet) so I have no issues with losing data. But the only thing that worked for me was to unlock again the bootloader and then change the active partition (from B to A) within fastboot. After that I could boot the system and do a factory reset.
My issue now is that I'm still with an unlocked bootloader and whether I lock it with one partition marked as active or the other I can't boot to system.
Click to expand...
Click to collapse
And what if you flash back the original bootloader to over the unlocked one, and after it you close it, not the modded one?
ErChisus said:
No matter from which partition (A/B)
I'm just testing the phone (driving another one yet) so I have no issues with losing data. But the only thing that worked for me was to unlock again the bootloader and then change the active partition (from B to A) within fastboot. After that I could boot the system and do a factory reset.
My issue now is that I'm still with an unlocked bootloader and whether I lock it with one partition marked as active or the other I can't boot to system.
Click to expand...
Click to collapse
Also, doing a factory reset from recovery doesn't relock the bootloader either.
I've tried now to sideload the .zip but it seems that even the supposed 1.1.0 full OTA zip available in the other post is older than my current ROM, so it can't be flashed like that. I'll have to wait for the next update.

Categories

Resources