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

Root Recovery for commando

If you get into that situation, post here, and someone will walk you through it.

Pax, did you figure out what that file was?
 
What are the steps to getting back to the screen where I can do the backup? I did it once but now cannot repeat.

Nevermind. Need to type adb reboot recovery
 
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

So if the phone is in a bootloop, how does one boot recovery? I noticed that you have to have USB debugging enabled in order to do it through ADB. Can't rely on doing it from the phone if the screen is locked in a bootloop.

As far as my comment on USB debugging, should a person always leave that turned on just in case? Again, if you can't get to the menu on the phone to turn it on, then what is the point?

I apoligize for all the questions, but I am trying to understand this.
 
I apoligize for all the questions, but I am trying to understand this.

basically this is just a terrible phone to try and monkey with. As far as I understand it, if you are stuck in a bootloop, and can't get to recovery via ADB, you are basically hosed. Casio in their infinite wisdom decided to not have any kind of physical button-press combo to go to recovery. This phone is a definite "play at your own risk" situation. And I wouldn't be nearly so cavalier as Jova33 regarding warning messages about potential bootloops unless I was 100% confident in my ability to get to recovery using ADB under pretty much ANY circumstance. Whatever you decide, good luck!
 
basically this is just a terrible phone to try and monkey with. As far as I understand it, if you are stuck in a bootloop, and can't get to recovery via ADB, you are basically hosed. Casio in their infinite wisdom decided to not have any kind of physical button-press combo to go to recovery. This phone is a definite "play at your own risk" situation. And I wouldn't be nearly so cavalier as Jova33 regarding warning messages about potential bootloops unless I was 100% confident in my ability to get to recovery using ADB under pretty much ANY circumstance. Whatever you decide, good luck!

That is what I figured. I don't plan on doing too much more messing around. I am rooted (M80) and debloated and happy. I just like the ability to be able to backup and restore but I thought that was what titanium backup could be used for as well. I seriously doubt anyone will come up with any cool roms to flash, but I wanted to be ready. I also hope my questions and answers from others will fill in some of the gaps for others who may read this.
 
Hi All! I have a trouble with Casio gzOne (C771). After successfully rootint this device and mods rom I was mistake: under root I change permissions on /system/lib from 755 to 644... Now phone start booting, then it show now loading and that all :( ADB entering me, but su, sudo and other not working... (segmentation fault, permissions denied). Rooting exploits not working too. any ideas ? I trying to copy lib-folder on other dir and use LD_PRELOAD, change var of path, but I can't change permissions to correct. I'm not a cool hacker :)
 
Adb wait-for-device reboot recovery

Does that work?

no. device just rebooting. as I know this device not have boot-rom, such as ssamsung or htc... such as personal computer... if i can't tell boot-loader to boot recovery image i can't boot. :( maybe using adb shell editing config boot-loader ? but I don't have enough permissions. I appreciate any ideas. thanks.
 
no. device just rebooting. as I know this device not have boot-rom, such as ssamsung or htc... such as personal computer... if i can't tell boot-loader to boot recovery image i can't boot. :( maybe using adb shell editing config boot-loader ? but I don't have enough permissions. I appreciate any ideas. thanks.

Sorry buddy, your phone is now an expensive paperweight (as of right now there is no way to recover a bootlooped phone)
 
I don't understand what exactly he did to his commando. I'd like to know just so I don't do it. Do you understand pax?
 
I don't understand what exactly he did to his commando. I'd like to know just so I don't do it. Do you understand pax?

He changed the /system/lib permissions from read, write, execute to read, write. what he did is pretty much equivalent to deleting the drivers on a windows computer with no (accessible) backup, no CDROM drive and no USB Ports. Unless somebody can figure out the testpoints on the phone (kinda like adam outwiler (sp) does on xdaTV) there's nothing he can do to fix his device. (due to how the (second stage?) Bootloader is setup.)

Sent from my phone, please excuse any Swypos.
 
paxchristos: thanks for decrypting my message :) possibly, write rom direct into flash-chip ? :) I was unpleasantly surprised: I see in a first time phone without combo-buttons, fastboot (or odin, etc)... casio is forgotten brand for me :(
 
paxchristos: thanks for decrypting my message :) possibly, write rom direct into flash-chip ? :) I was unpleasantly surprised: I see in a first time phone without combo-buttons, fastboot (or odin, etc)... casio is forgotten brand for me :(

To do that, you (or a good friend) will need to have an intermediate to advanced understanding of electronics & cellphones. If you hop on YouTube & check out the "unboxing" videos done by on xdaTV by Adam Outlier (sp), what he does is take apart a device as far as he can, and in some cases get hook up the testpoints to his computer, so he can literally hack the system.

To my knowledge, Verizon doors not have software to flash the chip (if you read about the "security" NEC-Casio put into the device, that might help illustrate, as well as with the original update received, & replacing rather than reflashing)

On top of that, while we do have (complete) nandroids, we do not have a way to apply an update from the source (innopath.) They encrypt the updates, and can only be unlocked by the "apply_patch" binary found in /system/bin (they also use a very funny hash check that has a built in date-time check, as well as being non-standard (i.e. Not md5/sha sums))

I completely agree, fastboot is disabled unless you (on purposely) soft brick your device (if you erase the /boot partition, you gain access to fastboot)

Heimdall/sbf/SEUS/HTC's bootloader are all examples of companies (Samsung/Motorola/Sony (Ericsson)) that already give people the option to try to fix their device.

My own personal opinion on the matter would be to go with either an OMAP based Samsung, or a Sony Mobile device. I haven't looked into Samsung too much (haven't had a phone by them or Motorola, I just know Motorola is very... non-Dev friendly) but if you look at developer.Sonymobile.com, it's probably the greatest resource I've seen development wise. Then again, I might be biased towards My phone, cause I'm running my own build of CM9 on it :p

Pax
 
<------------start cut------------->
I completely agree, fastboot is disabled unless you (on purposely) soft brick your device (if you erase the /boot partition, you gain access to fastboot)
<------------stop cut------------->
as I understanding, if I erase or corrupt /boot, I will get to fastboot phone ? :))) original way.
I read about security commando... Depressing... update only from air. nice. how repair device on factory or service ? I thing they can unlock fastboot. angry - this word describes my state. my experience tell me motorola more better then casio... :(
thank You for help and participating. :)
 
as I understanding, if I erase or corrupt /boot, I will get to fastboot phone ? :))) original way.
I read about security commando... Depressing... update only from air. nice. how repair device on factory or service ? I thing they can unlock fastboot. angry - this word describes my state. my experience tell me motorola more better then casio... :(
thank You for help and participating. :)

Needs to be erased, because if there's any trace left of the second stage bootloader they use, you will not be able to use fastboot. (we're talking about using fastboot from terminal, because there is a fastboot driver out there for windows, I just don't remember how I got it (it's separate from normal driver hosted here))

My guess is with the right testpoints, you can force the device to recognize USB input/fastboot (outside of my realm, I'm just guessing because with my phone, I used a testpoint unlock to access fastboot) (Sony Mobile does secure the bootloader for Verizon Xperia Plays (my guess is on big reds request))
 
Back
Top Bottom