Related
Guide to unlock Huawei Ascend Mate bootloader
I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE. DO IT AT YOUR OWN RISK.EVERYTHING WRITTEN IN THIS DOCUMENT WAS TESTED ON MY PHONE.
After playing with my Mate I found a way to unlock the locked bootloader. If your bootloader is unlocked you can flash custom kernel , recovery to your phone.
The files used to unlock the bootloader is from P6 KitKat firmware. These two files are for efi and fastboot partition. Flashing only these partitions can avoid problems with mismatching modem firmware. The process was tested on official B221 firmware , but should work with any firmware. Reflashing a stock firmware(as I know there are only firmwares for Mate only with locked bootloader) with dload will relock the bootloader.
Unlocking process need proper adb and fastboot drivers installed. I use this driver :Huawei handset drivers for windows
Guide in pdf format
If your adb and fastboot drivers are correct you can start unlocking the bootloader.
If you want to unlock the bootloader and install Twrp recovery use this package :Bootloader unlock with TWRP install
Bootloader unlock with TWRP install mirror
This way powering on your phone with volume up button hold TWRP recovery comes up instead of stock 3e recovery. If you want to use the dload method to install a stock rom you have to restore the stock recovery.
Stock B221 fastboot flashable recovery
Stock B221 fastboot flashable recovery mirror
The other package just unlocks the bootloader .Bootloader unlock.
Bootloader unlock mirror.
Turn on USB debugging on your phone (settings->developer settings)
Start the package.
File extraction starts.
Command prompt window should appear.
Your phone restarts in bootloader mode.
Efi partition is flashed.
Fastboot partition is flashed.
Your phone restarts in bootloader mode.
Your bootloader state is displayed. (should say bootloader unlocked)
Your phone restart in normal mode.
This is what the packages do :
.\adb wait-for-device
.\adb reboot bootloader
.\fastboot flash efi efi.img
.\fastboot flash fastboot fastboot.img
.\fastboot reboot-bootloader
timeout 2
.\fastboot oem get-bootinfo
timeout 10
If it says your bootloader is still locked you can try the following:
adb reboot bootloader
fastboot oem unlock UUUUUUUUUUUUUUUU
If you want to restore stock rom and recovery here are the packages.
Recovery restore package for B221
Recovery restore package for B907
These packages restores the original efi and fastboot partition and then restores the stock recovery. These packages do the opposite as the unlock bootloader , however my phone stayed unlocked. Also this package solves the problem when the stock recovery stuck at the begining when trying to flash a stock rom using dload method.
WARNING:If you plan to flash a rom not made for Mate , always check that it does not overwrite other partitions then boot, system, data, cust. If the install package reflash the modem do not install it as it can hard brick your device.
For updated versions of permanent TWRP recovery check my thread here
Thanks to surdu_petru for the initial device tree to compile twrp.
joe.stone said:
Guide to unlock Huawei Ascend Mate bootloader
I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE. DO IT AT YOUR OWN RISK.EVERYTHING WRITTEN IN THIS DOCUMENT WAS TESTED ON MY PHONE.
After playing with my Mate I found a way to unlock the locked bootloader. If your bootloader is unlocked you can flash custom kernel , recovery to your phone.
The files used to unlock the bootloader is from P6 KitKat firmware. These two files are for efi and fastboot partition. Flashing only these partitions can avoid problems with mismatching modem firmware. The process was tested on official B221 firmware , but should work with any firmware. Reflashing a stock firmware(as I know there are only firmwares for Mate only with locked bootloader) with dload will relock the bootloader.
Unlocking process need proper adb and fastboot drivers installed. I use this driver :Huawei handset drivers for windows
Guide in pdf format
If your adb and fastboot drivers are correct you can start unlocking the bootloader.
If you want to unlock the bootloader and install Twrp recovery use this package :Bootloader unlock with TWRP install
This way powering on your phone with volume up button hold TWRP recovery comes up instead of stock 3e recovery. If you want to use the dload method to install a stock rom you have to restore the stock recovery.
Stock B221 fastboot flashable recovery
The other package just unlocks the bootloader .Bootloader unlock.
Turn on USB debugging on your phone (settings->developer settings)
Start the package.
File extraction starts.
Command prompt window should appear.
Your phone restarts in bootloader mode.
Efi partition is flashed.
Fastboot partition is flashed.
Your phone restarts in bootloader mode.
Your bootloader state is displayed. (should say bootloader unlocked)
Your phone restart in normal mode.
This is what the packages do :
.\adb wait-for-device
.\adb reboot bootloader
.\fastboot flash efi efi.img
.\fastboot flash fastboot fastboot.img
.\fastboot reboot-bootloader
timeout 2
.\fastboot oem get-bootinfo
timeout 10
Thanks to surdu_petru for the initial device tree to compile twrp.
Click to expand...
Click to collapse
Thanks joe....atlast bootloader unlocked..
One more thing i installed Fly UI OS from p6 and replaced with stock HAM boot.img....OS is not booting properly getting lots of FC's...
Does CM10.1 require different kernel or do we need to change any setting?
svvv said:
Thanks joe....atlast bootloader unlocked..
One more thing i installed Fly UI OS from p6 and replaced with stock HAM boot.img....OS is not booting properly getting lots of FC's...
Does CM10.1 require different kernel or do we need to change any setting?
Click to expand...
Click to collapse
CM 10.1 may need some change in kernel or/and its config. Init.rc files needs modifications (framework , init.d support) , and it can happen that the init binary need some mods in cm source for proper working.For example wifi firmware path as on g510 . The standard cm init uses 2 firmware path , while the g510 init uses 4 to properly load wifi firmware files.You can check it on my github.
I am planning to compile a cm rom for our device , but the bootloader was the first step.
Awesome news mate ...
Finally someone can make goodies on HAM !
You can take a look also on my CM11 development project for P6, maybe you will make one for HAM !
Good luck !
Nice , very nice
Yes !!! This is best news on Ham. Thanks
Inviato dal mio HUAWEI MT1-U06 utilizzando Tapatalk
Thanks! ...While this method works to unlock bootloader in B907 HAM??? I think I'll try
Unlocked on B907 it was only a problem , the bat don't find the extracted folder on %temp% but it was there .....I was running adb cmd inside temp folder. Work perfect . THANKS
IT'S DAY ZERO FOR OWR DEVICE
Inviato dal mio HUAWEI MT1-U06 utilizzando Tapatalk
unlocked bootloader will be easier to carry kitkat HAM??
ErSergi said:
unlocked bootloader will be easier to carry kitkat HAM??
Click to expand...
Click to collapse
Yes, KitKat will be more easily to port on HAM !
surdu_petru said:
Yes, KitKat will be more easily to port on HAM !
Click to expand...
Click to collapse
but we need kernel from huawei right....for kitkat
Tested and works in B907 Oficial, unlocked bootloader ... Thank you for the contribution
Now this is a great Birthday present for me..
HAM Finally can be UNLOCKED.
i havent try yet but just wanna ask few questions.
1. Since now i'm using Hyd52Rom from Husen, can HAM be Unlocked with this Rom running?
2. Whats the best choice of current rom running for Unlocking?
maybe its sound stupid but its me (non-devs brain and only a user who dare to test..)...
Thanks guys.
You can unlock your phone using any rom. The only thing is needed turned on usb debugging. Of course the drivers on your pc should be installed .
After unlock check my other thread and update your permanent twrp to 2.6.3.2.
Sent from my HUAWEI MT1-U06 using xda app-developers app
HAM finally unlocked.
Looking forward for testing Compatible Roms.
Any suggestions highly appreciatable.
Thinking of trying P6 roms but not sure if theyre compatible
[email protected]
theoppositeman said:
HAM finally unlocked.
Looking forward for testing Compatible Roms.
Any suggestions highly appreciatable.
Thinking of trying P6 roms but not sure if theyre compatible
[email protected]
Click to expand...
Click to collapse
I think every p6 JB ROM will compitable just you have to change dpi in build.prop
Sent from my P6-U06 using xda app-developers app
Hi @ all,
it's all progressing really well in recent times
Can i use this method only for HAM or can i use this for my P6 also?
87insane said:
Hi @ all,
it's all progressing really well in recent times
Can i use this method only for HAM or can i use this for my P6 also?
Click to expand...
Click to collapse
It should work on P6 too , but for P6 there are stock roms with unlocked bootloader.(KK beta).
If you want to use it on your P6 , use unlock bootloader only , and flash permanent twrp made for P6.
Of course permanent twrp for Mate will work on P6 as well , but the device identifier will be hwmt1_u06 and not hwp6_u06 which can cause assert errors when you try to flash a recovery flashable P6 rom .
I know. But i search for a way to use this on B125 international. In the CN it is to easy
Gesendet von meinem HUAWEI P6-U06
Hi,
I can't flash [ROM][JB4.2.2][HAM][ HYD52ROM V5] [Superfast,Stable][V5 7-02-14]
from TWRP 2.6.3.2 . Everythings go right but on reboot the device never end logo.
I need to relock bottloader and start again whit dload. I have tryed flashing same zip from tmp recovery on locked and everything is working. i will to know if is a rom problem or twrp or unlocked bootloader.Also i have try buckup from HYD52ROM V5 whit twpr 2.6.3.2 and restore rom, after a factory reset, but was a id mismatching and no user app.
I will try to unlock and no permanent twpr, but use a cwm tmp whats happen. i will report
Edit: whit unlocked bootloader and tmp twrp
2.6.3.0 from sordu_petru recovery flash of same zip ad no problem.
anyone can help how to restock from lineage os to stock rom? first i try to flash stock recovery using adb, then i enter recovery mode but after restart, it always enter bootloader menu. im using recovery image Z00A_WW_2.20.40.194, because my stock rom using that version. please help me, i want back to stock rom. sorry if my english is bad. thank you..
You upgraded bootloader to M to flash Lineage .
To flash LP stock , you need to downgrade bootloader to LP.
OR
You could try but at your own risk > as always .
Use giovix modder tool to >
1 ) Select > return to stock option
2 ) In above^^ option selection in modder , flash boot and then recovery.(which will be 4.21.40 .134 M stock)
3 ) Reboot to stock recovery , adb sideload stock .134 M firmware from asus.
About
Who needs this?
When you unlocked by UsU you have to flash a special baseband package afterwards in order to make ROMs working higher then LP (so MM, N, ..).
This is annoying on the one hand and can cause problems on the other.
These UsU kernels are specific for your model and available for several custom and stock ROMs.
Just flash the corresponding UsU kernel after flashing a ROM and ensure that your modem partition is pure the one of yours model version (so no baseband package flashed).
Guide
(read FAQ #1 if you have the baseband package flashed currently!)
Choose the right UsU kernel (according to the ROM you have)
Ensure you have a ROM installed which is compatible with an UsU kernel (means an UsU kernel exists for your ROM and version)
If not: Flash a ROM which has an UsU kernel available NOW.
Download the UsU kernel to your PC
Boot device in fastboot mode (check the UsU OP thread for a how-to)
Flash the downloaded UsU kernel (has to be done again after a ROM flashing!):
Code:
fastboot flash boot <model>_xx_boot_xx.img
(replace "<model>_xx_boot_xx.img" with the real filename)
Reboot and enjoy:
Code:
fastboot reboot
Downloads
steadfasterX leech Server
Choose the folder of your device (all the ones named "-UsU" are obviously those of your interest)
Choose the ROM flavor of the ROM you have installed or want to install
Choose the version of that ROM
Download the latest boot image you can find (the higher the build number the newer)
Sources / Changelogs
aoscp | lineageos | rr : nougat
aoscp | lineageos | rr : oreo
stock : nougat
Credits
kessaras - without him the custom versions of the UsU kernels wouldn't be what they are
me - I provided the UsU patches included in every UsU kernel, a Jenkins build server, a download server and many of my free time.. so yes I think I can get some credits too
XDA:DevDB Information
UsU kernel versions, Kernel for the LG G4
Contributors
steadfasterX, kessaras
Source Code: https://github.com/Suicide-Squirrel
Kernel Special Features: Making UsU baseband package flashing obsolete
Version Information
Status: Nightly
Created 2018-03-15
Last Updated 2020-04-14
Frequently Asked Questions
FAQ
1) I want to use an UsU kernel but I had flashed the baseband package as recommended by the UsU thread. What do I need to do?
Pretty simple. Flash the modem partition again in fastboot.
Which one depends...
I highly recommend to use a MM modem of YOUR model (for MM ROMs) or the v29a N modem (for N and O ROMS).
Unfortunately for some models the v29a N modem does not work fine so you will be the safest when using the MM one of your device model.
Ensure you have a ROM installed which is compatible with an UsU kernel (means an UsU kernel exists for your ROM and version)
If not: Flash a ROM which has an UsU kernel available NOW.
Extract the latest MM KDZ of your device model with SALT (do NOT use the windows tools!)
Boot device in fastboot mode (check the UsU OP thread for a how-to)
Flash the modem:
Code:
fastboot flash modem modem.bin
(or if named img: fastboot flash modem modem.img)
Flash the downloaded UsU kernel:
Code:
fastboot flash boot <model>_xx_boot_xx.img
(replace "<model>_xx_boot_xx.img" with the real filename)
Reboot and enjoy:
Code:
fastboot reboot
2) Where are the sources for the UsU kernels?
AOSCP - Nougat -> here
AOSCP - Oreo -> here
STOCK - Nougat -> here
3) Are all UsU kernels based on the TITAN stuff?
No. Only AOSCP Nougat / Oreo for now are based on the TITAN kernel.
STOCK is pure STOCK plus the UsU patches.
ZZZ) I miss a UsU kernel for my ROM!! Could you provide it please?
Do not hesitate to ask.. KINDLY. There is no guarantee. Maybe I will add it - maybe not. There are too many out there to build for all of them.
Up to then you are stuck with flashing the baseband package or switch to an UsU kernel supported ROM
Reserved
steadfasterX said:
About
When you unlocked by UsU you have to flash a special baseband package afterwards in order to make ROMs working higher then LP (so MM, N, ..).
This is annoying on the one hand and can cause problems on the other.
These UsU kernels are specific for your model and available for several custom and stock ROMs.
Just flash the corresponding UsU kernel after flashing a ROM and ensure that your modem partition is pure the one of yours model version (so no baseband package flashed).
Click to expand...
Click to collapse
Just a couple of quick questions/clarifications:
- Is the H812 kernel for AOSCP in the downloads here, the same as the version you loaded in post # 327 in the bootloader unlock thread?
- If one was to restore the original TWRP backup of the just unlocked stock rom, should one for example, flash the 'stock' kernel after restoring? - also as an ancillary question, should one then install the TWRP preview version for 'stock' after the restore as well that you have uploaded in your TWRP thread?
Thanks,
S.
sdembiske said:
Just a couple of quick questions/clarifications:
- Is the H812 kernel for AOSCP in the downloads here, the same as the version you loaded in post # 327 in the bootloader unlock thread?
- If one was to restore the original TWRP backup of the just unlocked stock rom, should one for example, flash the 'stock' kernel after restoring? - also as an ancillary question, should one then install the TWRP preview version for 'stock' after the restore as well that you have uploaded in your TWRP thread?
Thanks,
S.
Click to expand...
Click to collapse
No they are not the same because I had to rebuild all kernel versions .
The stock kernel is only for the nougat based ROM available so if you had v29a before or when creating the backup then yes. But if you were on lollipop or marshmallow then a nougat kernel makes no sense on these.
there is no TWRP stock version available since a long time already.. just flash the latest N preview.
Sent from my LG-H815 using XDA Labs
Sorry, deleted. Thank you!!!
steadfasterX said:
About
These UsU kernels are specific for your model and available for several custom and stock ROMs.
Just flash the corresponding UsU kernel after flashing a ROM and ensure that your modem partition is pure the one of yours model version (so no baseband package flashed).
/QUOTE]
Downloaded latest H812 kernel for AOSCP, all went smooth but lost SuperSU on reboot - just had to re-flash it in TWRP again and reboot to reinstate. All good!
Click to expand...
Click to collapse
I did some research. Read that device drivers are stored in the kernel. So that means no matter what rom, if the kernel is H812, you cannot get the FM radio, right? Unless you can find a way to install H815 fm radio driver onto h812 kernel.
I have H812 unlocked with UsU and flashed baseband and I stayed on the stock MM rom.
As far as I can figure this is what I should do to get stock Nougat
Don't wipe anything in TWRP
Flash stock nougat rom G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip then reboot into fastboot,
flash modem.bin from my original SALT backup of original MM modem,
flash UsU kernel h812_stock_boot_build-11-nougat.img
reboot to system and enjoy!
Hopefully this is right!
Edit: Everything works perfectly except calls and corrupted sdcard!
Attached the error log for when making a call.
Thanks Chief :good: one should not need this kernel, in my case H815, if one is having no issues?
Edit: I do have a no Sim detection issue with aoscp oreo
grantdb said:
I have H812 unlocked with UsU and flashed baseband and I stayed on the stock MM rom.
As far as I can figure this is what I should do to get stock Nougat
Don't wipe anything in TWRP
Flash stock nougat rom G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip then reboot into fastboot,
flash modem.bin from my original SALT backup of original MM modem,
flash UsU kernel h812_stock_boot_build-11-nougat.img
reboot to system and enjoy!
Hopefully this is right!
Edit: Everything works perfectly except calls and corrupted sdcard!
Attached the error log for when making a call.
Click to expand...
Click to collapse
Checkout faq zzz in the UsU thread..
jason_l367 said:
Thanks Chief :good: one should not need this kernel, in my case H815, if one is having no issues?
Edit: I do have a no Sim detection issue with aoscp oreo
Click to expand...
Click to collapse
Well up to you if you flash it or not. If everything is working I see no other reason then cosmetics.
This is a very well known issue for aoscp oreo! Just use the a search in that thread! They also have issues with battery drain etc and I always said oreo is nothing which I can recommend atm. Its a play ground for me even if it boots and most things are working.
All I did for working everything with bootloader unlocked with SALT and baseband flashed on stock MM H812:
First thing I did was follow the following since I allready flashed the baseband after unlocking:
FAQ
1) I want to use an UsU kernel but I had flashed the baseband package as recommended by the UsU thread. What do I need to do?
Pretty simple. Flash the modem partition again in fastboot.
Which one depends...
I highly recommend to use a MM modem of YOUR model (for MM ROMs) or the v29a N modem (for N and O ROMS).
Unfortunately for some models the v29a N modem does not work fine so you will be the safest when using the MM one of your device model.
Ensure you have a ROM installed which is compatible with an UsU kernel (means an UsU kernel exists for your ROM and version)
If not: Flash a ROM which has an UsU kernel available NOW.
Extract the latest MM KDZ of your device model with SALT (do NOT use the windows tools!)
Boot device in fastboot mode (check the UsU OP thread for a how-to)
Flash the modem:
Code:
fastboot flash modem modem.bin
(or if named img: fastboot flash modem modem.img)
Flash the downloaded UsU kernel:
Code:
fastboot flash boot <model>_xx_boot_xx.img
(replace "<model>_xx_boot_xx.img" with the real filename)
Reboot and enjoy:
Code:
fastboot reboot
Click to expand...
Click to collapse
In the above procedure I first used my backup MM modem and calls had no sound then I repeated the same procedure using the N modem and it bootlooped.
Restored my FULL TWRP backup (Boot, Recovery, System, Data, Cache, Firmware image, EFS, BL unlock state, Bootloader, Carrier) to MM stock with root and custom kernel (LuPus).
Booted into the system once to make sure all working.
Boot into recovery.
Mount system partition.
Flash full stock nougat (G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip).
Reboot into recovery.
Mount system partition.
Flash baseband file (H812_UsU_baseband_flash-in-twrp.zip).
Reboot into system.
Wait for stock rom to fully load (Takes about 15 mins).
SIM and SD card fully working! Network is immediate with no delay only on first boot for some reason then see below.
Reboot into recovery.
Flash Magisk.
Reboot into system.
Notification that Network unavailable, service disabled message where carrier name should be, then the network works (had
to select my provider under APN settings and then my provider under network selection because it auto selected the wrong
but working provider) Network takes a couple of minutes to kick in properly on each reboot.
Bluetooth, Sound, calls, SMS, GPS, NFC, Camera(pics and vids incl playback), LG Apps like Quick remote and Health (even FM
Radio app runs but no sound), Dolby Atmos, Magisk all working!
Phone is now a LGLS991 and baseband unknown in settings.
EVERYTHING IS PERFECT!
steadfasterX said:
Checkout faq zzz in the UsU thread..
Click to expand...
Click to collapse
Do you think I will get any better than what I have by formatting Data?
Thanks!
grantdb said:
[............] EVERYTHING IS PERFECT!
Click to expand...
Click to collapse
Thx for your report!
so basically u did this (including what we discussed on IRC):
unlocked with UsU
flashed the baseband package
created a full TWRP backup
Flash full stock nougat (G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip)
flashed your backuped MM modem
flashed UsU kernel: h812_stock_boot_build-11-nougat.img
-> result: booted but calls had no sound
flashed N modem
flashed UsU kernel: h812_stock_boot_build-11-nougat.img
-> result: bootlooped
restored the full backup of the TWRP backup (means also: modem + baseband pkg)
-> result: booted, all working
Flash full stock nougat (G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip).
Flash baseband file (H812_UsU_baseband_flash-in-twrp.zip)
-> booted (took 15 min). Notification that Network unavailable, service disabled message where carrier name should be, then the network works (had
to select my provider under APN settings and then my provider under network selection because it auto selected the wrong
but working provider) Network takes a couple of minutes to kick in properly on each reboot.
Bluetooth, Sound, calls, SMS, GPS, NFC, Camera(pics and vids incl playback), LG Apps like Quick remote and Health (even FM Radio app runs but no sound)
Flashing Magisk, Dolby Atmos
-> result: all working
Note:
Phone is now a LGLS991 (known and written in FAQ of UsU thread) and baseband unknown in settings.
Is that summary correct?
Cheers
steadfasterX said:
Thx for your report!
so basically u did this (including what we discussed on IRC):
[.........]
Is that summary correct?
Cheers
Click to expand...
Click to collapse
Yes that's it!
Thank you once again for all your work and help!
Cheers!
EDIT: The network only takes 40 seconds to start working on boot.
steadfasterX said:
Thx for your report!
so basically u did this (including what we discussed on IRC):
unlocked with UsU
flashed the baseband package
created a full TWRP backup
Flash full stock nougat (G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip)
flashed your backuped MM modem
flashed UsU kernel: h812_stock_boot_build-11-nougat.img
-> result: booted but calls had no sound
flashed N modem
flashed UsU kernel: h812_stock_boot_build-11-nougat.img
-> result: bootlooped
restored the full backup of the TWRP backup (means also: modem + baseband pkg)
-> result: booted, all working
Flash full stock nougat (G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip).
Flash baseband file (H812_UsU_baseband_flash-in-twrp.zip)
-> booted (took 15 min). Notification that Network unavailable, service disabled message where carrier name should be, then the network works (had
to select my provider under APN settings and then my provider under network selection because it auto selected the wrong
but working provider) Network takes a couple of minutes to kick in properly on each reboot.
Bluetooth, Sound, calls, SMS, GPS, NFC, Camera(pics and vids incl playback), LG Apps like Quick remote and Health (even FM Radio app runs but no sound)
Flashing Magisk, Dolby Atmos
-> result: all working
Note:
Phone is now a LGLS991 (known and written in FAQ of UsU thread) and baseband unknown in settings.
Is that summary correct?
Cheers
Click to expand...
Click to collapse
So what does this tell us H812 users about the source of the problem. Flashing the original ARB O Nougat ROM (+ N bootloader stack?) kills calls. If you go back to the original state after unlock, then flash ARB any Nougat + baseband you are fine. So steadfasterx, can you answer this question: What does flashing the ARB O ROM (+N bootloader stack) do to continue to kill calls even after you flash with another ROM? What do you need to do (other than restoring a backup) to undo this? My original TWRP backup wouldn't boot so restoring a nandroid isn't an option for me.
mwahahaa said:
So what does this tell us H812 users about the source of the problem. Flashing the original ARB O Nougat ROM (+ N bootloader stack?) kills calls. If you go back to the original state after unlock, then flash ARB any Nougat + baseband you are fine. So steadfasterx, can you answer this question: What does flashing the ARB O ROM (+N bootloader stack) do to continue to kill calls even after you flash with another ROM? What do you need to do (other than restoring a backup) to undo this? My original TWRP backup wouldn't boot so restoring a nandroid isn't an option for me.
Click to expand...
Click to collapse
your bootloader stack (all files mentioned in FAQ 18) must be on MM
you would flash G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip (as described in the guide)
you would flash the baseband package
you would boot
everything should work but give it time (15min to fully boot the first time)
you should set the preferred network type to 3G or 2G (this setting here is the most important and - until now- missing part!)
reboot
give it at least 5min if it still does not connect to cellular network you may need to search cellular networks manually - several times if needed
you may need to set a cell network manually
you may need to reboot again
all the above has been written already but some users still report that this does not work for them. Maybe the time factor is important (most users are impatient)
steadfasterX said:
your bootloader stack (all files mentioned in FAQ 18) must be on MM
you would flash G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip (as described in the guide)
you would flash the baseband package
you would boot
everything should work but give it time (15min to fully boot the first time)
you should set the preferred network type to 3G or 2G (this setting here is the most important and - until now- missing part!)
reboot
give it at least 5min if it still does not connect to cellular network you may need to search cellular networks manually - several times if needed
you may need to set a cell network manually
you may need to reboot again
all the above has been written already but some users still report that this does not work for them. Maybe the time factor is important (most users are impatient)
Click to expand...
Click to collapse
I did all of that exactly and absolutely nothing has changed. No matter what I flash (AOSCP ROM, Stock ROM kernel, modem, radio, etc. etc. my calls hang up immediately when I dial and I don't receive any incoming calls. I am kicking myself for botching the SALT backup because the phone is useless to me without voice.
mwahahaa said:
I did all of that exactly and absolutely nothing has changed. No matter what I flash (AOSCP ROM, Stock ROM kernel, modem, radio, etc. etc. my calls hang up immediately when I dial and I don't receive any incoming calls. I am kicking myself for botching the SALT backup because the phone is useless to me without voice.
Click to expand...
Click to collapse
Yea the backup is gold in many situations...
There is still one thing (at least) you can try :
Do a basic backup in SALT now if you have no backup anymore.
If you have made a backup in the meanwhile ensure you see the modemst1 and modemst2 and misc images there. If not: do a backup NOW and do not proceed until you have these!!
It is also a good idea to do a backup in TWRP including EFS and NO unlock state so you have 2 ways of a backup! Do not skip that. It's done in a second..
Erase the following partitions (part of the EFS and contains network unlock state too! Means you will loose the network unlock if any):
fastboot erase modemst1
fastboot erase modemst2
As said you will loose your network unlock if any and in some circumstances even the imei .
That's why it is important to have the above partitions as a backup.
Boot. Search networks etc.
When booted check imei (*#06# in the dialer), too.
If you loose cell service and imei is still there:
You may need to network unlock the device again and as that may not popup on boot you may must type a secret code in the dialer to open it manually (Google it)
When even that has no positive effect ensure you format data as described in faq zzz and re-do the above erase commands in fastboot afterwards. Then boot again.
You can restore the both partitions and so going back to the current state by either restoring by TWRP the EFS or flashing the SALT backup in fastboot :
fastboot flash modemst1 modemst1.image
fastboot flash modemst2 modemst2.image
This will give you any network unlock back and if lost imei too.
Sent from my LG-H815 using XDA Labs
mwahahaa said:
So what does this tell us H812 users about the source of the problem. Flashing the original ARB O Nougat ROM (+ N bootloader stack?) kills calls. If you go back to the original state after unlock, then flash ARB any Nougat + baseband you are fine. So steadfasterx, can you answer this question: What does flashing the ARB O ROM (+N bootloader stack) do to continue to kill calls even after you flash with another ROM? What do you need to do (other than restoring a backup) to undo this? My original TWRP backup wouldn't boot so restoring a nandroid isn't an option for me.
Click to expand...
Click to collapse
I flashed the any ARB stock rom + baseband package and i also have the result of no call audio... I need this!!!
Hi Guys,
since few days I try to install a custom rom on my eu xt1635-02.
I opended the bootloader offical way and installed the latest twrp. 3.2.0.1,all went fine,but factory reset deletes not all data and when I try to install a custom rom ( tried several) I always got an error 7 from twrp? So not possible to install something.
I come from latest offical Nougat 7.1.1 rom with february patch.
There are so many theads I was reading,but I think I need help. Also I can't find a definetly method how to root without risk of brik.
Sorry für my bad english, my german is better.
Nobody got the same problem? Maybe phone is damaged?
messiahxavier said:
Hi Guys,
since few days I try to install a custom rom on my eu xt1635-02.
I opended the bootloader offical way and installed the latest twrp. 3.2.0.1,all went fine,but factory reset deletes not all data and when I try to install a custom rom ( tried several) I always got an error 7 from twrp? So not possible to install something.
I come from latest offical Nougat 7.1.1 rom with february patch.
There are so many theads I was reading,but I think I need help. Also I can't find a definetly method how to root without risk of brik.
Sorry für my bad english, my german is better.
Click to expand...
Click to collapse
messiahxavier said:
Hi Guys,
since few days I try to install a custom rom on my eu xt1635-02.
I opended the bootloader offical way and installed the latest twrp. 3.2.0.1,all went fine,but factory reset deletes not all data and when I try to install a custom rom ( tried several) I always got an error 7 from twrp? So not possible to install something.
I come from latest offical Nougat 7.1.1 rom with february patch.
There are so many theads I was reading,but I think I need help. Also I can't find a definetly method how to root without risk of brik.
Sorry für my bad english, my german is better.
Click to expand...
Click to collapse
1. It's always hard to help without logs. Error codes are too unspecific
2. Check the mount settings, under the partition list there is an option for mounting /system as read only. It has to be disabled for installing custom ROMs.
Found something intresting,when I flash twrp without any problem and boot to system...then again tomorrow recovery via hardbuttons over bootloader there comes stock recovery????what ist that? Not able to go to twrp,only after new flash in fastboot.
Then you didn't flash it but just boot it
Hi bro.
I did face same problem here.
Follow the below steps:
Take download a nougat firmware, currently the "NPNS26.118-22-1"
Enter fastboot mode and type these comands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
You can do on any rom. For example: You are on AEx nougat, enter fastboot mode and type the comands above.
I hope that helped you.
tiago1966 said:
Hi bro.
I did face same problem here.
Follow the below steps:
Take download a nougat firmware, currently the "NPNS26.118-22-1"
Enter fastboot mode and type these comands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
You can do on any rom. For example: You are on AEx nougat, enter fastboot mode and type the comands above.
I hope that helped you.
Click to expand...
Click to collapse
Current firmware is 118-22-2-17! Older builds could lead to downgrade issues!
hi there
I've just bout a new note 8 pro begonia(in) with no NFC but the is no update at all don't know why
I've tried to install recovery rom 12.5.3 and 12.5.5 Sayed cant install this stock rom
Aby updates? Having this problem on Global EEA. Stuck on 12.0.6.
Backup needed files.
Unlock bootloader
- Official way and wait 7 days.
- Unofficial way instant.
Flash rom
- Fastboot: Flash fastboot rom by Mi Flash tool and lock your bootloader (optional).
- TWRP: Flash twrp, flash recovery rom.