Database Develop

roms wont flash

im not sure if this has happen to anyone else but its has happen to my several times on 2 different roms i downloaded farias aku3.3 and pdaviet 4 once i extract these files i dont get a icon for the installer like other roms i have downloaded i get i folder with about 4 files in it. i try to click the files and i get the same thing everytime not a valid win 32 application. can anyone please help figure out what to do about this? i only get this problem with rar files every file that i download that was a zip file worked fine. thanks

glennh627 said:
im not sure if this has happen to anyone else but its has happen to my several times on 2 different roms i downloaded farias aku3.3 and pdaviet 4 once i extract these files i dont get a icon for the installer like other roms i have downloaded i get i folder with about 4 files in it. i try to click the files and i get the same thing everytime not a valid win 32 application. can anyone please help figure out what to do about this? i only get this problem with rar files every file that i download that was a zip file worked fine. thanks
Click to expand...
Click to collapse
Check to make sure that it is an "original" ROM not a retweaked one. I haven't had the problem you describe.
--M

glennh627 said:
im not sure if this has happen to anyone else but its has happen to my several times on 2 different roms i downloaded farias aku3.3 and pdaviet 4 once i extract these files i dont get a icon for the installer like other roms i have downloaded i get i folder with about 4 files in it. i try to click the files and i get the same thing everytime not a valid win 32 application. can anyone please help figure out what to do about this? i only get this problem with rar files every file that i download that was a zip file worked fine. thanks
Click to expand...
Click to collapse
what are you using to decompress the RAR? and when was the last time you updated it? I use WinRAR and have no issues. If you have a recent (last couple years or so ) copy of WinRAR and are still experiencing this then you probably got a bad or incomplete download -- How big is the file?

i have winrar as well and the files are about 60 mbs and 50mbs

Converting L09 to UL00

Hi,
I followed the instructions to convert L09 to Middle Eastern & North and South Africa version and it all worked well for me, but I'm wondering how do I convert to Chinese version? Can anyone help with some information?
Like do i just need to edit the build.prop and have the correct regions update.app file? or is something else necessary.
Thanks in advance
Gavin

brumgav said:
Hi,
I followed the instructions to convert L09 to Middle Eastern & North and South Africa version and it all worked well for me, but I'm wondering how do I convert to Chinese version? Can anyone help with some information?
Like do i just need to edit the build.prop and have the correct regions update.app file? or is something else necessary.
Thanks in advance
Gavin
Click to expand...
Click to collapse
So I managed to convert to Chinese version. This is how I did it.
While fresh in the memory, instructions on how to change the region+ firmware to UL00
What do you need (links in 004's original post earlier in the thread or here:
1. Firmware UL00-C433B114 (Middle East, North and South Africa)
2. The oeminfo.img program to change the locale (45.69 KB) Anti-Virus may or complain, so disable it)
3. Mounted on the phone ES Explorer (Solid or Root Explorer will not work !!!)
4. You need a copy of your existing ROM versions recovery.img. You can get this using the Huawei ROM extractor tool.
What to do:
1. Flash TWRP Recovery through Fastboot (Bootloader must be unlocked)
2..Get Root (install SuperSU.zip through TWRP), reboot.
3. Install and enable root in settings of ES Explorer and go to the folder /dev/block/platform/hi_mci.0/by-name/
4. Copy oeminfo file and transfer it to your computer
5. On your computer, unpack the oeminfo.exe program from the RAR. Put your oeminfo file in the same folder.
6. Rename oeminfo in oeminfo.img
7. Run oeminfo.img.exe and type hw / meafnaf replacing dualcu / cn - click apply
8. Rename oeminfo.img back to oeminfo and copy to your mobile phone
9. Replace the original file in the phone to change (overwrite)
10. Go to the phone / system / and open the file build.prop
11. Find the line ro.build.displey.id = change your version to "=" CRR-UL00C433B000 and save changes
EDIT ?: These steps (10/11) MUST be completed or it will not allow you to update later with new regions ROM
12. Extract the new ROM file on your computer with the firmware.
13. Copy dload folder with the Update.app file and copy it to the phone's internal memory or MicroSD card
14. Flash back stock recovery from your existing ROM (use the extractor tool if needed). You can do this now or at the end before flashing but you must remove TWRP and ROOT before attempting to flash new rom.
15. On the phone go Settings - Update.
16. Select Menu - Local update
I then ensured Google Play was installed.
After doing this, flashed TWRP again and Rooted the phone, I then edited the oeminfo file using the above method, changing the attribute back to "dualcu/cn". After this I edited the build.prop to using the above method but this time I changed "ro.build.display.id=CRR-UL00C00B131".
I then removed root and flashed the original Huawei recovery, and then rebooted and went to update settings. I searched for update and a new file was found however a modified system was detected so it offered to download a full version which was the B160 build. This downloaded and then updated and now I have CRR-UL00C00B160 version

