Database Info

[Q] Nexus 7 Bricked No OS stuck on Google screen

Good Afternoon
The other day I was having an issue with my Nexus 7 so I inadvertently went into TWRP on my device and wiped everything including the OS so when it starts up I just get the Google screen with the unlocked padlock on it.
I have tried several things so far
I have downloaded Nexus root Toolkit 1.7.3 and several stock images, I choose the option to flash stock + Unroot but it doesn't seem to do anything I just get the following screen as per attached screenshot, from looking around it looks like it should run something before I get that screen but nothing happens.
I really don't know where to go from here I have tried so many different things but just don't seem to be getting anywhere, any help would be soooooooo much appreciated, I can’t even send it back as I have unlocked it and I believe that voids the warranty.
I have managed to get into the TWRP section by choosing the custom recovery in the advanced section menu but when it loads up it asks me for a password on my Nexus and the password I had it keeps on saying password failed.
Is there anything I can do, I have literally spent hours searching around and I cant seem to get anything to work, as I say I have inadvertently wiped everything!!!!!!:crying:

davechampion said:
Good Afternoon
The other day I was having an issue with my Nexus 7 so I inadvertently went into TWRP on my device and wiped everything including the OS so when it starts up I just get the Google screen with the unlocked padlock on it.
I have tried several things so far
I have downloaded Nexus root Toolkit 1.7.3 and several stock images, I choose the option to flash stock + Unroot but it doesn't seem to do anything I just get the following screen as per attached screenshot, from looking around it looks like it should run something before I get that screen but nothing happens.
I really don't know where to go from here I have tried so many different things but just don't seem to be getting anywhere, any help would be soooooooo much appreciated, I can’t even send it back as I have unlocked it and I believe that voids the warranty.
I have managed to get into the TWRP section by choosing the custom recovery in the advanced section menu but when it loads up it asks me for a password on my Nexus and the password I had it keeps on saying password failed.
Is there anything I can do, I have literally spent hours searching around and I cant seem to get anything to work, as I say I have inadvertently wiped everything!!!!!!:crying:
Click to expand...
Click to collapse
Try reflashing TWRP first, then reply if you still have the password problem. We can work from there. Remember, you have a N7 - nexus devices are practically unbrickable (if you know what I mean)

Nexus 7 2013
Thanks for that will give it a try later.
I have also come across the website below
forums.androidcentral.com/google-nexus-7-2012-rooting-roms-hacks/191477-guide-nexus-7-factory-image-restore.
It gives a guide on how to reinstall the stock software, the only thing that I can see they have that I dont are a few files and I dont know where you get them from.
the files in the guide are
Bootloader-Grouper 3.34
Flash-all.sh
Flash-Base.sh
The image file I am fine with as I downloaded that from the site below.
developers.google.com/android/nexus/images
sorry I dont have enough privaleges to include link have to paste it manually

Nexus 7 2013
Also in regards to you last comment about TWRP
could you give step by step instructions on how to reinstall it, I am just paranoid that I may do something wrong again, I cant activate usb debugging so would need to do it via the bootlader and Command prompt ideally.

Nexus 7 2013 Re flash TWRP
Not to worry about steps I have managed to find some that will do the job
theunlockr.com/2013/03/25/how-to-install-twrp-recovery-on-the-asus-nexus-7/

davechampion said:
Thanks for that will give it a try later.
I have also come across the website below
forums.androidcentral.com/google-nexus-7-2012-rooting-roms-hacks/191477-guide-nexus-7-factory-image-restore.
It gives a guide on how to reinstall the stock software, the only thing that I can see they have that I dont are a few files and I dont know where you get them from.
the files in the guide are
Bootloader-Grouper 3.34
Flash-all.sh
Flash-Base.sh
The image file I am fine with as I downloaded that from the site below.
developers.google.com/android/nexus/images
sorry I dont have enough privaleges to include link have to paste it manually
Click to expand...
Click to collapse
Have you used 7z to unpack the files? Google puts all the files within an archive which is within another archive. In case you aren't able to successfully follow your guide, let me know and I will post steps. And btw, using CMD is actually quite easy once you get used to it... You just need to put in the effort! :good:

[GUIDE] How to install/reinstall/flash stock Nexus 7 Image from Google
I just saw your other thread mate! Seems like you're really worried about your device. And so I thought I'll give you step by step instructions;
1) Install, then open and navigate 7-zip to the location where you have the factory image file downloaded from google with the ".tgz" extension.
2) Unpack the .tgz file by selecting it and clicking extract (with the big blue negative sign).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3) Now, navigate to the extracted folder, you will see another file with the extension ".tar"
4) Repeat step 2 for the ".tar" file.
5) Now open this folder using windows. You should see the following files in your directory;
6) From here, you can either follow the instructions on the webpage you have or follow these instruction (using CMD and fastboot);
* Remember, after doing this you will not have any files/setting left on your N7.
1) Boot your N7 into bootloader.
2) Open cmd.exe and enter the following commands;
3) cd "put here without quatation marks, the directory of where the .img files are" (the last pic above)
4) fastboot devices (note: after entering this command your device should be displayed below)
5) fastboot erase boot
6) fastboot erase system
7) fastboot erase recovery
Perform steps 8 & 9 only if you have the 3G version of the N7:
8) fastboot erase radio
9) fastboot flash radio "put here without the quotation marks, the FULL name of a file that will look similar to this: radio-razor-m9615a-cefwmazm-2.0.1700.84.img"
10) fastboot update -w image-razor-jss15q.zip
11) fastboot reboot
Remember, because you have freshly flashed your N7, it will take little longer than usual to boot up.
​

Thank You!!!!!!!!!!
Thank you so much you are a LEGEND - I am all up and running again, just a quick question I re flashed the standard stock file which was listed as JSS15J (it wasn’t on the official factory image website) but my Nexus root toolkit seems to be playing ball after a re install, can I flash a later version over what I have without causing issues as I assume they have bug fixes.
I am unable to do an OTA update as I am in an unlocked state.
I have seen online that you can use the following code in CMD to flash newer factory images without wiping data, Is this correct?
here is the code they suggest to use
Code:
fastboot update <Filename>.zip
I suppose you could back up all data first and then re flash.
Again a massive thank you for all you help:victory:

[GUIDE] Reinstall/Update Android without loosing your Userdata (media Directory)
davechampion said:
Thank you so much you are a LEGEND - I am all up and running again, just a quick question I re flashed the standard stock file which was listed as JSS15J (it wasn’t on the official factory image website) but my Nexus root toolkit seems to be playing ball after a re install, can I flash a later version over what I have without causing issues as I assume they have bug fixes.
I am unable to do an OTA update as I am in an unlocked state.
I have seen online that you can use the following code in CMD to flash newer factory images without wiping data, Is this correct?
here is the code they suggest to use
Code:
fastboot update <Filename>.zip
I suppose you could back up all data first and then re flash.
Again a massive thank you for all you help:victory:
Click to expand...
Click to collapse
I'm glad to be of assistance. If you want to update your rom without loosing your data, I recommend you follow these steps (however, there is a catch: read the second last paragraph);
1) Boot into TWRP and wipe everything except "Internal Storage".
Reboot into bootloader and erase the following using CMD:
2) fastboot erase system
3) fastboot erase boot
4) Now unpack the <filename>.zip file. You will find that there are a multitude of <filename>.img files in there.
Flash two of the files named system.img and boot.img (this contains the Kernel) using CMD (remember CMD must be open in the folder containing these files):
2) fastboot flash system system.img
3) fastboot flash boot boot.img
And the other file (again is if you have the mobile version of the N7), is to flash the radio as given in my previous instructions (remember to erase radio first before flashing it).​
When you're done, you will have updated your N7 without losing your data (i.e. the files you see when you plug your N7 to the computer). However, following this method, you will not retain any Apps or settings (remember: Backing up apps and restoring them to a different ROM is a BAD idea). I have to say also that given you cannot use OTA, I am not aware of any other method that will keep your apps and settings untouched. I may be wrong, and if I am please do let me know. :good:
Finally as a personal note, I wouldn't flash anything to a Nexus but the latest stock files provided from Google until they stop providing updates to that particular device.

..
..

[SOLVED] Nexus 5 stuck in boot loop animation (Lollipop) , partially working with 4.4

