Hi everyone
you know that a big problem of upgrading using multiloader is that all of applications and our data will be deleted due to a firmware upgrade
*This method is found by mylove90 so all credits goes to him
special thanks to mylove90, adfree, and everyone who have helped this developement
Upgrading using this method is by using "PFS" file like kies upgrades
1. first you should prepare two firmwares, one is the firmware which is installed on your phone and the second is the firmware you want to upgrade to
2. Then you need to extract files of the new and the old firmware so download Trix, Select input file (You can make PFS file from a mix between FFS , ShpApp , CSC (Not Rcrs compressed part)) but just FFS is enough
then go to "scripts" tab and select "fs_shell.trx" and add it then run the script and ...
3.then download Winmerge (google it!) its an open source application which compares two files or folders with one click
then compare the new firmware folder and old firmware folder
then in view tab choose the files we want for upgrading
4. the files which are needed are "Different files" and "Unique files" from new firmware, so copy them to a new folder
also the "unique files" from old firmware must be deleted so "copy path names" and change path names to the correct pattern ex:"/appex/sys/blabla"
5. we can delete these files during PFS upgrade by adding the file paths to "/debug/PfsDeleteList.txt" file which we'll include it in our PFS
5. every thing is done
now just download wave_remarker and in FW view select "open dump" and select the files which we put into a new folder!
make a new folder named "debug" and put a txt file named "PfsDeleteList.txt" which contains the path of files which should be deleted during pfs upgrade
then save file as PFS
6. open multiloader and first check "boot change" and flash the new firmware's boot files
then again flash other firmware files (which does not contain FFS, CSC, shpapp (just the files which you extracted)) and includes pfs file
*note that no checkboxes in this level should be checked in multiloader
Thanks I will test this method
I have some questions from who have made this method
when i try dumping just FFS and making pfs of that in flashing it says error: shpapp write
when i try dumping FFS and Shpapp it says error: csc wite
when i try dumping FFS and shpapp and csc it says error: pfs write
edit
for deleting extra files i try putting all file paths into pfsdeletelist.txt
should i use _CSC_FsDeletelist.ini for some of them?
Sorry
I got no clue what you did wrong
Never tested the update from bada 1.2 to 2.0
Best Regards
when i tried bada 2 to bada 2 upgrade
everything was ok but at the end it says CMD_USB_LOCK fail
i could successfully turn my phone on but after some seconds a blue screen appears and it says:
platform "so" checking is failed
Platform "so" modification is detected!!!
Then you didn't edit the file handling .so signatures to add in it new signatures
You can find such a file in the data folder with .so files
It is named : GeneralSoInfo.so.sig
Edit it with Notepad++ only
If you don't know WTH you are doing please just stop !
Best Regards
Its not ever easy.
Depend really exact on Firmwareversion and what you want or what you did...
NOT TRY if you need data on your handset.
At your own risk.
platform "so" checking is failed
Platform "so" modification is detected!!!
Click to expand...
Click to collapse
This is ""standard"" Error message...
I have seen this also during my database experiments...
DB2 folder...
Or some spxxfing thingies...
More infos possible. If you play with Debug Level MID or HIGH...
Then you got if luck Blue Screen with additional infos, what goes wrong...
Feel free to learn.
Your handset will not explode, BUT again.
Security since XXJL2 is improved... since bada 2.0 higher.
All mistakes or Errors made by oyu leads to Security fail...
So you can loss data.
Backup before all you can.
Good luck.
Best Regards
mylove90 said:
Then you didn't edit the file handling .so signatures to add in it new signatures
You can find such a file in the data folder with .so files
It is named : GeneralSoInfo.so.sig
Edit it with Notepad++ only
If you don't know WTH you are doing please just stop !
Best Regards
Click to expand...
Click to collapse
adfree said:
Its not ever easy.
Depend really exact on Firmwareversion and what you want or what you did...
NOT TRY if you need data on your handset.
At your own risk.
This is ""standard"" Error message...
I have seen this also during my database experiments...
DB2 folder...
Or some spxxfing thingies...
More infos possible. If you play with Debug Level MID or HIGH...
Then you got if luck Blue Screen with additional infos, what goes wrong...
Feel free to learn.
Your handset will not explode, BUT again.
Security since XXJL2 is improved... since bada 2.0 higher.
All mistakes or Errors made by oyu leads to Security fail...
So you can loss data.
Backup before all you can.
Good luck.
Best Regards
Click to expand...
Click to collapse
I havent touched .so files ever
but as this is a custom rum which i want to upgrade to maybe the problem is here
so i try upgrading to another fw
in learning these things nothing else is important for me
i have backup of my apps that are important for me
so i try everything with your help
I havent touched .so files ever
Click to expand...
Click to collapse
This Error message is for wide range of Security issues...
Only if you enable Debug Level to see Blue Screens for more details...
Example for Blue Screen is attached...
1.
Post your Blue Screen...
Maybe we can help you...
2.
Or upload your files.
MAYBE someone has time to check...
Maybe with password and password only via PM, to prevent noobs to kill their handsets...
3.
To add any other Apps is not good idea... also leads to fail...
Security HIGH
Best Regards
Now i have full flashed to another rom so i dont have that bluescreen to post it for you
but bluescreen is showing just that 2 lines i wrote
first of all i'll try another fw to upgrade to
maybe the problem was with this fw
if again i failed, i'll try to upload my files (cuz my internet speed is very low!!)
Oh WTF i think i've found the problem
when i make a pfs using wave remarker then i add it into multiloader, it writes s8500 in front of pfs
but my device is s8530
how can i solve this problem
i havent seen such settings in wave remarker
i myself found a solution for this and made a correct pfs
but again multiloader says CMD_USB_LOCK fail
I think the best way for me is to make a video of what i do yes?
and someone do me a favor and kindly check whats my fault
I'll make a video in the next days
but again multiloader says CMD_USB_LOCK fail
Click to expand...
Click to collapse
Depend what you did... you could ignore this from Multiloader...
I see this Info often if I play with my modified apps_compressed... or do other stuff. Then Autorestart not work with Multiloader...
Try to press ON OFF... (hold Button to force Restart)
At your own risk.
Not during Bootloader write.
Best Regards
I have encountered this error while using modified apps_compressed and rebooting was fine
but in this case when i try to reboot i see the blue screen or the handset stops on the first screen:
"WAVE 2 S8530"
"WAVE 2 S8530"
Click to expand...
Click to collapse
apps_compressed is PROTECTED by Bootloader...
It checks Integrity...
For easier handle unsecdload.fota...
This is only for S8500 available.
For S8530 you can't easy use modified apps_compressed... WITHOUT dataloss.
As you have to flash more then once ...
So all data is erased... before handset can start proper...
Best Regards
adfree said:
apps_compressed is PROTECTED by Bootloader...
It checks Integrity...
For easier handle unsecdload.fota...
This is only for S8500 available.
For S8530 you can't easy use modified apps_compressed... WITHOUT dataloss.
As you have to flash more then once ...
So all data is erased... before handset can start proper...
Best Regards
Click to expand...
Click to collapse
Thank you but you didnt understand what i mean !!
i said i see this error while editing apps_compressed too
but in this case i'm not doing that but again i see this error
this is the video of all i do:
http://dolphintest.co.cc/video.rar
i want to make a pfs for upgrading from JPKA1 to XXKL6
here i encounter error: pfs write
if you can't understand a part, mention here
Please check the video so we can solve my problem!!
video is just 10 mins so it doesnt take so much time
JPKA1
Click to expand...
Click to collapse
XXKL6
Click to expand...
Click to collapse
This is bada 2.0... I'm sure, I used often...
But is JPKA1 not bada 1.x
You can't mix bada 1 with bada 2...
Please correct me, if I'm wrong.
Best Regards
yes your right
but why we can't upgrade from bada 1.2 to bada 2?
by the way i've tried bada 1.2 to bada 1.2 upgrade and bada 2 to bada 2 upgrade but same problems
but why we can't upgrade from bada 1.2 to bada 2?
Click to expand...
Click to collapse
Samsung did some funny things...
"New" Bootloader, new Memory Map...
Compare adresses in Multiloader... so NOT same position...
So major changes... maybe not impossible for Samsung to convert some...
Anyway. Its Security reason and to have "clean new" OS.
Maybe also to clean all Spoofer...
I have not seen whole Video...
No idea yet.
Maybe someone else...
Best Regards
Related
Hello guys,
first of all a big thank you to anghelyi for explaining this to me very patiently and for uploading the files!!
Of course the credit also goes to Oleg_k, rebellos,mijoma,srg.mstr,nbates66,adfree, etc. (sorry if i haven't mentioned anyone)
As adfree said, it would be nice to have a tutorial on how to install the current state of the android on the wave , so DO THIS AT YOUR OWN RISK
It is better only for people who have experience in flashing and using multiloader..
Read this tutorial carefully and please read the entire thing! then you will have something like this
http://www.youtube.com/watch?v=YlW7g21PprQ&feature=player_embedded (credits for video - anghelyi)
THIS IS NOT THE STABLE WORKING VERSION, IT IS THE CURRENT STATE
PLEASE FOR HEAVEN'S SAKE, DONT DO THIS IF YOU DONT KNOW TO FLASH PROPERLY, YOU WILL I REPEAT YOU WILL BRICK YOUR PHONE
The procedure:
*Works on s8500XXJL2 firmware. So flash to that firmware first.
XXJL2 Firmware - http://www.multiupload.com/WMGXTWKQH2 (thanks vivekforbes for link)
if pass asked - samfirmware.com (it should be)
Stuff needed
Ubuntu (if you can find a alternate to format to ext2 you are welcome to use it)
Multiloader(google it)
Download Kernel and Filesystem : (you will get an zImage from this file, DELETE it)
http://www.megaupload.com/?d=CI0QUBLY
The new zImage: (credit - anghelyi)
dowload either from :
http://badadroid.googlecode.com/files/zImage.anghelyi
and rename the file to just zImage without the .anghelyi
If lazy to rename just download from here:
http://www.mediafire.com/?xl5aikl5e8r7hv4
Updated FOTA (boot without USB cable
http://badadroid.googlecode.com/files/kernel_boot.fota
Sbl.bin
http://badadroid.googlecode.com/files/sbl.bin
XXJEE bootloader
http://badadroid.googlecode.com/files/S8500XXJEE_BL.zip
Work Begins :
1) Extract the files after download
2) Create folder "galaxyboot" (without quotes) in Wave internal memory and put the sbl.bin and the zImage to this folder.
3)Ok, now get into ubuntu and do the following :
Make two partitons using gparted on ubuntu , one fat32 and other ext2
You have to copy those files while being a root user in ubuntu. For this :
Open a terminal
Type "sudo su" without quotes in terminal
Enter new password
Then click the power button on top right
Login with username as root and password as the pass u entered
Open terminal
Type "sudo file-roller" it will open the archive manager.
Use archive manager to extract files from badadroid.tgz -> filesystem.tgz -> You need to extract 5 folders(system,lfs,dbdata,data,cache..select these 5) to ext2 drive directly.
Copy the new zimage and sbl.bin to galaxyboot folder(create it if it doesnt exist) in wave internal memory
In terminal type "sudo nautilus"
A window will open
Go to ext2 partition system/media/audio and rename "ui" folder to "uibackup"
Open Terminal
Now in terminal type "sudo sync"
Unmount the partitions before unplugging the phone (this step helped milli133 )
RISK RISK RISK RISK
4) Replace the bootloader to XXJEE one
5) Replace the FOTA with the one you have downloaded
TIP - to those who dont know the above two steps : (thanks vivekforbes)
=> Open multiloader and select LSI and select FULL DOWNLOAD
=> Select boot(use xxjee boot files) and FOTA ( precompiled one in above download)
=> click download to flash..
RISK OVER
6) Switch phone on normally to see if Bada is loading
7) Turn off phone, Press and hold call button + power button
8) Thats it! Android is on your phone
Oh disable swype in the settings menu else your keyboard wont work!
DONT DELETE ANY APK FILES, ANDROID WILL WORK FINE WITHOUT DELETING THEM
Enjoy
please dont complain if you brick your phone, i cant test it since i have s8530
umm
how do i delete this thread
cfernr says people may brick their phones because of this
Thank you.
I will try in next 2 days. Then I'll post my results... or my new Questions.
Best Regards
cfernr says people may brick their phones because of this
Click to expand...
Click to collapse
Please let this Thread alive.
HIGH RISK to brick handset
But you can choose self if it is worth to try.
Thanx in advance.
Best Regards
kadavil said:
RISK RISK RISK RISK
4) Replace the bootloader to XXJEE one
5) Replace the FOTA with the one you have downloaded
RISK OVER
Click to expand...
Click to collapse
one little question to these 2 steps:
is there a special method to replace them or do i just flash those 2 only with multiloader?
~MaX~ said:
one little question to these 2 steps:
is there a special method to replace them or do i just flash those 2 only with multiloader?
Click to expand...
Click to collapse
multiloader unless there is some other way to do it
kadavil said:
multiloader unless there is some other way to do it
Click to expand...
Click to collapse
thanks! so its just that easy as adding these 2 files to multiloader and flash them?
any special configuration options for multiloader?
~MaX~ said:
thanks! so its just that easy as adding these 2 files to multiloader and flash them?
any special configuration options for multiloader?
Click to expand...
Click to collapse
lol i dont know
let some PRO answer that
EDIT:
Yes it is through multiloader
thanks vivekforbes
kadavil said:
lol i dont know
let some PRO answer that
Click to expand...
Click to collapse
okay
better a litt,le time to wait than to brick the phone
Why in hell would you even want to get an unstable version of Android on your Wave?
Seriously, this thread should be deleted. Is it just so people can say, "look at me, I have Android on my Wave"??
Just wait until the guys have a stable and working version, instead of harassing them all the time in the other thread.
You will just stuff your phone up and brick it. It's not worth it.
kadavil said:
umm
how do i delete this thread
cfernr says people may brick their phones because of this
Click to expand...
Click to collapse
You can't delete a thread. Only mods can. But even though there's a risk of bricking your phone, people have a choice to do this and this could grow into a wonderful development. So this thread should continue and see what other developers can put into this to make it a stable build.
Altough people can blow up their houses, there exists detailed instructions how to make highly explosive materials.
You've made good howto with alot of warnings, I don't think you can and should feel responsible for any bricked handset.
I have requested this Thread.
Thank you very much kadavil.
To others. Please be sure you know what this means:
Bada Software and Hacking General
Technical discussion of Bada development and hacking. No noobs please.
Click to expand...
Click to collapse
Nobody is forced to try it.
Please stop "sabotage" and censorship.
I am old enough to know what I do.
All at your own risk.
Best Regards
kadavil said:
3) Then create a second partition (it must be the second partition!) with ext2 filesystem on your SD card and extract the filesystem here. (http://www.ehow.com/how_7492668_create-ext2-partition-windows.html)
Click to expand...
Click to collapse
Second partition?you mean logical partition?
Does anybody have the XXJEE bootloader? It's not in the XXJEE firmware on samfirmware.
tom112112 said:
Does anybody have the XXJEE bootloader? It's not in the XXJEE firmware on samfirmware.
Click to expand...
Click to collapse
http://code.google.com/p/badadroid/downloads/detail?name=S8500XXJEE_BL.zip&can=2&q=
How back to pure bada ? ( delete files from sd and flash via multiloader to bada ? )
pawlakpl said:
How back to pure bada ? ( delete files from sd and flash via multiloader to bada ? )
Click to expand...
Click to collapse
Just turn off the phone and turn it on holding the off button....
Just a little question, What's working and what's not working ?
PS: Sorry for my English
what is this step ?
Connect Wave to PC
edit : need i a special program installed on my PC or any speciall cable?
Hi every one !
I'm using the Belgian firmware with a Wave 2 TLBLB1 and I'm getting some strange errors after an upadte :
- The boot screen is reversed
- The boot animation is played in reverse
(just annoying)
- After doing the Samsung apps update it can't launch it says : " Impossible to launch (...) invalid app"
I tried several times to hard reset and recover a clean bada but after each samsung apps update the same error appear.
Does some know from where those errors come from ?
Thanks in advance.
Solution :
- Do a hard reset
- Don't recover your settings files and apps
- Do the update
Solution 2, thanks to mylove90 :
-Try removing it by deleting its folder with TK file explorer (edit ini file to make it work with bada 2.0)
-Copy Samsung Apps.oap file....i'll assume you know the path of that file
-Open it with 7z or any other program
-Edit manifest.xml file to give it higher version number
Click to expand...
Click to collapse
Are you updated your phone via OTA ?
Yes it was an OTA update. But apart from the bug I listed, everything works fine.
Exactly Don't know about samsung apps but Reversed also for me as this
http://forum.xda-developers.com/showpost.php?p=25923810&postcount=119
hahahahahahahahaha
These bugs are so funny
Thanks to Samsung we don't have OTA updates in Egypt
But i guess that you just got a bad Samsung Apps update
-Try removing it by deleting its folder with TK file explorer (edit ini file to make it work with bada 2.0)
-Copy Samsung Apps.oap file....i'll assume you know the path of that file
-Open it with 7z or any other program
-Edit manifest.xml file to give it higher version number
In Theory , This should prevent the update & make your Samsung Apps work
Best Regards
Yeah it's exactly the same... It should be normal for Samsung that the phone boot that way...
Could it be a general error from the OTA system update ?
For the samsung apps I expect the same bug since it was also with an OTA update.
Edit : yes I will try later this method I don't have time to do it right know I will report when I did it.
Edit 2 : So I hard reset and try again to update and it works even after the update. But after recovering my files it bugs. I will try to recover before updating.
Just a simple/noob question how do you express the files into a .oap file ?
Edit 3 : WTF it works. It should have been a setting error. Strange.
This is NO bug...
This is VISUAL teststuff...
Firmware like XXKKV... XXLAV, XXLBV
These are for internal testing... it is easier to see if success, instead wait and enter *#1234#
Read here:
http://forum.xda-developers.com/showthread.php?t=1363328
Remember... as V is highest "Character/Digit"... Kies nor OTA update again...
You have minimum to flash other apps_compressed.bin with Multiloader.
Best Regards
adfree said:
This is NO bug...
This is VISUAL teststuff...
Click to expand...
Click to collapse
Thanks I didn't know.
Anyway it works great. I'll wait untill next firmware.
We are now able to create patches for the FFS, SHPAPP and CSCfs areas using the PFS format, but I haven't found anything similar for the RC1 area. This would be immensely useful, as we'd be able to make design changes (like icon replacements, quickpanel, ...) without replacing the full RC1 file (which might lead to other problems, as these vary between different FWs).
Is there any possibility to patch the RC1 area via a MultiLoader patchfile (similar to PFS)? Any ideas?
k8500 said:
We are now able to create patches for the FFS, SHPAPP and CSCfs areas using the PFS format, but I haven't found anything similar for the RC1 area. This would be immensely useful, as we'd be able to make design changes (like icon replacements, quickpanel, ...) without replacing the full RC1 file (which might lead to other problems, as these vary between different FWs).
Is there any possibility to patch the RC1 area via a MultiLoader patchfile (similar to PFS)? Any ideas?
Click to expand...
Click to collapse
Nice idea...
This would make some changes much more easier...
1.
RC1 is mounted Image with READ Only access...
No writing...
No idea how to add Write access...
2.
Paths could be spread over more then 1 file...
apps_compressed.bin and/or *.so files involved...
http://forum.xda-developers.com/showpost.php?p=33706880&postcount=247
See here... its seems mirror paths... maybe we can use them...
3.
Reduce RC1 for faster testing.
This is 1 reason why I have create such files.
http://forum.xda-developers.com/showpost.php?p=32439954&postcount=112
Best Regards
http://wapinet.ru/files/show.htm?d=1885&f=nv_default.ini
Seems from U800...
But check this:
Code:
NV_SI_SKIN_COLOR_BASE_BITMAP_PATH=/System/Rsrc/Bmp/Black/
NV_SI_SKIN_COLOR_USED_BITMAP_PATH=/System/Rsrc/Bmp/Black/
Best Regards
Edit 1...
Seems also in Wave... Check this Thread:
http://forum.xda-developers.com/showthread.php?t=1507782
I will try...
Code:
/System/Rsrc/Bmp/Black/
/Media/Others/Bm/Black/
---------- Post added at 06:08 AM ---------- Previous post was at 05:36 AM ----------
Seems working...
Easy Text Edit...
Step 1.
FmSecureMode off
Step 2.
Copy folder NV... you need only nv_default.ini
Step 3.
Change paths...
Example:
Code:
/System/Rsrc/Bmp/Black/
[B]/Media/Others/Bm/Black/[/B]
Step 4.
Copy back nv_default.ini
CAUTION!!!
At your own risk.
Better create before folder /Media/Others/Bm/Black/
And copy all RBM files you need.
Best Regards
Cool !! How to disable FmSecure ?
http://forum.xda-developers.com/showpost.php?p=12436452&postcount=1
With QuB or other Tools possible...
Remember Screenshot Tool from User Dokugogagoji...
1 Click
Best Regards
I was just in the process of giving up, and then you come up with this. Absolutely great! Now, I'm going to do some experiments of my own. This will make everything that much easier.
k8500 said:
I was just in the process of giving up, and then you come up with this. Absolutely great! Now, I'm going to do some experiments of my own. This will make everything that much easier.
Click to expand...
Click to collapse
I didn't have success.If you'll be get it.Just tell me
hero355 said:
I didn't have success.If you'll be get it.Just tell me
Click to expand...
Click to collapse
It didn't work for me either... FMSecureMode Off and editing nv_default.ini works without trouble. Regardless of any changes, the actual RBM path does stay the same: Changes in the new Rbm path don't show up, and flashing a RC1 with an empty Rbm folder leads to bad graphical errors. Doing the changes via a full flash (nv_original.ini edited and Rbms in SHPAPP or FFS) doesn't change anything either (checked nv_default.ini after the full flash, paths are changed).
Adfree, I guess we did something wrong :-|.
k8500 said:
It didn't work for me either... FMSecureMode Off and editing nv_default.ini works without trouble. Regardless of any changes, the actual RBM path does stay the same: Changes in the new Rbm path don't show up, and flashing a RC1 with an empty Rbm folder leads to bad graphical errors. Doing the changes via a full flash (nv_original.ini edited and Rbms in SHPAPP or FFS) doesn't change anything either (checked nv_default.ini after the full flash, paths are changed).
Adfree, I guess we did something wrong :-|.
Click to expand...
Click to collapse
+++ I agree Waiting adfree's response
Big sorry, seems false alarm.
Best Regards
adfree said:
Big sorry, seems false alarm.
Best Regards
Click to expand...
Click to collapse
No problem, but that would have been great . BTW, I risked it today and flashed the Android boot loader. No bad consequences so far .
Next attempt... according to this. I made test...
http://forum.xda-developers.com/showpost.php?p=33706880&postcount=247
1.
Created second folder in RC1:
Code:
/System/Rsrc/Bmp/Red/
2.
Changed black folder to red in nv_default.ini
Not working...
Next attempt will be then ShpWindow.so
Maybe I can change to /System/Rsrc/Bmp/Red/ to think about further steps...
Best Regards
Edit 1.
It seems this time more luck with ShpWindow.so.
First succes 2 folders in RC1
Code:
/System/Rsrc/Bmp/Black/
/System/Rsrc/Bmp/Bl[B][COLOR="Red"]o[/COLOR][/B]ck/
Folder Black nearly empty... Block contain whole files from Black.
S8500 starts normal and shows all RBMs...
Now I'll try to change path again to MEdiablablbal...
Best Regards
Edit 2.
It seems ShpWindow.so can only look into RC1 Image...
So it checks System folder only.
Otherwise it jumps to given path by apps_compressed.bin... :crying:
And here I can see only .Rsrc/Bmp/Black/ ...
So I can't here change into /Media/Others/ :crying: :crying:
Best Regards
For those who are still waiting for a fix for the update error and don't want to undergo the recovery process, I found a different solution, which doesn't need a recovery operation on the phone.
I tested it with success on my 1020 and another 925 which were stuck in the CU build .297.
Keep in mind that the parameters that I will use are specific to these phone models, so if you have a different one you need to find the parameters specific to your phone model.
This is an heuristic procedure, tested on a limited number of phones, so use it at your risk, keeping in mind that you could have problems or need to recover your phone loosing all your data, so do a proper backup before.
Let's start.
The problem appears because, during update phase, the oeminput.xml file becomes corrupted: as far as I know it happens only on some x20 models, and not for all the users.
Now we're going to rebuild it...
Go to the following link
https://msdn.microsoft.com/en-us/library/windows/hardware/dn756630(v=vs.85).aspx
Copy the content of example file oeminput.xml: i.e. copy the content of the framed zone after the phrase "The following example shows the contents of a sample ProductionOEMInput.xml file"
Paste in a .txt file which you'll rename and change extension so that it becomes oeminput.xml. Save it with notepad.
Now modify the file
at the node <SOC>{PROCESSOR_NAME}</SOC> modify {PROCESSOR_NAME} fake parameter in order to have the processor name of your phone: for the 920/925/1020 use QC8960
at the node <Resolution>480x800</Resolution> instead of 480x800 use the resolution of your phone: for the 920/925/1020 use 768x1280
in all the nodes related to language <Language>en-US</Language> use the language of your phone: I used for example it-IT because I have the phone in Italian language.
Save the file.
Now if you still don't have interop tools installed (but I think you should have if you arrived to CU with an x20 phone model) install it.
Launch interop tools and then click this device and enable full file system access. Reboot your phone, connect it to a pc with cable: you'll see more directories than usual, because you also unlocked system dirs: be careful not to delete or modify any dir apart from what you find in this guide or you'll risk to damage your phone. If you want to find your usual dirs (docs photos...etc), go to phone\Data\Users\Public. I advise you that after the procedure I couldn't deactivate full file system access, because it continues re-activating in interop tools, maybe there is a way: but you can live with this, because you can find the usual dirs in the path that I specified...
Now go to phone\windows\imageupdate, make a backup on pc of the current oeminput.xml and overwrite it with the new one.
At this point in the phone go to settings, update and then search for updates: you should find Fall Creators Update...
Good Luck!
p.s. I didn't extensively search on the forum if a similar guide has been already posted, in the case sorry for the duplication.
Thanks to Antonio who has actively participated in the realization of this guide
sigfrid696 said:
https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx
Click to expand...
Click to collapse
The link is wrong
Thank you!
I modified it, now it should be ok!
friend can you share the oeminput.xml file that you used?
NeoTriXz said:
friend can you share the oeminput.xml file that you used?
Click to expand...
Click to collapse
Done! Let me know if it works...change only language to match your phone language and do a proper backup of your original file...
sigfrid696 said:
Done! Let me know if it works...change only language to match your phone language and do a proper backup of your original file...
Click to expand...
Click to collapse
no friend did not work, I keep throwing the same error, some idea that can be or another solution?
NeoTriXz said:
no friend did not work, I keep throwing the same error, some idea that can be or another solution?
Click to expand...
Click to collapse
At this point I think it's not a problem of corrupted oeminput file.
I googled around...not so many people having the problem...I found this link...
https://answers.microsoft.com/de-de...nd-eimem/0a6e1776-9005-40e8-a18e-9eaf0f35b648
It's in german language, but from what I understood the problem has been solved with Recovery Tool via pc: I know that's not the best solution, but maybe better than remaining without updates. Another significative information is that an hard reset alone doesn't solve the issue!
I hope that can be of any help...
sigfrid696 said:
At this point I think it's not a problem of corrupted oeminput file.
I googled around...not so many people having the problem...I found this link...
https://answers.microsoft.com/de-de...nd-eimem/0a6e1776-9005-40e8-a18e-9eaf0f35b648
It's in german language, but from what I understood the problem has been solved with Recovery Tool via pc: I know that's not the best solution, but maybe better than remaining without updates. Another significative information is that an hard reset alone doesn't solve the issue!
I hope that can be of any help...
Click to expand...
Click to collapse
thank you friend, for your time, but I already solved it, well I had to perform a hard reset,
does this works for lumia 520
and what parameter should i used for my lumia 520 Rm 914
i'm stuck on 15063.251
and my lumia finds fall cu update
but shows Error 0x80070273
does this really resolve this error
i could not able to copy paste it it shows you don't have permission
how i get permission
---------- Post added at 06:42 AM ---------- Previous post was at 06:22 AM ----------
it gives me this error
Yash Agarwal windows said:
does this works for lumia 520
and what parameter should i used for my lumia 520 Rm 914
i'm stuck on 15063.251
and my lumia finds fall cu update
but shows Error 0x80070273
does this really resolve this error
Click to expand...
Click to collapse
I think you should use for 520
<SOC>QC8227</SOC>
<Resolution>480x800</Resolution>
If you receive an error when you try to overwrite oeminput.xml, it means that your phone has not been unlocked for full filesystem access. Please refer to the guide in order to enable full filesystem access
thanks
it worked for me
Getting this error code - 0x8018830f while updating to 14393.1884 (Lumia 730)
Can I try the fix from this post for this error?
Donz7733 said:
Getting this error code - 0x8018830f while updating to 14393.1884 (Lumia 730)
Can I try the fix from this post for this error?
Click to expand...
Click to collapse
this error is get due to incorrect processor no or incorrect screen resolution
Donz7733 said:
Getting this error code - 0x8018830f while updating to 14393.1884 (Lumia 730)
Can I try the fix from this post for this error?
Click to expand...
Click to collapse
You can examine your oeminput.xml file and check if it is somehow not well-formed.
If that is the case you can use
<SOC>QC8926</SOC>
<Resolution>720x1280</Resolution>
Thanks for the reply guys.
I couldn't wait longer, so went with an reset. It updated fine after that.
Later came to know it was some server issue
how do you replace the xml file? it says copying but refuses to actually replace the file.
rancorx2 said:
how do you replace the xml file? it says copying but refuses to actually replace the file.
Click to expand...
Click to collapse
you should need completely interop unlock your device using interop tools
then restart your phone
then after it copies without error
Yash Agarwal windows said:
you should need completely interop unlock your device using interop tools
then restart your phone
then after it copies without error
Click to expand...
Click to collapse
how is complete unlock ??????????
I use interop tools
bloody_earth said:
how is complete unlock ??????????
I use interop tools
Click to expand...
Click to collapse
The error overwriting oeminput.xml happens when you haven't obtained full filesystem access.
In order to obtain full filesystem access:
Open Interop Tools, then this device, then Interop Unlock.
Check Full Filesysytem Access and restart your device.
Refer to this thread to download correct version of Interop Tools
https://forum.xda-developers.com/windows-10-mobile/tutorial-restore-glance-windows-10-t3540571
Let me know if you can solve the problem this way.
Hi All,
I downloaded the ROM for SM-R800 and would like to extract the contents of rootfs.img file.
But no success after renaming the extension to .zip and .rar.
Basically I want the system dump of the watch.
Would someone be able to share it with me?
As an Windows Fanboy... I am using WinHex to extract files from rootfs.img...
Best Regards
adfree said:
As an Windows Fanboy... I am using WinHex to extract files from rootfs.img...
Best Regards
Click to expand...
Click to collapse
Hi adfree,
Thanks for the advise. I installed Winhex, but I am finidng it difficult to extract the data. Openening the rootfs.img I get a lot of hexadecimal numbers as shown below.
Kindly request your guidance.
Here are Screenshots with WinHex...
Other way is to use for instance Tizen Studio and mount in Emulator... longer way...
Never tested with Linux PC...
Best Regards
rockz1991 said:
Hi All,
I downloaded the ROM for SM-R800 and would like to extract the contents of rootfs.img file.
But no success after renaming the extension to .zip and .rar.
Basically I want the system dump of the watch.
Would someone be able to share it with me?
Click to expand...
Click to collapse
How did you dump the ROM for SM-R800?? Can you please explain what you did?
I0T said:
How did you dump the ROM for SM-R800?? Can you please explain what you did?
Click to expand...
Click to collapse
I just googled the firmware. I didn't dump.
adfree said:
Here are Screenshots with WinHex...
Other way is to use for instance Tizen Studio and mount in Emulator... longer way...
Never tested with Linux PC...
Best Regards
Click to expand...
Click to collapse
I tried this but only get a message that size is not a multiple of 512 and there is an incomplete RAW image. Please let me know what steps you took to be able to read this information thanks.
@Mr Bigglesworth
Sorry, still too laz ehm busy to answer PMs...
Can you give full details...
SM-R815?
Because SM-R815U SM-R815F SM-R815W...
And Firmware you tried...
Filename...
Samsung did same "magic"... so few rootfs.img are easily extract able via 7Zip Tool...
Best Regards
Originally I looked at COMBINATION-FT40_R815FXXU1ASB1 (for my 815f). Then failed so I just tried looking in a r800 image (r800xxu1arh3) as my first stage was really to understand the make up and what changes might have happened between firmware, so it didn't need to be the specific firmware for my watch. Both returned the same when using winhex, and both have an error message if trying 7zip, the the file is corrupted. Do you know which firmware might be readable using 7zip as a start? Thanks