Related
If somebody want to replace provider/operator/or any other splash screen on Huawei device just do as follow:
Root required
First way:
Install Adb and Fastboot
Download this utility to ADB folder on PC
By Windows CMD go to ADB folder and use this commands:
(observe phone and make appropriate permissions if needed)
adb shell su -c "dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/sdcard/oeminfo"
adb pull /sdcard/oeminfo oeminfo
Make copy original oeminfo file
Download stock HW splash (logo) or make your own picture *.bmp. Bitmap resolution should match your device resolution (1080x1920 pixels). Put it to ADB folder.
In ADB folder use commands:
oem_logo.exe oeminfo logo.bmp
adb push oeminfo /sdcard/oeminfo
adb shell su -c "dd if=/sdcard/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo"
adb rm -f /sdcard/oeminfo
Reboot
More options described here.
Second way:
Download this (translated bye me) utility
Unzip and use it
Additionally:
If you want to use Huawei stock splash screen you can install this file by custom recovery. It replace any splash screen you have installed by original HW.
Off course you can use this script to installing your own logo. Just replace file \dev\block\platform\hi_mci.0\by-name\oeminfo in downloaded zip by your own file created accordingly to above first method (by oem_logo.exe).
All credits to:
Kostyan_nsk
wistonbogarde
For my just click thanks
Notice !
Everything you are doing on your own RISK !
nice ,but warning oeminfo contain such things as IMEI
Z!L0G80 said:
nice ,but warning oeminfo contain such things as IMEI
Click to expand...
Click to collapse
Are you sure? I'dont think so. At least, I was unable to find IMEI there. And it would be too easy to change IMEI if it could be in oeminfo partition...
Kostyan_nsk said:
Are you sure? I'dont think so. At least, I was unable to find IMEI there. And it would be too easy to change IMEI if it could be in oeminfo partition...
Click to expand...
Click to collapse
imei is crypted by aes key, oeminfo probably contain some other phone related information I DONT RECOMENDED TO FLASH THIS < YOU CAN PROBABLY BRICK YOUR PHONE
hi Kostyan_nsk and z!log80 !
I have recently flashed oeminfo.img without isssues (thanks again Kostyan_nsk)
I wanted to give it a try and ask please Kostyan_nsk or z!log80 for a brief explanation about how oem_logo.exe performs the bitmap replacement. Is it possible to mount oeminfo.img browse its file system and replace a particular file, or is it by searching bitmap signature, …?
Thanks Ziolek67 for starting this thread :laugh:
Printusrzero said:
hi Kostyan_nsk and z!log80 !
I have recently flashed oeminfo.img without isssues (thanks again Kostyan_nsk)
I wanted to give it a try and ask please Kostyan_nsk or z!log80 for a brief explanation about how oem_logo.exe performs the bitmap replacement. Is it possible to mount oeminfo.img browse its file system and replace a particular file, or is it by searching bitmap signature, …?
Thanks Ziolek67 for starting this thread :laugh:
Click to expand...
Click to collapse
do you have same imei as before ? oeminfo doesnt contain filesystem - no mount
yes, same as before
if no file system or mount then I guest search for a pattern or dedicated tool to package... I have been trying to find further more precise information about oeminfo.img but had not found much so far. I would appreciate if you can contribute to make this a bit clearer for me
thanks
[Edited]
After a bit of research I have found other mods for factory device location, etc. writing to particular offsets, tools to modify, backup and restore oeminfo.img. It is a data store. No embedded code. Thnx!
Z!L0G80 said:
imei is crypted by aes key, oeminfo probably contain some other phone related information I DONT RECOMENDED TO FLASH THIS < YOU CAN PROBABLY BRICK YOUR PHONE
Click to expand...
Click to collapse
Eazy. I tried it many times... It works perfectly. I never publish potentially dangerous untested features.
Z!L0G80 said:
imei is crypted by aes key, oeminfo probably contain some other phone related information I DONT RECOMENDED TO FLASH THIS < YOU CAN PROBABLY BRICK YOUR PHONE
Click to expand...
Click to collapse
I flashed whole oeminfo partition from other device and my IMEI stayed the same. As I supposed, it's somewhere else, but not in oeminfo partition. You are wrong.
You must NOT be alarm
Kostyan_nsk said:
I flashed whole oeminfo partition from other device and my IMEI stayed the same. As I supposed, it's somewhere else, but not in oeminfo partition. You are wrong.
Click to expand...
Click to collapse
Do not worry, I also used HW-OEM_LOGO.ZIP to change the booting logo for the original one, and my IMEI is the same as I bought it in the store, so do not be alarmed !!!!:laugh:
Also worked on P8 B321, IMEI stayed the same.
Download links not working, could someone provide new ones please?
Fedroid said:
Download links not working, could someone provide new ones please?
Click to expand...
Click to collapse
Hi!
You can to use the last version File, this is for change the intial Logo and/or bootanimation.
Thanks!
Hi,
I am trying to build a custom boot image to get rid of the immutable files of my P7-L00.
Specifically I haved done this : At a specific point in the boot process the rc scripts execute the set_immutable command with a 1 parameters that sets the immutable bits in all the files mentioned in the set_immutable.list file. If this command is changed to a 0 it clears the immutable bit for all the files. I have buit the custom ramfs necesary for this but when I repack the boot image it will not boot.
I am using the following command for mkbootimg ....
mkbootimg --kernel mykernel.img --ramdisk ramdisk.cpio.gz --ramdisk_offset 0x04000000 --base 0x07000000 --cmdline "k3v2mem k3v2_ion=1 vmalloc=448M maxcpus=4 initcall_debug=n" -o newimg.img
The resulting first page looks ok, it has the same offsets as my original working boot image, but as I mentioned before, it does not boot, but just cycles back to fastboot mode after about 1 minute.
Any help will be appreciated,
Thanks
The most probable that there's a problem with permissions.
Make
Code:
chown 0:0 init.rc
chmod 750 init.rc
before packing ramdisk.
Kostyan_nsk said:
The most probable that there's a problem with permissions.
Make
Code:
chown 0:0 init.rc
chmod 750 init.rc
before packing ramdisk.
Click to expand...
Click to collapse
Thanks a lot ! .... I had not checked the user/groups for the extracted files ...
gguemez said:
Hi,
I am trying to build a custom boot image to get rid of the immutable files of my P7-L00.
Specifically I haved done this : At a specific point in the boot process the rc scripts execute the set_immutable command with a 1 parameters that sets the immutable bits in all the files mentioned in the set_immutable.list file. If this command is changed to a 0 it clears the immutable bit for all the files. I have buit the custom ramfs necesary for this but when I repack the boot image it will not boot.
I am using the following command for mkbootimg ....
mkbootimg --kernel mykernel.img --ramdisk ramdisk.cpio.gz --ramdisk_offset 0x04000000 --base 0x07000000 --cmdline "k3v2mem k3v2_ion=1 vmalloc=448M maxcpus=4 initcall_debug=n" -o newimg.img
The resulting first page looks ok, it has the same offsets as my original working boot image, but as I mentioned before, it does not boot, but just cycles back to fastboot mode after about 1 minute.
Any help will be appreciated,
Thanks
Click to expand...
Click to collapse
I suggest, use kitchen.
gguemez said:
Hi,
I am trying to build a custom boot image to get rid of the immutable files of my P7-L00.
Specifically I haved done this : At a specific point in the boot process the rc scripts execute the set_immutable command with a 1 parameters that sets the immutable bits in all the files mentioned in the set_immutable.list file. If this command is changed to a 0 it clears the immutable bit for all the files. I have buit the custom ramfs necesary for this but when I repack the boot image it will not boot.
I am using the following command for mkbootimg ....
mkbootimg --kernel mykernel.img --ramdisk ramdisk.cpio.gz --ramdisk_offset 0x04000000 --base 0x07000000 --cmdline "k3v2mem k3v2_ion=1 vmalloc=448M maxcpus=4 initcall_debug=n" -o newimg.img
The resulting first page looks ok, it has the same offsets as my original working boot image, but as I mentioned before, it does not boot, but just cycles back to fastboot mode after about 1 minute.
Any help will be appreciated,
Thanks
Click to expand...
Click to collapse
You are correct in saying that modifying the setimmutable binary flag from 1 to 0 in the boot image solves the set_immutable.list problem referred to many times in various posts in this forum..
I have a P7-L07 emui2.3 B125 and a P7-L10 emui3.0 B609. I had no trouble modifying the boot.img for the L07 using
linux-kernelkitchen-0.002 under xubuntu. The L10 is a different story but the main problem is faulty flash memory.
At any rate, you don't really need to worry about the boot.img file at all. A simple and easy work around is to replace the file set_immutable.list with another empty file of the same name. This works quite well on my L10. I used the file manager FX to achieve this. As long as you have root access and can change file permissions correctly this method will work for you.
arthios said:
You are correct in saying that modifying the setimmutable binary flag from 1 to 0 in the boot image solves the set_immutable.list problem referred to many times in various posts in this forum..
I have a P7-L07 emui2.3 B125 and a P7-L10 emui3.0 B609. I had no trouble modifying the boot.img for the L07 using
linux-kernelkitchen-0.002 under xubuntu. The L10 is a different story but the main problem is faulty flash memory.
At any rate, you don't really need to worry about the boot.img file at all. A simple and easy work around is to replace the file set_immutable.list with another empty file of the same name. This works quite well on my L10. I used the file manager FX to achieve this. As long as you have root access and can change file permissions correctly this method will work for you.
Click to expand...
Click to collapse
Thank your for the info. In the P7-L00 with a KingUser Root I could not change the set_immutable.list to anything. Any attempt to modify the file, replace or change the permissions would fail, since the immutable bit was set.
Having fixed the problem I mentioned above I now find myself with the situation that if I change some, I can't say all files, in the system directory the phone reboot immediately. I dont know if this is due to the "partial" root some people say kinguser provides or to some other issue.
I will keep playing around, thanks for the help.
gguemez said:
Thank your for the info. In the P7-L00 with a KingUser Root I could not change the set_immutable.list to anything. Any attempt to modify the file, replace or change the permissions would fail, since the immutable bit was set.
Having fixed the problem I mentioned above I now find myself with the situation that if I change some, I can't say all files, in the system directory the phone reboot immediately. I dont know if this is due to the "partial" root some people say kinguser provides or to some other issue.
I will keep playing around, thanks for the help.
Click to expand...
Click to collapse
changing the 1 to 0 of set_immutable in rc won't work. i already tried that thing. i used 609 boot.img, unpack and repack it successfully but it wont work.
majcomtech said:
changing the 1 to 0 of set_immutable in rc won't work. i already tried that thing. i used 609 boot.img, unpack and repack it successfully but it wont work.
Click to expand...
Click to collapse
Thanks, do you also get the same effect of an immediate reboot when you modify system files? That is what I am really after, since I can't change anything I can't even update the SU or change any files ...
gguemez said:
Thanks, do you also get the same effect of an immediate reboot when you modify system files? That is what I am really after, since I can't change anything I can't even update the SU or change any files ...
Click to expand...
Click to collapse
if you want full root, i already made tut for that. http://forum.xda-developers.com/ascend-p7/general/rooted-p7-l10-609-t3003605
majcomtech said:
changing the 1 to 0 of set_immutable in rc won't work. i already tried that thing. i used 609 boot.img, unpack and repack it successfully but it wont work.
Click to expand...
Click to collapse
Thanks, I have tried this but in my case it has not worked. Everytime I reboot the phone the files are all back, as if there is a backup partition or something. I an now trying to do this via a UPDATE with CWM...
Thanks again.
gguemez said:
Thanks, I have tried this but in my case it has not worked. Everytime I reboot the phone the files are all back, as if there is a backup partition or something. I an now trying to do this via a UPDATE with CWM...
Thanks again.
Click to expand...
Click to collapse
I expect you are quite fed up by now and I offer my commiserations. There may be however be another solution to your problem. Have you considered downloading a custom ROM for your L00 created (say) by KangVIP or Killprocess, and then extracting the boot image from the zip file and flashing that? These boot images have the set_immutable flag set to 0. As I recall, the ROMs from KangVIP are password protected so a Killprocess ROM or one from someone else might be better. If you do decide to try this out, make sure the build number of the downloaded ROM is similar to yours. The boot images differ between emui2.3 and emui3.0. Good luck!
gguemez said:
Thanks, I have tried this but in my case it has not worked. Everytime I reboot the phone the files are all back, as if there is a backup partition or something.
Click to expand...
Click to collapse
Seems like you have locked bootloader.
Kostyan_nsk said:
Seems like you have locked bootloader.
Click to expand...
Click to collapse
No, the bootloader is unlocked. I can change the boot partition at will, I have many times letf it unbootable and restored it with no problem. I will try to do something via the recovery parition but, the only one I have found that worked in my phone, always gives me errors when running my scripts (so I am obviously doing something wrong).
I got to the point of sending a script that says ... ui_print ("Hello World"); ... but that gives me an error too!
I will keep trying to figure this out, thanks for your help.
Guillermo
What value has "fblock=" parameter in "/proc/cmdline"?
BassamKassem said:
Yes. In case you needed to do so .
Follow below instructions.
This operation requires Root Access (KingRoot version 4.60 apk from here ) and ES File Explorer from Play Store (you must enable root explorer from ES File explorer app)
1). It is necessary to change (or create if not present) the file called custom.bin in folder /data/
Open custom.bin file and edit it as below:
-To go to the Russian location: hw / ru
-To go to Malaysia: hw / spcseas
-To go to China: unicomelectric / cn
-To go to the Middle East or Pakistani firmware: hw / meafnaf
-To go to the Belarusian firmware: mts / by
-To go to the European firmware: hw / eu
IMPORTANT: After you edit the file you must make sure that it's permission is as it was before editing (See and memorize it's original permission before editing).
Correct permissions: ++ 0 ++ 0 ++ 0
2). It is necessary to replace the file called oeminfo in the folder /dev/block/platform/hi_mci.0/by-name/ (See it's Permission before replacing it and make a copy from the original file as well, just in case, better to keep) the new oeminfo files that holds the new desired region or locations
can be found in the downloaded archive. Below link
3). After a successful replacement of the resulting file in a folder, it's size must be zero KB. This is because in this location is not the actual files it's a symbolic links to them.
IMPORTANT: After replacing the file, it must be using below permissions: +++ +++ +++ I usually unnecessary , but verify.
4). Finally restart your phone and go to Settings then check your device model number it will be unknown instead of Che2-L11. (This is completely normal) .
5). Then open updater app and follow the update process normally by downloading the Lollipop firmware that matches the oeminfo location you picked then extract the downloaded zip file from Huawei support page then put UPDATE.APP file in the root of your SD Card inside folder called dload then from the updater app press on local update and make a backup then choose install.
.
Click to expand...
Click to collapse
Hi
I have a complex problem with my Honor 4x Che1-L04. I used this approachused for update my phone but everything is in disarrayrom. Before doing to change oeminfo and replace with original oeminfo file i unlocked bootloader and rooted my phone, and installed custom recover TWRP and there was no problem.
But now I have a lot of problems with my phone:
1. bootloader is locked and I have bootloader unlocked code but is not work
Code:
...
FAILED (remote: Invalid key,u
finished. total time: 0.089s
I think the Serial number is a Fick
8pic.ir/images/ey5iawposoedw7sob6ck.jpeg
8pic.ir/images/qcawescqs19kdmml21cm.jpeg
2. TWRP recoveries doesn't work for me.After reboot or use Power key+Down key volume is go to fastboot(rescue mode). If the phone is turned off and then turned on everything works well except:
***** If the image look,themes is different colors(red,blue,...), but it was not previously.
***** slot2 for each SIM card request PUK but the SIM cards in another phone works well.
3-When I upgrade with SD gives me "software update failed ".
I've got a backup by TWRP but i do not have any recovery on your phone and i can not use it
Please help, thank you.
Fixed your device?
Hello Guys,
So i was in the urge to Root my Phone so i went ahead and Unlocked the bootloader for my phone Honor 5c Nem L-22 (India). Then I flashed Twrp Recovery and download supersu and moved it to my sdcard, and when got into recovery mode and i wiped /data , /cache, /system after that i installed supersu and when i was going to reboot my phone a message displayed saying "No OS intalled , Do you wish to continue" This was the time i knew i messed up (worst part is i never backed up my data). Now i am trying to install OS into my phone i downloaed few Firmware for my phone and even got stock firm, Now when i go to Twrp recovery to install the .zip file i get many error notice saying unable to mount /vendor, /product (invalid argument) Which i am not able to understand (I even tried to mount /vendor /product from Twrp Menu>Mount but not able to select the tick in those). Please help What can i do to make my phone working.
Thank you.
get stock recovery and install stock recovery, then install B100. why people dont get that when twrp says system it means system....
hubertchen37 said:
Hello Guys,
So i was in the urge to Root my Phone so i went ahead and Unlocked the bootloader for my phone Honor 5c Nem L-22 (India). Then I flashed Twrp Recovery and download supersu and moved it to my sdcard, and when got into recovery mode and i wiped /data , /cache, /system after that i installed supersu and when i was going to reboot my phone a message displayed saying "No OS intalled , Do you wish to continue" This was the time i knew i messed up (worst part is i never backed up my data). Now i am trying to install OS into my phone i downloaed few Firmware for my phone and even got stock firm, Now when i go to Twrp recovery to install the .zip file i get many error notice saying unable to mount /vendor, /product (invalid argument) Which i am not able to understand (I even tried to mount /vendor /product from Twrp Menu>Mount but not able to select the tick in those). Please help What can i do to make my phone working.
Thank you.
Click to expand...
Click to collapse
Huge mistake. Why did you wiped data and system?
Sent from my Honor 8 using XDA Labs
hubertchen37 said:
Hello Guys,
So i was in the urge to Root my Phone so i went ahead and Unlocked the bootloader for my phone Honor 5c Nem L-22 (India). Then I flashed Twrp Recovery and download supersu and moved it to my sdcard, and when got into recovery mode and i wiped /data , /cache, /system after that i installed supersu and when i was going to reboot my phone a message displayed saying "No OS intalled , Do you wish to continue" This was the time i knew i messed up (worst part is i never backed up my data). Now i am trying to install OS into my phone i downloaed few Firmware for my phone and even got stock firm, Now when i go to Twrp recovery to install the .zip file i get many error notice saying unable to mount /vendor, /product (invalid argument) Which i am not able to understand (I even tried to mount /vendor /product from Twrp Menu>Mount but not able to select the tick in those). Please help What can i do to make my phone working.
Thank you.
Click to expand...
Click to collapse
Hi ..
Install this package and done.
http://www.hihonor.com/in/support/details?DOC_ID=91134
Download this file
Extract it and u will find a file named UPDATE.APP .
Create a folder named dload in your sdcard.
Put update.app in the dload folder.
Insert sdcard in ur phone and shutdown ur phone now.
Click vol down + vol up + power (all three buttons) simultaneously.
It will start to install it , let it continue and then ur phone will reboot . Thats it ur phone is brand new again
gopinaidu77 said:
Hi ..
Install this package and done.
http://www.hihonor.com/in/support/details?DOC_ID=91134
Download this file
Extract it and u will find a file named UPDATE.APP .
Create a folder named dload in your sdcard.
Put update.app in the dload folder.
Insert sdcard in ur phone and shutdown ur phone now.
Click vol down + vol up + power (all three buttons) simultaneously.
It will start to install it , let it continue and then ur phone will reboot . Thats it ur phone is brand new again
Click to expand...
Click to collapse
yeah but before you do any of this install stock recovery.
thelous said:
yeah but before you do any of this install stock recovery.
Click to expand...
Click to collapse
Erecovery does the job
Hi @hubertchen37 , can i know if u had solved the issue ? if so kindly post what u had done to tackle this issue . will help for future members coming here.
Flash nougat stock ROM...b3xx something and have full ota-mp-pv,it will appear ndrm90-testkey......and then, flash rollback package for nem l-22(India).
gopinaidu77 said:
Hi ..
Install this package and done.
Download this file
Extract it and u will find a file named UPDATE.APP .
Create a folder named dload in your sdcard.
Put update.app in the dload folder.
Insert sdcard in ur phone and shutdown ur phone now.
Click vol down + vol up + power (all three buttons) simultaneously.
It will start to install it , let it continue and then ur phone will reboot . Thats it ur phone is brand new again
Click to expand...
Click to collapse
Hey i Thanks for the info man really appreciate it but its not working. it says "Software install failed. Incompatibility with current version. please download correct package."
More worst part it now i am not able to connect phone to pc via usb. So now i cant even flash stock recovery. I am screwed .
hubertchen37 said:
Hey i Thanks for the info man really appreciate it but its not working. it says "Software install failed. Incompatibility with current version. please download correct package."
More worst part it now i am not able to connect phone to pc via usb. So now i cant even flash stock recovery. I am screwed .
Click to expand...
Click to collapse
Incompatible package, can u tell me the model again?
gopinaidu77 said:
Incompatible package, can u tell me the model again?
Click to expand...
Click to collapse
Honor 5c NEM L22C675 i think he need the backup of OEM file...
---------- Post added at 02:27 AM ---------- Previous post was at 02:09 AM ----------
hubertchen37 said:
Hello Guys,
So i was in the urge to Root my Phone so i went ahead and Unlocked the bootloader for my phone Honor 5c Nem L-22 (India). Then I flashed Twrp Recovery and download supersu and moved it to my sdcard, and when got into recovery mode and i wiped /data , /cache, /system after that i installed supersu and when i was going to reboot my phone a message displayed saying "No OS intalled , Do you wish to continue" This was the time i knew i messed up (worst part is i never backed up my data). Now i am trying to install OS into my phone i downloaed few Firmware for my phone and even got stock firm, Now when i go to Twrp recovery to install the .zip file i get many error notice saying unable to mount /vendor, /product (invalid argument) Which i am not able to understand (I even tried to mount /vendor /product from Twrp Menu>Mount but not able to select the tick in those). Please help What can i do to make my phone working.
Thank you.
Click to expand...
Click to collapse
You need to Flash the Oem file through twrp then Copy the stock rom to the dload folder and try again surely it will work..
Ranjithksr said:
Honor 5c NEM L22C675 i think he need the backup of OEM file...
You need to Flash the Oem file through twrp then Copy the stock rom to the dload folder and try again surely it will work..
Click to expand...
Click to collapse
Flashing oeminfo will wipe version history. Just install oeminfo through twrp and then u can restore ur rom again.
gopinaidu77 said:
Flashing oeminfo will wipe version history. Just install oeminfo through twrp and then u can restore ur rom again.
Click to expand...
Click to collapse
Ok Can you please share here?
Let me know if you still having issues. I updated the oeminfo file in repo thread for 5c.
Use it to see if your issue resolves.
shashank1320 said:
Let me know if you still having issues. I updated the oeminfo file in repo thread for 5c.
Use it to see if your issue resolves.
Click to expand...
Click to collapse
Also plz try to share custom.bin
i have a note 8 sm n950 i done the android update a few months ago and and it got my phone stuck in a boot loop, i installed new firmware which i was able to use the phone again but lost data signal, i fixed that but now my calls and text are coming through with a german number (im in the UK) i have tried to install stock firmware using odin and keep getting sw rev check fail device 11 binary 6 (and other variations of that error) i have also tried clearing the cache and wiping the phone from the boot menu but no luck, could anyone help, i would be very grateful
Have you check that you have downloaded and installed the correct version of the OS on your device?
pazler said:
i have a note 8 sm n950 i done the android update a few months ago and and it got my phone stuck in a boot loop, i installed new firmware which i was able to use the phone again but lost data signal, i fixed that but now my calls and text are coming through with a german number (im in the UK) i have tried to install stock firmware using odin and keep getting sw rev check fail device 11 binary 6 (and other variations of that error) i have also tried clearing the cache and wiping the phone from the boot menu but no luck, could anyone help, i would be very grateful
Click to expand...
Click to collapse
The binary error you are getting is because you are trying to flash older filmware than what is already on the phone., this is not possible because of security updates. Downloading the latest filmware for you device should resolve this error, and then hopefully fix the other errors you face.
stonedpsycho said:
The binary error you are getting is because you are trying to flash older filmware than what is already on the phone., this is not possible because of security updates. Downloading the latest filmware for you device should resolve this error, and then hopefully fix the other errors you face.
Click to expand...
Click to collapse
im pretty sure i have tried the latest one for my phone, as i have tried many others but i was never 100% certain it was, could you point me in the direction of one?
pazler said:
im pretty sure i have tried the latest one for my phone, as i have tried many others but i was never 100% certain it was, could you point me in the direction of one?
Click to expand...
Click to collapse
In post number 2 in the thread below, you can install "samfirm" on your Pc, this will give you the latest update to download, at a fast speed. For region (on samfirm) put your service provider, ie BTU or XEU for the UK.
https://forum.xda-developers.com/galaxy-note-8/how-to/official-stock-firmware-update-odin-t3677072
stonedpsycho said:
In post number 2 in the thread below, you can install "samfirm" on your Pc, this will give you the latest update to download, at a fast speed. For region (on samfirm) put your service provider, ie BTU or XEU for the UK.
https://forum.xda-developers.com/galaxy-note-8/how-to/official-stock-firmware-update-odin-t3677072
Click to expand...
Click to collapse
seems to of worked fine, no problems yet, thank you!
pazler said:
seems to of worked fine, no problems yet, thank you!
Click to expand...
Click to collapse
Glad to hear :highfive:
stonedpsycho said:
Glad to hear :highfive:
Click to expand...
Click to collapse
sooooo.... it was working fine for a couple days then the phone froze with a glitched horizontal line on the screen, i rebooted the phone and thought nothing more of it. A day later did the same thing (different place in the screen this time) i have wiped the cache a few time times but it hasnt improved. It is also freezing on the samsung loading screen and or getting stuck in a boot loop, the phone does work normaly for short amounts of time (few hours or so) but keeps happening, i managed to copy this log from the recovery menu if any help
p.s this is simlar to the original problem i was having before i changed the firmware
fail to open recovery_cause(no such file or directory)#
#reboot recovery cause is [unknown]#
support single-sku
file-based OTA
supported API: 3
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
# manual mode v1.0.0#
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT'(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/cid/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/cid/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/permissioins'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/permissioins'.(No such file or directory)
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree/firmware/android/compatible' : no such file or directory
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree/firmware/android/compatible' : no such file or directory
pazler said:
sooooo.... it was working fine for a couple days then the phone froze with a glitched horizontal line on the screen, i rebooted the phone and thought nothing more of it. A day later did the same thing (different place in the screen this time) i have wiped the cache a few time times but it hasnt improved. It is also freezing on the samsung loading screen and or getting stuck in a boot loop, the phone does work normaly for short amounts of time (few hours or so) but keeps happening, i managed to copy this log from the recovery menu if any help
p.s this is simlar to the original problem i was having before i changed the firmware
fail to open recovery_cause(no such file or directory)#
#reboot recovery cause is [unknown]#
support single-sku
file-based OTA
supported API: 3
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
# manual mode v1.0.0#
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT'(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/cid/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/cid/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/permissioins'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/permissioins'.(No such file or directory)
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree/firmware/android/compatible' : no such file or directory
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree/firmware/android/compatible' : no such file or directory
Click to expand...
Click to collapse
This is beyond my knowledge. I would take a guess that you have some sort of hardware issue as flashing stock filmware usually resolves any software bug. Hopefully someone who has faced the same or someone more knowledgeable will be able to help you further.
HI Experts i am getting the same issue in my note 8 sm-n950f according to my knowledge i lost its efs and baseband partition by mistake and my phone now stuck on Galaxy Logo now the OEM System is locked by default i am not able to flash TWRP please Suggest me how can i recover pretty phone back in Normal Condition :crying:
mehroz1234 said:
HI Experts i am getting the same issue in my note 8 sm-n950f according to my knowledge i lost its efs and baseband partition by mistake and my phone now stuck on Galaxy Logo now the OEM System is locked by default i am not able to flash TWRP please Suggest me how can i recover pretty phone back in Normal Condition :crying:
Click to expand...
Click to collapse
As we have said many of times before, if you lost your EFS folder and you never made a backup of it then you're screwed and you'll need to send it to Samsung for repair because you can't use anyone else's EFS because the EFS holds your IMEI and the phones serial numbers and such. It's information that's never supposed to be removed or deleted.. However someone else said if you delete certain stuff in the EFS folder and then reflash it that it would work and I tried this method and it failed to work so I don't know any other way except sending it to Samsung repair facility.. It also requires root access which you obviously can't do since it's OEM is not unlocked so I really doubt there's anything you can do short of sending it to Samsung..
https://forum.xda-developers.com/ga...i-detect-sim-card-t4134733/page2#post83127549
This is the link but like I said this didn't work for me..