[ROM] (CWM) HoneyComb Froyo V.3 (06-07-11) - XPERIA X1 Android Development

It is New release of HoneyComb Froyo Builds ...
* Working :
- Everything except Camera & BT
- Downloading from market may take long time to start at first time ..
* Features :
- Very Stable & Fast & Smooth Froyo CWM build ..
- Very Fast Wifi with No Dropping ..
- Very Good battery life ..
- Neocore : 25.6 FPS
* Kernel Related issues :
- You may not hear voice during incoming call > Just activate the speaker & deactivate it again to solve this issue ..
- Charging while in android isn't working > You should connect the charger before hitting (haret.exe) ..
-----------------------------------------------------------------
* Installing instructions :
1- Format SDcard To 4 Partitions :
- 1- partition: FAT32 (SDcard / Rest)
- 2- partition: EXT2 (System / about 250 MB )
- 3- partition: EXT2 (Data / about 450 MB)
- 4- partition: EXT2 (Cache / about 100 MB)
* Make sure That all partitions are set PRIMARY ..
2- Extract Package & Copy [npkboot] Folder to root SDcard ..
3- Copy [HoneyComb Build V.3] To root SDcard without extraction ..
4- Run Haret & wait till it ask you to press Volume Down shortly to launch ClockworkMod Recovery ..
5- While In recovery menu , choose " install zip from SD card >>
choose zip from sdcard and select " HoneyComb Build V.3.zip " ..
- Then return back to main menu using " ok " key , Then choose " reboot system now "
6- Run " HARET.exe " & leave it to continue booting into Android ...
** For More info see THIS TOPIC
------------------------------------
** Very Important :
* Please don't install GAPPS after rom installation directly , Otherwise you'll have a serious problems ..
So you must :
1- Install HoneyComb V.3
2- Run the build
3- Restart it
4- Install Gapps
* Attached Kernel is highly overclocked , it may not work with all kovsky devices , so if it doesn't work with you, try to change the overclocking value from 652 to 614 mhz in startup.txt ..
- If it is still not working , replace this kernel with "Turbo kernel" attached to package ...
*********************************************
* Thanks To :
- Neopeek ( For CWM & Many others )
- TiaD8 ( Many tweaks & stuff taken from his builds )
- Highlandsun ( For his libs )
- People made these themes & icons .
- All other persons who i forgot to mention ..
**********************************
DOWNLOAD
^^^^^^^^^^^^^^^^^^
* On Screen Answer interface
* For Keyboard Freezing proplem
**********************************
If you like my work, Please just Don't Mirror my links ..
Don't Forget To click Thanks Button ...

* Installing instructions :
1- Format SDcard To 4 Partitions :
- 1- partition: FAT32 (SDcard / Rest)
- 2- partition: EXT2 (System / about 250 MB )
- 3- partition: EXT2 (Data / about 450 MB)
- 4- partition: EXT2 (Cache / about 100 MB)
* Make sure That all partitions are set PRIMARY ..
2- Extract Package & Copy [npkboot] Folder to root SDcard ..
3- Copy [HenDroiD_V2.zip] To root SDcard without extraction ..
4- Run Haret & wait till it ask you to press Volume Down shortly to launch ClockworkMod Recovery ..
5- While In recovery menu , choose " install zip from SD card >>
choose zip from sdcard and select " HenDroiD_V2.zip " ..
- Then return back to main menu using " ok " key , Then choose " reboot system now "
6- Run " HARET.exe " & leave it to continue booting into Android ...
** For More info see THIS TOPIC

finally.....great work man....!!! download now....

nice work !!!
needo why you delete languages from this ROM?? ( please return choose czech language in Settings )

are the Keypad drivers modules or not ?

RenEdi said:
nice work !!!
needo why you delete languages from this ROM?? ( please return choose czech language in Settings )
Click to expand...
Click to collapse
this build isn't supporting many laguages, but you can use morelocale ( Attached to this post )
djkarl said:
are the Keypad drivers modules or not ?
Click to expand...
Click to collapse
the separate keypad modules isn't included in this package , i think you wan't need it again > i'm using it for more than 8 hours with no keyboard stoppage ..

trying now

Tried it for 2 hours now. I had only one wifi connection lost. But that was the only error. Market works. It's fast and stable LOVE IT ^^

I'll give it a try asap! =)
is AZERTY keymap available ?

can someone make a video on how to Become the process we do start the haret I've done it many times k no can do let us help someone. instructions I pay close attention but nothing.
sorry my english!

tried this for a few hours and the build is quite solid and stable, but with all other android builds ive tried, the keypad freezes all the time for me. froze 3 times so far in 4 hours. guess i still cant use any android build until thats fixed in the kernels. ill try the turbo keernel tosee if its any better

i have a problem, it don't ask me: press volume down
Do you know why that is?
(Sorry for my bad English)

Gameforce said:
i have a problem, it don't ask me: press volume down
Do you know why that is?
(Sorry for my bad English)
Click to expand...
Click to collapse
When you start android and the code is displayed there is the pinguine on the top, wenn the pinguin disapear and the code begin at the top, than press vol down

wi fi
- Very Fast Wifi with No Dropping .. ---- NOT Working for me.. when i try to start wi fi my x1 reboots back in winmo
great speedy rom, very fast!!!!

neoofoox said:
When you start android and the code is displayed there is the pinguine on the top, wenn the pinguin disapear and the code begin at the top, than press vol down
Click to expand...
Click to collapse
Oke thanks,
And do you know how long i need to wait before the pinguine dissapeared???

great rom !! but if i make a call or get incoming call,,i can't found red and green button in my screen,,so i used red/green button in under screen..thank very much

Gameforce said:
Oke thanks,
And do you know how long i need to wait before the pinguine dissapeared???
Click to expand...
Click to collapse
It should apeare after 30-60sec (normaly shorter)

PsychoAssasin said:
tried this for a few hours and the build is quite solid and stable, but with all other android builds ive tried, the keypad freezes all the time for me. froze 3 times so far in 4 hours. guess i still cant use any android build until thats fixed in the kernels. ill try the turbo keernel tosee if its any better
Click to expand...
Click to collapse
you can use the kernel with separate keyboard modulus so you can activate it with one touch everytime it freazes ...
ncw2k69 said:
- Very Fast Wifi with No Dropping .. ---- NOT Working for me.. when i try to start wi fi my x1 reboots back in winmo
great speedy rom, very fast!!!!
Click to expand...
Click to collapse
i don't know the reason , but it may be winmo related or radio related , BTW try to enable wifi in Winmo & start android ...
vannanta said:
great rom !! but if i make a call or get incoming call,,i can't found red and green button in my screen,,so i used red/green button in under screen..thank very much
Click to expand...
Click to collapse
yes it was excluded , it is always getting distorted & some times doesn't work ...

neoofoox said:
It should apeare after 30-60sec (normaly shorter)
Click to expand...
Click to collapse
it depends on the SDcard contents , if there are many files & folders it'll take longer & so on ...

needo said:
it depends on the SDcard contents , if there are many files & folders it'll take longer & so on ...
Click to expand...
Click to collapse
Ah okay I didn't know. I have quite clean sdcard.
And I have one question. After Installing gapps (after launching android) everything worked fine and I never get a force close message. But after starting Android after reboot I get a lot of force close messages. (The process android.process.acore has stopped unexpectedly. Please try again.)
I use turbo kernel (this one in the turbo kernel folder @612mHz)
The included one didn't work. I pressed harret and then phone restarted (i tried both 652 and 614 mHz) Do someone know what's the problem? But that is not so urgent

