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

Root This is an ugly problem. Need some serious help.

It just keeps failing on unzipping the system part of the RUU. That is what ive confirmed it as. Can I send one of you my house number to call and talk to about this? You can even block the call and be a private caller idc. I know for a fact this whole time it's been failing on unzipping the system. The original RUU was supposed to be downloaded as 418mb but it downloads 428. and the one someone provided in this thread is 422 i believe. So many different data readings hmm
 
*** RELOCKED ***
SHOOTER XC SHIP S-OFF RL
HBOOT-1.57.0000
RADIO-1.06.00.0426
OpenADSP-v02.6.0.2226.00.0217
eMMC-boot
apr 20 blah blah.

Then it has orange text that says RUU below that stuff. The bottom two corners have exclamation points. I'm obviously stuck in Fastboot, I don't think the bootloader itself is loading correctly.
 
Maybe we should wait for scotty to come take a look? We're starting to get out of my comfort zone with attempting anything further... I'll shoot him a pm.
 
Bootloader won't read the PG86IMG.zip on my sdcard either. I think my bootloader is corrupted. Can I flash one through fastboot? Ive been on administrator permissions this whole time on Cmd too. It said I had access denied when i tried to flash hboot through it
 
I don't know... The only way I've ever flashed a bootloader is through a pg86img...

Honestly I would practice patience right now. Scotty knows about everything htc. If anyone can recover this he can. Bootloader is not something you want to be messing and experimenting with. Let's see what he has to say?
 
I fixed the black screen! omg! i tried again to flash an hboot through fastboot flash zip and it worked. Now I have a working bootloader again! next step guys? Should I try to RUU again?
 
I just want to get my PACROM loading again so I'm gonna try and flash a recovery and then super wipe system like 10 times
 
RUU still fails in the bootloader with the zip method, and the error is Image Unzipping Fail! says FAIL-UZ next to (9) SYSTEM
 
It has to be the system partition. Even earlier when I tried reinstalling PAC it got stuck on Extracting System.. I had to pull the battery. So I might have to format the system partition or completely erase it and set it up as new? I know there are commands for that i've seen it. Kind of the same commands I saw on unlimited.io back in the Windows days
 
And I remember seeing that even after formatting it in 4Ext it wouldn't delete every single mb. There was like 40mb still being used in system
 
There is a command to wipe the system but I have never used it. I just read that you will lose recovery and have to flash a system.img. I assume that would be through a PG86IMG which I dunno would work for you right now.

Like I said I'm getting out of my comfort zone. My advice is to be patient so the phone doesn't end up damaged beyond repair.

If you want to Google it and experiment, it's on you but I don't want to have it on my conscience that I bricked someone's phone by giving advice I was unsure about. :/
 
Well I just wiped everything in recovery and I am gonna try to restore my blurom backup from last week. I think i'm going to stick to it and forget PACman. Currently restoring system now from the backup... I don't know if the system just needs wiped tho or if it actually needs erased and repartitioned because ive seen that happen before. There was a way to flash a system.img through fastboot but it kept saying the data of the img was too big or something,
 
As title states, i'm pretty sure the system partition itself has been corrupted. I've been trying to restore a blurom nandroid for 45 minutes now and it is stuck on System,

The RUU fails no matter how I do it, I was lucky to get bootloader and recovery working again.

Is there a set of commands I can issue that will fix/repair or rebuilt the block for system? I am literally certain it's corrupted or been erased, the RUU fails with error 153 I think it was, or 53. I don't remember. Just says "Image Unzipping Fail!" or something similar. I've done the RUU all 3 or 4 different ways and they all get stuck on installing the system image or unzipping it or whatever.

SO I need help before I decide to trash this phone and buy a shitty one.
 
HaTrEd360 said:
And I don't need to relock the bootloader before running an RUU because i'm s-off right? A lot of guides say I need to do that. I find it funny how every time I flash a different bootloader the version number changes but still says Unlocked at the top.
Click to expand...
no. you can be unlocked while s off

