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

Root Froyo restore method

Biotic

Biotic

Android Expert
Does anyone here have a restore method for the commando. Restore it to factory firmware release? Or a completely stock nandroid backup? So after restoring it and the recovery to stock, one could upgrade the software successfully to gingerbread?

P.s. anyone working on a custom rom for the commando, happy to help
 
rgocal said:
Does anyone here have a restore method for the commando. Restore it to factory firmware release? Or a completely stock nandroid backup? So after restoring it and the recovery to stock, one could upgrade the software successfully to gingerbread?

P.s. anyone working on a custom rom for the commando, happy to help
Click to expand...

Currently, there is no way to restore to a factory firmware setting (i.e. have everything setup like the day you got it outta the box)

There are a couple of nandroid backups floating around (GNM Recovery thread) but I don't think any of them are completely stock.

The one issue we're running into right now is the baseband/how the baseband is interacted with has changed, and we don't have a good radio.img to flash.

That and the bootloader is a pain in the butt to get to a state where you can flash images...

If you can share any pointers on developing custom roms, right now i'm working on a custom kernel (check my github, username paxchristos) for this phone, but I bricked my test device, and i'm waiting for a new one before I commence again (i need to check something...)

Pax
 
Wel the first thing you should do once you get a new commando is make sure everythings stock in froyo and root and do a nandroid backup.

As far as custom roms go. I have no skills in kernel development but as far as a rom go. I could do it.

We need a restore method made so that everyone can be on the same page. You cant make a custom rom and leave people behind, being the people stuck on froyo doing something stupid or mistaken (fiance...) anywho...
 
rgocal said:
Wel the first thing you should do once you get a new commando is make sure everythings stock in froyo and root and do a nandroid backup.

As far as custom roms go. I have no skills in kernel development but as far as a rom go. I could do it.

We need a restore method made so that everyone can be on the same page. You cant make a custom rom and leave people behind, being the people stuck on froyo doing something stupid or mistaken (fiance...) anywho...
Click to expand...


Agreed, and i feel as though froyo would be a better base for a custom rom even though i dont know much about making roms but it seemed to run more smooth apparently. I'm one of the ones stuck on froyo here and i'm really interested in developing this phone so it'd suck to be left behind. however rgocal, i have a nandroid of near stock but there is bloat removed from 2.2.1 but the baseband problem will still exist. i know another user has flashed it and successfully gotten back to 2.2.1 but with no signal or 3g so untill we figure out this baseband switch i'm not sure what we can do about it
 
rgocal said:
Wel the first thing you should do once you get a new commando is make sure everythings stock in froyo and root and do a nandroid backup.

As far as custom roms go. I have no skills in kernel development but as far as a rom go. I could do it.

We need a restore method made so that everyone can be on the same page. You cant make a custom rom and leave people behind, being the people stuck on froyo doing something stupid or mistaken (fiance...) anywho...
Click to expand...

Spike G said:
Agreed, and i feel as though froyo would be a better base for a custom rom even though i dont know much about making roms but it seemed to run more smooth apparently. I'm one of the ones stuck on froyo here and i'm really interested in developing this phone so it'd suck to be left behind. however rgocal, i have a nandroid of near stock but there is bloat removed from 2.2.1 but the baseband problem will still exist. i know another user has flashed it and successfully gotten back to 2.2.1 but with no signal or 3g so untill we figure out this baseband switch i'm not sure what we can do about it
Click to expand...

I'm getting a "new" commando on monday (to work with) so I will be starting again, soon. I have a few ideas that I want to test out, and I'll respond either here or in the new forum if I get anything...

Froyo was a nice os, but stock gingerbread is better battery/speed.
 
First goal
-get everyone to gingerbread / extract and create flashable gingerbread based baseband so a gingerbread nandroid flash will be successfull.
-get kernel built for custom rom /load up a crap ton of battery and system optimizer scripts in custom rom.
-either make new rom or port mine over to commando
 
rgocal said:
First goal
-get everyone to gingerbread / extract and create flashable gingerbread based baseband so a gingerbread nandroid flash will be successfull.
-get kernel built for custom rom /load up a crap ton of battery and system optimizer scripts in custom rom.
-either make new rom or port mine over to commando
Click to expand...

Sent you a PM with some ideas/answers

Pax
 
Really wanna get you guys up and running. Having a custom recovery that is useless is pretty um
Well boring? Is a good word to use i guess. Seeing my fiance frustrated on er commando is makin me get an itch to help out.

My main idea is build a custom rom for each operating system
Froyo and gingerbread
Just incase we cant get people on the same track.
 
Just had an Idea.
Could somebody on 2.2.1 make a complete (every single partition, not just /boot and /system) nandroid?
(I noticed in the GNM thread, people were told to only backup /boot & /system to have a nandroid)

I have a theory I wanna test...
(If it works, i'll explain my theory)

Pax
 
promise not to read my texts? haha i've got a copule right now for you

edit: i could always flash to a previous for you then delete texts and contacts and make a new one if that would be better for you. and is your theory that the baseband files are in a different part of the nandroid
 
paxchristos said:
Currently, there is no way to restore to a factory firmware setting (i.e. have everything setup like the day you got it outta the box)

There are a couple of nandroid backups floating around (GNM Recovery thread) but I don't think any of them are completely stock.

The one issue we're running into right now is the baseband/how the baseband is interacted with has changed, and we don't have a good radio.img to flash.

That and the bootloader is a pain in the butt to get to a state where you can flash images...

If you can share any pointers on developing custom roms, right now i'm working on a custom kernel (check my github, username paxchristos) for this phone, but I bricked my test device, and i'm waiting for a new one before I commence again (i need to check something...)

Pax
Click to expand...


I'm still at -

Android Version: 2.2.1
Basband version: 1
Kernel Version: 2.6 32.9-perf ncmc@ncmd #1
Build Number: M050
Hardware Version: 1.1

I am rooted, absolutely nothing stock removed - only frozen using Titanium Pro.
 
MikeDilligaf said:
I'm still at -

Android Version: 2.2.1
Basband version: 1
Kernel Version: 2.6 32.9-perf ncmc@ncmd #1
Build Number: M050
Hardware Version: 1.1

I am rooted, absolutely nothing stock removed - only frozen using Titanium Pro.
Click to expand...

Could you (or anybody else on 2.2) run the following code in either adb or terminal editor abd post the results
Code:
# cat /proc/mtd

(if I put a # in front of code, it means run it as root, not typing in "#")
 
Yupp, the file you sent me was missing one thing:

if you (or anybody on 2.2) could do the following
Code: 
# cat /dev/mtd/mtd5 > /sdcard/persist.img

and send me persist.img that'd be awesome!
(as soon as I get my commando up, the testing begins)
 
I'm getting the error "/scarf/is not a directory" if there us something wrong with this code let me know, if my phone us being dumb you'll have to wait till tomorrow when I'm at a computer with adb
 
Spike G said:
I'm getting the error "/scarf/is not a directory" if there us something wrong with this code let me know, if my phone us being dumb you'll have to wait till tomorrow when I'm at a computer with adb
Click to expand...

Instead of /sdcard, try /mnt/sdcard/persist.img
 
You must log in or register to reply here.
Back
Top Bottom