Related

[ROM] CyanogenMod 6.1 V1 - CWM - 23-04

Hi every one! I give you another good build. It repark from CM Modded Build V.2 by needo, and work with ClockworkMod, so here is the build:
I. Download needed file:
1. CyanogenMod 6.1 V1 - CWM - 23-04.zip
http://www.multiupload.com/QQF81OD7IE
2. npkboot-cwm-v15-x1-monsterKernel.rar
http://www.multiupload.com/R4A7PJE00T
II. before install :
1. Format your sdcard make 4 Partition with recommended size:
1st partition: FAT32 (sdcard / Rest)
2nd partition: EXT2 (system / about 150MB -> depends on the build )
3rd partition: EXT2 (data / about 250MB)
4th partition: EXT2 (cache / about 50MB)
Be sure make all 4 partition primary
2. extract and copy folder npkboot to root of sdcard.
3. Copy Rom ( zip file , don't extract) in to root of sdcard.
III. Install:
1. run Haret, and wait when it will be asked to press "Volume Down" shortly (!!important!! shortly) to launch ClockworkMod Recovery or any other key to usually continue booting into Android.
Press volume Down and wait for menu Recovery.
2. In menu recovery choose "install zip from sd-card" choose zip from sdcard and select "CyanogenMod 6.1 V1 - CWM - 23-04.zip" . Confirm instalation then reboot system.
4. Run HARET again and press any key (except Volume keys) to continue booting into Android.
Tips:
First boot :
*Settings > CyanogenMod Settings > User interface > tweaks extra > load theme > choose CM 6.1 white
- This will change the status bar text colour to white ...
*Launcher settings > change theme > choose the gre theme ...
*disable data transfer
*disable auto-rotate screen
- Android won't performing very well at first running hours, if you have many media files (pic,videos..) .. system will be busy searching for these files & creating thumbnails for them ... the time for that is depending on the quantity of the media on the SD card ..
UPDATE:
- If you can't boot to android, try change modules to Turbo kernel and reinstall.
- If you want stop problem key freeze, download kernel with keyboard as modules and follow this link http://forum.xda-developers.com/showpost.php?p=11808067&postcount=2 how to do ^^!
- For better batterry, download and install SetCPU, then custom it yourself !
- For better speed install ADW Laucher ^^!
Thanks to Neopeek, needo and other developers !
I have done:
- Everything copied to SD following the how to.
- [2011-04-18] FRX06 [CWM] worked, but this rom doesn't work
- Formated ext2 partitions to erease the old rom.
- Using Duckly's Kernel [Turbo Kernel] WITH KEYPAD DRIVERS AS MODULES
Problem:
I can run haret but when I have to click vol down it doesn't launch the recovery mode. it wants to continue.
With the FRX06 it worked but now it doesn't work
BTW: the hyperlink after "Update:" isn't working
Hope you can help me
EDIT: Changing Kernel to Duckly's Kernel [Turbo Kernel] [25-3-2011] WITH KEYPAD DRIVERS NOT AS MODULES has solved my problem.
Is there a way to use the Kernel with keypad drivers as modules?
neoofoox said:
I have done:
- Everything copied to SD following the how to.
- [2011-04-18] FRX06 [CWM] worked, but this rom doesn't work
- Formated ext2 partitions to erease the old rom.
- Using Duckly's Kernel [Turbo Kernel] WITH KEYPAD DRIVERS AS MODULES
Problem:
I can run haret but when I have to click vol down it doesn't launch the recovery mode. it wants to continue.
With the FRX06 it worked but now it doesn't work
BTW: the hyperlink after "Update:" isn't working
Hope you can help me
EDIT: Changing Kernel to Duckly's Kernel [Turbo Kernel] [25-3-2011] WITH KEYPAD DRIVERS NOT AS MODULES has solved my problem.
Is there a way to use the Kernel with keypad drivers as modules?
Click to expand...
Click to collapse
I see, your problem is monster kernel not work with your phone, and when you change it to Turbo kernel it work ^^!
FOr use kernel with kaypad as modules, please read this thread http://forum.xda-developers.com/showpost.php?p=11808067&postcount=2
First: boot to android, then install autostart.apk and GScript.apk.
next: open terminal , remove modules and copy autostart.sh like that thread write. then open GScript and add script like that thread write.
next: reboot to winmobile, copy Turbo Kernel with keypad as modules to your sdcard/npkboot folder, replace the old file in there.
Final: boot to android, then make a shotcut GScript in home screen, when keypad die, just open the shotcut and it will work again.
Hope it have you
I see, your problem is monster kernel not work with your phone, and when you change it to Turbo kernel it work ^^!
Click to expand...
Click to collapse
I have never used Monster Kernel because I think it needs more battery than the Turbo kernel so I changed it to the Turbo Kernel.
After adding "ts-calibration"-file to the npkboot folder, it is starting now
*Settings > CyanogenMod Settings > User interface > tweaks extra > load theme > choose CM 6.1 white
- This will change the status bar text colour to white ...
Click to expand...
Click to collapse
There is no "CM 6.1 white" (CMTheme folder is empty) but the "STOCK_Black" makes the clock visible (status bar still black). Finaly I copied the "CM 6.1 white"-file from the EXT2 version.

[ROM] NeoFroyo V0.1 for Xperia X1 [17-08-2011]

Initial Release V0.1:
This ROM is english only and has several tweaks inbuilt. Try it out yourself and you will be amazed of the overall speed. Maybe I will support more languages later (have to talk to Infinimint about this -> maybe he has enough CPU power and time + nerves to compile it in each language). Till then if you are searching for another language then move elsewhere to find your ROM...
you can find more informations here: http://www.neopeek.com/viewtopic.php?f=14&t=7524
**************************************
* Installing instructions :
1- Format SDcard To 4 Partitions :
- 1- partition: FAT32 (SDcard / Rest)
- 2- partition: EXT2 (System / about 250 MB )
- 3- partition: EXT2 (Data / about 450 MB)
- 4- partition: EXT2 (Cache / about 100 MB)
* Make sure That all partitions are set PRIMARY ..
***********************************************************************
2- Extract & Copy Npkboot Folder and Neofroyo-v01.zip to root SDcard ..
3- Run Haret & wait till it ask you to press Volume Down shortly to launch ClockworkMod Recovery ..
4- While In recovery menu , choose " install zip from SD card >>
choose zip from sdcard and select " Neofroyo-v01.zip " ..
-Then return back to main menu using " ok "
5- Check mounts (Mounts and storage menu), and make sure that system is mounted.
6- Install Gapps like you installed the build (point 4)
-Then return back to main menu using " ok "
- i fyou want you can instal neolang to have the build in other language, but maybe you will lose speed and stability (not sure).
7- reboot system now
8- Run " HARET.exe " & leave it to continue booting into Android ...
** For More info see http://www.neopeek.com/viewtopic.php?f=14&t=6630
***********************************************************************
* Attached Kernel is highly overclocked , it may not work with all kovsky devices , so if it doesn't work with you, try to change the overclocking value from 652 to 614 mhz in startup.txt ..
- If it is still not working , replace this kernel with "Turbo kernel" attached to package ..
***********************************************************************
Download: http://hotfile.com/dl/127082063/c9fda77/CWM_NeoFroyoV01X1.rar.html
Reported Bugs
Terminal Emulator and Quickpic not working: Oooops I forgot to exclude 'em! Just uninstall them via Settings and reinstall at least QuickPic again from Market -> not a serious bug, is it?
Credits & Thank You's:
Neopeek-Team for testing
XDAndroid-Team
Cyanogen + Team
Anybody else whom I forgot.
**********************************
I'm Not responsible for any damage for your device ....
Im not a dev, just put stuff together credit goes to all authors just posting here to spread the word, so if you have errors, please report in the threads linked above =).
sorry man, but this isn't right!
sure. you say all credits go to the devs in the very last paragraph.
but until there you make it look like you compiled this rom yourself by using simple c/p of neopeeks original post...
1- Format SDcard To 4 Partitions :
- 1- partition: EXT2 (System / about 250 MB )
- 2- partition: EXT2 (Data / about 450 MB)
- 3- partition: EXT2 (Cache / about 100 MB)
- 4- partition: FAT32 (SDcard / Rest)
Click to expand...
Click to collapse
this is wrong, fat32 needs to be first partition, otherwise windows won't recognize it anymore.
i don't know which gapps you put into this package, but it's certainly not the one neopeek tells you in cwm-thread. the meta-inf isn't replaced.
Is that any difference between this and THIS
jerrytan93 said:
Is that any difference between this and THIS
Click to expand...
Click to collapse
no difference, I just made all the steps for you so you just have to unzip the files and copy them in root of SDcard
ooooppssii daily i seemed to have made a new thread for something which is already thereE!
to bad wifi isnt working
It is, just get the right kernel, ygge or latest glemsom (19.08.)
but glemsom ain't so good for me:
- wifi working***
- system a bit snappier (or just wishful thinking?)
- permanent hiss from loudspeaker
- battery always full
- had to change cpu-freq to 652, phone kept freezing with 672
- sys-process-gapps fc's now and then
*** i didn't reinstall the rom, just changed kernel & wiped dalvik cache. So i don't know if something extra is left from ygge-kernel.
edit:
took longer, but it froze again. 633 mhz now.
Click to expand...
Click to collapse
Hi there!
It works fantastically, but I don't know if this build is supposed to have fixed this issue, I'm still having the hardware keyboard death problem. So I tried to implement ygge's keyboard-as-modules kernel, and when deleting the current modules, I have an error saying that they can't be removed because this is a Read-only file system. (like this: "cannot remove 'nameofthemodule.ko': Read-only file system")
It is not the first time I try to use this kernel, and the previous times, I could delete them without any trouble (through terminal emulator). I have tried with terminal emulator as a root, with other file explorers as a root and seems to be difficult to erase them. Is there any other solution? Oh, and I have already tried reinstalling again, but I guess I can't reinstall with ygge's kernel with keyboard as modules since I won't be able to press volume down to enter Recovery mode, am I right? Thanks.
Thanks in advance!
I already posted this issue twice in neopeek's forum, without any luck
Felipaoo said:
Hi there!
It works fantastically, but I don't know if this build is supposed to have fixed this issue, I'm still having the hardware keyboard death problem. So I tried to implement ygge's keyboard-as-modules kernel, and when deleting the current modules, I have an error saying that they can't be removed because this is a Read-only file system. (like this: "cannot remove 'nameofthemodule.ko': Read-only file system")
It is not the first time I try to use this kernel, and the previous times, I could delete them without any trouble (through terminal emulator). I have tried with terminal emulator as a root, with other file explorers as a root and seems to be difficult to erase them. Is there any other solution? Oh, and I have already tried reinstalling again, but I guess I can't reinstall with ygge's kernel with keyboard as modules since I won't be able to press volume down to enter Recovery mode, am I right? Thanks.
Thanks in advance!
I already posted this issue twice in neopeek's forum, without any luck
Click to expand...
Click to collapse
My X1i accept calls and wifi does not work, do not help any modifications.
Does someone else have this hardware key's freezing problem as well? How did you fix it? The current solution of the kernel with keyboard separated as modules doesn't seem to be working here
Felipaoo said:
Does someone else have this hardware key's freezing problem as well? How did you fix it? The current solution of the kernel with keyboard separated as modules doesn't seem to be working here
Click to expand...
Click to collapse
the fix doesnt work for me neither
Guy this is NEOPEEKS BUILD why u say its yours not fair......
ilgreco112 said:
the fix doesnt work for me neither
Click to expand...
Click to collapse
So what did you do? Use another build?
Felipaoo said:
So what did you do? Use another build?
Click to expand...
Click to collapse
Actually I'm not using android since I had too much problems with it

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

