Database Develop

[Q] CWM, Dual-boot & Market issues...dazed and confused

Hi Everyone,
Sorry for this long-winded post. I've spent hours reading posts here, AndroidCentral and AndroidTablets.net forums, but have not found answers that work for me.
I hope someone can sort out the mess I've created on my rooted 1.1 Nook. Everything worked for 4-5 weeks after I rooted with Decad3nce method until...
A few days ago I decided to try 1.1G kernel. Read many threads about issues with Root Manager/ CWM; 3.0.0.5/3.0.0.6/SD CWM/EMMC CWM/Nook/Nook (old). When I booted into CWM, the version was 3.0.0.5. If I tried flashing CWM through Rom Manager, it said it 'flashed' 3.0.0.6 (tried both "Nook" and "Nook(old)"), but it never changed version of CWM I booted into. I also tried nemiths' "[RECOVERY] Official CWM 3.0.0.6 Update [BROKEN] (new fix soon!)" method to flash 3.0.0.6, but "adb shell busybox" always gave a 'can't get root' type error, so I gave up on that. I ended up using my current CWM to flash 1.1G kernel, and it worked very well. So I ignored the the CWM issues.
Then, I decided to try rookie1's dual-boot method so I could try out Honeycomb. I could never get 'prep_dualboot' zip to flash. It always gave an 'error in zip (status 0)'. His thread showed a few others getting same error, but none of the fixes given worked for me. I re-flashed that zip and ran the 'un-dualboot' zip many times with same result. I then found a "EMMC_CWM_3.0.0.6" zip and flashed that with my CWM. That actually gave me 3.0.0.6 CWM, but flashing dualboot still didn't work. I also again un-dualbooted, wipe cache partition, wipe dalvik cache, fix permissions with same result. So I gave up on that for now.
Then this morning, I found Market updates and downloads don't work anymore. It says 'about to download', then shows the arrows in status bar and nothing else happens. Saw threads regarding this issue and tried clearing Market cache and wiping whatever I could in CWM. Nothing I've found has helped so far.
As a side note in Rom Manager, "Recovery" section now shows 3.0.0.5 (before it wanted to flash 3.0.0.6). Tried flashing 3.0.0.5 there, but it doesn't seem to do anything (same as when it tried to flash 3.0.0.6). I can't understand the logic in Rom Manager. I also have Fascinate phone and RM has issues on that phone also.
I do have CWM backups and Titanium backups of all my stuff, so at worst I can do those. Looking for possibly easier way to get back to 'normal' so Market works and I can download the 'dual boot' zip and be happy again.
Some additional questions I have:
1) I saw in Decad3nce post that he left out 'root' for busybox in an early release, so that may be why mine won't work. I know I had used busybox before, but that may have been on earlier rooted 1.0.1. Is there a way to fix my current busybox without re-rooting?
2) What is the correct CWM I should use for 1.1 and will let me flash dual-boot zip? Also, where can I download it from and how can I replace the one I have?
3) I have saved my SD card to my computer many times and then re-formated it on the Nook. Is there some partition on it that format isn't cleaning that may contain some CWM image(s) causing at least some of my headaches?
Thanks in advance to anyone that can help with these issues. I may have tried a few other 'fixes' that I've since forgotten in the 5 hours last night trying to setup dual boot and quick hour this morning before work trying to sort out Market. Sorry (in advance) if you suggest something and I then say I tried it already. Possibly, just doing all the fixes I've tried previously in the correct sequence is what I need.

I seem to back to where I was before 'bad' versions of CWM skewered Market on me.
1) busybox: found that I just had to 'chmod 755' on my /system/xbin/busybox.
2) Saw that nemith posted a 3.0.0.9 version of CWM. Flashed that using his manual method. Didn't flash his kernel. Rebooted.
3) Tried clearing Market cache and didn't help. Wiped partition cache in CWM (or possibly Dalvik cache, not sure now...was going to do both but rebooted by mistake). After reboot, Market is working again.
Not sure if any of these affected Market, but I also unchecked/checked "Allow Non-Market Apps" and Unchecked/Checked "USB Debugging" and Unchecked "Auto Mount" in Settings.
Can't post in Dev area, so hope some there having same issue as me Market see this.
Now, gonna try the dual-boot again.

Alas, still getting (status 0) error flashing dual boot prep zip. Project for another night.
Sent from my LogicPD Zoom2 using XDA App

I'm getting that same error trying to flash the dual boot prep zip on my rooted Nook. Very frustrating.

jhoward88 said:
I'm getting that same error trying to flash the dual boot prep zip on my rooted Nook. Very frustrating.
Click to expand...
Click to collapse
From error logs it appears the sizes used in re-partitions may be the problem. Over weekend I'm going to try to find values that work. Could be the size differences reflect how NC was originally configured or how many re-roots/updates it has gone through and affect whether the prep works or not. Errors do occur on the 'remove dual boot' ZIP also.

vinal said:
From error logs it appears the sizes used in re-partitions may be the problem. Over weekend I'm going to try to find values that work. Could be the size differences reflect how NC was originally configured or how many re-roots/updates it has gone through and affect whether the prep works or not. Errors do occur on the 'remove dual boot' ZIP also.
Click to expand...
Click to collapse
No luck getting this to work

vinal said:
No luck getting this to work
Click to expand...
Click to collapse
Got a suggestion from Rookie1 to reformat my media partition. Prep now succeeded!
newfs_msdos -F 32 -L media /dev/block/mmcblk0p8

[S5830 + B/D/L/T ONLY] A Newbie Guide for your Galaxy Ace

Note: CyanogenMod 7 Official Support is HERE
Note 2: THIS THREAD IS FOR THE SAMSUNG GALAXY ACE S5830/S5830B/S5830D/S5830L/S5830T ONLY. IT DOES NOT APPLY TO THE S5830i/C/M
This serves as a warning and guide to all the new users in the Galaxy Ace XDA forums .
Samsung Kies is Samsung's version of iTunes . It allows you to sync all your stuff and back them up in case of phone problems .
But there's one thing Samsung forgot about: Memory optimisation . Kies requires at least 1.5GB of system memory . Even iTunes handles memory better than Kies.....
As a result , many users brick their Aces because they use Kies to update their phone and Kies suddenly stops responding because of RAM .
EDIT: I am not so sure now because some users have successfully updated their devices with Kies .
ROM Manager is a manager for Clockworkmod Recovery , which saves time because you don't have to reboot to recovery .
People, don't use ROM Manager for your own good......
You can also use CWM Manager , which is included in most custom ROMs .
Clockworkmod Recovery supports Galaxy Ace with many versions (with the official one being v4.0.0.9) .
The unofficial versions are v3.2.0.1 (if I'm not wrong) , v5.2.0.3 and v5.2.0.6 .
Edit: WITH CF-ROOT , BUSYBOX is BULLETPROOF
Another note about UNLOCKING YOUR PHONE by consegregate:
consegregate said:
Unlocking is an extremely risky process which touches your efs folder. Your IMEI can be wiped if you do a wrong step and that's the end of your road in the android conquest. Many of us have fallen to the enticing prospect of unlocking where the phone gets out of the box and poof goes back in again in no time.
SO, until we can backup the IMEI, try not to unlock using unorthodox methods. It may work for some, but for most of you you'll be left with ****ty phones because you can't read and follow instructions. So until then, please don't post "bricked mai phone help plz" because if it was because of unlocking, we may not be able to help you.
Lastly, USE THE SEARCH TOOL. AIN'T THERE FOR NOTHING! Cheers, all you sad faces.
Click to expand...
Click to collapse
A view about this tutorial by Ardentfaith:
Ardentfaith said:
Okay first off, the tutorial is wrong.
I have a USA Samsung Galaxy ACE
WHAT MOST PPL WANT TO DO:
1) root phone 2) have an escape plan when it fails.
Let's work on the escape plan.
Make sure you use Samsung KIES to update to the latest version of Android Gingerbread. Why? You could go to samfirmware to get a firmware and then download odin to flash it but why? You want to BAckup an ORIGINAL working rom.
Now you have Gingerbread. You want a backup. Search for chinoray and clockwordmodace.zip. This'll give you the backup program (a.k.a Clockworkmod Recovery) so you can do a recovery no matter what. (Press home and power to boot into recovery mode. there's an option to install from a zip. Install chinoray's file)
Now backup. Remember to put the backupfile that's made in 2 other places. Your sdcard isn't exactly a bank.
Now you want to root. Do the same recovery thing with a file from davebyone called Acegingerroot.zip. That roots it to an english brazil portuguese kp7 thingie. It's just fastest way to root. You'll have superuser app on now. congrats.
Now what to do with root? Your ace has very little memory. You need to extend the internal app storage to the sd card. The FIRST thing you need to do is go back to Clockworkmod recovery mode and partition your sdcard so that it has a ext4 extension. Then update from ketut.kumajaya's post with cf-rootdtapps2sd???.zip(forgot the full name). That defaults all downloaded apps to run from the sd card.
--Or you can ignore all this and do the chainfire post cf-root guide but ket's modifications are more hassle free.
so now you have a rooted Samsung ACE running Gingerbread running Touchwiz with apps running off the SD card.
There's not a good rom out for Samsung ACE anyways. You might as well stick to this for now.
Click to expand...
Click to collapse
Here's a little guide on how to flash a ROM via ODIN by me:
Requirements:
- A Windows computer
- A Galaxy Ace plugged into the computer via USB
- You must have ODIN installed , duh !
- (Windows Vista/7 compulsory) Running ODIN with Administrative rights:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Ended KIES via Task manager:
Instructions:
1 - Download your favourite firmware here
2 - Extract the .rar out using WinRAR or 7zip (password is samfirmware.com)
3 - Check if it's a FULL package or ONE package:
FULL Package instructions:
1 - Open up ODIN (MAKE SURE ALL REQUIREMENTS ARE MET)
2 - Set your phone in Download Mode (Home + Power + Volume Down)
3 - Once you have correctly entered Download Mode and plugged in , this should appear in ODIN:
4 - Place the files in this order:
OPS - Select the file named Cooper_v1.0.ops (or anything like that)
BOOT - Select the file named "APBOOT_S5830xxxxx_CL514579_REV03_user_low_true.tar.md5"
where "xxxxx" = Your firmware version
Phone - Select the file named "CODE_S5830xxxxx_CL514579_REV03_user_low_true.tar.md5"
where xxxxx = firmware version
PDA - DO NOT PLACE ANYTHING
CSC - Select the file named "GT-S5830-MULTI-CSC-xxxxxx.tar.md5"
where "xxxxxx" = the CSC region
EFS - Select the file named "MODEM_S5830xxxxx_CL514579_REV03.tar.md5"
xxxxx = firmware version (Be VERY VERY careful with this EFS part)
After you're done , click on "Start" and let the magic reveal itself slowly......
ONE Package method:
1 - Open up ODIN
2 - Set your phone in Download Mode while plugged into USB
3 - Tick the option "One Package" in ODIN (Refer to previous ODIN picture)
4 - Select the only .tar.md5 file
Now press start and watch the magic.....

