Database Develop

[Root] [Recovery] [Wipe-optional] 4.4.4 KitKat SGP311/312 10.5.1.A.0.283 VMo US, EU1

Xperia Tablet Z 4.4.4 KitKat Rom - Pre-rooted - Includes Recovery
For SGP311 and SGP312 - Wiping is optional​
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **​
Requirements:
Flashtool 0.9.15.0 or higher
Rooted SGP31X (on any other previous Android version) with custom recovery (i.e. XZDualRecovery) installed.
Previous firmwares up to 4.4.2 can be rooted with towelroot.
If your current Rom doesn't have recovery, follow step 10 of this post: http://forum.xda-developers.com/showpost.php?p=53063218&postcount=14 with tablet in USB debugging mode (step 4 of the same post).
This works on locked or unlocked bootloaders and any customization.
This ROM is pre-rooted and comes with recovery. Other than that it is identical to stock rom.
Download links:
SGP311 US_CA_PR https://mega.co.nz/#F!dhMBkRpC!qAsRR7WXJlKwsUwBuv1vig
SGP311 EU1 https://mega.co.nz/#F!p4FzQaqQ!o88OJPX4SyAYOUM3PMb5_A
SGP312 US_CA_PR https://mega.co.nz/#F!El8QnQxC!BlkadNT5FWGF3dLfCbD4mA
Use the link that matches your tablet model. You only need the zip and ftf files. The txt file is just the checksum if you want to verify that your download is error-free.
Instructions:
0- Backup before you start messing with your tablet!
1- Put system.flashable.zip in /sdcard of your tablet.
2- Keep SGP31X_10.5.1.A.0.283_VMo US_CA_PR_NoSystem.ftf on your PC.
3- Disconnect any USB cable that may be attached to your tablet.
4- Reboot to recovery. Preferably to TWRP, but you can make CWM work too.
5- Do not wipe anything.
6- Once in recovery, flash system.flashable.zip.
7- It is important to TURN OFF the tablet after this step.
8- Find and use the Power Off option in the recovery and turn your tablet off. In CWM based PhilZ Touch it is under "Power Options" -> "Power Off". In TWRP it is under "Reboot" -> "Power Off". If you see your tablet rebooting, force it to turn off by pushing the power and volume up keys simultaneously (or however else you can!)
9- Open Flashtool 0.9.15.0 (or higher) and click on the flash icon. Choose flash mode.
10- Navigate to where you have saved SGP31X_10.5.1.A.0.283_VMo US_CA_PR_NoSystem.ftf
11- If you do not want your any of your current data to be wiped uncheck all the items under the "wipe" section. My recommendation however is to wipe.
12- Now flash this ftf with your tablet in flash mode. To put your tablet in flash mode, hold the volume down button when it is off and connect with the USB cable to the PC.
13- Reboot. You are now on rooted 4.4.4.
Credits:
I only put the files together. All the credit should go to XDA's [NUT] and DooMLoRD and many others...

Can I flash this on SGP312?

Kindly request if you could make also a flashable zip with any European rom

FiDra said:
Can I flash this on SGP312?
Click to expand...
Click to collapse
You can and it is not going to break your tablet but there are small differences between the two fimwares. I added a link for SPG312 too.

nick2crete said:
Kindly request if you could make also a flashable zip with any European rom
Click to expand...
Click to collapse
I can try when I have time. PM to me your model and your customization code.

Flashed and works good on SGP312
Thanks!

It worked perfect !
Thank you very much !

I wasn't going to update to 4.4.4 until you offered this solution. Swapping kernels,etc., re-rooting, reinstalling recovery was just more work than it was worth and had the potential to brick the device. Your approach is brilliant! Thank you very much.
However, I am not able to boot into recovery.

Thank you very much for the easy-to-follow instructions.
It worked perfectly on my SGP312. Fully rooted 4.4.4 Kitkat.

Working on 311

najoor said:
OP!!
Click to expand...
Click to collapse
Any chance that you can and will release a 10.5.1.A.0.283 deodex package for 311 / 312 versions / firmwares?

Shanliang- said:
Thank you very much for the easy-to-follow instructions.
It worked perfectly on my SGP312. Fully rooted 4.4.4 Kitkat.
Click to expand...
Click to collapse
How is it performing for you compared to omni rom?

