Database Info

CognitionV2.2Beta6 (noob guide)

**Please note that following these steps will completely erase your phone**
**Back up any important information before starting(contacts, photos, etc)**
**This guide is for Windows users**
Flashing Cog 2.2 Beta6 (From 2.1 Eclair or 2.2 Frozen Yogurt)
Things to download before you start:
Odin 1 click stock - http://www.thevod.org/misc/captivate/I897UCJF6-final-OCD-REV0.rar
one click root - http://forum.xda-developers.com/showthread.php?t=739304
cognition beta 6 - http://www.ponack.net/designgears/index.html
On your phone - go to Settings, Security, restore factory data.
Reboot your phone.
Enable USB debugging.
Start Odin (you downloaded earlier).
Plug your phone into your computer via USB.
Odin should recognize your phone at this point.
Click "Master Clear".
Once finished, close Odin. Your phone should be rebooting.
Once phone has rebooted, make sure usb debugging is still enabled.
Remove usb plug from phone and then power down the phone.
Remove battery, remove sim, (remove external SDCard).
Insert battery.
Open Odin.
Hold vol up and vol down.
While holding vol buttons, insert USB.
The phone should show a triangle with android digging (or sweeping?)
odin should recognize the phone at this point
Click "Start".
You should see a progress bar on your device display, and within Odin.
The phone will reboot when finished.
Close Odin.
Go back to your phone an re-enable usb debugging.
Run "One-Click Root"
Click "one click root"
Your phone will boot into recovery mode.
Use the volume buttons to highlight "reinstall packages".
Hit the power button to select.
Your phone will apply the update then reboot itself.
Go into app drawer and verify that "superuser permission" icon is visible.
Close one click root.
Power off your phone.
Re-insert your sim card.
Power phone on.
Allow your phone time to read the internal SD card.
Connect your phone to your computer via USB.
From your phone - select mount usb.
using windows, copy Cognitionv2.2beta6.zip onto your SD card.
Sign into Market.
Find ROM Manager, download, and install it.
On your phone, open ROM Manager.
Click "Flash clockwork mod recovery"
Select "Galaxy S Captivate".
Observe the green progress bar at the top of your phone's display.
When complete, clockwork will ask for superuser permissions - allow it.
Choose install rom from SD Card.
Navigate to your SD card and select the cognition zip.
Click OK.
Click OK.
Your phone will either install and reboot automatically, or it may hang at the recovery screen waiting for your input. If this happens, select reinstall packages.
From within this menu select install rom from .zip.
Navigate to the cognition rom and select it.
Confirm that you actually want to do this.
Your phone will reboot to menu again.
Select "reboot system" and sit back.
Your phone should boot into the Android OS.
Almost done...
Go here, https://www.paypal.com/cgi-bin/webs...bn=PP-DonationsBF:btn_donate_LG.gif:NonHosted and buy DesignGears some beverages

It seems that this is already well documented in the Cognition wiki, no?
http://cognition.theidiotshideout.net/mw/index.php?title=Main_Page
You may also catch some flack as this has nothing to do with actual android development.

Cog 2.2 Beta 6 should be rooted already when you flash it, unless something changed. I dont see the need to use one click root.

z28james said:
It seems that this is already well documented in the Cognition wiki, no?
http://cognition.theidiotshideout.net/mw/index.php?title=Main_Page
You may also catch some flack as this has nothing to do with actual android development.
Click to expand...
Click to collapse
+1
Plus this list may be a bit confusing to a real noob.

Jimmy thanks for this, simple but very precise. The wiki seems to be written for somebody that already knows all the details. It's also not very clear as to whether or not you can go straight from eclair to cog2.2, you cleared it up for me so now I don't have to start a "sorry about the noobness" thread/post. I'm running cog 2.1.5 so I have done it before, even used odin once. Thanks again

Or you could just use his pre-made Odin flash and skip all of those steps.
Delete.

kakwvu said:
Or you could just use his pre-made Odin flash and skip all of those steps.
Delete.
Click to expand...
Click to collapse
+1
Sent from my SAMSUNG-SGH-I897 using XDA App

kakwvu said:
Or you could just use his pre-made Odin flash and skip all of those steps.
Delete.
Click to expand...
Click to collapse
That's an answer that belongs in some sort of guide for noobs haha

