Database Users

[help] Buying a bricked tf300

Hello guy,
I have the possiblity to buy a tf300 wich is bricked. And I would like to know if someone could tell me if it's fixable.
The guy says that he unlocked the bootloader, apparently it worked fine and the he flash a TWRP 2.6.3.0 then it went bad. He says the tablet is directly booting up into recovery (at least that's working) that TWRP says "Omb" whatever that means and that he doesn't see any files into recovery, only folders and subfolders (isn't supposed to be normal, I mean doesn't the recovery only display .zip files ??). He says volume down + power doesn't work, adb gives a " protocol failure" and fastboot is waiting for device (but I'm gessing it's normal since he can't boot into menu obviously fastboot is not working).
So what do you think is it fixable?
Thanks

the guy gave me 2 images of the recovery:
{
"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"
}

Apparently the password asked on the screenshots is here because the recovery can't mount the storage partitions. Clearly he flash the wrong recovery. He says that he can't get fastboot because he can't install driver (something I could figure out how to do ).
My last question is, will I get fastboot in this recovery, dispite the storage not mounting and the incompatibility?
if yes then I can do a "fastboot getvar all" to get bootloader version and flash the right recovery? What do you think??
thanks

ayziaa said:
Apparently the password asked on the screenshots is here because the recovery can't mount the storage partitions. Clearly he flash the wrong recovery. He says that he can't get fastboot because he can't install driver (something I could figure out how to do ).
My last question is, will I get fastboot in this recovery, dispite the storage not mounting and the incompatibility?
if yes then I can do a "fastboot getvar all" to get bootloader version and flash the right recovery? What do you think??
thanks
Click to expand...
Click to collapse
that has append to me couple of times( i think 3 -4 times actually) , if you are confident you can get fastboot and ADB working should be really easy to fix. but ull have to flash ASUS blob file then start over like if it was a new tablet

ayziaa said:
Apparently the password asked on the screenshots is here because the recovery can't mount the storage partitions. Clearly he flash the wrong recovery. He says that he can't get fastboot because he can't install driver (something I could figure out how to do ).
My last question is, will I get fastboot in this recovery, dispite the storage not mounting and the incompatibility?
if yes then I can do a "fastboot getvar all" to get bootloader version and flash the right recovery? What do you think??
thanks
Click to expand...
Click to collapse
Yeah I ran into that bug personally and I fixed is in less than 5 minutes with the right setup. Of course, it could be a different situation but there is the chance that it is easily fixable.

Sadly the guy allready sold it. Thank you guy for replying

help
Hi guys....
on my bad luck, looks like I did the same thing.... I had CMB Roms cmb4.4.2 with Philz CWM v6.0.4.5, as I did like this, I went to flash another rom. So, I put the TWRP 2.6 on sdcard with Cromi rom.... flash recovery, reboot and there it stock on recovery and state just like on pictures ...
I can go with ABD but not FASTBOOT... my sdcard is SYSTEM when I mount the system from twpr !!!!
can someone help me ?

srdjank said:
Hi guys....
on my bad luck, looks like I did the same thing.... I had CMB Roms cmb4.4.2 with Philz CWM v6.0.4.5, as I did like this, I went to flash another rom. So, I put the TWRP 2.6 on sdcard with Cromi rom.... flash recovery, reboot and there it stock on recovery and state just like on pictures ...
I can go with ABD but not FASTBOOT... my sdcard is SYSTEM when I mount the system from twpr !!!!
can someone help me ?
Click to expand...
Click to collapse
You put the wrong version of TWRP on your tablet probably? when you restart and it boots into TWRP, on the starting screen you should be able to use fastboot.
---------- Post added at 04:33 PM ---------- Previous post was at 04:31 PM ----------
When it happened to me, it was a bootloader and TWRP conflict: I flashed the jb version instead of the -42 Version. to fix it, I did fastboot reboot bootloader and then got back into android and flashed the correct one from Terminal Emulator. Or you could just flash it from there.

cmendonc2 said:
You put the wrong version of TWRP on your tablet probably? when you restart and it boots into TWRP, on the starting screen you should be able to use fastboot.
---------- Post added at 04:33 PM ---------- Previous post was at 04:31 PM ----------
When it happened to me, it was a bootloader and TWRP conflict: I flashed the jb version instead of the -42 Version. to fix it, I did fastboot reboot bootloader and then got back into android and flashed the correct one from Terminal Emulator. Or you could just flash it from there.
Click to expand...
Click to collapse
nope, I can't use it, if you meen on blue screen when twrp starts, when it boots is the same.... fastboot devices command and it just don't do anything, when twrp boots adb devices turn up : 0123456789ABCDEF recovery
I tryed meny things but I can get it to boot in bootloader with tree options....
when I type fastboot -i 0x0B05 flash c:\Android SDK\sdk\platform-tools\blob
just says <waiting for device> and stays that way.... tryed to reset tab with pin let it boot but nothing ...

srdjank said:
nope, I can't use it, if you meen on blue screen when twrp starts, when it boots is the same.... fastboot devices command and it just don't do anything, when twrp boots adb devices turn up : 0123456789ABCDEF recovery
I tryed meny things but I can get it to boot in bootloader with tree options....
when I type fastboot -i 0x0B05 flash c:\Android SDK\sdk\platform-tools\blob
just says <waiting for device> and stays that way.... tryed to reset tab with pin let it boot but nothing ...
Click to expand...
Click to collapse
What is your OS of your PC??

