[SOLVED] Rooting Issues - Sony Xperia T, TL, TX, V

hi
clearly this wasn't as simple as the unrevoked method for my last phone,
I ran the script 'root many phone' and it cracked on whilst moaning about permissions and by the time it had finished the phone restarted a bit broken.
It had not play store, none of the previous apps on, wasn't actually rooted at all.
I managed to get play back on there but installing via adb.exe from the command line, and its almost like when I install something, that was on there before, it still has all the settings, so not quite sure what has gone on.
can anyone offer some advice, is it simplest to somehow get myself back to stock and start agin.
maybe I didnt run the root script from the right place. - phone was on and plugged in , usb debugging enabled.
any help much appreicated

I don't know of starting fresh is the 'best' option, but if you haven't done anything that you can't miss our can't do again it's never a wrong try.
Some people also reported that you need allow test locations on. And allow installation of external apps must also be set.
You can always try re rooting without reinstalling.
If you want to reinstall you're best of using Sony update service. Googling is fastest way to find it (not Sony pc companion)
Good luck,
And don't forget to mark your thread solved if it is solved
Did this help? Don't forget to press the thanks button
Sent from my LT30p using xda premium

http://forum.xda-developers.com/showthread.php?t=1914673
have you tried this method? I used it no problem last night.

welshkid said:
http://forum.xda-developers.com/showthread.php?t=1914673
have you tried this method? I used it no problem last night.
Click to expand...
Click to collapse
That's the root many android script he already used according to his post
Did I help? Then please don't forget to press the thanks button.
it's your question solved? Then mark your question solved in your title.
Sent from my Xperia T using XDA Premium.

hi
yes that was what I tried
do I need anything more than that script? (eg those ftf files i keep reading about?)
does the phone need to be on, or in the volume down on boot state
it appears I need 'test locations' and 'external apps' set
anything else I need?
i will try again today at some point
thanks

sure I am being a spanner, but I cant even find the test locations or external apps setting anywhere?
where might that be?
unless test locations is 'mock locations' (guess so)
stilll not finding the external apps option, thought it would be in apps setting somewhere..?
ok found that too in security > unknown sources.
ignore me

That root script didn't work for me either; it kept asking me to connect my device with USB-debugging enabled even though I had already done that.
I would suggest getting back to stock and trying again, BUT use FlashTool instead. It worked perfectly for me in mere seconds.

yesyesimanoob said:
That root script didn't work for me either; it kept asking me to connect my device with USB-debugging enabled even though I had already done that.
I would suggest getting back to stock and trying again, BUT use FlashTool instead. It worked perfectly for me in mere seconds.
Click to expand...
Click to collapse
I downloaded version 0.9.0.0 version, but no XperiaT in the list when I plug it in..
which phone did you pick?
presume the steps are
1. download flashtool
2. Install it on your PC
3. Run the Flashtool and connect your phone (enable USB debugging first)
4. Hit the Root button (second in row)
5. When you see "waiting for restore to finish" open your phone and run Backup&Restore app and restore RootMe.tar file.
6. Wait until Flashtool do the rest of work
thanks

xda-nat said:
I downloaded version 0.9.0.0 version, but no XperiaT in the list when I plug it in..
which phone did you pick?
presume the steps are
1. download flashtool
2. Install it on your PC
3. Run the Flashtool and connect your phone (enable USB debugging first)
4. Hit the Root button (second in row)
5. When you see "waiting for restore to finish" open your phone and run Backup&Restore app and restore RootMe.tar file.
6. Wait until Flashtool do the rest of work
thanks
Click to expand...
Click to collapse
If you mean in the adb drivers list, select Xperia TX. That was the only time I had to select a device.

OK finally success
although using the initial method.
maybe the problem was created by reading the 'root many phones' thread and where it says there is a special case for Xperia T/S etc I took that to mean when running the tool, to pick option '2) special case Xperia S tablet etc' - which didn't work
ran it again picked option '1) Normal' which did work
thanks for all your help
nat

Not necessarily relevant to the OP's problem but I thought I'd share in case it helps anyone else out...
When I tried rooting using Bin4ry's method I kept getting a adb server out of date error and the root failed.
I eventually traced this to having DROID explorer installed which was forcing an old version of adb to be running and stopped the newer version from starting up.
Once I uninstalled the old version I was able to runMe and root the phone.