Whats the advantage of this Version?

There are more updates to the Chinese version..they are on build B160 whereas UK still on build B144.
Some other features like dual SIM should work however I haven't tested this.
Other things like build in virus scanner, permissions manager and also the ability to set the date of your mobile data plan to help keep track of data usage and allowance.
Pressure sensitive screen is also featured although not yet used in any apps but maybe it will be enabled soon by Huawei

brumgav said:
So I managed to convert to Chinese version. This is how I did it.
While fresh in the memory, instructions on how to change the region+ firmware to UL00
What do you need (links in 004's original post earlier in the thread or here:
1. Firmware UL00-C433B114 (Middle East, North and South Africa)
2. The oeminfo.img program to change the locale (45.69 KB) Anti-Virus may or complain, so disable it)
3. Mounted on the phone ES Explorer (Solid or Root Explorer will not work !!!)
4. You need a copy of your existing ROM versions recovery.img. You can get this using the Huawei ROM extractor tool.
What to do:
1. Flash TWRP Recovery through Fastboot (Bootloader must be unlocked)
2..Get Root (install SuperSU.zip through TWRP), reboot.
3. Install and enable root in settings of ES Explorer and go to the folder /dev/block/platform/hi_mci.0/by-name/
4. Copy oeminfo file and transfer it to your computer
5. On your computer, unpack the oeminfo.exe program from the RAR. Put your oeminfo file in the same folder.
6. Rename oeminfo in oeminfo.img
7. Run oeminfo.img.exe and type hw / meafnaf replacing dualcu / cn - click apply
8. Rename oeminfo.img back to oeminfo and copy to your mobile phone
9. Replace the original file in the phone to change (overwrite)
10. Go to the phone / system / and open the file build.prop
11. Find the line ro.build.displey.id = change your version to "=" CRR-UL00C433B000 and save changes
EDIT ?: These steps (10/11) MUST be completed or it will not allow you to update later with new regions ROM
12. Extract the new ROM file on your computer with the firmware.
13. Copy dload folder with the Update.app file and copy it to the phone's internal memory or MicroSD card
14. Flash back stock recovery from your existing ROM (use the extractor tool if needed). You can do this now or at the end before flashing but you must remove TWRP and ROOT before attempting to flash new rom.
15. On the phone go Settings - Update.
16. Select Menu - Local update
I then ensured Google Play was installed.
After doing this, flashed TWRP again and Rooted the phone, I then edited the oeminfo file using the above method, changing the attribute back to "dualcu/cn". After this I edited the build.prop to using the above method but this time I changed "ro.build.display.id=CRR-UL00C00B131".
I then removed root and flashed the original Huawei recovery, and then rebooted and went to update settings. I searched for update and a new file was found however a modified system was detected so it offered to download a full version which was the B160 build. This downloaded and then updated and now I have CRR-UL00C00B160 version
Click to expand...
Click to collapse
Hello, could you please tell me why do you write (type) in step 11. CRR-UL00C433B000 instead of CRR-UL00C433B114? Thanks for your answer.

MoritzSu said:
Hello, could you please tell me why do you write (type) in step 11. CRR-UL00C433B000 instead of CRR-UL00C433B114? Thanks for your answer.
Click to expand...
Click to collapse
you need to set your build.id to B000 so you can update to B114 with an full update package in the EMUI Update app