cmendonc2 said:
You put the wrong version of TWRP on your tablet probably? when you restart and it boots into TWRP, on the starting screen you should be able to use fastboot.
---------- Post added at 04:33 PM ---------- Previous post was at 04:31 PM ----------
When it happened to me, it was a bootloader and TWRP conflict: I flashed the jb version instead of the -42 Version. to fix it, I did fastboot reboot bootloader and then got back into android and flashed the correct one from Terminal Emulator. Or you could just flash it from there.
Click to expand...
Click to collapse
lj50036 said:
What is your OS of your PC??
Click to expand...
Click to collapse
HE's ALIVE ....
:fingers-crossed::fingers-crossed::fingers-crossed:
I''m on WIN7 64...... like I said I boot it up, all I needed is command : abd reboot-bootloader
that cat me in bootloader mode, with http://forum.xda-developers.com/showpost.php?p=44244313&nocache=1&z=9056634965818376
I boot it up on stock 4.2.1 JOP40D.ww_epad-10.6.1.8-20130225
sorry for trouble ...... thanks all for trying to help ....

OP2 stuck in bootloop on upgrading 3.0.2 .. even after trying tons of things

First of all i want to say thankyou to the xda community who help people like us and build rooting and other flashing softwares.
So, this is probably my first post on xda, first for sure when i'm stuck and asking for help
Background of the Problem:
I was on OS 2.1.2 rooted with twrp recovery. (was really happy with my phone)
MM 3.0.2 upgrade comes and i decide to upgrade my phone manually (since ota was disabled due to root)
All goes well in first try..(did a dirty flash) OP2 3.0.2 runs smoothly
However, i found out i had lost root and couldn't boot into recovery.
I ignored for a month when i decided it was too hard to go on without root now..
So i searched through a few forums, went into fastboot tried oem unlocking.. failed.. Stuck hard in the bootloop..
Searched for about 3hours and used the MSM tool to finally unlock bootloader.. but still stuck at bootloop and no luck with recovery.. I couldn't boot into my installed rom(3.0.2)
I flashed recovery from OOS 2.1.2 or 2.0.1 and booted into recovery and flashed 2.1.2 again..
So now, 2.1.2 runs fine on my phone
I have refered to these guides/files while trying to install 3.0.2 or trying to recover my phone
http://forum.xda-developers.com/onep...s-3-x-t3392826
https://www.androidfilehost.com/?w=f...f4a13afecc347f
https://www.androidfilehost.com/?w=f...9e2340a15d9033
https://forums.oneplus.net/threads/u...plus-2.347607/
http://forum.xda-developers.com/oneplus-2/general/zip-oxygenos-3-x-t3392826
PROBLEM:
Whenever i update my phone to 3.0.2, it stucks at the bootloop (showing oneplus logo and cmd showing it in fastboot mode)
i lose recovery and rom
i have tried flashing grarak recovery and hybrid recovery (both of which i believe are modded recovery for OOS MM)
In cmd, fastboot flash command completes without any problem but the phone doesnt boot to recovery and both give an error while giving the fastboot boot command
" downloading boot.img
OKAY
booting...
FAILED (remote: dtb not found)"
finished. "
Please suggest me something so that i can boot into 3.0.2 without bootloop problem.. 3.0.2 runs really smooth..
and additionally if possible, i would like to root but thats secondary.
Thankyou guys in advance. Please help a brother out

Sahaj4 said:
First of all i want to say thankyou to the xda community who help people like us and build rooting and other flashing softwares.
So, this is probably my first post on xda, first for sure when i'm stuck and asking for help
Background of the Problem:
I was on OS 2.1.2 rooted with twrp recovery. (was really happy with my phone)
MM 3.0.2 upgrade comes and i decide to upgrade my phone manually (since ota was disabled due to root)
All goes well in first try..(did a dirty flash) OP2 3.0.2 runs smoothly
However, i found out i had lost root and couldn't boot into recovery.
I ignored for a month when i decided it was too hard to go on without root now..
So i searched through a few forums, went into fastboot tried oem unlocking.. failed.. Stuck hard in the bootloop..
Searched for about 3hours and used the MSM tool to finally unlock bootloader.. but still stuck at bootloop and no luck with recovery.. I couldn't boot into my installed rom(3.0.2)
I flashed recovery from OOS 2.1.2 or 2.0.1 and booted into recovery and flashed 2.1.2 again..
So now, 2.1.2 runs fine on my phone
I have refered to these guides/files while trying to install 3.0.2 or trying to recover my phone
http://forum.xda-developers.com/onep...s-3-x-t3392826
https://www.androidfilehost.com/?w=f...f4a13afecc347f
https://www.androidfilehost.com/?w=f...9e2340a15d9033
https://forums.oneplus.net/threads/u...plus-2.347607/
http://forum.xda-developers.com/oneplus-2/general/zip-oxygenos-3-x-t3392826
PROBLEM:
Whenever i update my phone to 3.0.2, it stucks at the bootloop (showing oneplus logo and cmd showing it in fastboot mode)
i lose recovery and rom
i have tried flashing grarak recovery and hybrid recovery (both of which i believe are modded recovery for OOS MM)
In cmd, fastboot flash command completes without any problem but the phone doesnt boot to recovery and both give an error while giving the fastboot boot command
" downloading boot.img
OKAY
booting...
FAILED (remote: dtb not found)"
finished. "
Please suggest me something so that i can boot into 3.0.2 without bootloop problem.. 3.0.2 runs really smooth..
and additionally if possible, i would like to root but thats secondary.
Thankyou guys in advance. Please help a brother out
Click to expand...
Click to collapse
Follow this step one by one ..
1. Flash this recovery via firstboot
https://drive.google.com/file/d/0B0OiN2evbEPuNk5KejhvLWsyeDg/view?usp=drivesdk
2. Now boot into recovery and flash this zip firmware .
https://drive.google.com/file/d/0B0OiN2evbEPucnBkUGZIdlZCSnM/view?usp=drivesdk
3. Now boot into new recovery and flash oxygen os 3.x.x .
That's it.
4. If camera or other sensor not work flash this persist.img file via firstboot.
https://drive.google.com/file/d/0B0OiN2evbEPueVNEQTdUSHJYTHM/view?usp=drivesdk

