Database Develop

[HOW-TO] How to flash a factory image / return to stock / unlock / root #

I have created this thread to give a step-by-step on how to flash a stock ROM build available on Google's developer site. (For those that are unaware, an unlocked bootloader is needed, and unlocking is part of the instructions below.)
I've also added a section on how to root for those that want it.
Note: There are other methods that are abbreviated and/or faster, but I wanted to spell out each step in the process for the purposes of learning. I'm a big believer in doing things manually before using a "toolkit", much the same way that, in school, we are taught to do math first, before being allowed to use a calculator. See here for some further explanation.
So, without further ado:
How to flash a stock ROM
Step-by-step
Notes:
1) For the n00bs: read the entire post before proceeding;
2) MacOS-specific instructions: a) no drivers needed, and b) replace fastboot in the steps below with ./fastboot-mac
A. Install the drivers
1) Do not install LG drivers or the PDAnet drivers, or any other driver you come across. If you have, and you are SURE they are working properly, fine, leave them. Otherwise uninstall them if you are unsure;
2) Download the drivers from here or from here;
3) Install the drivers. See here on how to install them. Note that the driver has to install twice: once when your device is booted normally (not required for this tutorial) with USB Debugging enabled in Settings, and once when your device is booted in fastboot (i.e., bootloader) mode (which is required for this tutorial). (To enable USB Debugging, you first need to enable Developer options by going to Settings->About phone and tapping 7 times on the build number.) If you are using Windows 8, you will need to do this before installing the drivers.
B. Backup your data
1) Backup all your personal data (e.g., photos, music, etc.) OFF of your device and onto your computer by using whatever method you want that works for you, e.g., MTP, ADB, email, Dropbox, Box.net, whatever.
2) This method will wipe your entire device, including the /sdcard folder, so once you do this, you will not be able to retreive anything that was on your device previously.
3) See here on how to backup your apps and app data if you don't have root.
C. Download the required files to your computer and extract them
1) All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory;
2) Download the attachment from the end of this post and extract the contents to the directory created in step 1. (Latest version for Windows is here). Note: if all you want to do is unlock your bootloader, skip to step 7 in this section (C).
3) Download the version of Android you want from here. Make sure you are using an occam image which is for the Nexus 4. Most old versions are not usually available on that site; however, there is a mirror on this site: Random Phantasmagoria.
4) Download the appropriate version (for your computer) of 7-zip from here and install it.
5) Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
6) Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
7) Reboot your device into bootloader mode (by turning it off, hold volume down, and press and hold power) and plug it into your computer;
8) Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt.
D. Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-mako-makoz10o.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Optional, but read note. Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 2 below.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: either a) fastboot erase cache OR b) fastboot format cache <<== the second option seems to work better for most people. Thanks joostburg.
14) Reboot: fastboot reboot
15) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked. See the notes section at the end of this post for information on re-locking the bootloader.
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset (this will obviously delete all your data & files in /sdcard...).
If you have a 16GB device, and it now shows up as 8GB, reboot into recovery (hold power and press volume up when you are at the screen with the android and the red exclamation mark), and wipe cache. If that still doesn't work, boot back into recovery and do a factory reset (which will obviously delete all your data & files in /sdcard...). Or do this.
E. Optional -- Root
If you want to get root access follow the steps below. (And no, this will not flash a custom recovery, and not, it will not make you "not stock".) Unlocked bootloader required. See steps above.
1) Download (to your computer) the latest version of CWM (from here) or TWRP (from here) for your device;
2) Rename the file to customrecovery.img, and make sure it is in the same directory as your fastboot.exe file;
3) Download (to /sdcard on your device) the latest version of either ChainsDD's Superuser (not currently working), or Chainfire's SuperSU or Koush's Superuser; NOTE: So far, only SuperSU v1.43 and newer currently work properly with JWR66V (i.e., 4.3). I've attached v1.51 below.
4) Restart your device in fastboot mode and plug into computer;
5) Open a command prompt in the directory mentioned above and type: fastboot boot customrecovery.img Note: Only if you are running the z20i bootloader: the command would be: fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img Thanks hwti & el_charlie
6) Wait for it to boot;
7) Navigate the menus the recovery menu on your device and select an option like "update zip from sdcard". Find the zip that you downloaded, and apply it.
8) Reboot. Done.
Notes:
1) Yes, you will receive the OTA update notification (when it is available) for the next update. WHEN you get the update notification, IF you want it to install automatically, you will need to ensure that that you are using the bootloader, radio, boot, radio and recovery images for the .tgz package you downloaded. Otherwise, the update will not install automatically.
2) There has been a lot of uncertainty and questions around stock ROMs and losing/wiping data. You CAN flash a stock ROM WITHOUT losing the data stored in /sdcard (and possibly even all apps and app data, although this depends on which apps you have installed). This can be done by skipping step 10 in part D. However, if your device goes into a boot loop, you will need to boot CWM, and wipe data <-- this will wipe your apps and app data, but not /sdcard.
3) Do NOT re-lock your bootloader after you are finished. The is no need. 2) Having an unlocked bootloader does not affect anything related to the ROM/GoogleWallet/OTAs. Nothing at all. If your bootloader is locked, you CANNOT use fastboot commands. This is pretty much the only thing it affects. If your bootloader is locked, and you need to unlock it, it will wipe everything, including /sdcard. This is the major drawback of re-locking your bootloader. If you do want to lock your bootloader, the command is: fastboot oem lock

How to return to stock if your USB port is broken
I am adding this how-to in case people need it, for return their device to Google, etc.
This is NOT meant to replace going through the steps in post #1. They are there for your learning, and should be used as a primary method of returning your device to stock. However, if your USB port is indeed messed up, then you will not be able to use the instructions in post #1.
Warning: if your USB port is indeed broken, and you complete all the steps below, you will have NO possible way at all to unlock your bootloader, or get root, or install a custom recovery. Period.
1) Ensure that you have root, and a custom recovery (CWM or TWRP) installed;
2) Download segv11's BootUnlocker app from the Play Store, install it and lock your bootloader with it;
3) Download the odexed version of this file (stock JDQ39 ROM) and place it on your device;
4) Download the JDQ39 stock boot image from here and the stock JDQ39 recovery from here.
5) If you want, you can also download the 0.48 radio and the z10o bootloader from here.
6) Reboot into CWM and flash the three files you downloaded in steps 3 and 4, and the file(s) you downloaded in step 5;
5) Turn off your device and reboot into the bootloader;
6) Go to recovery and access the stock recovery menu (i.e., when you see the android with the red triangle, hold power and press vol up) and do a factory reset and then wipe cache.
7) Reboot your device. Do NOT install any OTA updates if they present themselves. Read and follow this post.
8) Done. Now you are fully stock JDQ39 with a locked bootloader.

