Related
i've seen numerous posts about this all over the place and couldn't find a fix anywhere
after providing logs to jcsullins he managed to solve my issue and now have a fully working TP again
heres the thread i created over at rootzwiki http://rootzwiki.com/topic/37804-battery-question-mark-issue/
and heres the link to the irc post for jcsullins to guide people through it
only created this here as i know a lot don't go on rootzwiki but many have this issue
http://rootzwiki.com/topic/36658-tpdebrick-v01/page__st__310#entry1068329
hopefully this will help someone out and resurrect your thought to be dead TP
I noticed the links in this post doesn't really lead you to the debrick guide, so I am writing this.
P.S. I am ONLY reporting my experience as is to my HP Touchpad 16GB running CM-tenderloin. I am not in any way responsible for developing this method nor am I responsible for any extra damage that might happen to your already problematic Touchpad. Good luck, and research is your best friend.
I got this question mark battery problem as well and after doing some research I thought my HP Touchpad was gone for good. Then I saw this post and after reading it it inspired me to try the tpdebrick made my jcsullins. And... it worked and my touchpad is back to normal (with everything data intact as well, to my surprise!). My problem was similar to described by other posts in this forum: the touchpad was discharged until it turned off, and then it was left that way for a long time, and when I tried to charge again, it would first give me a flashing home button and then the battery with a question mark after a long time of charging. No matter how long I charged the problem persist, and the device refuses to go into recovery mode no matter what I do. WebOS is unable to detect the device as well, but the PC was able to recognize it as Palm or UQSB something something something (I forgot what it was). After this problem I did not do any battery change or hardware changes. Just me, the question mark battery, and the tpdebrick buigde by jcsullins.
So if you have this problem and absolutely cannot get into the recovery mode, give tpdebrick a try. I used tpdebrick-v004 by jcsullins: rootzwiki.com/topic/38786-tpdebrick-v004
Follow through the steps in that post and it should be okay. But, in case anyone needs it, this is all the steps I did:
0) While my screen was displaying the question mark battery, I pressed Power + Home + Vol Up + Vol Down for 30 seconds while USB plugged into PC to make sure everything turns off (i.e. black screen, no flashing home button). This step may or may not be necessary since part of the debrick process you need to do Power + Home + Vol Down, and it will most likely do the same thing. But just in case.
1) downloaded Ubuntu 12.04 32bit, downloaded webOS 3.0.5 doctor (this was in zip format, and I had to change it to .jar extension), and downloaded tpdebrick-v004.zip from the link above. You can download webOS doctor and tpdebrick in Ubuntu so that you can follow the instruction as written without any trouble, but I did it in my Windows and I fetched it from the Windows storage in Ubuntu. Whichever is easier for you.
2) Downloaded Universal USB Installer and made a bootable USB of Ubuntu. Followed instruction here: ubuntu.com/download/help/create-a-usb-stick-on-windows
3. Boot from USB and run Ubuntu OS
4. Found and moved the tpdebrick.zip and webos jar into the Ubuntu OS Downloads folder
5. Followed steps 14 to 23 from the debrick instruction by JC above. (Basically run terminal, unzip tpdebrick-v004.zip, and hold power + home + vol down for 30 seconds, and run script, and then run "sudo ./tpdebrick XX" where XX = size of your touchpad)
6. Wait patiently for 5 - 10 minutes, and then it says All Done. By this point, my HP touchpad rebooted back to the original state. If this does not happen for you, then you might need to keep researching! Good luck!
NOTE: After the process, my touchpad rebooted back into CM, and I noticed the battery was fully charged. So, obviously there was no problem with the battery nor the charging process. My problem must be due to miscommunication with the battery status.
Thanks
Thanks, it helped me a lot!
jackygogo said:
I noticed the links in this post doesn't really lead you to the debrick guide, so I am writing this.
P.S. I am ONLY reporting my experience as is to my HP Touchpad 16GB running CM-tenderloin. I am not in any way responsible for developing this method nor am I responsible for any extra damage that might happen to your already problematic Touchpad. Good luck, and research is your best friend.
I got this question mark battery problem as well and after doing some research I thought my HP Touchpad was gone for good. Then I saw this post and after reading it it inspired me to try the tpdebrick made my jcsullins. And... it worked and my touchpad is back to normal (with everything data intact as well, to my surprise!). My problem was similar to described by other posts in this forum: the touchpad was discharged until it turned off, and then it was left that way for a long time, and when I tried to charge again, it would first give me a flashing home button and then the battery with a question mark after a long time of charging. No matter how long I charged the problem persist, and the device refuses to go into recovery mode no matter what I do. WebOS is unable to detect the device as well, but the PC was able to recognize it as Palm or UQSB something something something (I forgot what it was). After this problem I did not do any battery change or hardware changes. Just me, the question mark battery, and the tpdebrick buigde by jcsullins.
So if you have this problem and absolutely cannot get into the recovery mode, give tpdebrick a try. I used tpdebrick-v004 by jcsullins: rootzwiki.com/topic/38786-tpdebrick-v004
Follow through the steps in that post and it should be okay. But, in case anyone needs it, this is all the steps I did:
0) While my screen was displaying the question mark battery, I pressed Power + Home + Vol Up + Vol Down for 30 seconds while USB plugged into PC to make sure everything turns off (i.e. black screen, no flashing home button). This step may or may not be necessary since part of the debrick process you need to do Power + Home + Vol Down, and it will most likely do the same thing. But just in case.
1) downloaded Ubuntu 12.04 32bit, downloaded webOS 3.0.5 doctor (this was in zip format, and I had to change it to .jar extension), and downloaded tpdebrick-v004.zip from the link above. You can download webOS doctor and tpdebrick in Ubuntu so that you can follow the instruction as written without any trouble, but I did it in my Windows and I fetched it from the Windows storage in Ubuntu. Whichever is easier for you.
2) Downloaded Universal USB Installer and made a bootable USB of Ubuntu. Followed instruction here: ubuntu.com/download/help/create-a-usb-stick-on-windows
3. Boot from USB and run Ubuntu OS
4. Found and moved the tpdebrick.zip and webos jar into the Ubuntu OS Downloads folder
5. Followed steps 14 to 23 from the debrick instruction by JC above. (Basically run terminal, unzip tpdebrick-v004.zip, and hold power + home + vol down for 30 seconds, and run script, and then run "sudo ./tpdebrick XX" where XX = size of your touchpad)
6. Wait patiently for 5 - 10 minutes, and then it says All Done. By this point, my HP touchpad rebooted back to the original state. If this does not happen for you, then you might need to keep researching! Good luck!
NOTE: After the process, my touchpad rebooted back into CM, and I noticed the battery was fully charged. So, obviously there was no problem with the battery nor the charging process. My problem must be due to miscommunication with the battery status.
Click to expand...
Click to collapse
I was able to fix my touchpad with this rootzwiki guide above. My touchpad had JB installed, after a battery drain it was completly dead. I was able to charge it by cutting down an old USB cable and charging the battery alone (touchpad had to be opened).
FYI (Tried ubuntu 12.04.2 in 2 different machines, the tpdebrick only worked on my alienware on the Dell with 1GB of ram it did not worked. The alienware has 2GB of RAM.)
The battery took almost 50% charge, then tried booting it up and nothing (only got question mark).
Theres a small button inside the unit in the charging module, I pressed it, and the unit turned off (it was the only way I could get it to shut down.
Did the debrick process, after that the touchpad would not charg via the USB port and only via the touchstone, so I did the ACMEUninstaller to remove android and it's good as new again. The problem for me was caused by the JB android installed. I had no problems when it had ICS.
Followed the instructions in the link from the first post. And it works!
Was skeptical as instructions seems very complex, but I thought I got nothing to lose. In summary, it was straight forward and you just need to:
1. Download Ubuntu 12.04 LTS and burn the iso to a CD/DVD.
2. Boot up your PC with the Ubuntu Installation CD.
3. Select Try Ubuntu rather than Install.
4. Follow the listed steps/instructions. PS: If you see a "space" for the terminal command, there is a "space" required when you key in the terminal command. And when the script is running, its working, even though you see nothing on the touchpad screen. When "All Done", the touchpad simply rebooted by itself, and ran through the usual boot-up sequence.
Good luck.
Its fixed!!!! Thanks!!!
jackygogo said:
I noticed the links in this post doesn't really lead you to the debrick guide, so I am writing this.
P.S. I am ONLY reporting my experience as is to my HP Touchpad 16GB running CM-tenderloin. I am not in any way responsible for developing this method nor am I responsible for any extra damage that might happen to your already problematic Touchpad. Good luck, and research is your best friend.
I got this question mark battery problem as well and after doing some research I thought my HP Touchpad was gone for good. Then I saw this post and after reading it it inspired me to try the tpdebrick made my jcsullins. And... it worked and my touchpad is back to normal (with everything data intact as well, to my surprise!). My problem was similar to described by other posts in this forum: the touchpad was discharged until it turned off, and then it was left that way for a long time, and when I tried to charge again, it would first give me a flashing home button and then the battery with a question mark after a long time of charging. No matter how long I charged the problem persist, and the device refuses to go into recovery mode no matter what I do. WebOS is unable to detect the device as well, but the PC was able to recognize it as Palm or UQSB something something something (I forgot what it was). After this problem I did not do any battery change or hardware changes. Just me, the question mark battery, and the tpdebrick buigde by jcsullins.
So if you have this problem and absolutely cannot get into the recovery mode, give tpdebrick a try. I used tpdebrick-v004 by jcsullins: rootzwiki.com/topic/38786-tpdebrick-v004
Follow through the steps in that post and it should be okay. But, in case anyone needs it, this is all the steps I did:
0) While my screen was displaying the question mark battery, I pressed Power + Home + Vol Up + Vol Down for 30 seconds while USB plugged into PC to make sure everything turns off (i.e. black screen, no flashing home button). This step may or may not be necessary since part of the debrick process you need to do Power + Home + Vol Down, and it will most likely do the same thing. But just in case.
1) downloaded Ubuntu 12.04 32bit, downloaded webOS 3.0.5 doctor (this was in zip format, and I had to change it to .jar extension), and downloaded tpdebrick-v004.zip from the link above. You can download webOS doctor and tpdebrick in Ubuntu so that you can follow the instruction as written without any trouble, but I did it in my Windows and I fetched it from the Windows storage in Ubuntu. Whichever is easier for you.
2) Downloaded Universal USB Installer and made a bootable USB of Ubuntu. Followed instruction here: ubuntu.com/download/help/create-a-usb-stick-on-windows
3. Boot from USB and run Ubuntu OS
4. Found and moved the tpdebrick.zip and webos jar into the Ubuntu OS Downloads folder
5. Followed steps 14 to 23 from the debrick instruction by JC above. (Basically run terminal, unzip tpdebrick-v004.zip, and hold power + home + vol down for 30 seconds, and run script, and then run "sudo ./tpdebrick XX" where XX = size of your touchpad)
6. Wait patiently for 5 - 10 minutes, and then it says All Done. By this point, my HP touchpad rebooted back to the original state. If this does not happen for you, then you might need to keep researching! Good luck!
NOTE: After the process, my touchpad rebooted back into CM, and I noticed the battery was fully charged. So, obviously there was no problem with the battery nor the charging process. My problem must be due to miscommunication with the battery status.
Click to expand...
Click to collapse
Thanks so much!!! I am so far from knowing how to fix a computer or tablet and my daughters HP touchpad did all of the things mentioned and I did the debrick and It is up and working. I was nervous to try this debrick thing since I have no clue how to do computer stuff but all the directions were clear and easy. Thanks!! I have a happy daughter
sudo ./tpdebrick command not found
hi dude, thank you for the post but i always got the message sudo ./tpdebrick command not found, could you help me?
note: the tpdebrick file is into the folder u.u
dfu-util and fastboot missing
[email protected]:~$ cd downloads
bash: cd: downloads: No such file or directory
[email protected]:~$ cd Downloads
[email protected]:~/Downloads$ unzip tpdebrick-v004
Archive: tpdebrick-v004.zip
replace tpdebrick-v004/tp16.cfg? [y]es, [n]o, [A]ll, [N]one, [r]ename: n
replace tpdebrick-v004/ebr16.bin? [y]es, [n]o, [A]ll, [N]one, [r]ename: N
[email protected]:~/Downloads$ cd tpdebrick-v004
[email protected]:~/Downloads/tpdebrick-v004$ script
Script started, file is typescript
[email protected]:~/Downloads/tpdebrick-v004$ sudo ./tpdebrick 32
dfu-util not installed
fastboot not installed
Aborted.
[email protected]:~/Downloads/tpdebrick-v004$ script
Script started, file is typescript
[email protected]:~/Downloads/tpdebrick-v004$ sudo ./tpdebrick 32
dfu-util not installed
fastboot not installed
Aborted.
[email protected]:~/Downloads/tpdebrick-v004$
why is this coming up? i cant find any links to where i would find dfu-util or fastboot or where it needs to be.
What version of Ubuntu are you using? Is it 32 or 64 bit?
gtallmadge said:
What version of Ubuntu are you using? Is it 32 or 64 bit?
Click to expand...
Click to collapse
I used this particular file and made it into a bootable usb stick
releases.ubuntu.com/12.04/ubuntu-12.04.4-desktop-i386.iso
ubuntu.com/download/desktop/create-a-usb-stick-on-windows
It was a lot easier than I thought, just did the tpdebrick today :good::good:
fixed for the right links
Glad it worked for you. I knew the directions said to use Ubuntu 12.04 which is still available so it is good to know 14.04 which is
the current Long term release of Ubuntu works as well.
I'm sorry, but it was this one that I used
releases.ubuntu.com/12.04/
Thanks for the info..I obviously misread your post.
Questionmark of Death on TP
First problem I ran into, couldn't find a working link for the webos doctor, after an hour of searching, came across a link but xda won't let me post since I don't have 10 posts.
w w w . adbtoolkit.com /rooting/devices/hp/tenderloin/webOS-Doctor/wifi/#.VGYTS9YghCW
Next issue, when it told me to hold my power+vol down+home button down, it would time out with some error( I think it said qdl not found something like that). Tried a few times, then tried a samsung cable for my phone instead of the original touchpad cable, and that worked. Thanks to the guy at rootzwiki for the information.
Does anyone have information on where to find this information now? rootzwiki seems to have deleted it.
ractar28 said:
Does anyone have information on where to find this information now? rootzwiki seems to have deleted it.
Click to expand...
Click to collapse
It's not deleted. You have to log into rootzwiki from the error screen, and the link will load.
Unfortunately if you don't have an account, you can't register any longer for one (I couldn't get the registration process to work).
Luckily, there is the Internet Archive. I can't post a link, so change the 2 "URL" with HTTP in the below:
URL://web.archive.org/web/20150211095226/URL://rootzwiki.com/topic/38786-tpdebrick-v004
Gamedays said:
Unfortunately if you don't have an account, you can't register any longer for one (I couldn't get the registration process to work).
Luckily, there is the Internet Archive. I can't post a link, so change the 2 "URL" with HTTP in the below:
URL://web.archive.org/web/20150211095226/URL://rootzwiki.com/topic/38786-tpdebrick-v004
Click to expand...
Click to collapse
Do you happen to have the guide as well, or am I missing it somewhere? I was also unable to get the registration process to work... the step I am on specifically:
5. Followed steps 14 to 23 from the debrick instruction by JC above. (Basically run terminal, unzip tpdebrick-v004.zip, and hold power + home + vol down for 30 seconds, and run script, and then run "sudo ./tpdebrick XX" where XX = size of your touchpad)
Thanks!
Hi All,
I'm trying to get Ubuntu installed on my Touchpad... with lots of problems... (anyway, for now most are fixed...)
However, does anyone have a working link for TouchPadBuntuRootfs.tar.gz version: 12.04 LTS edition...??
- all links I found so far are dead!!
Ubuntu 12.10 Final = Screen Corruption, graphics messed up.
Ubuntu 13.04 Final = Does not install, and need to get rid of E17 and restore normal desktop
Ubuntu 12.04 = Cannot find this addition anyone, and Ive been trying...
Many thanks, Lister
I'm downloading mine from here.
https://docs.google.com/file/d/0B4WUjKii92l2bDRlQ0NTbTZBemM/preview?pli=1 but haven't tried it in the process of installing it.
Took me awhile I had android on my tp so I ran acme uninstaller to do a fresh start because for some reason my WiFi is not working on android.
When I did that it messed up my whole TP then I had to follow directions to factory reset it took me about an hour so now I'm downloading the files to try to run Ubuntu
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Hi Hovax615,
Thanks for the link, but I am after the specific 12.04 LTS edition of that file...
As I have tried 12.10 but that appears to have limited driver support, and both the graphics display drivers are messed up, plus it wont let me join WiFi... Says I do not have permission, even though I'm an Admin user...
And 13.04 version does not install via the method I mentioned in the other post. It says it's installed, but ends up in a Boot-Loop (only in Ubuntu, all other OS's are fine...).
So if anyone has a link to the 12.04 / LTS Edition that would be most welcomed, as all links to that file seem to be dead at the moment...??
Yeah, restoring a Touchpad can be scary times... My first go at that, and I thought my Tablet had proper died... as even WebOS Doctor didnt want to know it... But thankfully, its alive and well... And now I know how to fix that again easily, its not so scary now... lol
Many thanks, Lister
[email protected] said:
I'm downloading mine from here.
https://docs.google.com/file/d/0B4WUjKii92l2bDRlQ0NTbTZBemM/preview?pli=1 but haven't tried it in the process of installing it.
Took me awhile I had android on my tp so I ran acme uninstaller to do a fresh start because for some reason my WiFi is not working on android.
When I did that it messed up my whole TP then I had to follow directions to factory reset it took me about an hour so now I'm downloading the files to try to run Ubuntu
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Yeah I got it to run pretty easily via smackme2. From clean install all you have to do is make a folder “sminstall" put the files in it should be
UImage,
the kexec which on Ubuntu 13.04 it comes with it already.
Moboot
You have to have the smackme2 in the folder that you have acmeinstaller in when you loaded android. I have windows so mine would be in
Program files/palm, in
Okay so let me run it down for you.
Download the files you need it should be 4 files total depending if your going to run the 12.04 which should be 4
UIMAGE SMACKME2
KEXEC.TAR(OR WHATEVER IT IS)
MOBOOT
UBUNTU
MAKE “SMINSTALL" FOLDER IN TOUCHPAD COPY KEXEC.TAR, MOBOOT, UBUNTU TO SMINSTALL FOLDER.
THAN YOU WANT TO PUT THE UIMAGE SMACKME2 IN THE PALM, INC FOLDER.
NOW TO GET THE PALM, INC FOLDER YOU'LL HAVE TO DOWNLOAD AND INSTALL THE NOVACOM DRIVER. WHICH I ASSUME YOU ALREADY DO.
UNMOUNT YOUR TP RESTART IT AND PUT IT INTO RECOVER (WHEN RESTARTED HOLD UP VOLUME)
NEXT YOU WANT TO OPEN UP “FIND" OR “SEARCH" ON YOUR LAPTOP OR COMPUTER AND OPEN EITHER CMD OR COMMAND PROMPT.
NEXT AS FOLLOWS FOR COMMAND PROMPT.
CD /PROGRAM FILES/PALM, INC
novacom boot mem:// < uImage.SmackMe2
You can copy and paste that last one.
After that it should show the two penguins and start extracting.
It'll reboot the boot into kexec then toggle with volume button to Ubuntu and to select it press/hold the power button at the top.
I'm going to try to find Ubuntu 12.04 for you but its 1am here in California and I'm about to go to bed.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
I was resizing the partitions for the 4.4.2 install following Roland's youtube instructions. I placed the zip package in the cminstall folder and than ran the installcm5 bat file and let the tp do it's thing but it farted out after a few minutes and was non responsive. Now it won't even turn on to be recognized by WebOS Doctor. Is TPDebrick my only option and if so, is there a noob friendly run through of how to use it in windows?
X-Nemesis said:
I was resizing the partitions for the 4.4.2 install following Roland's youtube instructions. I placed the zip package in the cminstall folder and than ran the installcm5 bat file and let the tp do it's thing but it farted out after a few minutes and was non responsive. Now it won't even turn on to be recognized by WebOS Doctor. Is TPDebrick my only option and if so, is there a noob friendly run through of how to use it in windows?
Click to expand...
Click to collapse
TPDebrick requires Ubuntu. It's unlikely your pad is completely fried though. TPDebrick works miracles.
So if I don't have access to an Ubuntu machine than it's pretty much bricked
You can download the version of Ubuntu required for free, download software that turns it into a Live USB (runs off a jump drive) version for free, and run Ubuntu and TPDebrick for free. The only roadblock is your own time and ability to read/comprehend the instructions. It really comes down to whether or not you want to fix it.
Sent from my TouchPad using XDA Premium 4 mobile app
Live CD
X-Nemesis said:
So if I don't have access to an Ubuntu machine than it's pretty much bricked
Click to expand...
Click to collapse
You can download Ubuntu 12.04 and burn a CD/DVD and run it without installing Ubuntu.
Here is a link with instructions for TBDebrick: http://rootzwiki.com/topic/38786-tpdebrick-v004/
Also, if you are unfamiliar with Linux and Ubuntu in particular, the Ubuntu forums are willing to help.
[size=+2]This only works if you are on a software version BEFORE 5.2.1.0![/size]
This will allow you to install recovery easily whether you are rooted or not. The downloads will be numbered starting at v1, and at the bottom of the post it will explain what is contained within each version.
You must extract the installer zip and a recovery zip to the same directory.
Versions for Linux, OSX, and Windows are included. I have not tested the OSX version. Running it won't cause any damage, so don't be afraid to try it. Please let me know if it works.
After extracting the zips, run the .bat file for Windows or the .sh script for Linux and OSX. Make sure the USB cable is connected and if using Windows your drivers are set up. Then power cycle the firetv and the script should start. It should take about 5 minutes to run.
You must copy the ramdisk-recovery.cpio.lzma to USB storage or an sdcard. This must be plugged in when you boot after running the script. The one catch is you need to have a USB keyboard plugged in to select Recovery from bootmenu. So either use an sdcard, a usb hub, or unplug the USB storage once the splash screen shows up and plug in a keyboard.
The first thing you should do after booting in to recovery is to install a prerooted rom. This will fully install recovery so you won't need the ramdisk on external storage anymore.
Source Code
You can find the source code here:
https://github.com/androidrbox/mediatek-preloader-tools
NOTE
This method is only for people on 100% stock rom or people who have rooted with the previous method. Once you install recovery with firetv2_recovery zip file or install a prerooted rom, this method will not work.
Thanks to everyone who has donated to me and those that helped to get me my FireTV 2. Thanks to @zeroepoch, without his work, this wouldn't be possible.
Changelog and Downloads:
February 9, 2016 - v3 (md5sum: d9432930b8a6d50b6b09c31ef698b209)
Fixed the windows bat file
Everything else same as last
February 8, 2016 - v2 (md5sum: 05ddfdf84d4298eb2935acc02c94b70c)
This adds error checking to the .sh and .bat file to make sure all the files exist before attempting to start. (Thanks to @ImCoKeMaN for the idea)
This comes with the same version of mediatek_inject.
February 6, 2016 - v1 (md5sum: b55c61075607fe5d716355dbd8b03a2c)
This comes with mediatek_inject version fa8d8f.
Awesome work!
For those who need a step-by-step guide with screenshots:
[GUIDE] How to Root a Fire TV 2 by installing rbox's Pre-Rooted Image
[VIDEO GUIDE]
md5 = b55c61075607fe5d716355dbd8b03a2c ?
Axecaster said:
md5 = b55c61075607fe5d716355dbd8b03a2c ?
Click to expand...
Click to collapse
I'm just trying to make sure people are paying attention, haha. Not really. I corrected it.
Trying this using Ubuntu Virtual Machine on Windows 10 laptop
I get this error:
[email protected]:~$ '/home/anthony/firetv2recoveryv1/install_firetv2_recovery.sh' Waiting for preloader...
Found port = /dev/ttyACM0
Handshake complete!
Injecting 2ndinit...
/home/anthony/firetv2recoveryv1/install_firetv2_recovery.sh: line 10: ./mediatek_inject.linux: cannot execute binary file: Exec format error
Injecting 2ndinitstub...
/home/anthony/firetv2recoveryv1/install_firetv2_recovery.sh: line 13: ./mediatek_inject.linux: cannot execute binary file: Exec format error
Any ideas?
gazdaman. said:
Trying this using Ubuntu Virtual Machine on Windows 10 laptop
I get this error:
[email protected]:~$ '/home/anthony/firetv2recoveryv1/install_firetv2_recovery.sh' Waiting for preloader...
Found port = /dev/ttyACM0
Handshake complete!
Injecting 2ndinit...
/home/anthony/firetv2recoveryv1/install_firetv2_recovery.sh: line 10: ./mediatek_inject.linux: cannot execute binary file: Exec format error
Injecting 2ndinitstub...
/home/anthony/firetv2recoveryv1/install_firetv2_recovery.sh: line 13: ./mediatek_inject.linux: cannot execute binary file: Exec format error
Any ideas?
Click to expand...
Click to collapse
You're using a 32bit ubuntu I assume? How easy would it be to switch to a 64bit version?
rbox said:
You're using a 32bit ubuntu I assume? How easy would it be to switch to a 64bit version?
Click to expand...
Click to collapse
Yep, Ubuntu 15.10 (32-bit)
It was the image prepared by someone on this forum, so others may run in to the same problem.
Not sure how hard it is to prepare a 64-bit Ubuntu VM.
gazdaman. said:
Yep, Ubuntu 15.10 (32-bit)
It was the image prepared by someone on this forum, so others may run in to the same problem.
Not sure how hard it is to prepare a 64-bit Ubuntu VM.
Click to expand...
Click to collapse
Why not just use the native windows version?
rbox said:
Why not just use the native windows version?
Click to expand...
Click to collapse
When it's waiting on pre loader, the Fire TV just reboots and doesn't catch the pre loader.
Maybe a driver issue. which I don't know how to resolve
gazdaman. said:
When it's waiting on pre loader, the Fire TV just reboots and doesn't catch the pre loader.
Maybe a driver issue. which I don't know how to resolve
Click to expand...
Click to collapse
@AFTVnews.com has an excellent guide: http://www.aftvnews.com/how-to-root-the-amazon-fire-tv-2/
rbox said:
@AFTVnews.com has an excellent guide: http://www.aftvnews.com/how-to-root-the-amazon-fire-tv-2/
Click to expand...
Click to collapse
Thanks.
Got it working on windows now
Much appreciated rbox.
Installer worked fine but I ran into the same problems I had with the updated root method on my mates box.
Constant dropouts and having to restart.
Its down to his box though, not any of the processes as they (eventually) work.
This took 2 1/2hrs for this box with roughly 50 restarts.
This is posted just as another reassurance to people having similar issues. Closing the command window, unplugging the box, re-running the script and powering the box back up works fine. It just takes a little more attention and hand holding
SO, many thanks rbox !!!
awesome! now I can mess around with making a ROM
is anybody else having issues running the .bat file and getting nothing when connecting with USB & powering on? constantly seem to not be able to get pass the stage of waiting for preloader
win 10
chantelle310 said:
is anybody else having issues running the .bat file and getting nothing when connecting with USB & powering on? constantly seem to not be able to get pass the stage of waiting for preloader
win 10
Click to expand...
Click to collapse
im of no help since i use win 7 x64
I tried windows 7 X 64 getting mscvr.dll not found error
and tried in linux still in waiting preloaded.
Any help pls
---------- Post added at 09:29 PM ---------- Previous post was at 09:26 PM ----------
i tried in mac it passes hand shake and stops at reading 0000200 0%
go2xraj said:
I tried windows 7 X 64 getting mscvr.dll not found error
and tried in linux still in waiting preloaded.
Any help pls
---------- Post added at 09:29 PM ---------- Previous post was at 09:26 PM ----------
i tried in mac it passes hand shake and stops at reading 0000200 0%
Click to expand...
Click to collapse
you have all drivers installed and what type of usb cable are you using?
When powered on, does Fire show asadrive on pc when its plugged in?
elliwigy said:
you have all drivers installed and what type of usb cable are you using?
When powered on, does Fire show asadrive on pc when its plugged in?
Click to expand...
Click to collapse
I am using A to A usb cable.
Yes it shows fire tv asadrive
rbox said:
This will allow you to install recovery easily whether you are rooted or not. The downloads will be numbered starting at v1, and at the bottom of the post it will explain what is contained within each version.
You must extract the installer zip and a recovery zip to the same directory.
Versions for Linux, OSX, and Windows are included. I have not tested the OSX version. Running it won't cause any damage, so don't be afraid to try it. Please let me know if it works.
After extracting the zips, run the .bat file for Windows or the .sh script for Linux and OSX. Make sure the USB cable is connected and if using Windows your drivers are set up. Then power cycle the firetv and the script should start. It should take about 5 minutes to run.
You must copy the ramdisk-recovery.cpio to USB storage or an sdcard. This must be plugged in when you boot after running the script. The one catch is you need to have a USB keyboard plugged in to select Recovery from bootmenu. So either use an sdcard, a usb hub, or unplug the USB storage once the splash screen shows up and plug in a keyboard.
The first thing you should do after booting in to recovery is to install a prerooted rom. This will fully install recovery so you won't need the ramdisk on external storage anymore.
Source Code
You can find the source code here:
https://github.com/androidrbox/mediatek-preloader-tools
NOTE
This method is only for people on 100% stock rom or people who have rooted with the previous method. Once you install recovery with firetv2_recovery zip file or install a prerooted rom, this method will not work.
Thanks to everyone who has donated to me and those that helped to get me my FireTV 2. Thanks to @zeroepoch, without his work, this wouldn't be possible.
Changelog and Downloads:
February 9, 2016 - v3 (md5sum: d9432930b8a6d50b6b09c31ef698b209)
Fixed the windows bat file
Everything else same as last
February 8, 2016 - v2 (md5sum: 05ddfdf84d4298eb2935acc02c94b70c)
This adds error checking to the .sh and .bat file to make sure all the files exist before attempting to start. (Thanks to @ImCoKeMaN for the idea)
This comes with the same version of mediatek_inject.
February 6, 2016 - v1 (md5sum: b55c61075607fe5d716355dbd8b03a2c)
This comes with mediatek_inject version fa8d8f.
Click to expand...
Click to collapse
Didn't work for me. Installed recovery (what appears successfully) on Windows 7; I did run the install more than once; was running over USB hub and it crapped out once or twice, so removing the USB hub allowed it to complete. Completed all the way to "Press any key to continue". I then plugged into my TV, plugged in the USB drive with the 2 files on it (lzma and pre-rooted zip) and my keyboard into a USB hub. Plugged in power and saw the regular black and white amazon boot logo, then the colored one that said Fire TV. I was (am) on 5.0.4 non-rooted.
Any ideas on how to get this to install?
bubbanc said:
Didn't work for me. Installed recovery (what appears successfully) on Windows 7; I did run the install more than once; was running over USB hub and it crapped out once or twice, so removing the USB hub allowed it to complete. Completed all the way to "Press any key to continue". I then plugged into my TV, plugged in the USB drive with the 2 files on it (lzma and pre-rooted zip) and my keyboard into a USB hub. Plugged in power and saw the regular black and white amazon boot logo, then the colored one that said Fire TV. I was (am) on 5.0.4 non-rooted.
Any ideas on how to get this to install?
Click to expand...
Click to collapse
So my first suggestion is to try the guide and/or video linked in the 2nd post. My other suggestion is to try without the hub. I know some can be flaky. The guide in the 2nd post has some tips to deal with not using a hub.
Ok so I installed Ubuntu 16.04 onto a fladhdrive and booted it.
I downloaded the files debrick005 and webdoc.jar files. I put them in my home folder. This is where I having problem. I can see the files in the visual part, but ls in terminal sees them but they are listed in red? Not sure if that's normal. I tried to unzip the folder in terminal with no luck. I was able to extract clicked the visual folder and clicking extract.
Everything seem ok even thought I couldn't unzip in terminal. When I run ./debrick 16 it checks the script and says it can't find the webdoctor.jar. it's in tpdebrick folder visually...
I'm kind of a linux noob . Surprised I got this far. Not really sure what's going on. The .jar file is in there and the file names match.
Anybelp from you guys would be awesome. My tp has sat with questionmark battery error for years....
Ok so I moved the .jar to the home folder. The script ran. It seemed like it was working til it gets to copying A6 files. It's spits "unable to negotiate with 192.168.7.7 port 22: no matching key exchange method found. Their offer: diffie-hellman-group1-shal. Lost connection. Copy failed aborted.
I'm not sure why the edit to my sshd_config isn't working as described.
I tried to modded tpdebrick script posted a few posts back with dellie-hellman support, Moved it to the tpdebrick folder and renamed it and replaced with the original tpdebrick script. Still same error when trying A6 firmware.
Edit: when I open sshd_config in gedit, it's blank except for the code changes I made. Pretty stuck at this point and don't know what should be there to begin with.
So I solved the problem. I ran the script in ubuntu 14. No modifications to the sshd_config needed. Scripts ran and said charge for a while. Couple hours later, my touchpad, which has sat unusable for 2yrs, is not operational. Hope this helps someone else who runs across this problem.
HP TOUCHPAD DEBRICK Linux Live CD
I have created an Ubuntu Live CD with all the necessary files to Debrick the Tablet from TP Debrick v005 by jcsullins.
If there is any Tablet that did not finished the flash process, run this Live CD and perform the Debrick again.
If you do not know the Tablet model do the following:
Flash using the 16 GB, then connect to charger. If the home LED does not come on after some time then.
Flash using the 32 GB, then connect to charger. If no LED light then
Flash using the 64 GB.
All process must finish in " ALL DONE "
Click HERE for the HP TOUCHPAD DEBRICK LIVE CD
For information about charging a Tablet after been store for 9 years go here:
https://forums.webosnation.com/hp-touchpad/332615-hp-touchpad-won-t-turn-brand-new-never-opened.html