Develop Bugs

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

[Tutorial] [Find 7] How to install Cyanogenmod Nightly on Find 7 X907x (OS X)

Note: This is for the Find 7 (the QHD version) not the 7a. I tested it on the x9076.
Note 2: I am on a Mac, so these instructions explain how to install Cyanogen on a Mac.
Note 3: If this is the wrong forum feel free to move it.
Note 4: The Find 7 is one of the few phones you can install 3rd party ROMs on without voiding your warranty.
Download Files
Get the simplified Fastboot and ADB package from here:
http://www.oppoforums.com/threads/find-7a-s-team-gummy-recovery.17476/
Get the boot.img from here:
http://www.oppoforums.com/threads/find-7a-s-team-gummy-recovery.17476/
Get Cyanogenmod nightly for 7a here (the branch supports both 7 and 7a):
http://download.cyanogenmod.org/?device=find7
Get Cyanogenmod google apps for KK:
http://wiki.cyanogenmod.org/w/Google_Apps
Get Android File Transfer for OS X here:
http://www.android.com/filetransfer/
You have now downloaded all the components you need.
Copy Files to your Find 7
Put all the zip files into a fresh folder to make them easy to find.
Rename the .img file to recovery.img.
Install Android File Transfer and restart your Mac or restart Finder.
Plug your phone into your Mac
Close the dialog informing you that the filesystem of the device you plugged in can't be read.
Android File Transfer will pop up automatically and open a folder view. If it doesn't, pull down the shade on your phone and try toggling between the two filesystem options (Image and File).
Copy the Cyanogen zip and the Google Apps zip onto your phone in the Download folder on your Find 7.
Install Bootloader
Turn on your phone and hold Power until the power off menu pops up.
Touch Power Off.
Immediately press and hold Volume Up.
Your phone will reboot into Fastboot.
Note: The words "Fastboot" appear in tiny, dim letters in the middle of the display.
Open a terminal on your Mac.
cd into the folder where you put your files.
Type the following commands:
Code:
chmod +X ./fastboot
./fastboot flash recovery recovery.img
You'll see some status go by on the terminal, then it will return to the command prompt.
Reboot Into Recovery, Wipe and Flash New Software
In your Mac terminal type:
Code:
./fastboot boot recovery.img
Wait for the recovery to load on your Find 7 and show the menu.
Use the volume down key to move to Wipe Data & Factory Reset.
Select this option and confirm.
After the wipe is done, go to Install Zip from SD Card (you're not actually installing it form an SD card, it just says this because the internal flash storage emulates an SD card).
Browse to the folder you put your Cynogen and Gapps zips into.
Select the Cyanogen zip to flash it and confirm you want to do that.
Repeat the process to flash the Gapps zipp.
Use +++GO BACK+++ until you return to the main menu.
Select Reboot.
If all goes well your phone will boot into Cyanogenmod.
The first boot can take several minutes, so be patient and don't yank the battery.
After first boot you'll be taken through the onboarding.
When the onboarding is done your Google stuff will start to syncronize and you'll be notified that you need to update Google Play Services.
Update Google Play Services, wait for Android to finish downloading app updates, then reboot your phone.
You're now ready to use Cyanogen on your Find 7.
Note: I found that upgrading the Google Search app included in the GApps package with the one from the Play Store breaks Google Now hotword detection on my phone. If you encounter this you can wipe, re-install gapps package, then go into the Play Store, browse to Google Search, hit the menu key and uncheck Automatic Update to stop it updating when you use Update All.

Note: This is a pretty unstable build.
In my testing I found that it crashed and hung a lot, and that many apps did not work as expected (force closes, refusal to install apk's, etc).
Also you will lose all the special camera features. You can't just port the camera apk because it has some system dependencies.
Ultimately I went back to ColorOS because this build doesn't seem to be ready for daily use.
Here's a bonus tip: If you install the Chinese version of ColorOS from here, you can go to About Phone > Updates and update to 2.14 Beta.
Edit: Gummy is a really good, stable, functional ROM. The only thing it's missing is the special camera app.

looking forward for Windows' instruction :laugh:
Anyway, thank you so much for posting instruction!

Is the VOOC still working? Is the 3GB apps limitation gone?

doomboss, attached is the fastboot with the gummy recovery in place for windows.
Just put your phone into fastboot follow the instruction of majikfox by putting the CM and Gapps zip file into your phone root folder.
Open command prompt on the fastboot folder by clicking shift+right click =Open command window here.
Then type the command:
fastboot flash recovery recovery.img
Once done
type:
fastboot boot recovery.img
and follow on the instruction of majikfox
1.Wait for the recovery to load on your Find 7 and show the menu.
2.Use the volume down key to move to Wipe Data & Factory Reset.
3.Select this option and confirm.
4.After the wipe is done, go to Install Zip from SD Card (you're not actually installing it form an SD card, it just says this because the internal flash storage emulates an SD card).
5.Browse to the folder you put your Cynogen and Gapps zips into.
6.Select the Cyanogen zip to flash it and confirm you want to do that.
7.Repeat the process to flash the Gapps zipp.
8.Use +++GO BACK+++ until you return to the main menu.
9.Select Reboot.

lexta said:
Is the VOOC still working? Is the 3GB apps limitation gone?
Click to expand...
Click to collapse
I'm having the same question also... looking forward! :good:

Which gapps do u need? 4.4.4 or 4.4.3?

bobbydigital222 said:
Which gapps do u need? 4.4.4 or 4.4.3?
Click to expand...
Click to collapse
Both version are fine just that do not download the version that will get overwritten by google camera.
Read all the package description. Safer to download the Micro modular package

kaiwong1020 said:
I'm having the same question also... looking forward! :good:
Click to expand...
Click to collapse
VOOC is not software related, so it should work.
Skickat från min GT-I9300 via Tapatalk

Exculpo said:
VOOC is not software related, so it should work.
Skickat från min GT-I9300 via Tapatalk
Click to expand...
Click to collapse
so CM should not have the 3GB apps storage issue :fingers-crossed:

Exculpo said:
VOOC is not software related, so it should work.
Skickat från min GT-I9300 via Tapatalk
Click to expand...
Click to collapse
VOOC is a hardware thing. It worked fine for me.

My answer was regarding whether the VOOC charger would work or not in 3rd party ROMs. The storage limit isn't that easy to just incorporate in a ROM since changes in the partition table would have to be made. Just settle with 3Gb for now and wait for a safer way to unify/modify the partitions. Who knows, you just might be fine with 3Gb for now
Skickat från min GT-I9300 via Tapatalk

Exculpo said:
My answer was regarding whether the VOOC charger would work or not in 3rd party ROMs. The storage limit isn't that easy to just incorporate in a ROM since changes in the partition table would have to be made. Just settle with 3Gb for now and wait for a safer way to unify/modify the partitions. Who knows, you just might be fine with 3Gb for now
Skickat från min GT-I9300 via Tapatalk
Click to expand...
Click to collapse
Just read in oppoforums that CM will be coming real soon for find7 but is a standard version. Hopefully the solution for unifying the storage will be ready soon.Everyone is waiting for that

lexta said:
doomboss, attached is the fastboot with the gummy recovery in place for windows.
Just put your phone into fastboot follow the instruction of majikfox by putting the CM and Gapps zip file into your phone root folder.
Open command prompt on the fastboot folder by clicking shift+right click =Open command window here.
Then type the command:
fastboot flash recovery recovery.img
Once done
type:
fastboot boot recovery.img
and follow on the instruction of majikfox
1.Wait for the recovery to load on your Find 7 and show the menu.
2.Use the volume down key to move to Wipe Data & Factory Reset.
3.Select this option and confirm.
4.After the wipe is done, go to Install Zip from SD Card (you're not actually installing it form an SD card, it just says this because the internal flash storage emulates an SD card).
5.Browse to the folder you put your Cynogen and Gapps zips into.
6.Select the Cyanogen zip to flash it and confirm you want to do that.
7.Repeat the process to flash the Gapps zipp.
8.Use +++GO BACK+++ until you return to the main menu.
9.Select Reboot.
Click to expand...
Click to collapse
I actually managed to install custom recovery and flashed CM11 already But I am just waiting for someone to post an instruction so that other people can have a clue of what they need to do (I am too lazy to write it ). Looks like this is the post that will help people using Windows :good::good::good::laugh::laugh::fingers-crossed:

Hmm. Fastboot cant find the device. Do we need drivers for Oppo find 7?
Edit: Switched pc. Now erverything works.

Exculpo said:
My answer was regarding whether the VOOC charger would work or not in 3rd party ROMs. The storage limit isn't that easy to just incorporate in a ROM since changes in the partition table would have to be made. Just settle with 3Gb for now and wait for a safer way to unify/modify the partitions. Who knows, you just might be fine with 3Gb for now
Click to expand...
Click to collapse
I tried to check this "limitation" and you could go really far away from it. I installed Asphalt8 (1GB) + GT Racing2 (1.4GB) + The Cave (1.5GB) and all my used apps (some have more than 100MB apk's size) and I still have space left (and no low storage notification).
I'm using ColorOS-1.2.2i without any modifications (it's just rooted) ...
Enjoy !

MrJiM said:
Hmm. Fastboot cant find the device. Do we need drivers for Oppo find 7?
Edit: Switched pc. Now erverything works.
Click to expand...
Click to collapse
When you plug in your phone, it should show you the OPPO driver. Double click on it to install the driver. I don't know if you need driver to access fastboot but doesn't hurt to try

last nightly (cm-11-20140703-NIGHTLY-find7) not work
blank screen when lock then unlock

I've been running the 7/3 nightly all day...no problems...no black screen.

Are you using the X9076?
Sent from my X9076 using XDA Free mobile app

[TUT] How to install CyanogenMod 11 /or any other ROM on your Xperia S 6.2.b.1.96

Okay guys,
I spent a whole day yesterday to exterminate lame SONY's firmware, and get a refreshment alternation
so I gathered all tutorials, which I had followed to give my Xperia S new soul, and made this all-in-one tutorial for anyone, who's not sure how to do it.
Big thank to DooMLoRD, who's is making all this awesome tools and stuff to make our Xperias alive again.
Before proceding, Your Xperia S should run on the latest official Sony's firmware (6.2.b.1.96). Otherwise...otherwise you probably ought to update it to the latest version.
Here are the links to the sites I used. I also recommend you to check them out, because there may be a more recent version of a file:
http://forum.xda-developers.com/showthread.php?t=2555243
http://forum.xda-developers.com/showthread.php?t=2447319
http://forum.xda-developers.com/showthread.php?t=2417672
1. Bootloader unlock
Checking (source: JuniorMember's post: http://forum.xda-developers.com/showpost.php?p=44713761&postcount=14)
1.1.1. In dial pad, type in *#*#7378423#*#*
1.1.2.Go to Service Info > Configuration
1.1.3. And check the Rooting Status
If it's Bootloader unlock allowed:Yes/No, then its not unlocked. If it says NO, you're not able to unlock it.
And if it's Bootloader unlocked:Yes, then it's (already) unlocked.
Unlocking (source: DooMLoRD's tutorial)
[ before we begin unlocking bootloader ]
1.2.1 Get the IMEI code for your device: type *#06# in phone dialer to find it out; note only the digits (no dashes)
1.2.2 Download the fastboot package with usb drivers (alternate drivers if the ones in package dont work OR this)
IMPORTANT: if you are using Windows 8 you will need to enable few things to allow driver installation
1.2.3.Make sure you have a windows PC with USB cable to connect the phone
1.2.4.Power down your phone and keeping the Volume Up button pressed connect the USB cable to PC; this will trigger FASTBOOT mode and windows will start driver installation, extract the above package and point the driver install to that location (usb_driver) folder.
If a phone enters but does not stay in a fastboot mode:I had that kind of problem, but I'm not sure how I actually fixed it; I only remember I did that:
1.2.4.1. Download and install Flashtool . After Installing, go to the folder where fastboot is installed and look for drivers folder; there you'll find Flashtool-drivers.exe. Install that: Be aware that there are Flashboot and Fastboot drivers at the bottom or at the top of the list Check also your phone's name.
1.2.4.2. If still does not work go to Device manager, trigger fastboot mode, connect to your computer, and quickly (when S1 Boot or sth like that appers in Device Manager) click with right mouse button (go to properties), then update driver and point to (usb_driver) folder in fastboot_with_Android_USB_file folder -> step 1.3.6.
1.2.5. Once drivers are installed just disconnect cable and power on device
[ how to unlock ] (official way)
1.3.1 First, you should confirm that it is possible to unlock the boot loader of your phone by checking the service menu: steps 1.1.1 - 1.1.3
1.3.2 Go to: http://unlockbootloader.sonymobile.com/ and read everything!
1.3.3 At the bottom click 'Start Unlocking the Bootloader'. Scroll to the bottom of the page and click "Continue" You will get numerous prompts, read all info and if you agree, click on "Accept"/"OK"/"Proceed"
1.3.4 Finally you will get a "Create Unlock request" page, enter your IMEI (sometimes the last digit needs to be removed for this to work), name and email address
1.3.5 You should now receive your unique unlock key via EMAIL, SAVE THIS KEY SAFELY
1.3.6 Extract fastboot_with_Android_USB_file.rar and open fastboot folder
1.3.7 Hold SHIFT and right click on the background of the folder Select 'Open command window here'
1.3.8 Connect your phone in fastboot mode (turn phone off, hold Volume UP button and plug in USB Cable) [make sure drivers are installed as explained above)
1.3.9 In the cmd windows type in fastboot.exe -i 0x0fce getvar version
1.3.10 If a value is returned (it will return 0.5), it means the phone is correctly connected
1.3.11 Type in fastboot.exe -i 0x0fce oem unlock 0xKEY and replace KEY with the key which u received earlier.
1.3.12 You're device should now be bootloader unlocked. You can check by followin steps 1.1.1 - 1.1.3.
2. Root (source: DooMLoRD's tutorial)
2.3.1 Download the three files from the download section in this post.
2.3.2 Open FlashTool and flash the XperiaS_LT26i_6.2.B.0.211_KernelOnly.ftf - 6.36 MB file, this is JUST the kernel of an older firmware which was rootable.
2.3.3 How to flash Put XperiaS_LT26i_6.2.B.0.211_KernelOnly.ftf to firware folder, which you can find in Fastboot's installation folder. Then hit the lighting strike, select Flashboot mode and select the kernel and hit flash and follow instructions how to enter flashmode.
2.3.4 Now once flashing is done reboot device and connect to PC in usb debuggin mode
2.3.5 CLOSE FLASHTOOL <<< VVVIMP STEP (Very very very important step it took me some time to figure out its meaning)
2.3.6 Extract the file DooMLoRD_Easy-Rooting-Toolkit_v18_perf-event-exploit.zip to root directory on c:\
execute runme_ file corresponding to your OS on desktop PC, this will execute a SPECIAL version of DooMLoRDs easy rooting toolkit <<< VVVIMP STEP
2.3.7 the above step is crucial! if you use any older version of the toolkit then IT WILL NOT WORK!
2.3.8 after rooting is over the device will restart
2.3.9 you can verify if device is rooted by checking for SuperSU app (it is the newest version)
2.3.10 once that's done, power down device and open FlashTool again
2.3.11 now flash XperiaS_LT26i_6.2.B.1.96_KernelOnly.ftf - 6.33 MB file to get back to the true kernel for the firmware
that's it after flashing is done just disconnect and power on device and enjoy rooted phone! Check with Root Checker app from GPlay.
3. CWM Recovery (source: hm9408's thorough version of DooMLoRD's tutorial)
3.1 Go to google play and download busybox. Once installed, open the app and tap install Also, make sure, you have SuperSU installed.
3.2. This should be relatively easy now. Your phone is now rooted, and you will now flash CWM Recovery on your phone. For this, hm9408 found a quick installer by DooMLoRD.
3.3 Just extract it anywhere, run it (cwm-install-en.bat, press Enter 3 times and it will start) while your phone is connected via USB, and you should be just fine. I had to do this step twice, because I didn't know you have to grant something with SuperSU. So during the process, watch the phone's screen.
3.4 You know CWM was flashed correctly when you shut down your phone, turn it on and your see the LED turns on BLUE when the Sony logo comes up. When it does, press the Volume Up button and the LED should turn GREEN for a couple of seconds, then boot into Recovery.
4. Installing custom ROM and gapps (google apps)
There's a link toCyanogenMod 11 beta 3 by RaymanFX which has already included kernel.
Other ROMs may not have included kernel, so you'll have to (1) flash it with Flastool, if it has kernel extension or (2) install it via recovery, it it has .zip extension.
4.1 Copy your ROM and gapps (their extensions have to be .zip.
4.2 Boot into recovery (step 3.4).
4.3 Navigate (with volume + and -, and power to select) to install zip, then select the file of you rom, install it, then install also the gapps by selecting the gapps.zip.
4.4. This is the most important step, DO NOT SKIP IT AT ALL COSTS For God's sake, in the main menu, wipe the cache and partitions and dalvik's cache. (I'm not sure if it's available to wipe dalvik's cache, but if it is, wipe it).
I forgot to wipe, and, holy cow, almost lost my pants, because phone didn't start, there was only sony's logo, slowly passing away again and again.
Well if that happens, look for an Xperia S firmware (e.g.) and appropriate kernel (e.g.), flash them via flashtool and wipe your sweat .

I think for a 2 years old phone, everybody should already know how to do this.
Or i think most of the people here on Xperia S XDA do already know how to do this.

xDroidZz said:
I think for a 2 years old phone, everybody should already know how to do this.
Or i think most of the people here on Xperia S XDA do already know how to do this.
Click to expand...
Click to collapse
Lol ya.

Sure?
xDroidZz said:
I think for a 2 years old phone, everybody should already know how to do this.
Or i think most of the people here on Xperia S XDA do already know how to do this.
Click to expand...
Click to collapse
I've had it for 2 years, but spent a whole day yesterday to install CM, because I struggled with fastboot drivers for 4hs, then 1h to root it, then another 2hs to properly install CWMrecovery, because I didn't know I have to have BusyBox installed and then I didn't wipe the cache and had to do everything again. And don't say me everybody should know that, because there are people who does not even try to do that, because then don't konw where to start and nothing.
Cheers!

Joej970 said:
I've had it for 2 years, but spent a whole day yesterday to install CM, because I struggled with fastboot drivers for 4hs, then 1h to root it, then another 2hs to properly install CWMrecovery, because I didn't know I have to have BusyBox installed and then I didn't wipe the cache and had to do everything again. And don't say me everybody should know that, because there are people who does not even try to do that, because then don't konw where to start and nothing.
Cheers!
Click to expand...
Click to collapse
are you kidding me? it takes me max 1 hour to read tutorial, unlock BL, flash custom kernel and flasch CM rom :laugh:

Joej970 said:
I've had it for 2 years, but spent a whole day yesterday to install CM, because I struggled with fastboot drivers for 4hs, then 1h to root it, then another 2hs to properly install CWMrecovery, because I didn't know I have to have BusyBox installed and then I didn't wipe the cache and had to do everything again. And don't say me everybody should know that, because there are people who does not even try to do that, because then don't konw where to start and nothing.
Cheers!
Click to expand...
Click to collapse
Nah. Max is 1H. there are alot of TUT already. but thanks anyways for this TUT helps alot of people who are actually new to this device

dobi235 said:
are you kidding me? it takes me max 1 hour to read tutorial, unlock BL, flash custom kernel and flasch CM rom :laugh:
Click to expand...
Click to collapse
It takes you one hour once you exactly know how to do it and in case you already have all files downloaded.
And about tutorials: they're often incomplete. In my case, I struggled with finding drivers for fastboot and making them work 4hs. The unlock tutorial says to install one drivers then try another, but none of them worked. So it took me time to search forums and find something out. Here, I wrote what I'd done, so anyone else would know what to do.
Edit: every tutorial about unlocking says Windows should report unsuccessful installation when you connect the device in fast boot mode. Well, my didn't report that, so I wasn't able to point to the usb_folder. And then phone booted up after 5secs in fastboot.

Joej970 said:
It takes you one hour once you exactly know how to do it and in case you already have all files downloaded.
And about tutorials: they're often incomplete. In my case, I struggled with finding drivers for fastboot and making them work 4hs. The unlock tutorial says to install one drivers then try another, but none of them worked. So it took me time to search forums and find something out. Here, I wrote what I'd done, so anyone else would know what to do.
Edit: every tutorial about unlocking says Windows should report unsuccessful installation when you connect the device in fast boot mode. Well, my didn't report that, so I wasn't able to point to the usb_folder. And then phone booted up after 5secs in fastboot.
Click to expand...
Click to collapse
no it took me hour to search for tutuorials (doom has for root and for unlocking BL too), read that, backup TA partiton, unlock, root, flash... DONE

I needed an whole afternoon, too! If you have to read everything from beginning and you are not able even to deal with the technical terms it needs long time. So, if I wouldn't have done it before, this tutorial would have been very useful to me :good:

magician
dobi235 said:
no it took me hour to search for tutuorials (doom has for root and for unlocking BL too), read that, backup TA partiton, unlock, root, flash... DONE
Click to expand...
Click to collapse
Well okay. Then write that down to a paper and stick it to a mirror, so you'll see your extraordinary achievement every time you wake up, and be proud of yourself, cause you did all that for the fisrt time in only one hour, although everyone else needed an afternoon. You're probably the smartest person I've ever seen, cause you apparently do magic :good:
Repair shops should totally hire you, since they often need an eternity to do their job.
Cheers

Joej970 said:
Well okay. Then write that down to a paper and stick it to a mirror, so you'll see your extraordinary achievement every time you wake up, and be proud of yourself, cause you did all that for the fisrt time in only one hour, although everyone else needed an afternoon. You're probably the smartest person I've ever seen, cause you apparently do magic :good:
Repair shops should totally hire you, since they often need an eternity to do their job.
Cheers
Click to expand...
Click to collapse
i only wanted to say that this thread is completely unnecessary.. this phone is more than 2 years old... last update was i think 1year ago.. so there is nothing new... tutorials for unlocking BL (2nd March 2012) and for rooting (17th June 2013) are here for more than a year...and tutorial for instaling CM you can find in almost every CM thread... thats all I wanted to say :victory:... have a nice day

It is kinda necessary..
Some people still dont know how to flash these roms...And then end up spamming other threads...:/

Joej970 said:
Okay guys,
I spent a whole day yesterday to exterminate lame SONY's firmware, and get a refreshment alternation
so I gathered all tutorials, which I had followed to give my Xperia S new soul, and made this all-in-one tutorial for anyone, who's not sure how to do it.
Big thank to DooMLoRD, who's is making all this awesome tools and stuff to make our Xperias alive again.
Click to expand...
Click to collapse
Your method is long and unnecessarily beating around the bush. Here's a much quicker way (how I did it in less than half an hour):
1) Copy the ROM zip to your internal storage
2) Unlock bootloader with Sony's info on their site.
3) Extract boot.img from the ROM zip / kernel zip.
4) In fastboot mode,
Code:
fastboot flash boot boot.img
fastboot reboot
5) Go into recovery while it's rebooting, wipe everything & flash the ROM zip.
TBH, DoomLord's stuff is not required, never really was for me..
Sure, it's good stuff, but not required in this case..

The tutorial is good, it's just unfortunate, is that after more than two years, yet no one has been able to unlock the bootloader problem that allows not be unlocked.
Sent from my LT26i using XDA Premium 4 mobile app

Great_Geek said:
Your method is long and unnecessarily beating around the bush. Here's a much quicker way (how I did it in less than half an hour):
1) Copy the ROM zip to your internal storage
2) Unlock bootloader with Sony's info on their site.
3) Extract boot.img from the ROM zip / kernel zip.
4) In fastboot mode,
Code:
fastboot flash boot boot.img
fastboot reboot
5) Go into recovery while it's rebooting, wipe everything & flash the ROM zip.
TBH, DoomLord's stuff is not required, never really was for me..
Sure, it's good stuff, but not required in this case..
Click to expand...
Click to collapse
Hey, hey, hey,
where do you type that code in? In terminal emulator on a phone or maybe cmd on a computer? I've seen a lot of tutorials ordering to type a code, but none of them actually explained how and where you have to write it.
Thankss!