I appreciate the detailed instructions. A few details to be added. Odin is Windows only, and one click root does not copy the zip file successfully for me (on a Mac). I had to view the package contents of the program and drag the file over and rename it myself, then used the program to reboot into recovery (3 button didn't work for me either).

kakwvu said:
Or you could just use his pre-made Odin flash and skip all of those steps.
Delete.
Click to expand...
Click to collapse
And this is +3.
Sent from my SAMSUNG-SGH-I897 using XDA App

For everyone that gripes about battery life after a flash, try this first after every new ROM:
http://forum.xda-developers.com/showthread.php?t=765656

joeybear23 said:
For everyone that gripes about battery life after a flash, try this first after every new ROM:
http://forum.xda-developers.com/showthread.php?t=765656
Click to expand...
Click to collapse
If you gonna take this there, I'd suggest this one instead.
http://forum.xda-developers.com/showthread.php?t=806211

So does this mean I cant go from stock eclair to froyo with only Rom Manager and no use of ODIN (my phone never recognizes ODIN )

Actually, I think this is a good idea, might keep some of the junk out of the regular Cog thread, that thing is Frickin HUGE...

ozy944 said:
So does this mean I cant go from stock eclair to froyo with only Rom Manager and no use of ODIN (my phone never recognizes ODIN )
Click to expand...
Click to collapse
yes you go from stock eclair to froyo with only Rom Manage...
i did it on sunday night and today i see new cog 6 beta released!!!!
copy cog file to your sd card; install rom manager and continue from there, it will fail the first time (mostly) start phone again and reinstall package..done.

There's also one more thing the op didn't mention. If this is targeted at noobs, it really should be mentioned that if you follow these instructions, you are essentially wiping your entire phone clean (by the odin one click stock). If your that paranoid, go for it.
To me though, I just use titanium backup first, and back everything up. Then after upgrading to cog from eclair (directly without reverting to stock) you can restore your THIRD PARTY apps plus their data. (avoid restoring core apps as thats a bad idea) Not to mention no need to back up and restore any of the media you might have on the internal sd card. (not sure if odin one click stock touches that stuff or not)
I've had no problems in any of my ROM upgrades, and I've moved from 2.1 to cog 2.2 beta 2, then again today to cog 2.2 beta 6. All of that without a restore to stock. You really should only restore to stock if you are having problems AFTER upgrading. Why do extra work and wipe the whole thing clean if it's not necessary? Just adds steps, and possible frustration from people not expecting a wiped phone.

thank u man! rly!

Please verify that you are able to get into download mode using only button combinations before you start any flashing process.
Sent from my SAMSUNG-SGH-I897 using XDA App

orlandoxpolice said:
Cog 2.2 Beta 6 should be rooted already when you flash it, unless something changed. I dont see the need to use one click root.
Click to expand...
Click to collapse
You have to root to be able to flash it in the first place.

Do you mean that Odin won't recognize your phone? WHat happens when you try?

Stuck in Bootloop

Hey guys,
i don't realy know why, but by phone crashed yesterday, and since then i'm stuck in bootloop. I can't even enter the RecoveryMode, i always get an Symbol with a phone and a 'TrafficSign'(Don't know the name of this).
The only thing i can do is enter the fastboot bootloader... i can't even charge the phone anymore...
H E L P!!!!!!!

opiswahn said:
Hey guys,
i don't realy know why, but by phone crashed yesterday, and since then i'm stuck in bootloop. I can't even enter the RecoveryMode, i always get an Symbol with a phone and a 'TrafficSign'(Don't know the name of this).
The only thing i can do is enter the fastboot bootloader... i can't even charge the phone anymore...
H E L P!!!!!!!
Click to expand...
Click to collapse
Hi opiswahn, you can try to flash rsd lite to reformat your back to stock. First download rsd lite and sbf files of your preference (I am using singapore sbf). Then open your phone while holding power button, sound up, media together. You will go into bootloader mode (black screen). Now flash rsd lite from your cpu and your phone should be alright. Hope it helps you.

thx for the reply, but RSDFlash won't let me flash... see picture

Maybe another version of RSD lite and/or try to run it in XP compatibilty mode.
I had the same situation like you in the screenshot when I installed an sbf using Windows 7 on the neighbour's PC.
But I can't remember clearly what was the key to get it working as it was in february.
Since then no more sbf ...
Milestone XT720 - CM6.3.0 RC3

WinXP did the trick, tried before running as admin or in compatiblity-mode, but nothing worked, so i tried a WinXP VMWare, and boom, it works!
*Edit*
Aw, damnit, every time rsd tries to write to the phone the VM crashes...

