Develop Bugs

[Q] Root fail help

First I searched for a help thread and this is my last resort.
this morning i tried to root my evo using this guide http://forum.xda-developers.com/showthread.php?t=838448
log >
It failed
------------ AutoRoot.bat Begin - v2.2 - Sun 02/06/2011 17:09:19.48
------------
Params=1'' 2'' 3'' 4'' 5'' 6''
Phone SN is HT0CWHL07773
Checking for ADB...
PLEN='1' PSTATE='device' RETURNTO='start' STEP='start'
PING ADB State Changed '1' out of '1'. ADB State is 'device' expected 'device'
Found the phone connected as 'device'.
Checking MTD configuration...
dev: size erasesize name
mtd0: 00c00000 00040000 "wimax"
mtd1: 00100000 00040000 "misc"
mtd2: 00480000 00040000 "recovery"
mtd3: 00340000 00040000 "boot"
mtd4: 15e00000 00040000 "system"
mtd5: 0a000000 00040000 "cache"
mtd6: 1aa00000 00040000 "userdata"
'check.bat mtd' returned 'new'
MTD data being saved for phone 'HT0CWHL07773'
'dev: size erasesize name mtd0: 00c00000 00040000 "wimax" mtd1:
00100000 00040000 "misc" mtd2: 00480000 00040000 "recovery" mtd3:
00340000 00040000 "boot" mtd4: 15e00000 00040000 "system" mtd5:
0a000000 00040000 "cache" mtd6: 1aa00000 00040000 "userdata" '
Firmware version '3.70.651.1'
Version Major '3'
Version Minor '70'
Battery is at 100 percent.
Checking for root...
UID is 'shell'
Installing exploit...
pkg: /data/local/tmp/AutoRoot.apk
Success
1364 KB/s (767044 bytes in 0.549s)
adb: Product directory not specified; use -p or define ANDROID_PRODUCT_OUT
Sending Intent...
Starting: Intent { act=android.intent.action.MAIN
cmp=com.autoroot.getroot/.getroot }
Checking for root...
UID is 'shell'
Checking for root...
UID is 'Got Root!'
Checking for needed files...
Pushing res\flash_image to /data/local/flash_image...
1375 KB/s (76044 bytes in 0.054s)
Pushing res\mtd-eng.img to /sdcard/mtd-eng.img...
2490 KB/s (655360 bytes in 0.257s)
Pushing res\URFSOFF.zip to /sdcard/URFSOff.zip...
2929 KB/s (225014 bytes in 0.075s)
Pushing res\URFSON.zip to /sdcard/URFSOn.zip...
2447 KB/s (225551 bytes in 0.090s)
Pushing res\PC36IMG_UD.zip to /sdcard/PC36IMG.zip...
1577 KB/s (179274182 bytes in 110.963s)
Flashing misc partition...
Rebooting in to bootloader...
Verifying bootloader status...
hBoot version '2.10.0001'
Version Major '2'
Version Minor '10'
Bootloader shows Firmware version '1.17.651.1'
Version Major '1'
Version Minor '17'
hbpreupdate set at '11'
Security is 'on'
Waiting on operator to flash the PC36IMG.zip and reboot into the recovery.
Checking for ADB...
PLEN='1250' PSTATE='recovery' RETURNTO='b2recovery' STEP='recoveryboot'
PING ADB State Changed '1' out of '1250'. ADB State is 'fastboot'
expected 'recovery'
PING ADB State Changed '357' out of '1250'. ADB State is
'disconnected' expected 'recovery'
PING ADB State Changed '362' out of '1250'. ADB State is 'recovery'
expected 'recovery'
Found the phone connected as 'recovery'.
Found the Recovery, proceeding to makenandroid...
Pushing amon_ra_1.8-mod to /...
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
Recovery type is 'stock'
adb server is out of date. killing...
* daemon started successfully *
- exec '/system/bin/sh' failed: No such file or directory (2) -
phone showes s-on
hboot-2.10.0001
radio-2.15.00.11.19
try to boot get the evo red ! screen
I know now that I need to run the ruu to restore it. so I fond this http://forum.xda-developers.com/showthread.php?t=874251
what do I do with these files how do I "run the ruu"
bricked phone here please help, my searches are sending me in circles. if someone could point me in the right diretion that would be much appreciated