Joej970 said:
Hey, hey, hey,
where do you type that code in? In terminal emulator on a phone or maybe cmd on a computer? I've seen a lot of tutorials ordering to type a code, but none of them actually explained how and where you have to write it.
Thankss!
Click to expand...
Click to collapse
You use fastboot.exe or the fastboot binary for linux, same one that you used for unlocking bootloader..
Finding something to type into terminal emulator is pretty rare, and it'll usually be specified that you need to type it there..

[Q] help me to get root my htc desire 820 dual sim..

Dear Sir,
I have followed all the steps but still not rooted my htc desire 820 dual sim
http://forum.xda-developers.com/desire-820/general/htc-desire-820-root-easily-t2913064..............this link I have followed.....
but didn't sucess.......
plz....help...Sir
HTC Desire 820 can be easily rooted with few simple steps.
I am not responsible for your warranty loss or device not functioning properly.
Steps
1] Unlock Bootloader if you don't know how to do it visit this page
2] Download TWRP Recovery from here
3] Download Super Su from Here and transfer it to your device
4] Reboot to Fastbboot mode using Volume Down and Power Key
5] Connect Phone to PC
6] Extract files from Recovery.zip in one location and simply click on flash-recovery.bat
7] After Step 6 is finished Using volume keys navigate and select recovery option and go to recovery
8] After rebooting in recovery select Install zip > and selecting supersu.zip transferred in first step to obtain root access.
9] Reboot
Very much urgent.......plz. reply...........

