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 ?
Related
Hi
Clockwork Recovery v 4.0.0.2 for Galaxy Ace
v2:
- working nandroid backup/restore!
For now i've disabled backup/restore of boot and recovery partitions. Restore of DATA, CACHE and SYSTEM is working fine.
If you have JTAG and want to test restore of boot/recovery please PM me!.
- it's based on KPH firmware + root in adb (both in normal and recovery mode)
v1:
Tested:
- wipe Data/Factory reset
- wipe cache partition
- some options under advanced menu (to wipe)
- install zip from SDCard (tested on some file from UOT kitchen)
- reboot recovery
- mount USB storage (and other mount options) Better not try to format partitions from recovery yet - it could format them to ext4 for which we probably not have yet support in kernel.
Know bugs:
- poweroff sems to reboot phone
- problem with graphics (probably framebuffer is set to 24 or 32 bpp mode. There is also missing double buffer support in framebuffer - thats why we have 2 recovery screens). It'll be fixed - thanks to tj_style!!
Remember, I am not reponsible if you brick your phone. You're flashing this on your own risk.Not all options are tested!!!.
How to flash (v2):
1. Download file from here .
2. flash it as PDA with odin
Mirrors:
Multiupload (thanks to peeter123)
I've removed recovery.zip - it was recovery.img packed with zip, not update for apply using stock recovery.
To move in recovery:
- Volume up/down to move.
- Home (center key) to select item.
- Back to move back.
Where did you get this?
Lovetz said:
Where did you get this?
Click to expand...
Click to collapse
I've build it from source using this tutorial Porting clockwork recovery to new device, with some changes. Then i've mixed recovery.img with those from samsung firmware.
PabloPL said:
I've build it from source using this tutorial Porting clockwork recovery to new device, with some changes. Then i've mixed recovery.img with those from samsung firmware.
Click to expand...
Click to collapse
You are elite, dude!;-) (Hackers)
This opens so many oppertunites to our Ace CyanogenMod being one of them. Have you got any further with these bugs? This is great. Thank you
Sent from my GT-S5830 using XDA App
awesome work!!!....it would be legendary if NANDROID backup works!!!!NO more bricking worries!!!
I've successfully to porting the Clockworkmod Recovery too for Galaxy mini.
The problem with framebuffer it's been fixed too.
I just have the problem with backup & restore, also with flashing full rom from zip.
Are you get success with backup and restore?
since galaxy ace / mini is using different tool for read / write the bml partition. not like SGS that can using redbend_ua
PabloPL said:
Hi
Today i managed to run the newest Clockwork Recovery on my Galaxy Ace. It has some problem with graphics (as you can see on screenshots).
I've tested following options (and for me they are working):
- wipe Data/Factory reset
- wipe cache partition
- some options under advanced menu (to wipe)
- install zip from SDCard (tested on some file from UOT kitchen)
- reboot recovery
- mount USB storage (and other mount options) Better not try to format partitions from recovery yet - it could format them to ext4 for which we probably not have yet support in kernel.
Know bugs:
- poweroff sems to reboot phone
- problem with graphics (probably framebuffer is set to 24 or 32 bpp mode. There is also missing double buffer support in framebuffer - thats why we have 2 recovery screens)
I've also managed to create nandroid backup of all partitions (boot,recovery,data and system) but not tried yet to restore them.
Phone info
In recovery mode (sorry for terrible image quality)
I've attached packed recovery.img. it's based on KPH firmware + root in adb (in both boot and recovery mode) + su binary.
Remember, I am not reponsible if you brick your phone. You're flashing this on your own risk.Not all options are tested.
How to flash:
1. take KPH firmware
2. extract CODE_S5830XXKPH_CL260130_REV03_user_low_true.tar.md5
- tar xvf CODE_S5830XXKPH_CL260130_REV03_user_low_true.tar.md5
3. replace recovery.img with attached file
4. pack it back
- tar -H ustar -c boot.img recovery.img data.rfs system.rfs >ODIN_FILE.tar
- md5sum -t ODIN_FILE.tar >>ODIN_FILE.tar
- mv ODIN_FILE.tar ODIN_FILE.tar.md5
5. flash it with odin
To move in recovery:
- Volume up/down to move.
- Home (center key) to select item.
- Back to move back.
Click to expand...
Click to collapse
GREAT JOB MAN!
Go ahead, you are on it!!!
CHEERS!
The main thing is to get the install update zip feature as that really is the reason we use ClockworkMod and what we wanted it for.
Sent from my GT-S5830 using XDA App
kills999 said:
awesome work!!!....it would be legendary if NANDROID backup works!!!!NO more bricking worries!!!
Click to expand...
Click to collapse
For now i've tested it only with creating backup of boot/recovery/data/system partitions and it generated without errors.
Jekle_Ace said:
The main thing is to get the install update zip feature as that really is the reason we use ClockworkMod and what we wanted it for.
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
I've tested installing update from zip on some theme from OUT Kitchen and it worked fine
PabloPL said:
I've tested installing update from zip on some theme from OUT Kitchen and it worked fine
Click to expand...
Click to collapse
Can you upload ready-to-flash KPH file with CWM integrated?
Wiping partitions /system /data etc is very important without wiping it can cause many problems as I've done that many times with my ZTE Blade. But still I appriciate this greatly
Sent from my GT-S5830 using XDA App
tj_style said:
I've successfully to porting the Clockworkmod Recovery too for Galaxy mini.
The problem with framebuffer it's been fixed too.
View attachment 623281
I just have the problem with backup & restore, also with flashing full rom from zip.
Are you get success with backup and restore?
since galaxy ace / mini is using different tool for read / write the bml partition. not like SGS that can using redbend_ua
Click to expand...
Click to collapse
Could You share what changed did you made to fix framebuffer problems ?? For now i've made some change found here to get 2 screens in recovery (was getting 4 before).
About backup, like i wrote, tested only creating. I have to set up correct size of all partitions in BoardConfig etc, Ace is my primary phone, so i don't want to brick it.
I've made some changes to recovery source (look into bmlutils/bmlutils.c - there are hardcoded paths to boot and recovery partitions, which on Ace are differend than those in code).
I've also used custom recovery_ui.c with custom key mapping.
Lovetz said:
Can you upload ready-to-flash KPH file with CWM integrated?
Click to expand...
Click to collapse
I have PDA file for odin with it, but i've messed something with Superuser.apk and you must install it by hand (only Superuser.apk, su binnaries are fine). Maybe when i'll have some free time - i'm working and studying (now have exams) - i'll upload it, if someone won't do this before .
Jekle_Ace said:
Wiping partitions /system /data etc is very important without wiping it can cause many problems as I've done that many times with my ZTE Blade. But still I appriciate this greatly
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
For now i've tested wipe only on following options (and it worked fine):
- battery stats
- cache
- data (factory reset)
Sorry for double-postings
PabloPL said:
Could You share what changed did you made to fix framebuffer problems ?? For now i've made some change found here to get 2 screens in recovery (was getting 4 before).
About backup, like i wrote, tested only creating. I have to set up correct size of all partitions in BoardConfig etc, Ace is my primary phone, so i don't want to brick it.
I've made some changes to recovery source (look into bmlutils/bmlutils.c - there are hardcoded paths to boot and recovery partitions, which on Ace are differend than those in code).
I've also used custom recovery_ui.c with custom key mapping.
Click to expand...
Click to collapse
Sure, You can see on my github soon. I'm not yet pushing to my github now.
because the project of Cyanogenmod port and Clockworkmod port for Galaxy Mini is pending now until i have the Galaxy mini back, you can see the progress in this thread.
I've add the double buffering to clockworkmod source, since Galaxy mini kernel doesn't suppot that.
I hope we can colaborate to make clockworkmod is fully working, because the Galaxy Mini, Ace, Gio and Fit is using similiar environtment.
thx dude, i really need this.
tj_style said:
I hope we can colaborate to make clockworkmod is fully working, because the Galaxy Mini, Ace, Gio and Fit is using similiar environtment.
Click to expand...
Click to collapse
It would be nice. As i see You have far more progress.
In my opinion it would be better to make it with only minimal changes (or even without) to android source (recovery etc), to keep it in synch with "mainline". Closer we keep(and less changes), longer we could have support.
Also getting rid of BML and use MTD (when we have sources for 2.3.4) would be great.
PabloPL said:
It would be nice. As i see You have far more progress.
In my opinion it would be better to make it with only minimal changes (or even without) to android source (recovery etc), to keep it in synch with "mainline". Closer we keep(and less changes), longer we could have support.
Also getting rid of BML and use MTD (when we have sources for 2.3.4) would be great.
Click to expand...
Click to collapse
Yup, i'm waiting to someone borrowing the galaxy mini to me and also waiting samsung to get released the 2.6.35.7 kernel source.
The source will come after 2.3 is offically released but we may be waiting a few weeks for it
Sent from my GT-S5830 using XDA App
Great work mate. Maybe you can work together with nprussel who is also trying to run cwm on g ace
@formatting partitions, there is indeed no support for ext4 in kernel
Sent from my GT-S5830 using XDA App
UNIVERSAL GINGERBREAD ROOT SAMSUNG GALAXY MODELS: GT-S5570, GT-S5570B, GT-S5570I, GT-S5570L, GT-S5571, GT-S5578 (Chinese Mini), GT-S5660, GT-S5660M, GT-S5660L, GT-S5660V, SHW-M290K (Korean Gio), GT-S5670, GT-S5670B, GT-S5670L, GT-S5830, GT-S5830B, GT-S5830C, GT-S5830D, GT-S5830F(La Fleur), GT-S5830i, GT-S5830L, GT-S5830M, GT-S5830T, GT-S5830V(new), GT-S5830Z, GT-S5839i, GT-S6802, GT-B5330, GT-B7510, GT-B7510B, GT-B7510L, GT-B7800, GT-B5510, GT-B5510B, GT-B5510L, GT-B5512, GT-B5512B, GT-S6102, GT-S6102B, GT-S5300, GT-S5300B, GT-S5302, GT-S5360, GT-S5360B, GT-S5360L, GT-S5360T, GT-S5363, GT-S5369, GT-S5690, GT-S5690M, GT-S5690L, GT-I8150, GT-I8150B, GT-I5510, GT-I5510B, GT-I5510L, GT-I5510M, GT-I5510T, SCH-i509, SGH-T499(new), SGH-T589(new), SGH-T589R(new), SGH-I827(new), SGH-I837(new), SGH-I857(new).
DISCLAIMER: ---You will have sucessfully rooted Samsung phone only for the models that are mentioned above. Any other phone model is incompatible at the present time. Phone models like GT-S6500, GT-S7500, GT-I9000 have a diferent structure from diferent point of view. Diferent certificate pass key to the signed zip files, diferent update binary in the zip file and so on. If anything new comes out you will be informed untill then it is strictly on the models that are presented.---
This is only for the people that they are using Gingerbread and can't root their phone with SuperOneClick. You can root your phone with universal_gb_root_v24.zip file for your phone model.
Question: How do I Root Gingerbread on my phone?
Answer:
- First enable Unknown sources on your phone (Settings -> Applications -> Unknown sources)
- Download the universal_gb_root_v24.zip file and put in your SD card.
* How do I transfer universal_gb_root_v24.zip on my SD card?
(You can tranfer the universal_gb_root_v24.zip to your phone via Wifi, Bluetooth, SD micro Adapter or USB cable. To transfer it via USB cable you need first to download KIES from the offical Samsung Web Site and after installing restart your PC so the USB drivers can be recognized properly.Enable USB debugging on your phone, Settings -> Applications -> Development -> USB debugging. Plug in the USB cable and enable the connection on you mobile phone like the picture in the bottom. After couple of seconds your SD card will be showed on your PC like Removable disk. Copy universal_gb_root_v24.zip to your SD card.)
{
"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"
}
- After transferring your file on your phone disable the USB by pressing "Disconnect storage from PC" after that remove the USB cable and turn off your phone "Power off".
Entering recovery mode on Samsung Galaxy: (Young CDMA SCH-i509 and Chinese Version CDMA SCH-i509)
- Make shure you start the phone like this : Long press and hold the (Volume up Button) + (Power Button)
Entering recovery mode on Samsung Galaxy: (551 GT-i5510/B/L/M/T) (Pro GT-B7510)
- Make shure you start the phone like this : Long press and hold the (T Button) + (Power Button)
Entering recovery mode on Samsung Galaxy: (Ace GT-S5830/B/C/D/L/M/T) (Gio GT-S5660/M/L/V) (Fit GT-S5670/B/L) (Mini GT-S5770/B/L, GT-S5771)
- Make shure you start the phone like this : Long press and hold the (Power Button) + (Home Button)
Entering recovery mode on Samsung Galaxy : (Ace GT-S5830i) (Mini GT-S5570I) (W GT-I8150/B) (Xcover GT-S5690/M/L) (Young GT-S5360/B/L/T, GT-S5363, GT-S5369) (Y-Duos GT-S6102/B) (Y-Pro GT-B5510/B/L) (Y-Pro Duos GT-B5512/B) (M-Pro GT-B7800) (Pocket GT-S5300/B)
- Make shure you start the phone like this :
Method 1:
Long press and hold the (Volume up Button) + (Home Button) + (Power button)
* If for some reason with Method 1 the phone reboot always when entering recovery mode (depends on the models) please use the Method 2 option
Method 2:
Long press and hold the (Volume up Button) + (Home Button) + (Power button) when you see the samsung logo for the second time release (Home Button) and press again the (Home Button) and after that release the (Power button)
- After couple of seconds you will see your phone booting in recovery mode
- Move in the menu with the Volume - Volume + to scroll up and down and choose "apply update from sdcard" with the Home button and choose the universal_gb_root_v24.zip and press once again the Home button to apply it.
- You will see a message "Install form sdcard complete".
- Then press on the "reboot system now"
- When you open SuperSU it will ask you to upgrade the SU binary just press continue your phone will reboot once and you are done!
Download link for Universal Gingerbread Root (by StoneBoyTony) :
universal_gb_root_v24.zip
What's new in this version:
- SuperSU Application v0.94 (new)
- SuperSU binary v0.93 (new)
- Root Validator
- BusyBox binary v1.20.2 (new)
- New signed release key of the zip files for better compatibility on the phone models (new)
IMPORTANT: Root and Unroot method is designed to work in recovery mode on Stock ROM's. CWM Recovery and Custom ROM's are not supported! And never try to unroot your phone when you are using Custom rom!
FAQ
AFTER ROOTING I SEE ONLY ROOT VALIDATOR BUT NOT THE SUPERSU APPLICATION?
As some people reported there is sometimes problem with the rooting procedure files can't be extracted properly (applications,binaries) so from today (04.08.2012) in every new update there will be an extra second alternative root zip file recognized with the letter "b" in the end of the version number. As always in life we must have a B PLAN. In this root zip file package it will be only the SuperSu application and the supersu binary, no Busybox, Rootvalidator or anything else. So if the rooting procedure from above didn't work for you then you should run again in recovery mode the universal_gb_unroot_v8.zip to delete all the half extracted files from the root procedure previously done. After that you can apply universal_gb_root_v24b.zip known as Root Only.
IMPORTANT: If for some reason after rooting with the universal_gb_root_v24b.zip want to install Busybox then when you open the application it will give you a location to install busybox to /system/bin (this is for the reason becouse there is no busybox binary in this root zip file) you just need to simply relocate the installation to /system/xbin (to relocate the path simply press on the text /system/bin it will open a new window and change it to /system/xbin) . This is for a reason becouse in the future you might want to remove busybox and many times happend that it can't be uninstalled properly leaving all the applets in bin folder mixing the files with the system files from your Android OS. Then you need to install root explorer and delete all the applets manualy and trust me is a painful job. So the problem it will be solved very quickly by installing in /system/xbin. if you don't like it to have anymore later just use the procedure for unroot (READ: HOW CAN I UNROOT MY PHONE?) universal_gb_unroot_v8.zip it will delete all the remaining stuff from busybox in /system/xbin and use again the universal_gb_root_v24b.zip to root.
Download link for Universal Gingerbread Root ONLY (by StoneBoyTony) : universal_gb_root_v24b.zip
THERE IS NO SU BINARY AFTER ROOT?
From today (02.04.2012) I can proudly present the third update zip universal_gb_c.c.b.s.f_v7.zip. C.C.B.S.F stand for "Cleanup Carrier Branded System Files" What makes this package very interesting is allowing you to cleanup your System files (applications) from your branded carrier provider such as Shops, Music, Web Launchers, Widgets...Games: Tetris,Sims3 etc ...making free space in the system partition ROM (not internal memory) so later the root installation can take place and have a sucessfully rooted phone. This package will clean up most of the carrier providers like:
What's new in this version:
Added Carrier Network Providers:
- 3 (new)
- Aircel (new)
- Airtel
- Asda (new)
- Axis (new)
- Banglalink
- BT Mobile (new)
- Cellone (new)
- Dialog
- Dolphin (new)
- E-Plus
- Etisalat
- Globe
- Grameenphone
- H3G (new)
- Hutch
- IDEA
- Indosat (new)
- IR MCI (new)
- IRANCELL (new)
- Loop Mobile (new)
- M1
- Meteor
- Mobitel
- Movistar
- MTCE (new)
- NCELL
- NepalTelecom
- O2
- Optus
- Orange
- Poland Plus
- Reliance (new)
- Robi
- SFR
- STEL (new)
- Taliya (new)
- Talkmobile (new)
- TataDOCOMO (new)
- Telcel
- Teletalk
- Telkomsel (new)
- TelstraOne
- TESCO (new)
- TKC (new)
- T-Mobile
- tuenti
- Uninor (new)
- Videocon (new)
- Virgin
- Vodafone
- XL (new)
- New signed release key of the zip files for better compatibility on the phone models (new)
IMPORTANT: The universal_gb_c.c.b.s.f_v7.zip can be applyed in recovery like the rest of the zip files for root and unroot. It will delete all Carrier Branded System Files (Applications) without to interfere with the system files of Samsung Stock ROM's all functions will work normaly only the applications from the carrier branded apps will be deleted. In order to bring them back you need to unroot your phone and make a Factory Reset and all will be back as usual. This zip file should be only applyed if you have Carrier Provider Phone (like the above list already mentioned) and can't root the phone becouse of the carrier apps making a full capacity of the Android OS (system partition).
Download link for C.C.B.S.F (by StoneBoyTony) : universal_gb_c.c.b.s.f_v7.zip
I HAVE TRY ALL THE ABOVE METHODS NOTHING IS WORKING?
Chapter I
-Removing Quickoffice-
Well some Stock Firmwares have been made that in the system partition you can not even copy via recovery a single file. So my task search begin and finaly I found the bug to solve the problem. In many Stock Firmwares they put Quickoffice application, this stock firmwares in some cases are very problematic to make root on them. So finaly here is the solution and very simple to make a free space for rooting. Apply in recovery the universal_gb_remove_quickoffice.zip and then you can use the universal_gb_root_v24b.zip to finaly root your phone. So Quickoffice will be deleted from your system partition but you can always install the Quickoffice.apk whenever you want and it will be installed on your SD card (you can have the rooted phone and using again the Quickoffice). If for some reason you need to take your phone to the samsung service center problem with hardware,software or anything like that you can reverse the process to install Quickoffice back to the system partition (if you have installed the Quickoffice.apk uninstall it first from the Task Maneger)using first the universal_gb_unroot_v8.zip to unroot and after that use the universal_gb_install_quickoffice.zip to install Qucikoffice back to your system partition and all will be back as normal.
Download link to Remove Quickoffice (by StoneBoyTony): universal_gb_remove_quickoffice.zip
Download link to install Quickoffice application: Quickoffice.apk
Download link to install Quickoffice back on your system partition (by StoneBoyTony): universal_gb_install_quickoffice.zip
Chapter II
-Removing Thinkfree Office-
Same as Chapter I in many Stock Firmwares we find the application Thinkfree Office, this stock firmwares in some cases are very problematic to make root on them. The solution is very simple we just need to make a free space for rooting in your system partition and remove Thinkfree Office. Apply in recovery the universal_gb_remove_thinkfreeoffice.zip and then you can use the universal_gb_root_v24b.zip to finaly root your phone. Thinkfree Office will be deleted from your system partition but you can always install the ThinkfreeOffice.apk whenever you want and it will be installed in your internal memory (you can have the rooted phone and using again the Thinkfree Office). If for some reason you need to take your phone to the samsung service center problem with hardware,software or anything like that you can reverse the process to install Thinkfree Office back to the system partition (if you have installed the ThinkfreeOffice.apk uninstall it first from the Task Maneger) using first the universal_gb_unroot_v8.zip to unroot and after that use the universal_gb_install_thinkfreeoffice.zip to install Thinkfree Office back to your system partition and all will be back as normal.
Download link to Remove Thinkfree Office (by StoneBoyTony): universal_gb_remove_thinkfreeoffice.zip
Download link to install Thinkfree Office application: ThinkfreeOffice.apk
Download link to install Thinkfree Office back to your system partition (by StoneBoyTony): universal_gb_install_thinkfreeoffice.zip
HOW CAN I REMOVE ROOT VALIDATOR I DON'T NEED IT ANYMORE?
- You need to open SuperSu application and under "Apps" press the icon or the text for RootValidator. A new window will open and press "Forget". Power off your phone and enter in recovery mode to apply universal_gb_remove_validator_v3.zip file.
Download link for Remover of RootValidator (by StoneBoyTony) : universal_gb_remove_validator_v3.zip
HOW CAN I UNROOT MY PHONE?
- First thing you need to remove all the applications that they are depended from root, after that open SuperSU -> Settings -> Full Unroot and press Continue. Your phone will reboot once and after that enter Recovery mode and use the universal_gb_unroot_v8.zip to delete all the traces remaining. If you were having Superuser app (the older one) just get in the Recovery mode and then apply the universal_gb_unroot_v8.zip
You can download the UNROOT (by StoneBoyTony) from here: universal_gb_unroot_v8.zip
What's new in this version:
- Deleting all traces of Superuser
- Deleting all traces of Suhax
- Deleting all traces of Busybox and Busyboxpro (and all applets created in xbin that they are symlinked causing sometimes Busybox to fail of uninstalling them so that problem is solved i add them all to be deleted and for the leatest version 1.20.2. )
- Deleting all traces of Superoneclick
- Deleting all traces of SuperSU and SuperSU Pro
- Deleting Root Validator
- New signed release key of the zip files for better compatibility on the phone models (new)
*NOTE* - FOR ALREADY ROOTED PHONES WITH SUPERUSER
For those who already have root with Superuser or any other kind of root method and want to update your root with the new SuperSU package you need first uninstall all app that they are depended from root then apply in recovery mode the universal_gb_unroot_v8.zip and enter again in recovery mode to apply the universal_gb_root_v24.zip or you can use Only Root universal_gb_root_v24b.zip .
This is how it looks rooted phone you will have application SuperSU
This post is good for noobs lik me. . But a similar post abt apps is already posted in themes and apps section...here --
http://forum.xda-developers.com/showthread.php?t=1569607
JoK€R said:
This post is good for noobs lik me. . But a similar post abt apps is already posted in themes and apps section...here --
http://forum.xda-developers.com/showthread.php?t=1569607
Click to expand...
Click to collapse
The diference is providing root and unroot for more phones that they didn't have any luck untill now.
hello
Newbie here,
Rooting my froyo with a tutorial whitout problems but now i have a new one with
gingerbread 2.3.6
It's a mt 6573 dapeng A7 and no real solution ar found to root.
Will this update zip also works on this device or not or is it just for the samsung bootrom.
I have boot into recovery an made a full backup.
So if i apply this update and it's not work for some reason can i still be enter the recovery mode or not to restore my backup from sdcard or is my phone bricked.
just learning so sorry if there are noob questions because there is no real tutorial for 2.3.6
grts b,
hi op you should know soc support rooting gb from a long time but this method is more easy
---------- Post added at 05:42 PM ---------- Previous post was at 05:36 PM ----------
have you checked it manually I have open the script and found that you have written a command which will format /system
and without how mobile will boot
Samsung Galaxy GT-S7500
Does not work with the s7500.
I got the following:
E: failed to verify whole-file signature
E: signature verification failed
Also downloaded the file again three times and got the same message
dhlalit11 said:
hi op you should know soc support rooting gb from a long time but this method is more easy
---------- Post added at 05:42 PM ---------- Previous post was at 05:36 PM ----------
have you checked it manually I have open the script and found that you have written a command which will format /system
and without how mobile will boot
Click to expand...
Click to collapse
You should know what is the sign before format command is "#" that mean that the command is not in function
sab65 said:
Does not work with the s7500.
I got the following:
E: failed to verify whole-file signature
E: signature verification failed
Also downloaded the file again three times and got the same message
Click to expand...
Click to collapse
Sorry about that it was experimental for Ace Plus removed from the Tutorial.
rcbadboy said:
hello
Newbie here,
Rooting my froyo with a tutorial whitout problems but now i have a new one with
gingerbread 2.3.6
It's a mt 6573 dapeng A7 and no real solution ar found to root.
Will this update zip also works on this device or not or is it just for the samsung bootrom.
I have boot into recovery an made a full backup.
So if i apply this update and it's not work for some reason can i still be enter the recovery mode or not to restore my backup from sdcard or is my phone bricked.
just learning so sorry if there are noob questions because there is no real tutorial for 2.3.6
grts b,
Click to expand...
Click to collapse
My friend you have mixed the pots. This is for Samsung Galaxy phones and nothing to do with Mediatek phones; Need to search for the forum about your phone.
StoneBoyTony said:
My friend you have mixed the pots. This is for Samsung Galaxy phones and nothing to do with Mediatek phones; Need to search for the forum about your phone.
Click to expand...
Click to collapse
hey
ik know this is the samsung sub but because i saw "universal gingerbread" it's maybe works for other phone's also.
But now i think not
i could just try because i have try everything to root my phone to get rid of this unwanted chinese apps.
grts b,
I know adding # before any line will tell system not to read that line but why take risk when we can remove that
StoneBoyTony said:
Sorry about that it was experimental for Ace Plus removed from the Tutorial.
Click to expand...
Click to collapse
Yes it is a pity. Have not been able to find a way to root the Ace Plus. It is very frustrating. This was the closest I got to doing it.
This worked perfect on samsung galaxy mini.
Thank you.
doesnt work on 2.3.4 galaxy ace
Gyku said:
This worked perfect on samsung galaxy mini.
Thank you.
Click to expand...
Click to collapse
Hi,
Certainly doesnt work on a Samsung galaxy ace S5830T on 2.3.4 and GINGERBREAD.DVKQ3.
anyone know what i can root this phone with ??
I tried everything on the web ..no luck.
oldernerd said:
Hi,
Certainly doesnt work on a Samsung galaxy ace S5830T on 2.3.4 and GINGERBREAD.DVKQ3.
anyone know what i can root this phone with ??
I tried everything on the web ..no luck.
Click to expand...
Click to collapse
It not support in script. Just edit update-script and change something to GT-S5830T from GT-S5830 and flash
Sent from my GT-S5570 using XDA
oldernerd said:
Hi,
Certainly doesnt work on a Samsung galaxy ace S5830T on 2.3.4 and GINGERBREAD.DVKQ3.
anyone know what i can root this phone with ??
I tried everything on the web ..no luck.
Click to expand...
Click to collapse
Redownload v14 now is fixed problem was that I forgot to put the script it in Unix Format...see if you have any luck now
tried this method with galaxy s6102 and worked with no issues.
thx
worked perfect on samsung galaxy y dous
Rename zip file
<THOR> said:
You have try to rename the package zip in upd_1.zip and then flash from recovery? if not, try.
Click to expand...
Click to collapse
Thor,
Thanks for your reply...
Rename it to what ??
Already called upd_.zip
---------- Post added at 12:30 PM ---------- Previous post was at 11:52 AM ----------
Hi,
Just downloaded V14 and whilst it says it is rooted and superuser app is loaded, i do not believe the phone is rooted.
Is there a definitive and SIMPLE way i can test
to see if it is actually rooted and that the software i am trying to use is incorrect ??
OR maybe, i dont have the latest V14....
Can i get a link to the latest V14 ??
oldernerd said:
Thor,
Thanks for your reply...
Rename it to what ??
Already called upd_.zip
---------- Post added at 12:30 PM ---------- Previous post was at 11:52 AM ----------
Hi,
Just downloaded V14 and whilst it says it is rooted and superuser app is loaded, i do not believe the phone is rooted.
Is there a definitive and SIMPLE way i can test
to see if it is actually rooted and that the software i am trying to use is incorrect ??
OR maybe, i dont have the latest V14....
Can i get a link to the latest V14 ??
Click to expand...
Click to collapse
install root apps like root explorer, titanium backup or freespace.. if these apps prompt you to allow or deny SU access, choose allow.. if you're phone is rooted, SuperUser app will display that these apps were granted superuser permissions.. simple..
new version
would be great of we could get a new version cut (V15 ??) with Thor's recommendations as well....
I am nearly at wits end with this S5830T rooting issue.
Hi,
I want to root my phone, a Galaxy Mini, but before I do that I have some noob questions, because I don't want to do something stupid...
1. This should work on android 2.3.6 S5570XWKT2, right?
and...
2. Is there any risk that this can brick my phone?
Thanks!
Sent from my GT-S5570 using XDA
T-Mobile/Samsung have rebranded the Exhibit II 4G, giving us a new kernel, a bump to Android v2.3.6 and performance improvements (they claim) in the process. The phone we all love is now the Samsung Galaxy Exhibit 4G.
This stock ROM (UVLG3) is NOT vulnerable to USSD Dialer Attacks!
Rooting
Currently, zergrush will not root this phone's Android 2.3.6. Three known methods:
Root Stock 2.3.6 w/o a new kernel or ROM
root-stock.zip
Mirror
This zip will install Superuser, su and busybox, leaving you rooted, but otherwise no changes to your phone. ClockworkMod must be installed to flash this. So:
1. Flash ClockworkMod
2. Boot into ClockworkMod and flash root-stock.zip.
Rooted Community ROM (forkable)
t679.uvlg3.odex.01.zip
Mirror
(also see custom ROMs)
Linked above is Samsung's newest release for the Galaxy Exhibit, a stock rooted UVLG3 Gingerbread ROM. Busybox is also included. You must flash it via clockworkmod. Clockworkmod can be flashed with Samsung's stock recovery.
Custom rooted kernel
t679-root-v1.8.zip
Mirror
Kernel sources
The kernel is based on Samsung's kernel source. This kernel is rooted; if you flash it via stock recovery or cwm your ROM will be rooted with Superuser.apk, Busybox and the Galaxy Exhibit cwm-recovery installed. This kernel works with all Samsung Gingerbread releases.
Rooted ROM Installation
CWM Keys:
Home key = enter
Back key = back
VolUp/Dwn = highlight choice
1. Back up your data. The installation will format your data partition. I suggest Titanium Backup, available in the Market.
2. Download & copy the current t679.uv???.deodex.0x.zip to your internal sd card (if you already have a cwm installed you may use your removable card).
3. Install Galaxy Exhibit Custom Recovery . If you're already rooted, you may install from the command line, otherwise you may install from Samsung's Recovery. Samsung's recovery only sees the internal SD, so copy the cwm zip there if you just have stock recovery. Stock recovery sometimes takes more than one try to start.
Easy way to start recovery
* Make sure the cwm zip is on your internal (non-removable) sd.
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold Volume-up
* Insert battery
Your phone will boot into recovery. Press the capacitive menu button (left bottom button) when you see the open white box and droid. Choose 'apply update from sdcard' and select the cwm zip file.
4. Start Custom Recovery (cwm): Press & hold Vol-Up, then press & hold Power. Shortly after the plain white Samsung logo appears, release both buttons. Recovery should start after the Galaxy Exhibit logo.
5. Select ROMwipe. This step is required!
6. Highlight install zip from sdcard, then press Home.
7. Highlight 'choose zip from sdcard/external sdcard, depending where you placed the download in step 2.
8. Highlight the rooted rom zip file, then press Home.
After you confirm your choice, installation should take less than three minutes.
Anything you download and install is at your own risk. No guarantees or warranties are given or implied. Your first post-installation boot may be several minutes long.
Rooted Kernel Installation
CWM Keys:
Home key = enter
Back key = back
VolUp/Dwn = highlight choice
1. Back up your data. I suggest Titanium Backup, available in the Market.
2. Download & copy t679-root-v1.8.zip to your internal sd card (if you already have a cwm installed you may use your removable card).
It's recommended to install Clockwork Mod, but you can also flash the kernel from Samsung's stock recovery. Samsung's recovery only sees the internal sd, so copy files there if you don't have cwm.
Stock recovery sometimes takes more than one try to start.
Easy way to start recovery
* Make sure the cwm zip is on your internal (non-removable) sd.
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold volume-up
* Insert battery
Your phone will boot into recovery. Press the capacitive menu button (left bottom button) when you see the open white box and droid. Choose 'apply update from sdcard' and select the cwm zip file.
4. Start Custom Recovery (cwm): Press & hold Vol-Up, then press & hold Power. Shortly after the plain white Samsung logo appears, release both buttons. Recovery should start after the Galaxy Exhibit logo.
5. Highlight install zip from sdcard, then press Home.
6. Highlight 'choose zip from sdcard/external sdcard, depending where you placed the download in step 2.
7. Highlight the kernel zip file, then press Home.
After you confirm your choice, installation should take less than a minute.
Anything you download and install is at your own risk. No guarantees or warranties are given or implied.
Please DO NOT PM me with support questions! They will be ignored! Post them in this thread!
Links and useful info
Galaxy Exhibit XDA Wiki
Galaxy Exhibit IRC channel
Galaxy Exhibit Themes
Custom ROMs
All ROMs listed require cwm for installation.
Peach Sunrise
RebelROM
XquiziT
CyanogenMod 9 Beta
Galaxy ExHibition
CM10 Port
AOKP (WIP)
CM7 (WIP)
CM9 Pure Nexus
Stalled, partially working
AOKP
KEMIUI
Help! I keep getting FCs!
Custom kernel for Rebel Rom
This is custom kernel 1.8 packaged specifically for RebelRom, tested on
version 3.0.8. This package includes kernel & modules only.
rrkernel.zip
Mirror 2
Stock 2.3.6 via Odin
uvlg3.odin.zip
Mirror
Adb for Windows
winadb.zip unzip and copy to your c:\Windows directory
Mirror
Flash2Stock
Flash2Stock (flash via cwm) will install stock UVLG3 and Samsung's stock recovery, un-rooting
your phone, removing ClockworkMod and returning your phone to factory condition.
uvlg3.flash2stock.zip
Mirror
SwapSD
SwapSD This simple app allows you to swap internal "usb storage" (aka /sdcard) and your removable sdcard (aka external_sd) so your larger "external sd" is mounted as "/mnt/sdcard/" and the smaller sd internal memory is mounted as "/mnt/sdcard/external_sd". This is done by changing a file called vold.fstab in your phone's /etc folder. The original device vold.fstab file is backed up to /etc/vold.fstab.backup when this app first runs. Your data on /mnt/sdcard and /mnt/sdcard/external_sd is not touched in any way whatsoever.
Dropbear (flash via cwm)
is a software package that provides a Secure Shell-compatible (ssh) server and client. It is designed as a replacement for standard OpenSSH for environments with low memory and processor resources, such as embedded systems. This archive also includes the scp and rsync utilities.
dropbear.zip
Mirror
Bloatware
These apps are safe to delete. You may also freeze them using Titanium backup.
AnalogClock.apk
Browser.apk (Only if you use an alternative browser)
Dlna.apk
DownloadProviderUI.apk
DualClock.apk
DualClock.apk
IQ-tmobile-release-signed-zipaligned-v1.1....
JobManager.apk
KiesAir.apk
MobileBackup-unsigned_v3.3.02.apk
MyFiles.apk(Only if you have an alternative File Browser i.e. Astro File Manager)
SamsungWidget_Program...
Swype.apk
TetheringManager2.apk(Only if you don't use T-Mo's tethering service)
TouchWizCalendar.apk
TouchWizCalculator.apk
TwCalendarAppWidget.apk
VideoPlayer.apk(Only if you have an alternative video player)
VoiceRecorder.apk
WiFi-Calling.apk(If you don't use it)
ZinioSettingsProvider.v2.03.3331.TMobile....
sihome-signed-tmo-android-8.apk
talkback.apk
tmobile_m4m_3_0_15.signed...
vvm-signed.apk
Partition Table
/dev/block/mmcblk0p1 secboot2 partition map
/dev/block/mmcblk0p2 dbl.mbn (boot loader)
/dev/block/mmcblk0p3 osbl.mbn (boot loader)
/dev/block/mmcblk0p4 MBR extended partition table
/dev/block/mmcblk0p5 EMMCBOOT.MBN (boot loader, has odin download mode)
/dev/block/mmcblk0p6 amss.mbn
/dev/block/mmcblk0p7 emmcparam.bin
/dev/block/mmcblk0p8 boot.img (linux kernel)
/dev/block/mmcblk0p9 adsp.mbn (baseband)
/dev/block/mmcblk0p10 rmt
/dev/block/mmcblk0p11 rmt
/dev/block/mmcblk0p12 persist.ext4
/dev/block/mmcblk0p13 recovery.img (linux kernel+initrd for recovery mode)
/dev/block/mmcblk0p14 param
/dev/block/mmcblk0p15 system.ext4
/dev/block/mmcblk0p16 cache.ext4
/dev/block/mmcblk0p17 data.ext4
/dev/block/mmcblk0p18 preload.ext4
/dev/block/mmcblk0p19
/dev/block/mmcblk0p20 all 0's
/dev/block/mmcblk0p21 all 0's
/dev/block/mmcblk0p22 all 0's
/dev/block/mmcblk0p23 all 0's
/dev/block/mmcblk0p24 all 0's
/dev/block/mmcblk0p25 all 0's
/dev/block/mmcblk0p26 all 0's
/dev/block/mmcblk0p27 efs (encrypted fs)
/dev/block/mmcblk0p28 /mnt/sdcard
Credits:VanillaTbone,s0unds,KemikalElite, jocala, Wildchild, bpear96, camcory, Intercepter and others. If your name belongs here or you have info that needs to be added please speak up!
Zergrush
Rooting the original Exhibit II via zergrush: Please read DooMLoRD's Easy Rooting Thread
Please note that this method does not work with Android 2.3.6 on the Galaxy Exhibit.
ClockworkMod
Galaxy Exhibit cwm-based recovery v6.0.1.2
6.0.1.2 has new features, including better support for both external and internal SD cards, faster backups and restores with a new backup format that de-duplicates data in between backups. Exclusive features for Galaxy Exhibit include:
wipe menu with rom wipe
All system wipes under one menu: rom (system/cache/data),cache,dalvik,cache/dalvik,data.
Stack zip files for installation:
Flash cm9 & gapps, etc. Select as many zip files for installation as you choose. Flash them all with one command.
Install system images:
Drop any recognized system image into a folder on your phone and recovery can flash it. You can even drop the entire contents of an odin tar/md5 file in a folder and cwm recovery will flash it all automatically.
All images must conform to Odin naming standards:
adsp.mbn
amss.mbn
boot.img
cache.img.ext4
preload.img.ext4
recovery.img
system.img.ext4
Click to expand...
Click to collapse
This is regular interface, not touch.
cwm.6012.t679.zip
Mirror
To initially install Galaxy Exhibit Custom Recovery you need to:
1. Copy cwm.galaxy.exhibit.zip to your internal SD storage.
2. Boot into stock recovery:
Starting recovery: Press & hold Vol-Up, then press & hold Power. Shortly after the plain white Samsung logo appears, release both buttons.
Or a different method some find easier:
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold Volume-up
* Insert battery
Recovery should start after the Galaxy Exhibit/T-Mobile logo.
3. Press the capacitive menu button (left bottom button) when you see the open white box and droid. Choose 'apply update from sdcard' and select the cwm.galaxy.exhibit.zip file.
If you already have cwm installed, to update follow the steps above, booting into your current cwm instead of stock recovery.
Should you need to install ClockworkMod via Odin:
cwm.6012.tar
Mirror
We have needed a new thread for our phone, thanks for making this!
kingdavidd said:
We have needed a new thread for our phone, thanks for making this!
Click to expand...
Click to collapse
You're welcome. Just fyi, I'm no longer going to post in the old dev thread or discussion thread. I also plan to make good use of the <reserved> posts above for Galaxy Exhibit links and information.
I'm committed to this phone for the long haul, so thanks for joining me here. I hope this thread will be used for any general discussion of our Galaxy Exhibits (concerning development as well). I also hope folks will evangelize and point people here rather than carry on in the older abandoned OP threads.
Nice job jocala! Thanks.
Sent from my Calculator with Android.
So the rom is stock exhibit after the update... Other than being rooted and the custom recovery, correct? Much rather flash that then go back to stock then update. Thank you for that.
Sent from my SGH-T679 using xda premium
jocala said:
You're welcome. Just fyi, I'm no longer going to post in the old dev thread or discussion thread. I also plan to make good use of the <reserved> posts above for Galaxy Exhibit links.
I'm committed to this phone for the long haul, so thanks for joining me here. I hope this thread will be used for any discussion of our Galaxy Exhibits.
Click to expand...
Click to collapse
Yea all the old threads OP's abandoned them and the original post had all old info, I am glad you're dedicated to this phone!
SurgeRush said:
So the rom is stock exhibit after the update... Other than being rooted and the custom recovery, correct?
Click to expand...
Click to collapse
Yep, that's it. Purely stock except for root, busybox & recovery.
Cant wait to see what roms come out of this
Sent from my SGH-T679 using XDA
The rebranding works out nicely, if for no other reason than providing a point of demarcation.
Many props to Jocala who is awesome, as we all know. It can't be said too often but we'll try not to overdo it. :thumbup:
Sent via frazzled carrier pigeon -->
Ditto here man. We'd all be screwed & tattooed without his know-how. BTW worth mentioning I had to refreeze all the bloatware again after the update. Noticed how the phone lagged and then checked Titanium Backup. Sure enough all the crap was back. Also re-check settings in programs like Juice Defender and Rom Toolbox. I had to re-enter some of them again as well.
Has anyone managed to update successfully while already being rooted? (Specifically by Zerg Rush method)
I've yet to received the OTA notification and still holding off If i should update using the software. Stock ROM but just rooted. Holding off on "flashing" anything as I've never done it before.
ArtfulDodger said:
Ditto here man. We'd all be screwed & tattooed without his know-how.
Click to expand...
Click to collapse
That's not true at all, but thanks for saying it. Anyone handy with *nix can do what I do, and 95% (or more) of the techniques I use were pioneered by others here on xda.
Hey so i was just looking, and had a few questions, the rom you say is stock and odexed, are all the official roms odexed? Also just curious is the extra file in ur rooted rom, that are not in stock, extra like tweaks or part of odex or are they needed? some are just text and xml so im sure prolly wouldnt hurt, but not exatly the same as stock. Also depending on the answers to the above would you mind looking at the rom i made or maybe releaseing one that has no extras just root and busybox so stock kernel and recovery?
edit: also just noticed theres an extra folder(not in stock) T9DB just wondering what they are for or what they do, looks to be like something for the keyboard?
edit2: i think i answered one of my questions stock is odexed., other questions still wondering about though. It also looks like you might have taken a different approach to rooting the rom, maybe you could look at mine see if its just complete fail or not lol and or maybe pming me, to avoid clutter, on how you did urs.
ive made sooo many edits lol but just wanted to add too, thanx for all the work you have done for us.
cars1189 said:
Hey so i was just looking, and had a few questions, the rom you say is stock and odexed, are all the official roms odexed? Also just curious is the extra file in ur rooted rom, that are not in stock, extra like tweaks or part of odex or are they needed? some are just text and xml so im sure prolly wouldnt hurt, but not exatly the same as stock. Also depending on the answers to the above would you mind looking at the rom i made or maybe releaseing one that has no extras just root and busybox so stock kernel and recovery?
edit: also just noticed theres an extra folder T9DB just wondering what they are for or what they do, looks to be like something for the keyboard?
edit2: i think i answered one of my questions stock is odexed., other questions still wondering about though.
Click to expand...
Click to collapse
The phones I use have always come odexed. I know of no other root methods. I don't have time to beta your rom, but feel free to post a link. I'm sure you'll have volunteers
cool, and no problem, and basically all i did was use the dsixd kitchen and added root(from in the kitchen menu), does that not really root it? does that just change the file permissions? cause when i did that it added the su binary so i assumed it did, but doesn't look like thats what you did, urs has a mkroot folder that im gonna guess is used by the update-script to add the su binary and such.
cars1189 said:
urs has a mkroot folder that im gonna guess is used by the update-script to add the su binary and such.
Click to expand...
Click to collapse
You are correct
Flashed the ROM, all went smooth, but I can't install anything from the Market. Every time I try I get "ERROR "Blah" Could not be downloaded due to an error." Any ideas? Did a full romwipe and dalvik before flashing. The markets not even updating to Play store either.
Dual Boot for P990 & SU660 on Both Bootloaders
Now with more and more new ROMs being released every day and only one phone (at least for most of us) to try them all, I think this was needed.
It is based on the method Bihariel found on a Chinese forum and his latest v2 version for the old bootloader and my previous version 3 for the new one.
It is now modified to work on both bootloaders and Partition layouts. Read change log for details.
Thanks to:
SuperSkill personally, for digging it up from the grave and giving me the vote of confidence to port dual boot into the new bootloader. He is also the 1st after me, who tested it. (thank you again my friend)
KingMGT personally, for helping me make the necessary modifications for SU660 and of course for testing it since I don’t own a SU660. (thank you again my friend)
Bihariel of course, for his great work on which I based the new version (and for copying a lot of text from his thread)
ChinaGB, the creator of the System changer app and the original idea.
What is this useful for?
Devs: you can have one ROM configured and ready for use in one partition and a second partition to test your ROMs without touching your daily ROM, so you won/t need to wipe or backup anything.
Users: you can have a stable ROM, let’s say a stock ROM with everything working and configured and you can have a second partition to test ROMs (for example a custom stock based one or a CM10 beta) so you won't need to do backups and wipes.
How Dual Boot works?
Dual-Enabler.zip: this file enables Dual boot by splitting system partition into two.
Dual-ROM-1-to-XX.zip: this file have to be flashed after flashing ROM 1, after flashing it and boot the phone, you will find an app called system changer, by launching this app and selecting Switch ROM, the phone will reboot and start the ROM 2.
Dual-ROM-2-to-XX.zip: this file have to be flashed after flashing ROM 2, after flashing it and boot the phone, you will find an app called system changer, by launching this app and selecting Switch ROM, the phone will reboot and start the ROM 1.
What ROMs can I use?
P990 Devices:
You can use theoretically, any combination of ROMs for dual booting, working on the same Bootloader of course.
SU660 Devices:
On OLD layout you can use theoretically, any combination of ROMs for dual booting, working on this Bootloader of course.
On ICS layout, due to lack of any custom ROMs for SU660, the p990 layout and bootloader is used so only custom CM, PA & MIUI ROMs are compatible, working on this Bootloader of course.
Attention !! The only ROMs you should not use are Auto-wipe ROMs because they will delete your data partition and with it ROM1 and ROM2 save files. Of course if you are an advanced user, you can open the wipe rom and modify the updater-script to remove the auto wipe lines.
Download from here the package for your device and follow the instructions in post #2.
For older versions follow the instructions included in package.
Change Log:
v5.0 Date 05 Feb 2013
DualBoot-Control.zip. All five zips used till now for enabling/maintaining Dual-Boot have been replaced by this aroma-style flash-able zip.
SU660 package now supports also the su660 ics bootloader & layout.
V4.6 Date 30 Jan 2013
512MB-512MB system partitions for both bootloaders,
Reduced data (to 2000MB) for old-bootloader (because a 2048MB one cannot be formatted on old bootloader)
Bug-fix for dual-boot remover (SystemChanger app wasn't removed).
V4.5 Date 22 Jan 2013
Now it auto enters recovery after repartitioning. No need to keep pressing Vol- & Pwr.
Linux nvflash binary added. (I had forgotten to include it in package, sorry.)
Minor changes in flash.sh (for linux).
V4 Date 20 Jan 2013
It now works on both bootloaders. During repartition with nvflash you have the option to select which one
In old bootloader the system partition is splitted in 370MB for ROM1 and 512MB for ROM2 (in case someone wants to install tonyp's & harsh's full ICS version for old bootloader).
Same simple procedure to enable and maintain dual-boot.
Common flash-able zips because they detect current bootloader and partition layout and act accordingly.
Re-compiled SystemChanger app to display more correct messages and also in which ROM you are switching to.
V3 Date 12 Jan 2013
System partition size is 512 MB for each ROM.
Data partition is still shared but with the max size of 2GB.
Included latest cwm recovery 6.0.2.5 by pengus77. It works for all available ROMs for new BL (DM X, FLEX-ICER & unofficial CM10 CM10.1 ones)
NewBL-Dual-Enabler’s scripts are modified not only for the new layout but now also check and format (if needed) the internal SD (the first time after NVFlash is always needed). It also returns to recovery automatically to let you install or restore the 1st ROM.
NewBL-Dual-ROM-1-to-XX.zip & NewBL-Dual-ROM-2-to-XX.zip no longer need to be updated with the boot images of the ROMs.
SystemChanger app’s scripts, before switching to the other ROM, check if current ROM is changed (by md5 checksum of its build.prop as before) and saves the boot.img for next switch.
noshare file, containing the data folders list, is now also saved under /data/dual-boot. This way it will be always accessible and updatable if needed, no matter which ROM is running.
Boot images and md5 checksums are also saved under /data/dual-boot.
Two more flash-able zips added:
Wipe-ROM-data.zip This will wipe the data of the current ROM. Useful for changing ROM or if required by ROM’s chef
Remove-DualBoot.zip This will wipe the data of the other ROM and will also remove the SystemChanger app and scripts from the current ROM. Useful if you want to make a clean nandroid backup, to restore after a repartition to normal layout.
For V2 change log see bihariel's thread
Here is the guide to get Real Dual boot on both BLs.
Please read carefully because this may mess up your phone if you don't know what you are doing.
Oh!! I forgot, this phone is unbrickable, so give it a try.
Installation Instructions
Extract the downloaded package with WinRAR or similar to any folder.
Copy ROM1, ROM2 and the DualBoot-Control.zip to external SD.
Go to the folder DualBoot-Partition-resizer and run flash.bat (or flash.sh for linux) follow on-screen instructions select BootLoader and wait until NVFlash process finishes and the screen goes black.
Disconnect the USB cable, put the battery back and just power on the phone it will enter into recovery automatically. (It takes about 40 secs to enter recovery 1st time after NVFlash)
Install DualBoot-Control.zip and select Enable Dual Boot option. The phone will reboot (if supported by recovery) and enter in recovery again (if not select reboot recovery from recovery).
Make a full wipe just in case to avoid boot-loops and format /system because it may not be formatted by ROM’s updater-script (mounts and storage --> format /system)
Now flash ROM1 (or restore a nandroid backup of ROM1) and without rebooting install DualBoot-Control.zip, select ROM1 update and reboot when it finishes.
When the phone completely boots, you will find an app called SystemChanger, launch it and click Switch ROM, it will ask you for root rights, click yes, the phone will reboot quickly, press and hold Pwr button + vol down when the screen goes black to enter recovery, if the phone doesn't go to recovery, remove the battery, plug it again and enter recovery.
Format /system (the 2nd system now), because it may not be formatted by ROM’s updater-script.
Now flash ROM2 and without rebooting install DualBoot-Control.zip, select ROM2 update and reboot when it finishes. (Attention: do not restore a backup of ROM2 because it will wipe data files of ROM1)
And that is all, if you want to switch to ROM1, as before, run SystemChanger and click Switch ROM.
Note for those having experienced the older version 2: No need to add boot images in Dual-ROM zips any more.
How to change/update a ROM or Kernel
You have to be on the ROM you want to change/update.
Enter Recovery
If you are changing the ROM or kernel and/or a wipe is needed, install the DualBoot-Control.zip and select Wipe current ROM data.
Flash the ROM or kernel and before reboot install the DualBoot-Control.zip and select ROM1 update if you flashed ROM1 or ROM2 update if you flashed ROM2.
Info: There is also the wipe-rom-x-data.sh in /data/dual-boot/ which can be used to delete the non-running Rom’s data. You can also run this from terminal or adb shell to clean the data of the non-running Rom quickly. For example if you are on ROM1 and you want to change the ROM2 run the script, switch to ROM2 but when screen goes black press pwr & vol- to enter recovery.
How to disable Dual Boot
You have to be on the ROM you want to keep.
Enter Recovery
Install the DualBoot-Control.zip and select Remove Dual Boot. This will wipe the data of the other ROM and will also remove the SystemChanger app and scripts. Useful if you want to make a clean nandroid backup, to restore after a repartitioning to normal layout with AIO-Toolkit.
Enjoy it !!
Wow......one thing i ws missing on NEW BL......thank you so much....now can hold onto this phone for 1more year....
This is just Aweosme <3 will give a try for sure ! LG O2X still the Crazy phone will try today eveng and comment back again ! can i try CM10.1 & V30B (Roms available) ???
Kudooos 4 ur post
This is what i need, i often flash rom 1 to another and restore my app and setting manualy... with this i would keep my daily rom and other for testing
thanks good job
Spyrosk, again, CONGRATULATIONS, this is another great product useful for all of us. To drop the bomb; i think you should add this in AIO, it would be natural if possible. Ive tested this during the weekend, its more easy than the previous gb version. Huge thanks for doing this spyrosk and also huge thanks to Bihariel who did the gb version, you have my deepest respect
Let me give you another challenge lol
It should be possible to.......no no, I must shut up now.
Thanks mate
Nice ! Trying soon... :fingers-crossed:
SuperSkill said:
Spyrosk, again, CONGRATULATIONS, this is another great product useful for all of us. To drop the bomb; i think you should add this in AIO, it would be natural if possible. Ive tested this during the weekend, its more easy than the previous gb version. Huge thanks for doing this spyrosk and also huge thanks to Bihariel who did the gb version, you have my deepest respect
Let me give you another challenge lol
It should be possible to.......no no, I must shut up now.
Thanks mate
Click to expand...
Click to collapse
Thank you too again.
No, don't give me another challenge now. :laugh:
I am thinking on making a v3 version for old bootloader too, or even better a v4 hybrid one for both bootloaders. So I do have work for now.
Yes I could integrate that into AIO-toolkit eventually in an "Addvanced Options" menu , but let's see how it is working, when more users will try it and "cure" any "baby sicknesses" that may come up first.
I can't thank you enough for your testing it so thoroughly.
I really appreciate it.
i don't really understand how this dual boot work
but, can i use my internal sd card for booting stock-based custom rom and using my external one for booting CM10 based rom?
what about ics and gingerbread on dual boot!?
jhonjames09 said:
what about ics and gingerbread on dual boot!?
Click to expand...
Click to collapse
you couldn't do that unless someone release GB rom for ics bootloader (is that even possible?)
Nice man" I ll try it soon!
jhonjames09 said:
what about ics and gingerbread on dual boot!?
Click to expand...
Click to collapse
babi_perang said:
you couldn't do that unless someone release GB rom for ics bootloader (is that even possible?)
Click to expand...
Click to collapse
I don't know if this will be ever possible or if it's worth trying it.
The only thing that can be done at the moment, is having one 370MB & one 512MB system partitions on the upcoming gb dual-boot version for installing the tonyp's and harsh's full ics 28g version as 2nd ROM on old bootloader.
I installed yesterday dual boot on my 2X and worked fine without any problems!
Great tool Spyrosk!!
You have done our life easier!!!
Thank you for dual boot
is indeed something very special!!!
It works beautifully for me,
the P990 is significantly upgraded:laugh:
And what about dual boot with linux?
tomsi91 said:
And what about dual boot with linux?
Click to expand...
Click to collapse
What do you mean? Read step 3 carefully.
3.Go to the folder NewBL-DualBoot-Partition-resizer and run flash.bat (or flash.sh for linux) follow on-screen instructions and wait until NVFlash process finishes and the screen goes black.
sorry, i didnt see it with linux
EDIT: no sorry. i mean, i want to dualboot android/linux (debian, ubuntu, etc.).
tomsi91 said:
sorry, i didnt see it with linux
EDIT: no sorry. i mean, i want to dualboot android/linux (debian, ubuntu, etc.).
Click to expand...
Click to collapse
And iOS & Windows Mobil 8...
How about flashing the second rom that have aroma installer??
Dualboot patcher 101
Device : Galaxy Note 4
Difficulty level : Easy
This is a full guide to understand and use Dualboot Patcher App
Download latest app snapshot from : Noobdev
Files » DualBootPatcherAndroid-9.1.0.r80.gd5920b2-snapshot.apk
Latest as of Jan 8 2017
Install it like a normal apk
Dualbooting begins here ---
Main things to do are
Setup Dualboot boot enviroment
Setup Dualboot files
Flashing
Switch between roms
App sharing
Part 1
Setting up for first time use
-Open dualboot patcher app and do the following
-Go to Roms tab then click the 3 dot menu on "Primary"
-Press Set Kernel {if it didnt ask you at the beginning}
-Then press "Update RamDisk"
Part 2
Patching Files for dualboot
-Download the rom you want to dualboot / any mods for it / xposed or whatever flashableZIP you want to install on your secondary rom
-Go to "Patch Zip File" Press the + and click "Add Flashable Zip"
-Select your ROM Zip
-Select your Device (Trelte For exynos or Trlte For Snapdragon)
-Select "Data slot" in Partition Configuration
-The ID is your parition name , basicly SAME ID for zips = Same flash location, Type rom1 for example [No caps]
-Do the same for any other zips (making sure the ID is the excat same)
Part 3
Flashing
Once you are done patching files , you will end up with a duplicate collection of your original files, but they end with _data-slot-[ID].zip suffix
-Grab those files and go flash them in your recovery
-in the recovery screen you will see [Multiboot] prefix behind most scripts, that means you are flashing a patched zip
-Once you are done flashing just hit reboot from the recovery
Part 4
Switching
You will be greated with your new rom , do the first setup and you are now running your secondary rom
Now, to switch roms do the following
-Install your dualboot patcher app on your secondary rom
-Open it and go to "Roms" Section
-Suprise, you will see Primary and below it [ID] (Data Slot)
-Press the primary and reboot , thats it
Part 5
App Sharing
Lets say you want your app data to be available on all your roms , Whatsapp data , telegram data , game data etc
-Open the app on your primary rom , go to "App Sharing" Section and enable " Share Individual applications"
-Press "manage shared applications"
-Click on an app "whatsapp for example"
-Tick "Use shared data"
-Hit ok then Then go back after selecting all your apps
-It must show a toast saying "The changes will take effect next reboot"
-Reboot your device to the secondary rom and do the same thing for the same apps
App data is now shared across both roms,
F.A.Q please read before attempting this
1- Faild to set kernel due to unrecognized device
-Common issue with custom roms, you can fix it by editing your Buid.prop , changing device name , code etc and ro.patcher
2- Flashing files via recovery , will it affect my primary rom ?
- No , all the files are directed to your new rom enviroment , the only things that can affect dualboot is kernel changes
3- How to change primary / secondary kernel ?
-To change primary , just flash the new kernel , then follow " Part 1 " of the guide again
-To Change Secondary , Follow " Part 2 " of the guide to patch the Kernel zip then flash in recovery
4- Where are the files located ?
-your secondary system can be found under /data/multiboot/data-slot[ID]/System (only seen when you are using primary rom or Recovery file manager)
-Your shared app data can be found under /data/multiboot/_Appsharing
5- Enabling app sharing, my data for the app is gone.
-When you enable app sharing it changes the data location, so whatever data you had need to be moved with it, best thing to do is to backup the app you want to share with titaniumbackup (before enabling shared data for it) then restore it when you enable data sharing and rebooting
6- How many roms can i "dualboot"
-As much as you like aslong as you have storage in your data partition i had 4 roms dualbooted at one point
7- How much storage does it consume ?
-CM roms are usually around 1GB for system + few GBs for data (total of 3GB-4GB For normal user with some apps)
-TW roms are heavier around 2-3GB for system (most bloated AF roms) and same for data
8- My secondary rom broke due to a mod or something, how can i switch roms in recovery ?
-Download dualboot utilites
-Files » Utilities : DualBootUtilities-9.1.0.r80.gd5920b2.zip
-Flash in recovery and it will give you an aroma installer enviroment to select your roms
9- Switch roms without aroma
-In TWRP select flash IMG option instead of zip
-Navigate to /internalmem/Multiboot/[ID]/boot.img
-select flash boot
-swipe to flash then reboot
10- Can i install a rom with aroma installer ?
-Yes , just make sure that the aroma does NOT reboot your device after completion as the dualboot script needs to run after the rom script is done to set the new kernel etc
—---------------------------
Hope this helps whoever wants to use this app , its very simple ,it might look complicated but its easy, GL and have fun
This guide can be used for other devices , Dont forget to hit thanks and reply if it helped.
All thanks for the original devoloper and poster @Anik_khan
First here
Will give it a try ASAP and post my feedback soon
I tried to set it up but i keep getting the error message whenever I click on Set kernel: "Could not determine the boot partition because this device's codename 'hltedalvik.dex2oat-filter=speed' is not recognised". I am using the exynos variant, Dooola v12 rom. Can anyone help me, please?
the\downslash\ said:
I tried to set it up but i keep getting the error message whenever I click on Set kernel: "Could not determine the boot partition because this device's codename 'hltedalvik.dex2oat-filter=speed' is not recognised". I am using the exynos variant, Dooola v12 rom. Can anyone help me, please?
Click to expand...
Click to collapse
If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Here is screenshot of my dualboot testing list
webmaster750 said:
If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Here is screenshot of my dualboot testing list
Click to expand...
Click to collapse
Very nice configuration, thank you
the\downslash\ said:
I tried to set it up but i keep getting the error message whenever I click on Set kernel: "Could not determine the boot partition because this device's codename 'hltedalvik.dex2oat-filter=speed' is not recognised". I am using the exynos variant, Dooola v12 rom. Can anyone help me, please?
Click to expand...
Click to collapse
F.A.Q number 2 : Common issue with Dooola roms , and DN7 roms due to changes in codename
ro.patcher.device=hltedalvik.vm.dex2oat-filter=speed
This line needs to be fixed in doola build.prop
Changing it to
ro.patcher.device=treltexx Used to work for me But some people reported bootloops , so take a back up first just in case
I have the n910v im running red dragon rom and its showing gracelte and its not compatible ive asked for the correct line for the build.prop and havent gotten an answer as wbat line to change and what to change it to ... can anyone help me?
happy2472 said:
I have the n910v im running red dragon rom and its showing gracelte and its not compatible ive asked for the correct line for the build.prop and havent gotten an answer as wbat line to change and what to change it to ... can anyone help me?
Click to expand...
Click to collapse
QUOTE=clewis.it;70300596]Add this line to the end of /system/build.prop
ro.patcher.device=trlte[/QUOTE
Try that it work for my n910w8.
BluePhnx said:
QUOTE=clewis.it;70300596]Add this line to the end of /system/build.prop
ro.patcher.device=trlte[/QUOTE
Try that it work for my n910w8.
Click to expand...
Click to collapse
ro.patcher.device=trlte ?
BluePhnx said:
QUOTE=clewis.it;70300596]Add this line to the end of /system/build.prop
ro.patcher.device=trlte[/QUOTE
Try that it work for my n910w8.
Click to expand...
Click to collapse
This is what i get
happy2472 said:
This is what i get
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2447534&page=1099
This is the thread I got my info. Go to page 644.
That is what I used.
ro.patcher.device=trlte
Search for that thread for your model but I think it's the same.
BluePhnx said:
Tthttps://forum.xda-developers.com/showthread.php?t=2447534&page=1099
This is the thread I got my info. Go to page 644.
Click to expand...
Click to collapse
Nope still no good ... let me reboot and see
New
happy2472 said:
New
Click to expand...
Click to collapse
Are you on the latest version?
Wow im usually pretty good at doing this stuff ... is there a more simple set of i structions?
happy2472 said:
Wow im usually pretty good at doing this stuff ... is there a more simple set of i structions?
Click to expand...
Click to collapse
look for ro.product.device= instead of ro.patcher.device=
This worked for me -> ro.product.device=trlte
happy2472 said:
This is what i get
Click to expand...
Click to collapse
Sorry for late response. Your issue is due to your custom Rom changing treltexx names in prop to graceltexx. Usually renaming the changed text to treltexx must work. Use a file editor and search for any grace mention and make sure it says treltexx. Specially the device codename
And update the app It seems old
Sent from my SM-G935F using Tapatalk
Unable to access Roms after a Nandroid Restoration
After doing a nandroid back up in twrp... I restored with my 4 roms with the dualboot patcher....
Only one Rom boots and works the others dont work... whats causing this.... is there anyway to fix this because I have many good data on those roms....plus I would like to feel safe I can do a backup of my roms.
ananjaser1211 said:
F.A.Q number 2 : Common issue with Dooola roms , and DN7 roms due to changes in codename
ro.patcher.device=hltedalvik.vm.dex2oat-filter=speed
This line needs to be fixed in doola build.prop
Changing it to
ro.patcher.device=treltexx Used to work for me But some people reported bootloops , so take a back up first just in case
Click to expand...
Click to collapse
You mentioned making a back up... I have not been sucessfull in making a back up of this app roms... I used twrp and None of the Roms work after restoring the back up.
I got error while flashing zip file from recovery on my device... Seems like it does not support for "trltechn".
Help Please
Thanks a lot