run the ruu.exe on your computer and should work from there

i dont have a ruu.exe does this "ruu.exe" have to be version specific?
further more where can i find a ruu.exe, and what mode should the phone be in to use the ruu.exe?

Hetrochromia said:
i dont have a ruu.exe does this "ruu.exe" have to be version specific?
further more where can i find a ruu.exe, and what mode should the phone be in to use the ruu.exe?
Click to expand...
Click to collapse
You can find the ruu in the same post that you downloaded that from. It should have given you instructions on exactly what to do when it failed as well. You just download it and run it.

ok thanks
fond the ruu here "cant post forum rules"
RUU to restore 3.70.651.1
turned phone on with power vol down
selected hboot USB
phone connects to pc
device manager shows "android bootloader interface"
run ruu.exe
error 170 can not find phone
tried this next
turned phone on with power vol down
selected recovery
phone shows red !
phone connects to pc
device manager shows "MY HTC"
run ruu.exe
error 170 can not find phone
any input?

dont select recovery just run it like that

When in the bootloader select fastboot, it should then change from hboot in blue to fastboot usb in red. Once you see that it should recognize your phone.
It looks like something was interfering with it talking to your phone, pdanet and apps like that can cause it but usually it's easier to just try with a different computer.
Sent from my PC36100 using XDA App

thanks that did it
now im going to do a fresh install of windows 7 on a laptop and retry the root

AutoRoot Failed - now phone consantly resets, cant charge, and cant see SD card

So I just got a brand new HTC Evo replacement because my old one had power button issues.
I tried using Universal AutoRoot 2.5. CMD closed and I got this output:
"------------ AutoRoot.bat Begin - v2.5 - Tue 06/07/2011 23:33:14.63 ------------
Params=1'' 2'' 3'' 4'' 5'' 6''
Working Directory is 'C:\Users\Mark\Desktop\AutoRoot_v2.5\'. Admin='true'
Clearing Temp Files...
The directory name is invalid.
---------
INFO: No tasks are running which match the specified criteria.
INFO: No tasks are running which match the specified criteria.
INFO: No tasks are running which match the specified criteria.
INFO: No tasks are running which match the specified criteria.
---------
Phone SN is HT15AHL06321
PING ADB State Changed '1' out of '0'. ADB State is 'device' expected 'device'
Checking MTD configuration...
dev: size erasesize name
mtd0: 00c00000 00020000 "wimax"
mtd1: 000a0000 00020000 "misc"
mtd2: 00480000 00020000 "recovery"
mtd3: 00300000 00020000 "boot"
mtd4: 15e00000 00020000 "system"
mtd5: 0a000000 00020000 "cache"
mtd6: 1aba0000 00020000 "userdata"
'check.bat mtd' returned 'old'
MTD data being saved for phone 'HT15AHL06321'
'dev: size erasesize name mtd0: 00c00000 00020000 "wimax" mtd1: 000a0000 00020000 "misc" mtd2: 00480000 00020000 "recovery" mtd3: 00300000 00020000 "boot" mtd4: 15e00000 00020000 "system" mtd5: 0a000000 00020000 "cache" mtd6: 1aba0000 00020000 "userdata" '
EVO Branding 'sprint'
Firmware version '3.70.651.1'
Version Major '3'
Version Minor '70'
Battery is at 70 percent.
Checking for root...
UID is 'shell'
Installing exploit...
pkg: /data/local/tmp/AutoRoot.apk
Success
1593 KB/s (767044 bytes in 0.470s)
adb: Product directory not specified; use -p or define ANDROID_PRODUCT_OUT
Sending Intent...
Starting: Intent { act=android.intent.action.MAIN cmp=com.autoroot.getroot/.getroot }
Checking for root...
UID is 'Got Root!'
Checking for needed files...
Pushing res\mtd-eng.img to /sdcard/mtd-eng.img...
1570 KB/s (655360 bytes in 0.407s)
Pushing res\URFSOFF.zip to /sdcard/URFSOff.zip...
1255 KB/s (225014 bytes in 0.175s)
Pushing res\URFSON.zip to /sdcard/URFSOn.zip...
1159 KB/s (225551 bytes in 0.190s)
Dumping WiMAX partition...
rm failed for -s, Read-only file system
1522 KB/s (12582912 bytes in 8.070s)
WiMAX partition saved as 'HT15AHL06321_wimax.img'
Backing up Apps...
pull: building file list...
0 files pulled. 0 files skipped.
The system cannot find the path specified.
Flashing misc partition...
mtd: read all-zero block at 0x00000000; skipping
mtd: not writing bad block at 0x00080000
error writing misc: No space left on device
Rebooting in to bootloader...
Verifying bootloader status...
hBoot version '2.10.0001'
Version Major '2'
Version Minor '10'
Bootloader shows Firmware version 'ECHO'
Version Major 'ECHO'
Version Minor '' "
----------------------------------------
Now everytime i try to use my phone while it's on:
It doesnt charge while its on
I cant see SD card within the stock ROM
Phone constantly resets after about a minute
However in bootloader i can see the SD card, and the phone charges while its off. I ran the 3.70 RUU which went smoothly, however it did not fix anything =/
Any other ideas? is there a reason why my AutoRoot failed? I've rooted many HTC evo's and never had this problem/problems.