Note: CyanogenMod 7 Official Support is HERE
Note 2: THIS THREAD IS FOR THE SAMSUNG GALAXY ACE S5830/S5830B/S5830D/S5830L/S5830T ONLY. IT DOES NOT APPLY TO THE S5830i/C/M
This serves as a warning and guide to all the new users in the Galaxy Ace XDA forums .
Samsung Kies is Samsung's version of iTunes . It allows you to sync all your stuff and back them up in case of phone problems .
But there's one thing Samsung forgot about: Memory optimisation . Kies requires at least 1.5GB of system memory . Even iTunes handles memory better than Kies.....
As a result , many users brick their Aces because they use Kies to update their phone and Kies suddenly stops responding because of RAM .
EDIT: I am not so sure now because some users have successfully updated their devices with Kies .
ROM Manager is a manager for Clockworkmod Recovery , which saves time because you don't have to reboot to recovery .
People, don't use ROM Manager for your own good......
You can also use CWM Manager , which is included in most custom ROMs .
Clockworkmod Recovery supports Galaxy Ace with many versions (with the official one being v4.0.0.9) .
The unofficial versions are v3.2.0.1 (if I'm not wrong) , v5.2.0.3 and v5.2.0.6 .
Edit: WITH CF-ROOT , BUSYBOX is BULLETPROOF
Another note about UNLOCKING YOUR PHONE by consegregate:
consegregate said:
Unlocking is an extremely risky process which touches your efs folder. Your IMEI can be wiped if you do a wrong step and that's the end of your road in the android conquest. Many of us have fallen to the enticing prospect of unlocking where the phone gets out of the box and poof goes back in again in no time.
SO, until we can backup the IMEI, try not to unlock using unorthodox methods. It may work for some, but for most of you you'll be left with ****ty phones because you can't read and follow instructions. So until then, please don't post "bricked mai phone help plz" because if it was because of unlocking, we may not be able to help you.
Lastly, USE THE SEARCH TOOL. AIN'T THERE FOR NOTHING! Cheers, all you sad faces.
Click to expand...
Click to collapse
A view about this tutorial by Ardentfaith:
Ardentfaith said:
Okay first off, the tutorial is wrong.
I have a USA Samsung Galaxy ACE
WHAT MOST PPL WANT TO DO:
1) root phone 2) have an escape plan when it fails.
Let's work on the escape plan.
Make sure you use Samsung KIES to update to the latest version of Android Gingerbread. Why? You could go to samfirmware to get a firmware and then download odin to flash it but why? You want to BAckup an ORIGINAL working rom.
Now you have Gingerbread. You want a backup. Search for chinoray and clockwordmodace.zip. This'll give you the backup program (a.k.a Clockworkmod Recovery) so you can do a recovery no matter what. (Press home and power to boot into recovery mode. there's an option to install from a zip. Install chinoray's file)
Now backup. Remember to put the backupfile that's made in 2 other places. Your sdcard isn't exactly a bank.
Now you want to root. Do the same recovery thing with a file from davebyone called Acegingerroot.zip. That roots it to an english brazil portuguese kp7 thingie. It's just fastest way to root. You'll have superuser app on now. congrats.
Now what to do with root? Your ace has very little memory. You need to extend the internal app storage to the sd card. The FIRST thing you need to do is go back to Clockworkmod recovery mode and partition your sdcard so that it has a ext4 extension. Then update from ketut.kumajaya's post with cf-rootdtapps2sd???.zip(forgot the full name). That defaults all downloaded apps to run from the sd card.
--Or you can ignore all this and do the chainfire post cf-root guide but ket's modifications are more hassle free.
so now you have a rooted Samsung ACE running Gingerbread running Touchwiz with apps running off the SD card.
There's not a good rom out for Samsung ACE anyways. You might as well stick to this for now.
Click to expand...
Click to collapse
Here's a little guide on how to flash a ROM via ODIN by me:
Requirements:
- A Windows computer
- A Galaxy Ace plugged into the computer via USB
- You must have ODIN installed , duh !
- (Windows Vista/7 compulsory) Running ODIN with Administrative rights:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Ended KIES via Task manager:
Instructions:
1 - Download your favourite firmware here
2 - Extract the .rar out using WinRAR or 7zip (password is samfirmware.com)
3 - Check if it's a FULL package or ONE package:
FULL Package instructions:
1 - Open up ODIN (MAKE SURE ALL REQUIREMENTS ARE MET)
2 - Set your phone in Download Mode (Home + Power + Volume Down)
3 - Once you have correctly entered Download Mode and plugged in , this should appear in ODIN:
4 - Place the files in this order:
OPS - Select the file named Cooper_v1.0.ops (or anything like that)
BOOT - Select the file named "APBOOT_S5830xxxxx_CL514579_REV03_user_low_true.tar.md5"
where "xxxxx" = Your firmware version
Phone - Select the file named "CODE_S5830xxxxx_CL514579_REV03_user_low_true.tar.md5"
where xxxxx = firmware version
PDA - DO NOT PLACE ANYTHING
CSC - Select the file named "GT-S5830-MULTI-CSC-xxxxxx.tar.md5"
where "xxxxxx" = the CSC region
EFS - Select the file named "MODEM_S5830xxxxx_CL514579_REV03.tar.md5"
xxxxx = firmware version (Be VERY VERY careful with this EFS part)
After you're done , click on "Start" and let the magic reveal itself slowly......
ONE Package method:
1 - Open up ODIN
2 - Set your phone in Download Mode while plugged into USB
3 - Tick the option "One Package" in ODIN (Refer to previous ODIN picture)
4 - Select the only .tar.md5 file
Now press start and watch the magic.....
Nice info
Could you add this:
Do not install busybox on custom ROMs because busybox already exist on most custom ROMs, and also stock firmware with CF-Root. If you're already do so, it mean that you're ready to reflash your phone ...or try to remove all files named "busybox" with root explorer then flash CF-Root b79 (then flash b80 for KPN users)
Ya you are right when I am new for galaxy ace I Install rom manager and while taking backup through it my phone suddently off and not start not even in downloading mode. Means it breaked. But thanks god it repaired by samsung service senter. So not install that app.
Here's a little Q&A:
Q-1: What is the Samsung Galaxy Ace? Is it edible?
A-1: Hello dear newbie , the Samsung Galaxy Ace is a mid-range phone that was released by Samsung in February 2011 .
Specifications:
-Supports Quad band GSM (850/900/1800/1900)
-Supports Duo band HSDPA (900/2100)
-Size is 112.4 x 59.9 x 11.5 mm
-Weighs 113g (light )
-Has a TrueFont Type capacitive touchscreen with 16,000,000 colours
-Screen resolution of 320x480 and a 3.5" display (160 dpi LCD density)
-Gorilla Glass display
-Multi-touch support
-Accelerometer sensor for auto-rotation
-Touch-sensitive Menu button and Back button (with physical Home button)
-TouchWiz v3.0 UI (Homescreen)
-Has a loudspeaker and has a 3.5mm audio jack with DNSe Sound Enhancement
-Has vibration(duh) ; supports MP3 and WAV ringtones .
-Has pratically unlimited entries for contacts and call records
-158MB internal storage with support for SDcard up to 32GB (2GB included)
-Supports GPRS , EDGE and HSDPA (7.2Mbps)
-WiFi 802.11b/g/n , Portable hotspot and DLNA certified
-Bluetooth v2.1 with A2DP (for bluetooth stereo headphones)
-No infrared port
-5MP Camera with autofocus , LED flash , geo-tagging , face and smile detection
-Records video at [email protected] (OMG ) with NO SECONDARY CAMERA
-Runs Android (Froyo , but upgradeable to Gingerbread)
-800Mhz Qualcomm MSM7227 ARM11 processor with an Adreno 200 GPU
-SMS (threaded view) and Email support
-Comes with a stock HTML Browser
-Supports Stereo FM Radio with RDS
-Supports Games (a.k.a APK files)
-Comes in Black and White (as in the selection of battery covers )
-A-GPS support with the normal GPS
-Supports Java with the MIDP emulator
- MP4/H.264/H.263 player
- MP3/WAV/eAAC+ player
- Organizer
- Document editor
- Image editor
- Google Search , Maps , Gmail , YouTube , Calendar , Google Talk , Picasa integration
- Voice memo/dial
- Predictive text input (Swype) (Other keyboards available on Market)
-1350mAh Lithium-Ion Standard Battery
-2G standby up to 640hours and 3G standby up to 420hours
-2G talktime up to 11hours and 3G talktime up to 6hours 30minutes
-Costs about 260 Euros
Thanks to http://www.gsmarena.com/samsung_galaxy_ace_s5830-3724.php
*Pants*
Q0: What is root? What advantages can it do to my phone?
A0: "Rooting" your phone is the process of allowing Superuser access to your phone (a.k.a su or sudo access) , thus opening up system files to the user .
This is usually needed/done by custom ROMs .
More info can be found here:
http://en.wikipedia.org/wiki/Rooting_(Android_OS)
"Rooting is a process that allows users of mobile phones and other devices running the Android operating system to attain privileged control (known as "root access") within Android's Linux subsystem with the goal of overcoming limitations that carriers and manufacturers put on some devices. It is analogous to jailbreaking on devices running the Apple iOS operating system."
Q1: What is a custom ROM? What to can it do to my phone?
A1: A custom ROM can be either:
- Modifications to the official company ROMs (a.k.a Stock ROMs) , which increases its speed and stability compared to original Stock ROMs .
These ROMs include:
-Blackhawk (by ketut.kumajaya)
-Fla.sh (by fla.sh) (No Support Available anymore , therefore no link)
-Sangingerace and Persian Gulf (by sasanekabaran)
-The BehradGH ROM series (by BehradGH):
-BehradGH ROM Series KPB
-BehradGH ROM Series KPN/KPH
-BehradGH ROM Series KP9
-NoName (by an0nym0us_)
-My-UI (by jusada)
-GingerReal (by redmaner and MuayThaiFighter08 (I think , sorry if I got it wrong !) )
-FirstUA (by Grif_07)
-Glsmt (by sametpoyraz)
-TheMyth (by devilsking) (Thread Closed)
-Blockbuster ROM Goes Ace
-Mush69ROM (Thread Closed)
-TurboBlue (by tazlooney89)
There are other ROMs that do not use Stock ROMs and are built from scratch by these AWESOME people:
-AOSP 2.3.7 (A work-in-progress by me , fla.sh , Jekle_Ace and consegregate)
-Grif_07's CM7.1 BETA-Kang 2.3.5
-BehradGH CyanoAce CM7.1 RC1 2.3.5
-Infinity ROM (Based on CM7.2 by nims11)
-Infinity ROM (Based on CM7.1 by nims11)
-Gingercruzt (Based on CM7.2 by nims11)
-Touchwiz4 Style CM7.2 ROM (by slaid480)
-HaniMod*LiteStar (By sasanekabaran)
-Icecream Sunday & Speed Blur (by jusada)
-Cre.ActiveX (CM7.1 by saigetshu)
That is all you actually need to know
Q2: What's Recovery Mode? What is Download Mode? What are the different "Modes" that my phone can go into?
A2: Recovery Mode is a place where you go to if your phone is ever "stuck" or in a "bootloop" if you installed a ROM wrongly .
The stock recovery mode can't do much and therefore if you want better advantages such as:
-Backing up your current ROM and data
-Fixing Force Close Permissions
-Wiping your Dalvik-Cache
-Wiping Battery Stats (if your battery meter is jumpy , like all custom Stock ROMs)
-Install unsigned .zip files
-Formatting various parts of your internal memory (/system , /data etc)
-Mount USB Storage in Recovery Mode
The only thing you can do is use CLOCKWORKMOD RECOVERY
For Download Mode , it is a Samsung-exclusive feature that allows you to "Download" custom stock ROM files into your phone .
It works like a normal install in ClockWorkMod Recovery (a.k.a CWM) , except that it automates everything (wiping data , wiping system stuff)
These are possible modes which you can use to enter different places (for advanced people only):
Home + Power = Recovery Mode (whether stock or CWM)
Home + Volume Down + Power = Download Mode (normal)
Home + Volume Up + Power = ARMv9 Dump Mode
Home + Volume Down + Volume Up + Power = Download Mode (EMERGENCY)
Q2.5: What is ClockworkMod Recovery? How do I use it?
A2.5: ClockworkMod Recovery is one of the best custom recoveries out there and was made by the AWESOME koush
Here's how you use it by devilcode:
devilcode said:
There you go.... not from v4.0.0.9 but its of a old version but will give you and idea or to anyone else .. will not post a link to some other site so just posting the explaination here
Options explained
1. reboot system now
This one is self-explanatory.
Reboots the phone.
2. apply update from sdcard
This can be used for installation of any official or unofficial update, ROM, kernel, theme etc. that is in a zip format installable from recovery, as long as the file is named update.zip and it has been placed on the root of your SD card (i.e. not in any sub-folder). Selecting this option (and most of the options featured below) will bring up a rather annoying confirmation prompt but this has saved us on multiple occasions from a lot of trouble we would have been into due to accidental key presses.
3. wipe data/factory reset
This option wipes all user data on the device as well as cache. Doing this will leave your phone in the state it was in when you bought it or when any custom ROM was first installed. It will also wipe any sd-ext partition that you might have set up.
4. wipe cache partition
Wipes the cache partition of the device to clear all the data accumulated there over use. This is often used before installing a new ROM, app, kernel or any similar mod via recovery.
5. install zip from sdcard
This option brings up the following sub-menu:
A. apply /sdcard/update.zip
This one is essentially the same as the ‘apply update from sdcard’ option of the main menu.
B. choose zip from sdcard
Lets you install any zip file (with any name) from any location on your SD card. The file can be for a ROM, a kernel, an application, a theme or any mod as long as it is in recovery-flashable zip format. This is the most widely used option for installing a ROM that you have downloaded and copied to your SD card. Entering this option will bring up a screen that will allow you to browse your SD card for the zip file and select it for installation
C. toggle signature verification
Turns the signature verification on and off. When signature verification is on, you will not be able to install any custom ROMs that haven’t been signed by the developers (most custom ROMs aren’t signed). Switching it off skips the signature verification check and proceeds with the installation.
D. toggle script asserts
Seldom-used option for a vast majority of users. It simply turns script asserts on or off. If you don’t know about these (i don’t), it’s best not to change this option. (For advanced users ONLY)
E. +++++Go Back+++++
Takes you back to the main recovery menu, obviously!
6. backup and restore
Undoubtedly one of the most important features provided by a custom recovery, the backup and restore feature – also known as Nandroid backup – allows you to take a backup of your phone’s entire internal memory including all partitions, and save it on the SD card.
A. Backup
Takes a Nandroid backup, as explained above.
B. Restore
Lets you restore a previously taken backup. Entering this option presents you with a list of existing backups from the SD card that you can choose from for restoration.
C. Advanced Restore
This option is similar to the Restore option but once a backup has been selected to be restored, this option allows you to choose what parts of it to restore. You can choose to restore the boot, system, data, cache and sd-ext partitions.
7. mounts and storage
Allows you to perform maintenance tasks on all the internal and external partitions of your android device.
A. mount/unmount /system, /data, /cache, /sdcard or /sd-ext
These options let you toggle between mounting or unmounting these respective partitions. Most Galaxy Ace users need to mount /system and /data for ROM installations
B. format boot, system, data, cache, sdcard or sd-ext
These let you directly format any of these partitions. Take extreme care with this option as formatting any of these partitions will result in losing all data on them, especially the boot and system partitions. Formatting the system partition will remove your ROM and leave your phone without an operating system while wiping the boot partition may brick your phone unless you restore or flash another one before rebooting your device.
What's lucky is that Galaxy Ace users don't have the option to format the boot partitions.
C. mount USB storage
Lets you enable USB mass storage mode for your SD card right from recovery so that you can connect it to your computer via USB and transfer any files to/from it without having to leave recovery.
8. advanced
This section contains a few options most users will not require, though these can come handy quite often, especially wiping Dalvik cache, which is required before most ROM installations. Here are the options from this section:
A. Reboot Recovery
Lets you directly and very conveniently reboot from recovery right back into recovery. This is a useful option for certain back-to-back installations that require the device to at least boot once between them OR installing another version of CWM (like v5.2.0.6).
B. Wipe Dalvik Cache
Allows you to wipe the cache for the Dalvik virtual machine (the custom-built Java virtual machine for Android).This is required before most ROM installations and at other occasions too, for fixing some problems.
C. Wipe Battery Stats
Wipes the saved battery usage statistics and effectively recalibrates the battery. Useful in various scenarios when Android isn’t showing correct battery levels.
*This style of wiping battery stats is no longer useful*
D. Report Error
In case of errors, this feature can be used to save a log of recent ClockworkMod recovery operations on the SD card that you can later report from Android using ROM Manager.
E. Key Test
Lets you press any of the hardware keys to see if they are properly functioning, and to see their key codes.
F. Partition SD Card
This option gives you a no-frills way to partition your SD card properly for use with ROMs that supports a2sd (a hack that moves entire applications to the SDcard). Once this option is selected, you will be given options to choose the sizes for the /sd-ext partition as well as an optional /swap partition on the SD card, and will then automatically format it for you, leaving the remaining space for normal SD card usage. This option will wipe all data from your SD card so use it with caution!
G. Fix Permissions
Fixes the file permissions for the internal memory partitions back to default. This is very useful as a fix for several errors and Force-Closes that start appearing after you or an application you installed and provided root access end up messing up the permissions of important files.
Hope it helps :d
Click to expand...
Click to collapse
It certainly helped my friend
Q3: Help me, my phone is in a bootloop and won't go into the Launcher!
A3: Firstly , define your bootloop:
If you are stuck at the "Galaxy Ace" logo , that means you did not make a factory reset and cache wipe from Recovery Mode . Do that , then reflash and try again .
If it still does not work , your kernel might have a problem because you did not install your kernel properly .
For that I recommend CF-ROOT for Gingerbread and Froyo
However , if your phone is stuck at the bootanimation:
Stuck for more than 10mins and is repeating the animation: You did not flash your ROM properly . Refer to above .
Stuck for less than 10mins and is NOT repeating: I suggest you have some patience
Q4: AHHHHHHHH! I flashed a theme but now my phone is going into force closes and bootloops!!!!!!!!!!!!!!
A4: You probably flashed a theme that was meant for another firmware version (E.g. flashing a KPH theme into KPO) .
In that case , all you have to do is flash another theme which is for that particular firmware and you're saved
Everytime I flash a theme I will make a backup prior to installing . This ensures that I can restore back if I did something wrong
Q5: Is there any overclock for the Galaxy Ace?
A5: With CF-ROOT 3.7 b83 I can achieve 100% stability with 902Mhz but 10% decrease in battery life :/
Q6: What about Adobe Flash support?
A6: It is only PARTIALLY supported on CyanogenMod 7 , but may work on stock Samsung ROMs if on Cf-root .
It works on the stock browser and Dolphin Browser HD , but does not work on Opera .
Q7: What is Cyanogenmod? Why do so much people love it?
A7: Cyanogenmod is a ROM built from a modified generic AOSP build , which offers faster speed , better stability and even eliminates some problems induced by stock ROMs (i.e. In our case , the Sleep of Death a.k.a SoD) .
This ROM was made by none other than the legendary Cyanogen .
This makes the phone fast , stable and yet problem-free .
however , CM7 for the Ace is currently unofficial and in early release candidate and beta versions and is NOT recommended for newbies as they might encounter into problems they might not know how to solve .
Also , the things that were added by Samsung WILL NOT APPEAR in Cyamogenmod 7 .
If you rely on Samsung's additions too much , I suggest that you revert back to stock
Q8: Oh no! My phone is bricked! I accidentally flashed the wrong device in ROM Manager!
A8: Oh no . You might wanna try either:
Method 1:
-Remove the SIM card , SD card and battery from the phone
-Hold Volume Down + Home + Power
-(Optional) Bring it near a heat source .
-While still holding those buttons , place the battery into the phone
-It should go into Download Mode .
-Try to flash a full package file via ODIN and your phone should come back to life .
If that doesn't work , try Method 2:
-Bring the phone to a nearby service center for repair .
Q9: Hello, what's the difference between a full package ROM and a one package ROM?
A9: When you download a ROM from SamMobile , they have all the files in a .rar , the contents of the .rar determine its Package:
A Full Package ROM has quite a few files when the .rar is opened , one of them being a .tar.md5 if I remember correctly .
A One Package ROM only has one .tar file when the .rar archive is opened .
Q10 by scoffyburito:
scoffyburito said:
Err sorry if this sounds dumb but what version of CWM would i need if when im restoring my cm7 backup it says Md5 mismatch. I made the backup on CWM 5.0.2.6?
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
A10: Taken from http://forum.xda-developers.com/showthread.php?t=714114
ihtfp69 said:
I figured I would post this fix here in case anyone else ran into this problem. This is assuming you did not change the folder names and let Clockworkmod create them. I haven't had it happen until today, but it's not a nice message to see when you are trying to do a restore.
Code:
Checking MD5 sums...
MD5 mismatch!
To fix this problem use the code below. Substitute the final folder name for the backup you need to fix.
Code:
adb shell
# cd /sdcard/clockworkmod/backup/[I]backupname[/I]
# rm nandroid.md5
# md5sum *img > nandroid.md5
When that finishes, re-run the restore and everything should be fine.
NOTE: As rpearl stated, there could be something really wrong with your nandroid, so use this tutorial as a learning experience and not a fix-all. In my case, everything was fine after restoring. However, that may not always be the case. Do this with caution.
Click to expand...
Click to collapse
Q11 by psychoo118:
psychoo118 said:
Hey guys! I'd like to ask that is there any way to get my warranty back if I flashed CyanogenMod 7.1 Cooper Kang? :/ Fortunately, I don't need my warranty now, only asking if i will in the future Thanks
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
A11: Just flash back to DXKC1 (Froyo 2.2.1) or the Gingerbread version for your region , you're bound to fool Samsung
Q12: I have been hearing everyone talk about this file named build.prop. What is that?
A12: Okay, build.prop is the build properties of your current ROM.
I will give more explanation of the different entries as time goes on (LOL).
ro.ril.disable.power.collapse - (0/1) Variable Values.
0: Allows the network power collapse, thus wasting battery
1: Disables the network power collapse, thus saving battery.
ro.ril.hsxpa - (0/1/2/3)Variable values.
0: Disables HSUPA completely.
1: Disables stock HSUPA speeds (speeds capped)
2: Enables stock HSUPA speeds (speeds capped)
3: Enables uncapped HSUPA speeds
Q13: What is CF-ROOT? Is it edible?
A13: LOL no it isn't! CF-ROOT is short for Chainfire-Root (a.k.a Rooting + some tweaks). It has root and installs 3 apps: CWM Manager, Superuser and Tweaks.
CWM Manager is a substitute for ROM Manager and allows:
- Rebooting to recovery
- Backing up using app
- Restore using app
- Deleting backups
- Flashing .zip files
- Flashing zImage kernels (a.k.a CF-ROOT fixes)
The current version is b84, which is only for XWKT5/7 firmwares.
You can use b83, which is the universal CF-ROOT.
Q14: I keep running out of internal memory. Why does this happen? How do I solve it then?
A14: It is because the Galaxy Ace's internal memory is only less than 200MB, therefore too many apps will cause the phone to run out of memory. There are 3 known solutions to that:
1: DarkTremor's Apps2SD (DTA2SD)
- Most commonly used way of moving apps to internal memory
- Has an app for it at the Android Market (A2SDGUI)
- Uses a flashable zip (find it in XDA)
- Easiest to use among the 3
2: link2SD
- Makes use of symbolic links to move apps to the SD-ext partition
- I don't know much about this one
3: S2E (simple2ext)
- An app that's available in the Android Market
- Only for CM7 ROMs and the only one working for Ice Cream Sandwich (by maclaw)
- Hardest to use among the 3
That is all.
Q?: This thread seems inactive! When will you update it?
A?: I will update my thread whenever I want to , once I find new information .
Thank you for reading this thread so that one less Galaxy Ace gets bricked
For me, this should be a sticky post on development.. Maybe you need to request this as sticky post from any MOD and update all about Ace there..
izzoe said:
For me, this should be a sticky post on development.. Maybe you need to request this as sticky post from any MOD and update all about Ace there..
Click to expand...
Click to collapse
Uhh.....can you help me , because I don't know any of the MODs here
The only mod here... Has been retired better ask senior moderators...
Sent from my GT-S5830 using XDA App
fla.sh said:
The only mod here... Has been retired better ask senior moderators...
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
Explain Univos' Mod Edit in the thread
Unfortunately there's no report for sticky in this forum, which is a bit poor.
russ18uk said:
Unfortunately there's no report for sticky in this forum, which is a bit poor.
Click to expand...
Click to collapse
Sigh , so that means the chances of a sticky are gone huh ?
Sent from my Awesome Galaxy Ace S5830 with XDA App
EmoBoiix3 said:
Sigh , so that means the chances of a sticky are gone huh ?
Sent from my Awesome Galaxy Ace S5830 with XDA App
Click to expand...
Click to collapse
Nah, just manually PM a mod
russ18uk said:
Nah, just manually PM a mod
Click to expand...
Click to collapse
I'm kinda shy when it comes to such stuff
Sent from my Awesome Galaxy Ace S5830 with XDA App
Just PM a mod I had the luck to read the failures of others, by that way saving my ace (even though i wasnt planning on installing it).
+1 for sticky
QNBT said:
Just PM a mod I had the luck to read the failures of others, by that way saving my ace (even though i wasnt planning on installing it).
Click to expand...
Click to collapse
Oh well
Sent from my Awesome Galaxy Ace S5830 with XDA App
i have an Acer Iconia A500 and when i open Rom Manager for the confirmation of my model i see that there is Samsung Galaxy Ace but when i do exactly the same thing with my Ace i cant see it. its the same version (premium v4.3.3.0)
sorry for my english
EmoBoiix3 said:
This serves as a warning to all the new users in the XDA forums .
ROM Manager is a manager for Clockworkmod Recovery , which saves time because you don't have to reboot to recovery .
However , it doesn't support Galaxy Ace yet .
You can probably use CWM Manager instead , which is included in most custom ROMs .
Clockworkmod Recovery , on the other hand , supports Galaxy Ace with many versions (with the official one being v4.0.0.9) .
REMEMBER THIS , DO NOT INSTALL/DOWNLOAD ANYTHING WITH ROM MANAGER . Use Clockworkmod Recovery for Backups , Restoring , Flashing .zip or whatever the Recovery can do .
IF YOU TRY TO INSTALL ANYTHING USING ROM MANAGER YOU MIGHT NEED TO BRING YOUR PHONE AND WARRANTY CARD TO THE NEAREST SERVICE CENTER .
Additional information by fla.sh about Busybox (with some grammar changes ):
Click to expand...
Click to collapse
Hey man,
great thread. Thnx
biupil said:
i have an Acer Iconia A500 and when i open Rom Manager for the confirmation of my model i see that there is Samsung Galaxy Ace but when i do exactly the same thing with my Ace i cant see it. its the same version (premium v4.3.3.0)
sorry for my english
Click to expand...
Click to collapse
Different phones have different CWMs . (I thought your were talking about CWM v4.3.3.0 , but you were talking about ROM Manager v4.3.3.0 instead )
Sent from my Awesome Galaxy Ace S5830 with XDA App
EmoBoiix3 said:
Different phones have different CWMs . (I thought your were talking about CWM v4.3.3.0 , but you were talking about ROM Manager v4.3.3.0 instead )
Sent from my Awesome Galaxy Ace S5830 with XDA App
Click to expand...
Click to collapse
yes i was talking about ROM Manager v4.3.3.0 my bad.
but why do is see my phone(ace) in the list of A500 and not in my ace? its the same version of the same program
biupil said:
yes i was talking about ROM Manager v4.3.3.0 my bad.
but why do is see my phone(ace) in the list of A500 and not in my ace? its the same version of the same program
Click to expand...
Click to collapse
That's a good question . Could you post a screenshot ?