Related

SOLVED: adb help for "error: device not found" after reboot from cmd

sorry if this clutters up the forum for a bit, i promise to delete it when it dies.
i've recently started using adb when i flashed over to 5.0.2h. i followed the instructions in the tutorial and was able to use adb. 2 nights ago, i began doing more complicated commands (for me) and tried to push a .apk into /system/app.
i wasn't immediately successful but i eventually got it in there and decided to reboot my phone. after this reboot, however, i lost the use of adb. i tried upgrading to the usb drivers haykuro posted, uninstalling them and re-trying the old one, rebooting the computer, rebooting my phone and none of it works. i've since wiped my phone and flashed it with the latest h build from haykuro (thanks haykuro!) but that didn't work either. now i'm trying to see if the 1.5 sdk will work.
i was wondering if anyone would have an idea about what i should do next. should i reinstall adb? try it on another computer? another cable? it's not the worst loss in the world, my phone is fine and my usb cable still works in the conventional way. i even checked to see if i somehow lost root and i was able to get su on the terminal emulator. but i still want the use of adb for nandroid, if nothing else.
thanks in advance!
I had the same problem after flashing to the G rom. I couldn't get ADB to work but fastboot recognized my phone and I was able to flash back to my backup. First time I did a complete wipe before flashing, second time, no wipe, made no difference in either case for me
When you plug Dream into your computer, does it show up in the Device Manager list? What is the entry? Hopefully it says HTC Dream Composite ADB Interface
I just had the same problem, I had to update the driver and it is working fine now.
Which driver did you use? I downloaded the one on the saphire port project page, but couldn't find a way to install it. When I open device manager, there is no ADB interface listed.
zer0day said:
Which driver did you use? I downloaded the one on the saphire port project page, but couldn't find a way to install it. When I open device manager, there is no ADB interface listed.
Click to expand...
Click to collapse
Give me a few minutes I will find you a link for it.
jordanjf86 said:
Give me a few minutes I will find you a link for it.
Click to expand...
Click to collapse
Here it is. http://dl.google.com/android/android_usb_windows.zip after downloading this when you go to update your driver in device manager make sure to use this. Hopefully this will help it worked for me.
jashsu said:
When you plug Dream into your computer, does it show up in the Device Manager list? What is the entry? Hopefully it says HTC Dream Composite ADB Interface
Click to expand...
Click to collapse
yes, that's what it comes up as. and i've tried the usb drivers from haykuro's page and they didn't work before and after rebooting my computer.
i'm on vista and it wont accept the updated drivers. it downloads the standard removable memory drivers and wont let me update to anything else. anybody have any ideas
just installed the 1.5 apk and adb and it works again. for people running haykuro builds, i would suggest trying this if you have adb problems. just intall the 1.5 sdk as normal, copy adb.exe and AdbWinApi.dll into \system32 and you should be good.
unless requested i will delete this thread in two days. thanks everyone!
Hmm... i tried that and its still not working ):
Ive tried like 10 different USB drivers from various sites including this one, downloaded the 1.5 SDK and installed it, wen through several reboots and it always says either that the driver is for the wrong platform, the most up to date one is ALREADY installed (HTC Bootloader), or that Windows couldn't find any drivers.
Under ADB Interface in device manager is "%USB\VID_0BB4&PID0FFF.DeviceDescRelease%"
did you try and update the driver through the device manager? i've heard that it's the only way to update it for some people.
I had already Posted & Solved This Issue here : http://forum.xda-developers.com/showthread.php?t=493703
Go Check It, It ll work for sure....
90% of the time the problem is with the drivers etc. Use this tutorial to fix that : http://goo.gl/OS3Vi
If you still encounter the problem then you can use ADBwireless available at google play to wirelessly connect your device to the computer
Hope it helps :highfive:
Hi
I actually replying about the bible quote you have mentioned? you into theology?

[Q] Need some help getting into Emergency - mode

