I had stock android 7, used the toolkit, "Unlocked" the bootloader, after that there was a part with erasing all data to factory due to an error, something along the lines there was a pin or password detected, and after I pressed reset the screen went black, and when it tries to boot it shows ZTE for a second and then it vibrates and shuts off instantly. So I can get it in to edl mode and I see the Qualcomm HS-USB QDLoader 9008 in my devices, but I can't find any thread to fix this. Tried flashing stock firmwares via MiFlash, no luck. And the thing is, most roms I download give me a batch of files in a zip, if I put them in a folder and try to flash I get this - Object reference not set to an instance of an object. Help asap, because I am having a horrible time using my partially destroyed S6 Edge Plus. If I spelled smth wrong sorry, Russian here.
This is what I had - My device is stuck on an 'Enter your password to start Android' screen.
Unfortunately this requires a factory reset.
1) Boot your device into recovery mode by pressing and holding the power and volume up buttons for 10-15 seconds.
2) Stock Recovery: Use the volume down key to go down to 'Wipe data/factory reset' and press power to select. Press the volume down key again to go down to 'Yes' and press power to select.
TWRP Recovery: Tap "Wipe" < Tap "Advanced Wipe" < Check the box next to "data" < Tap "Repair or change file system" < Tap "EXT4" < Swipe to confirm.
3) Reboot your device.
Jazkade said:
I had stock android 7, used the toolkit, "Unlocked" the bootloader, after that there was a part with erasing all data to factory due to an error, something along the lines there was a pin or password detected, and after I pressed reset the screen went black, and when it tries to boot it shows ZTE for a second and then it vibrates and shuts off instantly. So I can get it in to edl mode and I see the Qualcomm HS-USB QDLoader 9008 in my devices, but I can't find any thread to fix this. Tried flashing stock firmwares via MiFlash, no luck. And the thing is, most roms I download give me a batch of files in a zip, if I put them in a folder and try to flash I get this - Object reference not set to an instance of an object. Help asap, because I am having a horrible time using my partially destroyed S6 Edge Plus. If I spelled smth wrong sorry, Russian here.
Click to expand...
Click to collapse
I had a similar problem on my 2017U model after flashing a .zip that was supposed to remove the "bootloader is unlocked" screen that shows up after you unlock the bootloader. Long story short, the .zip wasn't meant for U models. Only G. So my phone was in a worse situation than yours and would not power on. You'll need to download an EDL recovery firmware .zip for your phone and place it within the toolkits folders manually and then go through the steps of the toolkit which I'll try to help you do.
First, download the full stock B09 (G) firmware from here. You can OTA update to the latest firmware after a successful flash. It's okay to flash an older firmware in this situation.
Once done, navigate to C:\Axon7Development\Axon7Toolkit\MiFlash\B09\ (copy/move the full .zip of the B09 firmware you downloaded in the first step into this folder) If the B09 folder doesn't exist under \MiFlash, create it manually.
Run the toolkit again from the start and type 11 "RESTORE TO STOCK/RECOVER FROM HARDBRICK (EDL)" and hit enter. On the next screen type in the number that will restore B09. It should tell you how to put the phone in EDL mode and automatically open MiFlash. Make sure to follow the steps and paste the directory path of the firmware in the top bar in MiFlash. After you pasted it his Flash and it should successfully flash the firmware. If it gives you an error or times out, unplug the phone and try a different USB port or USB cable. It's obviously recommended you use the one that came with the phone. My first attempt at MiFlash timed out and didn't flash anything. I tried a different USB port and then it flashed.
After it flashes the firmware, leave the phone plugged in and hold down the power button for about 10 seconds until it restarts out of EDL. From there you should have a working phone again with some exceptions. It'll be on an older firmware so I would recommend booting into stock recovery and factory resetting data and wiping your cache. Then restart the phone and do an OTA update to the latest firmware. After you reach the latest firmware you can then use the toolkit for whatever you need.
Sidenote, your English is very good considering you're Russian. No need to apologize because your post had no spelling errors. :highfive:
brian117 said:
I had a similar problem on my 2017U model after flashing a .zip that was supposed to remove the "bootloader is unlocked" screen that shows up after you unlock the bootloader. Long story short, the .zip wasn't meant for U models. Only G. So my phone was in a worse situation than yours and would not power on. You'll need to download an EDL recovery firmware .zip for your phone and place it within the toolkits folders manually and then go through the steps of the toolkit which I'll try to help you do.
First, download the full stock B09 (G) firmware from here. You can OTA update to the latest firmware after a successful flash. It's okay to flash an older firmware in this situation.
Once done, navigate to C:\Axon7Development\Axon7Toolkit\MiFlash\B09\ (copy/move the full .zip of the B09 firmware you downloaded in the first step into this folder) If the B09 folder doesn't exist under \MiFlash, create it manually.
Run the toolkit again from the start and type 11 "RESTORE TO STOCK/RECOVER FROM HARDBRICK (EDL)" and hit enter. On the next screen type in the number that will restore B09. It should tell you how to put the phone in EDL mode and automatically open MiFlash. Make sure to follow the steps and paste the directory path of the firmware in the top bar in MiFlash. After you pasted it his Flash and it should successfully flash the firmware. If it gives you an error or times out, unplug the phone and try a different USB port or USB cable. It's obviously recommended you use the one that came with the phone. My first attempt at MiFlash timed out and didn't flash anything. I tried a different USB port and then it flashed.
After it flashes the firmware, leave the phone plugged in and hold down the power button for about 10 seconds until it restarts out of EDL. From there you should have a working phone again with some exceptions. It'll be on an older firmware so I would recommend booting into stock recovery and factory resetting data and wiping your cache. Then restart the phone and do an OTA update to the latest firmware. After you reach the latest firmware you can then use the toolkit for whatever you need.
Sidenote, your English is very good considering you're Russian. No need to apologize because your post had no spelling errors. :highfive:
Click to expand...
Click to collapse
When I type in 11 I don't have any options, it forces me to download B10, but when it tries it fails.
Jazkade said:
When I type in 11 I don't have any options, it forces me to download B10, but when it tries it fails.
Click to expand...
Click to collapse
I haven't read what the other guy said, but basically you have to use miflash. just use my DFU unbrick guide but from the point where you short the testpad to enter EDL. But instead of opening the phone just put it in edl via adb reboot edl or holding vol+ - and inserting the cable
Jazkade said:
When I type in 11 I don't have any options, it forces me to download B10, but when it tries it fails.
Click to expand...
Click to collapse
Did you create the B09 folder in the MiFlash directory? I also had errors downloading firmwares through the toolkit, which is why I had to do it manually and move the firmware into the proper directory for the toolkit.
brian117 said:
Did you create the B09 folder in the MiFlash directory? I also had errors downloading firmwares through the toolkit, which is why I had to do it manually and move the firmware into the proper directory for the toolkit.
Click to expand...
Click to collapse
Yes I did
Choose an username... said:
I haven't read what the other guy said, but basically you have to use miflash. just use my DFU unbrick guide but from the point where you short the testpad to enter EDL. But instead of opening the phone just put it in edl via adb reboot edl or holding vol+ - and inserting the cable
Click to expand...
Click to collapse
Can you give me a link pls?
Choose an username... said:
I haven't read what the other guy said, but basically you have to use miflash. just use my DFU unbrick guide but from the point where you short the testpad to enter EDL. But instead of opening the phone just put it in edl via adb reboot edl or holding vol+ - and inserting the cable
Click to expand...
Click to collapse
Flashing in progress.. please may this work..
Oh yeis boiz, the phone is alive! And the main lol is, we have a guy that fixes devices for a living, and he was trashtalking that the Axon 7 is a trash phone and fixing it is a piece of cake, and he failed, and here I am thanks to you with a woring phone! I love you people, and xda in general!
EDIT: Seems you got it working. Congrats.
Jazkade said:
Oh yeis boiz, the phone is alive! And the main lol is, we have a guy that fixes devices for a living, and he was trashtalking that the Axon 7 is a trash phone and fixing it is a piece of cake, and he failed, and here I am thanks to you with a woring phone! I love you people, and xda in general!
Click to expand...
Click to collapse
Choose an username... said:
Click to expand...
Click to collapse
After I unlocked the bootloader via the toolkit by bkores, I get a message "To start android enter your password" even though it was a stock system with no password. Like I got every possible error and solved it and now this, just why?
Jazkade said:
After I unlocked the bootloader via the toolkit by bkores, I get a message "To start android enter your password" even though it was a stock system with no password. Like I got every possible error and solved it and now this, just why?
Click to expand...
Click to collapse
that's totally normal. Your internal storage is encrypted, you have to go into TWRP and format data (not wipe, format). Anyways by unlocking you lose all of your data so it's not like you lose anything
If it doesn't work, then you'll have to change the data partition's filesystem because it may be in F2FS. Change it back to ext4 if that happens
Choose an username... said:
that's totally normal. Your internal storage is encrypted, you have to go into TWRP and format data (not wipe, format). Anyways by unlocking you lose all of your data so it's not like you lose anything
If it doesn't work, then you'll have to change the data partition's filesystem because it may be in F2FS. Change it back to ext4 if that happens
Click to expand...
Click to collapse
I don't have TWRP, firs I Unlocked the bootloader, now I try to flash TWRP and get error due to the force encryption on Nougat, and I can't find a way to disable it, also now when I try to boot to stock recovery the led flashes for a milisecond and powers off.
Jazkade said:
I don't have TWRP, firs I Unlocked the bootloader, now I try to flash TWRP and get error due to the force encryption on Nougat, and I can't find a way to disable it, also now when I try to boot to stock recovery the led flashes for a milisecond and powers off.
Click to expand...
Click to collapse
Enter fastboot and type the command "fastboot erase userdata
Choose an username... said:
Enter fastboot and type the command "fastboot erase userdata
Click to expand...
Click to collapse
adb reboot fastboot and it just reboots normally.
Jazkade said:
adb reboot fastboot and it just reboots normally.
Click to expand...
Click to collapse
Well whatever then just install TWRP. Use controllerboy's guide
Choose an username... said:
Well whatever then just install TWRP. Use controllerboy's guide
Click to expand...
Click to collapse
idk how to downgrade to marshmellow.
Choose an username... said:
Well whatever then just install TWRP. Use controllerboy's guide
Click to expand...
Click to collapse
downgraded, unlocked, twrp is up and running
Related
The instructions are updated as of 11-20-17. Win7 only cause Win10 sucks and uses powershell and the fastboot commands don't work in powershell.
These are the proper files and procedures for installing Root, the latest Kernel, the best Superuser version and TWRP.
This is for NOUGAT 7.1.1. (and possibly beyond) There is a special procedeur to make flashtool work with the latest firmwares for Nougat ..
Before you Root and install TWRP you need to go back to my link and unlock bootloader..
You also need to download and install Android Studio Software and install it. Back to this portion of the install later.
You also need a special kernel to allow things on the phone to keep working.
This will work only for Nougat firmware.
You will need to download Boot img, TWRP img, SuperSu
Save TWRP and boot img files to the Android Platform folder in your PC here C:\Users\enter the current pc users log in name here\AppData\Local\Android\sdk\platform-tools . Save the Kernel zip and SUperSU zip file to an SD card and put the card inside your phone to access it through TWRP later in the process. Keep in mind that the Kernel may be updated. Check for updates herel here. Do a "date last modified" list of the files on that page by clicking on the grid view box on the upper right portion of the screen just under the "sign in" button. This helps you see what files have been updated in most recent order.
You will need to download the special Flashtool file here Install it.
Download the .jar patch file that makes the software version updated to the latest 9.23.2 and place it in this location C:\flashtools.
Now, download the special .fsc file and paste it in C:\Users"current user that is logged in"\.flashTool\devices\F81XX. Without this file you will not beable to update the device to nougat.
Goto C:\Flashtool\drivers and click on this file which was installed during the Flashtool installation.
Check off these boxes to install the drivers for the device you will be rooting. "Flash Boot Drivers, Flash Mode Drivers"
Now download and install these special ADB drivers to allow it to perform the Firmware update. Without it you wont beable to install the FTF file.
Open Sony Flash tool. Click on XI button. A window open. Click on Xperia Performance and then a small menu open under that. Choose F8132 ( i choose dual for my device)
If you can not get the newest firmware to show up for your device.( mine is 41.2.A.7.8 aka Nougat 7.1.1) then you can download it here Close Sony Flashtool.
Copy this FTF file and place it in folder C:\Users"The user you are currently logged into your pc with"\.flashTool\firmwares. Open Sony flash tool. Click on lightning bolt. Choose Flash mode in the small popup box. Window opens and shows your formware in the "firmwares" box. Click on plus symbol to the left of that firmware and it opens to the bottom to show the device model ( mine is F8132)/ Click on that plus symbol to the left of the model number to show the location of your firmware origination. Click on plus symbol and it then shows the firmware number 41.2.A.7.8. Click on the firmware and the entire window will populate a bunch of new options. If you want to wipe everythign on your phone then you need to check off the boxes "SSD and UserData" in the "wipe" box. Leave everythign else unchecked. Click the flash button at the bottom and it will start to prepare the files for installation onto yout device.
A window pops up that tells you to turn off your phone.
Turn your phone off. After its turned off, hold the volume down button while plugging the phone into your pc to get into fastboot mode. Your computer should be looking for the correct drivers to allow the device to work in this Flashboot mode. Once the flashing is done just close the flashtool. Turn your phone on. Go into settings and scroll down to "about phone then click on "build number" about 7 times. You will get a new optioon back in settings menu called "developer option". Click on that tabturn on "usb debugging" and turn off "verify apps over usb". Turn off phone.
Hold volum button UP this time while plugging phone back into pc.
Now go back to the folder C:\Users" name of user that is logged into the pc"\AppData\Local\Android\Sdk\platform-tools. You will open a cmd prompt in this folder by holding down your right mouse button and click on the shift key then release the mouse button. This will open a pop up window where you can choose to " open command window here" when the cmd window opens, copy and paste this "fastboot devices" press enter button, your computer should respond with this ......CB512A697c fastboot.......This lets you know that your phone is in the correct mode and ready to be programmed.
Now you will install the boot img by copy and pasting this in cmd line "fastboot flash boot boot.img" The PC should tell you OKAY with some other irrelevant info.
Now you will install the twrp img by copy and pasting this in cmd line "fastboot flash recovery TWRP-3.0.3-0-dora.img" The PC should tell you OKAY with some other irrelevant info.
Now you will install Kernel, and SuperSU. Turn on phone while pushing power button holding volume down button for about 5 secnds then release the bottom volum button then after 5 seconds release the power button to initiate TWRP.
Swipe to allow modifications then choose "Install" to install the zip files. Navigate to the SD card that has the kernel and SU zip files. Click on them to install. Reboot. TWRP might ask if you want to install the TWRP app before the phone starts to reboot. Just say no. After that, a few seconds later, the device reboots and then the Phone might go throw optimization process which takes some time. You will notice the counting of optimized files. Be patient.
When phone is booted and running, you might have to reinstall SuperSU via the Operating system as a APK like you would a normal app just to get root going. No big deal.
A caution...
When doing a backup with Twrp you should only backup System and Data
When doing a full restore, wipe only System, Data and the cache files. Do not ever delete your SDcard with the backups on it.
THIS IS THE VERY LAST UPDATE FOR ROOTING THE X Performance. IT IS NOUGAT 7.1.1
FORGET ABOUT ROOTING OREO>> ITS NOT GOING TO HAPPEN. PLUS IT IS NOT A DECENT UPDATE TO BE HONEST> IT JUST CHANGES A BUNCH OF MENUS AROUND AND LOCKS DOWN YOUR PHONE MORE>
Please do not upload my kernel to other hostings!
Official website for my kernel is
https://kernel.andro.plus/tone.html
So, if I was to relock my bootloader after installing TWRP and rooting, what would happen? Would TWRP go away? I'd like to let the phone OTA update to nougat, and you can't do that with an unlocked bootloader....
jakebriggs said:
So, if I was to relock my bootloader after installing TWRP and rooting, what would happen? Would TWRP go away? I'd like to let the phone OTA update to nougat, and you can't do that with an unlocked bootloader....
Click to expand...
Click to collapse
your phone will soft brick..or rather bootloop..if you're still on MM,do a nandroid backup..& here's what you do:
-relock phone using Flashtool.
-repair device using Xperia Companion(it will update automatically to Nougat).
-unlock phone again using Flashtool.
-install AndroPlus Kernel through command prompt(or you can also use Flashtool to do it.however you prefer).
-install TWRP recovery..you're all set!
P.S.
on steps i said(this is optional),you may not turn on your device along the process..that's what i do & i find it easier that way..goodluck!
Arturiuz! said:
your phone will soft brick..or rather bootloop..if you're still on MM,do a nandroid backup..& here's what you do:
-relock phone using Flashtool.
-repair device using Xperia Companion(it will update automatically to Nougat).
-unlock phone again using Flashtool.
-install AndroPlus Kernel through command prompt(or you can also use Flashtool to do it.however you prefer).
-install TWRP recovery..you're all set!
P.S.
on steps i said(this is optional),you may not turn on your device along the process..that's what i do & i find it easier that way..goodluck!
Click to expand...
Click to collapse
Thanks heaps! Now, to find a couple hours spare
Arturiuz! said:
your phone will soft brick..or rather bootloop..if you're still on MM,do a nandroid backup..& here's what you do:
-relock phone using Flashtool.
-repair device using Xperia Companion(it will update automatically to Nougat).
-unlock phone again using Flashtool.
-install AndroPlus Kernel through command prompt(or you can also use Flashtool to do it.however you prefer).
-install TWRP recovery..you're all set!
P.S.
on steps i said(this is optional),you may not turn on your device along the process..that's what i do & i find it easier that way..goodluck!
Click to expand...
Click to collapse
Following this left me with a phone that boots to a screen "To start Android, enter your password". I don't have a password to enter :/
jakebriggs said:
Following this left me with a phone that boots to a screen "To start Android, enter your password". I don't have a password to enter :/
Click to expand...
Click to collapse
that occured to me too!my apologies but i forgot mention about that..but you could try again that after you fixed/updated your phone using Xperia Companion to turn your phone first & set up everything.then unlock using Flashtool.install kernel & recovery.. :good:
Arturiuz! said:
that occured to me too!my apologies but i forgot mention about that..but you could try again that after you fixed/updated your phone using Xperia Companion to turn your phone first & set up everything.then unlock using Flashtool.install kernel & recovery.. :good:
Click to expand...
Click to collapse
I did try that - although, I set it up with a pin rather than a password. It didn't accept my pin when asking for the password.
Now I have a phone with a locked bootloader, running nougat, and I set it up with a password. I wonder if that password you use on the lock screen is the same password that Android is asking for when I unlock my bootloader?
I also could not seem to get the phone to boot into recovery after rebooting when I got the password screen. So weird....
jakebriggs said:
I did try that - although, I set it up with a pin rather than a password. It didn't accept my pin when asking for the password.
Now I have a phone with a locked bootloader, running nougat, and I set it up with a password. I wonder if that password you use on the lock screen is the same password that Android is asking for when I unlock my bootloader?
I also could not seem to get the phone to boot into recovery after rebooting when I got the password screen. So weird....
Click to expand...
Click to collapse
you can't use recovery or root your phone when bootloader is locked..could you try now unlock your phone using Flashtool?then install kernel & recovery?mind that data will be wiped..
Arturiuz! said:
you can't use recovery or root your phone when bootloader is locked..could you try now unlock your phone using Flashtool?then install kernel & recovery?mind that data will be wiped..
Click to expand...
Click to collapse
So if unlocking the boot loader wipes data, how can android ask for my password when I reboot? I am a little mystified at how this is supposed to work Rooting Marshmellow was easier than Nougat....
jakebriggs said:
So if unlocking the boot loader wipes data, how can android ask for my password when I reboot? I am a little mystified at how this is supposed to work Rooting Marshmellow was easier than Nougat....
Click to expand...
Click to collapse
true!MM was easier but Nougat is a bit complicated..however,you could still make changes on Nougat when phone is rooted.anyway,try again from the very beginning then this time after fixing phone using Xperia Companion,do the steps i mentioned..i myself couldn't figure out how it's asking for any password at first.AndroPlus also mentioned it before but didn't explain further.but it's alright coz i got it working now.
Arturiuz! said:
true!MM was easier but Nougat is a bit complicated..however,you could still make changes on Nougat when phone is rooted.anyway,try again from the very beginning then this time after fixing phone using Xperia Companion,do the steps i mentioned..i myself couldn't figure out how it's asking for any password at first.AndroPlus also mentioned it before but didn't explain further.but it's alright coz i got it working now.
Click to expand...
Click to collapse
I think my issue with the unknowable password after unlocking the bootloader on Nougat could have been fixed by wiping data+dalvik cache. I was having issues with the camera under nougat so I flagged trying to get it going and flashed MarshMellow. Once that was done, I got the bloody password prompt again, so I wiped data + cache and it booted correctly.
Anyway, gonna ignore Nougat until fastboot supports nougat
Issues with passwords kept / unknown and blocked are due to the fact the security portion is stored
next to the data partition area, in what we call the footer, and that area was wrong for you.
By wiping data completely (most reliably, a factory reset which will format the data partition),
the footer is also erased instead of simply deleting the files like a Wipe would do.
lost system?
I got as far as getting boot.img and twrp.img in my phone, and then appeared to lose my system since it stuck on the Sony logo and wouldn't boot into the system despite several tries. Idiot that I am, I panicked and come onto the forum to post a plead for help. I've managed to get my system back on now and feel very foolish, so just editing the post to remove the request for help. Thank you so much for the guide, very greatly appreciated! Looking forward to upgrading to Nougat.
Will this guide work with Nougat? I have a F8132 with 39.2.A.0.327
mongastein said:
I got as far as getting boot.img and twrp.img in my phone, and then appeared to lose my system since it stuck on the Sony logo and wouldn't boot into the system despite several tries. Idiot that I am, I panicked and come onto the forum to post a plead for help. I've managed to get my system back on now and feel very foolish, so just editing the post to remove the request for help. Thank you so much for the guide, very greatly appreciated! Looking forward to upgrading to Nougat.
Click to expand...
Click to collapse
Don't feel like a fool. I'm panicing right now.
Can flash boot.img and twrp.img and even enter twrp to flash su and kernel. But thats it. When done i reboot and i can pass SONY logo and enter bootanimation but it stucks here forever. Been trying with everything exept flashing official MM.
You did get the system back. So I'm the fool
---------- Post added at 07:45 AM ---------- Previous post was at 07:40 AM ----------
chiobesek said:
Will this guide work with Nougat? I have a F8132 with 39.2.A.0.327
Click to expand...
Click to collapse
Didn't for me. Have a softbricked phone in front of me since yesterday. Going to try to flash MM soon but my internet is terrible slow. Won't give up.
chiobesek said:
Will this guide work with Nougat? I have a F8132 with 39.2.A.0.327
Click to expand...
Click to collapse
It works if you get updated files. I struggled a bit before I finally extracted the boot.img from the AndroPlusKernel for my version which I flashed in fastboot and flashed the kernel and supersu in twrp. I think that's what did it. I was so eager to root that I missed that I was using MM-files at first. :silly:
Edit: oh I answered a pretty old post. Anyway, this is another way https://forum.xda-developers.com/xp...ment/mod-sony-stock-patcher-xperia-x-t3528148
Wimz3n said:
Don't feel like a fool. I'm panicing right now.
Can flash boot.img and twrp.img and even enter twrp to flash su and kernel. But thats it. When done i reboot and i can pass SONY logo and enter bootanimation but it stucks here forever. Been trying with everything exept flashing official MM.
You did get the system back. So I'm the fool
---------- Post added at 07:45 AM ---------- Previous post was at 07:40 AM ----------
Didn't for me. Have a softbricked phone in front of me since yesterday. Going to try to flash MM soon but my internet is terrible slow. Won't give up.
Click to expand...
Click to collapse
I ended up finding a way to downgrade to marshmallow following some instructions from from @sdugoten
The instructions are updated.. With proper files for the latest and greatest kernel and SuperSU and TWRP. NOUGAT Only .. Will not work for any other OS versions
AS flashtool does not work for 7.1.1 how to proceed to install nougat 7.1.1 and enable root and install twrp?
EDIT: Fixed! Big thanks to @S0wL , @bkores , @tamahouse02 and @tron1 for the help. I made a guide to help other people with the same problem:
Guide to get TWRP again HERE
Okay, it seems to me that I messed up kinda badly. The phone is fully operational, but after I got to 7.0 the stock recovery replaced good ol' TWRP... which left me with an unlocked bootloader and an useless recovery. I have no root, and that's pretty much the only thing that matters to me. I downloaded @bkores 's Axon7Toolkit but there is NO way to get fastboot on the damned thing. After the program tries to get to bl mode (I assume adb reboot bootloader?) the ZTE logo flashes and the unlocked BL image appears, then the phone starts as normal.
Same thing with the leaked 7.1.1, no difference.
I tried EDL, recovery, that shady factory test mode thing, no one gives fastboot... Any ideas as to why I can't get there??+
I suspect it may be something related to the OEM unlocking option in the dev options, but it is set to ON and greyed out. so no idea
Try the menu on the boot screen.
Choose an username... said:
Okay, it seems to me that I messed up kinda badly. The phone is fully operational, but after I got to 7.0 the stock recovery replaced good ol' TWRP... which left me with an unlocked bootloader and an useless recovery. I have no root, and that's pretty much the only thing that matters to me. I downloaded @bkores 's Axon7Toolkit but there is NO way to get fastboot on the damned thing. After the program tries to get to bl mode (I assume adb reboot bootloader?) the ZTE logo flashes and the unlocked BL image appears, then the phone starts as normal.
Same thing with the leaked 7.1.1, no difference.
I tried EDL, recovery, that shady factory test mode thing, no one gives fastboot... Any ideas as to why I can't get there??+
I suspect it may be something related to the OEM unlocking option in the dev options, but it is set to ON and greyed out. so no idea
Click to expand...
Click to collapse
Sounds like the issue is with the ROM like it is somehow blocking you from accessing bootloader mode. It's definitely not my toolkit.
Choose an username... said:
Okay, it seems to me that I messed up kinda badly. The phone is fully operational, but after I got to 7.0 the stock recovery replaced good ol' TWRP... which left me with an unlocked bootloader and an useless recovery. I have no root, and that's pretty much the only thing that matters to me. I downloaded @bkores 's Axon7Toolkit but there is NO way to get fastboot on the damned thing. After the program tries to get to bl mode (I assume adb reboot bootloader?) the ZTE logo flashes and the unlocked BL image appears, then the phone starts as normal.
Same thing with the leaked 7.1.1, no difference.
I tried EDL, recovery, that shady factory test mode thing, no one gives fastboot... Any ideas as to why I can't get there??+
I suspect it may be something related to the OEM unlocking option in the dev options, but it is set to ON and greyed out. so no idea
Click to expand...
Click to collapse
Feel the same, 7.1.1 stock recovery is evil, it keep coming back after flash twrp. LOL
Here what I didi to get twrp on 7.1.1:
1. Use axon7tool -w recovery (twrp of couse)
2. Watch closely the cmd, when it said "Successful!","Reboot in 5 second" - unplug your phone
3. Use Volume Up + Power to get to recovery (twrp)
4. Mount > Mount System (dont check read only)
5. Flash something - I don't know - But I get the feeling that it stop stock recovery coming back - I personally flash Chinese Modem (because I have to ))
6. Reboot system
@bkores Yeah I'm pretty sure it's not your toolkit since I can't access it even with key comb, adb, option on the unl bl page...
@lafester Nope, tried many times. It just boots to normal whenever I select fastboot
@tamahouse02 Well I believe that should work, but I can't get axon7tool not to crash... I'll keep trying, maybe it's a driver or sth.
Choose an username... said:
@bkores Yeah I'm pretty sure it's not your toolkit since I can't access it even with key comb, adb, option on the unl bl page...
@lafester Nope, tried many times. It just boots to normal whenever I select fastboot
@tamahouse02 Well I believe that should work, but I can't get axon7tool not to crash... I'll keep trying, maybe it's a driver or sth.
Click to expand...
Click to collapse
Have you restart after install zadig driver?
1. From system: adb reboot edl
2. Install zadig driver
3. Hold "Volume Up + Power"
4. Enter system again: adb reboot edl
5. axon7tool -w recovery
tamahouse02 said:
Have you restart after install zadig driver?
1. From system: adb reboot edl
2. Install zadig driver
3. Hold "Volume Up + Power"
4. Enter system again: adb reboot edl
5. axon7tool -w recovery
Click to expand...
Click to collapse
yes, like 4 times already. I even used the stock Qualcomm COM3 drivers... no dice.
the thing is that I had to do the same when I did the stuff on android 6 and it worked after some time. I even wrote the procedure on another thread xd
Choose an username... said:
yes, like 4 times already. I even used the stock Qualcomm COM3 drivers... no dice.
the thing is that I had to do the same when I did the stuff on android 6 and it worked after some time. I even wrote the procedure on another thread xd
Click to expand...
Click to collapse
Not same my axon7tool. I use this https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
Bootloader Mode is Disable/strip in G variant, and if this is how ZTE is headed to future updates it seems like U will have a Disable Bootloader Mode as well.
If you guy can rollback to MM , you can Unlock there using @bkores tool.
DrakenFX said:
Bootloader Mode is Disable/strip in G variant, and if this is how ZTE is headed to future updates it seems like U will have a Disable Bootloader Mode as well.
If you guy can rollback to MM , you can Unlock there using @bkores tool.
Click to expand...
Click to collapse
I was thinking about that, but does mifavor let you roll back from an SD update? I'll try later, but i doubt it.
Besides from that is there any way to flash stuff from the stock recovery? It tells me that ZIPs have to be signed only
tamahouse02 said:
Feel the same, 7.1.1 stock recovery is evil, it keep coming back after flash twrp. LOL
Here what I didi to get twrp on 7.1.1:
1. Use axon7tool -w recovery (twrp of couse)
2. Watch closely the cmd, when it said "Successful!","Reboot in 5 second" - unplug your phone
3. Use Volume Up + Power to get to recovery (twrp)
4. Mount > Mount System (dont check read only)
5. Flash something - I don't know - But I get the feeling that it stop stock recovery coming back - I personally flash Chinese Modem (because I have to ))
6. Reboot system
Click to expand...
Click to collapse
In step 1, which TWRP version did you use? The latest 3.1.0.-0 ?
dnlilas said:
In step 1, which TWRP version did you use? The latest 3.1.0.-0 ?
Click to expand...
Click to collapse
Official 3.0.4.1
@tamahouse02
The latest "official" TWRP is at TWRP site https://twrp.me/devices/zteaxon7.html , version 3.1.0-0.
Is there any problem using it instead of the previous "official" 3.0.4.1 ?
Edit: I also read on TWRP site:
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
This is in sync with your information requiring to reboot immediately to TWRP (step 2 and 3).
dnlilas said:
@tamahouse02
The latest "official" TWRP is at TWRP site https://twrp.me/devices/zteaxon7.html , version 3.1.0-0.
Is there any problem using it instead of the previous "official" 3.0.4.1 ?
Edit: I also read on TWRP site:
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
This is in sync with your information requiring to reboot immediately to TWRP (step 2 and 3).
Click to expand...
Click to collapse
I use 3.0.4.1 because I flash plenty things before without any issue, so I keep using it.
After write recovery by axon7tool, it's reboot automatically and override the recovery, that why I have to unplug to stop the reboot, and also flash all I can - fortunaeally it also stop recovery be overrided
@tamahouse02 sorry to ask, but is the a7tool of the link a fixed version? how does it differ from the one i have?
I've been in the same situation like you @Choose an username... Updated to nougat on G model and I had not bootloader. This is what I did :
1. Downloaded the tool from here https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
2. Installed the driver using the install driver option that you can choose once you connect you phone to your computer
3. Use the tool to perform the unlock bootloader command again even though you have unlocked it before
4. Use the tool to install twrp, it will boot the phone in twrp
5. Flash Supersu before you boot the system first time after flashing twrp
5. Install whatever version of android want after
@S0wL Funny, I had to use Zadig to make it work. I'll try r n, thx
Choose an username... said:
@S0wL Funny, I had to use Zadig to make it work. I'll try r n, thx
Click to expand...
Click to collapse
Use Zadig then and let me know if it worked
@S0wL I can't use bootloader unlock on it, says "This option does not support your device!"
How did you do this??
Choose an username... said:
@tamahouse02 sorry to ask, but is the a7tool of the link a fixed version? how does it differ from the one i have?
Click to expand...
Click to collapse
I try your version once, but it seems not work for me, so I keep using the old one.
---------- Post added at 03:42 AM ---------- Previous post was at 03:39 AM ----------
Choose an username... said:
@S0wL I can't use bootloader unlock on it, says "This option does not support your device!"
How did you do this??
Click to expand...
Click to collapse
I thought you had already unlocked bootloader? Why have you done it twice?
I need help! Here’s the story. Sorry for the lengthy post. TL;DR at the bottom..
- Was on B32, unlocked BL, TWRP installed, rooted with SuperSU
- Updated to B35, but lost TWRP and root (I don’t know how, but I assume I must have wiped the wrong things? - system? - I’m clearly a novice)
- Now I’m on B35 with an unlocked BL, but despite days of searching and researching, I can’t for the life of me figure out how to get TWRP reinstalled. I want to have TWRP before trying Magisk (have never used Magisk before, but would like to try it this time instead of SuperSU)
- From my Mac, using terminal, adb recognizes my devices.
- “adb reboot boot loader” gets me to a list of options “power off, restart, recovery, fastboot, back to previous page”. Choosing fastboot simply restarts the phone. What should “fastboot mode” look like?
- I tried flashing TWRP via adb while on this page and terminal stopped at “waiting for any device” and did nothing
My conclusion is that I need to downgrade to whatever latest version allows fastboot commands to work properly? Is this B15? If so, is the only available B15 zip the one that is on the ZTE website? Do I just wipe data/dalvick/cache and flash this zip?
Do I not need a Bootstock and Systemstock like @DrakenFX usually posts? That’s how I’m used to doing any updates.
Thank you all for your help, both past and present!
TL;DR: Would like to downgrade from B35 to B15 so that I can install twrp and root again. What’s the best way to do this and where can I find the appropriate files?
alajoy said:
I need help! Here’s the story. Sorry for the lengthy post. TL;DR at the bottom..
- Was on B32, unlocked BL, TWRP installed, rooted with SuperSU
- Updated to B35, but lost TWRP and root (I don’t know how, but I assume I must have wiped the wrong things? - system? - I’m clearly a novice)
- Now I’m on B35 with an unlocked BL, but despite days of searching and researching, I can’t for the life of me figure out how to get TWRP reinstalled. I want to have TWRP before trying Magisk (have never used Magisk before, but would like to try it this time instead of SuperSU)
- From my Mac, using terminal, adb recognizes my devices.
- “adb reboot boot loader” gets me to a list of options “power off, restart, recovery, fastboot, back to previous page”. Choosing fastboot simply restarts the phone. What should “fastboot mode” look like?
- I tried flashing TWRP via adb while on this page and terminal stopped at “waiting for any device” and did nothing
My conclusion is that I need to downgrade to whatever latest version allows fastboot commands to work properly? Is this B15? If so, is the only available B15 zip the one that is on the ZTE website? Do I just wipe data/dalvick/cache and flash this zip?
Do I not need a Bootstock and Systemstock like @DrakenFX usually posts? That’s how I’m used to doing any updates.
Thank you all for your help, both past and present!
TL;DR: Would like to downgrade from B35 to B15 so that I can install twrp and root again. What’s the best way to do this and where can I find the appropriate files?
Click to expand...
Click to collapse
I'm not sure where you read all that BS, but if your bootloader is unlocked then you can install TWRP via EDL (Or fastboot if you have it). No need to downgrade for anything :laugh: in the past you would have needed to downgrade in order to unlock the bootloader, now it's not even needed
Download EDL Tool by djkuz and install TWRP with that one. Or you can use axon7tool by tennear, but it's much more finicky and ran entirely by commands (no UI).
And just to avoid more trouble, DO NOT LOCK THE BOOTLOADER! You do that with the system even barely modified and you brick the phone. A bunch of people tried to do something, got scared because they made a simple correctable mistake and just locked the bootloader thinking everything would get restored to stock - doesn't work that way.
Not saying you will do this, but I've seen about 4 or 5 people that started just like you and ended up doing that
Choose an username... said:
I'm not sure where you read all that BS, but if your bootloader is unlocked then you can install TWRP via EDL (Or fastboot if you have it). No need to downgrade for anything :laugh: in the past you would have needed to downgrade in order to unlock the bootloader, now it's not even needed
Download EDL Tool by djkuz and install TWRP with that one. Or you can use axon7tool by tennear, but it's much more finicky and ran entirely by commands (no UI).
And just to avoid more trouble, DO NOT LOCK THE BOOTLOADER! You do that with the system even barely modified and you brick the phone. A bunch of people tried to do something, got scared because they made a simple correctable mistake and just locked the bootloader thinking everything would get restored to stock - doesn't work that way.
Not saying you will do this, but I've seen about 4 or 5 people that started just like you and ended up doing that
Click to expand...
Click to collapse
Wow, thanks so much for responding to this. Sounds like this should be easy! A couple of questions before I go about following your advice:
1). Do I download EDL Tool to my computer or phone??
2). If I'm downloading it to my computer, does it matter that I'm using a mac?
Thanks again for your help!
alajoy said:
Wow, thanks so much for responding to this. Sounds like this should be easy! A couple of questions before I go about following your advice:
1). Do I download EDL Tool to my computer or phone??
2). If I'm downloading it to my computer, does it matter that I'm using a mac?
Thanks again for your help!
Click to expand...
Click to collapse
Oh, skipped that part. EDL Tool is a .bat. I'm pretty sure you won't be able to run it on a Mac. If you can find a Windows PC somewhere to do this, it'd be much better...
But there's another way.
Issuing "adb reboot bootloader" effectively sends you into fastboot. That list you mentioned is fastboot (if it says "Start" in green, and you can scroll that, it is fastboot). Just use fastboot from the pc: Put TWRP on the fastboot folder on the PC, then issue "fastboot flash recovery twrp.img" with "twrp.img" being whatever the twrp file name is. After that issue "fastboot reboot recovery". And as soon as you are on TWRP, DON'T GET OUT OF IT. Just wipe data, system, caches; then flash a system (e.g. b10 bootstack and stocksystem), then also flash Magisk, and THEN boot to system
Choose an username... said:
Oh, skipped that part. EDL Tool is a .bat. I'm pretty sure you won't be able to run it on a Mac. If you can find a Windows PC somewhere to do this, it'd be much better...
But there's another way.
Issuing "adb reboot bootloader" effectively sends you into fastboot. That list you mentioned is fastboot (if it says "Start" in green, and you can scroll that, it is fastboot). Just use fastboot from the pc: Put TWRP on the fastboot folder on the PC, then issue "fastboot flash recovery twrp.img" with "twrp.img" being whatever the twrp file name is. After that issue "fastboot reboot recovery". And as soon as you are on TWRP, DON'T GET OUT OF IT. Just wipe data, system, caches; then flash a system (e.g. b10 bootstack and stocksystem), then also flash Magisk, and THEN boot to system
Click to expand...
Click to collapse
"adb reboot bootloader" takes me to the start up screen that says "your device software cannot be checked for corruption..." etc. and gives you 5 sec to either press up or down on volume keys to get to list: “power off, restart, recovery, fastboot, back to previous page”, but the list is all white. If I select "fastboot" it reboots the phone and starts that cycle over again at the "your device software cannot be checked for corruption..." etc page.
Nowhere am I given a chance to use fastboot commands. I'm never on the page with the green "Start".
..This all seemed a lot simpler on my Nexus 5..
Thanks for your help/patience.
alajoy said:
"adb reboot bootloader" takes me to the start up screen that says "your device software cannot be checked for corruption..." etc. and gives you 5 sec to either press up or down on volume keys to get to list: “power off, restart, recovery, fastboot, back to previous page”, but the list is all white. If I select "fastboot" it reboots the phone and starts that cycle over again at the "your device software cannot be checked for corruption..." etc page.
Nowhere am I given a chance to use fastboot commands. I'm never on the page with the green "Start".
..This all seemed a lot simpler on my Nexus 5..
Thanks for your help/patience.
Click to expand...
Click to collapse
I thought you had fastboot since you described the 5 seconds screen and both are very similar. It's normal not to have it though.
I think there's some version of axon7tool for Linux but I'm not sure at all. The best way would be to find a Windows computer.
I wonder how you actually installed TWRP the first time? Via fastboot?
As soon as you get TWRP you should be able to run a few commands to get fastboot back just to have it around.
Choose an username... said:
I thought you had fastboot since you described the 5 seconds screen and both are very similar. It's normal not to have it though.
I think there's some version of axon7tool for Linux but I'm not sure at all. The best way would be to find a Windows computer.
I wonder how you actually installed TWRP the first time? Via fastboot?
As soon as you get TWRP you should be able to run a few commands to get fastboot back just to have it around.
Click to expand...
Click to collapse
I have adb and fastboot installed on my Mac and I can't remember how I got it working on my phone in the first place, but I've only ever used a Mac for all this. Terminal recognizes my device and responds to commands until I try "fastboot flash recovery twrp.img" then it says "<waiting for any device>" and does nothing.
Thanks again for the help. I'll keep hunting though. I don't have access to any Windows computer.
Cheers
Current scenario: I can only boot into Android Recovery.
Options on screen:
.Reboot system rom
.Reboot to bootloader
.Apply update from ADB
.Apply update from SD card
.Wipe data/factory reset
.Wipe cache partition
.View recovery logs
.Power Off
Select "apply udate from ADB" only allows me ADB sideload. Not sure how to sideload TWRP. Selecting any rom gives me signature issue.
When I select "apply update from ADB", Windows 10 devmgmt.msc shows "Universal Serial Bus devices: ZTE A2017U".
I cannot boot to get any serial port connection.
Your assistance is appreciated!
itsmeinarizona said:
Current scenario: I can only boot into Android Recovery.
Options on screen:
.Reboot system rom
.Reboot to bootloader
.Apply update from ADB
.Apply update from SD card
.Wipe data/factory reset
.Wipe cache partition
.View recovery logs
.Power Off
Select "apply udate from ADB" only allows me ADB sideload. Not sure how to sideload TWRP. Selecting any rom gives me signature issue.
When I select "apply update from ADB", Windows 10 devmgmt.msc shows "Universal Serial Bus devices: ZTE A2017U".
I cannot boot to get any serial port connection.
Your assistance is appreciated!
Click to expand...
Click to collapse
Of course you can't sideload TWRP... Things would be much easier
You left out a rather important piece of info. Is your phone unlocked? Do you have OEM unlocking or usb debugging enabled?
Also, the current scenario is nice to know, but how did you get there?? ?
From the MiFavor recovery you can only install MiFavor ROMs that have been signed by ZTE, so no luck there. You have 3 things to try:
-Factory reset and see if it works. Honestly not knowing what the heck you did doesn't help, but if it suddenly entered the recovery without you touching anything, then you will probably recover the phone by formatting your data.
-Turn it off, then hold Vol+ and Vol- together and connect the USB cable (should be connected to your PC on the other end). The phone will either flash a red light and stay black or keep the red light on. If the red light stays on, get the MultiDL tool from raystef and use it to enter EDL, if the red light went off it already was in EDL. Then use EDL Tool by djkuz with a package corresponding to your phone model to rewrite the system
-Tinker with the official update.zip files and an SD card (or adb sideload). The sd card method is much more reliable than adb sideload, so get one if you will try the official update method
Choose an username... said:
You left out a rather important piece of info. Is your phone unlocked? Do you have OEM unlocking or usb debugging enabled?
Also, the current scenario is nice to know, but how did you get there??
Click to expand...
Click to collapse
Thanks! I'll try your suggestions and report back.
As for how I got here, I previously only had issues and ran MiFlash to get TWRP and access to the SD-Card. I then installed A2017Uv1.1.0B35_Bootstack_by_DrakenFX.zip and then A2017Uv1.1.0B35_StockRecovery_by_DrakenFX.zip.
Not sure what I did incorrect.
I'll spend a few days trying your suggestions. Again .. Thanks for your suggestions.
itsmeinarizona said:
Thanks! I'll try your suggestions and report back.
As for how I got here, I previously only had issues and ran MiFlash to get TWRP and access to the SD-Card. I then installed A2017Uv1.1.0B35_Bootstack_by_DrakenFX.zip and then A2017Uv1.1.0B35_StockRecovery_by_DrakenFX.zip.
Not sure what I did incorrect.
I'll spend a few days trying your suggestions. Again .. Thanks for your suggestions.
Click to expand...
Click to collapse
What were you trying to accomplish by flashing those two files? The bootstack is part of the official update files, you shouldn't have to use them at all unless you are using custom ROMs.
You can use EDL Tool to get TWRP back, instead of reflashing stock which is usually a huge file. But download a full EDL file anyways, it might save your arse someday
I have a old phone that had been stuck at this state for a while,
`orange state, your device has been unlocked and can't be trusted. Your device will boot in 5 seconds`
Should I follow this guide to un-brick it?
https://forum.xda-developers.com/le-2/how-to/repair-hard-bricked-phone-x52x-sd-t3648348
I have tried to follow the guide but after pressing volume up and down button the phone does not boot. Only shows it is in orange state.
Also if I hold the volume down button and the power button, it shows booting in fastboot.
But the FlashOne app cannot detect any phone.
What should I do ??:crying::crying::crying::crying:
mrchow19910319 said:
I have tried to follow the guide but after pressing volume up and down button the phone does not boot. Only shows it is in orange state.
Also if I hold the volume down button and the power button, it shows booting in fastboot.
But the FlashOne app cannot detect any phone.
What should I do ??:crying::crying::crying::crying:
Click to expand...
Click to collapse
What should I do? You need to read, the answers to your questions are here a million times over. Always do your homework first. Also thank someone who helps you. Otherwise they will not continue helping you.
FlashOne: Why are you using FlashOne? You are not bricked. Also FYI, if using FlashOne , you have to be in EDL mode. not fastboot.
Now here is probably good news, since you can enter fastboot then you are very likely just fine,and you are definitely not bricked. However, you will probably end up losing any files that you had on the phone, because the user data( storage ) will most likely need to be formatted, (type yes reboot to recovery)
So my instructions are to help get your phone working again, not to recover data. Unfortunately, you didn't provide much information so I have to assume some things.
Is the bootloader unlocked?
Have you flashed custom roms before?
Which phone do you have? A Leeco X5?? A Leeco X6??
Let guess and say that maybe bootloader is unlocked, you are asking a question on XDA so maybe that is a safe guess?
What you need to do is use ADB or the the Tool all in One and flash Recovery and root. Here comes the reading part again, I can't explain everything or I will be here all day. I assume that you know how what Recovery and root is?
Download the correct TWRP Recovery for your device, if you don't know your way around ADB too well.
You can use Mauronofrio's "TOOL ALL IN ONE" for removing encryption, installing TWRP, Root, your ROM, Gapps, and even to restore to stock Recovery, or to flash a stock Rom
Read that thread for instructions or for any questions.
If your device not recognized it is a usb driver issue, ensure that device drivers are installed and You will need to reinstall the Google USB driver, and while you are at it check to make sure adb is up to date. The All in One tool can do all of this for you, its with the advanced menu section. ** You will need to temporarily disable Windows defender for installation. **
Use the All in One tool to flash Recovery, then boot to recovery.
Ensure that you have TWRP installed permanently by rebooting to Recovery and then rooting the phone.
Always reboot to Recovery and check the boxes to install TWRP when rebooting to recovery
To remove encryption you will always need to format the storage
Not wipe >> Choose Format > type yes> Reboot to Recovery)**
(If you see a message that says there is no OS installed are you sure> Click Yes, then reboot to Recovery, ignore message about no OS)
When you reboot to recovery swipe to be able to read and write to the device.
Use an OTG Usb adapter to connect a USB to your phone and flash your prefered rom, Gapps, and root. Reboot to recovery, thenn reboot to system. If you were successful, the error message will be gone and you will be able to set up the phone.
As mentioned the tool will help you with installing your rom, Gapps, and root.
The All in One Tool can completely restore your phone to stock if absolutely needed. It actually links to Mauronofrio's server and it has all of the significant EUI Stock Roms, in case you want to restore the stock rom.
Hopefully this helps you, Good luck.
tsongming said:
.
Click to expand...
Click to collapse
thank you so much for the in depth explanation.
sorry for the super delayed reply.
I will try to follow the instruction and will update here soon.
again thank you.
I have the same problem with umidigi bison, I tried to root with the mtkroot tool v2.5.8, the process ended correctly but when I turned on it showed orange, the problem is that I cannot enter with any combination of keys, it does not recognize adb, please help