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

Root [Resolved] Need help from those who have stock C811

i assumed flashify just handled the adb commands for me. i know what the script does, copys parts of the ram to a file for him, i dont understand how it ****** me so hard, unless flashify pulled some junk.
 
yeah it looks like everything frozen stayed frozen, but titanium back up only brought up my backups from my old droid X... wtf... ugh
 
No s$%T! I bricked my phone running this. It's stuck in a boot loop. Oh well, I guess will get a chance to use my insurance now. LOL!
 
trx125 said:
No s$%T! I bricked my phone running this. It's stuck in a boot loop. Oh well, I guess will get a chance to use my insurance now. LOL!
Click to expand...

I've tested in in CWM.
Here is the video of me running this script via CWM on my device.
Proof that it's working via CWM


EDIT:
Now I know what was the problem. I contacted the flashify developer and asked if it mounts sdcard automatically like recoveries do.
Unfortunately falshify didn't mount /sdcard and my script had written the files to mountpoint instead of writing it to mounted storage.
I thought that flashify creates the same environment as a recovery, but it doesn't. That's a lesson: when making update-scripts always mount everything just in case.
I've updated the script and added mount command so now it should work.

For those that got problems try this approach
This script unmounts sdcard and clears the directory that was messed in case that my theory that flashify didn't automatically mount your /sdcard/ is correct.

https://drive.google.com/file/d/0Bw4z78Q7Eys6clN2RWo2a0ZuSGM/edit?usp=sharing
Rename it to "update.zip" and put in root of external storage, boot into your recovery and choose "apply update" from external storage.

Please run this and tell me if it fixed. I really need to know what caused the brick.
 
rjglenn said:
Oh My... Welcome to my world. Do not flash the 410 initialization tool, that Korean shit will cause you to loose LTE. Doctoror is in the Ukraine and probably won't see this until later.
Click to expand...

I sent through a PM an image from my baseband to doctoror. Maybe he could make a flashable baseband/rom out of it containing VZN baseband M8960A-1.5.38_C811M020. This is verizon's baseband for 4.0.4.
 
motumbo said:
I sent through a PM an image from my baseband to doctoror. Maybe he could make a flashable baseband/rom out of it containing VZN baseband M8960A-1.5.38_C811M020. This is verizon's baseband for 4.0.4.
Click to expand...

Yeap, going to make that in 1.5 - 2.5 hours. I am more interested if my fix helps currently.
 
Doctoror, send it to me. I already have a replacement on its way and I have a spare if we completely kill this one.
 
call me crazy, but im gonna hold off on trying more stuff for a few days.. wait for a safer way to help out...
 
I don't know anything about this "rooting" and "booting" stuff here :dontknow:(ONE step at a time) BUT loading that driver set got my Commando and computer to recognise each other and start "talking" :shakehands:. Now I can do some shuffling of my music files I've downloaded and reload them into my phone for playing, the radio in my truck :driver:has a USB port and THAT is one of the reasons I finally upgraded my phone (Merry Christmas to me :santaclaus:)
 
Doctoror said:
Those who modified their recoveries and images can't update and need your ROM.
To create a ROM I'you need to be rooted and execute these commands (I think you need busybox...)
Click to expand...

I can do this.

Is it still needed?

I'm just cringing at the thought of resetting my phone.

What are the specs for the zip format for update.zip?

Can anyone explain the button combination to get into recovery? I still don't get it.
 
GzOneDude said:
Is it still needed?
Click to expand...

I already got one but not tested. Would be nice of I'll have another one.

GzOneDude said:
I'm just cringing at the thought of resetting my phone.
Click to expand...

You can reset it the user data will not be stored in imgs anyway.

GzOneDude said:
What are the specs for the zip format for update.zip?
Click to expand...

What do you mean about specs of the update.zip?

GzOneDude said:
Can anyone explain the button combination to get into recovery? I still don't get it.
Click to expand...

The button combo seems to not work.
You can get there via
Code: 
su
reboot recovery
In terminal or adb shell.
 
Doctoror said:
Those who modified their recoveries and images can't update and need your ROM.
To create a ROM I'you need to be rooted and execute these commands (I think you need busybox...)

Code: 
su
dd if=/dev/block/mmcblk0p19 of=/mnt/sdcard/recovery.img
dd if=/dev/block/mmcblk0p1 of=/mnt/sdcard/modem.img
dd if=/dev/block/mmcblk0p5 of=/mnt/sdcard/aboot.img
dd if=/dev/block/mmcblk0p8 of=/mnt/sdcard/tz.img
dd if=/dev/block/mmcblk0p7 of=/mnt/sdcard/boot.img
dd if=/dev/block/mmcblk0p6 of=/mnt/sdcard/rpm.img
dd if=/dev/block/mmcblk0p2 of=/mnt/sdcard/sbl1.img
dd if=/dev/block/mmcblk0p3 of=/mnt/sdcard/sbl2.img
dd if=/dev/block/mmcblk0p4 of=/mnt/sdcard/sbl3.img
dd if=/dev/block/mmcblk0p13 of=/mnt/sdcard/system.img