Jyoti_re said:
Follow this step one by one ..
1. Flash this recovery via firstboot
https://drive.google.com/file/d/0B0OiN2evbEPuNk5KejhvLWsyeDg/view?usp=drivesdk
2. Now boot into recovery and flash this zip firmware .
https://drive.google.com/file/d/0B0OiN2evbEPucnBkUGZIdlZCSnM/view?usp=drivesdk
3. Now boot into new recovery and flash oxygen os 3.x.x .
That's it.
4. If camera or other sensor not work flash this persist.img file via firstboot.
https://drive.google.com/file/d/0B0OiN2evbEPueVNEQTdUSHJYTHM/view?usp=drivesdk
Click to expand...
Click to collapse
Heyy.. Thanks a lot Jyoti_re! It worked out perfectly..
I have done till step 3.. The phone booted into 3.0.2
The sensors are not working. I will flash the presist.img as you said in step 4
However, i have encountered a problem. My OP2 is a 64 GB version. But now the internal storage shows 7gb free out of 9.66 GB.. Earlier it used to show 54GB instead of 9.66..
What should i do?
Thanks again

Yes u must have to flash persist.img via firstboot mode by typing [ fastboot flash persist ] for sensor correctly working.
Install es file explorar from play store and check which folder taking More space
don't forget to press thanks if I helped u.

Thanks a lot Jyoti! /
Yeah i got it.. Flashed the persist img.
i searched through the forums.. somehow my device got the 16gb version img.. i dont know how..
i had to flash userdata64G.img as well
Now it all works perfectly.. sensors are working.. data storage is back at 54gb..
Thanks a lot! I had been stuck on this bootloop since 3 days..
and i pressed the thanks button.. i will press it 100 times over if possible Thanks again! Cheers!

Just to confirm.. Can i flash supersu via recovery now to get root? i hope it wont lead me to bootloops.. If there is some specific supersu file to flash for OOS 3.0.2 please guide me to it.. Thanks!

Sahaj4 said:
Just to confirm.. Can i flash supersu via recovery now to get root? i hope it wont lead me to bootloops.. If there is some specific supersu file to flash for OOS 3.0.2 please guide me to it.. Thanks!
Click to expand...
Click to collapse
Flash this SuperSU
https://drive.google.com/file/d/0B0OiN2evbEPuZk1KSk1hYUpEazA/view?usp=drivesdk
don't forget to press thanks if I helped u.

OP2 stuck in bootloop on upgrading from 2.0.2 to 3.0.2
Hi guys and thanks to all xda developers community for helping us. I'm trying to root my op2 via fastboot,using the comand fastboot oem unlock,but always having this message: <remote oem unlock is disabled>. And when i try to use volume down+power to get in recovery mode the op2 vibrate and flashes the screen and do nothing. I'm not having access to do anything with the op2. Please help...

ciroportugues said:
Hi guys and thanks to all xda developers community for helping us. I'm trying to root my op2 via fastboot,using the comand fastboot oem unlock,but always having this message: <remote oem unlock is disabled>. And when i try to use volume down+power to get in recovery mode the op2 vibrate and flashes the screen and do nothing. I'm not having access to do anything with the op2. Please help...
Click to expand...
Click to collapse
Have u enabled OEM unlocking in developer option ??

No i forgot to enable...

No i forgot to enable... What can i do now?
---------- Post added at 06:44 AM ---------- Previous post was at 06:39 AM ----------
Jyoti_re said:
Have u enabled OEM unlocking in developer option ??
Click to expand...
Click to collapse
No iforgot to enable...
What can i do now?

ciroportugues said:
No i forgot to enable... What can i do now?
---------- Post added at 06:44 AM ---------- Previous post was at 06:39 AM ----------
No iforgot to enable...
What can i do now?
Click to expand...
Click to collapse
Go thru "METHOD 1" of this post and fill free to contact if u face any problem.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/

Jyoti_re said:
Go thru "METHOD 1" of this post and fill free to contact if u face any problem.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Click to expand...
Click to collapse
Hi. I tried to do every steps in method 1,but when i try to enter to recovery mode my op2 vibrate and flash the screen till i stop pressing the power button,and never get into recovery mode.

ciroportugues said:
Hi. I tried to do every steps in method 1,but when i try to enter to recovery mode my op2 vibrate and flash the screen till i stop pressing the power button,and never get into recovery mode.
Click to expand...
Click to collapse
After use the recovery tool the op2 restarts and stuck into powered by android nothing more happens.

ciroportugues said:
After use the recovery tool the op2 restarts and stuck into powered by android nothing more happens.
Click to expand...
Click to collapse
What does the Device Manager show when you connect your phone? By what name is it identified?

Thanks for reply. When i put press volume+and- shows qualcomm hs-usb qdloader9008 (com29),and when i put into fastboot shows android bootloader interface,and when stucks into start shows the same(android bootloader interface).
---------- Post added at 10:06 PM ---------- Previous post was at 09:37 PM ----------
Sahaj4 said:
What does the Device Manager show when you connect your phone? By what name is it identified?
Click to expand...
Click to collapse
Thanks for reply. When i put press volume+and- shows qualcomm hs-usb qdloader9008 (com29),and when i put into fastboot shows android bootloader interface,and when stucks into start shows the same(android bootloader interface).