bigblueshock said:
So I just got a brand new HTC Evo replacement because my old one had power button issues.
I tried using Universal AutoRoot 2.5. CMD closed and I got this output:
"------------ AutoRoot.bat Begin - v2.5 - Tue 06/07/2011 23:33:14.63 ------------
Params=1'' 2'' 3'' 4'' 5'' 6''
Working Directory is 'C:\Users\Mark\Desktop\AutoRoot_v2.5\'. Admin='true'
Clearing Temp Files...
The directory name is invalid.
---------
INFO: No tasks are running which match the specified criteria.
INFO: No tasks are running which match the specified criteria.
INFO: No tasks are running which match the specified criteria.
INFO: No tasks are running which match the specified criteria.
---------
Phone SN is HT15AHL06321
PING ADB State Changed '1' out of '0'. ADB State is 'device' expected 'device'
Checking MTD configuration...
dev: size erasesize name
mtd0: 00c00000 00020000 "wimax"
mtd1: 000a0000 00020000 "misc"
mtd2: 00480000 00020000 "recovery"
mtd3: 00300000 00020000 "boot"
mtd4: 15e00000 00020000 "system"
mtd5: 0a000000 00020000 "cache"
mtd6: 1aba0000 00020000 "userdata"
'check.bat mtd' returned 'old'
MTD data being saved for phone 'HT15AHL06321'
'dev: size erasesize name mtd0: 00c00000 00020000 "wimax" mtd1: 000a0000 00020000 "misc" mtd2: 00480000 00020000 "recovery" mtd3: 00300000 00020000 "boot" mtd4: 15e00000 00020000 "system" mtd5: 0a000000 00020000 "cache" mtd6: 1aba0000 00020000 "userdata" '
EVO Branding 'sprint'
Firmware version '3.70.651.1'
Version Major '3'
Version Minor '70'
Battery is at 70 percent.
Checking for root...
UID is 'shell'
Installing exploit...
pkg: /data/local/tmp/AutoRoot.apk
Success
1593 KB/s (767044 bytes in 0.470s)
adb: Product directory not specified; use -p or define ANDROID_PRODUCT_OUT
Sending Intent...
Starting: Intent { act=android.intent.action.MAIN cmp=com.autoroot.getroot/.getroot }
Checking for root...
UID is 'Got Root!'
Checking for needed files...
Pushing res\mtd-eng.img to /sdcard/mtd-eng.img...
1570 KB/s (655360 bytes in 0.407s)
Pushing res\URFSOFF.zip to /sdcard/URFSOff.zip...
1255 KB/s (225014 bytes in 0.175s)
Pushing res\URFSON.zip to /sdcard/URFSOn.zip...
1159 KB/s (225551 bytes in 0.190s)
Dumping WiMAX partition...
rm failed for -s, Read-only file system
1522 KB/s (12582912 bytes in 8.070s)
WiMAX partition saved as 'HT15AHL06321_wimax.img'
Backing up Apps...
pull: building file list...
0 files pulled. 0 files skipped.
The system cannot find the path specified.
Flashing misc partition...
mtd: read all-zero block at 0x00000000; skipping
mtd: not writing bad block at 0x00080000
error writing misc: No space left on device
Rebooting in to bootloader...
Verifying bootloader status...
hBoot version '2.10.0001'
Version Major '2'
Version Minor '10'
Bootloader shows Firmware version 'ECHO'
Version Major 'ECHO'
Version Minor '' "
----------------------------------------
Now everytime i try to use my phone while it's on:
It doesnt charge while its on
I cant see SD card within the stock ROM
Phone constantly resets after about a minute
However in bootloader i can see the SD card, and the phone charges while its off. I ran the 3.70 RUU which went smoothly, however it did not fix anything =/
Any other ideas? is there a reason why my AutoRoot failed? I've rooted many HTC evo's and never had this problem/problems.
Click to expand...
Click to collapse
Well, I unfortunately don't have any experience with the Auto Root method. Hopefully xHausx will chime in here. Out of curiosity, your replacement phone did indeed have 2.2 on it, right? Because if it was updated to the OTA 2.3.3 that root method won't work. What is your software and hboot version?
Perhaps try running the RUU again?
I believe there is a thread around by Calkulin which addresses the issue of the phone not reading the sd card and not charging. I will see if I can dig that up for you. Good luck.
EDIT: Here is that thread by calkulin. I'm not sure if this will be able to help you out or not, but you can go through it anyways. When you boot to your bootloader, does it show S on or S off? What is the version number?