Nice info
Could you add this:
Do not install busybox on custom ROMs because busybox already exist on most custom ROMs, and also stock firmware with CF-Root. If you're already do so, it mean that you're ready to reflash your phone ...or try to remove all files named "busybox" with root explorer then flash CF-Root b79 (then flash b80 for KPN users)

Ya you are right when I am new for galaxy ace I Install rom manager and while taking backup through it my phone suddently off and not start not even in downloading mode. Means it breaked. But thanks god it repaired by samsung service senter. So not install that app.

Here's a little Q&A:
Q-1: What is the Samsung Galaxy Ace? Is it edible?
A-1: Hello dear newbie , the Samsung Galaxy Ace is a mid-range phone that was released by Samsung in February 2011 .
Specifications:
-Supports Quad band GSM (850/900/1800/1900)
-Supports Duo band HSDPA (900/2100)
-Size is 112.4 x 59.9 x 11.5 mm
-Weighs 113g (light )
-Has a TrueFont Type capacitive touchscreen with 16,000,000 colours
-Screen resolution of 320x480 and a 3.5" display (160 dpi LCD density)
-Gorilla Glass display
-Multi-touch support
-Accelerometer sensor for auto-rotation
-Touch-sensitive Menu button and Back button (with physical Home button)
-TouchWiz v3.0 UI (Homescreen)
-Has a loudspeaker and has a 3.5mm audio jack with DNSe Sound Enhancement
-Has vibration(duh) ; supports MP3 and WAV ringtones .
-Has pratically unlimited entries for contacts and call records
-158MB internal storage with support for SDcard up to 32GB (2GB included)
-Supports GPRS , EDGE and HSDPA (7.2Mbps)
-WiFi 802.11b/g/n , Portable hotspot and DLNA certified
-Bluetooth v2.1 with A2DP (for bluetooth stereo headphones)
-No infrared port
-5MP Camera with autofocus , LED flash , geo-tagging , face and smile detection
-Records video at [email protected] (OMG ) with NO SECONDARY CAMERA
-Runs Android (Froyo , but upgradeable to Gingerbread)
-800Mhz Qualcomm MSM7227 ARM11 processor with an Adreno 200 GPU
-SMS (threaded view) and Email support
-Comes with a stock HTML Browser
-Supports Stereo FM Radio with RDS
-Supports Games (a.k.a APK files)
-Comes in Black and White (as in the selection of battery covers )
-A-GPS support with the normal GPS
-Supports Java with the MIDP emulator
- MP4/H.264/H.263 player
- MP3/WAV/eAAC+ player
- Organizer
- Document editor
- Image editor
- Google Search , Maps , Gmail , YouTube , Calendar , Google Talk , Picasa integration
- Voice memo/dial
- Predictive text input (Swype) (Other keyboards available on Market)
-1350mAh Lithium-Ion Standard Battery
-2G standby up to 640hours and 3G standby up to 420hours
-2G talktime up to 11hours and 3G talktime up to 6hours 30minutes
-Costs about 260 Euros
Thanks to http://www.gsmarena.com/samsung_galaxy_ace_s5830-3724.php
*Pants*
Q0: What is root? What advantages can it do to my phone?
A0: "Rooting" your phone is the process of allowing Superuser access to your phone (a.k.a su or sudo access) , thus opening up system files to the user .
This is usually needed/done by custom ROMs .
More info can be found here:
http://en.wikipedia.org/wiki/Rooting_(Android_OS)
"Rooting is a process that allows users of mobile phones and other devices running the Android operating system to attain privileged control (known as "root access") within Android's Linux subsystem with the goal of overcoming limitations that carriers and manufacturers put on some devices. It is analogous to jailbreaking on devices running the Apple iOS operating system."
Q1: What is a custom ROM? What to can it do to my phone?
A1: A custom ROM can be either:
- Modifications to the official company ROMs (a.k.a Stock ROMs) , which increases its speed and stability compared to original Stock ROMs .
These ROMs include:
-Blackhawk (by ketut.kumajaya)
-Fla.sh (by fla.sh) (No Support Available anymore , therefore no link)
-Sangingerace and Persian Gulf (by sasanekabaran)
-The BehradGH ROM series (by BehradGH):
-BehradGH ROM Series KPB
-BehradGH ROM Series KPN/KPH
-BehradGH ROM Series KP9
-NoName (by an0nym0us_)
-My-UI (by jusada)
-GingerReal (by redmaner and MuayThaiFighter08 (I think , sorry if I got it wrong !) )
-FirstUA (by Grif_07)
-Glsmt (by sametpoyraz)
-TheMyth (by devilsking) (Thread Closed)
-Blockbuster ROM Goes Ace
-Mush69ROM (Thread Closed)
-TurboBlue (by tazlooney89)
There are other ROMs that do not use Stock ROMs and are built from scratch by these AWESOME people:
-AOSP 2.3.7 (A work-in-progress by me , fla.sh , Jekle_Ace and consegregate)
-Grif_07's CM7.1 BETA-Kang 2.3.5
-BehradGH CyanoAce CM7.1 RC1 2.3.5
-Infinity ROM (Based on CM7.2 by nims11)
-Infinity ROM (Based on CM7.1 by nims11)
-Gingercruzt (Based on CM7.2 by nims11)
-Touchwiz4 Style CM7.2 ROM (by slaid480)
-HaniMod*LiteStar (By sasanekabaran)
-Icecream Sunday & Speed Blur (by jusada)
-Cre.ActiveX (CM7.1 by saigetshu)
That is all you actually need to know
Q2: What's Recovery Mode? What is Download Mode? What are the different "Modes" that my phone can go into?
A2: Recovery Mode is a place where you go to if your phone is ever "stuck" or in a "bootloop" if you installed a ROM wrongly .
The stock recovery mode can't do much and therefore if you want better advantages such as:
-Backing up your current ROM and data
-Fixing Force Close Permissions
-Wiping your Dalvik-Cache
-Wiping Battery Stats (if your battery meter is jumpy , like all custom Stock ROMs)
-Install unsigned .zip files
-Formatting various parts of your internal memory (/system , /data etc)
-Mount USB Storage in Recovery Mode
The only thing you can do is use CLOCKWORKMOD RECOVERY
For Download Mode , it is a Samsung-exclusive feature that allows you to "Download" custom stock ROM files into your phone .
It works like a normal install in ClockWorkMod Recovery (a.k.a CWM) , except that it automates everything (wiping data , wiping system stuff)
These are possible modes which you can use to enter different places (for advanced people only):
Home + Power = Recovery Mode (whether stock or CWM)
Home + Volume Down + Power = Download Mode (normal)
Home + Volume Up + Power = ARMv9 Dump Mode
Home + Volume Down + Volume Up + Power = Download Mode (EMERGENCY)
Q2.5: What is ClockworkMod Recovery? How do I use it?
A2.5: ClockworkMod Recovery is one of the best custom recoveries out there and was made by the AWESOME koush
Here's how you use it by devilcode:
devilcode said:
There you go.... not from v4.0.0.9 but its of a old version but will give you and idea or to anyone else .. will not post a link to some other site so just posting the explaination here
Options explained
1. reboot system now
This one is self-explanatory.
Reboots the phone.
2. apply update from sdcard
This can be used for installation of any official or unofficial update, ROM, kernel, theme etc. that is in a zip format installable from recovery, as long as the file is named update.zip and it has been placed on the root of your SD card (i.e. not in any sub-folder). Selecting this option (and most of the options featured below) will bring up a rather annoying confirmation prompt but this has saved us on multiple occasions from a lot of trouble we would have been into due to accidental key presses.
3. wipe data/factory reset
This option wipes all user data on the device as well as cache. Doing this will leave your phone in the state it was in when you bought it or when any custom ROM was first installed. It will also wipe any sd-ext partition that you might have set up.
4. wipe cache partition
Wipes the cache partition of the device to clear all the data accumulated there over use. This is often used before installing a new ROM, app, kernel or any similar mod via recovery.
5. install zip from sdcard
This option brings up the following sub-menu:
A. apply /sdcard/update.zip
This one is essentially the same as the ‘apply update from sdcard’ option of the main menu.
B. choose zip from sdcard
Lets you install any zip file (with any name) from any location on your SD card. The file can be for a ROM, a kernel, an application, a theme or any mod as long as it is in recovery-flashable zip format. This is the most widely used option for installing a ROM that you have downloaded and copied to your SD card. Entering this option will bring up a screen that will allow you to browse your SD card for the zip file and select it for installation
C. toggle signature verification
Turns the signature verification on and off. When signature verification is on, you will not be able to install any custom ROMs that haven’t been signed by the developers (most custom ROMs aren’t signed). Switching it off skips the signature verification check and proceeds with the installation.
D. toggle script asserts
Seldom-used option for a vast majority of users. It simply turns script asserts on or off. If you don’t know about these (i don’t), it’s best not to change this option. (For advanced users ONLY)
E. +++++Go Back+++++
Takes you back to the main recovery menu, obviously!
6. backup and restore
Undoubtedly one of the most important features provided by a custom recovery, the backup and restore feature – also known as Nandroid backup – allows you to take a backup of your phone’s entire internal memory including all partitions, and save it on the SD card.
A. Backup
Takes a Nandroid backup, as explained above.
B. Restore
Lets you restore a previously taken backup. Entering this option presents you with a list of existing backups from the SD card that you can choose from for restoration.
C. Advanced Restore
This option is similar to the Restore option but once a backup has been selected to be restored, this option allows you to choose what parts of it to restore. You can choose to restore the boot, system, data, cache and sd-ext partitions.
7. mounts and storage
Allows you to perform maintenance tasks on all the internal and external partitions of your android device.
A. mount/unmount /system, /data, /cache, /sdcard or /sd-ext
These options let you toggle between mounting or unmounting these respective partitions. Most Galaxy Ace users need to mount /system and /data for ROM installations
B. format boot, system, data, cache, sdcard or sd-ext
These let you directly format any of these partitions. Take extreme care with this option as formatting any of these partitions will result in losing all data on them, especially the boot and system partitions. Formatting the system partition will remove your ROM and leave your phone without an operating system while wiping the boot partition may brick your phone unless you restore or flash another one before rebooting your device.
What's lucky is that Galaxy Ace users don't have the option to format the boot partitions.
C. mount USB storage
Lets you enable USB mass storage mode for your SD card right from recovery so that you can connect it to your computer via USB and transfer any files to/from it without having to leave recovery.
8. advanced
This section contains a few options most users will not require, though these can come handy quite often, especially wiping Dalvik cache, which is required before most ROM installations. Here are the options from this section:
A. Reboot Recovery
Lets you directly and very conveniently reboot from recovery right back into recovery. This is a useful option for certain back-to-back installations that require the device to at least boot once between them OR installing another version of CWM (like v5.2.0.6).
B. Wipe Dalvik Cache
Allows you to wipe the cache for the Dalvik virtual machine (the custom-built Java virtual machine for Android).This is required before most ROM installations and at other occasions too, for fixing some problems.
C. Wipe Battery Stats
Wipes the saved battery usage statistics and effectively recalibrates the battery. Useful in various scenarios when Android isn’t showing correct battery levels.
*This style of wiping battery stats is no longer useful*
D. Report Error
In case of errors, this feature can be used to save a log of recent ClockworkMod recovery operations on the SD card that you can later report from Android using ROM Manager.
E. Key Test
Lets you press any of the hardware keys to see if they are properly functioning, and to see their key codes.
F. Partition SD Card
This option gives you a no-frills way to partition your SD card properly for use with ROMs that supports a2sd (a hack that moves entire applications to the SDcard). Once this option is selected, you will be given options to choose the sizes for the /sd-ext partition as well as an optional /swap partition on the SD card, and will then automatically format it for you, leaving the remaining space for normal SD card usage. This option will wipe all data from your SD card so use it with caution!
G. Fix Permissions
Fixes the file permissions for the internal memory partitions back to default. This is very useful as a fix for several errors and Force-Closes that start appearing after you or an application you installed and provided root access end up messing up the permissions of important files.
Hope it helps :d
Click to expand...
Click to collapse
It certainly helped my friend
Q3: Help me, my phone is in a bootloop and won't go into the Launcher!
A3: Firstly , define your bootloop:
If you are stuck at the "Galaxy Ace" logo , that means you did not make a factory reset and cache wipe from Recovery Mode . Do that , then reflash and try again .
If it still does not work , your kernel might have a problem because you did not install your kernel properly .
For that I recommend CF-ROOT for Gingerbread and Froyo
However , if your phone is stuck at the bootanimation:
Stuck for more than 10mins and is repeating the animation: You did not flash your ROM properly . Refer to above .
Stuck for less than 10mins and is NOT repeating: I suggest you have some patience
Q4: AHHHHHHHH! I flashed a theme but now my phone is going into force closes and bootloops!!!!!!!!!!!!!!
A4: You probably flashed a theme that was meant for another firmware version (E.g. flashing a KPH theme into KPO) .
In that case , all you have to do is flash another theme which is for that particular firmware and you're saved
Everytime I flash a theme I will make a backup prior to installing . This ensures that I can restore back if I did something wrong
Q5: Is there any overclock for the Galaxy Ace?
A5: With CF-ROOT 3.7 b83 I can achieve 100% stability with 902Mhz but 10% decrease in battery life :/
Q6: What about Adobe Flash support?
A6: It is only PARTIALLY supported on CyanogenMod 7 , but may work on stock Samsung ROMs if on Cf-root .
It works on the stock browser and Dolphin Browser HD , but does not work on Opera .
Q7: What is Cyanogenmod? Why do so much people love it?
A7: Cyanogenmod is a ROM built from a modified generic AOSP build , which offers faster speed , better stability and even eliminates some problems induced by stock ROMs (i.e. In our case , the Sleep of Death a.k.a SoD) .
This ROM was made by none other than the legendary Cyanogen .
This makes the phone fast , stable and yet problem-free .
however , CM7 for the Ace is currently unofficial and in early release candidate and beta versions and is NOT recommended for newbies as they might encounter into problems they might not know how to solve .
Also , the things that were added by Samsung WILL NOT APPEAR in Cyamogenmod 7 .
If you rely on Samsung's additions too much , I suggest that you revert back to stock
Q8: Oh no! My phone is bricked! I accidentally flashed the wrong device in ROM Manager!
A8: Oh no . You might wanna try either:
Method 1:
-Remove the SIM card , SD card and battery from the phone
-Hold Volume Down + Home + Power
-(Optional) Bring it near a heat source .
-While still holding those buttons , place the battery into the phone
-It should go into Download Mode .
-Try to flash a full package file via ODIN and your phone should come back to life .
If that doesn't work , try Method 2:
-Bring the phone to a nearby service center for repair .
Q9: Hello, what's the difference between a full package ROM and a one package ROM?
A9: When you download a ROM from SamMobile , they have all the files in a .rar , the contents of the .rar determine its Package:
A Full Package ROM has quite a few files when the .rar is opened , one of them being a .tar.md5 if I remember correctly .
A One Package ROM only has one .tar file when the .rar archive is opened .
Q10 by scoffyburito:
scoffyburito said:
Err sorry if this sounds dumb but what version of CWM would i need if when im restoring my cm7 backup it says Md5 mismatch. I made the backup on CWM 5.0.2.6?
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
A10: Taken from http://forum.xda-developers.com/showthread.php?t=714114
ihtfp69 said:
I figured I would post this fix here in case anyone else ran into this problem. This is assuming you did not change the folder names and let Clockworkmod create them. I haven't had it happen until today, but it's not a nice message to see when you are trying to do a restore.
Code:
Checking MD5 sums...
MD5 mismatch!
To fix this problem use the code below. Substitute the final folder name for the backup you need to fix.
Code:
adb shell
# cd /sdcard/clockworkmod/backup/[I]backupname[/I]
# rm nandroid.md5
# md5sum *img > nandroid.md5
When that finishes, re-run the restore and everything should be fine.
NOTE: As rpearl stated, there could be something really wrong with your nandroid, so use this tutorial as a learning experience and not a fix-all. In my case, everything was fine after restoring. However, that may not always be the case. Do this with caution.
Click to expand...
Click to collapse
Q11 by psychoo118:
psychoo118 said:
Hey guys! I'd like to ask that is there any way to get my warranty back if I flashed CyanogenMod 7.1 Cooper Kang? :/ Fortunately, I don't need my warranty now, only asking if i will in the future Thanks
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
A11: Just flash back to DXKC1 (Froyo 2.2.1) or the Gingerbread version for your region , you're bound to fool Samsung
Q12: I have been hearing everyone talk about this file named build.prop. What is that?
A12: Okay, build.prop is the build properties of your current ROM.
I will give more explanation of the different entries as time goes on (LOL).
ro.ril.disable.power.collapse - (0/1) Variable Values.
0: Allows the network power collapse, thus wasting battery
1: Disables the network power collapse, thus saving battery.
ro.ril.hsxpa - (0/1/2/3)Variable values.
0: Disables HSUPA completely.
1: Disables stock HSUPA speeds (speeds capped)
2: Enables stock HSUPA speeds (speeds capped)
3: Enables uncapped HSUPA speeds
Q13: What is CF-ROOT? Is it edible?
A13: LOL no it isn't! CF-ROOT is short for Chainfire-Root (a.k.a Rooting + some tweaks). It has root and installs 3 apps: CWM Manager, Superuser and Tweaks.
CWM Manager is a substitute for ROM Manager and allows:
- Rebooting to recovery
- Backing up using app
- Restore using app
- Deleting backups
- Flashing .zip files
- Flashing zImage kernels (a.k.a CF-ROOT fixes)
The current version is b84, which is only for XWKT5/7 firmwares.
You can use b83, which is the universal CF-ROOT.
Q14: I keep running out of internal memory. Why does this happen? How do I solve it then?
A14: It is because the Galaxy Ace's internal memory is only less than 200MB, therefore too many apps will cause the phone to run out of memory. There are 3 known solutions to that:
1: DarkTremor's Apps2SD (DTA2SD)
- Most commonly used way of moving apps to internal memory
- Has an app for it at the Android Market (A2SDGUI)
- Uses a flashable zip (find it in XDA)
- Easiest to use among the 3
2: link2SD
- Makes use of symbolic links to move apps to the SD-ext partition
- I don't know much about this one
3: S2E (simple2ext)
- An app that's available in the Android Market
- Only for CM7 ROMs and the only one working for Ice Cream Sandwich (by maclaw)
- Hardest to use among the 3
That is all.
Q?: This thread seems inactive! When will you update it?
A?: I will update my thread whenever I want to , once I find new information .
Thank you for reading this thread so that one less Galaxy Ace gets bricked

