Database Users

wm2005 missing RAM theory

Hi all,
today in the morning, in my usually empty head, suddenly appeared this theory:
There is still one thing on my mind, probably i cannot just "eat the leek" that Micro$oft requested to delete translation of THIS page from THIS THREAD.
What could be so interesting about StrataFMD's registry settings, that they don't want us to know???
They are:
Code:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\StrataFMD]
"Key"="Drivers\\BuiltIn\\StrataFMD"
"Flags"=dword:00000004
"CompactionCritPrio256"=dword:ffffffff
"CompactionPrio256"=dword:000000ff
"ReservedBlocks"=dword:00000004
"IsPairedFlash"=dword:00000001
"WriteBufferSize"=dword:00000040
"SectorSize"=dword:00001000
"BlockSize"=dword:00040000
"MemLen"=dword:01f00000
"MemBase"=dword:a0080000
"Dll"="msflash.dll"
"IClass"="{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"
"Profile"="MSFlash"
"Ioctl"=dword:00000004
"Prefix"="DSK"
"Order"=dword:00000002
So the most interesting for me is this:
Code:
"MemLen"=dword:01f00000 <--- 31MB
"MemBase"=dword:a0080000 <--- !!!
The size looks OK to me, because that's the size of flash chip, but how about its location (a0080000)?
According to our Himalaya Memory layout WIKI PAGE StrataFMD is using base address, which is in RAM.
Somewhere in the msdn i've red, that by default OS assigns first contiguous block of RAM as free memory. If your RAM is not contiguous, you have to specify it in config.bib (Platform Builder) to be recognised as RAM.
So if the StrataFMD is assigned base address which is overlapping RAM address region it makes our RAM non contiguous...
Example:
Code:
|<-----------------------128 MB RAM----------------------->|
|<---RAM start--->|<----Strata----->|<----Rest of RAM----->|
That would mean, we can use the first chunk of RAM.
That makes me believe, it is the reason why we cannot use the whole RAM as in wm2003. If we could somehow shift the base address of Strata chip maybe we will get the whole RAM back to OS.
But this all is just my theory and it is probably not true...
I'd like to ask you guys and girl (at least the one i know, that it's here.. ) ) to post comments to this theory and to say what you think about it.
THANX
buzz

why don't you pm 'the one you know' buzz?

deleted
hehehe...maybe you got it BUZZ!

Re: deleted
xda2jojo said:
hehehe...you got it BUZZ!
Click to expand...
Click to collapse
i'm not quite sure... mamaich just said, that it is not right... hmm...
buzz

buzz_lightyear said:
The size looks OK to me, because that's the size of flash chip, but how about its location (a0080000)?
Click to expand...
Click to collapse
What is wrong with this address ? mickey$oft wince always maps the ROM
at the bottom.

Hi there,
I'm totally n00b here so pls consider this
Just ideas...
Let's offset the Strata by changing MemLen to allocate more RAM or by changing MemBase to 0 to position our Strata at the beginning?
and one more, what if we play with LoadFlags of StorageManager\AutoLoad\MSFlash so we can find maybe "load as RAM" not as disk flag?
And what if we disable MSFlash and will use our RAMDisk instead? So, the Image Updater will copy the OS image to our RAMDisk instead of Flash?

IMate->WM2k5 said:
Hi there,
I'm totally n00b here so pls consider this
Just ideas...
Let's offset the Strata by changing MemLen to allocate more RAM or by changing MemBase to 0 to position our Strata at the beginning?
and one more, what if we play with LoadFlags of StorageManager\AutoLoad\MSFlash so we can find maybe "load as RAM" not as disk flag?
And what if we disable MSFlash and will use our RAMDisk instead? So, the Image Updater will copy the OS image to our RAMDisk instead of Flash?
Click to expand...
Click to collapse
try it, but that doesn't really work...
buzz

Guys i'm a new memeber so i hope i will use the right terms :
this post is intended to let u know what is happening in my device so that we can undestand more about how this OS works( windows mobile 2005)
I installed Magneto dowloaded from this site's ftp
i expected to have no ram
but insted when i check the memory settings i have 62 MB storage and 56Mb for programs
even though i installed ramdrive which gives me 96 Mb of ramdrive space
i'm trying to understand ram and rom distribution and usage in the device
cause even if i coldboot i don't lose any data or any setting (except time the clock resets)
now i know that what i said does not make sense:
96 +62 +56 > 16mb (Extedend rom capacity )+ 128 Mb ram
i fist thought that this was a miscalculation (bug or so)
then i started to copy data (mp3s) into my root directory i was able to copy 60.84 Mb into the an mp3 directory in the root (not storage , ramdrive or storage card )
i tried to reset , hard reset (power + reset) , go to bootloader mode the hard reset and even the 2005 hardreset (power+CAMERA+NOTES+reset)
they are still there also contacts and all other databases
only time resets
to 1 september 2003
when i tried to copy 80 mb of data (mp3s) to ramdrive
the device froze and a simple reset was the solution but all data copied was erased .
i found out later that any reset does erase the ramdrive (ramdisk)
so it is eather a bug in the ramdrive driver/software or that the physical memory (ram) was actually full : the device froze at almost 16 mb copied
then i tried to delete the data from the root
my memory was free again only 4 mb used out of 62
i tried to copy to ramdrive and the device froze at almost 16 mb too
so i think it is a problem with the ramdrive driver ( is it ?? please reply if same problem occured )
i took some snap shots to prove what i said
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
other wise the os is wonderful
i just can't change the splash image
Hope that i can be of any help cause i always rely on yours so thank you

amalkaedbey said:
Guys i'm a new memeber so i hope i will use the right terms :
this post is intended to let u know what is happening in my device so that we can undestand more about how this OS works( windows mobile 2005)
I installed Magneto dowloaded from this site's ftp
i expected to have no ram
but insted when i check the memory settings i have 62 MB storage and 56Mb for programs
even though i installed ramdrive which gives me 96 Mb of ramdrive space
i'm trying to understand ram and rom distribution and usage in the device
cause even if i coldboot i don't lose any data or any setting (except time the clock resets)
now i know that what i said does not make sense:
96 +62 +56 > 16mb (Extedend rom capacity )+ 128 Mb ram
i fist thought that this was a miscalculation (bug or so)
then i started to copy data (mp3s) into my root directory i was able to copy 60.84 Mb into the an mp3 directory in the root (not storage , ramdrive or storage card )
i tried to reset , hard reset (power + reset) , go to bootloader mode the hard reset and even the 2005 hardreset (power+CAMERA+NOTES+reset)
they are still there also contacts and all other databases
only time resets
to 1 september 2003
when i tried to copy 80 mb of data (mp3s) to ramdrive
the device froze and a simple reset was the solution but all data copied was erased .
i found out later that any reset does erase the ramdrive (ramdisk)
so it is eather a bug in the ramdrive driver/software or that the physical memory (ram) was actually full : the device froze at almost 16 mb copied
then i tried to delete the data from the root
my memory was free again only 4 mb used out of 62
i tried to copy to ramdrive and the device froze at almost 16 mb too
so i think it is a problem with the ramdrive driver ( is it ?? please reply if same problem occured )
i took some snap shots to prove what i said
other wise the os is wonderful
i just can't change the splash image
Hope that i can be of any help cause i always rely on yours so thank you
Click to expand...
Click to collapse
Ram Drive cab file was created in aim of the bug, lack of ram, storage and it was meant to be used as a Storage. You flashed your device with the right rom so don't use the RamDrive! What's really missing is about 10 megs from the RAM Chip.
We're expecting a new modified rom soon from Buzz that combines the Extended ROM and Storage which they are 1 chip partitioned.
Buzz we're still waiting 8)
Thank you.
Ram!

