This method is useful if you're unable to change your CSC in multi-csc roms. Or if you don't have the desired CSC for Note FE, this tutorial will assist you to change with the best way.
1) Get the sec_csc.zip from other device that have your CSC as DEFAULT csc
Download other device's firmware here, note that newer devices like Note 8 doesn't have CSC system. Best way is to use S7 Edge files. Android version doesn't matter.
After downloading, extract the zip file. You should have 4-5 files inside folder. Pick one that starting with HOME_CSC or CSC. It doesn't matter. If you have 1 file rom, pick that file. Change file extension from tar.md5 to tar. Open the file with your desired archive manager application. Copy "cache.img" or "cache.img.lz4" out of the archive depending on what you have. You now need to decompress lz4 file if you have lz4 file. Use this link if you have Windows. For other OS'es do your own research.
Now you got the cache.img. Extract the files inside it. These links might help to extract cache.img, if you have another OS, use tool named "simg2img" and a tool to mount or extract img file as ext4. I'm leaving these kitchen links to extract cache.img.
https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
https://forum.xda-developers.com/ch...-android-roms-editor-assayyedkitchen-t3410545
Get "sec_csc.zip" in the "recovery" folder, if you don't have this file, try extracting this from another ROM. Open the zip file, and take a look inside it. In the "system/csc" folder there's a file named "sales_code.dat". Open this file with text viewer, and check if this sales code matches with your desired one. If it doesn't match, try extracting sec_csc.zip with desired sales code from another ROM. Don't try to edit this file, if you don't have a custom recovery or if you don't want to experiment it as I didn't try it.
2) Get platform-tools (SKIP THIS if you will use SD-Card for installation. USE Only if you don't have SD-Card or don't want to install with SD-Card)
Download platform-tools from Google. You will use adb sideload to install the zip. Check 3rd step for further information.
3) Installation (READ THIS even if you know about flashing ZIPs or you will probably fail, this part is the most important part of this tutorial)
Reboot into recovery
Wipe data
Install zip (sec_csc.zip) using SD-Card or ADB-Sideload
Your device will reboot and change the sales code to default one in the sec_csc.zip that you flashed.
4) Reflash official ROM (ONLY IF your CSC is in one of the official ROMS for your device with your desired Android version) using ODIN.
I won't be explaining this in detail. If you don't know do your research. Just take 4-5 files rom and select AP BL CP CSC (i'd prefer to not select HOME_CSC) in the appropriate places. If you aren't expert make sure that you don't tick the Re-Partition, nand erase etc. and don't select PIT file while flashing.
Hi, thanks for your guide
I just wannt confirm the SS Pay will work with that replacing CSC?
Google+ said:
Hi, thanks for your guide
I just wannt confirm the SS Pay will work with that replacing CSC?
Click to expand...
Click to collapse
If your region supports, it probably will.
No need to wipe data. However, if you have a Multi-CSC, it won't work that easy from firmware ARA1 and on, due to new security measures. You will then need either root or the combination firmware.
Hello. Thanks to add the credits. The first one who made this trick is me [emoji6]
Envoyé de mon SM-N935F en utilisant Tapatalk
treysis said:
No need to wipe data. However, if you have a Multi-CSC, it won't work that easy from firmware ARA1 and on, due to new security measures. You will then need either root or the combination firmware.
Click to expand...
Click to collapse
If you don't wipe data, sales code won't change, and this is the suggested method provided by Samsung. Without wipe, changes weren't persistent for me, they disappeared after wiping cache.
benyou54 said:
Hello. Thanks to add the credits. The first one who made this trick is me [emoji6]
Envoyé de mon SM-N935F en utilisant Tapatalk
Click to expand...
Click to collapse
All credits to Samsung, that's how CSC installation works. And I didn't see any tutorial for changing "sales" code, found it by trying. All I wanted was to switch to TUR csc on KSA rom, it has OJV csc which contains TUR. Got it after changing my sales code and reflashing the original rom. Everywhere suggests insert sim and wipe data, or some *#code etc which doesn't work anymore. And it's stupid idea to downgrade for that csc change code even if possible.
Madness. said:
All credits to Samsung, that's how CSC installation works. And I didn't see any tutorial for changing "sales" code, found it by trying. All I wanted was to switch to TUR csc on KSA rom, it has OJV csc which contains TUR. Got it after changing my sales code and reflashing the original rom. Everywhere suggests insert sim and wipe data, or some *#code etc which doesn't work anymore. And it's stupid idea to downgrade for that csc change code even if possible.
Click to expand...
Click to collapse
This process is not from Samsung. Samsung does not allow that kind of csc change. Now after the january security update, the only way to change the csc code for the multi CSC, it's to use the combination firmware used in the factory process to test.
If you used a single carrier csc, you don't need to factory reset your FE to change the sale code.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Envoyé de mon SM-N935F en utilisant Tapatalk
can i change korean CSC from N935k to another country CSC?
energizer said:
can i change korean CSC from N935k to another country CSC?
Click to expand...
Click to collapse
It should work for any Samsung phone with CSC system.
benyou54 said:
This process is not from Samsung. Samsung does not allow that kind of csc change. Now after the january security update, the only way to change the csc code for the multi CSC, it's to use the combination firmware used in the factory process to test.
If you used a single carrier csc, you don't need to factory reset your FE to change the sale code. View attachment 4501524
Envoyé de mon SM-N935F en utilisant Tapatalk
Click to expand...
Click to collapse
Well, that's how CSC gets loaded into system. It's in cache image, it gets flashed after firmware update. Wiping data yields more reliable results, but I wouldn't mind it if I had lots of data on my phone. Looks like you still didn't get the point though, this tutorial is for changing "sales code", not only "csc"
Madness. said:
It should work for any Samsung phone with CSC system.
Click to expand...
Click to collapse
if I change korean csc, is there a chance that I will earn volte and s pay?
Madness. said:
this tutorial is for changing "sales code", not only "csc"
Click to expand...
Click to collapse
What's the difference between CSC and sales code?
energizer said:
if I change korean csc, is there a chance that I will earn volte and s pay?
Click to expand...
Click to collapse
Yes, you should try it. It will probably work.
treysis said:
What's the difference between CSC and sales code?
Click to expand...
Click to collapse
Sales code is simply your device's country code. It determines your active CSC if your CSC package has that files. Otherwise ROM tries to set it to default CSC of installed CSC. If you want to make sure that changes are more "persistent", follow the tutorial. Otherwise, just flash the sec_csc.zip, changes might be lost after wiping cache or data.
Hm, benyou54 changed his sales code without factory reset. But he is still on older bootloader. I am on January patch and my sales code is XME, though active CSC is VIA from my sec_csc.zip.
treysis said:
Hm, benyou54 changed his sales code without factory reset. But he is still on older bootloader. I am on January patch and my sales code is XME, though active CSC is VIA from my sec_csc.zip.
Click to expand...
Click to collapse
I did the experiments with latest version (Oreo) with KSA package. Older versions might have different behavior.
Madness. said:
I did the experiments with latest version (Oreo) with KSA package. Older versions might have different behavior.
Click to expand...
Click to collapse
I see. But if I understand correctly, you can only change sales code to the default one of the CSC, not just any code you like, correct?
treysis said:
I see. But if I understand correctly, you can only change sales code to the default one of the CSC, not just any code you like, correct?
Click to expand...
Click to collapse
Yes. It will set to sec_csc.zip's default one.
Hi, I tried on my S9+ with csc from S7 Edge but signature verification failed when flashing zip file.
Related
All,
Please be aware of this. Flashing a compiled lollipop AOSP ROM may break your recovery. Actually, although I expect it - maybe you wont - but also factory images do this)
Zips may contain the following files:
/system/recovery.init.boot.p
/system/bin/install-recovery.sh
One is a recovery patch and the other is a script to run on boot and patch your recovery. If you flash a lollipop AOSP ROM and boot immediately, if these exist, your recovery will break.
Flashing superSU immediately after the ROM should
prevent the issue as that replaces /system/bin/install-recovery.sh with its own /system/etc/install-recovery.sh used to call root.
It may just be better for everyone to remove those from the zips before flashing (or uploading) though. If your bootloader is unlocked, you're OK, you can just fastboot flash your recovery back. However if its locked, you'll waste hours backing up your sdcard, preparing to unlock your bootloader and wipe the device, so beware and be careful
Dan
Thanks for heads up
Lukijs said:
Thanks for heads up
Click to expand...
Click to collapse
No probs.
Thanks bro ?
Gesendet von meinem Nexus 5
Do you mean flashing the ones built as zips or any?
Sent from my Android 5.0 Nexus 5
Ben36 said:
Do you mean flashing the ones built as zips or any?
Sent from my Android 5.0 Nexus 5
Click to expand...
Click to collapse
Anything not a dev preview. Just check the zip before flashing. If its a zip that contains .DAT archives, you can check from TWRP file manager after flash.
Although official may also have this one released. Not sure. Maybe just the OTA as some of the compiled ROMs seem to be using the OTA method instead of user debug or user method.
You mean something like this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AA1973 said:
You mean something like this?
Click to expand...
Click to collapse
Yep. Unless whomever compiled that changed the make to exclude those files, they'll be there. It shouldn't be a problem for most who will immediately flash superSU. Its just for anyone who attempts to boot before flashing superSU as the scripts run at boot then delete themselves.
Anyone not wanting root but wanting to keep recovery, you can check and delete the files using the recovery file manager (philz or TWRP) once flashed. Just don't boot until you do. The problem with the OTA zip is the .DAT files are harder to analyse unlike a normal zip.
Multi Rom decided to intervene by cancelling the boot up process, although I had flashed SuperSU.
Can we replace the stock recovery by TWRP.img and then flashall.bat ?
Envoyé de mon Nexus 5 en utilisant Tapatalk
Thanks
Oh - I'm so happy that I flashed SU right after the ROM... ;p
Ah well, unlocked bootloader anyways, but still good to know.
---------- Post added at 10:03 AM ---------- Previous post was at 09:59 AM ----------
vercety974 said:
Can we replace the stock recovery by TWRP.img and then flashall.bat ?
Envoyé de mon Nexus 5 en utilisant Tapatalk
Click to expand...
Click to collapse
Does the flashall.bat include a line : fastboot flash recovery recovery.img?
You can check by opening the bat file in notepad..
If it has, then no. Well yes, but it will overwrite your current recovery again.
vercety974 said:
Can we replace the stock recovery by TWRP.img and then flashall.bat ?
Envoyé de mon Nexus 5 en utilisant Tapatalk
Click to expand...
Click to collapse
You could if their flash all includes a recovery. I'm not sure about AOSP ROMs generated as full images. The patch I have seen comes from building AOSP from source and distributing the resultant ota package (which is a full rom)
Stock ROMs have this feature, it's nothing new.
Rusty! said:
Stock ROMs have this feature, it's nothing new.
Click to expand...
Click to collapse
Stock OTA zips have this feature. Factory images do not, yet that is irrelevant. The point here is that compiled AOSP ROMs should not be distributed as OTA packages, yet here we are, with rushed, ill-conceived builds causing this issue. This is new for AOSP flashable zips. I've been flashing AOSP since cupcake and its definitely new to me and since others have fallen in to this trap, let's assume its new to them too.
Yes, factory images do have this.
Rusty! said:
Yes, factory images do have this.
Click to expand...
Click to collapse
No, They have then shell script. Not the patch file.
..and from the thread title. Again - I remind you that it is irrelevant
I found this line(/system/bin/install-recovery.sh) in file_contexts, is it where i need to delete it?
jonathanxx1 said:
I found this line(/system/bin/install-recovery.sh) in file_contexts, is it where i need to delete it?
Click to expand...
Click to collapse
If you have file_contexts then you are flashing a .DAT OTA. You can't get to the files until you flash the ROM. Flashing the ROM unpacks the .DAT archives into /system at which point, you could use a recovery based file manager or adb to delete the 2 files mentioned in post 1. This is assuming you're not going to root it. If you root it, you *should* be OK but sometimes its best to be safe than sorry.
rootSU said:
Stock OTA zips have this feature. Factory images do not, yet that is irrelevant. The point here is that compiled AOSP ROMs should not be distributed as OTA packages, yet here we are, with rushed, ill-conceived builds causing this issue. This is new for AOSP flashable zips. I've been flashing AOSP since cupcake and its definitely new to me and since others have fallen in to this trap, let's assume its new to them too.
Click to expand...
Click to collapse
I just extracted the factory system.img of the 3rd revision of the L Preview, and it has both files mentioned in the OP.
Also, saying that compiled AOSP ROMs should not be distributed as OTA packages is not true. This has been done since this feature has been available.
I just finished building Lollipop for the first time. The files mentioned in the OP are not present in the out/target/product/hammerhead/system folder, or any other folder that I can find. Can't confirm if they are in the system.new.dat file, or after flashing since I haven't flashed it yet (maybe tomorrow). Hopefully there is an option to build a folder-based zip instead of these .dat files.
Scripts that install recovery have never been an issue unless a recovery.img is present in the zip, or there is a backup cached in a partition. Maybe that has changed. This will be figured out soon enough.
Still good advice to flash supersu before booting until this is understood.
upndwn4par said:
I just extracted the factory system.img of the 3rd revision of the L Preview, and it has both files mentioned in the OP.
Also, saying that compiled AOSP ROMs should not be distributed as OTA packages is not true. This has been done since this feature has been available.
I just finished building Lollipop for the first time. The files mentioned in the OP are not present in the out/target/product/hammerhead/system folder, or any other folder that I can find. Can't confirm if they are in the system.new.dat file, or after flashing since I haven't flashed it yet (maybe tomorrow). Hopefully there is an option to build a folder-based zip instead of these .dat files.
Scripts that install recovery have never been an issue unless a recovery.img is present in the zip, or there is a backup cached in a partition. Maybe that has changed. This will be figured out soon enough.
Still good advice to flash supersu before booting until this is understood.
Click to expand...
Click to collapse
When I talk about irrelevant factory images, I'm not talking about unofficial previews. ...and yes it has changed. It doesn't need a recovery.img because it has a .p which is a patch file. The patch file upgrades an existing recovery by patching new code into it. Obviously if the recovery is not stock, that code kills recovery. There's not really much to understand. If the files are there, take them out.
I've searched all over, and can't find a solution to my problem.
Finally received my Gear VR, plugged in my phone, need to take it out to install VR apps, network error.
Some background:
- I'm from South Africa, mobile operator Vodacom. Vodacom has bloat, which sucks, so I install the UK BTU rom from sammobile.
- After I received the error, I reinstalled the Vodacom version from sammobile, no luck.
- Factory reset, no luck.
- No apps of any kind (facebook or otherwise) are disabled on the phone.
Any other suggestions?
Update the gear vr app through the Samsung appstore
Sent from my SAMSUNG-SM-G935A using XDA-Developers mobile app
jdphilly said:
Update the gear vr app through the Samsung appstore
Sent from my SAMSUNG-SM-G935A using XDA-Developers mobile app
Click to expand...
Click to collapse
Gear VR app? Can't find it in the app store.
fanie.dry said:
Gear VR app? Can't find it in the app store.
Click to expand...
Click to collapse
i have the same problem. when i've got my s7 edge from H3G italy. my gear vr used to work, however, i have flashed the lated firmware from france and when i tried to attach my gear vr ang tried to install the required program, i got network error. i tried using wifi only, mobile data only and both wifi and mobile data toggling the download booster but to no avail.
I have the exact same problem. Any fix?
Solved my problem. I checked my phone info using app in the playstore and found out i have no csc, modem and other info except the baseband. So i decided to look for a complete firmware and reflashed on my phone complete with boot loader, csc, modem and base firmware. Now gear vr has been installed.
read below how to do this without re-flashing
thanks @ayongkot - missing CSC version was also problem in my phone
If you have certain custom FW, or you don't flash CSC partition to avoid crapware,
you might come up with network error
this file is used to show the CSC version:
/system/csc/sales_code.dat
If you are missing it, that's the cause of this mystique "network error"
- If you have root
create the file ( or use one from attachment. Unzip it first. )
the content of the file is
Code:
DDE
ending with a UNIX-style NewLine (the file is 4 bytes long)
DDE was in my phone. It's for German T-mobile. But I don't think it would matter what country and OP you'll use.
Just for reference, though this file contains DDE, the FW I flashed is showing CSC version: DDX.
If you don't have root
, still no need to reflash the whole FW
unpack only CSC (it's in cache partition) from the FW. use tar with ustar to pack it to tar and flash to phone.
be sure to backup your data before, changing CSC might trigger re-format.
Hello
Same problem in Brazil.
I could not find "/system/csc/sales_code.dat" in my phone.
Please could you teach me how I can find out this way?
Thanks.
JM
@JM Machado @burnoutsyndrome
If you can't find the file, than it's the same problem as described here.
Follow the instructions and you should be OK.
I re-wrote my original message, Msg #7, two posts up from here, to make it more understandable. I Also added an attachment.
It's working now! I created a backup and flashed the CSC part of a german T-Mobile firmware. It erased all my content, but after copying my backup to my S7 Edge, everything was fine, and the download of the Gear VR is working now! Now I have DDE as CSC code. Thanks to papo for his support!
S7 Edge
Dear Papo
Thank you for your support.
I was traveling and not able to reply back.
I will try to fix the problem having your information.
If I will not able to fix it, I let you know.
Thank you again.
Best Regards.
JM
Definitely a CSC problem, use this tool to install proper CSC - worked great for me
http://forum.xda-developers.com/s7-edge/development/utility-flashable-csc-selection-30-t3392957
I really don't understand any of this, but I can tell that you guys somehow fixed the problem and I REALLY wanna get it fixed as well.
Would any of you mind helping out a poorly educated Android user?
SpamThisJoint said:
I really don't understand any of this, but I can tell that you guys somehow fixed the problem and I REALLY wanna get it fixed as well.
Would any of you mind helping out a poorly educated Android user?
Click to expand...
Click to collapse
Yeah sure, is your phone rooted?
benno4678 said:
Yeah sure, is your phone rooted?
Click to expand...
Click to collapse
Nah it ain't. And my current software version is: G935FXXU1BP12//G935FXXU1BPHJ if that's any help?
Guys please help me man, I've been drooling over my Gear VR for two days now. There MUST be a less complicated fix out there somewhere.
---------- Post added at 08:45 PM ---------- Previous post was at 08:11 PM ----------
papo said:
read below how to do this without re-flashing
thanks @ayongkot - missing CSC version was also problem in my phone
If you have certain custom FW, or you don't flash CSC partition to avoid crapware,
you might come up with network error
this file is used to show the CSC version:
/system/csc/sales_code.dat
If you are missing it, that's the cause of this mystique "network error"
- If you have root
create the file ( or use one from attachment. Unzip it first. )
the content of the file is
Code:
DDE
ending with a UNIX-style NewLine (the file is 4 bytes long)
DDE was in my phone. It's for German T-mobile. But I don't think it would matter what country and OP you'll use.
Just for reference, though this file contains DDE, the FW I flashed is showing CSC version: DDX.
If you don't have root
, still no need to reflash the whole FW
unpack only CSC (it's in cache partition) from the FW. use tar with ustar to pack it to tar and flash to phone.
be sure to backup your data before, changing CSC might trigger re-format.
Click to expand...
Click to collapse
Can you somehow simplify this entire instruction for any noob to understand it?
use tar with ustar to pack it to tar and flash to phone.
I have already downloaded CSCSelection Zip file which you have uploaded, now could you please tell me the next step in detail that how to replace that csc file in my samsung device.
nougat beta rom 1.8.6 csc work ?
i think there is no latest csc for nougat since its only on beta so no other csc available as of now. unless they will release the official one.
hasanben35 said:
nougat beta rom 1.8.6 csc work ?
Click to expand...
Click to collapse
It is working ?!!!
Hi. I know, that this is not entirely a new topic, howewer for complete workaround, here is a solution to install B551 chinese firmware. (thanks Sokoban for packages)
1. First install firmware b052 via fastboot.
2. then install firmware b230 via fastboot.
3. install b535 package.
4. then THIS IS THE TRICK: change phone model name by editing build.prop (from: ro.product.model=hi6210sft Change to: ro.product.model=ALE-UL00) -Thanks to Sokkoban
5. IF you registered for beta testing you will receive b551 update via ota. (i dont know if this works for those that doesnt registered at beta testing)
p.s. - now im downloading the update, i will post after downloading is finished.
that would be great! please check if there is a light painting mode on the camera.
here it is:
ALE-UL00C00B551
p.s. i dont manage how to install. Because the local update option doesnt show, and the force update dont work, the service code update just the kernel version updates...
tamaskurti said:
here it is:
ALE-UL00C00B551
p.s. i dont manage how to install. Because the local update option doesnt show, and the force update dont work, the service code update just the kernel version updates...
Click to expand...
Click to collapse
Hello,
I moved to hw/eu B550. But if you want use another way to try install B551 CN
1. Change location to unicomelectric/cn (WIPE)
2. Install B220 via fastboot (WIPE)
3. Use system updater to receive OTA update to B230
4. install and use VPN software like HideMyIP to enter in Huawei account
5. Use System updater to receive OTA update to B535
6. Use my tutorial to recover local update in EMUI 4.0
7. Copy and replace local.prop but write string for B535 firmware
8. And finally try to install B551
I wish you success!
Thanks i will try.
tamaskurti said:
Hi. I know, that this is not entirely a new topic, howewer for complete workaround, here is a solution to install B551 chinese firmware. (thanks Sokoban for packages)
1. First install firmware b052 via fastboot.
2. then install firmware b230 via fastboot.
3. install b535 package.
4. then THIS IS THE TRICK: change phone model name by editing build.prop (from: ro.product.model=hi6210sft Change to: ro.product.model=ALE-UL00) -Thanks to Sokkoban
5. IF you registered for beta testing you will receive b551 update via ota. (i dont know if this works for those that doesnt registered at beta testing)
p.s. - now im downloading the update, i will post after downloading is finished.
Click to expand...
Click to collapse
Great !! Thanks for this!! Do you have installed this update? There are remains special effects in camera - Light painting, etc. from B535?
Please need chinese camera apk, and relative files/folders in system/etc/camera/
i wanna try on eu firmware, thanks.
Unfortunately i didnt have succes with those steps. I got Balong after editing local.prop - and for that the remaining steps doesnt worked.
Note:
- dont forget: this b551 from chinese fw is BETA (Android 6.0)!!! (kernel version from 27. febr.)
- the latest official chinese fw B240 (Android 5.0.1) (kernel version from 23 march) HAS the light painting camera functions.
- Compared the 2 above: the B240 build has more polished options, but beta 535 and probably beta 551 builds has more experimental features. (the commom ones from european fw, but has many more unique features too)
danvo01 said:
Great !! Thanks for this!! Do you have installed this update? There are remains special effects in camera - Light painting, etc. from B535?
Click to expand...
Click to collapse
Yes my friend I installed all Chinese firmware except 551. There are much more best from European firmware. So for me the best firmware for P8 Lite is B240 or B535(Beta 6.0)
This functions didn't present in European firmware
Touch Plus
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Driving Mode
Hardware Diagnosis
Camera Functions
sokkoban said:
Yes my friend I installed all Chinese firmware except 551. There are much more best from European firmware. So for me the best firmware for P8 Lite is B240 or B535(Beta 6.0)
This functions didn't present in European firmware
Touch Plus
Driving Mode
Hardware Diagnosis
Camera Functions
Click to expand...
Click to collapse
Thanks, I have installed B535, so I want to know if all great camera features are in B551 too.
Damn... this chineese version is really wonderfull , but why don't we also has same features ? :/
Update to v551 is not working due to changes in software - it said: try to download full update. Maybe is problem in rooted phone? Here on B535 is for me probably everything working so for now i will stay at this version.
sokkoban said:
Hello,
I moved to hw/eu B550. But if you want use another way to try install B551 CN
1. Change location to unicomelectric/cn (WIPE)
2. Install B220 via fastboot (WIPE)
3. Use system updater to receive OTA update to B230
4. install and use VPN software like HideMyIP to enter in Huawei account
5. Use System updater to receive OTA update to B535
6. Use my tutorial to recover local update in EMUI 4.0
7. Copy and replace local.prop but write string for B535 firmware
8. And finally try to install B551
I wish you success!
Click to expand...
Click to collapse
hi, what was the country that you changed your ip? I did everything as you say but when I try to update the system updater not appear to b535 but the B240 ...
velosa said:
hi, what was the country that you changed your ip? I did everything as you say but when I try to update the system updater not appear to b535 but the B240 ...
Click to expand...
Click to collapse
here you are OTA B535:
ALE-UL00C00B535
It is important to use OTA update! DO NOT USE these links!
For that chage you IP to Hong Kong and check for B535
managed to install the B551, but always with the model problem...
velosa,How did you manage to do?
armendeo said:
velosa,How did you manage to do?
Click to expand...
Click to collapse
follow the tutorial Sokkoban
Hi, velosa. I tried to follow the tutorial written by sokkoban, but without succes.
1. I dont have the b220 package, but the b230 via fastboot.
2. I cannot receive b535 via updater, but i have the b535 package so i installed from local update.
3. Editing lines:
a. I modified build.prop to showing ALE-UL00. effect: the b551 ota update appear.
b. I modified local.prop --- BUT: witch lines? all showing b551 to modifying to B535, or what. And after that witch permission to set, because i observed, that the original local.prop has rw - r -r, and the posted by sokkoban rwx - r - , maybe.
tamaskurti said:
Hi, velosa. I tried to follow the tutorial written by sokkoban, but without succes.
1. I dont have the b220 package, but the b230 via fastboot.
2. I cannot receive b535 via updater, but i have the b535 package so i installed from local update.
3. Editing lines:
a. I modified build.prop to showing ALE-UL00. effect: the b551 ota update appear.
b. I modified local.prop --- BUT: witch lines? all showing b551 to modifying to B535, or what. And after that witch permission to set, because i observed, that the original local.prop has rw - r -r, and the posted by sokkoban rwx - r - , maybe.
Click to expand...
Click to collapse
Here is B220 fastboot
About the local.prop
This is for B551
Code:
ro.product.CustCVersion=C00
ro.product.CustDVersion=D001
ro.build.display.id=ALE-UL00C00[B][COLOR="Red"]B551[/COLOR][/B]
ro.build.version.incremental=C00[B][COLOR="Red"]B551[/COLOR][/B]
ro.build.description=ALE-UL00-user 6.0 HuaweiALE-UL00 C00[B][COLOR="Red"]B551[/COLOR][/B] release-keys
ro.build.fingerprint=Huawei/ALE-UL00/hwALE-H:6.0/HuaweiALE-UL00/C00[B][COLOR="Red"]B551[/COLOR][/B]:user/release-keys
ro.confg.hw_systemversion=ALE-UL00C00[B][COLOR="Red"]B551[/COLOR][/B]_SYSTEM
ro.confg.hw_fastbootversion=ALE-UL00C00[B][COLOR="Red"]B551[/COLOR][/B]_FASTBOOT
ro.confg.hw_bootversion=ALE-UL00C00[B][COLOR="Red"]B551[/COLOR][/B]_BOOT
ro.fackInfoForCmccIot=false
Replace bold and colored symbols to B535 with following rights RW- R-- R--
NO AT&T BLOATWARE, ALL STOCK & UNLOCKED, FAST DOWNLOAD, QUICK AP LOAD + OTA UPDATES!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WARNING: BEFORE EVER FLASHING A NEW FIRMWARE TO YOUR DEVICE, YOU MUST REMEMBER - Flashing this firmware will erase the entire Internal Storage of your device... not just your app data, but also your private photos, music, text messages, call log and everything else that hasn't been synced or backed up will be completely erased when the drive for your device is entirely formatted when flashing your new firmware. KEEP READING TO LEARN HOW TO SYNC YOUR DEVICE, BACK UP YOUR DATA AND SAVE YOUR SANITY.
This is the unlocked version specified for AT&T S7 Edge models
But will work on the compatible S7 devices listed below.
:::This firmware will work for G935U, G935T, G935A, G935AZ, G935P, G935V, G935R4 Models ONLY:::
Filesize is only 1.85GB! Fast AP Load, Fast Flash, Snappy Rom, Can Remove/Uninstall Most Leftover Bloatware. OTA updates is confirmed to be working! I am now running G935UUEU4BQH3-NRD90M.G935UUEU4BQH3 because of the OTA update, and can now install S8 APKS like the latest version of TouchWiz, Gallery, MyFiles and more!
BACKUP YOUR DEVICE
○Sync App Data
Helium
○Download Win version
Smart Switch for Windows
(New Windows installations need this file installed on your PC if SmartSwitch gives a "Side by Side" installation error: 64 bit machines need both x86 and x64 files to install, x86 machines only need the x86 file to install Samsung SmartSwitch)
vcredist_x86.exe
vcredist_x64.exe
○Download Mac version
Smart Switch for MAC
○Download Mobile App(Needed For PC/MAC Backups)
Smart Switch Mobile
○Backup Your Phone using Desktop Computer
SyncMe
¡BE SURE YOU'VE BACKED UP YOUR ENTIRE PHONE BEFORE PROCEEDING TO FLASH THIS FIRMWARE!
DOWNLOAD FIRMWARE
DOWNLOAD G935UOYM4BQD2
HOW TO INSTALL
○Download Odin PC and v3.12.7(Just in case)
ODIN PC DOWNLOAD
ODIN DOWNLOAD
○Extract Odin ZIP file.
○Right click Odin and click Run as Administrator.
○Power Off phone and boot into Download Mode (Hold Home + Power + Volume Down)
○Select Continue on the warning screen.
○Connect phone and wait until you get a blue sign in Odin that says Connected
○Unzip and add files to BL, AP, CP, CSC
OPTIONS
○Make sure Re-Partition is NOT selected
○Fully Unroot: Select Phone Bootloader Update (Removes EngBoot Changes)
○Click Start
HOW TO OTA UPDATE
○Click Settings
○Click System Update
○Click Update Manually
○Click Confirm Update
INSTALL S8 APKS
○Download APK FILE
DOWNLOAD S8 APKS
○Click Install
○Click Unknown Sources
○Install APK
○Click Done
S8 APK INFO: You do not need Device Manager.
Alternate TouchWiz APK provided in case one doesn't work.
INSTALL PIXEL OREO LAUNCHER APK
○Download APK FILE
DOWNLOAD OREO LAUNCHER
○Click Install
○Click Unknown Sources
○Install APK
○Click Done
INFO
Reasons to install: Can receive OTA firmware updates, Unlocked for all carriers, doesn't have that branded bloat feel, RUNS SMOOTH after caching, can uninstall and disable most leftover stock Samsung apps (Bloatware). Cannot delete Facebook, etc, but you can still disable the app.
OP INFO UPDATE: CAN NOW INSTALL S8 APKS AFTER UPDATING FIRMWARE OTA TO VERSION G935UUEU4BQE2
HELP SECTION
Are you trying to flash this rom but you are stuck?
Here are the answers that most ask for in order to flash a ROM.
ODIN FAILED TO WRITE ERROR
Did you get this Failed To Write Message in Odin?
----------------------------
Odin Error Message:
<ID:0/003> FAIL! Model dismatch fail
<OSM> All threads completed. (succeed 0 / failed 1)
---See-Figure-Below---
SOLUTIONS
Did you:
○ Open Odin as Administrator?
○ Try the Prince Comsy version?
○ Enable Developer Settings?
-Open Settings > About Phone > Tap Build Number 7 Times
○ Enable OEM Unlock?
-Go Back to Settings > Tap Developer Options > Tap OEM Unlock
○ Enable USB Debugging?
-Tap Developer Options > Tap USB Debugging
NOTHING WORKS
Did you try every single thing but nothing works?
Well, did you right click "Odin" each time you go to open it and then click "open as administrator"?
Sometimes you have to try several different versions of Odin.
But I have found that Odin3 v3.12.7 was the one that would work when the others had not.
I always would forget to also open Odin as Administrator.
It's a pain in the neck to have to remember to open as admin every time.
But you usually have to do it.
Did you check that ADB had started? Maybe that might be the reason it won't work?
But I doubt it! But you just never know and I am just trying to help you get it flashed.
It's a very quick flash and you can see that the PDA load was very quick as well.
But as far as the errors, you just have to keep trying...
Which I mean, you sometimes have to open, close, reopen Odin when it doesn't work.
Sometimes that helps, sometimes it doesn't.
It's all about the right Odin version at the time
making sure the cord is good
Opening Odin as Admin
And keep trying again after restarting your phone by holding the download mode button sequence again.
Sometimes a fresh start will work, sometimes a restart of the PC will help
Basically, you just have to keep trying. I am on G935A too. I had the same issues, but I never gave up!
Keep trying, you'll get it!
Thanks for trying the rom guys! You are all awesome and helping me make the initial OP better with every question you ask, so thanks!
SCREENSHOTS
Several apps you see in these screenshots are not installed with this ROM
I am Just showing that Carrier Bloatware is minimal
I TAKE NO CREDIT FOR THIS BUILD, I ONLY FOUND THE FILES, EDITED INSTALLATION INSTRUCTIONS FOR THE LATEST UNLOCKED VERSION WITH THE SMALLEST FILESIZE, THEN SHARED AND DOCUMENTED IT HERE IN THE S7 FORUMS AFTER TESTING ROM.
A THANKS IS APPRECIATED.
PS, USING THIS FIRMWARE WILL NOT MAGICALLY "UNLOCK YOUR PHONE" YOUR PHONE WILL STILL STAY LOCKED TO YOUR PHONE'S CARRIER AFTER FLASHING THIS FIRMWARE. THIS IS ONLY THE FACTORY UNLOCKED VERSION OF THIS ROM.
This i can aplly with the 7.0 version of s7 edge att? build february 2k17? this can receive OTA update?
alexraptor4 said:
This i can aplly with the 7.0 version of s7 edge att? build february 2k17? this can receive OTA update?
Click to expand...
Click to collapse
Yes you can and it's reported that you can receive OTA with this firmware.
Overall, the only root method is still the engboot method?
I'm running tmo firmware on mine, but have been toying with the idea of flashing U.
t12icky0 said:
There is no specific at&t unlocked version. Plus there is already 2 threads with this same info on it so why make another?
Click to expand...
Click to collapse
Is this any different than the other threads?
t12icky0 said:
There is no specific at&t unlocked version. Plus there is already 2 threads with this same info on it so why make another?
Click to expand...
Click to collapse
Hey, post a link showing this same build on the S7 Edge forums instead of making wild claims without showing proof? You could have sent me a private message by the way, you don't have to start drama. Just saying.
dfdub said:
Is this any different than the other threads?
Click to expand...
Click to collapse
Yes, this is a different build.
Status update!
If you see another thread with this rom within this section of the forum, please show me. LOL. I wouldn't post without doing my homework, I didn't find this rom anywhere on XDA before posting. I'm doing you guys a favor and I don't have to do this, either appreciate it and try the ROM or move onto a different forum for a ROM you actually want to use. I like this rom, did hours of research finding it, and put it on my phone. I didn't have to share it guys, I chose to. As I mentioned before, a thanks is appreciated. I appreciate users concern over people double posting threads to take credit yadda yadda yadda, and the thrill of being a forum nazi, but please respect the thread owner, especially if you like people sharing rare ROMs here that they found.
Thanks for participating in the thread, and thanks for trying the rom, even though it doesn't bother me if you use it or not, I'm only sharing it and answering questions for those who actually WANT to try new roms to find the one they like. Thanks again for participating and trying the ROM, I like it, it has its perks and whatnot, and it's also not perfect, but it works. Hope you like using it, I do! #NoDrama :highfive:
t12icky0 said:
This is the same exact Rom on every thread. This is proof enough. It's the same everything from a different thread in this section. So please tell me how this is different? They pic I posted is from the nougat unlocked Rom. Look familiar??
Click to expand...
Click to collapse
It is not the same everything, you should take some time doing thorough research before bashing someone for something you think is a fraud. Thanks.
t12icky0 said:
Just because you post a title doesn't make it true.
Click to expand...
Click to collapse
HAHA, alright bro, one second... I'm about to solve this once and for all.
t12icky0 said:
Plus look at the upload date...You apparently didn't do your homework like you said. Just face it that this Rom you call the s7 edge+ is the same as every other Rom.
Click to expand...
Click to collapse
This download is 1.85 GB and others are 2.10 GB. Sorry, I had to do your homework for you since you didn't want to on your own. Now can we stop trolling the forum thread creator? Thanks!
MafiaIlluminati said:
You see that part in this title where it says S7 Edge +?
Click to expand...
Click to collapse
could you educate me on the +(plus) ?
dfdub said:
could you educate me on the +(plus) ?
Click to expand...
Click to collapse
WYM? I do not own one. Maybe I read the download wrong, because I know remembered there was an Edge + line? But either way the filesize is different so this is definitely a different build, maybe due to less bloatware, maybe different lines of coding, but it's smaller in size, which is why I wanted it when I found it, because I couldn't find this same exact file anywhere else and I wanted less preinstalled on my phone.
t12icky0 said:
Also just some more proof. The same Rom. This is from bytes thread and it was way before you because I was the one who uploaded the files for him.
Click to expand...
Click to collapse
Ok people lets stop acting like children and move on. Use the rom or dont use it. Enough with the bickering. Who gives a crap as to who posted what we are here to help each other.
---------- Post added at 02:37 PM ---------- Previous post was at 02:26 PM ----------
dfdub said:
could you educate me on the +(plus) ?
Click to expand...
Click to collapse
There is no+ with the s7. It is eaither an S7 or S7 edge. The plus came about when it was the S6 and S6+ which is basically S6 edge.
I'd appreciate it if you removed your posts now.
You have nothing to prove... Checksum all you want. The total zip filesize for each file you're obsessing over is different. No matter what you say, no matter how many ways you try to prove it, this is a different build. You cannot have two of the exact same builds and them both come out different filesizes, compression or not, you're not about to compress a file that much. Are you really going to keep being this silly and posting ridiculous harassing posts? Dude, this is why you have been added to the ignore list hours and hours ago. :good:
Ok, if it wasn't for your post I would have never seen the files for the ATT Version of the S7 Edge (G935A). I know it is usable on all the different versions, but I hardly ever check other forums.
That being said, has anyone used the ENG.IMG version of rooting this ROM? I am on the Rooted G935A and am wanting to use these files to update my phone and then root this version. Has anyone done it? I know how to root with the ENG.IMG but I just want to make sure I can do it with this one and to make sure there aren't any problems.
Thanks in advance.
From the Moderator
The next trolling post in this thread will be met with an infraction and possible Ban from XDA
If anyone has an issue report it Let the Mods manage issues or conflicts do not try to do that yourself.
CLEAR ENOUGH ???
~~~Oka1
freeop said:
Ok, if it wasn't for your post I would have never seen the files for the ATT Version of the S7 Edge (G935A). I know it is usable on all the different versions, but I hardly ever check other forums.
That being said, has anyone used the ENG.IMG version of rooting this ROM? I am on the Rooted G935A and am wanting to use these files to update my phone and then root this version. Has anyone done it? I know how to root with the ENG.IMG but I just want to make sure I can do it with this one and to make sure there aren't any problems.
Thanks in advance.
Click to expand...
Click to collapse
I got stuck in a bootloop trying to root yesterday, let me finish testing and I'll update the OP when I figure out how to do it without tripping the system up. Thanks!
I had to use PrinceComsy's Odin to flash this version. Any other version of Odin failed.
Hi folks
When I get back the device from Huawei services, I receive a boot.img without encryption that let me able to backup and restore the firmware hundred times without errors .
In this tutorial I'll show you how to do that without need to bring the phone to Huawei services to reset the software, starting from now can be done as well.
Requirements:
Unlocked bootloader, you know how to do that.
My own TWRP, that authorized Huawei store told should use my own TWRP to restore the phone, so get it from here by downloading the latest version.
Stock firmware, click here to download it, it's for single sim only.
Stock IMGS that needed for decrypt and to re-enable the encryption once firmware has been done with restoration, click here to download them.
7 zip to unpack the tar.gz.
Code:
[CENTER][COLOR="Red"][SIZE="4"][FONT="Comic Sans MS"]Please read the steps carefully because I'm not going to repeat them for each user, thanks[/FONT][/SIZE][/COLOR][/CENTER]
Reset Steps:
Download the C432B161.
Unpack the .tar.gz archive with 7 zip.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Rename from C432B161 to TWRP.
Copy to the Internal Storage.
Reboot to TWRP Recovery by the following command.
in the IMGS archive you will find a bootimage called boot.img, rename it to boot.emmc.win and copy to TWRP->BACKUPS->57UDU17709001769->2017-10-18--12-03-00_NRD90M_test-keys -> replace it and then follow the video
Go to the TWRP.
Wipe everything except the external_sd (the path where you copy the backup)
Tab on Restore.
Choose the copied backup make sure to rename from C432B161 to TWRP to match.
Select all partitions.
Swipe the screen and wait until finish.
Reboot to bootloader once done.
In the IMGS.tar.gz there is a file caller boot.img flash via fastboot as boot and will get booted like charm
Warning:
You are not allowed to copy or steal the files of my guide without ask my permissions.
Because I take almost week to upload the firmware after many times of failing upload.
Mention this guide for who looking helps to restore this device.
If I saw any piece of my contents in other threads, I'll report as abuse and ask a moderator to close his thread because I already saw someone rename my recovery and put it inside his thread without asking permission. that's all.
This guide could be helpful for who want to debrand his device, so we need tester.
to enable dual sim: you must flash an oeminfo partition from dual sim firmware.
Happy restoring.
Can I change from dualsim to monosim with this guide?
Wire1122 said:
Can I change from dualsim to monosim with this guide?
Click to expand...
Click to collapse
to be honest, I can't confirm since is the full backup from my single device.
in case dual sim still appear even after restore, you have to flash the single sim oeminfo partition.
when I must flash oeminfo?
Wire1122 said:
when I must flash oeminfo?
Click to expand...
Click to collapse
post firmware restoring
Wire1122 said:
when I must flash oeminfo?
Click to expand...
Click to collapse
not works to me. Pralx1c432b182 such before restoring
Wire112233 said:
not works to me. Pralx1c432b182 such before restoring
Click to expand...
Click to collapse
whats not work restoring firmware or converting from dual to single?
haky 86 said:
whats not work restoring firmware or converting from dual to single?
Click to expand...
Click to collapse
converting from dual to single. But after restoring the fw remains b182, not 161
Wire112233 said:
converting from dual to single. But after restoring the fw remains b182, not 161
Click to expand...
Click to collapse
yup because some partitions is upgraded to b182 (dual sim), same thing happen to me b181 (single sim). for converting to single sim, I'll upload the oeminfo partition soon.
Note: this operation might will lock bootloader/frp automatically, so I recommend to check them via fastboot mod.
When oeminfo?
Sent from my HUAWEI PRA-LX1 using XDA Labs
Looks like the images gone bad, and now point:
Wipe the following partitions like in the screenshot.
Click to expand...
Click to collapse
can be quite challenging
Wiped cache/data/system and restored everything that I was allowed to from your backup.
Meanwhile I changed name of directory: TWRP\BACKUPS\57UDU17709001769\2017-10-18--12-03-00_NRD90M_test-keys to
TWRP\BACKUPS\9DC7N17A17006059\2017-10-18--12-03-00_NRD90M_test-keys in order to make the backup visible in TWRP Restore menu.
(Hope that didn't change anything?)
Then I completed your "Reset Steps" tutorial, reboot and [...]
that hilarious green screen is still in place of previous Huawei:
After initial configuration my first impression was that I downloaded wrong backup, cause it looks more like the Elite ROM V6 (5 icons at bottom-screen menu, google searchbar, additional options (4 rows instead of 2) in upper-scroll menu and the pinkish-purple wallpaper) even the blinking NFC problem I had with that ROM is present there, but yet it's not that one. All informations in settings>about phone are from your backup, I even checked if the Android Studio will find my phone - and it did! That was unavaible in HassanMirza01's ROM.
So there's my question - does it suppose to look that way? Or I just messed something really hard and the visual theme files from previous OS's stayed somehow on my phone?
Don't take me wrong - after this tutorial I ended up with fully functional, nice looking (as soon as I change the pinkish wallpaper...) smartphone, so I'm really happy thanks to you!
Anyway I found it also interesting how the GreenScreen could ended up in such a place, so I'll try to figure that out.
Sixter said:
Looks like the images gone bad, and now point:
can be quite challenging
Wiped cache/data/system and restored everything that I was allowed to from your backup.
Meanwhile I changed name of directory: TWRP\BACKUPS\57UDU17709001769\2017-10-18--12-03-00_NRD90M_test-keys to
TWRP\BACKUPS\9DC7N17A17006059\2017-10-18--12-03-00_NRD90M_test-keys in order to make the backup visible in TWRP Restore menu.
(Hope that didn't change anything?)
Then I completed your "Reset Steps" tutorial, reboot and [...]
that hilarious green screen is still in place of previous Huawei:
After initial configuration my first impression was that I downloaded wrong backup, cause it looks more like the Elite ROM V6 (5 icons at bottom-screen menu, google searchbar, additional options (4 rows instead of 2) in upper-scroll menu and the pinkish-purple wallpaper) even the blinking NFC problem I had with that ROM is present there, but yet it's not that one. All informations in settings>about phone are from your backup, I even checked if the Android Studio will find my phone - and it did! That was unavaible in HassanMirza01's ROM.
So there's my question - does it suppose to look that way? Or I just messed something really hard and the visual theme files from previous OS's stayed somehow on my phone?
Don't take me wrong - after this tutorial I ended up with fully functional, nice looking (as soon as I change the pinkish wallpaper...) smartphone, so I'm really happy thanks to you!
Anyway I found it also interesting how the GreenScreen could ended up in such a place, so I'll try to figure that out.
Click to expand...
Click to collapse
might the elite rom v6 cause that issue, try to restore it again perhaps it will gone..I didn't get that green and red screen
Hey, any have oeminfo for single sim fw? its impossible to find
http://www.mediafire.com/file/0tnrmliuudsz9qo/OemInfo_EU_SS.zip
https://mega.nz/#F!0xcUWCBZ!FAXGLF3WC_uFsc5r--BqEQ
Wire1122 said:
http://www.mediafire.com/file/0tnrmliuudsz9qo/OemInfo_EU_SS.zip
https://mega.nz/#F!0xcUWCBZ!FAXGLF3WC_uFsc5r--BqEQ
Click to expand...
Click to collapse
Thanks for the help! For what version is this oem? (b161?)
dannyzamora said:
Thanks for the help! For what version is this oem? (b161?)
Click to expand...
Click to collapse
I don't know Sorry It is monosim c432
Wire1122 said:
I don't know Sorry It is monosim c432
Click to expand...
Click to collapse
Thx! One question... I have now installed b182, can i "downgrade" installing the b161 twrp backup with the tutorial and later install this oem?
Enviado desde mi PRA-LX1 mediante Tapatalk
dannyzamora said:
Thx! One question... I have now installed b182, can i "downgrade" installing the b161 twrp backup with the tutorial and later install this oem?
Enviado desde mi PRA-LX1 mediante Tapatalk
Click to expand...
Click to collapse
even if downgraded will keep on b182 because some partitions will not downgraded since my twrp is designed to backup/restore only necessary partitions for fully worked firmware.
I also had to rename TWRP\BACKUPS\57UDU17709001769\2017-10-18--12-03-00_NRD90M_test-keys to
TWRP\BACKUPS\<my device ID visible in adb devices>\2017-10-18--12-03-00_NRD90M_test-keys in order to make the backup visible in TWRP Restore menu, thanks @Sixter. Please update the first page accordingly.
But even doing so, when coming to Huawei eRecovery I'm still stuck with "Getting package info failed" issue, I cannot get back EMUI yet. Any hint?
bagage said:
I also had to rename TWRP\BACKUPS\57UDU17709001769\2017-10-18--12-03-00_NRD90M_test-keys to
TWRP\BACKUPS\<my device ID visible in adb devices>\2017-10-18--12-03-00_NRD90M_test-keys in order to make the backup visible in TWRP Restore menu, thanks @Sixter. Please update the first page accordingly.
But even doing so, when coming to Huawei eRecovery I'm still stuck with "Getting package info failed" issue, I cannot get back EMUI yet. Any hint?
Click to expand...
Click to collapse
You might want to try the Recovery MITM approach but its a tad more complicated. https://forum.xda-developers.com/p8lite/p8-lite-2017-discussion/guide-local-recovery-server-t3714900