Reserved.

Awesome! Thanks again efrant!

Ok...
So I consider myself fairly good at this stuff. I've been rooting and doing custom stuff since the N1. I have messed up somewhere...
So initially I used the "1-click" script method (I know) to unlock/root/BB/etc... It worked, but then I decided to go into recovery and wipe everything (inlcluding /format system) in CWR.
That ended up being unable to get passed the Google screen.
I then used your method, which appeared to work...
First time through it got to the "X" and just sat there for 5+ minutes (I unplugged the USB about a minute after it rebooted). I then attempted to restart and nothing.
I tried a second time and instead of it going to the "X" then screen just went black. The device is now recognized as a Nexus 4 under USB devices on my computer, but the screen is off and I can't turn it on. I just unplugged it and now nothing! It can't turn on!
Ummmm... ****! I even rooted the Desire HD back when you had to do a bunch of weird terminal stuff. What happened? Little help?
EDIT - Ummm I managed to get it turned on. I tried in bootloader and eventually it turned on. However it went staright to the Google screen with these weird graphical glitches, now it's on the "X" but I can still see "google" behind it. I'll leave it for a bit and see what happens....
Jesus...

tomedic said:
So initially I used the "1-click" script method (I know) to unlock/root/BB/etc...
Click to expand...
Click to collapse
Yeah, you know I personally don't recommend that
tomedic said:
It worked, but then I decided to go into recovery and wipe everything (inlcluding /format system) in CWR.
That ended up being unable to get passed the Google screen.
Click to expand...
Click to collapse
If you wipe system, there's nothing to boot to, so it certainly won't get past the Google screen.
tomedic said:
I then used your method, which appeared to work...
First time through it got to the "X" and just sat there for 5+ minutes (I unplugged the USB about a minute after it rebooted). I then attempted to restart and nothing.
I tried a second time and instead of it going to the "X" then screen just went black. The device is now recognized as a Nexus 4 under USB devices on my computer, but the screen is off and I can't turn it on. I just unplugged it and now nothing! It can't turn on!
EDIT - Ummm I managed to get it turned on. I tried in bootloader and eventually it turned on. However it went staright to the Google screen with these weird graphical glitches, now it's on the "X" but I can still see "google" behind it. I'll leave it for a bit and see what happens....
Click to expand...
Click to collapse
Boot back into CWM, wipe data, then boot into the bootloader, and re-flash the boot and system images, and erase the cache. Then reboot, and wait a good 5-10 mins for it to start.

efrant said:
Yeah, you know I personally don't recommend that
If you wipe system, there's nothing to boot to, so it certainly won't get past the Google screen.
Boot back into CWM, wipe data, then boot into the bootloader, and re-flash the boot and system images, and erase the cache. Then reboot, and wait a good 5-10 mins for it to start.
Click to expand...
Click to collapse
Ya, I did the format system out of habit because I usually did that when flashing ROM's.
So I'm still staring at the X. The graphically glitches have cleared up, but it's been 10+ minutes. I restarted into bootloader, went to recovery and have the andoid showing with a red exclamation mark!
I turned the phone off. I await your guidance...

tomedic said:
Ya, I did the format system out of habit because I usually did that when flashing ROM's.
So I'm still staring at the X. The graphically glitches have cleared up, but it's been 10+ minutes. I restarted into bootloader, went to recovery and have the andoid showing with a red exclamation mark!
I turned the phone off. I await your guidance...
Click to expand...
Click to collapse
The android with the red exclamation mark is the main screen of the stock recovery. (I'm assuming you flash it if you followed the guide in post 1. You need to re-flash CWM if you want CWM.) As an aside: if you want to see the menu, hold power and press volume up.
Ok, do you have data on your device you want to keep?
If not, do this: reboot into the bootloader and flash the following images as per the instructions in the first post: boot, system and userdata, and then erase the cache partition as per the first post.
If yes, then do this: reboot into the bootloader and flash the following images as per the instructions in the first post: boot and system. Then flash CWM. Then boot into CWM, and wipe data, and wipe cache. Then reboot.

efrant said:
The android with the red exclamation mark is the main screen of the stock recovery. (I'm assuming you flash it if you followed the guide in post 1. You need to re-flash CWM if you want CWM.) As an aside: if you want to see the menu, hold power and press volume up.
Ok, do you have data on your device you want to keep?
If not, do this: reboot into the bootloader and flash the following images as per the instructions in the first post: boot, system and userdata, and then erase the cache partition as per the first post.
If yes, then do this: reboot into the bootloader and flash the following images as per the instructions in the first post: boot and system. Then flash CWM. Then boot into CWM, and wipe data, and wipe cache. Then reboot.
Click to expand...
Click to collapse
I don't want to keep data. I chose that option (but didn't reboot the bootloader after boot.img because you said not too). It just went to the "X". I'll wait...
---------- Post added at 10:05 PM ---------- Previous post was at 09:50 PM ----------
tomedic said:
I don't want to keep data. I chose that option (but didn't reboot the bootloader after boot.img because you said not too). It just went to the "X". I'll wait...
Click to expand...
Click to collapse
Still nothing. Just the "X" animation. No graphical glitches though. It's been 15 minutes.
Any other suggestions? Your stuff works, it's just not booting...

tomedic said:
Still nothing. Just the "X" animation. No graphical glitches though. It's been 15 minutes.
Any other suggestions? Your stuff works, it's just not booting...
Click to expand...
Click to collapse
Strange. All the images flashed fine (without errors) and it won't boot?
Can't think of anything else to try at the moment.
Sent from my Galaxy Nexus using Tapatalk 2

Question, is there a reason to flash stock image at all if we get the phone brand new? Or is this only if we are coming from a custom ROM? Reason I ask, its not the question of build versions like the Galaxy Nexus - yakjux, and then flashing to yakju/takju, etc.
Just verifying that's all.