cantenna said:
How is it performing for you compared to omni rom?
Click to expand...
Click to collapse
I wouldn't be able to compare it to Omni as I haven't used it. Actually, I havent used any AOSP 4.4.4 version. But I can say that 4.4.4 stock so far it has worked pretty well.
There's no lag anymore in the options menu.
Battery seems to last as much as it did on 4.4.2, but I'll update this info after some more testing.
Stock launcher feels smoother, although I use Nova Launcher Prime.
I haven't noticed any bugs for now. Perhaps the only thing is a quite short, recurrent distortion in the sound when playing music, but I had that issue in 4.4.2 as well. Haven't found any info on that.
I'll try to report more as I continue using it.

Shanliang- said:
I wouldn't be able to compare it to Omni as I haven't used it. Actually, I havent used any AOSP 4.4.4 version. But I can say that 4.4.4 stock so far it has worked pretty well.
There's no lag anymore in the options menu.
Battery seems to last as much as it did on 4.4.2, but I'll update this info after some more testing.
Stock launcher feels smoother, although I use Nova Launcher Prime.
I haven't noticed any bugs for now. Perhaps the only thing is a quite short, recurrent distortion in the sound when playing music, but I had that issue in 4.4.2 as well. Haven't found any info on that.
I'll try to report more as I continue using it.
Click to expand...
Click to collapse
Tanks man for the feedback. Will you be re-locking the boot loader for the DRM xperia engine, is that possible?
I am really glad that we have this option available to us now

cantenna said:
Tanks man for the feedback. Will you be re-locking the boot loader for the DRM xperia engine, is that possible?
I am really glad that we have this option available to us know
Click to expand...
Click to collapse
yep! it's possble with BackupTA.

I'm surprised to hear there is occasional static sound with a stock ROM from Sony. Can you pleas elaborate as to the problem?
Also, if I follow this tutorial will it automatically relock my boot loader? I'd prefer to keep an unlocked boot loader until I have had opportunity to test drive.
I'm very pleased with my Omnirom ATM. Am curious to try though.
Thanks

Destroyedbeauty said:
Any chance that you can and will release a 10.5.1.A.0.283 deodex package for 311 / 312 versions / firmwares?
Click to expand...
Click to collapse
I've make one for 311/312, you can grab it here :
http://forum.xda-developers.com/xpe...ent/stock-rom-xperia-tablet-z-sgp312-t2876245

Not completely related to the OP, but this is the first time I've upgraded a device that I had encrypted. Following all the steps, my device is now stuck in a bootloop. TWRP is unable to mount the encrypted partition w/ the passphrase I had set.
Anyone else experience this, or better yet have experience with this in general?

tamasrepus said:
Not completely related to the OP, but this is the first time I've upgraded a device that I had encrypted. Following all the steps, my device is now stuck in a bootloop. TWRP is unable to mount the encrypted partition w/ the passphrase I had set.
Anyone else experience this, or better yet have experience with this in general?
Click to expand...
Click to collapse
Sorry, I do not and I have not tried this ROM yet

tamasrepus said:
Not completely related to the OP, but this is the first time I've upgraded a device that I had encrypted. Following all the steps, my device is now stuck in a bootloop. TWRP is unable to mount the encrypted partition w/ the passphrase I had set.
Anyone else experience this, or better yet have experience with this in general?
Click to expand...
Click to collapse
I got my stock 4.4.4 rooted, but unfortunately not with this ROM. Below are my thoughts on what the problem may be.
system.flashable.zip only includes TWRP 2.6.*, which apparently has issues mounting encrypted partitions. These issues are solved in TWRP 2.7; can the OP update system.flashable.zip to include 2.7?
For those who still want to use this ROM, after flashing system.flashable.zip, I'd immediately install dual recovery before rebooting. I've not tested it myself but it's my theory for what will work.

Can't load recovery after flashing Stock image 5.1.1

