4.4 rooted to 4.4.2, build.prop issue - Nexus 5 Q&A, Help & Troubleshooting

I'd like to update from 4.4 to 4.4.2 and ultimately root again. I'm trying to flash update via twrp but it says build.prop modified or something like that. I read it has to do with the softkey hide command which I've pasted in the file. I read the sticky in the general page and to get an untampered build.prop you have to flash system.img but I don't know how to do that, where to get it from and if it erases my data? Any help would be appreciated.
Thanks!

Follow method #2 but only flash system and boot.img http://forum.xda-developers.com/showthread.php?p=47156064
You won't lose your data

x3malex said:
I'd like to update from 4.4 to 4.4.2 and ultimately root again. I'm trying to flash update via twrp but it says build.prop modified or something like that. I read it has to do with the softkey hide command which I've pasted in the file. I read the sticky in the general page and to get an untampered build.prop you have to flash system.img but I don't know how to do that, where to get it from and if it erases my data? Any help would be appreciated.
Thanks!
Click to expand...
Click to collapse
I'm sure someone will help you with that but for future reference, rather than playing with the build.prop I would just install xposed framework and gravitbox. That lets you change all kinds of stuff. Then to sideload updates all you have to do is disable xposed framework., sideload, and re-enable it.

jd1639 said:
Follow method #2 but only flash system and boot.img http://forum.xda-developers.com/showthread.php?p=47156064
You won't lose your data
Click to expand...
Click to collapse
I flashed system.img and boot.img and I seemed to have lost root (still on 4.4).
I booted into TWRP and tried to flash 4.4.2 but it says:
verifying current system...
Not enough free space on /system to apply patch
E: Error executing updater binary in zip ' /sdcard...
Error flashing zip '/sdcard/ROM Toolbox/[the 4.4.2 file name here]
Updating partition details....
E: Unable to mount ' /cache'
I have 5g free on my phone, that should be ample space for a 50mb update?
EDIT: Also "Unfortunately, Google Play Store has stopped" keeps popping up and the app store force closes constantly

x3malex said:
I flashed system.img and boot.img and I seemed to have lost root (still on 4.4).
I booted into TWRP and tried to flash 4.4.2 but it says:
verifying current system...
Not enough free space on /system to apply patch
E: Error executing updater binary in zip ' /sdcard...
Error flashing zip '/sdcard/ROM Toolbox/[the 4.4.2 file name here]
Updating partition details....
E: Unable to mount ' /cache'
I have 5g free on my phone, that should be ample space for a 50mb update?
EDIT: Also "Unfortunately, Google Play Store has stopped" keeps popping up and the app store force closes constantly
Click to expand...
Click to collapse
Losing root is normal. What file are you flashing on twrp? Is it the update zip?

jd1639 said:
Losing root is normal. What file are you flashing on twrp? Is it the update zip?
Click to expand...
Click to collapse
It's the Nexus 5 4.4 to 4.4.2 I downloaded from:
http://android.clients.google.com/p...ed-hammerhead-KOT49H-from-KRT16M.b3d1f307.zip

x3malex said:
It's the Nexus 5 4.4 to 4.4.2 I downloaded from:
http://android.clients.google.com/p...ed-hammerhead-KOT49H-from-KRT16M.b3d1f307.zip
Click to expand...
Click to collapse
Re-download the file and try again. I've flashed that same file in twrp without any problems

jd1639 said:
Re-download the file and try again. I've flashed that same file in twrp without any problems
Click to expand...
Click to collapse
Thanks jd, it worked. I flashed superSU and I have root on 4.4.2
Now I just need to figure out how to hide the softkeys with xposed framework/gravitbox
Much appreciated!

x3malex said:
Thanks jd, it worked. I flashed superSU and I have root on 4.4.2
Now I just need to figure out how to hide the softkeys with xposed framework/gravitbox
Much appreciated!
Click to expand...
Click to collapse
No problem. Glad it worked for you

Related

[Q] catch-22 in TWRP - permissions

