Hello everyone.
Last week I got access to an old supposedly dead touchpad lying at my friends office. Had to fiddle with it for almost a day and a half to get it running as it was totally out of charge.
Tried all possible combinations of VolUp, VolDown, Home but it just would not start initially, even after leaving it for charging for whole night using the original charger.
Anyhow once it booted, to my surprise it had Android 2.3.3 preinstalled. The initialy few sec boot screen showed HP logo with few cmd lines mentioning topaz etc etc.
The few details in the back are as below...
Prototype - NfS
FB35UA-EVT
CPU - APQ80680(64M)Rev.2
So anyone around have been able to take a complete back of the original rom and then upgrade to CM9/Cm10?
I tried following the common steps for upgrading from WebOS to CMx but none works for obvious reasons.
I am currently trying to get help on how to install mboot and tenderlionCWM, hence any pointer would be of great help. FYI the terminal does not give SU access either.
Update 1 - Out of desperation, I ran the JC tool tpdebrick, well didn't went good, I believe.... the outcome is that the device does not show any activity on screen and under windows device manager it either shows Android or QHSUSB_DLOAD!!!
Hi, never heard of the hp touchpad coming with factory pre installed android, and j's debrick is i think only for something that is lifeless..
Anyway what I would suggest is this thread http://forum.xda-developers.com/showthread.php?t=1426244 paying particular attention to the first post on page 12. And with luck you will have a working TP.
PM if you want /need further assistance.
followed the give guid to restore to factory, however no positive results.
I got stuck on the first step itself as the PC shows the device as an Android device., Hence Novacom is unable to find the device.
The touchpad device property is as below.
Bus 002 Device 030: ID 18d1:d00d Google Inc.
I had to install the google usb drivers with tweaked inf as mentioned else where in the forums. The only difference was that the device id is different than the ones posted here.
I went ahead and tried placing the command
adb devices
but that too shows no device connected, even though the PC device manager shows it connect with drivers.
pls suggest possible wayouts
Android 2.3.3?, is there any pictures we can see? Pretty please.
Have you tried installing a camera launcher to see if the drivers are there?
Sent from my Nexus 7 using xda app-developers app
Well I wish I did a rom backup before moving forward, however as I had updated in my OP, Im in a brick situation right now, with no signs of life.
For last two days I am running tpdebrick by JC to revive it, but alas no positive signs for now.
P.S. For once when it did switch on, yes the stock camera was running, but the images were way below normal.
There were a select few Touchpads that accidentally shipped with Froyo 2.2 which was likely being used to test the hardware before WebOS was completed for it. But I've never heard of one shipping with GB, any CM7 ROMs for this were based on 2.3.7 IIRC.
sstar said:
Hi, never heard of the hp touchpad coming with factory pre installed android, and j's debrick is i think only for something that is lifeless..
Anyway what I would suggest is this thread http://forum.xda-developers.com/showthread.php?t=1426244 paying particular attention to the first post on page 12. And with luck you will have a working TP.
PM if you want /need further assistance.
Click to expand...
Click to collapse
I used the link above on a TP I bricked, did not work. What revived it was the TPdebrick following procedure
http://rootzwiki.com/topic/38786-tpdebrick-v004/
your tp might be valuable to developers. i would contact them and see if theres some system files on it they could use.
a very few prototype models had android installed on them, but they were never meant for the public. however a select few did manage to get out into the wild. this one you have is quite rare.
edit: never mind, i see you've bricked it. could have had some potential useful files on there
I'm guessing TP Debrick won't work for you because you're in Google Inc. mode already. A little modding of the tpdebrick script to skip the first steps would probably solve this problem.
I will attempt if no one beats me to it.
bonkers! I never realised that it was this a rare device . I had been careless handling this and overconfident in putting custom roms etc.
Anyway I spent the day last in running the tpdebrick004 again and again with different ways. Prior to that our fiddling with webdoctor, novaterm etc all failed.
The results are as below... for the honorary members here!
Test bed - Ubuntu live 12.04 32bit, with android-adb and fastboot installed and TPdebrick004
Scenario 1
1. Under Home+VolDown+Power mode
2. lsusb shows...
Code:
05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
3. Running tpdebrick004 aborts with the following
Code:
tpdebrick-v004$ sudo ./tpdebrick 32
checking doc files ...
Requesting SoftwareVersion...
Version: PBL_DloadVER1.0
Requesting Params...
Params: 06 01 01 00 90 00 00
Uploading file 'emmcbld.bin' to QDLOAD...
Writing 1024 bytes to 0x2a000000; 164996 bytes left.
Writing 1024 bytes to 0x2a000400; 163972 bytes left.
Writing 1024 bytes to 0x2a000800; 162948 bytes left.
Writing 1024 bytes to 0x2a000c00; 161924 bytes left.
.
.
.
.
Writing 1024 bytes to 0x2a027400; 4228 bytes left.
Writing 1024 bytes to 0x2a027800; 3204 bytes left.
Writing 1024 bytes to 0x2a027c00; 2180 bytes left.
Writing 1024 bytes to 0x2a028000; 1156 bytes left.
Writing 1024 bytes to 0x2a028400; 132 bytes left.
Writing 132 bytes to 0x2a028800; 0 bytes left.
Executing file...
Checking QDL mode...
Writing file tz.mbn ...
Sending MAGIC...
MSG: Qfprom Fuse List: Blowing FAILED
MSG: Failed Fuse addr:
MSG: 0x00000000
MSG: Error Status:
MSG: 0x00000000
Sending secureMode...
Sending openMulti ...
Uploading file 'tz.mbn'...
Writing 1024 bytes to 0x18000000; 97896 bytes left.
Response: ACK 0x18000000 (outstanding: 0)
Writing 1024 bytes to 0x18000400; 96872 bytes left.
Response: ACK 0x18000400 (outstanding: 0)
Writing 1024 bytes to 0x18000800; 95848 bytes left.
Response: ACK 0x18000800 (outstanding: 0)
.
.
.
Response: ACK 0x06410e00 (outstanding: 0)
Writing 1024 bytes to 0x06411200; 552 bytes left.
Response: ACK 0x06411200 (outstanding: 0)
Writing 552 bytes to 0x06411600; 0 bytes left.
Response: ACK 0x06411600 (outstanding: 0)
Sending CloseFlush...
Writing file mbr32.bin ...
Sending MAGIC...
Sending secureMode...
Sending openMulti ...
Uploading file 'mbr32.bin'...
Writing 512 bytes to 0x00000000; 0 bytes left.
Response: ACK 0x00000000 (outstanding: 0)
Sending CloseFlush...
Done writing files.
Reseting device...
Requesting Reset...
Waiting for fastboot mode...
fastboot mode not found
Aborted.
Nothing happens thereafter.
Scenario 2
4. After reading few tips in the tpdebrick discussion in rootzwiki, after getting the fastboot mode not found message I manually reset the TP into Home+VolUp+Power mode
5. lsusb in sperate terminal window shows
Code:
Bus 002 Device 030: ID 18d1:d00d Google Inc.
6. running tpdebrick again continues further after fastboot message..
Code:
Response: ACK 0x00000000 (outstanding: 0)
Sending CloseFlush...
Done writing files.
Reseting device...
Requesting Reset...
Waiting for fastboot mode...
Loading TPToolbox-Headless ...
sending 'bootmem' (13200 KB)...
OKAY [ 0.827s]
writing 'bootmem'...
OKAY [ 2.924s]
finished. total time: 3.751s
Waiting for netchip mode... (may take 3+ mins)
Waiting for ping check... (may take 1-2 mins)
Checking/updating known_hosts...
Copying A6 files...
a6_firmware.txt.00 100% 48KB 48.3KB/s 00:00
PmA6Updater 100% 13KB 13.4KB/s 00:00
Copying bootloader files...
bootie-topaz305.bin 100% 113KB 112.8KB/s 00:00
emmc_appsboot.mbn 100% 45KB 44.7KB/s 00:00
Checking A6 firmware...
processing file: /tmp/a6_firmware.txt.00
A6 device: /dev/a6_0
2.13.10 (0x020d000a)
fw file size: 49461
fw file mapped at: 0x401a3000
Firmware verification complete
Updating A6 firmware...
Write failed: Broken pipe
A6 firmware update failed.
Aborted.
It takes hell lot of a time after the Updating A6 firmware message... almost half hour or more...
And that is where I am stuck right now... Hope this is of some help in figuring out the next steps...
your device has different partitioning and no webos installed. the tpdebrick and the methods for installing the CM7/9/10 won't work for you.
when you have started messing with tpdebrick, webos doctor you have probably bricked the device for good and every valuable part of software that has been shipped with this prototype rom you had is lost.
maybe, though webdoctor was not able to connect, however how one would know that the partitioning was different. do excuse my lame Q
Because it didn't have web os.
desihu said:
bonkers! I never realised that it was this a rare device . I had been careless handling this and overconfident in putting custom roms etc.
Anyway I spent the day last in running the tpdebrick004 again and again with different ways. Prior to that our fiddling with webdoctor, novaterm etc all failed.
The results are as below... for the honorary members here!
Test bed - Ubuntu live 12.04 32bit, with android-adb and fastboot installed and TPdebrick004
Scenario 1
1. Under Home+VolDown+Power mode
2. lsusb shows...
Code:
05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
3. Running tpdebrick004 aborts with the following
Code:
tpdebrick-v004$ sudo ./tpdebrick 32
checking doc files ...
Requesting SoftwareVersion...
Version: PBL_DloadVER1.0
Requesting Params...
Params: 06 01 01 00 90 00 00
Uploading file 'emmcbld.bin' to QDLOAD...
Writing 1024 bytes to 0x2a000000; 164996 bytes left.
Writing 1024 bytes to 0x2a000400; 163972 bytes left.
Writing 1024 bytes to 0x2a000800; 162948 bytes left.
Writing 1024 bytes to 0x2a000c00; 161924 bytes left.
.
.
.
.
Writing 1024 bytes to 0x2a027400; 4228 bytes left.
Writing 1024 bytes to 0x2a027800; 3204 bytes left.
Writing 1024 bytes to 0x2a027c00; 2180 bytes left.
Writing 1024 bytes to 0x2a028000; 1156 bytes left.
Writing 1024 bytes to 0x2a028400; 132 bytes left.
Writing 132 bytes to 0x2a028800; 0 bytes left.
Executing file...
Checking QDL mode...
Writing file tz.mbn ...
Sending MAGIC...
MSG: Qfprom Fuse List: Blowing FAILED
MSG: Failed Fuse addr:
MSG: 0x00000000
MSG: Error Status:
MSG: 0x00000000
Sending secureMode...
Sending openMulti ...
Uploading file 'tz.mbn'...
Writing 1024 bytes to 0x18000000; 97896 bytes left.
Response: ACK 0x18000000 (outstanding: 0)
Writing 1024 bytes to 0x18000400; 96872 bytes left.
Response: ACK 0x18000400 (outstanding: 0)
Writing 1024 bytes to 0x18000800; 95848 bytes left.
Response: ACK 0x18000800 (outstanding: 0)
.
.
.
Response: ACK 0x06410e00 (outstanding: 0)
Writing 1024 bytes to 0x06411200; 552 bytes left.
Response: ACK 0x06411200 (outstanding: 0)
Writing 552 bytes to 0x06411600; 0 bytes left.
Response: ACK 0x06411600 (outstanding: 0)
Sending CloseFlush...
Writing file mbr32.bin ...
Sending MAGIC...
Sending secureMode...
Sending openMulti ...
Uploading file 'mbr32.bin'...
Writing 512 bytes to 0x00000000; 0 bytes left.
Response: ACK 0x00000000 (outstanding: 0)
Sending CloseFlush...
Done writing files.
Reseting device...
Requesting Reset...
Waiting for fastboot mode...
fastboot mode not found
Aborted.
Nothing happens thereafter.
Scenario 2
4. After reading few tips in the tpdebrick discussion in rootzwiki, after getting the fastboot mode not found message I manually reset the TP into Home+VolUp+Power mode
5. lsusb in sperate terminal window shows
Code:
Bus 002 Device 030: ID 18d1:d00d Google Inc.
6. running tpdebrick again continues further after fastboot message..
Code:
Response: ACK 0x00000000 (outstanding: 0)
Sending CloseFlush...
Done writing files.
Reseting device...
Requesting Reset...
Waiting for fastboot mode...
Loading TPToolbox-Headless ...
sending 'bootmem' (13200 KB)...
OKAY [ 0.827s]
writing 'bootmem'...
OKAY [ 2.924s]
finished. total time: 3.751s
Waiting for netchip mode... (may take 3+ mins)
Waiting for ping check... (may take 1-2 mins)
Checking/updating known_hosts...
Copying A6 files...
a6_firmware.txt.00 100% 48KB 48.3KB/s 00:00
PmA6Updater 100% 13KB 13.4KB/s 00:00
Copying bootloader files...
bootie-topaz305.bin 100% 113KB 112.8KB/s 00:00
emmc_appsboot.mbn 100% 45KB 44.7KB/s 00:00
Checking A6 firmware...
processing file: /tmp/a6_firmware.txt.00
A6 device: /dev/a6_0
2.13.10 (0x020d000a)
fw file size: 49461
fw file mapped at: 0x401a3000
Firmware verification complete
Updating A6 firmware...
Write failed: Broken pipe
A6 firmware update failed.
Aborted.
It takes hell lot of a time after the Updating A6 firmware message... almost half hour or more...
And that is where I am stuck right now... Hope this is of some help in figuring out the next steps...
Click to expand...
Click to collapse
I'm having the exact same issue on a 32GB 3G version of the Touchpad.
It always fails at the A6 flashing...
Redferne said:
I'm having the exact same issue on a 32GB 3G version of the Touchpad.
It always fails at the A6 flashing...
Click to expand...
Click to collapse
If you guys want to get these fixed, PM jcsullins and ask him to join you on IRC.
There are andriod 2.2.1 /2.3.3/2.3.4 os version for Touchpads in 2011(Never released).Andriod Version can flash back to webos. But need PalmWinDfuUtil/NovaDeviceInstaller/webos Tar files..etc
If use Tpdebrick 004 run to All Done. Will see flower type on the screen (The means into Revoery mode). Must use Nova Device Installer to flash the device.(Can not use doctor). But it will lost Wifi address and need to rewrite it....
Cannot get past Fastboot using TPDEBRICK 004
I posted the problem on RootzWiki, but essentially my 32GB 3G TP does not get past Fastboot:
Sending CloseFlush...
Done writing files.
Resetting device...
Requesting Reset...
Waiting for fastboot mode...
fastboot mode not found
Aborted.
Fastboot will work to communicate with the TP, but I don't know enough to troubleshoot the debrick scripts on my own.
lsusb reveals:
Bus 002 Device 015: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Is there anything that can be done manually via command line using fastboot? I'm not a Linux newbie, but i'm not a developer either.
So, I started digging because i'm curious...
in the tpdebrick script found the following:
devid_fastboot="18d1:d00d"
also found this:
echo "Reseting device..."
perl qdload.pl --lreset
echo "Waiting for fastboot mode..."
if ! `check_usbdevs 60 ${devid_fastboot}`
then
echo "fastboot mode not found"
echo "Aborted."
exit 1
fi
echo "Loading TPToolbox-Headless ..."
fastboot flash bootmem TPToolbox-Headless-v004
if [ $? -ne 0 ];
then
echo "TPToolbox-Headless load failed"
echo "Aborted."
exit 1
fi
So I sort of understand the script, but again i'm not a developer...
When I manually execute the perl command, I get the following result (is this a problem?):
[email protected]:~/Downloads/tpdebrick-v004# perl qdload.pl --lreset
Requesting Reset...
Invalid Response: 03 00 06
If the Invalid Response is correct, then it appears to be failing to execute the fastboot with the check_usbdevs devid.
Is there anyway to check the usbdevs and/or devid, and that these are correct?
Related
I was given a kindle fire hd 7 that is stuck in a boot loop. My friend gave up trying to root it and just gave it to me in its borked state. What he told me he did was root the device then used the one click apk, from that point on its been stuck in a boot loop. Past that he is not sure what he did. Fastboot does not recognize it unless using the 0x1949.
I am on Linux and have no simple access to a windows box, I have tried issuing fast boot commands to put a new system recovery and boot img on the device but, all I end up with is either a fastboot loop or the kindle loop. I am lost trying to sort out what I should be trying next or if this is just a brick at this point. Looking for some advice as to where to go now? Does anyone have a link to a good known working system recovery boot images or to a linux guide that shows what to do when its not recognized and how to restore? I took the ones from KFHD package and have tried every combo of images they had including each versions system.img and system2.img, all with the same results. I can post any other info needed to help diagnose the issue, also adb does not recognize the device either.
Here is some outputs
Code:
adb devices
List of devices attached
Code:
adb version
Android Debug Bridge version 1.0.31
Code:
lsusb -v -d 1949:0007
Bus 001 Device 008: ID 1949:0007 Lab126, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1949 Lab126, Inc.
idProduct 0x0007
bcdDevice 1.00
iManufacturer 5 Texas Instruments
iProduct 1 Tate-PVT-08
iSerial 2 69B8000200000001
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 3 Android Fastboot
bmAttributes 0xc0
Self Powered
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 66
bInterfaceProtocol 3
iInterface 4 Android Fastboot
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0001
Self Powered
Code:
fastboot -i 0x1949 getvar product
< waiting for device >
product: Tate-PVT-08
finished. total time: 0.001s
Code:
fastboot -i 0x1949 flash system system.img
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [312.399s]
writing 'system'...
OKAY [ 75.874s]
finished. total time: 388.273s
Code:
fastboot -i 0x1949 flash recovery recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 2.823s]
writing 'recovery'...
OKAY [ 0.929s]
finished. total time: 3.753s
Code:
fastboot -i 0x1949 boot boot.img
creating boot image...
creating boot image - 8390656 bytes
downloading 'boot.img'...
OKAY [ 2.831s]
booting...
OKAY [ 0.003s]
finished. total time: 2.834s
The order of the fastboot commands is the order that I issued them when trying to restore the KFHD7. Can anyone shed some light on what I am missing here or what I am doing wrong. I have never had so much issue as I have trying to fix this device. I always end up with the kindlefire logo looping. Thanks a bunch for any help with this.
vwyoda said:
I was given a kindle fire hd 7 that is stuck in a boot loop. My friend gave up trying to root it and just gave it to me in its borked state. What he told me he did was root the device then used the one click apk, from that point on its been stuck in a boot loop. Past that he is not sure what he did. Fastboot does not recognize it unless using the 0x1949.
I am on Linux and have no simple access to a windows box, I have tried issuing fast boot commands to put a new system recovery and boot img on the device but, all I end up with is either a fastboot loop or the kindle loop. I am lost trying to sort out what I should be trying next or if this is just a brick at this point. Looking for some advice as to where to go now? Does anyone have a link to a good known working system recovery boot images or to a linux guide that shows what to do when its not recognized and how to restore? I took the ones from KFHD package and have tried every combo of images they had including each versions system.img and system2.img, all with the same results. I can post any other info needed to help diagnose the issue, also adb does not recognize the device either.
Here is some outputs
Code:
adb devices
List of devices attached
Code:
adb version
Android Debug Bridge version 1.0.31
Code:
lsusb -v -d 1949:0007
Bus 001 Device 008: ID 1949:0007 Lab126, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1949 Lab126, Inc.
idProduct 0x0007
bcdDevice 1.00
iManufacturer 5 Texas Instruments
iProduct 1 Tate-PVT-08
iSerial 2 69B8000200000001
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 3 Android Fastboot
bmAttributes 0xc0
Self Powered
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 66
bInterfaceProtocol 3
iInterface 4 Android Fastboot
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0001
Self Powered
Code:
fastboot -i 0x1949 getvar product
< waiting for device >
product: Tate-PVT-08
finished. total time: 0.001s
Code:
fastboot -i 0x1949 flash system system.img
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [312.399s]
writing 'system'...
OKAY [ 75.874s]
finished. total time: 388.273s
Code:
fastboot -i 0x1949 flash recovery recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 2.823s]
writing 'recovery'...
OKAY [ 0.929s]
finished. total time: 3.753s
Code:
fastboot -i 0x1949 boot boot.img
creating boot image...
creating boot image - 8390656 bytes
downloading 'boot.img'...
OKAY [ 2.831s]
booting...
OKAY [ 0.003s]
finished. total time: 2.834s
The order of the fastboot commands is the order that I issued them when trying to restore the KFHD7. Can anyone shed some light on what I am missing here or what I am doing wrong. I have never had so much issue as I have trying to fix this device. I always end up with the kindlefire logo looping. Thanks a bunch for any help with this.
Click to expand...
Click to collapse
Download a windows iso for free from kick ads torrents with that you get 30days free trial of windows set up java jdk and android sdk download the recovery tool from the development thread fastboot start process wait wipe date reboot done.
Stupid question you are using a fast boot cable?
Sent from my GT-P3110 using xda app-developers app
mrkhigh said:
Stupid question you are using a fast boot cable?
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
Yes I am and I showed the output from the device in the lsusb portion. I get to the fastboot screen. It shows the output above stating its seeing it. Says its OK on each step for uploading the files.
[Edit:] Where did you get the partition images you're trying to restore?
soupmagnet said:
[Edit:] Where did you get the partition images you're trying to restore?
Click to expand...
Click to collapse
I got them from the 7" Dev board inside the KFHD System.img Restore Tool
http://forum.xda-developers.com/showthread.php?t=1951254
And just to confirm I am not dense this is the model number of the kindle X43Z60
Are there different images I should be using? Are the commands wrong?
vwyoda said:
Are there different images I should be using? Are the commands wrong?
Click to expand...
Click to collapse
It's hard to tell. With no way to check the md5 on the images you're restoring, who knows what you're dealing with. I can tell you that the boot and recovery partitions should be exactly the same size. Your outputs seem to differ, but I haven't taken the time to convert 8192kb to bytes to know for sure.
soupmagnet said:
It's hard to tell. With no way to check the md5 on the images you're restoring, who knows what you're dealing with. I can tell you that the boot and recovery partitions should be exactly the same size. Your outputs seem to differ, but I haven't taken the time to convert 8192kb to bytes to know for sure.
Click to expand...
Click to collapse
KFHD_SRTv1.3
Code:
md5sum boot.img
5ea5d3eaba8c8fe7e615aeb9c462a6d8 boot.img
Code:
md5sum system.img
7c93ab84d94e9bc8142b40c58fd1761f system.img
Code:
md5sum recovery.img
3b51741e72f985fa1eb86c2b7b9f7cac recovery.img
Code:
du -h *
8.0M boot.img
8.0M recovery.img
887M system.img
Okay, let me try and explain this to you. In your output from the OP you have the following listed for the boot and recovery images...
Code:
fastboot -i 0x1949 flash recovery recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 2.823s]
writing 'recovery'...
OKAY [ 0.929s]
finished. total time: 3.753s
Code:
fastboot -i 0x1949 boot boot.img
creating boot image...
creating boot image - 8390656 bytes
downloading 'boot.img'...
OKAY [ 2.831s]
booting...
OKAY [ 0.003s]
finished. total time: 2.834s
As I said before, the boot and recovery images should be the exact same size. When you convert 8192KB to bytes, you get 8388608B, which is obviously different from 8390656B. You should probably check your downloads and make sure you have the right ones.
That being said, I'd like to draw your attention to the following two lines of code posted above...
Code:
...
fastboot -i 0x1949 flash recovery recovery.img
...
fastboot -i 0x1949 boot boot.img
...
Don't you think it would work better if it looked like this?
Code:
...
fastboot -i 0x1949 flash recovery recovery.img
...
fastboot -i 0x1949 flash boot boot.img
...
@soupmagnet
Thanks!!! You spotted the issue cant believe I was missing that every time.
It showed the correct sizes once I added flash Thanks again.
Hello,
My Touchpad don't boot. I try several combi buttons, Vol+ Power Home, Home, etc...
It's recognized as "Qualcom QHSUSB_DLOAD" when I plugg it to a PC.
I try TPdebrick script and get the staus "Aborted":
Code:
[email protected]:~/Téléchargements/tpdebrick-v004$ script
Script started, file is typescript
[email protected]:~/Téléchargements/tpdebrick-v004$ sudo ./tpdebrick 32
checking doc files ...
Requesting SoftwareVersion...
Version: PBL_DloadVER1.0
Requesting Params...
Params: 06 01 01 00 90 00 00
Uploading file 'emmcbld.bin' to QDLOAD...
Writing 1024 bytes to 0x2a000000; 164996 bytes left.
Writing 1024 bytes to 0x2a000400; 163972 bytes left.
...
Writing 1024 bytes to 0x2a027c00; 2180 bytes left.
Writing 1024 bytes to 0x2a028000; 1156 bytes left.
Writing 1024 bytes to 0x2a028400; 132 bytes left.
Writing 132 bytes to 0x2a028800; 0 bytes left.
Executing file...
Checking QDL mode...
Writing file tz.mbn ...
Sending MAGIC...
MSG: Qfprom Fuse List: Blowing FAILED
MSG: Failed Fuse addr:
MSG: 0x00000000
MSG: Error Status:
MSG: 0x00000000
Sending secureMode...
Sending openMulti ...
MSG: Open multi failed, unknown error
ERROR: Open multi failed, unknown error
Invalid openMulti response.
Cannot write file tz.mbn
Aborted.
[email protected]:~/Téléchargements/tpdebrick-v004$ exit
exit
Script done, file is typescript
I try to search "QHSUSB_DLOAD" on internet but without success.
How can I solve this ?
Thanks.
Not trying to be the one to give you the bad news but there is no guaranteed fix when TPDebrick returns the Open Multi error.
Sent from my TouchPad using XDA Premium 4 mobile app
Yes, I know.
Maybe, there is a solution somewhere...I search, read a lot but not find.
I'm not optimistic a fix will ever come, but you never know.
Sent from my TouchPad using XDA Premium 4 mobile app
Plenty of folks on the tpdebrick thread have this issue, and as of yet there is no fix...
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
So i hard bricked my at&t Note 3 when i was in Odin. Looked like Odin froze so i unplugged it half way thru and tried to get back into download mode and NOTHING! Black screen ... can't get into download mode, power device on or nothing. Never bricked a device in all the years i've been rooting and tried everything. Unfortuantly, i still can't get this to work on Linux system and just want to know im doing things right. I placed the img on sd card and inserted it with thumb usb and that's fine. When i type in dmesg | tail i get this ...
[email protected] ~ $ dmesg | tail
[ 1548.786072] sd 10:0:0:0: [sdb] No Caching mode page found
[ 1548.786079] sd 10:0:0:0: [sdb] Assuming drive cache: write through
[ 1548.790452] sd 10:0:0:0: [sdb] No Caching mode page found
[ 1548.790461] sd 10:0:0:0: [sdb] Assuming drive cache: write through
[ 1548.791624] sdb: sdb1
[ 1548.794337] sd 10:0:0:0: [sdb] No Caching mode page found
[ 1548.794347] sd 10:0:0:0: [sdb] Assuming drive cache: write through
[ 1548.794355] sd 10:0:0:0: [sdb] Attached SCSI removable disk
[ 1549.170010] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 1956.468460] perf samples too long (2506 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
I know my card is sdb1 and tried typing in the rest of the commands. When i type in second command sudo dd if=/<path_to_debrick.img> of=/dev/sdX i get this ...
[email protected] ~ $ sudo dd if=/<path_to_debrick.img> of=/dev/sdb1
bash: path_to_debrick.img: No such file or directory
Really no idea what im doing to not get this work but i'm sure it's something simple. I just want to get back into download mode and then i'll be straight and can Odin my files to recover. Unfortuantely i can't get back in download mode!
Do i need MJ5 img since i was on MJ5 then did UNOFFICIAL KK update and was running DynamicKat when this happened?
Also i am using a SanDisk Elevate 32GB sdhc card on my 32 Note 3 so i know the cards not the problem. It's brand new and reads fine otherwise.
Please let me know if i'm doing anything wrong as i've been working on this for 48 hours and just need my phone back! lol
Thanks ... I really appreciate it!
I'm just going to bite my tongue on this one and help you.
"<path_to_debrick.img>" is just a place holder, you have to actually put the path of the debrick.img file you loaded onto your device, not <path_to_debrick.img>
SpikeyPsyche said:
I'm just going to bite my tongue on this one and help you.
"<path_to_debrick.img>" is just a place holder, you have to actually put the path of the debrick.img file you loaded onto your device, not <path_to_debrick.img>
Click to expand...
Click to collapse
Wow. That's all i have to say ... just wow! Atleast someone was able to "Bite their tongue" and let me know. Appreciate it. Will try again now. Thanks lol ... no words
SpikeyPsyche said:
I'm just going to bite my tongue on this one and help you.
"<path_to_debrick.img>" is just a place holder, you have to actually put the path of the debrick.img file you loaded onto your device, not <path_to_debrick.img>
Click to expand...
Click to collapse
Sent you a PM. Thanks again.
So i got the img to write onto sd card but still can't get into download mode when i hold the buttons. No signs of life still. This is what i got after i wrote the image
PaulMichael paul # dd if=/home/paul/Desktop/debrick/Unbrick_SM-N900A.img of=/dev/sdb1
400000+0 records in
400000+0 records out
204800000 bytes (205 MB) copied, 72.2845 s, 2.8 MB/s
PaulMichael paul # fdisk -l /dev/sdb1
WARNING: GPT (GUID Partition Table) detected on '/dev/sdb1'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sdb1: 31.9 GB, 31910789120 bytes
1 heads, 32 sectors/track, 1947680 cylinders, total 62325760 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1p1 1 61071359 30535679+ ee GPT
Any help would be appreciated. I even tried it twice with no luck. Also my new 32gb sd card won't read now when i put it reader into usb. No pop up or anything? Thanks guys.
***Edited*** also i was on MJ5 then did the Unofficial "Jump from Jellybean to kk" ... which image would i need then? And if someone has it can they send it to me please!
Something didn't go right with the debrick image writing. That fdisk command should have listed all the partitions on that disk, with should be 20+, and you are only seeing one.
Re-run writing the debrick image. Sometimes it fails on the first few tries.
SpikeyPsyche said:
Something didn't go right with the debrick image writing. That fdisk command should have listed all the partitions on that disk, with should be 20+, and you are only seeing one.
Re-run writing the debrick image. Sometimes it fails on the first few tries.
Click to expand...
Click to collapse
Tried writing it a few times but will keep trying. Atleast now i know where to look for the partitions to see. Thanks again.
Yeag3r24 said:
Tried writing it a few times but will keep trying. Atleast now i know where to look for the partitions to see. Thanks again.
Click to expand...
Click to collapse
You're not inputting the command to write the image correctly.
The last part should be of=/dev/sdb NOT of=/dev/sdb1. Lose the 1
You really didn't read the hard debrick OPs instructions closely. he explicitly says to ignore the partition number, being the 1, because you are overwriting the current partitions.
Correcting that issue with the command should write the image correctly, and you should be good to go from there
SpikeyPsyche said:
You're not inputting the command to write the image correctly.
The last part should be of=/dev/sdb NOT of=/dev/sdb1. Lose the 1
You really didn't read the hard debrick OPs instructions closely. he explicitly says to ignore the partition number, being the 1, because you are overwriting the current partitions.
Correcting that issue with the command should write the image correctly, and you should be good to go from there.
Click to expand...
Click to collapse
Funny you said that because i did just rewrite it twice without the 1 just as sdb and when i unplugged it and plugged it back into usb i did recieve about 6 pop ups but were all sd card readers showing on my desktop like i had 6 different usb readers with different size sd cards some
Here's the correct screenshot of whole desktop. Also battery was 65% when this all happened but hasn't been used since in last 2 days of trying to fix it so see no need why the battery would be dead, correct? I could have phone on for 2 days and not touch it and wouldn't be dead. Would still be at about 40-50% i would assume if left on untouched for a few days. I just know i could do this and see no reason why this shouldn't work. Do i need the MJ5 img or something since i was on that with unofficial KK on dynamickat?
SS
Yeag3r24 said:
SS
Click to expand...
Click to collapse
It looks like one of the partitions isn't being written correctly on the SD card for some reason.
How many partitions is the fdisk command showing?
SpikeyPsyche said:
It looks like one of the partitions isn't being written correctly on the SD card for some reason.
How many partitions is the fdisk command showing?
Click to expand...
Click to collapse
PaulMichael paul # dd if=/home/paul/Desktop/debrick/Unbrick_SM-N900A.img of=/dev/sdb
400000+0 records in
400000+0 records out
204800000 bytes (205 MB) copied, 74.1923 s, 2.8 MB/s
PaulMichael paul # fdisk -l /dev/sdb
WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sdb1: 31.9 GB, 31910789120 bytes
1 heads, 32 sectors/track, 1947680 cylinders, total 62325760 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1p1 1 61071359 30535679+ ee GPT
Yeag3r24 said:
PaulMichael paul # dd if=/home/paul/Desktop/debrick/Unbrick_SM-N900A.img of=/dev/sdb
400000+0 records in
400000+0 records out
204800000 bytes (205 MB) copied, 74.1923 s, 2.8 MB/s
PaulMichael paul # fdisk -l /dev/sdb
WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sdb1: 31.9 GB, 31910789120 bytes
1 heads, 32 sectors/track, 1947680 cylinders, total 62325760 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1p1 1 61071359 30535679+ ee GPT
Click to expand...
Click to collapse
Now it's back to one partition again. Very strange.
SpikeyPsyche said:
Now it's back to one partition again. Very strange.
Click to expand...
Click to collapse
Well today must be my day. I called to get replacement phone and girl was real cool and said I could just pick one up here locally at the support center. Luckily dude at support center was just as cool and just pretty much swapped it right out without even trying another battery or doing tests. However when he put my battery in replacement Note i stilll had 65% so who knows wtf i did. Lesson learned ... never pull out early when Odin looks like it freezes for a few mins. Just in time for the official KK root now that I'm actually on Official KK stock rom. Thanks again for all your help. Much appreciated!
Yeag3r24 said:
Well today must be my day. I called to get replacement phone and girl was real cool and said I could just pick one up here locally at the support center. Luckily dude at support center was just as cool and just pretty much swapped it right out without even trying another battery or doing tests. However when he put my battery in replacement Note i stilll had 65% so who knows wtf i did. Lesson learned ... never pull out early when Odin looks like it freezes for a few mins. Just in time for the official KK root now that I'm actually on Official KK stock rom. Thanks again for all your help. Much appreciated!
Click to expand...
Click to collapse
No prob. I hope you have better luck in the future.
Please delete.
Sent from my SM-N900A using XDA Free mobile app
N900A 4.4.2, 32GB Unbrick HELP!!!
Yeag3r24 said:
Well today must be my day. I called to get replacement phone and girl was real cool and said I could just pick one up here locally at the support center. Luckily dude at support center was just as cool and just pretty much swapped it right out without even trying another battery or doing tests. However when he put my battery in replacement Note i stilll had 65% so who knows wtf i did. Lesson learned ... never pull out early when Odin looks like it freezes for a few mins. Just in time for the official KK root now that I'm actually on Official KK stock rom. Thanks again for all your help. Much appreciated!
Click to expand...
Click to collapse
Help !!!
I have a N900A, tried to unlock the phone and now is dead.
I would like to know how you solve your problem?
Hi, I recently updated my Amazon Fire 7" 5th Gen tablet to the latest system update & prior to this the tablet had already been rooted when it was running Android 5.0.1, but now the newer update has un-rooted the device and I am having difficulties re-rooting the device as now I am receiving some error messages in the Amazon Fire Tablet CMD Tool and I am unsure about what I have to do to resolve the issue....Below is a copy of the error messages I am receiving:
--------------------------------------------------------------------------------
[*] NOTE this will not work unless your fastboot drivers are installed
[*] see option 1 ADB Driver install.
[*] Once the screen is black and says fastboot in the corner
[*] press and key to continue the script.
--------------------------------------------------------------------------------
...
(bootloader) APPEND KERNEL CMDLINE
OKAY [ 0.016s]
finished. total time: 0.016s
resuming boot...
OKAY [ 0.000s]
finished. total time: 0.000s
--------------------------------------------------------------------------------
[*] your device is rebooting and will inject root files.
--------------------------------------------------------------------------------
remount succeeded
759 KB/s (170232 bytes in 0.218s)
61 KB/s (1976 bytes in 0.031s)
1570 KB/s (75364 bytes in 0.046s)
2984 KB/s (5904943 bytes in 1.931s)
1360 KB/s (29972 bytes in 0.021s)
mkdir failed for /system/app/SuperSU, File exists
mkdir failed for /system/bin/.ext, File exists
cp: /system/xbin/su: Operation not permitted
Unable to chmod /system/xbin/su: Operation not permitted
chcon: Could not label /system/xbin/su with ubject_r:system_file:s0: Operation not permitted
cp: /system/xbin/daemonsu: Text file busy
cp: /system/xbin/supolicy: Operation not permitted
Unable to chmod /system/xbin/supolicy: Operation not permitted
chcon: Could not label /system/xbin/supolicy with ubject_r:system_file:s0: Operation not permitted
cp: /system/bin/app_process32_original: Text file busy
--------------------------------------------------------------------------------
[*] Once the screen is black and says fastboot in the corner
[*] press and key to continue the script.
--------------------------------------------------------------------------------
...
(bootloader) APPEND KERNEL CMDLINE
OKAY [ 0.006s]
finished. total time: 0.007s
resuming boot...
OKAY [ 0.497s]
finished. total time: 0.497s
--------------------------------------------------------------------------------
[*] your device is rebooting and will finish the root process.
--------------------------------------------------------------------------------
Thanks in advance for any help and advice you can give to me.
If you have 5.1.1, the root procedure is a bit different. Start here:
http://forum.xda-developers.com/amazon-fire/help/help-thread-question-noob-friendly-t3205441
shabuboy said:
If you have 5.1.1, the root procedure is a bit different. Start here:
http://forum.xda-developers.com/amazon-fire/help/help-thread-question-noob-friendly-t3205441
Click to expand...
Click to collapse
Thank you shabuboy, I will read through the thread and see if any of the information can help me....:good:
I've read through the links enlisted and watched the tutorials but I've still not been able to root my device as I continue to get the same error message ...I wish now I had not updated to Android 5.1.1 and at this point I think I'm going to give up until the next update or so ....
If you followed the procedures for 5.1.1 and/or used the supertool and still did not work, I would attempt to disable OTAs at the least.
shabuboy said:
If you followed the procedures for 5.1.1 and/or used the supertool and still did not work, I would attempt to disable OTAs at the least.
Click to expand...
Click to collapse
Yes I have disabled the OTAs now, as well as this I also found another XDA user who's having the same problem with he's device: http://forum.xda-developers.com/hd8-hd10/help/looking-help-rooting-kindle-5th-gen-v5-t3285665 & I've contacted him to see if he has found a solution to his, hopefully he'll get back to me.
DeeKay10 said:
Yes I have disabled the OTAs now, as well as this I also found another XDA user who's having the same problem with he's device: http://forum.xda-developers.com/hd8-hd10/help/looking-help-rooting-kindle-5th-gen-v5-t3285665 & I've contacted him to see if he has found a solution to his, hopefully he'll get back to me.
Click to expand...
Click to collapse
Have your tried doing a restore with the 5.1.1 stock firmware before proceeding with the root process?
I may try this option next
I may be forced to try this option next, I'll give a feedback on the results once I've done this although I did factory restore obviously to no avail as once the update has been done it cannot be downgraded....
Good news!!!! I now have full root access/super user privileges
***UPDATE***
I now have full root access to my Amazon device, I think that some of the files that were giving the error messages were corrupted and therefore last night I re-installed/restored the android 5.1.1 firmware to the tablet and this resolved the problem …Thank you both "shabuboy & thekrakah", I much appreciate your contribution to my query and thankfully now my device is operating correctly....
my phone stuck at erecovery mode . i did flash it with new rom using the dc phoenix but it turn out failed.
here is the progress :
Build number: :COR-L29 9.0.0.193(SP53C636E2R1P12)
Model: COR-L29
Battery state: 4885mv
OEM lock state info:
FB LockState: LOCKED
USER LockState: LOCKED
OEM get bootinfo:
locked
Process identifier:18080917
Getting build number...
Getting base version...
Getting cust version...
Getting preload version...
Erasing ver .. .
File size: 5,037,310,948 bytes
Current version(CURVER): CORC00B000
Writing rescue_recovery_kernel partition
rescue_recovery_kernel partition UPDATE ...OK
Writing rescue_recovery_ramdisk partition
rescue_recovery_ramdisk partition UPDATE ...OK
Writing rescue_recovery_vendor partition
rescue_recovery_vendor partition UPDATE ...OK
USB Device REMOVAL
Type: @OEM83.inf,%tplinkfastboot%;Android Bootloader Interface
VidPid: VID_18D1&PID_D00D
Instance id: 5&118960b2&0&2
Looking for device in upgrade mode...
USB Device INSERTION
Type: @OEM148.inf,%busfilter.devicedesc%;USB Composite Device
VidPid: VID_12D1&PID_107E
Instance id: 5&118960b2&0&2
COM11: DBAdapter Reserved Interface (COM11)
COM12: Android Adapter PCUI (COM12)
8/29/2019 3:56:10 PM Starting to write device in UPGRADE mode...
Device found: XTX7N18830004739
8/29/2019 3:56:38 PM start to write update file
File to update: UPDATE_SD.APP
File size: 5,037,310,948 bytes
Current version(CURVER): CORC00B000
Process identifier:18080974
Validating file...
Looking for attached port...
Preparing to write...
Writing file 1 of 43: SHA256RSA...OK
Writing file 2 of 43: CRC...OK
Writing file 3 of 43: CURVER...OK
Writing file 4 of 43: VERLIST...
Error downloading file 4 of 43
Error writing software
8/29/2019 3:57:16 PM Writing device finished with ERROR
anyone can help me with this ?