Hi all-so I decided to flash back to stock since my 32GB Nexus was down to about 14GB from flashing ROMS and such.Everything seems to have gone smoothly however when I try the oem unlock command I am told that the device is already unlocked.I proceeded to root and then I tried to flash TWRP but I get permission denied.
Also,my Play Store just crashed when I try and type in an app to search for.
The question is-how do I know which factory image is right for my device?
There are a number of 5.1.1 images,I selected the one marked for all carriers except T-Mobile.Could I have selected the wrong image to be causing some of these problems?
Or should I just go ahead and jump up to 6.0.1-there is only 1 image for that release.
I would't think the image mattered that much but something is wrong here.
I got the phone last week from the Amazon sale and I activated it no problem on Verizon and flashed several ROMS no issue.
Advice is much appreciated.

I really don't understand why anyone would flash to an old version of a ROM. I appreciate that people have different tastes (e.g. don't like material design) or perceive different characteristics (e.g. better battery life) but in general each new ROM brings advantages, stability, security, improvements, so why stick with an old one when you can have new?
Me, I'd definitely go for a full clean install of MMB29K.
And if you insist on root, be aware of the issues with Marshmallow - you need a different kernel (Elementalx is popular) or alternatively flash TWRP and install Chainfire's SuperSU 2.62. I say 2.62 rather than 2.65 because there are numbers of people reporting that root doesn't work with 2.65, which isn't the case with 2.62, and from personal experience 2.62 works absolutely fine on my 6.0.1 N6.

dahawthorne said:
I really don't understand why anyone would flash to an old version of a ROM. I appreciate that people have different tastes (e.g. don't like material design) or perceive different characteristics (e.g. better battery life) but in general each new ROM brings advantages, stability, security, improvements, so why stick with an old one when you can have new?
Me, I'd definitely go for a full clean install of MMB29K.
And if you insist on root, be aware of the issues with Marshmallow - you need a different kernel (Elementalx is popular) or alternatively flash TWRP and install Chainfire's SuperSU 2.62. I say 2.62 rather than 2.65 because there are numbers of people reporting that root doesn't work with 2.65, which isn't the case with 2.62, and from personal experience 2.62 works absolutely fine on my 6.0.1 N6.
Click to expand...
Click to collapse
Thanks for the detailed response. I was running 5.1 initially because that is what the phone booted with and I like full-featured ROMS like BlissPop. I guess I'll give 6.0.1 a whirl.It just seemed like it was too new to be rock solid. I had as many features on my old S3 running 4.4.2 as I have seen since then if not more actually. I am curious about Google Now On Tap however.
Hopefully this gets me fixed up.Cheers.

chiadrum said:
Hi all-so I decided to flash back to stock since my 32GB Nexus was down to about .......
Click to expand...
Click to collapse
It is possible that the issue is caused because you downgraded the bootloader by flashing 5.1.1.
Flash the complete latest stock 6.0.1 images.

Flashing 6.0.1 now. Both times the CMD window has showed me archive does not contain boot.sig and recovery.sig. I am guessing that is normal?
The 5.1.1 started working fine after an update all but I still couldn't install TWRP fyi.
Let's see how Marshmallow tastes!

The "does not contain boot.sig and recovery.sig" is standard. I have no idea why it continues to appear version after version, but it has no effect on the installation.

chiadrum said:
Flashing 6.0.1 now. Both times the CMD window has showed me archive does not contain boot.sig and recovery.sig.
Click to expand...
Click to collapse
Same on my N6 when flashing 6.0.1. When 6.0.1 is running, you can flash TWRP recovery in fastboot mode.

NLBeev said:
Same on my N6 when flashing 6.0.1. When 6.0.1 is running, you can flash TWRP recovery in fastboot mode.
Click to expand...
Click to collapse
Thanks guys.

chiadrum said:
Thanks guys.
Click to expand...
Click to collapse
Ok more strangeness.pPhone is working fine,no issues.However I am unable to unlock bootloader using the fastboot OEM unlock command.
The message is "Not supported command in current status".
Yes,OEM unlock is allowed in Dev Options.I tried turning that off in case the indicator was faulty and then I couldn't even attempt to unlock,immediate failure.
Tried this several times after reboots as well.
Build MMB29K.
Any ideas?

Would it be too simple an answer to say that it's because the phone is already unlocked? You couldn't install a new ROM with a locked bootloader.
I myself have been a bit surprised by the peremptory & derogatory comments of some of the very senior members in these forums when people ask what seem to be questions with obvious answers, and I'm beginning to see their point...
Still, I also recognise that an "easy" question is one that you know the answer to, and I don't want to put people off asking questions. Being knocked back myself several times hasn't stopped me asking.