Tuerkay said:
you need to set your build.id to B000 so you can update to B114 with an full update package in the EMUI Update app
Click to expand...
Click to collapse
Thanks for your soon answer. To say the truth, i have just completed the process. Unfortunately, i wrote (in my case) CRR-L09C432B114 instead of CRR-L09C432B000; my device ist just running with this B114 Rom. I was running the B119 Rom before, what should i do now in order to receive the updates?

MoritzSu said:
Thanks for your soon answer. To say the truth, i have just completed the process. Unfortunately, i wrote (in my case) CRR-L09C432B114 instead of CRR-L09C432B000; my device ist just running with this B114 Rom. I was running the B119 Rom before, what should i do now in order to receive the updates?
Click to expand...
Click to collapse
if you have changed your localization ( the "Cxxx" part) then you won´t receive any updates. You have to manualy update via Update.APP files.
Your IMEI is linked to you Build/Localization. This way, Huawei makes sure that every phone receives the right update file. If you change one of both, you won´t receive OTA updates anymore, since the update system can´t assign the "right" update file.

Anyone can confirm the dual sim function work after this procedure?? This I want a dual sim active dfsa

it does not, EU Mate S does not have dual-dim hardware

brumgav said:
7. Run oeminfo.img.exe and type hw / meafnaf replacing dualcu / cn - click apply
Click to expand...
Click to collapse
Anybody know, where to get this information from?
if I want to change to any other region where can I find the correct information for the OEMINFO.IMG?

Sventastic said:
Anybody know, where to get this information from?
if I want to change to any other region where can I find the correct information for the OEMINFO.IMG?
Click to expand...
Click to collapse
Sorry I don't know

Please share file oeminfo Dual Sim CRR-UL00 any region (hw/meafnaf or dualcu/cn)

Correct Xposed for Nexus 6?

I'm on Resurrection Remix Lollipop if that makes a difference.

Architecture is Arm, sdk22 (if android 5.1) version (latest as of this post) 85. As far as your ROM, some ROMs do experience issues with xPosed, I don't think that resurrection is one though

Thank you, I found the correct zip to flash with TWRP. But now I can't get the correct apk file. When I download the apk from the official thread it comes in .zip format and not .apk.

enginuity2 said:
Thank you, I found the correct zip to flash with TWRP. But now I can't get the correct apk file. When I download the apk from the official thread it comes in .zip format and not .apk.
Click to expand...
Click to collapse
Seems to be an issue with your browser. Try another one or head over to the Material Design Xposed Installer thread. It's the same as the official one, but with material design.

enginuity2 said:
Thank you, I found the correct zip to flash with TWRP. But now I can't get the correct apk file. When I download the apk from the official thread it comes in .zip format and not .apk.
Click to expand...
Click to collapse
All you need to do when it does this is rename .zip to .apk then it'll work

Noble Nougat Experience 1.2 Sim Card not working (HELP)

I recently installed the Noble Nougat Experience 1.2 rom on my galaxy s6 tmobile variant. Unfortunately the rom cannot recognize my sim card. Is there any way to fix this?

you can flash another rom, which is also based on android 7.0
I have tested on my G920T, and SIM card is working, the only problem is the battery is terrible.

The only nougot room with the kernel for our device is nemesis rom

That rom have the same problem and calle audio too

Nazury said:
That rom have the same problem and calle audio too
Click to expand...
Click to collapse
The version 3.1 has solved this problem.

I extracted both the Nemesis rom and Noble nougat. Copied Noble system to Nemesis, deleting the one origanily in Nemesis. Zipped back up and now running Noble with Nemesis kernel. I have debloated and have no battery issues. No issues at all that I have encountered.
EDIT: I forgot. only issue is when changing screen resolution which is known.

s89281b said:
I extracted both the Nemesis rom and Noble nougat. Copied Noble system to Nemesis, deleting the one origanily in Nemesis. Zipped back up and now running Noble with Nemesis kernel. I have debloated and have no battery issues. No issues at all that I have encountered.
EDIT: I forgot. only issue is when changing screen resolution which is known.
Click to expand...
Click to collapse
can you tell me what should i replace from Noble to Nemesis in detail. THX