For me, this should be a sticky post on development.. Maybe you need to request this as sticky post from any MOD and update all about Ace there..

izzoe said:
For me, this should be a sticky post on development.. Maybe you need to request this as sticky post from any MOD and update all about Ace there..
Click to expand...
Click to collapse
Uhh.....can you help me , because I don't know any of the MODs here

The only mod here... Has been retired better ask senior moderators...
Sent from my GT-S5830 using XDA App

fla.sh said:
The only mod here... Has been retired better ask senior moderators...
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
Explain Univos' Mod Edit in the thread

Unfortunately there's no report for sticky in this forum, which is a bit poor.

russ18uk said:
Unfortunately there's no report for sticky in this forum, which is a bit poor.
Click to expand...
Click to collapse
Sigh , so that means the chances of a sticky are gone huh ?
Sent from my Awesome Galaxy Ace S5830 with XDA App

EmoBoiix3 said:
Sigh , so that means the chances of a sticky are gone huh ?
Sent from my Awesome Galaxy Ace S5830 with XDA App
Click to expand...
Click to collapse
Nah, just manually PM a mod

russ18uk said:
Nah, just manually PM a mod
Click to expand...
Click to collapse
I'm kinda shy when it comes to such stuff
Sent from my Awesome Galaxy Ace S5830 with XDA App