That's actually a very good point.Perhaps the image came boitloader unlocked.I'll see if I can flash TWRP and install something. I haven't loaded any roms since the initial flash,I was following protocol to unlock,root and then flash.Appreciate the help.Sometimes obvious seems too easy.

chiadrum said:
That's actually a very good point.Perhaps the image came boitloader unlocked.I'll see if I can flash TWRP and install something. I haven't loaded any roms since the initial flash,I was following protocol to unlock,root and then flash.Appreciate the help.Sometimes obvious seems too easy.
Click to expand...
Click to collapse
Confirmed I am an idiot.Device is unlocked already. Wasn't expecting that.The people way smarter than me who prepared that image took care of it for me.

Not an idiot at all. Like I said, an easy question is one that you know the answer to. Experience counts...
It's not the image that is unlocked - it's the device. Once unlocked, you have to specifically lock it again, but it's neither simple nor a good idea. An unlocked device gives you a far better chance to recover from errors.

(Exynos) N910U downgrade to KitKat

Guys
I have tried to downgrade from stock MM to stock KitKat via odin for various reasons(battery,smoothness etc).
Every time it fails on bootloader step.
If anyone can provide me with kitkat bootloader and kitkat modem for the N910U it would be very helpful.
~~~N910U TGY HongKong based

If you have searched a little you probably already saw it. Unfortunately Samsung permanently blocked users from turning back to older versions of the OS since 5.1.1 Lollipop. There is no way of doing it unfortunately.

There are many a users who claim they are able to revert back from LP to KK and plenty youtubers show it.
I dont claim they are genuine but atleast one out of them would/may be genuine, so whats wrong in giving a try.
Anyways you have the files?

decron04 said:
If you have searched a little you probably already saw it. Unfortunately Samsung permanently blocked users from turning back to older versions of the OS since 5.1.1 Lollipop. There is no way of doing it unfortunately.
Click to expand...
Click to collapse
I did roll back to Kitkat in the end of July on my Note 4, when was the rollback blocked? Everything worked perfectly for me just a couple of months back

galaxyYtester said:
I did roll back to Kitkat in the end of July on my Note 4, when was the rollback blocked? Everything worked perfectly for me just a couple of months back
Click to expand...
Click to collapse
Can you share the method?
As when i try to do so it fails on the bootloader step.
I have also tried flashing the kitkat bootloader alone...still same error.

its_me_Sandy said:
Can you share the method?
As when i try to do so it fails on the bootloader step.
I have also tried flashing the kitkat bootloader alone...still same error.
Click to expand...
Click to collapse
I have the N910F, so it may be different for me (my device also shipped with Kitkat when I bought it), I got the Kitkat ROM from this thread, about 1,5 gigs:
http://forum.xda-developers.com/note-4/general/note-4-n910f-original-firmwares-t3189968
Even though at the time I had a MM or LP bootloader, the zip file only has one md5 file, and installing it worked perfectly with no errors (it probably installed a KK bootloader because, well, it booted after the installation and worked without any problems)
I don't think I can help you because you have an exynos and I have a snapdragon, but I still find the claims of Samsung making installing kitkat impossible VERY improbable, because I did it on the 26th of July this year with no errors
Edit: I digged up this guide I used, not sure if it helps but these are the steps I took and it worked for me: http://www.androidexplained.com/galaxy-note-4-how-to-downgrade-to-android-4-4-4-kitkat/

galaxyYtester said:
I have the N910F, so it may be different for me (my device also shipped with Kitkat when I bought it), I got the Kitkat ROM from this thread, about 1,5 gigs:
http://forum.xda-developers.com/note-4/general/note-4-n910f-original-firmwares-t3189968
Even though at the time I had a MM or LP bootloader, the zip file only has one md5 file, and installing it worked perfectly with no errors (it probably installed a KK bootloader because, well, it booted after the installation and worked without any problems)
I don't think I can help you because you have an exynos and I have a snapdragon, but I still find the claims of Samsung making installing kitkat impossible VERY improbable, because I did it on the 26th of July this year with no errors
Edit: I digged up this guide I used, not sure if it helps but these are the steps I took and it worked for me: http://www.androidexplained.com/galaxy-note-4-how-to-downgrade-to-android-4-4-4-kitkat/
Click to expand...
Click to collapse
Thanks for the detailed one.
i believe the issue is with snapdragon vs exynos processor, as i have followed the same procedure but iam unable to pass the sboot.bin step in odin, it fails there.
not sure on unlocking bootloader as i am rooted, tried few custom roms and kernels too, so i believe it may be unlocked.

