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

Root can't flash RUU, problems with sense based ROMs

M

msalivar

Newbie
Ok, so this one started out kind of similarly to happysteveo's post a couple weeks ago, which I just read through in retrospect. I was having radio problems with the AOSP roms I was trying out, so I decided to try a Sense based ROM for the hell of it. I think it was TrickDroid that I tried first, but I may be wrong. It seemed to flash ok, but immediately upon boot, before I could get through the lock screen, the phone app would start crashing repeatedly.

So I decided to reflash it, making sure I didn't forget to wipe something. I wiped the cache, dalvik, factory reset, and system before flashing again. It's been a few hours, but I think what happened next was that the .zip wasn't available on my sdcard. So I tried mounting USB, but it gave me an error about being unable to mount /sdcard. I found the solution to that here.

However, after all that, i still can't mount USB from TWRP, though it's no longer giving me an error. When /sdcard wasn't mounting, when I tried to mount USB it would result in Windows prompting me to format the drive (I never did). Now the drive shows up in My Computer, but if I try to click on it, I'm told that I need to insert a drive. I can, however, push it with adb. However, I'm still getting errors with Sense based ROMs, though I'll have to try a few more to make sure it's all Sense based ROMs and just Sense based ROMs.

Ok, I think, so I'll flash the RUU. By the way, thank you, agentc13, for mirroring them from filefactory. Unfortunately it's not working. I get my phone into fastboot, run the executable, and it reboots the phone to a black screen with a white 'htc' in the middle. I hear transistor or capacitor hum, so I'm pretty sure it's actually copying data over. However it fails with error 155, unknown error, and I have to force the phone to reboot.

I've been fighting with this for hours now, so I'm going to bed. I just wanted to get this down before sleep erased my memory. One thing that I'm thinking I might have done, but I'm not sure... I might have tried the RUU before I tried another Sense based ROM. Maybe this is a bad RUU and that was what caused all the problems to begin with. I had CM9 Alpha11 installed before trying this last RUU flash. I flashed the stock recovery and relocked the device, and then made sure that CM9 would still boot. After the RUU failed, I can no longer boot CM9, it just keeps looping to the bootloader.
 
Error 155 seems to happen when the bootloader isn't relocked. I know that you siad you locked it, but does it say 'relocked' when you boot into bootloader?


You typed "fastboot oem lock" in to lock the bootloader? Also you have your phone in bootloader mode when running the ruu?
 
So I flash the stock recovery with the AIO Kit

Code: 
C:\Users\msalivar\Downloads\Android\One_S_All-In-One_Kit_v1.1\data>fastboot flash recovery Recoveries/recovery.img
  sending 'recovery' (9480 KB)... OKAY [  1.653s]
            writing 'recovery'... OKAY [  2.322s]
finished. total time: 3.976s

C:\Users\msalivar\Downloads\Android\One_S_All-In-One_Kit_v1.1\data>fastboot reboot
                     rebooting...
finished. total time: 0.061s

Then I lock the bootloader with the same tool, which uses that command

Code: 
C:\Users\msalivar\Downloads\Android\One_S_All-In-One_Kit_v1.1\data>fastboot oem lock
< waiting for device >
                              ... INFOLock successfully...
INFOTZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Too many links))
finished. total time: 0.936s

I don't know about that (status read failed (Too man links)), but after rebooting the bootloader it says *** TAMPERED *** and *** RELOCKED *** up top. If I reboot the phone, it adds *** Security Warning *** to that, and won't boot Android.

Now I'm running the RUU, with FASTBOOT USB highlighted in red above the list, and BOOTLOADER highlighted in blue in the pick list. It verified the information about my phone alright, and on the next screen the current image version section is blank. I choose to update the current ROM version. "From Image Version:" is still blank, but at least it knows it's going to flash 1.53.531.16. So I hit next a couple times, and it boots to that black screen with the 'htc' logo in white. In RUU the progress bar is moving, saying it's updating the signature. As soon as it finishes with that, it flashes the next step too fast for me to read it, and fails with code 155.
 
