• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Please help me unbrick.

Well I wanted to microwave my phone and send it to HTC for warranty but I had second thoughts. I want to try and get this thing back up and running before I resort to the warranty, since It was rooted. Heres the info on the phone.

*** UNLOCKED ***
KINGDOM PVT SHIP S-ON
HBOOT-1.30.0000
RADIO-1.11.00.0418_2
eMMC-boot
Mar 26 2012,16:07:45

Gets stuck on white screen with green HTC logo.
CWM Recovery used to work but now it doesnt, probably somehow removed it with all my trial and error. Phone was working fine for two months on the Kingdom_xFuZiiOnZz-4.3.2 rom. Then updated some apps the other day and it restarted and got stuck on white HTC screen.

Iv tried flashing every rom i can find, and I have tried flashing different recoverys, and even tried flashing with the RUU, problem is it restarts the bootloader and then gets stuck on the HTC screen then gives a USB error.
 
People like you are the reason they want to void your warranty for rooting. If you can't fix your screw up then Don't try to commit fraud.

Just sayin.

Firstly, you're an a$$hole. Secondly, It seemed as if it was my only option for achieving a warranty for what seems like a hardware issue, due to my rooting. If HTC would have a more lenient policy in regards to rooted devices there would be no need to take these measures. Lastly, I had a change of heart and didn't do anything.
Now does anyone have any sound advice or is this not the type of forums where people help eachother?
 
This is exactly why phone manufacturers are so strict on rooting. Because people don't know what they are doing and end up screwing up their device.

Do more research next time. Good luck to you :thumbup:
 
Different recoveries? Can you get into fastboot and flash the correct recovery again? Then go through all the wipes and try flashing a rom again? You could also try the superwipe.

There's no reason it should be giving you so much issue. There could be a sd card problem...
 
Technically speaking if any of you fools read what he said was he updated a few apps, restarted and the issue happened. Where in all honesty if this is the case, well sorry to say it shouldn't have been his fault of the cause.

You guys are jumping the gun blaming him for the issue. Which it may have been, how ever the details he has listed isn't much to go off of. In all honesty what is there to say it wasn't a actual hardware failure?

I also fail to see how a bad sd card will cause a no boot issue. My roms don't install system files on sd, in turn there will be no booting issue at all from a sd card. You can boot all you want with out a sd card.

Edit: What was the purpose of the two threads? Also what do you mean by gets stuck on the HTC screen then gives a USB error? If I had to guess it is hardware failure or bad blocks/corruption on the emmc.
 
Edit: What was the purpose of the two threads? Also what do you mean by gets stuck on the HTC screen then gives a USB error? If I had to guess it is hardware failure or bad blocks/corruption on the emmc.

The other thread kinda got turned into a warranty thread. I wanted 1 place to address fixing of the problem.
Anyways when I run the RUU from my PC while the phone is in Fastboot, it says Verifying information about your android phone. Then it displays the version 1.10.653.3. Then when I click update it says Image version: 1.10.653.3 to 1.05.653.3. Then it proceeds with installation. The ruu says says rebooting bootloader, then waiting on bootloader, then the phone restarts and goes into the white screen with green HTC letters where it hangs, followed by a USB connection error Error [171].
 
Different recoveries? Can you get into fastboot and flash the correct recovery again? Then go through all the wipes and try flashing a rom again? You could also try the superwipe.

There's no reason it should be giving you so much issue. There could be a sd card problem...

I did suspect the SD card at one point, so i reformatted it.

I am able to wipe only certain things like cache, if I try and wipe system, it hangs.
I just tried to run superwipe and this is my results...

-- Installing: /sdcard/smw61850_superwipe.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop:("ro.product.device") == "jewel"
E:Error in /sdcard/smw61850_superwipe.zip
(Status 7)
Installation aborted.
 
assert failed: getprop:("ro.product.device") == "jewel"

^ That is the issue with it as it isn't made for the kingdom...
 
assert failed: getprop:("ro.product.device") == "jewel"

^ That is the issue with it as it isn't made for the kingdom...

Tried to install the same kingdom rom that I had on it before which worked fine for a couple months and it says this...

Formatting system and data
E:Error in /sdcard/ph44img.zip
(status 1)
Installation aborted

It was stuck on the formatting step for a few mins which didn't show progress on the bar.
 
How are you installing the said files with no recovery? If you have the recovery even though I said I wouldn't help you. I need you to dump something to the sd card.
 