subinoy.bose said:
Dear Sir,
I have followed all the steps but still not rooted my htc desire 820 dual sim
http://forum.xda-developers.com/desire-820/general/htc-desire-820-root-easily-t2913064..............this link I have followed.....
but didn't sucess.......
plz....help...Sir
HTC Desire 820 can be easily rooted with few simple steps.
I am not responsible for your warranty loss or device not functioning properly.
Steps
1] Unlock Bootloader if you don't know how to do it visit this page
2] Download TWRP Recovery from here
3] Download Super Su from Here and transfer it to your device
4] Reboot to Fastbboot mode using Volume Down and Power Key
5] Connect Phone to PC
6] Extract files from Recovery.zip in one location and simply click on flash-recovery.bat
7] After Step 6 is finished Using volume keys navigate and select recovery option and go to recovery
8] After rebooting in recovery select Install zip > and selecting supersu.zip transferred in first step to obtain root access.
9] Reboot
Very much urgent.......plz. reply...........
Click to expand...
Click to collapse
Try thishttp://forum.xda-developers.com/attachment.php?attachmentid=2784451&d=1402084843

Please let us know what is the exact message your getting are you not able to get to Recovery ???
I have been able to successfully root my device by following the steps outlined did not face any challenges hence wanted to check.

Same Probleam here pls help me
I AM SUFFERING FROM SAME PROBLEAM.
i am using desire 820q.
bootloader unlocked.
but when i enter in recovery then that says entering recovery then come back.
pls help me...