Flashing misc partition...
mtd: read all-zero block at 0x00000000; skipping
mtd: not writing bad block at 0x00080000
error writing misc: No space left on device
Click to expand...
Click to collapse
Your phone had some bad blocks there, that's strange for a new one. I can help you try to fix it but tbh your best bet is to run the 3.70 ruu and take it back for another. Otherwise odds are it'll start doing this again somewhere down the line.

xHausx said:
Your phone had some bad blocks there, that's strange for a new one. I can help you try to fix it but tbh your best bet is to run the 3.70 ruu and take it back for another. Otherwise odds are it'll start doing this again somewhere down the line.
Click to expand...
Click to collapse
Thanks Haus. Yea very odd... It's a brand new sealed 0004 model. I hope it's just luck of the straw. I'm going to head back to sprint later and get it replaced again. I just hope not all the new 0004's are like this. They dont have any refurbs in stock so they had to send me a brand new one.

bigblueshock said:
Thanks Haus. Yea very odd... It's a brand new sealed 0004 model. I hope it's just luck of the straw. I'm going to head back to sprint later and get it replaced again. I just hope not all the new 0004's are like this. They dont have any refurbs in stock so they had to send me a brand new one.
Click to expand...
Click to collapse
You should be good with another one, I've only had maybe 4 or 5 people have this happen before and up until now they were all refurbs. Just luck of the draw I guess.
edit: btw that speedtest result is sick, I would love to have a ping like that

The phone had stock 3.70 2.2 froyo. Phone is s-on with 2.10 bootloader, never got that far to get it s off
And yeah, too bad i just graduated from school, no more 100mbit pipe for me, was nice while it lasted

bigblueshock said:
The phone had stock 3.70 2.2 froyo. Phone is s-on with 2.10 bootloader, never got that far to get it s off
And yeah, too bad i just graduated from school, no more 100mbit pipe for me, was nice while it lasted
Click to expand...
Click to collapse
2.10 bootloader should work, it is the 2.19 one i believe that is locked.

So sprint swapped out the phone at the store. I'm pretty excited, he gave me a brand new White evo =)
I got home and autoroot worked flawlessly! Thanks again Haus for all your support and easy rooting techniques.
I'm not sure if this is the possible reason for my old phone bricking like that, but I'd like to share some knowledge.
My original 0004 model that sprint sent me was brand new, as well as the white evo 0004 sprint gave me was also brand new. While attempting to root the first replacement, 'check.bat mtd' returned 'old'. The second replacement white evo returned as "new". Not that i think it matters, but they both came with 2.10 bootloader and 3.70 base.
I have a strange feeling the first replacement had new block size, but for some reason a bug marked it as having the old block size. I just dont see how a brand new just made 0004 evo would have the old block size.
Could this have been the culprit?

