Database Develop

[Q] Please help w/bootloader

Hello guys! I I stucked in very interesting case.....Been flashing Resurrection Remix with fullwipe from Chroma, all ok, on first boot i do a silly thing while boot become too long i goind to reboot phone and then see that phone is encrypting......it reboots and here i have "Encryption unsuccessful" and button factory reset which do nothing. I know about reboot to bootloader, but NRT can't reboot my device in bootloader, and my Vol- button broken. What i gonna do, please help, heard about hardbrick method or something else for reboot to bootloader. Thanks for advance :cyclops:

TAGTRAUM said:
Hello guys! I I stucked in very interesting case.....Been flashing Resurrection Remix with fullwipe from Chroma, all ok, on first boot i do a silly thing while boot become too long i goind to reboot phone and then see that phone is encrypting......it reboots and here i have "Encryption unsuccessful" and button factory reset which do nothing. I know about reboot to bootloader, but NRT can't reboot my device in bootloader, and my Vol- button broken. What i gonna do, please help, heard about hardbrick method or something else for reboot to bootloader. Thanks for advance :cyclops:
Click to expand...
Click to collapse
Does NRT give you an error when it tries to reboot into bootloader? Another reason to stay away from toolkits, but that is another debate for another time. Have you tried manually running the ADB commands to boot into fastboot? Do you have access to a computer with Android SDK installed?

Not sure what you want to do in bootloader. Recovery makes more sense to me. Flash a non-force encrypt kernel, format userdata and you're away.
From a command prompt / termina (whilst booting and connected with USB cable)...
Code:
adb reboot recovery
or
Code:
adb reboot bootloader

Circaflex said:
Does NRT give you an error when it tries to reboot into bootloader? Another reason to stay away from toolkits, but that is another debate for another time. Have you tried manually running the ADB commands to boot into fastboot? Do you have access to a computer with Android SDK installed?
Click to expand...
Click to collapse
Yes, tried manually commands before use toolkit, no luck "device not found", drivers are ok, device visible in Device Manager as MTP, before this "unsuccessful" flash works like a charm. And then is no way out, when device is on it show encryption message and still no luck with ADB. Maybe some script that override ADB and took me into recovery/bootloader??

TAGTRAUM said:
Yes, tried manually commands before use toolkit, no luck "device not found", drivers are ok, device visible in Device Manager as MTP, before this "unsuccessful" flash works like a charm. And then is no way out, when device is on it show encryption message and still no luck with ADB. Maybe some script that override ADB and took me into recovery/bootloader??
Click to expand...
Click to collapse
Nope.. If adb doesn't work and volume buttons are broken, you're stuck. Get the buttons repaired.

rootSU said:
Not sure what you want to do in bootloader. Recovery makes more sense to me. Flash a non-force encrypt kernel, format userdata and you're away.
From a command prompt / termina (whilst booting and connected with USB cable)...
Code:
adb reboot recovery
or
Code:
adb reboot bootloader
Click to expand...
Click to collapse
No luck with running this commands in boot process

TAGTRAUM said:
No luck with running this commands in boot process
Click to expand...
Click to collapse
Adb only works if the device is booted up or in sideload mode in recovery, fastboot works in fastboot/bootloader mode. Is/was the device recognised as a adb device when you typed `adb devices`in cmd?

gee2012 said:
Adb only works if the device is booted up or in sideload mode in recovery, fastboot works in fastboot/bootloader mode. Is/was the device recognised as a adb device when you typed `adb devices`in cmd?
Click to expand...
Click to collapse
Adb should work from part way through the boot process and any mode. in custom recovery.

gee2012 said:
Adb only works if the device is booted up or in sideload mode in recovery, fastboot works in fastboot/bootloader mode. Is/was the device recognised as a adb device when you typed `adb devices`in cmd?
Click to expand...
Click to collapse
No, it's not appear in "adb devices" on any process of boot, but Windows recognise in Device Manages as "MTP USB Device" even when phone off and connected via USB

TAGTRAUM said:
No, it's not appear in "adb devices" on any process of boot, but Windows recognise in Device Manages as "MTP USB Device" even when phone off and connected via USB
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=2588979

Evolution_Tech said:
Try this
Click to expand...
Click to collapse
Will try, but decide to repair my Vol- button myself, i have no mind what can be broken in this part, watching video of N6 dissassembly, its pretty simple part indeed Walking w/o Vol- for a month, and this situation is frustrating me and other situations can happen, in certain cases i still need Vol- :cyclops:

System Recovery Access & Options

For what its worth-
I can boot into Android system recovery <3e> for Android 5.1.1 build # A1PV1.0.0B17 by powering off and pressing power and volume up at the same time then releasing when the Android appears. Pressing the volume key down instead takes you to Factory Test Mode. The following options are available in recovery:
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
apply update from cache.

Unfortunately there seems to be no way to get into the bootloader. Hitting "reboot to bootloader" just reboots the phone back to android. One of these days someone will crack this phone. Just hoping we get some people with some development experience on board with this phone.

There was a post that I saw that said that ZTE phones come with the bootloader already unlocked, but I haven't found a way to check it. Has anyone tried to see if the Factory Test is just their fancy way of saying that it's in bootloader mode?

For fastboot: If you have ADB you have fastboot, even if you don't know it yet. Make sure adb sees you device by running the following:
Code:
adb devices
Code:
adb reboot bootloader
Your device will have a RED light at the top, and your screen will be black. Make sure Windows Update can get drivers for you, and it'll install it.

http://forum.xda-developers.com/showpost.php?p=48319535&postcount=29

http://forum.xda-developers.com/showthread.php?t=2520309

http://cellphonetipsandtrickss.blogspot.com/2013/10/the-super-secret-codes-fr-zte.html

Sebring5 said:
For fastboot: If you have ADB you have fastboot, even if you don't know it yet. Make sure adb sees you device by running the following:
Code:
adb devices
Code:
adb reboot bootloader
Your device will have a RED light at the top, and your screen will be black. Make sure Windows Update can get drivers for you, and it'll install it.
Click to expand...
Click to collapse
I've tried this and it simply reboots my Axon Pro (model A1P). Where are you getting the drivers from? (Besides windows update and Install mode when you connect the Axon to your PC.)

I use a Mac. No drivers needed.

Sebring5 said:
I use a Mac. No drivers needed.
Click to expand...
Click to collapse
That..doesn't exactly help..

Archfeind2 said:
That..doesn't exactly help..
Click to expand...
Click to collapse
http://forum.xda-developers.com/zte-axon/help/zte-axon-drivers-adb-t3173020

Sebring5 said:
http://forum.xda-developers.com/zte-axon/help/zte-axon-drivers-adb-t3173020
Click to expand...
Click to collapse
Already checked that thread out and the ZTE or the google drivers doesn't allow me to get to fastboot. After putting in "adb reboot bootloader" it just reboots the phone.
I also see that whenever you install the drivers from the phone, it installs only adb with a bunch of other ZTE programs for adb with no fastboot in sight.

Archfeind2 said:
Already checked that thread out and the ZTE or the google drivers doesn't allow me to get to fastboot. After putting in "adb reboot bootloader" it just reboots the phone.
I also see that whenever you install the drivers from the phone, it installs only adb with a bunch of other ZTE programs for adb with no fastboot in sight.
Click to expand...
Click to collapse
Try this: http://www.downloads.techdiscussion.in/smartphones/zte-axon-pro-pc-suite-and-usb-driver/

Okay cool. I'll check it out in a couple of minutes.
Edit:
It didn't work it was the same as the axon installer unfortunately. Maybe I'll have to virtual machine either mac or Linux, again >.<
I really want this phone's bootloader unlocked xD

Op3t fastboot cannot install twrp

I tried to install twrp on my OP3T but everytime i write "fastboot flash recovery trwp.img" it says "error: cannot load 'twrp.img'"
When I type "adb devices" my phone doesn't show up
I unlocked the bootloader
I activated USB debugging
I checked the OEM thing
I have put the twrp.img in the same Minimal ADB and Fastboot folder
What could it be?

Install correct driveres or use another usb port. Device have to be adressed via "fastboot devices" or "adb devices".

It's probably a typing error ..Rename the twrp in whatever you want and then type " fastboot flash recovery " whatever you want".img

Rename file
Did you rename the file? You need to rename it before flashing.

IT WORKED
Everytime I was putting the phone into bootloader mode, the phone was already plugged in. Then I tried to put the phone to bootloader mode and THEN plugging it in my pc... and it worked ^^
Strange, right?

cerfeda.albert said:
Everytime I was putting the phone into bootloader mode, the phone was already plugged in. Then I tried to put the phone to bootloader mode and THEN plugging it in my pc... and it worked ^^
Strange, right?
Click to expand...
Click to collapse
I also experienced this thing this morning.
A simple unplug, re-plug solved for me

