Hard Brick/soft Brick ? Help! - Lenovo Zuk Z2 Pro Questions & Answers

Hi @All
At First sorry für my Bad Englisch
My Z2 pro Boot automatikli in the (i Thing) Fastboot
I Thing Something goes wrong when i was updating twrp
Aniway.
When i Push some buton IT Reboot and goes to the fastboot and dosnt Boot to the system aniway whitch Menu i click.
In cmd have i Something Whit Port 5037?
Can me someone Help? PLZ.

owczarek1987 said:
In cmd have i Something Whit Port 5037?
Click to expand...
Click to collapse
Yes, that's normal. It just says on which port ("door") adb is listening to. Don't worry about that, that's totally fine.
owczarek1987 said:
My Z2 pro Boot automatikli in the (i Thing) Fastboot
Click to expand...
Click to collapse
You think it's fastboot?
Try this and you'll know:
Code:
fastboot devices
If the output is empty, your device isn't being recognized.
owczarek1987 said:
When i Push some buton IT Reboot and goes to the fastboot and dosnt Boot to the system aniway whitch Menu i click.
Click to expand...
Click to collapse
Which button did you press?
Did you try a force reboot using your hard keys? Try one of the following:
Vol.up+power
Vol.down+power
1 should boot into recovery, 2 into fastboot. Can you tell us what happens if you try these buttons?
owczarek1987 said:
I Thing Something goes wrong when i was updating twrp
Click to expand...
Click to collapse
Well, if so you should try to reflash your boot.img (recovery.img if that applies to your device). If you have an update of your partitions, just reflash this update.
Else you have to find your (stock) rom and reflash it.
Besides: If you didn't do a backup, you maybe want to do it in the future. Since I know what it means to search very long for OS'/recoveries for a device, I really want to recommend you to backup your partitions. Always. And better each one, not only those you wan't to modify.

Hi user699
Thx for the fast anwere!
Yes IT IS fastboot Mode but nothing works,
The zuk is Off for example i Push the Power butten (only) or the vol+ AND Power or vol- and Power and IT Boot in the Fastboot (the picture what i was uploading)
I can choose restart bootloader, Recovery Mode,Power Off and Boot to FFBM
No matter what i choose IT Boot to the fastboot again and in cmd IT no responds
(I Think) when in was tipping ADB devices Ther only stand "LIST OF DEVICES ATTACHED"
i remember that there must some With Numbers stand? (Devices serial of Something)
Stay healthy

owczarek1987 said:
Yes IT IS fastboot Mode but nothing works,
The zuk is Off [...] IT Boot in the Fastboot (the picture what i was uploading)
I can choose restart bootloader, Recovery Mode,Power Off and Boot to FFBM
Click to expand...
Click to collapse
Okay. When you're in fastboot, what happens if you enter the following into cmd?
Code:
fastboot devices
Does it display your device or is its output empty?
Please make sure that you actually type "fastboot" if you're in fastboot since adb isn't available once you boot into fastboot mode. That means adb devices wouldn't recognize your phone.
owczarek1987 said:
i remember that there must some With Numbers stand? (Devices serial of Something)
Click to expand...
Click to collapse
Yes, numbers and letters are valid. You should get a similar outut using fastboot devices
If that doesn't work for you you should check your drivers (you're using windows, right?). I cannot help you with the driver part, however, since I'm using linux (I never had to install drivers, thus it always worked) but you should find something on the net or here in xda.

Yes i use Windows.
The ZUK is Off and when in Connect zu the Laptop it Turn on and IT go automatikli to the fast Boot nur Windows make a conecting Sound
Uff drivers ....
Okay i install some Driver from Here.
Okay ich will bei Test some driver.
When IT goes can U Tell me what Inhaber too do?
Is it okay when i Reinstall twrp ober fastboot?

Done