How are you installing the said files with no recovery? If you have the recovery even though I said I wouldn't help you. I need you to dump something to the sd card.
I managed to get recovery to work. Most of the time it starts to load then reboots. After a while I finally got into recovery. If i try to use fastboot command line i get an error every time i try to flash or boot something. What do you want me to dump?


Edit here is my current log...

Starting recovery on Tue Jan 8 03:07:54 1980
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (540 x 960)
2FS kingdom CWM Recovery v5.0.2.8
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /recovery emmc /dev/block/mmcblk0p21 (null)
2 /boot emmc /dev/block/mmcblk0p22 (null)
3 /cache ext4 /dev/block/mmcblk0p28 (null)
4 /data ext4 /dev/block/mmcblk0p27 (null)
5 /sd-ext ext3 /dev/block/mmcblk1p2 (null)
6 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
7 /system ext4 /dev/block/mmcblk0p26 (null)
8 /wimax emmc /dev/block/mmcblk0p25 (null)
9 /misc emmc /dev/block/mmcblk0p17 (null)

W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
W:failed to mount /dev/block/mmcblk0p28 (Invalid argument)
E:Can't mount /cache/recovery/command
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"

ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GINGERBREAD
ro.build.display.id=htc_kingdom-eng 2.3.7 GINGERBREAD eng.home.20120620.013219 test-keys
ro.build.version.incremental=eng.home.20120620.013219
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Wed Jun 20 01:33:37 EDT 2012
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=home
ro.build.host=home-EP45-UD3R
ro.build.tags=test-keys
ro.product.model=ADR6350
ro.product.brand=generic
ro.product.name=htc_kingdom
ro.product.device=kingdom
ro.product.board=kingdom
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7x30
ro.build.product=kingdom
ro.build.description=htc_kingdom-eng 2.3.7 GINGERBREAD eng.home.20120620.013219 test-keys
ro.build.fingerprint=generic/htc_kingdom/kingdom:2.3.7/GINGERBREAD/eng.home.20120620.013219:eng/test-keys
ro.cm.device=kingdom
ro.sf.lcd_density=240
debug.fb.rgb565=0
ro.gsm.2nd_data_retry_config=max_retries=3, 2000, 2000, 2000
rild.libpath=/system/lib/libhtc_ril.so
ro.ril.ecc.HTC-GCC=999,112,997
ro.ril.ecc.HTC-WWE=999
ro.ril.ecc.HTC-ELL=92,93,94
ro.ril.enable.a52.HTC-ITA=1
ro.ril.enable.a53.HTC-ITA=1
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.disable.fd.plmn.prefix=23402,23410,23411
ro.ril.enable.sdr=1
ro.ril.enable.amr.wideband=0
ro.ril.enable.dtm=0
ro.ril.gprsclass=12
ro.ril.hsdpa.category=10
ro.ril.hsupa.category=6
ro.ril.hsxpa=2
ro.telephony.default_network=0
wifi.interface=eth0
wifi.supplicant_scan_interval=15
mobiledata.interfaces=gannet0,rmnet0,rmnet1,rmnet2
ro.opengles.version=131072
dalvik.vm.heapsize=48m
ro.ril.def.agps.mode=2
ro.ril.disable.power.collapse=1
ro.ril.update.org.acoustic=1
net.tcp.buffersize.hsdpa=4094,87380,393216,4096,16384,110208
net.change=net.bt.name
keyguard.no_require_sim=true
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=HT253MB00165
ro.bootmode=recovery
ro.baseband=1.11.00.0418_2
ro.carrier=COMMON
ro.bootloader=1.30.0000
ro.hardware=kingdom
ro.revision=2
ro.emmc=1
init.svc.choice_fn=stopped
init.svc.recovery=running
init.svc.htcbatt=stopped
init.svc.adbd=running
ro.9kramdump=0

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p28 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p28 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p28 (Invalid argument)
W:Can't unlink /cache/recovery/command
E:Unable to write to ums lunfile (No such file or directory)W:failed to mount /dev/block/mmcblk0p28 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p28 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p28 (Invalid argument)
W:Can't unlink /cache/recovery/command

-- Installing: /sdcard/smw6180_superwipe.zip
Finding update package...
I:Update location: /sdcard/smw6180_superwipe.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "jewel"
assert failed: getprop("ro.product.device") == "jewel"
E:Error in /sdcard/smw6180_superwipe.zip
(Status 7)
Installation aborted.
Signature Check: Enabled

