yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi A1 Guides, News, & Discussion] SevenSlevin:
and why in that ss is used old baseband?? Xiaomi decided to revert baseband on oreo 8.1??

Baseband of gennuary/febbruary was: ta.2.3....

New baseband is: 953_gen....

For me it is fake, and anyway need a screen of OTA update when it is downloading. SS of system info means nothing.
[Xiaomi Mi A1 Guides, News, & Discussion] Anarchy666:
I really think that we'll recieve Android 8.1 at the end of this month, but the second thing that makes me doubt about originality of this screenshot is that I have never seen Xiaomi provide latest android security patch level with vendor/kernel specific patches, I mean it's always been like 01/04/2018, not 05/04/2018.
[Xiaomi Mi A1 Guides, News, & Discussion] N1ck474:
You can edit it too.

I need the download link ?
[Xiaomi Mi A1 Guides, News, & Discussion] Uvneshkumar:
I don't think so. What's the point of doing it? We don't even know who did this. So I think this is real.
[Xiaomi Mi A1 Guides, News, & Discussion] AndroGeek911:
Cant Trust Xiaomi

From past experience we cannot really say that this is legit. My be xiaomi are focusing more on MIIU running devices than their only stock android device and i doubt they will even make another successor of Mi a1. Their poll in twitter might have hurt their ego and might be taking sort of revenge on Android One device (No judgement Just a Thought)
[Xiaomi Mi A1 Guides, News, & Discussion] Uvneshkumar:
If xiaomi is smart enough, they'd definitely don't want to loose the customers who love stock ROM. There are a lot of people who love xiaomi for it's great value for money hardware spec and stock ROM experience. And xiaomi knows it very well. If xiaomi is smart enough, it'll update Mi A1 to 8.1.0 and will keep introducing new phones in the A1 lineup. That's what the most they can do to get both MIUI and Stock ROM lovers towards them.
[Xiaomi Mi A1 Guides, News, & Discussion] BtB:
I personally believe it's fake. I had 8.1 on my Nexus 5X before I switched to Mi A1, and 8.1 did bring back the traffic indicator arrows inside the icons, and the signal icons are slightly rounded at the edges. The picture is not very good quality, but they don't seem to have that rounded aspect on that screenshot.

Doesn't mean I don't believe we'll get 8.1, but this screenshot, I think it's fake.
[Huawei P20 Pro Questions & Answers] volco:
Hi, now that some of you have the P20 Pro in your hands, whats the haptic feedback like in comparison to other phones such as the iPhone X?
[Huawei P20 Pro Questions & Answers] Vogal:
Hi, i feel it soft. Softer than my previous S8.
[Huawei P20 Pro Questions & Answers] ketman5001:
When pressing finger print sensor or what ? I mean when exactly can you feel that haptic feedback
[Huawei P20 Pro Questions & Answers] volco:
If you hold down the middle O button, you can feel some nice haptic feedback there. But over the rest of the phone its just seems standard vibration.

Its a bit of a shame as it seems to have the hardware capable of advanced haptic feedback, hold down the O and you can feel it pull then poing.

Seems like its software limited, I would if its possible to develop an app to utilize it better across the OS.
[Xiaomi Mi Mix 2 Questions & Answers] Arn__:
I'm sorry for posting this here (I did't posted enough to have access to post new threads in the ROM section)

I ported the Red Wolf recovery (based on TWRP 3) for the Mi Mix 2.

I did not compile it from source but merged the RedWolf-027-kenzo.img and an unofficial TWRP-build for the Mi Mix2

Known bugs:

Touchscreen does not respond till the screen is locked and unlocked

Flashlight does not work

backing up wifi (and other special) partition (probably not set in fstab)

...

Tested and working:

Mounting partitions including the SDCARD

Setting up a password

Flashing ROM's and ZIP's

...

All credits to the RedWolf team, TWRP team and the person who ported TWRP to the Mi Mix 2 in the first place.