When you are in fastboot mode..
Try giving the command
"fastboot continue"
or
"fastboot reboot-bootloader"
"fastboot continue"
(without quotes) if your system files are not corrupt, it will boot you into your rom.. and then enable oem unlocking from settings

Tried this commands and the system reboots and stucks on the screen powered by android.
---------- Post added at 12:27 AM ---------- Previous post was at 12:25 AM ----------
Sahaj4 said:
When you are in fastboot mode..
Try giving the command
"fastboot continue"
or
"fastboot reboot-bootloader"
"fastboot continue"
(without quotes) if your system files are not corrupt, it will boot you into your rom.. and then enable oem unlocking from settings
Click to expand...
Click to collapse
Tried this commands but the sistem reboots and stucka on powered by android

ciroportugues said:
Tried this commands and the system reboots and stucks on the screen powered by android.
---------- Post added at 12:27 AM ---------- Previous post was at 12:25 AM ----------
Tried this commands but the sistem reboots and stucks on powered by android
Click to expand...
Click to collapse
Hi. want to know if you anymore command to help me? thanks for help

ciroportugues said:
Hi. want to know if you anymore command to help me? thanks for help
Click to expand...
Click to collapse
I don't know much.. only as much as i have tried..
try running the command
fastboot oem device-info
if your device is unlocked, you are lucky! then there are many options
but if your device is locked.. then as far as i know, msm tool is your only saviour
try using this guide to unbrick your phone
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/

P8lite has no operating sys. CAN ANYONE HELLP ?

I've P8lite .. Rom be deleted by mistake while trying install SU
Now, phone has no operating system, Trying a lot to install many of
Roms by twrp 3.0.2-0 ( C185B120, C185B525 And C185B560 ) more's the
pity to no end with message "Skipping MD5 check: no MD5 file found"
and "Could not find 'META-INF/com/google/android/update-binary' in the
zip file". "Error installing zip file". "Failed".
Thanks in advance
ALE-L21 UAE

hosamzaiher said:
I've P8lite .. Rom be deleted by mistake while trying install SU
Now, phone has no operating system, Trying a lot to install many of
Roms by twrp 3.0.2-0 ( C185B120, C185B525 And C185B560 ) more's the
pity to no end with message "Skipping MD5 check: no MD5 file found"
and "Could not find 'META-INF/com/google/android/update-binary' in the
zip file". "Error installing zip file". "Failed".
Thanks in advance
ALE-L21 UAE
Click to expand...
Click to collapse
Which rom are you trying to flash?

Suleiman01 said:
Which rom are you trying to flash?
Click to expand...
Click to collapse
thanx 4 reply .. i don't know which the suitable one 4 my phone, i tried to flash C185B120, C185B525 And C185B560

hosamzaiher said:
thanx 4 reply .. i don't know which the suitable one 4 my phone, i tried to flash C185B120, C185B525 And C185B560
Click to expand...
Click to collapse
Isn't it in Update.app format? This format is not supported by TWRP. Install original recovery first then update your phone.

Suleiman01 said:
Isn't it in Update.app format? This format is not supported by TWRP. Install original recovery first then update your phone.
Click to expand...
Click to collapse
I said that 2 my self " amazed " ! .. could u please tell me How ?
linking me to this recovery

hosamzaiher said:
I said that 2 my self " amazed " ! .. could u please tell me How ?
linking me to this recovery
Click to expand...
Click to collapse
You can extract original recovery from official firmware update.app using Huawei update extractor.
---------- Post added at 09:00 AM ---------- Previous post was at 08:59 AM ----------
Suleiman01 said:
You can extract original recovery from official firmware update.app using Huawei update extractor.
Click to expand...
Click to collapse
Link
https://goo.gl/aSMU9M

Suleiman01 said:
You can extract original recovery from official firmware update.app using Huawei update extractor.
---------- Post added at 09:00 AM ---------- Previous post was at 08:59 AM ----------
Link
https://goo.gl/aSMU9M
Click to expand...
Click to collapse
when i've never succeed flashing with TWRP, i converted into CWM
it stops to flash any thing more .. ZIP or IMG files with error message "couldn't un mount sdcard" !

hosamzaiher said:
when i've never succeed flashing with TWRP, i converted into CWM
it stops to flash any thing more .. ZIP or IMG files with error message "couldn't un mount sdcard" !
Click to expand...
Click to collapse
What are you talking about? I didn't say to flash cwm ( clockwork recovery) or twrp (team win recovery project).
Just install the Huawei update extractor on pc.
Extract original recovery from official firmware
Connect your phone to pc and go in fastboot mode
Open minimal adb on pc and type
Fastboot flash recovery recovery.img
Reboot your phone.
Done

Suleiman01 said:
What are you talking about? I didn't say to flash cwm ( clockwork recovery) or twrp (team win recovery project).
Just install the Huawei update extractor on pc.
Extract original recovery from official firmware
Connect your phone to pc and go in fastboot mode
Open minimal adb on pc and type
Fastboot flash recovery recovery.img
Reboot your phone.
Done
Click to expand...
Click to collapse
sorry dear
if i open minimal adb on pc and typ " adb devices " i've nothing till i back to check option " Apply from ADB " from cyanogen recovery then any command order followed by error message " phone closed " !

{
"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"
}
hosamzaiher said:
sorry dear
if i open minimal adb on pc and typ " adb devices " i've nothing till i back to check option " Apply from ADB " from cyanogen recovery then any command order followed by error message " phone closed " !
Click to expand...
Click to collapse