opiswahn said:
WinXP did the trick, tried before running as admin or in compatiblity-mode, but nothing worked, so i tried a WinXP VMWare, and boom, it works!
*Edit*
Aw, damnit, every time rsd tries to write to the phone the VM crashes...
Click to expand...
Click to collapse
Try this
Go on control panel , click on system , click on andvanced system settings then on advanced tab click settings under performance then the advanced tab and click change under virtual memory, then custom size and choose it the size u want it to be ,but bare in mind not to low and not to high , keep it under 3000MB
Also I found that OR sometimes gets corrupt. Most of the time if you just re-unzip the recovery and replace all the items in the Openrecovery folder (except the Updates b/c you'll lose whatever is in there when you overwrite it) on your PC and then xfr over to SD cardyou then you can enter recovery like normal. That usually does the trick. In fact that happened to my wife's phone last night and I fixed it up just like that.
I always hate flashing sbf when I can just restore a nandroid. Not sure if it will work since you started the sbf already.

I had the same issue with RSD Lite 4.6. I found a 5.0 with no problem. But now I saw yours! How ironic.

enter moto's recovery, do "factory reset"

You need to enter bootloader mode, not the fastboot bootloader.
Sent from my MilestoneXT720 using XDA App

Stuck in boot loop after upgrading to Bravo 2.2 v1.6 by brianlee+updates0926_bravo1.6
Help! My phone is experiencing the same thing... stuck in boot loop. The operator's logo (Singapore Starhub) keep appearing again... again... and again.
I upgraded it the from dexter's rom to Bravo 2.2 v1.6 by brianlee. I've followed all instructions below but after I install the update, my phone stuck in boot loop.
Instructions
Download 1.6 from one of the links above.
Download the Update from above.
Extract the contents of the 1.6 download.
Copy the contents of the sdcard folder to the root of your sd card. (You can skip the OpenRecovery files and just copy the nandroid folder if you already have OR).
Copy the update ZIP file into /sdcard/OpenRecovery/updates
Reboot into OpenRecovery
Nandroid > Restore > bravo2.2-brian
Apply Update > update-bravo1.6Mz-20110926-1328.zip
Wipe Cache, Wipe Dalvik, Factory Reset
My phone run perfectly well and after I apply this update (updates0926_bravo1.6.zip), I'm stuck in boot loop.
I've tried many ways to recover my phone, but none is successfull, including this thread. I've tried the camera button+power button and then volume up button. And this message appears on the screen: "E:Can't open /cache/recovery/command" with phone picture and exclamation mark on the background.
RSDlite 4.9 + sbf file can't detect my phone.
Can someone help me? Can I restore my phone?
---------- Post added at 02:36 PM ---------- Previous post was at 02:00 PM ----------
Sorry, I can recover my phone. I tried to press power button+volume up button+media button all at once and the recovery mode appeared. I applied the proper update and voila... My phone is working again.

[SCRIPT] Safe Bionic Path Saver + .901 + Liberty3 2.0 - VERSION 2

Yesterday afternoon I attempted the Bionic Path Saver update with 901 and Liberty 2.0. Due to issues with flashing the Webtop image and some flaws in the script I wound up with a dead phone. After hacking up a charger and over 12 hours of experimentation I was able to get the phone and and was able to update it. I do not want anyone to have to go through what I went through so I am posting this. I do not take credit for the files, I only came up with the combination. All download links lead to the creators. Let me know how this works out and of course always create backups before performing this.
**Things you will need**
A FULLY charged battery
My SafeBionicPathSaver_v2.rar - http://www.filesharesite.com/files/201201/1327968223SafeBionicPathSaver_v2.rar.html
RSDLite 5.5 - In this package
Motorola Drivers - In this package
flashme.zip - In this package
Liberty 2.0 (.901 OTA Compatible) - http://rootzwiki.com/topic/13096-901-radio-working-with-custom-rom/
bionicbootstrap.apk - http://droidmodderx.com/bionic/bootstrap-recovery-for-the-bionic/
**Instructions**
1.) Install RSDLite 5.5 and Motorola Drivers (32-bit or 64-bit accordingly).
2.) Extract flashme.zip to any location on your computer.
3.) Extract SafeBionicPathSaver_v2.rar (ME) files to any location on your computer.
4.) Copy bionicbootstrap.apk and copy the Liberty 2.0 (.901 OTA Compatible) ZIP to the root directory of your SD card.
5.) Connect phone to computer, set phone to USB Debugging Mode, and set it to Charge Only. You will also need to allow "Unknown sources" in your application settings.
6.) Go to the directory from Step 3 and run SBPSscript.bat. Let it run and wait for Phase 1 to complete.
7.) Phone should now be at the bootloader. Open up RSDLite and browse to the XML in the directory from Step 2. Flash this and the phone should reboot, it will take a while.
8.) The phone should now be at the Android setup screen. *The phone has been reflashed and reset, you now need to follow STEP 5 again to continue*. You may now contune following the prompts in the SBPSscript.bat script. Watch for any errors as directed. The phone should end up booted into stock recovery.
9.) At the recovery menu you are going to install updates manually. First do update893.zip, then do update901.zip. Make sure there were no errors then reboot the phone.
10.) You are now at version .901 and should still be rooted. To test root you can try and update Superuser by going to Superuser's menu and updating the binary. If it fails with a permission issue, you do not have root and have to start over.
***IF YOU WOULD LIKE TO REMAIN ON THE STOCK ROOTED .901 ROM YOU CAN STOP HERE. THE REST OF THE STEPS ARE FOR GETTING LIBERTY3 2.0 INSTALLED.***
11.) Now install bionicbootstrap.apk, open the application, and press the "Bootstrap Recovery" button (grant any SU access). This will install the Clockwork Recovery ROM and would fail if you were not still rooted.
12.) Now click the "Reboot Recovery" button. You will now be in the Clockwork Recovery Mod.
13.) At this menu you will need to wipe data, cache, dalvik cache, and format /system.
14.) Now you will select "install zip from sdcard" using the volume and power buttons and choose the Liberty ZIP you uploaded in Step 6.
15.) After this is done you can reboot the phone and you will have a Liberty3 2.0 / .901 Radio Bionic!
-Mark DePalma | MNetwork

I will be trying this later tonight. I'm hoping it goes well and I'll be sure to let you know. Thanks for taking the time to make the write-up. If it works properly, it's exactly what I've been looking for.

utcu said:
I will be trying this later tonight. I'm hoping it goes well and I'll be sure to let you know. Thanks for taking the time to make the write-up. If it works properly, it's exactly what I've been looking for.
Click to expand...
Click to collapse
You're welcome, a user just notified me of a typo "fixme = flashme" and I have updated that in my ZIP and in the post. The same user also told me that the flashme.zip file isn't available for download at the moment. I would host it myself, but I know that within 30 minutes my pipe would be saturated. Hopefully this link comes back up soon, if not I will find a way to host it somewhere.

utcu said:
I will be trying this later tonight. I'm hoping it goes well and I'll be sure to let you know. Thanks for taking the time to make the write-up. If it works properly, it's exactly what I've been looking for.
Click to expand...
Click to collapse
Worked like a charm. Greatly appreciated. Nothing like being on Liberty with 901.