did you try a full wipe whit TWRP, data, cache, dalvik, internal, wipe all, then install KK whit ODIN?

MatiasETirimaco said:
did you try a full wipe whit TWRP, data, cache, dalvik, internal, wipe all, then install KK whit ODIN?
Click to expand...
Click to collapse
Except for internal storage, all.

Actually you can't downgrade from stock mm to kk on n910u, your phone bl was locked when you flash 6.0 bl, but you can downgrade to 5.1 LL.
sorry for my bad English.

You are asking for the U model though. Mine is the C model. Sorry for that. However they shouldn't be that different because both have exynos soc. For the C model, you cannot turn back with odin.

decron04 said:
You are asking for the U model though. Mine is the C model. Sorry for that. However they shouldn't be that different because both have exynos soc. For the C model, you cannot turn back with odin.
Click to expand...
Click to collapse
OMG!
Really? I cannot back to KK from MM ? I have the 910c. It's already came with LP...
If I try I can kill my phone or I just will get a error message ?
Thank you!

You can't kill your phone. It just won't allow you to install the KK bootloader. Same goes for all exynos phones. Once you leave KK, there is no turning back. That's why I made sure to get a snapdragon. Sorry to be the bearer of bad news.

[Discussion / Poll] How successful was your unofficial upgrade to Nougat?

Hi! I am starting this discussion / poll in the hope that people will think twice before upgrading (unofficially) to Nougat. So far, what I see is 3 outcomes: 1) Device gets bricked 2) Unofficial Nougat has major bugs and people decide to downgrade back to Marshmallow 3) Upgrade is successful and user is pleased. I think that the latter scenario is actually quite rare and I feel for inexperienced people who brick their device. My question, before you try to upgrade unofficially: is it worth it?

People who brick their device doesn't follow the steps as there are written.
for example t hey flash the b370 version without the additional package and they reply 'bluetooth isnt working'
i encourage people upgrading to nougat because of the new ui, the better battery/ram management and the appearance of drawer
i rollbacked too many times to marshmallow, upgraded to nougat without any problem or brick, just follow the steps and the installation is successful.

StrangerWeather said:
Hi! I am starting this discussion / poll in the hope that people will think twice before upgrading (unofficially) to Nougat. So far, what I see is 3 outcomes: 1) Device gets bricked 2) Unofficial Nougat has major bugs and people decide to downgrade back to Marshmallow 3) Upgrade is successful and user is pleased. I think that the latter scenario is actually quite rare and I feel for inexperienced people who brick their device. My question, before you try to upgrade unofficially: is it worth it?
Click to expand...
Click to collapse
I have two p9 lites,and they are both running on b370,updated trough hicare (1.99gb),and it works perfectly.Battery life,camera,bluetooth,everthing works amazingly compared to older nougat betas.

L-31 P9, Battery life is much better used to get only 4 hours on screen time watching videos now i get 6 with 25% left so easily 7 (my screen is always at 60% brightness) I'm not rooted because i didn't flash it after but i will root soon using a PC (I'm new to rooting (came from IPhone) yet i can easily do it probably because I'm a very techy person) anyway it seems faster my camera and everything works fine i used to get 1.8gb 4am max now i get 2.2 (with no apps running) also split screen works very well and is not laggy at all, one complain i have is the live wallpaper i used for some reason stoped working after i updated (black hole stock love wallpaper) i went into settings to re apply it as it's happened once before on MM but i said there was no wallpapers at all not even still ones, if someone could give me a link to the live wallpaper I'd really appreciate that but other than that no complaints at all it's much better than MM it even has a F.LUX like function built in to reduce blue light levels to help late at night so you're​ not wide awake , the pull down menu has Many and i mean Many more functions not just 5-10 there's probably 20+ and you can have more than 5 at one time, notifications are good and work well, everything seems overly big to me but thats probably because i used to have my phone on a 300 DPI before de-rooting and updating, like i was saying it has almost no drawbacks it's very polished If you install it correctly (one package before the other and it only takes 20 mins max and you data is not deleted i used tarp not the one from this forum but it works the same i got logged out of apps and that's all that's happend when i updated)