The Mount USB feature is now working, anyway. I haven't tried another Sense based ROM yet, I'd like to get the RUU working first.
 
You are in fastboot mode, if you select bootloader it will say hboot instead of fastboot usb. I think that you need to do that in order to flash the ruu.
 
Crap. Can you flash the RUU if you're permanently rooted? I honestly didn't even realize there was a non-permanent root until I saw that option in the AIO just now.
 
Yeah, I flashed a RUU when I had CWM and rooted stock ROM. I am checking into the error you are getting, hopefully we can can get it sorted.

A couple of quick questions... International or US, and branded or unbranded?

Try doing the fastboot command manually instead of through the tool and see if it does anything different.

Also when in fastboot type this command and paste the results:
Code: 
fastboot getvar all
 
It's US Tmobile, and the results of getvar all follows.

C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar al
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.16.31501S.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno: ********** edited out
(bootloader) imei: ******** edited out
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4188mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e964c535
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
 
manually running the command results exactly the same as before, but I'll try the RUU again now.

C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Too many links))
finished. total time: 0.936s
 
Okay, and you were trying to run the 1.53 TMOUS RUU? Are you currently on 1.84 (I think from your baseband you are)? That could be the issue.

Can you unlock the bootloader, restore an old nandroid (that is 1.53) and flash the 1.53 radio? If so you should be able to lock the bootloader and run the RUU.
 
Here's something else I've noticed after a failed RUU. After I unlock it and install TWRP again, a ROM won't successfully load, it just hangs. So I go into recovery and wipe the cache, and there's a whole bunch of errors:

Code: 
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/command
 * Verifying Filesystems...
 * Verifying Parition sizes...
E:Unable to mount /data
E:Unable to mount /cache
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
Formatting /cache...
 * Verifying Filesystems...
 * Verifying Parition sizes...
E:Unable to mount /data

When I wipe the dalvik, I just see the one new error at the end about /data. Once I do a factory reset, if I go back to wipe the cache and dalvik, I don't get any new errors about /cache or /data. I don't know if this might be something, or if it would be expected behavior after a failed RUU flash, or after unlock and relocking, and swapping recoveries.
 
The ones I linked need to be done with ClockworkMod Recovery (TWRP won't restore them). It is done through the backup/restore option in CWM.


BTW, I have to get going for a bit, but I will be checking in periodically. So I will probably be slow to respond with more questions for a while.
 
Finding update package...
Opening update package...
Installing update...
Installation aborted.

CWM is also not successfully mounting USB storage, so I had to reinstall TWRP to do that. This was with the stock.no.root.zip file, I'll try the other one later. I just need to separate myself from this for a couple hours.

The worst part is, I don't even want this phone anymore. I don't like the button placement, and the thing just doesn't feel good in my hand. On the other hand, I flashed CM9 to my Nexus S as a dry run, and it's really breathed life into it. Even less cruft than there was before, it runs smoother, and my signal quality got significantly better. I think I'm just going to eat the cost of the phone and get out of the contract while I still can.

Theoretically, if this was all going right, would I be able to get rid of the red warning text on the boot splash and make it seem like it was in a proper factory state?
 
The only difference would be that the bootloader would say relocked.

Also, what exact steps did you take in CWM?
I don't think it mounts mass storage in CWM, but it works correctly otherwise (this might have changed, it's been a while since I used it) .
 
So that red text about being on a development version would be gone?

I just flashed CWM Touch, went to the mount menu, and tried to Mount USB Storage. I didn't get a removable storage popup in Window, and when I tried to open the drive in My Computer it said to insert a disk.
 
Yeah, I don't believe Mass Storage works in CWM.

You should still be able to select "Backup and restore" and then "Restore" to be able to use the nandroid just fine.
 
You must log in or register to reply here.
Back
Top Bottom