Whenever i flash twrp through fastboot it just gets stuck on the twrp logo and doesn't go beyond it.
I've tried with 3.0.3.1, 3.0.3.0, 3.0.2.0 but still the same
can anyone help me with this?

Guiliang said:
Did you rename the file? You need to rename it before flashing.
Click to expand...
Click to collapse
no you don't.
Just type the first few letters and hit [tab]. Works on windows, linux, mac os and every other shell made within the last 40 years.

cerfeda.albert said:
I tried to install twrp on my OP3T but everytime i write "fastboot flash recovery trwp.img" it says "error: cannot load 'twrp.img'"
When I type "adb devices" my phone doesn't show up
I unlocked the bootloader
I activated USB debugging
I checked the OEM thing
I have put the twrp.img in the same Minimal ADB and Fastboot folder
What could it be?
Click to expand...
Click to collapse
The last parameter has to be the EXACT filename, that you are flashing, which is the TWRP image. It has to be in the same folder as your command prompt is or you need to include the path to the twrp file.

Try the last TWRP release, should work!

Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
milanexplorer said:
Whenever i flash twrp through fastboot it just gets stuck on the twrp logo and doesn't go beyond it.
I've tried with 3.0.3.1, 3.0.3.0, 3.0.2.0 but still the same
can anyone help me with this?
Click to expand...
Click to collapse

originalnabisco said:
Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
Click to expand...
Click to collapse
After installing the twrp and then you type ... Fastboot boot twrp.img. Probably you are stuck on twrp splash screen...
Try to boot manually.to twrp by pressing power button and volume down button...Then you should be able to boot on twrp....

originalnabisco said:
Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
Click to expand...
Click to collapse
See this thread.

originalnabisco said:
Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
Click to expand...
Click to collapse
Did you try to fastboot TWRP after flashing it?
What I mean is, after you enter the command "fastboot flash recovery twrp.img", proceed with "fastboot boot twrp.img" and it will boot. Doing this you prevent Oxygen OS from overwriting TWRP. You should be able to boot normally after doing that.
Don't be worried and try to boot into recovery as described, that should work, if it doesn't I wonder if you flashed the right version of TWRP.
Try and let us know.

jmazzamj said:
Did you try to fastboot TWRP after flashing it?
What I mean is, after you enter the command "fastboot flash recovery twrp.img", proceed with "fastboot boot twrp.img" and it will boot. Doing this you prevent Oxygen OS from overwriting TWRP. You should be able to boot normally after doing that.
Don't be worried and try to boot into recovery as described, that should work, if it doesn't I wonder if you flashed the right version of TWRP.
Try and let us know.
Click to expand...
Click to collapse
how long does it usually take? i've waited more than 10 minutes now.

Razoth said:
how long does it usually take? i've waited more than 10 minutes now.
Click to expand...
Click to collapse
Boot manually on it...

cultofluna said:
Boot manually on it...
Click to expand...
Click to collapse
apperantly i'm a retard, after i rebooted to recovery with hardware keys it shows the oneplus logo and i was like "this isnt twrp startup" and hardreset it... waiting boots into twrp just fine...

adb cannot locate file
cerfeda.albert said:
Everytime I was putting the phone into bootloader mode, the phone was already plugged in. Then I tried to put the phone to bootloader mode and THEN plugging it in my pc... and it worked ^^
Strange, right?
Click to expand...
Click to collapse
I'm having some difficulty getting past this step.
I've unlocked bootloader, enabled oem unlock and enabled usb debugging. I've added the PATH where my twrp.img file is located.
Whenever I input fastboot flash recovery twrp.img, it says error: cannot load twrp.img: no such file or directory.
I see the file in the correct location so i'm not sure what i'm doing wrong here.
Any ideas?

chizzwhizz said:
I'm having some difficulty getting past this step.
I've unlocked bootloader, enabled oem unlock and enabled usb debugging. I've added the PATH where my twrp.img file is located.
Whenever I input fastboot flash recovery twrp.img, it says error: cannot load twrp.img: no such file or directory.
I see the file in the correct location so i'm not sure what i'm doing wrong here.
Any ideas?
Click to expand...
Click to collapse
Reinstall your adb + fastboot drivers

A guide for flashing TWRP?

I've been searching all over the place...
Could anyone point me at a guide for newbs?
Thanks!
X

