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

Root Recovery for commando

Oops...

paxchristos said:
Ok, what am i doing wrong, ?
Click to expand...


Sorry, I wasn't saying you were wrong. I answered a different thread in this one and then couldn't delete my post so I edited out my post for the other thread and then added something for this one. Sorry again for accidentally calling you out like that.
 
Once i finally committed to doing this, its stupid easy. Just read the full post on the how to page and it took me under 2 minutes with no mistakes. Just made my first nandroid of my modified 2.2.1 backup, thinking about doing 2.2.1 stock before i flash a 2.3.3
 
Alright...

The gingerbread system & boot images are here:

http://www.4shared.com/file/mAEpQ6fC/BS-20111129-2052.html

Now, I used schmude07's nandroid and restored my phone with it. It booted into 2.2.1, but I had no baseband and the cellular radio and battery meter did not work. So I suppose I did something wrong. Should I remove everything but the system & boot img files and the md5? Will it work - that big of a change should cause some problems. I want to experiment, but I don't want to brick.
 
rjglenn said:
Now, I used schmude07's nandroid and restored my phone with it. It booted into 2.2.1, but I had no baseband and the cellular radio and battery meter did not work. So I suppose I did something wrong. Should I remove everything but the system & boot img files and the md5? Will it work - that big of a change should cause some problems. I want to experiment, but I don't want to brick.
Click to expand...

Were you running 2.3.3 then restored into 2.2.1?
 
Yes, I went back to 2.2.1 but the radio did not work and I had no signal. In the "about phone" section it said the baseband was unknown.

I get it. The nandroid must be made with only the boot and system files and nothing else. When I went into the nandroid and deleted everything but the boot & system img and md5 it would not work. I suppose a checksum problem. I am now uploading a gingerbread nandroid made with only the boot & system img so the md5 will match.

Schmude07: please make and post a new nandroid that only has the boot and system image files.

Here is the link to the gingerbread nandroid:

BS-20111129-2052.zip - 4shared.com - online file sharing and storage - download

Exciting times nonetheless...
 
thanks for the link. I'll be giving this a try, but just to be sure, i can save the nandroid i made today and recover from a new one and still go back to exactly how it was today?

oh, btw
spike-g-albums-commando-picture4739-recovery.jpg

:)
 
It works kind of like windows restore points but better. If you made a full nandroid and then restored it 5 years later then your phone would be just like it was when the nandroid was made.

Since you are still on 2.2.1, please make a nandroid using only the boot.img and system.img and then post it somewhere so we can download it.
 
i would need to wipe my phone to do that correct? i want to fool around with this but i love it the way it is right now, i'm going to put a different sd card in with the nandroid i have now and mess with that, if you could run me through how to do this so i dont mess up completly, i'd be happy to provide 2.2.1 img files
 
No, you will not need to wipe your phone. You will only be creating a backup of the boot section and operating system and will not include your user data.

Reboot into recovery. Select backup/restore from the home menu. In the next menu select Nand backup. In the next menu there will be a list with check boxes on the left. Scroll through and ensure that only boot & system have an x in the boxes, leave all the others un-xed (?) then go to the bottom and select "Perform Backup".

What this does is creates a nandroid with the correct md5 checksum for the boot information and the operating system. It does not move any of the user data as that is all stored in the data section.

When you go into your SD card with your computer or file explorer the nandroid will be located on the SD card in a folder named nandroid. That folder opens to another folder that is used to identify the device to the recovery program. Your actual nandroids are in this folder and are named by which files they contain and the date and time they were created i.e the one I made & posted earlier is called BS-20111129-2052 because it containes the boot & system images and it was made on 29NOV2011 at 2052 UTC.

It would be a great idea to wipe the dalvik cach before rebooting the phone after restoring (replacing) the boot and system images because otherwise things are going to be weird.
 
I don't think that would be a good idea...

