Develop Bugs

[Q] Im new to Android

HI
I have just bought Xperia Arc S LT8i nd the normal android version is gingerbread ! i cant update the ICS version which is rolled out quite a time ago as my phone say its the latest updated !
now my question is, what tool i need to flash nd where can i find the best ROM or someone can update nd send me easy understanding links for a newbie
I use WIN7 64 bit version
Please help

stab2 said:
HI
I have just bought Xperia Arc S LT8i nd the normal android version is gingerbread ! i cant update the ICS version which is rolled out quite a time ago as my phone say its the latest updated !
now my question is, what tool i need to flash nd where can i find the best ROM or someone can update nd send me easy understanding links for a newbie
I use WIN7 64 bit version
Please help
Click to expand...
Click to collapse
Search for flashtool guide (for noobs). I hope this will get you there. Remember one of the most important rules here is 'search before posting'.
I hope you'll like it here

OK, so first you have to know I'm not one of those over experienced guy as I just bought my LT18i a month ago (wa on iPhone before).
I made a few mistakes in the process the first time, bricked my phone and stressed as hell before I finally repaired it.
Here is what you need to know if you want to avoid usual errors :
1 - There are 2 ways to proceed :
- With OR
- Without unlocked bootloader
(I only know how to do with an unlocked bootloader)​
2 - To upgrade to ICS you have to take 3 things in considerations :
- The Kernel (core of the phone system, supports ROMs)
- The ROM (Operating System of your phone, often with a patch for LT18i)
- The Baseband (System overlay that supports communications)​
3 - The tool used to flash ROMs, Basebands and Kernels with an unlocked bootloader is Flashtool.
4 - To authorize your phone to be flashed (modify the system memory) you'll have to plug it to your computer in Fastboot mode.
Turn off phone -> Plug to computer -> Press Menu button during boot -> Turn on phone -> Screen should be black and LED blue.
You'll need drivers for your phone to be actually recognized by Flashtool.​
5 - My personnal choice for ROMs is Arconium ICS 4.0.x (based on the stock ROM) which is supported by Xarc or ArcKnight kernels. Those two work with the baseband 72 ( you may currently have 64, search in Settings -> About Phone)
6 - The overall process should be like :
Unlock your bootloader (http://unlockbootloader.sonymobile.com / you may loose guarantee)
Get the latest version of Flashtool (v 0.8.sthg) and needed drivers for LT18i
Get the kernel, ROM, and baseband you chose (still keep in mind that they must be all 3 compatibles, look at specifications)
Have your phone charged (at least over 50~60%)
Download and install ROM Manager in Google Store
Copy your ROM and patch in your SD card (wherever you want)
- Plug your phone in fastboot mode and open Flashtool (drivers installed, obviously)
- Flash your kernel
- Flash your baseband
- Unplug and power up phone
- Go to ROM Manager and reboot in Recovery
- Clean UserData, Wipe cache, use every "wipe/erase stuff" command you see, this usually work
- Choose option "Install zip from SD Card" -> "your main ROM"
- Choose option "Install zip from SD Card" -> "your patch" (Don't swap those 2 steps or you'll brick your phone)
- Reboot
I think that's all I can provide to you, the hardest part being to find all necessary links. But I still believe it's a good summary of all you'll have to do to get your phone on ICS, from A to Z.
Sorry if i can't provide the very details (links, software or recovery mode step by step, ... ) but as I said before, I'm not an expert and I'm still in the process too !! (see http://forum.xda-developers.com/showthread.php?p=28006082)
Hope it'll be helpfull, and others can guide you if you don't find the rest by yourself !
Regards,
Minikrob

minikrob said:
OK, so first you have to know I'm not one of those over experienced guy as I just bought my LT18i a month ago (wa on iPhone before).
I made a few mistakes in the process the first time, bricked my phone and stressed as hell before I finally repaired it.
Here is what you need to know if you want to avoid usual errors :
1 - There are 2 ways to proceed :
- With OR
- Without unlocked bootloader
(I only know how to do with an unlocked bootloader)​
2 - To upgrade to ICS you have to take 3 things in considerations :
- The Kernel (core of the phone system, supports ROMs)
- The ROM (Operating System of your phone, often with a patch for LT18i)
- The Baseband (System overlay that supports communications)​
3 - The tool used to flash ROMs, Basebands and Kernels with an unlocked bootloader is Flashtool.
4 - To authorize your phone to be flashed (modify the system memory) you'll have to plug it to your computer in Fastboot mode.
Turn off phone -> Plug to computer -> Press Menu button during boot -> Turn on phone -> Screen should be black and LED blue.
You'll need drivers for your phone to be actually recognized by Flashtool.​
5 - My personnal choice for ROMs is Arconium ICS 4.0.x (based on the stock ROM) which is supported by Xarc or ArcKnight kernels. Those two work with the baseband 72 ( you may currently have 64, search in Settings -> About Phone)
6 - The overall process should be like :
Unlock your bootloader (http://unlockbootloader.sonymobile.com / you may loose guarantee)
Get the latest version of Flashtool (v 0.8.sthg) and needed drivers for LT18i
Get the kernel, ROM, and baseband you chose (still keep in mind that they must be all 3 compatibles, look at specifications)
Have your phone charged (at least over 50~60%)
Download and install ROM Manager in Google Store
Copy your ROM and patch in your SD card (wherever you want)
- Plug your phone in fastboot mode and open Flashtool (drivers installed, obviously)
- Flash your kernel
- Flash your baseband
- Unplug and power up phone
- Go to ROM Manager and reboot in Recovery
- Clean UserData, Wipe cache, use every "wipe/erase stuff" command you see, this usually work
- Choose option "Install zip from SD Card" -> "your main ROM"
- Choose option "Install zip from SD Card" -> "your patch" (Don't swap those 2 steps or you'll brick your phone)
- Reboot
I think that's all I can provide to you, the hardest part being to find all necessary links. But I still believe it's a good summary of all you'll have to do to get your phone on ICS, from A to Z.
Sorry if i can't provide the very details (links, software or recovery mode step by step, ... ) but as I said before, I'm not an expert and I'm still in the process too !! (see http://forum.xda-developers.com/showthread.php?p=28006082)
Hope it'll be helpfull, and others can guide you if you don't find the rest by yourself !
Regards,
Minikrob
Click to expand...
Click to collapse
Thank you for this reply it almost covers all aspects ! one more question is the phone has front face camera and if not then how it will support skype video !

stab2 said:
one more question is the phone has front face camera and if not then how it will support skype video !
Click to expand...
Click to collapse
arc s has front camera? no(dont you know it before you buy arc s?)
skype vid? maybe

Skype can use the rear camera for video calls.
Swyped from my SE Xperia arc (LT15i) using Tapatalk 2

[GUIDE] Huawei Ascend P1 U9200 AIO

U9200 AIO guide
This guide is made by me, but I've collected information from many others.
Special thanks to: arkedk, Urmet77, lee140685, faust93, spanorg, kiprap and others.​
First of all:
1. I am not responsible for ANY bricked device! You are doing this at your own risk.
2. Downloads are located here. Most of my uploads are heavily compressed by 7zip. Only 7zip will unzip correctly.
3. Install ADB and FASTBOOT drivers for making stuff in this guide work. Very easily done with: 15 seconds ADB Installer by Snoop05 @ xda
Eventually: Android SDK | Guide by demkantor | Guide by TeamAndroid
4. Backup stuff you want to keep. Easy with tools such as: MyPhoneExplorer, Super Backup, Titanium Backup or others. (Use Google)
5. Other things you should know:
→ Reboot phone to recovery: Turn on while holding volume up + volume down. Or through ADB: "adb reboot recovery"
→ Reboot phone to fastboot: Turn on while holding volume down. Huawei logo will appear and won't disappear. Or through ADB: "adb reboot-bootloader"
→ Shut down phone if it freezes: Hold power button until dead.
→ For ADB to work, debug mode must be enabled, and you must choose "Hi suite" as USB connection mode.
→ Some Huawei ICS ROM's comes without the FM radio app. If you want it, you can install this apk. NB: ONLY ICS (Android 4.0.X). For JB: B704 was the first version to include FM radio.
Here is "ascend-p1" forum category on xda: https://forum.xda-developers.com/t/ascend-p1​
Gain root access (Works on ANY Huawei stock firmware. Inspiration taken from arkedk's thread)
TWRP has the ability to root our device, regardless of firmware version!
1. Download TWRP v2.6.3.0 (img). Unzip it, and place the .IMG in "C:\Program Files (x86)\Android\android-sdk\platform-tools" folder.
2. Turn off your phone. Restart it while holding volume down (Fastboot mode). Connect your phone via USB. (ADB: adb reboot-bootloader)
3. In the "C:\Program Files (x86)\Android\android-sdk\platform-tools"-folder, hold shift while right click. Choose "open command window here".
5. Write "fastboot devices" to verify that the computer detects your device. If not detected, you failed install Fastboot drivers. (Look at the top of this guide)
6. Write "fastboot flash recovery recovery.img". This will flash/ install TWRP to your device. (Given that your recovery file is named recovery.img)
7. Boot into your new recovery, TWRP. (Volume + and - together at startup)
→ Go to the "Mount" menu and mount System.
→ Then go to the Reboot menu and reboot the system.
→ When it detects you are not rooted, TWRP will ask if you want to root.
→ Swipe to do so and let it boot back into the system.
8. Hit the SuperSU icon and let it setup for the first time. Either by downloading a flashable zip or by going to the Play Store. Both methods works.
9. You should now be rooted! ​
Install/flash stock or custom recovery. (Root not required.)
1. Download the recovery you want. Place the .IMG file in "C:\Program Files (x86)\Android\android-sdk\platform-tools"
2. Turn off your phone. Restart it while holding volume down (Fastboot mode). Connect your phone via USB
3. In the "C:\Program Files (x86)\Android\android-sdk\platform-tools" folder, hold shift while right click. Choose "open command window here".
4. Write "fastboot devices" to verify that the computer detects your device. If not detected, you failed install Fastboot drivers. (Look at the top of this guide)
5. Write "fastboot flash recovery <recovery_name>.img".
→ Let's say the recovery file is named twrp.img. Then you will type: "fastboot flash recovery twrp.img"
6. If unsuccessful, try again, be very careful about typing it right. If successful, write "fastboot reboot" to reboot your phone. You are done.​
Install any Huawei stock firmware, regardless of version (even from custom ROM)
- This will delete everything on your phone's internal memory, and you will loose root.
- The easiest way is by first flashing Intermediate Pack (B123). This is a stock Huawei ROM that will flash regardless of previous firmware version. Any Huawei ROM then will flash straight from Intermediate Pack. No build.prop modifications needed!
- Chinese versions don't have GAPPS installed. This must be installed through a custom recovery after flashing the firmware.
1. Grab "Intermediate Pack", desired firmware version, intermediate FashPack. Links in bottom of this guide.
2. Take the RECOVERY.IMG out of intermediate FlashPack, and Install it through the steps above. (fastboot flash recovery recovery.img)
3. Place "Intermediate Pack" UPDATE.APP on your SD-card. The file structure MUST be: (Root of SD-card) dload\UPDATE.APP
4. Boot into recovery (Volume up+down when powering on the device). This should start flashing procedure of B123, Intermediate Pack. If it doesn't work and you come from a custom ROM, you must change build.prop to the one included in Intermediate Pack FlashPack. See "FAQ" on how to replace build.prop.
5. After install, it will boot. Now switch the UPDATE.APP from Intermediate Pack with the one from desired firmware version. ((Root of SD-card) dload\UPDATE.APP)
6. Boot to recovery. The firmware flashing procedure will start.
Chinese version extra instructions. This is the time to install GAPPS! B704 extra instructions! arkedk has made a zip to enable all languages in B704. Grab Enable all languages in B704, by arkedk
→ FIRST boot the phone after the firmware installation has succeed.
→ Grab GAPPS corresponding to your android version. (I recommend miuiandroid.com's GAPPS lite, as they removed all unuseful stuff) Place the .zip on the sd-card. Place language enabler.zip on the sd-card as well
→ Install a TWRP v2.4.4.0 recovery
→ Boot into recovery. Install GAPPS.zip. Install language enabler .zip as well
→ Reboot. TWRP will ask you if you want ROOT access. Entirely up to you! For the language enabler to work, you must do a device reset. Relax, GAPPS should be there after the reset.
7. Done! If you want root access, check root guide on top. You can remove Chinese system apps with Uninstall Master. Weather, baidu, and Chinese market won't work outside china anyway. REQUIRES ROOT!​
OLD METHOD
Install any Huawei stock firmware, regardless of version (even from custom rom) B229 is a bit different. See "FAQ" at bottom.
This will delete everything on your phone's internal memory, and you will loose root.
Your phone must be rooted for this method to work (replacing/modifying build.prop. Check FAQ about build.prop if you have any questions)
1. Grab firmware (UPDATE.APP), recovery.img and build.prop (Both included in attached FlashPacks) for desired firmware version. Links in buttom of this guide.
2. Place UPDATE.APP on your SD-card. The file structure MUST be: (Root of SD-card) dload\UPDATE.APP
3. Install recovery through the steps above.
4. Download and open "Universal Android AIO Flasher Tool$" to replace build.prop:
→ A: Open desired build.prop in notepad, notepad++ or similar. Copy everything.
→ B: Connect phone in ADB mode (See "First of all" ↑ ).
→ C: Open "Universal Android AIO Flasher Tool$". Go to "Build.prop Editor"-tab
→ D: Insert what you copied into the empty text field.
→ E: Click the "save" button and then "Flash to device". You must grant access with SuperSU (or whatever superuser access management tool) on your phone.
→ F: If successful, you must click "Reboot device" for the changes to take effect. Let the phone reboot.
Manually: "adb pull /system/build.prop" to get the build.prop from your phone.. "adb push build.prop /system/build.prop" to push build.prop to device. "adb reboot" to reboot it (Must be done)
5. After reboot, check "Settings -> About" to check if stated firmware version has been changed to the one you want.
6. Turn off your phone. Restart while pressing volume up + volume down. The firmware flashing procedure will start. If not, you have done something wrong.
7. Done.​
Install custom firmwares/ROMs (Root not required)
- This will delete everything on your phone's internal memory. Backup stuff you want to keep.
- All custom ROMs i know is pre-rooted, so nothing to worry about there!
- You will need custom recovery for this to work. Look above.
Depending on firmware, GAPPS (Google Apps) might not be included and must be flashed afterwards if it's wanted. I recommend miuiandroid.com's GAPPS lite, as they removed all unuseful stuff
1. Download desired 3rd-party firmware, it must be a CWM/TWRP flashable .zip. Place it on you memory card. If you're flashing GAPPS aswell, place gapps.zip on the memory card too.
2. Reboot you phone to recovery.
3. Wipe everything the custom firmware needs to have wiped. Generally cache, dalvik and user data.
4. Flash the firmware .zip. Wait for everything to finish!
6. Restart the phone. It will use alot of time the first time. If it uses more than, let's say.. 7 minutes, something is wrong (bootloop).
You can eventually try these steps:
→ Wipe cache, dalvik and userdata with CWM.
→ If this does not solve the problem, check the files and reflash. If it still bootloops: The files don't work with U9200.
If you are going to flash GAPPS, now after the first boot is the time to do it. Boot into recovery, then flash the GAPPS .zip corresponding to your firmware version.
7. Restart and enjoy!​
"Ey, Olav! Do you know any other useful stuff I can do to my rooted phone?"
These settings can be edited by using the app Root Browser, for instance.
Boost GPS performance by changing default server to the respective one for your country. Should make the GPS faster and more precise.
The file holding this information is located in: /system/etc/gps.conf
Find respective gps server (NTP) here: http://www.pool.ntp.org/zone/@
I'm from Norway. My customized gps.cfg looks like this:
Code:
NTP_SERVER=no.pool.ntp.org
XTRA_SERVER_1=http://gllto.glpals.com/4day/glo/v2/latest/lto2.dat
XTRA_SERVER_2=http://gllto.glpals.com/4day/glo/v2/latest/lto2.dat
XTRA_SERVER_3=http://gllto.glpals.com/4day/glo/v2/latest/lto2.dat
# SUPL_HOST=supl.google.com
# SUPL_PORT=7276
Fix GPS log bug found in some Huawei ROMs. There seem to be a bug, where stock Huawei ROMs will create huge unnecessary GPS logs, that eventually will fill your entire SD card with trash! (We are talking several 100 MB's of logs!).
Disable log keeping by editing a setting in this file: /system/etc/gpsconfig.xml.
Edit: "cLogEnabled" from "true" to "false". Then delete all the logs in: system/data/gps/log.​
FAQ
Install latest baseband version
Why? Baseband / radio.img is the software controlling everything that has to do with signal. Newer baseband versions can boost your performance + make battery last longer. It might make things worse, but generally newer means better.
How? There is no way to extract radio.img from Huawei firmware at this point. So only way to do this is through flashing a stock firmware from Huawei containing the baseband (radio.img) version you want. (New firmware sometimes includes updated baseband version). If you want custom firmware/ROMs you can flash them over it, baseband version will remain/ radio.img/baseband is not included in custom firmwares/ROMs. Flashing any Huawei firmware will replace baseband with its own version.
For flashing procedure, see "Install any Huawei stock firmware, regardless of version you are on (even from custom rom)"
GAPPS
Why? You want Google applications, but it's not included in the ROM you've flashed.
Which? GAPPS is made for every android version (ICS=4.0.x, JB=4.1.x/4.2.x). Make sure you pick the right one! (Links in download section). I recommend OpenGapps Pico. Heavier GAPPS will make your device much slower.
How?
- Download GAPPS.zip, move it to your memory card.
- Use custom recovery such as CWM or TWRP to flash it.
Remember:
- Has to be done after the ROM is flashed (obviously) and it's recommended to boot the ROM once before flashing GAPPS.
- All Huawei stock firmwares (Except Chinese versions) have this preinstalled.
What does "Root"/"Root access" mean?
- System files is not editable on stock firmware. Editing these can potentially make your phone into a brick. To remove these restrictions follow the steps in my guide.
- Rooting will in most cases destroy warranty!
- MIUI, CM and other custom ROMs are pre-rooted[/I]
What is build.prop?
- This is a text file stored on your phone, which tells the phone about what firmware version it has + some other stuff.
Why replace build.prop?
Build.prop stores lots of settings and info about your phone. Changing it is most commonly used for tricking the upgrade procedure to think the firmware on the phone is compatible with the update.
- Huawei firmware updates is restricted to some few firmware versions. But they have made a "Intermediate Pack" which will flash from ANY stock huawei ROM. All huawei ROM's will flash from this intermediate pack without the need of changing build.prop. Think of "Intermediate Pack" as a intermediary for getting the firmware version you want.
- If you come from a custom ROM, and intermediate pack won't flash (verification fail in recovery), you must change build.prop to any stock huawei build.prop for it to work.
How to replace build.prop?
Phone must be rooted!
NB: There's a chance your custom ROM won't boot because of using stock Huawei build.prop with it. In case of updating to Huawei stock firmware, be smart. Flash stock recovery, and add the update.app to SD card BEFORE you change build.prop!
- Get desired build.prop (included in my "FlashPack" files.
- Download Universal Android AIO Flasher Tool$, by "fonehacker".
- Plug your phone in ADB mode. Open the tool above. Go to build.prop tab. Open your recovery. Press save. Then flash it to your device.
- Device must restart for the changes to work. The tool will ask you about this, and you press YES.
(Alternative: Take a custom rom zip (LineageOS for instance), open zip without unzipping (Use 7-zip), delete all the folders in the /system, including build.prop. Drag desired build.prop to /system folder. Flash this file from a custom recovery, such as CWM or TWRP. No root needed.)
What is boot.img for?
- It's a file that get flashed to your boot partition on the phone. This file is managing the booting process of your phone. This file is included in all ROM's, therefore there is no need for manual flashing. If the boot partition get's damaged in any way, flashing a boot.img made for the same firmware can fix it. Don't try boot.img from different firmwares/android version!
Why is boot.img included in your FlashPacks?
- ROM developers might use it for developing new and better roms. If you just are updating your phone, you will have no use for it.
What is EmUI?
- Huawei is making a custom version of android for their phones. This project is named Emotion UI, EmUI in short.
What is latest firmware(s) for my U9200?
- The download section always contains latest version of Huawei firmware. If there is a new version I have not listed, tell me
What's the difference of "boot recovery" and "flash recovery"?
Boot recovery will make your phone boot from the recovery file stored on your computer (Through fastboot, your phone is connected with usb)
Flash recovery will replace what ever recovery you already have on your phone.
Can I remove/change battery?
- It's not meant to be possible as there is no plastic cover you can remove without disassemble the phone. There is a small bolt underneath the SD-card cover. I think that's the place to start if you want to open it. This will most certainly break the warranty. If the phone's hardware misbehave in any way you should contact Huawei or the store you bought it from.
Guides:
→ How to split Huawei firmwares (get boot.img and recovery.img for a given Huawei firmware): http://madmodder.co.uk/huawei_gener...recovery-images-from-most-huawei-firmware.htm
→ How to root and install custom ROM and recovery, by lee140685: https://forum.xda-developers.com/showpost.php?p=33621360&postcount=310
→ Firmwares with flashing guide, by arkedk: https://forum.xda-developers.com/showthread.php?t=2075028
→ How to setup and use fastboot, by demkantor (Absolutely noob proof): https://forum.xda-developers.com/showthread.php?t=2277112
→ How to install and set up fastboot and adb (Android SDK), by Team Android: http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/
<.< Download links is found in a separate post - Click the image below >.>
​
Something's missing? You got feedback? Updates I've not included yet? Anything else? Reply to this thread.
Please press THANKS if this guide has helped you​

Great job,man! Thanks!:good:

This is THE GUIDE! :good:

Re: [GUIDE] Huawei Ascend P1 U9200 COMPLETE
Thanks Olav.
I suksessfulle installed muiu english v. On my p1.works Great.
Sent from my HUAWEI U9510E using xda app-developers app

gifr87 said:
Thanks Olav.
I suksessfulle installed muiu english v. On my p1.works Great.
Sent from my HUAWEI U9510E using xda app-developers app
Click to expand...
Click to collapse
Nice No problem!

Any Non-Huawei screenshots for EMUI? I mean uploaded by users
How's it working generally? Better than stock 4.0.3? Any bugs?
Thx

Great All-In-One for the Ascend P1... Was thinking about doing the same, but then I saw you already did it ...
Great work Olav!

arkedk said:
Great All-In-One for the Ascend P1... Was thinking about doing the same, but then I saw you already did it ...
Great work Olav!
Click to expand...
Click to collapse
Thanks
New EmUI beta, chinese version. B528
Mirror: https://mega.co.nz/#!7oRRlZ5Z!f8jFjj_HgVw1OWRLCbg4vgVloQNgRgNsNHv_f1C-wfY
FlashPack (Includes build.prop, recovery.img and boot.img): https://mega.co.nz/#!O9wjXByA!VzMAVV9zhmC70K9VI7jhwWLlDAs8CnBCvnfrAnVaRyc

o-l-a-v said:
Thanks
New EmUI beta, chinese version. B528
Mirror: https://mega.co.nz/#!7oRRlZ5Z!f8jFjj_HgVw1OWRLCbg4vgVloQNgRgNsNHv_f1C-wfY
FlashPack (Includes build.prop, recovery.img and boot.img): https://mega.co.nz/#!O9wjXByA!VzMAVV9zhmC70K9VI7jhwWLlDAs8CnBCvnfrAnVaRyc
Click to expand...
Click to collapse
perfomance wise, is emui better to miui?

areankim said:
perfomance wise, is emui better to miui?
Click to expand...
Click to collapse
When I tried the jelly bean emui, I thought it was a bit of a ripoff of MIUI. I like MIUI better.
Sent from my U9200 using xda app-developers app

Guys, jst flash to EMUI B528 custom without gapps, and dowlonad the 4.1.x gapss 20121011 but after i flash it, nothing appear.
then i tried the prev version and 20121130, stll nothing. Weird,

areankim said:
Guys, jst flash to EMUI B528 custom without gapps, and dowlonad the 4.1.x gapss 20121011 but after i flash it, nothing appear.
then i tried the prev version and 20121130, stll nothing. Weird,
Click to expand...
Click to collapse
You rooted before flashing GAPPS?

The "power bar"
I flashed B229 to a U9200, it had originally B103 which had been updated to 105. manually edited the build to B226 before updating with cwm. Everything is working fine no problems. Only couple of things are missing. The "power bar" which i use to control wifi, BT etc. power on and off in the notification menu (or what ever it is called, the menu that appears when swiping down from the upper edge) is missing and it is quite handy and I'm used to it. Other is the missing boot animation which i knew will be missing after update but did not care about that originally since other bigger issues in the B10x FWs forced me to update to B229. But if easy to apply and anyone knows the way to restore the animation (restore the looks as much "stock" as possible) i would appreciate. But the "power bar" would be very important, anyone know how to restore that? I have messed around with Android a bit and have installed and used custom ROMs and rooted several phones so using the basic root / fastboot / adb functions is no problem even though I'm no Android/Linux expert.
Thanks in advance for your help!
And thank you Olav for the very nice compilation thread for U9200.

JJVilzu said:
I flashed B229 to a U9200, it had originally B103 which had been updated to 105. manually edited the build to B226 before updating with cwm. Everything is working fine no problems. Only couple of things are missing. The "power bar" which i use to control wifi, BT etc. power on and off in the notification menu (or what ever it is called, the menu that appears when swiping down from the upper edge) is missing and it is quite handy and I'm used to it. Other is the missing boot animation which i knew will be missing after update but did not care about that originally since other bigger issues in the B10x FWs forced me to update to B229. But if easy to apply and anyone knows the way to restore the animation (restore the looks as much "stock" as possible) i would appreciate. But the "power bar" would be very important, anyone know how to restore that? I have messed around with Android a bit and have installed and used custom ROMs and rooted several phones so using the basic root / fastboot / adb functions is no problem even though I'm no Android/Linux expert.
Thanks in advance for your help!
And thank you Olav for the very nice compilation thread for U9200.
Click to expand...
Click to collapse
Check in the Display settings if the "Notification settings" option is checked. See screenshot from the B226 ROM attached. I hope it's still there?

Boot animation can changed with the AIO flasher tool.
Krizzii said:
Check in the Display settings if the "Notification settings" option is checked. See screenshot from the B226 ROM attached. I hope it's still there?
Click to expand...
Click to collapse
I checked, it's not there in B229 wtf

JJVilzu said:
I flashed B229 to a U9200, it had originally B103 which had been updated to 105. manually edited the build to B226 before updating with cwm. Everything is working fine no problems. Only couple of things are missing. The "power bar" which i use to control wifi, BT etc. power on and off in the notification menu (or what ever it is called, the menu that appears when swiping down from the upper edge) is missing and it is quite handy and I'm used to it. Other is the missing boot animation which i knew will be missing after update but did not care about that originally since other bigger issues in the B10x FWs forced me to update to B229. But if easy to apply and anyone knows the way to restore the animation (restore the looks as much "stock" as possible) i would appreciate. But the "power bar" would be very important, anyone know how to restore that? I have messed around with Android a bit and have installed and used custom ROMs and rooted several phones so using the basic root / fastboot / adb functions is no problem even though I'm no Android/Linux expert.
Thanks in advance for your help!
And thank you Olav for the very nice compilation thread for U9200.
Click to expand...
Click to collapse
Read Dddrko's post on page 13 at http://forum.xda-developers.com/showthread.php?t=1694228&page=13, he explained how to restore toggles.with this metod u will also restore original bootanimation.

Hello,
I own an huawei u9200
I would like to flash the B229 ROM on my device running B102.
I find this thread very interesting however I have a problem at the very first step.
I can't install fastboot usb drivers
I've been trying to follow the guide you linked at the top of your post, I had a slight issue with ADB Drivers as well,
I could not make those Google USB Drivers downloaded through Android SDK work, I would get the error telling me those drivers are not developed to work with windows x64. But after checking with the command prompt, it turns out that the drivers I needed were already installed and the device is detected as ADB Device.
Back on my current issue:
I understand that I have to shut down my phone and switch it on while pressing both volume up and volume down and after turning it on, I have to plug it to the computer through USB cable. My phone does turn on in download mode, however when I connect it to the USB my computer doesn't detect anything.
Is the screen I am getting the right screen or should I switch the phone on with a different shortcut?
How do I get my computer to detect my phone when I switch it on with the volume+&- buttons?
Which are the correct fastboot drivers to install and where can I download them?
I hope to receive assistance as soon as possible.
Thank you.
EDIT:
I've managed to reboot correctly by using ADB command prompt (typing ADB reboot fastboot)
Now, I'm trying to root and in the command prompt I get this error:
"cannot load 'cwm_touch_recovery_viva_beta.img': No error"
EDIT:
Supersu installed.
Now when attempting to edit the build.prop I get a error message
I check the Concole and I see "Remount failed: Operation not permitted
But I granted root access when prompted. Any Idea?
EDIT:
Tried 39 times until I got it successfully.
And don't ask me how. It's beyond me.
Checked About and version is good.
Now rebooted and "Version list verify fail!"
WHY?
I've checked the build.prop and it is flashed,
I've flashed the 229recovery.img
I reboot and it gives me "Version list verify fail!"
What could have I done wrong?

DenesS said:
I've checked the build.prop and it is flashed,
I've flashed the 229recovery.img
I reboot and it gives me "Version list verify fail!"
What could have I done wrong?
Click to expand...
Click to collapse
Try with the build.prop from b226, avaible here: http://openbuildprop.scheffsblend.com/mfg/Huawei (copy -> paste into notepad, save as build.prop)

o-l-a-v said:
Try with the build.prop from b226
Click to expand...
Click to collapse
Ok, this makes sense, it probably wouldn't like to update to a version which is already installed.
This wasn't clear on the tutorial, thanks for the hint.
I'm trying now
EDIT:
Nope, still "Version list verify fail!"
Even though I checked in the "About" and the version shown is B226, which means the .prop was correctly flashed.
So what could the problem be?
EDIT:
Should I also try flashing the B226 recovery?
Do you have a link for any download page?
Can I flash it directly through CWM? CWM wants a root://Update.zip can I put my UPDATE.APP into a zip archive and flash it or does it work differently?

People have had problems updating to B229 with the build.prop i extracted from the B229 fw.
There is simply a little difference at this line:
Code:
ro.build.display.id=V100R001C00B229
It should be:
Code:
ro.build.display.id=U9200-V100R001C00B229
Build.prop from all earlier firmwares (Exept B226) including EmUI betas and stables have the "U9200-"-part before product version on this line.
This is a mistake by Huawei, not me :good:
Updated the FlashPack for B229, new link from mega in first post!

LB757, how to update to rooted 108?

Hi All,
I am Locked Bootloader and using this rom 757(http://forum.xda-developers.com/showthread.php?t=2688933), and now want to upgrade to 4.4.4 (108) and need to root, how can I upgrade?
Thanks.

Maybe by reading the first sentence in the first post in that thread (the one in those giant letters).

Iruwen said:
Maybe by reading the first sentence in the first post in that thread (the one in those giant letters).
Click to expand...
Click to collapse
using Easy Root Tool? but where can I get the flashable zip for 108?
sorry I am new in Sony.

kwchan98 said:
using Easy Root Tool? but where can I get the flashable zip for 108?
sorry I am new in Sony.
Click to expand...
Click to collapse
It's all in this stickied thread. The first section "Quick Step Update Guide...".

kwchan98 said:
Hi All,
I am Locked Bootloader and using this rom 757(http://forum.xda-developers.com/showthread.php?t=2688933), and now want to upgrade to 4.4.4 (108) and need to root, how can I upgrade?
Thanks.
Click to expand...
Click to collapse
I can help you. I just did it a couple of hours ago and the step actually is quite easy but since it takes many steps, it might spend you one to two hours to learn if you aren't knowledgeable about flashing stuffs. I was on unlocked bootloader with .757 rooted but that should be no different at all if you don't flash custom kernel(I didn't do that too because currently no .108 custom kernel for us).
1. Be sure to backup your whole existing rom in recovery first and copy it to your computer
2. Use Titanium backup to backup all user apps and app data and copy it to your computer
3. Make sure your contact list in phone book is backed up by Google. If you aren't sure about that, remove your account in PlayStore and setup it again. You will see it asks you permission to backup contact list to Google via Internet in last step(default is yes).
http://forum.xda-developers.com/showthread.php?t=2635830
4. Install the latest ver of Sony pc companion in your windows and reboot. It will install the correct z1c driver into your system. Make sure you used a good quality usb cable because if not, that can cause serious problem during flashing firmware and brick your phone in worse case. You can also try to install Xperia driver set in the link above if your windows just can't install Sony pc companion successfully but I think PCC should be better.
5. http://forum.xda-developers.com/sony-xperia-z1-compact/general/stock-rom-xperia-z1c-d5503-14-4-0-108-t2801269
I used the rom in this thread. But I was having problem to download it with firefox, everytime it was stopped during in the middle progress, it might be conflicted with some of my add-on. At last, I use Chrome to download it and completely no problem at all.
6. http://www.xperiadownload.cz/index.php/xperiadownload/file/193-flashtool-6-2014
Download the latest flashtool from here and put the D5503_14.4.A.0.108_Generic_UK_1279-4053.ftf under /firmwares
7. Enable USB debugging mode and allow install app from unknown sources in your phone. When you first time to enable usb debugging and connected the phone to windows, there will be a screen to ask you accept and remember on your phone screen. Please immediately to click it.
8. Run flashtool(FlashTool for 32bit win, FlashTool64 for 64bit win). Click on the first icon(power icon) and select flash mode. It will open up a windows to let you select .ftf, pick the Generic_UK_1279-4053. Uncheck the DATA if you want to keep the existing system settings and apps and apps data. But it would be very easy to cause problem like battery draining and unstable after updated because the system settings in .757 and .108 is different. I would highly recommend you clean the DATA here and restore the apps and apps data from Titanium backup later. Please note that you have to quit PC Companion before you run flashtool, otherwise they may have chance to conflict.
9. http://www.theandroidsoul.com/sony-xperia-z-flash-mode/
Follow the guide here to enter flash mode. First power off your phone, second unplug the usb cable out of the phone, third press and remember to keep holding down the volume down key then connect the usb cable to your phone again. After a few seconds, my windows7 showed installing device driver at the right corner and wait it for a couple of mins it will be done and tell you flash drive installed. I still keep hold on the volume down at this moment but I'm not sure if it really needed. The guide in the link said there will be a Green LED light on xperia z but my z1c just didn't show me any LED light.
10. I remember the flashtool was aborted because I was unpluged the usb cable out(though I reconnected it later on). I was once again selected the .ftf and this time it immediately detected my phone was in flash mode and started to flash the firmware to my phone. I released the volume down key at this time. Remember to close all software in your windows, don't listen music or play games please, don't do anything and don't let any people near your computer now(if your computer health is bad and always easy to hang, you should give up now until fixed the problem or buy a new computer). If your windows is unstable and got blue screen, your phone will brick. Just wait it to finish, not too long, I think 10 to 15mins.
11. Your should flashed .108 successfully now and unplug the usb cable, press on the Power to let the phone boot into OS.
12. Repeat step seven again.
13. http://forum.xda-developers.com/showthread.php?t=2784900
Use the EasyRoot tool v11 here and run it in windows. After rooted then reboot first and go to playstore to install SuperSU(by Chainfire ver) and reboot again. Please note that sometimes EasyRoot tool v11 will get stuck during in the middle processing for some unknown reason, don't worry, just press Ctrl-C to cancel it and run it again.
14. https://www.sendspace.com/file/2tflfc
http://nut.xperia-files.com/
I've used Z1C-lockeddualrecovery2.7.150-BETA.installer.zip and please download it from the sendspace link above and run it in windows(it also worked perfectly on my unlocked z1c). In the command prompt window, select "1" - SuperSU and it will install custom recovery to your z1c. It will also install a NDR Utils app and you can select which recovery(cwm or twrp) you want to use in that app, default is TWRP. Please note that there are some new ver of Z1C-lockeddualrecovery but some may buggy and I don't have time to test them all.
Now you've done but if you want to deodex the rom to play more tweaking stuffs/mods. There are more steps to do.
15. http://www.oracle.com/technetwork/java/javase/downloads/jre7-downloads-1880261.html
Install the latest ver of Java runtime for windows and reboot.
16. http://forum.xda-developers.com/showthread.php?t=2713329
Use kamome tool v6a and run it in windows. Follow this steps: 1>2>3>5>4>6 and at last, copy the deodex_install.zip to your phone storage. Reboot into recovery and flash the deodex_install.zip, clean cache and dalvik cache then reboot. Please note that I think kamome tool v6a will also install a SuperUser into your phone which conflict with SuperSU. Don't worry, click on SuperSU and it will tell you SuperUser detected and ask you to uninstall it and click Yes.
17. Restore all apps and apps data from Titanium backup but if you are originally come from an odexed rom, don't restore those odex apps into a deodexed system, you have to install all of them via PlayStore manually first then only restore the app data in Titanium backup thereafter.
You have finished pretty much all things now. It will take you many steps to go but all are easy work.

TheEndHK said:
I can help you. I just did it a couple of hours ago and the step actually is quite easy but since it takes many steps, it might spend you one to two hours to learn if you aren't knowledgeable about flashing stuffs. I was on unlocked bootloader with .757 rooted but that should be no different at all if you don't flash custom kernel(I didn't do that too because currently no .108 custom kernel for us).
1. Be sure to backup your whole existing rom in recovery first and copy it to your computer
2. Use Titanium backup to backup all user apps and app data and copy it to your computer
3. Make sure your contact list in phone book is backed up by Google. If you aren't sure about that, remove your account in PlayStore and setup it again. You will see it asks you permission to backup contact list to Google via Internet in last step(default is yes).
4. Install the latest ver of Sony pc companion in your windows and reboot. It will install the correct z1c driver into your system. Make sure you used a good quality usb cable because if not, that can cause serious problem during flashing firmware and brick your phone in worse case.
5. http://forum.xda-developers.com/sony-xperia-z1-compact/general/stock-rom-xperia-z1c-d5503-14-4-0-108-t2801269
I used the rom in this thread. But I was having problem to download it with firefox, everytime it was stopped during in the middle progress, it might be conflicted with some of my add-on. At last, I use IE11 to download it and completely no problem at all.
6. http://www.xperiadownload.cz/index.php/xperiadownload/file/193-flashtool-6-2014
Download the latest flashtool from here and put the D5503_14.4.A.0.108_Generic_UK_1279-4053.ftf under /firmwares
7. Enable USB debugging mode and allow install app from unknown sources in your phone. When you first time to enable usb debugging and connected the phone to windows, there will be a screen to ask you accept and remember on your phone screen. Please immediately to click it.
8. Run flashtool(FlashTool for 32bit win, FlashTool64 for 64bit win). Click on the first icon(power icon) and select flash mode. It will open up a windows to let you select .ftf, pick the Generic_UK_1279-4053. Uncheck the DATA if you want to keep the existing system settings and apps and apps data. But it would be very easy to cause problem like battery draining and unstable after updated because the system settings in .757 and .108 is different. I would highly recommend you clean the DATA here and restore the apps and apps data from Titanium backup later.
9. http://www.theandroidsoul.com/sony-xperia-z-flash-mode/
Follow the guide here to enter flash mode. First power off your phone, second unplug the usb cable out of the phone, third press and remember to keep holding down the volume down key then connect the usb cable to your phone again. After a few seconds, my windows7 showed installing device driver at the right corner and wait it for a couple of mins it will be done and tell you flash drive installed. I still keep hold on the volume down at this moment but I'm not sure if it really needed. The guide in the link said there will be a Green LED light on xperia z but my z1c just didn't show me any LED light.
10. I remember the flashtool was aborted because I was unpluged the usb cable out(though I reconnected it later on). I was once again selected the .ftf and this time it immediately detected my phone was in flash mode and started to flash the firmware to my phone. I released the volume down key at this time. Remember to close all software in your windows, don't listen music or play games please, don't do anything and don't let any people near your computer now(if your computer health is bad and always easy to hang, you should give up now until fixed the problem or buy a new computer). If your windows is unstable and got blue screen, your phone will brick. Just wait it to finish, not too long, I think 10 to 15mins.
11. Your should flashed .108 successfully now and the phone rebooted into OS.
12. Repeat step seven again.
13. http://forum.xda-developers.com/showthread.php?t=2784900
Use the EasyRoot tool v11 here and run it in windows. After rooted then reboot first and go to playstore to install SuperSU(by Chainfire ver) and reboot again. Please note that sometimes EasyRoot tool v11 will get stuck during in the middle processing for some unknown reason, don't worry, just press Ctrl-C to cancel it and run it again.
14. http://nut.xperia-files.com/
Download the Z1C-lockeddualrecovery2.7.150-BETA.installer.zip and run it in windows(it also worked perfectly on my unlocked z1c). In the command prompt window, select "1" - SuperSU and it will install custom recovery to your z1c. It will also install a NDR Utils app and you can select which recovery(cwm or twrp) you want to use in that app, default is TWRP. Please note that 2.7.151-BETA is out but the TWRP in that ver is extremely buggy, not sure about cwm.
Now you've done but if you want to deodex the rom to play more tweaking stuffs/mods. There are more steps to do.
15. http://www.oracle.com/technetwork/java/javase/downloads/jre7-downloads-1880261.html
Install the latest ver of Java runtime for windows and reboot.
16. http://forum.xda-developers.com/showthread.php?t=2713329
Use kamome tool v6a and run it in windows. Follow this steps: 1>2>3>5>4>6 and at last, copy the deodex_install.zip to your phone storage. Reboot into recovery and flash the deodex_install.zip, clean cache and dalvik cache then reboot. Please note that I think kamome tool v6a will also install a SuperUser into your phone which conflict with SuperSU. Don't worry, click on SuperSU and it will tell you SuperUser detected and ask you to uninstall it and click Yes.
17. Restore all apps and apps data from Titanium backup and setup PlayStore to get back phone list. But if you are originally come from an odexed rom, don't restore those odex apps into a deodexed system, you have to install all of them via PlayStore manually first then only restore the app data in Titanium backup thereafter.
You have finished pretty much all things now. It will take you many steps to go but all are easy work.
Click to expand...
Click to collapse
Thanks. It's great and work, now I am restoring apps by titanium backup. Thank you so much.

Is there any way to simple update a previous rom version on an already rooted bootloader locked z1 compact device?
After root process in your guide, may I have reinstall dual recovery anyway? May I keep my previous recovery or it has been deleted by the flashtool?
Many thanks
Rose

There are several ways to update firmware (OTA, Sony PC Companion, Flashtool, Recovery). When doing a firmware update you will normally lose recovery on locked bootloader. You can however easily reinstall it.

rose_canter said:
Is there any way to simple update a previous rom version on an already rooted bootloader locked z1 compact device?
After root process in your guide, may I have reinstall dual recovery anyway? May I keep my previous recovery or it has been deleted by the flashtool?
Many thanks
Rose
Click to expand...
Click to collapse
Please give us more details. Which rom and what ver?
The problem is that some older ver recovery may not working in new rom, you will need updates. Flashtool usually will destroy custom recovery.

[G800F][ROM][5.0.2][LRX22G] CyanogenMod 12.0 for G800F [Alpha 23/03/2015]

This is a CyanogenMod 12 ROM for the Exynos3470 based Samsung Galaxy S5 mini (G800F).
DO NOT USE IT FOR G800H/M/... OR YOU WILL BRICK YOUR DEVICE
Although G800F and G800H share the same name they are not related in terms of hardware due to the different SoCs used (Exynos vs. Snapdragon).
Hence please do not ask for support or ROMs for the G800H or G800M here.
Working features
Receiving and making calls
Hardware sensors (Light, Orientation, Compass, Proximity, Acceleration)
Audio
Bluetooth
Wifi
HW accelerated GUI
USB-OTG (Keyboard, Mouse, USB-Audio, Mass-Storage)
Camera (pictures+video: Back+Front)
MTP storage
IR
GPS
NFC
Known-issues:
Capacitive lights are blinking in standby mode
Touchscreen unresponsive for some seconds after resume from standby mode
Non-working features:
Fingerprint scanner (no app for tests found)
Pulse sensor + Step counter (no app for tests found)
SELinux
Disclaimer:
You flash this image at your own responsibility. I am not responsible for any damage that might be caused by flashing this image (bricked device, lost data, ...)
Flashing this kernel image will trigger the KNOX counter, so your warranty will be void.
The image is only for S5 Mini SM-G800F (Exynos)
It might be instable, crash your device, drain your battery, or even might damage your smartphone (e.g. if an USB-OTG device drains too much power)
Backup your data before flashing and check if the original firmware is present (e.g. at SamMobile)
Click to expand...
Click to collapse
Before you start:
Backup your data, like call history, contacts, sms, WhatsApp messages, favourite app settings that are on internal and external sd (by using Titanium Backup or other apps available on PlayStore). At least all internal data will be lost in any case. If you have bad luck you might also loose data from your external sd card.
!!! Development of this ROM is discontinued in favor of the CM 5.1 ROM !!!
This means that known issues will not be fixed. It is not recommended to use this ROM anymore.
The downloads have been removed and fully replaced by the 5.1 version. You can find the new CM 5.1 ROM here
Download:
Odin3-v3.07 (it is contained in CF-Auto-Root)
TWRP 2.8.5.0 recovery image [Updated 23/03/2015] (MediaFire Mirror)
CM12 rom for G800F (MediaFire Mirror)
Google Apps from here (for Google Play, ...). Select the package that suits you best. If you do not need all of the Google services the Micro edition is enough (BasketBuild Mirror for Micro edition).
Install recovery:
Reboot your device into Odin mode: turn off your device, then press Volume-Down + Home + Power button at the same time and release them.
Confirm the following warning message with the Volume-Up button.
Connect your device to your PC via USB
Make sure the device driver's are installed on your PC
Start Odin
In Odin select PDA and select the recovery image (recovery.tar.md5)
Check that only "Auto Reboot" and "F. Reset Time" is set
Click on "Start": the kernel image should be flashed now and the device should reboot afterwards. By flashing the recovery, your warranty will be void.
After the recovery flashing process was successful, power of your device. If not restart into Download mode and flash again or flash the stock rom.
Before you flash:
You need the latest TWRP recovery [Updated 23/03/2015]. Otherwise TWRP might not be able to flash the ROM. This is because TWRP checks now if the device is "supported".
G800M/G800Y are not supported but are not blocked as the ROM might work on these (Exynos3470 based) devices. Only flash the ROM on a G800M/Y if you know what you do. Do not expect help if something went wrong.
Wipe the device to avoid problems with remaining files from the old installation (see instructions below). This also applies if you already installed an older version of CM12.
Flash CM12:
Reboot into recovery mode (Press Volume-Up + Home + Power button)
If you come from a stock rom, this is your opportunity to make a Backup of your phone(Backup, then select Boot, System, Data, then swipe to backup). Note that the recovery might fail to restore the backup when you want to go back to the stock ROM (for me it got stuck after a restore during boot. But the backup was made with a different version of TWRP, so it might work in general) - simply do not expect too much of it at the moment.
If you haven't copied the installation files yet, you can now copy the GApps and CM12 zip to your internal sd or external sd (be careful not to put the files into the data directory of the internal sd card as this will be deleted in the next step). Be sure that MTP is enabled (inside Mounts, click on Enable MTP), then, from your pc, copy the files. If MTP does not work from recovery, try it directly from Android or remove the external sd card from the phone and put it into your PC.
Wipe Dalvik Cache, Cache, System and Data (inside Wipe -> Advanced Wipe). Do not report problems if you did not wipe those partitions as the problems are most probably related to this!
Install the CM12 rom zip-package
Install the GApps zip-package
Reboot the system and enjoy a Lollipop
How to root:
No SuperSu is needed as CM12 already comes with integrated root support. Root access is disabled by default.
You normally do not need root access. If you want to activate root access for apps, do the following:
Open the Settings menu, select "About Phone"
Tap on the "Build number" entry seven times. You should be notified, that the developer settings are now active.
Open the Settings menu, select "Developer options". Enable root access by selecting "Apps" in the "Root-Access" setting.
In case you want to go back to the stock ROM:
lf you do not have the latest ROM for the G800F you can download it from SamMobile
Reboot your phone into Odin mode
Open Odin on your PC and connect your smartphone with your PC via USB
If you have a zip-file unzip it so that you have a .tar.md5 file
In Odin click on the PDA button and select the .tar.md5 file. Then press "Start".
Normally the stock rom fails to boot as the data from CM12 is still on the data partition. So after flashing the stock rom, reboot into recovery mode (it looks a bit different now). First wipe the data partition, then wipe the cache.
Reboot
Changelog
Code:
23-03-2015:
* Fixed non-working mic on incoming call issue
* Fixed non-working menu-button
* Synchronized with latest CM12 sources
This section is for developers:
A script to setup the build environment can be found here:
Code:
https://github.com/tobigun/kminilte-patcher
Sources:
Code:
https://github.com/cm-3470/android_device_samsung_kminilte
https://github.com/cm-3470/android_vendor_samsung_kminilte
https://github.com/cm-3470/android_kernel_samsung_kminilte
https://github.com/cm-3470/android_device_samsung_smdk3470-common
Thanks to Unjustified Dev from Team Regular. As the S5 mini (G800F) and the Galaxy Light are quite similar we worked on this together.
XDA:DevDB Information
[G800F][ROM][5.0.2][LRX22G] CyanogenMod 12.0 for G800F [Alpha 23/03/2015], ROM for the Samsung Galaxy S5 Mini
Contributors
hennymcc, Unjustified Dev
Source Code: https://github.com/cm-3470
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP Recovery [version from 2015-03-23]
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2015-03-03
Last Updated 2015-04-15

FAQ
Question:
I'm trying to flash this rom but it says to me: "This package is for kmniltexx, kminiltedv, kminilteub; this device is kminilte. E:Error executing updater binary zip ...."
Answer:
The device names were changed with the newest CM12 build to be able to distinguish between G800F (kmniltexx), G800Y (kminiltedv) and G800M (kminilteub) as all of them are kminilte devices. The new builds of TWRP and CM12 detect the correct device at runtime.
Older TWRP releases (for example that of RVR in another XDA thread) still detect the device as kminilte (instead of kmniltexx,...) and hence are not able to install the new CM 12 releases so please do not install RVR's TWRP if you want to install CM 12. Always use the TWRP image linked in the first post of this thread.

For future use

Thanks for great job. Looking forward to testing it soon!!

I also want to say BIG THANX!
My Phone now makes a backup and than i flash your rom
stiff

I just noticed that the mic is muted on incoming calls. If you want to use the phone for daily use you should not the flash the ROM.

I flashed it already and can confirm, that the mic is off.
But it looks good so far. :good:
stiff

stiffmeister75 said:
I flashed it already and can confirm, that the mic is off.
But it looks good so far. :good:
stiff
Click to expand...
Click to collapse
It works for outgoing calls so I did not notice it before.

Do you know a workaroud?
btw. can you provide a patch with a fix?
or is it necessary to build a new rom?
stiff

sorry my noob question: is this ROM going to be listed in the CM12 nightlies or how will it work? is it an unofficial one yet or... thanks

wabre said:
sorry my noob question: is this ROM going to be listed in the CM12 nightlies or how will it work? is it an unofficial one yet or... thanks
Click to expand...
Click to collapse
It is not official and there won't be nightlies. At the moment there are no plans to get it into the official repo.

stiffmeister75 said:
Do you know a workaroud?
btw. can you provide a patch with a fix?
or is it necessary to build a new rom?
stiff
Click to expand...
Click to collapse
There is some work on this at the moment but no fix yet. Seems as if the audio implementation has to be adjusted a bit. I don't know how much work there is left. As this is a spare time project, this might take some time.
When it works there will be a new ROM for download.

Hey there, been using the rom for a couple hours and I must say, you've done a great job ! The interface is faster than stock touchwiz, and everything runs really smoothly ! I've only encountered two small issues (apart from the incoming call muted mic) :
-when waking up the device, the lockscreen seems to freeze itself (touch doesnt respond), so to fix it, you have to press power button and wake it up again (happened sometimes)
-noticed something strange: while the phone is asleep, the capacitative buttons would blink (they turn on for like 1sec and then turn itself off like a notification light). I'm pretty sure you'll be able to fix it, as it might be kernel related.
-(edit) and I've just realised that the left menu capacitive button doesn't work (but you probably already know this)
other than that, this rom is flawless for an Alpha ! Great job buddy
I was able to score 23 000 pts on Antutu vs 20 000 pts with stock 4.4.2 lol

I have found an issue with the capacitive buttons on the bottom. I was not able to deactivate the lightning and some other settings does not work aswell..
But all in all great alpha, I really enjoyed it ?
Sent from my SM-T530 using XDA Free mobile app

Omg! For my phone!
How cool! I will wait for beta i think...but keep up the good work, i will use it someday
And ill try to help to get ppl to know this thread

basic086 said:
-(edit) and I've just realised that the left menu capacitive button doesn't work (but you probably already know this)
Click to expand...
Click to collapse
Will be fixed with the next build.

i can confirm, that somethimes the capacitive buttons doent work/react.
and the bigger problem is that the micro doent work. (worst problem for me)
and one more problem... the sound on my alarm somethimes got some glitches/sound stops too.
i'll backup the new CM12 and than restore my old backup back... until these errors are fixed.
but, most important, very good work! respect. can i give you a donation ?

E:signature verification failed
what to do?

Hi,
great work!
I also can confirm that the mic for incoming calls does not work and it also doesn't work for either incoming or outgoing calls when using a headset. Haven't used a bluetooth headset yet but will test it later that day.
Many thanks so far for this built and I hope the mic bugs won't be a big deal.
Cheers,
lotherk

bebe.fier said:
E:signature verification failed
what to do?
Click to expand...
Click to collapse
You have a G800F and not a G800H or another variant?
If it is a G800F try to reflash it, maybe somethin went wrong. What is the stock ROM you currently have installed? Is it the newest one - can you give me the version number?

How To Guide Samsung Galaxy A54 5G [Root Stock ROM with Magisk]

WARNING! THIS WILL WIPE ALL DATA FROM YOUR DEVICE!
1. Get your android and device version from settings -> about phone -> service provider software version (for me its SM-A546B EUX)
2. Download the latest stock ROM for your specific device from https://samfrew.com/
3. Download and install Odin from https://samsungodin.com/download/
4. Activate developer settings (click 8x on buildnumber)
5. Activate usb debugging from the developer settings
6. Activate OEM Unlocking (THIS WILL WIPE ALL YOUR DATA)
7. After this factory reset, hold down volume up + power to get to the recovery
8. Choose to reboot to bootloader
9. You will be asked if you want to unlock the bootloader, choose yes
10. Put the downloaded stock ROM onto your device (sdcard, internal storage, etc)
11. Download the Magisk app from the Playstore
12. Open Magisk and hit install
13. Select the downloaded stock ROM from your storage and wait for the process
14. Copy the magisk-modified ROM to your PC
15. Pack the magisk-modified ROM in a TAR and flash as "AP" with Odin
16. Let the phone boot and complete the initial setup
17. Open Magisk and reboot if suggested
(18. Go into Magisk again, go to Settings and enable Zygisk
19. and reboot again)
Magisk should now show the current version in "installed" and apps can request superuser access now. If "installed" shows n/a then magisk root did not work.
If anything fails, you should always be able to press the powerbutton + volume up to get to the bootloader (big blue screen) and flash the AP of the stock rom.
Need help with:
- Patch dm-verity/vbmeta (to install a custom recovery)
- Porting TWRP to Exynos1380 kernel

Recommended changes:
Build Number need only be tapped 8 times to activate developer mode, not ten.
After downloading the firmware zip, the user will need to extract it. The AP file is what needs to be patched in Odin.
Flashing the AP file won't wipe data. This is determined by which file the user selects in the CSC slot: CSC.tar will wipe the device, HOME_CSC will not.
The "Ramdisk" information in Magisk does not indicate whether or not the device has been rooted with Magisk. If you install the Magisk app on a stock unrooted ROM, it will still indicate whether the device has ramdisk or not. The only difference this makes is how Magisk should be installed. See Magisk Installation
The "Installed" indicator in Magisk is what actually indicates whether the device is rooted. If this says N/A, the device has not been properly rooted. With root, "Installed" should show the version of the Magisk patch:
{
"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"
}
"Magisk > Installed: 26.1" indicates that the device is currently rooted with the patch that corresponds to Magisk release 26.1.
"Magisk > Ramdisk" only indicates whether or not the device uses ramdisk. Again, this has nothing to do with whether the device is rooted.
"App > Latest" indicates the latest Magisk release for the selected update channel (stable, beta, custom)
"App > Installed" shows the currently installed version of the Magisk app​

V0latyle said:
Recommended changes:
Build Number need only be tapped 8 times to activate developer mode, not ten.
After downloading the firmware zip, the user will need to extract it. The AP file is what needs to be patched in Odin.
Flashing the AP file won't wipe data. This is determined by which file the user selects in the CSC slot: CSC.tar will wipe the device, HOME_CSC will not.
The "Ramdisk" information in Magisk does not indicate whether or not the device has been rooted with Magisk. If you install the Magisk app on a stock unrooted ROM, it will still indicate whether the device has ramdisk or not. The only difference this makes is how Magisk should be installed. See Magisk Installation
The "Installed" indicator in Magisk is what actually indicates whether the device is rooted. If this says N/A, the device has not been properly rooted. With root, "Installed" should show the version of the Magisk patch:
View attachment 5893171​"Magisk > Installed: 26.1" indicates that the device is currently rooted with the patch that corresponds to Magisk release 26.1.​"Magisk > Ramdisk" only indicates whether or not the device uses ramdisk. Again, this has nothing to do with whether the device is rooted.​"App > Latest" indicates the latest Magisk release for the selected update channel (stable, beta, custom)​"App > Installed" shows the currently installed version of the Magisk app​
Click to expand...
Click to collapse
thank you, ive adjusted the how-to to your recommendations

Hello,
What about Knox with this method ??
Thanks

leosoftstudios said:
Hello,
What about Knox with this method ??
Thanks
Click to expand...
Click to collapse
I think this easily trips it. Cant confirm, because the usual system information in the bootloader doesnt show up for me. I tried using Samsung Pass with zygisk + shamiko (tried to activate anything samsung related in the denylist) but i just get the message that "you cannot use samsung pass on a rooted device", so iam not even getting past that.

Why would someone root it? One UI is the most perfect Android imaginable....
Opinion,of course.

terry_mccann said:
Why would someone root it? One UI is the most perfect Android imaginable....
Opinion,of course.
Click to expand...
Click to collapse
Funny how this pops up in every thread here like people get paid to go to a forum for custom roms and then leave their opinion, why a custom rom is useless...just why? how do you people even get here, arent you in the totally wrong place?
and to settle the argument: install a custom rom to get rom updates beyond the manufacturers lifetime support, simple as that. faster security updates, debloating, etc, dont get me started.

Thank you for posting this guide, i had a question and was getting hung up on step 2.
The CSC code my phone is giving me is OYN, and I'm struggling to find that firmware version on the website provided. Do i just need to wait for the firmware for that CSC to be uploaded to that site?
Thanks!

draykhar said:
Thank you for posting this guide, i had a question and was getting hung up on step 2.
The CSC code my phone is giving me is OYN, and I'm struggling to find that firmware version on the website provided. Do i just need to wait for the firmware for that CSC to be uploaded to that site?
Thanks!
Click to expand...
Click to collapse
I guess the CSC is country/provider dependend. Maybe your mobile shop got the device from another country or so? Try to check the model number (check 'SM-A546B' for the last letter), I found some roms with OYN as CSC with this model of the A54 here: https://samfrew.com/model/SM-A546V/region/VZW/ but was just a lucky find - definetly check your model number and make sure, you got the right one.

So I'm currently missing the "OEM Unlock" option w/in the "Developer Options" menu on my device. Does anyone know of any other alternative method to unlocking the bootloader for my situation?

Hi there
knighToFdemonS said:
WARNING! THIS WILL WIPE ALL DATA FROM YOUR DEVICE!
1. Get your android and device version from settings -> about phone -> service provider software version (for me its SM-A546B EUX)
2. Download the latest stock ROM for your specific device from https://samfrew.com/
3. Download and install Odin from https://samsungodin.com/download/
4. Activate developer settings (click 8x on buildnumber)
5. Activate usb debugging from the developer settings
6. Activate OEM Unlocking (THIS WILL WIPE ALL YOUR DATA)
7. After this factory reset, hold down volume up + power to get to the recovery
8. Choose to reboot to bootloader
9. You will be asked if you want to unlock the bootloader, choose yes
10. Put the downloaded stock ROM onto your device (sdcard, internal storage, etc)
11. Download the Magisk app from the Playstore
12. Open Magisk and hit install
13. Select the downloaded stock ROM from your storage and wait for the process
14. Copy the magisk-modified ROM to your PC
15. Pack the magisk-modified ROM in a TAR and flash as "AP" with Odin
16. Let the phone boot and complete the initial setup
17. Open Magisk and reboot if suggested
(18. Go into Magisk again, go to Settings and enable Zygisk
19. and reboot again)
Magisk should now show the current version in "installed" and apps can request superuser access now. If "installed" shows n/a then magisk root did not work.
If anything fails, you should always be able to press the powerbutton + volume up to get to the bootloader (big blue screen) and flash the AP of the stock rom.
Need help with:
- Patch dm-verity/vbmeta (to install a custom recovery)
- Porting TWRP to Exynos1380 kernel
Click to expand...
Click to collapse
knighToFdemonS said:
WARNING! THIS WILL WIPE ALL DATA FROM YOUR DEVICE!
1. Get your android and device version from settings -> about phone -> service provider software version (for me its SM-A546B EUX)
2. Download the latest stock ROM for your specific device from https://samfrew.com/
3. Download and install Odin from https://samsungodin.com/download/
4. Activate developer settings (click 8x on buildnumber)
5. Activate usb debugging from the developer settings
6. Activate OEM Unlocking (THIS WILL WIPE ALL YOUR DATA)
7. After this factory reset, hold down volume up + power to get to the recovery
8. Choose to reboot to bootloader
9. You will be asked if you want to unlock the bootloader, choose yes
10. Put the downloaded stock ROM onto your device (sdcard, internal storage, etc)
11. Download the Magisk app from the Playstore
12. Open Magisk and hit install
13. Select the downloaded stock ROM from your storage and wait for the process
14. Copy the magisk-modified ROM to your PC
15. Pack the magisk-modified ROM in a TAR and flash as "AP" with Odin
16. Let the phone boot and complete the initial setup
17. Open Magisk and reboot if suggested
(18. Go into Magisk again, go to Settings and enable Zygisk
19. and reboot again)
Magisk should now show the current version in "installed" and apps can request superuser access now. If "installed" shows n/a then magisk root did not work.
If anything fails, you should always be able to press the powerbutton + volume up to get to the bootloader (big blue screen) and flash the AP of the stock rom.
Need help with:
- Patch dm-verity/vbmeta (to install a custom recovery)
- Porting TWRP to Exynos1380 kernel
Click to expand...
Click to collapse
Hi there!
I just unlocked my a54 from Metro PCS. Can this phone be rooted? I haven't rooted since Samsung put an iron fist on US-based phones.
Anyone chime in.

sameog said:
Hi there
Hi there!
I just unlocked my a54 from Metro PCS. Can this phone be rooted? I haven't rooted since Samsung put an iron fist on US-based phones.
Anyone chime in.
Click to expand...
Click to collapse
I got an A54 phone from MetroPCS as well, but was unable to unlock "OEM" b/c the option was missing from "Developer Options"... Could you screenshot where you were able to locate the "OEM unlock" option and what version firmware is your phone currently on?

Thanks for the tutorial!
However, I'm pretty sure I used the proper firmware, but now the phone keeps complaining that I have to "update carrier settings" and to "reboot" and then it complains that it "couldn't update carrier settings".
Anyone having this, or having a solution? Couldn't find anything by myself

LidelnFR said:
Thanks for the tutorial!
However, I'm pretty sure I used the proper firmware, but now the phone keeps complaining that I have to "update carrier settings" and to "reboot" and then it complains that it "couldn't update carrier settings".
Anyone having this, or having a solution? Couldn't find anything by myself
Click to expand...
Click to collapse
I currently have the same problem but I had not much time to try things out in the last 2 weeks (and somewhat still waiting on that thread from the guy who wanted to build TWRP for this kernel).
I remember that at one time, I fixed that problem, but I cannot recall the exact steps what I was doing.
I think I cleared all the data stuff from the bootloader-menu (ex. wipe cache, wipe data, etc) just right after a fresh AP/image flash with the magisk-rooted-ROM. I remember doing it multiple times, on several reboots (tried to follow some very old youtube-videos which apparently fixed that problem in android 4).
But it could also have happened while i debloated the rom one time with adb commands (just uninstalled all the extra stuff like facebook and alot of samsung stuff aswell - that also might have fixed it.
Just got another idea: try to find the provider-app of the system message via "adb logcat".
Maybe I can find some time on the weekend to take another look but maybe this already helps you.
I just didnt want to reflash the ROM all the time, just in case something breaks and I have no TWRP yet to recover from a bricked device.

knighToFdemonS said:
I currently have the same problem but I had not much time to try things out in the last 2 weeks (and somewhat still waiting on that thread from the guy who wanted to build TWRP for this kernel).
I remember that at one time, I fixed that problem, but I cannot recall the exact steps what I was doing.
I think I cleared all the data stuff from the bootloader-menu (ex. wipe cache, wipe data, etc) just right after a fresh AP/image flash with the magisk-rooted-ROM. I remember doing it multiple times, on several reboots (tried to follow some very old youtube-videos which apparently fixed that problem in android 4).
But it could also have happened while i debloated the rom one time with adb commands (just uninstalled all the extra stuff like facebook and alot of samsung stuff aswell - that also might have fixed it.
Just got another idea: try to find the provider-app of the system message via "adb logcat".
Maybe I can find some time on the weekend to take another look but maybe this already helps you.
I just didnt want to reflash the ROM all the time, just in case something breaks and I have no TWRP yet to recover from a bricked device.
Click to expand...
Click to collapse
Thank you kindly for this! I am quite a noob so I don't want to reflash the ROM all the time either ^^
Not sure about these adb commands, but I might have a look if I have time (this is my gf's phone, I don't want to bother her all the time)
Btw, for the installation, I had to do these steps (most are identical, but some are slightly different or more specific):
### Preparation steps:
"Called" *#1234# to get CSC and other information
I used SamMobile (premium sub to get the file quickly because I was in a hurry -- this is not a promo, I have zero link with them whatsoever)
Went to this thread to get Odin 3.14.1 3B PatcheD (not sure it changed anything)
Did the steps to activate developer mode, USB debugging, OEM unlocking (it did not wipe anything for me)
Turned the phone off
Turned it on again using VOL+ and VOL- at the same time (had to try again because it didn't work the first time)
Another option is to use ADB: adb reboot recovery (first you have to list devices, and if need be authorize (from the phone) ADB to access it)
In the blue screen, written at the center, are the options you can "press" for (not easy to see at first)
So, LONG (!!) press VOL+ to ask to unlock bootloader
SHORT press VOL+ to confirm unlocking the booloader (which will wipe data)
Reboot phone
### Firmware/flashing steps:
On the PC, unzip the Samsung firmware
Put (only) the "AP" file into the phone (e.g. "Downloads" directory) (I had first to remove the trailing ".md5" from the filename to only keep ".tar", not sure it is mandatory but I didn't want to lose 12 minutes of copy for nothing)
Install Magisk on the phone (ONLY from their GitHub : topjohnwu) (you have to do it AFTER the bootloader is unlocked, if I understood things properly)
Using Magisk, click the first "install" button at the top (which will actually patch an AP file), choose the AP.tar file from your "downloads" folder (for example)
When done, copy the newly generated file (magisk_patched-26100_{UID}.tar) to the computer (I first had to unplug USB and replug, because it would not refresh the folder properly, at least on Windows 10)
The file was already in .tar extension (at least for me) so I didn't have to compress it again
Reboot the phone in recovery or "download mode" (using the same steps as earlier)
Launch Odin, plug the phone, and flash the Magisk-patched AP file (only this file) (leave the options to their default)
It should reboot the phone when it's done
### Magisk-related steps:
Install Magisk again (it should (??) be wiped iirc), it will ask you to reboot after some changes it automatically made
Reboot
Relaunch Magisk, go to options, activate Zygisk: it will install a new module
Reboot
Go to Magisk, enable systemless host file (or something like that) so that ad blockers (e.g. AdAway) can work properly
Reboot
Go to Magisk again and enable "hide magisk" from the options, choose a custom name
Reboot one last time (not sure you have to reboot for each Magisk step, it's just to be sure)
Again, most steps are identical, but other change slightly or are more precise, because honestly I was kinda lost at first
Thank you again for the tutorial!
For the carrier services, I tried to "reset network" but it didn't do anything.

urbanman2004 said:
I got an A54 phone from MetroPCS as well, but was unable to unlock "OEM" b/c the option was missing from "Developer Options"... Could you screenshot where you were able to locate the "OEM unlock" option and what version firmware is your phone currently on?
Click to expand...
Click to collapse
Just throw some ideas, if flash another firmware change MetroPCS to T-Mobile for example or US global version, not sure if this OEM unlock toggle appears..if yes, it would be straightforward after that

urbanman2004 said:
I got an A54 phone from MetroPCS as well, but was unable to unlock "OEM" b/c the option was missing from "Developer Options"... Could you screenshot where you were able to locate the "OEM unlock" option and what version firmware is your phone currently on?
Click to expand...
Click to collapse
I believe what he said is just carrier unlocked not bootloader unlocked, 2 different things..

bizkit_120 said:
Just throw some ideas, if flash another firmware change MetroPCS to T-Mobile for example or US global version, not sure if this OEM unlock toggle appears..if yes, it would be straightforward after that
Click to expand...
Click to collapse
I would have to unlock the bootloader in order to flash a different rom which requires the OEM unlock toggle to be accessible, but it's not.

bizkit_120 said:
I believe what he said is just carrier unlocked not bootloader unlocked, 2 different things..
Click to expand...
Click to collapse
Possibly so... I was waiting for them to respond to my comment to get a definitive answer, but time will tell.

Flash stock firmware doesn't require bootloader to be unlocked.. you can try flash another firmware see if OEM toggle comes up, then unlock it..