This Guide is to update from B131 MM to B360 or B380 nougat. There's a new recovery with data encryption.
Realized today without issues in L09 EU, for L04 usa version only need the correct recovery stock versions , the other files are the same.
your bootloader must be unlocked first, and oem bootloader enabled....and in all the process not auto-blocked the bootloader never. Put all the flashable zips in SD.
Always put depuration usb on in dev options when connected to pc .
B360 EU update zip
B360 EU update hw
Download and install the android sdk tools, execute then sdk manager and only select and install android sdk tools,plattform tools and usb driver
Hisuite (for drivers)
I used Huawei_Multi-Tool_by_Team_MT_v6.zip for all the process
If you have problems with the driver, you can install in multi tool - option number 0
1 - Unrooted from B131 with the option in supersu to unroot and the option to restore stock boot
2 - With multitool I copied the recovery b131 I have extracted from update.app to ...Huawei_Multi-Tool\USER\RECOVERY and then options 3(recovery)-1(My bootloader is unlocked)-1(Install users Recovery from folder /USER/RECOVERY/) and then space bar to confirm. Flashed and rebooted automatically
3 - Go to system update and apply the ota b360, updated to nougat correctly and then the B380...
4 - I copied now the twrp for nougat to ...\Huawei_Multi-Tool\USER\RECOVERY and then options 3-1-1 and then space bar to confirm. Flashed and rebooted automatically
5 - without enter pin code or nothing in mobile, in multitool options 3-1-2(Reload device to Recovery) , this reboot and enters in twrp, manually you allow modifications-change storage to sd card and flashed supersu and rebooted( now without errors)
6- open supersu and set it to expert mode
7 - installed jrummy busybox in system\xbin, busybox
8 - tested last version of adaway, tested busybox with lucky patcher.
9 - now, i have all that I want and seems to works with all the apps that require root,
UPDATE TO B380 IF YOU DONE THE OLD TUTORIAL TO 360
sadly, the old method i removed now gives problems to update to b380, the solution I found was revert to mm with intermediate update.app in dload(disconnect the usb cable when updating), then the full update.app b131, (make sure dev option to unlock bootloader is on) unlock bootloader, update to 360 and then to 380. Install latest twrp and root with supersu for emui 5. Then, busybox from jrummy works
deadko said:
Realized today without issues in L09 EU
your bootloader must be unlocked first, and in all the process not auto-blocked the bootloader never. Put all the flashable zips in SD.
Always put depuration usb on and select archives when connected to pc . Pack to root
I used Huawei_Multi-Tool_by_Team_MT_v6.zip for all the process
1 - Unrooted with the option in supersu to unroot and the option to restore stock boot (i don't know if if was necessary but no problems)
2 - With multitool I copied the recovery b131 I have extracted from update.app to ...Huawei_Multi-Tool\USER\RECOVERY and then options 3-1-1 and then space bar to confirm. Flashed and rebooted automatically
3 - Go to system update and apply the ota b360, updated to nougat correctly
4 - I copied now the twrp nougat to ...\Huawei_Multi-Tool\USER\RECOVERY and then options 3-1-1 and then space bar to confirm. Flashed and rebooted automatically
5 - without enter pin code or nothing in mobile, in multitool options 4-1-1-selected supersu 2.79 emui 5.0-1-1 , this reboot and enters in twrp, manually you allow modifications-change storage to sd card and flashed supersu and rebooted( there are errors but the process end succefully.)
6- installed supersu from play store and set to expert mode
7 - with app quick reboot, rebooted to twrp and flashed busybox, reboot and update binaries in busybox
8 - tested last version of adaway, set nova for default launcher in options
9 - now, i have all that I want and seems to work all the apps that require root,
In dev options i see hability oem unlock greyed but activated (not possible to change it, someone knows why?) and system updates automatic activated that I disabled
Click to expand...
Click to collapse
It's nice to see a step by step but I have a couple of questions. The errors you got when flashing TWRP with the tool.. did they have to do with encryption? Meaning, do you have access to the data partition? Can you confirm that AdAway actually works? Every other post I see is that AdAway successfully installs, but fails to block any ads (my guess is because the hosts file did not get updated because it's not a full root you get when flashing supersu. Also, I've yet to see where you can relock the bootloader without fully flashing back to a full stock rom, which I have not seen a full copy of B360 available or even a process to do this yet.
Thanks!
joesee said:
It's nice to see a step by step but I have a couple of questions. The errors you got when flashing TWRP with the tool.. did they have to do with encryption? Meaning, do you have access to the data partition? Can you confirm that AdAway actually works? Every other post I see is that AdAway successfully installs, but fails to block any ads (my guess is because the hosts file did not get updated because it's not a full root you get when flashing supersu. Also, I've yet to see where you can relock the bootloader without fully flashing back to a full stock rom, which I have not seen a full copy of B360 available or even a process to do this yet.
Thanks!
Click to expand...
Click to collapse
I tested adaway now with blackmarket, you know if no adaway, when you close it, it popups an ad, now it closes without ad, like in b131 rooted, so it's fully working last version.
Only access to SD card, no data partition
I don't know how to relock, because I'm not interested in relock, someone knows and post it here?
I have updated the manual because of new great recovery , hope you understand it, if not,respond here
deadko said:
I have updated the manual because of new great recovery , hope you understand it, if not,respond here
Click to expand...
Click to collapse
You said "sadly, the old method i removed now gives problems to update to b380, the solution I found was revert to mm with intermediate update.app in dload(disconnect the usb cable when updating), then the full update.app b131, (make sure dev option to unlock bootloader is on) unlock bootloader, update to 360 and then to 380. Install latest twrp and root with supersu for emui 5. Then, busybox from jrummy works"
When I see the manual..... Did that mean I have to be on b131 with "intermediate update.app in dload(disconnect the usb cable when updating), then the full update.app b131" and only I have to unlock the bootloader and I will be able to update to b360 with dload method on my sdcard and then to b389, which is the official at this moment? After this I can install twrp and root if I want?
dewadi said:
You said "sadly, the old method i removed now gives problems to update to b380, the solution I found was revert to mm with intermediate update.app in dload(disconnect the usb cable when updating), then the full update.app b131, (make sure dev option to unlock bootloader is on) unlock bootloader, update to 360 and then to 380. Install latest twrp and root with supersu for emui 5. Then, busybox from jrummy works"
When I see the manual..... Did that mean I have to be on b131 with "intermediate update.app in dload(disconnect the usb cable when updating), then the full update.app b131" and only I have to unlock the bootloader and I will be able to update to b360 with dload method on my sdcard and then to b389, which is the official at this moment? After this I can install twrp and root if I want?
Click to expand...
Click to collapse
I think this manual is obsolete, because the new updates go to B402 and here b360 and b380. You must tell me in what situation are you, what version do you have now?
deadko said:
I think this manual is obsolete, because the new updates go to B402 and here b360 and b380. You must tell me in what situation are you, what version do you have now?
Click to expand...
Click to collapse
I bought the phone with b389 but I revert back to b131 using the official firmware and rollback package from the Honor website using the dload method, just to had the impression to use it under MM . Now I would like to update to Nougat, like was before. My phone is not rooted but I am considering to unlock the boot loader and root it.
dewadi said:
I bought the phone with b389 but I revert back to b131 using the official firmware and rollback package from the Honor website using the dload method, just to had the impression to use it under MM . Now I would like to update to Nougat, like was before. My phone is not rooted but I am considering to unlock the boot loader and root it.
Click to expand...
Click to collapse
the MM version was very good and the mobile works very well, but now in b402 the nougat works very well too. I encourage you to put the last version.
I remember when you put the intermediate version, then you must put in sd the full rom update.app b131 and start the honor touching 3 buttons and updates automatically.Then you have MM.
deadko said:
the MM version was very good and the mobile works very well, but now in b402 the nougat works very well too. I encourage you to put the last version.
I remember when you put the intermediate version, then you must put in sd the full rom update.app b131 and start the honor touching 3 buttons and updates automatically.Then you have MM.
Click to expand...
Click to collapse
How to update from b131 to b402? If I download manually the b402 could I installed in the same way, using the dload folder on the sdcard like install MM ore they have to be some firmware between them? My phone is not rooted and the bootloader is locked.
When I see your manual I understand I can update to b360 using the dload folder on the sd card but before that I have to unlocked the bootloader. It's that correct?
dewadi said:
How to update from b131 to b402? If I download manually the b402 could I installed in the same way, using the dload folder on the sdcard like install MM ore they have to be some firmware between them? My phone is not rooted and the bootloader is locked.
When I see your manual I understand I can update to b360 using the dload folder on the sd card but before that I have to unlocked the bootloader. It's that correct?
Click to expand...
Click to collapse
the bootloader can be unlocked at any time, i recommend to use the update through mobile to last official, and then to unlock bootloader and root. for example if you decide to stay in MM and unlock bootloader, when you decide to go to nougat, the bootloader locks itself another time when passed the b394 , from b394 to the last b402 do not lock it.
deadko said:
the bootloader can be unlocked at any time, i recommend to use the update through mobile to last official, and then to unlock bootloader and root. for example if you decide to stay in MM and unlock bootloader, when you decide to go to nougat, the bootloader locks itself another time when passed the b394 , from b394 to the last b402 do not lock it.
Click to expand...
Click to collapse
Could I update to b402 offline, like I revert back to MM with the firmware and rollpack package for the b131?
dewadi said:
Could I update to b402 offline, like I revert back to MM with the firmware and rollpack package for the b131?
Click to expand...
Click to collapse
I recommend online, because possibly, to update correctly must need to be incremental updates throught updates online to last.
Recently picked up a P8 from someone who had one lying around.
I'm trying to root it but after installing TWRP i keep entering a bootloop which apparentely is counteracted by holding some combination of buttons.
currently im on B222 and i also tried installing marshmallow (stock) from SD which also makes me enter a bootloop and when my phone finally turns on its like it forgot it had a command to update.....
I'm a little lost on what to do now, i tried googling and all that but i cant find similar issues.
You cannot install Marshmallow with a B222 build, so you'll first need to downgrade to a B200 build.
If you are on a C432 (European) build, you can download European B200 directly from Huawei via this link & install it: http://download-c.huawei.com/download/downloadCenter?downloadId=68483&version=238533
Once B200 is present, if you check via Settings > Update you'll most likely be offered a Marshmallow OTA update. If not immediately or within a few days, then update manually as you tried before, again using a C432 build only.
With Marshmallow installed, you can follow one of these guides to install TWRP & root:
[Guide][Huawei P8] TWRP + Root Systemless Marshmallow Installation (GRA-L09&GRA-UL00)
Rooting and Unroot Huawei P8 [6.0] [FOR All EMUI4.0.1] all [GRA-Types]
First off
I have a vnsL31 p9lite on mm c432b160
Unlocked bootloader and frp
Can flash TWRP, can root, can unroot
Can access fastboot
I have b160 firmware and rollback package
I have b336 update and data hw eu zips
I have the Huawei update extractor
I have Revolution recovery
I have Meticulous recovery
I have EliteKernel
I have the OEM unlock code
I have c432oeminfo zip and oeminfo with a custom.bin
I have hisuite
Phone is working fine
My issue is that I can't upgrade the phone or downgrade the phone to any software at all.
Before my issue I was on b160 and upgraded successfully to b336 and used it for a long time. I then upgraded to b370 using firmware finder successfully. I then wanted to root nougat so I could uninstall some Google apps and tried the EliteKernel method, which didn't work and started going into bootloops. I then tried to downgrade to mm using the rollback package and then flashing b160 which worked successfully.
Then I tried upgrading back to nougat with firmware finder which didn't work, I had missing apps so I did the rollback method again which landed me on nrd90m testkeys. I followed a guide I can't remember to get back to c432 which didn't work either my phone then got bricked. It was stuck on bootloop and vibrated twice each time it tried to go past the Huawei logo. I couldn't access anything but fastboot. I then followed another guide to extract cust,boot,system and recovery images from the b160 update zip and flash those through ADB which worked and have my phone in working order.
My phone now shows build number as vnsl31c432b160 but model number as hi6250. I can't update the phone to nougat or reflash mm to get back to completely stock. Dload 3 buttons method doesn't work for b160 or b336, it goes to 7% then System incompatible error. Flashing the update zips through TWRP doesn't work either, I always get a zip error although it says done but nothing happens.
I want to get back to stock nougat or may even try a custom ROM as long as it is extremely stable. I am willing to root and unroot and do whatever need be to upgrade again. I think I have all the files necessary and should be able to follow any advice given
You must try flashing a OEMInfo for your model and correspondent firmware.. If you want, you can send me a PM with the details of your phone and I'll try to give you the exact files you need to use..
The model is VNS L31, it's dual sim and I'm currently on marshmallow b160 region c432, I bought it carrier unlocked. But the model number shows hi6250 now. I'll try flashing the oeminfo you give me and hopefully it works
This is what I mean, but it is a VNS L31
Have a LeEco Pro 3 (US Version) running 5.8.19s official stock version, bootloader unlocked and official TWRP installed. But my system update fails everytime eventhough it shows there is new update 5.8.21s but phone boots to recovery in TWRP and asking for password. I have tried several times but its the same thing over and over again. Am I doing something wrong? Is there some different file that I must flash?
How can I stock update with rooted and TWRP?
Chattersking said:
Have a LeEco Pro 3 (US Version) running 5.8.19s official stock version, bootloader unlocked and official TWRP installed. But my system update fails everytime eventhough it shows there is new update 5.8.21s but phone boots to recovery in TWRP and asking for password. I have tried several times but its the same thing over and over again. Am I doing something wrong? Is there some different file that I must flash?
How can I stock update with rooted and TWRP?
Click to expand...
Click to collapse
You need the official recovery for update to work
Chattersking said:
Have a LeEco Pro 3 (US Version) running 5.8.19s official stock version, bootloader unlocked and official TWRP installed. But my system update fails everytime eventhough it shows there is new update 5.8.21s but phone boots to recovery in TWRP and asking for password. I have tried several times but its the same thing over and over again. Am I doing something wrong? Is there some different file that I must flash?
How can I stock update with rooted and TWRP?
Click to expand...
Click to collapse
You can update to 21s on the US version (727) from TWRP with a few modifications to the updater-script file (see the below post/thread):
https://forum.xda-developers.com/showpost.php?p=72815409&postcount=48
This will remove root but it keeps TWRP so you should be able to just reinstall root through TWRP.
Thank you. Will it keep my data and apps intact or will it erase them? I don't want to lose all my important data and setup.
Chattersking said:
Thank you. Will it keep my data and apps intact or will it erase them? I don't want to lose all my important data and setup.
Click to expand...
Click to collapse
I did a wipe before updating but it should work without wiping as the update zip file is the official OTA with only a modified updater-script. Do a backup from TWRP before you try it and if anything goes wrong you can revert to that backup.
Running into the same issue..did your script and that worked. Thanks for that.
Flash 19s using TWRP and needed a somewhat official way to get to 21s. Use the script of d/l the official 21s update and pushed the modified zip to sdcard to get flashed in TWRP. So hopefully this update, updated whatever it needs to update and maybe it will fix my other issue... why when I flash Lineage base ROMs they show my battery only at 50%
I followed the above instructions and replaced with the updated script however TWRP is giving me Error 7 and a quick google search is saying it is due to problem with updated script. How do you guys fix this?
I really try to do stuff on my own without having to make other people repeat themselves a million times but this process is just so complicated and confusing that it's giving me a headache.
My goal: Be able to boot up LineageOS 16.
Code:
httpsforum.xda-developers.comnote-4snapdragon-devrom-lineageos-16-0-t3900807
It says it requires MM firmware and TWRP 3.2 or higher.
I have the retail 900V Note 4.
So far I have managed to downgrade to 5.1.1 and unlock the bootloader. (It says MODE: Developer)
From there I was able to install TWRP 3.0.2.
But now what?
Right now I have a phone that won't boot because there is no OS on it.
1. I can't get Odin to flash any other TWRP besides the 3.0.2 version. Odin just freezes halfway through and never completes. I'm assuming this might be because I'm not on an unlocked MM build yet. Currently still on LP.
2. I'm unsure how to get root back once I upgrade to a MM build. (I only have access to WiFi atm and this guide says it will disable it.)
Code:
https://forum.xda-developers.com/note-4-verizon/development/howto-bootloader-unlock-upgrade-to-t3398144
Any help is greatly appreciated.
I'm no expert so some of the things I'll suggest may not work.
As a first thought have you tried installing Lineage from TWRP 3.0.2
I'd suggest
1. downloading the OEM MM ROM from Sammobile and install that first so at least you have an OS to start with.
2. after setting it up install the official TWRP App update to the latest version of TWRP
3. ensure SuperSU is on the internal drive although I've not had problems installing it from a MicroSD and install it from TWRP Recovery. You should now have a rooted phone on the latest version of TWRP
4. put the Lineage ROM on the internal drive although again I've not had problems installing from a MicroSD (although it does take longer) and after 'Wiping' the system (it should tell you what steps are required from the Lineage guidance) install it.
5. After setup you will probably have to install SuperSU again or Magisk assuming there's no trace of SuperSU left on the system.
Hopefully someone will jump in and comment if I've missed something obvious or got it all wrong. Although I've rooted all 3 of my SM-N910Fs and SM-N910C at least once and installed various ROMs I don't consider myself particularly knowledgable. So far I've not bricked any of my phones or Tablets.
I really appreciate the reply.
Currently I am trying to flash 5.1.1 stock onto the phone and Odin just freezes about 25% into system.img.ext4
I have tried a dozen times.
I believe what makes my phone so difficult to flash is the stock bootloader is locked.