Hello people,
First I'd like to thank everyone contributing on this forum, the posts here have made it possible for a beginner like I am to have a rooted phone.
I am posting this after trying in vain to find a solution to an issue I'm having with permissions on my Ascend Y300.
I rooted it and had CM 10.2 running smoothly for over a month while updating to nightly builds. After one of these updates I accidentally did a full advanced wipe in TWRP v2.5.0.1., but re-installed the rom and all seemed well. Then I started having "insufficient space available" notifications when trying to install apps from Google Play, despite having plenty of space available on both the internal and external SD. I reinstalled the rom, wiping only cache and dalvik this time. This time I couldn't download anything due to low space.
Looking into the problem I tried to delete the dump files in \data but when trying to reach that folder, whether via shell or the file manager in CM, I would get denied access due to permissions. I tried through TWRP's file manager and terminal but ran into the same problem.
I did a full system wipe again out of frustration, then tried Fix Permissions in TWRP. Am getting this as a result:
Can't check permissions after Factory Reset.
Please boot rom and try again after you reboot into recovery.
Done.
Failed
Click to expand...
Click to collapse
Then I tried to flash the rom I had before, which failed with the following message:
set_perm: some changes failed
E:Error executing updater binary in zip '/sdcard (truncated)
Error flashing zip '/sdcard/cm-10.2.......
Failed
Click to expand...
Click to collapse
I tried to sideload my rom as well, to no avail (permissions error).
Basically, TWRP is telling me that I need to install a rom to fix permissions, but I need to fix permissions to install a rom.
I tried to restore settings in TWRP: clicking the option freezes the phone. Perhaps I could flash an update to TWRP which has fixed permissions? However I cannot access the Fastboot menu on my Y300: I can either get the recovery menu, the purple screen, or a freeze on the Huawei logo which shows up as "unauthorized device" when checking devices in cmd (the bootloader is unlocked).
All I would like to achieve is having CM running normally, allowing me to download a few apps from the Play Store.
Thank you for reading! Any advice is greatly appreciated, especially as I use this phone for work (luckily all this is happening over my Christmas leave!).
Cheers
Update: through fastboot I managed to update TWRP to the latest version, flash the stock rom for the Y300, and because I have a system installed I was also able to Fix Permissions in TWRP.
When I install supersu I get a "successful" result, however I still get the following error when trying to flash a CM 10.2 rom:
set_perm: some changes failed
E:Error executing updater binary in zip '/sdcard (truncated)
Error flashing zip '/sdcard/cm-10.2.......
Failed
Click to expand...
Click to collapse
Anybody know how to give full permissions to TWRP?
Thanks.
P.S. Merry Christmas!

[Q] "audio_effects.conf" has unexpected contents" error prevent OTA sideload

[Q] "audio_effects.conf" has unexpected contents" error prevent OTA sideload
Sideloaded ota 5.0 fails on Nexus5
Downloaded ota.zip and did adb sideload.
The update aborts with a message:
"/system/vendor/etc/audio_effects.conf" has unexpected contents"
I installed Viper4Android for Audio enhancement. Guess, its playing around.
Any idea how to over come this?
A guy posted his audio_effects.conf file in xda forum. Even if I have the file, how am I supposed to make it work, as expected. TIA
gladijames said:
Sideloaded ota 5.0 fails on Nexus5
Downloaded ota.zip and did adb sideload.
The update aborts with a message:
"/system/vendor/etc/audio_effects.conf" has unexpected contents"
I installed Viper4Android for Audio enhancement. Guess, its playing around.
Any idea how to over come this?
A guy posted his audio_effects.conf file in xda forum. Even if I have the file, how am I supposed to make it work, as expected. TIA
Click to expand...
Click to collapse
You'd have to replace it, but viper makes many changes. Your best bet would be to backup and either flasha rom.zip from recovery or fastboto flash boot and system image.

[Q] LRX22C from LRX210 OTA fails (fingerprint error)

I installed the factory image from Android Developers to my Nexus 5 and applied Chainfire's CF Autoroot. (I did this exact process on my old Nexus 4, my Nexus 7, and Nexus 10). Beyond that, I left everything as stock and the only root applications I run are Titanium and ES File Explorer.
The LRX22C OTA patch came down for all the devices recently, and none of them patched successfully. They all came up with the stock recovery android with simply: "Error".
I copied the OTA zip from the /cache folder to my /sdcard folder and booted into CWM to flash the zip manually. I get the following error:
Package expects build fingerprint of google/hammerhead/hammerhead:5.0/LRX210/1570415:user/release-keys or google/hammerhead/hammerhead:5.0.1/LRX22C/1602158:user/release-keys; this device has google/hammerhead/hammerhead:4.4/KRT16M/893803:user/release-keys
Then the installation aborts. I get this fingerprint error on all the Nexus devices.
It's not a signature verification issue, and disabling signature verification doesn't help.
Any idea why this might be happening and how to get around it? Thanks!
Edit:
Someone pointed out the answer is here: http://forum.xda-developers.com/showpost.php?p=57575654&postcount=3532
I've just tried it at it seems to work.
Mods can you please delete this thread.