efrant said:
Strange. All the images flashed fine (without errors) and it won't boot?
Can't think of anything else to try at the moment.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
No errors, I checked the MD5 of the factory image and it's fine. I even re-downloaded it. I did every step as listed in your procedure (even the optional ones). The phone is dead now, it's charging. It spent over 20 minutes on the X. Everything seems to work per your instructions. I don't get it. Could something be corrupted on my phone itself? System/Boot/Recovery images are all dated Jan 1/09, but I assume that's correct (it's from Google after all). Should I try directly flashing CWM recovery instead of stock during the initial process? I dunno...
I will try your method from the beginning again tomorrow.
I assume I'm not bricked if I can still do this stuff. It doesn't bode well if you don't know what's wrong either. I appreciate any further help/suggestions...

evaradar said:
Question, is there a reason to flash stock image at all if we get the phone brand new? Or is this only if we are coming from a custom ROM? Reason I ask, its not the question of build versions like the Galaxy Nexus - yakjux, and then flashing to yakju/takju, etc.
Just verifying that's all.
Click to expand...
Click to collapse
No, no reason to flash a stock image on a brand new phone. Only if you want to go back to stock following a custom ROM.
Sent from my Galaxy Nexus using Tapatalk 2

tomedic said:
No errors, I checked the MD5 of the factory image and it's fine. I even re-downloaded it. I did every step as listed in your procedure (even the optional ones). The phone is dead now, it's charging. It spent over 20 minutes on the X. Everything seems to work per your instructions. I don't get it. Could something be corrupted on my phone itself? System/Boot/Recovery images are all dated Jan 1/09, but I assume that's correct (it's from Google after all). Should I try directly flashing CWM recovery instead of stock during the initial process? I dunno...
I will try your method from the beginning again tomorrow.
I assume I'm not bricked if I can still do this stuff. It doesn't bode well if you don't know what's wrong either. I appreciate any further help/suggestions...
Click to expand...
Click to collapse
It happened to me the same thing... I did everything right just as suggested in every step, but my phone won't get past the X logo... I solved it by going to the stock recovery (unhide the menu by pressing POWER+VOL. UP), wipe data/factory reset, wipe cache partition. Reboot (to me it rebooted automatically after wiping the cache partition) and everything went fine, it took very few time to get past the X logo...
Hope it works for you too.

Maverick1707 said:
It happened to me the same thing... I did everything right just as suggested in every step, but my phone won't get past the X logo... I solved it by going to the stock recovery (unhide the menu by pressing POWER+VOL. UP), wipe data/factory reset, wipe cache partition. Reboot (to me it rebooted automatically after wiping the cache partition) and everything went fine, it took very few time to get past the X logo...
Hope it works for you too.
Click to expand...
Click to collapse
This is indeed strange, as steps D10 and D13 do exactly that: factory reset and wipe cache.
In any case, I will make a note of it in the first post.

efrant said:
No, no reason to flash a stock image on a brand new phone. Only if you want to go back to stock following a custom ROM.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Gotcha. By the way when I rooted the Nexus 4 even before this guide, I know how to do it but I had one slight issue after flashing TWRP's latest recovery. When I tried to enter Recovery mode on the phone I got the Red Triangular Exclamation mark, even after flashing the stock recovery back. To get it working I had to type in fastboot erase cache to get it working then rebooted the bootloader to test it out and it was fine.
Then after installing SuperSu using TWRP, it got stuck on the Nexus logo, even after pressing down on the Power Key for 10 seconds or slightly longer same thing. Then I resolved the problem by clearing cache and dalvik cache using TWRP and it solved the problem.
So just a heads up if anyone runs into this problem.

Maverick1707 said:
It happened to me the same thing... I did everything right just as suggested in every step, but my phone won't get past the X logo... I solved it by going to the stock recovery (unhide the menu by pressing POWER+VOL. UP), wipe data/factory reset, wipe cache partition. Reboot (to me it rebooted automatically after wiping the cache partition) and everything went fine, it took very few time to get past the X logo...
Hope it works for you too.
Click to expand...
Click to collapse
It worked! Thanks man!
And thank you efrant. Now to switch recoveries and get root! :laugh:
---------- Post added at 10:55 AM ---------- Previous post was at 10:40 AM ----------
evaradar said:
Gotcha. By the way when I rooted the Nexus 4 even before this guide, I know how to do it but I had one slight issue after flashing TWRP's latest recovery. When I tried to enter Recovery mode on the phone I got the Red Triangular Exclamation mark, even after flashing the stock recovery back. To get it working I had to type in fastboot erase cache to get it working then rebooted the bootloader to test it out and it was fine.
Then after installing SuperSu using TWRP, it got stuck on the Nexus logo, even after pressing down on the Power Key for 10 seconds or slightly longer same thing. Then I resolved the problem by clearing cache and dalvik cache using TWRP and it solved the problem.
So just a heads up if anyone runs into this problem.
Click to expand...
Click to collapse
Yup, I just rooted and had to do the same thing.
I assume if I wanted to keep the custom recovery I would just have to: fastboot flash recovery customrecovery.img ?
Thanks again all. These little hiccups make it interesting!

evaradar said:
By the way when I rooted the Nexus 4 even before this guide, I know how to do it but I had one slight issue after flashing TWRP's latest recovery. When I tried to enter Recovery mode on the phone I got the Red Triangular Exclamation mark, even after flashing the stock recovery back. To get it working I had to type in fastboot erase cache to get it working then rebooted the bootloader to test it out and it was fine.
Click to expand...
Click to collapse
As I mentioned before, the "Red Triangular Exclamation mark" is the stock recovery. It gets flashed on every re-boot if you updated you stock ROM via an OTA update. More details on this in this thread.
evaradar said:
Then after installing SuperSu using TWRP, it got stuck on the Nexus logo, even after pressing down on the Power Key for 10 seconds or slightly longer same thing. Then I resolved the problem by clearing cache and dalvik cache using TWRP and it solved the problem.
Click to expand...
Click to collapse
Again, interesting. Not sure why this is.
tomedic said:
I assume if I wanted to keep the custom recovery I would just have to: fastboot flash recovery customrecovery.img ?
Click to expand...
Click to collapse
Correct.

efrant said:
As I mentioned before, the "Red Triangular Exclamation mark" is the stock recovery. It gets flashed on every re-boot if you updated you stock ROM via an OTA update. More details on this in this thread.
Again, interesting. Not sure why this is.
Correct.
Click to expand...
Click to collapse
I'm assuming that like the GN we need to rename the recovery-from-boot.p file if we want our custom recovery to survive a reboot?
EDIT- never mind I just looked through your 101 thread and answered my own question- thanks!!

Thank you for making this thread over here. Glad to have you as a moderator. I hope every noob reads all of your threads.
Sent from my BAKED N7

[Q] Stuck in bootloop after attempted upgrade

I just recently got my TF701T. I unlocked the boot loader with the Asus unlock tool and then attempted to upgrade to version 11.4.1.17 so that I could install Cromi-X 7 on it. I placed the file UL-K00C-US-11.4.1.17-user.zip on the root of the tablet and rebooted. Once the OS booted back up I was alerted that an update file had been found and I clicked it to begin installing.
The tablet rebooted and appeared to be upgrading but now all I see is a robot on his back with a red exclamation point. After a while the tablet will reboot and again show the Asus splash screen and then the upgrading robot then immediately go to the robot on its back.
I can get to fastboot by pressing power and volume down. I see "the device is unlocked" at the top of the Asus splash screen then I see a screen with the following. Android macallan-user bootloader (1.00 e) released by "US_epad-10.14.1.47-20131022" Choosing RCK, Android or Wipe Data do nothing to help the situation.
I thought I had found a solution in this thread http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1 but the link for drgravy's recovery.img is not working.
I would appreciate any help recovering this tablet. Thank you.

jggrnaut said:
I just recently got my TF701T. I unlocked the boot loader with the Asus unlock tool and then attempted to upgrade to version 11.4.1.17 so that I could install Cromi-X 7 on it. I placed the file UL-K00C-US-11.4.1.17-user.zip on the root of the tablet and rebooted. Once the OS booted back up I was alerted that an update file had been found and I clicked it to begin installing.
The tablet rebooted and appeared to be upgrading but now all I see is a robot on his back with a red exclamation point. After a while the tablet will reboot and again show the Asus splash screen and then the upgrading robot then immediately go to the robot on its back.
I can get to fastboot by pressing power and volume down. I see "the device is unlocked" at the top of the Asus splash screen then I see a screen with the following. Android macallan-user bootloader (1.00 e) released by "US_epad-10.14.1.47-20131022" Choosing RCK, Android or Wipe Data do nothing to help the situation.
I thought I had found a solution in this thread http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1 but the link for drgravy's recovery.img is not working.
I would appreciate any help recovering this tablet. Thank you.
Click to expand...
Click to collapse
Do you have the Asus drivers and adb/fastboot installed on your PC?
If you have fastboot access, it would be as easy as:
Download CWM 6.0.4.7 from here http://droidbasement.com/db-blog/?p=3207
I know it says you have to be on 10.26.1.18 for this, but since you will use it only to flash the latest bootloader, you should be fine.
Put the recovery.img into your fastboot folder and flash it (if you need help here, let me know).
Then fastboot reboot
Your tablet should boot up normally now
Part 2:
Head here http://forum.xda-developers.com/transformer-tf701/development/rom-nov-24-t2951032 and grab the 11.4.1.27 bootloader/CWM 6.0.5.1 package
Flash it in your existing CWM
Reboot
Part 3:
Boot to recovery
Make a nandroid of your stock rom
Go back to home
Wipe data, cache and Dalvik
Flash the rom (which you have loaded onto your microSD)
All done.
Don't forget to delete the (probably corrupted) firmware file
EDIT: BTW, when you reboot to system from CWM you will always get the question if you want to fix root. Choose NO - it's a bug....

berndblb said:
Do you have the Asus drivers and adb/fastboot installed on your PC?
If you have fastboot access, it would be as easy as:
Download CWM 6.0.4.7 from here http://droidbasement.com/db-blog/?p=3207
I know it says you have to be on 10.26.1.18 for this, but since you will use it only to flash the latest bootloader, you should be fine.
Put the recovery.img into your fastboot folder and flash it (if you need help here, let me know).
Then fastboot reboot
Your tablet should boot up normally now
Part 2:
Head here http://forum.xda-developers.com/transformer-tf701/development/rom-nov-24-t2951032 and grab the 11.4.1.27 bootloader/CWM 6.0.5.1 package
Flash it in your existing CWM
Reboot
Part 3:
Boot to recovery
Make a nandroid of your stock rom
Go back to home
Wipe data, cache and Dalvik
Flash the rom (which you have loaded onto your microSD)
All done.
Don't forget to delete the (probably corrupted) firmware file
EDIT: BTW, when you reboot to system from CWM you will always get the question if you want to fix root. Choose NO - it's a bug....
Click to expand...
Click to collapse
Thanks for the reply. I do have the drivers and adb/fastboot setup on PC.
After I could not find anywhere to download the version of CWM that was supposed to be for my firmware version I was afraid to proceed.
When I get home I will try the steps you have listed above and report back how it turned out.
One question, In part one after I flash recovery CWM 6.0.4.7 do I reboot to recovery or let the tablet reboot to the OS?

jggrnaut said:
Thanks for the reply. I do have the drivers and adb/fastboot setup on PC.
After I could not find anywhere to download the version of CWM that was supposed to be for my firmware version I was afraid to proceed.
When I get home I will try the steps you have listed above and report back how it turned out.
One question, In part one after I flash recovery CWM 6.0.4.7 do I reboot to recovery or let the tablet reboot to the OS?
Click to expand...
Click to collapse
Shouldn't matter. When you flash recovery or bootloader, you flash it to the staging partition. The actual installation happens during the next boot - you'll see a brief blue progress bar under the Asus logo.
Booting a recovery for the first time I always reboot to system after the flash, then power down and enter the new recovery from the bootloader. Probably booting straight to recovery or bootloader is ok, but I have not tested it.

berndblb said:
Shouldn't matter. When you flash recovery or bootloader, you flash it to the staging partition. The actual installation happens during the next boot - you'll see a brief blue progress bar under the Asus logo.
Booting a recovery for the first time I always reboot to system after the flash, then power down and enter the new recovery from the bootloader. Probably booting straight to recovery or bootloader is ok, but I have not tested it.
Click to expand...
Click to collapse
Well it has gotten worse and I think I have lost fastboot now. I downloaded the CWM from part 1 above and flashed it in fastboot. I typed fastboot reboot and now I am stuck in a bootloop still. It says "The device is unlocked" at top of Asus splash screen for about 15 seconds, screen turns black and the goes back to Asus splash screen.
I tried holding power and volume key to get back to fastboot but no luck. Any ideas?

Wow! You are really having some bad luck there!!
First the failed firmware update and now this.... Please post the commands you used to flash CWM.
I have no explanantion for this since you did not even boot into CWM.......
Unless..... the bad firmware flash left a command behind calling the stock recovery to do something (which in your case did not work anyway since it just looped) and now the bootloader tries to execute the command which is not "understood" by CWM. But that still does not explain why you cannot boot into the BL anymore......
Can you turn it off by long pressing power? Try every which way to get into fastboot. Without it there is not much you can do I'm afraid.
Try the restart pin hole (I believe it's on the left side of the tablet near the top) in conjunction with Volume Down, try leaving it alone for a while, try timing the button press somewhat differently - anything to get you into the BL again...
I feel very sorry for you, mate!!

Thanks for helping even if it didnt turn out great.
I typed fastboot flash recovery recovery.img after I had downloaded 6.0.4.5 and put it in my fastboot folder. I got confirmation that it transferred successfully.
Then fastboot reboot The tablet rebooted but still would not boot into OS. It still boot looped but did not show the dead android icon anymore.
I got back into fastboot and selected RCK but it would not boot into recovery. Finally I got back into fastboot and selected wipe data and that is what got me to current situation. Now the only thing I get is when I long press power and volume up my PC picks up an unknown device that says apx.

jggrnaut said:
Thanks for helping even if it didnt turn out great.
I typed fastboot flash recovery recovery.img after I had downloaded 6.0.4.5 and put it in my fastboot folder. I got confirmation that it transferred successfully.
Then fastboot reboot The tablet rebooted but still would not boot into OS. It still boot looped but did not show the dead android icon anymore.
I got back into fastboot and selected RCK but it would not boot into recovery. Finally I got back into fastboot and selected wipe data and that is what got me to current situation. Now the only thing I get is when I long press power and volume up my PC picks up an unknown device that says apx.
Click to expand...
Click to collapse
I don't know what happened before - maybe you were doomed since the bad firmware flash - but that last step sealed the coffin.
Using Wipe Data from the bootloader with a custom recovery installed is asking for trouble. Never ever do that.... Sorry, it's a brick. [emoji24]

Bricked my myphone uno using Android One Toolkit

After having issues with the low 4GB memory of the myphone uno, i decided to try rooting the phone using some online instructions using Android One Toolkit. I ended up bricking it. Now when i turn on the phone, its stuck with the 4 animated circles.
I am a noob when it comes to android phones, but i do know how to install windows xp, vista, 7. I have used online instructions to clone my pc HD using clonezilla. I believe that if someone were kind enough to give step by step instructions on what files to download(like the original "OS" / "image") and where to get them. And how to use the software, i can get my myphone uno back to working order. So please anyone out there, can you help?

t-rayms said:
After having issues with the low 4GB memory of the myphone uno, i decided to try rooting the phone using some online instructions using Android One Toolkit. I ended up bricking it. Now when i turn on the phone, its stuck with the 4 animated circles.
I am a noob when it comes to android phones, but i do know how to install windows xp, vista, 7. I have used online instructions to clone my pc HD using clonezilla. I believe that if someone were kind enough to give step by step instructions on what files to download(like the original "OS" / "image") and where to get them. And how to use the software, i can get my myphone uno back to working order. So please anyone out there, can you help?
Click to expand...
Click to collapse
If you could tell us more clearly about what did you do actually and which instructions did you followed?

DNA_Uncut said:
If you could tell us more clearly about what did you do actually and which instructions did you followed?
Click to expand...
Click to collapse
i followed(or tried to) the instructions from the site of androidmtk with topic
"how to root android one devices easily"
sorry but system will not let me paste the actual link.
Process involved the use of android one toolkit.
and now my phone no longer boots. Stuck with those 4 animated circles. I have to remove the battery to get out of that screen. But no matter what i did, isn't there a way to just install android? Like installing windows on a blank hard drive? Start from scratch? Loss of data is not a factor

t-rayms said:
i followed(or tried to) the instructions from the site of androidmtk with topic
"how to root android one devices easily"
sorry but system will not let me paste the actual link.
Process involved the use of android one toolkit.
and now my phone no longer boots. Stuck with those 4 animated circles. I have to remove the battery to get out of that screen. But no matter what i did, isn't there a way to just install android? Like installing windows on a blank hard drive? Start from scratch? Loss of data is not a factor
Click to expand...
Click to collapse
Just follow the thread
http://forum.xda-developers.com/dream-uno/development/stock-rom-spice-dream-uno-mi498-t2915844
Download ROM (from the same thread)
http://forum.xda-developers.com/showpost.php?p=61588267&postcount=23
You should get back to stock kitkat (if you follow the instructions as explained). Once you get back your phone to working. Install ota updates you receive that will get you to stock 6.01

t-rayms said:
After having issues with the low 4GB memory of the myphone uno, i decided to try rooting the phone using some online instructions using Android One Toolkit. I ended up bricking it. Now when i turn on the phone, its stuck with the 4 animated circles.
I am a noob when it comes to android phones, but i do know how to install windows xp, vista, 7. I have used online instructions to clone my pc HD using clonezilla. I believe that if someone were kind enough to give step by step instructions on what files to download(like the original "OS" / "image") and where to get them. And how to use the software, i can get my myphone uno back to working order. So please anyone out there, can you help?
Click to expand...
Click to collapse
You don't need to go back on kitkat as DNA uncut says .....your device is running on which recovery ??

devil anand said:
You don't need to go back on kitkat as DNA uncut says .....your device is running on which recovery ??
Click to expand...
Click to collapse
im sorry but i dont know what "recovery" is. The phone is also no longer turning on so i cant get that info. But im ok with trying kitkat and if the flashing of the ROM works, at least ill have a working phone. And go from there and experiment some more to get the most out of the device.

When your phone is switched off. ....press the power and volume+ button at the same time and hold it till you see a menu .....then navigate to recovery as the menu instructs ....then tell me what you see
---------- Post added at 03:58 AM ---------- Previous post was at 03:49 AM ----------
t-rayms said:
im sorry but i dont know what "recovery" is. The phone is also no longer turning on so i cant get that info. But im ok with trying kitkat and if the flashing of the ROM works, at least ill have a working phone. And go from there and experiment some more to get the most out of the device.
Click to expand...
Click to collapse
When your phone is switched off. ....press the power and volume+ button at the same time and hold it till you see a menu .....then navigate to recovery as the menu instructs ....then tell me what you see

DNA_Uncut said:
Just follow the thread
http://forum.xda-developers.com/dream-uno/development/stock-rom-spice-dream-uno-mi498-t2915844
Download ROM (from the same thread)
http://forum.xda-developers.com/showpost.php?p=61588267&postcount=23
You should get back to stock kitkat (if you follow the instructions as explained). Once you get back your phone to working. Install ota updates you receive that will get you to stock 6.01
Click to expand...
Click to collapse
i installed the Android CDC Driver. DL the SP Flash Tool and the custom ROM. Rebooted the PC. Ran the SP Flash Tool. The final stage where i click on DL and connect my phone, nothing happens. The scrolling progress bar at the bottom of the flash tool doesnt start. With or w/o batteries in the phone. What do i do next?

devil anand said:
When your phone is switched off. ....press the power and volume+ button at the same time and hold it till you see a menu .....then navigate to recovery as the menu instructs ....then tell me what you see
---------- Post added at 03:58 AM ---------- Previous post was at 03:49 AM ----------
When your phone is switched off. ....press the power and volume+ button at the same time and hold it till you see a menu .....then navigate to recovery as the menu instructs ....then tell me what you see
Click to expand...
Click to collapse
when i selected the recovery option, the next screen is a picture of the android robot lying face up. With its body panel door open with red triangle with black exclamation markm, "No command" prompt

t-rayms said:
when i selected the recovery option, the next screen is a picture of the android robot lying face up. With its body panel door open with red triangle with black exclamation markm, "No command" prompt
Click to expand...
Click to collapse
First download a custom kernel zip (recommend thunderzap 5.1)
Then SuperSU 2.54 zip
Move this to files to your phones sd card
And again go to the menu which I told you during recovery (power and volume+ buttons at same time holding) then navigate to fastboot and enter ....you will se fastboot mode in the last line of the menu .
Now connect your phone to pc and open toolkit and press root.
You will see philz recovery loaded on your phone (philz recovery written on the top).
Then tap on wipe option and then factory reset and confirm it.
After factory resetting tap on install zip and select thunderzap zip
After successful installation of thunderzap select SuperSU zip and after installation of super su ...reboot now .......it will take 10 -15 mins......
Link - kernel- http://www.thunderzap.in/downloads/
SuperSU - https://download.chainfire.eu/741/SuperSU?_e_pi_=7,PAGE_ID10,5223979215

devil anand said:
First download a custom kernel zip (recommend thunderzap 5.1)
Then SuperSU 2.54 zip
Move this to files to your phones sd card
And again go to the menu which I told you during recovery (power and volume+ buttons at same time holding) then navigate to fastboot and enter ....you will se fastboot mode in the last line of the menu .
Now connect your phone to pc and open toolkit and press root.
You will see philz recovery loaded on your phone (philz recovery written on the top).
Then tap on wipe option and then factory reset and confirm it.
After factory resetting tap on install zip and select thunderzap zip
After successful installation of thunderzap select SuperSU zip and after installation of super su ...reboot now .......it will take 10 -15 mins......
Link - kernel- http://www.thunderzap.in/downloads/
SuperSU - https://download.chainfire.eu/741/SuperSU?_e_pi_=7,PAGE_ID10,5223979215
Click to expand...
Click to collapse
great. thanks. it worked. still cant believe it. But thank you very very very much.

t-rayms said:
great. thanks. it worked. still cant believe it. But thank you very very very much.
Click to expand...
Click to collapse
Just hit thanks!!
I went to Android mtk website ...then I knew where was the problem.
Note : SuperSU zip is used to root a phone via custom recovery (twrp,philzz) ...but in marshmallow you can't root your phone just by installing SuperSU zip ....you need to install a custom *kernel* first ....remember next time??

devil anand said:
Just hit thanks!!
I went to Android mtk website ...then I knew where was the problem.
Note : SuperSU zip is used to root a phone via custom recovery (twrp,philzz) ...but in marshmallow you can't root your phone just by installing SuperSU zip ....you need to install a custom *kernel* first ....remember next time
Click to expand...
Click to collapse
i take it that this step Then tap on wipe option and then factory reset and confirm it. fixed the bricking of the phone
and these steps After factory resetting tap on install zip and select thunderzap zip
After successful installation of thunderzap select SuperSU zip and after installation of super su ...reboot now .......it will take 10 -15 mins......
rooted the phone right?
One other thing is, whenever theres a system update, during the rebooting it does an error and i have to remove battery to restart the phone. Does rooting the phone cause updates not to work?

t-rayms said:
i take it that this step Then tap on wipe option and then factory reset and confirm it. fixed the bricking of the phone
and these steps After factory resetting tap on install zip and select thunderzap zip
After successful installation of thunderzap select SuperSU zip and after installation of super su ...reboot now .......it will take 10 -15 mins......
rooted the phone right?
One other thing is, whenever theres a system update, during the rebooting it does an error and i have to remove battery to restart the phone. Does rooting the phone cause updates not to work?
Click to expand...
Click to collapse
You took a bit ....if you have rebooted your phone after just factory reset .....you may have got bootloop again.....(stuck on boot animation).
About your second problem ....
When the error happens in between these steps of installation .......you tap on reboot and install and your phone goes to recovery and after successful installation your reboots .
What's the error ??
Yeah rooting your phone changes system which causes problem while installation of the original update...??

devil anand said:
You took a bit ....if you have rebooted your phone after just factory reset .....you may have got bootloop again.....(stuck on boot animation).
About your second problem ....
When the error happens in between these steps of installation .......you tap on reboot and install and your phone goes to recovery and after successful installation your reboots .
What's the error ??
Yeah rooting your phone changes system which causes problem while installation of the original update...
Click to expand...
Click to collapse
i get the prompt about an update ready for install, i click on it, it does the prompt to reboot so i choose to reboot. During the rebooting it tries to install updates, then the robot image comes up with the word "error". Stuck there until battery is removed. Afterwards the phone will turn back on.

t-rayms said:
i get the prompt about an update ready for install, i click on it, it does the prompt to reboot so i choose to reboot. During the rebooting it tries to install updates, then the robot image comes up with the word "error". Stuck there until battery is removed. Afterwards the phone will turn back on.
Click to expand...
Click to collapse
Just unroot your phone and try updating again !!!??

devil anand said:
First download a custom kernel zip (recommend thunderzap 5.1)
Then SuperSU 2.54 zip
Move this to files to your phones sd card
And again go to the menu which I told you during recovery (power and volume+ buttons at same time holding) then navigate to fastboot and enter ....you will se fastboot mode in the last line of the menu .
Now connect your phone to pc and open toolkit and press root.
You will see philz recovery loaded on your phone (philz recovery written on the top).
Then tap on wipe option and then factory reset and confirm it.
After factory resetting tap on install zip and select thunderzap zip
After successful installation of thunderzap select SuperSU zip and after installation of super su ...reboot now .......it will take 10 -15 mins......
Click to expand...
Click to collapse
It worked for me too, but now I can`t update SuperSU.
Update from OS failed, from TWRP gives bootloop.
I`m on CM13 SNAPSHOT.
... also front camera cant take picture, but preview works ok.

Johnny_16 said:
It worked for me too, but now I can`t update SuperSU.
Update from OS failed, from TWRP gives bootloop.
I`m on CM13 SNAPSHOT.
... also front camera cant take picture, but preview works ok.
Click to expand...
Click to collapse
What's the need of updating SuperSU ..,...
Use Google camera ....
Sent from my A1 using XDA-Developers mobile app

t-rayms said:
i get the prompt about an update ready for install, i click on it, it does the prompt to reboot so i choose to reboot. During the rebooting it tries to install updates, then the robot image comes up with the word "error". Stuck there until battery is removed. Afterwards the phone will turn back on.
Click to expand...
Click to collapse
You've root? And which update do you wanna install on your phone!?
Just tell me what's your build number.. I'll help ya out.

HELP
My cousins Myphone Uno is not turning on when pressing the power button, but if I put in a charge the screen turns on after a few minutes showing the battery but I don't know if it is charging. after a minute the display will go out and the screen flashes a once or twice then off and screen turns on and display the battery it will be on a loop, I can still get to boot option when screen flashes starts,
it shows:
[Recovery Mode]
[Fastboot Mode]
[Normal Boot]
[Normal Boot +ftrace]
[Normal slub debug off]
but when I select any options or not to ,the phone will turn off. Can you help me find a way to make this phone work again? thank you in advance!
PS: If I connect it in my PC it wasn't detected and the the loop will go on and on.
Usb debugging mode is also turned off

Failed downgrade from Nougat to MM bricked my EVA-L09

Recently I tried out the Nougat preview on my EVA-L09C636. It was ok but seeing as there was a problem with fonts and I'd lost root access, I began thinking about going back to MM.
To prepare for downgrade I tried using srktool to bring TWRP back (and I think this is my big mistake as srktool uses a TWRP made for MM, not N, is that right?). After I tried to restore TWRP I noticed "not recognised" errors when I connected my phone to PC again.
System recovery using hajuuk's Firmware Updater and HiSuite looked like it would complete but near the end of the process (the restoring system part) HiSuite aborted itself saying my device wasn't supported. This has left my P9 is in an unusable state where the only thing I can access is fastboot. Also I can't turn off my phone - holding down power simply makes it reboot then get stuck at the "Your device ... can't be trusted / Your device is booting now" screen.
Reading around a bit I attempted to unbrick it without any luck:
1. downloaded EVA-L09C636B152 update.zip from http://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586 and installed Snoop05's 15 seconds ADB Installer.
2. extracted images from update.zip using Huawei Update Extractor and did
Code:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cust cust.img
then tried rebooting holding volume up + power several times (but never got past untrusted device boot screen).
3. extracted contents of update.zip to folder 'dload' on a blank sd card, trying to force update several times by rebooting and holding down power + volume up + volume down (still never get past the screen saying my device is booting).
At this point I'd be happy to get anything happening on my phone - Marshmallow, Nougat or even some other ROM so I can use my device again.
Any ideas? I'm on EVA-L09 C636.

i2ectcf said:
Recently I tried out the Nougat preview on my EVA-L09C636. It was ok but seeing as there was a problem with fonts and I'd lost root access, I began thinking about going back to MM.
To prepare for downgrade I tried using srktool to bring TWRP back (and I think this is my big mistake as srktool uses a TWRP made for MM, not N, is that right?). After I tried to restore TWRP I noticed "not recognised" errors when I connected my phone to PC again.
System recovery using hajuuk's Firmware Updater and HiSuite looked like it would complete but near the end of the process (the restoring system part) HiSuite aborted itself saying my device wasn't supported. This has left my P9 is in an unusable state where the only thing I can access is fastboot. Also I can't turn off my phone - holding down power simply makes it reboot then get stuck at the "Your device ... can't be trusted / Your device is booting now" screen.
Reading around a bit I attempted to unbrick it without any luck:
1. downloaded EVA-L09C636B152 update.zip from http://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586 and installed Snoop05's 15 seconds ADB Installer.
2. extracted images from update.zip using Huawei Update Extractor and did then tried rebooting holding volume up + power several times (but never got past untrusted device boot screen).
3. extracted contents of update.zip to folder 'dload' on a blank sd card, trying to force update several times by rebooting and holding down power + volume up + volume down (still never get past the screen saying my device is booting).
At this point I'd be happy to get anything happening on my phone - Marshmallow, Nougat or even some other ROM so I can use my device again.
Any ideas? I'm on EVA-L09 C636.
Click to expand...
Click to collapse
did you wiped data, cache, dalvik?

snapdesign said:
did you wiped data, cache, dalvik?
Click to expand...
Click to collapse
Hi! I'm not sure how to wipe data, cache or dalvik, because when I upgraded to Nougat this apparently removed TWRP.
Also I'm wondering if trying to use srktool to reinstall TWRP for 6.0 might have corrupted my 7.0 phone?
Is there any way to wipe data, cache, and/or dalvik now? Or are there other things I could try to unbrick?

Although my phone was in a pretty bizarre state - it would get hot and sit on the booting now screen until battery died - I was able to use DC Phoenix to make it boot up again. At that point it had no themes and only KitKat-esque icons. A reset and upgrade later icons and themes work and I'm back on stock Marshmallow. Here's an outline:
1. Google "Huawei Bricked phone repair guide with DC Phoenix", go to the first result and look at the instructions (I can't post URLs yet).
I used Method 1. But note! The newer versions of DC Phoenix are missing a feature that the instructions make clear you have to use. To get the original version used in their guide, you have to download the latest version of DC Phoenix, open it on your PC, then click "Enter Support Area" which logs you in to a download section. Find "DC Unlocker Softwares", "DC_Phoenix", then download DC_Phoenix_v14.rar and run that instead. Whether it's Method 1 or 2 make sure you complete it - i.e. the fastboot flash step AND a step they call "flashing in upgrade mode."
(Also note that for DC Phoenix you want to feed it the oldest version of firmware available for your phone, in my case b152. This is because themes and icons won't be fixed until it receives the next version of firmware as an update.)
2. Once I did the fastboot and upgrade flash, I did a system reset from the Settings app trying to get themes and current icons again. (This didn't work but doesn't do any harm or might have helped somehow further down the line).
3. I used hajuuk's Firmware Updater and HiSuite to upgrade to the next version of firmware available (in my case b168).
3. All fine and your phone is back to stock - icons look nice again and local themes are back. To get the original icons layout, go to Recents, hold down on the Trash Icon, show system apps, and Clear Data for Huawei Home.

i2ectcf said:
Although my phone was in a pretty bizarre state - it would get hot and sit on the booting now screen until battery died - I was able to use DC Phoenix to make it boot up again. At that point it had no themes and only KitKat-esque icons. A reset and upgrade later icons and themes work and I'm back on stock Marshmallow.
Click to expand...
Click to collapse
Thanks for sharing! You saved me!

HUAWEI P9 EVA L19 Nougat: /Data partition corrupted or damaged

Hello,
I am previously a Sony Xperia user. Rooting is not my first time. However, since i got a Hauwei P9 (EVA L19), I messed up with the rooting process and thereby acquired such issues with the phone.
History:
I accidentally used a SRK tool by some thai developer for huawei. I didn't realize it was only for MM versions. I followed the instructions there and managed to unlock my bootloader. However, during the installation of the TWRP, it replied some error so I read some more articles and found the right version for it which is the 3.1.0. So, I was able to install TWRP using fastboot. After that, since i can't get my phone rooted, i tried several ways (which so badly i couldn't remember, sorry) but still it's not successful. I then decided to flash back the stock ROM for B386 (latest nougat OTA) via fastboot. I flashed the BOOT, SYSTEM and RECOVERY. So far it went well, but the time it booted, i realized my stock apps like Camera, themes, Alarm clock were missing! so i panicked and tried to reboot many times. I also wiped cache/dalvik but to no avail. Then i decided to wipe everything including the system and boot. There it messaged from the TWRP "No OS" something. so again, I flashed B386. It flashed but again my stock apps were missing. the same result when flashed with B361 and B381. It seems like my settings remain intact and unchanged no matter how i flash the stock firmwares.
the next time i flashed a firmware, it says "data partition is seriously damaged... restore to factory setting..." i did reset it but still it doesnt make any change. So now i realize that my security settings are fcked up too. I cant open the developer options to enable usb debugging. I cant open the security tab under advanced setttings. Theyre all just gonna exit after tapping on them.
Question:
Would it be possible that my data partition is corrupted? because no matter how i install firmware, it always goes back to its "original setting" (no stock camera, themes etc etc)
is there a way to recreate the data partition? wipe all of its contents so i can rewrite from stock firmware? it seems like the system wont let me write over it.
Present status:
So far, the phone is okay with calls, txts and games (i need to download apps from playstore as i cant install backups since i cannot enable "install from unknown sources" in security setting. I can access the cam via messenger or any app. wifi and bluetooth still works.
but i really really want to get back the stock apps like the camera.
please help. im really running our of idea here. any comment would be highly appreciated.
Thanks!

Go to this thread:
https://www.google.it/amp/s/forum.x...i-p9-eva-l19-android-7-0-nougat-t3532649/amp/
Download both files and flash them either via TWRP or dload.
Dload:
1. Put your sd card in your computer and create a folder in the root of the sd card called dload
2.unzip the archive. You will find some files
3. Copy the file called UPDATE.APP into the dload folder
4. Put the sdcard back in your phone and turn it of.
5. Hold volume up, volume down and power at the same time. The phone should boot and install the firmware.
6. Repeate the steps with the other zip file
TWRP
1. Copy both zip files on your phone
2. Turn of your phone
3. Hold volume up and power. You should boot into TWRP
4. Press install and select your file, when finished install the other one to
5. The device should boot
If this didn't work try to rollback to marshmallow via dload and then update to nougat over OTA.

_Frostplexx_ said:
Go to this thread:
https://www.google.it/amp/s/forum.x...i-p9-eva-l19-android-7-0-nougat-t3532649/amp/
Download both files and flash them either via TWRP or dload.
Dload:
1. Put your sd card in your computer and create a folder in the root of the sd card called dload
2.unzip the archive. You will find some files
3. Copy the file called UPDATE.APP into the dload folder
4. Put the sdcard back in your phone and turn it of.
5. Hold volume up, volume down and power at the same time. The phone should boot and install the firmware.
6. Repeate the steps with the other zip file
TWRP
1. Copy both zip files on your phone
2. Turn of your phone
3. Hold volume up and power. You should boot into TWRP
4. Press install and select your file, when finished install the other one to
5. The device should boot
If this didn't work try to rollback to marshmallow via dload and then update to nougat over OTA.
Click to expand...
Click to collapse
I tried this but it didnt work. do you have any other solution?

The dload / 3 Button method doesn't work any more. Here is what worked for me:
For anyone pretty much, who has ****ed up his Huawei P9:
I got to the state where I could only enter Fastboot mode (Press vol- and connect power cable). When I tried to start the phone / go into recovery it would only display the "Your device has been unlocked and can't be trusted" Message. My mistake was to relock the bootloader in an attempt to get the recovery to work.
I looked for hours for the answer, here is what worked for me:
follow this tutorial (the "update firmware" part)
German
English
But with real precision, every step.
If you have a european unbranded L09 you should be fine using the firmware you can find on this site:
https://thedroidguru.com/download-install-huawei-p9-b394-nougat-update-europe/
if not you gotta find the full firmware (3 files!!) yourself - good luck!
If you only want to go back to stock you should be fine afterwards.
If you want to install twrp for root/custom rom/... follow these steps after installing twrp with the tool:
Upon flashing TWRP, FIRST THING YOU MUST DO is rebooting to TWRP. If you don't do that, stock Recovery will ovewrite TWRP.
Find instructions in the TWRP threads how to enforce immediate booting to TWRP, upon you flashed it:
-Type on the PC: fastboot reboot -but don't press Enter yet.
-Press and keep pressing Vol+ and Power buttons together on the phone
-Press Enter on the PC and then immediately unplug USB cabel.
-When phone shows Booting, release Power but keep pressing Vol+. button
Hope this helps, I don't take responsability for anything, happy flashing!

Nooby Paul said:
The dload / 3 Button method doesn't work any more. Here is what worked for me:
For anyone pretty much, who has ****ed up his Huawei P9:
I got to the state where I could only enter Fastboot mode (Press vol- and connect power cable). When I tried to start the phone / go into recovery it would only display the "Your device has been unlocked and can't be trusted" Message. My mistake was to relock the bootloader in an attempt to get the recovery to work.
I looked for hours for the answer, here is what worked for me:
follow this tutorial (the "update firmware" part)
German
English
But with real precision, every step.
If you have a european unbranded L09 you should be fine using the firmware you can find on this site:
https://thedroidguru.com/download-install-huawei-p9-b394-nougat-update-europe/
if not you gotta find the full firmware (3 files!!) yourself - good luck!
If you only want to go back to stock you should be fine afterwards.
If you want to install twrp for root/custom rom/... follow these steps after installing twrp with the tool:
Upon flashing TWRP, FIRST THING YOU MUST DO is rebooting to TWRP. If you don't do that, stock Recovery will ovewrite TWRP.
Find instructions in the TWRP threads how to enforce immediate booting to TWRP, upon you flashed it:
-Type on the PC: fastboot reboot -but don't press Enter yet.
-Press and keep pressing Vol+ and Power buttons together on the phone
-Press Enter on the PC and then immediately unplug USB cabel.
-When phone shows Booting, release Power but keep pressing Vol+. button
Hope this helps, I don't take responsability for anything, happy flashing!
Click to expand...
Click to collapse
DLOAD does not work for half a year, ie since Huawei stopped releasing FullOTA-MF-PV builds (it worked only for them)
Here, on XDA there are two proven guides for recovering Nougat (not just for EU c432 but for all custs, not only for P9 L09 but also for L19, L29) - just search for them: HWOTA7, HuRUpdater
PS: You have crossposted the same to several threads