[Q]How to get boot.img and recovery.img

Hi.
I'd like to get boot.img and recovery.img from my Acro(Arc)
I read this 'how to'.
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
But I could not get same result.
Please tell me how to get it.

Recovery & boot are held on the same partition. So there is only one "boot.img".
Sent from my R800i using Tapatalk

Thank you.
I understood it.
But I can't find that partition.
Code:
~ # cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 13880000 00020000 "system"
mtd1: 00a00000 00020000 "appslog"
mtd2: 0e100000 00020000 "cache"
mtd3: 17c00000 00020000 "userdata"
How is it done?

[Q] Desire Partitions

I am trying to get a handle on the NAND partitioning in Desire out of curiosity.
Desire has got 512 MB ROM and after flashing hboots I realized that things are not adding up.
1. I had set up my hboot as follows:-
cache - 5 MB
System - 150 MB
Data - 282 MB
Total - 437 MB
So where is the Balance 512-437=75MB ?
Click to expand...
Click to collapse
2. OK lets take the other partitions like misc, recovery and boot into the calculations. I typed cat /proc/mtd and got:-
dev: size erasesize name
mtd0: 000a0000 00020000 "misc"
mtd1: 00480000 00020000 "recovery"
mtd2: 00300000 00020000 "boot"
mtd3: 09600000 00020000 "system"
mtd4: 00500000 00020000 "cache"
mtd5: 11aa0000 00020000 "userdata"
Click to expand...
Click to collapse
Total size 1bdc0000hex is equal to 445.75MB
Still balance 512-445.75=66.25MB unaccounted for.
3. Time to dig a bit deeper. I got hold of some useful commands using 'fastboot oem h' one of them being fastboot oem listpartition.
listpartition gives this data(formatted):-
Partition Blocks Size(Hex) MB
radio: 497 3E20000 62.125
hboot: 6 C0000 0.75
sp2: 7 E0000 0.875
mfg: 6 C0000 0.75
sp1: 9 120000 1.125
wifi: 5 A0000 0.625
recovery: 36 480000 4.5
boot: 24 300000 3
system: 1200 9600000 150
cache: 40 500000 5
userdata: 2261 11AA0000 282.625
misc: 5 A0000 0.625
4096 20000000 512
Click to expand...
Click to collapse
When you add up the MB column you get the magic figure 512MB. Fine. But I have got more questions now after I see the listpartition output:-
A. I thought that hboot and radios being so special are in seperate areas compared to say data or system partitions. But from this table it looks apparently that they are in the same contiguous memory. So is everything in the same area/chip?
B. The radio and wifi partitions are seperate. So does flashing radio only affect 2G/3G?
C. What is sp1, sp2 or mfg partitions?