dd if=/dev/block/mmcblk0p22 of=/mnt/sdcard/fota.img
dd if=/dev/block/mmcblk0p10 of=/mnt/sdcard/modemst1.img
dd if=/dev/block/mmcblk0p11 of=/mnt/sdcard/modemst2.img
dd if=/dev/block/mmcblk0p12 of=/mnt/sdcard/nvbackup.img
dd if=/dev/block/mmcblk0p15 of=/mnt/sdcard/persist.img
dd if=/dev/block/mmcblk0p17 of=/mnt/sdcard/tombstones.img
dd if=/dev/block/mmcblk0p18 of=/mnt/sdcard/misc.img
dd if=/dev/block/mmcblk0p20 of=/mnt/sdcard/fsq.img
dd if=/dev/block/mmcblk0p23 of=/mnt/sdcard/ftm.img
dd if=/dev/block/mmcblk0p27 of=/mnt/sdcard/extres.img
Click to expand...

i rooted my phone using the unlockroot method described elsewhere on this forum a while back. installed super su and android root apps. also titanium backup and rootappdelete, which i used to uninstall bloatware that was classified as system apps. as far as rooting and ROM and all that stuff that is all i have changed.

that being said... do you still need the above information? it seems as if you guys may have gotten the files you need. i might as well be reading russian when it comes to all the references to ADB, CWM, ROM and flashify, etc. so i'm not really sure of what to do but am willing to give it a shot to help out.

i have not done the OTA update yet as i was really unsure about what will happen since my phone is rooted. i made a backup with titanium backup and i've gotten the android SDK manager downloaded so that i can fumble through this adb stuff.

before i venture out on a limb and try the jelly bean update i can try to provide the files needed if necessary.

from what i've read in the OTA update thread, it looks like i should be able to do the update and not get a brick since i haven't modified anything.
 
pitapoket said:
i rooted my phone using the unlockroot method described elsewhere on this forum a while back. installed super su and android root apps. also titanium backup and rootappdelete, which i used to uninstall bloatware that was classified as system apps. as far as rooting and ROM and all that stuff that is all i have changed.

that being said... do you still need the above information? it seems as if you guys may have gotten the files you need. i might as well be reading russian when it comes to all the references to ADB, CWM, ROM and flashify, etc. so i'm not really sure of what to do but am willing to give it a shot to help out.

i have not done the OTA update yet as i was really unsure about what will happen since my phone is rooted. i made a backup with titanium backup and i've gotten the android SDK manager downloaded so that i can fumble through this adb stuff.

before i venture out on a limb and try the jelly bean update i can try to provide the files needed if necessary.

from what i've read in the OTA update thread, it looks like i should be able to do the update and not get a brick since i haven't modified anything.
Click to expand...

Thanks. I have gotten all the files I need and zipped the ROM. This is no longer needed. I forgot to notify here, gonna edit the post now.
 
I don't imagine anyone has a copy of the Windows 7x64 drivers for this thing, do they? It's not picking it up automagically and I'm trying to get Win7 to recognize it for the tl-bootstrap program
 
Doctoror said:
The C811 drivers: link.
Click to expand...
Nice. Windows now recognizes my bricks. Adb still can't see it, though. And I can't seem to do a factory reset on either of them. It's there any known way to push the aboot, boot.img, and a recovery to a C811 that doesn't boot far enough to use adb?
 
Ok, one of the two is working with the Windows software upgrade application and is downloading what I presume to be M050. I hope that whoever had the phone prior to me didn't do anything that would prevent the device from being able to be repaired/upgraded
 
And I ran into the same issue I've seen others have. It says my battery is lower than 25%, even though it's fully charged. It's there a way to take the mbn file and drop it in the SD card so that the phone will flash it without help from the computer?
 
First of all hello to everyone ... i think that i have the same problem of unitypunk.I screwed with my super G'zOne Commando. I live in Italy, and I have to say that the G'zOne is not well adapted to our network, type text messages do not work, at every reboot I have to reset the time ... small problems, but nothing serious ... but I wanted to that my phone worked perfectly. The other day I decided to make the move to C811. But instead of improving the phone, I totally ruined: not working camera, wi-fi, the hot-spot ... then I tried to install another baseband as he put a forum to solve problems, and now the phone will not turn on anymore ... it freezes on the verizon screen and does not go forward, but the worst thing is that I can not get into recovery ... I urgently need your help to know what should I do to solve the problema.io I would like to put the phone in the original version ... but how can I do if I no longer get into recovery? help me please
 
I'm slowly working on trying to put together a bootable SD card image. I don't know for sure if this hardware supports booting from SD or not, but that is how you root and install a bootloader on a soft bricked Nook Color or Nook HD. it's a long shot, but I'm hoping to get a way to boot the C811 to a point where we can use adb to push the image files from the update manually from a command line adb shell.
 
You must log in or register to reply here.
Back
Top Bottom