Root [T-Mobile] M7 no OS - HELP please

[Recon11C]

ubuntu@ubuntu:~/Downloads/sdk-tools$ sudo ./adb-linux devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached

ubuntu@ubuntu:~/Downloads/sdk-tools$

 

[Recon11C]

Now when I double click the phone icon it gives me

Unable to open MTP device '[usb:002,009]

 

[EarlyMon]

Now when I double click the phone icon it gives me

Unable to open MTP device '[usb:002,009]

Because you don't have an operating system up and running on your phone.

 

[EarlyMon]

Now with TWRP, adb sideload on, do -

sudo ./adb-linux sideload ViperOne_7.0.2.zip

 

[Recon11C]

ubuntu@ubuntu:~/Downloads/sdk-tools$ sudo ./adb-linux sideload ViperOne_7.0.2.zip
loading: 'ViperOne_7.0.2.zip'
error: device not found
ubuntu@ubuntu:~/Downloads/sdk-tools$

 

[EarlyMon]

Yeah. I saw it not respond to the devices command but expected that to sometimes happen.

And adb sideload is on in TWRP, you can see that on the phone screen?

 

[Recon11C]

Yes it is on, and the thinking bar is moving.

Would installing the OS on my hard drive have any impact?

 

[EarlyMon]

Yes it is on, and the thinking bar is moving.

Would installing the OS on my hard drive have any impact?

Nope, no impact, I've done this too many times to count just the way you're set up.

Can you move the cable to another usb port? We definitely don't want it in a USB 3 port.

I trust the cable because it has identified the Android phone in the left panel.

If that fails, reboot the phone into TWRP again, give it another try.

 

[Recon11C]

i rebooted and then switched the USB port to a different usb 2.0 port. I am getting the same error.

 

[EarlyMon]

If it's still failing, we can update TWRP -

http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.8.4.0-m7.img

I already tested that link.

After downloading with Firefox, do -

cd ..
mv openr* sdk-tools
cd sdk-tools

Power down phone. Power on while holding volume down key.

Screen on phone should say FASTBOOT USB - stop if it doesn't.

Back to the command window -

sudo ./fastboot-linux flash recovery openrecovery-twrp-2.8.4.0-m7.img

Reboot into TWRP, adb sideload on, repeat the sudo adb-linux sideload command as before.

 

[Recon11C]

Ok - downloading now.. very slowly =o)

 

[EarlyMon]

Yeah, I feel for you on that.

The updated TWRP does the adb sideload operation a bit differently under the hood than your current version.

While you're waiting on the download, go ahead and get through the hassle of putting the phone in FASTBOOT USB mode.

After that and after the download completes, remember to run the three commands beginning with "cd .." - you can copy and paste all three at once into the command window.

 

[EarlyMon]

If the phone doesn't say FASTBOOT USB highlighted nearer the top, if it just says FASTBOOT, unplug and plug in the USB cable at the phone.

 

[Recon11C]

ubuntu@ubuntu:~/Downloads/sdk-tools$ cd ..
ubuntu@ubuntu:~/Downloads$ mv openr* sdk-tools
ubuntu@ubuntu:~/Downloads$ cd sdk-tools
ubuntu@ubuntu:~/Downloads/sdk-tools$ sudo ./fastboot-linux flash revovery openrecovery-twrp-2.8.4.0-m7.img
sending 'revovery' (11994 KB)...
OKAY [ 1.867s]
writing 'revovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.924s

 

[Recon11C]

oh.... typo... I'll fix that

 

[Recon11C]

ok, what did I break?


ubuntu@ubuntu:~/Downloads$ mv openr* sdk-tools
mv: cannot stat ‘openr*’: No such file or directory

 

[Recon11C]

I guess the file has gone? I'm downloading it again

 

[EarlyMon]

ok, what did I break?


ubuntu@ubuntu:~/Downloads$ mv openr* sdk-tools
mv: cannot stat ‘openr*’: No such file or directory

The move (mv) was right the first time.

It's saying that the file is corrupted.

Get back to the sdk-tools folder -

cd sdk-tools

Now say -

md5sum openr*

You should get the value shown -

 

[Recon11C]

Yes. got that value
ubuntu@ubuntu:~/Downloads/sdk-tools$ md5sum openr*
1060cbe5131edb0cc6c235a6d488721e openrecovery-twrp-2.8.4.0-m7.img
ubuntu@ubuntu:~/Downloads/sdk-tools$

 

[Recon11C]

ubuntu@ubuntu:~/Downloads/sdk-tools$ sudo ./fastboot-linux flash recovery openrecovery-twrp-2.8.4.0-m7.img
sending 'recovery' (11994 KB)...
OKAY [ 1.880s]
writing 'recovery'...
OKAY [ 0.826s]
finished. total time: 2.706s
ubuntu@ubuntu:~/Downloads/sdk-tools$


but when I rebooted the device it still says v2.6.0.1

 

[Recon11C]

Actually, I just had to manually put it into recovery mode, then it changed updated.

and now... IT'S INSTALLING VIPER!!!!!

=o)

 

[Recon11C]

I can't thank you enough....but before I do anything stupid, should i select "Install ViperOne" on the phone.. gives me a couple options... Change Log, Flash Extras, etc

 

[EarlyMon]

You can always go back and add extra.

Just roll with whatever the defaults are, get it up and running.

As soon as it's finished and you've booted - first one will take a while - go back to TWRP and make a nandroid backup.

If the install goes well but it doesn't boot, don't panic - let me know. Sometimes we have to give an s-on model a little push.

Otherwise - congrats on getting it done.

 

[EarlyMon]

OK, lol, with all you've been through, here's what you do if it won't boot up after the install.

Command window -

unzip -j ViperOne_7.0.2.zip boot.img -d .

sudo ./fastboot-linux flash boot boot.img


Note the spacing and the dot at the end of the first line, it means "put it right here."

That way if you have the issue, ask, and I'm gone again for a bit, you won't be stuck waiting.

If your boot up worked after the sideload, ignore this post.

It's just for s-on phones and only when necessary to get normal booting right after a rom flash. It's just as normal to have to do this as not.

If you have Linux buds and you want to get your brag on with them, call the command window a terminal, or, terminal window.

Let me know how it's going when you can.

 

[EarlyMon]

And yes, install ViperOne.

Sorry I missed the question.