utcu said:
Worked like a charm. Greatly appreciated. Nothing like being on Liberty with 901.
Click to expand...
Click to collapse
Great! Good to hear. I have updated the post with a 2nd link to download the flashme.zip file since that went down last night. Very happy XDA is finally back online.

can this be used to go back to 5.5.839 from .901?

waffleb051 said:
can this be used to go back to 5.5.839 from .901?
Click to expand...
Click to collapse
I believe you can, but you MAY have to flash a .901 CDT image after you flash back to .839. I came back from a failed root attempt on .901, but I was also playing with different CDTs. If you try it out you can definately get it working, may or may not have to flash that .901 CDT.

I haven't able to have any success with this. I tried it twice but it keeps hanging on the Motorola screen. This is after I flash flashme (step 9) and when it goes to reboot. I've waited both time for 15-20 minutes but nothing. Is there something I'm missing? I have RSDLite 5.5 and Drivers 5.4

Stealth36 said:
I haven't able to have any success with this. I tried it twice but it keeps hanging on the Motorola screen. This is after I flash flashme (step 9) and when it goes to reboot. I've waited both time for 15-20 minutes but nothing. Is there something I'm missing? I have RSDLite 5.5 and Drivers 5.4
Click to expand...
Click to collapse
Well since you have rebooted you now have to manually get it into the fastboot mode. Turn the phone off, hold both volume buttons down, then hold the power button down for a second or two and the phone should enter fast loader mode. At this point you can connect it to the computer and RSDLite will see the phone and you can resume. Let me know if this works for you...

so I'm taking this doesn't work... files aren't even there
all i need is the last one... BPS_Safe_Scripts
plus there is a safe strap now... whats' going on.

Slie said:
all i need is the last one... BPS_Safe_Scripts
plus there is a safe strap now... whats' going on.
Click to expand...
Click to collapse
My web server runs on an old P2V'd box in my ESXi cluster and I've been meaning to port all my web sites over to a new web server VM, but haven't had the chance. I have to restart this VM every once in a while... I just rebooted it and the web site is back up. You can download this file now.

mnetwork said:
Well since you have rebooted you now have to manually get it into the fastboot mode. Turn the phone off, hold both volume buttons down, then hold the power button down for a second or two and the phone should enter fast loader mode. At this point you can connect it to the computer and RSDLite will see the phone and you can resume. Let me know if this works for you...
Click to expand...
Click to collapse
I went to try it again and it worked this time. It ended up on the Android welcome screen. Thanks for the script!

Stealth36 said:
I went to try it again and it worked this time. It ended up on the Android welcome screen. Thanks for the script!
Click to expand...
Click to collapse
Good to hear!

I have one more question. Right before I installed the Liberty(.901).zip my system version said 901 but after installing Liberty it now says 886. So is that telling the truth?

Stealth36 said:
I have one more question. Right before I installed the Liberty(.901).zip my system version said 901 but after installing Liberty it now says 886. So is that telling the truth?
Click to expand...
Click to collapse
I am in the same boat. I believe since the ROM is built on .886 that is what it is going to report. The radio, however, has already been updated and Liberty doesn't contain a radio and therefor would not roll it back. The version of Liberty used in here is only patched with libraries to handle the .901 radio. Since the upgrade I have not had the contant data drops and 3g/4g switching that I had before. The only time the data really drops now is when I'm going through a tunnel or something like that.

Unfortunately it seems that all of the servers for these files have been stopped or are now unavailable. Anyone got the files or a new location for the files? This situation has gotten out of control with the sites.

treefrog20012003 said:
Unfortunately it seems that all of the servers for these files have been stopped or are now unavailable. Anyone got the files or a new location for the files? This situation has gotten out of control with the sites.
Click to expand...
Click to collapse
The governement is getting out of control with the piracy protection... I can make one complete package that would be much smaller than all of them combined, but if I host it I know I will be out of bandwidth in 30 min (it would still be fairly large).

treefrog20012003 said:
Unfortunately it seems that all of the servers for these files have been stopped or are now unavailable. Anyone got the files or a new location for the files? This situation has gotten out of control with the sites.
Click to expand...
Click to collapse
Which files did you find were missing? I was able to download two of the larger ones with no problem.

The flash me zip was not available and one other file was blocked on two of the sites and on a third it called for four hours to download. I want to get off the 901 system and downgrade so I can run the ics ROM. I tried once and was bricked for 24 hours until I found the bin swap method to get back to 893 from the motorola files using rsdlite.
Sent from my DROID BIONIC using XDA App

Same Problem -- Need Help
mnetwork said:
Well since you have rebooted you now have to manually get it into the fastboot mode. Turn the phone off, hold both volume buttons down, then hold the power button down for a second or two and the phone should enter fast loader mode. At this point you can connect it to the computer and RSDLite will see the phone and you can resume. Let me know if this works for you...
Click to expand...
Click to collapse
I am running into the same problem. I have re-ran the RSDLite script, it finishes but the phone never goes to the Android Welcome Screen. It stays on the Motorola Dual Core start-up screen

[Q] Atrix 2 won't boot past "M" Motorola logo

Hey guys,
Forgive me for being frantic and (probably) not taking the steps needed to research this issue, or not taking the time to do so, but I'm sure you can all presumably imagine -if you've not been in this situation before- that it SUCKS not having a phone in this day in age...
My problem: Atrix 2 (Rooted + CWM Recovery) now won't boot passed the "M" Motorola logo upon start up. It won't even allow me to access the factory Android Recovery by holding down Volume Up, Volume Down, and Power. I think I inadvertently bricked the phone? (Hope not!)
Further, the "M" Motorola logo is skewed in appearance, like its not even loading correctly. I'm not sure what to do. This is my first time rooting and getting experienced with custom ROMS.
Anyone able to help this helpless sap?
Thanks is advance to your replies...