simo255 said:
People who brick their device doesn't follow the steps as there are written.
for example t hey flash the b370 version without the additional package and they reply 'bluetooth isnt working'
i encourage people upgrading to nougat because of the new ui, the better battery/ram management and the appearance of drawer
i rollbacked too many times to marshmallow, upgraded to nougat without any problem or brick, just follow the steps and the installation is successful.
Click to expand...
Click to collapse
I agree 100%.
Upgrade to newer version of OS, official or unofficial, is one of the best thing of Android. But people need to be careful with their device, if it's not an OTA update obviously there are some steps to follow.. every device is different and just flashing whatever without attention may cause problem. Reading the steps to follow takes only 1 minute.

I'm on B132, is there a quick way to upgrade to B370? I've tried hi-care app but says no updates
Thanks

simo255 said:
People who brick their device doesn't follow the steps as there are written.
for example t hey flash the b370 version without the additional package and they reply 'bluetooth isnt working'
i encourage people upgrading to nougat because of the new ui, the better battery/ram management and the appearance of drawer
i rollbacked too many times to marshmallow, upgraded to nougat without any problem or brick, just follow the steps and the installation is successful.
Click to expand...
Click to collapse
sirjohnrl said:
I have two p9 lites,and they are both running on b370,updated trough hicare (1.99gb),and it works perfectly.Battery life,camera,bluetooth,everthing works amazingly compared to older nougat betas.
Click to expand...
Click to collapse
bghyt said:
L-31 P9, Battery life is much better used to get only 4 hours on screen time watching videos now i get 6 with 25% left so easily 7 (my screen is always at 60% brightness) I'm not rooted because i didn't flash it after but i will root soon using a PC (I'm new to rooting (came from IPhone) yet i can easily do it probably because I'm a very techy person) anyway it seems faster my camera and everything works fine i used to get 1.8gb 4am max now i get 2.2 (with no apps running) also split screen works very well and is not laggy at all, one complain i have is the live wallpaper i used for some reason stoped working after i updated (black hole stock love wallpaper) i went into settings to re apply it as it's happened once before on MM but i said there was no wallpapers at all not even still ones, if someone could give me a link to the live wallpaper I'd really appreciate that but other than that no complaints at all it's much better than MM it even has a F.LUX like function built in to reduce blue light levels to help late at night so you're​ not wide awake , the pull down menu has Many and i mean Many more functions not just 5-10 there's probably 20+ and you can have more than 5 at one time, notifications are good and work well, everything seems overly big to me but thats probably because i used to have my phone on a 300 DPI before de-rooting and updating, like i was saying it has almost no drawbacks it's very polished If you install it correctly (one package before the other and it only takes 20 mins max and you data is not deleted i used tarp not the one from this forum but it works the same i got logged out of apps and that's all that's happend when i updated)
Click to expand...
Click to collapse
Potato997 said:
I agree 100%.
Upgrade to newer version of OS, official or unofficial, is one of the best thing of Android. But people need to be careful with their device, if it's not an OTA update obviously there are some steps to follow.. every device is different and just flashing whatever without attention may cause problem. Reading the steps to follow takes only 1 minute.
Click to expand...
Click to collapse
I take your points but looking at the answers and questions forum again today, I still think the number of people bricking or downgrading is quite high. I love Nougat too, but I am warning newbies that it might be worth waiting for an official update or if not, concentrating on what you're doing. My penny's worth...

StrangerWeather said:
I take your points but looking at the answers and questions forum again today, I still think the number of people bricking or downgrading is quite high. I love Nougat too, but I am warning newbies that it might be worth waiting for an official update or if not, concentrating on what you're doing. My penny's worth...
Click to expand...
Click to collapse
I updated to B370 but had to downgrade to mm because my camera wasn't working, but overall it was a great experience. Can't wait to get an update where my camera works.
Sent from my HUAWEI VNS-L31 using Tapatalk

