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

Root HELP! Accidentally Wiped Internal Storage and OS on HTC ONE M8

EatedCookies said:
I got it from here http://forum.xda-developers.com/showthread.php?t=2694917
I'm certain I didn't have the Lollipop update on my phone
Click to expand...
You have two choices.

If you want to use ARHD 43.0 you're going to need the Lollipop firmware or it's going to be incompatible and a lot of trouble. Being s-on, you're going to want to apply the latest RUU.

Boot into FASTBOOT, plug in to PC, so it says FASTBOOT USB at the top. From the command window -

fastboot oem lock

Get a 50% charge on the phone, run the RUU found here (carrier-branded AT&T M8) -


http://www.htc.com/us/support/htc-one-m8-att/news/

Unlock the bootloader again using the same Unlock_code.bin as before.

fastboot flash recovery twrp-whatever.img

(Forgive me, I assume that you have the file and the right name.)

Just to be safe, make sure that you followed ARHD down to the 43.0 download - http://www.androidrevolution.org/do...oid_Revolution_HD-One_M8_43.0.zip&hash=391da9

TWRP, Advanced, adb sideload that.

That's going to completely erase your whole phone - any backups or personal files on internal storage will be gone.

Option 2 - install a working KitKat, back up everything you need to your pc, then do Option 1.

If you didn't make a nandroid backup, I'd recommend installing ViperOneM8 for this step.


http://venomroms.com/htc-one-m8/

Scroll down and open PREVIOUS ROMS, try version 2.5.0, if that won't function properly, go down to 1.7.1.

Full wipe from within the ViperOneM8 Aroma installer and choose to install the full stock rom, nothing fancy on the options.

~~~~~~~~~

It looks like you adb sorted out for the sideload but don't have the right files.

If adb sideload continues to give you trouble, get an OTG USB cable, put the rom zip on a USB stick formatted to FAT32, plug it directly into the phone, and do a normal TWRP install with that as the source.
 
fastboot oem lock fails and returns with this

C:\Users\Nick\AppData\Local\Android\android-sdk\platform-tools>fastboot oem lock

...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [ERR] Cannot halt SPMI arbiter!!
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.217s
 
What the...

OK let's see what we get (in FASTBOOT USB mode) for -

fastboot getvar all

Please edit out your IMEI and serial numbers for your protection ok.
 
C:\Users\Nick\AppData\Local\Android\android-sdk\platform-tools>fastboot getvar a
ll
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 4.0.U605611@50319A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.28.502.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: -
(bootloader) imei: -
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.120s
 
And btw -

When you executed the dir command earlier - all of that output came from that command?

I'd thought I was seeing error text from some other command interspersed with the dir output.

If that's not so, then you're trying to run tools from a corrupted Windows configuration - you're going to want to do a full disk repair before proceeding if that's the case.

You can save yourself the trouble of a full tools download by just getting our Mini-SDK, everything you need is in the sdk-tools.zip file -

http://androidforums.com/threads/adb-guide-updated-2014-11-11.443072/#post-5389081
 
Your getvar output said that you had the latest system installed last - what do the header lines on your HBOOT screen say?

I don't think that you need the RUU after all - you have the Lollipop firmware.
 
Should I redo the steps in case something changes?
Edit:
Oh good, I thought that I didn't have lollipop, I must of been mistaken.
This changed after I tried fastboot oem lock

*** Software status: Modified ***
*** RELOCKED ***
*** Security Warning ***
M8_UL_CA PCT SHIP S-ON
HBOOT_3.19.0.0000
RADIO-4.0.U605611@50319A
OpenDSP-v47.2.2-00564-M8974_F0.1024
OS-4.28.502.1
eMMC-boot 2048MB
Mar 20 2015,03:01:11.0
HBOOT
 
EatedCookies said:
Should I redo the steps in case something changes?
Click to expand...
No, let's see what the problem is for sure first.