Some questions answered. hboot and radio and I guess almost everything else is on NAND chip called MCP(Multi Chip Package) from Samsung. The only reason hboot and radio are special is because radio is the bootloader for the modem processor whereas the hboot is the bootloader for the application processor. The Desire contains a Qualcom SOC (System on Chip) which has these processors. So if either the application or the modem processor cannot boot due to hboot or radio image corruption then thats it , your desire is bricked.
The sp1 and sp2 partitions house the splash1 and splash2 splash screens. The mfg partition houses the MFG_DIAG image ?? The wifi partition is seperate from radio. But who uses the wifi partition?
Is it possible to access these hidden partitions? I did some digging. The very first requirement is to find out the starting address and size on NAND for each of these partitions. You get some data from 'fastboot oem listpartition' and some more data from 'dmesg'. You got to do some mathematics and at the end of it you get this neat table.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For accessing the hidden partitions like radio,hboot,sp1,sp2,mfg and wifi you will need to change the kernel commandline. It is quite simple actually. All you need to do is keep a recovery image handy and get into fastboot mode. The idea is to boot the desire with a alternate kernel which you supply during fastboot.
example:-
Without Kernel Commandline
C:\sdktools-toolsonly\android-sdk-windows\tools>fastboot boot recovery-clockwork-5.0.2.0-bravo.img
Click to expand...
Click to collapse
Now you will be in cwm 5 recovery
C:\sdktools-toolsonly\android-sdk-windows\tools>adb shell
~ # cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 000a0000 00020000 "misc"
mtd1: 00480000 00020000 "recovery"
mtd2: 00300000 00020000 "boot"
mtd3: 09600000 00020000 "system"
mtd4: 00500000 00020000 "cache"
mtd5: 11aa0000 00020000 "userdata"
Click to expand...
Click to collapse
Since no kernel commandline is given only the default partitions are shown.
With Kernel Commandline
C:\sdktools-toolsonly\android-sdk-windows\tools>fastboot -c "mtdparts=msm_nand:[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),0x11aa0
[email protected](userdata),[email protected](misc)" boot recovery-clockwork-5.0.2.0-bravo.img
C:\sdktools-toolsonly\android-sdk-windows\tools>adb shell
~ # cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 00480000 00020000 "recovery"
mtd1: 00300000 00020000 "boot"
mtd2: 09600000 00020000 "system"
mtd3: 00500000 00020000 "cache"
mtd4: 11aa0000 00020000 "userdata"
mtd5: 000a0000 00020000 "misc"
~ # exit
Click to expand...
Click to collapse
Again only the default partitions are shown.
Custom Commandline
Now lets expand the commandline
C:\sdktools-toolsonly\android-sdk-windows\tools>fastboot -c "mtdparts=msm_nand:[email protected](sp2),[email protected](sp1),[email protected](misc),[email protected](recovery),[email protected]
x046c0000(boot),[email protected](system),[email protected](cache),[email protected](userdata)" boot recovery-clockwork-5.0.2.0-bravo.img
C:\sdktools-toolsonly\android-sdk-windows\tools>adb shell
~ # cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 000e0000 00020000 "sp2"
mtd1: 00120000 00020000 "sp1"
mtd2: 000a0000 00020000 "misc"
mtd3: 00480000 00020000 "recovery"
mtd4: 00300000 00020000 "boot"
mtd5: 09600000 00020000 "system"
mtd6: 00500000 00020000 "cache"
mtd7: 11aa0000 00020000 "userdata"
~ # mount /sdcard
mount /sdcard
~ # cat /dev/mtd/mtd1 > /sdcard/sp1.img
cat /dev/mtd/mtd1 > /sdcard/sp1.img
~ # cat /dev/mtd/mtd0 > /sdcard/sp2.img
cat /dev/mtd/mtd0 > /sdcard/sp2.img
~ # umount /sdcard
umount /sdcard
~ # exit
exit
Click to expand...
Click to collapse
Lets chcek out the sp1 and sp2 images
D:\store\Desire\nbimg-1.1win32>copy sp1.img sp1.nb
D:\store\Desire\nbimg-1.1win32>copy sp2.img sp2.nb
D:\store\Desire\nbimg-1.1win32>nbimg -F sp1.nb -w 480 -h 800
D:\store\Desire\nbimg-1.1win32>nbimg -F sp2.nb -w 480 -h 800
Click to expand...
Click to collapse
Just check out the extracted images sp1 and sp2. I never knew sp2 image.
Now lets give the command for the full table
C:\sdktools-toolsonly\android-sdk-windows\tools>fastboot -c "mtdparts=msm_nand:[email protected](radio),[email protected](hboot),[email protected](sp2),[email protected](mfg),[email protected]
4080000(sp1),[email protected](wifi),[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected]
0000(userdata)" boot recovery-clockwork-5.0.2.0-bravo.img
C:\sdktools-toolsonly\android-sdk-windows\tools>adb shell
~ # cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 03e20000 00020000 "radio"
mtd1: 000c0000 00020000 "hboot"
mtd2: 000e0000 00020000 "sp2"
mtd3: 000c0000 00020000 "mfg"
mtd4: 00120000 00020000 "sp1"
mtd5: 000a0000 00020000 "wifi"
mtd6: 000a0000 00020000 "misc"
mtd7: 00480000 00020000 "recovery"
mtd8: 00300000 00020000 "boot"
mtd9: 09600000 00020000 "system"
mtd10: 00500000 00020000 "cache"
mtd11: 11aa0000 00020000 "userdata"
~ # mount /sdcard
mount /sdcard
~ # cat /dev/mtd/mtd0 > /sdcard/radio.img
cat /dev/mtd/mtd0 > /sdcard/radio.img
cat: read error: I/O error Gak!But Nothing happened
~ # cat /dev/mtd/mtd1 > /sdcard/hboot.img
cat /dev/mtd/mtd1 > /sdcard/hboot.img
~ # cat /dev/mtd/mtd3 > /sdcard/mfg.img
cat /dev/mtd/mtd3 > /sdcard/mfg.img
~ # cat /dev/mtd/mtd5 > /sdcard/wifi.img
cat /dev/mtd/mtd5 > /sdcard/wifi.img
~ # umount /sdcard
umount /sdcard
~ # exit
Click to expand...
Click to collapse
So could access and get dumps of all the partitions except for radio.

