[Guide][Rom]Carbon AOSP Jelly Bean 4.3 - T-Mobile, Samsung Galaxy SIII

The T-Mobile variant for the Samsung Galaxy S3 can now be update to Android 4.3 Jelly Bean using the Carbon AOSP JB custom ROM. Read this entire post and you should be able to complete all instructions easily without bricking the device.This is a custom ROM that is based on Android 4.3 AOSP, CyanogenMod, AOKP, Paranoid Android builds. More info is listed here:* http://goo.im/devs/carbon .
In order to install this new custom ROM at your first attempt, you should take a look at the guidelines below:
This tutorial works only with the T-Mobile Samsung Galaxy S3 smartphone. Do not attempt to update any other devices with the files you find here.Your phone should be factory unlocked and rooted.
Also, for the new ROM to be flashed you need to use a custom Recovery image like CWM or TWRP, as both these variants are supported by this guide.
A ‘factory reset’ is required before flashing the new ROM files. This means that you will lose all data from system partition.
If you want to backup installed apps data then you can use the following tools for Android:*Helium tool from Google Play Store*or*Titanium Backup.
Backup the SMS text messages, Call Logs and APN Internet Settings with these apps:*SMS backup & restore*|*Call Logs backup & restore*|*APN Settings Backup & Restore.
You will need to grant root access for some of these applications.If you don’t want to lose any important phone numbers and contacts data, then make sure to sync Contacts with your Gmail account. Use this guide*here: http://www.android.gs/how-to-sync-contacts-on-android-with-your-gmail-account/ .
Enable USB Debugging.Make sure that the phone’s battery will not get drained completely before completing the tutorial. The power charge levels should be over 50% in order to prevent that from happening.
This guide is for more advanced users.
Do not blame us in case you brick your phone or lose important files in the process.
Read all the info listed in this article and don’t skip any steps.
Also, make sure to create a NANDROID Backup of your current ROM before installing the new one. There is also a tutorial step that will teach you how to do that.
How to flash Carbon AOSP Jelly Bean 4.3 custom ROM for T-Mobile Samsung Galaxy S3:
1.Download the custom ROM latest Nightly build from*here: http://goo.im/devs/carbon/d2tmo/nightly .
- make sure to download the latest version and not an older one, as those aren’t very stable.
2.Download gapps for Android 4.3 ROMs from*here: http://www.android.gs/download-install-and-flash-google-apps-for-android/ .
- this has to be installed after you flash the ROM, as it will add all Google applications that your device requires.
3.Connect your smartphone with your PC, then move both files to your phone’s internal SDcard.
- disconnect the phone from computer when the files are moved.
4.Power off the smartphone.
5.Boot the device into*Custom Recovery Mode.
6.First, create the NANDROID Backup for the installed ROM:
- CWM: select ”backup and restore” option, then use the backup to internal SDcard option. Confirm.
- TWRP: press Backup, select the system file you want to backup. Confirm.
7.Next, apply ‘factory reset’:
- CWM: select ‘wipe data/ factory reset’ and confirm.
- TWRP: press Wipe, then Factory Reset. Confirm.
8.Now you can finally install the Carbon AOSP Jelly Bean 4.3 zip:
- CWM: select install zip from sdcard. Locate the custom ROM file and confirm its installation.
- TWRP: press Install, then load the Carbon AOSP zip in TWRP. Confirm.
9.When the ROM is installed, repeat step 8 actions and flash the Gapps zip.
10.After both files are flashed you should return to the main Recovery screen. Reboot your smartphone.
11.Enter the Google Account details and take control over your device.
12.Test all the new features of your new ROM.

Is the site up yet?
sent from my Samsung Galaxy T999 Powered by Bean Stalk 4.3

Not sure if I'm missing something
doesn't connect to the network and the power button doesn't respond

Related

[GNEX TOOLKIT V11.1] Drivers, Backup, Unlock, Root, Recovery, Flash + MORE [VERIZON]

