[Q] Stock Kindle Fire Stuck in Boot Loop (No Space on Device - Kindle Fire Q&A, Help & Troubleshooting

I have a Kindle Fire that is stock and was NEVER rooted. It was being used and the user said it told them that the space was getting full. He began to remove apps in order to free up space (he's a novice user) and as he was doing this it rebooted and is now stuck in a boot loop. It will flash the kindle fire logo for a few seconds, screen goes black, etc.
I was able to get it connected and accept adb commands. I first was able to reboot it (./adb reboot) and then see it listed as a device (./adb devices). However, it still wouldn't boot up all the way. I've rooted a number of devices before and work with computers for a living so I'm pretty familiar with what's going on, however I know that every device is different. I looked into the different things to do with a Kindle Fire and decided I should try to push the fbmode app to the kindle. When I tried that I got an error saying:
failed to copy 'fbmode' to '/data/local/temp': No space left on device​
Any idea what I should do? I don't really want to root the device if I can just get it to run first. What is the best way to free up some storage so that it might boot again?
UPDATE: I've sent the wipe_data and wipe_cache commands to the KF. The screen kinda turns yellow for a second and then reboots and goes back into a boot loop. I can't seem to find another way to clean up space. Help?

Same here
I'm having the same problem. Did you ever find a solutions?

dawn12123 said:
I'm having the same problem. Did you ever find a solutions?
Click to expand...
Click to collapse
No. I'm still searching or hoping someone else might have an answer.

carlowahlstedt said:
No. I'm still searching or hoping someone else might have an answer.
Click to expand...
Click to collapse
I started a new thread about it. Here is the link:http://forum.xda-developers.com/showthread.php?p=40509965#post40509965

arestspubs
Thanks! Looks like you might be getting somewhere. I'll be anxious to see what you figure out.

Connect it to computer and navigate to Android/data/com.amazon.venezia/cache and delete the entire folder.
This took about 3.51 GB of the Kindle's 4.99 GB of Space!When clearing up after receiving a low storage notification, i saw that the Android folder had over 3 GB so i decided to see if i could clean anything over there.Once I saw that this had 3.51 GB in a cache folder,I googled com.amazon.venezia to see if i could delete it and this post was the first link.:good:Thanks this really helped me a lot and i have no idea why amazon follows this method

Related

No space left on device

Afternoon all,
Last night I left my Desire charging as normal, having recently installed the Remote Media App. I suspect it used up all my storage with some sort of indexing process, as I returned to the phone this morning to find it perpetually showing the glinting HTC logo.
A reboot failed to clear it, and booting into recovery mode reveals"E:Error in DATA:data/recovery/log, (No space left on device)"
I've tried connecting to it with adb, but I get the following error
- exec '/system/bin/sh' failed: No such file or directory (2) -
Is there any way out of this bind? I had/have ClockWorkMod recovery installed in order to use ROM Manager, but I'm not terribly clued up on what else is out there on offer.
Any advice would be greatly appreciated.
Kyle
Try rebooting the phone into recovery mode and wipe/factory reset and see if this fixes it?
(Although you will loose all your apps/settings/scenes, though)
This should resolve the problem though.
hehe, there is always that option. I was hoping not to lose texts, settings, etc though this time round. Sadly my backup is more than a few days old.
I was mistaken in thinking I had ClockWorkMods recovery image installed, it appears to have gone back to the default image. I've just discovered a modified recovery ROM from JesusFreke here http://forum.xda-developers.com/showthread.php?t=443041 which may be of use.
Having to wipe and start from scratch again is a disgustingly appaling out of space failure mode. >:-/
bin the phone and use a pineapple
That recovery image is for G1! Don't even think about flashing it.
Even if you have stock recovery, you should still be able to clear storage from HBOOT.
Regards,
Dave
One other thing that might be worth trying is booting the device in safe mode.
Whilst the phone is power down, hold down the menu button and then power on - keep menu held down until the phone is fully booted.
I doubt that it will help in this situation, since clearly /data is completely full, but there's always a slim chance it work.
Regards,
Dave
munkehman said:
bin the phone and use a pineapple
Click to expand...
Click to collapse
Thanks for the advice m, I'll be sure to kick you in the nads next time you cross the border
Sadly Safe Mode fails too. The HTC logo appears and glints for a while, and then briefly vanishes just to reappear again. My thumb got sore after 5 minutes of holding the button down
I realised that was a G1 ROM shortly after reading more about it! I see there may be a more suitable recovery ROM at http://forum.xda-developers.com/showthread.php?t=709146 that I can flash. Failing that, then I'll clear storage and consign myself to failure
Wahey! It's sorted! Well, it was sorted a couple of hours ago, but a meeting got in the way
Wrote up some of the details here - http://lodge.glasgownet.com/2010/08/31/recovering-a-htc-desire/ if anyone is interested!
kylegordon said:
Wrote up some of the details here - http://lodge.glasgownet.com/2010/08/31/recovering-a-htc-desire/ if anyone is interested!
Click to expand...
Click to collapse
Sorry to dig up an OLD OLD thread, but your "guide" helped me out last night.
In addition to looking for "big" items in the data partition, I also moved some of the Google updates (5meg Maps.apk anyone ?) from /data/app to /system/app ... renaming to overwrite the original version from my Rom.
Thanks Again.

huawei mytouch root

I've been working on this for the past week. Every exploit I've tried just hangs after a while. I've gotten much further manually. I've got unbuntu and been working using various manual methods. The thing I've noticed is that there is no system folder in root. There is a system partition in which app and bin folders exist. Later today I'm going to have time to try some more. If it weren't for these silly rules id reply to somebody elses post, but I guess reading in forums for 3 years as a registered user doesn't count. Never a need to post as I've always found something using a search. And now I've got a phones that's been out for a week and there's no info out on it so I guess I get to develop myself. Not a hard thing...just time consuming and I've got better things to do, but these pink apps gotta go and I need wired or wireless tehter again. Hopefully I have succcess later today and can post how I accomplished it.
I'll be waiting anxiously. please post updates in this thread with your progress!
Any progress on this? I have been attempting but no luck.
update on progress
jb0ne said:
I'll be waiting anxiously. please post updates in this thread with your progress!
Click to expand...
Click to collapse
ok so here's what i've learned so far from trying every method that i can find...
when you boot the phone into the pink screen (volume up and volume down plus power) there is a partition containing 1 folder with 5 files. That folder is called image and the file inside are amss.mbn, boot.img, cust.img, emmcboot.mbn, and recovery.img
The Ascend G300 is a similar phone to the G312 and there is a filed called superrecovery which changes the recovery to set ADB with root priveliges and installs SU in system. If we use the recovery from that batch file made by PauloBrien and push it to the device while in pink screen mode and then reboot into recovery the phone won't power on. You can return to the pink screen and change back to the original recovery, but you can not boot the device into recovery nor regularly. Now this gave me an idea as i'm typing. what if i change it and issue the command in ADB as ADB works during the pink screen. I'm going to try that now.
But this can't be done when in bootloader, only in pinkscreen which makes me think it's fastboot USB mode, but fastboot commands dont work uless you are in the bootloader with the huawei logo which you can only get into by issuing the reboot-bootloader command through adb. once you enter bootloader mode via ADB reboot command then you are able to issue some fastboot commands.
ok so that didn't work...basically when the files in the imge folder are changed the device won't boot into anything but the pink screen mode.
the original recovery file size is 6340KB and the one from PauloBrien is smaller at 5074KB. I'm wondering if file size has something to do with why it won't boot, however, i'm not familiar with what's inside of these files. So...as i reasearch how to build our own clockworkmod recovery i'm wondering if there's a way to change the ADB command inside from not root to root. if it's a on off selecton i'm not sure how i'd affect file size. this is where we get into the realm of knowledge that i don't possess.
so if anybody can offer up some knowledge from where i stand now... please do so.
on a side note, when running exploits, (gingerbreak, zergrush, doomsomething, psneuter, etc)...they all hang.
in linux when trying to drop a file into /system/bin the terminal read out says something about failing to cycle power, not certain what this means.
as i learn a bit more, i'll go ahead and add more...
I am hopeful to hear back from you with a successful root method for this device. I myself just purchased this phone for myself and would really love to see more development on it. Seems like a solid phone with a low entry price. Look forward to seeing what you come up with.
I'm also waiting anxiously for someone to figure this out. I just got this phone and while I really like it, there is just so much packed on this thing that I want to get rid of before I can really enjoy the phone.
I'll be watching this thread as well hopefully OP or someone else will figure out the trick to rooting this phone, like others I have used the usual methods but no luck. I've counted no less than 13 programs I'd uninstall right off the bat.
For what its worth the phone seems to not be considered part of the Ascend models of phones although they are quite similar our model is called the Unite U8680 and the Unite Q U8730 (the slider version). I've sent a email to Huawei lets see if they respond at all.
It's pretty much useless but this is all I can find on the G312 on the Huawei website:
http://www.huaweidevice.com/worldwide/technicaIndex.do?method=gotoProductSupport&productId=4086&tb=0
I'll be watching this thread as well. According to a post on another forum regarding a different Huawei model, dialling *#*# 2846579 #*#* and making some changes in the log file settings suddenly made their phones rootable for some reason. However while the same # gets you into the service mode on this phone, the log file changes made no difference.
I wonder, though, there are quite a few other options in that service mode. Maybe something in there that could be useful.
Edit: There's one menu that looks interesting, the USB one. You can change it to all sorts of modes including "Manufacture mode" whatever that is. Afraid to try it, don't want to brick my wife''s new phone
I've been playing with this menu as well and some of the USB modes do seem interesting. I was hoping this would let me find the product ID for the phone cause I found a link on the Huawei homepage to register to get an unlock code for the boot loader on this phone. If anyone is interested here is a link to the page and sadly the method they say to find the product ID doesn't work on our phone.
http://www.huaweidevice.com/worldwide/servicePolicy.do?method=toApplyUnlock
huawei says the product ID is an 8 digit number. I've been trying to dump the log files so i can scan them for some kind of 8 digit number. i've also tried all the different USB modes as well as a few other changes in the project menu that we're able to access. These haven't given me any success in changing the ownership of the folders needed to gain root access. i've not had any time to tear apart the recovery image to figure out what it's doing. but all in due time somebody will figure this out. still haven't been able to get fastboot to work properly either. am running through the usb modes on that now.
Yes please help i cannot figure out out either
builder.clockworkmod.com
so i've been working on building a recovery image for this devices using koush's site and have been able to build it, but the device won't boot into recovery yet. not sure how to fix this, gonna mess around and keep on trying. i can get it to boot back up and can get it to respond to adb commands when in the mode that just shows the android 4g logo. but i can't get into recovery. not through adb and not through using the power and volume buttons.
still working on it... any body else have anything yet?
No info on rooting this phone but Huawei just posted on their website the open source gingerbread kernel for the G312 U8680 here is a link to it:
http://www.huaweidevice.com/worldwi...=toDownloadFile&flay=software&softid=NDY3MzU=
It's been rooted!
Yep, it's a simple one too. Happy to have my wife's phone rooted Removing bloat, however, is tricky -- it's hidden in an inaccessible partition and when you erase it, it restores it on next reboot.
http://forum.xda-developers.com/showthread.php?p=31237225#post31237225
http://www.droidrzr.com/index.php/topic/4276-how-to-root-huawei-mytouch-4g/
Big thanks to mattlgroff for cracking this nut!
jb0ne said:
Yep, it's a simple one too. Happy to have my wife's phone rooted Removing bloat, however, is tricky -- it's hidden in an inaccessible partition and when you erase it, it restores it on next reboot.
http://forum.xda-developers.com/showthread.php?p=31237225#post31237225
http://www.droidrzr.com/index.php/topic/4276-how-to-root-huawei-mytouch-4g/
Big thanks to mattlgroff for cracking this nut!
Click to expand...
Click to collapse
When you install an update to one of these apps lets use the, yahoo mail on for example, it will show in the /system/app or /data/app. The problem is the apk before the update is in /cust/t-mobile/us/app which is read only and unable to be mounted as R/W and that is why Titanium backup is unable to uninstall it.
I have tried moving it and deleting it manually with no luck. I have not tried through ADB yet but may give that a try next.
jamonthis said:
When you install an update to one of these apps lets use the, yahoo mail on for example, it will show in the /system/app or /data/app. The problem is the apk before the update is in /cust/t-mobile/us/app which is read only and unable to be mounted as R/W and that is why Titanium backup is unable to uninstall it.
I have tried moving it and deleting it manually with no luck. I have not tried through ADB yet but may give that a try next.
Click to expand...
Click to collapse
If you figure it out and find anything out I would love to know about it. Where should I watch for an update in case someone does get that sorted out?
Recovery mode
There is an accessible recovery mode, at least on my querty version of the phone. You have to completely pull the battery first. Put the battery back in, hold Volume up, and then hit power. I held the power button for a couple seconds, and volume up for maybe 6-8 seconds, then started hitting volume up repeatedly. The key is to pull the battery each time you try, I think. It looks like powering off from the phone's power menu just puts it in a suspend sort of mode. (Compare boot times when rebooting, and when pulling battery)
Apparently the bootloader is locked, so not sure how useful it is yet.
For anyone with a T-Mobile MyTouch Q (Huawei U8730), I created a wiki page for it, and we should post in the New Device Forum Requests thread so we have a specific place to post info.
I just purchased a U8730 today and will definitely be figuring out how to root it at some point.
For anyone that cares here's a link in case you haven't registered at the other site.
http://j.gs/1U5q
I'm hoping we can get some development going for this phone. I just picked one up for my daughter a month ago and it's giving her memory filled messages already. It'd be great if we can get it permanently rooted and remove bloat to start... then possibly move onto Cyanogen... considering she had the horrible Comet (also by Huawei) previously and it had development for CM7. I may be taking a leap from my contract soon, but can't go to Straight Talk with her phone unless it's unlocked

Recover / Hard Reset

Anyone have the steps to take to preform a hard reset of fix a non booting device?
I am stuck on the amazon Fire TV part where the boot animation is doing nothing. Can't get past this screen and have been stuck for the last 10 minutes.
jamesrascal said:
Anyone have the steps to take to preform a hard reset of fix a non booting device?
I am stuck on the amazon Fire TV part where the boot animation is doing nothing. Can't get past this screen and have been stuck for the last 10 minutes.
Click to expand...
Click to collapse
End Result. If you brick you box Amazon has no troubleshooting steps outside of rebooting the box. Once you get past that step and your still having an issue Amazon will issue you a replacement FireTV.
You will need to call Amazon as the Live chat is useless: 866-216-1072 Press 0 and ask to be transferred to the Fire TV department.
jamesrascal said:
Anyone have the steps to take to preform a hard reset of fix a non booting device?
I am stuck on the amazon Fire TV part where the boot animation is doing nothing. Can't get past this screen and have been stuck for the last 10 minutes.
Click to expand...
Click to collapse
Oh, boy. That is unfortunate. What did you do that lead to bricking your box?
I am in the same situation with one of my FireTV box. What caused it was one of the SQLite editor I used to explore the settings database: it changed the permissions on the files. I only realized the problem once I rebooted it
On the other box, I used the SQLite3 command line client from TitaniumBackup instead, and directly did my edit as root. No problem there.
Unfortunately, I am not in US; so if there is a way to do a hard reset, I would be glad to know.
if you bought yours at a local best buy and are a select customer, you may have an extended return policy.
You must have edited something you shouldn't have with the sqlite editor. I edited mine to allow package installs and did a factory reset and its all good. Did you only disable the updates through pm disable com.amazon.dcp or did you also edit the /etc/hosts? Lets get this figured out so others don't end up the same way.
Stupid question, did you pick TWRP as a method of recovery during the rooting process? I did that on my note 10.1 and boy did it mess up that tablet when I tried to recover it. Luckily I had Odin at the time.
Sent from my SM-N900V using Tapatalk
arman68 said:
I am in the same situation with one of my FireTV box. What caused it was one of the SQLite editor I used to explore the settings database: it changed the permissions on the files. I only realized the problem once I rebooted it
On the other box, I used the SQLite3 command line client from TitaniumBackup instead, and directly did my edit as root. No problem there.
Unfortunately, I am not in US; so if there is a way to do a hard reset, I would be glad to know.
Click to expand...
Click to collapse
Do you recall which sqlite editor app you used that caused the problem?
Be interesting to know if there's a stock recovery, and if there is, if it's looking for an update.zip file on a thumb drive in the USB slot. We can tell that USB slot is getting polled at start time by the way that certain connections to it will hang the device.
If it were me, I'd try is to obtain a 1 gig or so USB drive, format it fat32 and copy the OTA update to it.
- Leave it zipped.
- Name it update.zip
- pull the plug on the FTV
- put the USB stick in
- power it on and leave it for a bit. Watch it - is the power LED going out? If so, it may doing a recovery install of the signed OTA and rebooting - many Android devices will install anything on the sdcard called Update.zip if it's there at boot time.
The idea is that if there's a stock recovery it may be able to see that USB storage and read the OTA file as a recovery source.
roustabout said:
Be interesting to know if there's a stock recovery, and if there is, if it's looking for an update.zip file on a thumb drive in the USB slot. We can tell that USB slot is getting polled at start time by the way that certain connections to it will hang the device.
If it were me, I'd try is to obtain a 1 gig or so USB drive, format it fat32 and copy the OTA update to it.
- Leave it zipped.
- Name it update.zip
- pull the plug on the FTV
- put the USB stick in
- power it on and leave it for a bit. Watch it - is the power LED going out? If so, it may doing a recovery install of the signed OTA and rebooting - many Android devices will install anything on the sdcard called Update.zip if it's there at boot time.
The idea is that if there's a stock recovery it may be able to see that USB storage and read the OTA file as a recovery source.
Click to expand...
Click to collapse
There might be something to this idea. There was a review posted on Amazon and the reviewer had a Best Buy box that wouldn't go past the Amazon screen. They said Amazon told them how to use the USB to get it to work. A couple people asked for more info but they never responded. I have tried going back through the reviews to see if they ever did, but there are almost 6000 reviews.
kairnage said:
There might be something to this idea. There was a review posted on Amazon and the reviewer had a Best Buy box that wouldn't go past the Amazon screen. They said Amazon told them how to use the USB to get it to work. A couple people asked for more info but they never responded. I have tried going back through the reviews to see if they ever did, but there are almost 6000 reviews.
Click to expand...
Click to collapse
i have only sideloaded a few apps , no root or root attempt was made before issues.
i have a similar boot issue ( stops at amazon first screen and led flashes white) . i believe my remote is fried , batteries heated up while pressing the home button to pair remote , i removed battery and found the plastic wrap on one starting to burn . i believe remote is toast .
can anyone verify that the boot will stop until remote is paired ?
ps : amazon phone help mentioned reset on remote was hold right arrow key ( ie right circle ) and home button for 10 secs , to reset just the remote ,. nothing helped mine , i say its dead. another is on the way ,. he also said the lack of pairing with remote should not have stopped the ftv boot , it should have gone past first amazon screen . other than restarting the ftv by disconnecting power he offered no other reset method .
bkdg100 said:
i have a similar boot issue ( stops at amazon first screen and led flashes white) . i believe my remote is fried , batteries heated up while pressing the home button to pair remote , i removed battery and found the plastic wrap on one starting to burn . i believe remote is toast .
can anyone verify that the boot will stop until remote is paired ?
Click to expand...
Click to collapse
Removed batteries from remote and rebooted FTV, boots like normal, could not find a way to delete a paired remote otherwise I would have tried that too,
userr12 said:
Removed batteries from remote and rebooted FTV, boots like normal, could not find a way to delete a paired remote otherwise I would have tried that too,
Click to expand...
Click to collapse
thanks ,. i called amazon they confirmed normal boot even without pairing ,. also said how to reset "just the remote" ,. right tab and home for 10secs.
kairnage said:
There might be something to this idea. There was a review posted on Amazon and the reviewer had a Best Buy box that wouldn't go past the Amazon screen. They said Amazon told them how to use the USB to get it to work. A couple people asked for more info but they never responded. I have tried going back through the reviews to see if they ever did, but there are almost 6000 reviews.
Click to expand...
Click to collapse
I'm trying to find that review now. so far nothing
fireTVnews.com said:
Do you recall which sqlite editor app you used that caused the problem?
Click to expand...
Click to collapse
I have reviewed the logs of what I did, and it was my fault:
I used a non-root SQLite editor, which means I had to give -rw-rw-rw- access to the database folder and content, which I did.
With the SQLite editor, all I did was to explore the database structure.
Once done, I restored the original permissions, fist -rw------- (chmod 660) on the database folder and database file itself.
Finally I restored read-only -r-------- (chmod 600) to the extra files (settings-*), and that was my mistake: I did not notice my chmod line had 2 entries, with the first one being the database folder (wrong)
If only I would have root write access to the file system with adb, I could easily fix it, with a simple chmod 660 on the database folder.
In hindsight, I was very careless to do that directly on the FireTV; I should have taken a copy of settings.db, and explore it on the PC.
Luxferro said:
I'm trying to find that review now. so far nothing
Click to expand...
Click to collapse
Yeah I took a look again today. Their search doesn't really drill down very well.
Luxferro said:
I'm trying to find that review now. so far nothing
Click to expand...
Click to collapse
kairnage said:
Yeah I took a look again today. Their search doesn't really drill down very well.
Click to expand...
Click to collapse
Here are all the reviews with the word "USB" in them on one page:
http://firetvnews.com/review_usb.html
I skimmed through it but couldn't find the elusive review.
@Firetv: please review post #15 in this thread, and consider adjusting the post on your website accordingly - when I saw your site, it was stating that adjusting values in the settings databases risked changing the permissions on those databases.
That does not appear to be the case, but rather reflected confusion on the part of the person who was doing the settings changes and permissions changes from the shell at the same time.
I haven't seen a db editor that changes the permissions of the dbs themselves....'
Back to softbricked devices: I see that Amazon sells a thing called a "fastboot cable" which in theory forces the Kindle Fires to reboot into fastboot mode if attached to a computer. I'd be interested in what one of these did in conjunction with an A to A converter, since I haven't seen fastboot mode available yet (that I know of)
roustabout said:
@Firetv: please review post #15 in this thread, and consider adjusting the post on your website accordingly - when I saw your site, it was stating that adjusting values in the settings databases risked changing the permissions on those databases.
That does not appear to be the case, but rather reflected confusion on the part of the person who was doing the settings changes and permissions changes from the shell at the same time.
I haven't seen a db editor that changes the permissions of the dbs themselves....'
Back to softbricked devices: I see that Amazon sells a thing called a "fastboot cable" which in theory forces the Kindle Fires to reboot into fastboot mode if attached to a computer. I'd be interested in what one of these did in conjunction with an A to A converter, since I haven't seen fastboot mode available yet (that I know of)
Click to expand...
Click to collapse
I've definitely been tempted to remove the warning about SQLite databases after reading arman68's update. I haven't, however, because I've been individually contact by someone stating they used a free SQLite app from the Google Play store which caused them to lose their ethernet connection and soft-bricked after a restart.
I have gone ahead and updated the post to reduce the concern and stated that the SQLite Editor app everyone is using here seems to be safe.
Also, a fastboot connection can be achieved with any A to A USB cable. You simply need to boot the Fire TV while it's connected to a computer and it will boot into fastboot. I've done this myself with a Mac (have not tried a PC). The Fire TV displays a white Amazon logo on the screen and stays there until you reboot it without the cable plugged in. There doesn't seem to be much that can be done with the locked bootloader, but then again, I'm not the one to know as that is all new territory for me. Got any suggestions on things to try with fastboot?
fireTVnews.com said:
I've definitely been tempted to remove the warning about SQLite databases after reading arman68's update. I haven't, however, because I've been individually contact by someone stating they used a free SQLite app from the Google Play store which caused them to lose their ethernet connection and soft-bricked after a restart.
I have gone ahead and updated the post to reduce the concern and stated that the SQLite Editor app everyone is using here seems to be safe.
Also, a fastboot connection can be achieved with any A to A USB cable. You simply need to boot the Fire TV while it's connected to a computer and it will boot into fastboot. I've done this myself with a Mac (have not tried a PC). The Fire TV displays a white Amazon logo on the screen and stays there until you reboot it without the cable plugged in. There doesn't seem to be much that can be done with the locked bootloader, but then again, I'm not the one to know as that is all new territory for me. Got any suggestions on things to try with fastboot?
Click to expand...
Click to collapse
I didn't mean to say you can't hose your device by changing settings with an editor, just that I don't think any of them change permissions. so using them to look but not change is pretty safe, IMO, and I'd hate to see folks discouraged from doing so.
I'm surprised that there's not a better onboard recovery on this device, or at least not one anyone's figured out how to get moving. I'dthink it'd be cheaper for Amazon if the devices had a viable recovery, or if there was a solid reset to factory which actually did a full reinstall of the OS.
Interesting about the fastboot mode - when i connect the FTV to my laptop using an A to A cable I don't get a device recognized in fastboot, but it may be down to not having a driver for it.

[Q] Galaxy S3 stuck on samsung screen

I have been looking online for 3 days trying to get a definite answer on one thing. Is there anyway I can recover pictures off the phone.
The short is that the phone froze and would not respond. Pushing the power button for a while and then let off it rebooted but stuck on the Samsung screen. Most people respond to similar issues to do a factory reset which wipes your data.
I saw one other forum that discussed finding someone witha JTAG rig but I dont think i am going to have access to this and dont know anyone who does. They also mentioned ADB but i am not sure if i can use this or not. I do have drivers installed for my device on the PC and when I plug the phone in it recognized that a device has been plugged in and the drivers loaded but i did show that 'MTP USB Device' failed.
http://forums.androidcentral.com/sa...alaxy-s3-frozen-start-screen-help-please.html
When I started to crate this thread i saw about 5 similar threads. None of them answered my question. One that was linked from it confuses me though.
http://forum.xda-developers.com/galaxy-s3/help/flashing-rom-s3-change-setting-t1958368
So I have ADB and fastboot installed on my box. I want to give something a try but i am just not sure exactly what direction to start in to hopefully reach my goal of getting the phone up so i can grab the pics via USB. I saw where ADB could have uses such as 'pull' which could pull data off so hypothetically it could be possible to say pull the contents of the dir off but again not sure.
http://lifehacker.com/the-most-useful-things-you-can-do-with-adb-and-fastboot-1590337225
http://forum.xda-developers.com/showthread.php?t=2317790
So, even when I buy a GS3 or any other phone i usually have 1gig or so for the OS and then an internal storage for keeping data. So my thought, and I understand I could be wrong here, is that I SHOULD be able to flash the current factory image (like overwriting the existing) or along side the existing without touching the internal storage with the data (the 16/32gigs). I want to give something a try and not lose the pics. I would certainly appreciate some links to help me figure out what to do next. Thanks in advance.
Sprint SPH-L710 stock, un-rooted without 3rd party recover (TWRP, etc). I can boot into recovery and get a 'no command' message. Deleting cache has not helped. Leaving batt out for a while has not helped. I think its running 4.3.
Thanks in advance.
Hi,
You will definitely need to ask the experts who own your device for help on this, so I will have your thread moved to your device section.
Good luck!

Abdroid tv box T9 RK3318 2gb ram 16gb rom stuck on TV logo after unroot with superSU

Hi all!
Some days ago I urooted my TV android tv box with superSU and then I restarted it. From that moment when I plug the device it only reach the T9 logo (not the android one) and don't go further.
I've tried different ways to try to unstuck it, but nothing has worked.
I tried:
- enter recovery boot by holding the button in the av hole -> nothing happens
- install new firmware with adb sideload with both ubuntu and windows 10 -> always get errors (often error: closed, sometime other errors that at the moment don't remember)
- install new firmware with sd card using SDCard Installer -> the device doesn't boot when the sd is inserted
Moreover, with adb in ubuntu sometimes it recognises the device and I can enter the adb shell (but obtain errors when try any tipe of command), and sometimes don't (after adb devices I see list of attached devices: ??????????????? offline)
Now I'm thinking to try to install an ubuntu like on an usb pendrive...
I will be very grateful of any help/suggestion to how to revive my device :fingers-crossed:
Thank you!!!
Does this happen to be a pendoo model? I have a pendoo x10 MAX and i actually simply just installed supersu while it was rooted. Since then, I haven't gotten this thing to boot. Just stays on the boot screen the entire way. I wiped in recovery, knew that'd do nothing. I just wanted a root MANAGER. I tried Magisk, my favorite.. no go.. so then I went a bit old school.. so I tried ChainFire's SuperSU.. and THAT updated the SU binary! It said it succeeded.. it asked to do recovery install or normal install.. on phones, I've always done normal.. so I chose normal. Plus.. this thing has no custom recovery. I found it on Amazon. Overpriced, but great with the controller it had. It looks like I'll need a replacement and maybe a request to ask this guy if he could possibly NOT use something like KingRoot/KingoRoot/AmaraRoot or ANY One click root tool.. they just cause more bloatware, inciting boot issues and problems within the Android box itself. These One Click Root tools are out of control. It's to the point where I need to find a way in to adb and find the firmware for the latest version of this thing... X10Max from Pendoo.. I have not found a thing anywhere regarding firmware, and their website is ****. NOTHING *anywhere* on these things.. hell I'm about to return it as I bought it for $72. I have another one, same model.. wondering if the root method was different. About to boot that up and find out. I'll even swap the board. At this point.. he rooted it.. the WRONG way.. you can MOUNT THE /SYSTEM PARTITION IN RECOVERY. THIS IS ANDROID 9 we're talking about--the recovery supported by API v3.
This can and should have a TWRP custom recovery. If none exists, don't bother. As long as you can mount /system then you have a chance, at least, to root the damn thing.. which is why I'm still messing with it. I have another two weeks to return it. I'll give it another couple of days before I call it off and just switch out the good board for the bad one, return it, then return the other one and just use it until I find a way to use a custom recovery on this thing. There has to be.. unless there is no firmware available in sight (for an RK3318 or 3328, can't tell.. recovery mode says 3328, model name says RK3318. I see no difference at the moment aside from processor naming at this point--maybe speed?)
I'm still a nub with Android TV boxes so don't hold it against me for updating the damn root binary. If I could find a way to just reinstall the entire firmware and delete all previous stuff, I would. It would be worth it to learn. I would then mount /system in recovery and soldier on.
One little issue with this thing.. there's only one USB port that actually works. Same applies for the same exact product, a replication of the same thing.. was a "replacement" that still have/has the same qualities.
I've ranted enough. I vote more research into RK33xx processors and possible custom recoveries. I'm about to look for it based on only the device itself.
Note: Been stuck at boot screen ever since the binary was updated. I felt it was necessary to have a boot manager. I don't know where to even find the firmware. Can.. anyone point me in any direction? Something that MIGHT work on this thing? Android 6 or 7 would even suffice, return or no return, as "stuck on boot screen" will be my complaint. That's.. the actual complaint. I can't just *flash it* like the old days.. and maybe the original Android 9.0 firmware would suffice.. I don't know, but Pendoo.. wouldn't that be preferred?
You will need an SDcard to recover this box. I think the T9 32GB 4GB rom will do the job since its a cut down version.
Make a update SDcard and pop it in and power on the box. It will start the recovery on its own.
hello, sorry for my English I live in France I would have a question about the box: TV T9 RK3318, 4gb / 64gb. the problem is that the time is desynchronized on restart and creates problems to connect to applications when the time is out of order, I tried everything changed the time zone to deactivate and entered the time Manual it goes out of order all the time . is there a custom version or a version 10?
Very cook did I checked this out awhile back alot of good information that's for your contribution

Categories

Resources