Develop Bugs

Phone "bricked"?? [CM7]

So here is what happened...
I am on the 2.2.2 Nordic sbf and Installed CM7 5.1 on it...
I used it for now 1 week.
But when the phone was booting, the green LED appeared while the Red M was displayed (due to the 2nd-init)
But I accidentally removed the battery at this moment and now my phone don't want to boot anymore........
I tried to reboot again but it was in a boot loop....
Then I wiped data by stock recovery and when I reboot,
It stays on the Red M logo and nothing......
I tried everything!
Go to system recovery and wipe data
Went to Custom Recovery and Restore
Re-installed the fixed Nordic sbf...
STILL NO LUCK :"(((((((((((((((((((
Please help me guys.....
please....
I'm gonna cry if it's bricked...
EDIT: Flashed 3.4.3-11 it boots but stuck in a boot loop... :'(

WIIstpM said:
So here is what happened...
I am on the 2.2.2 Nordic sbf and Installed CM7 5.1 on it...
I used it for now 1 week.
But when the phone was booting, the green LED appeared while the Red M was displayed (due to the 2nd-init)
But I accidentally removed the battery at this moment and now my phone don't want to boot anymore........
I tried to reboot again but it was in a boot loop....
Then I wiped data by stock recovery and when I reboot,
It stays on the Red M logo and nothing......
I tried everything!
Go to system recovery and wipe data
Went to Custom Recovery and Restore
Re-installed the fixed Nordic sbf...
STILL NO LUCK :"(((((((((((((((((((
Please help me guys.....
please....
I'm gonna cry if it's bricked...
Click to expand...
Click to collapse
Did you reinstalled it with RSD Lite?

