Related
My friend has HTC One. He wiped all the data on SD including the ROM files and One is not booting right now. It's rooted and has Trickdroid's 4.2.2 based ROM.
We tried lots of things so far;
- Pushing files via ADB
Trying ADB, it says device not found, no matter we did we couldn't manage the pc to recognize the phone.
- Mounting SD via CWM
I have HOX, when I enter CWM I can see the option to mount the SD but on One there's no line like this.
- Activating Sideload on TWRP
We also flashed TWRP and tried to use Sideload feature but when we tried to activate it, it says something like "unable to mount .."
- Flashing the RUU
And lastly we tried to flash the RUU, we checked the CID and it says o2___001 and there's no RUU for it.
I just saw that One could be S-OFF and got Super-CID, but to do that again, I have to pull and push some files via ADB so we stuck here.
Could you plese help me on this?
Try cwm recovery it has sideload feature I was in a similar situation once before and it worked using cwm recovery
Also. If you want to try use adb again, try to plug in your device and then wait for few seconds before running a push command. It worth mentioning that once adb fail one time, it is not going to work again by repeating the same push command. Once it fails run this command: adb kill-server
This command will stop the previous failed process after killing the server then try to push again
NiMH_999 said:
Try cwm recovery it has sideload feature I was in a similar situation once before and it worked using cwm recovery
Also. If you want to try use adb again, try to plug in your device and then wait for few seconds before running a push command. It worth mentioning that once adb fail one time, it is not going to work again by repeating the same push command. Once it fails run this command: adb kill-server
This command will stop the previous failed process after killing the server then try to push again
Click to expand...
Click to collapse
We tried a different computer and solved the ADB problem, then I did just like you told and it's OK now.
Thank you.
You're welcome. glad it's all all OK for you
Boot TWRP, then select “Mount”, then select only “Data” and connect your HTC One to your computer.
Considering you have adb.exe (Windows, part of fastboot.zip) or on Linux:
cd Downloads\ROM.zip
adb push ROM.zip /sdcard/
Replace ROM.zip with the ROM filename you copied earlier to Downloads (or any other) folder, then install the ROM.
It should be nearly same running CWM recovery. Hope that helps.
Same problem as you --> fixed
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
If you found that adb worked from a different machine, you might check whether you had any tethering drivers installed (eg EasyTether) on the machine that was not able to see the phone via adb. I found that they interfered with adb's operation on my Macbook previously; it was maddening.
woraz said:
My friend has HTC One. He wiped all the data on SD including the ROM files and One is not booting right now. It's rooted and has Trickdroid's 4.2.2 based ROM.
We tried lots of things so far;
- Pushing files via ADB
Trying ADB, it says device not found, no matter we did we couldn't manage the pc to recognize the phone.
- Mounting SD via CWM
I have HOX, when I enter CWM I can see the option to mount the SD but on One there's no line like this.
- Activating Sideload on TWRP
We also flashed TWRP and tried to use Sideload feature but when we tried to activate it, it says something like "unable to mount .."
- Flashing the RUU
And lastly we tried to flash the RUU, we checked the CID and it says o2___001 and there's no RUU for it.
I just saw that One could be S-OFF and got Super-CID, but to do that again, I have to pull and push some files via ADB so we stuck here.
Could you plese help me on this?
Click to expand...
Click to collapse
if you have problems always use Hasoon All-In-One_Kit for HTC
Am having the same issues, have tried everything I can think off and everything google has suggested. I'm beyond stuck any and all help would be greatly appreciated
my bad exp
I don't know if that help anyone but I had the problem "device not found" when I was trying to side load with HTC AIO KIT.
I removed all my drivers for htc from the control panel and installed only the htc driver (binary100100.googlecode.[com]/files/HTCDriver3.0.0.007.exe). Then the adb started to work. (after the htc drivers install you need to restart your OS)
When I installed new ROM and reboot the device it showed me the screen with the developer's rom. I thought that I failed and flashed new rom then suddenly the new ROM after one minute started to work. So looks like that I should wait long enough for the first and may be it would also starts to work.
Was he by chance having issues charging his phone before he wiped it?
Myself and my brother both a had issues with the USB port going. Couldn't charge while phone was on. PC wouldn't pick it up so no adb. However was able to pickup fastboot and charge while in fastboot mode.
If that's the case you could try running a zip in oemRUU mode just to get an os on there.
Is he soff?
Sent from my HTC One using xda premium
makkasi said:
I don't know if that help anyone but I had the problem "device not found" when I was trying to side load with HTC AIO KIT.
I removed all my drivers for htc from the control panel and installed only the htc driver (binary100100.googlecode.[com]/files/HTCDriver3.0.0.007.exe). Then the adb started to work. (after the htc drivers install you need to restart your OS)
When I installed new ROM and reboot the device it showed me the screen with the developer's rom. I thought that I failed and flashed new rom then suddenly the new ROM after one minute started to work. So looks like that I should wait long enough for the first and may be it would also starts to work.
Click to expand...
Click to collapse
This worked for me. Thanks!!
Once I removed all the extra crap from control panel and used the latest I was able to do adb devices successfully from bootloader / recovery.
I was just having the same problem on the new LG G2 (D803). It was perplexing because the computer *bleeped* every time it attached so I knew that it saw something. Based on the tips here I went to the Device Manager and sure enough there it was... I reinstalled the drivers inside device manager and then I got an easy adb hit on the phone... hmmm :fingers-crossed:
EazyVG said:
Boot TWRP, then select “Mount”, then select only “Data” and connect your HTC One to your computer.
Considering you have adb.exe (Windows, part of fastboot.zip) or on Linux:
cd Downloads\ROM.zip
adb push ROM.zip /sdcard/
Replace ROM.zip with the ROM filename you copied earlier to Downloads (or any other) folder, then install the ROM.
It should be nearly same running CWM recovery. Hope that helps.
Click to expand...
Click to collapse
flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
This worked for my Nexus 4 and TWRP installed. Running the ADB sideload commad from TWRP did not, and just trying to push or sideload from command prompt on PC (Win 8) did not. I had drivers for Nexus 4 recognition installed previously from Nexus Root Toolkit which worked when the Nexus 4 was booted into system, but did not recognize it when wiped and/or in recovery mode. Loading these drivers the Nexus 4 was recognized in recovery mode, and I was able to push the ROM and install using TWRP.
Thanks much!
:good:
timekills said:
This worked for my Nexus 4 and TWRP installed. Running the ADB sideload commad from TWRP did not, and just trying to push or sideload from command prompt on PC (Win 8) did not. I had drivers for Nexus 4 recognition installed previously from Nexus Root Toolkit which worked when the Nexus 4 was booted into system, but did not recognize it when wiped and/or in recovery mode. Loading these drivers the Nexus 4 was recognized in recovery mode, and I was able to push the ROM and install using TWRP.
Thanks much!
:good:
Click to expand...
Click to collapse
Man, I just wanted to say thank you. I've been stuck on this for hours and this did the trick!
Worked
flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
the drivers mentioned here worked for me.
Device : HTC One M7
Recovery : TWRP
Thanks
Thank you so much! This universal driver worked for me! (HTC One Mini with TWRP, soft-bricked)
NiMH_999 said:
Try cwm recovery it has sideload feature I was in a similar situation once before and it worked using cwm recovery
Also. If you want to try use adb again, try to plug in your device and then wait for few seconds before running a push command. It worth mentioning that once adb fail one time, it is not going to work again by repeating the same push command. Once it fails run this command: adb kill-server
This command will stop the previous failed process after killing the server then try to push again
Click to expand...
Click to collapse
Years later, thank you sir, for helping a noob with "adb kill-server"
I was so freaked as to why TWRP wasn't sideloading but PhilZ was.
flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
ADB didn't recognize my Xperia SP in Clockworkmod. That driver worked like a charm Thank you!
This worked for me...
flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
Thank you so much for this. This really helped me out.
I was messing around in CWM touch. In the Storage and Mounts directory..
I've done this before , (format /sdcard)..but this time I went a step further and did (format /data) AND also
(format /data and /data/media) commands. I might have even hit the Format /system command .
Now I'm stuck at the HTC quietly brilliant screen, with the red text on the bottom..and it wont go no further...i just wanted to shine my sd card..
And because I have formated my SD card, there is nothing on it so no back up now... I'm on the Viperone rom..and by formating system i think i wiped the device :S..i really dont know..man.
So i tried opening an ADB shell to see if i could push the Viperone zip from my pc direcctly..but adb doesn't recocgnize the device..
I'm Unlocked bootloader
S-Off
SuperCid- 11111111
Sounds like you’ve got nothing left. Reflash your rom on your super shiny phone.
My device is bricked, like really is bricked..
I can boot into boot loader but what good is that if my PC is saying unknown usb device..
XdaNonDeveloper said:
My device is bricked, like really is bricked..
I can boot into boot loader but what good is that if my PC is saying unknown usb device..
Click to expand...
Click to collapse
fastboot flash your recovery again?
Edit: uninstall everything HTC
reboot pc
plug phone back in and it should install the drivers again
Lim Wee Huat said:
Sounds like you’ve got nothing left. Reflash your rom on your super shiny phone.
Click to expand...
Click to collapse
lol..
faack
bigdaddy619 said:
fastboot flash your recovery again?
Edit: uninstall everything HTC
reboot pc
plug phone back in and it should install the drivers again
Click to expand...
Click to collapse
Not the problem, I can boot into recovery but my phone doesnt start up.
I cant place nothing on the sd card to flash, and ADB SHELL isnt recognizing my device..
so i have to reflash a stock carrier right? by running an RUU exe?
which one can i Use for a M7_UL i think the closest one to a bell canada ruu would be ATT?
Wait can't I just PUSH the zip. to my sdcard then run the zip from clockwork??
XdaNonDeveloper said:
Not the problem, I can boot into recovery but my phone doesnt start up.
I cant place nothing on the sd card to flash, and ADB SHELL isnt recognizing my device..
so i have to reflash a stock carrier right? by running an RUU exe?
which one can i Use for a M7_UL i think the closest one to a bell canada ruu would be ATT?
Click to expand...
Click to collapse
If you can get into recovery then sideload a rom
Edit: uninstall everything HTC
reboot pc
plug phone back in and it should install the drivers again
you sure about that?..
okay but first let me try a command in ADB, whats that show CID command??
if that works then i dont have to uninstall drivers..
XdaNonDeveloper said:
Edit: uninstall everything HTC
reboot pc
plug phone back in and it should install the drivers again
you sure about that?..
okay but first let me try a command in ADB, whats that show CID command??
if that works then i dont have to uninstall drivers..
Click to expand...
Click to collapse
In recovery type adb devices
In bootloader type fastboot devices
bigdaddy619 said:
If you can get into recovery then sideload a rom
Click to expand...
Click to collapse
Would this work even though its for TWRP http://forum.xda-developers.com/showthread.php?t=2318497
XdaNonDeveloper said:
Would this work even though its for TWRP http://forum.xda-developers.com/showthread.php?t=2318497
Click to expand...
Click to collapse
If there is a sideload option in CWM then yes it will work
or adb push nameofrom.zip /sdcard/
bigdaddy619 said:
In recovery type adb devices
In bootloader type fastboot devices
Click to expand...
Click to collapse
In recovery, typing ADB devices gives me a serial with (*recovery*) next to it.
In bootloader it *Lists* no device serial number.
If i try ADB Push should I be in recovery?.. wow I can see the ~# in ADB shell when in recovery ..theres connections being made lol
XdaNonDeveloper said:
In recovery, typing ADB devices gives me a serial with (*recovery*) next to it.
In bootloader it *Lists* no device serial number.
If i try ADB Push should I be in recovery?.. wow I can see the ~# in ADB shell when in recovery ..theres connections being made lol
Click to expand...
Click to collapse
Your good to sideload a rom in recovery
Put the rom zip in the folder you are running your cmd commands from
OR use adb push with the rom in the same folder
adb push rom.zip /data/media/0/
---------- Post added at 08:09 PM ---------- Previous post was at 08:02 PM ----------
You don't need to open an AD shell to push the rom
bigdaddy619 said:
If there is a sideload option in CWM then yes it will work
or adb push nameofrom.zip /sdcard/
Click to expand...
Click to collapse
I did the following command - adb push ViperOne_2.1.0 /sdcard/
got the following - /sbin/sh: adb: not found
bigdaddy619 said:
Your good to sideload a rom in recovery
Put the rom zip in the folder you are running your cmd commands from
OR use adb push with the rom in the same folder
adb push rom.zip /data/media/0/
---------- Post added at 08:09 PM ---------- Previous post was at 08:02 PM ----------
You don't need to open an AD shell to push the rom
Click to expand...
Click to collapse
Okay I'll try again without an ADB shell open
Okay now Im getting the following - cannot stat "ViperOne.." no such file or directory..
CWM touch does not have a sideload option :|
XdaNonDeveloper said:
I did the following command - adb push ViperOne_2.1.0 /sdcard/
got the following - /sbin/sh: adb: not found
Click to expand...
Click to collapse
check my edit sorry
adb push ViperOne_2.1.0.zip /data/media/0/
It should look like that
bigdaddy619 said:
check my edit sorry
adb push ViperOne_2.1.0.zip /data/media/0/
It should look like that
Click to expand...
Click to collapse
OK, this time I added the .ZIP to the end of the file.
Now its showing just a (-) blinking.. never returned a message.. i'll wait for a bit
then i'll try pushing it to the /sdcard/ and see what happens then.
After the blinking - stopped it returned this mesage
failed to copy ViperOne..zip) to data/media/0/': Is a directory
trying again..
[DRIVERS] Latest HTC Drivers [4.2.0.001] Use the ones dated 6-6-13 and don't forget the BMP drivers
[ADB/FB/APX Driver] Universal Naked Driver 0.72 (We dont need no stinking HTC Sync)
If you can't get it to work try what I said about uninstalling the HTC stuff and installing one of these if we can get you recognized ih bootloader we can flash twrp and you can sideload the rom
Please Read the ViperOne Terms of Use...
Team Venom proudly presents....
Thanks bigdaddy lol, thanks for your guidance I am installing Viperone now
XdaNonDeveloper said:
Please Read the ViperOne Terms of Use...
Team Venom proudly presents....
Thanks bigdaddy lol, thanks for your guidance I am installing Viperone now
Click to expand...
Click to collapse
Cool glad you got it going enjoy
After rebooting for a cyanogenmod update which failed to install, my phone will not boot into Cyanogenmod - only clockwork.
I have precious data on the phone that I need to extract, mainly pictures.
ADB only recognizes the phone as "offline" and I cannot pull any files from it.
Any suggestions? Thanks a lot guys.
icer22x said:
After rebooting for a cyanogenmod update which failed to install, my phone will not boot into Cyanogenmod - only clockwork.
I have precious data on the phone that I need to extract, mainly pictures.
ADB only recognizes the phone as "offline" and I cannot pull any files from it.
Any suggestions? Thanks a lot guys.
Click to expand...
Click to collapse
did you cleared cache?
When you are trying to use adb your phone is in cwm recovery?
alray said:
did you cleared cache?
When you are trying to use adb your phone is in cwm recovery?
Click to expand...
Click to collapse
Yes I've cleared the cache and rebooted with the same results - just boots back into Recovery Mode.
And yes, when I am using ADB I am in Recovery Mode. I can't get past that.
icer22x said:
Yes I've cleared the cache and rebooted with the same results - just boots back into Recovery Mode.
And yes, when I am using ADB I am in Recovery Mode. I can't get past that.
Click to expand...
Click to collapse
Do you have a nandroid backup on your phone?
Also is all your drivers properly set and updated on your cumputer? Can you post a screenshot of Windows devices manager with the phone info?
Are you using the original usb cable? Some usb cables only have GND and 5V pins (no data). Also be sure to use usb 2.0 and a usb port directly from your motherboard (not in front of your computer) and don't use any usb hub.
Well I got it recognized by ADB now.
What is the file structure like in order to pull files from the phone?
What commands can I use in ADB to pull the main sd directory?
icer22x said:
Yes I've cleared the cache and rebooted with the same results - just boots back into Recovery Mode.
And yes, when I am using ADB I am in Recovery Mode. I can't get past that.
Click to expand...
Click to collapse
oh and when you are in bootloader, is fastboot working?
Code:
fastboot devices
does it says fastboot usb or only fastboot (in red)
I nerver used adb to pull files so idk. Maybe somthing like ''adb pull /sdcard/ C:\something'' ?
maybe you can find here
or use twrp to make a backup of your data, then pull the backup to your computer
alray said:
oh and when you are in bootloader, is fastboot working?
Code:
fastboot devices
does it says fastboot usb or only fastboot (in red)
I nerver used adb to pull files so idk. Maybe somthing like ''adb pull /sdcard/ C:\something'' ?
Click to expand...
Click to collapse
Thanks man. That helped.
If anyone ever finds themselves in this situation, make sure your SDK packages are updated to the latest Android OS version. This is why ADB was recognizing my device as offline.
Also, running the command adb pull /sdcard/ C:<somewhereonyourPC> will pull all the data from your HTC one.
icer22x said:
Thanks man. That helped.
If anyone ever finds themselves in this situation, make sure your SDK packages are updated to the latest Android OS version. This is why ADB was recognizing my device as offline.
Also, running the command adb pull /sdcard/ C:<somewhereonyourPC> will pull all the data from your HTC one.
Click to expand...
Click to collapse
oh nice to see adb pull /sdcard/ C:<somewhereonyourPC> was the right syntax :laugh:
For the sdk packages you should always make sure it is updated before doing anything to the phone. Same for drivers. An ''adb devices'' and ''fastboot devices'' won't hurt before messing with the phone to make sure everything set correctly.
Now I presume you'll be ok to flash your rom again?1
HI everyone, i have unlocked Mi Mix with EU Global ROM (rooted) and TWRP installed.
After the phone was playing up, I idiotically removed root and deleted Xposed, and it was OK, but tonight I tried to re-install originial ROM, and now can't do anything with the phone.
I can boot into TWRP, but when i try fastboot, the fastboor screen comes up for 20 seconds, then the phone boots to Mi logo, and nothing happens.
I can't get computer to recognize the phone so can't add new ROM - so unsure how to do anything now
Any help appreciated, thanks!
Jamie
Hello !! i think i can help you , well same thin happened to me and what i did was ----∑ Boot into recovery , plug your phone to computer , download Universal ADB Driver and when it detects Adb Composite click install . Then you will be able to unlock and use fastboot. Hope it helps if not im sorry , this is all i know. Good Luck !!!
If you are able to boot in to twrp why just install the original Chinese rom and start from scratch.
YazumiWuHung said:
Hello !! i think i can help you , well same thin happened to me and what i did was ----∑ Boot into recovery , plug your phone to computer , download Universal ADB Driver and when it detects Adb Composite click install . Then you will be able to unlock and use fastboot. Hope it helps if not im sorry , this is all i know. Good Luck !!!
Click to expand...
Click to collapse
Thanks, will try
jaime4272 said:
If you are able to boot in to twrp why just install the original Chinese rom and start from scratch.
Click to expand...
Click to collapse
Hey, thanks for the reply - in TWRP though I can't see any ROM files, or anything to install?
Download a ROM (from desktop)... boot to TWRP (device)... Mount storage... Copy Rom to device... Flash ROM...
lesscro said:
Download a ROM (from desktop)... boot to TWRP (device)... Mount storage... Copy Rom to device... Flash ROM...
Click to expand...
Click to collapse
Hi, thanks for the reply. the problem is, the computer doesn't recognize phone no matter what I do, and I tried the mount storage option but it only shows the phone internal storage!
Sorry, i'm new to this all, thanks,
Jamie
There is sdcard on Mix, then if you see internal storage you can copy rom on it then when u try to flash, navigate to this zip file...
Other u can flash using MiFlashTool using adb feature....
lesscro said:
There is sdcard on Mix, then if you see internal storage you can copy rom on it then when u try to flash, navigate to this zip file...
Other u can flash using MiFlashTool using adb feature....
Click to expand...
Click to collapse
Thanks! Yeah, I noticed it said SD card - but it's not removable, no? So i don't know how to put ROM onto it, when my computer doesn't recognise it!
Thanks
Jamie
When you boot into TWRP, try "adb devices" on your PC. If it's read there, you can use the "adb push filename.zip /sdcard/" command to push the ROM to your phone and then install it.
admirdante said:
When you boot into TWRP, try "adb devices" on your PC. If it's read there, you can use the "adb push filename.zip /sdcard/" command to push the ROM to your phone and then install it.
Click to expand...
Click to collapse
Thanks, is adb devices the same as mimal ADB and fastboot? As in, the program? I have that installed, although it can't find phone
And sorry for knowing so little, i don't have much Android experince.
Thanks,
Jamie
Check if u have an issue with your driver when device is connected... device manager on windows 10...
If yes, check to install driver from computer (not from web or cd's or something like that), select universal USB/adb feature... and ur device will appear...
Weirdali said:
Thanks, is adb devices the same as mimal ADB and fastboot? As in, the program? I have that installed, although it can't find phone
And sorry for knowing so little, i don't have much Android experince.
Thanks,
Jamie
Click to expand...
Click to collapse
Well, I use minimal ADB and fastboot too. Just run it, and try "adb devices". If it's read, you can try the "adb push". If not, please check your Device Manager to see if it is read there.
admirdante said:
Well, I use minimal ADB and fastboot too. Just run it, and try "adb devices". If it's read, you can try the "adb push". If not, please check your Device Manager to see if it is read there.
Click to expand...
Click to collapse
It doesn't appear in Device Manager, and it always has done before. I installed new drivers (made sure they were correct), rebooted PC, and still doesn;'t show in device manager, so not sure what top do!
Thanks,
Jamie
Weirdali said:
It doesn't appear in Device Manager, and it always has done before. I installed new drivers (made sure they were correct), rebooted PC, and still doesn;'t show in device manager, so not sure what top do!
Thanks,
Jamie
Click to expand...
Click to collapse
Damn. Not sure what to do either. Maybe download a fastboot ROM from their site and flash it trough Miflash? Maybe that'll work? If not, then I'm out of ideas.
lesscro said:
Check if u have an issue with your driver when device is connected... device manager on windows 10...
If yes, check to install driver from computer (not from web or cd's or something like that), select universal USB/adb feature... and ur device will appear...
Click to expand...
Click to collapse
I've 100% installed the right drivers, but the device doesn't show in device manager, or anywhere on my PC! It does charge though, which is weird
Weirdali said:
I've 100% installed the right drivers, but the device doesn't show in device manager, or anywhere on my PC! It does charge though, which is weird
Click to expand...
Click to collapse
if you have a usb OTG adapter you can put a rom on an usb stick mount it in twrp and flash from there
Did you do a total wipe? And left your device totally clean?
Weirdali said:
Thanks, is adb devices the same as mimal ADB and fastboot? As in, the program? I have that installed, although it can't find phone
And sorry for knowing so little, i don't have much Android experince.
Thanks,
Jamie
Click to expand...
Click to collapse
Put your ROM in the same folder as your adb drivers folder. Hold shift while right clicking in this folder and choose "open command window here". Boot into TWRP and goto "advanced", then "adb sideload". Now write in the command prompt "adb devices". It should now show your device id and "sideload" after it. Write "adb sideload name of your rom.zip"
At least your phone isn't totally dead like mine. I powered mine off with a full charge and we to power it back on a little while later and it's totally dead now. Even Xiaomi Flash Tool won't let me flash anything. Sees the phone but won't let me flash anything. I get an error code. Xiaomi, via email says they can't service my phone because I'm in the USA. This will be my last Xiaomi phone. So pissed off
I have unlocked the bootloader but when I boot into Twrp recovery and Format the Data then I am unable to Enable the USB in the Enable MTP section . So, because of this I am unable to transfer any files and I am unable to root my phone . Please help me . Thank you .
I have the same issue. Even if I disable and then again enable mtp, the internal storage isn't displayed on my computer. I had formatted data. Because of this I cannot even load any OS zip and my phone is just with no OS. It's not working on any version of twrp posted in the official twrp page for the x526. Can anyone help? It's urgent.
How can I transfer files from my PC to x526 when it's in TWRP? Reinstalling Twrp or Full device wipe didn't help either.
Disabling/Enabling MTP makes the disconnection/connection sound on my PC ,but No x526 data disk is displayed.
Can anyone please reply? Is MTP transfer working fine for everyone else?
RandomDelta said:
Can anyone please reply? Is MTP transfer working fine for everyone else?
Click to expand...
Click to collapse
Why mtp when you can do with otg
Prince4le said:
Why mtp when you can do with otg
Click to expand...
Click to collapse
1. Usb type C otg cables are costly
2. I'm not looking forward to an added hassle of moving files into a flash drive when there is an option to directly put files in root memory.
Here is the solution :-
1 open twrp recovery in your phone
2 connect the data cable to your phone and your computer
3 in the recovery click on ENABLE MTP option
4 after that download MINIMAL ADB AND FASTBOOT SOFTWARE IN YOUR COMPUTER i will post the link
5 install it on your pc and copy any file you wanna past and past it in the c drive programme files x86 minimal adb folder
6 than open the cmd by shift and right click open cmd here
7 in cmd type 1st command - adb devices hit enter
2nd. adb push (file name) without breakets /sdcard/.
Done your file will be copied to twrp and now you can easily flash a rom , file etc.
---------- Post added at 05:53 PM ---------- Previous post was at 05:52 PM ----------
shaikiffu said:
I have unlocked the bootloader but when I boot into Twrp recovery and Format the Data then I am unable to Enable the USB in the Enable MTP section . So, because of this I am unable to transfer any files and I am unable to root my phone . Please help me . Thank you .
Click to expand...
Click to collapse
Solution posted
---------- Post added at 05:56 PM ---------- Previous post was at 05:53 PM ----------
Minimal adb and fastboot link
https://forum.xda-developers.com/showthread.php?t=2317790
Prince4le said:
Here is the solution :-
1 open twrp recovery in your phone
2 connect the data cable to your phone and your computer
3 in the recovery click on ENABLE MTP option
4 after that download MINIMAL ADB AND FASTBOOT SOFTWARE IN YOUR COMPUTER i will post the link
5 install it on your pc and copy any file you wanna past and past it in the c drive programme files x86 minimal adb folder
6 than open the cmd by shift and right click open cmd here
7 in cmd type 1st command - adb devices hit enter
2nd. adb push (file name) without breakets /sdcard/.
Done your file will be copied to twrp and now you can easily flash a rom , file etc.
---------- Post added at 05:53 PM ---------- Previous post was at 05:52 PM ----------
Solution posted
---------- Post added at 05:56 PM ---------- Previous post was at 05:53 PM ----------
Minimal adb and fastboot link
https://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
It's a very roundabout way of doing a simple thing.
Does mtp work for you on your x526?
If yes which version /variant of twrp are you on?
RandomDelta said:
It's a very roundabout way of doing a simple thing.
Does mtp work for you on your x526?
If yes which version /variant of twrp are you on?
Click to expand...
Click to collapse
I had a Chinese recovery and a new also both works
If your mtp is not showing in latest try Chinese recovery maybe it works
Mi sim network does not work what can I do? For Brazil
RandomDelta said:
Can anyone please reply? Is MTP transfer working fine for everyone else?
Click to expand...
Click to collapse
I have the same problem as you have with my cm 14 version of my Ray. I just hear the USB-off sound when plugging in and out the USB cable but never saw a drive symbol on my laptop (Windows 7).
I would wish to find the answer why it doesn't work.
However, I found a way out:
The only file transfer method that works fine is USB-OTG.
Hope that helped...
Best wishes.
shaikiffu said:
I have unlocked the bootloader but when I boot into Twrp recovery and Format the Data then I am unable to Enable the USB in the Enable MTP section . So, because of this I am unable to transfer any files and I am unable to root my phone . Please help me . Thank you .
Click to expand...
Click to collapse
Try ADB push command it works.
Prince4le said:
Here is the solution :-
1 open twrp recovery in your phone
2 connect the data cable to your phone and your computer
3 in the recovery click on ENABLE MTP option
4 after that download MINIMAL ADB AND FASTBOOT SOFTWARE IN YOUR COMPUTER i will post the link
5 install it on your pc and copy any file you wanna past and past it in the c drive programme files x86 minimal adb folder
6 than open the cmd by shift and right click open cmd here
7 in cmd type 1st command - adb devices hit enter
2nd. adb push (file name) without breakets /sdcard/.
Done your file will be copied to twrp and now you can easily flash a rom , file etc.
---------- Post added at 05:53 PM ---------- Previous post was at 05:52 PM ----------
Solution posted
---------- Post added at 05:56 PM ---------- Previous post was at 05:53 PM ----------
Minimal adb and fastboot link
https://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
Just wanted to let you know you saved my life. 3 Years gone but still helpful. Thanks a heck ton!
For me, it worked by using a USB2 port instead of USB3.