UPDATES:
[GUIDE] Flashing Your First Galaxy Nexus Rom For Newbs [GSM and LTE]
Frequently Asked Questions:
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF (e.g removing system apps).
From Google:
Android Debug Bridge (adb) is a versatile tool lets you manage the state of an emulator instance or Android-powered device. It is a client-server program that includes three components:
A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
A daemon, which runs as a background process on each emulator or device instance.
----------------------------------------------------------------------------
Q. What is FASTBOOT?
Fastboot is 2 things. It is a mode on the phone, which looks a little like Bootloader. You can access it by holding 'Volume Up' and 'Volume Down' whilst turning on the phone.
It is also a way of flashing radios, recovery, boot images and system images in a command line method from a PC much like adb.
----------------------------------------------------------------------------
Q. I flashed CWM but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on certain Stock Android Builds that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from Google Play such as ES File Explorer). Rename the files /system/recovery-from-boot.p and /system/etc/install-recovery.sh. Now when you flash CWM Recovery it will NOT be overwritten after a reboot.
OR you can use the ToolKit to rename the files (root access needed).
----------------------------------------------------------------------------
Q. I want to send my phone back so I need to flash a stock rom and relock the bootloader
1. Download, install and run the Google Nexus 4 Toolkit.
2. Install adb/fastboot drivers (if you havent already done so)
3. Option 9 to download a Google Factory Image.
4. After it finishes downloading you will be given the option to flash the image to your tablet. Do this.
4. Let the phone reboot, then shut the device down and reenter fastboot mode (or boot to fastboot mode via the Reboot Screen in the ToolKit).
5. Option3, 2 to relock the bootloader.
Your internal storage will be formatted and data and cache wiped. Your tablet will now be back to an out-of-the-box FULLY STOCK state and ready to send back.
----------------------------------------------------------------------------
Q. What is the difference between Nandroid and Titanium backup?
A NANDROID will backup the whole system including boot, system, data and recovery partitions so you can restore a complete rom and all data and settings.
Essentially Titanium Backup is used to backup apps and associated user data. These could be restored AFTER a full wipe and a new Rom had been flashed on your phone.
The other option now which google added into the new adb command list is the adb backup which is in the ToolKit and can do the same job as Titanium Backup but will store the data on your PC rather than on the phone (where it takes up space and could be deleted).
----------------------------------------------------------------------------
Q. When I try to open the ToolKit I get a box pop up for a split second and then it goes away. My AntiVirus program says the file may be harmful.
The exe files I compiled are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton) will pick it up as potentially harmful when it is not. They will pick up ANY file that doesnt contain a purchased Microsoft certificate in the same way. Restore the deleted file and exclude it from further scans and it will be fine.
----------------------------------------------------------------------------
Q. The ToolKit recognises my tablet in adb mode but not in fastboot mode (or other way round).
Open the Device Manager on your pc and then boot your tablet into fastboot mode or adb mode (dont plug the usb cable in yet). Make sure USB debugging is enabled on your tablet in settings, developer options. Plug the cable in while watching the Device Manager and determine which item is added to the list with the device plugged in. Once you have found it right click on the item and select update driver. Select 'browse my computer' from the list and then browse to the 'drivers' folder in the ToolKit folder (wherever you installed the ToolKit to). Make sure sub folders is ticked and click next. Hopefully the driver will be picked up and installed.
You can check if a driver has been installed by looking at the top of the Main Menu in the ToolKit while in fastboot mode and adb modes. If a serial number is displayed in each mode then it will work fine.
----------------------------------------------------------------------------
Q. Can I back up my apps before unlocking the Bootloader so I don't lose everything?
Performing an APPS BACKUP (option2, 1) will backup all apps that were installed after you first used your device. This will include any associated user data (such as settings or high scores for games) and apps you installed from Google Play Store. Just follow the recommended options and remember to turn your phones screen on before starting it as you need to confirm on your screen.
This option will NOT require your bootloader to be unlocked first.
You can also backup your Internal Storage without unlocking using option 2, 3 from the main menu. This will backup anything you store on your Internal Storage such as game data, music, videos. This is just pulled from your /data/media folder so you can view or edit the files on your pc after they have been pulled.
You can then unlock the bootloader (wiping your device) and retore the apps (option 2, 10) and Internal Storage data (option 2, 11) after doing whatever you want to with your device.
The only thing you cannot do with the ToolKit is to save the system settings but some of those are backed up by google if you chose that option when turning your device on the first time.
----------------------------------------------------------------------------
Q. I have Windows 8 and cannot install the drivers
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
When your computer restarts, select ‘Disable driver signature enforcement‘ from the list. You can now load your modified driver. Reboot again once the driver is installed and all will be well.
----------------------------------------------------------------------------
Q. I cannot find Developer options to Enable USB Debugging
With Android 4.2 google have thought it would be funny to hide the Developer options screen in the Settings. This means you cannot enable usb debugging to communicate with your device. To show the Developers options screen do the following:
Goto Settings, About tablet and tap your finger on the the 'Build number' text at the bottom 7 times (not too fast).
When you have tapped 3 times you will be given a countdown of taps until you become a 'developer'.
Once you are told you are now a developer you can go back to the Settings screen and can see Developer options.
You can now go into Developer options and enable usb debugging.
----------------------------------------------------------------------------
Q. I tried to enter the code for the professional version but the Toolkit says the code is incorrect
Make sure the code entered is for the correct Toolkit being used.
You need to make sure you start the Toolkit with the toolkit.exe file when activating and not the tkmain.exe file so the settings can be initialised or the code will not be accepted.
Also make sure you enter the code correctly as the characters are case sensitive.
[TOOLKIT] SKIPSOFT ANDROID TOOLKIT -GNEX VER- Drivers, Root, Recovery + MORE
GALAXY NEXUS - SUPPORTS ALL AVAILABLE VERSIONS
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports many Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT V1.4.1 [05th Oct 2015]
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* [NEW] use SkipRoot boot image to Auto Root device, install Busybox Binaries and rename Recovery Restore files [selected devices]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn’t corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Flash any part of a stock Nexus image to device [boot, system, recovery] – Great for fixing broken parts of firmware
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk’s to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Credits: ChainsDD for Superuser, Chainfire for SuperSU, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR ‘AUTO UPDATES’ DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE ‘QUICK PICKS’ SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE “ANY BUILD” OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).
MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
ChangeLog:
ToolKit v1.4.1 (05th Oct 2015)
+Added new upcoming devices to device selection screen
+Main files now signed with Digital Certificate to ensure files are original and safe
+Added file checker after device selection to check needed files are up to date
+Updated UniversalAdbInstaller for Windows 10 compatability
+Added driver installation option at startup for new installs
+Updated ToolKitClean.exe to allow users to update the main ToolKit.exe file to latest available version without having to download/install the whole ToolKit again (like when a new device is added or files/drivers updated)
+Improvements and minor bug fixes
+Installer now give option for Fresh Install (removes any existing device files) or Upgrade (to just update base files)
--------------------------------------------------------------
USEFUL INFORMATION
How to get into your FastBoot Mode
1. Turn your phone off
2. Unplug your usb cable if you have one plugged in
3. Keep holding the 'Volume Down' and 'Power' buttons to boot the phone into FastBoot Mode
How to get into Recovery
1. First boot into FastBoot Mode as described above
2. Scroll down with the 'Volume Down' button until it says 'Recovery mode' at the top and press the 'Power' button to enter Recovery
Show the Menu in the Stock Recovery Screen
1. Hold the Power button and keep holding as you press the Volume Up button quickly. The blue recovery menu screen should pop up.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
Amazing thread! This thread would probably be really helpful for newbies
Just a few suggestions:
1.)You might want to include how to flash custom kernels
and also that you can
2.)Clockwork Recovery can be instealled through Rom Manager
Nonetheless, great thread
mohitrocks said:
Amazing thread! This thread would probably be really helpful for newbies
Just a few suggestions:
1.)You might want to include how to flash custom kernels
and also that you can
2.)Clockwork Recovery can be instealled through Rom Manager
Nonetheless, great thread
Click to expand...
Click to collapse
Thanks
1. Added Step 7, how to flash kernels and Radios via CWM.
2. Added a Note at the end of the CWM flashing step for the Rom Manager method.
Mark.
mskip said:
Thanks
1. Added Step 7, how to flash kernels and Radios via CWM.
2. Added a Note at the end of the CWM flashing step for the Rom Manager method.
Mark.
Click to expand...
Click to collapse
No problem, and thanks for the additions
EDIT: Nevermind, didn't read the thread properly, sorry
Are you completely sure this will work with the LTE version? Being that it comes out tomorrow, I have yet to get mine. I also think it may be a christmas present.....nonetheless, I don't know if Verizon has made any changes to the bootloader or not. Have I anything to worry about or am I just being paranoid?
_AI_ said:
Are you completely sure this will work with the LTE version? Being that it comes out tomorrow, I have yet to get mine. I also think it may be a christmas present.....nonetheless, I don't know if Verizon has made any changes to the bootloader or not. Have I anything to worry about or am I just being paranoid?
Click to expand...
Click to collapse
The bootoader and root steps will definitely work paul has confirmed in his thread that superboot will work on LTE devices. Im not sure if CWM has been tested on an LTE device but if it doesnt work the stock Recovery image can easily be flashed via fastboot. Once you have CWM then you just need to find a Rom that will work on LTE devices as im not sure if the Roms are different.
No need to be paranoid as the GN is close to unbrickable as long as you can enter fastboot
Mark.
Very much appreciated! Thank you for the time and effort you put in to help out others. Coming from my G1, I am not up to date with the newer methods and this certainly gave me confidence to go forth with my GNEX.
I've flashed CWM through ROM Manager but still get the stock recovery in recovery mode - isn't that a fake flash anyways? Does anybody know if you can restore a nandroid via the stock recovery?
Sent from my GN
Hey thanks you alot, made me more comfortable messing with me "GN".
Much appreciated
Regards
Schmee
Thank you sir for taking the time to write this. Just went through the process successfully to flash a stock Google rom to remove the Samsung one from my phone as I want to get the rom updates quicker via Google vs waiting for the Samsung port. However, to ensure I get the updates via OTA, do I have to unroot/ relock bootloader? Does it hurt anything leaving it as is or do we need to button down again.
Thanks in advance.
Awesome thread!
Quick Q though, if im currently using a custom ROM, when i use the advanced restore option in CWM, can someone quickly describe what each option will do to my phone?
ie.
Whats will happen if im running custom ROM and i select restore boot? restore system? restore data? restore cache? restore sd-ext?
Thanks in advance!
I have unlocked the bootloader, and flashed cwm. When I try to install from sdcard, I get this error: E:Can't mount /sdcard/
Any suggestions?
tristan202 said:
I have unlocked the bootloader, and flashed cwm. When I try to install from sdcard, I get this error: E:Can't mount /sdcard/
Any suggestions?
Click to expand...
Click to collapse
To copy the rom to your Internal Storage you need to reboot your phone into Android, then connect the usb cable and copy it across using your file manager. Then you can reboot into CWM and flash the Rom.
Mark.
ahqball said:
Awesome thread!
Quick Q though, if im currently using a custom ROM, when i use the advanced restore option in CWM, can someone quickly describe what each option will do to my phone?
ie.
Whats will happen if im running custom ROM and i select restore boot? restore system? restore data? restore cache? restore sd-ext?
Thanks in advance!
Click to expand...
Click to collapse
I will add this to the FAQ as I build it up:
> Restoring boot will restore your boot image which contains the kernel. Useful if you try custom kernels and something goes wrong with it.
> Restoring system will restore your system files (Rom).
> Restoring data will restore your installed apps. Good if you install a new rom and do a wipe before flashing (which will format the data partition). If you flash a new Rom without wiping the data partition isnt usually touched.
> Not exactly sure about cache..
> Galaxy Nexus doesnt have sd-ext so no need to worry about that.
Mark.
TorontoR said:
Thank you sir for taking the time to write this. Just went through the process successfully to flash a stock Google rom to remove the Samsung one from my phone as I want to get the rom updates quicker via Google vs waiting for the Samsung port. However, to ensure I get the updates via OTA, do I have to unroot/ relock bootloader? Does it hurt anything leaving it as is or do we need to button down again.
Thanks in advance.
Click to expand...
Click to collapse
Not so sure how a stock image is affected. At worst case you will still get the update notification but the install will fail. As long as you have the latest build on your phone then you wont get any notification so you could easily flash the latest CWM Stock image as it is made available.
You just cant hurt this monster
Mark.
DJ "suMo* said:
I've flashed CWM through ROM Manager but still get the stock recovery in recovery mode - isn't that a fake flash anyways? Does anybody know if you can restore a nandroid via the stock recovery?
Sent from my GN
Click to expand...
Click to collapse
There is an auto recovery restore system on stock android builds so when the phone is rebooted it restores the stock recovery image.
Remove 'recovery-from-boot.p' from /system and it wont restore the stock recovery after you flash CWM.
Mark.
Thanks for this. Do you have to delete or can you just rename that file?
Hey bro.tks for this but need some clarification if you don't mind
1.if I flash a new rom in cwm from stock rom,and I do a superwipe,will all my data like music etc from internal storage get wiped as well?
2.you mentioned above about using restoring data option under advanced in cwm,when do I do this?right after I flash or after I have booted to android and go back to cwm and click restore data?
Please advice