I see a lot of people have camera issue on l31 but for l21 everything seems to be OK. I have B370 on my l21 and I don't even think about rolling back to MM. Newest firmware is (at least in my opinion) stable and for now it runs flawlessly

JaccaPL said:
I see a lot of people have camera issue on l31 but for l21 everything seems to be OK. I have B370 on my l21 and I don't even think about rolling back to MM. Newest firmware is (at least in my opinion) stable and for now it runs flawlessly
Click to expand...
Click to collapse
+1

I have not managed to update my phone to Nougat. Everytime i try to use firmware finder or Hi suite , it keeps downloading the 1,24GB package and not the 1,99GB so i end up with a generic a15 Test Key phone

kourkoubas1981 said:
I have not managed to update my phone to Nougat. Everytime i try to use firmware finder or Hi suite , it keeps downloading the 1,24GB package and not the 1,99GB so i end up with a generic a15 Test Key phone
Click to expand...
Click to collapse
Try the TWRP method.

zgomot said:
Try the TWRP method.
Click to expand...
Click to collapse
I think that you must be bootloader unlock and rooted to use TWRP method . Too complicated for me :/
I have L21C900B170 after the fifth or sixth failure to go to 370 .
Whatever I try through Firmware Finder or HiSuite it keeps downloading the 1,24GB file and not the 1,99 Gb upgrade so I always and up with ND90 test key .
Something is blocking it but no one knows what

kourkoubas1981 said:
I think that you must be bootloader unlock and rooted to use TWRP method . Too complicated for me :/
I have L21C900B170 after the fifth or sixth failure to go to 370 .
Whatever I try through Firmware Finder or HiSuite it keeps downloading the 1,24GB file and not the 1,99 Gb upgrade so I always and up with ND90 test key .
Something is blocking it but no one knows what
Click to expand...
Click to collapse
It's really not all that difficult and there are several guides around here. Unlocking the bootloader and rooting MM is pretty much without risks. I'd say go for it.

kourkoubas1981 said:
I think that you must be bootloader unlock and rooted to use TWRP method . Too complicated for me :/
I have L21C900B170 after the fifth or sixth failure to go to 370 .
Whatever I try through Firmware Finder or HiSuite it keeps downloading the 1,24GB file and not the 1,99 Gb upgrade so I always and up with ND90 test key .
Something is blocking it but no one knows what
Click to expand...
Click to collapse
First this: https://forum.xda-developers.com/huawei-p9lite/how-to/root-root-recovery-bootloader-unlock-t3457564
Then this: https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932

Looks like there is a majority of successful upgrades after all!

Well I did an upgrade and although at first I thought I 'borked it' - the build I have is 'NRD90M test-keys'
But I have to say after manually installing google keyboard and getting a few play store updates installed, it feels like an absolute rocket compared to the old EE B132 version

StrangerWeather said:
First this: https://forum.xda-developers.com/huawei-p9lite/how-to/root-root-recovery-bootloader-unlock-t3457564
Then this: https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932
Click to expand...
Click to collapse
OK i managed to do the unlocking of bootloader - root but the first try of upgrading went me again to N90RDM test keys something :/
During the installation of the b370 files throught TWRP i got a message that there is /system

kourkoubas1981 said:
OK i managed to do the unlocking of bootloader - root but the first try of upgrading went me again to N90RDM test keys something :/
During the installation of the b370 files throught TWRP i got a message that there is /system
Click to expand...
Click to collapse
Did you flash both files?

StrangerWeather said:
Did you flash both files?
Click to expand...
Click to collapse
If he made the same mistake as me then he didn't flash the second file, doh!:silly:
i'm thinking of trying to get twrp back on and having another go......

Huawei P9 - Android 6 to 7 Firmware

Hi all,
Ive been a fair while out of flashing ROMs since Note 4 Edge / HTC M7 and have today unlocked bootloader and rooted my P9.
It is currently Australian Vodafone release EVA-L09CC346B160 (Android 6) but I want Nougat.
There is no local carrier updates available but I understand that there is Android 7 available in Australia on 'international' branded handsets.
How can I identify what this firmware is for international Nougat? Can some one assist me. Or can someone advise what would be a suitable equivalent firmware that I can use in place of.
I am unsure how this device goes in flashing ROMs of higher or lower android versions on the current firmware and dont really want to brick it.
Thanks for any tips / suggestions