Please see my edits above (you're pretty quick, not a bad thing lol).

It looks like you have the Lollipop firmware so you ought to proceed to the ARHD 43.0 installation directly.

First though, in a NEW command window open to platform-tools, what is the result of the dir command?
 
dir returns with

D:\sdk-tools>dir
The system cannot find message text for message number 0x235e in the message fil
e for Application.
The system cannot find message text for message number 0x235b in the message fil
e for Application.

DNS bad key.
06/16/2015 12:21 AM The system cannot find message text for message number 0
x2373 in the message file for Application.
.
06/16/2015 12:21 AM The system cannot find message text for message number 0
x2373 in the message file for Application.
..
10/16/2014 04:33 PM 1,318,951 adb-linux
11/11/2014 07:50 PM 1,324,340 adb-mac
11/11/2014 07:50 PM 1,009,664 adb.exe
11/11/2014 07:50 PM 96,256 AdbWinApi.dll
11/11/2014 07:50 PM 60,928 AdbWinUsbApi.dll
06/15/2015 10:26 PM 1,717,252,429 AndroidM841.zip
11/20/2010 11:23 PM 345,088 cmd.exe
10/16/2014 04:33 PM 215,626 fastboot-linux
11/11/2014 07:50 PM 213,404 fastboot-mac
11/11/2014 07:50 PM 196,608 fastboot.exe
08/26/2011 07:59 PM 28,160 md5sums.exe
05/18/2014 03:16 PM 1,414 sdk.sh
11/11/2014 07:59 PM 83 Version.txt
The system cannot find message text for message number 0x2378 in the messa
ge file for Application.
The system cannot find message text for message number 0x2379 in the messa
ge file for Application.
 
EatedCookies said:
Should I redo the steps in case something changes?
Edit:
Oh good, I thought that I didn't have lollipop, I must of been mistaken.
This changed after I tried fastboot oem lock

*** Software status: Modified ***
*** RELOCKED ***
*** Security Warning ***
M8_UL_CA PCT SHIP S-ON
HBOOT_3.19.0.0000
RADIO-4.0.U605611@50319A
OpenDSP-v47.2.2-00564-M8974_F0.1024
OS-4.28.502.1
eMMC-boot 2048MB
Mar 20 2015,03:01:11.0
HBOOT
Click to expand...
Well I apologize - I ought to have verified with the getvar first.

Go ahead and unlock the bootloader again.

If the dir is corrupted from the above test, definitely try again using the Mini-SDK, for both the unlock and the adb sideload.

Go ahead and grab a fresh copy of ARHD and put it in the sdk-tools folder just to be safe.
 
Yeah, you really can't trust anything else to run right out of that platform-tools folder.

See what the dir looks like from the sdk-tools folder after you grab it.
 
Edit - ok. I see, that was the sdk-tools folder.

I'm trying to answer from my phone without benefit of seeing the post after I start to reply.

I'd advise a chkdsk on the pc before anything else, using this if Windows 7 -

https://support.microsoft.com/en-us/kb/2641432

If that fixed stuff, I'd move to repeat it and scan and fix bad sectors.

It's entirely up to you - however - if a corrupted adb or fastboot sends something really bad down the pipe, your phone could become a paperweight.

That's the sky-is-falling scenario that s-on ought to completely protect you from - so you have to ask if you're feeling lucky and want to just proceed with the unlock and adb sideload install again.
 
I decided to go through and use the RUU and I've had my first success in 2 days.
Can you link me to the md5sums tool?
With hope I'll be able to fix things with an OS now.
 
EatedCookies said:
I decided to go through and use the RUU and I've had my first success in 2 days.
Can you link me to the md5sums tool?
With hope I'll be able to fix things with an OS now.
Click to expand...
Congratulations!!

The md5sums tool is included in the Mini-SDK, you'll find it in your sdk-tools folder. :)

Just say -

md5sums name-of-file.zip (or img or whatever)

You can ignore the adornments in the output, you only care about the actual checksum value.

By the way, you can verify md5 checksums on your phone - Check out "AFV File Verifier for Android™"

https://play.google.com/store/apps/details?id=sa.afvx

Absolutely free, no spyware or garbage.

Personally, that's my favorite. Get the rom zip on to the phone, check it there because that's the point where you're going to be using it.
 
Btw - for your protection - first things after installing TWRP -

Do NOT let it automatically install superuser for you. Just say no to that.

Do make a (nandroid) backup of the new stock, right away, unrooted and all. Back it up to your pc for safe keeping. There's nothing like a good stock backup.
 
You must log in or register to reply here.
Back
Top Bottom