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

Root no os

ok, I forgot that version of TWRP foobar's reporting of the OS version (you should have firmware version numbers next to OS- ). If memory serves correctly from the bootloader version and if you thought it was running Android 4.4.2 you most likely have 1.54.xxx.x firmware. What I don't know is what that version of Viper is based off - if it's newer you might find first boot takes a long time and some things might not work correctly (wifi and maybe other stuff).

Ok, do you have Viper rom and/or CM12 copied on to your micro sd card, and card is in phone?

Then follow the instructions in EarlyMon's post #10, that is:

sdk-tools are set-up
TWRP 2.8.5.0 img file is in sdk-tools folder
Viper and/or CM12 rom zip files copied to sd card and sd card is in phone

then:

Phone in FASTBOOT mode, plug in to PC (should see FASTBOOT USB on white bootloader screen)

Open command window to sdk-tools folder (shift + right click on the sdk-tools folder name, open command window here) and type:

fastboot devices (you should get a string on characters/numbers - this is your phone's serial number, as a check fastboot connects to phone ok)

type:

fastboot flash recovery openrecovery-twrp-2.8.5.0-m8.img (check you see [OKAY] message for successful flash)

From FASTBOOT go to HBOOT using vol down button and select using power button

In HBOOT go to RECOVERY (again vol down and power to select)

You should see the TWRP screen, then buttons.

Install rom (check/change TWRP file location to the external sd card folder where you copied the roms)

Reboot.

Come back and let us know how you got on :)
 
i tried tille the OKAY MESSAGE step i did it...there's nothing written after the OS- i confirm it was 4.4.2...
i have the cm12...i tried recovery...now it dont go to the recovery,..it keep show
Entering recovery...
 
Rewind a bit, did you follow the steps through to flashing the recovery and getting [okay]. If so did you check the md5 of the TWRP download as it may have been bad?

Is it still stuck at Entering recovery? Press and hold vol up + power button until screen goes black then quickly hold power down - this should get you back to bootloader. Check the recovery md5 value on download site with your download, in command prompt type:

md5sums openrecovery-twrp-2.8.5.0-m8.img

If numbers match, download was OK, if not download twrp again and recheck.

Plug phone in to PC, and make sure you have FASTBOOT USB.

Fastboot flash recovery again.

Then type:

fastboot erase cache

Then boot to HBOOT, and Recovery again.
 
From the link to the techerrata site in EarlyMon's previous post, if you click it again the md5sum value is on the download page. Compared this with the md5 of the TWRP you downloaded using the above commands.
 
Patience, one step at a time. No reason to think it won't work, you already got TWRP 2.7.0.0 on there [emoji6]
 
My bad for not explaining properly. You do the md5sums check on your PC using command prompt same way as fastboot . The md5sums tool should be in the same sdk-tools folder as the fastboot tool and the TWRP you downloaded and saved on your PC.
 
Wait now I'm confused. What do you mean by "TWRP where to find it?". As per previous posts, did you download the sdk-tools zip and unzip it to sdk-tools folder on your PC? Did you download the TWRP version from the link and save, or copy it to the sdk-tools folder?
 
OK, in the sdk-tools folder do you have a file called md5sums.exe in there.

Run the md5sums command from the command prompt window - does the value returned match the number listed on the techerrata site?
 
No, but we need to check you didn't get a bad download of the recovery. I wonder if it's your bootloader version stopping the latest recovery from starting. Let's try this. First make sure you have grabbed the sdk-tools.zip from here - scroll to the bottom of that post, where the zip file is attached - and check you have the md5sums.exe set up as well as fastboot:

http://androidforums.com/threads/adb-guide-updated-2014-11-11.443072/#post-5389081

Go here and download this TWRP version:

http://dl.twrp.me/m8/twrp-2.8.0.3-m8.img

This is the version I first installed on my M8 when I had same bootloader version and firmware as you so I know for a fact it works.

Check the md5 of the download, against the value on the website - the md5 link on the website is at the top, I've copied it here as well:

aef8193a8142f9450f7438901095ed2f - make sure it matches your download.

Also does fastboot recognise the phone - did you try the fastboot devices command?

If everything checks out fastboot flash this recovery and then try and enter via HBOOT.
 
I'm in Scotland so might be too late to still be up. But don't panic, we can get you sorted and pretty sure @EarlyMon will drop in again at some point.
 
Don't do the SDK download.

Use the Mini-SDK that I linked earlier on.

The full SDK does not have the md5sums tool.

If you're looking for md5.exe then you're not using the Mini-SDK I linked - it's a download named sdk-tools.zip - unzip it and it creates an sdk-tools folder.

I'm mostly out of town today, sorry, unexpected, so I can't do more.

Follow @saltire instructions exactly.

@saltire - the date and radio version are enough to establish that this phone won't support Lollipop completely, as I suspected, so ViperOneM8 3.x that I mentioned earlier would be right.
 
You must log in or register to reply here.
Back
Top Bottom