Suleiman01 said:
What are you talking about? I didn't say to flash cwm ( clockwork recovery) or twrp (team win recovery project).
Just install the Huawei update extractor on pc.
Extract original recovery from official firmware
Connect your phone to pc and go in fastboot mode
Open minimal adb on pc and type
Fastboot flash recovery recovery.img
Reboot your phone.
Done
Click to expand...
Click to collapse

https://s18.postimg.org/ic04061op/image.png

Use fastboot command when in fastboot mode, not adb. try fastboot devices

hosamzaiher said:
sorry dear
if i open minimal adb on pc and typ " adb devices " i've nothing till i back to check option " Apply from ADB " from cyanogen recovery then any command order followed by error message " phone closed " !
Click to expand...
Click to collapse
No. Type fastboot devices. Adb is used when phone is powerd on and usb debugging is enabled.
Go in fastboot mode by pressing power button and volume down key. Then attach it to pc and do the steps stated in previous post.

Suleiman01 said:
No. Type fastboot devices. Adb is used when phone is powerd on and usb debugging is enabled.
Go in fastboot mode by pressing power button and volume down key. Then attach it to pc and do the steps stated in previous post.
Click to expand...
Click to collapse
thanx brother, i back TWRP 3.0.2-0 and installed http://huaweip8lite.blogspot.com.eg/2016/07/custom-romtwrpemui-40p8-lite-ale.html?view=sidebar
but the screen stuck on logo

hosamzaiher said:
thanx brother, i back TWRP 3.0.2-0 and installed http://huaweip8lite.blogspot.com.eg/2016/07/custom-romtwrpemui-40p8-lite-ale.html?view=sidebar
but the screen stuck on logo
Click to expand...
Click to collapse
Maybe try flashing official firmware.

Suleiman01 said:
Maybe try flashing official firmware.
Click to expand...
Click to collapse
How to determined the suitable official firmware ?

hosamzaiher said:
How to determined the suitable official firmware ?
Click to expand...
Click to collapse
Which was your last firmware? Flash that firmware's recovery. Then using that recovery update your phone.
---------- Post added at 07:23 PM ---------- Previous post was at 07:23 PM ----------
Suleiman01 said:
Which was your last firmware? Flash that firmware's recovery. Then using that recovery update your phone.
Click to expand...
Click to collapse
Try flashing B120 recovery.

Suleiman01 said:
Which was your last firmware? Flash that firmware's recovery. Then using that recovery update your phone.
---------- Post added at 07:23 PM ---------- Previous post was at 07:23 PM ----------
Try flashing B120 recovery.
Click to expand...
Click to collapse
it seems to be Solved :laugh:
but with a bit trouble ..
first: i used HuaweiUpdateExtractor to extract all files inside, then, did 3 orders on fastboot . . ( flash boot.img - flash recovery.img - flash sys.img )
phone booted on 3.1 Emul with alot stopped functions ( wifi, sim card and so on) finally made a local update using app file stored in SD card for "B560" .. phone started correctly but there was a problem with WIFI wasn't stable .. connect and disconnect !

hosamzaiher said:
it seems to be Solved :laugh:
but with a bit trouble ..
first: i used HuaweiUpdateExtractor to extract all files inside, then, did 3 orders on fastboot . . ( flash boot.img - flash recovery.img - flash sys.img )
phone booted on 3.1 Emul with alot stopped functions ( wifi, sim card and so on) finally made a local update using app file stored in SD card for "B560" .. phone started correctly but there was a problem with WIFI wasn't stable .. connect and disconnect !
Click to expand...
Click to collapse
Update your phone to marshmallow. This might fix wifi issue. By the don't forget to hit thanks button :good: if your problem is solved.

How To Recover from Hard Bricked ZUK Z2 (PLUS)

Hey guys... Well I was one of the flashaholics who went ahead and tried to flash some custom roms and ended up bricking my phone which was completely bricked (NOT even FASTBOOT!) and after loads of googling I was able to get my phone working again.
WARNING
Your device is already bricked and if it goes worse than I am not responsible for it. Do at your own risk.
Requirements:
1. Windows PC with driver signature disabled.
(i). Press and hold the Shift key on your keyboard and click the Restart button.
(ii). Choose Troubleshoot > Advanced options > Startup Settings and click the Restart button.
(iii). When your computer restarts you’ll see a list of options. Press F7 (the number may change on your pc) on your keyboard to select Disable driver signature enforcement.
(iv).Your computer will now restart and you’ll be able to install unsigned drivers.
2. Drivers
(i). ZUK USB driver
(ii). Qualcomm_QHSUSB_driver
(iii). ADB & Fastboot drivers
(iv). QPST
3. QPST Rom
(i). INDIAN ROM
STEPS:
1. Install the ZUK USB driver downloaded from above.
2. Install qpst downloaded from above.
FOLLOW THE ON SCREEN INSTRUCTIONS. IF IT ASK TO DOWNLOAD C++ REDISTRIBUTABLE THAN DO IT.
3. Extract the ROM on the root of the C drive.
4. Restart your PC and open QFILClick
(i) Select "Flat Build" and "Browse". Now navigate to the extracted ROM/Firmware, and select prog_emmc_firehose_8996_ddr.elf.
(ii) Select the "load xml" button. This will appear a new explorer. One of them will be needed to navigate to the file rawprogram-flash0.xml the second one will ask for patch0.xml .
(iii) Turn your phone off. Now press and hold the volume + button, while pressing the power button for 0.5 seconds and plug in the USB cable in the same moment. If it was successful your phone should appear at QPST/QFIL and you are able to press the download button. Press the download process and wait to finish.
if it fails, In QFIL Change
"Device Type" to eMMC
"Validation Mode" to 0-No validation
"Reset after Download" no needed to tick (optional)
If your phone is not detected in the QFIL then,
Close QFIL
Right click on my computer and select MANAGE, then select Device Manager
See if your device is connected as Diagnostic Port 900E
If it is shown as “QHSUSB_BULK” under Other Device
1. Right-click on QHSUSB_BULK and choose “Update Driver Software“
2. Now click on the Browse button and locate the extracted Qualcomm QDLoader drivers.
3. The installation process shall take place immediately and a system notification will appear. Just choose “Install this driver software anyway“.
4.Click the Close button and check back at Device Manager window. You will now see “Qualcomm HS-USB QDLoader 9008 (COM10)” under Ports (COM & LPT) section.
Now start QFIL and press download.
DONE!!
REFERENCES: https://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-z2131-only.104/
DON'T QUOTE THE WHOLE OP