Hello,
I just got my new Optimus 2x in.
After 2 days using it and draining a lot of battery life installing apps and getting the phone the way I liked it.
The LG apps installed on it started to annoy me bigtime.
So i did the most respectfull thing every tweaker does, i rooted the phone.
Installed the Titanium Backup software and started deleting LG apps.
The deleting part went perfect, then my screen turned black and the only thing working was the kill andriod app software on top.
So i pulled the battery and rebooted, nothing.... the phone got stuck at the LG logo.
Did a Hard reset Volume down + the power button.
It started the installation --> google login --> setting up extra account --> and then got the error about a wizard having problems.
So i guess my rom is corrupt.
Tried updating trough the LG software - emergency and got the message "not possible anymore".
Tried updating trough KDZ firmware update tool but it can not find the phone*.
*Downloaded the original firmware from a thread located here.
Does anybody know how to get in emergency mode so i can try different things.
Or maybe other options i could consider?
If not i'd might considering sending it in for warranty.
But it boots so there must be a way to get things working again.
Thx i appreciate getting all the help and ideas.
Im sorry to hear about your problem
Hope u can fix it
But may i ask how do u root it? I try z4root but no use...
heroddaji said:
Im sorry to hear about your problem
Hope u can fix it
But may i ask how do u root it? I try z4root but no use...
Click to expand...
Click to collapse
I rooted it with superoneclick.
--small update--
If i skip the setup part after my google login, i can force stop the wizard error.
But it does not go into android itself, i get the top bar but thats it.
The LG software recocgnizes my phone but says it's OK and it does not need a update.
Wait for android 2.2.3?
That might do the trick, but then i might have to wait more than 2 weeks
1.Turn the power off. If your LG Optimus 2X is frozen, pull the battery out and reinsert it
2.Hold the Home and Volume Down button
3.Press and hold the Power button until the device turns on
4.Follow the on-screen instructions to reset your device
That's the only option, on this time.
Tried this.
It says S/W Upgrade
Please wait
while upgrading...
and then nothing.
Try boot your phone to android then connect it to pc and run adb shell if shell working put all apk,s from rom dump here.
You have to copy all files to /system/app.
I'll give it a try tomorrow, have to get to work in like 3 hours =)
Im done for today.
Actually, if you get the notification bar, Android is working.
Sounds like you just deleted the Launcher, did you replace it?
If not, adb install and new launcher and you'll be good to go. Although you'll want one on your system partition too!
Have a look in the "Safe to remove" apps thread.
That's it, that's the one i accidently removed.
Any idea how to put it back on the phone?
As described above your post, trough ADB shell?
Can someone post LGLauncher in this thread?
FEARME said:
That's it, that's the one i accidently removed.
Any idea how to put it back on the phone?
As described above your post, trough ADB shell?
Can someone post LGLauncher in this thread?
Click to expand...
Click to collapse
Download here LGHome
Thanks i downloaded it.
But the thing is i can't run adb it gives me the error: device not loaded.
Tried installing the google usb drivers, gives me a no can do.
Another thing i figured out is this: Installing LG PC Suite IV.
It does give me the device connected, but i can not update.
* Can sync contacts
* Can sync Favourites
* Can sync Memo's
But no update (because it's not out yet)
Isn't there a way to fool the suite there is an update but in fact it's just the old firmware and replacing it (making it a repair).
This Thread is discussing the same problem as i am, btw
Fixed!
Obtained the LGLauncher.apk and emailed it to my google account!
Got it out of the above link i posted.
FEARME said:
Fixed!
Obtained the LGLauncher.apk and emailed it to my google account!
Got it out of the above link i posted.
Click to expand...
Click to collapse
Great, but you going to want to fix this problem:
FEARME said:
But the thing is i can't run adb it gives me the error: device not loaded.
Click to expand...
Click to collapse
djmcnz said:
Great, but you going to want to fix this problem:
Click to expand...
Click to collapse
as i said in the other thread you should use root explorer to copu the launcher to /system/app
if you dont it will be gone again if you ever factory reset.
And next time dont delete stuff... just freez it from titanium... Frozen apps are gone (cant be started by the system or seen in launcher) but you get them all back if you factory reset (so no risk of bricking)
OK... we dont get the few megs of free space by freezing... but that is not really an issue on this phone.

Rooting Help

Hi,
I'm new here, and I've just got the new Xperia Z, I do have some experience rooting android, flashing custom roms etc, I've been using the rooting tools to try and get root followed them step by step but no avail.
Now I have checked if I can unlock my bootloader sadly this is a no for me , I've installed the sony drivers (flashtools & fastboot), ran the runme.bat from bin4ry's root with restore pack and still nothing the white screen does come up but I get this error:
"Warning: Activity not started, its current task has been brought to the front
/data/local/tmp/onload.sh ..."
And it just stays on the white screen for ages and does nothing has anyone else had this problem, or is there any help regarding my problem.
Thanks in advance.
[THIS HAS BEEN SOLVED IT WAS JUST WINDOWS BEING A NUISANCE]
deadrising said:
Hi,
I'm new here, and I've just got the new Xperia Z, I do have some experience rooting android, flashing custom roms etc, I've been using the rooting tools to try and get root followed them step by step but no avail.
Now I have checked if I can unlock my bootloader sadly this is a no for me , I've installed the sony drivers (flashtools & fastboot), ran the runme.bat from bin4ry's root with restore pack and still nothing the white screen does come up but I get this error:
"Warning: Activity not started, its current task has been brought to the front
/data/local/tmp/onload.sh ..."
And it just stays on the white screen for ages and does nothing has anyone else had this problem, or is there any help regarding my problem.
Thanks in advance.
Click to expand...
Click to collapse
I guess it would be better if you posted it in the appropriate topic itself
Have you enabled development options and ticked the usb debugging option in that section?
Yes
Lol sorry thought that this might be the place :/ well I've installed the drivers on Windows, the SDK, enabled USB debugging I've done everything that your supposed to but still no luck just seems to get to running .sh and just sticks there ...
deadrising said:
Hi,
I'm new here, and I've just got the new Xperia Z, I do have some experience rooting android, flashing custom roms etc, I've been using the rooting tools to try and get root followed them step by step but no avail.
Now I have checked if I can unlock my bootloader sadly this is a no for me , I've installed the sony drivers (flashtools & fastboot), ran the runme.bat from bin4ry's root with restore pack and still nothing the white screen does come up but I get this error:
"Warning: Activity not started, its current task has been brought to the front
/data/local/tmp/onload.sh ..."
And it just stays on the white screen for ages and does nothing has anyone else had this problem, or is there any help regarding my problem.
Thanks in advance.
[THIS HAS BEEN SOLVED IT WAS JUST WINDOWS BEING A NUISANCE]
Click to expand...
Click to collapse
The same reply I posted in other thread:
Try doing the process again! But before that, open Task Manager kill adb.exe and retry rooting! You can also disconnect the phone, kill the services option in device then connect!
gire.prasad said:
The same reply I posted in other thread:
Try doing the process again! But before that, open Task Manager kill adb.exe and retry rooting! You can also disconnect the phone, kill the services option in device then connect!
Click to expand...
Click to collapse
P.S. adb.exe in Windows, don't try to find it on your phone

[Q] Stuck in bootloop after modifying build.prop

Hey everyone,
I've been eyeing this forum ever since I got my XZ, two months ago. I decided to root a few days ago (that Kingo one click program) and tried to improve my phone a bit everyday.
Today, I tried to hide the navbar by adding that line at the bottom of build.prop. I edited the file with QuikOffice but when I wanted to save, I couldn't simply replace the one there so I saved it somewhere else and copy/pasted it in place of the old one. I shut down the phone and when I tried to turn it on again : bootloop. I don't know how an extra line could mess the phone this much but I'm wondering if I haven't modified some other line without knowing it.
I read that using flashtool was an option so I downloaded an installed SEUS and then Flashtool (EMMA). I connected the phone following the instructions (volume down button) but I got a "Locked phone error". I haven't done much after rooting, especially not setting up a recovery or unlocking the bootloader.
Can anyone guide me through this ? I read things about using an update.zip file but have no idea how that works. I also don't have access to the original build.prop. I've also read people who espaced a bootloop without losing data. But the "locked phone" part doesn't seem to be common. As for the Sony Update Service, it just tells me that the phone already has the last "software version" and that's it.
Thanks.
hm, can you download sony pc companion and try? I used it yesterday and there is a service tab where you can fix and download updates etc. Maybe there is a reinstall firmware or some such
pixellegolas said:
hm, can you download sony pc companion and try? I used it yesterday and there is a service tab where you can fix and download updates etc. Maybe there is a reinstall firmware or some such
Click to expand...
Click to collapse
Thank but PC Companion offered to repair the device but at the cost of all data.
I was able to solve the issue and keep my data by flashing a stock ROM using the actual Flashtool and not Emma. I'm not running CM10.2 and everything is looking great .

Recovery Mode - what to do?

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

Categories

Resources