Noble Rom is about to be updated this weekend with support for T-Mobile. I would just wait for the update. But if you don't want to wait. Once you have extracted both ROMs. Take the folder named Dream from Noble and copy it to Nemisis. Delete system folder from Nemisis and then rename Dream to system. Archive the Rom and flash as usual.

s89281b said:
Noble Rom is about to be updated this weekend with support for T-Mobile. I would just wait for the update. But if you don't want to wait. Once you have extracted both ROMs. Take the folder named Dream from Noble and copy it to Nemisis. Delete system folder from Nemisis and then rename Dream to system. Archive the Rom and flash as usual.
Click to expand...
Click to collapse
yesterday, I already did this as what you say, but when i flash the new mixed rom, but failed with "the zip file is invalid "
anyway thx a lot. I will wait for the Noble Rom.

semory said:
yesterday, I already did this as what you say, but when i flash the new mixed rom, but failed with "the zip file is invalid "
anyway thx a lot. I will wait for the Noble Rom.
Click to expand...
Click to collapse
Are you extracting/archiving on phone or computer? I did on phone using Root Explorer. Some other apps I have tried fail to properly extract/archive.

s89281b said:
I extracted both the Nemesis rom and Noble nougat. Copied Noble system to Nemesis, deleting the one origanily in Nemesis. Zipped back up and now running Noble with Nemesis kernel. I have debloated and have no battery issues. No issues at all that I have encountered.
EDIT: I forgot. only issue is when changing screen resolution which is known.
Click to expand...
Click to collapse
I did exactly what you did it and it worked great. One question though: I noticed by doing this method you do not get the edge features that come with either of the roms alone. Do you know of a way to get that? Thank you.

hshafi said:
I did exactly what you did it and it worked great. One question though: I noticed by doing this method you do not get the edge features that come with either of the roms alone. Do you know of a way to get that? Thank you.
Click to expand...
Click to collapse
I upgraded to Noble 2.0. I don't use edge panel but I installed to test for you and it is working. But it was reported that TMO was still not working in 2.0 so instead of moving the new system to Nemisis I moved Nemisis kernel boot.img and TMO fix folder to Noble.
Edit: Edge panel is installed using aroma which is another reason to move to Noble instead of Nemisis.

s89281b said:
I upgraded to Noble 2.0. I don't use edge panel but I installed to test for you and it is working. But it was reported that TMO was still not working in 2.0 so instead of moving the new system to Nemisis I moved Nemisis kernel boot.img and TMO fix folder to Noble.
Edit: Edge panel is installed using aroma which is another reason to move to Noble instead of Nemisis.
Click to expand...
Click to collapse
There are multiple boot.img files within the nemesis zip file. Would all be required or is there a specific one that is necessary to work for T-mobile?

hshafi said:
There are multiple boot.img files within the nemesis zip file. Would all be required or is there a specific one that is necessary to work for T-mobile?
Click to expand...
Click to collapse
Just the one for your model. boots6etmo.img=edge. boots6ftmo.img=flat. Be sure to rename the files to the same as files they are replacing.

s89281b said:
I upgraded to Noble 2.0. I don't use edge panel but I installed to test for you and it is working. But it was reported that TMO was still not working in 2.0 so instead of moving the new system to Nemisis I moved Nemisis kernel boot.img and TMO fix folder to Noble.
Edit: Edge panel is installed using aroma which is another reason to move to Noble instead of Nemisis.
Click to expand...
Click to collapse
Confirmed to be working flawlessly on G920T (XAR). :highfive: Curious whether this would also work on the Golden Griffin ROM

s89281b said:
I upgraded to Noble 2.0. I don't use edge panel but I installed to test for you and it is working. But it was reported that TMO was still not working in 2.0 so instead of moving the new system to Nemisis I moved Nemisis kernel boot.img and TMO fix folder to Noble.
Edit: Edge panel is installed using aroma which is another reason to move to Noble instead of Nemisis.
Click to expand...
Click to collapse
I install the Noble 2.0 ，but with the problem that the app of "phone" loading very slowly and system FC. Now i back to the offical ROM with T-Mobile.:crying: Tired