Download:

https://www.androidfilehost.com/?fid=890129502657597234

MD5 checksum: 5281496e745c1aeaf49f2cb09f91a98a

More about RedWolf Recovery and its features:

http://redwolfrecovery.cf/

Use at own risk. My phone is still alive after flashing a new ROM so I assume it's ok to use..
[Xiaomi Mi Mix 2 Questions & Answers] GuestX0006:
fingerprint sensor stopped working for me after a few rom flashes. also official twrp is now available, is this still being maintained?
[Xiaomi Mi Mix 2 Questions & Answers] Arn__:
It doesn't matter if you use TWRP, Redwolf recovery or any other recovery. I have no plans to maintain this recovery. Maybe when a newer Redwolf comes with extra features in a newer version I port a new version.

When you flash a different rom it is recommended to clear data. You can try to roll back to the last working rom and hope your settings and and data of your fingerprint sensor will work again. DIsabling and enabling your fingerprint can also do the trick. Otherwise restore a backup or clear data, cache and dalvic cache.
[OnePlus 5T  Questions & Answers] eerrroh:
Hello.

I'm trying to find a rom which have full black theme system wide since i'm sensitive to white.

If possible, substratum-less.

Thank you.
[OnePlus 5T  Questions & Answers] vipsms:
Any AOSP oreo rom should do the work fine, just install substratum either with root or andromeda app then install swift black theme which costs around dollar or two.

---------- Post added at 09:20 PM ---------- Previous post was at 09:16 PM ----------

Maybe off topic, but if you use desktop chrome browser, try "dark reader" extension. It is great :)
[OnePlus 5T  Questions & Answers] eerrroh:
I tried OmniRom with what you said, but it doesn't theme anything.
[OnePlus 5T  Questions & Answers] eerrroh:
I tried OmniRom with what you said, but it doesn't theme anything.... or it does ! For some reasons, it worked the second time i activated the theme.
[OnePlus 5T  Questions & Answers] vipsms:
yeah it should work as omnirom supports OMS theme. just make sure to update your themed apps when swift black theme gets an update to avoid any issues.
[Samsung Galaxy J ROMs, Kernels, Recoveries, & Othe] XxViRUsPRO:
Tuti OS by [MENTION=8203069]XxViRUsPRO[/MENTION]

You are NOT allowed to use any part of this rom without my permission!​

/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

THIS IS ONLY FOR SM-J110H

​

-I MADE THIS ROM JUST FOR FUN MAYBE I WILL MOD IT LATER CUZ ITS NOT MY PHONE ITS MY FRIEND PHONE

-Based On: J110HXXU0AQI1 (Latest Security Patch)

-Debloat

-DeKnoxed

-BusyBox Added

-Rooted

-OPTIMIzED

-Build.prop Tweaks

-Intid Support

-Adb At Boot Support

-Patched SEPolicy

#Rom Size:370MB#

DOWNLOAD LINK:HERE!

DONT FORGOT THANKS BUTTOM!!!
[Samsung Galaxy J ROMs, Kernels, Recoveries, & Othe] shaik shakur:
i flashed this rom but i stuck on samsung logo
[Samsung Galaxy J ROMs, Kernels, Recoveries, & Othe] whitehackeruz:
Mine Too. This ROM is suck
[Samsung Galaxy J ROMs, Kernels, Recoveries, & Othe] whitehackeruz:
Same
[Xiaomi Redmi 2 Questions & Answers] Destrocamil:
[SOLVED; MOD PLS DELETE]

Hello guys,

Well, short story: had an oneplus one, today i woke up with the usb port melted and a very dizzy burnt smoke. The replacement phone i got is a Redmi 2. Since i'm a "pure" Android fan, can not stand with the MIUI.