Just PM a mod I had the luck to read the failures of others, by that way saving my ace (even though i wasnt planning on installing it).

+1 for sticky

QNBT said:
Just PM a mod I had the luck to read the failures of others, by that way saving my ace (even though i wasnt planning on installing it).
Click to expand...
Click to collapse
Oh well
Sent from my Awesome Galaxy Ace S5830 with XDA App

i have an Acer Iconia A500 and when i open Rom Manager for the confirmation of my model i see that there is Samsung Galaxy Ace but when i do exactly the same thing with my Ace i cant see it. its the same version (premium v4.3.3.0)
sorry for my english

EmoBoiix3 said:
This serves as a warning to all the new users in the XDA forums .
ROM Manager is a manager for Clockworkmod Recovery , which saves time because you don't have to reboot to recovery .
However , it doesn't support Galaxy Ace yet .
You can probably use CWM Manager instead , which is included in most custom ROMs .
Clockworkmod Recovery , on the other hand , supports Galaxy Ace with many versions (with the official one being v4.0.0.9) .
REMEMBER THIS , DO NOT INSTALL/DOWNLOAD ANYTHING WITH ROM MANAGER . Use Clockworkmod Recovery for Backups , Restoring , Flashing .zip or whatever the Recovery can do .
IF YOU TRY TO INSTALL ANYTHING USING ROM MANAGER YOU MIGHT NEED TO BRING YOUR PHONE AND WARRANTY CARD TO THE NEAREST SERVICE CENTER .
Additional information by fla.sh about Busybox (with some grammar changes ):
Click to expand...
Click to collapse
Hey man,
great thread. Thnx

biupil said:
i have an Acer Iconia A500 and when i open Rom Manager for the confirmation of my model i see that there is Samsung Galaxy Ace but when i do exactly the same thing with my Ace i cant see it. its the same version (premium v4.3.3.0)
sorry for my english
Click to expand...
Click to collapse
Different phones have different CWMs . (I thought your were talking about CWM v4.3.3.0 , but you were talking about ROM Manager v4.3.3.0 instead )
Sent from my Awesome Galaxy Ace S5830 with XDA App

EmoBoiix3 said:
Different phones have different CWMs . (I thought your were talking about CWM v4.3.3.0 , but you were talking about ROM Manager v4.3.3.0 instead )
Sent from my Awesome Galaxy Ace S5830 with XDA App
Click to expand...
Click to collapse
yes i was talking about ROM Manager v4.3.3.0 my bad.
but why do is see my phone(ace) in the list of A500 and not in my ace? its the same version of the same program

biupil said:
yes i was talking about ROM Manager v4.3.3.0 my bad.
but why do is see my phone(ace) in the list of A500 and not in my ace? its the same version of the same program
Click to expand...
Click to collapse
That's a good question . Could you post a screenshot ?

[GUIDE & TOOLKIT][1.21.14 Final Update] One-stop Guide for 7300/7310

