Root Recovery for commando

[jova33]

yeah, warranty doesn't cover abuse lol

 

[Spike G]

bummerrrrrr hahah, what if you brick it on purpose and say after it updated it never turned on. I'm sure they had a bunch of people claim the updates are messing up their phones since that was the only way to update after 2.2.1 root *shrug*

 

[aus4000]

do someone have update.zip file, the official ones?
so i can update via this custom recovery
still on froyo

Don't try to use the Verizon updates through GNM's recovery, When you do and your phone restarts, you get constant messages that say that core system utilites need force closing, but here's the .dat file for M080:
https://dl11.innopath.com/prod/v1/fota/6972396.dat?j=171143378&m=1&j=2tw72q
you can find the websites for all of them if you have a failed update (if I remember right) in /data/data/com.innopath.activecare

 

[paxchristos]

@aus4000- have you looked into spoofing the original recovery to accept a custom update file? Also, do you know what kind of checksum it uses, I don't recognize it at all...

Sent from my R800x using Tapatalk

 

[aus4000]

@ paxchristos- No, never tried, but that could work. No idea about the checksum, either. If you wanted to try to apply the update with stock un-spoofed recovery, you have to blank out parts that check for VZNavigator.apk and wGzWeatherWidget.apk (unless you didn't go on a total debloat rampage) or it won't even attempt to update. (this might go with all updates, so flashing the old recovery with the new .dat right after it downloads the original .dat file and then letting it update might let you get away with it, one could also make a M100 update with the Superuser.apk and su command in the update, thus giving you root with M100)

 

[paxchristos]

@ paxchristos- No, never tried, but that could work. No idea about the checksum, either. If you wanted to try to apply the update with stock un-spoofed recovery, you have to blank out parts that check for VZNavigator.apk and wGzWeatherWidget.apk (unless you didn't go on a total debloat rampage) or it won't even attempt to update. (this might go with all updates, so flashing the old recovery with the new .dat right after it downloads the original .dat file and then letting it update might let you get away with it, one could also make a M100 update with the Superuser.apk and su command in the update, thus giving you root with M100)

You just have to remove the first 1130 lines or so... they're the checks (at least in M070)

Does the M080 update have a radio.diff file in the bin (zip) archive?

Sent from my R800x using Tapatalk

 

[aus4000]

Yup, it sure does. Is that the radio baseband update?

 

[paxchristos]

Yup, it sure does. Is that the radio baseband update?

If I'm guessing correctly, yes... no we need to figure out how to make radio.diff flashable...

Sent from my R800x using Tapatalk

 

[computergeek24]

apparently i have drawn a blank. I can't get some .dat files to open. Can anyone help me with this? either linux or windows

 

[brilars10]

When you say "2. Place the recovery.img you downloaded in this folder in /sdcard/recoveryflash and then turn off sdcard as mass storage."

What exactly do you mean? Where is the recovery.img file? Do I have to create it somehow?

 

[Spike G]

this file...
recovery-ra-commando-3.06-gnm.img

 

[brilars10]

this file...
recovery-ra-commando-3.06-gnm.img

Where do I find this file? Is it already on the phone? Do I create it with an app like Rom Manager?

 

[jova33]

What is this file in /system, recovery-from-boot.p ?

 

[paxchristos]

What is this file in /system, recovery-from-boot.p ?

Can you open it? (otherwise if you have terminal emulator installed try this command "cat /system/recovery-from-boot.p > /sdcard/recovery_boot.txt" & upload that)

 

[jova33]

opened it as a text document. just a bunch of garbled text to me. what can you make of it? oh and it was too big to attach as a txt

 

[brilars10]

Where is recovery.img located? My system folder contains 10 folders and 2 files. I do not see the file recoveyr.img

 

[jova33]

Go up like three posts above yours

 

[brilars10]

Yes, I see that Spike G posted the file. I want to know where to find it on my phone. It is not in the system folder.

 

[jova33]

The download file on your sd card?

 

[brilars10]

Please read this very carefully. I do not think you understand what I am asking.

No. The zip file that I downloaded "recoveryflash.zip" contains these files: busybox, dump_image, flash_image, README, reboot, and recoveryflash.sh.

The instructions say: Place the recovery.img you downloaded in this folder in /sdcard/recoveryflash and then turn off sdcard as mass storage . (Do not rename the recovery.img from the download)

So! Here is the question again. There is not a file called recovery.img in the recoveryflash folder created by unzipping the recoveryflash.zip AND it says to place that file into /sdcard/recoveryflash. That in an of itself tells me it is not in the folder if I have to place it (recovery.img) in the same folder.

 

[jova33]

this file...
recovery-ra-commando-3.06-gnm.img

You download this file. This is the recovery.img file specific for the commando

 

[brilars10]

You download this file. This is the recovery.img file specific for the commando

Thank you. Where did you or Spike G download that file from? Starting at the very beginning of this thread, I did not see anything about getting that particular file separately.

 

[brilars10]

I got the recovery installed. This may be a stupid question, but what is the next step? Do I select Backup/Restore? and backup the X items?

 

[jova33]

I lurked the all in one recovery thread by getitnowmarketing until I found the answer. I think I might have asked for it.

What now? Create a nand backup, and go to work f***ing up your phone knowing that you can always restore your nand. If something says -warning! May cause boot loops- go for it, cause you can revert back to your backup

 

[brilars10]

I lurked the all in one recovery thread by getitnowmarketing until I found the answer. I think I might have asked for it.

What now? Create a nand backup, and go to work f***ing up your phone knowing that you can always restore your nand. If something says -warning! May cause boot loops- go for it, cause you can revert back to your backup

Well, hopefully, that will never happen. If it does get caught in a boot loop, which I have never seen thankfully, what would one do? I guess what I am asking is should I have USB debugging always on so when I plug connect to my pc, I would be able to activate the restore?