Umm, just found a thread mentioning L09C636B361 - will check this out, but is there any more recent? And still how does fl;ashing other premade ROMs on 7 go on top of the current Android 6 firmware go?.. Ta

https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
using this guide you can update to the latest nougat release

Thank yuo Xtcislove
I have completed the steps suggested and now have Nougat. Though it is a newer version being .383 which was updated via OTA to .378 and then zip to .383.
Thank you for the help

I'm trying to flash firmware on my P9, now I have EVA-L09C40B181, but it stuck on 5% and HiSuite shows Recovery failed! I tried custom firmware, same problem. What can I do ?

Dfani511 - just follow the instructions in the thread provided by Xtcislove, it works but took me a long time.
I found the steps concerning the update to be added in dload was a little not clear, in the update zip that's downloaded, you need to open it until you get the dload folder, extract that and copy to the SD card.
Throughout my updating, o never ended up on the firmware you have

This N seems to be working fine, nicer looking.
I do have 1 issue, no matter what I do I can not get root to work. I'm on .383, can this one be rooted or not currently? If it can, how do I root .383? I have TWRP 3.1.0.3 as current recovery..
Or, is that ok to flash on my current P9 L09C432B383 ? from this thread - https://forum.xda-developers.com/p9/development/root-pre-rooted-boot-img-p9-nougat-b378-t3574548
The stock and pre-rooted boot.img states its form .378 but would it be ok on .383?
I dont know how to get root on it currently...

twerg said:
This N seems to be working fine, nicer looking.
I do have 1 issue, no matter what I do I can not get root to work. I'm on .383, can this one be rooted or not currently? If it can, how do I root .383? I have TWRP 3.1.0.3 as current recovery..
Or, is that ok to flash on my current P9 L09C432B383 ? from this thread - https://forum.xda-developers.com/p9/development/root-pre-rooted-boot-img-p9-nougat-b378-t3574548
The stock and pre-rooted boot.img states its form .378 but would it be ok on .383?
I dont know how to get root on it currently...
Click to expand...
Click to collapse
This is what I did to root my Huawei P9 on Nougat L09C432B383:
Use the SuperSU-v.27.9-201612051815EMUI5.0.zip file flash via custom recovery and it should root your device no problem.

twerg said:
This N seems to be working fine, nicer looking.
I do have 1 issue, no matter what I do I can not get root to work. I'm on .383, can this one be rooted or not currently? If it can, how do I root .383? I have TWRP 3.1.0.3 as current recovery..
Or, is that ok to flash on my current P9 L09C432B383 ? from this thread - https://forum.xda-developers.com/p9/development/root-pre-rooted-boot-img-p9-nougat-b378-t3574548
The stock and pre-rooted boot.img states its form .378 but would it be ok on .383?
I dont know how to get root on it currently...
Click to expand...
Click to collapse
Use this
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258

xtcislove said:
Use this
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
Click to expand...
Click to collapse
Hey xtcislove - is there a preferred version? 1, 2 or 3 do you recommend? Thanks mate
--------------
EDIT - Nevermind, Xtcislove, your the best man, appreciate your help with your guides etc. I went with option 1 and the handset is now rooted on Nougat. Thanks so much

twerg said:
Hey xtcislove - is there a preferred version? 1, 2 or 3 do you recommend? Thanks mate
--------------
EDIT - Nevermind, Xtcislove, your the best man, appreciate your help with your guides etc. I went with option 1 and the handset is now rooted on Nougat. Thanks so much
Click to expand...
Click to collapse
3 is the version i preffer, you cant freeze apps with v1 but most things should work fine.
btw you can flash v3 over v1.

Ive flashed v3 over 1 and all appears good, root working fine. Thanks again.
Though I have noticed on both v1 and v3 that SuperSU binary needs to be updated, ob both v1 and v3. The phone fails to update both, states unsuccessful and to reboot, which also does not update the binary.
Only other thing I have done is to get BusyBox.
What can be done about the failing binary update? Will it be fine to leave as is, just getting rid of the prompt when it appears, or does it really need to have the update done sometime?