Related
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?
OK folks, I know some of you are going to jump straight down my throat, but please, back off and stick to the friendly forums that this used to be where anyone would help anyone.
the story so far is that I once loved my Nexus One, I've had it since launch, I have ran Cynogen Mod 7 for a couple of years, I have had MUI roms running, I have played with various kernels, updated radio, upgraded hardware, all was going wonderfully.
the one thing I could never get was full SU!! Heck knows why!!
I then started getting random problems and downloaded the original google frf83 software and flashed the phone via update.zip using amon-ra recovery.
I thought all was well after this, as my phone received 3 OTA updates and now my phone is on...
Android 2.3.6
Baseband 32.41.00.32U_5.08.00.04
Kernel 2.6.35.7-59465-g42bad32 ([email protected] #1)
Build GRK394
I noticed that in the Status (settings) it was displaying my old sim card number, which is not the number for the sim in the phone now. his I thought was odd and that something had gone wrong.
So as most of us would do, I went to boot AmonRa recovery and it wasnt available, it had been overwritten with the default recovery; ok lets just ADB and reflash it, I hadnt used ADB for a couple of years because I did everything through AmonRa's awesome recovery!!
So off I go, install the SDK, all the appropriate packs including the USB driver, just like I did when I originally flashed the phone with the recovery image!
But an old problem came back that I hadnt even been bothered about because I always put stuff on SDcard via a card reader!!
I have had consistent problems with my nexus one for some time now in regards to the USB drivers, no matter what I do the phone will not install and I believe it could be some conflict in the device.
I am running Vista Ultimate (fully registered) and no matter what I do I cannot get the Nexus One to install. It will only display as unknown device, which is absolutely useless.
I have browsed every post and tried everything I have found, and yet nothing is working. I have used devmgmt, I have tried the roll backs, I have tried to install every driver available to get it working. I have uninstalled the device, updated drivers after fresh install attempts, I have even formatted my laptop thinking it may have had a corrupt OS and bought Vista Ultimate.
I am not a complete noob and I have been around these forums for some years, but I never thought I would have to cry out like a 4ucking Noob with such a seemingly simple problem, but it is not simple, I have done everything I can possibly find!!
I must get the USB working in order to get the recovery back, I can access my phones default recovery but it will not work when trying various roms as update.zip!!
I have tried the terminal commands on the phone to install the recovery.img but I do not have SU access and the phone point blank refuses.
I have attempted to change and remove the recovery files reffered that are causing the revert to default recovery, but shock.. I cannot delete because of insufficient permissions. I cannot ADB because the USB driver refuses to install.
So if I cannot change the files due to permissions, I cannot ADB because of USB, I cannot get to Ra's recovery because of bootfiles, I cannot use default recovery to update.zip... I am absolutely losing my mind and I'm going nuts browsing the forums for the second week running, yes I am now on day 12 of trying to fix this problem and at a complete loss...
Can someone please help??
I will even allow remote access to pc because I am that desperate to resurrect my beloved Nexus One.
I also have a Galaxy I9000 without 3 button download mode but that is an entirely different story!!
Please just someone, come to an oldskoolers rescue, and yes PAYMENT will be given to the knight in shiny armour!!
You could try on another computer which doesn't run Vista
tommert38 said:
You could try on another computer which doesn't run Vista
Click to expand...
Click to collapse
Or just use fastboot instead of adb...
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
tommert38 said:
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
Click to expand...
Click to collapse
Install the drivers for fastboot already Jeez and then read How to use android for dummies.
So I know XDA is full of answers to this one, but it seems everyone either has some snarky comment like, "they won't check' or whatever. There are also some ok answers and tuts but some of it's confusing and a lot of the threads go off topic. So i'd like to ask, how do i get my phone back to stock? i have to mail my device back in for a warranty exchange as the speakers and camera stopped working suddenly.
My device is stock rooted, odex rom w/ TWRP. unlocked bootloader. Super CID and S-off. Tampered message gone in boot loader. My laptop runs Windows 8, which I'm having an issue getting the HTC manager to stay open for some reason, even after an uninstall/ reinstall of the manager and drivers. The drivers themselves seemed to have installed fine as my device is recognized as "my HTC" though when in fastboot, my comp will tell me the device is unrecognized. Using the stock usb plug that came with my phone and I've plugged in to both usb 3.0 and 2.0 ports. And yes, I do have ADB in the root of my computer, though I'm wondering if i need a different type of ADB since this is the one i used with windows 7 a while back..or does it matter?
I'd like to get things back to stock as much as possible and would be very appreciative. Thanks!
whitetiger_0603 said:
So I know XDA is full of answers to this one, but it seems everyone either has some snarky comment like, "they won't check' or whatever. There are also some ok answers and tuts but some of it's confusing and a lot of the threads go off topic. So i'd like to ask, how do i get my phone back to stock? i have to mail my device back in for a warranty exchange as the speakers and camera stopped working suddenly.
My device is stock rooted, odex rom w/ TWRP. unlocked bootloader. Super CID and S-off. Tampered message gone in boot loader. My laptop runs Windows 8, which I'm having an issue getting the HTC manager to stay open for some reason, even after an uninstall/ reinstall of the manager and drivers. The drivers themselves seemed to have installed fine as my device is recognized as "my HTC" though when in fastboot, my comp will tell me the device is unrecognized. Using the stock usb plug that came with my phone and I've plugged in to both usb 3.0 and 2.0 ports. And yes, I do have ADB in the root of my computer, though I'm wondering if i need a different type of ADB since this is the one i used with windows 7 a while back..or does it matter?
I'd like to get things back to stock as much as possible and would be very appreciative. Thanks!
Click to expand...
Click to collapse
if your problem is adb have you tried to add it in the "Environment Variables" ?
have you enabled USB debugging in your phone ?
i have windows 8 too and i don't have this kind of problem
I use windows 8 and it has mostly been trouble free for me. However I did have problems with my laptop recognising my phone when in recovery. It eventually worked on it's own but I found this after:
http://forum.xda-developers.com/showthread.php?t=2232799
Maybe try installing the windows 8 drivers above.
Ardmanz said:
I use windows 8 and it has mostly been trouble free for me. However I did have problems with my laptop recognising my phone when in recovery. It eventually worked on it's own but I found this after:
http://forum.xda-developers.com/showthread.php?t=2232799
Maybe try installing the windows 8 drivers above.
Click to expand...
Click to collapse
Yeah i saw that thread, but my phone was already showing up in devices. It just won't be recognized in bootloader or fastboot.
whitetiger_0603 said:
Yeah i saw that thread, but my phone was already showing up in devices. It just won't be recognized in bootloader or fastboot.
Click to expand...
Click to collapse
Mine was recognised everywhere (including recovery). I'd get the beep from windows 8 and the driver would initialise but it wasn't recognised by adb.
If you haven't tried installing the above drivers yet it certainly wouldn't hurt to try.
Ardmanz said:
Mine was recognised everywhere (including recovery). I'd get the beep from windows 8 and the driver would initialise but it wasn't recognised by adb.
If you haven't tried installing the above drivers yet it certainly wouldn't hurt to try.
Click to expand...
Click to collapse
I gave it a shot while in bootloader. Thanks tons. Just a question though, my cope recognizes my phone however when i input "adb devices" in CMD, nothing shows up. Just wondering if that is an issue before i continue.
Rayskull said:
if your problem is adb have you tried to add it in the "Environment Variables" ?
have you enabled USB debugging in your phone ?
i have windows 8 too and i don't have this kind of problem
Click to expand...
Click to collapse
I glanced at something about the environmental variables but i can't find it again. Yeah i have all the correct settings marked to do this
well, as the title says. Its been like this for a few months now, so I decided reinstall the ROM. I've tried different ROMs and every time it shows up as SM-N900s (Galaxy Note 3) in windows. However, on the phone under settings, it says HTC One. On the newest insertcoin ROM it came up in windows as HTC ONE on first boot, but after that, it went back to being the SM-N900s. As well, I always make sure to do a full wipe before I install a new ROM. I checked the build.prop and it list the model ID as HTC ONE so I have no clue what could be going on here. maybe someone here has a suggestion? I'm thinking maybe this is a possible cause of my mediaserver problem that I just couldn't fix, since it happened in every rom I've tried. phone is rooted, unlocked, and S-OFF.
bbmaster123 said:
well, as the title says. Its been like this for a few months now, so I decided reinstall the ROM. I've tried different ROMs and every time it shows up as SM-N900s (Galaxy Note 3) in windows. However, on the phone under settings, it says HTC One. On the newest insertcoin ROM it came up in windows as HTC ONE on first boot, but after that, it went back to being the SM-N900s. As well, I always make sure to do a full wipe before I install a new ROM. I checked the build.prop and it list the model ID as HTC ONE so I have no clue what could be going on here. maybe someone here has a suggestion? I'm thinking maybe this is a possible cause of my mediaserver problem that I just couldn't fix, since it happened in every rom I've tried. phone is rooted, unlocked, and S-OFF.
Click to expand...
Click to collapse
Its most likely a driver issue on your computer, nothing to do with the phone imo. Uninstall these Samsung drivers and install HTC drivers.
didn't work. removed all traces of samsung drivers and software from the drive and the registry, but still comes up as SM-N900s. I Don't get it. There must be some root cause that's creating all the strange (though minor) issues on my phone.
@bbmaster123 install the latest HTC sync manager after uninstalling every older driver version.. do a full reset if that's possible. Do you end up having this problem with every custom Rom that you flash?
It's not a widely reported issue which leads me to thinking that it's more about your computer than your phone.
Still says sm-n900s after installing sync manager. While I haven't tried many custom roms, it still said smn900s in all the rims I've tried, regardless of kitkat or lollipop. I'll try using my brothers laptop tomorrow when he comes to visit and let you know how it goes
bbmaster123 said:
Still says sm-n900s after installing sync manager. While I haven't tried many custom roms, it still said smn900s in all the rims I've tried, regardless of kitkat or lollipop. I'll try using my brothers laptop tomorrow when he comes to visit and let you know how it goes
Click to expand...
Click to collapse
See question 2 here about how to force the HTC driver, this is a driver problem, the 2nd link below is another guy who recently had the same problem.
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
http://forum.xda-developers.com/htc-one/help/hard-brick-how-fix-t3135013/page2 post 15 onwards.
Seanie280672 said:
See question 2 here about how to force the HTC driver, this is a driver problem, the 2nd link below is another guy who recently had the same problem.
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
http://forum.xda-developers.com/htc-one/help/hard-brick-how-fix-t3135013/page2 post 15 onwards.
Click to expand...
Click to collapse
Thanks, I never would have found that!
My phone already comes up as My HTC in device manager when running normally. in any other mode it comes up as android composite usb. It does try and fail to install some driver during boot though, however it only lasts for about 3 seconds, so I have no time to install anything. as well, fastboot boot recovery.img never worked for me anyway, so instead I always just flashed my recoveries. So I can't get my computer to trigger that driver installer besides rebooting the phone, unless you know a way. But yeah, you may be right about it being my pc and not my phone (for this problem anyway).
bbmaster123 said:
Thanks, I never would have found that!
My phone already comes up as My HTC in device manager when running normally. in any other mode it comes up as android composite usb. It does try and fail to install some driver during boot though, however it only lasts for about 3 seconds, so I have no time to install anything. as well, fastboot boot recovery.img never worked for me anyway, so instead I always just flashed my recoveries. So I can't get my computer to trigger that driver installer besides rebooting the phone, unless you know a way. But yeah, you may be right about it being my pc and not my phone (for this problem anyway).
Click to expand...
Click to collapse
Ignore that HTC MTP driver thing that pops up on you computer whilst your phone is booting, we all get that.
fastboot boot recovery command no longer works unless you are on HBOOT 1.44 I think was the last time it worked, only way to do it now is to flash recovery files.
Seanie280672 said:
Ignore that HTC MTP driver thing that pops up on you computer whilst your phone is booting, we all get that.
fastboot boot recovery command no longer works unless you are on HBOOT 1.44 I think was the last time it worked, only way to do it now is to flash recovery files.
Click to expand...
Click to collapse
I don't think my phone even shipped with hboot 1.44. Or maybe it did. what the hell do I know. I guess then I'll have to wait until I can access my brother's pc later today to test it out
Well, turns out you were right all along. its my computer's fault. I guess I'll just have to mess around with the drivers. Thanks for the help! Too bad though, I was hoping that was the root cause of all the other annoying issues on my phone... oh well I guess I can live with unlocking my phone to change songs!
bbmaster123 said:
Well, turns out you were right all along. its my computer's fault. I guess I'll just have to mess around with the drivers. Thanks for the help! Too bad though, I was hoping that was the root cause of all the other annoying issues on my phone... oh well I guess I can live with unlocking my phone to change songs!
Click to expand...
Click to collapse
Get yourself into device manager and add/remove programs, and remove everything to do with your HTC, the trouble is, windows is a pain for still remembering and self installing the driver again upon reboot, so before you restart your computer, unplug your phone, restart your computer, and look up or get a driver cache cleaner for you PC, run that then restart again, now try reinstall the drivers, drivers firtst ie HTC Sync Manager and then plug your phone in.
I finally fixed it just by uninstalling HTC driver installer and plugging my phone back in. windows right away installed:
USB Composite device
HTC One
My HTC
usb mass storage device
HTC Sync manager serial interface
HTC Android Phone USB Device
I probably am going to fresh install windows anyway, been meaning to for a while, but at least I got this one solved. thanks for the help seanie!
I guess I should make new individual threads for my other phone problems, eh? I got the mediaserver battery drain issue, ACR doesn't record anymore for some reason, and the music controls on my lock screen stopped functioning.
bbmaster123 said:
I finally fixed it just by uninstalling HTC driver installer and plugging my phone back in. windows right away installed:
USB Composite device
HTC One
My HTC
usb mass storage device
HTC Sync manager serial interface
HTC Android Phone USB Device
I probably am going to fresh install windows anyway, been meaning to for a while, but at least I got this one solved. thanks for the help seanie!
I guess I should make new individual threads for my other phone problems, eh? I got the mediaserver battery drain issue, ACR doesn't record anymore for some reason, and the music controls on my lock screen stopped functioning.
Click to expand...
Click to collapse
I guess your on Lollipop, The media server issue can be sorted by going into settings - developer options - use NuPlayer (experimental), uncheck it and restart, not sure about the other issues, but it may be worth reflashing your rom and starting fresh.
As for re-installing Windows, prepare for Windows 10 or download the beta of it, when it goes RTM you can use your windows 7 or 8 key to activate it, and it totally rocks, ive been using it as my main driver now for 3 months.
I'm running kitkat (I like it better) and that option isn't under developer options. The only options I've changed under there are enabling usb debugging(but of course) and force gpu rendering. also using dalvik instead of ART, since in kitkat it was buggy, from what I've heard. I do want to also start a fresh install of the same rom, but I just haven't found the time. I did try reinstalling the rom and restoring my data with Titanium Backup, but it just ended up restoring the problem too. For now, I've just been using system tuner to kill mediaserver right after boot, and the problem goes away until next boot.
I have windows 10 build 10130 on another drive and have been testing it since the first TP, and I agree, its pretty sweet, but I'm not 100% sure yet that I'm gonna switch over to it as my main OS on my main PC. I will be definitely updating my windows 8.1 recording computer to Windows 10 as soon as it goes RTM.
bbmaster123 said:
I'm running kitkat (I like it better) and that option isn't under developer options. The only options I've changed under there are enabling usb debugging(but of course) and force gpu rendering. also using dalvik instead of ART, since in kitkat it was buggy, from what I've heard. I do want to also start a fresh install of the same rom, but I just haven't found the time.
I have windows 10 build 10130 on another drive and have been testing it since the first TP, and I agree, its pretty sweet, but I'm not 100% sure yet that I'm gonna switch over to it as my main OS on my main PC. I will be definitely updating my windows 8.1 recording computer to Windows 10 as soon as it goes RTM.
Click to expand...
Click to collapse
Not heard of the media server bug on KitKat soz.
Still don't like the Windows 10 start menu live tiles, but Start10 fixes that.
I've been using classic start, but I always have to keep switching back to the stock start to launch modern apps, which I only barely use, just stuff like calculator and settings
bbmaster123 said:
I've been using classic start, but I always have to keep switching back to the stock start to launch modern apps, which I only barely use, just stuff like calculator and settings
Click to expand...
Click to collapse
bit off topic really, but see the picts below:
cool, then I'll have to give it a try. Much more like the win7 start menu than win10's stock menu.
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