Please! If someone can help me. I did step by step correctly and my le max 2 still with original recovery. All cmd messages are successful, but when I turn on recovery mode, this is the original EUI version. I wanted to use some rom of you but without the TWRP I can not. Some help?
lucasnoman said:
Please! If someone can help me. I did step by step correctly and my le max 2 still with original recovery. All cmd messages are successful, but when I turn on recovery mode, this is the original EUI version. I wanted to use some rom of you but without the TWRP I can not. Some help?
Click to expand...
Click to collapse
If you have your device rooted you can download rashr from the play store and flash the recovery.img from there
moto999999 said:
If you have your device rooted you can download rashr from the play store and flash the recovery.img from there
Click to expand...
Click to collapse
Unfortunately he is not. I solve the problem with unrecognized device, but it always come back. In this post: https://forum.xda-developers.com/le-max-2/development/recovery-twrp-3-0-2-0-unofficial-t3443611
The author says: "OTG is working for some people but not for others also some readers and flash drives are not being seen. Will look into fixing it."
This is kinda my problem. For now i'm using 19s indian stock
Do you immediatly reboot into recovery after flashing TWRP? If not, the Stock Recovery will be restored and twrp is getting deleted again.
if you type "fastboot reboot" just hold the "volume up" key at this moment until you're in twrp...
Antisound said:
Do you immediatly reboot into recovery after flashing TWRP? If not, the Stock Recovery will be restored and twrp is getting deleted again.
if you type "fastboot reboot" just hold the "volume up" key at this moment until you're in twrp...
Click to expand...
Click to collapse
Yes, I did it. But a blue screen appear fast and my smartphone turns off. It does not go into recovery at all, only after I start the phone normally. Funny that I only get message of success since the release of the bootloader until the installation of twrp.
Have you tried "fastboot boot <recovery.img>"?
sudloa said:
Have you tried "fastboot boot <recovery.img>"?
Click to expand...
Click to collapse
I forget to mention. After the "successful" twrp install, the device is not recognized. What I mean: "List of devices attached" is blank. So I can't use this command.
lucasnoman said:
I forget to mention. After the "successful" twrp install, the device is not recognized. What I mean: "List of devices attached" is blank. So I can't use this command.
Click to expand...
Click to collapse
fastboot could use in fastboot mode (shutdown then vol down + power) only and windows sohuld recognize this.
But I think your adb usb driver got conflict somehow.
You can try "usbdeview" to uninstall all adb usb drivers then use some knid of universal adb usb driver installer.
Antisound said:
Do you immediatly reboot into recovery after flashing TWRP? If not, the Stock Recovery will be restored and twrp is getting deleted again.
if you type "fastboot reboot" just hold the "volume up" key at this moment until you're in twrp...
Click to expand...
Click to collapse
This is the key part I have missed as well !!!!!!!!!!!!!!!!!!!!!!!!!!!!
Along with the AT USB unlock code (Dial *#*#76937#*#*) to allow ADB
Thank you :laugh:
---------- Post added at 11:45 PM ---------- Previous post was at 11:40 PM ----------
lucasnoman said:
Unfortunately he is not. I solve the problem with unrecognized device, but it always come back. In this post: https://forum.xda-developers.com/le-max-2/development/recovery-twrp-3-0-2-0-unofficial-t3443611
The author says: "OTG is working for some people but not for others also some readers and flash drives are not being seen. Will look into fixing it."
This is kinda my problem. For now i'm using 19s indian stock
Click to expand...
Click to collapse
Hi, You should TITLE your post Why does TWRP not stay resident ?
paulsnz2 said:
This is the key part I have missed as well !!!!!!!!!!!!!!!!!!!!!!!!!!!!
Along with the AT USB unlock code (Dial *#*#76937#*#*) to allow ADB
Thank you :laugh:
---------- Post added at 11:45 PM ---------- Previous post was at 11:40 PM ----------
Hi, You should TITLE your post Why does TWRP not stay resident ?
Click to expand...
Click to collapse
You're Welcome
Antisound said:
You're Welcome
Click to expand...
Click to collapse
I have the 820. Could NOT get windows to see this phone on stock rom. Don't recall exact steps I took, but I do remember the ADB feature within TWRP saved my day. Windows would see the phone in TWRP recovery adb mode, but could never get windows to adb connect with stock rom.
Hey people, sry I'm coming back now. Lightning struck my street and burned my pc. But I come back with another problem, when I connect my phone to the pc nothing happens. I mean, I can't transfer cause MTP doesn't work. I tried install unninstall and install again adb, and all the drivers but it did not work. So I'll need to fix this to try to install twrp again
Guys! I was being too stupid! I found my mistake... I was using another smartphone twrp... So, for who are having same issue, pay attention to this. But, thanks everybody and sry for this hahaha
Related
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
osikiri said:
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
Click to expand...
Click to collapse
My watch is now bricked because I have no way to get out of "adb sideload" mode...how did you get out of that mode? please tell me.
TjPhysicist said:
My watch is now bricked because I have no way to get out of "adb sideload" mode...how did you get out of that mode? please tell me.
Click to expand...
Click to collapse
I pushed the reset button on the back(the silver one right above the charging connectors) with a pen for about 10 seconds, and it rebooted.
osikiri said:
I pushed the reset button on the back(the silver one right above the charging connectors) with a pen for about 10 seconds, and it rebooted.
Click to expand...
Click to collapse
Wow ok, that's a LOT longer than I'm used to with other devices...THANK GOD I thought I had bricked it completely.
Anyway, now i have to figure out a way to get adb to work in sideload,...i mean CLEARLY it's possible lots of others doing it..
---------- Post added at 08:26 AM ---------- Previous post was at 07:41 AM ----------
TjPhysicist said:
Wow ok, that's a LOT longer than I'm used to with other devices...THANK GOD I thought I had bricked it completely.
Anyway, now i have to figure out a way to get adb to work in sideload,...i mean CLEARLY it's possible lots of others doing it..
Click to expand...
Click to collapse
Ok, does anyone know how to get my computer to recognise my watch in recovery mode? It's not about 'driver' the computer plain doesn't recognise that anything is plugged in at all.
I know the post is quite old already, but I experience exactly the same phenomenon...
I tried multiple PCs Linux and Windows,but non of them recognized the watch (neither on 4.4W1 nor on 4.2W2).
Anyone any idea?
Wikiwix said:
I know the post is quite old already, but I experience exactly the same phenomenon...
I tried multiple PCs Linux and Windows,but non of them recognized the watch (neither on 4.4W1 nor on 4.2W2).
Anyone any idea?
Click to expand...
Click to collapse
I believe u need to update the drivers.....I always go-to device manager...update driver..hit select from list..and choose android adb....
Sent from my LGLS990 using XDA Free mobile app
mrkrabs said:
I believe u need to update the drivers.....I always go-to device manager...update driver..hit select from list..and choose android adb....
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
The problem, as @osikiri stated, is that the device does not get recognized at all (no unknown devices in devicemanager and the sound that comes on plugging in a device does not come as well). Furthermore, afaik Linux does not even need any drivers
Had the same issue today... and the only way out way battery death and recharge
JaceAlvejetti said:
Had the same issue today... and the only way out way battery death and recharge
Click to expand...
Click to collapse
If this really helps (seems weird): I guess the exact setting could be necassary:
You simply ran out of battery while the watch was running(not recovery or fastboot) and then plugged it in and went directly (or not?) to the recovery?
Thanks in advance, would be really great to fix this!
Anyone ever find a fix to this? I'm trying to manually install the 5.0 update and I'm having the same issue. Every post I find with search tells me to update drivers but I'm on a Mac that doesn't even use ADB drivers. I've updated the SDK.
MSigler said:
Anyone ever find a fix to this? I'm trying to manually install the 5.0 update and I'm having the same issue. Every post I find with search tells me to update drivers but I'm on a Mac that doesn't even use ADB drivers. I've updated the SDK.
Click to expand...
Click to collapse
I'm doing the same thing and having the same issues!
Yeah, same issue for me as described.
Windows (Win7 x64 for me) doesn't even realise that the device is connected when it is in recovery mode. Although it will connected properly when booted normally.
+1 Any ideas?
Same issue for me. I've tried removing and replacing it on the cradle, killing and restarting the adb server, entering recovery by the touchscreen or by the adb/fastboot commands, clearing debugging keys, etc... Anybody have any other ideas?
---------- Post added at 07:25 PM ---------- Previous post was at 06:46 PM ----------
Ok, so it appears that the recovery img on 4.4w2 broke adb support or something. There are a few threads that suggest you can root and flash it or just wait for the OTA. We'll see whether I get the OTA before I have time to try this out.
Lollipop OTA Update: Download and How-To (Root Required)
I made a script that roots and updates your watch to 5.0.1 in a click.
[UTILITY][RESTORE][UNLOCK][ROOT] LG G Watch Tool
My way of doing it
osikiri said:
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
Click to expand...
Click to collapse
I've similar problem, and I've spent almost 3 hours to find the solution. I found that following solution work for me:
http://forum.xda-developers.com/g-watch-r/development/manual-ota-update-root-t2969845
I've changed the step slightly according to the comments inside the thread:
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot boot recovery.img)
// Do Not Flash 5.0.2 stock recovery
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
//you might have to reinstall the ADB drivers, just follow the simple step to install ADB driver
Done.
fi thought it was finally the solution, but fastboot oem unlock bricked my sony smartwatch3. I see tomorrow if with my windows pc i can fix with sony companion, otherwise i'll have to use the warranty
willisc said:
I've similar problem, and I've spent almost 3 hours to find the solution. I found that following solution work for me:
http://forum.xda-developers.com/g-watch-r/development/manual-ota-update-root-t2969845
I've changed the step slightly according to the comments inside the thread:
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot boot recovery.img)
// Do Not Flash 5.0.2 stock recovery
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
//you might have to reinstall the ADB drivers, just follow the simple step to install ADB driver
Done.
Click to expand...
Click to collapse
Already posted this 5 times on 3 sites and just not getting a lot of help. If it's bricked, fine, tell me. If it can be fixed, give me ideas.
I can't flash the bootloader or boot in any possible way. not through adb, not through tool kit, not through nexus 7 restore, nothing.
I can access fastboot mode (power+vol down) but nothing else. Standard power on gets stuck on google screen. It is unlocked. I have tried 3 different USB ports and 6 cables with no change.
No BS please, either Yes it's bricked sorry or No, it's not bricked, here are some ideas.
now i see that i'm not alone
same problem here, nobody ? It's a powerfull tablet, maybe now is going to be a powerfull paperweight, big paperweight, so sad.
can you boot into download mode if u can then
1.put your device into download mod 2.download the official firmware for your device on your computer
3.connect yor phone into your computer and flash it
if you can't boot into download mod then sorry I think it's bricked try to bring it to a service center
Sent from my SM-N7505 using XDA Free mobile app
pls answer me so I can help you
I couldn't help myself... I love my Nexus 7.
mrdownboy said:
I couldn't help myself... I love my Nexus 7.
Click to expand...
Click to collapse
LOL
and
zidozido22, i can boot just in fastboot mode
j4k0 said:
LOL
and
zidozido22, i can boot just in fastboot mode
Click to expand...
Click to collapse
Does the PC recognize? If you run the "fastboot devices" does it return a serial number? These things are pretty difficult to hard brick and if you can still get to the bootloader, then chances are it is recoverable. It helps to mention what you did for it to get to this state as well.
es0tericcha0s said:
Does the PC recognize? If you run the "fastboot devices" does it return a serial number? These things are pretty difficult to hard brick and if you can still get to the bootloader, then chances are it is recoverable. It helps to mention what you did for it to get to this state as well.
Click to expand...
Click to collapse
yes, it sends the serial number but when I had tried to flash it then it returns an error.
.***now im trying again with SkipSoft Android Toolkit, but it is stuck waiting for adb mode
before that state, it was charging, just that.
The tablet got Android 5 from OTA, and then android 5.1, i was using it as normal, but one day, while it was charging, it just show the google logo (name) and the lock down.
My 2012 wifi did that exactly. I downloaded wugfresh Nexus Root Toolkit yours can be d/loaded from here http://forum.xda-developers.com/showthread.php?t=2389107
All i did was put my 7 in fastboot mode then ran the tool kit. I then launched the advanced utilities and then fastboot format. Then i flashed stock rom.
Worked a treat. Thought mine was toast as well good luck.
snod33 said:
My 2012 wifi did that exactly. I downloaded wugfresh Nexus Root Toolkit yours can be d/loaded from here http://forum.xda-developers.com/showthread.php?t=2389107
All i did was put my 7 in fastboot mode then ran the tool kit. I then launched the advanced utilities and then fastboot format. Then i flashed stock rom.
Worked a treat. Thought mine was toast as well good luck.
Click to expand...
Click to collapse
I tried once, but i will try it again, thank you
---------- Post added at 12:25 AM ---------- Previous post was at 12:09 AM ----------
doing that you said:
Advanced tools--> fastboot format
now it is stuck in "Fastboot Formating CACHE..."
=(
i think the main problem (one o f them) is that i cannot use adb, when i use the command
Code:
fastboot devices
i get the serial number but when i use
Code:
adb devices
the results is nothing.
j4k0 said:
I tried once, but i will try it again, thank you
---------- Post added at 12:25 AM ---------- Previous post was at 12:09 AM ----------
doing that you said:
Advanced tools--> fastboot format
now it is stuck in "Fastboot Formating CACHE..."
=(
Click to expand...
Click to collapse
I hate to be the bearer of bad news, but that's not a good sign. I haven't found anyone reporting success when it's having that issue. If you have exhausted the external possibilities such as drivers, USB cords, the PC, trying Windows and Linux, etc and still getting the same thing then that means the eMMC is probably messed up. Examples here:
http://forum.xda-developers.com/showthread.php?t=2602638
can you boot into bootloader if you can then navigate by using volume up volume down till you find the recovery and press lock button and factory reset
zidozido22 said:
can you boot into bootloader if you can then navigate by using volume up volume down till you find the recovery and press lock button and factory reset
Click to expand...
Click to collapse
They're way past the point that a factory reset would help or even work as wiping cache is not working and that is part of a factory reset. If it isn't wiping through fastboot commands, it definitely won't work through recovery.
sorry, then you should bring it to a service center
very hard and sad to hear that, thank you anyway guys...
about RMA i saw that will be expensive bcz the warranty time expired
Hi everyone! After happily rooting my Kindle and leaving it unattended for less then a few minutes, I came back to a boot-looped Kindle HD 6 because it had taken an OTA update.
I've looked at a few threads on this forum about how to get into Fastboot mode but I can't seem to get it working right. I have a Fastboot cable but that doesn't do anything either. Can someone help me?
PROBLEM SOLVED: I switched out the Motherboard c:
merlise said:
Hi everyone! After happily rooting my Kindle and leaving it unattended for less then a few minutes, I came back to a boot-looped Kindle HD 6 because it had taken an OTA update.
I've looked at a few threads on this forum about how to get into Fastboot mode but I can't seem to get it working right. I have a Fastboot cable but that doesn't do anything either. Can someone help me?
Click to expand...
Click to collapse
This is from another thread about a boot loop thought it might help you.
powerpoint45 said:
I do not know if this would work or even the steps, but you can download the stock firmware from here: www.amazon.com/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=201596860
Also the ????????????? Besides your device from "adb devices" just means you need to install the driver for it. That should not be too hard to find out how to do. But really I think you'd need the fastboot drivers more. But in the past I have fixed a bootloop by just looking at the logs to figure out where the crash is coming from via adb logcat, then fixing that issue. But since this is using xposed it'd probably be too complicated to fix manually. Don't ask me for drivers tho cause I use Linux.
Note: the firmware update downloads as a bin file but it is just a zip file. A fastboot update might actually work with it since it is signed by Amazon.
Something like:
Wipe your device. (only if necessary)
fastboot -w
Update your ROM.
fastboot update
---------- Post added at 11:03 PM ---------- Previous post was at 10:45 PM ----------
I've gotten into fastboot on this device. I think it was either "adb reboot bootloader" or "adb reboot fastboot" that works. Keep in mind when in fastboot mode the fire hd6 screen is completely blank.
Click to expand...
Click to collapse
AlbusAngelus said:
This is from another thread about a boot loop thought it might help you.
Click to expand...
Click to collapse
Thanks for trying to help I tried just about everything, but nothing is working.
I decided to just get another used HD 6 and switch out the motherboards and see what happens. I'll come back to the rooting game as soon as there is a working custom recovery and rom up, haha. Thanks.
See my thread: http://forum.xda-developers.com/fire-hd/general/to-fastboot-t2988597
meganoahj said:
See my thread: http://forum.xda-developers.com/fire-hd/general/to-fastboot-t2988597
Click to expand...
Click to collapse
Yours was actually the first I looked at! I tried but I unfortunately couldn't get ADB to recognize the device properly. I've already switched out the motherboards so my problem is somewhat fixed for now.
Think that you need a fastboot cord to get into fastboot. Just what I've heard.
ryanyz10 said:
Think that you need a fastboot cord to get into fastboot. Just what I've heard.
Click to expand...
Click to collapse
I have a fastboot cable, but it still didn't put me into fastboot
merlise said:
I have a fastboot cable, but it still didn't put me into fastboot
Click to expand...
Click to collapse
You need to power of and then press and hold volume up while plugging in the tablet i think.
Have you searched how to get into fastboot with fastboot cable on google?
ryanyz10 said:
You need to power of and then press and hold volume up while plugging in the tablet i think.
Have you searched how to get into fastboot with fastboot cable on google?
Click to expand...
Click to collapse
I have haha, I honestly tried everything but I just couldn't get it into fastboot. When I'm feeling adventurous, I'll probably try it again, but I just ended up switching out the motherboards with another HD6 for convenience.
Greetings,
Upon unboxing my OPO X and discovering it's limitations in regard to customization compared to Cyanogen (following this guide :
HTML:
http://oneplus.wonderhowto.com/how-to/install-cyanogen-os-12-your-oneplus-one-0161384/
),
I attempted to flash it using TRWP which I managed to install and start properly.
Either I messed something up with the install process or selected the wrong build for my specific phone (used YNG1TAS0YL-bacon-signed) but I was prompted to reboot my phone upon what I though was completion and ended up with no OS, hard bricked with QHSUSB BULK showing in device manager and totally blanked screen.
I then attempted to fix my own mess by following this guide :
HTML:
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
which suggested I uninstall the faulty driver and replace it with the one suggested.
By doing so, I then ended up with an unknown device and from there my real nightmare started.
I've about tried every single restore guide I could find narrowing my search to my specific model this time figuring it would prevent compatibility issues but still nothing is working.
The sum up what is currently going on with my phone, if I press Power + Volume up, I get "Qualcomm HS-USB QDLoader 9008" listed under the "Ports" section of the device manager. However I now get a result with QCOMDownloadTool (which fail to to anything but is listed in some guides). No access to either fastboot or ADB.
On the other end, Power + Volume down booting will list whatever drivers I've choosen among Google, Samsung, Universal ADB or OnePlus i've tried to install and will list the device as an "Android device". This give me access to fastboot, however ADB never ever detect any devices and attempting to boot the "twrp-2.8.7.0-onyx_f2fs_r5.img" will display "FAILED (remote:dtb not found)".
Also, I noticed that within driver detail under "hardware id's" I get :
USB\VID_18D1&PID_D00D&REV_0100
USB\VID_18D1&PID_D00D
but with the official "OnePlus_android_winusb.inf" it is not replicated for adb value with instead
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_D00D ;fastboot
%SingleBootLoaderInterface% = USB_Install, USB\VID_2A70&PID_D00D ;oem fastboot
%SingleAdbInterface% = USB_Install, USB\VID_2A70&PID_4EE7 ;adb
I'm all out of ideas, looking to try and fix it myself (with your help of course) before I go begging OnePlus customer support to save me.
Thanks in advance folks!
Try booting with your stock recovery. Img if you think it boots in fastboot
Sent from my ONE E1003 using Tapatalk
loveboy_lion said:
Try booting with your stock recovery. Img if you think it boots in fastboot
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
I think the most basic problem is that no matter what driver I attempted to use so far, end up not showing in ADB.
I don't know the relation between ADB and fastboot, but I probably don't have a fully functional driver.
I made I backup with TWRP before wiping, but I don't think "recovery.emmc.win" & "recovery.emmc.win.md5" will help me a whole lot from fastboot.
Any idea where to get an image file of the stock recovery and the exact commands sequence to be used afterward?
It might sound like I have an idea of what i'm doing because I've been trying to fix this mess for 2 days, but I really don't...
KrapnoV said:
I think the most basic problem is that no matter what driver I attempted to use so far, end up not showing in ADB.
I don't know the relation between ADB and fastboot, but I probably don't have a fully functional driver.
I made I backup with TWRP before wiping, but I don't think "recovery.emmc.win" & "recovery.emmc.win.md5" will help me a whole lot from fastboot.
Any idea where to get an image file of the stock recovery and the exact commands sequence to be used afterward?
It might sound like I have an idea of what i'm doing because I've been trying to fix this mess for 2 days, but I really don't...
Click to expand...
Click to collapse
if i am understanding you correctly then you tried to install oneplus one twrp and rom on oneplus x if you really did so no wonder device is bricked since either you erased all your partitions (which is bad since oneplus did not release files required to debrick hardbrick device) if you only messed up your recovery then you would need stock recovery.img of your e1005 since recovery.img of e1003 most probably wont work you could try though
regarding if you are not sure if your phone is connecting in fastboot or adb try uninstalling all drivers you have installed and install the below drivers and hope your phone is in fastboot mode
https://drive.google.com/open?id=0B48lBYmwzkD5WlFrU2lNb2d5WlE
---------- Post added at 05:40 AM ---------- Previous post was at 05:33 AM ----------
if you have fastboot chances to repair your phone are 99%
your device wont detect under adb
---------- Post added at 06:01 AM ---------- Previous post was at 05:40 AM ----------
you could also check this for help
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Well, either I have rebooted before the installation was completed or I had the wrong kernel, but I no longer get any visual response from my phone beside vibrations when I power it on/off.
The drivers currently installed are the ones you provided, still there is nothing in ADB.
I can start a cmd fastboot and get a results from "fastboot devices".
See screen capture blow:
i.imgur(dot)com/KnFmTcf.jpg
i.imgur.(dot)com/4kat7Cv.jpg
I doesn't go any further than that, phone is still dead.
its good news for you
you are in fastboot mode
instead of installing twrp recovery install your stock recovery
it wont flash twrp since its getting dtb error and fastboot wont allow it to load since this version of twrp is for e1003 and yours is e1005
Where can I get an .img of the stock recovery?
I already did overwrite with TWRP so stock recovery is no longer present on the phone right?
I saw this file but I don't think I can use it:
drive.google(dot)com/file/d/0B0pr-ZA5b-1pM1prTmMwQmhOMXM/view?pli=1
you could try it hope it works chances of it working is 50%
fastboot flash recovery recovery.img
fastboot boot recovery.img (if this does not work and manualy try with power+volumedown)
---------- Post added at 06:40 AM ---------- Previous post was at 06:34 AM ----------
you are not alone with same problem
http://forum.xda-developers.com/oneplus-x/help/users-twrp-t3258756/post64071152#post64071152
---------- Post added at 06:49 AM ---------- Previous post was at 06:40 AM ----------
unless someone makes unified build of twrp for e1003 and e1005 you will face same problem if u try to flash twrp again
I do NOT have access to a "recovery.img" file on my phone.
What can I do next? Can these files I made a backup from be of any help currently?
i.imgur(dot)com/uEPBECy.jpg
yes the files are of help but only when u have twrp they cannot be used by fastboot
---------- Post added at 07:08 AM ---------- Previous post was at 07:05 AM ----------
try flashing this twrp recovery
http://ns336247.ip-91-121-110.eu/h2o64/onyx/twrp/
Bacon is for the oneplus one...
KrapnoV said:
Well, either I have rebooted before the installation was completed or I had the wrong kernel, but I no longer get any visual response from my phone beside vibrations when I power it on/off.
The drivers currently installed are the ones you provided, still there is nothing in ADB.
I can start a cmd fastboot and get a results from "fastboot devices".
See screen capture blow:
i.imgur(dot)com/KnFmTcf.jpg
i.imgur.(dot)com/4kat7Cv.jpg
I doesn't go any further than that, phone is still dead.
Click to expand...
Click to collapse
Do you realize you tried to install stuff for an entirely different phone? OnePlus One is not OnePlus X. There was the problem with your installs...
If you get into to fastboot I would try flashing something that is made for OnePlus X and see how it goes.
I would be very happy to flash a compatible rom this time, but while fastboot SEEM to work, i'm not sure it does.
Understand I've never done that before, but all the guide requires to be able to boot recovery to progress, and with that "FAILED remote dtb" error I'm getting I don't know how to go any further. The TWRP version i'm using "twrp-2.8.7.0-onyx_f2fs_r5.img" is supposed the be the right one for my phone.
I would also test stock recovery but I don't have an image file and so far no luck finding one.
KrapnoV said:
I would be very happy to flash a compatible rom this time, but while fastboot SEEM to work, i'm not sure it does.
Understand I've never done that before, but all the guide requires to be able to boot recovery to progress, and with that "FAILED remote dtb" error I'm getting I don't know how to go any further. The TWRP version i'm using "twrp-2.8.7.0-onyx_f2fs_r5.img" is supposed the be the right one for my phone.
I would also test stock recovery but I don't have an image file and so far no luck finding one.
Click to expand...
Click to collapse
Here is stock recovery image for E1005. https://drive.google.com/file/d/0B6zU7r3AtRjFb2tyQU11YTdLVEU/view?usp=sharing
Hi,
My phone OnePlus X E1003 was hard brick after install twrp.. now phone is dead..cannot access recovery and fastboot,screen blank and just vibrate.. when i plug in. it only detect qualcomm HS-USB driver.. but opx still dont have zip to repair the broken partition. anybody have ideal?pls help me.
Same problem here
apekgee said:
Hi,
My phone OnePlus X E1003 was hard brick after install twrp.. now phone is dead..cannot access recovery and fastboot,screen blank and just vibrate.. when i plug in. it only detect qualcomm HS-USB driver.. but opx still dont have zip to repair the broken partition. anybody have ideal?pls help me.
Click to expand...
Click to collapse
Same here, black screen only vibrates on holding power button for 10 seconds :crying:
apekgee said:
Hi,
My phone OnePlus X E1003 was hard brick after install twrp.. now phone is dead..cannot access recovery and fastboot,screen blank and just vibrate.. when i plug in. it only detect qualcomm HS-USB driver.. but opx still dont have zip to repair the broken partition. anybody have ideal?pls help me.
Click to expand...
Click to collapse
What did you do besides trying to install twrp? It would be difficult to brick by just flahshing recovery unless it was the wrong one.
Sent from my ONE E1005 using Tapatalk
If you can get it in bulk mode then you should probably try this http://forum.xda-developers.com/one...stboot-adb-t2835696/post55024864#post55024864
Ok...easy peasy....it happened to me too...Just open a ticket for a remote session with oneplus.....
They do mostly everything in about 45 minutes.
I tried everything too, nothing worked. Don't stress yourself out...They were good about it.
joey24z1 said:
Ok...easy peasy....it happened to me too...Just open a ticket for a remote session with oneplus.....
They do mostly everything in about 45 minutes.
I tried everything too, nothing worked. Don't stress yourself out...They were good about it.
Click to expand...
Click to collapse
pls help me how u manage to contact technical support?
SOME USERS CAN'T MAKE THIS GUIDE. PLEASE READ ALL POST BEFORE DO THIS GUIDE.
bibiii79 said:
Thanks a lot, worked perfectly !!!
:good:
Cheers!
Click to expand...
Click to collapse
muzzz33 said:
Many thanks , worked a charm , installed latest TWRP AND Magisk once unlocked . I thought this would be a night mare but no issues so far. I was on 7.1.1 2017G 1.20B08
Click to expand...
Click to collapse
bibiii79 said:
Thanks a lot, worked perfectly !!!
:good:
Cheers!
Click to expand...
Click to collapse
muzzz33 said:
Many thanks , worked a charm , installed latest TWRP AND Magisk once unlocked . I thought this would be a night mare but no issues so far. I was on 7.1.1 2017G 1.20B08
Click to expand...
Click to collapse
emanulian said:
How?
I can´t do it (anything).
---------- Post added at 01:24 PM ---------- Previous post was at 01:17 PM ----------
This help me:
"10- You'll boot in TWRP once there do the following :
Code:
* tap CANCEL
* tap WIPE
* tap FORMAT DATA and Follow the Instructions"
Thank you.
Click to expand...
Click to collapse
atakan33 said:
i try on nougat B08 also B09 works too
Click to expand...
Click to collapse
bersek71 said:
thanks! It's OK with nougat!
Click to expand...
Click to collapse
Martinius79 said:
Thanks!
This method worked for me on a A2017G running stock B08 (Nougat) with locked bootloader.
Build number: ZTE A2017GV1.2.0B08
Only difference was between step 10 and 11. The device was encrypted so I ended up in the "enter password" dialog after flashing, reset and reboot from edl (because of verity break I guess).
I had to force the device manually into the bootloader (switch off and then hold Volume-Up and Power button to get into the recovery and then to the bootloader).
BTW: Flashed TWRP 3.2.1.0 directly after first boot with axon7tool and then installed Magisk 15.3. Magisk seems to work pretty well for me with this device, root/SU support is working and SafetyNet Patch is also fine.
Thanks for the guide and the links again!
Bye
Martinius
Click to expand...
Click to collapse
[GUIDE]Unlock Bootloader Easily
Hi all. I will present new and easier method to unlock bootloader. This guide works on all models.
Before begin;
- Be sure backed up your stuffs on internal storage.
- Be sure that using x64 Windows.
- Be sure that your battery is over 50%
- Be sure that Disable Driver Signature Verification
Download:
MiFlash 20160401 https://drive.google.com/file/d/0B065LdNGqJLGM2xfSkZMbVYwc3M/view
15 second ADB Installer https://forum.xda-developers.com/showthread.php?t=2588979
ZTE Axon 7 USB Drivers https://androidfilehost.com/?fid=889964283620763004
ZTE Axon 7 Bootloader Unlock Images by TurkDevs https://androidfilehost.com/?fid=817906626617943545
Unlock Bootloader:
1. Install MiFlash. Driver installation will be done automatically.
2. Install ADB Installer. Press Y for all steps on installation.
3. Install Axon 7 Driver.
4. Turn on from developer options "USB Debugging" and "Unlock OEM".
5. Enter; "adb reboot edl"
6. Go Device Manager of Windows and be sure you see your device as "Quallcomm HS-USB QDLoader 9008".
7. Extract ZTE_AXON_7_BOOTLOADER_UNLOCK_IMAGES_BY_TURKDEVS.zip
8. Go MiFlash and Refresh. Your device will be there. Select from top Unlock Images folder which you've extracted.
9. Flash and wait until it is done.
10. Long press power button and let your device is on.
11. Enter "adb reboot bootloader" after your device is on.
12. Enter "fastboot oem unlock-go" when you are on bootloader interface.
13. Your data will be erased on this step and device will boot with unlock bootloader.
This tool is from forum.turkdevs.com
Orginal thread: https://forum.turkdevs.com/konu/zte-axon-7-bootloader-acma-root-ve-twrp-yukleme.12225
Hit thanks button if I help you.
Isn't this the same exact method just with a different file?
is this method working 7.1.1 stock ?
atakan33 said:
is this method working 7.1.1 stock ?
Click to expand...
Click to collapse
Yes it works
and how to flash twrp easily?
Is there a zip to relock the device on an Easy way like this?
Lycidias said:
Is there a zip to relock the device on an Easy way like this?
Click to expand...
Click to collapse
actually to relock you should flash a FULL_EDL package through MiFlash, then flash fastboot, maybe with the package on this thread, and then relock. But check if I'm right cause I've never done that
Lycidias said:
Is there a zip to relock the device on an Easy way like this?
Click to expand...
Click to collapse
Yes there is. Check first message https://forum.turkdevs.com/konu/zte-axon-7-bootloader-acma-root-ve-twrp-yukleme.12225/
what about twrp ?
is this working on my A2017G unlocked bootloader ?
atakan33 said:
is this working on my A2017G unlocked bootloader ?
Click to expand...
Click to collapse
it should.
I follow yours steps, All was donde fine, but now, to start it ask me for password!!! What is it?!?!
emanulian said:
I follow yours steps, All was donde fine, but now, to start it ask me for password!!! What is it?!?!
Click to expand...
Click to collapse
You should format data
How?
I can´t do it (anything).
---------- Post added at 01:24 PM ---------- Previous post was at 01:17 PM ----------
This help me:
"10- You'll boot in TWRP once there do the following :
Code:
* tap CANCEL
* tap WIPE
* tap FORMAT DATA and Follow the Instructions"
Thank you.
When I put "adb reboot edl" in the Commend Prompt, it came up the device cannot found. Where did I do wrong? Thanks.
jjremax said:
When I put "adb reboot edl" in the Commend Prompt, it came up the device cannot found. Where did I do wrong? Thanks.
Click to expand...
Click to collapse
Like, on the start? Look you need to enable USB debugging and keep the phone on and unlocked. Issue 'adb devices' and a pop-up should appear on the phone. Allow the connection and then try 'adb reboot edl'
The phone will seem like it's completely off but it will be in EDL mode
Choose an username... said:
Like, on the start? Look you need to enable USB debugging and keep the phone on and unlocked. Issue 'adb devices' and a pop-up should appear on the phone. Allow the connection and then try 'adb reboot edl'
The phone will seem like it's completely off but it will be in EDL mode
Click to expand...
Click to collapse
Actually, I enabled USB debugging and kept the phone on. I don't understand the meaning of keeping it unlocked, which I thought that was what I am trying to do.
Another question is whether I should download those files into my computer or into the phone. I downloaded them into my PC.
Unlock Bootloader Easily
jjremax said:
Actually, I enabled USB debugging and kept the phone on. I don't understand the meaning of keeping it unlocked, which I thought that was what I am trying to do.
Another question is whether I should download those files into my computer or into the phone. I downloaded them into my PC.
Click to expand...
Click to collapse
I re-did the whole process and finished the step 9 (Flash and wait until it is done). However, the device won't be on after long press the power button as indicated in Step 10. What should I do now?
jjremax said:
I re-did the whole process and finished the step 9 (Flash and wait until it is done). However, the device won't be on after long press the power button as indicated in Step 10. What should I do now?
Click to expand...
Click to collapse
Make it a really long press. Like a couple of minutes long. After that release it and hold it again, it should boot up
What I meant with 'keep it unlocked' was that you had to leave it with the screen on, not locked.
Unlock Bootloader Easily
Choose an username... said:
Make it a really long press. Like a couple of minutes long. After that release it and hold it again, it should boot up
What I meant with 'keep it unlocked' was that you had to leave it with the screen on, not locked.
Click to expand...
Click to collapse
Thanks for the info. I have long pressed the power button more than 4 minutes, but it still won't power up. I saw the LED light up very shortly and felt the phone motor vibrated little bit (You normal can feel the vibration very strong before I did such unlock bootloader thing when the phone powers on). Also, it would repeate such LED and little motor vibration if I hold the power button long enough. How should I do? Thanks again.