Related
So, like everyone else, I rooted my phone and decided I dont need all this bloatware and other nonsense system apps.
I was foolish enough not to back up things I were removing, and nothing SEEMED important, but all of the sudden my "Htc dialer": Has stopped working.
My phone will turn on, but I cant turn it off, it just reboots without actually turning the phone off when I hold the power down.
I cant get it into recovery mode ( power vol up) and when it turns on, it goes to the default lock screen the phone comes with, and then I CANT see my home screen at all. The home button doesnt work either.
I cant get to my apps, I have to use my girlfriends DNA to beam whatever app im trying to get to onto my phone.
I can go to settings, but cant factory reset.
I tried killing the battery to get power it off, but then cant get to recovery screen there either.
I'm not sure if anyone has the system apps apk's just laying around so I can attempt to repair my phone, ( my girlfriend wont let me root her phone, but thatll be the next step if no one can help) but any insight as to what I can do would be appreciated.
Try fastboot flashing recovery and then dirty flashing the rom you were on before you started deleting things. This may help you keep your rom setup. If this doesn't work then go to the moonshine thread run the ruu and start from scratch.
xiastro1ix said:
So, like everyone else, I rooted my phone and decided I dont need all this bloatware and other nonsense system apps.
I was foolish enough not to back up things I were removing, and nothing SEEMED important, but all of the sudden my "Htc dialer": Has stopped working.
My phone will turn on, but I cant turn it off, it just reboots without actually turning the phone off when I hold the power down.
I cant get it into recovery mode ( power vol up) and when it turns on, it goes to the default lock screen the phone comes with, and then I CANT see my home screen at all. The home button doesnt work either.
I cant get to my apps, I have to use my girlfriends DNA to beam whatever app im trying to get to onto my phone.
I can go to settings, but cant factory reset.
I tried killing the battery to get power it off, but then cant get to recovery screen there either.
I'm not sure if anyone has the system apps apk's just laying around so I can attempt to repair my phone, ( my girlfriend wont let me root her phone, but thatll be the next step if no one can help) but any insight as to what I can do would be appreciated.
Click to expand...
Click to collapse
Honestly I don't know where to begin with your post. Its all over the place. The phone turns off by holding the power button for 10 seconds and waiting for the capacitive buttons to stop flashing. If your phone turns on its really not possible for this NOT to work. Yes it will reboot this is normal, though once the lights stop blinking you can quickly hold volume down and power to access boot loader and power down fully from there. Recovery is accessed from bootloader too assuming you have one installed. A lot can be done from both bootloader and recovery to solve problems so finding out if you can access them is the first step. I don't understand your statement about the default lock screen showing and you can't see your home screen. Which ROM is it? Which lock screen are you referring to? Why can't you simply unlock the phone? What is stopping you from doing that? Your home button doesn't work and you can't get to your apps...meaning? You can't access the app drawer? I thought you couldn't unlock the device there is conflicting info there. I don't see how you are beaming tasks one at a time through this painful process but I would just avoid that until you've fixed the problem. You can access settings but no factory reset, why? What can you do from settings? And finally you are asking for some apk's "just lying around".....dude your issues seem severe, obviously you are inhibited from using your phone right now but someone giving you some apps won't solve your problem in fact it would probably make it worse. Get into recovery perform a full wipe and flash a different ROM. Also don't mess with deleting apps if your not sure it might screw up your system.
xlxcrossing said:
Honestly I don't know where to begin with your post. Its all over the place. The phone turns off by holding the power button for 10 seconds and waiting for the capacitive buttons to stop flashing. If your phone turns on its really not possible for this NOT to work. Yes it will reboot this is normal, though once the lights stop blinking you can quickly hold volume down and power to access boot loader and power down fully from there. Recovery is accessed from bootloader too assuming you have one installed. A lot can be done from both bootloader and recovery to solve problems so finding out if you can access them is the first step. I don't understand your statement about the default lock screen showing and you can't see your home screen. Which ROM is it? Which lock screen are you referring to? Why can't you simply unlock the phone? What is stopping you from doing that? Your home button doesn't work and you can't get to your apps...meaning? You can't access the app drawer? I thought you couldn't unlock the device there is conflicting info there. I don't see how you are beaming tasks one at a time through this painful process but I would just avoid that until you've fixed the problem. You can access settings but no factory reset, why? What can you do from settings? And finally you are asking for some apk's "just lying around".....dude your issues seem severe, obviously you are inhibited from using your phone right now but someone giving you some apps won't solve your problem in fact it would probably make it worse. Get into recovery perform a full wipe and flash a different ROM. Also don't mess with deleting apps if your not sure it might screw up your system.
Click to expand...
Click to collapse
Alright let me try to be a little more descriptive.
So as for the lock screen, I can unlock the screen, but then I see a black screen, no home page/icons. I cant get into the app drawer, when i try to factory reset, it says "rebooting" for a few seconds, screen turns off, right back on to lock screen, sim card says preparing, and then i'm back to where i was, doesnt actually reset. As for the beaming, I can say, open system app remover or file viewer on my girlfriends phone, then beam it, and my phone will open the corresponding app. This is the only way I can get apps to open, since I can't get to drawer or go to home screen.
When I hold down the power button down, the buttons flash, I get a message saying " continue to hold for 3 seconds" it counts down to 1, and then nothing. I can hold it til my arm falls off, nothing at all happens when it hits 1, I also can't power the phone down. If i try to, the screen goes black, capactive buttons turn white, back to lock screen and phone does " preparing sim" and the network/wifi reconnect as if it was just rebooted.
I have the default rom the phone came with, I believe I have a bootloader, I used a guide from this site to perform my root. The folder I have contains distiller, dnashellroot.apk, boot_secure, busybox, su and superuser.apk
dude your issues seem severe, obviously you are inhibited from using your phone right now
Click to expand...
Click to collapse
The weird part is, other then not being able to turn it off/get into drawer/see home screen, everything else works. If i get a text, i can drag down and select it and it opens. If i open gmail on my GF's phone and beam it, will open Gmail and function 100%. Same goes for any app we both have that I beam.
I just used my rooting method to force bootloader up, which worked, but when i hit recovery, im looking at a picture of a phone laying down with a orange triangle/exclamation point in the center of it.
xiastro1ix said:
The weird part is, other then not being able to turn it off/get into drawer/see home screen, everything else works. If i get a text, i can drag down and select it and it opens. If i open gmail on my GF's phone and beam it, will open Gmail and function 100%. Same goes for any app we both have that I beam.
I just used my rooting method to force bootloader up, which worked, but when i hit recovery, im looking at a picture of a phone laying down with a orange triangle/exclamation point in the center of it.
Click to expand...
Click to collapse
Ok - fact of the matter is that you might want to try getting into recovery via the bootloader (vol down + power from off). If you can access the recovery module from there, you are then able to click advanced (using TWRP) then click sideload. You will then need to use ADB to sideload a new ROM onto the phone, then install via TWRP. Hopefully you might even still have the old .zip for the current ROM that you're using and just really need to get to recovery.
mushroomhead13xx said:
Ok - fact of the matter is that you might want to try getting into recovery via the bootloader (vol down + power from off). If you can access the recovery module from there, you are then able to click advanced (using TWRP) then click sideload. You will then need to use ADB to sideload a new ROM onto the phone, then install via TWRP. Hopefully you might even still have the old .zip for the current ROM that you're using and just really need to get to recovery.
Click to expand...
Click to collapse
I can get into bootloader, i tried recovery, i get a verizon screen bootloader but just resets phone after a few minutes.
At my friends suggestion i just got TWIP installed and now i'm just waiting to see what she suggests next. I figured out thanks to my advance app killer I can get to the play store whenever i need to, and then open any apps i've installed through there. Stupid work around, but hey, it works lol.
xiastro1ix said:
I can get into bootloader, i tried recovery, i get a verizon screen bootloader but just resets phone after a few minutes.
At my friends suggestion i just got TWIP installed and now i'm just waiting to see what she suggests next. I figured out thanks to my advance app killer I can get to the play store whenever i need to, and then open any apps i've installed through there. Stupid workout, but hey, it works, lol.
Click to expand...
Click to collapse
Well if you just got TWRP installed via fastboot or goo manager you should be pretty well set. Download a new ROM, reboot into recovery and install. I would suggest wiping the davik and cache - possibly even the system just to give you a fresh start.
mushroomhead13xx said:
Ok - fact of the matter is that you might want to try getting into recovery via the bootloader (vol down + power from off). If you can access the recovery module from there, you are then able to click advanced (using TWRP) then click sideload. You will then need to use ADB to sideload a new ROM onto the phone, then install via TWRP. Hopefully you might even still have the old .zip for the current ROM that you're using and just really need to get to recovery.
Click to expand...
Click to collapse
mushroomhead13xx said:
Well if you just got TWRP installed via fastboot or goo manager you should be pretty well set. Download a new ROM, reboot into recovery and install. I would suggest wiping the davik and cache - possibly even the system just to give you a fresh start.
Click to expand...
Click to collapse
So far Ive used goo to get twrp installed and now we are working on getting sense 5 working.
Appreciate all the input, might be getting somewhere finally lol.
xiastro1ix said:
So far Ive used goo to get twrp installed and now we are working on getting sense 5 working.
Appreciate all the input, might be getting somewhere finally lol.
Click to expand...
Click to collapse
I highly suggest NOS M7 Sense 5 Build ( http://forum.xda-developers.com/showthread.php?t=2184706 ) - Absolutely stunning at how well it works. I just switched from that to the GPE port from NOS M7 as well. Good work on getting somewhere, I remember the days of IDK WHAT IM DOING OMG WHAT IS THE ADB ...FASTBOOT..... UGH WHATS WITH THIS VERIFICATION ERROR! lol
mushroomhead13xx said:
I highly suggest NOS M7 Sense 5 Build ( http://forum.xda-developers.com/showthread.php?t=2184706 ) - Absolutely stunning at how well it works. I just switched from that to the GPE port from NOS M7 as well. Good work on getting somewhere, I remember the days of IDK WHAT IM DOING OMG WHAT IS THE ADB ...FASTBOOT..... UGH WHATS WITH THIS VERIFICATION ERROR! lol
Click to expand...
Click to collapse
[ROM] Sense 5 M7 Digital Dream ROM v2.1 7/30/13
Im actually all set, i got the phone up and working on this rom, and now im SAFELY using the list below to delete all the apps I dont want.
http://forum.xda-developers.com/showthread.php?p=34704106
This rom kicks ass, i cant believe i stayed with default rom all this time to begin with, turned a bad situation into a much better one
Love XDA so much, this sites a life saver. The first thing that came into mind when I bricked it was, Yep, time to hit XDA.
xiastro1ix said:
[ROM] Sense 5 M7 Digital Dream ROM v2.1 7/30/13
Im actually all set, i got the phone up and working on this rom, and now im SAFELY using the list below to delete all the apps I dont want.
http://forum.xda-developers.com/showthread.php?p=34704106
This rom kicks ass, i cant believe i stayed with default rom all this time to begin with, turned a bad situation into a much better one
Love XDA so much, this sites a life saver. The first thing that came into mind when I bricked it was, Yep, time to hit XDA.
Click to expand...
Click to collapse
Absolutely! I first started out on XDA when I got my first android phone; MyTouch 3g (HTC Magic). I then took my tinkering to full fledged modding where I was charging to overclock, root and unlock phones. It used to be fairly profitable, now there's one click steps for everything. Glad you were able to figure it out instead of having to take it to someone! Good work!
Before the incident, I had root, no unlocked bootloader, stock JB, v20h.
What had happened was I was trying the Font Installer app in th Play Store because of the added customization that would have been nice.
I found a cool font, and I backed up my current fonts and then pressed install. SuperSU asked for permissions like normal and then my phone restarted.
Then it was so that my phone was stuck at the T-Mobile boot animation after the LG Logo. For about 15 minutes. This is where I believed something was starting to go very wrong. After contemplating for a few extra minutes, I decided to just take out the battery and restart. Same outcome. I thought of all the things that were on the phone thus far because I had just gotten it recently, and decided that it wouldn't hurt me to just do a hard reset by pressing home + vol down + power. Everything went smoothly. Except for the fact that even after I did that, it was leaving me at the T-Mobile screen.
I decided to look on the forums for development and tried to do the unbrick method, to no avail after about 3 hours now. I used the LG User Support Tool and since I hadn't updated to V20f, I decided to do that to see if it would solve my problem. It still didn't, and I'll be honest, I'm a little upset just typing this right now.
I also tried the Upgrade Recovery option and it warmed my heart to see that the process was actually starting. But right at the screen where it says that it is supposed to be downloading something, it freezes up and nothing happens no matter how long I wait. I saw somewhere that it should be a glowing red bar, but I do not see that anywhere, it is just frozen, saying Time Elapsed: 00:12. And before anyone asks, yes, I ran absolutely everything as an administrator.
Is there any possible way to bring this phone back? Any help would be immensely appreciated. Thank you in advanced.
anticlotto_ said:
Before the incident, I had root, no unlocked bootloader, stock JB, v20h.
What had happened was I was trying the Font Installer app in th Play Store because of the added customization that would have been nice.
I found a cool font, and I backed up my current fonts and then pressed install. SuperSU asked for permissions like normal and then my phone restarted.
Then it was so that my phone was stuck at the T-Mobile boot animation after the LG Logo. For about 15 minutes. This is where I believed something was starting to go very wrong. After contemplating for a few extra minutes, I decided to just take out the battery and restart. Same outcome. I thought of all the things that were on the phone thus far because I had just gotten it recently, and decided that it wouldn't hurt me to just do a hard reset by pressing home + vol down + power. Everything went smoothly. Except for the fact that even after I did that, it was leaving me at the T-Mobile screen.
I decided to look on the forums for development and tried to do the unbrick method, to no avail after about 3 hours now. I used the LG User Support Tool and since I hadn't updated to V20f, I decided to do that to see if it would solve my problem. It still didn't, and I'll be honest, I'm a little upset just typing this right now.
I also tried the Upgrade Recovery option and it warmed my heart to see that the process was actually starting. But right at the screen where it says that it is supposed to be downloading something, it freezes up and nothing happens no matter how long I wait. I saw somewhere that it should be a glowing red bar, but I do not see that anywhere, it is just frozen, saying Time Elapsed: 00:12. And before anyone asks, yes, I ran absolutely everything as an administrator.
Is there any possible way to bring this phone back? Any help would be immensely appreciated. Thank you in advanced.
Click to expand...
Click to collapse
did you hard reset? then turn off your phone disconnect the battery, connect to the pc holding the volume up button? then try the Update Recovery?
i would just go through that process over and over until it works, theres not really a way to brick this phone i've heard...
CROSSFREEZE said:
did you hard reset? then turn off your phone disconnect the battery, connect to the pc holding the volume up button? then try the Update Recovery?
i would just go through that process over and over until it works, theres not really a way to brick this phone i've heard...
Click to expand...
Click to collapse
Thank you for your reply! I have tried hard resetting multiple times, but I had removed some bloatware apps (I will quarantine them next time instead because I don't wanna go through this ever again) and I have tried the kdz method to only be stuck at 15% every time when I followed instructions to the pixel. I have tried to do it on windows 7 and windows 8. I have also tried the fastboot method by lelus, and that manages to "work" but I am still stuck at the tmobile boot screen afterwards. I have gotten the hang of the process of getting into the fastboot, but what do I do from there? I chose to flash ics xloader and uboot, but the process goes by so fast, I'm not even sure it is doing anything. The LG Tool has really gotten me nowhere, it just gives me a lovely error and then cannot continue the upgrade recovery process.
It said somewhere that after I flash through the fastboot I then have to try the kdz method, so I am going to do that now and see if it works. I don't know if there would be a difference between flashing a jb kdz or an ics kdz, but I will just do ics to be on the safe side.
I am quite happy to say that flashing the ics kdz was successful, and my phone is now up and running.
My p769BK is stuck on the LG screen. /: months
Sent from my LG-MS770 using xda app-developers app
im terrible with fastboot, i used the unlock the bootloader for noobs with an offline flash.
heres what i did to get out of bootloops....
alright, this is all from memory but the offline flash didnt work as well for me when stuck in weird bootloops.
Step one-going back to online flash---->
A---
the easiest way i found was to go to C:/windows/system32/drivers/ect/hosts
right click>open with notepad
there should be two lines at the bottom
"127.0.0.1 csmg.lgmobile.com
127.0.0.1 csmgdl.lgmobile.com"
i would cut them out and paste them in a text doc in the same folder for reference later...
but either way you should remove them from the hosts file and save
B----
Make sure your small server is closed! once you minimize it it should go down to your status bar (shttps)
Step two-LGMS---->
make sure you have LG mobile support installed or install it.
open lg mobile support
install needed drivers for your phone
power your phone off/remove the battery
put battery back in
connect it to your computer holding down the volume up button
S/W UPDATE mode should pop up, if it doesn't preform and hardreset and try again til it works (it will)
then in the top right corner there should be a button or two click them both until you see
"restore update" or Update restore or something to that effect
select that
and let it ride man
i got my phone ****ed many times and just had to keep redoing this until it worked. if your bootloader is truely unlocked you can probably go through all that again and get CM10 working, i did but im still working through kinks.....
GOOD LUCK feel free to ask any more Q's about this process if you run into any problems
Alright. I need some advice one last time, I swear... after this I'm not going to try to do anything.
Phone worked quite well for 2 days. I was enjoying this rom quite a bit. I decided to change the DPI down to 560. I saw that some others in this thread had done so quite easily... so I used this app to change it. Made the change to 560, granted supersu permission and rebooted. Only problem is that... the phone has yet to turn back on. At the moment the only thing I can get it to do is give me a screen that shows a large white empty battery with a cable leading up to it and a hazard exclamation mark in the bottom right when I am trying to put it in download mode. I have tried on multiple computers to restore back to stock following these directions. The best that happens is my computer recognizes an unrecognized device. No luck.
I would love to change the buildprop back or anything, but not even adb recognizes the device.
Otherwise, nothing. I can't get into recovery. I can't get the phone to start at all. All black screen. I can't get any reaction out of it. Any advice would be helpful, I'm on hour two of this. I realize that this is most likely not a problem with the rom, but wanted to see if anyone else had an issue and has advice/let anyone else who's thinking of changing the DPI and shared my troubles reconsider.
Thanks again!
The empty the battery logo is because the phone is dead try charging it for like 30 mins. Also it seems that app you used is 3 years old so it does not support lollipop or even kitkat. After charging it try get it into recovery and restore a backup. If you don't have a backup try wiping your data and cache.
1619415 said:
The empty the battery logo is because the phone is dead try charging it for like 30 mins. Also it seems that app you used is 3 years old so it does not support lollipop or even kitkat. After charging it try get it into recovery and restore a backup. If you don't have a backup try wiping your data and cache.
Click to expand...
Click to collapse
Thanks for the reply!
That emblem only shows up when the battery is removed and I'm trying to put the phone in download mode. So it makes sense. Any other ideas? The battery that I'm using is about 80% full. I still can't find a way to recovery mode.
What other information can I provide to help you out?
Well when your in download mode it does not take any commands can you get the lg powered by android screen? Or just nothing happens? If nothing at all happenes it is most likly bricked. If it boots to the lg screen it is most likly soft bricked.
Bricked- Phone is dead and very very hard to fix if there is a fix
Soft Brick- No OS so you have to reinstall a rom could also be, because of apps.
1619415 said:
Well when your in download mode it does not take any commands can you get the lg powered by android screen? Or just nothing happens? If nothing at all happenes it is most likly bricked. If it boots to the lg screen it is most likly soft bricked.
Bricked- Phone is dead and very very hard to fix if there is a fix
Soft Brick- No OS so you have to reinstall a rom could also be, because of apps.
Click to expand...
Click to collapse
No screen. For anything (other than described).
This is exactly what I was afraid of, but my phone has always been odd. This dead battery screen has always shown up in download mode... even when my phone worked, I've never had the firmware update screen. Which has always been weird to me.
However, the only time my phone shows anything is with the dead battery screen. During such it will show up as an unrecognized device when attached to a computer, again... it's always done this. I was just curious if there was something else or a suggestion that someone more experienced then myself might have.
No that I read it, it sounds like there maybe a very slim chance of getting your device to work. If you mange to get some drivers for the unreconized device driver you maybe able to send adb and fastboot commands. I found this one tool (will limk below) that is call cydia impactor I found in one of rootjunky's toolkit files. I used this one function that was able to make drivers for my sony smartwatch 3 and phone. I will link for the direct download make sure to extract the zip. Inside of the zip you will find another zip called "Impactor_0.9.14.zip" make sure to extract it to it's own folder. If you want you can delete the first folder juat save the impactor folder. Then run the program called "Impactor" can connect your phone to the computer and click on the tab called "USB" then click the button called "Driver Scan". Follow any on screen instructions. It should now generate a driver for your phone if all went well and it will be reconized. Then you should be able to run adb reboot recovery or fastboot reboot-bootloader. The fact that your computer is even seeing the phone tells me that it has so hope of being fixed because your computer see's it. Your device might be in a bootloop of some sort. You may just have no os installed and it may have just glitched.
Download: http://rootjunkysdl.com/getdownload.php?file=Tegra Note 7/ADB root.zip (will immeditly download it)
Worst case scenario, you may try this, or at least read it for general info. I don't think you'll have to go this far though
http://forum.xda-developers.com/showthread.php?t=2582142
[FIX] NO Recovery mode, No download mode, after OTA on rooted LG G2
i changed my dpi once and it bootlooped on me. i was lucky enough to get into recovery and then i restored the data partition from an older nandroid.
i agree with 16. it does sound like the drivers may not be loaded up properly if your computer recognizes a device. have you tried the official lg drivers?
What system are you guys running?
Well, I've found out that for whatever reason... on my phone I have to take out the battery for a period of ~5-10 mins on any change DPI, system rom update, anything. Otherwise, my phone will not turn on. So if someone else find this, give it a try.
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?
I have a pixel 6a that I successfully rooted but when I tried to unroot it something went wrong. When I restarted the phone I got a message saying
Your device is corrupt. It can’t be trusted and may not work properly.” then it was stuck on the Google logo. I managed to get it unstuck but then when it restarted I got the error message again and it shut off. Now the phone will not turn on at all. I tried charging it for hours. I tried forcing it to turn on with every ossible button configuration I could think of. It is completely unresponsive. Please help. I literally just reviewed it from Google Fi a week ago
Cheesymatt661 said:
I have a pixel 6a that I successfully rooted but when I tried to unroot it something went wrong. When I restarted the phone I got a message saying
Your device is corrupt. It can’t be trusted and may not work properly.” then it was stuck on the Google logo. I managed to get it unstuck but then when it restarted I got the error message again and it shut off. Now the phone will not turn on at all. I tried charging it for hours. I tried forcing it to turn on with every ossible button configuration I could think of. It is completely unresponsive. Please help. I literally just reviewed it from Google Fi a week ago
Click to expand...
Click to collapse
Are you on A13?
Did you have, at the minimum, the A13 bootloader on both slots?
What method did you use to uninstall Magisk?
What happens when you connect phone to computer?
Will Android Flash Tool recognize it? If so, use that to flash back to stock.
Try holding the power button down for at least 30 seconds?
If you were on A13 and didn't have the A13 bootloader on both slots, when bootlooping your phone may have reverted to the A12 slot. If so, your device may be a brick due to the new ARB and you should probably RMA it.
Yes it was A13. And nothing happens when I connect it to my laptop. And I'm not sure what you mean by "both slots". My apologies... This is my very first time rooting and trying to unroot a device
I am also using Linux. So I don't really know what other tools I could or should try other than sdk platform tools.
Cheesymatt661 said:
Yes it was A13. And nothing happens when I connect it to my laptop. And I'm not sure what you mean by "both slots". My apologies... This is my very first time rooting and trying to unroot a device
Click to expand...
Click to collapse
Did you do this after updating to A13?
It's a hard brick as per the link in the above post.
But why root, then unroot?
What steps did you take?
It would be helpful to others to find out where you went wrong.
Cheesymatt661 said:
I have a pixel 6a that I successfully rooted but when I tried to unroot it something went wrong. When I restarted the phone I got a message saying
Your device is corrupt. It can’t be trusted and may not work properly.” then it was stuck on the Google logo. I managed to get it unstuck but then when it restarted I got the error message again and it shut off. Now the phone will not turn on at all. I tried charging it for hours. I tried forcing it to turn on with every ossible button configuration I could think of. It is completely unresponsive. Please help. I literally just reviewed it from Google Fi a week ago
Click to expand...
Click to collapse
Why not post this in Pixel 6a forum?
@Cheesymatt661 Okay so you have unlocked bootaloder + fastboot is working right? One of my friend also faced this and what he did was flashed latest (A13) factory images to both A & B slots separately and that's it. It was simple as that for him.