-- Installing: /sdcard/smw6180_superwipe.zip
Finding update package...
I:Update location: /sdcard/smw6180_superwipe.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:verify_file returned 1
E:signature verification failed
Installation aborted.

-- Installing: /sdcard/smw6180_superwipe.zip
Finding update package...
I:Update location: /sdcard/smw6180_superwipe.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:verify_file returned 1
E:signature verification failed
Installation aborted.

-- Installing: /sdcard/smw6180_superwipe.zip
Finding update package...
I:Update location: /sdcard/smw6180_superwipe.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:verify_file returned 1
E:signature verification failed
Installation aborted.

-- Installing: /sdcard/smw6180_superwipe.zip
Finding update package...
I:Update location: /sdcard/smw6180_superwipe.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:verify_file returned 1
E:signature verification failed
Installation aborted.

-- Installing: /sdcard/smw6180_superwipe.zip
Finding update package...
I:Update location: /sdcard/smw6180_superwipe.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:verify_file returned 1
E:signature verification failed
Installation aborted.

-- Installing: /sdcard/smw6180_superwipe.zip
Finding update package...
I:Update location: /sdcard/smw6180_superwipe.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:verify_file returned 1
E:signature verification failed
Installation aborted.

-- Installing: /sdcard/smw6180_superwipe.zip
Finding update package...
I:Update location: /sdcard/smw6180_superwipe.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:verify_file returned 1
E:signature verification failed
Installation aborted.

-- Installing: /sdcard/smw6180_superwipe.zip
Finding update package...
I:Update location: /sdcard/smw6180_superwipe.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:verify_file returned 1
E:signature verification failed
Installation aborted.

-- Installing: /sdcard/smw6180_superwipe.zip
Finding update package...
I:Update location: /sdcard/smw6180_superwipe.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:verify_file returned 1
E:signature verification failed
Installation aborted.
Script Asserts: Enabled

-- Installing: /sdcard/smw6180_superwipe.zip
Finding update package...
I:Update location: /sdcard/smw6180_superwipe.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:verify_file returned 1
E:signature verification failed
Installation aborted.
Signature Check: Disabled
Script Asserts: Disabled

-- Installing: /sdcard/smw6180_superwipe.zip
Finding update package...
I:Update location: /sdcard/smw6180_superwipe.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "jewel"
assert failed: getprop("ro.product.device") == "jewel"
E:Error in /sdcard/smw6180_superwipe.zip
(Status 7)
Installation aborted.
W:failed to mount /dev/block/mmcblk0p28 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p28 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p28 (Invalid argument)
W:Can't unlink /cache/recovery/command

-- Wiping data...
Formatting /data...
Creating filesystem with parameters:
Size: 1252770816
Block size: 4096
Blocks per group: 32768
Inodes per group: 7647
Inode size: 256
Journal blocks: 4778
Label:
Blocks: 305852
Block groups: 10
Reserved block group size: 79
Created filesystem with 11/76470 inodes and 10067/305852 blocks
error: file_write: write: I/O error
Starting recovery on Tue Jan 8 03:39:43 1980
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (540 x 960)
2FS kingdom CWM Recovery v5.0.2.8
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /recovery emmc /dev/block/mmcblk0p21 (null)
2 /boot emmc /dev/block/mmcblk0p22 (null)
3 /cache ext4 /dev/block/mmcblk0p28 (null)
4 /data ext4 /dev/block/mmcblk0p27 (null)
5 /sd-ext ext3 /dev/block/mmcblk1p2 (null)
6 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
7 /system ext4 /dev/block/mmcblk0p26 (null)
8 /wimax emmc /dev/block/mmcblk0p25 (null)
9 /misc emmc /dev/block/mmcblk0p17 (null)