owczarek1987 said:
Yes i use Windows.
The ZUK is Off and when in Connect zu the Laptop it Turn on and IT go automatikli to the fast Boot nur Windows make a conecting Sound
Uff drivers ....
Okay i install some Driver from Here.
Okay ich will bei Test some driver.
When IT goes can U Tell me what Inhaber too do?
Is it okay when i Reinstall twrp ober fastboot?
Click to expand...
Click to collapse
Hello.
Sorry, I am a bit busy in the moment an didn't log into xda.
So, yes, you can try to reinstall twrp as long as your device is being recognized.
And if you can flash twrp, then maybe search for stock ROM (or custom if you whish) and install that.
This should unbrick your device.

Related

[Q] Htc One BRICKED.

After only four day of having this phone i managed to brick it. I would really like to know if its fixable or if i have a really nice paper weight. Im stuck on a boot loop, I was half way through flashing a rom when it suddenly shut off. Now it will not boot up. I can load into the bootlader but when i try to go into recovery it just sends me to fastboot. When i restart the phone i can see the old recovery (TWRP)for just an instant but then the screen goes completely black. If i plug in to my pc, nothing happens my computer detects it but it says y device is damaged nd it cant identify it. PLEASE HELP Am i out of luck?
Ive looked around but i couldnt seem to find anyone with the same problem as me (Sprint Variant)
Good news it's not bricked i would put this question on the rom thread someonethere sshould be able to help
There's a Sprint One forum as well, so hopefully you found a ROM on there!
http://forum.xda-developers.com/forumdisplay.php?f=2215
jaythenut said:
Good news it's not bricked i would put this question on the rom thread someonethere sshould be able to help
Click to expand...
Click to collapse
I really hope so because on a college budget i cant afford another phone D:
Seen this in a couple of other places. Seems certain recoveries are possibly becoming currupted during flashing a new ROM.
What you need to do it get back into fastbboot, and....
fastboot erase recovery
fastboot erase cache
the re-flash your recovery, boot into recovery, full wipe and reflash your ROM.
wnp_79 said:
Seen this in a couple of other places. Seems certain recoveries are possibly becoming currupted during flashing a new ROM.
What you need to do it get back into fastbboot, and....
fastboot erase recovery
fastboot erase cache
the re-flash your recovery, boot into recovery, full wipe and reflash your ROM.
Click to expand...
Click to collapse
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
i suggest you contact with HTC customservices to repair this problem.
Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
Can you flash recovery in fastboot ?
the safest thing to do is relock and use a matching RUU to get back to stock
Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
Your phone isn't bricked. There are two tools in this forum that can help you. One is made by hasoon2000(I think that's his user name), and the other is jwtool(I think). Use them to help to flash a recovery if you don't know how to use fastboot.
DynamicRam said:
Can you flash recovery in fastboot ?
the safest thing to do is relock and use a matching RUU to get back to stock
Click to expand...
Click to collapse
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.
Muquita said:
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.
Click to expand...
Click to collapse
dont give up
Sent from my HTC One
Muquita said:
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.
Click to expand...
Click to collapse
Edit: Just got done typing the stuff below and saw you can't connect to your device in fastboot? What do you mean by re-installed driver?
Don’t worry, as long as you can still get into hboot your phone is not completely bricked!
The fastboot commands I referred to need to be carried out on your laptop/pc when you phone is connected in fastboot.
Can I assume that as you have already unlocked bootloader and flashed a custom recovery you are already familiar with this and have your computer set up for fastboot commands?
(Apologies if you already know some of this, best not to skip parts out though!)
I’d start with downloading a fresh version of your chosen recovery, and place it in your fastboot directory ready. I’d also do the same with your ROM.
Like you have already done, boot into fastboot. Connect your phone to your pc, and the red text should change to ‘Fastboot USB’.
Then open up command prompt and get to your fastboot directory. (On Windows 7 you just find that folder in Explorer, hold shift and right-click, then choose ‘Open command window here’.)
To check your pc is talking to your phone, type ‘fastboot devices’. You should get a device serial number back if all is well.
Then type ‘fastboot erase cache’ and hit enter.
Then type ‘fastboot erase recovery’ and hit enter.
Then type ‘fastboot flash recovery [name of recovery].img’ and hit enter.
Then type ‘fastboot reboot recovery’ and hit enter.
Hope fully you should successfully boot into recovery now. Once in recovery, mount USB storage and copy over your fresh ROM. Choose to do a full wipe including cache and dalvik, then reflash your ROM.
Reboot.
Let me know how this goes.
cronus101 said:
Your phone isn't bricked. There are two tools in this forum that can help you. One is made by hasoon2000(I think that's his user name), and the other is jwtool(I think). Use them to help to flash a recovery if you don't know how to use fastboot.
Click to expand...
Click to collapse
I used the hasoon2000 to flash TWRP earlier, but my problems is that my pc wont recognize my phone. When i plug it in it and try to re-flash it it cant find it. When i check my devices it shows up as an android device but it says the drivers are damaged. if i could get it to read it i think i should be eable to reflash somethint.
I APPRICIATE ALL THIS HELP. i really am trying to be as specific as possible :fingers-crossed:
Hey so just a thought and experience I have had with all my HTC phones is when you see that quick glimpse of the TWRP recovery screen then it disappears to an empty black screen......you are sometimes still in a form of recovery but during your Rom flash something (i don't know for sure) changed and it doesn't show the screen only black. So with that long explanation out of the way....have you tried once the screen goes black the
"adb devices "
Mine whenever in this situation would return the output of serial number and recovery so then you can push or sideload the Rom and boot into the system at which point your fastboot drivers will finally be recogniZed.....
Hope this helps a little
Sent from my HTC EVARE_UL using xda app-developers app
Muquita said:
I used the hasoon2000 to flash TWRP earlier, but my problems is that my pc wont recognize my phone. When i plug it in it and try to re-flash it it cant find it. When i check my devices it shows up as an android device but it says the drivers are damaged. if i could get it to read it i think i should be eable to reflash somethint.
I APPRICIATE ALL THIS HELP. i really am trying to be as specific as possible :fingers-crossed:
Click to expand...
Click to collapse
I'd say the next step is to re-install your drivers in the SDK. Open up your Android SDK and reinstall them. In Windows Device Manager, find your connected device (probably now with an exclamation mark on it) and right click on it and select 'Update Driver'.
(Assuming you are using Windows 7 here?)
http://developer.android.com/tools/extras/oem-usb.html
Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
when you are in fastboot, connect your phone using the usb cable, and when you see "fastboot" written in red turned into "fastboot usb" or something like this, do the commands below using cmd window of course :
1) fastboot erase recovery
2) fastboot erase cache
3) fastboot flash recovery recoveryname.img
4) fastboot erase cache
Let us know when you fix it
Good Luck
wnp_79 said:
I'd say the next step is to re-install your drivers in the SDK. Open up your Android SDK and reinstall them. In Windows Device Manager, find your connected device (probably now with an exclamation mark on it) and right click on it and select 'Update Driver'.
(Assuming you are using Windows 7 here?)
http://developer.android.com/tools/extras/oem-usb.html
Click to expand...
Click to collapse
(Win8 but the procces is identical.) All my drivers are up to date. Still no love.
On the dev forum is a thread that includes all the latest drivers (including an app to remove older drivers.)
Find that thread, download the drivers and bmp and driver removal tool. Remove drivers with tool, install the new drivers, reboot, connect phone and see if 'adb devices' finds anything.
Also make sure you're using the latest adb.
Sent from my HTC One using xda app-developers app
thneed said:
Hey so just a thought and experience I have had with all my HTC phones is when you see that quick glimpse of the TWRP recovery screen then it disappears to an empty black screen......you are sometimes still in a form of recovery but during your Rom flash something (i don't know for sure) changed and it doesn't show the screen only black. So with that long explanation out of the way....have you tried once the screen goes black the
"adb devices "
Mine whenever in this situation would return the output of serial number and recovery so then you can push or sideload the Rom and boot into the system at which point your fastboot drivers will finally be recogniZed.....
Hope this helps a little
Sent from my HTC EVARE_UL using xda app-developers app
Click to expand...
Click to collapse
This actually sounds really similar to my situation.. Would you care to be a little more specific on the procedure? noob here.
Tabtoub said:
when you are in fastboot, connect your phone using the usb cable, and when you see "fastboot" written in red turned into "fastboot usb" or something like this, do the commands below using cmd window of course :
1) fastboot erase recovery
2) fastboot erase cache
3) fastboot flash recovery recoveryname.img
4) fastboot erase cache
Let us know when you fix it
Good Luck
Click to expand...
Click to collapse
My pc will not recognize my phone. The drivers are up to date but when i plug it in it says something malfunctioned ?