I used the "Newbie" guide here to unlock bootloader and install twrp(i'm pretty used to it and know the basics).

After that, i installed AOKP 8, it boots correctly and it work, but a message keeps poping up every boot:

"A vendor image mismatch has been detected. Typically this means your vendor image is out of date. Please ensure your vendor image matches LMY47V".

Any help with this? Any fix? Anything that i did not notice?

THANKS!
[Xiaomi Redmi 2 Questions & Answers] jorgeenriqueruizflorez:
I think (just think, not sure) it's about the firmware. If you got a Redmi 2, it's probably that it runned KitKat before you flash a custom ROM.

As you didn't mention flashing Lollipop firmware, my suggestion is: If you want to use a ROM that is Lollipop or higher, you need to flash Lollipop firmware before flashing ROM. You can find it in the third post in Lineage thread for Redmi 2.

I say I'm not sure, because I've flashed Lollipop firmware a while ago, but last week when I flashed AOKP, the same message came every boot.

Maybe you can try wiping everything, flash Lollipop firmware and then flash ROM and Gapps.

If that works for you (or not), then you can confirm here and help someone else having that same issue.

Good luck!
[Xiaomi Redmi 2 Questions & Answers] hariGS:
that's just mismatch error nothing serious

first flash this firmware via twrp https://androidfilehost.com/?fid=673368273298919092 and then flash any ROM :)
[Xiaomi Redmi 2 Questions & Answers] Destrocamil:
Hello to both,

First sorry for the delay, i was travelling and internet connection , you know, meeehh!

I did notice that after a few minutes searching and flashed the firmware and it is running butter smoth!!

Thanks to everyone, guys!
[LeEco Le Pro3 Guides, News, & Discussion] Sony make.believe:
Hey guys,

a few minutes ago, someone posted on ydss a new ROM for our device!

Mod Edit: Link removed

BE VERY CAREFUL! X722/X727 HAVE A HIGH RISK TO GET HARD BRICKED!

Instructions for download are in the description, or here:

Mod Edit: Link removed

I also re-uploaded the file (this is available for 30 days):

Mod Edit: Link removed

I don't know any features of this ROM (Only, that its build on LOS tree). But if you want to know more about this developer team, here is the offical site for more information:

Mod Edit: Link removed

Bugs I've found:

- Cannot control brightness through notification center

Please feel free to test this and give us all a feedback! :)
[LeEco Le Pro3 Guides, News, & Discussion] collisiion:
if u can upload it i would appreciate, im downloading from chinese forum and it will be complete in 90 hours lol
[LeEco Le Pro3 Guides, News, & Discussion] Sony make.believe:
I need 20 minutes, I will reupload it then
[LeEco Le Pro3 Guides, News, & Discussion] collisiion:
thanks :)
[LeEco Le Pro3 Guides, News, & Discussion] Sony make.believe:
No problem, please test it and give me a feedback!
[LeEco Le Pro3 Guides, News, & Discussion] collisiion:
tomorrow i'll do it
[LeEco Le Pro3 Guides, News, & Discussion] mchlbenner:
To any 727 users leave this alone will not turn out well.
[LeEco Le Pro3 Guides, News, & Discussion] tsongming:
It seems to be based on Lineage and free! Wow, usually, I can't download anything from this site.

Here is the English website for this Rom: https://dotos.github.io/

Download Address: https://pan.baidu.com/s/19fMOynX1aOlKx2S0HvHj5g

Password:

dyns

Seems okay to me : here is the Github pages: https://github.com/dotos and www.github.com/lineageos

---------- Post added at 11:51 PM ---------- Previous post was at 11:47 PM ----------

Sorry,

I duplicated some of your comments, my webpage had not yet refreshed and I only saw part of your original post before clicking the link.

Nice Find, I am not installing it. But, still glad to hear about more roms being made for our devices.

---------- Post added 10th April 2018 at 12:06 AM ---------- Previous post was 9th April 2018 at 11:51 PM ----------

Right, so far I have only seen that it's official for other Leeco devices but not the Le Pro 3.