[PORT][ROM][BETA-2][4.4.4] MIUI v6 for Android One 1st gen

Hello guys, just sharing my first porting work to u all
Please read this post from first to the end of this post
"Please respect to my work,
I'm doing this fix all alone by
giving up my rest time, quota (since i didnt have wifi), etc..
so dont complain if u find any bugs, or
a lil bit hassle to install it.
if u find any, just report it to me
if it's possible to fix,
i will try to make a patch / troubleshoot updates."
Click to expand...
Click to collapse
NOTE : DO THIS AT YOUR OWN RISK
Changelogs :
ROM :
#> BETA 2 - 20151213
- Fixed META-INF problem, can flash using any recovery now except stock
- Fixed Completely selinux problem
- Fixed Camera and screen issues on other A1 devices (ex Mito Impact a10)
- Fixed Flashlight
- Fixed Bootloop at first time install (dont need to wipe dalvik again)
- Fixed Offline charging
- New kernel and ramdisk
- some other patches and minor fix
#> BETA 1 - 20151211
- Fixed RIL (only single sim for now)
- Fixed Launcher icons
- Fixed Dialer and Contacts FC
- Fixed Change wallpaper FC
- Fixed some layout
- Fixed MTP
- Fixed Themes FC
- some minor fix and patches
#> DevBuild 1 (Tester Only)
- Initial Release
- All Devices standard features working except (for now) :
RIL (SIM Network/Data Cellular)
- Some of apps fc
Click to expand...
Click to collapse
PATCH :
#> Patch for BETA 2 - 20151220
Fix LED notification
New sqlite_jni [test] : tell if u got any huge sqlite problem in the {logcat} than before patch
Fix weather app
#> Patch for BETA 1 - 20151211
Patched services.jar to disable apps verify
DownloadProvider fix
Click to expand...
Click to collapse
Bugs :
- DUALSIM
- Launcher 4x5 layout bug (use another launcher if u want)
- Google play services sometimes fc. Due to unexpected sqlite problem sometime
- Media stopped working after 5-10 seconds gplay services fc so cant take screenshot and gallery become empty, and in some cases taking screenshot while opening screenshot folder using miuigallery (u need to reboot the phone or wait approx 10-30min)
- Font changing in theme app only works for miui's default browser
- tell me other
Click to expand...
Click to collapse
Download links :
ROMs :
MIUI6_20151213_BETA 2
MIUI6_20151211_BETA 1
GApps :
GApps_miui6_optimized_edition
Patchs :
BETA 2 :
miui6_patch_beta2_20151220
BETA 1 :
miui6_patch_20151211
BOOTLOOP PATCH : miui6_patch_after_flash
BOOTLOOP PATCH : miui6_patch_after_boot
Installation Procedure :
1. Go to recovery
2. Wipe data, cache, system
3. Flash the rom
4. Flash miui gapps
5. Flash the patch (if any)
6. Reboot.
If u are updating from BETA 1 to BETA 2, i recommend to do a wipe data or clean flash to avoid some unexpected issues
BETA 1 Notes :
For you who gettings bootloop at last time, try this :
1. Download these two bootloop patch
2. Rewipe your phone (data,cache,system)
3. Flash the rom, then flash gapps, after that reboot to recovery mode
4. Flash the miui6_patch_after_flash
5. Reboot. Wait till its booting to homescreen (approx 6-10mins)
6. After finishing the setupwizard, go back to recovery
7. Flash the miui6_patch_after_boot
8. Reboot. And ur done
After booting and finishing the setup wizard (and done flashing the bootloop patch if u got bootloop), set selinux to permissive, set using kernel adiutor (go to plugins, download selinux plugin, set to permissive), enable apply on boot
After booting to homescreen u can reput your 2nd card now. but remember its will still didnt detect your 2nd card
Troubleshoot :
1. How to enable root access?
- Open security app, choose permissions, root access .. there u go (make sure ur root apps already asked for root first to show it on there)
2. How to disable warn when want to install app?
- Open Privacy, choose device administration, change in unknown sources from ask to allow
3. How to make my phone mtp detected?
- Unplug ur usb, open miui default file explorer, select phone, wait till its complete loading, then connect ur usb
4. Google apps or keyboard is force closing how to fix?
- Use my miui6_gapps
5. Titaniumbackup is restarting after grant root access, how to fix?
- Update your current tb to version 7.2.1.2 or latest
6. Cant install apps from PS, says no free storage, how to fix?
- Flash the download provider fix
7. Cant install apps from my sdcard, says no free storage, then after i try it its says install failed
- Set your phone selinux to permissive, then use root ex delete the package folder in data/data .. ex Im failed to install bbm, delete the com.bbm folder
8. Cant import theme from sdcard, what to do?
- The new MIUI at default doesnt allow you to apply theme which not from their store, but try other theme, theres some of theme still can be imported
9. Issues with downloading, how to fix?
- Turn off the xunlei download engine at download - settings, also set the limit to unlimited
10. Navbar is too small, how to fix?
- If u want alternative, use MiPop 2.0 .. im reduced its size due to fix some of layout bugs. To remove the navbar add "qemu.hw.mainkeys=1" without " in the bottom of the build.prop then push Mipop.apk to system/priv-app
11. How to show messenger chat heads?
- Download app-ops app from playstore, install then reboot, after that search for messenger permission, enable the draw over blabla permission : thanks to Kishan Kumar for the guide
How to Install Video Review, thanks to Sounak Pal :
Here
To appreciate my hard works, you can consider giving me some donations by :
Giving some steam wallets : nteztaz
or if u at Indonesian country, u can send me some credit balance to buy quota,
msg me for my call number
Credits :
[email protected] for the rom base
Yusuf Maulana for the idea of porting from 'based cm11'
Sounak Pal for the video review
All my Tester
All Android One users
Me (TezTaz Si Rama)
A huge thanks for this Rom was waiting for different ui.
It would be great if u will provide some screen shots
Screenshots
I havent found any fc
Hoping that the sim bug will be fixed soon
I dont mind using the Single SIM as I use it for single sim most of the time. Thank you for sharing it here. I'm downloading it now.
an awesome rom
This is the best rom I have ever used on my Sparkle V. Very smooth ,
but I found a bug - while backing up data on local storage the phone hangs and reboots itself in a minute, but that's not a major issue.:good:
guys, I tried flashing, but failed. ,
- first I tried wipe everything, and then flash. But flash or rom failed, giving sole softlink issue. I tried multiple times, but failed. Finally, fixed issue by having another 4.4.4 rom installed first and then flashing this rom without wiping system
- once flash was successful, I rebooted device, but it keeps looping wihout booting up. OP suggested multiple iterations of (battery remove, goto recovery, wipe dalvik, boot) , but I am in my 7th attempt and device not booting still.
How many times you guys had to wipe dalvik? Very much anxious to test this MIUI rom !
Flash why philz
Do not flash gapps it was bootlooping
yadavdharmendar said:
Flash why philz
Do not flash gapps it was bootlooping
Click to expand...
Click to collapse
thanks @yadavdharmendar, I am installing from philz, and I avoided installing gaps as well. Still not luck. I get Simlink error.
I am coming from FIUI rom. Not sure if that matters (as anyway I am wiping everything before starting rom flashing).
I was on Fiui too
Then i flash cm11 ,then miui
yadavdharmendar said:
I was on Fiui too
Then i flash cm11 ,then miui
Click to expand...
Click to collapse
thanks! But why you installed CM11 first before installing Miui. OP didn't asked for it. Just curious to know!
And where you got CM11 from? From Cyanogenmod download page for "sprout"?
mobilepgk said:
guys, I tried flashing, but failed. ,
- first I tried wipe everything, and then flash. But flash or rom failed, giving sole softlink issue. I tried multiple times, but failed. Finally, fixed issue by having another 4.4.4 rom installed first and then flashing this rom without wiping system
- once flash was successful, I rebooted device, but it keeps looping wihout booting up. OP suggested multiple iterations of (battery remove, goto recovery, wipe dalvik, boot) , but I am in my 7th attempt and device not booting still.
How many times you guys had to wipe dalvik? Very much anxious to test this MIUI rom !
Click to expand...
Click to collapse
Its not davlick issue it's just meta inf folder bug
Just open ROM zip and delete meta inf folder and replace it from any downloaded sprout ROM zip just copy meta inf folder frm there and paste it in miui ROM n u r done just do a clean install n w8 for 5 mins
teztaz--v3 said:
Hello guys, just sharing my porting work to u all
"Please respect to my work,
I'm doing this fix all alone,
so dont complain if u find any bugs,
if u find any, just report it to me
if it's possible to fix,
i will make a patch updates."
Changelogs :
Bugs :
Download links :
ROMs :
Here
MIUI GAPPS :
soon
Patchs for Download Provider :
Here
Installation Procedure :
1. Remove your 2nd sim card, then go to philz recovery or LATEST (2.8.7.x) TWRP recovery (darkplay)
2. Wipe data, cache, system (or just use the 'clean to install rom' function)
3. Flash the rom
4. Flash miui gapps
5. Flash patch
6. Reboot, wait till 6 mins, pull your phone battery, then goto recovery and wipe dalvik cache, then reboot*
7. After booting and finishing the setup wizard, set selinux to permissive, set using kernel adiutor, enable apply on boot
*do it again until the progress bar bottom of the screen showing
Troubleshoot :
1. How to enable root access?
- Open security app, choose permissions, root access .. there u go (make sure ur root apps already asked for root first to show it on there)
2. How to disable warn when want to install app?
- Open Privacy, choose device administration, change in unknown sources from ask to allow
3. How to make my phone mtp detected?
- Unplug ur usb, open miui default file explorer, select phone, wait till its complete loading, then connect ur usb
4. Google apps or keyboard is force closing how to fix?
- Change your gapps, use pico/nano gapps for now
5. Titaniumbackup is restarting after grant root access, how to fix?
- Update your current tb to version 7.2.1.2 or latest
6. Cant install apps from PS, says no free storage, how to fix?
- Flash the download provider fix
7. Cant install apps from my sdcard, says no free storage
- Wipe data your phone, reflash again, after boot set selinux to permissive
Credits :
[email protected] for the rom base
Yusuf Maulana for the idea of porting from 'based cm11'
All my Tester
All Android One users
Me (TezTaz Si Rama)
Click to expand...
Click to collapse
not downloading rgt now....will instead wait for another a bit stable build...a salute to your work...hope ur working on fixes...already pressed thanx button...keep going boy...
Thanks all. Installed cm11, then installed ROM with the patch, and avoided flashing any gapps. It worked! Just one bootloop, which went away after wiping dalvik.
Thanked OP!!
BTW, any ways to make the navigation buttons look big. And possibly increase bar height?
about 2nd sim
bro plz plz get 2nd sim working.
thanks for your work and you are awesome.
@teztaz--v3
how to make navigation bar transparent ?
and a big thanks for your beautiful awesome work
no FCs seen so far!! Looks perfectly usable as daily rom.
Just one problem seen :
Can not install Google maps. Says insufficient space, which is strange. Also failed to install Link2SD. Tried even installing from ADB, gave error INSTALL_FAILED_UID_CHANGED. Hope Miui is not blocking it.
Every thing is fine bro its super rom but I can't move apps to SD card
Thanks bro! gr8 work! bt can u make e single zip with all fixes? people will get confused with so many patches
nsytechno96 said:
bro plz plz get 2nd sim working.
thanks for your work and you are awesome.
Click to expand...
Click to collapse
B'coz this ROM is based on CM11, it's impossible to get multi sim working

[Dualboot Patcher]Full Guide For How To DualBoot Your Note 4 (EXY/SD)

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

Categories

Resources