1xcalibur1 said:
I've been searching all over the place...
Could anyone point me at a guide for newbs?
Thanks!
X
Click to expand...
Click to collapse
First, you need your bootloader to be unlocked. It's pretty easy if you have that done already.
You'll need ADB and Fastboot. It can be tricky to get the right drivers. The driver used when your phone is connected in normal mode is not the same when connected in fastboot mode, in my experience anyway. You'll want the 15sec ADB driver and you'll need to update the driver when it is in fastboot mode.
Next, get the correct twrp img and put it in the ADB folder(you'll need a different one based on flashing a pie rom or a q rom). You may want to rename it so it's easier to type in fastboot.
To enter fastboot mode, hold volume up and plug in the usb cable. The LED should light up blue.
Open a command prompt and navigate to wherever you've installed ADB(mine is on C:\ so it's really easy).
Type "fastboot devices" to double check if the driver is installed and your phone is connected in fastboot mode.
------It should show something like: BH9090808E fastboot
Then type "fastboot flash recovery twrp.img" - or whatever you've named the file. It will take less than a few seconds.
Then type "fastboot reboot" and let your phone reboot.
Done

Thanks a lot for the reply!
I've been experiencing the exact issues you described. I'm having issues unlocking the Bootloader. "Fastboot.exe devices" does not show anything, the phone is with a blue led on and a balck screen and when I look in Device Manager there's an "Other" Android device with an "!".
Could you please share the drivers you mentioned? Because I really went through
everything and none was accepted. Also the 15 Seconds ADB Drivers did not help.
Thanks!

1xcalibur1 said:
Thanks a lot for the reply!
I've been experiencing the exact issues you described. I'm having issues unlocking the Bootloader. "Fastboot.exe devices" does not show anything, the phone is with a blue led on and a balck screen and when I look in Device Manager there's an "Other" Android device with an "!".
Could you please share the drivers you mentioned? Because I really went through
everything and none was accepted. Also the 15 Seconds ADB Drivers did not help.
Thanks!
Click to expand...
Click to collapse
My apologies. It's been so long since I've started from scratch, I must've gotten the drivers mixed up. The 15sec ADB is for the phone connected in normal mode.
I'm pretty sure this one is the fastboot one:
https://developer.sony.com/file/download/xperia-xz1-compact-driver/
If not, I'm sorry because that's all I have.

I nailed it eventually!
For anyone that comes across this thread,
this video will solve all your problems with adb drivers:

Question [Resolved] No connection with pc in fastboot mode.

Hello all, I'm trying to install a new ROM but one of the first steps consists in getting access to adb and fastboot mode.
Unfortunately, I can easily access to adb mode, and adb commands respond well, but when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
I've tried to install adb drivers, uninstall/reinstall the drivers (but it's always the windows drivers that installs first). I even tried to install google usb drivers using SDK manager, but didn't succeed this step.
I've tried to change the usb cable, but with another one, it was worse: even the adb commands would not work. So I guess the one I'm using is ok.
I'd be very happy if someone could help me fixing this frustrating bug!
Model:M1903F11A
kernel:4.14.117-perf-g0f2347b
MIUI Global 12.0.6
Android version : 10 QKQ1.190825.002

Cyjam said:
.. new ROM but one of the first steps consists in getting access to adb and fastboot mode.
...
Click to expand...
Click to collapse
The first step is to unlock the bootloader.
Cyjam said:
... when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
....
Click to expand...
Click to collapse
For fastboot try:
adb devices
........... (here you must see a number)
adb reboot bootloader
fastboot devices
........... (here you must see that number again)

Hi, thanks for trying to help me:
you're right , first is the unlock, but it's done. it's even in "grey" on the screen and written: bootloader is already unlocked. I've tested my phone with "root checker" and test is ok.
you're right about the command, this is the one I've used to go to fastmode and actually this command works: as I said, when in adb mode, it's all good: my phone is connected to pc and accepts the adb commands. But once I switch to fastboot, this is when it's going wrong: my phone's not answering to any commands.
To be more precise: when prompting: adb devices: i get a number. When prompting, in fastbood mode, fastboot devices: i get nothing.

Alleluia!!
Finally found out how to fix it!
After going in fasboot mode with the command: adb reboot bootloader, i opened the windows device manager: There I found a android XXx interface, or something like this: anyway, something barely identified by windows. Right clik, update drivers, manually update, pointing to the folder I store the google usb drivers and : Bingo! It works like a treat.
I now can step further in the process... Hope I won't need to come back with another question in the next minutes!