HaTrEd360 said:
Now because it failed, it shows a black htc screen with exclamation points in the corners.
Click to expand...
this is RUU mode,looks like youve figured th is out allready.youre stuck there becasue of youre failed flash attempt. youll need to successfully flash something and it will let you out. typically id suggest a recovery,wich is relatively harmless.

HaTrEd360 said:
Can I flash this through fastboot flash zip?
Click to expand...
yes

HaTrEd360 said:
Could it be a mainver problem? Idk what to do. I'm on the 2.95 OTA but I installed it through Ramjets firmware pg86img.
Click to expand...
no. nothing to do with main version. youre s off and its not doign any security checks.

HaTrEd360 said:
As far as I knew adb didnt work in bootloader?
Click to expand...
correct

HaTrEd360 said:
What is rcdata? Can I just remove that from the RUU and maybe it will work?
Click to expand...
radio configuration. i thot it was sticking on system? any trouble with the radio or support firmware is typically a very bad sign :eek:

HaTrEd360 said:
Bootloader won't read the PG86IMG.zip on my sdcard either. I think my bootloader is corrupted. Can I flash one through fastboot? Ive been on administrator permissions this whole time on Cmd too. It said I had access denied when i tried to flash hboot through it
Click to expand...
bootloader is fine,its doing what its supposed to to(keep you in ruu mode until working software is successfully flashed). it let yuo out of ruu mode when you successfully flashed the new hboot.

HaTrEd360 said:
Anyone know how to check the file system on HTC through CMD?
Click to expand...

you can fastboot erase system but thats not really doing anything different than youre recovery is doing. sounds like you have a number of bad blocks in your system partition,making a big chunk of it unuseable. if there is a way to repair bad emmc blocks with fastboot,im not sure what it is.

your only hope,that i know of,is to try and find a rom that fits into the working flash memory that you have.

roll all the way back to GB firmware. run a GB ruu with recovery,system,and boot images removed.

then flashed the smallest cm7 rom you can find. GB is much less complex,so you hopefully can find a cm7 rom that takes up half the footprint(or less) in memory.

it may not be the latest and gretest OS,but may get you a working phone. :)
 
almost forgot... you can check the condition of your emmc.

-install a recovery
-boot to it
-open cmd
adb devices should return xxxxxx recovery

then:
adb shell
dmesg | grep mmc0

good output(gsm 3d with ext 4 recovery):
Code: 
c:\miniadb_shooteru>[COLOR="Red"]adb shell[/COLOR]
~ # [COLOR="red"]dmesg | grep mmc0[/COLOR]
dmesg | grep mmc0
<3>[    2.973723] mmc0: No card detect facilities available
<6>[    2.974150] mmc0: Qualcomm MSM SDCC at 0x0000000012400000 irq 136,0 dma 18

<6>[    2.974333] mmc0: Platform slot type: MMC
<6>[    2.974455] mmc0: 8 bit data mode enabled
<6>[    2.974638] mmc0: 4 bit data mode disabled
<6>[    2.974730] mmc0: polling status mode disabled
<6>[    2.974852] mmc0: MMC clock 400000 -> 48000000 Hz, PCLK 0 Hz
<6>[    2.975035] mmc0: Slot eject status = 0
<6>[    2.975127] mmc0: Power save feature enable = 1
<6>[    2.975310] mmc0: DM non-cached buffer at ff007000, dma_addr 0x570ac000
<6>[    2.975432] mmc0: DM cmd busaddr 0x570ac000, cmdptr busaddr 0x570ac300
<6>[    3.099577] mmc0: new high speed MMC card at address 0001
<6>[    3.100005] mmcblk0: mmc0:0001 KLL00M 2.25 GiB
~ #


bad output(from internet):
Code: 
mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed

bad blocks will show something similar to the good output,but with errors

you can copy/paste the output here if you want. :)
 
I merged your other thread into this one. No need to start another thread to discuss the same issue. It just makes it less confusing to keep all the help in one thread.
 
I think i'll worry about it at another date. I bought a Kyocera Event for 54 bucks as a temporary replacement lolol
 
You must log in or register to reply here.
Back
Top Bottom