You are Right Ramram
Many things lead to my confusion
first i didn't know how to hardreset the device
and maybe i read somewhere (in this forum i guess) a theory that said that WM5.0 is not using ram for storage (using some kind of Rom )... bla bla
to cut a story short
i found the extended rom unlocker
i was able to change my splash images
etc
there are few other problems i'm having with WM5.0:
Persave is not working (maybe because storage is now nand disk)
Activesync(in the device does not notice if the device is removed from cradle
thought i think they must be discussed in an other topic i'd like to know if these problems can be solved
thanks

[Gen8v2] Stock 2.4.81 rooted build for SDE enabled A70it2/A70B

Hi All,
Here is 2.4.81 firmware for SDE enabled devices.
I did two versions:
- squashfs, in this one, system is read-only, you can't add/remove stock apps and edit system files. Files are compressed so it takes less storage space than ext3, it should be also slower than ext3.
- ext3, system is read/write and should be quicker. Be careful if you modify system files though. No ext4 for the moment as source code for the kernel is not available and ext4 is not enabled in stock kernel.
To install it:
(Pictures are from G9 A101 but menus are similar)
0) You must have SDE installed. If you didn't do it already, check there instructions on how to do it.
1) Extract zip file content
2) Copy android_2.4.81.squashfs (or android_2.4.81.ext3) to internal storage root.
3) Reboot
4) On boot menu, select "Recovery system"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5) Select "developer edition menu"
6) Select "flash kernel and initramfs"
6) A drive should appear on your PC, copy zImage and initramfs.cpio.gz to it.
7) Select OK, the kernel should flash.
8) Select OK to reboot and maintain vol+ pressed. Boot menu should appear after reboot.
9) Select SDE in boot menu, you should be rooted and SuperUser functional.
Download rooted 2.4.81 on squashfs here.
Download rooted 2.4.81 on ext3 here.
Cheers,
LeTama

*reserved*

Hey letama,
it seems you're cracking everything you got at hand
So how about the OS on this devices... is it still Froyo?
Extracting and grepping the included kernel gives:
Code:
Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.1 (GCC) ) #1 PREEMPT Mon Dec 5 13:58:23 CET 2011
EDIT:
Not sure, seems to be recovery kernel
Waiting for letama's reply...
So what did they change here... better hardware specs of course.
So did they use 512MB RAM?
Screen resolution also increased, right?
What's the actual kernel version?
Congratulations for your new toy!!
Cheers,
scholbert

scholbert said:
it seems you're cracking everything you got at hand
So how about the OS on this devices... is it still Froyo?
Click to expand...
Click to collapse
Well, now it's easy as I know where to look and wrote my tools.
So what did they change here... better hardware specs of course.
So did they use 512MB RAM?
Screen resolution also increased, right?
What's the actual kernel version?
Click to expand...
Click to collapse
512 MB of ram yes, a quite nice 1024x600 screen, and charging through usb which was one of my main grip with ram.
And yes, it's a 2.6.29 as expected to match froyo. Unfortunately no kernel source and too lazy to backport panel and touchscreen from .35 knowing that gingerbread should come soon.
Congratulations for your new toy!!
Click to expand...
Click to collapse
Thanks! Was lucky to get it at a low price, it's a nice upgrade that didn't cost too much. I really like 7", easier to work with it and laptop in the train, my main hack time . Next will be asus I presume if they arrive here, but until then...

Hi,
I have a A70b and i have the Developer menu active. However i put the rooted build (i have tried both) and did all the instructions...but well i try to boot into developer edition the devices stays freeze on "Archos" boot logo.
Any ideias on what could be the problem?
Thanks

scalaneo said:
Hi,
I have a A70b and i have the Developer menu active. However i put the rooted build (i have tried both) and did all the instructions...but well i try to boot into developer edition the devices stays freeze on "Archos" boot logo.
Any ideias on what could be the problem?
Click to expand...
Click to collapse
Hi scalaneo,
Kernel did get flashed properly ?
You're sure the ext4 or squashfs file is at root of internal storage ?
It's not hard drive model, right ?

Hi,
Yes it´s hard drive 250gb model. Developer Menu is ok and the i copied the file to root yes.

scalaneo said:
Hi,
Yes it´s hard drive 250gb model. Developer Menu is ok and the i copied the file to root yes.
Click to expand...
Click to collapse
Ok, that's why, I was not aware that HD model was out already when I did it, I mounts SD internal storage only. I'll take a look to see how I can detect HD and mount it.

Thanks Letama!

Can you try to flash this kernel and let me know ?
It should mount hd instead of sd.