[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!

[Guide] Installing Custom Rom Xperia Ion (CM)

I have made this thread as a desperate attempt to minimize questions such as the one that follows. I have seen these questions clog up development threads and the responses are usually short and the user if extremely new to android, gets lost.
In making this guide, I have chosen to use the custom rom: CM-10 for Locked Bootloaders Rom shared by @optimumpro
I chose this rom due to the simple fact that the question was based from that thread AND because I myself use this rom.
qzone23 said:
Sorry to bother you all with my annoying questions, but, as far as twrp or cwm go, will titanium
backup suffice and how exactly do I install the rom?
Sent from my LT28at using XDA Free mobile app
Click to expand...
Click to collapse
The instructions as given are
1. Have JB latest Stock Kernel, Roger's Baseband in case of LT28i, Root and Recovery
2. Format System/Data/Cache in TWRP or Mount and Format the same in CWM
3. Install the ROM and Reboot. Nothing else is needed
here is the general breakdown if you are moving from Stock on XPERIA ION to in this example, the CM 10 rom for locked bootloaders.
------If from ICS, follow from step 1
------If from JB, follow from 1a
1)
1a)----Flash----
-You need flashtool (http://www.flashtool.net/index.php)
-You need the firmware (http://forum.xda-
developers.com/showthread.php?t=1752345)
You need to download the JB for Generic International Firmwares - LT28h and if you wish to have LTE for AT&T devices then
you must also download the latest JB for rogers (Rogers Stock Firmwares - LT28i)
First, Flash the Generic Ftf
(optional) For LTE, flash the Rogers Firmware with EVERYTHING excluded except for baseband
1b)----Root----
There are a few methods but personally I use:
http://forum.xda-developers.com/showthread.php?t=1886460
Download the current version (happens to be v33 at the moment)
-Connect phone to computer with Android Debugging Enabled with Unknown Sources
-Run the required File and follow the instructions in the Command Prompt Window
--It will complete the required steps and upon reboot, you will have root access.
-Install Busybox after root
1c)----Recovery----
-http://forum.xda-developers.com/showthread.php?p=30149181#poststop
--Download RECOVERY for XperiaIon v.4.zip
-Connect phone with same requirements for root
--extract and run the .bat file->done
MAKE SURE YOU HAVE THE SPECIFIC ROM YOU WANT ALREADY ON YOUR INTERNAL OR EXTERNAL SD CARD BEFORE CONTINUING you have been warned
2) CWM MENU SELECTION
-Upon Reboot a BLUE LED should appear, immediately hold the volume DOWN key, CWM menu should appear
--Scroll using the volume and select using the power key--
-Go to Storage and as instructed by the CM 10 Rom I specified, wipe System/Data/Cache
For more information on the CWM menu breakdown visit:
http://forum.xda-developers.com/gala...neral/ref-cwm-clockworkmode-menu-options-t1542857
------OPTIONAL BACKUP------
-If you would like to make a backup of your current rom, go to option 4 the Nandroid menu and select the Backup Option
3) INSTALL
Then go back to main menu, to go the INSTALL MENU
and select choose zip from (external/interenal (depends on where you stored the zip))
-navigate to zip location-> select-> yes-> install
-----wait patiently-----
Reboot
Done
I think you should talk about making data backup too. For a newbie, he may never know that he should first have a back up and how to go about it.

