I've used the tablet for 6 years now and suddenly ... The battery drained to 0 so after charging and powering up .. it got stuck at boot loop, as it gets to the word android after the 5 dots animation. then the android is starting - optimizing app x of 37...
I've tried disconnecting the battery cable and reconnecting them again.
Wiping cash several times.
Usb debuging is enabled.
No root or custom recovery.
The question is .. if I can solve this problem without factory reset as I would resort to that if there's nothing else ... I have some important data That I'd like to backup if I can. even IF I can backup the data then factory reset it .. that would be fine.
corabict said:
I've used the tablet for 6 years now and suddenly ... The battery drained to 0 so after charging and powering up .. it got stuck at boot loop, as it gets to the word android after the 5 dots animation. then the android is starting - optimizing app x of 37...
I've tried disconnecting the battery cable and reconnecting them again.
Wiping cash several times.
Usb debuging is enabled.
No root or custom recovery.
The question is .. if I can solve this problem without factory reset as I would resort to that if there's nothing else ... I have some important data That I'd like to backup if I can. even IF I can backup the data then factory reset it .. that would be fine.
Click to expand...
Click to collapse
if ok connect to computer then you can move files to computer
jjgvv said:
if ok connect to computer then you can move files to computer
Click to expand...
Click to collapse
jjgvv said:
if ok connect to computer then you can move files to computer
Click to expand...
Click to collapse
I can't choose file transfer as USB mode .. so I can't see the files .. even though I hear the sound of USB connecting but I can't see the device.
corabict said:
I can't choose file transfer as USB mode .. so I can't see the files .. even though I hear the sound of USB connecting but I can't see the device.
Click to expand...
Click to collapse
reboot recovery and adb pull sdcard
corabict said:
No root or custom recovery.
Click to expand...
Click to collapse
If your hardware/eMMC is not faulty, then...
If it is unlocked, flash/boot TWRP and get your data.
If it is locked, get RESTOCK and try SAFE UNLOCK...
"Unlock your device without data loss. MiFlash is described in the Unbricking Guide:
https://forum.xda-developers.com/showpost.php?p=75360854&postcount=199
Do not proceed unless you have read the unbricking guide and downloaded all components."
jjgvv said:
reboot recovery and adb pull sdcard
Click to expand...
Click to collapse
Thank you so much for your help.
I tried to do that and it returns an error
adb: error: remote object '\sdcard' does not exist
I tried to make sure the device is recognized so I used Adb devices and it returns:
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
057f2788 device
But that when it's stuck on the animation optimization loop.
If I'm in bootloader ore recovery mod ... it returns
List of devices
And it's empty. So what do you suggest.
k23m said:
If your hardware/eMMC is not faulty, then...
If it is unlocked, flash/boot TWRP and get your data.
If it is locked, get RESTOCK and try SAFE UNLOCK...
"Unlock your device without data loss. MiFlash is described in the Unbricking Guide:
https://forum.xda-developers.com/showpost.php?p=75360854&postcount=199
Do not proceed unless you have read the unbricking guide and downloaded all components."
Click to expand...
Click to collapse
Thank you so much for your help.
I used restock 1 and it downloaded the stock but after that ... I get that
Can't install .inf
because it is not better than the current drivers.
INFO: Returning with code 0x100
Device not found...
1. disconnect it from PC
2. reboot to bootloader again
3. reconnect it to PC
Press any key to continue . . .
And I can't get past that.
corabict said:
Thank you so much for your help.
I tried to do that and it returns an error
adb: error: remote object '\sdcard' does not exist
I tried to make sure the device is recognized so I used Adb devices and it returns:
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
057f2788 device
But that when it's stuck on the animation optimization loop.
If I'm in bootloader ore recovery mod ... it returns
List of devices
And it's empty. So what do you suggest.
Thank you so much for your help.
I used restock 1 and it downloaded the stock but after that ... I get that
Can't install .inf
because it is not better than the current drivers.
INFO: Returning with code 0x100
Device not found...
1. disconnect it from PC
2. reboot to bootloader again
3. reconnect it to PC
Press any key to continue . . .
And I can't get past that.
Click to expand...
Click to collapse
maybe the posts in this thread can help you
[Q] How to mount internal storage through ADB?
A few days ago I cracked my phone screen and I can't see anything, but I want to access the internal storage, can I do this through ADB command?if possible, HOW? Please! can someone help me! Thanks!
forum.xda-developers.com
on boot loop screen of course
jjgvv said:
maybe the posts in this thread can help you
[Q] How to mount internal storage through ADB?
A few days ago I cracked my phone screen and I can't see anything, but I want to access the internal storage, can I do this through ADB command?if possible, HOW? Please! can someone help me! Thanks!
forum.xda-developers.com
on boot loop screen of course
Click to expand...
Click to collapse
Sorry for bothering you ... but really I Don't know what to do.
I used ADb shell then ls ... and listed all the files and sdcard is one of them but when I try to access it it returns this error
cd: /sdcard: No such file or directory
Then tried ..
>> Adb shell ls /sdcard/sdcard
it returns the same message.
>> c:\Adb>adb shell ls /mnt
asec
expand
media_rw
obb
runtime
sdcard *******************
secure
user
c:\Adb>adb shell ls /mnt/sdcard/
/mnt/sdcard/: No such file or directory
So why this error??
Do I need root or what. ??
and if so can I flash twerp and do backup ..if you have any links,
THank you very much for your help.
corabict said:
Sorry for bothering you ... but really I Don't know what to do.
I used ADb shell then ls ... and listed all the files and sdcard is one of them but when I try to access it it returns this error
cd: /sdcard: No such file or directory
Then tried ..
>> Adb shell ls /sdcard/sdcard
it returns the same message.
>> c:\Adb>adb shell ls /mnt
asec
expand
media_rw
obb
runtime
sdcard *******************
secure
user
c:\Adb>adb shell ls /mnt/sdcard/
/mnt/sdcard/: No such file or directory
So why this error??
Do I need root or what. ??
and if so can I flash twerp and do backup ..if you have any links,
THank you very much for your help.
Click to expand...
Click to collapse
adb pull /
and see What happened
avoid adb shell as it needs root.
jjgvv said:
adb pull /
and see What happened
avoid adb shell as it needs root.
Click to expand...
Click to collapse
Yes I tried that and returns this
>>c:\Adb>adb pull /
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: warning: stat failed for path /proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/222/task/1208/fd/15: Protocol not available
Related
Root from Paul didn't come with one, and seeing as we can't get full system access (from what i understand) im curious as to if we can actually get busybox?
The 'busybox on rooted desire' on MoDaCo didn't help at all.
I've installed bb via Titanium, yet Metamorph didn't recognise it anywhere.
Cheers in advance for help
It comes with A2SD - but you can push the busybox binary to /system while the phone is in recovery.
If you pushed bb yourself, use its absolute path (like /data/somewhere/busybox) or put its path in your $PATH to get it going. I personally, without root, put busybox in the free-to-write-to /sqlite* directory (I put * because I don't recall the full name) and it runs fine from there.
do you have a link to apps2sd & does it come with a guide as to how to install it so noobs can understand?
A2SD was taken down "temporarily".
http://android.modaco.com/content/h...ide-now-with-new-improved-easier-root-method/
Sorry
Although this still seems to work:
http://android.modaco.com/content/htc-desire-desire-modaco-com/307398/apps2sd-miniguide/
LeszekSwirski said:
Although this still seems to work:
http://android.modaco.com/content/htc-desire-desire-modaco-com/307398/apps2sd-miniguide/
Click to expand...
Click to collapse
Bare in mind I think it was taken down as (for some) it 'removed root' and also got some phones stuck in a reboot loop. Bad times.
GANJDROID said:
Root from Paul didn't come with one, and seeing as we can't get full system access (from what i understand) im curious as to if we can actually get busybox?
The 'busybox on rooted desire' on MoDaCo didn't help at all.
I've installed bb via Titanium, yet Metamorph didn't recognise it anywhere.
Cheers in advance for help
Click to expand...
Click to collapse
You didn't read to the end of that thread
* install Titanium
* run Titanium
* click the "problems" button and install Busybox
* boot into recovery
* adb shell from my Mac
* mount /system
* cp /data/data/com.keramidas.TitaniumBackup/files/busybox /system/bin
* cd /system/bin
* ./busybox --install -s .
Click to expand...
Click to collapse
By what I've read, though, Metamorph dies on its arse because of the lack of system rw access.
Loccy said:
You didn't read to the end of that thread
Click to expand...
Click to collapse
Aye, I read that, but no Mac, and I can't get to the folder where Titanium saved bb to (assuming that because it's not on the sd card in any data or the titanium folders) the phone system(?)
jayshah said:
Bare in mind I think it was taken down as (for some) it 'removed root' and also got some phones stuck in a reboot loop. Bad times.
Click to expand...
Click to collapse
Had heard about that, but I think he may be working for a solution?
From what I can remember from the rooting guide he said it was 'currently unavailable'
GANJDROID said:
Had heard about that, but I think he may be working for a solution?
From what I can remember from the rooting guide he said it was 'currently unavailable'
Click to expand...
Click to collapse
Yeah, hence it's hopefully only temporary.
GANJDROID said:
Aye, I read that, but no Mac, and I can't get to the folder where Titanium saved bb to (assuming that because it's not on the sd card in any data or the titanium folders) the phone system(?)
Click to expand...
Click to collapse
Install Titanium. Then get your phone into recovery using Paul's Linux ISO. In the Linux console (i.e. where you'll have typed ./step2.sh to get the recovery up), you should be able to do adb shell from there. Then follow my instructions from mount /system onwards.
I didn't follow Pauls guide as I only have access to Windows, so I used the lanarchy guide, which I think might have been taken from The Unlockr.
Maybe fill me in w/ bb according to that?
i am a bit ashamed to ask this but:
....
* boot into recovery
* adb shell from my Mac
* mount /system
....
boot into recovery -> ok
adb shell from mac.. ok? hm, i have macos as a seperate installation and i used it for rooting, so there is a pushfiles folder with recovery-mac.sh.. sudo ./recovery-mac.sh?
How do i mount /system then? Don't know where to navigate to find access to the sdcard . @volumes there are only my harddrive partitions, can't see the sdcard?
No idea, sorry, first time (ok, second time after root) i get in touch with adb, mac, sudo wtf?
Ok, all you need is some kind of environment where adb actually works.
Get your phone into recovery (the green menu screen) using whatever means or method you have.
Then, if you have Windows, you'll need the Android SDK. Ditto on a Mac. Anything with adb so that you can plug your device into your computer, do adb shell, and get a shell window up. Then
mount /system
onwards.
The key is that your phone needs to be in recovery before you do adb shell, otherwise you have no r/w access to /system.
ah! ok, perfect. The android sdk is on my windows computer, the push-files on my mac, that's the problem
thanks for your help!
the recovery is not the problem, but mount /system did nothing because there is no android sdk on my mac.. got it now i think.
mount system -> ok
copy busybok -> ok
when i try to install i get dozens of lines with "no such file or directory".
reboot -> phone not booting, hangs when displaying the HTC Logo omg
flash rom again?
same problem as watercool. Loads of "No such file or directory" messages.
But, I rebooted and it went through as normal, booted the OS fine.
hm, dont want to wipe again, pff..
flashed AhmgskMod mod again without wiping, everything ok now
watercool said:
mount system -> ok
copy busybok -> ok
when i try to install i get dozens of lines with "no such file or directory".
reboot -> phone not booting, hangs when displaying the HTC Logo omg
flash rom again?
Click to expand...
Click to collapse
Sounds like you missed the . off of the end of the
./busybox --install -s .
command.
You need that . if you're following my instructions.
ok, i did it with and without the "."
With the dot there was no response (so probably it installed correctly?).
Anyway it didn't boot afterwards. i will try it again
edit: ok, tried again and my phone stucks @ htc screen
i think busybox is installed but for some reason it doesn't boot (using the ahmgsk mod)
anyway, thanks for your kind help!
I a newbie and I am trying to change my bootanimation.
I have
HTC Desire
OS: Android 2.2 (froyo) I updated it though OTA
HBoot: 0.93.0001
Radio: 5.09.05.30_2
Actually my device was unlocked but branded with UK O2 and loaded with Android 2.1 (Eclair). I used GOLDCARD procedure to make the device unbranded and then updated the OS. I also rooted the device using unrevoked 3.21 and it was successful.
Now the last thing I want to do is to change the bootanimation and I cant make it work. I am using rootexplorer to copy the bootanimation.zip file to
/system/customize/resources
/data/local
But no luck .. the bootanimation screen remains the same “HTC quietly brilliant”
I am also trying to copy bootanimation.zip file in
/system/media
But after copying the file use to disappear. I cant see you though root explorer. I never checked by using "ls" command. Can you please help me guys
Moved to Q&A as not development
I think i dont have completely rooted device
here is the thing i am doing using "abd"
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\android-sdk_r07-windows\android-sdk-windows\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ su
su
Permission denied
$
Click to expand...
Click to collapse
Ok,
Super user permission issue is solved
just have to keep the screen active to see the authentication messages from "Super user permissions" and then it works like a charm.
See the uploaded snapshots as a reference
C:\android-sdk_r07-windows\android-sdk-windows\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ su
su
#
Click to expand...
Click to collapse
ok now i also managed to put bootanimation.zip in /system/media path and its still not working
... really i am out of ideas ... need some help
DO I NEED TO PLAY WITH THE PERMISSIONS OF THE bootanimation.zip FILE.... I am still seeing htc quietly brilliant at start up
helscream said:
ok now i also managed to put bootanimation.zip in /system/media path and its still not working
... really i am out of ideas ... need some help
DO I NEED TO PLAY WITH THE PERMISSIONS OF THE bootanimation.zip FILE.... I am still seeing htc quietly brilliant at start up
Click to expand...
Click to collapse
you cant write to /system/ when the device is booted even if your rooted, because we dont have an unlocked spl yet the nand protection prevents it, you need to put your device into recovery, and use adb to push the bootanimation.zip to /system/customise/resource/ and if that dosent work try pushing it to /system/media/
AndroHero said:
you cant write to /system/ when the device is booted even if your rooted, because we dont have an unlocked spl yet the nand protection prevents it, you need to put your device into recovery, and use adb to push the bootanimation.zip to /system/customise/resource/ and if that dosent work try pushing it to /system/media/
Click to expand...
Click to collapse
hmmm .. ok now i am going to ask you a very stupid question
how i can use adb in recovery mode
my device is turned off
Then I pressed "power + volume down" and I entered HBOOT menu
my device is connected to the PC though a USB
so i have options
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
i chose RECOVERY and then i had an other menu
ClockworkedMod Recovery v2.5.0.7
what to do now
helscream said:
hmmm .. ok now i am going to ask you a very stupid question
how i can use adb in recovery mode
my device is turned off
Then I pressed "power + volume down" and I entered HBOOT menu
my device is connected to the PC though a USB
so i have options
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
i chose RECOVERY and then i had an other menu
ClockworkedMod Recovery v2.5.0.7
what to do now
Click to expand...
Click to collapse
Thats it your in recovery, you can now issue commands to your device using adb just make sure the usb cable is connected,
AndroHero said:
Thats it your in recovery, you can now issue commands to your device using adb just make sure the usb cable is connected,
Click to expand...
Click to collapse
ok now
when I try its saying some thing like this
Code:
C:\android-sdk_r07-windows\android-sdk-windows\tools>adb push bootanimation.zip /system/customise/resource/
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
C:\android-sdk_r07-windows\android-sdk-windows\tools>
sorry ... i cant understand
AndroHero said:
Thats it your in recovery, you can now issue commands to your device using adb just make sure the usb cable is connected,
Click to expand...
Click to collapse
Ok i tried the same command several times without making any change on the device and suddenly it worked. BUT THIS DIDNT SOLVE THE PROBLEM OF CHANGING THE BOOT ANIMATION. ITS STILL THE SAME
Code:
C:\Users\omer\Downloads\android-sdk_r07-windows\android-sdk-windows\tools>adb sh
ell
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
C:\Users\omer\Downloads\android-sdk_r07-windows\android-sdk-windows\tools>abd pu
sh bootanimation.zip /system/customise/resource/
'abd' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\omer\Downloads\android-sdk_r07-windows\android-sdk-windows\tools>adb pu
sh bootanimation.zip /system/customise/resource/
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
C:\Users\omer\Downloads\android-sdk_r07-windows\android-sdk-windows\tools>adb pu
sh bootanimation.zip /system/customise/resource/
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Users\omer\Downloads\android-sdk_r07-windows\android-sdk-windows\tools>adb pu
sh bootanimation.zip /system/customise/resource/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
failed to copy 'bootanimation.zip' to '/system/customise/resource/': Is a direct
ory
C:\Users\omer\Downloads\android-sdk_r07-windows\android-sdk-windows\tools>adb pu
sh bootanimation.zip /system/customise/resource/
adb server is out of date. killing...
* daemon started successfully *
1941 KB/s (4509259 bytes in 2.268s)
C:\Users\omer\Downloads\android-sdk_r07-windows\android-sdk-windows\tools>
helscream said:
ok now
when I try its saying some thing like this
Code:
C:\android-sdk_r07-windows\android-sdk-windows\tools>adb push bootanimation.zip /system/customise/resource/
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
C:\android-sdk_r07-windows\android-sdk-windows\tools>
sorry ... i cant understand
Click to expand...
Click to collapse
ive never come across this error before i found a thread in the hero section about it tho, maybe you should take a look
http://forum.xda-developers.com/showthread.php?t=582378
this seems to be the remedy to your problem acording to that thread
simplyphp said:
The ADB server binds and listen to port 5037. If that port is taken and/or if the daemon is already running, you'll see that error message.
Start task manager and kill adb.exe (all the instances of it).
If that don't work, try rebooting your computer and your phone, and trying again.
If it still don't work, try this:
http://groups.google.com/group/android-developers/msg/dfae5da4a3c80aa8
Click to expand...
Click to collapse
AndroHero said:
ive never come across this error before i found a thread in the hero section about it tho, maybe you should take a look
http://forum.xda-developers.com/showthread.php?t=582378
Click to expand...
Click to collapse
Thankx AndroHero
I think, I found out the problem but I am not sure its the actually reason or not. If it worked I will come back to post my results.
helscream said:
Thankx AndroHero
I think, I found out the problem but I am not sure its the actually reason or not. If it worked I will come back to post my results.
Click to expand...
Click to collapse
i hope you can sort it out
Hey guys.
I've been installing roms on my Galaxy Nexus and my Nexus One before that... but today I was talking with my gf while installing a rom and after formatting the system I accidentally formatted the sd card. Now I don't have a ROM on the phone and am unable to access the phone from my mac or a PC to install a ROM... did I just brick this? I have CWM touch recover v6.0.3.1 and going into mount sd doesn't work.
Thanks for any assistance.
pikaia said:
Hey guys.
I've been installing roms on my Galaxy Nexus and my Nexus One before that... but today I was talking with my gf while installing a rom and after formatting the system I accidentally formatted the sd card. Now I don't have a ROM on the phone and am unable to access the phone from my mac or a PC to install a ROM... did I just brick this? I have CWM touch recover v6.0.3.1 and going into mount sd doesn't work.
Thanks for any assistance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1529058
http://forum.xda-developers.com/showthread.php?t=1812959
10chars
beekay201 said:
http://forum.xda-developers.com/showthread.php?t=1529058
http://forum.xda-developers.com/showthread.php?t=1812959
10chars
Click to expand...
Click to collapse
I've worked through those How-Tos. I've attempted to push in adb and despite the fact that a fastboot devices shows my phone, a push produces the error: device not found
any further input?
Code:
./adb-mac push /Users/Aaron/Desktop/fastboot/ROMS /sdcard/
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
fastboot != adb.
pikaia said:
Code:
./adb-mac push /Users/Aaron/Desktop/fastboot/ROMS /sdcard/
* daemon not running. starting it now *
* daemon started successfully *
[B]error: device not found
[/B]
Click to expand...
Click to collapse
somehow I doubt 'adb devices' outputs your device id. At least in Linux there's a adb parameter that is 'adb start-server'.. which is that "daemon not running, starting it now", and another one that is 'adb devices'..which in your case, comes up "error: device not found".
Check your ADB drivers. CWM had adbd enabled by default, from what I remember.
meet my maguro - ADB style ('adbdev' is just an alias for 'adb devices')
Code:
+6:59% adbdev
List of devices attached
016B*******1B010 device
and fastboot
Code:
+6:59% fastboot devices
016B*******1B010 fastboot
Oh and adb in recovery:
Code:
+7:07% adb shell ls /sdcard/
Alarms Podcasts
Android ROMs
DCIM Ringtones
Download TWRP
MAME4all UPDATE-SuperSU-v1.34.zip
MAME4droid UltimateCustomClockWidget
Movies cm-10.1-20130721-NIGHTLY-maguro.zip
Music gapps-jb-20130615-signed.zip
My Documents tapatalk4
Notifications uccwOutput
Pictures
+7:08% adbdev
List of devices attached
016B*******1B010 recovery
Zepius said:
fastboot != adb.
Click to expand...
Click to collapse
this.
fastboot and adb are not even close to being the same thing....
Pirateghost said:
this.
fastboot and adb are not even close to being the same thing....
Click to expand...
Click to collapse
Ok, clearly I was mistaken. With that said, adb is NOT finding my phone, so is there a way I can push a ROM to my phone using fastboot (which is finding my phone), Or some other feature which I am clearly missing?
I do appreciate the help, despite whatever it might seem I have gone through the help and How-Tos but have been unsuccessful... I'm sure there is something I'm missing... which is why I'm asking.
Thank you again for any assistance.
Are you in recovery when you are trying to connect to adb?
Sent from my Galaxy Nexus
pikaia said:
Ok, clearly I was mistaken. With that said, adb is NOT finding my phone, so is there a way I can push a ROM to my phone using fastboot (which is finding my phone), Or some other feature which I am clearly missing?
I do appreciate the help, despite whatever it might seem I have gone through the help and How-Tos but have been unsuccessful... I'm sure there is something I'm missing... which is why I'm asking.
Thank you again for any assistance.
Click to expand...
Click to collapse
you can flash the stock rom in fastboot very easily.
OK here is the story
FireTV 51.1.0.2_user_510058520 2 days old
Rooted and installed busybox everything was fine. So I figured I wanted the latest Rootable version.
Followed this guide (http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/ )
Problems started here: at the end trying to push update.zip to cache got error "cannot stat ‘update.zip’: no such file or directory"
update.zip was in same directory as adb
So I went and Installed Clockworkmod Recovery and pushed it using "adbfire" since it can push files to /sdcard (used this other guide http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/)
Went and rebooted into clockworkmod and that's when I saw the Previous command running trying to install update.zip wich was not there cuz I was never able to push it in the first place.
Well I could not get out of there by any means since I don't have a USB keyboard with me anymore
well I pushed the update.zip to /sdcard (again using adbfire) and used the mv command to transfer the file to /cache aaaaaaand reboot
Now I have my android logo updating the firmware and rebooting the FireTV when reaching the middle of the process just to start again and again
note: I can still connect to my firetv via adb while the screen is on and lose connection when reboots.
Any help would be greatly appreciated
Thanks in advance
LastDeuS said:
OK here is the story
FireTV 51.1.0.2_user_510058520 2 days old
Rooted and installed busybox everything was fine. So I figured I wanted the latest Rootable version.
Followed this guide (http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/ )
Problems started here: at the end trying to push update.zip to cache got error "cannot stat ‘update.zip’: no such file or directory"
update.zip was in same directory as adb
So I went and Installed Clockworkmod Recovery and pushed it using "adbfire" since it can push files to /sdcard (used this other guide http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/)
Went and rebooted into clockworkmod and that's when I saw the Previous command running trying to install update.zip wich was not there cuz I was never able to push it in the first place.
Well I could not get out of there by any means since I don't have a USB keyboard with me anymore
well I pushed the update.zip to /sdcard (again using adbfire) and used the mv command to transfer the file to /cache aaaaaaand reboot
Now I have my android logo updating the firmware and rebooting the FireTV when reaching the middle of the process just to start again and again
note: I can still connect to my firetv via adb while the screen is on and lose connection when reboots.
Any help would be greatly appreciated
Thanks in advance
Click to expand...
Click to collapse
Well you can do
Code:
adb reboot recovery
to get to recovery, Then in one window run
Code:
adb shell
and in then run
Code:
/sbin/recovery-input
and then in another window run adb shell again and this time run killall recovery. Then you can use recovery-input to control recovery. I would recommend pushing one of the prerooted updates, flashing it, doing a factory reset, then reboot and it should be fine. Another option is to use adb sideload.
rbox said:
Well you can do
Code:
adb reboot recovery
to get to recovery, Then in one window run
Code:
adb shell
and in then run
Code:
/sbin/recovery-input
and then in another window run adb shell again and this time run killall recovery. Then you can use recovery-input to control recovery. I would recommend pushing one of the prerooted updates, flashing it, doing a factory reset, then reboot and it should be fine. Another option is to use adb sideload.
Click to expand...
Click to collapse
First thanks for your quick reply
the thing is my current state is Recovery looping while the firetv tries to install the new software so what I see is
Amazon logo
Android logo updating but just the blue bar filling
then shuts down
then android logo again and again
the commands you recommended were adb reboot recovery ----> /sbin/sh: not found
adb shell ---->/sbin/sh: not found
/sbin/recovery-input ----> Welcome to recovery input (this one works but I'm not quite where I need to be to control anything)
killall recovery ----> This command just reboots again into the same state
You also mentioned adb sideload but that's after I regain control of recovery right???
Please let me know other options to get out of this loop
Thanks again
LastDeuS said:
First thanks for your quick reply
the thing is my current state is Recovery looping while the firetv tries to install the new software so what I see is
Amazon logo
Android logo updating but just the blue bar filling
then shuts down
then android logo again and again
the commands you recommended were adb reboot recovery ----> /sbin/sh: not found
adb shell ---->/sbin/sh: not found
/sbin/recovery-input ----> Welcome to recovery input (this one works but I'm not quite where I need to be to control anything)
killall recovery ----> This command just reboots again into the same state
You also mentioned adb sideload but that's after I regain control of recovery right???
Please let me know other options to get out of this loop
Thanks again
Click to expand...
Click to collapse
If recovery is still in some kind of a loop, doing rm /cache/recovery/* while in adb shell should clear that up.
rbox said:
If recovery is still in some kind of a loop, doing rm /cache/recovery/* while in adb shell should clear that up.
Click to expand...
Click to collapse
I tried rm /cache/recovery/* and I think it erases that folder cuz when trying to run same command again it states as no such file or directory but then I wait and reboots again into same loop
again ran killall recovery and nothing reboot again looping T_T
LastDeuS said:
I tried rm /cache/recovery/* and I think it erases that folder cuz when trying to run same command again it states as no such file or directory but then I wait and reboots again into same loop
again ran killall recovery and nothing reboot again looping T_T
Click to expand...
Click to collapse
I dunno. Recovery shouldn't be doing any looping... With an empty /cache/recovery it should just sit there and do nothing. And it makes it more difficult without a usb keyboard.
rbox said:
I dunno. Recovery shouldn't be doing any looping... With an empty /cache/recovery it should just sit there and do nothing. And it makes it more difficult without a usb keyboard.
Click to expand...
Click to collapse
I can bring a keyboard from work tomorrow if that would help us troubleshoot cuz right now my keyboard is wireless
I know I've been asking a lot this last hour but can you please point me in the right direction so tomorrow I can Try something else using an usb keyboard?
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset Cache
Reboot
or
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset to factory defaults
Reboot
roligov said:
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset Cache
Reboot
or
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset to factory defaults
Reboot
Click to expand...
Click to collapse
Well yesterday I couldn't bring the keyboard but now I have it in front of me but I haven't been able to reproduce the recovery mode with the keyboard combination.
I know it works because the firetv reboots but sometimes goes to the initial amazon logo and sometimes just the same updating android logo
So any suggestions now that we have the keyboard here???
OK I finally figured it out.
All started when I ran the command "echo --update_package=/cache/update.zip > command" to update to a stock ROM but was never able to PUSH the actual file... kept getting error "cannot stat ‘update.zip’: no such file or directory"
THEN
I successfully installed Clockworkmod Recovery (luckily) and when rebooted to recovery I was presented with Clockwmod Recovery asking if sure to install the NON PRESENT "rom.zip"
BUT i didn't have a keyboard with me at that moment and didn't know the "control recovery" command either... SO I thought to find a different way to PUSH the file....
So I used push file function in adbfire to get the file into /sdcard/ and the the mv command to get it to /cache
SO I got my problem right there wich I was able to reproduce today: When you connect to adb during recovery or booting the FireTV you will get this error for most commands including su ----> "/sbin/sh: not found"
NOW if you try to push a file it will say it got pushed but only half of it or some shortcut of it I'm not sure
The thing is with that half pushed file the system now obeys "echo --update_package=/cache/update.zip > command" and starts updating and shuts down reboots and update again, whatever you do it keeps on booting again to the same state(trust me nothing works)
What I did basically with the few seconds I got between reboots I ran "rm -f /cache/*.bin" and rm -f /cache/*.zip to erase all cache folder and then I was again asked to install the file (not there again) and disabled recovery flash
Anyways thanks for all the replys I got really appreciated all your help and keep up the good work ppl I hope this helps someone out there besides me.
I'm now running the latest prerooted rom from rbox thanks again for that
have a good one
question: Is there an actual gui windows app to transfer files to FireTV???
2: Do I need to block updates for this custom rom also or that's already implemented?
The pre-rooted ROM blocks updates. You can check using TiBU. I think three files are frozen.
Glad you pulled out of your crash.
schneid said:
The pre-rooted ROM blocks updates. You can check using TiBU. I think three files are frozen.
Glad you pulled out of your crash.
Click to expand...
Click to collapse
It doesn't. But if you had dcp blocked before installing it, it'll remain blocked. You should always have dcp blocked.
rbox said:
It doesn't. But if you had dcp blocked before installing it, it'll remain blocked. You should always have dcp blocked.
Click to expand...
Click to collapse
TiBU shows mine "frozen". Did I do that previously with something else?
schneid said:
TiBU shows mine "frozen". Did I do that previously with something else?
Click to expand...
Click to collapse
Either you froze it with titanium previously or you did the pm disable command.
rbox said:
Either you froze it with titanium previously or you did the pm disable command.
Click to expand...
Click to collapse
I did do the PM disable thing but thought your rooted ROM would undo it. Guess not. Anyway, I'm happy. Thanks.
Think I bricked mine
Just got my firetv and did the usual ie. rooted, su added , then I Installed Clockworkmod Recovery and tried to upgrade to the latest rootable firmware, using update.zip to /cache and then it just keeps rebooting.
No amazon screen, goes to Andriod loads 1/3 of the way andf reboots, over and over.
picture attached
Cant adb to it , when doing the alt+print screen+i with my keyboard just reboots it faster
Think i'm offically bricked and its a bummer , be careful when changing firmware with CWR and sending your update.zip .
I dont know where it went wrong but it did
Note3usr said:
Just got my firetv and did the usual ie. rooted, su added , then I Installed Clockworkmod Recovery and tried to upgrade to the latest rootable firmware, using update.zip to /cache and then it just keeps rebooting.
No amazon screen, goes to Andriod loads 1/3 of the way andf reboots, over and over.
picture attached
Cant adb to it , when doing the alt+print screen+i with my keyboard just reboots it faster
Think i'm offically bricked and its a bummer , be careful when changing firmware with CWR and sending your update.zip .
I dont know where it went wrong but it did
Click to expand...
Click to collapse
Don't use update.zip and don't put it in /cache. Since so many people seem to be screwing up by doing that, I'm going to disable the automatic flashing in the next version. As for not being able to adb to it, it's probably using a different ip than what you are expecting. In every instance of people doing this, adb has always worked. Then just rm whatever you put in /cache. Next time use sideload or put it in /sdcard.
rbox said:
Don't use update.zip and don't put it in /cache. Since so many people seem to be screwing up by doing that, I'm going to disable the automatic flashing in the next version. As for not being able to adb to it, it's probably using a different ip than what you are expecting. In every instance of people doing this, adb has always worked. Then just rm whatever you put in /cache. Next time use sideload or put it in /sdcard.
Click to expand...
Click to collapse
I send the update.zip to the ftv with Amazon FireTV Utility App and it looked like it went all the way through , by default isnt that where it send it to ? /cache
Ive been trying to ping the ip , or shell to it but how much times could I have when it just keeps cycling. I dont think its possible to adb to it at this point as I get the attached screen for like 10 seconds or something it will just hold at the all white amazon logo if i'm screwing around with the keyboard combantions , i'm just stuck at this point and dont wanna keep burning hours if i cant go further.
I'm assuming its trying to load whatever is in the /cache folder which is either nothing or ave an update.zip file no idea
thanks for the reply as i will try some more to adb in
I am in a similar boat. I tried to install "rom.zip" per the instructions here http://www.aftvnews.com/how-to-install-a-custom-rom-image-on-the-amazon-fire-tv/
but it would not install it from CWM. It would abort the installation instantly. I read another thread where someone wasn't able to do something through ADB Shell because of SU permissions. I tried to uninstalled it and sideloaded SuperSU again. When I accessed it instead of clicking on "Normal" I chose the other option. Well, it's not stuck in the same loop as mentioned here.
I see the Amazon logo briefly, then it shows the android logo and reboots. It disconnects for a few seconds with the TV saying there is no HDMI connection and then shows the amazon logo shortly after again. I can no longer ADB into it.
Please help.
Note3usr said:
I send the update.zip to the ftv with Amazon FireTV Utility App and it looked like it went all the way through , by default isnt that where it send it to ? /cache
Ive been trying to ping the ip , or shell to it but how much times could I have when it just keeps cycling. I dont think its possible to adb to it at this point as I get the attached screen for like 10 seconds or something it will just hold at the all white amazon logo if i'm screwing around with the keyboard combantions , i'm just stuck at this point and dont wanna keep burning hours if i cant go further.
I'm assuming its trying to load whatever is in the /cache folder which is either nothing or ave an update.zip file no idea
thanks for the reply as i will try some more to adb in
Click to expand...
Click to collapse
Hey your problem is really similar to mine and what I did was connect to adb in between the loops and erase all cache
try searching on your router or do a scan on your network and find the correct ip address for the firetv
also don't worry about not being able to SU just erase cache using "rm -f /cache/*.bin" and "rm -f /cache/*.zip"
then it will ask for the actual file and just choose "not to install" then "disable recovery flash"
pd: Don't try to enter recovery by keyboard combinations it's useless trust me I tried A LOT
The bootloop started very randomly one day and my phone kept restarting and the battery became very hot.(I was asleep so I noticed this after I woke up). I had already switched to an iphone but I was using the moto g for music and stuff like that. I was able to boot once and then the storage suddenly got full and the bootloop started again. So, I just removed the battery and left it. I have a whatsapp backup on it that has some very important data which I need at the moment. The phone is stock without root or cwm. Usb debugging was on, I don't know if that helps though. I really need to recover just that one backup file. I went through quite a few threads and didn't find anything that could help me. Is there any way to recover it. I don't mind if the process is tedious.
Z91 said:
The bootloop started very randomly one day and my phone kept restarting and the battery became very hot.(I was asleep so I noticed this after I woke up). I had already switched to an iphone but I was using the moto g for music and stuff like that. I was able to boot once and then the storage suddenly got full and the bootloop started again. So, I just removed the battery and left it. I have a whatsapp backup on it that has some very important data which I need at the moment. The phone is stock without root or cwm. Usb debugging was on, I don't know if that helps though. I really need to recover just that one backup file. I went through quite a few threads and didn't find anything that could help me. Is there any way to recover it. I don't mind if the process is tedious.
Click to expand...
Click to collapse
I guess you can pull files from your phone via ADB commands. Can you get into recovery mode?
sharjeel.019 said:
I guess you can pull files from your phone via ADB commands. Can you get into recovery mode?
Click to expand...
Click to collapse
I can get into recovery but adb only works in sideload so I can't do stuff like adb pull, etc.
If your bootloader is unlocked you can flash twrp and then pull files via adb or by mtp (drag and drop files to pc)
If your bootloader is locked there's nothing you can do
Note adb doesn't work in stock recovery
TheFixItMan said:
If your bootloader is unlocked you can flash twrp and then pull files via adb or by mtp (drag and drop files to pc)
If your bootloader is locked there's nothing you can do
Note adb doesn't work in stock recovery
Click to expand...
Click to collapse
I haven't unlocked the bootloader so I'm assuming it's locked. Is there no way around it?
Z91 said:
I haven't unlocked the bootloader so I'm assuming it's locked. Is there no way around it?
Click to expand...
Click to collapse
No - unlocking the bootloader requires a data wipe
Technically if adb debugging is enabled your phone might boot enough for adb to become available but it might only be for a few seconds before it restarts
You'll keep having to type
adb devices
And see if you get a device listed but the chances of it being available long enough for you to pull anything is pretty much zero
TheFixItMan said:
No - unlocking the bootloader requires a data wipe
Technically if adb debugging is enabled your phone might boot enough for adb to become available but it might only be for a few seconds before it restarts
You'll keep having to type
adb devices
And see if you get a device listed but the chances of it being available long enough for you to pull anything is pretty much zero
Click to expand...
Click to collapse
Ohh, I don't remember exactly where but while researching I had read that it's possible to stop the phone at that boot stage. Is something like that doable?
Z91 said:
Ohh, I don't remember exactly where but while researching I had read that it's possible to stop the phone at that boot stage. Is something like that doable?
Click to expand...
Click to collapse
Found this it may help
Create a script and run it when adb is available on the device - usually sometime after boot logo
Windows version batch script eg run.bat
Code:
@ECHO off
cd /d %~dp0
echo.
echo Waiting for device…
adb wait-for-device
echo.
adb -d shell stop
adb pull (put directory location here)
Linux Version script eg run.sh
Code:
#!/system/bin/sh
echo " "
echo "Wating for device..."
./adb wait-for-device
echo " "
./adb -d shell stop
./adb pull (location of directory here)
TheFixItMan said:
Found this it may help
Create a script and run it when adb is available on the device - usually sometime after boot logo
Windows version batch script eg run.bat
Code:
@ECHO off
cd /d %~dp0
echo.
echo Waiting for device…
adb wait-for-device
echo.
adb -d shell stop
adb pull (put directory location here)
Linux Version script eg run.sh
Code:
#!/system/bin/sh
echo " "
echo "Wating for device..."
./adb wait-for-device
echo " "
./adb -d shell stop
./adb pull (location of directory here)
Click to expand...
Click to collapse
So, I tried this. Bu I realized soon that adb devices was recognizing the device during the boot. SO, the scrip couldn't work I guess. Do I have to do something so that the phone gets recognized during boot.
Z91 said:
So, I tried this. Bu I realized soon that adb devices was recognizing the device during the boot. SO, the scrip couldn't work I guess. Do I have to do something so that the phone gets recognized during boot.
Click to expand...
Click to collapse
If your phone doesn't reach the stage where adb is enabled there's nothing you can do