W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
W:failed to mount /dev/block/mmcblk0p28 (Invalid argument)
E:Can't mount /cache/recovery/command
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"

ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GINGERBREAD
ro.build.display.id=htc_kingdom-eng 2.3.7 GINGERBREAD eng.home.20120620.013219 test-keys
ro.build.version.incremental=eng.home.20120620.013219
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Wed Jun 20 01:33:37 EDT 2012
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=home
ro.build.host=home-EP45-UD3R
ro.build.tags=test-keys
ro.product.model=ADR6350
ro.product.brand=generic
ro.product.name=htc_kingdom
ro.product.device=kingdom
ro.product.board=kingdom
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7x30
ro.build.product=kingdom
ro.build.description=htc_kingdom-eng 2.3.7 GINGERBREAD eng.home.20120620.013219 test-keys
ro.build.fingerprint=generic/htc_kingdom/kingdom:2.3.7/GINGERBREAD/eng.home.20120620.013219:eng/test-keys
ro.cm.device=kingdom
ro.sf.lcd_density=240
debug.fb.rgb565=0
ro.gsm.2nd_data_retry_config=max_retries=3, 2000, 2000, 2000
rild.libpath=/system/lib/libhtc_ril.so
ro.ril.ecc.HTC-GCC=999,112,997
ro.ril.ecc.HTC-WWE=999
ro.ril.ecc.HTC-ELL=92,93,94
ro.ril.enable.a52.HTC-ITA=1
ro.ril.enable.a53.HTC-ITA=1
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.disable.fd.plmn.prefix=23402,23410,23411
ro.ril.enable.sdr=1
ro.ril.enable.amr.wideband=0
ro.ril.enable.dtm=0
ro.ril.gprsclass=12
ro.ril.hsdpa.category=10
ro.ril.hsupa.category=6
ro.ril.hsxpa=2
ro.telephony.default_network=0
wifi.interface=eth0
wifi.supplicant_scan_interval=15
mobiledata.interfaces=gannet0,rmnet0,rmnet1,rmnet2
ro.opengles.version=131072
dalvik.vm.heapsize=48m
ro.ril.def.agps.mode=2
ro.ril.disable.power.collapse=1
ro.ril.update.org.acoustic=1
net.tcp.buffersize.hsdpa=4094,87380,393216,4096,16384,110208
net.change=net.bt.name
keyguard.no_require_sim=true
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=HT253MB00165
ro.bootmode=recovery
ro.baseband=1.11.00.0418_2
ro.carrier=COMMON
ro.bootloader=1.30.0000
ro.hardware=kingdom
ro.revision=2
ro.emmc=1
init.svc.choice_fn=stopped
init.svc.recovery=running
init.svc.htcbatt=stopped
init.svc.adbd=running
ro.9kramdump=0

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p28 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p28 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p28 (Invalid argument)
W:Can't unlink /cache/recovery/command
Formatting /data...
Creating filesystem with parameters:
Size: 1252770816
Block size: 4096
Blocks per group: 32768
Inodes per group: 7647
Inode size: 256
Journal blocks: 4778
Label:
Blocks: 305852
Block groups: 10
Reserved block group size: 79
Created filesystem with 11/76470 inodes and 10067/305852 blocks
error: file_write: write: I/O error
Starting recovery on Tue Jan 8 03:58:50 1980
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (540 x 960)
2FS kingdom CWM Recovery v5.0.2.8
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /recovery emmc /dev/block/mmcblk0p21 (null)
2 /boot emmc /dev/block/mmcblk0p22 (null)
3 /cache ext4 /dev/block/mmcblk0p28 (null)
4 /data ext4 /dev/block/mmcblk0p27 (null)
5 /sd-ext ext3 /dev/block/mmcblk1p2 (null)
6 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
7 /system ext4 /dev/block/mmcblk0p26 (null)
8 /wimax emmc /dev/block/mmcblk0p25 (null)
9 /misc emmc /dev/block/mmcblk0p17 (null)