[UPDATED][TUTORIAL][REDMI 1S]Dual-System Installation in detail!!

First of all i would like to thank ->Tsing Yi qingyi @http://weibo.com/1048297887 for his effort to make this possible!!
As some fellas request....I'm Just giving a detailed guide for the process to have Dual-System{Dual_Boot} in our little dragon @rmani :laugh:
DOWNLOADS:
1.HM1S-Sysrec.zip: http://pan.baidu.com/s/1jGzfP3o
2.M1S-System-Menu1.3-test.zip: http://pan.baidu.com/s/1qWDN5u8
if want it in a simpler way download 3
3.Mokke + Miui.zip: http://pan.baidu.com/s/1sjCyI3z
:good: @bhushan2k
MIRROR Link: https://drive.google.com/folderview...NrYmkzLTN3WmlONEczVnlzajg0emo3ZHM&usp=sharing
WARNING!! : Installation of Dual System is Complecated, include data loss and may brick your devices and i'm not responsible for any kind of Loss or Failure..!!
CAUTION!! : During this Process, Your Phone gets Factory Reset and all internal memory gets wiped!! Make a Backup of all internal data as well as a nandroid to extrnal sd!!
***//For Users coming from MIUI rom and want to have MIUI on one of the Systems continue from step 1-2 and read NOTE and in step 3 tick the checkbox promting special!
STEP1:
Flash HM 1S-Sysrec.zip...[after flashing, recovery gets rebooted].......In this Process Phones Intrernal Memory gets formatted and current ROM gets Factory Reset!
STEP2:
Flash HM 1S-System-Menu1.3-test.zip...Select English->Press Next->Accept and Press Next->Enter the function->Install and uninstall->Install the dual system.....This installs Dual-System and gets rebooted to recovery, meaning dual system got installed!!
**NOTE 1 : If you wish to install mokee+MIUI which was provided #3 in download section.....You can flash that mokee+MIUI.zip here, without proceeding further...and reboot!!
**NOTE 2 : Now we have two System partitions installed and we are on system1, which already have the previous Rom residual and System2 is Void!!
**NOTE 3 : If you want to have a fresh Installation of AOSP Rom on System1, you can directly flash a AOSP rom of your choice! or continue with previous rom!
STEP3:
Now that we have a Rom in System1 [MIUI or a AOSP]....so we need to install system switching software in it....
Flash HM 1S-System-Menu1.3-test.zip, Follow the prompts to enter the main menu -> enter the function -> Install switching software -> System I-> Next [check special for MIUI users]...and reboot system!!
STEP4:
After the completion of boot process you will see a system changing app....open the app ->give root permissions and the phone gets rebooted and gets stuck at mi logo indicating we are in System2....Now Enter Reovery (Powr+VolUp same time)
STEP5:
Flash a ROM of your choice...."and dont reboot!"....after flashing rom again flash HM 1S-System-Menu1.3-test.zip, Follow the prompts to enter the main menu -> enter the function -> Install switching software -> System 2-> Next....now reboot !!!.. which will take you to ROM installed in System 2 ....
STEP6:
After the completion of boot process, now that you are in System2, will see a system changing app as well ....open the app ->give root permissions and you will be able to switch to the other system/ROM........
////**Manual System switching process: **///
Flash HM 1S-System-Menu1.3-test.zip Follow the prompts to enter the main menu -> enter the function ->System Switching -> and select a System of your choice and proceed and Finally reboot !!!
***///Wanna change rom or try a new ROM keeping the other still///***
Stay on the System on which you want to try a new ROM....Reboot to recovery...
Flash HM 1S-System-Menu-Test1.3.zip and Follow the prompts to enter the main menu -> enter the function ->clear data->
Continuing which will wipes and factory Resets the current Rom....After proceeding further enter RECOVERY....
and Flash the ROM u wanna Try...and repeat #STEP5 and install switching software on new system!!(Hope U Understand)!!!
For reverting back...we need to flash Sysrec.zip once again and flash Sysmenu.zip and follow uninstall procedure...then everything will be normal...
...for further questions comment below...............Give :good: if useful!!!....
Happy Flashing!!!
If anything Goes wrong...How to revert Back ?
Sent From My Redmi
1.Does we need to follow a unbrick tutorial
To revert back OR just restore a backup
2.Should we install twrp and continue or
Continue with philz recovery
3. Can we access system partition of system 2 from system 1 and vise versa
Sent from my Redmi 1S using XDA Free mobile app
can we use rom??and can i install custom kernel for both roms??
as9333 said:
1.Does we need to follow a unbrick tutorial
To revert back OR just restore a backup
2.Should we install twrp and continue or
Continue with philz recovery
3. Can we access system partition of system 2 from system 1 and vise versa
Sent from my Redmi 1S using XDA Free mobile app
Click to expand...
Click to collapse
For reverting back...we need to flash Sysrec.zip once again and flash Sysmenu.zip and follow uninstall procedure...then everything will be normal...
2.cwm or twrp...u can try philz.. Dunno..
3.We can browse sys2 directories from sys1 & vice versa
how can i restore my data on my first rom? help me plz
chauhansonu104 said:
how can i restore my data on my first rom? help me plz
Click to expand...
Click to collapse
I don't think restoring nandroid data will work... Because....as u can see there are two two folders inside root/data/.......by restoring data from recovery will first wipes current root/data content and writes content from backup....so no dual-system!!! Hope you understand....tell me whether u have installed dual system? If so once see inside root/data /....u will get it!
sathyakaushik4 said:
can we use rom??and can i install custom kernel for both roms??
Click to expand...
Click to collapse
We can install gapps for system1 and system 2 separately....and can install custom kernels as well...!
very good tutorial.. thnx for this.. I tried on my own and couldnt manage.. will try again this time following ur simple steps..
Just a doubt if we install cm r18 and PAC ROM with custom kernel can we install kernel patch for both the ROMs
Will cm work
Can we boot into sys 2 within recovery
If sys 1 got bootloop
Sent from my Redmi 1S using XDA Free mobile app
Great, Thanks for info, will try after my exams, one again Thank You Very Much.
@as9333
i guess we can switch between system 1 & 2 from recovery itself.. just flash the zip and explore through its aroma installer and see theres that option to switch...
as9333 said:
Just a doubt if we install cm r18 and PAC ROM with custom kernel can we install kernel patch for both the ROMs
Will cm work
Can we boot into sys 2 within recovery
If sys 1 got bootloop
Sent from my Redmi 1S using XDA Free mobile app
Click to expand...
Click to collapse
Note 1: Two Roms will be installed with two separate system partitions....all u can do things like installing custom add-ons or patches either being on system1 or system 2..use switching software to switch between system partition 1or 2...
Note 2: U can switch to system of ur choice from recovery...by flashing HM1s-system-menu.zip...there u will c an option to switch system...hope u understand if u had read the procedure with a bit of pathence!
Thanx alot bro! now im running miui 6 and carbon rc6..
a small doubt.. in the dual boot system menu there are 2 options saying system change(install systemchange and direc system change or sumthing) whats the second one? what will it do?
had hard time downloading from chinese server... here is gdrive mirror link @pawanzZ
N-Gavin said:
Thanx alot bro! now im running miui 6 and carbon rc6..
a small doubt.. in the dual boot system menu there are 2 options saying system change(install systemchange and direc system change or sumthing) whats the second one? what will it do?
Click to expand...
Click to collapse
Read note2 of the above replied post...ur doubt will be clarified!!
bhushan2k said:
had hard time downloading from chinese server... here is gdrive mirror link @pawanzZ
Click to expand...
Click to collapse
Mk+miui is not mandatory to download!!!.... Remaining 2 are <30mb...any ways u made it easy ...tnx for mirror!!
internal storage
Thnx for the great tutorial
but i still have few question
First ,do external storage also wipe out?
Second ,are app installed in each rom are shared among them,includin data?
Hsmetric181 said:
Thnx for the great tutorial
but i still have few question
First ,do external storage also wipe out?
Second ,are app installed in each rom are shared among them,includin data?
Click to expand...
Click to collapse
figured it out myself,for everybody else
won't format external sd card
and apps will be installed separately
Maybe some mistakes in step 2. The dev recommended unmount system, data and cache before installed Dual-System (doesn't matter really). Some user may need install it twice to success for unknown factors. And as I know on earlier versions, after you installed Dual-System, both partitions are empty. You need to flash a rom to system 1. But I haven't try v1.3 yet so I don't know if anything changed.
The tutorial seems so long but it's very reasonable to proceed.
1. (unnecessary for the 1st time) recover your phone's status - flash sysrec.zip
2. install the dual-boot system - flash into aroma and choose the option
3. flash a rom to current (1st) system - flash it in recovery
4. (optional but recommended) install a switcher in the rom - install it in the aroma, caution the options, don't choose the wrong system
5. switch to system2 - switch directly in the aroma, or [ boot your phone to use the switcher app (after that plz press vol+ to enter recovery because system2 is empty now)]
6. flash another rom to current (2nd) system - just flash it in recovery, it will be in system2
7. (optional but recommended) install a switcher in the rom - install it in the aroma, caution the options, don't choose the wrong system
now you have dual system installed.
For changing between systems, use the switcher (if installed) or change in the aroma installer.
For replacing a rom, switch to the rom you unwanted, and reboot to recovery and flash the new one.
For clear data, don't use recovery,it will clear both. Use the aroma (change to the system you want to clear data and choose clear current).
For miui user, special for miui is actually for miui 6 because /system/app can't get root permission in miui 6.
For uninstall, do it in aroma and then flash sysrec.zip
@pawanzZ

Htc One M9 Camera

This Is Working fine on my grand duos And s5. If you are facing any problem so please flash only camera but resolution patch is working fine on my phone .
First Of All M Sorry For My Previous post Because It Is A Alpha Version And But Is working fine on my s5 but I am trying to improve it
Prerequisites:
■A rooted device with TWRP/CWM
■ Recovery installed. KK (not tested) or Lollipop based AOSP or CM ROM.
■Make sure you have 90MB free system space available on the device.
How to Install If you have been using an AOSP or CyanogenMod ROM on your phone, you probably won’t need instructions on flashing a Zip. Still, I am providing some quick steps.
1. Download both the Zip files from above and copy them to your phone.
2. Reboot your device to CWM/TWRP recovery.
3. First of all, create a backup of your ROM as precaution.
4. Select the Install option, navigate to HTC One M9 camera Port V1.zip and flash it.
5. Then also install the resolution patch file the same way.
6. Wipe cache.
7. Return to the main menu and reboot the device.
Download camera - http://www.mediafire.com/download/4abd4cytzwbw3i9/HTC+One+M9+camera+Port+V1.zip
Download - Resolution Patch http://www.mediafire.com/download/7h12ol3i8se1ham/HTC+One+M9+camera+Port+V1.1+Resolution+Patch.zip
In settings not found - save photo to SD card
Working well on cm12.1 good job
Screenshots?

Categories

Resources