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

Root I broke it. Help please?

Mabster

Android Enthusiast
Well I think I need some help, hopefully somebody can point me in a direction to fix this.

I rooted my phone way back in week one of release using the http://androidforums.com/evo-4g-lte...-mac-linux-one-click-partial-root-method.html

Today I installed GooManager from the play store and got the current version of TWRP.

Obtained S-off using http://androidforums.com/evo-4g-lte...panda-s-htc-dev-ltevo-root-dummies-guide.html

Created a nandroid and transferred it to my computer for safe keeping.

Performed a cache, dalvic, factory reset, and system wipe using TWRP.

Flashed a rom ([ROM][9.17.12][2.10]Stock w Goodies - True Multitasking // Extended Music EQ - xda-developers if it matters) and walked away since the flash can take a while.

Came back to my phone hung on the white "HTC quietly brilliant" splash screen. Holding the power button causes the three soft buttons to flash.

Holding the power button causes the three soft buttons to flash. That's the only response it get.

I tried using [Windows] RegawMOD Rebooter 1.2 | Updated 06.14.12 - xda-developers but the program says no device connected.

I'm on HBOOT 1.12 and stock software (1.13?).

Anyone have any ideas for me?
 
Hey compadre, long time no chat! Sorry for the grief.

Could have been a flash gone wrong, I'll recommend a re-flash, so we need to get you into recovery.

If you don't have adb, please just grab the Mini-SDK here, you won't need the whole enchilada -

our forums' mini-sdk

It's got the goods for Win, Mac and Linux, ignore the two you don't need.

Please unzip that, go into the directory with adb and its dll files with your phone plugged in, and try -

adb reboot recovery

With a little luck, we can get you back to your TWRP screen for a reflash.

BTW - after the 3 buttons flashed, did you continue mashing down on the power for a few more seconds (they act as a reset warning) - and get it to try to power up again?
 
EarlyMon, just the man I was hoping to see. Long time no chat as everything has been running perfectly till today.

First, I mashed the power till my heart was content and nothing happened. Just did it again for even longer, it forced a reboot but then hung on the splash screen again.

Going to go try the adb reboot recovery now.

I'll be back.
 
Device not found
:(

Edit: Ok here's progress. In that split second in between reboots I was able to hold the volume down and tap the power to force it into HBOOT and into recovery from there.

Looks like the rom zip file is corrupt as it's unable to open it.

I did screw up and not leave a nandroid on the phone to restore.

How can I pull the nandroid off my pc and put in on the phone? PC won't recognize that the phone is plugged in.
 
Figured out how to use TWRP to mount/unmount the phone so the PC would recognize it but the internal storage structure is missing from what I see. I'm not sure where to put the nandroid image so that TWRP will find it and restore.

Currently I'm downloading another zip to try to flash.

At least some progress is being made. I'm confident this will get worked out.
 
Sorry for the delay, they're keeping me busy. :(

OK, glad you got into recovery with the volume trick, that was going to be my next suggestion.

In TWRP, there's an option to set your sd card as mountable for PC transfers.

I'll go into mine to look for the right menus and such, unless you get there first.

Once there, it ought to show as a usb mass storage - I think.

I've used the feature, I know it works, I just need to refresh my head on the details.

You have an external sd card, yes (assume so, because you got s-off going) - and also, just in case it triggers a memory or something, which Windows are you running?
 
Figured out how to use TWRP to mount/unmount the phone so the PC would recognize it but the internal storage structure is missing from what I see. I'm not sure where to put the nandroid image so that TWRP will find it and restore.

Currently I'm downloading another zip to try to flash.

At least some progress is being made. I'm confident this will get worked out.

Ah, ninja'd again.

The file structure (for both internal or external sd) is:

TWRP/BACKUPS/HT25FS409294/

then folder containing the nandroid files.

Example -

Code:
Earl:HT25FS409294 earl$ cd ../../../ext_sd/TWRP/BACKUPS/HT25FS409294/
Earl:HT25FS409294 earl$ ll
total 0
drwxr-xr-x  3 earl  staff  102 Sep 15 15:19 ./
drwxr-xr-x  3 earl  staff  102 Sep 15 15:19 ../
drwxr-xr-x  8 earl  staff  272 Sep 15 15:25 viper-1/
Earl:HT25FS409294 earl$ ll viper-1
total 3592040
drwxr-xr-x  8 earl  staff         272 Sep 15 15:25 ./
drwxr-xr-x  3 earl  staff         102 Sep 15 15:19 ../
-rw-r--r--  1 earl  staff    16777216 Sep 15 15:19 boot.emmc.win
-rw-r--r--  1 earl  staff          48 Sep 15 15:19 boot.emmc.win.md5
-rw-r--r--  1 earl  staff  1026203648 Sep 15 15:25 data.ext4.win
-rw-r--r--  1 earl  staff          48 Sep 15 15:19 data.ext4.win.md5
-rw-r--r--  1 earl  staff   796130816 Sep 15 15:29 system.ext4.win
-rw-r--r--  1 earl  staff          50 Sep 15 15:25 system.ext4.win.md5
 
....just in case it triggers a memory or something, which Windows are you running?

BUSY?!!? I'm not the only one here?;)

Win7.

Either the internal memory is gone, or TWRP only allows access to the sdcard....

Created the twrp folders and am now copying the 1.4G nandroid back to the phone.
 
They did have sd card access bugs at one point, once this is all cleared up for you, maybe update TWRP to the latest, should be able to get to either one with a later version.
 
I just got the most recent TWRP through GooManager today. I was getting a windows popup asking for me to "insert the last disk of multi-volume disk" every time I tried to mount the internal storage. Wierd.

Anyway, I'm back in the game.

TWRP wouldn't see the nandroid in the file structure I created but I made another quick backup so that it created the folder structure for me on the sdcard and moved the previous nandroid into there. TWRPs finally saw it and the restore was successful.

:beer:

Now I gotta go figure out what went wrong in the first place. I'll start with reinstalling twrp.
 
I saw you're S-OFF, you could always just flash things like recoveries through the bootloader with a PJ75IMG. Just another path to get there. ;)

Glad you got things squared away in the end tho. :)

A good practice before flashing anything is to check and be sure the MD5SUM matches what the dev posts with the file.
 
Also, while you're in the neighborhood, make sure you're running LazyPanda 1.12.2222 as hboot if you haven't already. :)

When I did s-off I was on 1.12.1111 but I do it to 1.12.2222 after that. But what does this do?

Is this like Hboot 1.12, 1.15 and 1.19 ? I thought this is not Lazypanda stuff.
 
When I did s-off I was on 1.12.1111 but I do it to 1.12.2222 after that. But what does this do?

Is this like Hboot 1.12, 1.15 and 1.19 ? I thought this is not Lazypanda stuff.


Good question.

H-boot 1.12.2222 adds back the fastboot adb abilities. It looks like it was left out/disabled for some reason on hboot 1.12.1111. They released 1.12.2222 shortly after lazypanda was released to fix that bug
 
Back
Top Bottom