I guess the link is for a unofficial build? Or maybe it's strictly for the Cool S1?

I believe the S1 has the exact same specs as the X727. But, I have installed installed S1 roms on my phone in the past and it would get very hot, so if this ROm is strictly for the S1, I would agree with you and not try it.

They have many official roms, and alot of developers. So I would guess, that something specific for the X727 or X720 will turn up soon.
[LeEco Le Pro3 Guides, News, & Discussion] Hidden1977:
Working for x722?
[LeEco Le Pro3 Guides, News, & Discussion] Sony make.believe:
Yes, on ydss it shows in the description "for Cool S1 and Le Pro 3".

So those who wanna try, can do it, but only if you do a nandroid backup before! :)
[LeEco Le Pro3 Guides, News, & Discussion] Hidden1977:
Thx. currently my leaders are Aosp extended and RR. But it is worth checking.
[LeEco Le Pro3 Guides, News, & Discussion] tomgar:
Be careful!!! I have a x722, have installed this ROM and my phone has died. Now,my phone is a stone.Don't turn on,don't chargue,don't is recognizeded for the computer,don't work led of notifications.

I hate this thread. Thanks to the comment of our partner my phone is dead.

Thanks for all.
[LeEco Le Pro3 Guides, News, & Discussion] mchlbenner:
I had early warned about this rom you need to read all threads in this small thread

It your fault no one else's!
[LeEco Le Pro3 Guides, News, & Discussion] tomgar:
No,this thread was edited after I installed this ROM. Have you read any comments about the compatibility with x722?.

I read the warned but it was after.

You can read "Last edited by Sony make.belive; Yesterday at 08:18 PM. Reason: Warning for hard bricking" so it is not my fault.
[LeEco Le Pro3 Guides, News, & Discussion] Oel:
You are always responsible for ehat you flash to your phone.

I look always into the downloaded zip, BEFORE i flash ir. In this zip here, is included a firmware.zip. This means, it will flash a firmware to your phone.

And now think, can it be, that one firmwate will fit different phones?

No.

But this bricked your phone.

We all now the risk of flashing. I am a flashaholic, but it's always clear for my, it's my fault if something gets wrong.

Nobody will make pressure to me to flash his rom. Its always my opinion.

So act like an adult person and don't blame other peoplr for your own decision.
[LeEco Le Pro3 Guides, News, & Discussion] mchlbenner:
Don't blame other for your mistakes.

When ever you flash anything you have chance of being bricked.

On top it said for 720 so you took that chance when you decided to flash it.

I also flashed it and had a had time getting into recovery to get rid of it.

If it had bricked me it would have been my fault.
[LeEco Le Pro3 Guides, News, & Discussion] tomgar:
"Quote:

Originally Posted by Hidden1977

Working for x722?

Yes, on ydss it shows in the description "for Cool S1 and Le Pro 3".

So those who wanna try, can do it, but only if you do a nandroid backup before!"

This information is false.

If you like that somebody can upload any custom ROM I see it perfect but is not my opinion.

Administrators should see what content users up in the forum.

I wish that tomorrow yours phones are a brick in your walls.
[LeEco Le Pro3 Guides, News, & Discussion] Oel:
How old you are?

13?
[LeEco Le Pro3 Guides, News, & Discussion] tomgar:
Is this your argument? can you explain me why that false information?.
[LeEco Le Pro3 Guides, News, & Discussion] Oel:
He is not the developer from this rom. And when you read the question and his answer, you must see that he missunterstood the question about the number.

But still, its up to you, to flash unknown stuff or not. I am sorry about your bricked phone, realy, but thats always possible when you flash things.

Sorry man.
[LeEco Le Pro3 Guides, News, & Discussion] Az Biker:
* * * REMINDER * * *

Every member is responsible for what they do with their device.

Unless there is malicious intent to damage member's devices, no rules are broken.

