Related
I am pretty sure I know the answer but want to make sure its true as its a costly issue: I did some searching and found a lot of threads with different options over the last few years, so just want to confirm; I have:
Asus Transformer Prime TF201, unlocked with latest ICS official (WW) installed via SD Card
I was intending on giving the tablet away to a family member, so decided to factory reset the device. I went to the PWR+VOL Down menu, and selected wipe which I read was the way to perform a factor reset. After a long time of this process, the tablet powered off (was plugged into mains with full batteries). I powered on by pressing PWR button some time later. Now the tablet just boots onto the screen that states "The device is UnLocked" in the top left, ASUS in the middle (and some lies about perfection), and the bottom right "Powered by Nvidia TEGRA".
If I power on:
1. PWR + VOL Down, nothing happens, it boots to the same screen, no menu
2. PWS + VOL UP, the screen is black, the tablet vibrates and if i have it plugged into a PC it detects it in APX mode.
I've tried a full power cycle, and read about the nvflash tool. I unfortunately have no nvflash backups, I'm not sure that tool was around when I unlocked the tablet, and as i'd not been flashing any custom roms (although I had intended) I'd not seen that tool before.
As I understand the state of affairs is:
1. Somehow the bootloader is jiggered, i guess the wipe didn't work right
2. APX is useless if you don't have some backups created with a tool
3. The only current solution is to send it to ASUS and pay almost exactly the same price as a new tablet costs
Is there any other options I can do with an unlocked tablet and only access to APX?
Any likelihood that there is anything that can be done with nvflash in the future without needing a custom backup that is unique per tablet?
I have exactly the same problem please someone help us :angel:
virus4o said:
I have exactly the same problem please someone help us :angel:
Click to expand...
Click to collapse
I have the same problem too. Only apx.
Please, Anyone knows any solution for this issue?
Same problem while flashing CM
Aduniel said:
I have the same problem too. Only apx.
Please, Anyone knows any solution for this issue?
Click to expand...
Click to collapse
My tf is in the same state. Got there when trying to install CM's nightly build.
Bricked TF201 - Stuck in bootscreen
I have the exact same problem. :crying:
Please, I know that there are many brilliant minds in this forum, help us n00bs get out of this mess and lead us into the light. Oh, and bump this thread
I hate to be the bearer of bad news, but I hate hit and run thread posters so I will provide an update.
I am afraid that my tablet was bricked. No way back from that state after reading the entire internet. I have purchased a replacement motherboard, popped open the case and replaced this. After replacing the motherboard, I now have a working tablet. I wish someone would have documented the NVFlash process requirements previously, but that's the risk of following guides on android sites I guess.
So to summarise the initial post, if you are in that state, at current and likely forever, you are hardbricked and the tablet can not be recovered in that states without a previous backup. The only way for it to be repaired is to send it to Asus who have a database of firmware, etc. and will charge you for repairs (~200€), or to go on ebay and purchase this motherboard:
0K0AMBA000
This will cost you ~80€ + shipping, and you must be comfortable working with electronics. Its mostly very clear when you pop off the case, everything has its place. You will need some plastic case pries and a small screw driver.
spudthedestroyer said:
I hate to be the bearer of bad news, but I hate hit and run thread posters so I will provide an update.
I am afraid that my tablet was bricked. No way back from that state after reading the entire internet. I have purchased a replacement motherboard, popped open the case and replaced this. After replacing the motherboard, I now have a working tablet. I wish someone would have documented the NVFlash process requirements previously, but that's the risk of following guides on android sites I guess.
So to summarise the initial post, if you are in that state, at current and likely forever, you are hardbricked and the tablet can not be recovered in that states without a previous backup. The only way for it to be repaired is to send it to Asus who have a database of firmware, etc. and will charge you for repairs (~200€), or to go on ebay and purchase this motherboard:
0K0AMBA000
This will cost you ~80€ + shipping, and you must be comfortable working with electronics. Its mostly very clear when you pop off the case, everything has its place. You will need some plastic case pries and a small screw driver.
Click to expand...
Click to collapse
This sucks, I did the same exact thing last night factory resetting it to give it to my brother. I still don't understand what exactly I did wrong as I've factory reset this thing before. I had CM on it before but have been using the stock rooted ROM & recovery for the past 6+ months.
bricked?
I've been scouring that internet and haven't been able to find a case exactly like mine, but most are similar. From what I can remember (it's been months since I initially 'bricked' it), I was upgrading a cm nightly and did the data/cache/dalvik wipe like the instructions said and I became stuck in a bootloop after leaving recovery. When I tried volume-down and power, I was left with the original 3 options and after some reboots and shutdowns I ended up doing a factory data wipe. From there, when I rebooted the phone I was left with just 'Wipe Data' and 'Fastboot.' Wipe data does nothing more and when I choose fastboot I am left a message 'Starting fastboot usb download protocol' which never changes.
I have tried to push TWRP onto the device but I can't get into recovery (unless I'm doing something wrong of course). Sorry if I missed a duplicate of my post somewhere on here, but if so can someone at least point me in the right direction? Thanks!
i.imgur.com/LEHNREw.jpg
try another ROM
This has worked for me everytime, possibly due to dud bootloader install or some other thing: so long as I was able to recover to CWM with pwr+vol down, I installed virtuous prime rom. This rom was on sdcard already, not sure if you can get from adb if machine in this state. Anyhow, this virtuous prime rom replaced the booting sequence, restored OS and machine worked again.
Asus TF201 stuck on Asus Logo
My Asus Tablet was slow while browsing, and it had JB 4.1.1 with stock rom, so i tried to unlock the device, which was successful and was planning to push the CM11 Kit Kat. I booted in to recovery mode as i could see the 4 icons and then tried to do wipe data/factory reset and then it rebooted and got stuck on the asus logo and at the right bottow with the message powered by NVIDIA Tegra. I tried all the options to get into recovery and also downloaded drivers on my laptop for APX, but no luck at all. What are my options or if any one was successful to get it fixed. Appreciate any help here from smart guys out there. Thanks
spudthedestroyer said:
I am pretty sure I know the answer but want to make sure its true as its a costly issue: I did some searching and found a lot of threads with different options over the last few years, so just want to confirm; I have:
Asus Transformer Prime TF201, unlocked with latest ICS official (WW) installed via SD Card
I was intending on giving the tablet away to a family member, so decided to factory reset the device. I went to the PWR+VOL Down menu, and selected wipe which I read was the way to perform a factor reset. After a long time of this process, the tablet powered off (was plugged into mains with full batteries). I powered on by pressing PWR button some time later. Now the tablet just boots onto the screen that states "The device is UnLocked" in the top left, ASUS in the middle (and some lies about perfection), and the bottom right "Powered by Nvidia TEGRA".
If I power on:
1. PWR + VOL Down, nothing happens, it boots to the same screen, no menu
2. PWS + VOL UP, the screen is black, the tablet vibrates and if i have it plugged into a PC it detects it in APX mode.
I've tried a full power cycle, and read about the nvflash tool. I unfortunately have no nvflash backups, I'm not sure that tool was around when I unlocked the tablet, and as i'd not been flashing any custom roms (although I had intended) I'd not seen that tool before.
As I understand the state of affairs is:
1. Somehow the bootloader is jiggered, i guess the wipe didn't work right
2. APX is useless if you don't have some backups created with a tool
3. The only current solution is to send it to ASUS and pay almost exactly the same price as a new tablet costs
Is there any other options I can do with an unlocked tablet and only access to APX?
Any likelihood that there is anything that can be done with nvflash in the future without needing a custom backup that is unique per tablet?
Click to expand...
Click to collapse
I had messrd up my tf101 with cm nightly to. I did manage to get it working again with adb tool of sorts. When im home i will tr y to find it on my comp. Th
Good evening all, my apologies in advance if i am asking a stupid or already answered question,
i have looked through this forum and many others along side through google and i am unable to find a solution or solved post in regards to fixing this phone.
I recently purchased a second hand s2 from ebay, not the best move but it was cheap, and i was in need of a phone.
the phone came with damaged screen, so i ordered a replacement and thought no more.
after receiving the screen i replaced it fitted it and was in the belief that the phone would be up and running, no no no this is not the case...
upon fitting the screen i found that the phone would lag as such, as if two fingers were placed on the screen, with motions being very sticky also requiring a large amount of force to respond when trying to use it. normal androids will switch between home screens effortlessly and relatively fluid.
Seeing this issue i thought a simple firmware upgrade would suffice and id have a usable phone. upon upgrading via kies i was unable to install the MTP drivers and so switched to the program odin for the update.
i downloaded what i believe to be uk firmware from samsung-updates,
firmware I9100XWMS2_I9100BULS3_I9100VODLSF_HOME
which has also caused the phone to boot in what looks to be spanish. although e3 and cwm show in english.
after the update the phone seems to be in a soft bricked state, the phone will repsond to input from soft keys, go into recovery and download mode accept all firmwares i have tried 9 times out of 10. but when reaching the android home screen is completely frozen, no response from touch or soft keys, except only for volume up and power to reset the device.
thinking the recently purchased LCD was the culprit i have sent it back and had a replacement, still the issue is present.
I have tried many different roms/kernels in the hope to solve this problem and i am at my wits end!
any help in bringing this thing back to life would be of great help as i am without a phone, or enough money to replace it again...
thanks for any response
cheers Ansell2k12
Hopper8's 'Odin troubleshooting' thread stickied in the General section; in particular flashing the 3 part firmware (this will wipe your phone). Also try everything in that thread for as long as you have the patience for it. These cases tend to be fixed by perseverance, or not at all. There's no easy fix. It's either a hardware issue(s), NAND corruption, or something really obvious being missed here. If it's the latter, hopefully the stuff in Hopper's thread helps you fix it. If it's either of the other two, I'd be cutting my losses.
Ansell2k12 said:
Good evening all, my apologies in advance if i am asking a stupid or already answered question,
i have looked through this forum and many others along side through google and i am unable to find a solution or solved post in regards to fixing this phone.
I recently purchased a second hand s2 from ebay, not the best move but it was cheap, and i was in need of a phone.
the phone came with damaged screen, so i ordered a replacement and thought no more.
after receiving the screen i replaced it fitted it and was in the belief that the phone would be up and running, no no no this is not the case...
upon fitting the screen i found that the phone would lag as such, as if two fingers were placed on the screen, with motions being very sticky also requiring a large amount of force to respond when trying to use it. normal androids will switch between home screens effortlessly and relatively fluid.
Seeing this issue i thought a simple firmware upgrade would suffice and id have a usable phone. upon upgrading via kies i was unable to install the MTP drivers and so switched to the program odin for the update.
i downloaded what i believe to be uk firmware from samsung-updates,
firmware I9100XWMS2_I9100BULS3_I9100VODLSF_HOME
which has also caused the phone to boot in what looks to be spanish. although e3 and cwm show in english.
after the update the phone seems to be in a soft bricked state, the phone will repsond to input from soft keys, go into recovery and download mode accept all firmwares i have tried 9 times out of 10. but when reaching the android home screen is completely frozen, no response from touch or soft keys, except only for volume up and power to reset the device.
thinking the recently purchased LCD was the culprit i have sent it back and had a replacement, still the issue is present.
I have tried many different roms/kernels in the hope to solve this problem and i am at my wits end!
any help in bringing this thing back to life would be of great help as i am without a phone, or enough money to replace it again...
thanks for any response
cheers Ansell2k12
Click to expand...
Click to collapse
lcd may be the culprit but also the firmware is crashed flash it again properly after a factory reset from e3
Progress...but not as id hoped...
first off thanks to you mistahbungle & bhavstech,
unfortunately im only little further forward.
After the flash using 3 part file firmware the phone is now running in English language on an updated firmware, but still appears to be frozen/ crashed.
updates on appearance, maybe its still salvageable?
Clock now updates after reboot
English language
charge icon does not change when unplugging/replugging charger/data cable but is recognized by the PC - MTP is now installing, but requires reboot, after reboot of the PC, MTP installs again and request reboot again... and continues to do so.
clock doesn't update at home screen, again appears to be frozen/crashed
still no response to touch, touch buttons or soft keys - only phone rest volume up and power.
when phone is at samsung splash screen i get notification of voice mails/texts on the phone.
Thanks again Ansell2k12
Ansell2k12 said:
first off thanks to you mistahbungle & bhavstech,
unfortunately im only little further forward.
After the flash using 3 part file firmware the phone is now running in English language on an updated firmware, but still appears to be frozen/ crashed.
updates on appearance, maybe its still salvageable?
Clock now updates after reboot
English language
charge icon does not change when unplugging/replugging charger/data cable but is recognized by the PC - MTP is now installing, but requires reboot, after reboot of the PC, MTP installs again and request reboot again... and continues to do so.
clock doesn't update at home screen, again appears to be frozen/crashed
still no response to touch, touch buttons or soft keys - only phone rest volume up and power.
when phone is at samsung splash screen i get notification of voice mails/texts on the phone.
Thanks again Ansell2k12
Click to expand...
Click to collapse
Your issue of a semi frozen state is very familiar to me but the reasons can be many and one of those are the /sdcard partition not mounting properly and likewise it could also be a failure of the other major partitions but if the device booted and made it to the lockscreen then you may have some hope, first if you have a external card plugged try booting without it, if the issues repeat try swapping the ext card with the internal /sdcard by flashing a modified vold.fstab file for your firmware which swaps the partitions effectively making the device mount the ext card as the /sdcard partition. I am expecting you have gone through the default troubleshooting methods like a clean flash etc.
Sent from my GT-I9100 using Tapatalk
king_below_my_lord said:
Your issue of a semi frozen state is very familiar to me but the reasons can be many and one of those are the /sdcard partition not mounting properly and likewise it could also be a failure of the other major partitions but if the device booted and made it to the lockscreen then you may have some hope, first if you have a external card plugged try booting without it, if the issues repeat try swapping the ext card with the internal /sdcard by flashing a modified vold.fstab file for your firmware which swaps the partitions effectively making the device mount the ext card as the /sdcard partition. I am expecting you have gone through the default troubleshooting methods like a clean flash etc.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Yes i have done multiple flashes, tried another sd card as the original was unreadable by the phone but picked up the second faultlessly, although flashing a custom firmware failed when trying to load in cwm.
as for a modified vold.fstab file,this is new to me. Could i ask how its modified or where i would get the file? im guessing id use odin to flash it to the device?
thanks for the response
Ansell2k12
Ansell2k12 said:
Yes i have done multiple flashes, tried another sd card as the original was unreadable by the phone but picked up the second faultlessly, although flashing a custom firmware failed when trying to load in cwm.
as for a modified vold.fstab file,this is new to me. Could i ask how its modified or where i would get the file? im guessing id use odin to flash it to the device?
thanks for the response
Ansell2k12
Click to expand...
Click to collapse
There are some threads in which I myself detailed about swapping memory its done via a custom recovery and not using Odin.
Sent from my GT-I9100 using Tapatalk
??
king_below_my_lord said:
There are some threads in which I myself detailed about swapping memory its done via a custom recovery and not using Odin.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
any chance you could point n the right direction?
i have had a look at the stuff to edit vold, and it seems i am unable to do so as my phone isnt usable once booted
cheers Ansell2k12
Phone has gone in the bin cheers guys, thanks for the help
....
You could easily flash a edited vold.fstab file by generating a flashable zip file. That's why I said via recovery or if you are clever enough you can easily use recovery flashable Aroma file manager to overwrite the file.
Sent from my GT-I9100 using Tapatalk
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?
Hello,
Explain my experience with the BQ E6 (more info bq.com/es/support/aquaris-e6/support-sheet)
You need to be root to use an application, I did this with the following procedure provided by the manufacturer, installing a Recovery custom:
mibqyyo.com/comunidad/discussion/37470/recovery-custom-y-root-e6/p1
At the end of the process received an error "PMT changed for rom, must be downloaded" and no longer started android, it was constantly restarting.
I tried to reinstall the recovery but get the same error.
I looked for another solution, to make a Hard Reset and to reinstall all the firmware according to these indications of the manufacturer:
mibqyyo.com/articulos/2014/06/04/hard-reset-smartphone-gama-aquaris-e/
The procedure I did without problems and then started the mobile with the factory parameters, I configured some things and left, after a while I wanted to continue but the mobile was off. When I started it again it was on the white screen of BQ and it did not start.
I went back to make a Hard Reset in case I had done something wrong, the whole process was correct and then started the system again, I configured some parameters but after a while it was the same, turned off and it did not start.
I repeated the Hard Reset a third time, but after 20 seconds of starting it goes off.
Commenting that a forum partner told me that when connecting the mobile to the usb to start the copy from Flash Tools did so by pressing the + button of the volume (without getting better result).
I installed another recovery (TWRP) and other rooms (CyanogenMod13 / Miui-7), everything installs correctly but in all cases within 20 seconds of starting it goes off.
The TWRP recovery is accessed correctly and for a long time you use it does not shut down, it is when android starts.
Has anyone ever had something similar and know what I can do?
Thank you very much
jucuegas said:
Hello,
Explain my experience with the BQ E6 (more info bq.com/es/support/aquaris-e6/support-sheet)
You need to be root to use an application, I did this with the following procedure provided by the manufacturer, installing a Recovery custom:
mibqyyo.com/comunidad/discussion/37470/recovery-custom-y-root-e6/p1
At the end of the process received an error "PMT changed for rom, must be downloaded" and no longer started android, it was constantly restarting.
I tried to reinstall the recovery but get the same error.
I looked for another solution, to make a Hard Reset and to reinstall all the firmware according to these indications of the manufacturer:
mibqyyo.com/articulos/2014/06/04/hard-reset-smartphone-gama-aquaris-e/
The procedure I did without problems and then started the mobile with the factory parameters, I configured some things and left, after a while I wanted to continue but the mobile was off. When I started it again it was on the white screen of BQ and it did not start.
I went back to make a Hard Reset in case I had done something wrong, the whole process was correct and then started the system again, I configured some parameters but after a while it was the same, turned off and it did not start.
I repeated the Hard Reset a third time, but after 20 seconds of starting it goes off.
Commenting that a forum partner told me that when connecting the mobile to the usb to start the copy from Flash Tools did so by pressing the + button of the volume (without getting better result).
I installed another recovery (TWRP) and other rooms (CyanogenMod13 / Miui-7), everything installs correctly but in all cases within 20 seconds of starting it goes off.
The TWRP recovery is accessed correctly and for a long time you use it does not shut down, it is when android starts.
Has anyone ever had something similar and know what I can do?
Thank you very much
Click to expand...
Click to collapse
Wysłane z mojego HUAWEI CUN-L21 przy użyciu Tapatalka
Hello,
After a week I have good news,
I omitted content because I thought it was not relevant, but it was.
I recently broke the screen and I changed it.
Everything worked fine, but in the process the camera was damaged and only focused on infinity.
It seems that the problem was bigger and it was the fault that caused not being able to start the system.
Start the cell with the power and volume (-) button, then I entered the test menu and I passed the test, until I got to the camera and then suddenly the cell phone turned off.
I opened the phone and I removed the camera and now starting normally.
Many thanks to those who have interested you and those who can serve you in the future, although it is rare that damage the camera.
How u fix ur BQ E6 ? What firmware u flash ?
plzz help me
BQ E6 flash
zazi1991ix said:
Wysłane z mojego HUAWEI CUN-L21 przy użyciu Tapatalka
Click to expand...
Click to collapse
Hello,
it's been some years ago now, but do you still have the instructions from page mibqyyo.com/articulos/2014/06/04/hard-reset-smartphone-gama-aquaris-e/
to install a different ROM? That page isn't available anymore.
Hello, i am new here and i came in here for help.
It all started when i blindly flashed twrp v2.6.0.0 on my tablet, and now i regret that i have done that.
The problem is that it is stuck in a bootloader boot loop and the screen does not work at all when i am at the menu. The os is gone and i can't even go into download mode because the tablet does not have physical volume buttons.
The tablet is an estar mid 7818 mini (rebranded onda v818 mini).
Is there anything i can do? This is my last resort since i am tired of trying to find a solution to this rare problem.
edit:
The os is not gone, as it seems that the thing still has the default battery charging screen while being off, but it don't know anymore. I am no stranger to rooting and flashing, but that was mainly done on Samsung phones, which have much better support than some random chinese tablets.
I still need help, though :^(
Cheers if you read my mess.
edit v2:
I actually fixed it! So this is what i did:
1. found a thread on a different forumsuggesting that i should use iroot to download the drivers (because the device was not recognised by any software);
2. rommaster was installed with me not even knowing;
3. I pressed some buttons and the tablet rebooted to android (the ui was in chinese)'
And with my blind luck - i somehow fixed it.
Hopefully i will not end up in this mess again.
Cheers.