will this guide work with QPST 2.7.496?
I want to revert to stock zui

i just successfully hard bricked my phone. i flash 2.5 rom with baseband from 2.3.042 . now i can only see the boot up zuk logo and screen turn black with notification lights on.
unable to switch it off at all.
come back later and report

in the port its showing 900E inead of 9008 what should i do?

Dragonlord07 said:
its showing 900E
Click to expand...
Click to collapse
Try this thread: https://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/

device isn't showing up in device manager...what should I do?

first of all, thank you for the clear guide since the one on zukfans,eu was taken down. I am recieving an error :
Download Fail:Saha Fail:QSaharaServer Failrocess fail
the two discrepancies from the guide are that my phone shows up as (COM3) and not (COM10), and the rawprogram file is rawprogram0.xml
any help or guidance would be appreciated
edit: nvrmind, i just kept trying plugging in during the power button + volume down button boot and it finally let me download without error

locolyric said:
i just successfully hard bricked my phone. i flash 2.5 rom with baseband from 2.3.042 . now i can only see the boot up zuk logo and screen turn black with notification lights on.
unable to switch it off at all.
come back later and report
Click to expand...
Click to collapse
the issue is with me, did find a solution for this
---------- Post added at 07:18 AM ---------- Previous post was at 07:06 AM ----------
it says failed to load edl
what to do
---------- Post added at 07:36 AM ---------- Previous post was at 07:18 AM ----------
locolyric said:
i just successfully hard bricked my phone. i flash 2.5 rom with baseband from 2.3.042 . now i can only see the boot up zuk logo and screen turn black with notification lights on.
unable to switch it off at all.
come back later and report
Click to expand...
Click to collapse
bro i have solved it
steps i have followed
1)press volume up+volume down+power for 30 seconds (phone will show zuk logo and switches off, donot bother about that)
2)now remove the finger from power button(keep holding volume up and power buttons)
3)there u go u will see the fastboot mode
******* I have followed those steps and my phone got booted**********
error is because of locked bootloader
i have unlocked it again and using stock rom now

Dead
A make all point ... with success, but ... After Qfil end works, my zuk don't want switch on. PC doesn't see it. Please help

help me
sairam96 said:
the issue is with me, did find a solution for this
---------- Post added at 07:18 AM ---------- Previous post was at 07:06 AM ----------
it says failed to load edl
what to do
---------- Post added at 07:36 AM ---------- Previous post was at 07:18 AM ----------
bro i have solved it
steps i have followed
1)press volume up+volume down+power for 30 seconds (phone will show zuk logo and switches off, donot bother about that)
2)now remove the finger from power button(keep holding volume up and power buttons)
3)there u go u will see the fastboot mode
******* I have followed those steps and my phone got booted**********
error is because of locked bootloader
i have unlocked it again and using stock rom now
Click to expand...
Click to collapse
same here.i was on custom rom and insatlled zui2 2.0 and my phone isnt starting. only zuk symbol coes and goes.

I'm having trouble, my zuk z2 is stuck with relocked bootloader and custom recovery
I can boot to fastboot mode, reboot in EDL mode and I've had many tries to flash a new stock ROM but none progress so far
And I get Firehose errors when trying to flash a QFIL stock rom
It means my phone is hard bricked but is there any solution to that or I'm bound to buy another cellphone ?
BTW my sister has the same phone as me, is there any way I can use her phone as a backup ?
Much appreciated for the tips and help

fraucred said:
I'm having trouble, my zuk z2 is stuck with relocked bootloader and custom recovery
I can boot to fastboot mode, reboot in EDL mode and I've had many tries to flash a new stock ROM but none progress so far
And I get Firehose errors when trying to flash a QFIL stock rom
It means my phone is hard bricked but is there any solution to that or I'm bound to buy another cellphone ?
BTW my sister has the same phone as me, is there any way I can use her phone as a backup ?
Much appreciated for the tips and help
Click to expand...
Click to collapse
U must have to unlock bootloader
Then install twrp recovery
Now connect the phone to the computer
Now send any of the custom roms to phone
Now flash the custom rom
Boot into it
Then u can goto stock rom by rrbooting into edl
---------- Post added at 02:31 AM ---------- Previous post was at 02:26 AM ----------
NISHUHACKER said:
same here.i was on custom rom and insatlled zui2 2.0 and my phone isnt starting. only zuk symbol coes and goes.
Click to expand...
Click to collapse
Boot into recovery n flash other custom roms n after booting u can goto stock rom , if u dont know how to just msg here