Final Update 1.21.2014 » Changelog.
For support beyond this guide, please look in another thread. I no longer have this product.
Thanks for all your support in this thread!
Bulletin Board
If your ROM has issues with root, see Fixing Root How-To for the solution.
-----------------------------
Common ICS issues FAQ by fred_be9300 here
------------------------------
NOTE: If you ever experience screen issues with the included CWM Recovery in the Toolkit, please flash the alternate version here or even better, flash TWRP (but be warned this guide's based on CWM).
Click to expand...
Click to collapse
This guide covers the following for models GT-P7300 and GT-P7310 in FAQ and How-TO sections:
Root/Unroot, Bootloader Mode, Odin, Recoveries & NANDROID Backup.
--------------------------------------------------​
Greetings people. The main focus of this guide is centralizing information and files about the title contents to help bolster this community. I'll be as clear as possible in this little guide and excuse me if my English isn't perfect (it isn't my native language) and this is my first XDA guide. Oh and a little disclaimer: I AM NOT RESPONSIBLE IF YOU IN ANY WAY DAMAGE YOUR TABLET. BY FOLLOWING THIS GUIDE YOU ACCEPT FULL RESPONSIBILITY FOR YOUR ACTIONS. ALSO PLEASE NOTE THIS GUIDE HAS BEEN WRITTEN WITH A WINDOWS PC IN MIND. IF YOU DON'T HAVE A WINDOWS PC AVAILABLE, GET ONE, BORROW ONE, I DUNNO, but you need one. That said, let's begin.
--------------------------------------------------
FAQ Section​
About Root
What exactly is root and what does it do in my Galaxy Tab 8.9?
XDA user phonic covered the technical details in this post, but basically root allows you to access and control (through applications) the device's internal system files, therefore making you a "superuser". Some apps require root. Advantages such as ad-blocking and more are only available if your device is rooted.
About Bootloader, Recovery & Download Modes
What is Bootloader Mode and how can I access it?
Bootloader Mode is a menu where you manage core functions in your device. In order to access Download Mode (needed for ODIN) and/or Recovery Mode (needed to flash ROMs and more), you will need to enter Bootloader Mode by holding VOL- when turning ON your Gtab, selecting the mode using VOL-, and entering by using VOL+. The box icon represents the Recovery Mode and the other one the Download Mode. While inside Recovery Mode, the Power button will act as an "Enter" button while the volume buttons will move the cursor.
I read something about Stock Recovery and CWM Recovery. What are those?
There are two types of recoveries. The default one that comes with your GTab (Stock Recovery which looks like this) and the CWM (Clockwork Mod) one which has cyan-colored letters for our GTabs. To flash ROMs and manage your device a bit more, you need the CWM one.[/U][/COLOR][/B]
Can I flash the CWM Recovery using the ROM Manager app? Oh and which file format is compatible?
Refrain from that. As of this writing, the ROM Manager app does not have a CWM Recovery compatible with our specific GTabs. If you still proceed, you will softbrick your device and your device will have to do a trip to ODIN in order to work properly once more. CWM-flashable files are .zip files.
About NANDROID Backup
What's NANDROID and why is it recommended?
Simple, a NANDROID is a master backup tool which is available through the CWM Recovery's "backup and restore" menu. It stores everything in the ROM except the kernel and your SDcard contents such as pictures, music, documents, etc (so always backup those elsewhere). It's more like this analogy: a photograph which captured the exact state of your ROM, apps and all at the moment of backup. It is recommended in case of emergency and in case you need to go back to the latest working ROM. How-To section below.
About ODIN
What's ODIN?
ODIN's a troubleshooting/emergency tool in case your GTab bootloops (eternal restarting of a device, i.e. softbrick). Please note that if your device's screen doesn't even turn on (an example of a hardbrick) then you may be out of luck. This tool can save your GTab if you follow instructions, or can hardbrick your GTab if you don't follow instructions.
Where can I find ODIN? Do I need something like a driver to make it work? Also, which file format is compatible?
Yes you do need a driver first (provided at the end of this guide) and a Windows PC. The ODIN program is inside the zip inside the Toolkit provided at the end of this guide. As suggested by developer alterbridge86, use ODIN version 1.85. Regarding file compatibility, generally the .tar files are the ones for ODIN.
Does it remove Root and custom recoveries such as CWM in case of a warranty claim?
Yes. There are two ways:
[*]Flashing an ODIN image to go back to stock defaults (easier in my opinion). If you want to use ODIN then you have options in the Development forum, specifically this thread.
OR
[*]Flashing a CWM zip file (CWM, which is a Recovery, will be discussed in the Recovery FAQ below) after doing all wipes and restoring Stock Recovery (Restoring Stock Recovery How-To is below these FAQs)
Ok, so how do I use the tool?
The How-to section is below the FAQs.
How-To Section
Remember, all files mentioned in this section this way are included in the Toolkit at the end of this guide.​
[ Rooting ]:::::::::::::::::::::::::::::::::::::::::::
Make sure to download the Toolkit from the link at the end of this post and put the "Root" .zip in your device's internal memory. You will enter Bootloader Mode, and then Recovery Mode as detailed in the About Bootloader FAQ above. You will now select "install zip from sdcard" then "choose zip from sdcard" and look for the Root.zip which you previously put in your SDcard. Select it with the Power button to flash it and then reboot your device. When your device finally boots, check if the SuperSU app is available, if it is then you're rooted now.
[ Fixing Root ]:::::::::::::::::::::::::::::::::::::::::::
In some cases a ROM can come with a broken root due to the superuser binary being located in the wrong system folder. Please flash the Root.zip package in CWM Recovery. The Root package will delete the offending binary from the wrong place and install it in the right place. For more instructions, see Rooting How-to.
[Unrooting]:::::::::::::::::::::::::::::::::::::::::::
For unrooting, proceed to Bootloader Mode and select the Recovery icon (detailed in the About Bootloader FAQ above) please flash the CWM Recovery flashable file provided in the Toolkit link at the end of this guide called "Unroot". Now reboot your device. If there is no app called SuperSU or Superuser in your apps list, then your device is now unrooted.
[Installing the CWM Recovery]:::::::::::::::::::::::::::::::::::::::::::
First, you need the file called either "7310_CWMR" or "7300_CWMR" depending on your model, inside your device's SDcard. The procedure is very similar to Rooting and either procedure can be done first. Go to Bootloader Mode (as detailed in the FAQ above), then Recovery (assuming you've Stock Recovery), select "apply update from /sdcard", then look for the file you put in the SDcard. Select it with the Power button to flash it. Now, reboot once more to Bootloader Mode, go to Recovery Mode and now you will see the CWM Recovery Mode. You are now ready to flash stuff. Please note you don't need root to flash a ROM, just this CWM Recovery. Be sure to follow the ROM thread's instructions precisely.
[Restoring Stock Recovery]:::::::::::::::::::::::::::::::::::::::::::
For this one you will need to use ODIN. Locate the file "Stock Recovery", which is a .tar file, perfect for ODIN's PDA section. Follow the ODIN 1.85's HOW-TO below.
[Doing a NANDROID Backup/Restore]:::::::::::::::::::::::::::::::::::::::::::
You need CWM Recovery for this one. Once you're in CWM Recovery, the process is straightforward. Look for the "backup and restore" menu, access it and you will see two options: "backup" and "restore". Select "backup" and wait until the system gathers all data and packs it as a backup located in your internal memory, inside a folder called "clockworkmod". Once more, remember this will not backup your SDcard contents such as your documents, music, pictures, etc (so always have a backup of those elsewhere).
For restoring the process is the same. You need to do the following to ensure a proper restore and prevent issues that might pop up: Wipe your system using CWM Recovery's "wipe data/factory reset" and after that go to "advanced" and now "wipe dalvik cache". Now go to the "mounts and storage" menu and select "format /system". That was a full wipe. Now proceed to the "backup and restore" menu, select "restore" to select your backup. Remember to reflash the kernel if you had one that didn't come with the ROM (like _motley's for example).
[Using ODIN 1.85]:::::::::::::::::::::::::::::::::::::::::::
Enter Bootloader Mode and then Download Mode as detailed in the FAQ above. Be sure to have installed the drivers (included in the zip at the end of this guide) in your Windows computer along with the ODIN program anywhere in your PC (also included in the Toolkit at the end of this guide). Open ODIN 1.85 in your PC, look for the "PDA" button, press it and look for the right file (which usually is the biggest-size file inside the downloaded and unzipped ROM .zip). THE FOLLOWING THREAD OFFERS MOST ODIN IMAGES. IF AVAILABLE, put the CSC, PIT and whatnot files in their corresponding places by pressing the corresponding buttons (IF these files aren't available, ignore this sentence). The PIT file is only necessary in case you want to have the Repartition option available and want to repartition the device (this is an alternative that can work in case of a really borked tablet full of bootloops even after a normal ODIN session without Repartition). Now, assuming you have the drivers installed in your PC, connect the device while in Download Mode, and you will see that ODIN will see it in a yellow rectangle in the upper section that says COM# (# being any number). BEFORE CLICKING "START" MAKE SURE "F. RESET TIME" IS CHECKED ON THE LEFT SIDE. Now, click the START button inside ODIN and it's flashing time. Wait until the blue meter fills. After ODIN says PASS in a green square, you can then reboot the device (long pressing the Power button is an alternative if it doesn't auto-reboot).
Toolkit Link: shorturl.at/pqCIY
SHA-1: 4DC13D60280ECA6352704AA72153E5E4EDF875E0
MD5: 59CC2548FC76D93075FDF8B392DAA1AE
Contains essentials such as: Drivers, Root, Unroot, Stock Recovery, CWM Recovery & ODIN files. Remember to unzip the package. Also, with drivers being included, you don't need to install KIES.​
[CREDIT GOES TO]:::::::::::::::::::::::::::::::::::::::::::
alterbridge86 (For his ROMs and the first CWM Recovery for our tablets)
_motley & Team Galaxian Soup (For their excellent kernels and deodexed ROMs)
kallt_kaffe (Pioneer in bringing the newer CWM Recovery to our tablets along with CyanogenMod ROMs)
suwandiapr (For the flashable unroot file and ODIN image thread)
phonic (Great rooting explanation and manual unroot post)
lufc & sudec123 (For the past mirror links)
Chainfire (For making SuperSU)
SamHaLeKe (For the Samsung USB drivers)
...and to anyone I might have forgotten, do say in a PM .
Click to expand...
Click to collapse

Changelog
Code:
[B][COLOR="Red"][I]1/21/2014 - FINAL UPDATE[/I][/COLOR][/B]
[B]TOOLKIT[/B] - Updated SuperSU to v1.91 for Root.zip - Important fix for Android 4.4.x
[B][COLOR="DarkOrange"][I]1/19/2014[/I][/COLOR][/B]
[B]TOOLKIT[/B] - Updated SuperSU to v1.89 for Root.zip
[B]TOOLKIT[/B] - Updated Adobe Flash Player to last release v.11.1.115.81
[B]TOOLKIT[/B] - Updated Samsung USB drivers to v1.5.29.0
[B]BULLETIN BOARD[/B] - Suggested TWRP Recovery with a warning.
[B]GUIDE[/B] - Deleted Mirror Link for Toolkit due to HotFile's shutdown.
[B][COLOR="DarkOrange"][I]4/20/2013[/I][/COLOR][/B]
[B]TOOLKIT[/B] - Replaced Superuser with SuperSU (v1.25) for Root.zip
[B]TOOLKIT[/B] - Updated Unroot.zip to remove either Superuser or SuperSU
[B]TOOLKIT[/B] - Updated Adobe Flash Player to version 11.1.115.54
[B]TOOLKIT[/B] - Updated Samsung USB drivers to version 1.5.18.0
[B]GUIDE[/B] - Modified Rooting, Fixing Root and Unrooting How-to to reflect Toolkit changes.
[B]BULLETIN BOARD[/B] - Redirected users having root issues to the right place, reflecting Toolkit changes.
[B][COLOR="DarkOrange"][I]1/13/2013[/I][/COLOR][/B]
[B]GUIDE[/B] - Unroot How-To - Added solution for ROMs that have the root binary
in the wrong place. See [B][COLOR="Red"]red[/COLOR][/B] note.
[B][COLOR="DarkOrange"][I]1/9/2013[/I][/COLOR][/B]
[B]GUIDE[/B] - Corrected error in the manual Unroot command (thanks trekker99!)
[B][COLOR="DarkOrange"][I]11/17/2012[/I][/COLOR][/B]
[B]TOOLKIT[/B] - Updated Root.zip and Unroot.zip
[B]TOOLKIT[/B] - Updated Adobe Flash Player to version 11.1.115.27
[B]TOOLKIT[/B] - Updated MD5 and SHA-1 checksums.
[B][COLOR="DarkOrange"][I]10/12/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Suggested Common ICS issues FAQ by fred_be9300
before the introduction.
[B][COLOR="DarkOrange"][I]10/07/2012[/I][/COLOR][/B]
[B]TOOLKIT[/B] - Updated & Fixed Root.zip. Independent file [URL="http://forum.xda-developers.com/showpost.php?p=32496433&postcount=257"]here[/URL].
[B]TOOLKIT[/B] - Updated USB drivers to v1.5.15.0.
No need to reinstall if you installed a previous version.
[B]TOOLKIT[/B] - For convenience. Added Adobe Flash Player 11.1.115.17
(latest version for ICS and Jelly Bean ROMs).
[B][COLOR="DarkOrange"][I]8/04/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Added MD5 and SHA-1 of the Toolkit in its section.
[B][COLOR="DarkOrange"][I]7/25/2012[/I][/COLOR][/B]
[B]TOOLKIT[/B] - CWM Recovery v.6.0.0.8 included.
[B]GUIDE[/B] - Alternate version link also [URL="http://forum.xda-developers.com/showpost.php?p=21194554&postcount=2"]included[/URL] in case
of screen issues in some units.
[B][COLOR="DarkOrange"][I]7/22/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Major redesign. Users can now choose what to view.
[B][COLOR="DarkOrange"][I]7/21/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Minor, simpler redesign using the Roboto font.
[B]TOOLKIT[/B] - PIT file for ODIN now included
[B]TOOLKIT[/B] - Drivers updated to v.1.5.6.0
[B]TOOLKIT[/B] - CWM Recovery v.6.0.0.0 included
[B][COLOR="DarkOrange"][I]7/1/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - *Fixing Root* How-To section updated and further simplified.
[COLOR="DarkOrange"][I]6/17/2012[/I][/COLOR]
[B]GUIDE[/B] - Added one important detail in Nandroid FAQ/How-To and Toolkit sections.
[B]CHANGELOG[/B] - Format revised for consistency.
[COLOR="DarkOrange"][I]6/10/2012[/I][/COLOR]
[B]TOOLKIT[/B] - Updated Drivers to v.1.5.5.0.
[COLOR="DarkOrange"][I]5/19/2012[/I][/COLOR]
[B]GUIDE[/B] - Reorganized contents for ease of use.
[B]TOOLKIT[/B] - Changed the CWM Recovery to a fixed one by kallt_kaffe due
to several getprop status7 flash errors with the one provided by alterbridge86.
[COLOR="DarkOrange"][I]5/8/2012[/I][/COLOR]
[B]GUIDE[/B] - Minor redesign.
[COLOR="DarkOrange"][I]4/24/2012[/I][/COLOR]
[B]TOOLKIT[/B] - USB Driver version 1.5.4.0 now included.
[COLOR="DarkOrange"][I]4/8/2012[/I][/COLOR]
[B]GUIDE[/B] - Included suwandiapr's ODIN images thread link in both ODIN FAQ & How-To
as reference.
[COLOR="DarkOrange"][I]4/7/2012[/I][/COLOR]
[B]GUIDE[/B] - Minor revisions in "Fixing Root" and manual "Unroot" commands.
[B][COLOR="DarkOrange"][I]2/25/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Minor redesign.
Fixed manual Unroot commands.
[B][COLOR="DarkOrange"][I]2/23/2012[/I][/COLOR][/B]
[B]TOOLKIT[/B] - Discarded model specific CWM Recoveries and
replaced them with an universal flashable
for convenience. Credit goes to alterbridge86.
[B][COLOR="DarkOrange"][I]2/16/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Deleted ODIN image suggestions.
[B][COLOR="DarkOrange"][I]2/5/2012[/I][/COLOR][/B]
[B]GUIDE & TOOLKIT[/B] - Updated with the newer CWM Recovery along with instructions where needed.
[B]TOOLKIT[/B] - Unroot flashable included along with a newer driver (not necessary if you already installed the previous one).
[B]GUIDE[/B] - Suggested firmware KHA for the 7310 instead of the KL2 one at ODIN FAQ's third question due to better feedback.
[B][COLOR="DarkOrange"][I]1/30/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Added newer KL2 ODIN firmware link for the 7310 in the FAQ.
[B][COLOR="DarkOrange"][I]1/27/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Minor reorganization/cleanup.
[B][COLOR="DarkOrange"][I]1/25/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Improved ODIN How-To with one little but very important detail in red.
[B][COLOR="DarkOrange"][I]1/23/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Removed Filesonic mirror due to them shutting down their file sharing services.
[B][COLOR="DarkOrange"][I]1/20/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Improved 3rd question of ODIN FAQ and also replaced links with the right ODIN images (had mistakenly put CWM links instead of ODIN image links).
Added a little disclaimer in the Bootloader FAQ in red.
[B][COLOR="DarkOrange"][I]1/19/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Removed the non-working Megaupload mirror link because of [URL="http://gizmodo.com/5877612/feds-kill-megaupload"]this[/URL].
[B][COLOR="DarkOrange"][I]1/14/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Added 3 new mirror links (thanks sudec123!).
Replaced KK5 (7300) ODIN firmware link with KL4.
[B][COLOR="DarkOrange"][I]1/12/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Improved Unroot How-To.
[B][COLOR="DarkOrange"][I]12/28/2011[/I][/COLOR][/B]
[B]GUIDE[/B] - Added Fixing Root How-To and updated ODIN FAQ with a new question.
[B][COLOR="DarkOrange"][I]12/26/2011[/I][/COLOR][/B]
[B]GUIDE[/B] - Added NANDROID FAQ and How-To.
[B][COLOR="DarkOrange"][I]12/22/2011[/I][/COLOR][/B]
Initial guide.

Thank for create this thread.

Nice work mate
Thanks for all the info, Will give it a sticky
Did a Mirror on File Sonic if you want to use it

mynewuser said:
Thank for create this thread.
Click to expand...
Click to collapse
No worries!
lufc said:
Nice work mate
Thanks for all the info, Will give it a sticky
Did a Mirror on File Sonic if you want to use it
Click to expand...
Click to collapse
Thanks a lot, lufc. I've put your provided link at OP along with credit.

Hi, I've installed the clockwork Recovery, I wiped everything because I wanted to turn back to factory defalut and now the tab is bricked.
I can turn on it, I see the galaxy tab logo but nothing happens.
So I turned to the default system recovery, wiped again but it is the same: after 10 minutes the screen shows only the logo and nothing else.
Any advice?
Thanks

HarryCustom said:
Hi, I've installed the clockwork Recovery, I wiped everything because I wanted to turn back to factory defalut and now the tab is bricked.
I can turn on it, I see the galaxy tab logo but nothing happens.
So I turned to the default system recovery, wiped again but it is the same: after 10 minutes the screen shows only the logo and nothing else.
Any advice?
Thanks
Click to expand...
Click to collapse
Flash a rom and you will be fine.

Done! Now it works perfectly.
Now i'll retry to install clockwork recovery...

Overcome_CWM_Recovery_v5.1.2.6_P73xx,Can use with the other galaxy device such as galaxy S plus?

somboons said:
Overcome_CWM_Recovery_v5.1.2.6_P73xx,Can use with the other galaxy device such as galaxy S plus?
Click to expand...
Click to collapse
I don't know. This guide is focused on the 7300/7310 variants of the Tab 8.9 as specified in the OP.
Sent from my GT-P7310

thanx nirogu for the guide..
all the steps is correct rite?
im going to try soon.... ^^
install CWM, backup stock rom using nandroid,
and then root....its better this way rite?
about root, it will void the warranty rite?
how about CWM? did we need to instal stock recovery back before claim for warranty or no need?
Thanx..^^

slaughterer0206 said:
thanx nirogu for the guide..
all the steps is correct rite?
im going to try soon.... ^^
install CWM, backup stock rom using nandroid,
and then root....its better this way rite?
about root, it will void the warranty rite?
how about CWM? did we need to instal stock recovery back before claim for warranty or no need?
Thanx..^^
Click to expand...
Click to collapse
Yes, you are correct. You can root while being in Stock ROM (the system that comes with your device) or after flashing a custom ROM. Yes, root will void it, but you can always go back to the factory image (hint: ODIN) and that removes everything, including CWM Recovery and Root. If you're staying with Stock ROM, then yes, you need to flash the Stock Recovery and Unroot (both How-Tos in the guide).

nirogu325 said:
[Restoring Stock Recovery]:::::::::::::::::::::::::::::::::::::::::::
For this one you will need to use ODIN. Locate the file "Stock Recovery" (in the zip included at the Download Link at the end of this post), which is a .tar file, perfect for ODIN's PDA section. Follow the ODIN 1.85's HOW-TO above.
[Doing a NANDROID Backup/Restore]:::::::::::::::::::::::::::::::::::::::::::
You need CWM Recovery for this one. Once you're in CWM Recovery, the process is straightforward. Look for the "nandroid menu", access it and you will see two options: "backup" and "restore". Select "backup" and wait until the system gathers all data and packs it as a backup located in your internal memory, inside a folder called "clockworkmod".
For restoring the process is the same. You need to do the following to ensure a proper restore and prevent issues that might pop up: Wipe your system using CWM Recovery's "wipe menu", do a "wipe data/factory reset" and after that "wipe dalvik cache", now go to the "storage menu" and select "format /system". Then proceed to the "nandroid menu", select "restore" to select your backup. Remember to reflash the kernel if you had one that didn't come with the ROM (like _motley's for example).
.
Click to expand...
Click to collapse
Hello All,
Maybe a stupid question but, I did not find any clear answer to my question.
I have taken a backup with NANDROID and got the backup into the folder clockworkmod as told in the instruction. Now as I Understand this does not include the ROM or does it?
Also the Restoring stock recovery, how does that work, I put the "recovery.img.md5" file into Odin and flash, but from where does the stock firmware come? Most probably it's not in the 4MB "recovery.img.md5" Do I need to prepare something before using this or does it work without any preparation?
Does it also erase Overcome CWM Recovery that I installer earlier?, It did not say anywhere in the post if I need to have Root permissions to use this?
---------- Post added at 08:35 PM ---------- Previous post was at 08:30 PM ----------
taiger78 said:
Hello All,
Maybe a stupid question but, I did not find any clear answer to my question.
I have taken a backup with NANDROID and got the backup into the folder clockworkmod as told in the instruction. Now as I Understand this does not include the ROM or does it?
Also the Restoring stock recovery, how does that work, I put the "recovery.img.md5" file into Odin and flash, but from where does the stock firmware come? Most probably it's not in the 4MB "recovery.img.md5" Do I need to prepare something before using this or does it work without any preparation?
Does it also erase Overcome CWM Recovery that I installer earlier?, It did not say anywhere in the post if I need to have Root permissions to use this?
Click to expand...
Click to collapse
Hmm, for some reason I did not see page 2 before posting my questions, Got answers to most already, Only the Restoring stock recovery question left, how doest it really work?

taiger78 said:
Hello All,
Maybe a stupid question but, I did not find any clear answer to my question.
I have taken a backup with NANDROID and got the backup into the folder clockworkmod as told in the instruction. Now as I Understand this does not include the ROM or does it?
Also the Restoring stock recovery, how does that work, I put the "recovery.img.md5" file into Odin and flash, but from where does the stock firmware come? Most probably it's not in the 4MB "recovery.img.md5" Do I need to prepare something before using this or does it work without any preparation?
Does it also erase Overcome CWM Recovery that I installer earlier?, It did not say anywhere in the post if I need to have Root permissions to use this?
Hmm, for some reason I did not see page 2 before posting my questions, Got answers to most already, Only the Restoring stock recovery question left, how doest it really work?
Click to expand...
Click to collapse
A Nandroid, as stated in the guide (FAQ section), is an exact copy of the ROM you were using with all its settings and apps you had. For the Stock Recovery, you just need the file you mentioned, and as stated in the guide, use ODIN and put the file into the PDA section. Yes, it overwrites the CWM Recovery, and no, Root is a process inside the ROM (once your device boots into it), it doesn't have any effect in Bootloader Mode.

Okay, don't know if it's me that is just stupid or what the problem is. I have tried to root my device and it does not seam to work as I'm not able to install any new kernel. Picture attached of when I try to install root.zip
It complains about: "Can't access to '/system/csc/NEE/system/'.
I have successfully installed Android 3.2 (http://forum.xda-developers.com/showthread.php?t=1410887) At least in About it says that I'm running Android 3.2. From new it was running 3.1

taiger78 said:
It complains about: "Can't access to '/system/csc/NEE/system/'.
Click to expand...
Click to collapse
This error doesn't have anything to do with root or kernel. It is just trying to set your CSC and fails because the folder is not there. It happens if you flash firmware that is not intended for your region, it doesn't effect anything else, so don't worry about that.

poisike said:
This error doesn't have anything to do with root or kernel. It is just trying to set your CSC and fails because the folder is not there. It happens if you flash firmware that is not intended for your region, it doesn't effect anything else, so don't worry about that.
Click to expand...
Click to collapse
+1 Okay, thank you for your answer, the firmware I flashed, included all European languages that's why I used it.
Anyhow any ides to why I can't install a custom kernel after I have installed the Root.zip file? I get following screen when installing:
But after rebooting I still have the original kernel from flashing 3.2

taiger78 said:
Anyhow any ides to why I can't install a custom kernel after I have installed the Root.zip file? I get following screen when installing:
But after rebooting I still have the original kernel from flashing 3.2
Click to expand...
Click to collapse
Okay got it now, problem was that "Overcome_CWM_Recovery_v5.1.2.6_P73xx" had been removed when installing HC 3.2

taiger78 said:
+1 Okay, thank you for your answer, the firmware I flashed, included all European languages that's why I used it.
Anyhow any ides to why I can't install a custom kernel after I have installed the Root.zip file? I get following screen when installing:
But after rebooting I still have the original kernel from flashing 3.2
Click to expand...
Click to collapse
The picture you posted shows stock recovery and you can't flash a kernel with stock recovery.
You need to install CWM recovery and then you can flash the kernel from there. I'm using CWM recovery from there http://forum.xda-developers.com/showthread.php?t=1321142
I used the Overcome_CWM_Recovery_v5.1.2.6_P73xx.zip and flashed it using stock recovery.
If you know how to use Odin then you can download the Overcome_CWM_Recovery_v5.1.2.6_P73xx.tar and flash it using Odin.
It doesn't matter which you use, the end result is the same. Only flashing method is different.
When you have CWM recovery installed, then you can boot to CWM recovery and flash the kernel from there.
If you at any time flash stock rom back using Odin, then it will overwrite all, including the recovery. So you have to start all over.

I registered to say THANKS!!
I'm fairly new at this, and did something rather stupid this morning.
Thought my tab was hosed, but following the excellent instructions provided here I was able to recover it, what a relief...
It was actually a pretty good learning experience, although a bit traumatic.

[Q] Help me to fix “NULL NULL” after N7000DDLA5

I update to N7000DDLA5, but after that when I type any key from keyboard showing “NULL NULL”.
I found some fix from XDA, by flashing “CSC” file by mobile odin. But from where I will get that CSC file, I have only single N7000DDLA5…..TAR.MD5 file only.
Advise please…

i extract TAR.MD5 with WINRAR. then flash with Mobile odin > Cache > Internal SD-Card > Cache.img
but after restart i am getting below message and issue still persist. please help me....
# MANUAL MODE #
--Updating application..
Successfully updated application.
--Appling Multi-CSC…
Installing Multi-CSC
Can’t access to ‘/system/csc/XSG/system/’.
Successfully applied multi-CSC.

I faced the same problem. Use the latest version of Mobile Odin to flash the whole thing again, you'll be fine. You can also use the CWM app to flash this.
1. If you have an extra memory card, use it. Make a folder named 'firmware' (without quotes) and put your tar.md5 file in it.
2. In the CWM app, select 'flash stock firmware'.
3. Select continue>keep CF Root kernel.
If you don't happen to have an extra memory card,create a folder named 'external_sd' at the root of your internal storage (/sdcard/external_sd/firmware/blahblah.tar.md5).
I must tell you, this has never worked for me though, and I've always managed to miss the error message thrown up by the recovery, so I can't tell you why

I got this error when updating to la4, not sure what the issue is but I don't use the samsung keybaord anyway I use smart keyboard and the issue doesn't happen with this keyboard, so I'm not t bothered about it

Flash stock firmware method stated above

bloodyhippo said:
I faced the same problem. Use the latest version of Mobile Odin to flash the whole thing again, you'll be fine. You can also use the CWM app to flash this.
1. If you have an extra memory card, use it. Make a folder named 'firmware' (without quotes) and put your tar.md5 file in it.
2. In the CWM app, select 'flash stock firmware'.
3. Select continue>keep CF Root kernel.
If you don't happen to have an extra memory card,create a folder named 'external_sd' at the root of your internal storage (/sdcard/external_sd/firmware/blahblah.tar.md5).
I must tell you, this has never worked for me though, and I've always managed to miss the error message thrown up by the recovery, so I can't tell you why
Click to expand...
Click to collapse
Bloodyhippo, issue resolved, I follow your steps.
1. Update Mobile ODIN pro (v2.15)
2. re-flash same firmware (N7000DDLA5) whole again.
3. after restart, Samsung keyboard issue resolved. Done!
Many thanks guys.

musheercmr said:
Bloodyhippo, issue resolved, I follow your steps.
1. Update Mobile ODIN pro (v2.15)
2. re-flash same firmware (N7000DDLA5) whole again.
3. after restart, Samsung keyboard issue resolved. Done!
Many thanks guys.
Click to expand...
Click to collapse
Thats what I was going to say. Glad you got it

thnxxxxxxxxxxxx 4 this useful tip

null keyboard characters after rooting my Samsung Galaxy Note
I just got my samsung galaxy note (SGN) and rooted it following the instructions on this page (very good - worked great)
http://forum.xda-developers.com/showthread.php?t=1331784
When the SGN booted it was rooted but the built in samsung keyboard would display null no matter what key i hit.
I did not have mobil odin installed nor could i install it without using my keyboard and i did not want to re-flash a kernel or any other drastic measures... so to fix this easily i went into the android market now (google play store) and then tapped CATEGORIES then TOOLS then TOP FREE and scrolled down to GO Keyboard (i am sure any free keyboard will work - this is just the first one i found) and installed it.
This resolved the Samsung keyboard problem and i can now type normally so i can upgrade to new ROM's etc...
-Mitch SGN / CF-ROOT / CWM / android 2.3.5 / baseband LA4 / kernel KJ1

hi guys
i m new to this site
this small tutorial is when ur restoring ur rooted or normal stock firmware with any other firmwares or unrooting and restoring to stock firmware.
btw its very simple when u update firmware over odin use the latest version and don't forget to check USB debuggin start update process.......
it takes some time.
when ur device is working it will be null null null .........
go to recovery mode wipe factory reset first then wipe partition...
when ur finished with above steps
go to downloading mode and repeat the update of firmware procedure from ODIN again ...
ur phone will be without any errors (for ex: no null in keyboard wen u type
and will be able to update from ur current firmware if updates are available ...
any doubts please feel free to ask thank you.

flash it via pc odin
i flashed it via mobile odin and got the null error too

bloodyhippo said:
If you don't happen to have an extra memory card,create a folder named 'external_sd' at the root of your internal storage (/sdcard/external_sd/firmware/blahblah.tar.md5).
Click to expand...
Click to collapse
I dont have the firmware in "md5" format, but in "TAR", will that work?

How-To: Samsung Allshare Cast dongle with custom N7100 ROM

Hey guys,
I was having serious issues getting my Allshare Cast dongle to work with my rooted Note 2 (N7100). It either broke off the connection because of the flash counter or (even worse), when I ran TriangleAway beforehand, always rebootet my phone.
I've dug through countless threads addressing this issue and offering all kinds of different until I was finally able to make it work - still being rooted and using a custom rom. So I thought I'd just share my solution with anybody here who may find it useful.
*Edit*
Seems like Allshare Cast still tends to be a bit picky. The first connection is stable, but a second one reboots my phone after a few minutes. Quite annoying, but at least it works.
As usual, I will not be held responsible for any damage that might occur, so don't blame me if your phone blows up itself, or your house. :angel:
This works *for me*, other phones might yield other results.
These are step-by-step instructions if you're coming either from a f%*'ed up ROM that needs major repairs anyway (like me), or from a different android version. If you're running a 4.1.2 ROM you can try to jump directly to step 2. c). Still, I'd suggest you backup everything, see below 2. a)
Here we go:
1. Things you'll need:
a) Wanamlite 3.9 (http://wanamlite.com/2013/07/19/wanamlite-mg1-v3-9-android-4-1-2-clean-stable/) by Wanam (who saved me from ruining my phone btw: tried Wanamlite 4.2 with new bootloader, and without his warning, I would've used the MK4 bootloader instead of MJ5 and would've been stuck with Android 4.3/Know forever...)
b) Adam Kernel v2.7, Odin and/or CWM version (http://wanamlite.com/2013/07/19/adam-kernel-v2-7/) by Wanam
c) Stock recovery, kernel, etc. (http://forum.xda-developers.com/showpost.php?p=31986738&postcount=7), provided by dr. ketan. I'm using this one: http://d-h.st/gwn (Stock Recovery/Kernel/Modem from XXDMB6 19th March13)
d) Mobile Odin (http://forum.xda-developers.com/showthread.php?t=1347899) by Chainfire
along with the FlashKernel file (MobileODIN_FlashKernel_N7100-v5.0.apk) further down on the same page. if v5.0 doesn't work, try v4.0 instead.
e) TriangleAway (http://forum.xda-developers.com/showthread.php?t=1494114) by Chainfire
f) I'm assuming you're already rooted and therefore have a working CWM/TWRM running.
2. What to do (step-by-step):
a) I'm being a bit paranoid by now, but for various good reasons. These instructions may be a bit overcautious, but at least your data will be safe from being accidentally erased. Trust me, you do not want that ever to happen... :crying:
Also, I always carry a ROM with me so I can repair my phone on the go. So of course, you can also do the flashing via PC Odin, but I prefer the CWM method I've described further down.
- backup everything. And I mean EVERYTHING! I did a full backup, i.e. Titanium Backup, TWRP backup, and I copied the whole contents of my internal and external SD cards to my PC. I'd even suggest you use another extSd during this process (which will save you from the hassle of copying the whole thing btw). This whole backup thing took me about 2-3 hours, but I would've gone mad if I'd lost either internal or external SD data.
- copy Wanamlite 3.9 onto the external SD your're going to use.
- power off your phone (take out the battery to be sure)
- take out your external sd to protect all your precious data. Just in case you accidentally do something wrong and end up formatting the extSd (in TWRM, this option hovers dangerously between "Factory Reset" and "Format Data")
- boot into recovery and do a full wipe (Wipe Cache / Wipe Dalvik Cache / Factory Reset / Format Data)
- power off your phone (take out the battery to be sure), re-insert the external SD
- boot into recovery and flash Wanamlite 3.9 (follow the instructions on his site). Be sure to chose Adam Kernel and checke "Allshare Cast" during the installation process. The Adam Kernel works best with TriangleAway, because (unlike the stock kernel provided with his ROM) you can reset the flash counter without rebooting.
Now you have an absolutely clean 4.1.2 rooted custom ROM running on your phone.
b) Restore your data.
- run Titanium Backup, and restore everything that's important (all user apps w/ data, call logs, messages, email etc.). I'd suggest you just leave out system apps if you're coming from another ROM. You can try to restore everything of course, worst thing to happen is that you'll habe to re-wipe and then re-flash the ROM. In my case, it was no problem, because I had made my backup from this very ROM version.
- Next, copy at least the "Android" folder (containing /data and /obb) from your backup back to your internal SD card. By default, TB doesn't backup large files and folders, so all the bigger apps (like e.g. games) are still missing. If asked to overwrite, simply say "yes". If you want to make sure everything's back to how it was before, copy your whole internal SD backup back to your phone.
c) You've spent an awful lot of time by now, and still, Allshare Cast won't work. So let's go for it:
- install Mobile Odin and the appropriate Flashkernel.apk
- install TriangleAway
- unpack and then copy the contents of "Stock Recovery/Kernel/Modem from XXDMB6 19th March13" to your internal or external SD card (doesn't matter which one).
- run TriangleAway. It should read "Counter: 1 /Binary: Custom".
- tap "Reset flash counter". TriangleAway confirms that the counter was reset to 0 and closes.
- restart the app. Now you should see "Counter:0 / Binary: Official".
- run Mobile Odin, chose the stock kernel (tap "Kernel" -> "[path where you stored the kernel.tar from the archive]")
- tap "Flash Firmware". Your phone will reboot.
Congratulations! If you did everything correctly, you should now be running Wanamlite 3.9 (JB 4.1.2) ROM with rooted stock kernel. Allshare Cast works like it should. FIFA14 or DIII4A are really fun on a 40" screen.
If you don't want to use the stock kernel all the time, flash Adam Kernel v2.7 through Mobile Odin or CWM. Allshare Cast functionality will be broken, but you have all the nice benefits of the custom kernel like STweaks or BoefflaSound. To make Allshare Cast work again, simply repeat the last five steps from above: "c) - run TriangleAway... etc."
That's it. I hope this is helpful! Suggestions are welcome. If something's missing, or if I posted anything dangerous, please feel free to scream, and I'll correct it ASAP.
Cheers,
- Alex

Thanks for the nice review. I have these and wholeheartedly recommend them as well.

does anyone know how to update Allshare Dongle via N7100?
I've had many ROMs and on every single one I have message that update was downloaded and to restart the dongle, but after I restart the dongle it connects again with the same message, so it is infinite loop. I can connect, but sometimes it laggs, so I assume that newer firmware would fix that issue.
I've even contacted Samsung's support service and they couldn't help me. They told me to wait for update, but even on the newest stock it is still the same.
If anyone knows the solution please share.

thanks
thanks for the review its really helpful