Step 1 is where you tell what you did to get into the state you are in. You wouldn't believe how far it goes toward fixing something if you know how it got broken.
Sent from my MB865 using XDA

If you have CWM recovery on boot can't you just do a battery pull? You do NOT want to let that thing bootloop forever until the battery dies.
The End.

KEB64 said:
If you have CWM recovery on boot can't you just do a battery pull? You do NOT want to let that thing bootloop forever until the battery dies.
The End.
Click to expand...
Click to collapse
Agreed pull the battery. If you run out of juice you'll be in some serious trouble.
Did you try to flash the fkz? Unless you have CWM on Boot it's the only way you can get your phone working.

Okay, sorry for not giving a full rundown on what stupidity on my part cause all of this. Let me start by saying that (sadly) I am a great big n00b when it comes to Linux, and I thought that despite my research online I would sort of explore the CWM Recovery 'Advanced' sections.
I downloaded ROM Toolbox from the Play Store, and installed a custom boot animation, and replaced -or thought I was- the startup "M" logo with something else. This is what concerned me: After re-booting, the "M" logo was all crazy looking, with a "stretched" "M" logo over the top of the "regular" logo.
So, I uninstalled the app, but the logo was still all messed up. So, I used Root Uninstaller to get rid of the ROM Toolbox files, still no resolve to the crazy boot logo.
So, I went into CWM Recovery Advanced, and wiped everything. The Dalvik, cache, System, Data, etc... didn't think that it would -what appears to have happened- wipe out the OS on the phone.
I tried pulling the battery, and re-booting, won't boot passed the skewed "M" logo still. Tried getting into Android Recovery, and it looks to go through the recovery goes through its thing, but never boots normally afterward.
Sorry for being such an idiot, I really shouldn't have messed with this while half asleep, and again I can't apologize enough for being such a stupid n00b.
I can attach an image of the boot logo if that helps, but I'm worried I am just S.O.L. at this point...
Also, not sure what an FKZ is. I tried to install a 2.3.6 apk file to my wife's SD card on her phone and booting from the file after putting the SD card into mine. Still nothing.

pull the battery, put it back in, and hold vol up and down while turning on. choose ap fastboot at the menu. go to the thread in my signature and under the mirrors there is also a download of the return to stock script. run it while in fastboot and plugged in with usb. DO NOT pull the chord until it is done. when it is you should be good.

Apex_Strider said:
Okay, sorry for not giving a full rundown on what stupidity on my part cause all of this. Let me start by saying that (sadly) I am a great big n00b when it comes to Linux, and I thought that despite my research online I would sort of explore the CWM Recovery 'Advanced' sections.
I downloaded ROM Toolbox from the Play Store, and installed a custom boot animation, and replaced -or thought I was- the startup "M" logo with something else. This is what concerned me: After re-booting, the "M" logo was all crazy looking, with a "stretched" "M" logo over the top of the "regular" logo.
So, I uninstalled the app, but the logo was still all messed up. So, I used Root Uninstaller to get rid of the ROM Toolbox files, still no resolve to the crazy boot logo.
So, I went into CWM Recovery Advanced, and wiped everything. The Dalvik, cache, System, Data, etc... didn't think that it would -what appears to have happened- wipe out the OS on the phone.
I tried pulling the battery, and re-booting, won't boot passed the skewed "M" logo still. Tried getting into Android Recovery, and it looks to go through the recovery goes through its thing, but never boots normally afterward.
Sorry for being such an idiot, I really shouldn't have messed with this while half asleep, and again I can't apologize enough for being such a stupid n00b.
I can attach an image of the boot logo if that helps, but I'm worried I am just S.O.L. at this point...
Also, not sure what an FKZ is. I tried to install a 2.3.6 apk file to my wife's SD card on her phone and booting from the file after putting the SD card into mine. Still nothing.
Click to expand...
Click to collapse
Yeah wiping the system partition is a no no unless you flash another rom afterwards. Do like ikrasner says and you should be back to normal.
Sent from my MB865 using XDA

Thanks for all the help guys, I really hope that something positive comes about this... though, to go without mention, I certainly need more knowledge on WTH I am doing to my phone: understanding flashing ROMS, what dangers come with rooting, and a vast array of other "all things root" that I need to learn up on.
I will try to install from SD card the 2.3.5 zip tonight, but will it (the phone) look for the newest 2.3.6 OTA update and try to ask me to install? How does that work after rooting, will I re-brick my clearly bricked phone all over again?
As always, thanks for all your replies in advance -you guys really know what's going on here!

can you read chinese?
Maybe I can solve your question,but poor of my english.
and what is your phone type?
at&t hktw or china ?
Sent from my ME865 using xda premium

Apex_Strider said:
Thanks for all the help guys, I really hope that something positive comes about this... though, to go without mention, I certainly need more knowledge on WTH I am doing to my phone: understanding flashing ROMS, what dangers come with rooting, and a vast array of other "all things root" that I need to learn up on.
I will try to install from SD card the 2.3.5 zip tonight, but will it (the phone) look for the newest 2.3.6 OTA update and try to ask me to install? How does that work after rooting, will I re-brick my clearly bricked phone all over again?
As always, thanks for all your replies in advance -you guys really know what's going on here!
Click to expand...
Click to collapse
It should ask you to install 2.3.6. Just go into setting>about phone>check for updates. Or you could go and install one of the roms that are based on 2.3.6 such as Lithium Sonya or SCv5.

