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

Root no os

Is it the sdk-tools.zip you downloaded - small file about 1.7 MB size? If so you extract the files from that includes adb.exe, fastboot.exe and md5sums.exe.

Then make sure recovery (2.8.0.3) is also in sdk-tools folder.

First step is to check the recovery download didn't get corrupted. This involves no flashing. Open a command prompt window in the sdk-tools folder and type:

md5sums <exact name of recovery>.img

And check the string of characters matches the string in my post above.

Then with phone in fastboot mode, plug in to PC, check fastboot connects OK by typing:

fastboot devices

Check you get phone serial number returned in command prompt window.

Then you flash the recovery, by typing :

fastboot flash recovery <exact name of 2.8.0.3 recovery>.img

Check flash was successful, get [OKAY] message in command prompt.

Then just to make sure, type :

fastboot erase cache

Then on phone in Fastboot menu enter HBOOT (vol down / power to select), then Recovery in Hboot menu.
 
the phone gets to the fastboot usb..yes im using the 1.7 sdk files...i flashed with 2.8.3.0 it says waiting for devices but on mobile its fastboot usb
 
C:\sdk-tools>md5sums openrecovery-twrp-2.8.3.0-m8.img

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help

[Path] / filename MD5 sum
------------------------------------------------------------------------
Error: Unable to read file/directory openrecovery-twrp-2.8.3.0-m8.img
 
C:\sdk-tools>md5sums.exe

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/

Usage: md5sums.exe [OPTION] filespec1 [filespec2 ...]

OPTION switches:
-B Base64 encoded output, instead of default hex format
-b Bare output, no path headers
-e Exit immediately; don't pause before returning
-n No percent done indicator
-p Pause before returning (incompatible with -e)
-s Display statistics at end (hashing speed)
-u Mimic output of UNIX md5 command (implies -b, -n)

Examples:
md5sums c:\temp
md5sums original.doc copy*.doc backup*.doc
md5sums -n -e d:\incoming > log
 
Then with phone in fastboot mode, plug in to PC, check fastboot connects OK by typing:

fastboot devices
what you mean by it ?
 
You must make sure you get the exact name of the recovery img right. The one I think will work is 2.8.0.3

Right if md5 matches, on to the next steps.
 
after it matches i type fastboot device in the same CMD it says waiting for device..
Remember i flashed 2.8.0.5 earlier..it got stuck to enter recovery
 
i will catch some sleep i will be back in 7 hours..

The phone says fastboot usb...but waiting for device of cmd ! help for this :)
 
i just tried the 3.1.0 too...it flashed successfully to the carrier....i rebooted....waiting since 10 mins... nothing happening
 
@saltire help me with the rom :/
@EarlyMon please guys search a really good rom that will really flash for me...
i tried 3.2.1 3.2.0 when i reboot system nothing happens..
Remember i was using android 4.4.2
 
Last edited:
Ok, you will probably have to flash the Viper boot image file separately in fastboot. On your PC, go to the folder where you downloaded the Viper rom zip. What zip compression tool do you use? Open the zip file and/or extract contents of the zip file on to your PC - probably a either a double-click, or a right click and an option to "extract here" or something similar. As an aside, I prefer to use this utility here for working with compressed files:

http://www.7-zip.org/

Once you have the zip file contents extracted, we need to find the boot.img file - it will usually just be in the root directory of the zip file, and therefore should sit in the folder where you just extracted the zip file contents. The boot.img file needs to be in the sdk-tools folder where you have already set up fastboot and md5sums - if it's not copy it over.

Then boot phone in to bootloader again, plug in to PC so you see FASTBOOT USB on the phone screen. Open command prompt in the sdk-tools folder. Then type:

fastboot devices (just to check fastboot connects)

then type:

fastboot flash boot boot.img

check that file is sent and flashed successfully - get the [OKAY] message in command prompt window.

Then to reboot, type:

fastboot reboot

Phone should now reboot, which might take a few minutes and you should then get to phone set-up screens. Once booted, I'd recommend you go to Settings > Developer Options and tick the USB Debugging option. If you don't see Developer Options go to About > Software Information > More and then press Build Number 7 times - you should see a message saying something like you're now a developer and the Developer Options will be available in Settings. At least that's where this lies on my rom, Viper might be slightly different.
 
You must log in or register to reply here.
Back
Top Bottom