Please do all the research possible to make sure what you are flashing is for your device, if there is ANY question, DO NOT FLASH questionable mods to your device.

Again, every member is responsible for what they do with their device.
[LeEco Le Pro3 Guides, News, & Discussion] Az Biker:
Closed per OP request
[Amazfit] justwondering:
Great little smart watch , but I was hoping I could change the intensity and perhaps vibration pattern and length of vibration..

Are any of the above configurable ?
[Amazfit] Locksoft:
No.
[Amazfit] tgondar:
yes you can

yes you can:

- swipe down

- gear icon

- Common

- vibration
[Amazfit] lfom:
I know it works for Pace and Stratos, but the OP has a BIP... Does it work for BIP too? I don't think so...
[Samsung Galaxy S9  Questions & Answers] kkh786:
I had a black screen of death incident today on my S9.. a hard reboot fixed it (after a Google search).

Samsung users.. is this a major issue? Do I need to get a replacement? I'm near the end of my return period.

Never heard of this until today.. seen some websites down playing it..

Any advice?

Sent from my Galaxy S9 (SM-G960F)
[Samsung Galaxy S9  Questions & Answers] sirsomething:
Just wait and if keeps happening just go to the store. Of course it's not normal nor should it ever be xD

Sometimes **** just happens and everything stays normal
[Samsung Galaxy S9  Questions & Answers] kkh786:
Thanks.

That's my plan for now.. as I'm past the return period.. it may have been a one off.

On the plus side my Gear Sport is here! [emoji16]

Sent from my Galaxy S9 (SM-G960F)
[Samsung Galaxy S9  Questions & Answers] JS_racer:
How was the hard reboot performed? Just asking cause I don't know how. Thanks
[Samsung Galaxy S9  Questions & Answers] kkh786:
Hold down power and volume down buttons for about ten seconds.

Sent from my Galaxy S9 (SM-G960F)
[Upgrading, Modifying and Unlocking] fireburned:
Hi,

I try to cook a rom based on an official rom for Vox (HTC FRA 1.34).

I would understand all steps of cooking, i have already made this :

1 - Extract RUU_Vox_HTC_FRA_1.34.406.1_4.1.13.54_03.10.90_Ship.exe to RUU_signed.nbh (7-zip)

2 - Extract RUU_signed.nbh to IPL.nb/PrimarySpalsh.nb/Radio.nb/SPL.nb/Windows.nb (nbhtool.exe)

3 - Dump rom Windows.nb with prepare_imgfs.exe and viewimgfs.exe

4 - Move dump files in OEM/SYS folders with PKGTool

If i understood well, i must extract XIP from Windows.nb, before cook.

I have tried some soft like nbsplit/rommaster/buildxip, but i have errors, could someone help me for this step ?

Thanks.

And sorry for my poor english.
[Upgrading, Modifying and Unlocking] cruzzmz:
have u try msflshtool
[Upgrading, Modifying and Unlocking] fireburned:
Thanks for this idea.

I test it, with this command :

msflshtool.exe Windows.nb -d

I obtain 3 files :

- Windows.nb.part0

- Windows.nb.part1

- Windows.nb.part2

Here is the part info :

***********************************************************
msflsh50dump v0.1 code by blueboy
***********************************************************
partinfo
part <0> offset <00000400> size <00217400>
part <1> offset <00217800> size <00333000>
part <2> offset <0054A800> size <03586800>
end

What is the newt step ?

Thanks you.
[Upgrading, Modifying and Unlocking] cruzzmz:
usually it is in part0 or part1 ... use xipport to see which have the boot.hv & boot.rgu ... u only need those files ... around 20-40Kb files

Then u can put it in ROM folder in ur Kitchen

:D
[Upgrading, Modifying and Unlocking] fireburned:
Thank you cruzzmz for your replies ;)

I used XIPort to extract Windows.nb.part0/Windows.nb.part1.

I obtain this :