Hboot tampered

I hboot unlocked my htc one vx. But being an idiot, i fastboot a 4ext.img and now it says tampered when i try to go into in hboot. Also when into recovery it says security warning and just freezes. I got ahead of my self, i was googling everywhere and they said something about the RUU, can anyone help me?:crying:

Night_Slayer said:
I hboot unlocked my htc one vx. But being an idiot, i fastboot a 4ext.img and now it says tampered when i try to go into in hboot. Also when into recovery it says security warning and just freezes. I got ahead of my self, i was googling everywhere and they said something about the RUU, can anyone help me?:crying:
Click to expand...
Click to collapse
It seems this device is difficult to flash. I just unlocked my bootloader and it says tampered with and after my recovery doesn't work.

There is no RUU file for this device yet unfortunantly, i already tried many. I WISH there was, then i can get my phone to work again! God know's when one will be made. Because the phone is so new, your pretty much screwed if you mess the phone up. Dead phone speaking here<--- If i find something, i will let you know though.

Thank you guys, Lets hope theres one soon, and you have a dead Speaker yikes :/

Fixing the recovery issue shouldnt be too big of a deal. Someone still stock and locked dumps the recovery partition and you just fastboot flash it.
Sent from my HTC One XL using xda premium

Can anyone who have stock try this lol, it can be a big help

If someone has adb setup can they plug in the device and run the command below. Paste the results here.
adb shell cat /proc/emmc
Sent from my HTC One XL using xda premium

jmztaylor said:
If someone has adb setup can they plug in the device and run the command below. Paste the results here.
adb shell cat /proc/emmc
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I would try, but I believe my recovery img is corruputed :/

jmztaylor said:
If someone has adb setup can they plug in the device and run the command below. Paste the results here.
adb shell cat /proc/emmc
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
This is what I got when i used your command, hope it helped. not sure if someone already did this for you or not.
c:\SDK\sdk\tools>adb shell cat /proc/emmc
dev: size erasesize name
mmcblk0p22: 000ffa00 00000200 "misc"
mmcblk0p21: 00fffe00 00000200 "recovery"
mmcblk0p20: 01000000 00000200 "boot"
mmcblk0p32: 54fffc00 00000200 "system"
mmcblk0p29: 00140200 00000200 "local"
mmcblk0p33: 0dfffe00 00000200 "cache"
mmcblk0p34: 49fffe00 00000200 "userdata"
mmcblk0p25: 01400000 00000200 "devlog"
mmcblk0p27: 00040000 00000200 "pdata"
mmcblk0p35: 1097fe000 00000200 "fat"
mmcblk0p30: 00010000 00000200 "extra"
mmcblk0p16: 02d00000 00000200 "radio"
mmcblk0p17: 00a00000 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p18: 00500000 00000200 "wcnss"
mmcblk0p19: 007ffa00 00000200 "radio_config"
mmcblk0p23: 00400000 00000200 "modem_st1"
mmcblk0p24: 00400000 00000200 "modem_st2"