[SOLVED] hosts file restored at boot

Hello,
I rooted my device and installed AdAway,
Everytime I reboot I lose the blocking functionality.
How do I fix that?
Thanks
EDIT: https://forum.xda-developers.com/mate-9/help/ro-rooted-mate9-t3564231
bel3atar said:
Hello,
I rooted my device and installed AdAway,
Everytime I reboot I lose the blocking functionality.
How do I fix that?
Thanks
EDIT: https://forum.xda-developers.com/mate-9/help/ro-rooted-mate9-t3564231
Click to expand...
Click to collapse
If you used PHH to root, open the zip, open config.txt in a text editor, change "verity" to "noverity". Save and flash again.
You might need to flash back your stock boot image before flashing.
Edit: That link you posted there is full of misinformation.
Keeping system RO is best. It's not read-only/read-write that's causing it to roll back hosts.
I did that, but the flash fails with error 1.
I can't even install the original superuser-r310-beta.zip
bel3atar said:
I did that, but the flash fails with error 1.
I can't even install the original superuser-r310-beta.zip
Click to expand...
Click to collapse
Did you restore your stock boot image first?
Post your full build if you don't have it.
MHA/LON-LxxCxxxBxxx
ante0 said:
did you restore your stock boot image first?
Post your full build if you don't have it.
Mha/lon-lxxcxxxbxxx
Click to expand...
Click to collapse
mha-l29c432b182
bel3atar said:
mha-l29c432b182
Click to expand...
Click to collapse
https://mega.nz/#!VhlkmQbJ!sgq55_e6cf78VwxmKvUHD7f23aJnnWUwdOehft2Lpdk
Flash In TWRP to Boot partition, then flash your superuser zip with "noverity" in config.txt
ante0 said:
https://mega.nz/#!VhlkmQbJ!sgq55_e6cf78VwxmKvUHD7f23aJnnWUwdOehft2Lpdk
Flash In TWRP to Boot partition, then flash your superuser zip with "noverity" in config.txt
Click to expand...
Click to collapse
Solved, thank you =)
One more question: Will I still get OTA updates or will I have to apply them manually?
bel3atar said:
Solved, thank you =)
One more question: Will I still get OTA updates or will I have to apply them manually?
Click to expand...
Click to collapse
If you don't modify anything in /system, /product or /vendor you should still get OTA.
For example: installing Busybox modifies /system. Viper4Android modifies /vendor and /system.
If you need Busybox you should consider switching to Magiskv12. Its busybox is systemless (Doesn't modify anything).
And with Magisk you can use Android Pay and PokemonGO (and other apps that use SafetyNet).
MagiskHide is a little buggy on Mate 9, and other Huawei devices that use Nougat. If you enable it, fingerprint and pin will break after you reboot. If you just enable, run Android Pay, and disable after you will be fine.

Mate 9 L29C185B181 camera not working after decrypting data.

Hello guys, I seriously need help please.
I decrypted my data. Everything is working perfectly with the exception of the Huawei camera.
1.The icon has change to android green icon
2.It flashes when u open
3 . 3rd party camera app like camera 360 which I just Install from playstore also not working, only showing me black screen.
Will be glad if someone can restore my camera back:crying:.
Am on firmware L29C185B181 please.
golastic said:
Hello guys, I seriously need help please.
I decrypted my data. Everything is working perfectly with the exception of the Huawei camera.
1.The icon has change to android green icon
2.It flashes when u open
3 . 3rd party camera app like camera 360 which I just Install from playstore also not working, only showing me black screen.
Will be glad if someone can restore my camera back:crying:.
Am on firmware L29C185B181 please.
Click to expand...
Click to collapse
Did you flash some other models boot image?
ante0 said:
Did you flash some other models boot image?
Click to expand...
Click to collapse
Everything I flashed was extracted from my firmware version... update_data_full_public.zip and update_full_hw_meafnaf.zip.
golastic said:
Everything I flashed was extracted from my firmware version... update_data_full_public.zip and update_full_hw_meafnaf.zip.
Click to expand...
Click to collapse
Camera is not part of those zips so that can't be it. Could you backup your current boot image in twrp and send to me?
Maybe Flash public and hw in twrp to fix the camera?
ante0 said:
Camera is not part of those zips so that can't be it. Could you backup your current boot image in twrp and send to me?
Click to expand...
Click to collapse
Sure Sir.....
https://mega.nz/#!8JNX3CwZ!PjSDO9c4mNWh5_ddKANmLNqLPRo7hyk_of5lAZThPUU (from partitions backup apk)
https://mega.nz/#F!BZ0XRb6Z!Y8QkOaw6K8dtuzuysgImNA (from twrp)
You can revert to stock anytime using this tool https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108/page74
golastic said:
Sure Sir.....
https://mega.nz/#!8JNX3CwZ!PjSDO9c4mNWh5_ddKANmLNqLPRo7hyk_of5lAZThPUU
Click to expand...
Click to collapse
Something is up with your boot images, none can be unpacked.
Try flashing https://mega.nz/#!lhVTmbqQ!gIf4Tu4JC3pdzz-T7OAxi4wr3PQySkqdTgclkOkEU2E
Then re-root without rebooting.
Which root are you using by the way?
ante0 said:
Something is up with your boot images, none can be unpacked.
Try flashing https://mega.nz/#!lhVTmbqQ!gIf4Tu4JC3pdzz-T7OAxi4wr3PQySkqdTgclkOkEU2E
Then re-root without rebooting.
Which root are you using by the way?
Click to expand...
Click to collapse
Magisk 13.3 alongside superuser-r310-beta.zip
golastic said:
Magisk 13.3 alongside superuser-r310-beta.zip
Click to expand...
Click to collapse
Ah. Phh is probably why it won't unpack then.
I'm not sure then. If re-flashing B181 hw and public doesn't fix it, it's probably the boot image (seeing as regular camera apps don't work either something is up with the drivers).
I'd try with SuperSU/phh too or update to b182+ if possible and flash regular magisk 13.3, without phh.
ante0 said:
Ah. Phh is probably why it won't unpack then.
I'm not sure then. If re-flashing B181 hw and public doesn't fix it, it's probably the boot image (seeing as regular camera apps don't work either something is up with the drivers).
I'd try with SuperSU/phh too or update to b182+ if possible and flash regular magisk 13.3, without phh.
Click to expand...
Click to collapse
Thx sir but huawei firmware finder is only tell me current firmware to be C185B181.
Will be glad to link me to me 182 .
Thx
golastic said:
Thx sir but huawei firmware finder is only tell me current firmware to be C185B181.
Will be glad to link me to me 182 .
Thx
Click to expand...
Click to collapse
Correct. Latest is 181. I guess you could try installing Magisk, it will reboot instantly in twrp if it can't mount image as loop. 182+ is only because most firmware got loop support in 182. (First) B182 for C432 was released 12th of April and yours was released 24th of April, so it might work.
Or rebrand to C636.
golastic said:
Thx sir but huawei firmware finder is only tell me current firmware to be C185B181.
Will be glad to link me to me 182 .
Thx
Click to expand...
Click to collapse
New build for C185: B184.
It says BC185, but checking VERSION.mbn in update.zip confirms it's for C185:
MHA-L29C185B184
There was actually a B182 too for C185, released as BC185 too.
http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=MHA-L29BC185&firmware_page=0
ante0 said:
New build for C185: B184.
It says BC185, but checking VERSION.mbn in update.zip confirms it's for C185:
MHA-L29C185B184
There was actually a B182 too for C185, released as BC185 too.
http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=MHA-L29BC185&firmware_page=0
Click to expand...
Click to collapse
Can Install the firmware through Huawei finder apk and will it restore my camera please. I love my phone but without the camera working is makes my headache.
Have tried all u ask me by restoring stock boot loader and flashing superSu but the camera is still not working. It flashing :crying::crying::crying::crying:
golastic said:
Can Install the firmware through Huawei finder apk and will it restore my camera please. I love my phone but without the camera working is makes my headache.
Have tried all u ask me by restoring stock boot loader and flashing superSu but the camera is still not working. It flashing :crying::crying::crying::crying:
Click to expand...
Click to collapse
Before updating, have you tried restoring boot without rooting and see if that fixes camera?
Try this one, I removed verity and replaced fileencryption with encryptable so it doesn't encrypt your /data again.
https://mega.nz/#!lhE2zLSR!ngNY3bXKMS_eKizjmfnKHbFgVSVnp94dgCXnxuL_G_0
If it doesn't do anything, continue below.
Currently, https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Other ways are Firmware Finder or OTA, but both those require your IMEI to be approved for the update.
And Funky Huawei, which you need to pay for.
It will wipe /data when/if you decrypt again so make sure to make a backup of /data first, or backup apps with Titanium Backup or which backup app you use.
Basically download the Base zip, MHA zip and Windows or linux zip from https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Extract all to the same folder (hwota) and merge if it asks.
Then download:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1366/g104/v91627/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...hw_meafnaf/update_full_MHA-L29_hw_meafnaf.zip
http://update.hicloud.com:8180/TDS/...27/f1/full/public/update_data_full_public.zip
Put all in the "update" folder in the hwota folder you extracted before.
Rename update_full_MHA-L29_hw_meafnaf.zip to update_all_hw.zip
Rename update_data_full_public.zip to update_data_public.zip
Put phone in fastboot mode (download mode) and run update.bat (windows) or update.sh (linux)
Pick "Same brand update" when it asks, and "Script update directory".
When it's done your bootloader will be locked again so you need to unlock it if you want to root again.
You will be able to install regular Magisk 13.3 now without superuser (phh)
ante0 said:
Before updating, have you tried restoring boot without rooting and see if that fixes camera?
Try this one, I removed verity and replaced fileencryption with encryptable so it doesn't encrypt your /data again.
https://mega.nz/#!lhE2zLSR!ngNY3bXKMS_eKizjmfnKHbFgVSVnp94dgCXnxuL_G_0
If it doesn't do anything, continue below.
Currently, https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Other ways are Firmware Finder or OTA, but both those require your IMEI to be approved for the update.
And Funky Huawei, which you need to pay for.
It will wipe /data when/if you decrypt again so make sure to make a backup of /data first, or backup apps with Titanium Backup or which backup app you use.
Basically download the Base zip, MHA zip and Windows or linux zip from https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Extract all to the same folder (hwota) and merge if it asks.
Then download:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1366/g104/v91627/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...hw_meafnaf/update_full_MHA-L29_hw_meafnaf.zip
http://update.hicloud.com:8180/TDS/...27/f1/full/public/update_data_full_public.zip
Put all in the "update" folder in the hwota folder you extracted before.
Rename update_full_MHA-L29_hw_meafnaf.zip to update_all_hw.zip
Rename update_data_full_public.zip to update_data_public.zip
Put phone in fastboot mode (download mode) and run update.bat (windows) or update.sh (linux)
Pick "Same brand update" when it asks, and "Script update directory".
When it's done your bootloader will be locked again so you need to unlock it if you want to root again.
You will be able to install regular Magisk 13.3 now without superuser (phh)
Click to expand...
Click to collapse
Resolved the camera issue by following the last steps by flashing the 3 zip files......have unlocked bootloader and installed twrp 3.1.0.1 and trying to install magisk 13.3 but it always stuck at huawei logo.
Have also tried rooting but it seems only SuperSU2.82EMUI5noverityEnforcing works and do i need to follow the steps of formatting data to get it decyrpted?
Currently on MHA-L29C185B182 at the moment.
Thx @ante0 for your kind gesture.Appreciated
golastic said:
Resolved the camera issue by following the last steps by flashing the 3 zip files......have unlocked bootloader and installed twrp 3.1.0.1 and trying to install magisk 13.3 but it always stuck at huawei logo.
Have also tried rooting but it seems only SuperSU2.82EMUI5noverityEnforcing works and do i need to follow the steps of formatting data to get it decyrpted?
Currently on MHA-L29C185B182 at the moment.
Thx @ante0 for your kind gesture.Appreciated
Click to expand...
Click to collapse
My bad.
If you're using official Magisk 13.3, that's why it's not booting. Since your data partition is encrypted, and Magisk removes the encryption flag, it tries to boot without decrypting. So it ends in a boot loop.
Use this: https://mega.nz/#!I4FQzbyA!gBZelHmD3lGGwzGISUXkf7GQTUAq5i785d_qPHQOaVE (this one just doesn't force remove encryption)
Or decrypt first, then flash HW and Public and official Magisk 13.3.
But yes, to decrypt you need to format data.
ante0 said:
My bad.
If you're using official Magisk 13.3, that's why it's not booting. Since your data partition is encrypted, and Magisk removes the encryption flag, it tries to boot without decrypting. So it ends in a boot loop.
Use this: https://mega.nz/#!I4FQzbyA!gBZelHmD3lGGwzGISUXkf7GQTUAq5i785d_qPHQOaVE (this one just doesn't force remove encryption)
Or decrypt first, then flash HW and Public and official Magisk 13.3.
But yes, to decrypt you need to format data.
Click to expand...
Click to collapse
Is there another way of flashing the 3 zip files without running through pc cuz i dont know whats happening. Am done with with everything working with Magisk and data encrypted but what i have realised this around is my development option is not working along with debugging mode. Also am not able to install apk aside from playstore....Due to that adb in command prompt is not working cuz debugging mode is disables.
In fastboot mode am only able to check device status and reboot device.Id you send a commnd to flash an image it response failed....
golastic said:
Is there another way of flashing the 3 zip files without running through pc cuz i dont know whats happening. Am done with with everything working with Magisk and data encrypted but what i have realised this around is my development option is not working along with debugging mode. Also am not able to install apk aside from playstore....Due to that adb in command prompt is not working cuz debugging mode is disables.
In fastboot mode am only able to check device status and reboot device.Id you send a commnd to flash an image it response failed....
Click to expand...
Click to collapse
If you can't get in to dev options, wipe dalvik/art & cache in twrp, it could fix playstore as well.
If you can't enable adb, try enable disable a few times and remove USB cable between. I always have to do that the first time.
You can actually do everything from twrp to install firmware. But you'd have to check the hwota.sh file for commands... There are a few you must execute.
And is camera working now again?
ante0 said:
Before updating, have you tried restoring boot without rooting and see if that fixes camera?
Try this one, I removed verity and replaced fileencryption with encryptable so it doesn't encrypt your /data again.
https://mega.nz/#!lhE2zLSR!ngNY3bXKMS_eKizjmfnKHbFgVSVnp94dgCXnxuL_G_0
If it doesn't do anything, continue below.
Currently, https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Other ways are Firmware Finder or OTA, but both those require your IMEI to be approved for the update.
And Funky Huawei, which you need to pay for.
It will wipe /data when/if you decrypt again so make sure to make a backup of /data first, or backup apps with Titanium Backup or which backup app you use.
Basically download the Base zip, MHA zip and Windows or linux zip from https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Extract all to the same folder (hwota) and merge if it asks.
Then download:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1366/g104/v91627/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...hw_meafnaf/update_full_MHA-L29_hw_meafnaf.zip
http://update.hicloud.com:8180/TDS/...27/f1/full/public/update_data_full_public.zip
Put all in the "update" folder in the hwota folder you extracted before.
Rename update_full_MHA-L29_hw_meafnaf.zip to update_all_hw.zip
Rename update_data_full_public.zip to update_data_public.zip
Put phone in fastboot mode (download mode) and run update.bat (windows) or update.sh (linux)
Pick "Same brand update" when it asks, and "Script update directory".
When it's done your bootloader will be locked again so you need to unlock it if you want to root again.
You will be able to install regular Magisk 13.3 now without superuser (phh)
Click to expand...
Click to collapse
ante0 said:
If you can't get in to dev options, wipe dalvik/art & cache in twrp, it could fix playstore as well.
If you can't enable adb, try enable disable a few times and remove USB cable between. I always have to do that the first time.
You can actually do everything from twrp to install firmware. But you'd have to check the hwota.sh file for commands... There are a few you must execute.
And is camera working now again?
Click to expand...
Click to collapse
Yes Camera is working good and it looks like they have added a new feature in the camera app for b182 called MOVING PICTURE which add sound whiles you capture.I use to love that when i was using S5.
Now after careful observation about the instruction u gave me,am able to install B182 ,have decyrpted data ,have magisk 13.3 running without any issue.
I jux wanna say thanks so much for your patience with me...Much appreciated:good::good::good::good::good:
BTW which of the models will u recommend if want to rebrand?:

Categories

Resources