How should I proceed to unlock the bootloader once again ? I tried the fastboot mode but I've seen failures until now
I had bricked my phone when I still had access to TWRP recovery, probably with a stock - modded rom (the indian one I believe) and after that everything went down.
Thought locking the bootloader would allow me to get back to another stock rom but now I can only get to the phone through fastboot mode or 9008 COM port
sairam96 said:
U must have to unlock bootloader
Then install twrp recovery
Now connect the phone to the computer
Now send any of the custom roms to phone
Now flash the custom rom
Boot into it
Then u can goto stock rom by rrbooting into edl
---------- Post added at 02:31 AM ---------- Previous post was at 02:26 AM ----------
Boot into recovery n flash other custom roms n after booting u can goto stock rom , if u dont know how to just msg here
Click to expand...
Click to collapse

fraucred said:
How should I proceed to unlock the bootloader once again ? I tried the fastboot mode but I've seen failures until now
I had bricked my phone when I still had access to TWRP recovery, probably with a stock - modded rom (the indian one I believe) and after that everything went down.
Thought locking the bootloader would allow me to get back to another stock rom but now I can only get to the phone through fastboot mode or 9008 COM port
Click to expand...
Click to collapse
Downlad bootunlock.img from zuk official site
Then download minimal adb drivers
Move the download img file to minimal adb directory
Then follow the following commands
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
fastboot -i 0x2b4c oem unlock-go

sairam96 said:
Downlad bootunlock.img from zuk official site
Then download minimal adb drivers
Move the download img file to minimal adb directory
Then follow the following commands
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
fastboot -i 0x2b4c oem unlock-go
Click to expand...
Click to collapse
Which is what I try to do but no success
{
"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"
}
Here is my device bootloader status
PS C:\Users\xxxxx\adb> .\fastboot.exe -i 0x2b4c oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device relocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.065s]
finished. total time: 0.066s
PS C:\Users\xxxxxx\adb>

fraucred said:
Which is what I try to do but no success
Here is my device bootloader status
PS C:\Users\xxxxx\adb> .\fastboot.exe -i 0x2b4c oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device relocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.065s]
finished. total time: 0.066s
PS C:\Users\xxxxxx\adb>
Click to expand...
Click to collapse
Try sideload process

sairam96 said:
Try sideload process
Click to expand...
Click to collapse
How do I do that ?

fraucred said:
How do I do that ?
Click to expand...
Click to collapse
Go to twrp
Advanced
Adb sideload and connect it to the pc
Now dowload update.zip from zuk development or xda development
And copy the downloaded.zip to adb directory
Now type the command adb sideload update.zip

It seems I need to use adb but I have the adb drivers installed, my device in fastboot mode is not listed when I use the "adb devices" command
I cannot access to the USB Debugging option either because my phone is bricked
---------- Post added at 02:42 PM ---------- Previous post was at 02:41 PM ----------
sairam96 said:
Go to twrp
Advanced
Adb sideload and connect it to the pc
Now dowload update.zip from zuk development or xda development
And copy the downloaded.zip to adb directory
Now type the command adb sideload update.zip
Click to expand...
Click to collapse
I don't have access to TWRP either, because I locked my bootloader as I explained earlier
---------- Post added at 02:43 PM ---------- Previous post was at 02:42 PM ----------
sairam96 said:
Go to twrp
Advanced
Adb sideload and connect it to the pc
Now dowload update.zip from zuk development or xda development
And copy the downloaded.zip to adb directory
Now type the command adb sideload update.zip
Click to expand...
Click to collapse
I don't have access to TWRP either, because I locked my bootloader as I explained earlier

I figured it out, installed a chinese stock rom which made my bootloader set to default
After that I unlocked it, installed TWRP and I successfully installed Lineage OS
My Zuk Z2 looks completely different now

my phone was bricked , i flashed zui 2.0 , 2.3 and 2.5 with QFIL but steel bricked so i unlocked my bootloader again and flashed TWRP but i can't even enter recovery mode i got black screen with white LED :crying::crying:

Unable to boot into TWRP recovey