Okay gang, perhaps I'm just certifiably dumb, or I am simply just not doing this correctly. I downloaded the "Returntostock2.3.5.script" zip file and copied it to my wife's SD card to 'apply update from sdcard' option from the Android Recovery area by holding Vol Up, Vol Down, & Power buttons. What I got was this:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
I tried to just plug the USB into the phone and run the 2.3.5. script from there. but again- I'm stuck in the crazy skewed "M" logo startup screen with nothing following. That's all the phone will do at this point, other than my getting into Android Recovery.
I'm not sure how or what fastboot is, or how it works. If the phone is plugged into the USB, it will only boot the stupid screwed up "M" logo screen. Noting else.

Apex_Strider said:
Okay gang, perhaps I'm just certifiably dumb, or I am simply just not doing this correctly. I downloaded the "Returntostock2.3.5.script" zip file and copied it to my wife's SD card to 'apply update from sdcard' option from the Android Recovery area by holding Vol Up, Vol Down, & Power buttons. What I got was this:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
I tried to just plug the USB into the phone and run the 2.3.5. script from there. but again- I'm stuck in the crazy skewed "M" logo startup screen with nothing following. That's all the phone will do at this point, other than my getting into Android Recovery.
I'm not sure how or what fastboot is, or how it works. If the phone is plugged into the USB, it will only boot the stupid screwed up "M" logo screen. Noting else.
Click to expand...
Click to collapse
do not flash this. unzip it on your computer, choose to boot into fast boot in the same place you chose recovery, then run the .bat file that was in the zip.
Sent from my MB865 using XDA

What that file does is reflash your system.img, basically restoring your phone to factory default. And just as a sidenote you cannot flash things with the standard Android Recovery. You need CWM.

did you try apboot mode and ise fastboot to flash system.img ?
Sent from my ME865 using xda premium

Still not working... not sure how to flash from fastboot. I don't have any options to run a file from there, or at least not sure ow to go about that.

Fastboot sample, hope will help you.
http://bbs.gfan.com/mobile/android-3701449-1-1.html
Sent from my ME865 using xda premium

dickluo said:
Fastboot sample, hope will help you.
http://bbs.gfan.com/mobile/android-3701449-1-1.html
Sent from my ME865 using xda premium
Click to expand...
Click to collapse
So, if I'm looking at this correctly, I need to open command prompt from my computer, and type the commands in from there?
I don't think my computer is recogzining the phone in any way, as I cannot get into the 'manage usb connections' options.
If I have the 2.3.5.script downloaded on my desktop, and l plug my phone in after launching AP Fastboot on the phone, will the computer know where to flash the file to?
I know, I'm a dolt... please bear with me, I really need to get this thing working again -I feel naked without my phone!

Apex_Strider said:
So, if I'm looking at this correctly, I need to open command prompt from my computer, and type the commands in from there?
I don't think my computer is recogzining the phone in any way, as I cannot get into the 'manage usb connections' options.
If I have the 2.3.5.script downloaded on my desktop, and l plug my phone in after launching AP Fastboot on the phone, will the computer know where to flash the file to?
I know, I'm a dolt... please bear with me, I really need to get this thing working again -I feel naked without my phone!
Click to expand...
Click to collapse
Before using the restore script you need to install the usb drivers for your mb865, you can get those from here: http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/MotoHelper_2.1.40_Driver_5.5.0.exe
Next unzip the Return to Stock 2.3.5 Fastboot SCRIPT.zip to anywhere you like in your pc (example: C:\RestoreScript\ )
Next connect your phone with the usb cable to the pc and get into fastboot mode for this in your phone press volume down + volume up + power it should appear a screen with some options, use the volume down key of your phone to navigate through the menu until you see the Fastboot option, then enter by pressing the volume up key, this will show you some messages and the finally it should said usb connected.
Then open the folder where you extracted the Return to Stock 2.3.5 Fastboot SCRIPT files and search a .bat file call "Stock Restore" then run the file (double click on it) and it should open a command promt screen with some instructions if the phone is connected correctly and you installed the drivers correctly then in some point the screen will show you the id of your device and it will wait you to press the enter key to start the proccess, press key enter wait all the proccess until the program said to you its finished, after that it will reboot your phone and install the stock 2.3.5 when it boots up you should see the android logo and a progress bar filling up.
when it's done wait the reboot and your phone should be ok.
hope this helps.