Windows.nb.part0
OUT\
PARTHDR.txt
ROMHDR.txt
\FILES
boot.hv
boot.hv.imageinfo.txt
ceconfig.h
ceconfig.h.imageinfo.txt
default.hv
default.hv.imageinfo.txt
initobj.dat
initobj.dat.imageinfo.txt
user.hv
user.hv.imageinfo.txt
\MODULES
busenum.dll
cecompr.dll
ceddk.dll
cereg.dll
certmod.dll
coredll.dll
device.exe
devmgr.dll
diskcache.dll
encfilt.dll
fatfsd.dll
fatutil.dll
filesys.exe
fsdmgr.dll
imgfs.dll
mmtimer.dll
mspart.dll
nk.exe
OMAP850_SDHC.dll
ONDisk.dll
packageinfoapi.dll
pm.dll
ramdisk.dll
rawfs.dll
regenum.dll
romfilter.dll
sdbus.dll
sdmemory.dll
serial.dll
uldrui.dll
updateapp.exe
busenum.dll.txt
cecompr.dll.txt
ceddk.dll.txt
cereg.dll.txt
certmod.dll.txt
coredll.dll.txt
device.exe.txt
devmgr.dll.txt
diskcache.dll.txt
encfilt.dll.txt
fatfsd.dll.txt
fatutil.dll.txt
filesys.exe.txt
fsdmgr.dll.txt
imgfs.dll.txt
mmtimer.dll.txt
mspart.dll.txt
nk.exe.txt
OMAP850_SDHC.dll.txt
ONDisk.dll.txt
packageinfoapi.dll.txt
pm.dll.txt
ramdisk.dll.txt
rawfs.dll.txt
regenum.dll.txt
romfilter.dll.txt
sdbus.dll.txt
sdmemory.dll.txt
serial.dll.txt
uldrui.dll.txt
updateapp.exe.txt

Windows.nb.part1
OUT\
PARTHDR.txt
ROMHDR.txt
\FILES
42d1aab7-6dfa-4c03-9797-d66f7620883d.dsm
42d1aab7-6dfa-4c03-9797-d66f7620883d.dsm.imageinfo.txt
7da1c1a8-1fd2-4a18-a081-84e4825266b1.dsm
7da1c1a8-1fd2-4a18-a081-84e4825266b1.dsm.imageinfo.txt
966f2a5f-b510-8a60-28bc-6c06a3376c66.dsm
966f2a5f-b510-8a60-28bc-6c06a3376c66.dsm.imageinfo.txt
b5332311-48f1-4b76-ad70-8efa5db8fa3a.dsm
b5332311-48f1-4b76-ad70-8efa5db8fa3a.dsm.imageinfo.txt
b5332311-48f1-4b76-ad70-8efa5db8fa3a.rgu
b5332311-48f1-4b76-ad70-8efa5db8fa3a.rgu.imageinfo.txt
boot.hv
boot.hv.imageinfo.txt
boot.rgu
boot.rgu.imageinfo.txt
e7cdacc2-b776-1926-fd10-4b8c9b712e9b.dsm
e7cdacc2-b776-1926-fd10-4b8c9b712e9b.dsm.imageinfo.txt
initflashfiles.dat
initflashfiles.dat.imageinfo.txt
mxip_initdb.vol
mxip_initdb.vol.imageinfo.txt
mxip_lang.vol
mxip_lang.vol.imageinfo.txt
wince.nls
wince.nls.imageinfo.txt
\MODULES
busenum.dll
cachefilt.dll
cecompr.dll
ceddk.dll
certmod.dll
coredll.dll
device.exe
devmgr.dll
diskcache.dll
encfilt.dll
fatfsd.dll
fatutil.dll
filesys.exe
fsdmgr.dll
fsreplxfilt.dll
hd.dll
HtcFsdspy.dll
imgfs.dll
mspart.dll
nk.exe
ONDisk.dll
osaxst0.dll
pm.dll
ps2fatutil.dll
regenum.dll
busenum.dll.txt
cachefilt.dll.txt
cecompr.dll.txt
ceddk.dll.txt
certmod.dll.txt
coredll.dll.txt
device.exe.txt
devmgr.dll.txt
diskcache.dll.txt
encfilt.dll.txt
fatfsd.dll.txt
fatutil.dll.txt
filesys.exe.txt
fsdmgr.dll.txt
fsreplxfilt.dll.txt
hd.dll.txt
HtcFsdspy.dll.txt
imgfs.dll.txt
mspart.dll.txt
nk.exe.txt
ONDisk.dll.txt
osaxst0.dll.txt
pm.dll.txt
ps2fatutil.dll.txt
regenum.dll.txt