problem with htc 820q root
mukulatri said:
Try thishttp://forum.xda-developers.com/attachment.php?attachmentid=2784451&d=1402084843
Click to expand...
Click to collapse
I'm following this instruction and could not root my device,
My HTC 820q is unlock but when I want read SuperU.zip from Sd card at fastboot>recovery my mobile goes to restart and procedures been uncompleted.
Please help me, is this instruction only for HTC 820?
How we can root HTC 820q?

tah3r said:
I'm following this instruction and could not root my device,
My HTC 820q is unlock but when I want read SuperU.zip from Sd card at fastboot>recovery my mobile goes to restart and procedures been uncompleted.
Please help me, is this instruction only for HTC 820?
How we can root HTC 820q?
Click to expand...
Click to collapse
http://forum.xda-developers.com/desire-820/general/htc-desire-820-root-easily-t2913064

mukulatri said:
Try thishttp://forum.xda-developers.com/attachment.php?attachmentid=2784451&d=1402084843
Click to expand...
Click to collapse
Well I have the same issue, recovery looks installed after pressing power button to launch it goes to a screen and go back almost instantly on fastboot screen. I also tried last version of framaroot, does not help either... just get a failed message

尚雷諾 said:
Well I have the same issue, recovery looks installed after pressing power button to launch it goes to a screen and go back almost instantly on fastboot screen. I also tried last version of framaroot, does not help either... just get a failed message
Click to expand...
Click to collapse
Hi there, let's go step by step without "shortcuts" that are typically working on PC/WIn.
1. Unlock bootloader of your phone at HTCdev[dot]com [replace 'dot' with . - sorry for confusion I haven't earned reputation to post external links yet]. All necessary tools (fastboot) will be provided to download during process as well as necessary instructions. You need Windows/Linux or OS X computer to complete this step.
2. Download custom recovery .img file and save it to same directory you have fastboot files (e.g. from step 1) on you computer
3. Start phone in fastboot mode (mind fast boot option in Power settings must be unchecked if you using VolDown [-] start option (not necessary if you use adb reboot bootloader). Battery must be charged over 10% (I suggest 30% to stay secure); connect to computer (phone shall display Fastboot USB)
4. Navigate command/terminal window on your computer to location of recovery image file from step 2 (fastboot files must be there or have a correct path specified).
5. On computer terminal window run command: fastboot flash recovery filename_of_recovery.img . Red section must be exact custom recovery file name.
6. You'll get some communication in terminal. If completed OK will be among them, if failure, there will be FAIL with description of reason (e.g. low_power). If only "waitng for device" dislays, check connection with phone.
7. Navigate phone to HBOOT, then select recovery. If recovery don't start, check step 1 and restart from step 3. If only icon with red ! appears, it means you have stock recovery installed. Please verify from step 1.
8. Once custom recovery is installed and working, use it to flash SuperSU or any other superuser app (must be flashable .zip to be applied). Install just 1 root application, to avoid problems. At this point, you may consider flashing busybox also if you plan extensive file modification, but it's not necessary for root. For any sake, clear cache befor restart.
9. Restart the phone - you shall view SuperSU application or any other superuses app you've flashed i step 8.
Hope now works.

T0ark said:
Hi there, let's go step by step without "shortcuts" that are typically working on PC/WIn.
1. Unlock bootloader of your phone at HTCdev[dot]com [replace 'dot' with . - sorry for confusion I haven't earned reputation to post external links yet]. All necessary tools (fastboot) will be provided to download during process as well as necessary instructions. You need Windows/Linux or OS X computer to complete this step.
2. Download custom recovery .img file and save it to same directory you have fastboot files (e.g. from step 1) on you computer
3. Start phone in fastboot mode (mind fast boot option in Power settings must be unchecked if you using VolDown [-] start option (not necessary if you use adb reboot bootloader). Battery must be charged over 10% (I suggest 30% to stay secure); connect to computer (phone shall display Fastboot USB)
4. Navigate command/terminal window on your computer to location of recovery image file from step 2 (fastboot files must be there or have a correct path specified).
5. On computer terminal window run command: fastboot flash recovery filename_of_recovery.img . Red section must be exact custom recovery file name.
6. You'll get some communication in terminal. If completed OK will be among them, if failure, there will be FAIL with description of reason (e.g. low_power). If only "waitng for device" dislays, check connection with phone.
7. Navigate phone to HBOOT, then select recovery. If recovery don't start, check step 1 and restart from step 3. If only icon with red ! appears, it means you have stock recovery installed. Please verify from step 1.
8. Once custom recovery is installed and working, use it to flash SuperSU or any other superuser app (must be flashable .zip to be applied). Install just 1 root application, to avoid problems. At this point, you may consider flashing busybox also if you plan extensive file modification, but it's not necessary for root. For any sake, clear cache befor restart.
9. Restart the phone - you shall view SuperSU application or any other superuses app you've flashed i step 8.
Hope now works.
Click to expand...
Click to collapse
Thanks for your answer, I have to say I properly unlocked the phone so I do not think there is a way I messed up with this step as when I start bootloader it clearly shows on the top of the screen ''UNLOCKED".
When I flashed recovery on my phone I had no errors prompted or any message of failure. The process went well until a success notification.
Now when I start my phone into bootloader I repeat, I clearly see that recovery has been installed but when I attempt to start it then I'll be almost instantly brought back to the bootloader screen... now I started to wonder if... if an update of android could cause this kind of issue? The point is my phone is using android 4.4.4 and not the factory version 4.4.2. I remember having updated my android version which was perhaps a mistake as this phone is not very old and I was planning to root it in the next days... Now I'm not expert just try to figure it out.
I tried different system to auto root via different apps, some using the PC some using directly the phone, I never get any success...

尚雷諾 said:
Thanks for your answer, I have to say I properly unlocked the phone so I do not think there is a way I messed up with this step as when I start bootloader it clearly shows on the top of the screen ''UNLOCKED".
When I flashed recovery on my phone I had no errors prompted or any message of failure. The process went well until a success notification.
Now when I start my phone into bootloader I repeat, I clearly see that recovery has been installed but when I attempt to start it then I'll be almost instantly brought back to the bootloader screen... now I started to wonder if... if an update of android could cause this kind of issue? The point is my phone is using android 4.4.4 and not the factory version 4.4.2. I remember having updated my android version which was perhaps a mistake as this phone is not very old and I was planning to root it in the next days... Now I'm not expert just try to figure it out.
I tried different system to auto root via different apps, some using the PC some using directly the phone, I never get any success...
Click to expand...
Click to collapse
Ok, please try twrp from Original Android Development tread (it works for me, mind, I'd question it's stability) or Philz recovery (sorry, I found only Chinese, but it's for verivication only: h...ps://drive.google.com/file/d/0BygOvRquk4z8S05kRC1XMXdSbXM/view?usp=sharing - please adjust tt in address - rookie rules).
I'd suggest test running from Fastboot: fastboot boot custom_recovery.img - replace with actual file name from directory you're running terminal.
This shall verify if it's problem with recovery file or any remaining protection...

T0ark said:
Ok, please try twrp from Original Android Development tread (it works for me, mind, I'd question it's stability) or Philz recovery (sorry, I found only Chinese, but it's for verivication only: h...ps://drive.google.com/file/d/0BygOvRquk4z8S05kRC1XMXdSbXM/view?usp=sharing - please adjust tt in address - rookie rules).
I'd suggest test running from Fastboot: fastboot boot custom_recovery.img - replace with actual file name from directory you're running terminal.
This shall verify if it's problem with recovery file or any remaining protection...
Click to expand...
Click to collapse
Does having S-ON bother? I was also wondering about that but all tutorials I found no one mentions anything about the S-ON or S-OFF thing.
But I do have a S-ON under UNLOCKED

what is stock recovery.img name
i dont know what is the real stock recovery.img name.

htc desire 820q dualsim
I can't root my htc desire 820q by this method, is any alternative way?

I just root my phone with same procedure but my phone still show s-on..... How can i s-off my phone.....

Blackview BV9000 Pro-F ROOT SUCCESS [TWRP + Magisk v16 + Stock Rom]

EDIT: included rough procedures for OEM unlocking, and updated link to recovery-verified.img (Sorry for uploading the wrong file ><)
Hi all bv9000 pro Users!
Recently I went on a journey to root this awesome rugged phone with one purspose: to remove that F*@(#&$ god awful loud annoying sound triggered by the OS when you use a camera app to take a picture + the boot startup sound (A bug blackview hasn't gotten around to fixing).
I successfully managed to port TWRP 3.1.1 from the Blackview bv8000 Pro and run it on the Blackview bv9000 Pro-f!
I've then managed to flash in Magisk to gain root access.
DISCLAIMER: I do not take responsibility for any bricked phones caused by the process, do so at your own risk (yadayadayada).
NOTE 1: Although I've got it running on the bv9000 Pro-F, this image should also work for the non-fullHD version, if someone can test this I'd be happy.
The link to the stock ROM (with the modified recovery img) can be found in the post below.
NOTE 2: No need to download anything other than what I've listed, Magisk is included in my custom recovery to circumvent the need to load the devices encrypted storage (or any other external storage) nothing stops you from mounting external usb storage.
What you'll need:
- USB Mouse (As there is no touchscreen input support, your device should have come with a usb-c otg cable so there's no problem here!)
- MediaTek SP Flash tools (I'd recommend the latest version) https://spflashtool.com/
- unlocked bootloader (You should be able to do this via the developer settings -> unlock OEM Bootloader)
EDIT: To unlock the boot loader, do the following:
1) Go to settings -> unlock OEM Bootloader (tick)
2) plug your device in (assuming you have ADB installed), use adb to access fastboot via. command prompt:
"adb reboot bootloader"
Then once the device is rebooted into fastboot mode
"fastboot oem unlock"
KEEP IN MIND THIS WILL REMOVE ANY FILES, so back them up
- I've done this with windows, but you should be able to repeat with linux no problems!
- A little patience
Pre-preparation:
First install any updates and back up your data (it's just easiest to use the google cloud backup as restoring becomes easy as pie, updating also fixes the setup wizard crashing on first setup). This is necessary because OTA updates cannot be performed with TWRP recovery, and flashing TWRP before doing OTA updates will flick the device into a recovery boot loop.
Install the SP Flash tools, and the MediaTek VCOM Drivers
(I won't link the specifics here, a quick google search should be able to help you, just note you might need to disable driver signature enforcement)
Two options for flashing:
1)
My Full Stock ROM already pre-prepared for flashing:
Patched ROM
No need for extra prep here! you should just be able to load the scatter
2)
My custom patched TWRP stock rom: recovery-verified.img
Blackiew's stock rom: stock rom
- Download the stock rom, backup the recovery-verified.img in the R06 folder, and then replace it with my custom patched TWRP stock rom (file name should be the same).
- Run "CheckSum_Gen.exe" once you replaced the file, it will generate the necessary checksum to allow SP flash tools to successfully flash recovery.
Once you've done with the pre-prep, switch off your device, take a deep breath and you're ready to go!
Steps!
1) Load up SP Flash Tools, select the android scatter file you've downloaded in the R06 folder
2) Select Download Only (I MEAN IT, FORMATTING WILL REMOVE YOUR IMEI AND RENDER THE PHONE USELESS)
3) Deselect everything but recovery (You only want to flash this)
4) Hit download
https://pasteboard.co/HkufwZZ.png
5) Hold volume up + power and plug in your phone, keep the volume up button held
6) very quickly the flash should be complete, and you should be greeted with a big ol' green tick to verify
https://pasteboard.co/HkuiTBB.png
7) Once you're done, remove your USB cable, plug in the OTG then we proceed to flash magisk
8) Hold power + volume up until you reach the bootloader, then use the menu to select recovery
9) You *should* be greeted with the TWRP recovery screen (Which is great success! )
DON'T PANIC IF YOU CANNOT USE THE TOUCH SCREEN, the kernel I've patched is missing this, seems the driver is different between touch screens, just plug in your OTG mouse to continue from here!
10) Use your mouse to first hit cancel, we don't need to decrypt the user data storage.
11) But oh no! it's all in Russian (no problem, Next step sorts that)
12) Use your mouse to navigate the menus as shown here to change to English! (or your preferred language) Change Language
13) Click install, then navigate up folder levels until you are in the root directory
14) scroll down and click on Magisk.zip, install it, allow it to install any apps as system apps (because this will then install to the system image, not the userdata)
15) reboot the phone (if it hasn't rebooted already)
16) You should be able to boot into your usual phones OS, if you don't see Magisk listed in your phone apps, just download it from here:
Magisk Manager
17) Congratulations! You should have complete root access :laugh::laugh::laugh:
Feel free to express your thanks, or list any problems you have, but keep in mind my studies take all my life, so I may not be able to help with all the problems you have

