Related
Right now my phone is stuck in recovery with no ROM installed, so I tried to adb sideload one.
Whenever I try to do anything with adb, my phone does not register at all with my computer under adb devices.
Is there any way someone could help?
cortem said:
Right now my phone is stuck in recovery with no ROM installed, so I tried to adb sideload one.
Whenever I try to do anything with adb, my phone does not register at all with my computer under adb devices.
Is there any way someone could help?
Click to expand...
Click to collapse
What is your recovery?
cortem said:
Right now my phone is stuck in recovery with no ROM installed, so I tried to adb sideload one.
Whenever I try to do anything with adb, my phone does not register at all with my computer under adb devices.
Is there any way someone could help?
Click to expand...
Click to collapse
Make sure u have installed the drivers on ur PC.....
If u havent installed Try HTC Sync that will automatically install the necessary drivers...........
Gud luck
Danny Samuel said:
Make sure u have installed the drivers on ur PC.....
If u havent installed Try HTC Sync that will automatically install the necessary drivers...........
Gud luck
Click to expand...
Click to collapse
Also, let us know the OS you are using.. Win 8 x64 is a tricky BS.. sometimes the drivers work, some times they don't...
for my recovery, I have TWRP 2.5.0.0
I'll check my drivers just in case.
For my computer OS, I have windows 7 x64
I'm on Windows 7 and had the same problem the other night when I needed to sideload a rom, it just would not find my device. Even though I had previously flashed kernels without any issues.
I ended up removing the drivers, re-installing them using Hassoons toolkit and rebooting both PC and phone. It will work, just can be a bit finnicky. I used his toolkit to sideload a rom through twrp.
cortem said:
for my recovery, I have TWRP 2.5.0.0
I'll check my drivers just in case.
For my computer OS, I have windows 7 x64
Click to expand...
Click to collapse
I hope you are giving enough time for the device to be recognized.
BTW TWRP has been updated to 2.6
Sent from my GT-I9300 using xda premium
So i accidently wiped my phone and i have twerp so i tried to push a new os to my phone threw adb but whern a type adb devices no devices show up and i know i have the drivers installed becsause ive done this before 5 times. and i downloades the android sdk and installed everything from 4.0 to 4.4 in the sdk managers. please help me. the problem was i tried to flash twrp using flashify but it took the place of my os.
SuperAndroidTech said:
So i accidently wiped my phone and i have twerp so i tried to push a new os to my phone threw adb but whern a type adb devices no devices show up and i know i have the drivers installed becsause ive done this before 5 times. and i downloades the android sdk and installed everything from 4.0 to 4.4 in the sdk managers. please help me. the problem was i tried to flash twrp using flashify but it took the place of my os.
Click to expand...
Click to collapse
twrp took the place of my OS. and clockwork mod touch is my recovery is there any way i can fix this.
SuperAndroidTech said:
twrp took the place of my OS. and clockwork mod touch is my recovery is there any way i can fix this.
Click to expand...
Click to collapse
you can RUU back to stock
do you have an AT&T Phone
Hello,
Recently I achieved root on my Fire via KingRoot on Fire OS 5.0.1. I disabled the Fire Launcher, and then I stupidly decided to remove KingUser and replace it with SuperSU with SuperSU-Me. Long story short, I rebooted the device when SuperSU finished updating the binaries, and I was greeted with a bricked Fire that would stay on the Fire screen but would not dim and do much else. I can get ADB access, but my Windows PC says that the device is unauthorized and my Linux box says that the device is offline. Any help? I am kind of lost as to what I can do. Thank you in advance
HyperNyan said:
Hello,
Recently I achieved root on my Fire via KingRoot on Fire OS 5.0.1. I disabled the Fire Launcher, and then I stupidly decided to remove KingUser and replace it with SuperSU with SuperSU-Me. Long story short, I rebooted the device when SuperSU finished updating the binaries, and I was greeted with a bricked Fire that would stay on the Fire screen but would not dim and do much else. I can get ADB access, but my Windows PC says that the device is unauthorized and my Linux box says that the device is offline. Any help? I am kind of lost as to what I can do. Thank you in advance
Click to expand...
Click to collapse
Can you get into recovery by holding Power and Volume-Up?
DoLooper said:
Can you get into recovery by holding Power and Volume-Up?
Click to expand...
Click to collapse
Yes, I indeed can get into recovery mode! There might be some hope for my tablet
HyperNyan said:
Yes, I indeed can get into recovery mode! There might be some hope for my tablet
Click to expand...
Click to collapse
Yes, indeed! You can sideload the latest Amazon update. It's 5.1.1. (AFAIK, the November 5.0.1 is not available.) Get the update here: http://kindle-fire-updates.s3.amazo...aZE/update-kindle-20.5.4.1_user_541113320.bin
In recovery, highlight the adb sideload option and press power to get into sideload mode. I don't know linux, but if using Windows install adb drivers. Now, from CMD window, type:
adb sideload <name of the update file>
The update will install and you should be able to boot. You can root with kingroot. After rooting, read/use @bibikalka's guide to reinstall 5.1.1 with SuperSU (to kill Kingroot) and to install Gapps.
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
DoLooper said:
Yes, indeed! You can sideload the latest Amazon update. It's 5.1.1. (AFAIK, the November 5.0.1 is not available.) Get the update here: http://kindle-fire-updates.s3.amazo...aZE/update-kindle-20.5.4.1_user_541113320.bin
In recovery, highlight the adb sideload option and press power to get into sideload mode. I don't know linux, but if using Windows install adb drivers. Now, from CMD window, type:
adb sideload <name of the update file>
The update will install and you should be able to boot. You can root with kingroot. After rooting, read/use @bibikalka's guide to reinstall 5.1.1 with SuperSU (to kill Kingroot) and to install Gapps.
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Click to expand...
Click to collapse
Thank you! My Fire tablet is now able to boot and can run normally, but with root access this time Thank you for helping me through this issue
Update:
I tried to install TWRP without reading that it would not work on the newer Fire OS bootloader, and now I am stuck with no recovery. Attempting to boot into TWRP results in a black screen after the Amazon logo and then it reboots into the OS. I do have access to Android, but I cannot flash the stock recovery as I am currently without a recovery. Any pointers as to how I can possibly get the stock recovery again so then I can redo the whole process of attempting to install CM11?
You may be able to dd the recovery partition. Someone else will have to help with that.
HyperNyan said:
Update:
I tried to install TWRP without reading that it would not work on the newer Fire OS bootloader, and now I am stuck with no recovery. Attempting to boot into TWRP results in a black screen after the Amazon logo and then it reboots into the OS. I do have access to Android, but I cannot flash the stock recovery as I am currently without a recovery. Any pointers as to how I can possibly get the stock recovery again so then I can redo the whole process of attempting to install CM11?
Click to expand...
Click to collapse
Just do this, run the script provided :
http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
I'll get you TWRP and 4.5.3 bootloaders. Then flash 5.4.1 stuff from TWRP.
DoLooper said:
Yes, indeed! You can sideload the latest Amazon update. It's 5.1.1. (AFAIK, the November 5.0.1 is not available.) Get the update here: http://kindle-fire-updates.s3.amazo...aZE/update-kindle-20.5.4.1_user_541113320.bin
In recovery, highlight the adb sideload option and press power to get into sideload mode. I don't know linux, but if using Windows install adb drivers. Now, from CMD window, type:
adb sideload <name of the update file>
The update will install and you should be able to boot. You can root with kingroot. After rooting, read/use @bibikalka's guide to reinstall 5.1.1 with SuperSU (to kill Kingroot) and to install Gapps.
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Click to expand...
Click to collapse
THANK YOU SO EFFING MUCH! I thought my HD6 was done. I was beginning to panic. I went through a LOT of guides to fix it and nothing worked except what you posted.
I know this thread is pretty old, but I haven't fixed the recovery issue yet due to being scared of bricking my tablet. So, just asking, which script do I run? Thanks!
HyperNyan said:
I know this thread is pretty old, but I haven't fixed the recovery issue yet due to being scared of bricking my tablet. So, just asking, which script do I run? Thanks!
Click to expand...
Click to collapse
The recommendations have not changed since the last time you asked Either install stock recovery via Flashify (dig out the recovery image from this zip : 5.2.0_stock_recovery_only.zip , here : http://forum.xda-developers.com/showpost.php?p=62011272 ), or run the script in post #2, and from TWRP, re-install 5.4.1 bootloaders :
http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
Thank you! My tablet is now working great, TWRP successfully installed. Just about a few minutes ago I had a panic attack when it started boot-looping, but then I shut it off for a while, and booted it into TWRP, and it was fine. Go figure I will now attempt to install cm11! Thank you for all of your help!
I tried to flash the team spain 5.8 recovery but it does not work , flash seem to go well but still only boots into stock recovery.
Rom is 15s
zsajak said:
I tried to flash the team spain 5.8 recovery but it does not work , flash seem to go well but still only boots into stock recovery.
Rom is 15s
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=68462069&postcount=2
sanke1 said:
http://forum.xda-developers.com/showpost.php?p=68462069&postcount=2
Click to expand...
Click to collapse
How can I follow your guide If I cannot flash the recovery?
zsajak said:
How can I follow your guide If I cannot flash the recovery?
Click to expand...
Click to collapse
Are you having correct adb drivers installed? On my PC Windows 10 X64, they get installed from Windows Update and show up as "London Marshal adb interface."
It wouldn't hurt to try a different USB port.
Also try fully resetting your phone to factory default from the settings.
I am using X821 and only the TWRP recovery posted in my guide works. Other recoveries do not work for our device.
BTW I have updated my guide. Check it out again.
sanke1 said:
Are you having correct adb drivers installed? On my PC Windows 10 X64, they get installed from Windows Update and show up as "London Marshal adb interface."
It wouldn't hurt to try a different USB port.
Also try fully resetting your phone to factory default from the settings.
I am using X821 and only the TWRP recovery posted in my guide works. Other recoveries do not work for our device.
BTW I have updated my guide. Check it out again.
Click to expand...
Click to collapse
For some reason it was not working, it is now.
I still get a bootloop when I try to flash the resurrection remix rom.
cm13 by teamspain worked fine though
sanke1 said:
Are you having correct adb drivers installed? On my PC Windows 10 X64, they get installed from Windows Update and show up as "London Marshal adb interface."
It wouldn't hurt to try a different USB port.
Also try fully resetting your phone to factory default from the settings.
I am using X821 and only the TWRP recovery posted in my guide works. Other recoveries do not work for our device.
BTW I have updated my guide. Check it out again.
Click to expand...
Click to collapse
I followed your guide and installed twrp correctly and it worked.
I cannot install any rom besides cm13 unofficial though, i always get a bootloop if I install resurrection remix for example.
Its really very annoying, I wiped everything including data and system, only the official 16s roms works and cm13 unofficial, all other roms result in a bootloop.
something is not right here.
twrp not mounting storage data
sanke1 said:
Are you having correct adb drivers installed? On my PC Windows 10 X64, they get installed from Windows Update and show up as "London Marshal adb interface."
It wouldn't hurt to try a different USB port.
Also try fully resetting your phone to factory default from the settings.
I am using X821 and only the TWRP recovery posted in my guide works. Other recoveries do not work for our device.
BTW I have updated my guide. Check it out again.
Click to expand...
Click to collapse
twrp flased but its not mounting storage data, also sideload command to install supersu.zip didnt worked tried several times
its just stopping exactly at 73% everytime
OK, so I flashed TWRP and now I have sort of a halfway bricked x829- I can load TWRP and Fastboot, that's it. I can't adb sideload anything because I get a "cannot read" error. I also can't Fastboot flash anything because all the ROMs I can find are zip files, and not .img files. What am I doing wrong?
Wagmans said:
OK, so I flashed TWRP and now I have sort of a halfway bricked x829- I can load TWRP and Fastboot, that's it. I can't adb sideload anything because I get a "cannot read" error. I also can't Fastboot flash anything because all the ROMs I can find are zip files, and not .img files. What am I doing wrong?
Click to expand...
Click to collapse
ok why do you even want to flash the rom with adb/fastboot?
even if you forgot to cp the rom onto the sdcard - just flash with twrp from a stick - OTG works fine
Horsebeatsbishop said:
ok why do you even want to flash the rom with adb/fastboot?
even if you forgot to cp the rom onto the sdcard - just flash with twrp from a stick - OTG works fine
Click to expand...
Click to collapse
OTG not working for me either. I have a USB C to standard USB adapter and it doesn't see any flash drives (I can see the drive being accessed- the light flashes, but doesn't mount). Do I need a USB OTG C Y adapter? I'm a bit lost why I can't just adb sideload.
Someone explain it to me like I'm a child. Obviously I'm doing something wrong and I'm missing something.
Wagmans said:
OTG not working for me either. I have a USB C to standard USB adapter and it doesn't see any flash drives. Do I need a USB OTG C Y adapter? I'm a bit lost why I can't just adb sideload.
Someone explain it to me like I'm a child. Obviously I'm doing something wrong and I'm missing something.
Click to expand...
Click to collapse
ok sounds like a toughie - never had a problem with OTG (neither with fat32 nor ntfs both works (twpr 3.0.2.1 myself) )
since i'm just a beginner myself i can only give you ideas where i would look:
-do you even see your device in adb service?
-enabled usb-debug?
-current usb driver?
-current adb version?
-correct adb version (32/64b)?
Horsebeatsbishop said:
ok sounds like a toughie - never had a problem with OTG (neither with fat32 nor ntfs both works (twpr 3.0.2.1 myself) )
since i'm just a beginner myself i can only give you ideas where i would look:
-do you even see your device in adb service?
-enabled usb-debug?
-current usb driver?
-current adb version?
-correct adb version (32/64b)?
Click to expand...
Click to collapse
I flashed TWRP properly- but when I put it into recovery I get half a corrupted screen- after the screen goes off if I press the power button I can access TWRP.
I tried flashing multiple flash drives in different formats- yes, I can see the drive LEDs flash after I insert it, but when I try to mount it says "0" space for all drives.
So, I assume everything is working properly because adb can see the device in sideload mode (Win 10 device mgr shows it as a USB device, when in TWRP (no sideload mode) it sees it as ADB device- but when I try to run ADB it doesn't show any devices):
List of devices attached
17963e29 sideload
No devices listed when sideload in TWRP is off.
I should be able to sideload something, but I get:
loading: 'le_x2_x820-5.9.020S.zip'
* cannot read 'le_x2_x820-5.9.020S.zip' *
Every time- every file.
Bricked?
are you using the official twrp ?
you should... https://twrp.me/devices/leecolemax2.html
or use multirom.
you can also transfer the rom first using mtp (in twrp).and flash afterwards.
Gesendet von meinem LEX820 mit Tapatalk
A.N.Droid said:
are you using the official twrp ?
you should... https://twrp.me/devices/leecolemax2.html
or use multirom.
you can also transfer the rom first using mtp (in twrp).and flash afterwards.
Gesendet von meinem LEX820 mit Tapatalk
Click to expand...
Click to collapse
FlashTools64_20161125.zip
I figured it out. I had to download FlashTools64 from Asus in order to sideload the file without the "cannot read" error. Well, that took me all morning.
This should be posted in the TWRP sticky.
I'm sideloading a rom right now. Let's see what happens...
Wagmans said:
FlashTools64_20161125.zip
I figured it out. I had to download FlashTools64 from Asus in order to sideload the file without the "cannot read" error. Well, that took me all morning.
This should be posted in the TWRP sticky.
I'm sideloading a rom right now. Let's see what happens...
Click to expand...
Click to collapse
looks like the standard 15 sec adb installer to me... seems u had the wrong version
Horsebeatsbishop said:
looks like the standard 15 sec adb installer to me... seems u had the wrong version
Click to expand...
Click to collapse
I don't know- I dowloaded it right from the link in the TWRP thread.
Anyways. now when I'm sideloading a ROM it times out at 46% every time (TWRP stops sideload mode). Any ideas?
Wagmans said:
I don't know- I dowloaded it right from the link in the TWRP thread.
Anyways. now when I'm sideloading a ROM it times out at 46% every time (TWRP stops sideload mode). Any ideas?
Click to expand...
Click to collapse
I had sort of the same problem, your not encrypted are you?
Supertacomonkeyexplosion said:
I had sort of the same problem, your not encrypted are you?
Click to expand...
Click to collapse
Nope. Unless I can sideload a ROM I'm stuck because TWRP won't mount a flash drive for me.
why dont you transfer the zip first with mtp?
Gesendet von meinem LEX820 mit Tapatalk
Wagmans said:
Nope. Unless I can sideload a ROM I'm stuck because TWRP won't mount a flash drive for me.
Click to expand...
Click to collapse
You can't boot the OS at all ?
I flashed twrp, couldn't backup,side load or read any OTG. I ended up booting back into my stock OS, loosing twrp, putting teamspain cm13 on, reflashing twrp from fastboot then immediately booting into twrp and flashing CM zip.
Mine was encryption problem though, cm let me decrypt and twrp started working right
Supertacomonkeyexplosion said:
You can't boot the OS at all ?
I flashed twrp, couldn't backup,side load or read any OTG. I ended up booting back into my stock OS, loosing twrp, putting teamspain cm13 on, reflashing twrp from fastboot then immediately booting into twrp and flashing CM zip.
Mine was encryption problem though, cm let me decrypt and twrp started working right
Click to expand...
Click to collapse
Nope. Just TWRP, that's it. As for MTP it doesn't even show up- just as a Android ADB Device in the drivers when in TWRP, and as a USB Device in TWRP Sideload mode. Remember, I'm stuck in either TWRP or Fastboot mode.
Wagmans said:
Nope. Just TWRP, that's it. As for MTP it doesn't even show up- just as a Android ADB Device in the drivers when in TWRP, and as a USB Device in TWRP Sideload mode. Remember, I'm stuck in either TWRP or Fastboot mode.
Click to expand...
Click to collapse
you have strange issues. are you sure you installed the right twrp version for your device? a link would help.
about adb:
i'm using universal ADB drivers and it just works.
http://adbdriver.com
Gesendet von meinem LEX820 mit Tapatalk
Wagmans said:
Nope. Just TWRP, that's it. As for MTP it doesn't even show up- just as a Android ADB Device in the drivers when in TWRP, and as a USB Device in TWRP Sideload mode. Remember, I'm stuck in either TWRP or Fastboot mode.
Click to expand...
Click to collapse
Strange that you lost your OS just flashing a recovery image, I've never seen that before. My last suggestion would be to fastboot flash a earlier version of TWRP.
Not sure of you seen this..... Last resort if you can't figure it out
https://forum.xda-developers.com/le-max-2/how-to/guide-hard-brick-fix-qualcomm-hs-usb-t3492949
Getting closer- I gave up on sideloading and I was finally able to push a ROM to the phone.
Thanks for all the help guys. Now running Chinese .20s ROM. Took long enough.lol
Wagmans said:
Getting closer- I gave up on sideloading and I was finally able to push a ROM to the phone.
Thanks for all the help guys. Now running Chinese .20s ROM. Took long enough.lol
Click to expand...
Click to collapse
Glad you figured it out.
Your running Chinese 20s on x829?
Lots of people will be interested to know how it runs..... Fingerprint? Language? Band 20? VoLTE?
Supertacomonkeyexplosion said:
Glad you figured it out.
Your running Chinese 20s on x829?
Lots of people will be interested to know how it runs..... Fingerprint? Language? Band 20? VoLTE?
Click to expand...
Click to collapse
Been playing with it a bit:
Shows as X820 with 64GB
Fingerprint still doesn't work for me
Google Voice doesn't work- at least I haven't figured it out (Doesn't recognize "OK Google"- I have to go into the app by hand).
Same problem- no VoLTE on AT&T here in US (didn't think it would work- unsupported phone). On Band 2 with LTE (cycled it- was on band 17 before). Haven't checked the other bands yet.
Lots of bloatware. That I can deal with. If I can't get Google voice recognition working properly I'll probably go to a custom ROM.
Wagmans said:
Getting closer- I gave up on sideloading and I was finally able to push a ROM to the phone.
Thanks for all the help guys. Now running Chinese .20s ROM. Took long enough.lol
Click to expand...
Click to collapse
You should share how did u fix it for helping other people in the future
Enviado desde mi ASUS_Z00TD mediante Tapatalk