Related
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
Nexus 7 (2013) multiple "Unfortunately..." after motherboard swap / image reflash
Hello all - I'm hoping someone can provide some assistance / suggestions...
A few months ago, my son's tablet went for a quick swim (dropped into the toilet ) Unfortunately, I wasn't at home (on a business trip) to immediately power it down and pull the battery. I'm not sure if it was turned off / back on / off again or what, but it was quickly put into a bag of rice to try and minimize the damage until I came home to review.
Inspection of the tablet confirmed it was dead - no response to either buttons or plugging in the charger. Found the ifixit how-to, and after obtaining some tools I popped the back case off to see what was what. Disassembly revealed an nice scorch mark on the underside of the motherboard, right where the main chip was, so it was pretty obvious what the failure was.
I decided that I'd give repairing it a go, and bought a replacement motherboard from ebay a couple of weeks ago. Swapping the board over was no problem, and I was happy to see that after letting it charge fully, it booted up and went into the 'Setup' routine.
However, this is where the problems started - as it was working through the setup (language / wifi / copy apps/data from other device etc) there were numerous "Unfortunately, xxx has stopped" messages. I kept 'ok'ing them, and the tablet made it to the point where it was starting to download the saved apps etc from the playstore before it rebooted.
When it powered back up, the 'Unfortunately" pop ups were worse than before, so after doing some searching I decided to try flash a factory image (razor-mob30x) , as per the link on the Nexus help forum. The flash seemed to work (no errors in fastboot mode, laptop was communicating with the tablet) but the pop ups were still as plentiful as before. I have tried the flash multiple times, even going back to lollipop, but with no real improvement. The last thing I tried tonight was to start the recommended flash process from step 1, re-downloading and installing all the required programs, but without success.
I'm not sure what else to try, as the factory image reflash should erase all the installed files.
My only thought is maybe trying to sideload the correct gapps / play services / etc in fastboot mode?
Any suggestions appreciated,
Roadie73
Update..
So, because I'm a glutton for punishment, I've been playing with the N7 again this evening...
Grabbed my old laptop, and went through the complete routine again - loading adb and fastboot onto the laptop, then the N7 factory image - and ended up with basically the same result - the tablet will look like the files have taken, but almost immediately after restarting and loading to the blue set up screen, the "Unfortunately..." messages start again.
I was able to get all the way through the set up, and have it copy and start to download the files off the tablet I was using previously, but the pop ups persisted, and it gets to a point where it is looking for a google play services update, and the process comes to a screeching halt.
I found another 'How To" and tried sideloading a rescue OTA update, which might be a little better, but the messages persist....
I'm almost wondering if it's worth reflashing the factory image back to whatever the N7 shipped with, and then trying updates from there, as it seems to be the play services / store / apps that is the issue.
The other strange thing is that when I sign in with my google account, it shows as a Nexus 7 2012, even though it's a 2013 - might the original software on the replacement motherboard have been corrupt?
Still trying...
Roadie73 said:
it shows as a Nexus 7 2012, even though it's a 2013 - might the original software on the replacement motherboard have been corrupt?
Click to expand...
Click to collapse
Interesting, please post the output of the 2 commands...
boot the Nexus in fastboot mode (when off press power+vol.dn)
connect it to your PC
on PC run:
fastboot getvar all
fastboot oem gpt-info
If you can, also attach logs...
download get-logs.zip to a FAT32 flash drive
connect the flash drive to your N7 with OTG adapter
download TWRP to your folder with fastboot and adb apps
boot the Nexus in fastboot mode (when off press power+vol.dn)
on PC run: fastboot boot twrp-3.1.0-0-flo.img
when TWRP is up, go: install/select-storage/usb-otg/get-logs.zip/flash
logs.tgz will be saved on the flash drive
attach logs.tgz here
It's simpler if you have TWRP already installed. You can also use get-logs.zip from internal storage.
Hi k23m,
I ran the two commands you suggested (getvar all and oem gpt-info) , and grabbed the outputs of both as screen captures and dumped them into a ppt file (which I can't seem to attach - there is no 'manage attachments' option I can see )
I installed TWRP on the N7, but was unsuccessful in creating / grabbing logs.tgz file - which might have to do with the USB connector on the N7 being flaky - if the otg cable wasn't held in exactly the right way it wouldn't recognize the flash drive.
If I can figure out how to add the attachment I will in a separate post, or I can always email it to you direct.
Thanks,
Roadie
Hello k23m,
Finally ad a couple of minutes to play with the N7 again - copied the get-logs file over to the tablet (that was behaving for once).
Unfortunately, despite copying the file off the N7 onto the laptop, a *.tgz file can't be attached. So I did the next best thing and copied the screen caps into an excel doc, which is one of the valid extension.
Please see the attached file - I had a look at the output, but it means nothing to me...
Thanks,
Roadie
added 'logs.tgz' file run previously - please rename from *.xls
Hopefully it might provide some insights into why the N7 is mis-behaving.
Thanks,
Roadie
The logs are OK.
Roadie73 said:
when I sign in with my google account, it shows as a Nexus 7 2012, even though it's a 2013
Click to expand...
Click to collapse
If you have followed the factory image installation instructions and you see the error messages before setup's initial sign in, then your hardware is faulty.
If it happens after sign in, then perhaps Google has corrupt account data ("it shows as a Nexus 7 2012"). Try a new account. Try a custom ROM with Gapps.
Ok, thanks.
Just tried a factory reflash as per the link, but fastbooted the individual files (boot / recovery / system / userdata / cache) separately as from what I have read using the 'flash-all' batch file has intermittent results.
Looked like the files loaded in successfully, but I'm still getting the "Unfortunately.." messages popping up on the initial sign in screen for set-up
So, based on k23m's assessment above, it sounds like it's a hardware problem
As far as I know the touch screen is ok (it's responsive in all areas, as far as I can tell). The daughterboard is not the original (that took a swim) - it was swapped out of another N7 when the charging port started to spread (and that tablet was issue free) So it looks as if the issue is in the replacement motherboard.
I guess I could try removing and reinstalling it, on the off chance it's a flaky connection somewhere.
I will also check to see if there was any sort of gaurentee / replacement policy for the replacement mobo, but it sounds like I'm out of luck
Any other suggestions / checks I can perform to see if I can narrow down where the issue lies?
Thank you,
Roadie
I may have a bricked phone on my hands, my fault I guess.
Although, I feel TWRP should share at least some of the blame.
I'm hoping someone can help to get me going again.
Last Xmas I got a refurbished Note 4 from Ebay and followed directions
here to root it. This all went well, I put TWRP 3.0.2 and Jasmine on it,
and it has worked just fine since then.
A couple days ago I realized I hadn't made a Nandroid backup of my phone
lately so I went into TWRP and did so. This went just fine and I stored
the backup on the external SD card.
A few hours later I bought a cheap home controller from Ebay. The controller
brand name is "Vera" and despite all of the negative comments on Google Play
I went ahead and installed the app. For the next day or two my phone began to
hang, stall, hesitate, whatever... and I remembered installing that app from
Google play so I went into the app manager and selected the uninstall option.
This caused the phone to hang indefinitely, I had to cycle the power button to
regain control. I then went back to Google Play and downloaded an uninstaller
program, told it to uninstall the vera app. It tried for a long time but
eventually gave up. "Uninstall failed" was all it would say.
So to stop this Vera app from hanging my phone I ran a freeze program ("Freeze"
is the actual name of the program) and had the vera app frozen. This worked, my
phone began to respond normally again. But I didn't like having this bad software
in my phone and that is when I remembered the recent TWRP backup.
I decided to do a complete restore with TWRP. TWRP did a restore of boot - (success),
recovery - (success), system - (success), data - "ERROR extractTarFork() process ended
with ERROR=255". Thanks TWRP, that really tells me a lot...
I repeated the restore effort a total of three times and same results. Google
wasn't much help, one suggestion was to unmount the data partition and try again.
Same results. Same error. Another suggestion was “stop and learn how to fix it”, well
sure, but I need a solution right now, I don’t have time right now for the learning part.
This is probably my first *big* mistake, I exited TWRP to see If I could boot
the OS and maybe fix it from there, (factory restore or something...). As you might
have guessed, it wouldn't boot the system with an incomplete data partition. I
suspected it too but I was desperate to try something. It would have been nice if TWRP
had warned me not to exit, instead of just saying "error 255..." because now it wont
boot back into recovery, just hangs. Odin mode appears to be working but I suspect it isn't.
It looks like it enters odin mode just fine, but odin can't see it.
So here is where it stands at the moment:
SYSTEM - Wont boot. Shows the Samsung logo, shows "custom", hangs at this point.
RECOVERY- Wont enter recovery mode. Small text in upper left says it is entering recovery
mode then it hangs.
ODIN/DOWNLOAD - Appears to enter this mode, usual screen appears, will not communicate
with Odin, will not communicate with adb.
One other note, the external sd card has a copy of the twrp log file written to it, as well
as the nandroid backup. But plugging the sd card into an adapter and then into a pc... It
says it can’t read it, and would I like to format it(?).
And of course there is valuable information on the phone.
I've run out of ideas, I'm asking anyone who is still reading this lengthy message(apologies)
for any other options, suggestions, any hope at all, instead of just throwing it in the trash.
Thanks for reading. I hope the dialog was understandable.
RT
UPDATE:
Progress. I have odin talking with the phone now, was able to re-flash TWRP and boot into it.
Still getting error 255. I am under the impression that this means I am out of space???
I pulled the recovery logs with adb, here is the relevant lines:
==> extracting: //data/app/radiotime.player-1/lib/arm/libtunein.uap.so (file size 5499572 bytes)
I:Unable to extract tar archive '/external_sd/TWRP/BACKUPS/657e54fc/2017-04-08--07-58-24_JasmineROM_v7.0-MMB29M.N910VVRU2CPF3/data.ext4.win001'
Error during restore process.
I:Error extracting '/external_sd/TWRP/BACKUPS/657e54fc/2017-04-08--07-58-24_JasmineROM_v7.0-MMB29M.N910VVRU2CPF3/data.ext4.win001' in thread ID 0
I:Error extracting split archive.
Error during restore process.
extractTarFork() process ended with ERROR: 255
I:Set page: 'action_complete'
Iperation_end - status=1
I still don't understand "error 255" well enough to proceed. Google is not a wealth of information when it comes to this subject. Any suggestions on how to proceed are greatly appreciated.
thanks!
RT
LAST UPDATE:
I want to thank everyone here for all the help. Or the lack there of.
Since I had Odin and TWRP both working, I reconstructed the phone from scratch.
Re-rooted and re-installed Jasmine. So I am back up and running now, I just need
to get all the apps re-installed and configured.
But I must say that I am really disappointed with the lack of support from this forum.
It used to be that people were falling all over each other to help others out.
But 3 days and 49 views and not one of you had anything to say.
I guess that's what happens to all forums sooner or later, the newbies here don't know what
to say and are just looking for answers to their own issues, and the regulars become jaded
over time and can't be bothered anymore.
I used to think this forum was awesome, but now its just another forum like all the rest.
I will look to other websites for any future learning.
To the Admin: (If you can be bothered for a moment)You can close this thread, I consider
the issue resolved, and you can close my account too, I won't be back.
Good luck to you guys.
RT
RootieTootie said:
I may have a bricked phone on my hands, my fault I guess.
Although, I feel TWRP should share at least some of the blame.
I'm hoping someone can help to get me going again.
Last Xmas I got a refurbished Note 4 from Ebay and followed directions
here to root it. This all went well, I put TWRP 3.0.2 and Jasmine on it,
and it has worked just fine since then.
A couple days ago I realized I hadn't made a Nandroid backup of my phone
lately so I went into TWRP and did so. This went just fine and I stored
the backup on the external SD card.
A few hours later I bought a cheap home controller from Ebay. The controller
brand name is "Vera" and despite all of the negative comments on Google Play
I went ahead and installed the app. For the next day or two my phone began to
hang, stall, hesitate, whatever... and I remembered installing that app from
Google play so I went into the app manager and selected the uninstall option.
This caused the phone to hang indefinitely, I had to cycle the power button to
regain control. I then went back to Google Play and downloaded an uninstaller
program, told it to uninstall the vera app. It tried for a long time but
eventually gave up. "Uninstall failed" was all it would say.
So to stop this Vera app from hanging my phone I ran a freeze program ("Freeze"
is the actual name of the program) and had the vera app frozen. This worked, my
phone began to respond normally again. But I didn't like having this bad software
in my phone and that is when I remembered the recent TWRP backup.
I decided to do a complete restore with TWRP. TWRP did a restore of boot - (success),
recovery - (success), system - (success), data - "ERROR extractTarFork() process ended
with ERROR=255". Thanks TWRP, that really tells me a lot...
I repeated the restore effort a total of three times and same results. Google
wasn't much help, one suggestion was to unmount the data partition and try again.
Same results. Same error. Another suggestion was “stop and learn how to fix it”, well
sure, but I need a solution right now, I don’t have time right now for the learning part.
This is probably my first *big* mistake, I exited TWRP to see If I could boot
the OS and maybe fix it from there, (factory restore or something...). As you might
have guessed, it wouldn't boot the system with an incomplete data partition. I
suspected it too but I was desperate to try something. It would have been nice if TWRP
had warned me not to exit, instead of just saying "error 255..." because now it wont
boot back into recovery, just hangs. Odin mode appears to be working but I suspect it isn't.
It looks like it enters odin mode just fine, but odin can't see it.
So here is where it stands at the moment:
SYSTEM - Wont boot. Shows the Samsung logo, shows "custom", hangs at this point.
RECOVERY- Wont enter recovery mode. Small text in upper left says it is entering recovery
mode then it hangs.
ODIN/DOWNLOAD - Appears to enter this mode, usual screen appears, will not communicate
with Odin, will not communicate with adb.
One other note, the external sd card has a copy of the twrp log file written to it, as well
as the nandroid backup. But plugging the sd card into an adapter and then into a pc... It
says it can’t read it, and would I like to format it(?).
And of course there is valuable information on the phone.
I've run out of ideas, I'm asking anyone who is still reading this lengthy message(apologies)
for any other options, suggestions, any hope at all, instead of just throwing it in the trash.
Thanks for reading. I hope the dialog was understandable.
RT
UPDATE:
Progress. I have odin talking with the phone now, was able to re-flash TWRP and boot into it.
Still getting error 255. I am under the impression that this means I am out of space???
I pulled the recovery logs with adb, here is the relevant lines:
==> extracting: //data/app/radiotime.player-1/lib/arm/libtunein.uap.so (file size 5499572 bytes)
I:Unable to extract tar archive '/external_sd/TWRP/BACKUPS/657e54fc/2017-04-08--07-58-24_JasmineROM_v7.0-MMB29M.N910VVRU2CPF3/data.ext4.win001'
Error during restore process.
I:Error extracting '/external_sd/TWRP/BACKUPS/657e54fc/2017-04-08--07-58-24_JasmineROM_v7.0-MMB29M.N910VVRU2CPF3/data.ext4.win001' in thread ID 0
I:Error extracting split archive.
Error during restore process.
extractTarFork() process ended with ERROR: 255
I:Set page: 'action_complete'
Iperation_end - status=1
I still don't understand "error 255" well enough to proceed. Google is not a wealth of information when it comes to this subject. Any suggestions on how to proceed are greatly appreciated.
thanks!
RT
LAST UPDATE:
I want to thank everyone here for all the help. Or the lack there of.
Since I had Odin and TWRP both working, I reconstructed the phone from scratch.
Re-rooted and re-installed Jasmine. So I am back up and running now, I just need
to get all the apps re-installed and configured.
But I must say that I am really disappointed with the lack of support from this forum.
It used to be that people were falling all over each other to help others out.
But 3 days and 49 views and not one of you had anything to say.
I guess that's what happens to all forums sooner or later, the newbies here don't know what
to say and are just looking for answers to their own issues, and the regulars become jaded
over time and can't be bothered anymore.
I used to think this forum was awesome, but now its just another forum like all the rest.
I will look to other websites for any future learning.
To the Admin: (If you can be bothered for a moment)You can close this thread, I consider
the issue resolved, and you can close my account too, I won't be back.
Good luck to you guys.
RT
Click to expand...
Click to collapse
sorry we missed your call gratz on the working phone . you know what they say "give a man a fish he ****s up his phone .....
This might sound stupid. Being fan of Mi device, I had bought Mi6 from a second hand market after loosing one in CAB.
The guy was using it and did factory reset in front of me. Since i did not had the option to test the device completely; took the device happily and installed China developer ROM and observed i'm not able to turn on Wi-Fi. Flashed all type of developer and Beta ROM. Including my failed efforts to flash persist.img file.
I have a partially working device with no option to turn on Wi-Fi. and not able to .
Any pointers, please help
sending 'persist' (4692 KB)...
OKAY [ 0.123s]
writing 'persist'...
FAILED (remote: partition write protected)
finished. total time 0.157s
iyengar said:
This might sound stupid. Being fan of Mi device, I had bought Mi6 from a second hand market after loosing one in CAB.
The guy was using it and did factory reset in front of me. Since i did not had the option to test the device completely; took the device happily and installed China developer ROM and observed i'm not able to turn on Wi-Fi. Flashed all type of developer and Beta ROM. Including my failed efforts to flash persist.img file.
I have a partially working device with no option to turn on Wi-Fi. and not able to .
Any pointers, please help
sending 'persist' (4692 KB)...
OKAY [ 0.123s]
writing 'persist'...
FAILED (remote: partition write protected)
finished. total time 0.157s
Click to expand...
Click to collapse
Sounds like your bootloader is still locked. Use mobile data to bind the accounts etc etc (idk if you'll need to find that guy again to remove his old account if it was on there and you can explain the problem) and then go through the unlock process.
Use the xiaomi fastboot flash tool and flash a full dev or stable ROM and boot it up. If it works you'll know right away if you can enable WiFi or not
Dobsgw said:
Sounds like your bootloader is still locked. Use mobile data to bind the accounts etc etc (idk if you'll need to find that guy again to remove his old account if it was on there and you can explain the problem) and then go through the unlock process.
Use the xiaomi fastboot flash tool and flash a full dev or stable ROM and boot it up. If it works you'll know right away if you can enable WiFi or not
Click to expand...
Click to collapse
Bootloader is very well unlocked. The seller factory reset was done in front of me. I'm able to log in via My MiAccount anyway and sync all items with mobile data and not WiFi. As stated earlier I have installed full rom via Mi PC Flash Tool quite a lot of time to see if it works this time.
Any pointers to help fix this issue please, I can't even use hotspot.. don't know what else is not working
if you can flash other roms, and they worked, then probably your wifi is broken. should open to check if the socket is loose
I have 2 firestick 4ks.
Both identical in that they are rooted and debloated with (the same) various system apps frozen...
Both been running fine for a month or so...
Where I live I get frequent power cuts.
Yesterday after a power cut... one reboots correctly the other just goes to a black screen.
I connected it to my PC and ADB into it, I reenabled all apps via adb and rebooted, it just went to the same black screen.
So I booted to TWRP and reflashed RBoxes prerooted image, still nothing...
I then installed a stock image (Skel40's).... Still nothing.
Up to this point I had only been wiping Cache & Dalvik and dirty flashing.
I figured that there was a corrupted file that was affecting full boot, so I made the mistake of wiping data and installing stock again...
When I rebooted I had lost ADB!
I could still see the firestick in windows, however it just comes up as "Fire" in device manager with no ADB..
I grabbed an OTG cable and booted to TWRP and tried a few more times... each time gave exactly the same black screen (no orange amazon logo).
Finally I tried wiping system as well in case something was corrupted and reflashed stock.... Still nothing!
So I don't really know where to go from here... (I'm going to backup the other firestick and restore that over this one then reflash stock and see where that gets me...)
Does anyone have any ideas! I can get into TWRP, but I'm not sure it's wiping or flashing things correctly...
Any help greatly appreciated... Thx
Have you done any of the ideas listed in the other thread? Let me know if i can help #lockdown
Michajin said:
Have you done any of the ideas listed in the other thread? Let me know if i can help #lockdown
Click to expand...
Click to collapse
Hi Michajin...
Thanks for taking the time to help
I'll fill you in as to what I have and haven't tried...
I have wiped all standard partitions ( cache, dalvik, data, system) and reflashed both rooted and stock images *.*.6.8 and *.*.7.1
I think I may have wiped the Vendor partition, I'm not sure.
Under backup in TWRP I can see the Vendor partition, however under Wipe I see an extra 2 partitions (both) called storage and having not made a backup (I know!... )
I did'nt realise that the storage partition(s) may have been the Vendor partition.
After wiping cache, dalvik, data, system partitions and then flashing stock and rooted images multiple times and still getting a black screen... I tried wiping the one storage then the other and then finally Internal.
A couple of points that I can tell you...
I can boot to TWRP
I can reboot to hacked Bootloader
When I connect the firestick to my windows PC It's senses it straight away for a bout 10 seconds then drops it... It then senses it again and stays connected to my PC.
Windows recognizes it under portable devices as simply "fire" and an empty explorer window pops up, if I right click on the firestick in windows explorer (it shows as drive) I can pull a properties page which shows its serial number...!
On both my firesticks I have modified my build.prop for a faster boot which doesn't show the splash screen.
Both sticks were modified identically about a month ago and once setup had nothing added to them. They just get used for Kodi and catch-up TV apps.
I root them so as to boot directly into Kodi and freeze the bloat.
Both sticks have been rebooted multiple times.. This one failed after a powercut...
I been reading in the main rooting thread and have come across something about sticks not booting properly due to dm_verity failing and having to flash magisk before (or after... I'm not sure) the image flash.
I'm still reading through the thread so haven't tried anything yet... When i get head round what it is, I'll try.
The other 2 ideas I thought to try was to
1) flash an image directly from the bootloader (if possible.. I need to find more info on this) and
2) taking a backup of the working stick and trying that (It's in use a lot... due to #TotalLockdown! we're at 4 weeks with heavy police curfew! So I haven't had access to it)
If have any ideas or thoughts... I would be very grateful. Also I'm happy to try anything...
tinybilbo said:
Hi Michajin...
Thanks for taking the time to help
I'll fill you in as to what I have and haven't tried...
I have wiped all standard partitions ( cache, dalvik, data, system) and reflashed both rooted and stock images *.*.6.8 and *.*.7.1
I think I may have wiped the Vendor partition, I'm not sure.
Under backup in TWRP I can see the Vendor partition, however under Wipe I see an extra 2 partitions (both) called storage and having not made a backup (I know!... )
I did'nt realise that the storage partition(s) may have been the Vendor partition.
After wiping cache, dalvik, data, system partitions and then flashing stock and rooted images multiple times and still getting a black screen... I tried wiping the one storage then the other and then finally Internal.
A couple of points that I can tell you...
I can boot to TWRP
I can reboot to hacked Bootloader
When I connect the firestick to my windows PC It's senses it straight away for a bout 10 seconds then drops it... It then senses it again and stays connected to my PC.
Windows recognizes it under portable devices as simply "fire" and an empty explorer window pops up, if I right click on the firestick in windows explorer (it shows as drive) I can pull a properties page which shows its serial number...!
On both my firesticks I have modified my build.prop for a faster boot which doesn't show the splash screen.
Both sticks were modified identically about a month ago and once setup had nothing added to them. They just get used for Kodi and catch-up TV apps.
I root them so as to boot directly into Kodi and freeze the bloat.
Both sticks have been rebooted multiple times.. This one failed after a powercut...
I been reading in the main rooting thread and have come across something about sticks not booting properly due to dm_verity failing and having to flash magisk before (or after... I'm not sure) the image flash.
I'm still reading through the thread so haven't tried anything yet... When i get head round what it is, I'll try.
The other 2 ideas I thought to try was to
1) flash an image directly from the bootloader (if possible.. I need to find more info on this) and
2) taking a backup of the working stick and trying that (It's in use a lot... due to #TotalLockdown! we're at 4 weeks with heavy police curfew! So I haven't had access to it)
If have any ideas or thoughts... I would be very grateful. Also I'm happy to try anything...
Click to expand...
Click to collapse
It's really strange. Usually these steps should fix the issue :
1) Factory Reset from TWRP
2)Wipe System from TWRP
3) Flash full stock (non rooted) firmware
Of course, you could try flashing each image with hacked fastboot, or just boot, system and vendor with TWRP, which also have an option (install image) for that.
But you will have to convert system and vendor from sparse (.dat) to . img before being able to flash them.
Wiping these should have taken care of you issue.
"After wiping cache, dalvik, data, system partitions and then flashing stock and rooted images multiple times and still getting a black screen... I tried wiping the one storage then the other and then finally Internal."
What stock did you flash from where?
When you flash stock are there any errors?
You should be able to take a backup from you other one also for other one (if you are doing a full backup/restore, i would wipe data and cache after restore)
Thanks guys for the replies, I couldn't respond earlier due to an 8 hr powercut today!
Pretoriano80 said:
It's really strange. Usually these steps should fix the issue :
1) Factory Reset from TWRP
2)Wipe System from TWRP
3) Flash full stock (non rooted) firmware
Of course, you could try flashing each image with hacked fastboot, or just boot, system and vendor with TWRP, which also have an option (install image) for that.
But you will have to convert system and vendor from sparse (.dat) to . img before being able to flash them.
Click to expand...
Click to collapse
Hi Pretoriano80
Yeah... It's really weird... I'm starting to think that the stick is damaged in some way, although the fact I can get in both the hacked bootloader and TWRP confuses me!
I've even wiped each partition 3 or 4 times (and rebooted back into recovery to remount) before writing the new image just to make sure.!
I'm ready to try anything at this point, since the stick is a brick at this point.
I'm not really sure how or what to flash from the bootloader, I'll read up a bit before I try especially your tips about converting from sparse to .img.
(I may have some further questions for you, if that's alright )
I will try to restore a backup from another stick first (if I can get access to that stick for long enough...)
Michajin said:
Wiping these should have taken care of you issue.
"After wiping cache, dalvik, data, system partitions and then flashing stock and rooted images multiple times and still getting a black screen... I tried wiping the one storage then the other and then finally Internal."
What stock did you flash from where?
When you flash stock are there any errors?
You should be able to take a backup from you other one also for other one (if you are doing a full backup/restore, i would wipe data and cache after restore)
Click to expand...
Click to collapse
Hi Michajin
Thanks again for taking the time to reply... much appreciated...
I have tried this stock image update-kindle-mantis-NS6271_user_2493_0003590962564
https://forum.xda-developers.com/fire-tv/general/official-stock-image-fire-tv-stick-4k-6-t4059777
as well as a update-kindle-mantis-NS6268_user_2315_0003255372676 image (stock that I think i got from the main rooting thread)
I've also used Rboxes pre-rooted image mantis-6.2.6.8-rooted_r1
which was the image that worked fine on both boxes...
I'm happy to try any other image that you might have a link for.....
When I wipe the partitions there are no errors, except for when I wiped the storage partitions - they did throw up an error - although at this point I had already tried flashing new images at least a dozen times,
All the images flash without error as well!
I'm stumped... I've never had any android device brick before... (soft bricks many times! but never a hard brick), and it's weird since I have access to both the bootloader and TWRP.
Tomorrow I'll be able to get a restore image from the other stick, Then I'll try flashing from bootloader..
The only other thing i thought to try was to crack the case open and redo the the whole root procedure from scratch...
Sorry to double-post...
However I wanted to add this as a separate post rather than an edit.
After playing with my firestick for a few days, during which I tried a working backup and erasing from the bootloader and then restoring multiple images (stock and prerooted), as well running the exploit again.
I realised that the OS was loading (I regained ADB after the full restore) despite not giving an image over HDMI (just a black screen).
I was about to give up when I happened to be going through the options in ADBLink and I found the screenshot button.
I gave it a try and to my surprise it sent back an image of the stick with a working OS/screen.
I even manged to navigate through the settings and do a full reset from within FireOS by taking screengrabs.
After the reset it still gave a black screen, I re-enabled ADB from TWRP and was able to verify that it had reset correctly...
From ADB I ran a logcat...
I'm not really familiar with logcat but a couple of things seemed to jump out...
Code:
1) 596 617 I DisplayManagerService: Display device changed: DisplayDeviceInfo{"Built-in Screen": uniqueId="local:0", 720 x 480, modeId 4, defaultModeId 1, supportedModes [{id=1, width=1920, height=1080, fps=60.000004}, {id=2, width=1920, height=1080, fps=59.94}, {id=3, width=720, height=576, fps=50.0}, {id=4, width=720, height=480, fps=60.000004}], colorMode 0, supportedColorModes [0], HdrCapabilities [email protected], density 320, 213.0 x 216.0 dpi, appVsyncOff 1000000, presDeadline 16666666, touch INTERNAL, rotation 0, type BUILT_IN, state ON, FLAG_DEFAULT_DISPLAY, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}
2) 1145 1145 I AmazonHdmiServiceManager: resolution applied and hdmi turned off
3) 596 2438 E AmazonHdmiService: Settings client binder died.
Seeing that there were some issues with the HDMI display (Display device change to built-In screen? and HDMI turned off?), I used the screengrab to navigate my way to display settings which wouldn't allow me to change resolution
So to sum it up...
Everything is loading and running correctly, however I can't get an image over HDMI only by getting screengrabs via ADBlink.
Maybe something on the chip (HDMI output) is damaged, I've had the stick for a while and it's had heavy usage, or something has stuck in a toggled state.
I don't know....
If anyone has any ideas how to test it I have full root access via TWRP and probably can get it over ADB, so any help or commands to try would greatly appreciated....
Thanks :good:
tinybilbo said:
Sorry to double-post...
However I wanted to add this as a separate post rather than an edit.
After playing with my firestick for a few days, during which I tried a working backup and erasing from the bootloader and then restoring multiple images (stock and prerooted), as well running the exploit again.
I realised that the OS was loading (I regained ADB after the full restore) despite not giving an image over HDMI (just a black screen).
I was about to give up when I happened to be going through the options in ADBLink and I found the screenshot button.
I gave it a try and to my surprise it sent back an image of the stick with a working OS/screen.
I even manged to navigate through the settings and do a full reset from within FireOS by taking screengrabs.
After the reset it still gave a black screen, I re-enabled ADB from TWRP and was able to verify that it had reset correctly...
From ADB I ran a logcat...
I'm not really familiar with logcat but a couple of things seemed to jump out...
Code:
1) 596 617 I DisplayManagerService: Display device changed: DisplayDeviceInfo{"Built-in Screen": uniqueId="local:0", 720 x 480, modeId 4, defaultModeId 1, supportedModes [{id=1, width=1920, height=1080, fps=60.000004}, {id=2, width=1920, height=1080, fps=59.94}, {id=3, width=720, height=576, fps=50.0}, {id=4, width=720, height=480, fps=60.000004}], colorMode 0, supportedColorModes [0], HdrCapabilities [email protected], density 320, 213.0 x 216.0 dpi, appVsyncOff 1000000, presDeadline 16666666, touch INTERNAL, rotation 0, type BUILT_IN, state ON, FLAG_DEFAULT_DISPLAY, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}
2) 1145 1145 I AmazonHdmiServiceManager: resolution applied and hdmi turned off
3) 596 2438 E AmazonHdmiService: Settings client binder died.
Seeing that there were some issues with the HDMI display (Display device change to built-In screen? and HDMI turned off?), I used the screengrab to navigate my way to display settings which wouldn't allow me to change resolution
So to sum it up...
Everything is loading and running correctly, however I can't get an image over HDMI only by getting screengrabs via ADBlink.
Maybe something on the chip (HDMI output) is damaged, I've had the stick for a while and it's had heavy usage, or something has stuck in a toggled state.
I don't know....
If anyone has any ideas how to test it I have full root access via TWRP and probably can get it over ADB, so any help or commands to try would greatly appreciated....
Thanks :good:
Click to expand...
Click to collapse
Just checking, but have you tried another HDMI cable and different TV? Somehow it is not recognizing the format in the OS. TWRP uses a lower format i believe. I have had a power surge before damaging HDMI here, but I wouldn't get anything with it plugged in.
Michajin said:
Just checking, but have you tried another HDMI cable and different TV? Somehow it is not recognizing the format in the OS. TWRP uses a lower format i believe. I have had a power surge before damaging HDMI here, but I wouldn't get anything with it plugged in.
Click to expand...
Click to collapse
Hi Michajin,
Thanks for your reply...
Yes I have tried multiple TV's, Monitors , and cables... Including the TV that it had been running on for almost a year...
I get frequent powercuts where I live, and often power surges when the power comes back on...
I do use surge protectors, however they don't always work....
One time the electricity board double one of the phases to 440v and knocked out £5k worth of equipment!
So between that and the humidity I think there is some minor damage to the stick... shame because it's still running.
I'm going to see if I can get a logcat from TWRP and see what it says about the HDMI output, not that it'll help...
tinybilbo said:
Hi Michajin,
Thanks for your reply...
Yes I have tried multiple TV's, Monitors , and cables... Including the TV that it had been running on for almost a year...
I get frequent powercuts where I live, and often power surges when the power comes back on...
I do use surge protectors, however they don't always work....
One time the electricity board double one of the phases to 440v and knocked out £5k worth of equipment!
So between that and the humidity I think there is some minor damage to the stick... shame because it's still running.
I'm going to see if I can get a logcat from TWRP and see what it says about the HDMI output, not that it'll help...
Click to expand...
Click to collapse
So you get a display in TWRP, but go black after booting? I wonder if you can force whatever display mode and setting as used in TWRP as your display mode in FireOS. Had you tried another wall outlet (higher mA) ? A long shot at this point that you havent tried it....
Michajin said:
So you get a display in TWRP, but go black after booting? I wonder if you can force whatever display mode and setting as used in TWRP as your display mode in FireOS. Had you tried another wall outlet (higher mA) ? A long shot at this point that you havent tried it....
Click to expand...
Click to collapse
Correct, I can get a display with TWRP, but it goes black when it boots into FireOS (from which I can get screengrab via adblink of the stick displaying FireOS or whatever app is running).
Up until now (for almost a year) I've just used the power adapter that came with the stick, but it's a good idea to try something more powerful (I have a 2.4a one that I'll try a little later).
Another thing I'm going to try is "adb shell wm size ***x***" "adb shell wm density ***" command to change the resolution & pixel density (I think).
I hadn't thought about power being an issue up until you mentioned it (because so far it hasn't been), but maybe a component has (or is) failed (or failing) so it might need more power...
I can't try until a little later this evening, but at least I have something to try now cheers! I'll let you know how I get on....
tinybilbo said:
Correct, I can get a display with TWRP, but it goes black when it boots into FireOS (from which I can get screengrab via adblink of the stick displaying FireOS or whatever app is running).
Up until now (for almost a year) I've just used the power adapter that came with the stick, but it's a good idea to try something more powerful (I have a 2.4a one that I'll try a little later).
Another thing I'm going to try is "adb shell wm size ***x***" "adb shell wm density ***" command to change the resolution & pixel density (I think).
I hadn't thought about power being an issue up until you mentioned it (because so far it hasn't been), but maybe a component has (or is) failed (or failing) so it might need more power...
I can't try until a little later this evening, but at least I have something to try now cheers! I'll let you know how I get on....
Click to expand...
Click to collapse
Hey I have a debloated clean stable rom that will be available soon. You can try that and you need to be sure to have either a usb otg or a hub for transferring this backup which will be titled ftvs4kdebloatedv1.0. Paste this folder to TWRP/BACKUPS/YOUR SERIAL #/ftvs4kdebloatedv1.0.
Skel40 said:
Hey I have a debloated clean stable rom that will be available soon. You can try that and you need to be sure to have either a usb otg or a hub for transferring this backup which will be titled ftvs4kdebloatedv1.0. Paste this folder to TWRP/BACKUPS/YOUR SERIAL #/ftvs4kdebloatedv1.0.
Click to expand...
Click to collapse
Thanks Skel40
I'll definitely give the clean rom a go
I have an OTG & Hub and the serial number already
hi guys
i have a firestick 2th gen model ly78pr its brick stock on logo , the problem is usb debbug was off and i tried with the key board and otg cable pressing alt + printscreen + i and it does not work as , i tried different combination and nothing help , also i connected to the pc and it does not work with adb it doesnt reconize , if anyone can help to find any solution