Congrats! Would it work on the BV9000 HD version?

Hi!
From what I've seen they both run the helio p25 chip
(Just a difference in RAM size) so it should.
You're more than welcome to try.
Just keep a backup of the original ROMs recovery. If something goes wrong during the boot to recovery you can easily re flash

hi i tried both optinos but they didn't work for me
I tried the first and the second options and it was showed me same error:
ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
I tried download only, format all and download, if i install original ROM its installing without problems!
In settings-> developer options -> OEM unlocking is enabled
can someone give me tips if I'm doing something wrong. thanks
My phone is Blackview BV9000PRO-F

Hello,
i have the blackview 9000 pro Hd (not full hd)
i first tried your prepared patched rom = not working (get erorrers in step 6)
then i chose step 2 and i was thinking to use the stock rom from the NOT full hd rom
now i get a green screen from the flashing: but after rebooting in recovery nothing happens, just normal reboot then
perhaps this is not so clair for me:
- Download the stock rom, backup the recovery-verified.img in the R06 folder, and then replace it with my custom patched TWRP stock rom (file name should be the same).
- Run "CheckSum_Gen.exe" once you replaced the file, it will generate the necessary checksum to allow SP flash tools to successfully flash recovery.
the file name you posted here " My custom patched TWRP stock rom: recovery-verified.img" is ramdisk-recovery.img
i replaced the ramdisk-recovery.img... it is not clair need to replace recovery-verified.img to?