but you can try it. Worst case is you go into a boot loop and would need to call recovery with adb.
 
Successfully updated from 2.2.1 to 2.3.3 without losing root! Unfortunately i also do not have service and get the "baseband unknown"...
 
Fix it back by going into recovery & restoring your nandroid. On the 2.3.3 to 2.2.1 from it bootloops. Fortunately I can go into recovery with adb.

It almost works. It gets to the VWZ screen with the progress bar with the "initializing, please wait". It freezes and then reboots. Not good. So I have some more research to do.
 
mine also did the initializing please wait screen and i held my breath but i had a successful boot into 2.3.3 with root privileges already which was nice. Maybe if we make another nandroid with more than just the boot and system? what does the .android_secure do? i'm assuming data would just be my preferences and such and sd-ext is sd card contents? also what about clearing the cache? or other things. Also it may seem dumb, but did you clear your dalvik cache again when you restored my .img?
 
would updating to 2.3.3 and doing a factory reset do anything? also how hard would it be to get back to how i was if it doesnt? would i need to root again to do it?
 
Spike G said:
Maybe if we make another nandroid with more than just the boot and system?
Click to expand...

Something is missing, I'm just not sure what. What is your baseband on 2.2.1?

Spike G said:
what does the .android_secure do?
Click to expand...

This is where apps that are apps that are moved to the SD card go. It's just a backup of the .android_secure folder from the SD card.

Spike G said:
i'm assuming data would just be my preferences and such and sd-ext is sd card contents? also what about clearing the cache? or other things. Also it may seem dumb, but did you clear your dalvik cache again when you restored my .img?
Click to expand...


When I did a complete wipe I was able to boot into 2.2.1, but the baseband was unknown and the cellular radio did not work. We are missing a crutial step here, and we need to quit before one of us loses a phone. Someone more knowledgeable will step in and tell us what we are doing wrong.
 
Mine says baseband version 1 on 2.2.1, i've gone back and forth between the two and i'm not seeing anything that would help me aside from maybe doing a factory reset in 2.3.3 but i havent tried it
 
Please just standby at least over night and see what shakes out. We are doing something wrong and may end up with a problem.
 
jova33 said:
Almost a big leap forward. I'd like to go back to 2.2.1 as soon as someone figures this out.
Click to expand...

I'm curious as to why you want to go back, i've heard a lot of people saying this, is it mainly because of the status bar?
 
The commando on 2.2.1 with all the bloatware removed runs very well with no lag, no stutter and no crashes. It seems to have better battery life too. The commando running 2.3.3 has some stutter and lag, and seems to use more battery. My experience had been that it has some force close issues with some applications that it did not have on 2.2.1. I actually prefer the status bar on 2.3.3, but other than that I see no improvement.

Others may have had different experiences and may think I am totally wrong. YMMV.
 
rjglenn said:
The commando on 2.2.1 with all the bloatware removed runs very well with no lag, no stutter and no crashes. It seems to have better battery life too. The commando running 2.3.3 has some stutter and lag, and seems to use more battery. My experience had been that it has some force close issues with some applications that it did not have on 2.2.1. I actually prefer the status bar on 2.3.3, but other than that I see no improvement.

Others may have had different experiences and may think I am totally wrong. YMMV.
Click to expand...

I know Spike already uploaded his 2.2.1 boot and system backup, but would it help if I did also? I was really looking forward to upgrading to 2.3.3 but since everyone seems to want to go back, maybe I should just stay put :confused:.
 
The problem is if the nandroid didn't come from your phone, it doesn't seem to have a recognizable baseband and the cellular radio doesn't work. No radio=no connectivity. I took my phone back to 2.2.1 and initially had a bootloop. When I did a full wipe it booted normally into 2.2.1, but there was no signal in an area that normally has excellent signal and was working just moments before. So until someone helps us figure out how to work around this we are stuck.
 
You must log in or register to reply here.
Back
Top Bottom