Hi ya'll. I have recently bought a Xiaomi Redmi note 7, and I wish to install a different ROM (Resurrection Remix). Though in order to do so I must of course flash the TWRP recovery. The flash itself seems to be successful as can be seen in the log I attached, but when I try to reboot into recovery it just enters the old default recovery of the device.
I have looked up in the internet and found some possible ways to solve the issue, which all failed. For example trying to enter with pressing power+volume up+volume down, just power+volume up or any combination possible with those buttons. Also tried to use the command
Code:
adb reboot recovery
which only works when the device is turned on and in system mode.
Tried entering with pressing power+volume up+volume down, just power+volume up or any combination possible with those buttons. I have also tried using the command
Code:
fastboot flash boot recovery.img
right after flashing the recovery, and then though to use the TWRP commandlines somehow, but i didn't really knew how actually.
All these trials failed as been said.
The most probable cause I have found for this problem was in a nother forum (can't enter the link for some reason...) stating that when I reboot into the device normally into the system, it automatically installs the old recovery mode again, over the TWRP recovery, and so I must try and enter the TWRP recovery immediately after I flashed it, before I get to reboot into system. But the thing is that when I try to do so, pressing any button combination that is supposed to get me into recovery, just boots the device into bootloader again. Any other combination just reboots into system. So it is possible to get into recovery only when I turn of the device completely, and then try and enter reboot. Though in order to turn it of I must reboot into system first.
So that's my story guys, really hope someone can help me cause the MIUI ROM is just horrible.
Thanks and have a nice one
The ADB log of the flash:
{
"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"
}

Not fastboot reboot.
Flash ur recovery and unplug ur USB cable and boot by pressing volume+ and power

joke19 said:
Not fastboot reboot.
Flash ur recovery and unplug ur USB cable and boot by pressing volume+ and power
Click to expand...
Click to collapse
Still doesn't work... just goes into fastboot again...

semperfi0510 said:
Still doesn't work... just goes into fastboot again...
Click to expand...
Click to collapse
fastboot reboot recovery
Or was it adb reboot recovery?
without installation
fastboot boot recovery.img
Helpful?

joke19 said:
fastboot reboot recovery
Or was it adb reboot recovery?
without installation
fastboot boot recovery.img
Helpful?
Click to expand...
Click to collapse
Well I'm not sure if I understood what you meant, but this is what I tried
Again with no success...
Using the "boot" command didn't change anything visual in the device. Also the command is "adb reboot recovery" and not "fastboot reboot recovery" as you can see in the log.
Still thank you very much for your attempts to help

And fastboot boot recovery.img and the flash the recovery.zip don't work?
Normally ur phone boot the recovery.img without flashing...
Which recovery?
I flashed orangefox

joke19 said:
And fastboot boot recovery.img and the flash the recovery.zip don't work?
Normally ur phone boot the recovery.img without flashing...
Which recovery?
I flashed orangefox
Click to expand...
Click to collapse
I am note sure what is orangefox, but it seems that I still need to get into the TWRP recovery mode in order to install it.
If you mean to ask which version of TWRP I am using, then I tried a few different versions, including the latest.
As for using the boot first and then flashing the recovery (I guess you meant the "recovery.img" file) that too didn't work, and still goes into fastboot instead of recovery.
But now actually when I tried using the latest TWRP version, and then the "fastboot boot recovery.img" it finally gave me some failure message, though only after I flashed the recovery. This you can see in the attached log.
Thank you very much.

Yup and now I'm stuck in fastboot loop...

Violet? We're here in lavender forum

semperfi0510 said:
I am note sure what is orangefox, but it seems that I still need to get into the TWRP recovery mode in order to install it.
If you mean to ask which version of TWRP I am using, then I tried a few different versions, including the latest.
As for using the boot first and then flashing the recovery (I guess you meant the "recovery.img" file) that too didn't work, and still goes into fastboot instead of recovery.
But now actually when I tried using the latest TWRP version, and then the "fastboot boot recovery.img" it finally gave me some failure message, though only after I flashed the recovery. This you can see in the attached log.
Thank you very much.
Click to expand...
Click to collapse
Note 7 Pro is Violet and lavender is note 7!
---------- Post added at 09:13 PM ---------- Previous post was at 09:10 PM ----------
https://forum.xda-developers.com/re.../official-orangefox-recovery-project-t3941822
I'm a big fan :victory:

Yes guys the problem with this specific TWRP version was that it was for violet, though the original problem was still with a lavender version (yes my device is a lavender).
Though I managed to solve the problem eventually, even though I'm not really sure how. I think it is because I flashed a different "boot.img" file.
Since I accidentally used "fastboot flash boot recovery.img" instead of "fastboot boot recovery.img", I erased the device "boot into system" (I think so), then I flashed an original "boot.img" taken from the MIUI stock ROM using "fastboot flash boot boot.img". I'm not sure why, but after that the original TWRP I used finally stuck, and I could get into the TWRP recovery mode normally (using power+volume up).
My opinion is that the original "boot.img" file I had, somehow interrupted flash the TWRP, but IDK.
Anyway thanks very much for the help!!! Have a nice one.

semperfi0510 said:
Since I accidentally used "fastboot flash boot recovery.img" instead of "fastboot boot recovery.img", I erased the device "boot into system" (I think so), then I flashed an original "boot.img" taken from the MIUI stock ROM using "fastboot flash boot boot.img".
Click to expand...
Click to collapse
I have the exact same issue with violet. I am stuck in an infinite fastboot loop. Can you remember the order of the commands?
fastboot flash recovery twrp.img
fastboot format userdata
fastboot flash boot boot.img
then when I press POWER+VOLUME UP it takes me back into the damn fastboot. Damn Chinese PoS

Your devices are lavender here recovey for them https://androidfilehost.com/?fid=4349826312261697967
It will boot from the first time.

I'm having same issue with Tecno camon 12, any help will be appreciated

Jokamp said:
I'm having same issue with Tecno camon 12, any help will be appreciated
Click to expand...
Click to collapse
Don't reboot after flashing the recovery in fastboot. Hold the recovery button on your phone

I've solved this in this way:
1. Boot to Fastboot
2. Flash the TWRP "fastboot flash recovery twrp.img"
3. Boot to TWRP through ".img" file "fastboot boot twrp.img"
4. In TWRP interface selected "Reboot -> Recovery"

damn

I have the same problem I'm using a pine (Redmi 7a) phone and god damn that make me angry a friend some how I think he wanned to change rom and it bricked it I mean the firmware is still there but the phone doesn't have ROM neither not a custom recovery all is FASTBOOT the recovery and the bootloader is FASTBOOT and so I tried to flash TWRP the CMD says all is ok flashed and its not ****ING boot to TWRP it boots to FASTBOOT again, any idea how to fix that?

Hello.
I need help, please.
I have a Redmi Note 7 and I tried to install android 13 on it using TWRP, however I made a mistake and using TWRP I ended up formatting the entire smpartphone. I can no longer use Mi-Recovery 3.0 or enter TWRP, because when I click volume up and power nothing happens and the cell phone just starts, because I managed to install its original android using Miflash.
How can I restore or install recovery mode with mi-recovery 3.0 and thus be able to install the newest versions of android?
I also wanted to know if I can install android 13 or others that were not official for my device without TWRP, mi-recovery mode or another that depends on the commands described above, which are not working.
Thanks for the help.