Related
I been trying to flash twrp in fastboot. But every time I run the command to flash twrp it does nothing. I'm running marshmallow flashing twrp should work. I do have my bootloader unlocked.
Sent from my XT1575 using Tapatalk
What commands are you using?
StreetkillnHD said:
I been trying to flash twrp in fastboot. But every time I run the command to flash twrp it does nothing. I'm running marshmallow flashing twrp should work. I do have my bootloader unlocked.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I seem to recall having an issue where the fastboot command would not work. I updated my sdk and it worked.
Are you using a Windows machine or Linux. I had and issue with fastboot on Ubuntu, and eventually found a fix.
Also make sure your computer is seeing your phone in bootloader mode type... fastboot devices.
rsmiff said:
Also make sure your computer is seeing your phone in bootloader mode type... fastboot devices.
Click to expand...
Click to collapse
just tried that and i guess my computer isnt seeing it.. odd
StreetkillnHD said:
just tried that and i guess my computer isnt seeing it.. odd
Click to expand...
Click to collapse
Maybe try reinstalling the Moto drivers?
gokart2 said:
Maybe try reinstalling the Moto drivers?
Click to expand...
Click to collapse
should repairing it work or do i need to uninstall it and redownload
StreetkillnHD said:
should repairing it work or do i need to uninstall it and redownload
Click to expand...
Click to collapse
I would try the repair function. If you uninstall the Moto program, the drivers stay installed. So you would have to manually remove the drivers.......I would just try the repair function. Then make sure you have oem unlocking and usb debugging turned on in the dev options. Then try the
Code:
adb devices
command. It should return your device id.
I have a relatively new P8-lite L21 dual sim phone and I am quite happy with it. It came with C432B170 which is Lollipop I think 5.01. After a few days it updated to B172. I have unlocked the bootloader after registering with Huawei and waiting 2 weeks. Then I have successfuly rooted the phone with Kingroot phone version. Two or three weeks ago I have updated the phone to MM (6) and Emui 4 with local update (B560) that I have gotten from this forum. 2 days ago I recieved the notification of OTA B564 which went smoothly beside the fact that it reset the phone but i have succesfully restored (contacts, data etc.) All of this time since I upgraded to MM i have tried to root the phone but I was unsuccesful either with any software solution ( Kingroot, Kingoroot or others). After reading most if not all discussions on this forum and several blogs and how -tos, I tried the so called fastboot method others have recommended but here is now the gist of my problem. My phone is seen by my PC - OK so USB drivers are properly installed (by the way my PC is Win 10) and I have installed Android SDK as well as minimal ADB. When i try to flash TWRP 3.00.2 I can not do it (the message says something about not able to access or i think remote command not allowed. So since I cannot flash TWRP i am unable to put SU on the phone and root it. I hope someone more experienced and skillfull in Android world can point me in the right direction and help me. Thank you
Download mininal adb fastboot and then try to flash twrp via fastboot.
That error occurs because your adb doesn't have full permissions.
Minimal adb will solve this.
VladHD said:
Download mininal adb fastboot and then try to flash twrp via fastboot.
That error occurs because your adb doesn't have full permissions.
Minimal adb will solve this.
Click to expand...
Click to collapse
Downloaded minimal adb fastboot and installed it. Tried the procedure. Copied TWRP recovery to the minimal folder. Shift right clicked in the folder of minimal and opened command window. Adb rebooted to bootloader. Phone shows it is unlocked. The device is seen in fastboot window but flashing recovery doesn't work (same message) I am really confused. How do I give adb full permissions ?
Any way thanks in advance.
Did you activate usb debugging ?
VladHD said:
Did you activate usb debugging ?
Click to expand...
Click to collapse
Yes of course !
Try reinstalling drivers with universal adb.
Are you sure your bootloader is unlocked?
Type fastboot devices and let me know the output.
VladHD said:
Try reinstalling drivers with universal adb.
Are you sure your bootloader is unlocked?
Type fastboot devices and let me know the output.
Click to expand...
Click to collapse
The drivers were reinstalled. My bootloader shows unlocked on bootloader (bottom of fastboot screen). Fastboot devices does nothing. Adb devices shows my phone serial number correctly (I have it written down). But then when i try to flash recovery it is unsuccessfull. It says "FAILED (remote: Command not allowed)"
What is the command that you typed..?
Fastboot flash recovery xxx.img
Sent from my ALE-L21 using XDA-Developers mobile app
amageek said:
What is the command that you typed..?
Fastboot flash recovery xxx.img
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
Fastboot flash recovery recovery. img I renamed the twrp 3.0 to recovery.img
doomking_99 said:
Fastboot flash recovery recovery. img I renamed the twrp 3.0 to recovery.img
Click to expand...
Click to collapse
sorry, if you've already answered this, but you can also do it by flashify... flash the recovery image via flashify (root needed though)
amageek said:
sorry, if you've already answered this, but you can also do it by flashify... flash the recovery image via flashify (root needed though)
Click to expand...
Click to collapse
Thanks, but my problem is that i cannot root without installing TWRP is my understanding.
doomking_99 said:
Thanks, but my problem is that i cannot root without installing TWRP is my understanding.
Click to expand...
Click to collapse
ahhh... sorry mate, dont know the solution.. but try re-installing adb drivers again ...
Are you logged as adminstrator on pc?
Try to plug usb into different slots.
VladHD said:
Are you logged as adminstrator on pc?
Try to plug usb into different slots.
Click to expand...
Click to collapse
I am and I have. I am stumped. Obviously something is wrong with windows permissions I think. Is it possible to put recovery. img on sd card or on phone and flash recovery from the phone ?
This is the output every time no matter which usb port
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
W3D7N15C08019820 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (27062 KB)...
OKAY [ 0.624s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.627s
C:\Program Files (x86)\Minimal ADB and Fastboot>
The thing i don't understand is why fastboot command doesn't show device while adb command does.
You said that you have android sdk too... Have you tried using that?
If it doesn't help them try to do it on other computer or reset your windows...
Sent from my ALE-L21 using XDA-Developers mobile app
amageek said:
You said that you have android sdk too... Have you tried using that?
If it doesn't help them try to do it on other computer or reset your windows...
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank you but i have tried with SDK and with minimal and always the same result as i posted. I will try and do it on my wife's PC.
doomking_99 said:
Thank you but i have tried with SDK and with minimal and always the same result as i posted. I will try and do it on my wife's PC.
Click to expand...
Click to collapse
Sorry for the zombiethreading here, but... what whas the solution? I'm curious
For the time being there is no solution. Can not flash TWRP - phone not rooted
doomking_99 said:
For the time being there is no solution. Can not flash TWRP - phone not rooted
Click to expand...
Click to collapse
Weird... i can't think of anything else myself that hasn't been said. Perhaps... redownloading twrp? Maybe the image is corrupted by something... ot's a long shot because ot should flash everytging that comes its way. But it's the only thing you hven't tried.
why do I keep getting this error when trying to flash twrp? I'm on lineage 14.1
C:\Users\spam1\Desktop\Minimal ADB and Fastboot>fastboot flash boot twrp-mata_6.img
target didn't report max-download-size
sending 'boot' (32124 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.123s
Thanks
I had this same problem. Have you tried "fastboot -w" before attempting to flash twrp?
Try android studio tools, outdated ADB/fastboot was an issue when I was on the pixel xl due to the partitions
Jaysonvstel said:
I had this same problem. Have you tried "fastboot -w" before attempting to flash twrp?
Click to expand...
Click to collapse
I'll try that once I get home. All I did was the update and lost root and recovery
networx2002 said:
I'll that that once I get home. All I did was the update and lost root and recovery
Click to expand...
Click to collapse
It will rested the phone, so backup.
DaveHTC200 said:
Try android studio tools, outdated ADB/fastboot was an issue when I was on the pixel xl due to the partitions
Click to expand...
Click to collapse
Here is the link for OP.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
I just got home and wanted to tried and flash twrp recovery before I fastboot -w" it and it worked... LOL who knows!
I have the same problem. I tried many times, many methods found online, including swapping USB port, cables, and tried fastboot -w. Neither of them works...
heximing said:
I have the same problem. I tried many times, many methods found online, including swapping USB port, cables, and tried fastboot -w. Neither of them works...
Click to expand...
Click to collapse
Me too, can't figure it out..
networx2002 said:
why do I keep getting this error when trying to flash twrp? I'm on lineage 14.1
C:\Users\spam1\Desktop\Minimal ADB and Fastboot>fastboot flash boot twrp-mata_6.img
target didn't report max-download-size
sending 'boot' (32124 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.123s
Thanks
Click to expand...
Click to collapse
Try changing USB port or use a different USB cable. The is known to solve the issue.
Also once you are in fastbot, reboot again into fastboot using "fastboot reboot bootloader"
And the flash TWRP image
If you still get the error, install Fastboot drivers from Essential website.
networx2002 said:
why do I keep getting this error when trying to flash twrp? I'm on lineage 14.1
C:\Users\spam1\Desktop\Minimal ADB and Fastboot>fastboot flash boot twrp-mata_6.img
target didn't report max-download-size
sending 'boot' (32124 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.123s
Thanks
Click to expand...
Click to collapse
Jaysonvstel said:
I had this same problem. Have you tried "fastboot -w" before attempting to flash twrp?
Click to expand...
Click to collapse
DaveHTC200 said:
Try android studio tools, outdated ADB/fastboot was an issue when I was on the pixel xl due to the partitions
Click to expand...
Click to collapse
heximing said:
I have the same problem. I tried many times, many methods found online, including swapping USB port, cables, and tried fastboot -w. Neither of them works...
Click to expand...
Click to collapse
dsulps said:
Me too, can't figure it out..
Click to expand...
Click to collapse
Use the adb/fastboot from the drivers from essential. It sets environment variable in Windows. Uninstall any other adb/fastboot, and check your environment path to make sure only essential bone is there.
You could easily brick your phone using the wrong adb/fastboot. Beware of dragons and such.
Did that, but somehow it didn't help. Tried a different computer, installed the essential drivers, and used the cable that came with the phone; everything went smoothly. Still don't know what the problem was, the first computer does not have any fastboot/adb in the path variable, after removing the essential drivers, but I suppose the problem's solved, for now. Thanks everyone!
dsulps said:
Did that, but somehow it didn't help. Tried a different computer, installed the essential drivers, and used the cable that came with the phone; everything went smoothly. Still don't know what the problem was, the first computer does not have any fastboot/adb in the path variable, after removing the essential drivers, but I suppose the problem's solved, for now. Thanks everyone!
Click to expand...
Click to collapse
It's Essential voodoo...
@aer0zer0
devnull advocates a PC reboot with the device unplugged, run the command, then plug the device in while "Waiting for device..." And it has worked for me twice when fastboot was drunk
rignfool said:
It's Essential voodoo...
@aer0zer0
devnull advocates a PC reboot with the device unplugged, run the command, then plug the device in while "Waiting for device..." And it has worked for me twice when fastboot was drunk
Click to expand...
Click to collapse
Oh sure, but the bigger question is, why is fastboot drunk to begin with?
aer0zer0 said:
Oh sure, but the bigger question is, why is fastboot drunk to begin with?
Click to expand...
Click to collapse
Because it got into your liquor cabinet?
rignfool said:
Because it got into your liquor cabinet?
Click to expand...
Click to collapse
so fastboot says its hammertime
aer0zer0 said:
so fastboot says its hammertime
Click to expand...
Click to collapse
More like...
"Can't Touch This"
Hi.
I was having trouble when I try to follow the method on essential's site.
Here's what adb told me:
"opening 'ota_file.zip'...
connecting...
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information."
Did some research on google. But sadly still don't know how this happened. Plz, help me, if you know what to do. thx
I suggest trying to flash the stock dump OB3 from here:
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
I assume you already unlocked the bootloader.
You will need to unlock critical as well, but if you got ADB up and running already, should be easy.
Download and unzip the OB3 dump.
Unzip and place all files where fasboot is placed, should be platform-tools.
fastboot flashing unlock_critical (will wipe entire phone)
Then run the flash-all.bat in terminal (you can just drag and drop the flash-all file into terminal)
If successful, run fastboot -w to format data just for good measure.
If unsuccessful, open the flash-all in a text editor and copy paste the commands one at a time in terminal, enter after each one.
If not able to get either to work, DO NOT REBOOT. ask for more help.
q13017 said:
Hi.
I was having trouble when I try to follow the method on essential's site.
Here's what adb told me:
"opening 'ota_file.zip'...
connecting...
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information."
Did some research on google. But sadly still don't know how this happened. Plz, help me, if you know what to do. thx
Click to expand...
Click to collapse
Normally you should be able to adb sideload with a locked bootloader and the original recovery.
Try another computer or USB-C cable, and yes USB-C cable quality does make a big difference.
Double check these
1. Bad drivers (i.e dont use Leca driver, but Google usb driver)
2. Bad USB Cable
3. Too outdated adb version
4. Bad flashable zip download
jamesst20 said:
Normally you should be able to adb sideload with a locked bootloader and the original recovery.
Try another computer or USB-C cable, and yes USB-C cable quality does make a big difference.
Double check these
1. Bad drivers (i.e dont use Leca driver, but Google usb driver)
2. Bad USB Cable
3. Too outdated adb version
4. Bad flashable zip download
Click to expand...
Click to collapse
I just wait until the bts is available. I've had bad luck sideload in.
Sent from my PH-1 using XDA Labs
avd said:
I just wait until the bts is available. I've had bad luck sideload in.
Click to expand...
Click to collapse
I have gotten the essential today and the first thing I did is flash Android O and everything seems flawless
avd said:
I just wait until the bts is available. I've had bad luck sideload ing.
Click to expand...
Click to collapse
And if your bootloader is locked you can't fallback to other methods of your system goes wonky even if we have an a/b system.
Sent from my PH-1 using XDA Labs
Airwolf79 said:
I suggest trying to flash the stock dump OB3 from here:
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
I assume you already unlocked the bootloader.
You will need to unlock critical as well, but if you got ADB up and running already, should be easy.
Download and unzip the OB3 dump.
Unzip and place all files where fasboot is placed, should be platform-tools.
fastboot flashing unlock_critical (will wipe entire phone)
Then run the flash-all.bat in terminal (you can just drag and drop the flash-all file into terminal)
If successful, run fastboot -w to format data just for good measure.
If unsuccessful, open the flash-all in a text editor and copy paste the commands one at a time in terminal, enter after each one.
If not able to get either to work, DO NOT REBOOT. ask for more help.
Click to expand...
Click to collapse
Just wondering if I can delete -w to save user data? LIke the old day nexus devices.
jamesst20 said:
Normally you should be able to adb sideload with a locked bootloader and the original recovery.
Try another computer or USB-C cable, and yes USB-C cable quality does make a big difference.
Double check these
1. Bad drivers (i.e dont use Leca driver, but Google usb driver)
2. Bad USB Cable
3. Too outdated adb version
4. Bad flashable zip download
Click to expand...
Click to collapse
Thx for the help,
1. I used the one provided on the official website.
2. The one comes with the phone. (My motherboard do support Type-c Male to Male )
3. I'm pretty sure it is the newest version.
4. Maybe...
q13017 said:
Just wondering if I can delete -w to save user data? LIke the old day nexus devices.
Click to expand...
Click to collapse
It only works with fastboot factory images. These are recovery flashable zip as far as I know.
Also, you need unlocked bootloader to flash factory images and in case you are already unlocked, you could just push the zip into your phone and use twrp to flash it.
q13017 said:
Thx for the help,
1. I used the one provided on the official website.
2. The one comes with the phone. (My motherboard do support Type-c Male to Male )
3. I'm pretty sure it is the newest version.
4. Maybe...
Click to expand...
Click to collapse
You could try booting your phone with usb debugging enabled and see if the command "adb push file.zip /sdcard/Download"
If this command fail aswell, it's probably driver related or cable. I don't think an invalid zip would make it fail
q13017 said:
Thx for the help,
1. I used the one provided on the official website.
2. The one comes with the phone. (My motherboard do support Type-c Male to Male )
3. I'm pretty sure it is the newest version.
4. Maybe...
Click to expand...
Click to collapse
The one that change with the phone is not for flashing
Sent from my PH-1 using XDA Labs
avd said:
The one that change with the phone is not for flashing
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
Yeah, don't use the charging cable for flashing. Essential has confirmed that some phones have been bricked using their included cable.
Sent from my PH-1 using Tapatalk
jamesst20 said:
It only works with fastboot factory images. These are recovery flashable zip as far as I know.
Also, you need unlocked bootloader to flash factory images and in case you are already unlocked, you could just push the zip into your phone and use twrp to flash it.
You could try booting your phone with usb debugging enabled and see if the command "adb push file.zip /sdcard/Download"
If this command fail aswell, it's probably driver related or cable. I don't think an invalid zip would make it fail
Click to expand...
Click to collapse
Anyway, fastboot flash method works for me. There's a guy post the dumped image files above. Thx for your help!
q13017 said:
Anyway, fastboot flash method works for me. There's a guy post the dumped image files above. Thx for your help!
Click to expand...
Click to collapse
No problem! Then you had an unlocked bootloader
q13017 said:
Just wondering if I can delete -w to save user data? LIke the old day nexus devices.
Click to expand...
Click to collapse
Doesn't matter. If you use the fastboot method, you need to unlock the bootloader AND unlock critical, which will wipe user data anyway, unless you had already done that previously. You can try the sideload method with stock recovery, but if you're not able to get that to work, you don't have a choice but to unlock and try the fastboot method.
I'm trying to install Beta 3 (I'm coming from stock NMJ51B), but the sideload will end at 94% and I get the Message:
Unable to open sysfs usb node (no such file or directory) Trying configfs failed to set driver control: No such device
Install from ADB complete
The PH-1 will then boot just fine and everything seems to work.
Any ideas?
power-on+volume-up ..bootloader running?
Was problem solved?,I wanted looking for solved of same things.Just I found it's lost my process of running fastboot.
im a XDA pleb im sorry but before i junk my ph-1 which i love to death i want to flash it to something spicy, i got the bootloader unlocked started to get twrp going then thats where it all went bad. 1. im feb 2020 update latest 2. fastboot is kinda working, i see my phone flash the img to slot a not slot b which im on and well says either file size too large or another error i can pull it all up. one error i got through my attempts i seen my bootloader was out of date update for a/b ? but some direction would BE MUCH appreciated !?!? also maybe a suggestion on a rom thats works best thats de-googled?
im even willing to pay a little bit to help me over discord or something, really would like to de-google my ph-1 hit things past my knowledge
TDIfrogman said:
im even willing to pay a little bit to help me over discord or something, really would like to de-google my ph-1 hit things past my knowledge
Click to expand...
Click to collapse
If you like the rom without Google, then there're only two right now far I know: LineageOS and crDroid
To install LineageOS, you don't need TWRP, because LineageOS has its own recovery image, you must follow exactly their instruction for installation.
Here's the link for LineageOS: https://download.lineageos.org/mata
To install crDroid, you need TWRP, at first, you must go back to Jan stock since Feb stock rom has issue with using TWRP.
Also, you need special TWRP image patched that gives you touch otherwise you need USB dongle with mouse to use TWRP. I can give you that TWRP if you need.
Here's the link for crDroid: https://forum.xda-developers.com/t/...microg-volte-wireguard-crdroid-v6-13.4129739/
Good luck!
TDIfrogman said:
im a XDA pleb im sorry but before i junk my ph-1 which i love to death i want to flash it to something spicy, i got the bootloader unlocked started to get twrp going then thats where it all went bad. 1. im feb 2020 update latest 2. fastboot is kinda working, i see my phone flash the img to slot a not slot b which im on and well says either file size too large or another error i can pull it all up. one error i got through my attempts i seen my bootloader was out of date update for a/b ? but some direction would BE MUCH appreciated !?!? also maybe a suggestion on a rom thats works best thats de-googled?
Click to expand...
Click to collapse
You can download that special TWRP image from Telegram channel
Essential Nostalgia Chat
and memes.
t.me
chanh2018 said:
If you like the rom without Google, then there're only two right now far I know: LineageOS and crDroid
To install LineageOS, you don't need TWRP, because LineageOS has its own recovery image, you must follow exactly their instruction for installation.
Here's the link for LineageOS: https://download.lineageos.org/mata
To install crDroid, you need TWRP, at first, you must go back to Jan stock since Feb stock rom has issue with using TWRP.
Also, you need special TWRP image patched that gives you touch otherwise you need USB dongle with mouse to use TWRP. I can give you that TWRP if you need.
Here's the link for crDroid: https://forum.xda-developers.com/t/...microg-volte-wireguard-crdroid-v6-13.4129739/
Good luck!
Click to expand...
Click to collapse
this is what i get after trying to flash recovery
target didn't report max-download-size
sending 'boot' (25741 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
TDIfrogman said:
this is what i get after trying to flash recovery
target didn't report max-download-size
sending 'boot' (25741 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Click to expand...
Click to collapse
What rom did you try to flash?
chanh2018 said:
What rom did you try to flash?
Click to expand...
Click to collapse
the one on there site you linked , also tried sideloading the .zip and got Signature verification failed , no where to click continue just failed with error 21
TDIfrogman said:
the one on there site you linked , also tried sideloading the .zip and got Signature verification failed , no where to click continue just failed with error 21
Click to expand...
Click to collapse
Ok, here's the steps that I do to install custom rom (not LineageOS):
1. Make sure Essential driver is installed in computer
2. Make sure to use the latest adb package from Essential (or from Android)
3. Make sure your phone is unlocked boot loader
4. Make sure your phone is in Jan stock rom
5. Make sure to turn off finger print log in and password
6. Copy TWRP installer .zip and Rom to phone
7. Boot phone to boot loader and flash boottwrp.img
8. In TWRP, in Wipe, in Advanced Wipe, select Dalvik/ ART Cache, System, Data (DO NOT select Internal Storage), and Swipe to Wipe
9. Now still in TWRP, in Install, install ROM (first), after ROM installation is done, do not reboot, install TWRP installer .zip
10. Reboot phone.
11. DONE
that's the thing i have Feb 2020 on it, how do i go back now ?
TDIfrogman said:
that's the thing i have Feb 2020 on it, how do i go back now ?
Click to expand...
Click to collapse
Download original Jan stock rom
- Unzip it to your computer
- Put phone in boot loader
- From command prompt, goto unzip folder and run flashall.bat
- Sit back and let the batch file running installation process
- When it's done, just reboot, and you'll be back to Jan stock
chanh2018 said:
Download original Jan stock rom
- Unzip it to your computer
- Put phone in boot loader
- From command prompt, goto unzip folder and run flashall.bat
- Sit back and let the batch file running installation process
- When it's done, just reboot, and you'll be back to Jan stock
Click to expand...
Click to collapse
ok so it hangs on first command might be my cable ? im gonna run and go grab a better one and try that switching ports too
TDIfrogman said:
ok so it hangs on first command might be my cable ? im gonna run and go grab a better one and try that switching ports too
Click to expand...
Click to collapse
Make sure your path of adb is working, or quick solution is to copy these 4 files into your unzip folder and run flashall.bat
You can find these 4 files in your adb folder: adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll, fastboot.exe
chanh2018 said:
Make sure your path of adb is working, or quick solution is to copy these 4 files into your unzip folder and run flashall.bat
You can find these 4 files in your adb folder: adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll, fastboot.exe
Click to expand...
Click to collapse
i couldnt find a single cable in town, its not the best cable either no damage just kinda cheap i left my anker at my friends house
im pretty sure my path is ok using the essential drivers and adb/fastboot "platform-tools_r30.0.5-windows" i tried moving those files over same thing hangs at
fastboot flash nvdef_a nvdef
Sending 'nvdef_a' (310 KB)
but i can see it with fastboot devices
TDIfrogman said:
i couldnt find a single cable in town, its not the best cable either no damage just kinda cheap i left my anker at my friends house
im pretty sure my path is ok using the essential drivers and adb/fastboot "platform-tools_r30.0.5-windows" i tried moving those files over same thing hangs at
fastboot flash nvdef_a nvdef
Sending 'nvdef_a' (310 KB)
but i can see it with fastboot devices
Click to expand...
Click to collapse
Did you enable USB debugging in Developer options?
chanh2018 said:
Did you enable USB debugging in Developer options?
Click to expand...
Click to collapse
yes dev options on , usb debug on
- Un plug USB cable from phone
- Goto Setting - About phone - Build number, tap on Build number (don't remember how many, maybe 5 or 7 times) until Developer Options is enable
- Goto System - Developer Options and turn on Android debugging (or USB debugging...I forgot)
- Connect USB cable back to phone, you will see a message popup asking to allow, enable it.
- Now from command prompt, in that unzip folder (assume you already have those 4 files copied), type: adb reboot bootloader
- Let see if your phone can goto bootloader
- If it does, continue to issue command flashall
TDIfrogman said:
yes dev options on , usb debug on
Click to expand...
Click to collapse
Ok, I'm not sure it's the cable or the adb path.
If you're positive about adb path, then your cable is bad.
You can try another version of adb (version 1.4.3)
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
chanh2018 said:
Ok, I'm not sure it's the cable or the adb path.
If you're positive about adb path, then your cable is bad.
You can try another version of adb (version 1.4.3)
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
Click to expand...
Click to collapse
i just uninstalled the essential driver/adb , using the universal everything now and i get this
fastboot flash nvdef_a nvdef
fastboot: error: cannot load 'nvdef': No such file or directory and more , but my phone reboots seems to be adb/driver issue
tried the auto install now it doesnt see my phone at all, found this user same issue but i cant follow what he did to fix it
https://www.reddit.com/r/essential/comments/8vi0nt
TDIfrogman said:
i just uninstalled the essential driver/adb , using the universal everything now and i get this
fastboot flash nvdef_a nvdef
fastboot: error: cannot load 'nvdef': No such file or directory and more , but my phone reboots seems to be adb/driver issue
Click to expand...
Click to collapse
Did you copy those 4 files to unzip rom folder?
If you did, then you can run fastboot or adb within that folder.