Related
Hi, I have a rooted HTC One running the Google Play Edition ROM (first rooted device) but I stupidly hit the 4.3 OTA update when I got the notification. Apparently this is a big no-no, but I didn't know any better and now my phone can't get past HTC's splash screen. I can still enter bootloader and recovery (CWM 6.0.3.2) but that's about it.
I don't have a ROM on the internal memory, so can't just revert to the previous 4.2.2 and because I can't enter the phone's settings to turn on USB Debugging. The phone does not show up in Windows Explorer, nor in 'adb devices' when I do the usual thing on Command Prompt. The phone shows up in Device Manager under Android USB Devices as 'My HTC' but again, no device will appear in Command Prompt, otherwise I'd adb push a new ROM onto the phone.
I've tried clearing cache, dalvik and so on with zero luck. It's causing me all sorts of grief and I've been pulling out my hair since yesterday. I've heard that an OTG micro-USB cable might help by loading a ROM onto a flash card, but I'm looking at a few days delivery (at least) and would like to get this problem sorted ASAP. If you can help, I'll name my firstborn after you.
Strand0410 said:
Hi, I have a rooted HTC One running the Google Play Edition ROM (first rooted device) but I stupidly hit the 4.3 OTA update when I got the notification. Apparently this is a big no-no, but I didn't know any better and now my phone can't get past HTC's splash screen. I can still enter bootloader and recovery (CWM 6.0.3.2) but that's about it.
I don't have a ROM on the internal memory, so can't just revert to the previous 4.2.2 and because I can't enter the phone's settings to turn on USB Debugging. The phone does not show up in Windows Explorer, nor in 'adb devices' when I do the usual thing on Command Prompt. The phone shows up in Device Manager under Android USB Devices as 'My HTC' but again, no device will appear in Command Prompt, otherwise I'd adb push a new ROM onto the phone.
I've tried clearing cache, dalvik and so on with zero luck. It's causing me all sorts of grief and I've been pulling out my hair since yesterday. I've heard that an OTG micro-USB cable might help by loading a ROM onto a flash card, but I'm looking at a few days delivery (at least) and would like to get this problem sorted ASAP. If you can help, I'll name my firstborn after you.
Click to expand...
Click to collapse
I think an RUU for your carrier will do the trick. There are a lot of RUU's posted in the HTC One forums in the various sections, search and find the one for your phone/carrier. Pretty sure that will do the trick!
dgtiii said:
I think an RUU for your carrier will do the trick. There are a lot of RUU's posted in the HTC One forums in the various sections, search and find the one for your phone/carrier. Pretty sure that will do the trick!
Click to expand...
Click to collapse
Hi, I've read up on this option but apparently it unroots my phone and basically returns it to factory settings. This will be my last choice. Thankfully all my photos from a recent trip have been backed up to Dropbox/Drive, but I'd need to root again and jump through all the hoops. I simply want a way to get a new ROM onto the phone to flash it, but neither of my computers are recognising the phone in recovery, with USB debugging off.
Strand0410 said:
Hi, I've read up on this option but apparently it unroots my phone and basically returns it to factory settings. This will be my last choice. Thankfully all my photos from a recent trip have been backed up to Dropbox/Drive, but I'd need to root again and jump through all the hoops. I simply want a way to get a new ROM onto the phone to flash it, but neither of my computers are recognising the phone in recovery, with USB debugging off.
Click to expand...
Click to collapse
Dude, have you a phone that won't get past the splash screen, and you're worried about losing data? If you could get a computer to see the phone, you could push a rom to it in ADB and then sideload it in recovery. If you can't, I think you're left with an RUU I'm afraid.
Strand0410 said:
Hi, I've read up on this option but apparently it unroots my phone and basically returns it to factory settings. This will be my last choice. Thankfully all my photos from a recent trip have been backed up to Dropbox/Drive, but I'd need to root again and jump through all the hoops. I simply want a way to get a new ROM onto the phone to flash it, but neither of my computers are recognising the phone in recovery, with USB debugging off.
Click to expand...
Click to collapse
You can just root/unlock/s-off it after, you've come this far already so you should be familiar with the short process
Flash a ROM using an OTG cable if you have one.
AllAboutTheCore said:
Flash a ROM using an OTG cable if you have one.
Click to expand...
Click to collapse
Cheers for the info guys. I think I'll wait till Monday to buy an OTG cable, fingers crossed this will work. In hindsight, I should have kept some ROM on the phone memory or left debugging on. At least now I'll know not to do an OTA update on a rooted phone.
Hello, I have searched for a solution and found some that worked, My WIFI on my moto x will not connect to any network.
it just started a few weeks ago, But going to in to recovery mode and wiping the cache was working it would connect again.
Thing is it's not only on my home network if i go to any place with WIFI it shows the network, I try to connect and it disappears.
I had the kitkat update I tried to factory reset that did not work also reflashed to jelly bean to see if that would fix the problem. I did not restore any back ups of my device since it could have been a corrupt setting or file that was messing it up. Still no luck I tried some of the router options found on the web about changing the channels. Just to be clear it will not connect to any WIFI not just the one at my house.
I spoke with Fido tech support and after explaining everything i tried they said i was out of options and since I bought the phone right out, I would have to call Motorola and see if they can fix it, thing is i unlocked the bootloader when I rooted it when i first had it with it's stock jelly bean.
I know this is a on going issue for many other moto x, could it just be a hardware issue now my phone has been in a otter box defender since the day i bought it, it has no damage or ever been dropped in water.
it's frustrating, my data works perfect and every thing else on phone works great. I really like the phone but since the bootloader is unlocked the warranty is now void and I only had the phone since dec 2013.
does any one have any last options I could possibly try thanks in advance.
xsnyper said:
Hello, I have searched for a solution and found some that worked, My WIFI on my moto x will not connect to any network.
it just started a few weeks ago, But going to in to recovery mode and wiping the cache was working it would connect again.
Thing is it's not only on my home network if i go to any place with WIFI it shows the network, I try to connect and it disappears.
I had the kitkat update I tried to factory reset that did not work also reflashed to jelly bean to see if that would fix the problem. I did not restore any back ups of my device since it could have been a corrupt setting or file that was messing it up. Still no luck I tried some of the router options found on the web about changing the channels. Just to be clear it will not connect to any WIFI not just the one at my house.
I spoke with Fido tech support and after explaining everything i tried they said i was out of options and since I bought the phone right out, I would have to call Motorola and see if they can fix it, thing is i unlocked the bootloader when I rooted it when i first had it with it's stock jelly bean.
I know this is a on going issue for many other moto x, could it just be a hardware issue now my phone has been in a otter box defender since the day i bought it, it has no damage or ever been dropped in water.
it's frustrating, my data works perfect and every thing else on phone works great. I really like the phone but since the bootloader is unlocked the warranty is now void and I only had the phone since dec 2013.
does any one have any last options I could possibly try thanks in advance.
Click to expand...
Click to collapse
Hi,
I suggest you do a full SBF restore. Don't confuse this with a factory reset....SBFing can actually repair a corrupted filesystem, while a factory reset does not.
You can find a great guide here:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
There are 2 methods. RSD Lite and manual method. Either will work, but pay very close attention to the instructions.
You will find the SBF file for your particular carrier/version here:
http://sbf.droid-developers.org/phone.php?device=0
Good Luck
P.S. I too was having strange WIFI issues. The SBF back to stock fixed it 100%. Hope it works for you.
no luck
samwathegreat said:
Hi,
I suggest you do a full SBF restore. Don't confuse this with a factory reset....SBFing can actually repair a corrupted filesystem, while a factory reset does not.
You can find a great guide here:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
There are 2 methods. RSD Lite and manual method. Either will work, but pay very close attention to the instructions.
You will find the SBF file for your particular carrier/version here:
http://sbf.droid-developers.org/phone.php?device=0
Good Luck
P.S. I too was having strange WIFI issues. The SBF back to stock fixed it 100%. Hope it works for you.
Click to expand...
Click to collapse
I followed the guide step by step, Still no luck.
shows the wifi connections, saves them and shows that it is connecting and just goes back to saved, or disabled. Sometimes even just disappears took it in to have it looked at and the guys at the fido store had the same issue trying to connect to their network.
They keep saying it is a software issue but i'm starting to think it might be hardware. I even tried some fixes with Root to get access to the persist folder to change a file. Tried booting in safe mode to see if it would connect and just does the same thing, I might just be buying a new device just got one of those unlucky ones thanks again tho.
xsnyper said:
I followed the guide step by step, Still no luck.
shows the wifi connections, saves them and shows that it is connecting and just goes back to saved, or disabled. Sometimes even just disappears took it in to have it looked at and the guys at the fido store had the same issue trying to connect to their network.
They keep saying it is a software issue but i'm starting to think it might be hardware. I even tried some fixes with Root to get access to the persist folder to change a file. Tried booting in safe mode to see if it would connect and just does the same thing, I might just be buying a new device just got one of those unlucky ones thanks again tho.
Click to expand...
Click to collapse
I would suspect a hardware issue since you have doctored your persist partition, and you have restored the others via SBF. Bummer :/ Maybe someone else will have another suggestion for you.
Good Luck
Thank you
Thank you Very Much
Working again!
I did not give up and it's working again thanks to samwathegreat, I dont mean to bump my old post but I just want to share with other xt 1058 users that may have been having this issue.
I had mentioned before I used some one else's persist files to try and fix mine and thought it was a hardware problem, Well turns out it was not.
I used the files samwathegreat posted in this post
http://forum.xda-developers.com/showpost.php?p=54089540&postcount=7
I also made a back up of mine, the files in that folder are for a xt 1060 but corrected my problem now I can connect every where again including my house and any other place that offer WIFI.
I was not able to send it to Motorala since I had unlocked the boot loader and warranty was void. All I could do was wait, I even flashed a tmobile 4.4.3 to see if that would fix it with no luck. Any ways just want to say thanks again samwathegreat!!! :good::good:
xsnyper said:
I did not give up and it's working again thanks to samwathegreat, I dont mean to bump my old post but I just want to share with other xt 1058 users that may have been having this issue.
Click to expand...
Click to collapse
Congrats bud!!! Don't worry about the files being from an XT1060 - they are the same on all Moto X variants.
Glad to hear it is all sorted out!!! Enjoy.
Recently, I have recovered from a bootloop when trying to install an older stock Android for my SM-G900A. I now have the original, UCU1ANCE 4.4.2 Firmware. I flashed it through a stock OA1 Kernel with Odin 3.09. Here's the issue.
I need all the help I can receive because I am desperate at this point.
[PROBLEMS!]
1. With my sketchy way of installing an older version, I triggered Knox which keeps telling me to reboot my device, but since it can't repair it on it's own, it continues to give me this error no matter what I do.
2. I've already tried to do the procedure where you Backup all info through Kies, format device, then Recover, but for some reason I can't even connect my device to Kies, it keeps telling me my device is not supported, I've also tried everything in that area to fix it. Still no luck whatsoever.
3. When I try an OTA update, it downloads, tries to install, but when it returns to the home screen it continues to tell me that the process was interrupted by something and it could not be installed.
[OTHER BUGS]
1. Every time I reboot or turn on my device, the WIFI does not automatically connect. It is my personal network and there's no doubt it should work.
2. Camera. When I open the camera, the color of the picture is dilated. The colors that should be where they are, are instead randomly scattered about the image, making those (what should be colored) areas black and white.
As I said I am in desperate need to find these things fixed. I can't find any solutions online for these. It seems like I'm the only person in the world with these problems, and it's not fair. If anyone can give me a solid solution, I would love you forever. THANK YOU.
[OP] Photo of Camera Issue
Here is a photo of what I mean by the Camera color dilation. Demonstrated by a couple of Multi-Color Expo markers.
Download the G900A_Downgrade_to_NCE.tar from here:
https://www.androidfilehost.com/?fid=23622183712464416
Use Odin 3.09 and flash in AP slot. Once it is done then take the OTA for NG3 then OA1
Thanks to @muniz_ri
Tried it once before. It didn't work, ended up with a bootloop after flash of NCE.
ElectricBiskitz said:
Tried it once before. It didn't work, ended up with a bootloop after flash of NCE.
Click to expand...
Click to collapse
Did you use the same file from the link I provided?
Sent from my SAMSUNG-SM-G900A
I have used the same link you provided.
ElectricBiskitz said:
Recently, I have recovered from a bootloop when trying to install an older stock Android for my SM-G900A. I now have the original, UCU1ANCE 4.4.2 Firmware. I flashed it through a stock OA1 Kernel with Odin 3.09. Here's the issue.
I need all the help I can receive because I am desperate at this point.
[PROBLEMS!]
1. With my sketchy way of installing an older version, I triggered Knox which keeps telling me to reboot my device, but since it can't repair it on it's own, it continues to give me this error no matter what I do.
2. I've already tried to do the procedure where you Backup all info through Kies, format device, then Recover, but for some reason I can't even connect my device to Kies, it keeps telling me my device is not supported, I've also tried everything in that area to fix it. Still no luck whatsoever.
3. When I try an OTA update, it downloads, tries to install, but when it returns to the home screen it continues to tell me that the process was interrupted by something and it could not be installed.
[OTHER BUGS]
1. Every time I reboot or turn on my device, the WIFI does not automatically connect. It is my personal network and there's no doubt it should work.
2. Camera. When I open the camera, the color of the picture is dilated. The colors that should be where they are, are instead randomly scattered about the image, making those (what should be colored) areas black and white.
As I said I am in desperate need to find these things fixed. I can't find any solutions online for these. It seems like I'm the only person in the world with these problems, and it's not fair. If anyone can give me a solid solution, I would love you forever. THANK YOU.
Click to expand...
Click to collapse
*UPDATE*
Fingerprint scanner does not work anymore either. Camera fixes itself if you change a setting and put it back.
[OP] It's Fixed!
ElectricBiskitz said:
Recently, I have recovered from a bootloop when trying to install an older stock Android for my SM-G900A. I now have the original, UCU1ANCE 4.4.2 Firmware. I flashed it through a stock OA1 Kernel with Odin 3.09. Here's the issue.
I need all the help I can receive because I am desperate at this point.
[PROBLEMS!]
1. With my sketchy way of installing an older version, I triggered Knox which keeps telling me to reboot my device, but since it can't repair it on it's own, it continues to give me this error no matter what I do.
2. I've already tried to do the procedure where you Backup all info through Kies, format device, then Recover, but for some reason I can't even connect my device to Kies, it keeps telling me my device is not supported, I've also tried everything in that area to fix it. Still no luck whatsoever.
3. When I try an OTA update, it downloads, tries to install, but when it returns to the home screen it continues to tell me that the process was interrupted by something and it could not be installed.
[OTHER BUGS]
1. Every time I reboot or turn on my device, the WIFI does not automatically connect. It is my personal network and there's no doubt it should work.
2. Camera. When I open the camera, the color of the picture is dilated. The colors that should be where they are, are instead randomly scattered about the image, making those (what should be colored) areas black and white.
As I said I am in desperate need to find these things fixed. I can't find any solutions online for these. It seems like I'm the only person in the world with these problems, and it's not fair. If anyone can give me a solid solution, I would love you forever. THANK YOU.
Click to expand...
Click to collapse
Thank you for helping me with my problems. I did realize when I came back to the forum a couple of hours ago that my NCE download was only a kernel and not a firmware. I flashed the link provided and voila! It's fixed. I hope others that may have this problem can use this guide as an example. Because let's face it, you're living on the edge with an Android.
ElectricBiskitz said:
Thank you for helping me with my problems. I did realize when I came back to the forum a couple of hours ago that my NCE download was only a kernel and not a firmware. I flashed the link provided and voila! It's fixed. I hope others that may have this problem can use this guide as an example. Because let's face it, you're living on the edge with an Android.
Click to expand...
Click to collapse
I have the same issue exactly it says my bootloader is fused or something I have to flash the newest kernel to get it too boot up . I think I tried this already but can't hurt to try again .
Found my fire tablet with a black screen and in Amazon system recovery <3e> this morning - not sure how it got into that state & how to get out of it. To my knowledge I didn't press any combination of keys that would get me into that state. It had been only very low battery when I plugged it into the electrical socket last night but I didn't touch it until the morning when I found it in this black screen state.
From searching I think this is the Amazon version of Android System Recovery screen. The exact options are:
-------
Amazon system recovery <3>
Volume up/down to move highlight;
enter button to select.
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
----------
I haven't rooted the tablet although I did apply the "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)"
(http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122)
I've had it for about a month without problems although a couple of days ago it kept trying to update several times in succession.
It has attempted to update a couple of times in the past, which put me into a panic at the time but when I'd check afterwards it would still show 5.0.1. firmware. Also the difference this time was that in the past it would only attempt to update the once, not several times in succession.
I'd assumed that installing "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)" doesn't stop the fire downloading updates but prevents them being installed. So when it happened in the past I didn't worry.
I'm not sure what to do (logically I'd assume I should just select the 1st option and reboot) but I'm not sure how I even got into this screen and if there's a reason for it so hoped someone might be able to advise me.
With thanks & crossed fingers
Frankie
Sorry - one other question!
Which key is the "enter button"?
FrankieChen said:
Sorry - one other question!
Which key is the "enter button"?
Click to expand...
Click to collapse
I've not used it but as we only have three buttons I'm going with the power button.
Pond-life said:
I've not used it but as we only have three buttons I'm going with the power button.
Click to expand...
Click to collapse
That's what I suspected!
Update
Well I ran out of power so the tablet switched off.
When I plugged it into an electricity socket, I decided to try the "reboot system now" option but it just rebooted and cam back to the same screen. I tried it about 4 times with the same result so I tried the "power down" option but it still returned to the same screen when switched back on.
Would really appreciate anyone's help.
Hmm, is there anything in the recovery logs?
Maybe reboot to bootloader, and see if it'll let you twrp to it from a pc, head to the twrp thread and grab the files.
fastboot boot TWRP_Fire_2.8.7.0.img
If it'll do that it's not on 5.1.1 at least, if not it might have tried to get there.
I haven't followed your instructions yet as after I posted last, it started to flash an error message along the lines of battery was too low to "factory reset" and something else - I don't recall what though. I didn't actually select any options apart from reboot and power down.
It was plugged in at the time but I unplugged it & replugged it in, in case for some reason it wasn't charging.
Since then the error message has stopped flashing and I just have a blank screen although you can see it is backlit. Pressing the power button has no effect
And that's on the charger it came with?
It's not looking good.
FrankieChen said:
...I haven't rooted the tablet although I did apply the "Installing Google Framework/Playstore...
...I'd assumed that installing "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)" doesn't stop the fire downloading updates but prevents them being installed....
Click to expand...
Click to collapse
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.
julianpaul said:
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.
Click to expand...
Click to collapse
True but the thread he's referring to does offer that function as an option in the batch file.
http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122
Tomsgt has put together a little install bat (Amazon-Fire-5th-Gen-Install-Play-Store.zip)
Now includes Removing Advertising and Blocks Over the Air System Updates (02 Nov 2015)
Click to expand...
Click to collapse
julianpaul said:
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.
Click to expand...
Click to collapse
It's still useful information - thanks
It's on the charger it came with and it has finally returned to the same Amazon system recovery screen.
In regards to preventing the updates - I think I did that when I installed the google apps but it was the 1st time i ever did this (it's my 1st tablet), and as it was over a month ago I can't be sure - this is all very new to me.
There are 4 recovery logs, completely meaningless to me.
/cache/recovery/last_kmsg
/cache/recovery/last_log
/cache/recovery/last_log1
/cache/recovery/last_log2
the kmsg log zooms past too fast to read with endless pages dealing with "swapper/0"
the last_log seems to have stuff reffering to tzdata, build, product.cpu, ro.product, dalvik and so on . Log1 and log2 seem to be similar stuff but shorter.
Any idea what I should be looking for?
I hoped it would be readable, build number might yield clues.
Given it will show something seems worth trying to see if twrp can see it in bootloader.
It may not have any thing to do with the updates as it was working after the updates had tried to install though I have to admit I only used it for a few minutes and I didn't check it before I plugged it in to charge the night before I found the black screen.
I don't actually have a clue what you mean when you say "twrp can see it in bootloader." so I will have to spend some time reading the forums to figure out what to do.
In desperation this morning I took the wipe data/factory reset option but it didn't work. It returned with the same screen and the error message
E:Error in /cache/recovery/dropbox_last_kmsg (Read-only file system)
I had installed the dropbox app but I had never actually signed in so there wouldn't be any data there.
After rebooting and being returned to the same screen, I attempted again to wipe data/factory reset.
This time it gave the message "data wipe complete" but still returned to the Recovery screen.
I've read the term "bricked" in several of the forums - is this what has happened to my device?
I wondered if I should contact Amazon about it as it's still under warranty but wondered if by installing gapps (and most likely having prevented updates as I followed all the instructions), whether I'd have invalidated my warranty.
FrankieChen said:
After rebooting and being returned to the same screen, I attempted again to wipe data/factory reset.
This time it gave the message "data wipe complete" but still returned to the Recovery screen.
I've read the term "bricked" in several of the forums - is this what has happened to my device?
I wondered if I should contact Amazon about it as it's still under warranty but wondered if by installing gapps (and most likely having prevented updates as I followed all the instructions), whether I'd have invalidated my warranty.
Click to expand...
Click to collapse
At this point, if you have adb drivers (or are comfortable installing them) you may as well try sideloading an update bin file. Links are here. I'd get the 3820 file.
If you want to do this, post back and I or someone will give you the steps. Otherwise, Amazon has been good about replacing tablets if you just describe what you say in the 1st paragraph of your post.
FrankieChen said:
It may not have any thing to do with the updates as it was working after the updates had tried to install though I have to admit I only used it for a few minutes and I didn't check it before I plugged it in to charge the night before I found the black screen.
I don't actually have a clue what you mean when you say "twrp can see it in bootloader." so I will have to spend some time reading the forums to figure out what to do.
Click to expand...
Click to collapse
use the reboot to bootloader option
set pc up with fastboot and see if it can be booted into twrp by fastboot
http://forum.xda-developers.com/showpost.php?p=63635664&postcount=9
http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548
Thank you for the replies. Sorry not to have responded earlier, I had a busy few days and although I have spent a lot of hours trying to read through the forums and find out about twrp, this is the 1st opportunity I have had to get back to trying to resolve the problem.
If I understand correctly, DoLooper has suggested sideloading an update bin file. (3820). I just started trying to do this but as the file to be downloaded is over 600MB and I am on a very slow connection it's showing it's going to take between 7-8 hours to download. If I take this option I will need to wait until tomorrow when I can get to a faster internet.
Pond-life, you have suggested that I
1. "use the reboot to bootloader option"
I'm presuming that this means that I have to select this option from the recovery screen on the tablet - does the tablet have to be attached to the pc via the USB cable when I select the option?
What should I expect once I have selected this option?
Would the tablet not need to be rooted to access the bootloader (as it isn't)?
2. "set pc up with fastboot and see if it can be booted into twrp by fastboot"
When I 1st got the tablet I had difficulties getting the adb drivers to install on my pc and after several days of trying I ended up doing it on another pc which I no longer have access to.
I have tried again to reinstall the drivers using rootjunkies file but again without success. I tried doing it using that method as I remember trying to do it that way (what felt like a billion times) though I don't remember if I finally ended up succeeding with that method or another.
I followed your link "http://forum.xda-developers.com/showpost.php?p=63635664&postcount=9" and tried the 1st method
"[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by Snoop05"
running the "adb-setup-1.4.3.exe" I get "0 files copied" after selecting "Yes to install ADB system-wide" which I recall was the problem (zero files copied) that I had previously.
Openning Device Manager after this does show any Fire or Android devices even when the tablet is connected so I'm assuming that the adb driver installation is failing.
I tried again with "adb-setup-1.3.exe". This time I had 4 files copied and got fire listed in the device manager but when I tried to update the driver I am not given the Android option in the list when I select the option to install driver.
I googled to see if anyone else had this error and I found that some peoplehad difficulties installing on XP but seems that MTP not being supported is the reason and it is resolved by installing WMP v10 and above. I have v11 so presume that's not the problem.
I don't have access to another computer at the moment to try and install the adb drivers but should be able to use another one tomorrow. Last time when I got the drivers to install it was on a vista machine so I wondered if that might have something to do with it.
The other thing that occurred to me was maybe there is something wrong with the cable as I only get the fire shown in the device manager for a few moments before it refreshes and then the fire is no longer shown.
I wondered if I should try to use USBDeview (as per http://www.inlovewithandroid.com/android-usb-connection-problems.html) to see if that is the problem. Certainly if I can the drivers installed on another pc it might suggest that there's a problem with mine.
Anyway, if I get the adb drivers to install successfully on another pc, could you explain what I am trying to do by "booted into twrp by fastboot"? Sorry to be so useless!
Huge thanks
Yeah the files needed will all be pretty hefty. So if thinking about going to a custom rom this would be a good time. Though wouldn't download one or the stock until you've seen if you can use it.
1. Yeah I did mean choose that option on that menu you have onscreen. Doesn't need to be attached to go to the screen technically, but won't be able to do anything there until it is connected so no benefit in not waiting until you are. No doesn't need to be rooted. You'd expect it to go to an almost blank screen with =>FASTBOOT mode.... on it in landscape.
2. On plus side you wouldn't need the adb drivers... But the fastboot ones are probably similarly tricky. These ones worked for me https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
Though I've not used XP.
If it will fastboot into twrp then you can put the original stock rom on or either of the custom ones from there, so it's not dead and can get to downloading. (or 5.1.1 stock using the safe twrp method)
Did you use a different cable on the machine you got it to work on then? If not probably not the cable.
Pond-life said:
Yeah the files needed will all be pretty hefty. So if thinking about going to a custom rom this would be a good time. Though wouldn't download one or the stock until you've seen if you can use it.
1. Yeah I did mean choose that option on that menu you have onscreen. Doesn't need to be attached to go to the screen technically, but won't be able to do anything there until it is connected so no benefit in not waiting until you are. No doesn't need to be rooted. You'd expect it to go to an almost blank screen with =>FASTBOOT mode.... on it in landscape.
2. On plus side you wouldn't need the adb drivers... But the fastboot ones are probably similarly tricky. These ones worked for me https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
Though I've not used XP.
If it will fastboot into twrp then you can put the original stock rom on or either of the custom ones from there, so it's not dead and can get to downloading. (or 5.1.1 stock using the safe twrp method)
Did you use a different cable on the machine you got it to work on then? If not probably not the cable.
Click to expand...
Click to collapse
Thanks for all your help Pond Life.
I had such difficulties get the files to download that in the end I gave up and rang Amazon and they offered to send me a replacement.
Sorry to bail out, this is all new to me and most of what everyone has said has me completely baffled so I've decided to take the easy way out.
Thank you again - I really appreciated all your advice.
FrankieChen said:
Thanks for all your help Pond Life.
I had such difficulties get the files to download that in the end I gave up and rang Amazon and they offered to send me a replacement.
Sorry to bail out, this is all new to me and most of what everyone has said has me completely baffled so I've decided to take the easy way out.
Thank you again - I really appreciated all your advice.
Click to expand...
Click to collapse
Better luck with the new one
Hello! If you're reading this i hope you can help me, cause right now i have no idea what to do. First I'm going to tell my phone specs. I have a rooted, Moto X 2nd Edition XT1092, without any custom ROM installed, running Android Lollipop, with the option to upgrade to marshmallow and an unlocked bootloader. It uses the google launcher by default. I am pretty experienced with root as i have used rooted android phones for more than 4 years now (my first one was a Samsung Galaxy S2) and haven't had any problems until now. I had recently downloaded FaceNiff, one of the sniffing apps for android, and when i pressed start, it would automatically stop. I thought it was maybe a problem of the apps compatibility with my phone, but after researching for a long time, nothing came up so i decided to try another sniffing app. I moved on to DroidSniff, yet, I had the same problem, but this one wouldn't only stop, it would crash. I researched on this app too. Nothing. So I later downloaded one called DroidSheep, and when I started this one, I was lucky that an error was displayed, it was something about Position Independent Executables (PIE), it said "Only Position Independent Executables are supported" or something around those lines. So I decided to research PIE, and I found on the XDA Forums that you could fix this by changing the system/bin/linker file for a custom linker file, which a download link was provided for. I downloaded the file, changed it for the old linker file and tried the apps again. Apparently, I didn't have root access anymore! None of the root apps worked, I thought maybe I had to reboot my phone for my root to come back or for the custom linker to work. So i powered off my phone, turned it on, but instead of turning on, it would say the "Warning unlocked bootloader" thing, and then show a picture of and Android lying down with a caution sign, with the text "No Command" underneath. It's currently in this state, and the phone won't stop repeating this until it runs out of battery. The good thing is I can hold the power and volume down button to enter the fastboot menu, and i can then go into recovery. After this happened, I went to recovery and factory reset my phone, but it still didn't work, so I factory reset it again. It still charges, with a wall plug and with a computer. I think the computer recognises the phone, and I'm pretty sure I have USB Debugging enabled.
To sum this up, I changed the file system/bin/linker for a modified version of it and my phone won't boot up.
Custom linker file: http://forum.xda-developers.com/attachment.php?attachmentid=2821644&d=1403933203
Link to the website where it said you can change the linker files to fix the PIE problem: http://forum.xda-developers.com/google-nexus-5/development/fix-bypassing-pie-security-check-t2797731/page1
AgusC said:
Hello! If you're reading this i hope you can help me, cause right now i have no idea what to do. First I'm going to tell my phone specs. I have a rooted, Moto X 2nd Edition XT1092, without any custom ROM installed, running Android Lollipop, with the option to upgrade to marshmallow and an unlocked bootloader. It uses the google launcher by default. I am pretty experienced with root as i have used rooted android phones for more than 4 years now (my first one was a Samsung Galaxy S2) and haven't had any problems until now. I had recently downloaded FaceNiff, one of the sniffing apps for android, and when i pressed start, it would automatically stop. I thought it was maybe a problem of the apps compatibility with my phone, but after researching for a long time, nothing came up so i decided to try another sniffing app. I moved on to DroidSniff, yet, I had the same problem, but this one wouldn't only stop, it would crash. I researched on this app too. Nothing. So I later downloaded one called DroidSheep, and when I started this one, I was lucky that an error was displayed, it was something about Position Independent Executables (PIE), it said "Only Position Independent Executables are supported" or something around those lines. So I decided to research PIE, and I found on the XDA Forums that you could fix this by changing the system/bin/linker file for a custom linker file, which a download link was provided for. I downloaded the file, changed it for the old linker file and tried the apps again. Apparently, I didn't have root access anymore! None of the root apps worked, I thought maybe I had to reboot my phone for my root to come back or for the custom linker to work. So i powered off my phone, turned it on, but instead of turning on, it would say the "Warning unlocked bootloader" thing, and then show a picture of and Android lying down with a caution sign, with the text "No Command" underneath. It's currently in this state, and the phone won't stop repeating this until it runs out of battery. The good thing is I can hold the power and volume down button to enter the fastboot menu, and i can then go into recovery. After this happened, I went to recovery and factory reset my phone, but it still didn't work, so I factory reset it again. It still charges, with a wall plug and with a computer. I think the computer recognises the phone, and I'm pretty sure I have USB Debugging enabled.
To sum this up, I changed the file system/bin/linker for a modified version of it and my phone won't boot up.
Custom linker file: http://forum.xda-developers.com/attachment.php?attachmentid=2821644&d=1403933203
Link to the website where it said you can change the linker files to fix the PIE problem: http://forum.xda-developers.com/goo...x-bypassing-pie-security-check-t2797731/page1
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. For the best available help, I'm going to move your question to your device's Q&A forum. Good luck!
AgusC said:
Hello! If you're reading this i hope you can help me, cause right now i have no idea what to do. First I'm going to tell my phone specs. I have a rooted, Moto X 2nd Edition XT1092, without any custom ROM installed, running Android Lollipop, with the option (...)
Click to expand...
Click to collapse
I do not know if finally you fixed the problem with your moto, but you can do a clean install of a stock rom, or maybe cm12/cm12.1...
How to, and link with the rom: http://forum.xda-developers.com/moto-x-2014/general/img-5-0-reteuall-xt1092-lxe22-46-19-t2997745
cyker31 said:
I do not know if finally you fixed the problem with your moto, but you can do a clean install of a stock rom, or maybe cm12/cm12.1...
How to, and link with the rom: http://forum.xda-developers.com/moto-x-2014/general/img-5-0-reteuall-xt1092-lxe22-46-19-t2997745
Click to expand...
Click to collapse
Hey! Thanks a lot for the advice, ill try to do what you said, although im not sure how to use fastboot. Ill tell you if it worked.