Related
Feeling brave? Help me test / develop my superboot!
http://android.modaco.com/content/h...9976/13-jan-1-0-superboot-rooting-the-tattoo/
P
sorry, but your batch makes problemm...
and when i make it manual:
C:\Android\superboot>fastboot-windows boot tattoo.superboot.img
downloading 'boot.img'... OKAY
booting...
then nothing
for me doesn't work... i've got mac and the message in terminal is:
./install-superboot-mac.sh: line 3: unexpected EOF while looking for matching `''
./install-superboot-mac.sh: line 14: syntax error: unexpected end of file
and if i try to do the steps inside the script terminal says:
bash-3.2# chmod +x fastboot-mac
bash-3.2# chmod +x adb-mac
bash-3.2# ./adb-mac shell reboot oem-78
error: device not found
bash-3.2# ./fastboot-mac oem-78
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
bash-3.2# ./fastboot-mac boot tattoo.superboot.img
downloading 'boot.img'... FAILED (remote: not allow)
bash-3.2# ./fastboot-mac reboot
rebooting... (here with no reboot)
i hope this could help you...
You could try fastboot oem boot superboot.img allthough I don't think it will work, we have tried this on the Eris but who knows maybe yours will be different
Any advance on this guys?
If you need my help, just tell me, I'm newbie but I love to take risks!
I tried this method on my HTC.
downloading 'boot.img'... OKAY
booting.....
Click to expand...
Click to collapse
I waited for few min nothing happen.so un plug the cable it goes to RUU.
And then i insert the cable it rebooted.
What about this?
i'm New
Did anyone try what I said, "fastboot oem boot superboot.img" make sure you have oem in there otherwise it will just hang at booting..... I'm just curouse if it works for you guys.
I have a feeling there stuck on it same as we are, the tattoo and eris are more alike than either to the hero
binny1007 said:
Did anyone try what I said, "fastboot oem boot superboot.img" make sure you have oem in there otherwise it will just hang at booting..... I'm just curouse if it works for you guys.
Click to expand...
Click to collapse
Yup, tried that. It just boots the phone to it's current (flashed) rom
I tried using the boot command and, while it's hanging at "booting...", I sent a oem boot, but no luck
If it boots to the current flashed rom then it might have worked. you wont notice a physical different if superboot boots.
FireSokar said:
If it boots to the current flashed rom then it might have worked. you wont notice a physical different if superboot boots.
Click to expand...
Click to collapse
Interesting. When I get mine (tattoo), I'll try it out. Superboot just allows us superuser access, doesn't it? If we boot with this, then run a Terminal emulator, type 'su', we'll be able to get root (temporarily)?
Im pretty sure thats how it works, im not 100% sure im following this thread closely as we are stuck @ the exact same point on getting the droid eris rooted, better side of 2 months working on it.
The wait for my HTC Tattoo is killing me. I really want to try this out before I go back to school...
I ordered it last week sometime and it's supposedly coming next week... If it all comes to the worse, I'll just try this at school.... Hehe
Alright, I did this, and I think it may get me somewhere.
I did this while on the home screen, with USB debugging enabled. I ran the mac fastboot script, and it booted into the HTC logo screen. It said "Booting..." and got stuck.
After a minute, I yanked the USB cord out, and it dumped me at the RUU screen with text like this in my Terminal:
Terminal said:
Matthew-Coburns-MacBook:1.2-tattoo-superboot matthew$ ./install-superboot-mac.sh
Superboot for HTC Tattoo by Paul O'Brien @ http://www.MoDaCo.com
----------------------------------------------------------------
Rebooting device...
* daemon not running. starting it now *
* daemon started successfully *
0
Waiting 10 seconds for reboot...
Booting superboot...
ERROR: could not get pipe properties
downloading 'boot.img'... OKAY
booting... ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
ERROR: could not get pipe properties
< waiting for device >
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
Click to expand...
Click to collapse
I then reinserted the USB cable and got this:
rebooting...
Done!
Click to expand...
Click to collapse
After that, I did some exploring with adb-mac:
Matthew-Coburns-MacBook:1.2-tattoo-superboot matthew$ ./adb-mac shell
$ ls
sqlite_stmt_journals
cache
sdcard
etc
system
sys
sbin
proc
logo.rle
init.rc
init.goldfish.rc
init.bahamas.rc
init
default.prop
data
root
dev
$ su
su: permission denied
Click to expand...
Click to collapse
And so, I got the dreaded permission denied error! Oh well, at least I tried...
Any suggestions?
EDIT: I can do 'cat /proc/cpuinfo' and get:
Processor : ARMv6-compatible processor rev 2 (v6l)
BogoMIPS : 244.94
Features : swp half thumb fastmult edsp java
CPU implementer : 0x41
CPU architecture: 6TEJ
CPU variant : 0x1
CPU part : 0xb36
CPU revision : 2
Hardware : bahamas
Revision : 0080
Serial : 0000000000000000
Click to expand...
Click to collapse
Interesting...
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?
My AT&T HTC One (32 GB) that I bought day one keeps rebooting randomly.
From day one, I rooted, unlocked my bootloader, flashed CWM, and installed Android Revolution.
I've since updated up to AR 31.0 without any problem, and have been running that version for quite a few months.
I have never had any problems with Mike's roms on any of my other phones.
Recently, it reboots completely, even when I'm not touching it.
Once booted up, it will revert to a previous state. The same apps will begin to update, I will be notified of the same emails, voicemails, texts, etc.
If I touch it while all this happens, it will reboot again, and do all of the same things.
If I leave it alone until all of this occurs, I might have some luck using the phone in a stable state.
I've not installed anything new recently.
I run Seeder, a few Xposed tweaks, a couple of Sense Toolbox tweaks, and Tasker at root level, but all of these things have been running simultaneously without a problem for months.
This just started happening out of no where.
Again, running AR 31.0, Android 4.3, Sense 5.5. Random reboots.
Any ideas guys?
does this happens on any other ROM?
kamilmirza said:
does this happens on any other ROM?
Click to expand...
Click to collapse
Nope. Never had this happen before. I just wonder how something could have changed without me doing anything.
try any other ROM and see
kamilmirza said:
try any other ROM and see
Click to expand...
Click to collapse
Been trying to.
I've tried to flash the rom cleanly, but it reaches 30% and reboots every time.
I'd flash another rom, but I'm running CWM, and all I seem to find is new roms that require TWRP.
When trying to install TWRP recovery, the phone still boots into CWM.
I have no idea what to do.
fromtheaudible said:
Been trying to.
I've tried to flash the rom cleanly, but it reaches 30% and reboots every time.
I'd flash another rom, but I'm running CWM, and all I seem to find is new roms that require TWRP.
When trying to install TWRP recovery, the phone still boots into CWM.
I have no idea what to do.
Click to expand...
Click to collapse
download TWRP from here
then place it in your adb folder
Boot into HBOOT then Fastboot
From fastboot. Use command "fastboot erase cache"
From fastboot. Use command "fastboot flash recovery recovery_file.img"
Click to expand...
Click to collapse
then reboot your phone into recovery and try any other ROM
---------- Post added at 12:07 AM ---------- Previous post was at 12:04 AM ----------
before all that paste the "fastboot getvar all" (without S/N and IMEI removed) from the bootloader
Tried exactly that twice before you posted it, but still no luck.
Boots into CWM, won't allow full flashes, and still reboots randomly.
Here's the info though:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4237mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.042s
I found the usb read status to be interesting. Maybe that's the issue.
Any idea how to fix that if that's the problem?
have you tried the latest CWM?
kamilmirza said:
have you tried the latest CWM?
Click to expand...
Click to collapse
I'm on CWM 6.0.3.1.
Just tried to flash two different versions of TWRP, and CWM, standard and touch.
None of them stuck when I tried to enter recovery from the bootloader, even though fastboot gave me successful flashes.
Had something similar happen on a nexus ages ago. Internal SD died..
we need a professional here
let's call @nkk71 :fingers-crossed:
kamilmirza said:
we need a professional here
let's call @nkk71 :fingers-crossed:
Click to expand...
Click to collapse
Didn't read much, but
1- CWM 6.0.3.1... r u kidding?
2- 31.0 was released (at first) with w/p kernel, so changes wont stick,
Use 31.6 instead
3- 'random reboots' -> how's your power button?
Go to bootloader, any reboots ->
no -> go to custom recovery -> any reboots?
If yes to any of above, then ur power button is stuck.
Good night...
Sent from my HTC One using Tapatalk
fromtheaudible said:
Tried exactly that twice before you posted it, but still no luck.
Boots into CWM, won't allow full flashes, and still reboots randomly.
Here's the info though:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.042s
I found the usb read status to be interesting. Maybe that's the issue.
Any idea how to fix that if that's the problem?
Click to expand...
Click to collapse
My AT&T HTC One (32 GB) that I bought day one keeps rebooting randomly.
Click to expand...
Click to collapse
okay, just reread, so a couple of questions:
1- So you had this problem from day 1? and didnt think of exchanging it?
2- what OS you running (Win7, mac, etc)
Code:
(bootloader) version-main:
3- what did you try to flash (any firmware)??
Code:
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
4- have you tried restoring to stock using RUU_1.26.502.12_PN0712000_CWS__001_4A.14.3250.13
5- The random reboots, could indicate a hardware problem and/or corrupted partition(s), you could check those by opening a shell while in custom recovery (CWM or TWRP), and check the output:
Code:
C:\...> [B]adb devices[/B]
List of devices attached
H*********** recovery <- yep it's in recovery
C:\...> [B]adb shell
umount /system
umount /data
umount /sdcard
umount /cache[/B]
[B]e2fsck -n -v -f /dev/block/mmcblk0p35[/B] <- this checks /system
[B]e2fsck -n -v -f /dev/block/mmcblk0p36[/B] <- this checks /cache
[B]e2fsck -n -v -f /dev/block/mmcblk0p37[/B] <- this checks /data
if there are no major errors then output will look something like this:
[HIDE]~ # e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
39356 inodes used (2.31%)
350 non-contiguous files (0.9%)
31 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 38933/54
4696398 blocks used (68.91%)
0 bad blocks
1 large file
36560 regular files
2426 directories
0 character device files
0 block device files
0 fifos
0 links
357 symbolic links (357 fast symbolic links)
4 sockets
--------
39347 files[/HIDE]
if there [B]are [/B]major error, then output will look something like this:
[HIDE]~# e2fsck -v -f /dev/block/mmcblk0p37
e2fsck -v -f /dev/block/mmcblk0p37
e2fsck 1.41.11 (14-Mar-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p37
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>[/HIDE]
In response to your post:
1. Haven't had the problem from day one. This just started occurring. I've had the device since day 1.
2. I run Windows 7, and Mac OSX 10.9 on separate computers. I've got options.
3. I have tried running the RUU you linked. No dice. Image versions don't match up and won't allow me to push the stock rom. I've tried another that had a closer image version, and also tried a world wide edition. No luck.
My image version is 3.62.401.1
4. Here is my adb shell log:
Code:
localhost:~ ****$ adb devices
List of devices attached
HT34GW905119 recovery
localhost:~ ****$ adb shell
~ # umount /system
umount: can't umount /system: Invalid argument
~ # umount /data
~ # umount /sdcard
umount: can't umount /sdcard: Invalid argument
~ # umount /cache
~ # e2fsck -n -v -f /dev/block/mmcblk0p35
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 31691 has zero dtime. Fix? no
Deleted inode 31907 has zero dtime. Fix? no
Deleted inode 31908 has zero dtime. Fix? no
Deleted inode 79295 has zero dtime. Fix? no
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(133064--133066) -(148739--148743) -(154603--154607) -(341749--342089)
Fix? no
Free blocks count wrong for group #4 (1802, counted=1797).
Fix? no
Free blocks count wrong (125515, counted=125510).
Fix? no
Inode bitmap differences: -31691 -(31907--31908) -79295
Fix? no
Free inodes count wrong for group #4 (7691, counted=7690).
Fix? no
Free inodes count wrong (116323, counted=116322).
Fix? no
/dev/block/mmcblk0p35: ********** WARNING: Filesystem still has errors **********
2477 inodes used (2.09%)
21 non-contiguous files (0.8%)
2 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 2171
349620 blocks used (73.58%)
0 bad blocks
0 large files
2091 regular files
79 directories
0 character device files
0 block device files
0 fifos
0 links
295 symbolic links (295 fast symbolic links)
0 sockets
--------
2465 files
~ # e2fsck -n -v -f /dev/block/mmcblk0p36
e2fsck 1.41.14 (22-Dec-2010)
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
21 inodes used (0.05%)
1 non-contiguous file (4.8%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 13
5719 blocks used (3.49%)
0 bad blocks
0 large files
8 regular files
4 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
12 files
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck 1.41.14 (22-Dec-2010)
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix? no
Inode 254019 was part of the orphaned inode list. IGNORED.
Inode 254153 was part of the orphaned inode list. IGNORED.
Deleted inode 255336 has zero dtime. Fix? no
Inode 255428 was part of the orphaned inode list. IGNORED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -1016475 -(2083011--2083012) -2178670 -2178844 -2180689 +2186831
Fix? no
Free blocks count wrong for group #58 (5718, counted=5716).
Fix? no
Free blocks count wrong for group #63 (21182, counted=21181).
Fix? no
Free blocks count wrong (2577130, counted=1786950).
Fix? no
Inode bitmap differences: -254019 -254153 -255336 -255428
Fix? no
Free inodes count wrong for group #30 (5628, counted=5618).
Fix? no
Free inodes count wrong for group #31 (5994, counted=5963).
Fix? no
Free inodes count wrong for group #116 (6273, counted=6272).
Fix? no
Free inodes count wrong for group #117 (6642, counted=6497).
Fix? no
Free inodes count wrong for group #160 (7948, counted=7947).
Fix? no
Free inodes count wrong (1679719, counted=1674260).
Fix? no
/dev/block/mmcblk0p37: ********** WARNING: Filesystem still has errors **********
24217 inodes used (1.42%)
1679 non-contiguous files (6.9%)
39 non-contiguous directories (0.2%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 29119/223
4238614 blocks used (62.19%)
0 bad blocks
1 large file
27526 regular files
1815 directories
0 character device files
0 block device files
0 fifos
0 links
313 symbolic links (313 fast symbolic links)
9 sockets
--------
29663 files
Didn't see anything there that looked like a corrupt partition. But I haven't had success unmounting system or sdcard.
To respond to an earlier post, power button is fine. Bootloader and recovery never reboot. First thing I noticed.
Maybe too low voltage?
Or http://android-revolution-hd.blogspot.ch/2013/10/fix-data-htc-one.html ?
fromtheaudible said:
1. Haven't had the problem from day one. This just started occurring. I've had the device since day 1.
Click to expand...
Click to collapse
ah, ok my bad, i misunderstood.
2. I run Windows 7, and Mac OSX 10.9 on separate computers. I've got options.
Click to expand...
Click to collapse
Windows 7 should do nicely.
3. I have tried running the RUU you linked. No dice. Image versions don't match up and won't allow me to push the stock rom. I've tried another that had a closer image version, and also tried a world wide edition. No luck.
My image version is 3.62.401.1
Click to expand...
Click to collapse
I think above refers to your ROM, cause your "(bootloader) version-main: " (ie firwmare) is blank, and since you're on hboot 1.44 + radio 4A.14.3250.13 should equal the RUU I posted earlier.
but nevermind for now
Didn't see anything there that looked like a corrupt partition. But I haven't had success unmounting system or sdcard.
Click to expand...
Click to collapse
it won't unmount if it's already umounted, so that was not really an error
/dev/block/mmcblk0p35: ********** WARNING: Filesystem still has errors **********
/dev/block/mmcblk0p37: ********** WARNING: Filesystem still has errors **********
Click to expand...
Click to collapse
and there we go , the plot thickens, both /system and /data have some corruptions, not completely unmountable but also not completely clean, which would be a good reason you're experiencing problems.
the one thing i'm concerned about it that the problem is with both /system and /data, which may indicate a hardware fault.
we can go ahead and perform a "real" format (as opposed to wipe) of these partitions, if the formatting sticks (ie without filesystem errors coming up again), then it could just be a software issue.
Let me know if you want to proceed? (if you are going to format /system and /data), you need to be comfy with adb shell, adb push and/or adb sideload)
PS: I may need to offline in about 20mins, and could be back in a few (probably like 3+) hours or so
nkk71 said:
ah, ok my bad, i misunderstood.
Windows 7 should do nicely.
I think above refers to your ROM, cause your "(bootloader) version-main: " (ie firwmare) is blank, and since you're on hboot 1.44 + radio 4A.14.3250.13 should equal the RUU I posted earlier.
but nevermind for now
it won't unmount if it's already umounted, so that was not really an error
and there we go , the plot thickens, both /system and /data have some corruptions, not completely unmountable but also not completely clean, which would be a good reason you're experiencing problems.
the one thing i'm concerned about it that the problem is with both /system and /data, which may indicate a hardware fault.
we can go ahead and perform a "real" format (as opposed to wipe) of these partitions, if the formatting sticks (ie without filesystem errors coming up again), then it could just be a software issue.
Let me know if you want to proceed? (if you are going to format /system and /data), you need to be comfy with adb shell, adb push and/or adb sideload)
PS: I may need to offline in about 20mins, and could be back in a few (probably like 3+) hours or so
Click to expand...
Click to collapse
That's what I gathered I'd have to do once LibertyMarine linked that forum post from Mike1986.
I'm all for it.
fromtheaudible said:
That's what I gathered I'd have to do once LibertyMarine linked that forum post from Mike1986.
I'm all for it.
Click to expand...
Click to collapse
i've done it with other users 3 or 4 times successfully, and 1 failure because of the filesystem errors kept coming back and back and back = hardware problem.
so have you read @mike1986. thread? you comfy with it?
here goes:
1- download this: http://goo.gl/pmZ9Mt and place it in your adb/fastboot folder
2- in recovery:
Code:
[B]adb push mkfs.ext4 /tmp/
adb shell
chmod 777 /tmp/mkfs.ext4
umount /data
umount /sdcard
umount /system
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p35
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37
[/B]
you can see the expected output in mike's blog: http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html
Code:
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
1703936 inodes, 6815744 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
208 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768,98304,163840,229376,294912,819200,884736,1605632,2654208,4096000
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 25 mounts or 180 days, whichever comes first.
Use tune2fs -c or -i to override.
if that goes all well, continue in the shell:
Code:
[B]mount /data
mkdir -p /data/media/0
exit[/B]
then push your rom:
adb push rom.zip /data/media/0/ <- this will take 5 mins or so with no progress showing until finished
then install your rom in recovery, and hope for the best, stay away from 4.4 (KitKat) ROMs for now, because of recovery version (BTW: which one and version do you have?)
No working mirror for mkfs.ext4 file. :/
fromtheaudible said:
No working mirror for mkfs.ext4 file. :/
Click to expand...
Click to collapse
working here: http://www.androidrevolution.nl/downloader/download.php?file=mkfs.ext4
otherwise i'll upload it to my dropbox.
I am attempting to use Heimdall (with the S5 patch) with my Note 4 in Xubuntu 14.10, but I keep getting the following error:
Code:
Initialising protocol...
ERROR: Failed to receive handshake response. Result: -7
ERROR: Protocol initialisation failed!
In a clean install of Xubuntu 14.10 I did the following:
Code:
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-uprade -y
sudo apt-get install android-tools-adb build-essential git libudev-dev pkg-config zlib1g-dev
sudo wget https://raw.githubusercontent.com/snowdream/51-android/master/51-android.rules -O /etc/udev/rules.d/51-android.rules
sudo chmod a+r /etc/udev/rules.d/51-android.rules
sudo service udev restart
mkdir ~/.source
cd ~/.source
wget 'http://sourceforge.net/projects/libusb/files/libusb-1.0/libusb-1.0.19/libusb-1.0.19.tar.bz2'
tar -vxjf libusb-1.0.19.tar.bz2
rm libusb-1.0.19.tar.bz2
cd libusb-1.0.19
./configure
make
sudo make install
cd ~/.source
git clone https://github.com/sshimko/Heimdall.git --branch gs5 --single-branch heimdall-gs5
cd heimdall-gs5/libpit
./configure
make
cd ../heimdall
./configure
make
sudo make install
sudo udevadm control --reload-rules
adb reboot download
heimdall print-pit --verbose
Here is the result of "heimdall print-pit --verbose":
Code:
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "Sasmsung"
Product: "MSM8960"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 0100
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 82
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
ERROR: Failed to receive handshake response. Result: -7
ERROR: Protocol initialisation failed!
Releasing device interface...
Re-attaching kernel driver...
Does anyone who has been able to use Heimdall with the Note 4 in Linux have any suggestions as to how I can get this setup correctly?
Thanks.
I had the same results with https://github.com/karabijavad/Heimdall/tree/issue-197 and https://github.com/Benjamin-Dobell/Heimdall/issues/232.
Did you ever figure this out? I'm getting the same "Failed to send request to end PIT file transfer!" error.
As far as i I know, there's only so much heimdall can do. I've only had success on windows for flashing the full firmware. I'm on Linux mint and I'm still not sure. You could try jodin on this site. It's a web based Odin.
Jodin uses Heimdall, so it doesn't fix the problem. On windows I couldn't get the stupid Samsung drivers to work.
Sent from my SM-N910T using XDA Free mobile app
DieHappy said:
I am attempting to use Heimdall (with the S5 patch) with my Note 4 in Xubuntu 14.10, but I keep getting the following error:
Code:
Initialising protocol...
ERROR: Failed to receive handshake response. Result: -7
ERROR: Protocol initialisation failed!
In a clean install of Xubuntu 14.10 I did the following:
Code:
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-uprade -y
sudo apt-get install android-tools-adb build-essential git libudev-dev pkg-config zlib1g-dev
sudo wget https://raw.githubusercontent.com/snowdream/51-android/master/51-android.rules -O /etc/udev/rules.d/51-android.rules
sudo chmod a+r /etc/udev/rules.d/51-android.rules
sudo service udev restart
mkdir ~/.source
cd ~/.source
wget 'http://sourceforge.net/projects/libusb/files/libusb-1.0/libusb-1.0.19/libusb-1.0.19.tar.bz2'
tar -vxjf libusb-1.0.19.tar.bz2
rm libusb-1.0.19.tar.bz2
cd libusb-1.0.19
./configure
make
sudo make install
cd ~/.source
git clone https://github.com/sshimko/Heimdall.git --branch gs5 --single-branch heimdall-gs5
cd heimdall-gs5/libpit
./configure
make
cd ../heimdall
./configure
make
sudo make install
sudo udevadm control --reload-rules
adb reboot download
heimdall print-pit --verbose
Here is the result of "heimdall print-pit --verbose":
Code:
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "Sasmsung"
Product: "MSM8960"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 0100
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 82
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
ERROR: Failed to receive handshake response. Result: -7
ERROR: Protocol initialisation failed!
Releasing device interface...
Re-attaching kernel driver...
Does anyone who has been able to use Heimdall with the Note 4 in Linux have any suggestions as to how I can get this setup correctly?
Thanks.
Click to expand...
Click to collapse
Did you put it to work?
BR
I have not been able to get it to work with my Note 4.
Sent from my SM-N910T using XDA Free mobile app
I am currently running into the same problems as well
Nobody has a fix yet.
Hi,
First OP, so be gentle!
Please help. I'm trying to install Remix OS Player directly in Windows 10 and I get this message. I'm using a Dell Latitude 11 tablet; m5 processor, 8GB RAM, plenty of storage.
Error message:
emulator: WARNING: userdata partition is resized from 550 M to 3900 M
Hax is enabled
Hax ram_size 0xc0000000
HAX is working and emulator runs in fast virt mode.
ERROR: resizing partition e2fsck failed with exit code 8
emulator: Listening for console connections on port: 5554
emulator: Serial number of this emulator (for ADB): emulator-5554
*** BUG ***
In create_bits_image_internal: The expression bits == NULL || (rowstride_bytes % sizeof (uint32_t)) == 0 was false
Set a breakpoint on '_pixman_log_error' to debug
Assertion failed!
Program: C:\RemixOSPlayer\remixemu\tools\qemu\windows-x86_64\qemu-system-x86_64.exe
File: /var/lib/jenkins/jobs/workspace/build-remixemu-emulator-executable/emulator/external/qemu-android/ui/console.c, Line 1276
Expression: surface->image != NULL
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Any suggestions please? Apologies in advance if I'm being stupid. Or if someone could point me in the direction of a step-by-step guide, that would be great.
Thanks.