semory said:
I install the Noble 2.0 ，but with the problem that the app of "phone" loading very slowly and system FC. Now i back to the offical ROM with T-Mobile.:crying: Tired
Click to expand...
Click to collapse
Download Nemesis ROM 3.1 and Noble ROM 2.0, decompile on your computer, copy the Nemesis boot image and T-mobile files to the Noble folder, recompile the Noble folder on your phone using Root Explorer, full wipe and flash the recompiled zip, and there you go
Everything works perfectly smooth

s89281b said:
I upgraded to Noble 2.0. I don't use edge panel but I installed to test for you and it is working. But it was reported that TMO was still not working in 2.0 so instead of moving the new system to Nemisis I moved Nemisis kernel boot.img and TMO fix folder to Noble.
Edit: Edge panel is installed using aroma which is another reason to move to Noble instead of Nemisis.
Click to expand...
Click to collapse
Can u please tell me the steps how u did ?did u do it with root Explorer can u tell me in details thanks.

azezamere said:
Can u please tell me the steps how u did ?did u do it with root Explorer can u tell me in details thanks.
Click to expand...
Click to collapse
Using Root Explorer I extracted Nemesis v3.1 and Noble 2.0. Then go to extracted folder( stock location is speedsoftware/extracted). From Nemesis you want to copy the following files, nemesis/kernel/TMO_FIX and the boot.img file for your device. (boots6etmo.img=edge)(boots6ftmo.img=flat) You want to put TMO_FIX in Noble folder. You will see a folder named T-Mobile. Delete it and rename TMO_FIX to T-Mobile. Then put your boot.img in Noble/Kernels/920_TMobile if you have flat or 925_TMobile if you have edge. Delete the original boot.img file and rename one frome Nemesis to boot.img. Go back and archive the Noble Rom. You should get a folder in Speedsoftware/Archives tiltled Noble_Nougat_Experience_2.0.zip. This is what you will flash in recovery. Be sure to do a clean install.

s89281b said:
Using Root Explorer I extracted Nemesis v3.1 and Noble 2.0. Then go to extracted folder( stock location is speedsoftware/extracted). From Nemesis you want to copy the following files, nemesis/kernel/TMO_FIX and the boot.img file for your device. (boots6etmo.img=edge)(boots6ftmo.img=flat) You want to put TMO_FIX in Noble folder. You will see a folder named T-Mobile. Delete it and rename TMO_FIX to T-Mobile. Then put your boot.img in Noble/Kernels/920_TMobile if you have flat or 925_TMobile if you have edge. Delete the original boot.img file and rename one frome Nemesis to boot.img. Go back and archive the Noble Rom. You should get a folder in Speedsoftware/Archives tiltled Noble_Nougat_Experience_2.0.zip. This is what you will flash in recovery. Be sure to do a clean install.
Click to expand...
Click to collapse
Thank you so much I appreciate it.

Samung Galaxy Tab S2 T819 Bootloader T819xxu2brb2

Hey,
i cant install LineageOS, cuz when im in TWRP it says the Package i tried to install is only for other Bootloader versions
my Version is T819xxu2brb2

Obstkartoffel said:
Hey,
i cant install LineageOS, cuz when im in TWRP it says the Package i tried to install is only for other Bootloader versions
my Version is T819xxu2brb2
Click to expand...
Click to collapse
Until officially fixed:
Open the newest version, like lineage-15.1-20180313_142801-UNOFFICIAL-gts210velte.zip
Go to: \META-INF\com\google\android\ and there extract updater-script
Open with Notepad++. Starting on line 2 you can see all supported loaders. Modify one of them to yours. Save and move back to the zip file overwriting the current file.
DONE.

emuandco said:
Until officially fixed:
Open the newest version, like lineage-15.1-20180313_142801-UNOFFICIAL-gts210velte.zip
Go to: \META-INF\com\google\android\ and there extract updater-script
Open with Notepad++. Starting on line 2 you can see all supported loaders. Modify one of them to yours. Save and move back to the zip file overwriting the current file.
DONE.
Click to expand...
Click to collapse
Im always getting Error 7.. tried to wipe data, dalvik and cache.. nothing works.. some tips?
E: found the issue, forgot to change getprop, just changed the other bootloader infos... *facepalm*