>I tried the first and the second options and it was >showed me same error:
>ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
> tried download only, format all and download, if i install >original ROM its installing without problems!
>can someone give me tips if I'm doing something wrong. >thanks
>My phone is Blackview BV9000PRO-F
Hi, you need to unlock the OEM bootloader, if this is still locked it will prevent the flashing of custom ROMS.
I might've missed this step, will update post as necessary.

>
dingsje said:
Hello,
>i have the blackview 9000 pro Hd (not full hd)
>i first tried your prepared patched rom = not working >(get erorrers in step 6)
>then i chose step 2 and i was thinking to use the stock >rom from the NOT full hd rom
>now i get a green screen from the flashing: but after >rebooting in recovery nothing happens, just normal >reboot then
>perhaps this is not so clair for me:
>- Download the stock rom, backup the recovery->verified.img in the R06 folder, and then replace it with >my custom patched TWRP stock rom (file name should >be the same).
>- Run "CheckSum_Gen.exe" once you replaced the file, >it will generate the necessary checksum to allow SP >flash tools to successfully flash recovery.
>the file name you posted here " My custom patched >TWRP stock rom: recovery-verified.img" is ramdisk->recovery.img
>i replaced the ramdisk-recovery.img... it is not clair >need to replace recovery-verified.img to?
Click to expand...
Click to collapse
Hi,
I've uploaded the wrong file, the uploaded file should be recovery-verified.img.
I'm uploading a new file and will correct the link now,
Please accept my apologies ><