I have a Nexus 5 32GB that's about 14 month old. Was running Lollipop 5.1 which was installed through OTA updates (4.44 >5.0 >5.01>5.1). The device is stock and unrooted.
One day, after powering the device up, it went into the boot screen and never managed to finsih the boot (for hours).
After reading extensively on this and other forums , here are the steps I tired , without success:
1. Go to bootloader and press Start
2.Go to bootloader , erase cache
3.Go to bootloader erase user data (factory reset).
I then tried to flash the factory image back. I tried all Lollipop versions from the google developers page of factory images.
starting with 5.1.0 (LMY47I) and going down. All flashing was completed successfully, but the problem remains.
Then I tried 4.4.4 (KTU84P) and the device finally booted up, but it was crippled: Most times It only sees a storage of 16GB , the phone does not recognize any cellular carriers, google play crashes, camera crashes, gallery crashes. An error states that "no external memory is available". Basically it was useless.
I took the phone to an LG lab. They said I need to replace the motherboard. Costs about 200$ !!
I was about to get a new phone , but decided to try one more google search for a fix.
This guide is for any poor soul in the same state.
This issue can be solved without replacing the motherboard for 200$.
The problem in my case was that the /persist partition was degraded, and could not mount.
I found out by trying to follow this guide: http://android.stackexchange.com/qu...dots-lollipop-screen-after-hard-factory-reset
I got as far as activating ADB Sideload when I got the error "cannot mount /persist".
This is a software problem.
Her's how to fix it (It's a long and detailed guide - but worth the result):
First, you must enable USB debugging mode , if it was not enabled (if it is enabled you can skip the first step of this guide) . The way to do that is to flash a stock image that will load, even if not fully working. In my case I could flash version 4.4x and get the phone to load. I am not aware of any other way to enable USB debugging, other than from within a working OS. If someone knows a way - please post it.
The easiest way I found to flash my phone is using Julian OS' script. You can download the stock image5.0 and 5.01 with the script from here:
https://www.androidfilehost.com/?w=files&flid=22367
You will need to adapt the 4.4x firmware to have the script flash it, but it's very easy, just a couple of files to rename.
When you open Julian's zip file you will see that he uses a script that flashes the firmware's images one by one. What I did was download the stock images from Google https://developers.google.com/android/nexus/images , used winrar to extracrt all the files from the .tgz file to a folder, then unzip the only zip file there (image-hammerhead-xxxxx.zip) which contains 5 img files. I then renamed the radio-hammerhead-xxxxx.img to radio.img and bootloader-hammerhead-xxxx.img to bootloader.img. Now all the file names comply with Julian's script. From Julian's archive copy the files "From Bootloader.bat" and "fastboot.exe" to the folder where all the images you just renamed are.
Put the phone in bootloader mode (turn the phone off, press the Vol- and the power buttons). Once the the phone is in bootloader mode, connect it to the PC and run "From Bootloader.bat" and follow the onscreen instructions. In about 2 minutes, your phone will be flashed.
Turn the phone on, it should load the OS. Disregard all the error messages, and don't bother setting the phone up. If you skip wifi, and don't have a sim in the phone you can finish the basic setup quickly.
Next you need to get developer tools activated: Settings>about phone>Build number. Tap 7 times on the build number and this will unlock Developer tools. Go back to settings and the new Developer Tools and enable usb debugging. Approve any popups.
*** I am not aware of how to enable usb debugging if you cannot go into the settings. If non of the stock images loads for you, search for a way to get usb debugging working , or else you cannot continue. You need this for ADB to connect to the phone.****
Next, you need to have ADB on your PC, and it should be able to reach your phone. If you already have - then skip to the next step. If you don't - then here is how to get the latest version:
Go here and download the installer https://developer.android.com/sdk/index.html#Other
Install the file and when it's done run SDK manager. Choose only the first 2 tools (Android sdk tools and Platform tools), this will install the latest adb and fastboot tools. To make sure all is installed open a command prompt (Click Start, type cmd in the search and run cmd.exe) and type adb. You should see all the adb possible commands typed. Now you can test if your phone can be reached by adb: connect your phone (remember usb debugging must be on!) and type: adb devices. After a few seconds you should see something like this:
List of devices attached
024703f599cc8feb device
If you get this, it means you have usb debugging enabled and a proper usb driver installed and you can go to the next step . If there is no device in the list you need to install/update the USB driver:
You have to make sure that when you connect your phone with USB debugging on, you have 2 entries in Winodws Device manager:
Under Portable devices >Nexus 5 , and under Android device> Android composite ADB Interface.
If the second one is missing, ADB will not work and you can't continue. There are 2 ways to fix that :
1. You can install an Android driver called Universal Naked Driver 0.73 from here: http://forum.xda-developers.com/showthread.php?t=2386956. Unzip the file to a folder.
The author of that guide states you need to uninstall any driver that already exists. This proved tricky because Windows would not uninstall the Nexus 5 driver. I decided to install it on a PC that has no android driver.
When you connect the phone to a windows 7 pc for the first time it will search for a driver. I disconnected the internet and windows installed a generic driver. In device manager I saw Nexus 5 with a yellow triangle. I Right clicked on it > update driver software > Browse my computer for driver software and point to the folder you unzipped the driver. You will get a warning - allow the installation.
2. If that does not work or if you don't have another "virgin" PC try this:
Run SDK Manager, under Extras mark Google USB driver. You don't need anything else marked. Install the driver.
Now connect your phone to the PC in normal mode (not bootloader!) . Open device manager. You should have two entries: Portable devices >Nexus 5 and Android device > Android Composite ADB Interface
If the second one is missing, but the Nexus 5 is properly installed, Right click on the Nexus 5 device >Update driver software > Browse my computer for driver software >Let me pick from a list. Now make sure that "Show compatible Hardware" is ticked . You should now have an entry called "USB composite device". Choose that and let it install. When it's done, if you still have an an Unknown device >Nexus 5 and no Android Composite ADB Interface in device manager, then unplug the phone and reconnect it again . You should now have both devices installed.
If by chance this does not work, and you have a Nexus 5 with a yellow error , right click it>update software driver> Browse my computer.> and point it to the Universal Naked Driver folder or the SDK>Extras>Google USB driver folder and it should update so both devices appear (Nexus 5 and ADB).
Once adb can see your pohne go here, to read bitdomo's guide to fix the broken persist partition.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
There are some prerequisites to getting this to work:
The first one is that the phone can be reached by ADB, this is why you needed the usb debugging mode to be turned on, and the proper usb driver installed.
Second, you need to install a custom recovery image. Don't worry, you will overwrite it later. The one I used is TWRP. Get the latest version from here:
http://techerrata.com/browse/twrp2/hammerhead
To install I recommend you copy Fastboot.exe and the TWRP file to an empty folder on your PC . Rename the TWRP file to "recovery.img". Open a command prompt in the folder (see here if you don't know how http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm) , in the black window type: fastboot flash recovery recovery.img and hit Enter. Wait a few seconds and it will finish.
Last, you need to root your device. There are many ways to do this. I did this very simply by downloading CF-Auto-Root from https://autoroot.chainfire.eu/ The file you need is this: https://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip . Unzip it, put your phone in bootloader, run root-windows.bat.
Now you are prepaired... Follow the guide by bitdomo . Open a command prompt , and run the 2 commands bitdomo wrote. You will get a series of questions , type y followed by Enter until it's all done.
SInce you are still in bootloader mode, and a big START is at the top of the screen, click the power button to reboot. Now your oS 4.4x should load properly. Make sure everything is working.
I did not follow the steps for the wifi and BT fix , because they worked fine (and still do 4 months later) , but you can go ahead and do that too.
Now you can flash to the latest firmware 5.10 - download the file from the developer site I gave before, use Jason Os's script to flash the image, and lock the device. Done! Boot up the device and make sure it recognizes the right amount of RAM on your phone (16 or 32GB). If it does, then all is well .
When I first booted the device , I saw that it only recognized 16GB instead of 32GB. To solve this install TWRP again, go to Wipe>Format data . Then reboot the device and make sure you have 32GB.
If you like the stock recovery instead of TWRP you can use Fastboot to flash the original recovery.img.
Now you have a working Nexus 5 , v5.10.
Thanks to LyricWulf and bitdomo for their life saving guides. I hope this helps others in the same spot, and saves them 200$ .

stuck at unlock step
how u unlock nexus 5 when stuck booplop n cnt go to android screen?alrdy using ths step "fastboot oem unlock" when i reboot for unlock,stuck at bootloop n alrdy w8ing 24hr still bootloop cnt see android home screen...n i go to restart nexus5,n locked again... i just stuck on this place,cnt go to next step..pls help me
sry my englsh so bad

Thanks! Helped me to save my N5!
Do not need to exactly as it is posted but the directions is good!
Thanks again.

killian.1140 said:
how u unlock nexus 5 when stuck booplop n cnt go to android screen?alrdy using ths step "fastboot oem unlock" when i reboot for unlock,stuck at bootloop n alrdy w8ing 24hr still bootloop cnt see android home screen...n i go to restart nexus5,n locked again... i just stuck on this place,cnt go to next step..pls help me
sry my englsh so bad
Click to expand...
Click to collapse
Not sure what your problem is, but if you are stuck at the boot screen (with the colored dots spinning) you might have the smae problem I describe. You can try to go to bootloader and wipe the cache, if that does not help and you don't mind a wiping all your data do a factory reset. , Go to recovery mode (third option in bootloader), then press the powr and vol up buttons together several times until you get into recovery. Then choose what you want to wipe.
If that does not restore your phone you need to follow my guide. Probably your persist partion is degraded and needs to be fixed. If you follow my guide you will find out what your problem is.
Good luck

Or just read the stickies.

I had the same problem, and for me, simple NAND restore from TWRP recovery solved this issue. I recently made this NAND backup for no reason and it happens to be a very good move. Cheers

Thank you so much for this! You saved my phone!

volvoxxda said:
I had the same problem, and for me, simple NAND restore from TWRP recovery solved this issue. I recently made this NAND backup for no reason and it happens to be a very good move. Cheers
Click to expand...
Click to collapse
But for that you have had to install TWRP in the first place...
Mine was stock.
Where is the backup saved?

Mine was rooted + TWRP recovery and I saved my backup on flash drive with TWRP's backup option. I was able to boot into boot menu (pwr + vol-) and it would let me to enter into TWRP only. For me it was enough to initiate a restore process..

volvoxxda said:
Mine was rooted + TWRP recovery and I saved my backup on flash drive with TWRP's backup option. I was able to boot into boot menu (pwr + vol-) and it would let me to enter into TWRP only. For me it was enough to initiate a restore process..
Click to expand...
Click to collapse
Flash drive? Do you mean the Nexus internal memory?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
External, like on this picture.

Final solution: power button micro tactile switch was faulty, causing boot loop from time to time. Replacing that little bastard solved this heartbreaking issue

volvoxxda said:
Final solution: power button micro tactile switch was faulty, causing boot loop from time to time. Replacing that little bastard solved this heartbreaking issue
Click to expand...
Click to collapse
Did you just replace the button or did you have to replace something more?
Thanks

Just the button. You can DIY, it's easy.

worked
worked great. confusing in the start but got it working. Thanks for a life saving guide for nexus 5

incredible
Hi eross,
I registered and logged in just to say thank you for this amazing tutorial. I've been trying to repair my N5 for about 12 hours, and I was about to give up when I saw this post. You saved my Nexus!!
Thanks again. :victory::highfive::good:

eross said:
Not sure what your problem is, but if you are stuck at the boot screen (with the colored dots spinning) you might have the smae problem I describe. You can try to go to bootloader and wipe the cache, if that does not help and you don't mind a wiping all your data do a factory reset. , Go to recovery mode (third option in bootloader), then press the powr and vol up buttons together several times until you get into recovery. Then choose what you want to wipe.
If that does not restore your phone you need to follow my guide. Probably your persist partion is degraded and needs to be fixed. If you follow my guide you will find out what your problem is.
Good luck
Click to expand...
Click to collapse
What if you cannot even get into recovery because it is missing?
Sent from my SM-G920T

ambervals6 said:
What if you cannot even get into recovery because it is missing?
Sent from my SM-G920T
Click to expand...
Click to collapse
You can try to download the stock firmware that's installed on your phone and flash the recovery img, or flash twrp recovery.

help
eross said:
This is a Nexus 5 32GB that's about 14 month old. Was running Lollipop 5.1 which was installed through OTA updates (4.44 >5.0 >5.01>5.1). The device is stock and unrooted.
Yesterday after powering the device up, it went into the boot screen and never managed to finsih the boot (for hours).
After reading extensively on this and other forums , here are the steps I tired , without success:
1. Go to bootloader and press Start
2.Go to bootloader , erase cache
3.Go to bootloader erase user data (factory reset).
I then tried to flash the factory image back. I tried all Lollipop versions from the google developers page of factory images. (can't post links yet...)
starting with 5.1.0 (LMY47I) and going down. All flashing was completed successfully, but the problem remains.
Then I tried 4.4.4 (KTU84P) and the device finally booted up, but it is crippled: Most times It only sees a storage of 16GB , the phone does not recognize any cellular carriers, google play crashes, camera crashes, gallery crashes. An error states that "no external memory is available". Basically it is useless.
I am wondering if it is a software or hardware problem. It appears as though part of the phone's memory is not functioning . Is there a way to check this? Is there a way to fix this?
Thanks
Edit: Just came back from an LG lab. Bad news. Need to replace the motherboard. Costs about 200$ !! Can't find anything cheaper on ebay. Guess it's time for a new phone
Edit #2 - SOLVED !!:laugh:
OK, this for any poor soul in the same state. This issue can be solved without replacing the motherboard for 200$.
The problem in my case was that the /persist partition was degraded, and could not mount. Here is how I found it out, and how I fixed it:
First, try to flash a stock image that will load, even if not fully working. You will need this later. In my case I could flash version 4.4x and get the phone to load.
The easiest way I found to flash my phone is using Julian OS' script. You can download the stock image5.0 and 5.01 with the script from here:
https://www.androidfilehost.com/?w=files&flid=22367
You will need to adapt the 4.4x firmware to have the script flash it, but it's very easy, just a couple of files to rename.
When you open Julian's zip file you will see that he uses a script that flashes the firmware's images one by one. What I did was download the stock images from Google https://developers.google.com/android/nexus/images , used winrar to extracrt all the files from the .tgz file to a folder, then unzip the only zip file there (image-hammerhead-xxxxx.zip) which contains 5 img files. I then renamed the radio-hammerhead-xxxxx.img to radio.img and bootloader-hammerhead-xxxx.img to bootloader.img. Now all the file names comply with Julian's script. From Julian's archive copy the files "From Bootloader.bat" and "fastboot.exe" to the folder where all the images you just renamed are.
Put the phone in bootloader mode (turn the phone off, press the Vol- and the power buttons). Once the the phone is in bootloader mode, connect it to the PC and run "From Bootloader.bat" and follow the onscreen instructions. In about 2 minutes, your phone will be flashed.
Turn the phone on, if you are lucky it will load the OS. Disregard all the error messages, and don't bother setting the phone up. If you skip wifi, and don't have a sim in the phone you can finish the basic setup quickly.
Next you need to get developer tools activated: Settings>about phone>Build number. Tap 7 times on the build number and this will unlock Developer tools. Go back to settings and the new developer tools and enable usb debugging. Approve any popups.
I am not aware of how to enable usb debugging if you cannot go into the settings. If non of the stock images loads for you, search for a way to get usb debugging working , or else you cannot continue. You need this for ADB to connect to the phone.
Once this is done , boot the phone into debugging mode.
Read the guide here http://android.stackexchange.com/qu...dots-lollipop-screen-after-hard-factory-reset
I got as far as activating ADB Sideload when I got the error "cannot mount /persist". I then understood what the problem was. If you get the same error - you are in luck!
Then go here, to learn how to fix the broken persist partition.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
There are some prerequisites to getting this to work.
The first one is that the phone can be reached by ADB, this is why you needed the usb debugging mode.
Second, you need to install a custom recover image. Don't worry, you will overwrite it later. The one I used is TWRP. Get the latest version from here:
http://techerrata.com/browse/twrp2/hammerhead
To install I recommend you copy Fastboot.exe and the TWRP file to an empty folder on your PC . Rename the TWRP file to "recovery.img". Open a command prompt in the folder (see here if you don't know how http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm) , in the black window type: fastboot flash recovery recovery.img and hit Enter. Wait a few seconds and it will finish.
Third, you need to install an Android driver called Universal Naked Driver 0.73 from here: http://forum.xda-developers.com/showthread.php?t=2386956. Unzip the file to a folder.
Since the author of that guide states you need to uninstall any driver that already exists, I decided to install it on a PC that has no android driver. When you connect the phone to a windows 7 pc for the first time it will search for a driver. I disconnected the internet and windows installed a generic driver. In device manager I saw Nexus 5 with a yellow triangle. I Right clicked on it > update driver software > Browse my computer for driver software and point to the folder you unzipped the driver. You will get a warning - allow the installation.
Last, you need to root your device. (I think this can also be done from within TWRP , but I am not sure how...) I did this very simply by downloading CF-Auto-Root from https://autoroot.chainfire.eu/ The file you need is this: https://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip . Unzip it, put your phone in bootloader, run root-windows.bat.
Now you are prepaired... Follow the guide by bitdomo . Open a command prompt where adb.exe is located , and run the 2 commands bitdomo wrote. You will get a series of questions , type y followed by Enter until it's all done.
SInce you are still in bootloader mode, and a big START is at the top of the screen, click the power button to reboot. Now your oS 4.4x should load properly. Make sure everything is working.
Now you can flash to the latest firmware 5.10 - download the file from the developer site I gave before, use Jason Os's script to flash the image, and lock the device.
When I first booted the device , I saw that it only recognized 16GB instead of 32GB. To solve this install TWRP again, go to Wipe>Format data . Then reboot the device and make sure you have 32GB.
If you like the stock recovery instead of TWRP you can use Fastboot to flash the original recovery.img.
Now you have a working Nexus 5 , v5.10.
Thanks to LyricWulf and bitdomo for their life saving guides. I hope this helps others in the same spot, and saves them 200$ .
Addendum: According to bitdomo, installing a custom recovery like TWRP enables USB debugging by default even if the phone does not boot. I have not tried this myself, but this means you can foergo installing os 4.4x , and go straight to ADB and run the command that fixes the persist partition.
Go ahead and try it. It will save you a lot of time!
Click to expand...
Click to collapse
My N5 has exact problem as yours even same errors of camera and playstorw crashing when i loaded older android version.. now im positive your instructions will help me but im having some trouble with your steps i do not know how to type comnands with ADB .. im truly novice and dont want to damage the phone more could you simplify the steps or make a video please? Thank you

Sorry, I can't make it any simpler than that. I can't make a video now because my phone is fixed. Adb is very simple, it's like an old DOS window where you type the text. I would follow Bitdomo's advice and start by installing TWRP. This will get you USB debugging, and you can run ADB and follow his instructions to fix the persist partition.

[GUIDE] Unlock/Root/Flash for Moto X Style/Pure

[SIZE=+3]Heisenberg's How-To Guide For Beginners[/SIZE]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[SIZE=+2]Moto X Pure[/SIZE]​
[SIZE=+1]Intro[/SIZE]
This thread will serve as a location for basic how-to guides for the Moto X Pure. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
[size=+1]Prerequisites[/size]:
You'll need a working adb/fastboot environment on your PC to get through some of these guides. Go here to download the Android SDK, which will give you most updated version of adb and fastboot. Scroll to the bottom of the page and find Other Download Options>SDK Tools Only, and grab the right version for your OS. While it's downloading create a folder in C:\ called SDK (C:\SDK). Once you've downloaded the zip you can extract it into your C:\SDK folder. Navigate to C:\SDK\android-sdk-windows and open SDK Manager.exe. In SDK Manager you need to install the following packages:
Tools> Android SDK Tools, Android SDK Platform-tools
Extras> Android Support Library
Once you have installed those, inside C:\SDK you should see some new folders, one of them will be called platform-tools, within that folder you should see fastboot.exe and adb.exe. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide. To make sure adb is correctly installed, open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You'll find Motorla drivers here, download it and install, then reboot your PC.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
[SIZE=+1]Index[/SIZE]
How To Unlock Your Bootloader
How To Install A Custom Recovery On Your Device
How To Make A Nandroid Backup With TWRP Recovery
How To Root Your Stock Rom
How To Install A ROM with TWRP Recovery
How To Install A Custom Kernel With TWRP Recovery
How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System
[SIZE=+1]1. How To Unlock Your Bootloader[/SIZE]
Go into About Phone in Settings, click on Build Number 7 or 8 times until it says you have enabled Developer Options. Go back to Settings and enter the newly opened Developer Options section, scroll and click on the Enable OEM Unlock option.
Power off your phone then boot into fastboot mode (power + volume down).
Connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here).
Check your fastboot connection by issuing this command:
Code:
fastboot devices
It should return your device serial number, if not you need to make sure your drivers are installed correctly.​
Once you've confirmed your fastboot connection issue this command:
Code:
fastboot oem get_unlock_data
It should return something like this:
Code:
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
Copy that code (with no spaces between the characters) and paste it somewhere for safekeeping, you'll use it in a minute.
Go to the Motorola bootloader unlocking page. You'll need to create an account with Motorola if you don't already have one. Once you're signed in you can scroll down to step 6 and paste the above code into the text field and hit the “can my device be unlocked” button.
Read the terms and conditions and accept them if you agree (you can't continue unless you accept).
Click the “request unlock key” button and an email with your unlock token will be sent to the email account that you signed up with.
Once you have retrieved the token from the email you can use it within the following command to unlock your bootloader:
Code:
fastboot oem unlock xxxxxxxxxx
(Replace the xxxxxxxx with your unique unlock token)​
Your bootloader is now unlocked!
Reboot with this command:
Code:
fastboot reboot
It's now safe to disconnect your usb cable.
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
[SIZE=+1]2. How To Install A Custom Recovery On Your Device[/SIZE]
Prerequisites: unlocked bootloader.
Download the recovery of your choice, here's TWRP.
Make sure you check the md5 to verify its integrity (where possible).
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Put the phone in fastboot mode and connect it to your PC via usb cable.
Open a command prompt from within your fastboot folder (shift + right click, select open command prompt here), and enter the following commands:
Code:
fastboot flash recovery <filename>.img
(Replace <filename> with the actual filename of the recovery, the recovery filename in the command will change depending on which recovery you're flashing)
Wait for the recovery to flash, it'll only take a few seconds, you'll get a finished message in your command prompt window once it's done.
It's now safe to disconnect your usb cable.
Don't reboot the phone normally, use the volume buttons to highlight recovery and press the power button to select it. This will stop the stock OS from patching it with the stock recovery in boot. Once you've booted into TWRP like this once, you can reboot normally.
[SIZE=+1]3. How To Make A Nandroid Backup With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
A nandroid backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back. You can also use the backup tool to create a backup of your favourite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
All you need to do is enter TWRP recovery, select the backup option from the TWRP home screen, check the system/data/boot boxes, and swipe to backup. The process will take a few minutes.
[SIZE=+1]4. How To Root Your Stock Rom[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
Please note: this method is only valid for Lollipop, do not use this method on Marshmallow. You can find a systemless root method for Marshmallow here, big thanks to @ivcarlos!
Download SuperSU to your phone.
Boot into TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to where you have SuperSU stored on your sd card and select it.
Swipe to install.
Once you've installed SuperSU you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button. That's it.
[SIZE=+1]5. How To Install A ROM with TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
Installing a ROM is a pretty straight forward and easy process. Before you install anything you should make a nandroid backup (instructions above).
Download a ROM and appropriate Gapps package and place on your device.
Boot into your custom recovery.
Perform a full wipe.
Select the wipe option from the TWRP home screen.
Select advanced wipe.
Check the system, data, cache, and dalvik cache options.
Swipe to wipe.
Install the ROM.
Select the install option from the TWRP home screen.
Navigate to where you have the ROM zip stored on your sd card and select it.
Swipe to install.
Most ROMs will run an installer script at this point but some ROMs have what is called an Aroma Installer which allow you to choose some install options before the script runs.​
You will also need to install the appropriate gapps package directly after installing the ROM.
Once you've installed all necessary zips you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
[SIZE=+1]6. How To Install A Custom Kernel With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
A custom kernel can open up a new level of control over your device, such as overclocking/underclocking, undervolting, changing governors, changing I/O schedulers, adjusting colour calibrations, adjusting sound calibrations, and many other options.
Download a kernel that is compatible with your current ROM.
Check the md5 to verify its integrity.
Enter TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to the kernel and select it.
Swipe to install.
You'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
Once your phone has booted up you can use a kernel tuning app to change governors, I/O scheduler, clock speed, and other options. Some of the popular kernel apps are Kernel Auditor, Trickster Mod, No Frills, Kernel Tuner, and many more.
[SIZE=+1]7. How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
There may come a time when you accidentally wipe your OS while trying to perform a basic cache wipe in recovery. Don't laugh, it can happen to the best of us. The best way to insure yourself against being stuck in recovery is to keep a ROM zip or a TWRP/CWM backup (a nandroid backup) on your sd card at all times.
This solution seems like common sense but apparently there are quite a few people out there who don't store a ROM or backup on their phone. You might think it's easy to just mount the OTG storage and copy a ROM across to your phone from your PC (which is definitely an option), but there's always a chance that you won't be near your HDD or sd card at the time, or it won't recognise your phone properly. Basically you need to insure yourself against Murphy's law.
Donate To Me

This will be very helpful to many thanks for taking the time to put this together!
Sent from my XT1575 using Tapatalk

Thank you so much for taking the time on the guide. There will be many who will use it in the years to come! I'm just about at the verge of needing to root so I can get some insight into my battery life woes

This is much appreciated. All I did on my LG G2 was root as I did not see any roms that interested me since the bootloader is locked. I haven't used TWRP in a couple of years, so all this will help me clear the old cobwebs in my head.

Thank you so much for this! Exactly the kind of information I need. Can I trouble you to maybe add one more section to your guide: What to do when there's an OTA update from the manufacturer (Motorola)? I have concerns like:
- Would being rooted prevent OTA updates? (Assuming stock ROM).
- Would I need to "unroot" the phone to get the update? If so, how to unroot the the phone?
- Is the process to root the phone again after the the update the same, or could it possibly change?
- Would I need to wait until root is confirmed for the new version before attempting to re-root?

You said to "Make sure you check the md5 to verify its integrity".
What does this mean and how would I do this?

Thanks again for the guide. I went through this for my own unlock and root, so added a couple of minor things that will help noobs (and me!)
1. Add info on opening developer options, enabling ADB devices, and enable OEM unlock (in options screen)
2. Move this part to the start of the OEM unlock section : )
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
3. Add instructions to copy SuperSU zip file to internal storage and then flash in recovery

elitemeat said:
You said to "Make sure you check the md5 to verify its integrity".
What does this mean and how would I do this?
Click to expand...
Click to collapse
You can download an MD5 checker. They give you the MD5 checksum and you can compare when you run the utility. Just do a google search for md5 checker.

Oops

emailrob said:
Thanks again for the guide. I went through this for my own unlock and root, so added a couple of minor things that will help noobs (and me!)
1. Add info on opening developer options, enabling ADB devices, and enable OEM unlock (in options screen)
2. Move this part to the start of the OEM unlock section : )
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
3. Add instructions to copy SuperSU zip file to internal storage and then flash in recovery
Click to expand...
Click to collapse
Thanks for your suggestions.
1. This info has been added.
2. This section is in the same place in all of my guides, I see no problem (and have had no problems) with its location. Anyone following a guide should read it first before attempting it anyway.
3. I've added inductions to download the zip directly to the phone, less mess.

emailrob said:
Thanks again for the guide. I went through this for my own unlock and root, so added a couple of minor things that will help noobs (and me!)
1. Add info on opening developer options, enabling ADB devices, and enable OEM unlock (in options screen)
2. Move this part to the start of the OEM unlock section : )
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
3. Add instructions to copy SuperSU zip file to internal storage and then flash in recovery
Click to expand...
Click to collapse
This is already covered here:
http://forum.xda-developers.com/moto-x-style/help/root-to-updates-t3200588

Oaklands said:
You can download an MD5 checker. They give you the MD5 checksum and you can compare when you run the utility. Just do a google search for md5 checker.
Click to expand...
Click to collapse
If you're on Windows, I highly recommend this one, I've been using it for ages: http://code.kliu.org/hashcheck/

I flashed SU and it didn't give me root, any suggestions?

mxpxboi said:
I flashed SU and it didn't give me root, any suggestions?
Click to expand...
Click to collapse
Have you enabled root for apps (and adb if you wish) in Developer Options?

Heisenberg said:
Have you enabled root for apps (and adb if you wish) in Developer Options?
Click to expand...
Click to collapse
I don't see root for apps in Developer Options.

mxpxboi said:
I don't see root for apps in Developer Options.
Click to expand...
Click to collapse
Ok. I don't have this device yet (I have to jump through a few hoops to get it in my country), hopefully one of our other helpful members can lend a hand with your problem.

Heisenberg said:
Ok. I don't have this device yet (I have to jump through a few hoops to get it in my country), hopefully one of our other helpful members can lend a hand with your problem.
Click to expand...
Click to collapse
Well thanks for your help anyway. I followed the steps to a tee, and no root. So I was a little confused.

mxpxboi said:
Well thanks for your help anyway. I followed the steps to a tee, and no root. So I was a little confused.
Click to expand...
Click to collapse
It's a bit odd because this is definitely how to root this phone. Was the SuperSU flash successful in TWRP? Have you tried a second time?

Heisenberg said:
It's a bit odd because this is definitely how to root this phone. Was the SuperSU flash successful in TWRP? Have you tried a second time?
Click to expand...
Click to collapse
It did flash successfully, I flashed the one it linked to UPDATE-SuperSU-v1.94.zip, I'm going to try the newest one BETA-SuperSU-v2.49.zip. I'll report back.
---------- Post added at 10:57 PM ---------- Previous post was at 10:44 PM ----------
That worked, I would update your post with this link BETA-SuperSU-v2.49
Now if I can figure out how to remove the bootloader unlocked boot screen.
All root apps except Titanium Backup seem to be working for me.

mxpxboi said:
It did flash successfully, I flashed the one it linked to UPDATE-SuperSU-v1.94.zip, I'm going to try the newest one BETA-SuperSU-v2.49.zip. I'll report back.
---------- Post added at 10:57 PM ---------- Previous post was at 10:44 PM ----------
That worked, I would update your post with this link BETA-SuperSU-v2.49
Now if I can figure out how to remove the bootloader unlocked boot screen.
All root apps except Titanium Backup seem to be working for me.
Click to expand...
Click to collapse
Cool, I've updated the link. There's a thread discussing how to remove that boot screen in the q&a or general section. Not sure about your Titanium problem, if you have root access it should work.

How to install new ROM on GEM 701, 702 and 703

This thread is a continuation of existing threads, which started when Model 701 was not out yet.
Update 2017-04-22
Since we have verified that the "downgrade script" opens the door for multiple Mediapad X2 models we have much easier way:
Do a full backup with Huawei Backup Application ("Datensicherung") and copy all stuff from internal sd to external which you put manually on it.
For push applications like whatsapp do a backup of chat in whatsapp, manually on your google drive.
Unlock bootloader
https://emui.huawei.com/en/plugin/unlock/detail
create account, via selecting Honkong as localisation.
Then login on https://emui.huawei.com/én/plugin/unlock/detail
If it's redirected to a EMUI site, then simply call the link again https://emui.huawei.com/en/plugin/unlock/detail
check the agree box and fill the page with: "Before EMUI 5.0" and put model name in the field "GEM-701L" or "GEM-702L"
Then fill out the rest (you have to optain the productID via entering in Phone as if you will make a call: *#*#1357946*#* )
Then Huwaei will give you the bootloader code directly on this page.
install minimal adb and open cmd window
connect phone and start with VOL down key
type: fastboot devices
if you get no answer you'll have to update the windows driver to "ADB sooner single interface"
if you get answer type
fastboot oem unlock xxxx (wher xxxx is the bootloadercode you got from page above)
Do factory reset from EMUI (not from recovery, it will work, but you'l get problems later)
if you had replaced the original recovery with TWRP you must flash it back:
fastboot flash https://drive.google.com/file/d/0B5TWnuLR7ugZRmdVdEhzdjM3Tms/view?usp=drivesdkrecovery.img for B003 or B005 back if you already replaced it.
then download the "downgrade script" . Unpck the rar and put the dload folder to internal SD
Select Update in EMUI settings menu and select "local upate" and then "full update" from internal SD.
Then download the from the very slow huawei server B202 full package (DEMO) and put the dload folder to external SD (or internal)
Start system and select update and "local update" and install it.
Then boot in bootloader/fastboot mode again via VOL - key and flash TWRP for Android 6.0 via adb: fastboot flash recovery TWRP-ENG-6.0-BLACK-BLUE.img
If you install it via fastboot flash recovery2 TWRP-ENG-6.0-BLACK-BLUE.img , you will not overwrite the original recovery, which is need for factory reset or dload) If recovery is on recovery2 then you must keep a USB connection to PC to be able to start the TWRP. Otherwise remove USB cable before you boot into TWRP.
Start TWRP via holding VOL + Key via starting the phone and allow modifications and then press Install button and select external SD and then the kangVIP 212 V2
Or now newest version KangVIP V3 from thread https://forum.xda-developers.com/showthread.php?t=3215851
Wipe cache and dalvic and reboot to system.
Wait several minutes until first boot is finished. If you already have apps installed (dirty flash over existing KANGVIP) this may take up to 40 minutes)
If you need to do a factory reset from EMUI you will need the original Huawei recovery B202 wich you can install via fastboot
Restore your apps from Huawei Backup, besides Whatsapp.
Install whatsapp and then the question comes up to restore your backup.

THE REST BELOW THIS LINE HERE IS ONLY FOR HISTORICAL INTEREST or for people who have already updated to 5.11
################################################################################
Update 2016- 04 -05
See short way with B112 on http://forum.xda-developers.com/showpost.php?p=66156287&postcount=215
Hint: This seem not a 100% convesion to 5.1.1 because storage handling did not change.
Advantage: You may goback to B003 with a nandroid.
Unverified: If it can still charge on such a rollback
----------------
Meanwhile we have figured out how to flash a new ROM even on GEM 701 L.
Thanksgiving to all who have participated in this. Especially to ajsmsg78, eennap, ZeuseZ, and Ante666
I you have a 703 Model, you can simply upgrade via OTA and then go to one of the threads ajsmsg78 made and choose which ROM you like.
If you have Model 701 oder Model 702 you can use this thread, if you already have at least firmware B003 on your device.
Current situation in Jan 2016:
If you have a firmware B001, or B002, then zip your folder "/cust" and send it to ajsmsg78.
Then he would integrate it into the "universal cust". Please wait until he did this.
The "Universal Cust B112" hast the filename variant "UNIVERSAL-CUST-B112.zip"
Later if you install the SIMPLY_GOOGLE ROM Version a variation of this "cust" will be automatically installed then it is called "Simply Google B111 Cust".
If you install a B111KangVip or the NearStockB111 the "universal cust" also is integrated
Don't worry about the names, it is used to display the correct Roms name.
If you have 701 or 702 model, you may have heard, that Huawei published firmware only for the 703 model.
So we have to convert our device into a 703 model, by keeping it's hardware based additional LTE bands.
If you have converted by doing the following steps to B015,
you will be able to upgrade Android 5.0 to Android 5.1.1 on the follwing steps for D106
---------------------------
Update 2016-28-02
It seems possible directly install the B112. So much easier now. Just flash 4 B015 files, install the "universal cust B112" and then do "dload" procedure for B112.
Then you are on stock B112 can can flash the stabile "Near Stock B111". I have edited the new way in the post below
------------------------------------------------------------------------------
After that you will be able to install updated directly from Huawei via the OTA (Over the air) method, if you have a stabile WLAN connection.
This does not give you a direct jump from B106 to B111 (or B112) , so don't try this on the "dload" method.
My experience was that some components are not updated if you skip a version. Evidence see here
Alternatively you will also be able to do manual "dload" processes.
This both methods lead you up to version B112
After this you can install one on ajsmsg78 ROMS.
They differ in the composition of removing and adding components.
So look which version is the best for you and check, if it is up to date or maybe discontinued.
This are the steps to flash from 701L (B003) to custom firmware
Be aware: Don't try to return to B015 or B003 (Android 5.0), after you have once installed Andoid 5.1.
You will loose the ability to charge the phone in this case.
But it is possible temporary go back. For this you will find the guide in post 2 of this thread
If you have a lower version like B001 or B002 you MUST save your folder /cust to a zip fle and send it to ajsmsg78 and ask for advice!
Don't start flashing in this case!
If you already have a higher version than B003 you can skip the steps which lead to your version.
If you have B006, it seems that you can not upgrade. You must first downgrade to B003. Please report if you find a way.
Maybe you can do the dload for B112. Try this and report!
In case if you want to return to B003 there is a possibilty - > this is documented at post 2
----- To those who have already installed: Please check if there is missing something or wrong and leave a comment. ---
Steps are numbered to be compatible to then numbering of eennaps guide. (Some steps differ, because of newer cognitions.
- First of all: Be sure you have enabled USB debugging on your device. Otherwise you can not go into "manufacture mode" for DC - unlocker
To enable this you have to select "about phone" and tap 7 times on the "build number". After that you will find "developer options" in main menu.
- install ADB or got to ADB XDA Forum
- if you are on Win 10, then install Hisuite (for DC - unlocker manufactur mode drivers)
- Unlock Bootloader via DC-Unlockerr (see [https://drive.google.com/file/d/0By1mhgPLc1LqUzV0QVVRWmpBWlE/view?usp=sharing] reduced eennaps document just for the unlock chapture [/URL] for these steps )
If you get you code from Huawei, just open cmd window on PC and type
fastboot oem xxx
and replace xxx with the bootloader code you got from Huawei or DC-Unlocker software
If you have an unlocked phone you can start with these steps
Step 1
1.1 a - Download 2 TWRP versions
To download the files from Google drive klick on the little download icon. NOT ON THE FOLDER
5.0: https://drive.google.com/file/d/0By1mhgPLc1LqSlRTRVhmbjhTcjg/view?usp=sharing
5.1.1 https://drive.google.com/file/d/0B5I_q70mNuR4QkFzM2xOWVlvRkk/view
and put both files into your ADB folder on Windows PC.
1.1 b
- Download 4 Files from Firmware B015 which I have extracted via Huawei Update extactor
BOOT.img, https://drive.google.com/file/d/0By1mhgPLc1LqeGNLc0VKRVRNR2s/view?usp=sharing
RECOVERY.img, https://drive.google.com/file/d/0By1mhgPLc1LqTVd0c3FYVWJrVlU/view?usp=sharing
SYSTEM.img https://drive.google.com/file/d/0By1mhgPLc1LqZWY2SHJuaXB4YUk/view?usp=sharing
USERDATA.img. https://drive.google.com/file/d/0By1mhgPLc1LqeTJITEhGRk9ZNGs/view?usp=sharing
You can check the MD5.
1.1 c Copy these 4files into your ADB Folder on PC
1.1 d : insert a at least 32 GByte Class 10 SD Card. (better 64 GByte)
B: Copy all your content from the internal drive to the external SD card in a folder (for example name it "int_SD_Backup")
1.1 e: download ajsmsg78's "universal cust" and put it to the external SDCard.
1.1 d: Download at least the first 2 files (if you later want to go via OTA ) or all 4 Firmware versions, if you prefer the offline "dload" method for all files.
edit: It seems it is sufficient only download the B112 stockhttps://www.androidfilehost.com/?fid=24385226645962831
optional: B015
and also optional: B106,
optional: B109, and B111 if you prefer the dload method for these versions, too. For this download them from here
Step 1g-unzip these files to your PC and copy later step by step the unzipped folder "dload" of version B112 to your ext SD-Card (root directory not in subfolder)
I used a external USB SD Card Reader, this is faster than to copy via USB. But both works.
1.1 h: I recommend fist do download a near stock Variant NearStockB111 [/B] an put it on your external SD Card.
But you can also download B111KANGVIP or the much more dbloated "Google" ROM SimplyGoogle and put the zip file on the external SD-Card. Be aware: these 2 last variants do not include the Huawai Backup appliation to restore your saved configuraton. And the SimplyGoolge Variant is not stabile at this point of time.
After 4 weeks testing the Kangvip V2 and Simply Google (made in Feb 2016) I return today to "Near Stock", because KangVipV2 has white icons on white background on navigation bar when you hold in landscape mode. SimplyGoogle has not the full features of boot menu and a
advanced settings and you can not install XPOSED on it. So I recommend the "Near Stock". I saw no added features between 111 and 112.
I believe it is just to skip B109. This makes things easier. I update the guide for this today (2016-02-24)
1.1 i On Phone: Start the Huawei Backup App (Icon "Backup" or german: "Datensicherung")
and do 2 Backups on SD Card (one for account and settings and one for your apps)
1.1 j: Restart Phone in BootloaderMode (Vol - and Power Key while USB Cable is connected)
1.2.a On Windows PC: Do a Shift-Key-right-click on the ADB folder and select "open command here" .
Then type in the cmd window the following command to Flash X2_TWRP_CN_5.0 (not yet version 5.1 because it does not start on a 5.0 System)
fastboot flash recovery TWRP-ENG-5.0.img
(this takes 2-3 seconds)
1.2.b Remove USB cable and press Power Key until screen is dark
then press Vol + and PowerKey and hold until something comes on screen
then release PowerKey and hold Vol+ Key until TWRP starts.
1.2c Make a "NANDROID" of your current ROM
press "Backup" Button.
press the last line "storage:" and select external_sd
swype for backup and wait (about 4 -10 minutes until message [Backup Completed ....])
- press home key (bottom left)
1.2d WIPE CACHE and DALVIC
from main menu select "Wipe" and then "Advanced Wipe"
check "Dalvic Cache" and "Cache"
swipe to wipe
press home key (bottom left)
1.2e press Install and select UNIVERSAL-CUST-B112 (this is the universal cust) and swpe to install (maybe change "storage" to find it)
Step 2a) boot into fastboot (Vol - and power key)
- on windows in command window go to the ADB folder and type the following commands.
I highly recommend to copy the black lines from here an paste in the adb window to prevent typos.
Step 2b
If you come from B003 you can directly flash thes 4 files from the B015 version
fastboot flash boot BOOT.img
fastboot flash system SYSTEM.img
flashing system takes some minutes and does several actions. Wait until all are finished
fastboot flash userdata USERDATA.img
fastboot flash recovery RECOVERY.img
fastboot reboot
New: --> Try to skip step 3 and directly go to step 4a to "dload" the B112 stock
3a reboot system and do minimal setup and select "Settings" and scroll down for the "Backup and reset" menu.
3b select "Factory data reset" and check "format internal SD" (Remember : you had copied everything to SD Card and made a backup with the Huawai Backup Application. So you can do this risk free)
EDIT: (see post 3 and 4 normal recovery is necessary to do the factory reset)
3c after system reboots, shut down by pressing powerkey to be able to install the "universal cust"
- boot into fastboot mode and flash vom ADB window:
fastboot flash recovery TWRP-ENG-5.0.img
then and boot into TWRP and
3d press "Install" ,select KANGVIP-B111-CUST-MOD.zip and swype to flash. (you have to disable the MD5 verification checkbox.)
3f - boot into fastboot mode and flash the B015 recovery.img again which you had uploaded on step 1.1.b , because system needs it for the dload process in step 4.
fastboot flash recovery RECOVERY.img
Update 2016-28-02
4. a then reboot the machine and select from "options" -> "Update" and press menu icon for "manual firmware update" and select update from ext SD Card. This flashes all components of GEM-703L official stock ROM B112 via the dload folder.
--> Now go to Step 6
4. b If you come from B006 and and you run into error, you could try to dload the B106 update.app on this step. If this fails you have to install the B003 first and then flash the B015 and go on.
If you come form B006 and decide to stop the whole process you can restore your backup and then install B006 recovery
If you come from B006 the latest tests show that you first have to install the B003 and then start from the beginning of this thread
If you do the "dload" for B106 then it might might fail at 98%, because you have not installed a full B015. But don't worry, you can go on in the next steps without any errors. We have tested, if this can be prevented via dload B015 first. Some people reported it worked, but I seems not to be neccessary, so I removed this point in the guide
THIS is the point where you change from Android 5.0 to Android 5.1
5 g Reboot Phone, do a minimal configuration and select "Settings" and scroll down for the "Backup and reset" menu.
5 h select "Factory data reset" and check "format internal SD" This is important because now you are on Android 5.1.1 and the internal SC Card handling has changed.
5 i wait until reset is finished and the system starts again: Do again minimal configuration
5 j Then go to the firmware update menu and check if there is a OTA update available
5 k Select firmware update B106-> B112 (this comes via OTA)
6 If you have installed the B112 reboot the system and do a minimal configuration[/B]
7-9 dropped, because we don't need to install B109 and B111 stock anymore
Don't worry about the the info in "about phone" that internal Memory is only 1 GByte and you were on Android 4.1.1
This is, because the 703 firmware is running on a 701 or 702 model.
This is only a display issue. This will be fixed via the "universal cust", which will be automatically again installed later.
10 reboot into fastboot to flash the new TWRP
11 fastboot flash recovery TWRP-ENG-5.1.1.img[/B]
12 reboot into TWRP and make a backup of this clean stock B112, to be able to do a upgrade to Android 6.0 in future.
The next step will install the first custom ROM on your device wich will fix the problem with the wrong display of memory and Andriod Verision
13. Press "Wipe" and do a factory reset within TWRP
14 Press "Install" and install NearStockB111 from your external SD Card.
15. select Press Button "WIPE" and "Avanced" and check boxes to wipe cache and dalvic and Data and reboot into system.
16 go for coffee and after about 5 minutes later you are in B111 KangVip.
Now check in the "about phone info" if, Version = Android 5.1.1 and your Memory is correct.
This version is made from B111. I tested KangViPB112 and found no advantage in it. It was not stabile with KANGVIP V2. It has ab bug on the navigaton bar in landscape mode. On some apps you will have white icons on white background. So I advice to stay on B111 KangVipV1 near Stock. It is stabile and has the most feature. And you can install Xposted via the playstore Xposed installer, too.
17. do a full configuration. Maybe your 5 MHz WLAN will not be displayed. Then turn WLAN off an on or do a reboot to fix that.
18. Go into Advanced Settings in Settings and uncheck Lunar Calendar and Desktop Weather Lunar (if you see chinese letters somewhere)
19 Start Huawai Backup application and select your backupfiles to restore (first the accounts then apps)
If you can't find Huawei Backup look inside app folder of this link on phone and click on HWALLBackup and "install"
20 If you don't like gmail, install "myMail" app from playstore.
20 If you don't see SuperSu, you can alternatively use "Kingroot" and do start konfiguration inside to get the full control which apps will be allowed to have root access
You have alternatives which custom ROM you could flash via TWRP later:
NearStockB111: You have already installed this, if you followed this guide.
I advise to use this version. It is stabile.
It does not contain Supersu, but it uses KingRoot. (You can change to SuperSu)
This means you will be rooted and have control via the Purify app on the root authorization and autostart via this alternative
you will not have the whitescreen bug which has something to do with conflicts between SuperSu and KANGVIP Tools V2.
This version is almost like the stock B111, rooted but without chinese bloat ware: NearStock B111
You will find all Huawei system apps and the Backup.app where you can recover all your saved data
The other 2 versions do not include the Backup app. You can install them later.
KangVipSlim : Version with reduced system apps and "old" KangVipTools V1" very less Google staff go here
21. Goto http://forum.xda-developers.com/mediapad-x2/development/rom-kangvip-5-1-1-b108-t3215851
SimplyGoogle with KangVipTools V2 (And Supersu) and integrated Xposted SimplyGoogle
and read whats new on the release and don't forget to press thankyou button for asjmsg78
Be aware on SimplyGoogle: On the first boot, there may be a window form Superuser (SuperSu), which asks for permisson to "KangVipTools"
You must give permanent access, otherwise you will get a white sceen and you would not be able to use the Rom.
This is currently a known problem and might be solved later.
There are some unsolved problems with "Xposed" on this version.
If you ever want to start the whole process again from B106 then
download the 5.1.1 recovery from B106
--- reserved ----
01-15 installing the recovery is nevertheless necessary to do a factory reset on step 3 b
01-16 reduced the word document to just the steps for DC-unlocker
inserting installing universal cust on start
and wipe dalivic/cache
and skipping flashing normal cust (ajsmsg78 says this will work)
01-17 changing the link for the cust to the "universal cust", because of the includes ROM name. This may be confusing on this process.
01-18 inserting a format of internal SD card. Someone reported it was not correct after the whole process.
inserting wipe also data to prevent the while screen bug on the first start of SIMPLY GOOGLE
replacing SimplyGoogle with the NearCustB111 variant as first Custom Rom, because it includes the Backup.App from Huawei.
01-19 the error free dload on the B015 is confirmed. This is because we inserted to flash the universal cust before and skipped to install the cust.img
added reset and format internal sd directly after first android 5.1.1 installation
If you use the NearStock Rom you have to launch kingroot an do start konfiguration inside.
01-24 Moved the steps for returning back to Android 5 to this post 1, because it is a fact, that the phone will not continue charging, even if you have installed the "dload" of B003.
02-28 Seems that dload B112 stock on a patched B112 (via fasboot flash) gives you the full upgade (B016 and B0109 only were "delta" upgrades)
03-28 TheNearStock B111 link has been lost: I uploaded my copy from Jan18 here
Return to B003
If you have not updated to B105 and you are still on a Android 5.0 system you can install the B003 software again via "dload"
B003: Here you get the original B003 firmware which we could download directly from Huawei. Meanwhile it not available anymore, so we were lucky to save a copy.
It will work to do a manual firmware upgrade ( "dload") this, if you are still on a Android 5.0 version up to B015.
If you are on a Andriod 5.1.1, this may work also. But don't try this for fun.
You will loose the abilty to charge the battery.
This is because the method of charging the phone has changed in Android 5.1.
This specific charging method for Android 5.0 is not included in a Nandroid backup or any update.app (dload) files Huawei published.
So you could go back , but only do this with a full charged phone. Then you would be able to restore the NANDROID you have made as the first step before flashing the update. You will be able to look into some data, which you may forgot to save or for any reason else. But don't wait so long until your battery is empty. To return to Android 5.1.1 simply flash the boot.img, userdata.img and cust.img and system.img then do a "dload" to B105 (Andoid 5.1) Then you will be able to restore a 5.1.1. NANDROID of your last running system.
But in case of emergency and after you have tried everything else.
1 a install TWRP (if possible)
if not possible go to step f
b Wipe -> factory reset then
c boot into fastboot mode:
d to Step 2
f only if the above steps didn't work do this:
boot into fastboot and paste the follwing commands into your ADB windows (on PC) and press Return
fastboot erase userdata
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
2
Install on your PC the Huawei Update extractor
3 Extract the files boot.img , recovery.img, userdata.img, cust.img, system.img, cache.img
4 Flash boot, userdata and cust files: from your PC ADB window:
fastboot flash boot BOOT.img
fastboot flash userdata USERDATA.img
fastboot flash cust CUST.img
fastboot flash cache CACHE.img
then boot into TWRP and do a recovery of your last Andriod 5.0 NANDROID
5 Then you would be able start the system and do minimal configuration
6 then do a factory reset from the system.
7 a after reboot you can flash the rest via initiating update via running system
or via a manual "dload" :
- putting the folder "dload" with the B003 update.app into the root directory of a SD card.
- put the SD card into the phone and press Vol+ and Vol- and Power at the same time.
If something comes visible on screen, then release the power key and hold both knobs until the dload starts.
Maybe you have to connect the phone via USB to the PC, or flash the 5.0 recovery before you try this.
Please report if you came in this situation and tried this.
Please keep in mind: If you have came to this point, you will not be able to charge the battery anymore.

My 'old' GEM 701 converted to 703 got stolen. The only positive aspect of this event is I was able to repeat the conversion process again on a new 701 and verify the guide audioralf built so far.
My findings:
1. I was not able to do step 3.a (factory reset + internal SD format). The system didn't boot with TWRP 5.0 flashed no matter what I tried. Ii was rebooting back to TWRP in a loop. Then I did following:
1.a fastboot stock B15 recovery
1.b reboot,
1.c minimal setup (internal SD 3GB only).
1.d factory reset + internal SD card format. Completed with an error
1.e reboot
1.f minimal setup (internal SD size ok, >20GB)
1.g fastboot TWRP 5
1.h flash universal B111 cust
1.i fastboot stock B15 recovery
1j. dload B15 - no errors, wrong info
1.k fastboot TWRP 5
1.l flash universal B111 cust
1.m fastboot stock B15 recovery
1.n factory reset, no errors
1.o B15 intalled, info correct
2. dload B106 , no errors, wrong info
2.a fastboot TWRP 5.1
2.b flash universal B111 cust (info correct)
2.c fastboot stock B106 recovery
2.d factory reset, no errors
2.e B106 intalled, info correct
3. dload B109 , no errors, wrong info
3.a fastboot TWRP 5.1
3.b flash universal B111 cust (info correct)
3.c fastboot stock B109 recovery
3.d B109 intalled, info correct
4. OTA B111 , no errors, info correct
final note: it is important to flash universal B111 cust after each dload, otherwise the phone info is incorrect and following dloads/factory resets/OTAs will fail

Thank you for replying.
The steps you describe were steps to come out of the returning to TWRP.
I have updated the guide!
Reason:
I see that we have to install the original recovery to be able to do the factory reset from the running system (UI)
So I inserted the installing of recovery. It i circumstandly but it was a restrict advice from ajsmsg78 do run a factory reset from UI
I have inserted the universal cust like you have described everytime until step 5.
I was able do do the dload 106, 109 and 111 without any error and without installing the universal cust on each step.
If the "about info" is wrong it doesn't matter if you are already on B106.
The "universal cust" is integrated in the SimlpyGoogle Version, so everything is fine after you have installed that on the last step
I guess it is necessary to install the universal cust only on the step, where you are installing the B015 to make it a "703 device"
and on updating to B106 when it upgrades vom 5.0 to 5.1.1
So i keep the instructions in this way. I have a fully updated and good running system.
If anyone still gets problems, feel free to report here.

I edited my guide: First I thought it was because of flashing also the userdata.img. But this seems to be not the issue, but the missing recovery for the factory reset.
but I don't know if it is normal that you got this:
1.d factory reset + internal SD card format. Completed with an error
Click to expand...
Click to collapse
So let's hear what ajsmsg78 thinks about this.

audioralf said:
I edited my guide: First I thought it was because of flashing also the userdata.img. But this seems to be not the issue, but the missing recovery for the factory reset.
but I don't know if it is normal that you got this:
So let's hear what ajsmsg78 thinks about this.
Click to expand...
Click to collapse
Yes, it is normal, because phone info is wrong at this time, universal B111 cust were not flashed yet. But internal SD got formatted in the process.

Ok to prevent this error message we should install the universal cust additional before this step?
Some more step ...
I suggest the easiest way is to install the universal cust at the first step when doing the TWRP backup, and then skipping to fastboot the normal cust.
I edited the guide for this variant and inserted the wipe for cache and dalvic.
Ralf via Tapatalk. GEM701L, B111Kangvip Rom

Hi, is the B003 method also appy on my GEM-702l B005 version?
A while back, there's an ota and I've got my gem-702l updated to B005.
My current Android version is 5.0.1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Do a NANDROID this will bring you back.
I don't know if B003 would run on a 702. If if was delivered with b003 I would try it, if other solutions had failed. If you are still on 5.0 you will be able to restore the nandroid If it fails. I know from 1 person, who has successfully used this b003 package on a 701.
Please report if you had tried and what the result is.
Ralf via Tapatalk. GEM701L, B111Kangvip v2 SiGo

audioralf said:
Do a NANDROID this will bring you back.
I don't know if B003 would run on a 702. If if was delivered with b003 I would try it, if other solutions had failed. If you are still on 5.0 you will be able to restore the nandroid If it fails. I know from 1 person, who has successfully used this b003 package on a 701.
Please report if you had tried and what the result is.
Ralf via Tapatalk. GEM701L, B111Kangvip v2 SiGo
Click to expand...
Click to collapse
　
Yes, B003 runs on gem-702l. My device is a TW version. The default ROM when I bought it was B003, then there was an OTA to B005 about 1 or 2 weeks ago. I am still on stock rom of B005. I am gonna give it a try. Thanks.
By the way, I read it from the previous thread that a B005 version was found in Huawei's official website but everyone's not sure about it. I believe Huawei indeed has a B005 for gem-702l. At least for a TW version.
Here's the download link I copy from the Huawei TW official website:
GEM-702LV100R001C209B005CUSTC158D001
---------- Post added at 12:06 AM ---------- Previous post was at 12:04 AM ----------
Ok, I have a new question.
The step 4:
"4. b This flashes all components of GEM-703L official stock ROM B015 via the dload folder. "
But my TW version has different 4G LTE bands from China gem-703l. Does that mean my bandbase will be modified by this process?
Thanks.

We have never heard anyone loosing LTE bands. The hardware sets which LTE bands will be supported. The baseband drivers inside these packages seem to be designed for all variants.

A(alternative) for installing a Stock B111 with GApps and Root
As of B109 Google Apps are missing from the ROM.
In case you want stay Stock B111 but don't want to live without the Google Apps, most notably the Play Store, here's a guide how to add them to a ROM. The guide takes place after you installed B111. I wrote it because I want to stay Stock.
Oh - you can indeed uninstall all Chinese Apps and some Huawei apps without root.
A(alternative) for installing a Stock B111 with GApps and Root
A10 - restart in fastboot mode
A11 - flash the TWRP for 5.11 from ADB cmd window with the command
fastboot flash recovery TWRP-ENG-5.1.1.img
A12 - download OpenGAPPS micro package from opengapps.org . NOTE: select ARM64 and Android 5.1 . The Huawei X2 is equipped with a 64bit processor
A12b - copy the ZIP to your external microsd (either with a USB Stick, or while in TWRP recovery and connected via USB)
A13 - boot into TWRP recovery and flash "open_gapps-arm64-5.1-micro-20160119.zip"
(A13b - you could also flash SuperSU at this step while you are at it)
A14 - IMPORTANT: Go to 'WIPE' in TWRP and do a full factory reset! Otherwise, when booted youll be greeted with a black desktop and only the status bar visible!
A15 - reboot into the system, configure it, and that's it. NOTE: Most Chinese mobile phones with Google Services missing won't let you add more than 1 Google Account from the Settings -> Accounts options. So, if you want to use more than 1 Google Account on your X2 , just fire up Google Mail and add the second, third, etc Google account in GMail. It'll be fully synchronized with your mobile then.
NOTE: You edited the system that way. Even if you do a factory reset from within the Android System, GApps and SU will stay.

I have a problem, I can't run Huawei Update extactor on my win10 pc, it keeps saying " Huawei Update extactor stop working " and it terminates it self before the program even start. I've tried in al different compability mode, but none of them is working.
Anyone got an idea about whats wrong ?

Aznbull said:
I have a problem, I can't run Huawei Update extactor on my win10 pc, it keeps saying " Huawei Update extactor stop working " and it terminates it self before the program even start. I've tried in al different compability mode, but none of them is working.
Anyone got an idea about whats wrong ?
Click to expand...
Click to collapse
Try this. Click Start, click Run, type MSIEXEC /UNREGISTER, and then click OK. Even if you do this correctly, it may look like nothing occurs.
Then click Start, click Run, type MSIEXEC /REGSERVER, and then click OK. Even if you do this correctly, it may look like nothing occurs, or you may briefly see an hourglass. After you run this command, the operation is complete. Reboot your computer, then try running it.

I am an owner of Mediapad X2 701L on B001 and there is no OTA update for my device. I used to have Mediapad X1 501u which didn’t get update too. So I converted it to 503L and managed to get updates. But this conversion uncalibrated my device sensors like digital compass and I didn’t manage to fix that.
I am very tempted to convert my 701L to 703L, but I’m just worry about four things?
1- Are the sensors calibrated and exact after conversion of 701L to 703L?
2- Is my LTE bands still supported in 703L?
3- How can I zip my cust? I haven’t managed to root my device yet, so I can’t use root explorer / is there any other method like updating my 701L to B003 locally? Any download link would be appreciated
4- Is there any method to restore my current ROM if I didn’t get good feedback from the conversion?
Many thanks in advance

1 have no problems with Sensors
2 no problems with LTE
3You must unlock anb install TWRP for 5.0
Then install superuser.
Then install a filemanager to be able to copy your \cust folder to discard
Then copy it via usb to pc
Then zip this folder
Then send it to ajsmsg78 or upload it to dropbox and publish the link
It does not contain any personal data. You will see this on the filedate.
There are done people waiting for you, who have already flashed a new firmware and have problems because ajsmsg78 has to integrate some files from your cust to the universal cust.
4 you can make a nandroid Backup of your System to return. So after flashing B003 you would be able to restore you're backup, and you will be back on b001.
Ralf via Tapatalk. GEM701L, B111Kangvip v2 SiGo

ajsmsg78 said:
Try this. Click Start, click Run, type MSIEXEC /UNREGISTER, and then click OK. Even if you do this correctly, it may look like nothing occurs.
Then click Start, click Run, type MSIEXEC /REGSERVER, and then click OK. Even if you do this correctly, it may look like nothing occurs, or you may briefly see an hourglass. After you run this command, the operation is complete. Reboot your computer, then try running it.
Click to expand...
Click to collapse
It doesn't change anything, still can't run the software.

For what do you need the extraxtor? The files you need are already extracted and linked in my guide.
Ralf via Tapatalk. GEM701L, B111Kangvip v2 SiGo

I know that you already linked the files i needed, I just wanted to try everything out before I jump in all this flashing to another version. Just to make sure that if the link you provide all of a sudden is dead, I still can extract the files my self.

I have a gem-702 b006
They are blocked in step 4 b
when you restart hangs straight at 0% and does not install the dload b015
how to solve?
I also recharged 2 times "fastboot flash recovery RECOVERY.img"

[STOCK] [MM] Root Xperia Z5 Premium Sony Stock Marshmallow (Android 6.0) Guide

The updated cross-device Sony thread tested with Nougat is here.
Guide updated on 21 October 2016.
PREFACE
First of all, this guide will probably work for all recent Sony phones.
This guide is based on a work of number of people. The information how to get this goal achieved is very sparse and it is scattered across the Internet. There are lot of guides, but typically they require a strong familiarity with many things, so inexperienced users may became confused. I decided to assemble a detailed newbie-friendly guide myself. So here it is.
Get rooted stock Sony firmware is not a straightforward and easy task, but if all steps covered in this guide are performed well, the goal will be achieved. Since the creation of this guide, stock firmware versions got bumped multiple times, but nothing has changed fundamentally in terms of rooting.
In this guide I (and you) will use the stuff from these notable people:
@Androxyde — Flashtool
@IgorEisberg — XperiFirm (integrated into Flashtool)
@Dees_Troy et al. — TWRP
@Chainfire — SuperSU
@tobias.waldvogel — Kernel repack script and DRM fix
@zxz0O0 — iovyroot
The whole process divided into the following steps:
Getting your phone recognized by your computer (driver installation).
Backup your DRM keys.
Unlocking a bootloader.
Flashing stock firmware with Flashtool.
Repacking and flashing a kernel.
Rooting with SuperSU.
Restore your DRM keys.
Optional tasks.
The one thing to consider before the flashing of your Xperia phone is the unlocking of the bootloader. There is the official way of doing this provided by Sony. It's easy and straightforward. Check step #3 below.
Before unlocking, one should know the main caveat: once you have unlocked your phone, you have lost your DRM keys. These keys are used to make certain proprietary Sony functions to work, such as X-Reality for Mobile, camera noise suppression and some others. It is possible to backup your keys in beforehand and restore them once the phone is rooted. This will be covered in this guide.
The repack script mentioned before, incorporates a so called DRM fix which effectively emulates lost DRM keys and most of proprietary functions remain in a working state. This fix will suffice for most users, so you probably may want to root your phone straight away, nevermind the keys. I hadn't myself extracted and restored DRM keys ever, since DRM fix works perfectly for me, so you may want to forget about these keys too. Some users are not ready to just erase them, however. The choice is up to you, but if the camera performance is your sole concern, I can confirm that with DRM fix it works perfectly.
After the completion of this guide, your phone contents will be completely erased, so you may want to backup all what is important to you to some external locations. External microSD card will not be erased, so you may copy your stuff to it. If you are on a rooted Lollipop or older Android, you may want to use some specialized tools like Titanium Backup or like. TWRP also have a nice backup features, if you have one already installed.
The guide was tested on Windows 10 Pro 64-bit and Sony Xperia Z5 Premium Dual-SIM E6883 official model for the Russian market. During the course of this guide you will get a specific firmware for your particular market so don't worry, this guide is market-agnostic. It is even model-agnostic. I believe this guide works for most Xperia phones on the market, but I personally tested it just with my Z5 Premium.
Let's go.
1. GETTING YOUR PHONE RECOGNIZED BY YOUR COMPUTER (DRIVER INSTALLATION)
During the course of this guide, your phone will comminicate with your computer in Fastboot and Flashmode connection modes. When connected in these modes, for the phone to be properly recognized by a computer, you have to provide special drivers. Thanks to Flashtool creators, it comes bundled with generic drivers compatible with all recent Windows operating systems, so at first you should install Flashtool. You can get installer from the official website.
Next, you should install Fastboot and Flashmode drivers for your phone.
One caveat here however, these drivers are not from a "recognized Windows developer", that is they are not Windows-certified, so to get them installed on Windows 8/10, you should reboot with the disabled driver signature enforcement. Use Google to know how to perform this.
Once booted in the aforementioned mode (or in a regular mode if you are still on Windows 7), proceed to the actual driver installation. The drivers are packed into the Flashtool\drivers\Flashtool-drivers.exe executable, but it didn't work on my system, perhaps because it is 64-bit (but feel free to try it yourself), so I simply unarchived it with 7-Zip (right-clicked it and chose 7-Zip > Extract to "Flashtool-drivers"). I got a Flashtool-drivers folder, which contained all the drivers from the executable.
Once drivers are unpacked, connect your phone in a Fastboot mode. Recent Sony devices can boot in Fastboot just like this: shutdown the phone, press and hold Volume Up rocker button and connect USB cable to the phone while the other end is connected to a running PC. The phone's LED will turn blue shortly. That's it, you are in a Fastboot mode. Open Device Manager (Win + X, Device Manager) and check if there is some unknown device (with the name S1Fastboot or something like this).
Double-click this unknown device in the Device Manager, click Update Driver..., then Browse my computer for driver software, and choose the Flashtool-drivers folder created earlier with 7-Zip (leave Include subfolders checked). Shortly you will get a red warning dialog window, which inform you that this driver doesn't have a proper signature:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Very scary. Just proceed with the install despite all the red flags, it's safe.
Once Fastboot driver is installed, plug out the USB cable off the phone and connect it in a FlashMode mode. This is done just like for Fastboot, but in this case you should press and hold Volume Down rocker button during the cable plugging in. The LED in this case will be green and not blue. The procedure to install the driver is exactly the same.
After the successful installation, try to reconnect the phone in these modes again couple more times to make sure all devices get properly recognized by Windows. If all seems good, proceed to the next step.
2. BACKUP YOUR DRM KEYS
There is a tool called iovyroot, with which you can backup your DRM keys from an unrooted phone, but at the time of the writing it doesn't support latest firmwares. It does support a lot of older firmwares so it may be useful to not upgrade your phone before checking up this tool.
If you're into this backup DRM thing, go to the original thread, download the latest version and check if it is working for you. For now I just skip this step. Basically, you want to download the zip, connect your phone in USB Debugging mode, run the tabackup.bat script and see the output.
I will not cover DRM keys extraction/restore in details, since I never did it, so I don't want to write about something I haven't myself performed. Please check corresponding threads.
Note that most proprietary Sony features will work even without DRM keys, such as X-Reality for Mobile, camera denoise filter and some others. DRM fix will be covered later in this guide. Some features will not work with DRM fix, Widevine for example. Most users will not even notice these.
3. UNLOCKING A BOOTLOADER
Sony does provide its own guide. It is a plain and simple and — good news! — if you have followed the previous steps, you just got all the prerequisites covered!
4. FLASHING STOCK FIRMWARE WITH FLASHTOOL
The Flashtool was installed on the completion of the first step, so let's start it. If you are on 64-bit Windows, start Flashtool64 (there is a shortcut in the Start menu). It does require administrator privileges.
Once you are in Flashtool, at first you need to obtain the most recent official stock firmware from Sony. Press the "XF" icon (the right-most one in the toolbar) to start XperiFirm. The window will open, choose the phone from the left part of the window (Xperia Z5 Premium (Satsuki)), then choose your particular model (I chose E6883 Dual) and after that choose your market and operator from the right part of the window. I chose 1299-4828 Russia Customized RU. Of course, you don't have to choose exactly this, click on the entries of your own choice. The entry will become highlighted and shortly there will be some info in the last column (Latest Firmware). This definition will be also in the right-most part of the window just under the phone thumbnail, click on it. Not a brilliant design decision, but that's it. Here is a screenshot for your reference:
The new window will pop up, press Download. The stock firmware will be downloaded to your computer and unpacked. Once the download is completed, close all XperiFirm windows to return to the main Flashtool window. Flashtool will begin creation of the .ftf file from the downloaded files which will be used for a (subsequent) flashing. FTF-files are similar to ZIP-files, and may be opened with 7-Zip. I've got E6883_32.2.A.0.305_1299-4828_R4C.ftf after the completion of this procedure. Flashtool places firmwares in the C:\Users\<Your Windows Username>\.flashTool\firmwares.
Now, once the stock firmware is downloaded, packed into .ftf and ready to be installed, let's do this. Disconnect the phone for now, physically extract microSD card (if any) and press the left-most button on the Flashtool's toolbar (the "Lightning" one) and choose Flashmode. The Firmware Selector window will appear with a selected default folder and list of all firmware available for a flashing. I've got a single entry, the firmware I just downloaded. Before actual flashing, you can check some checkboxes from the Wipe section, I usually check all to start clean (all the data on the phone is erased). Once again, just to be safe, extract the microSD card from the phone at this moment. It is not needed for a flashing anyway. Here is how the window looked to me:
After all is set up, press Flash. The flashing process will begin. At first Flashtool will prepare files for a flashing. After a while, window will appear which will ask you to connect the phone in the Flashmode mode. Shutdown the phone, hold the Volume Down button, connect the USB cable. Once Flashtool detects the phone in the Flashmode mode, it will start the actual flashing automatically.
After the completion of the flashing procedure after some minutes, you'll get a stock Sony firmware installed, and now it is perfect time to proceed to the next step. You may leave your phone off at this moment, but if you are curious, start it up and check if the new Android is actually there. Note however that first start after the firmware installation takes a long time.
5. REPACKING AND FLASHING A KERNEL
To get the stock firmware rooted, you need a way to install SuperSU. SuperSU is some tool which enables root access to the Android system. To install SuperSU, you need TWRP. To run TWRP, you need a kernel, which supports both TWRP and your Android version.
You can extract the kernel from .ftf file, prepared by Flashtool earlier, repack it and integrate TWRP (and DRM fix) into it, and finally flash it to your phone back modified. Sound like a complex task but it's definitely achievable.
At first you should extract the actual kernel from the .ftf file. Reminder: it's in the C:\Users\<Your Windows Username>\.flashTool\firmwares folder and may be titled E6883_32.2.A.0.305_1299-4828_R4C.ftf or something like this. Open it as an archive (right-click on a file, 7-Zip > Open archive) and extract kernel.sin. It's your phone's packed kernel.
If it is packed, obviously you need to unpack it. Thankfully the almighty Flashtool can do this. Open Flashtool, navigate to the Tools > Sin Editor, select a kernel.sin you've just extracted and press Extract data. As a result, you'll get a kernel.elf file in the directory where your packed kernel was. As you may have guessed, kernel.elf is an unpacked kernel. It can be modified, repacked and flashed back to the phone. Let's do this.
You will need a Stock kernel repack script from @tobias.waldvogel. Here is the original thread. Grab the script there. I used v5.0 and it worked perfectly for .253 and older.
Once the contents of the zip-file are extracted to some directory, copy the kernel.elf there and summon command prompt in this directory (right-click in the empty space of this folder in File Explorer with the Shift button pressed and choose Open command windows here).
In the command line type the following:
Code:
rootkernel.cmd kernel.elf boot.img
You'll get some questions about adding some features/tools to your kernel, feel free to answer "Yes" (type Y) to all of them. Screenshot for your reference:
If all went smoothly, you'll get a repacked kernel, boot.img in the script folder, supercharged with TWRP and DRM fix, and most importantly, which also supports rooting. Now it is time to flash it to your phone.
Turn off your phone and connect it in a Fastboot mode: hold the Volume Up rocker button and connect USB cable. The LED on the phone will turn blue.
Flashing images in this mode is typically done with a fastboot.exe from the Android SDK. Android SDK weighs many gigabytes but thankfully you don't need to download it. Fortunately Flashtool contains fastboot.exe from the SDK. It's in the Flashtool\x10flasher_lib folder. For the brevity of the following steps, copy the newly generated boot.img to this folder. Shift-right-click in the empty space of this folder window and choose Open command window here entry from the context menu. Windows console will appear.
At first try this command:
Code:
fastboot.exe devices
If all is good, there will be one device in the output of this command, just like this:
If not, perhaps there is some driver issue, so head back to the step #1 and make sure the drivers are installed correctly.
If your device is shown correctly, let's flash some files to the phone. Execute the following command to flash the modified kernel:
Code:
fastboot.exe flash boot boot.img
The proper output of this command will be like this:
If you get any errors, the first and more likely reason is that you still have a locked bootloader. Head to the step #3 to verify its state and unlock it if necessary.
If there were no errors, you now just flashed a custom kernel with TWRP recovery and DRM fix. You're almost done! You may plug out the cable from your phone. If you are attentive to the details, you'll notice that now, once your phone is started, its LED turns amber for 2-3 seconds. This is a special signal for those looking to boot into a recovery (TWRP).
Although @tobias.waldvogel claims his script is able to also integrate SuperSU during the kernel repacking, I didn't managed to get this working, so the SuperSU installation is a separate step in my guide. The next step.
6. ROOTING WITH SUPERSU
Now when you have TWRP in place and Marshmallow installed, let's root it. SuperSU distributed in a TWRP-friendly .zip archives, so you should copy one to your microSD card. I used beta version 2.78 SR1 from here. At the time of your reading, there probably will be some newer versions available, try them instead.
Once SuperSU zip-file is copied to your microSD card, reboot to recovery (TWRP). To do this restart or power up your phone and look at the LED. Once it lights amber, press Volume Up rocker button and you'll get into recovery — TWRP 3.0.
To install SuperSU, press Install, go to the /external_sd and select the .zip (in my case SR1-SuperSU-v2.78-SR1-20160915123031.zip). Swipe right to confirm installation. Once it is installed, press Reboot System button. Phone will reboot twice. Do not interfere with the phone during these multiple reboots, the things are getting done right, so just wait once Android is started. Once it's started, the phone is rooted and functional!
7. RESTORE YOUR DRM KEYS
If you had successfully backed up your DRM keys in step #2, it is now time to restore it back to the device. There is a flash_dk.cmd script shipped with the Root kernel repack script you used in the previous step. flash_dk.cmd can be used to flash the DRM partition back to your phone.
At first prepare the flashable .ftf:
Code:
flash_dk.cmd <ta backup image> dk.ftf
And then flash dk.ftf via Flashtool, just like you flashed the whole firmware in the step #4, but don't wipe anything this time.
8. OPTIONAL STEPS
8.1. Xposed installation
Since Z5P uses Lollipop and later, you should install Xposed APK from here. At the time of writing there is XposedInstaller_3.0_alpha4.apk installer there.
Once APK is installed, grab the latest .zip from the repository, I've got xposed-v86-sdk23-arm64.zip. Install it in a regular TWRP way covered in step #6.
Once all these steps are done, you should have Xposed Installer app in your phone, and if you open it and check Framework section, if everything is alright, there will be text in green, something like "Xposed framework version 86 is active".
Installation of actual Xposed modules can be performed in different ways. For example you may install HideSimIcons module from @tobias.waldvogel if you've got dual-SIM Z5P and you're mad at SIM-card icons in the system tray. Get the APK from the original thread and install it just like you install regular APKs.
8.2. Resolving Voice Search and random volume up/down issues while using regular headphones
See this thread.
8.3. Disable startup notification if there is a newer firmware available
Some people get annoyed by a persistent notification, which is displayed once the new firmware become available (new Android version from Sony). Rooted users cannot just tap it and update over-the-air, because they need to perform a complex rooting procedure in beforehand (covered in this guide). It is possible to disable this notification. You may get these notifications by email anyway.
The easiest and safest way is to use some autorun manager. I used Autorun Manager Pro and disabled all receivers of system apps com.sonymobile.fota.service, fota update service and Software update. Notification vanished after a restart.
You may even freeze or remove these apps via some app manager like Titanium Backup Pro.
THAT'S IT
At this point you have a stock Sony Android enhanced with root privileges. SuperSU app is also installed, so you are ready to use root right away. SuperSU now can be updated in a regular way via Play Store.
P.S. WHEN NEW FIRMWARE IS AVAILABLE
Once the new firmware is released, you may perform the same procedure for it beginning from the step #4, but if it is a minor upgrade, you may want not to wipe anything during Flashtool flashing this time. If it is a major upgrade, e.g. Marshmallow > Nougat, you probably may want to start with a clean system and wipe all.

Hello
THX for this guide
ihave this problem
C:\Android\sdk\platform-tools>fastboot.exe flash boot E6883_MM_ROOTABLE_PERMISSIVE_boot.img
target reported max download size of 536870912 bytes
sending 'boot' (15548 KB)...
OKAY [ 0.353s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.384s
---------- Post added at 12:01 PM ---------- Previous post was at 11:59 AM ----------
I dont have this folder with"Flashtool\x10flasher_lib f"

get2easy said:
Hello
THX for this guide
ihave this problem
C:\Android\sdk\platform-tools>fastboot.exe flash boot E6883_MM_ROOTABLE_PERMISSIVE_boot.img
target reported max download size of 536870912 bytes
sending 'boot' (15548 KB)...
OKAY [ 0.353s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.384s
---------- Post added at 12:01 PM ---------- Previous post was at 11:59 AM ----------
I dont have this folder with"Flashtool\x10flasher_lib f"
Click to expand...
Click to collapse
Hello. This seem like a driver problem to me. Or maybe bootloader is locked. Was fastboot driver installed from the Flashtool package? Do you have your bootloader unlocked?

Hy THX for ure answer.
Drivers are installed, but myBL is LOCKED!! Must i have UL BL??

get2easy said:
Hy THX for ure answer.
Drivers are installed, but myBL is LOCKED!! Must i have UL BL??
Click to expand...
Click to collapse
Sure, I've explicitly stated in the preface section of this guide, that you need to unlock your bootloader to get things done.

OK THX. I dont will loose my performance and the quality from the cam. I wait when is available from the Locked BL.

Hey thank you for posting this it helped a lot! But I don't really know what happened after I flashed the custom kernel and TWRP my phone won't recognize the microSD, not even when booting at recovery. Help.

renezada88 said:
Hey thank you for posting this it helped a lot! But I don't really know what happened after I flashed the custom kernel and TWRP my phone won't recognize the microSD, not even when booting at recovery. Help.
Click to expand...
Click to collapse
I heard about this issue with some large microSD cards of sizes >=128 GB. What is your card?

128gb indeed

renezada88 said:
128gb indeed
Click to expand...
Click to collapse
That's probably a kernel issue. You can try to ask support from its creators, but don't expect anything, because this all is a volunteer work.

get2easy said:
OK THX. I dont will loose my performance and the quality from the cam. I wait when is available from the Locked BL.
Click to expand...
Click to collapse
Just updated the guide, adding the last section (P.S.). Check it out, you may be interested.

Fragmentation said:
That's probably a kernel issue. You can try to ask support from its creators, but don't expect anything, because this all is a volunteer work.
Click to expand...
Click to collapse
Solved it! I needed the E6583 kernel not the E6883. Thanks for everything now root is working with that kernel and it reads the microSD.

Fragmentation said:
Just updated the guide, adding the last section (P.S.). Check it out, you may be interested.
Click to expand...
Click to collapse
sir are all the drm protected features restored by the mod????, and my phone is already MM can I proceed to the 3rd step??

renezada88 said:
Solved it! I needed the E6583 kernel not the E6883. Thanks for everything now root is working with that kernel and it reads the microSD.
Click to expand...
Click to collapse
That's good. I will update the guide and explicitly mention, that it is needed to pay attention to what particular model the phone is. There are different kernel options for different models of Z5P.
1dave said:
sir are all the drm protected features restored by the mod????, and my phone is already MM can I proceed to the 3rd step??
Click to expand...
Click to collapse
I think they are all restored, however I applied the mod just yesterday and checked only photo quality in dark conditions. X-Reality is also seems like works properly, but honestly I didn't tested it before and after the mod. So far so good.
If you already have stock MM, proceed to the stage 3 directly. But of course you should have fastboot drivers properly installed, if not, head to the stage one.

Does anybody have some problem with whatsapp notification when the smartphone is wifi connected?
Sometimes I don't receive any message until I enter the application. This does not happen if I am connected via 3g.
Edit: Sometimes I received delayed whatsapp notification even if the smartphone is connected through 3g.
Inviato dal mio E6853 con Tapatalk 2

We needs this! A light for LB users... Someone can port for Z5? ?
http://forum.xda-developers.com/showthread.php?t=3337357
Enviado de meu E6853 usando Tapatalk

Guto ViP said:
We needs this! A light for LB users... Someone can port for Z5? ?
http://forum.xda-developers.com/showthread.php?t=3337357
Enviado de meu E6853 usando Tapatalk
Click to expand...
Click to collapse
1. There is no dm-verity on Z3 Beta MM but we have it
2. Flashing needs working recovery for locked bootloader (it needs root to install recovery!)

Is it possible to make a flashable.zip of twrp? For a pre-rooted stock rom

Black_Focus_X said:
Is it possible to make a flashable.zip of twrp? For a pre-rooted stock rom
Click to expand...
Click to collapse
That'd be great !

Black_Focus_X said:
Is it possible to make a flashable.zip of twrp? For a pre-rooted stock rom
Click to expand...
Click to collapse
If you are talking about the PRFCreator, then no, currently it doesn't work with Marshmallow for some reason. Check the corresponding thread.