jfrank1485 said:
Before using the restore script you need to install the usb drivers for your mb865, you can get those from here: http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/MotoHelper_2.1.40_Driver_5.5.0.exe
Next unzip the Return to Stock 2.3.5 Fastboot SCRIPT.zip to anywhere you like in your pc (example: C:\RestoreScript\ )
Next connect your phone with the usb cable to the pc and get into fastboot mode for this in your phone press volume down + volume up + power it should appear a screen with some options, use the volume down key of your phone to navigate through the menu until you see the Fastboot option, then enter by pressing the volume up key, this will show you some messages and the finally it should said usb connected.
Then open the folder where you extracted the Return to Stock 2.3.5 Fastboot SCRIPT files and search a .bat file call "Stock Restore" then run the file (double click on it) and it should open a command promt screen with some instructions if the phone is connected correctly and you installed the drivers correctly then in some point the screen will show you the id of your device and it will wait you to press the enter key to start the proccess, press key enter wait all the proccess until the program said to you its finished, after that it will reboot your phone and install the stock 2.3.5 when it boots up you should see the android logo and a progress bar filling up.
when it's done wait the reboot and your phone should be ok.
hope this helps.
Click to expand...
Click to collapse
jfrank1485,
This stepped me through the entire process without any confusion! Everything is back to normal! Hooray and three Huzzahs!
Also, many many thanks to dickluo, farshad525hou, lkrasner, mtnlion, and KEB64!
You guys really saved my stupid (you know what) on this deal! Next order of business: figure out what the heck I am doing before doing ANYTHING!
Problem solved, my world has regained sanity, and my phone is back to life!
You guys are the best, thank you all so much!!!

Apex_Strider said:
jfrank1485,
This stepped me through the entire process without any confusion! Everything is back to normal! Hooray and three Huzzahs!
Also, many many thanks to dickluo, farshad525hou, lkrasner, mtnlion, and KEB64!
You guys really saved my stupid (you know what) on this deal! Next order of business: figure out what the heck I am doing before doing ANYTHING!
Problem solved, my world has regained sanity, and my phone is back to life!
You guys are the best, thank you all so much!!!
Click to expand...
Click to collapse
I'm glad it work , keep it at hand before doing anything to your phone, it really helps

[Q] botched ROM load, now stuck in recovery hell

I got in a SK4g for my wife intent on upgrading her current phone. I own a 4g myself, and have Rooted/ROM'd it with no issues, we we thought it best to get her the same phone for ease of use/manipulation.
I got the phone in and used superoneclick to root it, then went through the process of putting CWM in place and installing GenericGinger_2.0_SK4G. The process ran smooth as glass (as expected) until it got to reboot. On reboot it hung up on the sidekick screen. After about an hour of waiting I pulled the battery and restarted the machine.
It came back up in recovery mode with the stock recovery (blue) text. Since then I haven't been able to get it to do anything but restart into that recovery screen. Odin doesn't see the phone in download mode and t839-Sidekick4G-UVKG2-One-Click does nothing. It shows it uploading, reboots the phone, and I'm back at the blue text. flashing the bootloaders with One-Click shows success on everything *except* uploading the bootloaders. If I tell it to re-install packages I get a 'cannot validate signature' response. I've tried using android commander to push CWM's recovery file to the phone and get 'permission' denied.
I've done a lot of searching on this site, trying most suggested fixes I've come across with no luck.
what can be done with this phone to get it back in operating condition?
Thanks in advance!

try installing kies odin wouldnt see my phone until i installed it

Kies installed and Odin saw the phone. excellent, thanks!
now, the next issue... lol
I used Odin to push KD1OdinSTOCK onto the phone. it's doing more than it was (going to the initial sidekick screen then dumping to recovery). Now it'll load through the sidekick and samsung splash screens, then reset and do it again. The same thing happens when I tried StockKG2ODIN. I'm using the sk4g.pit that I pulled from this site, could that have anything to do with it/is there another one around that I could try? Anybody have thoughts or ideas on what to do next? I've tried using t839-Sidekick4G-UVKG2-One-Click again, but it nuked the drivers kies put into place and dropped the phone back to what it was doing before.

okay, I did some light reading of this thread here
and followed the directions closely. I also went through sduvick's list of things to do with the following results:
Black screen, no logo.
1. Get into download mode by using VolDown+Touchpad+Power
2. flash full sk4g.tar.md5 as posted.
device will boot through the logo and splash screens, then repeat. note: if I leave the USB cable plugged in on reboot it will go to the battery screen, otherwise it just boot loops.
_________________________________
logo only
1. Download mode
2. Flash full package
device boot loops
_________________________________
Can't flash recovery/boot/sbl
1. Download mode
2. use PIT only, run with repartition checked
3. reboot/reDownload mode
4. run the full image in Odin.
PIT only returns a black screen on the device. running the full image in afterward returns to the boot loop.
_________________________________
Anything else
1. Download mode
2. Full tar.md5 flash in Odin
3. Ask if it doesn't work
okay, so I'm asking...
I'm still able to boot into recovery mode (blue text).
I've noted a bit of strange behavior when trying to boot into download mode. holding vol down + trackball + power does nothing. however, if I plug the phone in while powered down while holding down the trackball it'll boot into download mode, no power or vol down required.

If you can't flash with Odin, you may have a hardware problem.
Judging from your issue with installing Kies, you had a driver problem previously.
Seems that you are bumbling in the dark here. Once again, people need to be better prepared to Odin their devices before they start modding them.
In fact, getting Odin working should be the first thing a person should do with their phone after rooting and installing CWM.
Anyhow, try a different version of Odin. If that doesn't clear up your problem, I suspect some bad blocks in your flash memory are responsible here. It's a dorment issue that would really only be a problem when you flashed the device. If that's the case, you have a new paperweight.
Good luck.

i never could get kd1 to work try kg2
use pit check repartion and place tar file in pda

I don't think the problem is that I can't flash with Odin, but that the device isn't loading the ROM that's flashed. poking around in the filestructure with android commander after a fresh load shows that the system makes it onto the phone.
Speaking of poking around with Android Commander, I've noted that the device is software rooted, but not hardware rooted. the default.class file shows ro.debuggable set at 0 where it should be 1. this is keeping me from just pushing the CWM recovery onto the system and restoring the backup I made before getting into this mess. Anybody want to help me pull/edit/flash the image to change that?
As for a driver issue, that's a good possibility given that the one-click uses a driver set, kies mini uses another, kies has a different one yet and we (as a community) started screwing with the t839's using vibrant drivers. I've got them all. thusfar the only drivers I've found that work with both flavors of Odin I have (1.61 and 1.85) would be those that came with the Kies (thanks for the tip pmp326).
On bumbling in the dark, yes, yes I am. There isn't much of an instruction manual for Odin past what's written here, and 90% of that is 'put your phone in download mode, connect Odin, plug the pit in pit and the tar in PDA make sure only auto-reboot is checked and hit start'. to be honest I haven't had to use the program previously as the stock one-click actually worked on my T839. This new device is being ... difficult.
the dormant bad blocks issue you spoke about, was this something found in new-out-the-box phones? I haven't seen a lot about that in the threads, can you point in at more info, please?
at any rate, it doesn't matter which version of Odin I use, I got the same result from both. I tried using a different cable/different USB port as well. I haven't tried using a different system (yet), but don't want to go through all the trouble of setting up everything on another box. Win7 is finicky enough, trying to get everything operating on Server2k3 would most likely end up a challenge. *lol*
I'll try repartitioning with KG1 when I get back to the house.

Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.

also i had some troubles a while back while in recovery wipe data and cache turn off phone pull sd card then flash with odin

orange808 said:
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
Click to expand...
Click to collapse
I've gotta pop the debug lock in the default.class to be able to push anything into the system folders with Android Commander. I've found a nice walk-thru to do this, it just requires a little knowledge of c++ and some patience. with any luck I should be able to pull default.class out of its img, edit it and flash that back (most likely with Heimdall since it can do itemized flashing).
pmp326 said:
i never could get kd1 to work try kg2
use pit check repartion and place tar file in pda
Click to expand...
Click to collapse
tried it, no joy.
pmp326 said:
also i had some troubles a while back while in recovery wipe data and cache turn off phone pull sd card then flash with odin
Click to expand...
Click to collapse
tried this, brings me back to the boot loop.

orange808 said:
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
Click to expand...
Click to collapse
currently I'm running into issues with getting ADB to push onto the system as the system is claiming it isn't rooted. Is there a way I haven't read about or found to root the phone without getting into the actual O/S (i.e. from the blue recovery screen)?

If you can get in to CWM Recovery you are fine.
If you cannot, just ODIN to stock.
If you cannot do that, or it doesn't boot after that, try a different PC, os, or drivers (x86 os is usually easier then an x64 os).
If it is still no good, buy a new phone on ebay .
Once booted, Root and install CWM first thing.
Once you are in CWM Recovery...
1) Check mounts (everything should be mounted, and therefore read "unmount [...]")
2) Format EVERYTHING one at a time: cache, data, system, sdcard (optional).
(sdcard should be fine, but to be sure you can format it too after backing it up to PC first and restore what you need after)
(you probably don't need to Wipe and Wipe-Dalvik as they should already be gone, but go ahead and do it anyway)
3) Check mounts again!
4) Install a ROM (must reload it to your sdcard first if you formatted your sdcard)
5) Check mounts one final time before rebooting.
That should ALWAYS work.
NOTE: This was said before: "2. flash full sk4g.tar.md5 as posted.", but that doesn't seem right... you should not be flashing a .md5 file... you need to flash the .tar... the .tar.md5 is just a checksum. (right?)

rpmccormick said:
If you can get in to CWM Recovery you are fine.
If you cannot, just ODIN to stock.
If you cannot do that, or it doesn't boot after that, try a different PC, os, or drivers (x86 os is usually easier then an x64 os).
If it is still no good, buy a new phone on ebay .
Once booted, Root and install CWM first thing.
Once you are in CWM Recovery...
1) Check mounts (everything should be mounted, and therefore read "unmount [...]")
2) Format EVERYTHING one at a time: cache, data, system, sdcard (optional).
(sdcard should be fine, but to be sure you can format it too after backing it up to PC first and restore what you need after)
(you probably don't need to Wipe and Wipe-Dalvik as they should already be gone, but go ahead and do it anyway)
3) Check mounts again!
4) Install a ROM (must reload it to your sdcard first if you formatted your sdcard)
5) Check mounts one final time before rebooting.
That should ALWAYS work.
NOTE: This was said before: "2. flash full sk4g.tar.md5 as posted.", but that doesn't seem right... you should not be flashing a .md5 file... you need to flash the .tar... the .tar.md5 is just a checksum. (right?)
Click to expand...
Click to collapse
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.

Artemis257 said:
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Click to expand...
Click to collapse
I like turtles.

Artemis257 said:
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Click to expand...
Click to collapse
Even the end... I mean, your not trying to odin a "tar.md5" are you?

rpmccormick said:
Even the end... I mean, your not trying to odin a "tar.md5" are you?
Click to expand...
Click to collapse
No....

Sorry man. I've never had to ODIN (this phone). I say check the md5 to make sure you downloaded a good copy, and maybe try a different USB cable. The ADB method seems nutz... if it doesn't boot after a successful ODIN, the phone is probably a paperweight.
Good luck!