hyperlethalvector92 said:
>I tried the first and the second options and it was >showed me same error:
>ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
> tried download only, format all and download, if i install >original ROM its installing without problems!
>can someone give me tips if I'm doing something wrong. >thanks
>My phone is Blackview BV9000PRO-F
Hi, you need to unlock the OEM bootloader, if this is still locked it will prevent the flashing of custom ROMS.
I might've missed this step, will update post as necessary.
Click to expand...
Click to collapse
I already did this step:
Enable developer options-> OEM unlocking is enabled
Is that enough for this MTK phone to be unlocked the bootloader ?
And tried the both options but the results are same.
I have been unlocking bootloaders on many phones but first time MTK phones. If i try with adb commands it recognize when is in the android with command adb devices and show my device but if I try reboot bootloader and check in device manager in windows its show its connected and drives are correct but if i try to show the devices, it doesn't show any device connected

Hi,
You need to install fastboot drivers once it's in bootloader mode,
then use fastboot, not adb.
"fastboot oem unlock"
Then follow instructions.
simply doing settings -> oem unlock won't unlock the bootloader, it allows you to do so later via. fastboot
Check the original post, I've added the extra instructions sorry about the confusion!

Thanks a lot. I finally succeeded to unlock the bootloader and root my phone and install the magisk.. I did without use your rom just I unlocked the bootloader and install your twrp file and after in the recovery mode i format the data and istall magic and i still have the last updated android.
I hope this it ill help to other people. Cheers