Hi,
I have tested it and i get same result. :-(
It flashes kernel but then i get´s freeze at boot screen.

Grrr!
Ok, if you don't mind, could you try this one ? It should display two debug screens, could you show me the result (picture or write it here ?)

First Screen:
Product name is A70HDD (A70H2)
Second Screen:
Product name: [A70H2]
Thanks

scalaneo said:
First Screen:
Product name is A70HDD (A70H2)
Second Screen:
Product name: [A70H2]
Thanks
Click to expand...
Click to collapse
Ok, so detection is good.
On second screen, nothing is displayed under the "Product Name: [A70H2]" ?
If nothing is there, mount didn't work.
Can you try the one attached ? And if not better, give me the result of "adb shell mount" on regular boot?
Sorry for the trial and errors

Hi again,
Menu 1 and Menu 2 photos attached:
After i can boot into Developer mode. But i always get the hdd as "Damaged internal storage". Internal storage problem. Please reboot.
It seems that i cannot access the hard drive somehow. Could it be because the build was done to work on SD card and not the internal HDD?
Many thanks for your support on this mate.

scalaneo said:
Hi again,
Menu 1 and Menu 2 photos attached:
After i can boot into Developer mode. But i always get the hdd as "Damaged internal storage". Internal storage problem. Please reboot.
It seems that i cannot access the hard drive somehow. Could it be because the build was done to work on SD card and not the internal HDD?
Many thanks for your support on this mate.
Click to expand...
Click to collapse
Hum, ok.
So mount worked, Android starts and you get this message just after?
I have no idea why, build should be the same between SD and HD as far as I know. The only thing I do differently from stock is that I mount the internal storage at the beginning to be able to access the ext4 file, but I do it in a separate directory than normal mount location to avoid interaction.
I'll take a look if I can find something.

Hi,
Thanks again for your help.
Well yes...this happens after the boot. Everything works fine but i cannot access the files or anything in HDD.
Also...everytime i try to access aplications that were installed in HHD it gives me an error saying that cannot find sd/.
I think that it assumes sd as default and not hdd. Also this is ext3 and not ext4, but i don´t think it will affect here.
Thanks again for the help.

scalaneo said:
Hi,
Thanks again for your help.
Well yes...this happens after the boot. Everything works fine but i cannot access the files or anything in HDD.
Also...everytime i try to access aplications that were installed in HHD it gives me an error saying that cannot find sd/.
I think that it assumes sd as default and not hdd. Also this is ext3 and not ext4, but i don´t think it will affect here.
Thanks again for the help.
Click to expand...
Click to collapse
Oh, ok so it boots fine but only hd is not accessible.
Could you give me the result of "adb shell mount" on both working stock and not working rooted build ?

letama said:
Could you give me the result of "adb shell mount" on both working stock and not working rooted build ?
Click to expand...
Click to collapse
And I was thinking... Could you also do "adb pull /mnt/system/androidmerged.squashfs.secure" and "adb pull /mnt/rawfs/init" (while rooted),and upload files somewhere (multiupload.com or something else) ? Maybe I could pinpoint differences.
Thanks,
LeTama

Hi,
Sorry for the delay. I have been really busy does days.
I have attached the adb shell mount.
About the other ones that you wanted me to try it says for both that "does not exist".
Thanks again

Lumia 1520 Starting work on custom ROM !

Hi Everyone !!
Work on the first custom rom WP8 for Huawei w1 been completed successfully .
Time for something new !
I would like to announce that I start work on Custom ROM for nokia lumia 1520. First attempt at flashing the modified file ffu done successfully .
Unfortunately, in another attempt something went wrong. I switched the phone in Download mode, QPST can repair the phone but I dont have appropriate files (currently). I have Riff Box JTAG but this programator does not support L1520 and i need ATF jtag.
I'll keep you informed about the progress !! :fingers-crossed:
I collect money for the ATF and the new phone, otherwise I can't continue to work. In the future, project will be developed for many other devices with WP8.

Interesting. First of all: Congrats on the succesfull flash,
second of all: I hope you can resurrect your Lumia 1520 how did you get the 1520 to accept the modified rom though? Though Lumias check the signature after the flashing process has completed?

Thanks for congrats
I can ressurect my lumia in 2 ways:
1. I need have repair boot files for QPST
2. I need AFT JTAG
I have methods to cheat the verification process. In the same way I did in Huawei W1. :victory:
These are my priorities:
1. Development and refinement the ability to flash the modified FFU file.
2. Ability to run the phone in mass storage mode
3. Modification software
4. Adapting WP8CRUU for Luma 1520

WojtasXda said:
Thanks for congrats
I can ressurect my lumia in 2 ways:
1. I need have repair boot files for QPST
2. I need AFT JTAG
I have methods to cheat the verification process. In the same way I did in Huawei W1. :victory:
These are my priorities:
1. Development and refinement the ability to flash the modified FFU file.
2. Ability to run the phone in mass storage mode
3. Modification software
4. Adapting WP8CRUU for Luma 1520
Click to expand...
Click to collapse
Getting the boot files might be the trickier method, but you could try what I described in your other post. I guess the ATF Box is your best chance. I'll look through the 1520 update cabs maybe theres something in there that'll help you build the mbn boot image, like on htcs. (which are, for the 8s encrypted, for the 8x not, as far as I know.) If you feel okay with it you can shoot me a message with tips on how you managed to do that, if not, that's not a problem

WojtasXda said:
Thanks for congrats
I can ressurect my lumia in 2 ways:
1. I need have repair boot files for QPST
2. I need AFT JTAG
I have methods to cheat the verification process. In the same way I did in Huawei W1. :victory:
These are my priorities:
1. Development and refinement the ability to flash the modified FFU file.
2. Ability to run the phone in mass storage mode
3. Modification software
4. Adapting WP8CRUU for Luma 1520
Click to expand...
Click to collapse
Are you reading this thread: http://www.coolxap.com/forum-199-1.html ?
I received a lot of information about huawei w1 on this site. When read about it in December 2013.

Actually if the verification bypass works (which, knowing MS's tight security on Nokias, I highly doubt), it just needs to be released as a method, and after that, anyone can make their own custom ROM.
I'd definitely make some changes to the system (clear out some default apps, add some of my own, change the accent colours, allow interop and other caps to any apps, increase custom app limit), but that would break the built-in system updater. So beware modders, DO NOT use official updates when on modded firmware!

WojtasXda said:
Hi Everyone !!
Work on the first custom rom WP8 for Huawei w1 been completed successfully .
Time for something new !
I would like to announce that I start work on Custom ROM for nokia lumia 1520. First attempt at flashing the modified file ffu done successfully .
Unfortunately, in another attempt something went wrong. I switched the phone in Download mode, QPST can repair the phone but I dont have appropriate files (currently). I have Riff Box JTAG but this programator does not support L1520 and i need ATF jtag.
I'll keep you informed about the progress !! :fingers-crossed:
Click to expand...
Click to collapse
Hi,
I have an ATF Box (lordmaxey & me interop unlocked our Lumias with it, do you remember me ) and would like to help you. Feel free to PM me
Another question, did you just modify the .ffu file via Hex Editor? I've tried it myself a long time ago, but it didn't work and I had to repair it with my ATF. Is there a bug in newer Nokia FFU files?
myst02

feherneoh said:
Flashing the custom ROM is not hard, so I would give it a try
Just be sure you don't touch boot partitions, so you will be able to boot into flashmode
On L520, I could simply flash ANY ffu using CareSuite, so flashing works, just need idea, what to change in ROM
Click to expand...
Click to collapse
How are you able to bypass signature checking though? Funny how on Lumias you can apparently edit the MainOS Partition but cannot touch the Boot ones, and on HTC it's exactly the reverse.

Guys ... the only barrier that separates us from the Custom ROM are 2 files that i need to create and adapt to the device. I mean MPRG8974.mbn ((hex) and msimage8974.mbn . Anyone who has knowledge on this topic, please help !!
This is my other topic about mprg/misimage
http://forum.xda-developers.com/hardware-hacking/hardware/qpst-help-create-mprg-msimage-mbn-t2949492
Here is a lot of information about QPST
http://forum.xda-developers.com/showthread.php?t=2136738
how to build mprg and msimage [/url]
http://blog.csdn.net/ziyouwa/article/details/16331545

feherneoh said:
Start phone recovery process in CareSuite, select official firmware, press start
When it asks you, to connect the phone, just replace the ffu file with the modified one
Boot partition should not be touched, as the SoC checks its signature, and your phone will be stuck in quallcomm's DLMODE
Click to expand...
Click to collapse
how to modify FFU ? have you any tool for it ?
I know we can Convert it using ImgMounnt but how to reconvert it to ffu ?

feherneoh said:
Start phone recovery process in CareSuite, select official firmware, press start
When it asks you, to connect the phone, just replace the ffu file with the modified one
Boot partition should not be touched, as the SoC checks its signature, and your phone will be stuck in quallcomm's DLMODE
Click to expand...
Click to collapse
Okay, good, Are you sure that your phone will not reject the file when it encounters an error?
How do you think why was invented HSPL ?
For Huawei just enough to crack the flash tool in PC to be able to upload an unsigned app / ffu file. Phone does not validate the data but Huawei is different story. While working on the Custom ROM I used QPST with MPRG ,MSIMAGE, xml's and other files. JTAG also be useful. Without QPST not have been possible creating Custom ROM for Huawei.
Therefore necessary there is start working on the most needed things.
ngame said:
how to modify FFU ? have you any tool for it ?
I know we can Convert it using ImgMounnt but how to reconvert it to ffu ?
Click to expand...
Click to collapse
Do you think it is that simple? If yes, where are the custom roms? Where these modified files? Of course there are tools to build files ffu, signing and opening them, but they are not available for "ordinary" people.
Well ... I go learn and explore the dark side of QPST
Regards

WojtasXda said:
Okay, good, Are you sure that your phone will not reject the file when it encounters an error?
How do you think why was invented HSPL ?
For Huawei just enough to crack the flash tool in PC to be able to upload an unsigned app / ffu file. Phone does not validate the data but Huawei is different story. While working on the Custom ROM I used QPST with MPRG ,MSIMAGE, xml's and other files. JTAG also be useful. Without QPST not have been possible creating Custom ROM for Huawei.
Therefore necessary there is start working on the most needed things.
Do you think it is that simple? If yes, where are the custom roms? Where these modified files? Of course there are tools to build files ffu, signing and opening them, but they are not available for "ordinary" people.
Well ... I go learn and explore the dark side of QPST
Regards
Click to expand...
Click to collapse
I know it's not easy and simple and I know there's at least one tool to create and edit ffu files and it's also not public but i thought he developed a FFU Editor app ! or he flashed Custom Rom many times !
and also I think you mean Phone Image Designer of Microsoft :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

feherneoh said:
I have used HxD hex editor to find the partition headers, then used OSFMount to mount them. You can either mount a part of the ffu, or copy the partition to a separate image
As far as I know (my bricked 520 proves it) SoC's built-in ROM checks the first partition's signature using the public key in Q-Fuse, so let's crack RSA and stuff like that. SPL/HSPL was used to load CE, NT on ARM uses UEFI
Click to expand...
Click to collapse
you bricked your phone when you try this way ?
If( YourAnswer == "Yes" )
{
MessageBox.Show("Surely This way can't be useful or it's not the complete way and we need to research more");
}
else
{
//More Details go here
}

feherneoh said:
This happened when I tried to modify first partition (shown in attachments in previous post)
I'm not sure, if I added that in this thread, too, but only try, if you have JTAG box, so you won't mess up everything
Click to expand...
Click to collapse
Unfortunately I have no JTAG box (riff , atf and etc.)
I will look for way you provide and check it .
I have to find someone with JTAG in Mashad,Iran . Is there anyone ?

it is necessary to learn how to create MPRG / MSIMAGE and use QPST Then jtag will not be needed. These files are obtained by reading the data from the memory EMMC in this case VHD would be the best solution.

OK OK your way worked
I could create 3 Partitions from my L920 (RM-821) Rom .
I couldn't access MainOS partition in this ROM .
sounds good to find this working way but need to work on it hours and hours .

feherneoh said:
Once found something like MPRG in ffu
Open another SoC's MPRG, and look for the first 8 0r 16 bytes in ffu file
Click to expand...
Click to collapse
I do not know if this is true, but MPRGXXXX.bin or MPRG.hex (Intel hex) suitable for many devices. Msimage is built only for the appropriate device.
@WojtasXda : Are you using caresuite to flash the rom, or do you have another tool?
Click to expand...
Click to collapse
Yes i have own tools for example WP8RUU or WP8CRUU

Things that might be of interest to a custom ROM developer:
* I've just made big progress in figuring out how capabilities work on the phone. Setting them via custom ROM is definitely one of the easier ways it might be done, if you can create arbitrary registry keys and set arbitrary values in them.
* One particularly valuable thing you could add to a non-Samsung ROM is the RPC driver/service/whatever that lets Samsung's RCPComponent library work. I don't know how hard it would be to hack that in, though. The binaries and the registry keys for the service shouldn't be hard to obtain, but I don't know if there will be problems with signatures or anything. Still, if you can get it working, this would mean that Samsung homebrew, and everything we can do with it (such as write arbitrary places in the registry and move files around as SYSTEM) becomes available on the 1520.
Somewhat relatedly, I find myself in need of a new phone (I think my ATIV S may be unrecoverable, and it wasn't even due to a hack I was doing!) and this piques my interest in getting a 1520...

feherneoh said:
Also (just an idea) RT certificates could be added. Maybe some(!) RT apps could run on the phones
Click to expand...
Click to collapse
These apps work now on WP8.1
wp8.1 supports appx and appxbundle formats so we don't have problem with running them on phones .
If you mean running apps like Multimedia 8 on phone I think we will run into resolution problem .

Not going to happen. First of all, the ported desktop apps only work when signature enforcement is off ("jailbroken") even *on RT*; until/unless we get a signature bypass for WP8 that's a complete non-starter.
The other major problem is that all the base libraries for RT are different than for WP. This extends all the way down to the really core stuff like Kernel32.DLL; RT (like normal Windows) has one, but WP8 doesn't (the functions are split into kernelbase.dll and kernel32legacy.dll). Then there's all the code (like support for the normal desktop interface) that WP8 just flat out doesn't have.
I'm not saying it's impossible to get RT code running on WP8... but it's probably easier to port the entire RT OS to the phone (which is *not* easy, but is possible) than it is to get RT software running on WP8 OS.

Universal ReadBack Extractor for mtk feature watchphones

Update Mar-12/2016: as long as on the market appeared a long line of new types of mtk6260 mtk6261 mtk2502C mtk2502A (etc) watches equipped with strange new PCB or flash_ID parameters, the new release <Readback Extractor mtk 2.0> now has the capacity to identify, to read, check, rebuild firmware and collect and insert in the .cfg files the flash_ID's coded inside the ROM dump for almost all types of mtk watchphones or smartwatches based on RTOS Nucleus
NOTE: being tested already for mtk6260 mtk6261 mtk2502C and mtk2502A
In short - if you intend to install in your smartwatch new firmwares, mods etc, before to initiate any flashing with the Flash Tool app (pushing that goddamn < Download > button) think twice, 'bove all better DO a backup for the original firmware, why so? because it's containing all original drivers hence you'll be able to recover 100% your watch in case of bricking.
How to:
First you have need of a full dump of your ROM. Assuming that you already got a Flash Tool 5.15.16 and drivers, and you were at the point of flashing something (already chose the download agent and scatter file)
preparations:
a. Set options/backup and restore on no action
b. load the download agent (you find this file inside the flash tool folder)
c. load a scatter firmware - for initialization flash tool needs a scatter file (.cfg) - for dz09 you get this one - for any other than mtk6260A get here and get a firmware compatible with your PCB
d. in case you have W10 - go to the start menu and click on power and hold down the shift key while clicking on restart. A screen then comes up and you need to choose troubleshooting and then startup options. It will then reboot and give you a menu. press 7 which is ignore signed drivers and then when windows comes up, you will be able to install the drivers.
for instance let's say you have a DZ09 smartwatch:
1 - press < Readback > in upper menu and so < Add > in the middle menu
2 - click twice on the item appears in the main window, set name as ROM_DZ choose in browser the path and save
3 - set as Physical start address 0x00000000 and as Length 0x01000000 or 0x00800000 or 00400000 (try them in this order) then ok
4 - turn off the watch, press < Readback > in the middle menu wait 2 seconds and connect through USB your watch
5 - wait until the upload is complete (big green ring)
Now second stage:
1 - download the app I've built attached here (Readback Extractor mtk) and unzip it
2 - create a folder where you intend to keep in safe the original firmware and name it for instance DZ09-Orig
3 - do a copy of Readback Extractor mtk 2.0.exe and place it inside the DZ09-Orig folder then click twice on it
4 - press <Load Readback file> and browse after the ROM_DZ file created before with the Flash Tool then open
5 - Wait about a minute while the app will check bit by bit the integrity of your file
6 - If everything went ok and your file is healthy then app will show " health 100% " so you can proceed to the next step
7 - Press <Rebuild Firmware> and wait about one minute (it shows a progress counter)
8 - When appears the message " - ALL DONE!!!" close app and go back in the DZ09-Orig folder, now you'll find there a set of new files which are the original firmware kit ready to be flashed back in your phone anytime you want
9 - Enjoy flashing anything you like without any fear that something bad can happen
Some tricks for writing IMEI in your watch NVRAM:
you connect to usb your watch (turned on this time) and set the com port on the watch screen, go in device manager and check the port number your watch is connected, then you open Tera Term hyperterminal (google for this app), connect it as serial com on watch com port and then give the command:
AT + EGMR = 1, 7, " imei number "
if on screen appears OK then ready, you've changed your imei
AFTERWARDS READ ME story - Anywhere you search, there is no one to tell you explicitly how to extract from your mtk smartwatch the firmware kit
All says a halfmouth: Do a full < Readback > in Flash Tool, you'll do it being confident that from now on you say goodbye to any risk because you have A BACKUP hence you start flashing new firmwares. And the Big Brick is coming , you smile and get back to your < Readback > backup discovering that, sadly, you have a binary bulk at first sight good for nothing. It cannot be so useless, isn't it? after all it contains full dump of your ROM! I was in exactly the same situation, so 'cause I didn't find any answer I've started reverse engineering . . . and it worked, first I did it manually for guys being in the same situation, 've noticed that is a common issue so I had to choose how to help, simpler but dangerous (for you) way, to create a tutorial <how to> or the hard way (hard for me), to develop an app which will do all "cooking" automatically and I choose the second because in manually way there is a quite big "chance" to mess up with your primary bootloader which could get to a real tragedy - no modem - brickest brick you saw in your entire life
Readback extractor mtk 2.1 beta
Flash Tool and drivers

Lil to late for me XD.... *just ordered a new one btw*

franc33s said:
Lil to late for me XD.... *just ordered a new one btw*
Click to expand...
Click to collapse
Sorry man, couldn't earlier because I have mine either of two weeks or so. . . still a beginner
Look at the bright side, best lessons we learn from our own mistakes, best part is that if you buy the new one from the same seller, you'll have the firmware hence two working watches!

Are there apps in the works to change watch faces without flashing?

kyitech said:
Are there apps in the works to change watch faces without flashing?
Click to expand...
Click to collapse
Unfortunately, yet, there is no way to get in contact with the watch else than through proprietary mediatek drivers so that the only ways to communicate for now are Flash Tool app and bluetooth modem proprietary commands (the most important of them being secret as well)
To do such a reverse engineering is way way way over my pay grade
Still I'm working for an app which could replace any media in the watch (backgrounds, icons) but through flashing method of course

Thanks for the info...I just think this watch have great potential

Golem_ said:
Unfortunately, yet, there is no way to get in contact with the watch else than through proprietary mediatek drivers so that the only ways to communicate for now are Flash Tool app and bluetooth modem proprietary commands (the most important of them being secret as well)
To do such a reverse engineering is way way way over my pay grade
Still I'm working for an app which could replace any media in the watch (backgrounds, icons) but through flashing method of course
Click to expand...
Click to collapse
Sorry for not knowing, but what about bluetooth app transfer in the Google play store. How can they be used on dz09-?

kyitech said:
Sorry for not knowing, but what about bluetooth app transfer in the Google play store. How can they be used on dz09-?
Click to expand...
Click to collapse
. . . bluetooth modem AT commands, just I told this before, generally speaking, in this way all bluetooth app are working, in our case they are proprietary and most of them SECRET. For more information please check this link, it is an older tutorial posted by me on that site

franc33s said:
Lil to late for me XD.... *just ordered a new one btw*
Click to expand...
Click to collapse
I'm almost sure you found these before me, still, here link you have more than 10 versions of dz09 firmwares (others than we checked before)
It looks like they made a firmware for each phone ) very prolific guys when about dz09
Hope this time you catch the right one!

Golem_ said:
I'm almost sure you found these before me, still, here link you have more than 10 versions of dz09 firmwares (others than we checked before)
It looks like they made a firmware for each phone ) very prolific guys when about dz09
Hope this time you catch the right one!
Click to expand...
Click to collapse
yup already did try them all, they boot fine, just no luck getting the Padgene (padgeME) one yet (so my touchscreen driver would work), the guy is still uploading more firmwares tough *fingers crossed*

Golem_ is a hero!
Thanks for all the time you spend with the gt08

flashtool
Hy ,
I am trying to search for the wright flashtool to make my backup.
And where can i find a tutorial?
I have a gv08s.
Wich drivers do i need, and wich version of flashtool?
Thanks in advance

xeph20 said:
Golem_ is a hero!
Thanks for all the time you spend with the gt08
Click to expand...
Click to collapse
thank you for kind words!

Golem_ said:
thank you for kind words!
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

carlospaco said:
Hy ,
I am trying to search for the wright flashtool to make my backup.
And where can i find a tutorial?
I have a gv08s.
Wich drivers do i need, and wich version of flashtool?
Thanks in advance
Click to expand...
Click to collapse
here link you find a good tutorial but instead <download> you have to use <readback>

Golem_ said:
here link you find a good tutorial but instead <download> you have to use <readback>
Click to expand...
Click to collapse
Yes , i have done everything like its said, for couple off days, but i keep getting this error always.
lashtool error: S_BROM_DOWNLOAD_EPP_FAIL (2036)
[EPP] FlashTool environment preparation failed
It May be caused from DRAM initialization failed
Pleace check the EMI information of the MAUI load is correct and fit the target.
Hope that someone can help me with this, i am desperated.
Thanks

carlospaco said:
Yes , i have done everything like its said, for couple off days, but i keep getting this error always.
lashtool error: S_BROM_DOWNLOAD_EPP_FAIL (2036)
[EPP] FlashTool environment preparation failed
It May be caused from DRAM initialization failed
Pleace check the EMI information of the MAUI load is correct and fit the target.
Hope that someone can help me with this, i am desperated.
Thanks
Click to expand...
Click to collapse
give me in PM a skype ID

Golem_ said:
give me in PM a skype ID
Click to expand...
Click to collapse
Oh, i am sorry, but i don't have a skype id.

carlospaco said:
Oh, i am sorry, but i don't have a skype id.
Click to expand...
Click to collapse
Alternatives for live screen sharing like, for instance TeamViewer?

Golem_ said:
Alternatives for live screen sharing like, for instance TeamViewer?
Click to expand...
Click to collapse
i have send you id teamviewer

[HOW-TO]Android 8.1 for Z00VD/ZC500TG

Hello people of XDA,
as I promised here, here's a tutorial for getting Android Oreo 8.1 up and running to your device.
NOTE: I DID NOT MAKE THIS TUTORIAL! This is a translated guide from 4PDA by nik-kst. I've also rehosted some of the files on Google Drive so you won't have to register on 4PDA(hopefully).
Code:
[B]Your warranty is now void. [/B]
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.
Now that the disclaimer is dealt with, let's get on with this tutorial shall we?
First things first, we need to grab a bunch of things:
SP Flash Tool;
MediaTek VCOM Drivers;
The Stock Kernel(it will make sense to you soon!);
Scatter file for repartitioning, drop it inside the stock kernel folder(credit to fca.sjc);
ADB and Fastboot of your choice;
New recovery;
Oreo's Backup, drop it inside a MicroSD card or drop it once you have re-partitioned the device successfully;
Once you have everything setup and extracted, you're ready to go!
First, we gotta go ahead and install VCOM drivers - we won't be able to do anything to our phone without them.
If you're running Windows 8/10, make sure to disable Driver Signature Verification.
Go to Device Manager, click Action at the top and click Add legacy hardware. A new wizard window will appear.
Choose Install the hardware that I manually select from a list(Advanced);
In the next window, choose Show all devices and click Next, then click Have disk...
Then you will be prompted to direct to the driver install info, so click Browse...
Now go to the folder of drivers and select the Setup Information file that's fitting for your computer, x86 for 32-bit and x64 for 64-bit.
You should now find 5 new devices in the list, add them one by one by repeating steps 2 to 6 until you have all of them installed.
Windows might complain about unsigned drivers, just allow their installation and proceed.
If your ports list looks similar to the picture below, then you're set for the next step!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Next, we'll want to back up the NVRAM partition, because AFAIK, it keeps important unique data about your device such as WiFi, IMEI etc. data.
Note: You may want to take out your MicroSD card and SIM cards prior to this just in case. Also, might be the possible fix if readback for NVRAM fails(needs confirmation).
First, open up Flashtool.exe as admin and go to Readback tab;
Click on Add, a new item in the list will appear. You want to double-click on it, so that a Save File window would appear.
Save that file anywhere you want, name it whatever you like, for convenience I've named mine ROM_NVRAM.
Now, you'll want to find the address in the memory for NVRAM partition. To do this, open up the stock firmware(credit to fca.sjc) scatter file in a text editor(like Notepad++), and find line partition_name: nvram
In that paragraph, find two values: linear_start_addr and partition_size they should be 0x380000 and 0x500000 respectively.
Punch in those values into the Readback block start address window, so it should look something like this:
Now, click Read Back, it should gray out along with Add and Remove.
Now, turn off your device, pull out the battery for about 30 seconds, reinsert it and DO NOT TURN IT ON YET! With the Volume Down "-" button pressed, plug in your device into the USB port.
The NVRAM partition should've been read and you'll get a giant green tick sign when it's done.
Now that that's done, we can start repartitioning our device.
Make sure your SP FlashTool is running as admin, otherwise restart it as admin.
Open up the Download tab and in the line Scatter-loading File click Choose and navigate to the 8.1 scatter file, it should be named MT6580_Android_scatter_8.1.txt.
From the dropdown list, select Format All + Download.
Again, take out the battery for 30 seconds and put it back in WITHOUT turning it back on.
Now click Download, and with the Volume down "-" button held down, plug the device into your PC. There should be a bunch of colored progress bars at the bottom of the window.
Once it's done, you should get the giant tick pop-up, after which you can disconnect the device, and start it normally.
NOTE: it takes a while for the first launch, so give it some time!
Once it starts up into the first launch wizard, we can now restore the NVRAM.
In order to activate the memory writing function of SP FlashTool, re-start it with admin and press Ctrl + Alt + V, the window header should have (Advanced mode) now.
From the Window drop-down, select Write Memory, it should redirect you to a new tab named accordingly.
In the File Path field, browse to the ROM_NVRAM backup that you made earlier.
In the Begin Address (HEX) field, copy the linear_start_addr value off the scatter file.
The region should be left at EMMC_USER.
Now, click the Write memory button, turn off the device, re-insert the battery just like before, and connect the device with the Volume Down "-" button pressed.
It should begin the writing of the NVRAM and once it's done a giant tick pop-up will appear.
Now after that is done, boot into the OS, check that everything works, including IMEI and WiFi.
Also, during the setup wizard or later in the settings setup a screen lock with a pattern or a PIN or a password(credit to fca.sjc), because the partitions may remain encrypted and show 0mb(needs confirmation)
Now you'll want to unlock the bootloader and flash the TWRP recovery.
Now this is a standard recovery flash, but for a quick summary:
Enable Developer options;
Enable OEM unlocking;
Reboot into bootloader mode(I like to use ADB for adb reboot-bootloader);
Make sure your device is detected via fastboot devices, if not, google some drivers for ADB;
Unlock the bootloader via fastboot oem unlock, and press the Volume up button to confirm the bootloader unlocking.
Now, reboot the phone, it will take a while to reboot, DO NOT PANIC AND WAIT.
Now that we have bootloader unlocked, we can flash the TWRP:
Go into bootloader mode;
Confirm you are being detected again by fastboot devices;
Flash the recovery with fastboot flash recovery [twrp recovery name].img;
now, WITHOUT booting into system we boot into recovery and confirm it works.
Now that you've done all this, you propably want to run Oreo now, eh? Well, here's what we do now:
Note: make sure you have the Oreo's backup zip extracted at it's own folder inside your MicroSD card or inside the phone's internal storage by now(thanks @ZappaDong for letting me know)
From recovery, select Wipe > Advanced Wipe and select system and vendor, and wipe them. Logs may complain about not seeing vendor, ignore that message.
Then, we restore everything from the Oreo backup;
Finally, do a factory reset(aka wipe Data, Dalvik and cache);
And reboot!
Now, fingers crossed, you should be booting into a fully functional 8.1 Oreo! if you did, congratulations!
Please let me know if I've made any mistakes and/or this has worked for you.
All credits go to the awesome people at 4PDA, especially nik-kst(if you're reading this, you the real MVP!), below I've linked the sources I've written this guide from.
Nik-kst's guide to repartitioning the device for Oreo;
Nik-kst's post about the Stable Oreo ROM.

Reserved for possible FAQ in the future

@aurismat, Hey man it worked as expected ! However, I was a bit confused on the repartitioning part when selecting ''Format all+download'' option then clicking ''start'' will only give an error stating that the IMG file of ''vendor'' is missing. (I am using SP FLASH v5.1744)
But nevertheless, I tried the ''Download only'' option and lucky it worked as well. I just wanted to clarify should it be Format all +download or Download only? Or is there a missing corresponding IMG file for vendor ?

Hey @JustAnormalGuy,
It should've been Format All + Download.
Also I'm glad that my post has helped at least one person.
Thanks for pointing out this omitted detail though, I'll edit the post ASAP.

Thanks for the translation!
--- solved ---
I have tried it three times but never managed to back up the NVRAM partition.
Error: s_dl-get_fram_setting_fail (5054) see attached screenshot
-----------
I have used Win 10 on my Mac and it worked.
Now I am stuck at step "5. Unlock the bootloader via fastboot oem unlock, and press the Volume up button to confirm the bootloader unlocking."
this looks O.K. to me
----------------------------------
>fastboot oem unlock
...
(bootloader) Start unlock flow
OKAY [ 16.047s]
finished. total time: 16.047s
-----------------------------------
But now nothing happens after
-----------------------------------
> fastboot reboot
rebooting...
finished. total time: 0.000s
-----------------------------------
It's stuck in
[Fastboot Mode] <<==
=> FASTBOOT Moe ...
and nothing happens.
UPDATE
O.K. I have used the Power Button to switch it off and on again, there was a small Android for a few seconds and the phone rebooted the second time. Now I am waiting for it to finish booting.
UPDATE 2
TWRP is working now
And what TWRP.img should I use for
"3. Flash the recovery with fastboot flash recovery [twrp recovery name].img;"
in the next paragraph? Is this the "New recovery;" from the download section at the top?
Thank you!

Missing tips:
- Put both scatter files inside the stock kernel folder before starting.
-I used the stock scatter file for the NVRAM backup then the 8.1 scatter only for the Formal all+Download step.
- When you first run the stock ROM, set up a pin or a password, otherwise you will have failed to mount data in twrp and data will show as 0mb due to its encryption.

@aurismat does that WW file includes the new vendor release?
In the vendor, a bug was detected, the camera with the auto flash turned on, did not turn on (rather, it turned on and off immediately), the flash when shooting video.
Now everything works as it should: yes2:
Fixed vendor: 07/07/2018
https://yadi.sk/d/DUGRYLnc3YtADV

I did everything according with this tutorial. Sadly my mobile network is not connecting idk why. I get an error saying Simprocessor and it doesnt connect on mobile network. It detects the networks but wont connect. Im going back to stock until someone can help me fix it.

@ZappaDong:
Yes, you should use the one I provided the link at the list of downloads.
Also, a bit late and I may be wrong, but your DRAM reads may be hindered by a MicroSD card(confirmation needed). Try ejecting it before you read off the NVRAM.
@fca.sjc:
First of all, thanks for pointing out my missing tips.
I'm not really sure if it includes the fixed vendor. I didn't really have any issues with the camera's flash, so they already included it(?)(again, needs confirmation).
For failed connections, make sure you flashed the NVRAM correctly(hence why you should test the telephony after you've repartitioned to stock 5.0 with the NVRAM backup flashed).If you failed to do that, I was told you should be able to recover the NVRAM data with Maui(?) software(confirmation needed, once again).
Thanks to both of you for pointing out these tips, I'll update the guide and credit you when I'll have more time. Cheers!

[*]For failed connections, make sure you flashed the NVRAM correctly(hence why you should test the telephony after you've repartitioned to stock 5.0 with the NVRAM backup flashed).If you failed to do that, I was told you should be able to recover the NVRAM data with Maui(?) software(confirmation needed, once again).
[/LIST]
Click to expand...
Click to collapse
After repartition, wifi, 3g and mobile signal works fine. I just cant flash twrp after unlocking bootloader otherwise i get a bootloop (unable to mount data and storage). So after i installed twrp and wiped/restore vendor and system, i reflashed stock recovery to acess android and then, restarted again to recovery. At this point, i did the write memory step again, using old vendor and the new vendor. None seem to work. I even backed up NVRAM using TWRP at first to make sure i did it right and tried to restore from there and it doesnt seem to be an IMEI issue. Maybe it has something to do with the frequency. Im on Brazil right now and idk
It does recognize my Sim card, my number, it downloads the data operators and etc but it doesnt connect to the mobile signal idk why. The bug starts at the restore step so it has something to do with this part.
I just test stuff but im pretty experienced at flashing and reflashing, etc. I guess only a dev can help and i actually went back to 7.1 UHANS rom, wich i got from 4pda.ru. Before using this rom, I was having a bluetooth audio stream bug and Ive tested like 4-5 roms, one for each kernel that was there. Lets see if someone can help me with this, cause i want oreo for better bluetooth audio stream.
Thanks for your help so far. I really apreciate it. This device is very good and we dont see many mods here on xda for it.

aurismat said:
@ZappaDong:
Yes, you should use the one I provided the link at the list of downloads.
Also, a bit late and I may be wrong, but your DRAM reads may be hindered by a MicroSD card(confirmation needed). Try ejecting it before you read off the NVRAM.
Click to expand...
Click to collapse
Thanks again!
I am using Windows 10 (bootcamp on the iMac) now and I have read the description in the 'old' [ROOT/TWRP] thread but used the files you have provided.
TWRP is working now, but I got an error that the ZIP file on the SD card was corrupted. Maybe I have damaged it when copying it to the SD card under OS X.
I am just redownloading it with Windows 10 and give it another try. (Yandex is very slow now, about 60 KB/s)
------------------------------------------------------------------
UPDATE
I have downloaded "WW_Phone-user_810_O11019_1528478718_release.zip" again, put in on the SD card, booted into Recovery, wiped system and vendor and chose "Install" , selected the "WW_Phone-user_810_O11019_1528478718_release.zip" file.
But I still get an error message.
Installing zip file '/external_SD/WW ... release.zip'
Checking for digest file
Skipping Digest Check: no Digest file found
[IN RED]Invailid zip file format!
Error installing zip file '/ 'external_SD/WW ... release.zip' [/IN RED]
Updating partion details...
...done
I have just copied the zip file from the download folder to the SD card - have I missed anything?

ZappaDong said:
And what TWRP.img should I use for
"3. Flash the recovery with fastboot flash recovery [twrp recovery name].img;"
in the next paragraph? Is this the "New recovery;" from the download section at the top?
Thank you!
Click to expand...
Click to collapse
Yup that one

@ZappaDong, yeah I kind of forgot to mention again - you should've extracted the .zip in which the backup came in. It's a backup, not an installation zip.
It needs to be extracted into its own folder inside the MicroSD card, so that then it could be used by TWRP to recover the partitions.
Thanks for pointing this out to me though, gonna edit it ASAP.

@fca.sjc bro AFAIK that problem of yours could be because of one or more of the following:
1. Your IMEI is missing or null. I would suggest SN Write tool (since I already tried it). Is quite effective, it is comparable to Maui Meta although I haven't tried it yet. (Tutorial here ==> https://forum.hovatek.com/thread-12306.html )
It is better to use PC restore tools since it writes directly to the nvram unlike apks like Chamelephon which (according to what I know) writes only to nvdata.
2. You need to switch the sims. What i mean is just if you have 2 sims on your phone, switch sim 1 in with sim 2. I forgot the explanation on it but it helps.
3. You need to switch off data connection on the other sim. On the several roms I tried on 4pda including this 8.1 pixel based rom, upon first bootup, the data connection on both sims are already on, therefore 3G cannot work. So first turn both sim's connection off then check if network mode is set to 3G. If not do the Solution #2.

JustAnormalGuy said:
@fca.sjc bro AFAIK that problem of yours could be because of one or more of the following:
1. Your IMEI is missing or null. I would suggest SN Write tool (since I already tried it). Is quite effective, it is comparable to Maui Meta although I haven't tried it yet. (Tutorial here ==> https://forum.hovatek.com/thread-12306.html )
It is the best IMEI restore tool since it writes directly to the nvram. (Meaning it retains even after wipes to data, system etc. via twrp)
2. You need to switch the sims. What i mean is just if you have 2 sims on your phone, switch sim 1 with sim 2. I forgot the logic on how that helps but I've seen it as a solution as the phone rereads the sims.
3. You need to switch off data connection on the other sim. On the several roms I tried on 4pda including this 8.1 pixel based rom, upon first bootup, the data connection on both sims are already on, therefore 3G cannot work. So first turn both sim's connection off then check if network mode is set to 3G. If not do the Solution #2.
Click to expand...
Click to collapse
Thanks for your help bro. I did check the IMEI while i was on this oreo rom. It seem to be ok. Number was there but i did not check if it was the right number. I might check it when i try to flash again. Probably later today when i'm home.
The problem wasnt just data connection, it was the connection itself. I couldnt call or receive SMS to activate whatsapp, for example. Like i said previously, those features were ok after repartitioning (on stock repartitioned). After the restore step, i did check all network options, including data, network mode, network connections available,etc. I'll follow your tutorial to restore the IMEI if the numbers are different then. I'll remember to take some screenshots next time so you guys can help me figure out what the problem is. Thanks again

aurismat said:
@ZappaDongIt's a backup, not an installation zip.
Click to expand...
Click to collapse
Yes, that did the trick. The installation went through and everything seems to work now.
Thank you again for your patience.

I saw there in the forum 4pda that are doing roms project treble pro zenfone go, only that I can not understand the mode of installation, you know how?

Ricardo Flowers said:
I saw there in the forum 4pda that are doing roms project treble pro zenfone go, only that I can not understand the mode of installation, you know how?
Click to expand...
Click to collapse
Yeah, it is possible -
FIrstly you'd need a vendor image that has fixed RIL(telephony) - vendor off this thread's 8.1 has RIL broken in Treble ROMs.
Luckily you can get it off any 8.1 custom ROM off ska-vova in 4pda. Just download any of his .zips(i.e. his ResurrectionRemix ROM(which imo is just official ResRemix with their Russian preference for a browser, but fine)), flash them and then backup the /vendor off it(and /boot for good measure)
Buuuuut then you need a TWRP that supports system image flashing - not sure if the one I provided here has it, if it hasn't - I'll post it here.
Then all you need to do is flash the Treble image, restore the /vendor(and /boot if you need to) and hope for the best!
Sadly the Havoc OS 2.0, the only ARM A-Only Pie-based ROM available here didn't work for me - just straight bootloops.
Your mileage may vary - if you get the Havoc OS 2.0 instaled, I'd love to read about it.

aurismat said:
Yeah, it is possible -
FIrstly you'd need a vendor image that has fixed RIL(telephony) - vendor off this thread's 8.1 has RIL broken in Treble ROMs.
Luckily you can get it off any 8.1 custom ROM off ska-vova in 4pda. Just download any of his .zips(i.e. his ResurrectionRemix ROM(which imo is just official ResRemix with their Russian preference for a browser, but fine)), flash them and then backup the /vendor off it(and /boot for good measure)
Buuuuut then you need a TWRP that supports system image flashing - not sure if the one I provided here has it, if it hasn't - I'll post it here.
Then all you need to do is flash the Treble image, restore the /vendor(and /boot if you need to) and hope for the best!
Sadly the Havoc OS 2.0, the only ARM A-Only Pie-based ROM available here didn't work for me - just straight bootloops.
Your mileage may vary - if you get the Havoc OS 2.0 instaled, I'd love to read about it.
Click to expand...
Click to collapse
Can you do a tutorial? I did not quite understand how it installs. Sorry, google translate does not help.

Deleted