[Q] Stuck in Bootloader

After flashing successfully viper rom after a full data wipe my phone is now stuck in the Bootloader screen. I can't get to recovery, I can't reboot, and factory resetting does nothing. Help?
cknuth said:
After flashing successfully viper rom after a full data wipe my phone is now stuck in the Bootloader screen. I can't get to recovery, I can't reboot, and factory resetting does nothing. Help?
Click to expand...
Click to collapse
What happens when u choose reboot in fastboot mode in the bootloader??
cknuth said:
After flashing successfully viper rom after a full data wipe my phone is now stuck in the Bootloader screen. I can't get to recovery, I can't reboot, and factory resetting does nothing. Help?
Click to expand...
Click to collapse
Can you reboot into recovery again and enter to fastboot mode?
Can go between fast boot and the Bootloader menu but if I hit reboot, it just comes back to Bootloader. If I pick recovery it just flashes for a second and comes back to Bootloader. I am S-off btw.
cknuth said:
If I pick recovery it just flashes for a second and comes back to Bootloader. I am S-off btw.
Click to expand...
Click to collapse
fastboot erase cache
nkk71 said:
fastboot erase cache
Click to expand...
Click to collapse
Computer wont recognize device. While I can enter fastboot mode it does not go to fastboot usb mode when I plug it in and fastboot only will "waiting for device"
cknuth said:
Computer wont recognize device. While I can enter fastboot mode it does not go to fastboot usb mode when I plug it in and fastboot only will "waiting for device"
Click to expand...
Click to collapse
OS, and hboot versions? (and if you're on Windows what does Device Manager show?)
nkk71 said:
OS, and hboot versions? (and if you're on Windows what does Device Manager show?)
Click to expand...
Click to collapse
unfortunately my HBOOT is 1.44 (I just now read that it needs to be 1.55) My OS is Win 8.1. My work computer is Vista though.
device manager shows nothing connected via USB
cknuth said:
unfortunately my HBOOT is 1.44 (I just now read that it needs to be 1.55) My OS is Win 8.1. My work computer is Vista though.
device manager shows nothing connected via USB
Click to expand...
Click to collapse
if you have a USB stick, just make an Ubuntu Live USB (no need to install, you just make it, then boot the laptop/pc from the USB), check my guide under FAQ #5 (i think) it's very easy and ubuntu doesn't have issues with hboots, drivers, etc...
nkk71 said:
if you have a USB stick, just make an Ubuntu Live USB (no need to install, you just make it, then boot the laptop/pc from the USB), check my guide under FAQ #5 (i think) it's very easy and ubuntu doesn't have issues with hboots, drivers, etc...
Click to expand...
Click to collapse
ok so the guide walks me up to the point of installing fastboot for unbuntu using a couple cmd lines but for my specific situation will I need any files saved in specific locations? I have never used Ubuntu or Linux before so youll have to bear with me.
Ok so im in Ubuntu, I think I have the guide pretty much figured out, but It still doesnt want to detect my device. I installed ADB according to the guide, but "sudo fastboot devices" comes up blank and the phone only says "fastboot" not "fastboot usb"
entering the command to flash CWM gives me the same waiting for device message. I have tried multiple USB cables as well.
cknuth said:
Ok so im in Ubuntu, I think I have the guide pretty much figured out, but It still doesnt want to detect my device. I installed ADB according to the guide, but "sudo fastboot devices" comes up blank and the phone only says "fastboot" not "fastboot usb"
entering the command to flash CWM gives me the same waiting for device message. I have tried multiple USB cables as well.
Click to expand...
Click to collapse
the phone has to say FASTBOOT USB, otherwise it's a problem with the port (phone/PC/cable).
ubuntu doesn't have driver issues, but when you connect your phone to the PC, it has to change from FASTBOOT to FASTBOOT USB.
nkk71 said:
the phone has to say FASTBOOT USB, otherwise it's a problem with the port (phone/PC/cable).
ubuntu doesn't have driver issues, but when you connect your phone to the PC, it has to change from FASTBOOT to FASTBOOT USB.
Click to expand...
Click to collapse
It doesnt change, so then its likely something with the system partition as it relates to the USB port? Because the port was working fine until the failed flash. But what it sounds like is this is a brick?
cknuth said:
It doesnt change, so then its likely something with the system partition as it relates to the USB port? Because the port was working fine until the failed flash. But what it sounds like is this is a brick?
Click to expand...
Click to collapse
doesn't sound like a brick at all, as long a hboot (ie bootloader is fine) no brick should be involved.
but i have to call it a night, hopefully someone will be along shortly, and take over... (timezones ) take it ease, DO NOT PANIC, DO NOT RUSH things!!
Cool, all your help is greatly appreciated. So I should hold off on the trip to the phone store?
Any other ideas to get communication to the phone?
Different Computer, USB Port, and USB Cable. Without saying FASTBOOT USB on the phone, can't do anything.

[Q] help bootloader & root

hello,
I buyed a moto g, it's my first smarthphone... it's a XT1069 Dual Sim
I followed this tuturial http://forum.xda-developers.com/moto-g-2014/development/guide-root-moto-g-2nd-gen-2014-t2874245 ,
I get to unlock the bootloader, but when I get to this point
4. Flash Recovery through fastboot mode/bootloader mode
and Go into your adb+fastboot folder and Type in CMD prompt
Command :
Code: fastboot flash recovery TWRP2801-titan-motog-2014.img
can't get the moto g in flash recovery mode, it appear a dead android with a RED ! TRIANGLE...
any idea to resolve this...
RastaFATian said:
hello,
I buyed a moto g, it's my first smarthphone... it's a XT1069 Dual Sim
I followed this tuturial http://forum.xda-developers.com/moto-g-2014/development/guide-root-moto-g-2nd-gen-2014-t2874245 ,
I get to unlock the bootloader, but when I get to this point
4. Flash Recovery through fastboot mode/bootloader mode
and Go into your adb+fastboot folder and Type in CMD prompt
Command :
Code: fastboot flash recovery TWRP2801-titan-motog-2014.img
can't get the moto g in flash recovery mode, it appear a dead android with a RED ! TRIANGLE...
any idea to resolve this...
Click to expand...
Click to collapse
There's no need to make multiple topics, my friend...
Remember that the TWRP IMG file must be in the same folder as your Fastboot files.
So, you can copy TWRP2801-titan-motog-2014.img file to the directory where your Fastboot is.
Or, you can type the directories correctly. For example, if your TWRP2.8.0.1 IMG file is located on your Desktop:
So, your command should be: fastboot flash recovery C:\Users\"username"\Desktop\TWRP2801-titan-motog-2014.img
Instead of typing, you can also drag-and-drop the TWRP2801-titan-motog-2014.img file into the CMD window.
Got it?
rafaelbrunner said:
There's no need to make multiple topics, my friend...
Remember that the TWRP IMG file must be in the same folder as your Fastboot files.
So, you can copy TWRP2801-titan-motog-2014.img file to the directory where your Fastboot is.
Or, you can type the directories correctly. For example, if your TWRP2.8.0.1 IMG file is located on your Desktop:
So, your command should be: fastboot flash recovery C:\Users\"username"\Desktop\TWRP2801-titan-motog-2014.img
Instead of typing, you can also drag-and-drop the TWRP2801-titan-motog-2014.img file into the CMD window.
Got it?
Click to expand...
Click to collapse
I'm sorry about multiple topics... my bad.... but you can erase the other in general topic....
but to flash i need to be in recovery mode at boolloader, no?
i can do this command in bootloader menu?
can't get the moto g in flash recovery mode, it appear a dead android with a RED ! TRIANGLE...
any idea to resolve this...
Fastboot and recovery are two different things. If you can get to Fastboot (bootloader) mode you should be able to flash recovery from there as stated by rafaelbrunner.
Hi Guys !
I'm facing a problem on rooting my Moto G 2014.
I've easily unlocked the bootloader but i can't flash the TWRP recovery.
I've read everything I could read about the process and I think I'm doing it the right way (the recovery file in the adb folder, etc...) and everything seems to be ok.
I've just a purple line at the end of the TWRP flashing procedure saying:
Mismatched partition size (recovery)
This post says that it's not really a problem: http://forum.xda-developers.com/showpost.php?p=48294073&postcount=6
Then, when I reboot the recovery, the phone reboots and the system starts normally (instead of restarting with the custom recovery ?). When I switch it off and switch it on in recovery mode, I still have the stock recovery.
Tried several times with TWRP 2.8.0.1
I can't say if it's because of a problem with TWRP (it's said here that it is buggy) or because I'm doing something wrong that I don't succeed.
I saw that there was a 2.7.1.1 release of TWRP for Moto G 2014 but it's no more available anywhere for now. I would have liked to try it...
Do you know if there's some known issues about flashing the Moto G 2014 recovery or can you help in any way ?
Hi guys !
I'm still investigating my problem and still trying to root the phone.
Here is what I get with adb:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWAP2801 titan-motog-2014.img
target reported max download size of 536870912 bytes
sending 'recovery' (9738 KB)...
OKAY [ 0.344s]
writing 'recovery'...
OKAY [ 0.353s]
finished. total time: 0.700s
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot recovery
error: device not found
C:\Program Files <x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
The device seems to be seen when it's about writing the file on the storage but it's no more found when it's about rebooting the recovery...
Can someone help ?
magmatik said:
Hi guys !
I'm still investigating my problem and still trying to root the phone.
Here is what I get with adb:
The device seems to be seen when it's about writing the file on the storage but it's no more found when it's about rebooting the recovery...
Can someone help ?
Click to expand...
Click to collapse
First of all Uninstall ur old Moto Usb Drivers and fastboot drivers and Reboot your Pc And Again Install Ur Usb Drivers.
2987
jbanti said:
First of all Uninstall ur old Moto Usb Drivers and fastboot drivers and Reboot your Pc And Again Install Ur Usb Drivers.
Click to expand...
Click to collapse
Hi !
Thanks for your answer !
What do you mean exactly ? I didin't have any "old Moto usb drivers before". I installed them for the first time few days ago to unlock my bootloader.
Do I still have to uninstall these drivers (that are not that old) and install again the same ones ?
magmatik said:
Hi !
Thanks for your answer !
What do you mean exactly ? I didin't have any "old Moto usb drivers before". I installed them for the first time few days ago to unlock my bootloader.
Do I still have to uninstall these drivers (that are not that old) and install again the same ones ?
Click to expand...
Click to collapse
You can use "adb reboot recovery" only if the phone is turned on in normal android os ( in bootloader mode it'll only recognize fastboot commands ), and you must be sure also to have debug usb option enabled under settings/developer settings.
1932
eskamhl said:
You can use "adb reboot recovery" only if the phone is turned on in normal android os ( in bootloader mode it'll only recognize fastboot commands ), and you must be sure also to have debug usb option enabled under settings/developer settings.
Click to expand...
Click to collapse
Hi eskamhl,
I warmly thank you for trying to help me.
I'had enabled usb debbug, no problem about that.
I"m not sure I understand what you mean when you say that the phone has to be " turned on in normal android os". I thought that the device had to started in recovery mode to install TWRP.
I tried to install TWRP with adb reboot recovery and with the phone turned on in normal android os.
adb says <waiting for device> when i paste and execute flash recovery TWRP2801-titan-motog-2014.img
magmatik said:
Hi eskamhl,
I warmly thank you for trying to help me.
I'had enabled usb debbug, no problem about that.
I"m not sure I understand what you mean when you say that the phone has to be " turned on in normal android os". I thought that the device had to started in recovery mode to install TWRP.
I tried to install TWRP with adb reboot recovery and with the phone turned on in normal android os.
adb says <waiting for device> when i paste and execute flash recovery TWRP2801-titan-motog-2014.img
Click to expand...
Click to collapse
Adb is one thing, fastboot is a different one.
If you give a "fastboot command" from the command prompt the phone must be in bootloader mode, instead if you give an "adb command" you must have the phone normally turned on.
Having said that, I didn't understand what's your problem... are you tryin' to boot into recovery mode or trying to flash twrp recovery?
It seems that you already flashed/installed a custom recovery ( TWRP ) from what you wrote, isn't it?
eskamhl said:
Adb is one thing, fastboot is a different one.
If you give a "fastboot command" from the command prompt the phone must be in bootloader mode, instead if you give an "adb command" you must have the phone normally turned on.
Having said that, I didn't understand what's your problem... are you tryin' to boot into recovery mode or trying to flash twrp recovery?
It seems that you already flashed/installed a custom recovery ( TWRP ) from what you wrote, isn't it?
Click to expand...
Click to collapse
That's the point, I'm trying to flash a custom recovery (TWRP) in order to be able to flash SU.
I'm sorry about my poor english. I'm french and I confess that I'm absolutely comfortable in english.
For now the only thing I succeeded to do is to unlock the bootloader.
What I understand is that I have now to install TWRP with adb, am I right ?
magmatik said:
That's the point, I'm trying to flash a custom recovery (TWRP) in order to be able to flash SU.
I'm sorry about my poor english. I'm french and I confess that I'm absolutely comfortable in english.
For now the only thing I succeeded to do is to unlock the bootloader.
What I understand is that I have now to install TWRP with adb, am I right ?
Click to expand...
Click to collapse
No, you're not
You already did the installation of the custom recovery since you said that you received this message "Mismatched partition size (recovery)", now from bootloader menu you should boot into recovery ( volume down to scroll thorugh the options and volume up to select ).
If it won't boot maybe you should check the md5 of the downloaded recovery .img, probably it's a corrupted download.
eskamhl said:
No, you're not
You already did the installation of the custom recovery since you said that you received this message "Mismatched partition size (recovery)", now from bootloader menu you should boot into recovery ( volume down to scroll thorugh the options and volume up to select ).
If it won't boot maybe you should check the md5 of the downloaded recovery .img, probably it's a corrupted download.
Click to expand...
Click to collapse
When I try to boot into recovery from the bootloader (what I already did before), the screen turns black, 1 sec later the led switch on for half a sec and nothing else happends.
So, as you say, the recovery I downloaded was maybe corrupted. I'll check.
Guys, I've found the solution !
I think everything was ok from the beginning. The only thing that I did not understand was that I have to press vol- in fastboot to focus on "recovery" and to press vol+ to launch the recovery.
I didn't read it anywhere, i just see this in this video : https://www.youtube.com/watch?v=jr14wNgazOw&hd=1 (see at 7"15).
Anyway, thank you for trying to help me and see you soon for all the good things coming for this phone !
magmatik said:
Guys, I've found the solution !
I think everything was ok from the beginning. The only thing that I did not understand was that I have to press vol- in fastboot to focus on "recovery" and to press vol+ to launch the recovery.
I didn't read it anywhere, i just see this in this video : https://www.youtube.com/watch?v=jr14wNgazOw&hd=1 (see at 7"15).
Anyway, thank you for trying to help me and see you soon for all the good things coming for this phone !
Click to expand...
Click to collapse
My friend... a few posts above
eskamhl said:
now from bootloader menu you should boot into recovery ( volume down to scroll thorugh the options and volume up to select )
Click to expand...
Click to collapse
I successfully installed twrp recovery system but I can't do any backup, the system reboot in the process...
eskamhl said:
My friend... a few posts above
Click to expand...
Click to collapse
You're right... my bad

Is it possible to access files / pics via fastboot only?

Hello All,
I have following issue and hope that - if possible - someone can help me. I also would like to mention that I am not an
Android expert but did read a lot of articles here in the forum to find out - or better - to get an idea how things are working.
My Z3C had a water damage. Now I only get fastboot mode. Display is broken and does not show anything. I installed Android-SDK
to get ADB and Fastboot. I installed also drivers.
When I connect the device while pushing the "volume down" button the device manager show me a somc flash device with the "volume up" button I see an Android ADB Interface device. However ADB is not working (no device found) only Fastboot does.
I flashed the "Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img" with Flashtool via fastboot in the hope that I can somehow access
to "sdcard" by blindly navigating to "mount storage" but nothing seem to work.
On my linux device I see that the usb device is recognized but that it is not an mtp device.
Before I continue to spent hours without really knowing what I am doing I thought that if there is a solution I would find it here.
So if there is any way to get access to my files / pics on the device I would be really glad if someone can let me know how or
at least bring me to the right direction.
Thanks a lot in advance!
Is your bootloader unlocked?
clouds5 said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Thanks for your reply clouds5.
I followed the process to unlock the bootloader (got code from sony side and unlocked via fastboot with
"fastboot.exe -i 0x0fce oem unlock 0xKEY").
In Flashtool, when I click on the "BLU" Icon I get a window with with my IMEI and my Unlock Code and a
Relock Button. So I assume that the bootloader is unlocked.
If there is another way to verify please let me know and I will do.
no you cannot access files via fastboot only. but isn't it possible to flash custom recovery img file and boot into recovery and access files?
evildog1 said:
no you cannot access files via fastboot only. but isn't it possible to flash custom recovery img file and boot into recovery and access files?
Click to expand...
Click to collapse
I flashed "Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img" from doomlord.xperia-files.com/download.php?dlid=WjNjX0Rvb01Mb1JEX0FkdlN0a0tlcm5lbF92MDFfRlctMTA1 with
fastboot flash boot Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img
in the hope that it is possible but after rebooting it immediately goes into fastboot again. As I do not have
a screen I can not see anything - so I can not really confirm if it works or not - and in windows I do not see
anything either..
Galbasib said:
I flashed "Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img" from doomlord.xperia-files.com/download.php?dlid=WjNjX0Rvb01Mb1JEX0FkdlN0a0tlcm5lbF92MDFfRlctMTA1 with
fastboot flash boot Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img
in the hope that it is possible but after rebooting it immediately goes into fastboot again. As I do not have
a screen I can not see anything - so I can not really confirm if it works or not - and in windows I do not see
anything either..
Click to expand...
Click to collapse
hmm you better send it to repair.
evildog1 said:
hmm you better send it to repair.
Click to expand...
Click to collapse
That's unfortunately not an option as I had to disassemble the device
evildog1 said:
no you cannot access files via fastboot only. but isn't it possible to flash custom recovery img file and boot into recovery and access files?
Click to expand...
Click to collapse
Should sdcard appear automatically when booting into recovery or are there any specific steps I would need to complete?

Problems Going Back To Stock Rom

Hi,
tried to go back to stockrom using this article (2. guide):
https://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.57/
When I write adb reboot edl in the command prompt and klick enter, nothing happens in QFil, the phone makes a normal reboot und goes to startscreen.
What's wrong?
Regards Robert
robert_b said:
Hi,
tried to go back to stockrom using this article (2. guide):
https://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.57/
When I write adb reboot edl in the command prompt and klick enter, nothing happens in QFil, the phone makes a normal reboot und goes to startscreen.
What's wrong?
Regards Robert
Click to expand...
Click to collapse
Go into recovery adn then try adb reboot edl or inside the twrp use terminal to reboot edl.
Starchm said:
Go into recovery adn then try adb reboot edl or inside the twrp use terminal to reboot edl.
Click to expand...
Click to collapse
Thank you. I don't know much about adb. What's recovery adn?
or is it a mistake und simply means "and"? Sorry
robert_b said:
or is it a mistake und simply means "and"? Sorry
Click to expand...
Click to collapse
its an and*
sorry, doesn't work. Can't boot into EDL and not into bootloader too, even the phone shows unlock status.
May be I made a mistake when flashing other baseband and kernel??
Flashed this kernel https://forum.xda-developers.com/zuk-z2-pro/development/pro-plus-f1xy-kernel-t3866779 and this baseband https://forum.xda-developers.com/zuk-z2-pro/development/radio-modem-basebands-zuk-z2-pro-t3715835
The phone works with RR 6.2.1 but makes some problems, i.e. with Titanium Backup and skips pin-query for simcard. So I intended to go back to stockrom and then start once more from the beginning.

Categories

Resources