zlatkomas said:
Thanks a lot. I finally succeeded to unlock the bootloader and root my phone and install the magisk.. I did without use your rom just I unlocked the bootloader and install your twrp file and after in the recovery mode i format the data and istall magic and i still have the last updated android.
I hope this it ill help to other people. Cheers
Click to expand...
Click to collapse
I'm glad ^______^
Enjoy your rooted phone

I used this video to root my bv9000 pro hd
much easier than this above, i think it works to on bv9000 pro fhd
https://www.youtube.com/watch?v=c48ISLPjn4Q

Congratulations .... I need a tip,.
And, brother, thank you very much. Worked perfectly.
But first I would like to get you a tip ..
One of the main reasons I have done all this complicated process was to be able to disable the crap of the loud music that plays when the device is started.
I want complete silence at startup.
How do I disable this ****?

Code for Huawei mobile Wi-Fi e5577s-321
Pls help unlock my Huawei mobile Wi-Fi e5577s-321
Imei
860782038163889

TWRP looping after OTA update
My dear, the procedure worked very well, until an OTA update was downloaded.
You are now looping on TWRP. How do I get out of this?
:crying:

help!
i missed to run wireless software update,so ROM clashed.
How can i re-install custom ROM?

mackie_ma said:
help!
i missed to run wireless software update,so ROM clashed.
How can i re-install custom ROM?
Click to expand...
Click to collapse
Hi guys, lemme apologize for disappearing, life and whatnot!
For those stuck in a TWRP boot loop, simply restoring the original recovery then restarting the phone will be enough to fix the problem.
(Actually you really don't need TWRP after the phone is rooted, maybe I should update the guide?)

Many Thanks
First off, thank you for your hard work. Loved the "**** it we have an OTG cable let's use it" haha. It works fine for me.
Second, do you happen to know if someone has ported Oreo on our bv9000 ? Or do you know of any ETA ?
Thanks again,
Cheers

Anyone tried on the BV9000 Pro? Don't think mine is 'F' OR 'Fhd'.... I must have first model brought out...

Ugh.. Windows and Drivers?!?!
I keep getting Driver not Recognized in Windows 7 Pro X86.
I installed the latest vcom/usb drivers, in legacy also. No Go.
I installed from several other sources the drivers, including the Automatic Mediatek driver install. No Go.
So if anyone has a tip for me, please let me know because once more Windows is proving itself ridiculous. I can't even get to the storage of my phone. Did something change with a Windows Update that it's not allowed anymore?
I put my BV9000 Pro in OEM Unlock and USB Debugging. I backupped everything. My phone is ready for it. It's as ready as Amy having coitus with Sheldon for the first time.