W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
W:failed to mount /dev/block/mmcblk0p28 (Invalid argument)
E:Can't mount /cache/recovery/command
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"

ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GINGERBREAD
ro.build.display.id=htc_kingdom-eng 2.3.7 GINGERBREAD eng.home.20120620.013219 test-keys
ro.build.version.incremental=eng.home.20120620.013219
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Wed Jun 20 01:33:37 EDT 2012
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=home
ro.build.host=home-EP45-UD3R
ro.build.tags=test-keys
ro.product.model=ADR6350
ro.product.brand=generic
ro.product.name=htc_kingdom
ro.product.device=kingdom
ro.product.board=kingdom
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7x30
ro.build.product=kingdom
ro.build.description=htc_kingdom-eng 2.3.7 GINGERBREAD eng.home.20120620.013219 test-keys
ro.build.fingerprint=generic/htc_kingdom/kingdom:2.3.7/GINGERBREAD/eng.home.20120620.013219:eng/test-keys
ro.cm.device=kingdom
ro.sf.lcd_density=240
debug.fb.rgb565=0
ro.gsm.2nd_data_retry_config=max_retries=3, 2000, 2000, 2000
rild.libpath=/system/lib/libhtc_ril.so
ro.ril.ecc.HTC-GCC=999,112,997
ro.ril.ecc.HTC-WWE=999
ro.ril.ecc.HTC-ELL=92,93,94
ro.ril.enable.a52.HTC-ITA=1
ro.ril.enable.a53.HTC-ITA=1
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.disable.fd.plmn.prefix=23402,23410,23411
ro.ril.enable.sdr=1
ro.ril.enable.amr.wideband=0
ro.ril.enable.dtm=0
ro.ril.gprsclass=12
ro.ril.hsdpa.category=10
ro.ril.hsupa.category=6
ro.ril.hsxpa=2
ro.telephony.default_network=0
wifi.interface=eth0
wifi.supplicant_scan_interval=15
mobiledata.interfaces=gannet0,rmnet0,rmnet1,rmnet2
ro.opengles.version=131072
dalvik.vm.heapsize=48m
ro.ril.def.agps.mode=2
ro.ril.disable.power.collapse=1
ro.ril.update.org.acoustic=1
net.tcp.buffersize.hsdpa=4094,87380,393216,4096,16384,110208
net.change=net.bt.name
keyguard.no_require_sim=true
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=HT253MB00165
ro.bootmode=recovery
ro.baseband=1.11.00.0418_2
ro.carrier=COMMON
ro.bootloader=1.30.0000
ro.hardware=kingdom
ro.revision=2
ro.emmc=1
init.svc.choice_fn=stopped
init.svc.recovery=running
init.svc.htcbatt=stopped
init.svc.adbd=running
ro.9kramdump=0

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p28 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p28 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p28 (Invalid argument)
W:Can't unlink /cache/recovery/command
W:failed to mount /dev/block/mmcblk0p28 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p28 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p28 (Invalid argument)
W:Can't unlink /cache/recovery/command

-- Installing: /sdcard/ph44img.zip
Finding update package...
I:Update location: /sdcard/ph44img.zip
Opening update package...
Installing update...

Creating filesystem with parameters:
Size: 840956416
Block size: 4096
Blocks per group: 32768
Inodes per group: 7333
Inode size: 256
Journal blocks: 3208
Label:
Blocks: 205311
Block groups: 7
Reserved block group size: 55
Created filesystem with 11/51331 inodes and 6666/205311 blocks


====================================
| Welcome to xFuZiiOnZz-4.3.2 |
| by 2fast4u88 and Team |
====================================
| Team Consists Of |
| Cookiefrog, Grad and BMaae4 |
************************************
Thanks To Mrsboots For The BackUp
************************************
* Carrier Detection *
* Magic By: 2fast4u88 *
************************************
* TEAM INVICTUS *
************************************
************************************


Formatting System And Data
error: file_write: write: I/O error
E:Error in /sdcard/ph44img.zip
(Status 1)
Installation aborted.
W:failed to mount /dev/block/mmcblk0p28 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p28 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p28 (Invalid argument)
W:Can't unlink /cache/recovery/command
 
Come on, 2fast. You're a car man. You should know there is often more than one problem. A messed up sd card could cause additional problems if you try flashing a new rom. It's happened to me before.
 
Why would an sd card matter? Unless you are flashing a bad download from you sd then the sd is touched until after it boots.
 
Go here Directory listing of http://www.htcruu.com/ navigate to the kingdom section and download thge ruu.eve you need.. If it is sprint only pick the last one. If it is sprint-boost pick the newest of the three.. Plug in your phone and power it on.. Run the ruu, if the software version is older on your phone, than the one you downloade, then you can update it and that should help with your issue.. If it is newer than the file you downoladed it will give you a error code..
 
Why would an sd card matter? Unless you are flashing a bad download from you sd then the sd is touched until after it boots.

Well you kind of just answered your own question. But it could be a bad download, a misread, data corruption as the rom is being flashed, etc. There are many possible problems. I had a sd card that would unmount itself.
 
But he already had it flashed, so the sd wouldn't be used during boot

From the op "I tried flashing every rom I could find"
That means he tried flashing new roms, maybe a bad one, or any other issue started here. My point is that your phone is very vulnerable at this step.

But do we really need to be having this conversation?
 
From the op "I tried flashing every rom I could find"
That means he tried flashing new roms, maybe a bad one, or any other issue started here. My point is that your phone is very vulnerable at this step.

But do we really need to be having this conversation?

This was after the fact that my phone was already bricked. And nothing would take. Also, I mostly tried flashing through fastboot and not the SD Card.
 
Back
Top Bottom