Related
I have a 80 G9 (16GB) . It came with 3.2.79, I updated to 3.2.80 when it came out.
I successfully rooted 3.2.80 using information from this site.
This weekend I tried to update to the new 4.0.4. The update seemed to "hang", and I ended up forcing a power-off.
I subsequently used the recovery menu to do a full system format, and then tried to reinstall the 4.0.4 firmware - I've tried this a few times and each time it *seems* to be successful. After copying the AOS file to the device over USB, and selecting "ok", it says to leave the USB connected, a progress bar winds its way across the bottom of the screen, and then it reboots.
However, each time when it tries to boot, it just sits at the animated boot logo and never proceeds further. I've even tried letting it sit overnight - when I checked it in the morning after allowing it 6+ hours, it was STILL just sitting there rolling that bright bar across the "ARCHOS" logo..
I've tried to go back to 3.2.80, it gives an "update failed" on that every time I try.
I did the "remove developer edition" in the recovery menu, thinking perhaps the official firmware was balking on a 'rooted' device. Reformat, recopy AOS file, reboot, still no cigar..
I tried downloading the AOS file again, no luck..
Am I now the not-so-proud owner of a flat shiny brick? Is there some other procedure I can try? Has anyone else experienced this?
ANY advice or suggestions will be greatly appreciated.
If anyone needs more details or other info just let me know.
1. Download update .aos again (just to be sure)
2. Boot to recovery
3. Select Reset Android option
4. Install update
I hope this helps
gen_scheisskopf said:
1. Download update .aos again (just to be sure)
2. Boot to recovery
3. Select Reset Android option
4. Install update
I hope this helps
Click to expand...
Click to collapse
I've already done 2,3,4 several times. I managed to get a hold of someone at Archos that said that the file gets validated when it goes to update, and I'd get an error if it was corrupt. It doesnt give me an error there, it accepts the file.
As I'm currently on a slow hotel Internet connection, does anyone have an md5sum or sha1sum of their ICS .aos file I can use to validate mine against? (Annoying that Archos doesnt include a hash on their site)
Update .aos file is digitally signed (this also includes checksums of contents). If signature check fails recovery will not flash it.
My guess is that you'll have to give tablet to service unfortunately
tapatalked from Desire
In case anyone cares, I did in fact end up sending it back, and they sent me a replacement.
The replacement had ICS on it, and has in fact since OTA's another update without any problem.
Megadave123 said:
In case anyone cares, I did in fact end up sending it back, and they sent me a replacement.
The replacement had ICS on it, and has in fact since OTA's another update without any problem.
Click to expand...
Click to collapse
I cant believe you got through to support. I have been trying for the best part of 3 months and got no reply. I am new to XDA since I recently got a HTC Sensation. Saw that we have this section here for Archos G9s. Got my ''broken'' one out of storage and rooted and flashed it with a custom ROM. And it works again. Surprised since I had the exact same issue you got but I was not rooted when updating.
Hi everyone, i have a problem with my Sony Tablet S, suddenly it's freezing and when i try to turned it back on it stuck on booting screen (with sony logo ).
then i checked to the internet and i found that i have to hard reset it, by holding down the + volume button and power button in order to get to the Android System Recovery. But then again no clue, i have tried reset to factory setting and keep stuck on boot screen. its frustating.
Prompt on my screen :
E: Fail to read boot logo flag
E: Cant Open / Dev/block/mmcblk0p5
(No Such file or directory)
E: Failed to Mount /cache (No such file or directory)
E: Cant mpunt/ cache/recovery/command
E: failed to mount /cache (No such file or directory)
E: failed to mount /cache (No such file or directory)
On the Android System Recovery there is Update System from SD Card, is there any possible ways that i can put Honeycomb virtual image on to the SD Card then make it as a bootable device, so i can boot from my SD Card.
Please help! thanks a lot !
If it was previously on Honeycomb, and you could find someone with a rooted Tablet running ICS from the same region and same version (WiFi vs 3G etc) then you might be able to recover it.
You would need to get them to install the rescue-bcakdoor on their device, allowing them to download the OTA update file. You could then try and ABD push that file onto your device's storage and install from the Recovery menu.
Just a thought! Otherwise, you could try sending it back under Warranty or something..
Disclaimer: This is by no means a tested solution and you may want to check on a few things before trying this. I take no responsibility for anything that happens as a result of this procedure. As always, I recommend trying Sony's Warranty and Repairs department for an official, warranty-valid repair.
Same problem here
I have the same problem with my Sony tablet s, i udated it to 4.0.3, it was working fine till yesterday when it would not start, its stuck at the logo, ive tried factory reset, but nothing changed, i did not have a recovery data either.
i would appreciate if some one would guide me how to fix it, either upload the ota update file, can i root it some how or flash it by using an UPDATE.Zip on memory card and try system recovery using android 3.2.1 ota file. please help
help me too
I got the same problem yesterday(29. May), it might be google did something via OTA. I'm using China version, changed region to US and upgraded it to ICS, but unfortunatlly, can't root in ICS now. Yesterday, it suddenly stuck and can't reboot any more. always stuck on Starting Screen. I called Sony Customer Center, and follow their struture to reset the tablet, but not help. Can any one help me to fix it....
InMyEyes said:
I got the same problem yesterday(29. May), it might be google did something via OTA. I'm using China version, changed region to US and upgraded it to ICS, but unfortunatlly, can't root in ICS now. Yesterday, it suddenly stuck and can't reboot any more. always stuck on Starting Screen. I called Sony Customer Center, and follow their struture to reset the tablet, but not help. Can any one help me to fix it....
Click to expand...
Click to collapse
I'm not too sure about easy fixes (I'd have to work through it a lot more, which is tricky without the error), but I know that it can't be Google. Google neither could nor would release an OTA package that aggressively downloaded to the device, installed and then broke something at system boot-level. Doesn't really work like that.
arso123 said:
I have the same problem with my Sony tablet s, i udated it to 4.0.3, it was working fine till yesterday when it would not start, its stuck at the logo, ive tried factory reset, but nothing changed, i did not have a recovery data either.
i would appreciate if some one would guide me how to fix it, either upload the ota update file, can i root it some how or flash it by using an UPDATE.Zip on memory card and try system recovery using android 3.2.1 ota file. please help
Click to expand...
Click to collapse
If you have this problem and you don't have a rooted tablet, you won't be able to downgrade. you must send it back for repair, since it can't reboot normally, sony won't detect any self bricking tracks, so warranty is still in the game, had the same problem to with Region Changer somewhere in V2.1 or something.
Goodluck.!
I have the same problem too, and I can't send it to sony service because it's not on sale in my country. I look forward to deal with it through sd card. Can't use USB connection. (not rooted too).
I have a similar issue, but mine seems to be stuck on the bootscreen animation (with the swirly yellow lines traveling from one side to the other). Haven't tried the power + volume up yet, will try that to see if I can hard reset. I was rooted on HC, but decided to take the ICS update so I believe that I'm unrooted at this point--still unsure though.
Regions - guarantee
Same problem here
Have tried all of the tips in this post...Still stucked with the Sony logo..
I bought my in Krakow, Poland, but lives in Norway... it has the /P on the back instead of the /N.
Do you know if the guarantee is worldwide? If I can drop this to a Sony shop in Norway?
I dont have the receipt anymore, because I claimed a refound from the company I work in...
Thanks
Rune
What color is on the tabblet?
Is it green or red?
I think if its green, there is no fix.
If its red, use the battery completely then recharge it until green light.
Try after that. Mine was fixed whit same problem.
Well, I've tried everything that I've found on the forums/internet to no avail. Just contacted Sony support and am having them send me a box to ship it back for repairs (luckily I only bought it last December). The operator on the phone says that it's most likely a hardware issue if it doesn't get pass the "Sony" logo. This leaves me a bad taste with Sony, won't be buying a tab or phone from them again.
I have had the same issue, so will be going back to Sony soon for a repair. Disappointed as I've only had it 6 weeks, but as long as the repair service is good I'll be ok.
Same problem here tonight. Unreal. Purchased last August. Won't buy another Sony again. First it was the constant soft resets in order to power on. Now this.
I got the same problem on my sony tablet s device too model SGPT111US/S anykne fixed this erorr yet?
Now i can't do any things because it stoped at logo SONY, please help, any flasher or rom support this device from pc ?
Just got off the phone with tech support. Couldn't even get it to do a factory reset. Stuck on system restore screen. Sending it in for repair. Very disappointing. Paid $500 for this thing. Didn't last a year. A few more weeks and I would have been out of luck on the warranty.
SCIONTX said:
Just got off the phone with tech support. Couldn't even get it to do a factory reset. Stuck on system restore screen. Sending it in for repair. Very disappointing. Paid $500 for this thing. Didn't last a year. A few more weeks and I would have been out of luck on the warranty.
Click to expand...
Click to collapse
I Have no money for this, and i'm in vietnam, can't contact with any one.
No way to fix this ?
update, when i'm enter recovery mode, i enter ADB, run via cmd, adb can send reboot comand: adb reboot :cyclops:
then the tablet reboot, but still loop at sony, and i see windows is try to install MTP USB Device but un successful.
Any ideas ?
goldenfish said:
update, when i'm enter recovery mode, i enter ADB, run via cmd, adb can send reboot comand: adb reboot :cyclops:
then the tablet reboot, but still loop at sony, and i see windows is try to install MTP USB Device but un successful.
Any ideas ?
Click to expand...
Click to collapse
What version did you have before boot loop? 3.2.1, 4.0.3?? Try to flash a us rom from recovery. You can find in my signature link.
Good luck
Chur
stifilz said:
What version did you have before boot loop? 3.2.1, 4.0.3?? Try to flash a us rom from recovery. You can find in my signature link.
Good luck
Chur
Click to expand...
Click to collapse
it's 4.0.3,
custom rom from your link is zip file, i don't know how to flash this file, because the tablet can't mount sdcard ????
goldenfish said:
it's 4.0.3,
custom rom from your link is zip file, i don't know how to flash this file, because the tablet can't mount sdcard ????
Click to expand...
Click to collapse
Oh didn't realise you can't mount, that is an issue then. Sorry you may be soft-bricked
Hope you can find something
Chur
So, I rooted my phone saturday, and didn't do much on it til early this morning when I started deleting factory apps with Terminal Emulator...I had succesfully deleted Photobucket, Books, Ponyt, Talk, and a couple others, but then I accidentally switched to landscape while using TE and I thought that pressing execute would return me back to the regular TE screen, it didn't. And when I did return to the regular TE screen, all of the android system items began force closing repetitively.
So initially I believed that it was the TE that accidentally deleted the android system stuff when I was pressing execute, but now I believe it was just a common mishap that happens once a phone is rooted, given the user toggled with the phone.
Well, I unfortunately did not download Rom Manager, or anything that would have gotten ClockWork on to my phone. Therefore when I get into recovery mode, it is the Android recovery mode, and after the wiping of cache and wiping of data/factory reset and rebooting, the bootanimation continues to reboot, never getting to the home.
I have read the guide by Phistachio on fixing such problem, and I have tried such. But while using Odin, my final message has continuously been <ID: 0/005> SetupConnection..
And looking at the loading bar, no progress has seemed to be made. I was wondering what I may be doing wrong or what may I do to fix this issue. And also, does the ZTE score have a Download Mode?
PS: Thanks to anyone who've taken their time to read and/or aid me with this.
JummyBlazed said:
So, I rooted my phone saturday, and didn't do much on it til early this morning when I started deleting factory apps with Terminal Emulator...I had succesfully deleted Photobucket, Books, Ponyt, Talk, and a couple others, but then I accidentally switched to landscape while using TE and I thought that pressing execute would return me back to the regular TE screen, it didn't. And when I did return to the regular TE screen, all of the android system items began force closing repetitively.
So initially I believed that it was the TE that accidentally deleted the android system stuff when I was pressing execute, but now I believe it was just a common mishap that happens once a phone is rooted, given the user toggled with the phone.
Well, I unfortunately did not download Rom Manager, or anything that would have gotten ClockWork on to my phone. Therefore when I get into recovery mode, it is the Android recovery mode, and after the wiping of cache and wiping of data/factory reset and rebooting, the bootanimation continues to reboot, never getting to the home.
I have read the guide by Phistachio on fixing such problem, and I have tried such. But while using Odin, my final message has continuously been <ID: 0/005> SetupConnection..
And looking at the loading bar, no progress has seemed to be made. I was wondering what I may be doing wrong or what may I do to fix this issue. And also, does the ZTE score have a Download Mode?
PS: Thanks to anyone who've taken their time to read and/or aid me with this.
Click to expand...
Click to collapse
Well..its sounds like u deleted a app or something else that nececary for ur phone to work like it should
so i recomend u to reflash it u dont need the clockworkmod for every rom just try to download a custom rom and flash it
if this doenst work try to flash a cwm image via odin or adb
for ur interest:
http://forum.xda-developers.com/showthread.php?t=1706918
hy guys, i have a ZTE V9 light and after an unsuccessful update i've managed to brick it. Now it won't start at all no mater what button configiration i use. The only thing working is the red led when i connect the tablet to my laptop. Have any ideas haw to boot in FTM mode to do recover? Thank you
Sent from my GT-I9000 using xda app-developers app
mihaidntgv said:
hy guys, i have a ZTE V9 light and after an unsuccessful update i've managed to brick it. Now it won't start at all no mater what button configiration i use. The only thing working is the red led when i connect the tablet to my laptop. Have any ideas haw to boot in FTM mode to do recover? Thank you
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
check out this stuff
http://forum.xda-developers.com/showthread.php?t=1706918
I've been searching the forums, and google for a while and can't seem to find a solution that works at all for me. First off, a little history. I am a n00b, and I very stupidly rooted my phone last night, without a recovery.... Actually I don't think just rooting was a big deal, it was me changing the vm heap properties that was really stupid. Why did I change it when the phone was working fine you might ask? Because I quickly gleaned over a forum post about adjusting the heap size to make your phone blazing fast, so, like any other idiot would, I did what the thread suggested, and instead of blazing fast speeds I got a boot screen logo....... forever... Talk about a huge mistake on my part....
Here's the problem,
Phone is stuck on the bootscreen, I can boot into system recovery (stock).
Android System Recovery has a message on the bottom of the screen that says "E: Cannot load volume /misc!"
I have wiped the cache partition, and did factory reset according to the manufactures website.
I cannot get ADB of Fastboot to see the device, even with drivers installed.
I do have a back up of build.prop that is unscathed, but I have no idea how to flash it, or "push" it or whatever.
I do not have CWM installed, and it appears that usb debugging is disabled.
My phone is a Kyocera Hydro. I'm using Windows 7 64bit.
I know I should never have done this, it was idiotic, and easily the dumbest thing I've done in a while. I'm hoping someone out there can help me fix this. Is it possible to put the backup of build.prop on the SD card and have it overwrite the corrupted one? Is there any hope at all?
I guess it can't be done then? I had hoped that as long as the bootscreen could come on that there was hope. Hopefully someone out there knows how to push the backup build.prop back onto the phone.
Well right now you're pretty screwed. There's no way to restore it without a custom recovery. You have 2 options -
1) Wait for someone to make a custom recovery for your phone.
2) Try to claim warranty and get it restored/exchanged at the service center. Say it just randomly rebooted and got stuck at the boot screen.
Sent from my Desire HD using xda premium
Aravoth said:
I guess it can't be done then? I had hoped that as long as the bootscreen could come on that there was hope. Hopefully someone out there knows how to push the backup build.prop back onto the phone.
Click to expand...
Click to collapse
Where did you get the phone Boost, Amazon Wal-Mart?
Sent from my KFTT using xda app-developers app
This will help you unbrick a bricked FireTV 2. You must download the following:
FireTV 2 Recovery Installer
FireTV 2 Recovery
Unbrick Images (md5sum: 5e774497b3bad5c47d1c744410f6db12)
Extract all 3 zip files to the same directory.
You must decide if you want to use unbrick.img or unbrick+ramdisk.img. Using unbrick.img, it should take about 30 minutes. Using unbrick+ramdisk.img it could take up to 2 hours. You can only use unbrick.img if you have an sdcard. If you have an sdcard, place ramdisk-recovery.cpio.lzma in the root directory of it.
Run unbrick_firetv2.bat for Windows or unbrick_firetv2.sh for Linux or OSX.
First, it will ask you which file you want to use, unbrick.img or unbrick+ramdisk.img. You must type the name of the image you want to use.
Make sure the USB cable is connected and turn on the FireTV 2.
Then it will start reading from the FireTV. Then it will prompt you with a warning:
Code:
No target file specified. Is this a partition image?
If this is not, DO NOT CONTINUE, otherwise press 'y' to continue.
Write partition image? <y|n>
Type a 'y' and hit enter.
It should start writing. Eventually it will finish. If you put the ramdisk on the sdcard, make sure it is plugged in and power cycle the Fire TV. It should skip the bootmenu and take you straight to recovery. If for some reason the USB keyboard doesn't work, unplug and replug it. It should start working.
rbox said:
This will help you unbrick a bricked FireTV 2. You must download the following:
FireTV 2 Recovery Installer
FireTV 2 Recovery
Unbrick Images
Extract all 3 zip files to the same directory.
You must decide if you want to use unbrick.img or unbrick+recovery.img. Using unbrick.img, it should take about 30 minutes. Using unbrick+recovery.img it could take up to 2 hours. You can only use unbrick.img if you have an sdcard. If you have an sdcard, place ramdisk-recovery.cpio.lzma in the root directory of it.
Run unbrick_firetv2.bat for Windows or unbrick_firetv2.sh for Linux or OSX.
First, it will ask you which file you want to use, unbrick.img or unbrick+recovery.img. You must type the name of the image you want to use.
Make sure the USB cable is connected and turn on the FireTV 2.
Then it will start reading from the FireTV. Then it will prompt you with a warning:
Code:
No target file specified. Is this a partition image?
If this is not, DO NOT CONTINUE, otherwise press 'y' to continue.
Write partition image? <y|n>
Type a 'y' and hit enter.
It should start writing. Eventually it will finish. If you put the ramdisk on the sdcard, make sure it is plugged in and power cycle the Fire TV. It should skip the bootmenu and take you straight to recovery. If for some reason the USB keyboard doesn't work, unplug and replug it. It should start working.
Click to expand...
Click to collapse
Awesome rbox! I see you've been busy...Really appreciate everything you do for us Fire TV folks.
Awesome work as always!
Thank you mate... Your great work made my day and got out of bricked state !!!!!
Got to recovery and flashed your rooted 5.0.31 and rebooted to perfectly working aftv2 + rooted .. Good job as always mate , thanks
One question, could I just flash the rooted 5.0.4 from recovery or should I do something else??
samykoka said:
Thank you mate... Your great work made my day and got out of bricked state !!!!!
Got to recovery and flashed your rooted 5.0.31 and rebooted to perfectly working aftv2 + rooted .. Good job as always mate , thanks
One question, could I just flash the rooted 5.0.4 from recovery or should I do something else??
Click to expand...
Click to collapse
You can flash whatever version you want...
rbox, looks like amazon sent me a bricked fire tv, while im at possession, i figured a i play around with it.
when i got it it was stuck to amazon white amazon logo,
so i waited for it for like 30 minutes to boot, but nothing changes... then with recent root method (aftv gen 2)
i figured i install this
http://forum.xda-developers.com/fire-tv/development/firetv-2-recovery-t3309780/page17#post65265240
i was able get to recovery!
and applied pre rooted firmware, but after completion,
i think its beyond bricked..
no screen, my led flash drive does not even flash or blink anymore when i put it on boot...
i can still handshake still apply the unbrick method
my question is after applying this brick.img
would i suppose to get a screen? and boot up
but still the same no screen nothing... not even white amazon logo...
or this is done..
thanks
daffung said:
rbox, looks like amazon sent me a bricked fire tv, while im at possession, i figured a i play around with it.
when i got it it was stuck to amazon white amazon logo,
so i waited for it for like 30 minutes to boot, but nothing changes... then with recent root method (aftv gen 2)
i figured i install this
http://forum.xda-developers.com/fire-tv/development/firetv-2-recovery-t3309780/page17#post65265240
i was able get to recovery!
and applied pre rooted firmware, but after completion,
i think its beyond bricked..
no screen, my led flash drive does not even flash or blink anymore when i put it on boot...
i can still handshake still apply the unbrick method
my question is after applying this brick.img
would i suppose to get a screen? and boot up
but still the same no screen nothing... not even white amazon logo...
or this is done..
thanks
Click to expand...
Click to collapse
After using unbrick.img, if you put the ramdisk on the sdcard, you should get recovery. If not, then there is something bad the hardware.
Many thanks, rbox -- unbrick_firetv2.bat worked for me in bootcamp. Selected unbrick+ramdisk.img, then rebooted into TWRP. Initially when I installed prerooted 5.0.5_r2, setup gave me a screen (after remote pairing and language selection) that it was checking for updates. The setup then halted with an error window that it could not connect to Amazon's server, and that I should power off and reset the AFTV. I then flashed prerooted 5.0.4_r2, completed the initial setup, and reflashed prerooted 5.0.5_r2 (which let me get around the update error).
Again, thanks for all your work!!
rbox said:
After using unbrick.img, if you put the ramdisk on the sdcard, you should get recovery. If not, then there is something bad the hardware.
Click to expand...
Click to collapse
i wonder what caused that bricked.. , ( well it was already bricked, when amazon send it to me it was stuck at white amazon logo, then only when i applied the pre rooted firmware, thats when it stop showing screens from there..wouldn't it fix the problem already since i was able to get to recovery.....
id try the sd card 1 last thing il probably go to walmart and try that, if nothing fix it i guess its total beyond brick..
Hi,
thank you very much for your great work @rbox!
Just a note:
I think, in the bash script, there is a "2" in the last line that doesn't belong there?
And there is a "unbrick+ramdisk.img" file, but no "unbrick+recovery.img" in the zip container. Some might get confused by that...
But everything works fine (using ramdisk)!
thx
Takeoo111111 said:
Hi,
thank you very much for your great work @rbox!
Just a note:
I think, in the bash script, there is a "2" in the last line that doesn't belong there?
And there is a "unbrick+ramdisk.img" file, but no "unbrick+recovery.img" in the zip container. Some might get confused by that...
But everything works fine (using ramdisk)!
thx
Click to expand...
Click to collapse
Thanks. I fixed it all.
rbox said:
After using unbrick.img, if you put the ramdisk on the sdcard, you should get recovery. If not, then there is something bad the hardware.
Click to expand...
Click to collapse
rbox, looks like its a hardware problem? but problem is i had white screen when i applied the pre rooted fire tv, thats when i get no screen, no boot... do think its possible a fix for this, via handshake?
daffung said:
rbox, looks like its a hardware problem? but problem is i had white screen when i applied the pre rooted fire tv, thats when i get no screen, no boot... do think its possible a fix for this, via handshake?
Click to expand...
Click to collapse
Well try the unbrick image and see if it works.
rbox said:
After using unbrick.img, if you put the ramdisk on the sdcard, you should get recovery. If not, then there is something bad the hardware.
Click to expand...
Click to collapse
rbox said:
Well try the unbrick image and see if it works.
Click to expand...
Click to collapse
yup,
sucessfully flashed unbrick.img, and had sd card ramdisk-recovery.cpio.lzm.
still the same...
no boot, no screen, not even white screen?
and no signal from hdmi
I am afraid I have to report a brick on 5.0.5r3 -
Played some Vice City, went back into Kodi, played a video that was still in the paused state, then the screen flashed to black and then back to the Video in Kodi twice and then - a dreaded blackscreen.
Upon a reboot I still get the amazon logo, I get the recovery bootscreen and also can still enter TWRP recovery, but when I try to boot into the normal OS I only get the amazon logo and then a fade to black (amazon Fire TV animated logo not showing up). The blue LED on the Fire TV is steadily blinking along...
(Switched TVs and HDMI cables - just in case (no HDCP problem.. ))
Already wiped /system /data /data including media /cache and /dalvik - and reinstalled both 5.0.5r1 and r3 multiple times.
Right now I have two questions - 1st (for the fast ones, because I am trying it anyway) - should I still try to unbrick using this tutorial (i.e. If I have access to the recovery and already formated the whole range of partitions once - does the unbrick image do anything more than that?).
And 2nd - is there any "factory image" maybe without the stock recovery disabled - just in case, at this point - I'd try most things - really...
harlekinrains said:
I am afraid I have to report a brick on 5.0.5r3 -
Played some Vice City, went back into Kodi, played a video that was still in the paused state, then the screen flashed to black twice and then - a dreaded blackscreen.
Upon a reboot I still get the amazon logo, I get the recovery bootscreen and also can still enter TWRP recovery, but when I try to boot into the normal OS I only get the amazon logo and then a fade to black (amazon Fire TV animated logo not showing up). The blue LED on the Fire TV is steadily blinking along...
(Switched TVs and HDMI cables - just in case (no HDCP problem.. ))
Already wiped /system /data /data including media /cache and /dalvik - and reinstalled both 5.0.5r1 and r3 multiple times.
Right now I have two questions - 1st (for the fast ones, because I am trying it anyway) - should I still try to unbrick using this tutorial (i.e. If I have access to the recovery and already formated the whole range of partitions once - does the unbrick image do anything more than that?).
And 2nd - is there any "factory image" maybe without the stock recovery disabled - just in case, at this point - I'd try most things - really...
Click to expand...
Click to collapse
The unbrick image just puts enough on system to be able to get to recovery. If you can already get to recovery, it won't get you anything. The disabled stock recovery isn't going to effect anything while running android. All it does it prevent the bootloader from running it. I can't really explain it if you did an advanced wipe of data.
Hardware Issue probably. Thanks for the fast response.
Cheers.
(I'll do another advanced wipe - just for kicks.. )
edit: Went through with another full wipe - rebooting the device afterwards (= softbrick for sure, because not even TWRP is accessible and there is no OS on the device) - which at that point got "parked" on the white amazon logo indefinitely. (Perfect for the "I aint know nothing" returning the device approach. Just in case Amazons 5.0.5 turns out to brick a few more Fire TVs... As long as rbox didnt modify the kernel, I'd say its Amazons fault. ) Then went through the unbrick procedure in this thread - which worked as described (TWRP was installed on the device and autobooted on the powercycle after the unbrick script had finished). Then installed 5.0.5r1 again and rebootet - just to be met with the same error profile as before "dark screen" - not even the animated amazon logo (just the white one in the beginning).
This time - on a better TV screen it was visible though, that the screen showed a small horizontal line, and then flashed in a lighter black color twice, before going back to full TV black. So yes the problem seems to lay somewhere on the video signal path. Its curious though, that TWRP still got (and gets) displayed...
Works perfect. Thx
Can someone help me? I followed all the steps in the guide and when the unbricking program is writing the filesystem, it always gets stuck at 17%. Maybe I am doing something wrong?
rbox said:
After using unbrick.img, if you put the ramdisk on the sdcard, you should get recovery. If not, then there is something bad the hardware.
Click to expand...
Click to collapse
I am in a boot loop. Goes to amazon white logo. Light on FireTV2 turns orange then reboots into custom recovery but it automatically starts trying to mount partitions (one of them is cache) and it fails on all of them. Then moves along to the white amazon screen again and repeats the entire process. I ran the unbrick.img and the problem persists.
I'm currently in the process of running unbrick+recovery.img method to see if it makes any difference. Should it? Is there anything that I may be overlooking?
I'm fairly sure that the reason this happened is from checking ALL the check boxes in the format/wipe section of the custom recovery. After that these issues happened. Does that mean permabrick?