AkkiandDefy said:
Did you reinstalled it with RSD Lite?
Click to expand...
Click to collapse
Yes I reinstalled Nordic sbf with RSD Lite but didn't work....
Now I tried with the 3.4.3-11 One and it Boot with the Blur animation but it's STILL in a boot loop :'(( :\ ....

WIIstpM said:
Yes I reinstalled Nordic sbf with RSD Lite but didn't work....
Now I tried with the 3.4.3-11 One and it Boot with the Blur animation but it's STILL in a boot loop :'(( :\ ....
Click to expand...
Click to collapse
Sorry for off-topic but at this point I would cry, too

AkkiandDefy said:
Sorry for off-topic but at this point I would cry, too
Click to expand...
Click to collapse
what do you mean............
Is it bricked then?................

WIIstpM said:
what do you mean............
Is it bricked then?................
Click to expand...
Click to collapse
I would say, yes
but it could be that somebody has a way to make it functional again.
PS.: I would post this to the Defy Development topic, because the activity there is muuuch higher.

AkkiandDefy said:
I would say, yes
but it could be that somebody has a way to make it functional again.
PS.: I would post this to the Defy Development topic, because the activity there is muuuch higher.
Click to expand...
Click to collapse
Gosh it Booted FINALLY!!
I went to system recovery and wiped data again... Phew... I was about to commit suicide... lol
I wonder If I can still go to Nordic again and install CM7....

Did you wipe date/factory reset in stock recovery?
Edit: ok, glad to got it back
What did you do to make it work?
Just a question when you flashed as example the 3.43.11 Rom , did the M-Logo appear??

spryte said:
i had a similar problem, but i wasn't able to flash my device any more.
Try to wipe and afterwards install beta 5.0, for me it worked.
Otherwise try this rom and flash it. This is the one i use as base rom.
Finally, as long as you are still able to power up your phone with the charger it should be possible to find a solution for your problem.
Click to expand...
Click to collapse
What do you mean by flash?? a SBF or a ROM??
What happened when you tried to flash another??
Phew... I'm so relieved now... I'm now definitely more careful with my phone!!

WIIstpM said:
Gosh it Booted FINALLY!!
I went to system recovery and wiped data again... Phew... I was about to commit suicide... lol
I wonder If I can still go to Nordic again and install CM7....
Click to expand...
Click to collapse
When it boots and gets stuck in a bootloop the phone is not, and I repeat, NOT bricked. Apparently there was clearly a software problem but as long as the device turns on, the display works and you manage to get to the bootloader then there is very little need to worry. So you know for the next time: suppress your panic, breathe and just keep trying.
Even when the screen doesn't turn on it isn't necessarily a bricked phone. This happened to me a few months ago because I was so stupid to flash an older sbf. It turned out that the device actually still functioned up to the bootloader. RSD lite detected the phone and I managed to revive it completely by flashing the original sbf. The Defy really is almost unbrickable mostly thanks to the locked bootloader, a blessing in disguise.

AgentSmith said:
When it boots and gets stuck in a bootloop the phone is not, and I repeat, NOT bricked. Apparently there was clearly a software problem but as long as the device turns on, the display works and you manage to get to the bootloader then there is very little need to worry. So you know for the next time: suppress your panic, breathe and just keep trying.
Even when the screen doesn't turn on it isn't necessarily a bricked phone. This happened to me a few months ago because I was so stupid to flash an older sbf. It turned out that the device actually still functioned up to the bootloader. RSD lite detected the phone and I managed to revive it completely by flashing the original sbf. The Defy really is almost unbrickable mostly thanks to the locked bootloader, a blessing in disguise.
Click to expand...
Click to collapse
The same I asked, if he saw the M-Logo because then it's normal that it needs more time (5-10 minutes)

AkkiandDefy said:
Did you wipe date/factory reset in stock recovery?
Edit: ok, glad to got it back
What did you do to make it work?
Just a question when you flashed as example the 3.43.11 Rom , did the M-Logo appear??
Click to expand...
Click to collapse
Yes everything appeared as normal (white M-logo though)..
When I flashed 3.4.3-11 I got a boot loop then I went to system recovery and wipe Data and it works again..
Do you know if I still can flash other sbf or rom??
I want to go back to CM7... I also have a CWM backup but I'm afraid to restore this...

WIIstpM said:
Yes everything appeared as normal (white M-logo though)..
When I flashed 3.4.3-11 I got a boot loop then I went to system recovery and wipe Data and it works again..
Do you know if I still can flash other sbf or rom??
I want to go back to CM7... I also have a CWM backup but I'm afraid to restore this...
Click to expand...
Click to collapse
Then it maybe wasn't a bootloop, because if you flash a new sbf, its normal that it can take 10 minutes to boot

AgentSmith said:
When it boots and gets stuck in a bootloop the phone is not, and I repeat, NOT bricked. Apparently there was clearly a software problem but as long as the device turns on, the display works and you manage to get to the bootloader then there is very little need to worry. So you know for the next time: suppress your panic, breathe and just keep trying.
Even when the screen doesn't turn on it isn't necessarily a bricked phone. This happened to me a few months ago because I was so stupid to flash an older sbf. It turned out that the device actually still functioned up to the bootloader. RSD lite detected the phone and I managed to revive it completely by flashing the original sbf. The Defy really is almost unbrickable mostly thanks to the locked bootloader, a blessing in disguise.
Click to expand...
Click to collapse
lol I panicked because I tried almost everything!
weird bootloop (after M-logo, black screen)
bootloader -> didn't work
custom recovery -> didn't work
stock recovery -> didn't work
CWM Backup -> didn't work
Different sbf -> bootloop
Finally Stock recovery again -> worked!

hi, i have a similar problem to yours (i made my own thread about it and still no ideas) but RSD Lite doesn't discover my phone, it just doesn't appear there. How can i try to make it appear in RSD LitE? My prhone also doesnt load the system, just hangs in Motorola logo moment. I can go to recovery and boot menu etc...
please help me, i feel like crying as well.... (

AkkiandDefy said:
Then it maybe wasn't a bootloop, because if you flash a new sbf, its normal that it can take 10 minutes to boot
Click to expand...
Click to collapse
no it was, after some minutes the animations froze and it started all other again. the first few secs of booting are laggy as it used to, and it repeated..

your_login said:
hi, i have a similar problem to yours (i made my own thread about it and still no ideas) but RSD Lite doesn't discover my phone, it just doesn't appear there. How can i try to make it appear in RSD LitE? My prhone also doesnt load the system, just hangs in Motorola logo moment. I can go to recovery and boot menu etc...
please help me, i feel like crying as well.... (
Click to expand...
Click to collapse
Install the drivers
You will ask where to download them?
Google it
Click to expand...
Click to collapse

@AkkiandDefy
@spryte
@AgentSmith
THANK YOU FOR EVERYTHING!!
You were quick, helpful, and helped me to stay calm
Really I thank you!
:")
But could you please help @your_login too??
He got more severe problems than me apparently...

WIIstpM said:
@AkkiandDefy
@spryte
@AgentSmith
THANK YOU FOR EVERYTHING!!
You were quick, helpful, and helped me to stay calm
Really I thank you!
:")
But could you please help @your_login too??
He got more severe problems than me apparently...
Click to expand...
Click to collapse
He just need to install the Moto-Drivers, and RSD-Lite will recognize it

AkkiandDefy said:
He just need to install the Moto-Drivers, and RSD-Lite will recognize it
Click to expand...
Click to collapse
I have the drivers already installed, i managed to flash the nordic sbf a few days ago without any problem maybe its my computers fault that it fails to see the phone now..? i reainstalled them anyway and still no luck. However, i forgot to mention it earleier - when i connect a turned off phone via usb to my computer the phone itself turns on, hangs at motorola logo and on my computer i can hear 'device plugged' sound and MotoHelper windows appears on my computer, so it is being recognised to some extent. However, in RSD Lite there is still no device in the list and i can't try with flashing another sbf ((((

[Q] HTC One X not switching on

Okay, first of all, I would like to mention that I'm new at all of this.
I brought this phone 2 years ago and 2 months ago I decided I was going to root it. So I switched to CyanogenMod 11 M4 and did everything that was required i.e., unlocking bootloader and flashing a recovery and all that.
Just 2 days ago my phone showed an update available to CyanogenMod 11 M5. So I downloaded it and then the phone took me to my recovery. There I made a backup and flashed the M5.zip file that was downloaded. But when I rebooted my system a popup came saying com.process.phone has stopped unexpectedly. I pressed OK but it was persistent. I had no idea what to do so I booted into recovery and wiped data and then performed a restore of my previous backup that I had taken. Half-way through the backup the phone just switched off and then restarted with the traditional HTC logo and then it switched off again and restarted again and this process kept looping.
I loaded my bootloader and connected the phone via fastboot to my computer and erased the cache and flashed the recovery again. Then wehn I restored it started working normally as it did before.
But the battery was around 20% at that time so I left it to charge overnight. When I woke up the next day it was insanely hot and the LED was constantly red but it wouldnt wake up. So I loaded into recovery to restore it again but it kept on saying "Error mounting /system!"
And then after a few tries it switched off. Now it won't wake up again. Even the LED seems dead.
Has anyone of you ever encountered a similar issue? Any help would be appreciated. I've tried all the button combinations that are recognized by the device but nothing seems to work.

dead battery
i guess its because of corrupt or dead battery
try giving external power or replace battery and try
further you could even try other options like booting cwm
flashing last kernel image found

jhakjhuk1853 said:
i guess its because of corrupt or dead battery
try giving external power or replace battery and try
further you could even try other options like booting cwm
flashing last kernel image found
Click to expand...
Click to collapse
Booting CWM or flashing the last kernel image aren't an option because the device doesn't switch on at all. I cannot access the bootloader.

try changing battery
try changing battery by buying new battery and connecting
or remove battery and charge it with external source i guess u must have heard of jump starting battery
kartikeym309 said:
Booting CWM or flashing the last kernel image aren't an option because the device doesn't switch on at all. I cannot access the bootloader.
Click to expand...
Click to collapse

kartikeym309 said:
Okay, first of all, I would like to mention that I'm new at all of this.
I brought this phone 2 years ago and 2 months ago I decided I was going to root it. So I switched to CyanogenMod 11 M4 and did everything that was required i.e., unlocking bootloader and flashing a recovery and all that.
Just 2 days ago my phone showed an update available to CyanogenMod 11 M5. So I downloaded it and then the phone took me to my recovery. There I made a backup and flashed the M5.zip file that was downloaded. But when I rebooted my system a popup came saying com.process.phone has stopped unexpectedly. I pressed OK but it was persistent. I had no idea what to do so I booted into recovery and wiped data and then performed a restore of my previous backup that I had taken. Half-way through the backup the phone just switched off and then restarted with the traditional HTC logo and then it switched off again and restarted again and this process kept looping.
I loaded my bootloader and connected the phone via fastboot to my computer and erased the cache and flashed the recovery again. Then wehn I restored it started working normally as it did before.
But the battery was around 20% at that time so I left it to charge overnight. When I woke up the next day it was insanely hot and the LED was constantly red but it wouldnt wake up. So I loaded into recovery to restore it again but it kept on saying "Error mounting /system!"
And then after a few tries it switched off. Now it won't wake up again. Even the LED seems dead.
Has anyone of you ever encountered a similar issue? Any help would be appreciated. I've tried all the button combinations that are recognized by the device but nothing seems to work.
Click to expand...
Click to collapse
After the phone updated did u extract and flash boot.img from M5.zip?

convict_moody said:
After the phone updated did u extract and flash boot.img from M5.zip?
Click to expand...
Click to collapse
No, I didn't do that because when I switched over from a CM11 Nightly to CM11 Snapshot M4 I didn't extract and flash the boot image even then and everything was working perfectly. So, I didn't think I would need to.

kartikeym309 said:
No, I didn't do that because when I switched over from a CM11 Nightly to CM11 Snapshot M4 I didn't extract and flash the boot image even then and everything was working perfectly. So, I didn't think I would need to.
Click to expand...
Click to collapse
U should give it a try, since some CM updates triggers the kernel itself so boot.img should be flashed again.

convict_moody said:
U should give it a try, since some CM updates triggers the kernel itself so boot.img should be flashed again.
Click to expand...
Click to collapse
That is the problem. I can't. When I connect it to the PC it just never shoes up and I have no luck getting into the bootloader. Do you know of any reliable unbricking guides? I'm guessing my phone is possibly bricked.

kartikeym309 said:
That is the problem. I can't. When I connect it to the PC it just never shoes up and I have no luck getting into the bootloader. Do you know of any reliable unbricking guides? I'm guessing my phone is possibly bricked.
Click to expand...
Click to collapse
Check the guides in here:
HTC One X Reference

convict_moody said:
Check the guides in here:
HTC One X Reference
Click to expand...
Click to collapse
Nah, nothing is suitable. There are guides on how not to brick your device but nothing to unbrick it. :|
Thanks anyways. It's appreciated.

Another bricked HOX apparently. There seem to be loads of these on the internet. In my case, it can't have to do with custom roms or rooting since I never messed around with stuff like that. I even opened the HOX and checked all cables etc. There is no part that looks damaged or otherwise suspicious.
What can we do? How can we at least get access to the data in the internal memory?

Don't know if this will help, but it might be that it hasn't actually charged properly over night and has drained itself to death.
Try plugging into PC and get to fast boot.
Fastboot = Volume Down + Power Button
Then make a batch file out of this:
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
Click to expand...
Click to collapse
Then run the Batch File
Credit to Floepie for writing the .bat

Wilks3y said:
Don't know if this will help, but it might be that it hasn't actually charged properly over night and has drained itself to death.
Try plugging into PC and get to fast boot.
Fastboot = Volume Down + Power Button
Then make a batch file out of this:
Then run the Batch File
Credit to Floepie for writing the .bat
Click to expand...
Click to collapse
Unfortunately, there's no way this could help. because the HOX is literally dead. There is not even a charging indication when plugged into a PC or the wall charger. And thus it's not recognised by the PC and fastboot won't find it.

[Q] Nexus 7 suddenly bricked ?

Hello all, so yesterday I went on my tablet (Nexus 7 2013 WIFI ver.) and browsed the net a bit and went to sleep. I recall having around 30% battery power. This morning I wake up to an apparently flat battery (power button didn't turn on anything) so I just plugged it in and did something else. After a while, I took my tablet and started it with the power button. However, it got stuck on the Google logo and never fired up anything. I've rooted the tablet quite some time ago (months) so the cause is not from there.
Things I haven't recently done:
Installing an app.
Rooting or flashing anything.
Updating an app.
Things I have tried doing to fix the problem:
Booting into FASTBOOT then trying the recovery mode = still stuck on the Google logo.
Booting a custom recovery image using Wug's toolkit = frozen at the team logo (TWRP) / black screen (CWM).
Flash Stock + Unroot (Soft-Bricked/Bootloop) = FAILED (flash write failure).
So now I'm really stuck and desperate to make the device work again. I've been reading all day long and trying all sorts of solutions to no avail. And it seems far-fetched to me for a device like this to just instantly brick itself without any reason at all.
Can anyone help me with this case ? Or does anyone has any idea what just happened to my tablet ? :crying:
EDIT: I'm afraid that warranty might not work as the device was unlocked and rooted so it's the last solution for me.

Bumpity bump
No one has any idea what happened to the tablet and how to fix it ? I've tried doing some more flashing but to no avail. It just refuses to flash and keeps failing to write the files.

I think you need to leave out on the charger for 1/2hr without doing anything with it. You are probably using what little power it has charged by trying to reboot it, etc.
I had to do that once and it did the trick.
Sent from my Nexus 7 using XDA Free mobile app

There is no reason you should not be able to get in to recovery (power and volume down).
You could call Motorola. They have good tech support.

The exact same thing happened to me. I rooted it months ago and haven't changed a thing since then. It just froze up a few days ago. I restarted and it just gets stuck on the google screen. I can get into the bootloader, but when I try to go to recovery, the google screen comes up and won't go away. I've tried every method I can find for flashing the stock image and absolutely nothing is working. I just get stuck on the google screen.
Please update this if you find a solution!

Do u guys have the most up to date version of whatever particular recovery that you're on?

Yep. I've flashed the stock recovery multiple times to no avail. :/

nexusjas said:
Yep. I've flashed the stock recovery multiple times to no avail. :/
Click to expand...
Click to collapse
If you can't get into recovery or flash any images it sounds to me like a hardware failure. Bad memory maybe? If you've tried everything then RMA to Asus before the one year warranty runs out.
Have you tried to see if your computer sees your N7 by typing fastboot devices if you have the sdk installed?

wantabe said:
If you can't get into recovery or flash any images it sounds to me like a hardware failure. Bad memory maybe? If you've tried everything then RMA to Asus before the one year warranty runs out.
Click to expand...
Click to collapse
Not what I wanted to hear, but you're probably right. Thanks :/

nexusjas said:
Not what I wanted to hear, but you're probably right. Thanks :/
Click to expand...
Click to collapse
I was to slow with my update. Does your computer see your N7 with fastboot?

wantabe said:
I was to slow with my update. Does your computer see your N7 with fastboot?
Click to expand...
Click to collapse
Yes, I can get into the bootloader just fine and I can use fastboot. I go through the flashing process and the command prompt says everything flashed successfully, but when I restart the device, it hangs on the google logo. The same thing happens when I try to boot into recovery.

nexusjas said:
Yes, I can get into the bootloader just fine and I can use fastboot. I go through the flashing process and the command prompt says everything flashed successfully, but when I restart the device, it hangs on the google logo. The same thing happens when I try to boot into recovery.
Click to expand...
Click to collapse
If you fastboot flashed the factory image and can't boot up then it sounds like a hardware problem. Out of ideas, sorry.

wantabe said:
If you fastboot flashed the factory image and can't boot up then it sounds like a hardware problem. Out of ideas, sorry.
Click to expand...
Click to collapse
I'm not sure what happened, but I just ran this little utility again (I've done it many times over the last week or so to no avail) and it actually worked. Hopefully it keeps working!
Thanks for your help!

[Q] [Help] Phone tried to update now bricked

I seem to be having tons of problems with this new phone =( HTCdev unlock failed work and now the phone has bricked while trying to do an update.
It is stuck on the "HTC powered by android" splash screen. The screen wont turn off and the phone does not change. Is there some way to fix this or am I farked? The phone is literally 3 days old and I hope there is a way to save it.
I can shut it down with Power and vol+ but when it restarts it just locks up. computer does not recognize it though it did install some form of driver.

Dlome said:
I seem to be having tons of problems with this new phone =( HTCdev unlock failed work and now the phone has bricked while trying to do an update.
It is stuck on the "HTC powered by android" splash screen. The screen wont turn off and the phone does not change. Is there some way to fix this or am I farked? The phone is literally 3 days old and I hope there is a way to save it.
I can shut it down with Power and vol+ but when it restarts it just locks up. computer does not recognize it though it did install some form of driver.
Click to expand...
Click to collapse
I would return it

Since I cant do anything until Monday I decided to mess with the phone a little more, I was able to get a custom recovery installed finally so hopefully all I need to do is install a new rom but the problem is the recovery is unable to mount my SD card to perform the install. I can read the sd card when it is in my old phone but not on the HTC One. Currently have Philz Touch installed as the recovery.
Is there any way to fix this or even bypass it all together?
Edit: I have been able to side load CM11 Nightly onto the phone so now it is functioning. I am having an issue with sound though so hopefully I can fix that.

clsA said:
I would return it
Click to expand...
Click to collapse
Warranty returns are for manufacturing defects, not botched mods done by the owner. The phone is completely recoverable.

redpoint73 said:
Warranty returns are for manufacturing defects, not botched mods done by the owner. The phone is completely recoverable.
Click to expand...
Click to collapse
This sounded like a hardware problem to me
I seem to be having tons of problems with this new phone =( HTCdev unlock failed work and now the phone has bricked while trying to do an update.
Click to expand...
Click to collapse
it's hard to mess the phone up when you can't even get the bootloader unlocked

clsA said:
it's hard to mess the phone up when you can't even get the bootloader unlocked
Click to expand...
Click to collapse
User error. The phone wasn't bricked (if the screen comes on, its not bricked) and 99% of the time when folks here say the phone is bricked, its just not booting. As you can see from his subsequent post, he was obviously able to get bootloader unlocked, custom recovery and custom ROM. Of course, you could have not known that when you made your previous post. But failed bootloader unlock, and then the phone won't boot, is a big red flag that the user just did something wrong.

redpoint73 said:
User error. The phone wasn't bricked (if the screen comes on, its not bricked) and 99% of the time when folks here say the phone is bricked, its just not booting. As you can see from his subsequent post, he was obviously able to get bootloader unlocked, custom recovery and custom ROM. Of course, you could have not known that when you made your previous post. But failed bootloader unlock, and then the phone won't boot, is a big red flag that the user just did something wrong.
Click to expand...
Click to collapse
Fair enough ... I read it wrong I guess

clsA said:
Fair enough ... I read it wrong I guess
Click to expand...
Click to collapse
Naw, really looks more like a matter of the OP needs being clear enough, and not giving enough info. If anything, best to get clarification before suggesting warranty service (especially once mods have been started - but again it was hard from the OP's description to know how far it got). Although if it was in fact a hardware defect, of course a warranty claim is valid.

[Q] Think I bricked it from flashing!! Please help!!

Pretty sure that I screwed things up pretty good and its either bricked or I think stuck in fastboot every time it turns on!! Here's what I did:
So I downloaded the newest rooted rom (51.1.4.0_514006420 updated) from aftvnews.com...
not very patient so put it on an external drive and copied it to internal sd on the FireTV...
went into CWM (6.0.5.1.4a) and tried to flash it but got an error that it failed, wiped cache/dalvik just because and rebooted...
It kept on booting into CWM and finally realized I had another file on the sd just named rom - assuming that it was the version I was on before (51.1.3...) so wiped data/factory reset and flash that...
Immediately tried to flash the 51.1.4 over that - like an idiot - and that failed again...
wiped data/factory reset and tried to flash 51.1.3 and that failed...
wiped data/factory reset and rebooted...
Now I'm stuck on white Amazon logo and cant do anything with it!!
Any ideas would be greatly appreciated!!!! Is there any way to force it into recovery when it starts up

Mike3.14159 said:
Now I'm stuck on white Amazon logo and cant do anything with it!!
Any ideas would be greatly appreciated!!!! Is there any way to force it into recovery when it starts up
Click to expand...
Click to collapse
Does anyone know if the plain white amazon logo means it's stuck in fastboot??
If so, has anyone had any luck attaching a male-to-male usb to the back and do any fastboot commands??
If I can do a "fastboot reboot recover" then I can possibly fix it from CWM...

Mike3.14159 said:
Does anyone know if the plain white amazon logo means it's stuck in fastboot??
If so, has anyone had any luck attaching a male-to-male usb to the back and do any fastboot commands??
If I can do a "fastboot reboot recover" then I can possibly fix it from CWM...
Click to expand...
Click to collapse
Have you tried this:
http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/

cd2022 said:
Have you tried this:
http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/
Click to expand...
Click to collapse
Yeah, tried that like a dozen times before I posted again last time. Seems like that will only work if you soft bricked and the rom just wont fully boot. They were talking about the 'color logo' which I'm not even getting that far - gets hung up on the initial white logo. Appreciate the try though, thanks!

Mike3.14159 said:
Yeah, tried that like a dozen times before I posted again last time. Seems like that will only work if you soft bricked and the rom just wont fully boot. They were talking about the 'color logo' which I'm not even getting that far - gets hung up on the initial white logo. Appreciate the try though, thanks!
Click to expand...
Click to collapse
To quote the CWM post...
[size=+2]If something fails to flash DO NOT reboot. Try again and/or retransfer the file over adb.[/size]
Click to expand...
Click to collapse
If your /system is corrupt, it's not gonna boot. You can try the sysrq trick, but I don't think anyones ever been able to make that work with a bad /system.

Not sure what the 'sysrq' trick is but I will look it up and see what I can do, thanks! Saw on aftvnews late yesterday that the newest ota - after being rooted - did something crazy to yours so was actually waiting to see what had happened to yours and if you were able to get it back right then was hoping I could maybe learn some trick from that haha

Have you managed to fix this? i'm also stuck on the white logo

Looks like white logo without going to the colored logo means hard brick. Any USB attached will not work. There is no power coming out.
I wonder if there is a way to open up the unit and reflash the hardware from there.