Related
Hello,
I need to unlock my Seimens Sx56 I downloaded version 1.2exe
but I get an error message "can not find ROM image to upgrade your Pocket PC"
Current
ROM A30.09
ROM 01/01/04
Radio Version A.33.02
Protocol version 1.3.3
Any suggestions, please help :
looking for the same.
it might require special editio rom.
What have you downloaded, and what is required by you? Maybe i can help....
Stefan
as per following thread link
http://forum.xda-developers.com/viewtopic.php?t=1611
http://forum.xda-developers.com/viewtopic.php?p=4203
I came to know from following
"Update: Do not download or install The Manipulator unless you have a serial cable already, and need to reset the call counters or change the IMEI on phones with Radio software prior to 4.20. To remove the SIMlock, simply install the XDA-developers Special Edition ROM, which, apart from unlocking the device, adds lots of other extras. Look at the forum for details on where to get it"
I think I must have "Special Edition ROM" which is not available right now. "I am downloading XDA-developers-SER-v12.exe" but Its for new xdaII I think, it might not work for xdaI.
some other I have downloaded are,
*Unlock XDA manipulator program.zip (contains XDAmSetup.exe)
*XDAunlock.exe (of 19k, which is not working I have tried it. )
*XDAunlock-src.zip (I have download this 2 months back but dont know what is it for).
my phone details
==================
make : ATT
ROM : A.30.09 eng
rom date : 01/01/04
radio ver: A.33.02
protocol v.: 1.3.3
MODEL : PW10B1
==================
Please tell me what should I do.
xdaI99 said:
I am downloading XDA-developers-SER-v12.exe" but Its for new xdaII I think, it might not work for xdaI.
Click to expand...
Click to collapse
That is the right file. It's designed for the xda I devices and is able to unlock your device.
There are several places to download it. You can get it via edonkey, should be announced somewhere here on this site, or you can get it from me.... http://lumpistefan.dyndns.org/tools/special_rom_1.2.exe.zip
xdaI99 said:
*Unlock XDA manipulator program.zip (contains XDAmSetup.exe)
Click to expand...
Click to collapse
This tool requires a serial cable and i think a Radio version before yours
xdaI99 said:
*XDAunlock.exe (of 19k, which is not working I have tried it. )
Click to expand...
Click to collapse
This tool requires the wmodem application installed in the ROM A.30.09 do not have this.
xdaI99 said:
*XDAunlock-src.zip (I have download this 2 months back but dont know what is it for).
Click to expand...
Click to collapse
Same as above, but this is the sourcecode, for modyfing, or self compiling....
HTH
Stefan
thanks for the gr8 help man.
what you suggest me to do for unlocking now.
can you tell me small stepwise procedure because I have many following files and dont know which one should I use first. I am very new and I dont want to take risk, I came to know that procedure can permanent damage my pdaphone, I dont have serial cable yet I am going to buy it rightnow.
Thanks
Just download the XDA-developers Special-Edition ROM 1.2 and install it on your device. (just run the exe)
This should install a new rom on your device (based on 3.17.03) and this ROM includes the xdaunlockk tool. This will automaticly started at the first boot, so that your device will be unlocked.
Test it if it's really unlocked, afterwards you can upgrade your ROM to any version you want. If you don't have an image of your rom you cann cook your own rom at http://lumpistefan.dyndns.org or you can save your old rom before flashing the xda-developers rom to an SD-Card and use that for flashing back....
Check also:
http://lumpistefan.dyndns.org/tools/manual_unlock.htm
http://lumpistefan.dyndns.org/tools/manual2_unlock.htm
HTH
Stefan
as per your instruction in given link.
http://lumpistefan.dyndns.org/tools/manual_unlock.htm
there is no need of manipulator I think because I can unlock by othere way as you given.
what I will do is.
1. will backup my original rom.
2. install new SE 1.2 rom which can be install without serial cable I think as per you.
3. this rom included unlock tool inbuilt and can unlock my phone.
is this work.
and please tell me what is "XDArit (XDA ROM Image Tool V1.2)"
is it available here http://lumpistefan.dyndns.org/tools/
:?
That's it. That should work.....
xdaI99 said:
and please tell me what is "XDArit (XDA ROM Image Tool V1.2)"
is it available here http://lumpistefan.dyndns.org/tools/
:?
Click to expand...
Click to collapse
XDArit shoud be old program to write ROMS on SD-Cards.
This tool is included in the XDATools. You can get it also from my site....
Stefan
ok I am going to install special editon rom 1.2 with usb today.
as per following tutorial step.
Backup the existing bootloader and operating system using card reader
---------------------------------------------------------------------
1) Insert a blank SD card into the XDA
2) Do a hard reset (hold on/off key then press the soft-reset button) click on Contacts button and choose 'CE+BOOT TO SD', and press the action button to backup the ROMs.
3) Once complete, remove the SD card from the PPC and insert it into the card reader.
---------------------------------------------------------------------
I have now back of rom in my 256 mb sd card.
after backup my sd card is not redable not in reader and in phone, so confused again and not sure that rom is there or not . please suggest if any other backup method.
ok, as per status if its in sd card then how can I restore is in to the phone again If somthing will happen wrong while installing se_rom_1.2.
You should be able to read the card via XDATools.
The format of the Card is in a special way, to get the bootloader of the xda to read the file and flash it back on your device.
You can test it by pressing power button and doing a soft reset. Then bootloader should come up and will tell you, that he found a ROM on your card and asks you if you want to install it.
Entering the bootloader deletes all data on your device....
But if you're going to flas a new ROM on your device it's not important...
Stefan
I stuck in "Create a V5.15..." pls help
To LumpiStefans and all guys,
Your instruction to unlock SX-56 is impressive. I did perform the "backup ROM" procedure successfully although it quite not the same as you directed, cuz I using ImageTool V1.0.5, but, I stuck in "Create a V5.15 Boot Loader ..." Below are my problems:
1/ I did find the "bootloader_v5_15.nb0 from the self-extracting zip downloadable here in the 'binaries' folder" as you quoted but when I attempt to write to my SD card by Image Tool V1.0.5, I got the message " Unsupported file format, don't know how to how to read the sourcefile..."
2/ Couldn't find XDA ROM Image Tool V1.02. Was it replaced by V1.0.1 or 1.05?
3/ There is no "radio button for 'before 5.17 (1K)'"
3/ therefore, I couldn't do the following steps:
-Select SD Card from the dropdown & Choose 'Write to SD card'
-Click on the radio button for 'before 5.17 (1K)'
-Click the 'Bootloader' checkbox
-Click the '...' button and browse to the 'bootloader_v5_15.nb0' file
-Click 'OK' to write the bootloader ROM to the SD card..
BTW, I did have my new ROM cook downloaded. Just waiting for your suggestion to solve the above problems. Your help is highly appreciated!!!
Big thanks! :wink:
Hi, i have a SPV5000 and i can put a lot of kind of 1.13 rom inside, like Qtek or Orange.
But impossible to put any 1.30 rom (orange, qtek french or WWE).
I've tried a lot of solution like "put the radio first" ... rest after.
Do you know if it's possible that my hardware version refuse this 1.30 rom?
I think the guy who sell me the spv sell me a pre-serie .
Thanks
The first question I want to ask is: How do you perform the upgrade? Do you use the No ID Tool? If not, try using it. Here is an instructions I made:
The file is extracted in your computer. Once you run the shipped.exe file, you need to go to:
My Computer
Your Drive (mine is Drive C)
Show the contents of this drive
Documents and Settings
Choose your folder name
Choose "TOOLS" from the menu bar
Choose "FOLDER OPTIONS"
Click on the "VIEW" tab
Click on "HIDDEN FILES AND FOLDERS"
YOU WANT TO SHOW ALL HIDDEN FILES AND FOLDERS
Now go to TEMP folder
Now you will notice a bunch of folders will show up, tons of them to be exact. What you need to do now is click on the shipped.exe file again and "LOOK" for the folder being created because that folder is what you want to copy. If you did not see it created, you have to manually open each folder and look for the files I listed below.
Assuming you found the folder, you will have these following files inside that folder:
ms_.nbf----------------------this file is responsible for EXT ROM Version
nk.nbf------------------------this file is responsible for Windows Mobile Version
radio.nbf---------------------this file is responsible for Radio Version
EnterBL
GetDeviceData
readme
ROMUpgradeUt
RUU.conf
RUU.dll
UI.dll
MaUpgradeUt_noID
If the file MaUpgradeUt_noID is not there. You need to get hold of a copy of this file as you need this.
There you have it, REMEMBER, you need to have the MaUpgradeUt_noID file plus all the rest of the file in one folder if you want to upgrade to the ENTIRE I-Mate ROM, QTEK, O2, or whatever ROM you want.
If you only want to upgrade to the radio version then you need to delete 2 files namely: "ms_.nbf" and "nk.nbf". Leave "radio.nbf" alone and click on the "MaUpgradeUt_noID" file to initiate the Radio installation. Basically those 3 files control what you want to update on your device.
Hope my instructions were clear enough for you. Hope this helps.
Thanks for your complete response
Of course i'm using the MaUpgradeUt_noID ... i have no error message during the process but at the end after the hard reset i have black screen.
and to try to only flash the radio I renames other files .
thanks
I steel don't enderstand ....
Do you think the bootloader version is important ?
i have the O.56
SEB152030 said:
Do you think the bootloader version is important ?
i have the O.56
Click to expand...
Click to collapse
It won't hurt to try and update using Boot Loader Mode.
What do you mean "0.56"?
when I put my spv in bootloader mode, I can see on the screen :
on the top : USB
Botom of the screen V.0.56
SEB152030 said:
when I put my spv in bootloader mode, I can see on the screen :
on the top : USB
Botom of the screen V.0.56
Click to expand...
Click to collapse
You might be right. Your exec must be one of the earlier version. I remeber some time ago, someone asked the same question you did. Maybe someone else can help. Have you tried upgrading it using my instructions?
thank you again and of course I've tryed your method.
every thing works with previous version but not on 1.30
i spent 3 days on it .....
SEB152030 said:
thank you again and of course I've tryed your method.
every thing works with previous version but not on 1.30
i spent 3 days on it .....
Click to expand...
Click to collapse
I believe you need to find out how to upgrade the "Serial USB" application on your Universal for the No_ID Tool to work. Other than that you probably need a version of the No_ID Tool that works at an earlier version of the "Serial USB" version that you have. I'm sorry too, if I didn't help.
The attached utility will allow to extract .NB0 OS image from ASUS P525 "galaxy.cap" complete rom update packages, and also to update CRC on modified NB0 ROM image, to pass the flasher validity check and flash the modified ROM. Also it will allow to unpack compressed kernel partition.
The application dynamically linked to Visual C runtime libraries. They used by myriads of applications, and most likely you already have them on your system installed. If you are not (on a clean PC for example) and P525ROMTool complains about lack of needed libraries,- download and install this - http://www.microsoft.com/downloads/details.aspx?familyid=32BC1BEE-A3F9-4C13-9C99-220B62A191EE
For you technical people, the utility source is included too. You can see the basic layout, and that ASUS used Adler32 algorithm to calculate the checksum on ROMs (with slight modification that base sum was initialized to zero instead of one).
The basic procedure for cooking your own custom P525 rom is:
1) P525ROMTool -d galaxy.cap
This will extract the ROMGalaxy.NB0 OS-only image. For custom ROMs I recommend working with NB0 OS images only - no danger of corrupting bootloader & IPL this way.
2) prepare_imgfs ROMGalaxy.NB0 -nosplit
3) DelFile / AddFile
Iam not sure if you can truly fully rebuild the ROM and not to break anything (ROM tools were made for HTC platform, not for ASUS). So I recommend using DelFile/AddFile method at least for the start.
There are a lot of different ROM editing tools around, but I can not give you exact directions what is better and in which conditions - ASUS ROM cooking is less charted area then for HTCs.
I assume you know what you actually need to change on file basis for your ROM customization. If you dont know what I am talking about, this is not for you (read disclaimer at the end of the post, and think over it).
4) make_imgfs ROMGalaxy.NB0 -nosplit
5) P525ROMTool -s ROMGalaxy.NB0
it will ask about changed checksum. Enter "y" to update it. You can run P525"ROMTool -s ROMGalaxy.NB0" again to be sure that checksum was updated properly - it should'nt ask to change it second time.
6) Flash ROMGalaxy.NB0 via bootloader (copy it to SD card root, press "camera" fully, press reset).
Techincally, you can make the .cap file to flash via "autorun" loader, hovewer, I must warn you that .cap file will flash not only OS image, but also the IPL+bootloader. If something goes wrong, bootloader can be corrupted and device will be bricked.
If you flash ROMGalaxy.NB0, it will not flash over bootloader+IPL, so its a lot safer - if something goes wrong, you still must be able to flash emergency rom via bootloader.
Take note that any activity that involves the ROM updating is dangerous. Even if you understand everything, there is some risk. If you have only basic understanding of ROM mechanics, risk increases tenfold - you better consider before screwing up perfectly working and expensive device.
You have been warned.
Ingvarr, thanks a million time. I love yr WM5 Storage and I think I will love this tool also. I will start building my rom based on Sorg's build 6 since it does provide some very useful tools for us.
Ingvarr thank you for your cool tools.
But when I DIY my ROM, I can't make make_imgfs.exe work correctly. It returns some symbols I can't understand.
Even I run make_imgfs.exe just after finish running prepare_imgfs.exe, it returns the err.
Could you help me with this?
make_imgfs ROMGalaxy.NB0 -nosplit
NOT "nk.nba"
It writes the modified filesystem back in the original image, so it should remain the same. You dont want to mix the ASUS and HTC ROMs and then flash it to your device, trust me
I recommend you to read HTC ROM Tools instructions and forum threads and be sure you've got right how it works, before you screw something up
sir,
Bad news，it can't work with CHS ROM （ROMgalaxy.nb0） checksum error！～～～
Does it correctly verify the checksum on original ROM?
I will try to look over it, maybe I've missed something.
Btw, if you can, write down what does writes on screen _exactly_, down to the point of failure (including error message).
Ingvarr said:
Does it correctly verify the checksum on original ROM?
I will try to look over it, maybe I've missed something.
Btw, if you can, write down what does writes on screen _exactly_, down to the point of failure (including error message).
Click to expand...
Click to collapse
i have tried it too.
i updated the checksum in sorgs rom, and then i found, that the checksum from ur SW is diffrent with the original Checksum in sorgs ROM
harlemyin said:
i have tried it too.
i updated the checksum in sorgs rom, and then i found, that the checksum from ur SW is diffrent with the original Checksum in sorgs ROM
Click to expand...
Click to collapse
You mean, it claims that checksum is wrong even when you have not modified NB0 yet?
I may look over this NB0, can you host it somewhere? But better not at rapidshare, Iam already topped my limit
Ingvarr said:
You mean, it claims that checksum is wrong even when you have not modified NB0 yet?
I may look over this NB0, can you host it somewhere? But better not at rapidshare, Iam already topped my limit
Click to expand...
Click to collapse
yes
and it happens by official P525_V3320_WWE2nd too
checksum in official P525_V3320_WWE2nd is 79AB7436
ur SW changed it to EF722461----not modified NB0
u can download official P525_V3320_WWE2nd with www.asus.com or
ftp://dlsvr02.asus.com/pub/ASUS/IA/P525/P525_V3320_WWE2nd.zip
Thats odd, because I've just checked it with WWE 3.32 and at least checksum calculation defenitely works ok...
This roms are in .CAP package. Have you actually extracted .NB0 from .CAP?
I have uploaded version 1.01 - it has additional sanity checks to make sure that you try to run it on NB0 with structure it expects.
Try it on WWE 3.32 and write what the original checksum and calculated checksums will be.
sorry
our mistake
i tested ur SW with a *.nb0, which extracted with xda3nbftool.exe------*.nb0 with ipl and bootloader.
and now i find, that *.nb0 should be and must be extracted with ur P525ROMTool -d galaxy.cap,------that means *.nb0 without ipl and bootloader
everything is fine, when *.nb0 is extracted with ur P525ROMTool
i think creazy2000 just made the same mistake like me.
o
thanks a lot.
Thanks. The tool works perfectly on my P525.
Ingvarr said:
Thats odd, because I've just checked it with WWE 3.32 and at least checksum calculation defenitely works ok...
This roms are in .CAP package. Have you actually extracted .NB0 from .CAP?
I have uploaded version 1.01 - it has additional sanity checks to make sure that you try to run it on NB0 with structure it expects.
Try it on WWE 3.32 and write what the original checksum and calculated checksums will be.
Click to expand...
Click to collapse
I make a mistake, thanks!
harlemyin said:
sorry
our mistake
i tested ur SW with a *.nb0, which extracted with xda3nbftool.exe------*.nb0 with ipl and bootloader.
and now i find, that *.nb0 should be and must be extracted with ur P525ROMTool -d galaxy.cap,------that means *.nb0 without ipl and bootloader
everything is fine, when *.nb0 is extracted with ur P525ROMTool
i think creazy2000 just made the same mistake like me.
Click to expand...
Click to collapse
Oh, I know !
I make a mistake !
thanks
Is it a seperate tools that the imgfs? Need I find this tool to finish the whole things? Where can I find this tool?
P525_V3320_WWE2
I have P525_V3.29.0 WWE3
Can someone tell the difference between them it looks that the first one is newer but I am confused by the WWE which is newer
Thanks all
Night Runner said:
Is it a seperate tools that the imgfs? Need I find this tool to finish the whole things? Where can I find this tool?
Click to expand...
Click to collapse
Everything about complete process is in the first post. What is you dont understand from here?
jmfa59 said:
P525_V3320_WWE2
I have P525_V3.29.0 WWE3
Can someone tell the difference between them it looks that the first one is newer but I am confused by the WWE which is newer
Thanks all
Click to expand...
Click to collapse
WWE means "world wide english".
First is 3.32, therefore, its newer.
Ingvarr
Thanks Buddy,
can you explain WW2 and WWE3 it seems that the latter is newer but the version V3.29 is older or is ment for different country
sasovics said:
OK folks I DIT IT FINALLY!
Use the patched "Upgrade Tool.exe" (attached)
Then download both WWE version WM6 ROM and your current language WM6 ROM (mine was Czech so I dowloaded CSY).
Use a HEX editor and copy the ROM header (range: 00000h - 10000h) from your current lang. ROM and paste (overwrite the header - same range) in WWE ROM. Uplolad the modified ROM onto your SD card along with patched Upgrade Tool and update.dat (this was unchanged) and begin update.
My PDA was Czech and now is English!!! Everything's working like a charm!
Please note, my upgrade was successful, but if you want to try this method, do it on your own risk! I will not take any responsibility in case you damage your device!
Cheers,
sasovics
Click to expand...
Click to collapse
Does anyone tried this and get it successfully done? I got one A639 last week but it is English version. I cann't install too much thing.
i have a blue ASUS screen
i cannot enter windows in asus to make the update.
is anybody knows the way to ulpoad a new ROM to the A639 without entering windows. for ex: from the SD in bootloader, or by USB
thanks for any help!
update: i can maker hard reset - but nothing happens
i can enter to bootloader, and the device recognizes the FAT16 SD, but the upgrade does not start...
i need the rom as BIN file for that. does somebody have it..?
Hey guys,
It seems more and more people are receiving the new version of the P8000:
- Stock Android 6
- New fingerprint scanner that is moved slightly higher and is able to unlock phone from screen-off (I confirm this is working)
- Sim 2 is combined with the micro-sd (I haven't tried whether you can have them both in at the same time)
- Somethings new about the display, since people are reporting errors with it after flashing older roms.
Warning: do NOT flash other roms. We have no way to unbrick the soft bricks yet!
---
Other topics that refer to this version:
http://forum.xda-developers.com/elephone-p8000/general/rom-p8000-t3431571
http://forum.xda-developers.com/elephone-p8000/help/stock-rom-p8000b-t3434477
http://forum.xda-developers.com/elephone-p8000/general/p8000-version-announced-t3346848
---
For development:
- The phone does not come pre-rooted. We have no way to flash custom recovery yet. Any tips for getting root? I've tried such tools as Kingo and vRoot, they don't work.
- We need the blocks file (scatter file) for SP Flash Tools. MTKDroidTools reports "unknown rom structure". Any help? Would love to start working on this.
Looking forward to hearing from others who have this version/who can help me with these questions.
Thanks!
Emile
Nice! Can you provide a dump from /system and /boot maybe?
BlueFlame4 said:
Nice! Can you provide a dump from /system and /boot maybe?
Click to expand...
Click to collapse
I would, if I knew how to. Any pointers?
Emileh said:
I would, if I knew how to. Any pointers?
Click to expand...
Click to collapse
Sure thing. On a rooted device, go into adb shell.
Then use "mount" command to check which partitions are mounted. One should be "/dev/block/platform/mtk-msdc.0/by-name/system" or similar. Use "dd if=/dev/block/platform/mtk-msdc.0/by-name/system of=/storage/emulated/0/system.img bs=1M" to dump the system to the internal sdcard to the file "system.img". If adb complains that bs=1M is an invalid option, try again without that one. A system dump can take some time where you will not get any feedback, so be patient there
Do the same for boot. So "/dev/block/platform/mtk-msdc.0/by-name/boot" should be the way to go for the path. I cannot tell the definite pathes on Android 6.0 but I am rather sure they are more or less like this.
If you run into troubles, just ask
BlueFlame4 said:
Sure thing. On a rooted device, go into adb shell.
Then use "mount" command to check which partitions are mounted. One should be "/dev/block/platform/mtk-msdc.0/by-name/system" or similar. Use "dd if=/dev/block/platform/mtk-msdc.0/by-name/system of=/storage/emulated/0/system.img bs=1M" to dump the system to the internal sdcard to the file "system.img". If adb complains that bs=1M is an invalid option, try again without that one. A system dump can take some time where you will not get any feedback, so be patient there
Do the same for boot. So "/dev/block/platform/mtk-msdc.0/by-name/boot" should be the way to go for the path. I cannot tell the definite pathes on Android 6.0 but I am rather sure they are more or less like this.
If you run into troubles, just ask
Click to expand...
Click to collapse
Thank you for your great instructions! The problem is that we've yet to achieve root on this device. We don't have a custom recovery for this version of the P8000 yet and other 'standard' methods of rooting don't work for me.
(I'm pretty solid in shell, so I'll do this afterwards, but I guess root is actually the first step).
// Edit to say: it does not come pre-rooted
Since the elephone support on facebook didn't realize there are two different versions of the P8000 available, I still need a ROM to unbrick my phone.
flo1k said:
Since the elephone support on facebook didn't realize there are two different versions of the P8000 available, I still need a ROM to unbrick my phone.
Click to expand...
Click to collapse
Ok, we know that, but doesn't really help us
Can you write them an e-mail?
I will do
Edit: OK, see if there will be an answer.
Thank you flo1k!
I have e-mailed as well, and would like to post on the Elephone forum, but don't seem to have access (because of minimum post count, I guess)
Anyone willing to ask for a ROM for the new P8000 on the forum there?
ROM Dump
@BlueFlame4
I can provide ROM dump in two versions:
1) a dump from adress 0000 0000 to 9d80 0000 (apr. 2.5 GB in one file)
2) a readback generated with the scatter.txt of the 'old' 5.1 stock ROM (apr. 2.8 GB seperated in 23 files)
FrauHofrat said:
@BlueFlame4
I can provide ROM dump in two versions:
1) a dump from adress 0000 0000 to 9d80 0000 (apr. 2.5 GB in one file)
2) a readback generated with the scatter.txt of the 'old' 5.1 stock ROM (apr. 2.8 GB seperated in 23 files)
Click to expand...
Click to collapse
The second choice looks promising
Maybe a stupid question
where shall I upload the files - any preferred webspace?
I'm uploading the files - because they contain my NVRAM I send the link as PM as soon as the upload is finished
FrauHofrat said:
Maybe a stupid question
where shall I upload the files - any preferred webspace?
I'm uploading the files - because they contain my NVRAM I send the link as PM as soon as the upload is finished
Click to expand...
Click to collapse
Are you sure we're talking about the same version of the P8000? Cause as far as I know there isn't 5.1 available for this version... Right?
Just checking thank you for your help in any case!! Really looking forward to it.
// edit: ah, you just used the old scatter file. But does that one work for this version?
Emileh said:
Are you sure we're talking about the same version of the P8000? Cause as far as I know there isn't 5.1 available for this version... Right?
Click to expand...
Click to collapse
No, there is only one Firmware available - the mysterious P8000_6.0_20160516.
Btw, this Phone contains a new mainboard model "K06TS-L-V2.0.3" - the 'old' mainboard is moder "K05T...."
// edit: ah, you just used the old scatter file. But does that one work for this version?
Click to expand...
Click to collapse
No, it doesn't work resp. the phone boots with this firmware, but the LCD-driver is the wrong one - the display only shows coloured lines and blurry spots. And there are probabely some more bugs ....
FrauHofrat said:
No, there is only one Firmware available - the mysterious P8000_6.0_20160516.
Btw, this Phone contains a new mainboard model "K06TS-L-V2.0.3" - the 'old' mainboard is moder "K05T...."
No, it doesn't work resp. the phone boots with this firmware, but the LCD-driver is the wrong one - the display only shows coloured lines and blurry spots. And there are probabely some more bugs ....
Click to expand...
Click to collapse
But if the phone boots with the firmware, doesnt that mean that the scatter file of the regular P8000 works? Since it flashes the firmware correctly.
The problem is that I was not able to flash the 'readback files' to the faulty phone.
When selecting 'Only Download' at SP-Flashtool I got the error "PMT... must be download"
When selecting 'Firmware Upgrade" I got some BROM error code
In both cases I used the same scatter,txt which I used to 'readback' the firmware from the working phone
Actually I have to correct my statement in post #15:
I flashed the faulty phone with the last 5.1 stock ROM (160711) - with this stock ROM the phone boots up but LCD (and probably more things) is not working.
I have actually gotten alot further
You have the use the scatter.txt from Android 6.0, which works perfectly fine. I have been able to extract boot.img, system.img and recovery.img that way (using Readback in SP Flash Tools)
Which ones do you need?
They probably flash fine (only thing I've flashed so far are custom recoveries, and although my ported PhilZ starts, I havent gotten it to mount anything.)
A little warning: don't use anything that has anything to do with Android 5.1. Those scatter files don't work
These are great news!
"Which ones do you need?"
Probably all of them
Ok this contains the scatter file, preloader, system.img, boot.img and stock recovery.img
https://ehaffmans.stackstorage.com/index.php/s/uKGKCir0BociydU
You need SP Flash Tools v5, select the scatter file first, then deselect everything, and only select these 4 and manually select the correct files.
Btw, the name of the preloader file is wrong, don't worry. It came from this phone
I am of course not responsible for anything!
Can you guys please confirm this doesn't contain anything personal? Like personal files or IMEI or something. Thanks!