The good files are in Windows.nb.part1 ?

Next step : copy boot.hv/boot.rgu in ROM/XIP folder ?

Thank you very much ! :)
[Upgrading, Modifying and Unlocking] fireburned:
And another question, i have "missing files" when i use PKGTool :

[Missing Manifests]
(Maybe):\ROM\XIP\b5332311-48f1-4b76-ad70-8efa5db8fa3a.dsm
(Maybe):\ROM\XIP\7da1c1a8-1fd2-4a18-a081-84e4825266b1.dsm
(Maybe):\ROM\XIP\42d1aab7-6dfa-4c03-9797-d66f7620883d.dsm
(Maybe):\ROM\XIP\e7cdacc2-b776-1926-fd10-4b8c9b712e9b.dsm
(Maybe):\ROM\XIP\966f2a5f-b510-8a60-28bc-6c06a3376c66.dsm

It's a problem ?
[Upgrading, Modifying and Unlocking] cruzzmz:
dont think it is a problem as long as when u do buildOS u dont get any error (hint: if there is error check the temp folder open log.txt)
[Upgrading, Modifying and Unlocking] fireburned:
I created a *.bat file wich does this :

1- nbhextract "RUU_Signed.nbh" to "00_IPL.nb 01_SPL.nb 02_MainSplash.bmp 02_MainSplash.nb 03_GSM.nb 04_OS.nb"

2- dumprom.exe 04_OS.nb wich extract files in "Temp" folder :

boot.bin
msflsh.bin
romhdr.bin
\Imgfs (1599 objects)
\XIP (37 objects)

3- pkgtool.exe : Temp\Imgfs => Temp\Imgfs\OEM and SYS

4- move Temp\Imgfs\OEM and SYS in root kitchen directory

My problem :

* When i try to re-"BuildOS" (to test if my dump works), i have an error : Error, last status: "Creating initflashfiles.dat..."

I have found a file "initflashfiles.dat" in my ROM\XIP foler. What is the problem ?

Thanks you.
[Upgrading, Modifying and Unlocking] fireburned:
Help me please... I tried... But i'm blocked... :(
[Upgrading, Modifying and Unlocking] cruzzmz:
I dont seem to hv that file on my ROM\XIP folder, maybe u can try deleting all files inside XIP except for boot.hv & boot.rgu

then try buildOS again

BTW what is the size of both files?
[Upgrading, Modifying and Unlocking] fireburned:
I deleted all files in XIP folder, except boot.hv/boot.rgu

boot.hv = 40 Ko

boot.rgu = 27 Ko

Again, BuildOS fails : Error, last status: "Creating initflashfiles.dat..."

When i search in OEM and SYS folders, i don't have a "initflashfiles.dat" file.

An idea ?
[Upgrading, Modifying and Unlocking] cruzzmz:
dunno if this can help

seems like the initflashfiles.dat is in the dump folder after u do a viewimgfs
[Upgrading, Modifying and Unlocking] cicciocant:
You can put initflashfile.dat inside imgfs (for example OEM/OEM_LANG_XXX) and delete it from XIP.

Buildos.exe from Bepe search initflashfiles.dat insiede IMGFS: