I got a XDA new ROM which is 4.00.01. It's a BIN file. 32 MB. I don't know how to flash it. Anyone has ideas?
What's the exact size in bytes?
I have seen .bin files which start with the string 'B000FF'
you can use
Code:
perl splitrom.pl yourfile.bin -wo outfile.nb1 -t nb1
to convert it to nb1.
you can find splitrom.pl in the mkrom distribution archive.
splitrom understands several types of romimages.
Can I convert to NBF file? So that I can use PROGRAM A to install. Size is 33,555,995 bytes. It start with B000FF.
you must make sure there is either a bootloader in your .bin file,
or you get a bootloader from another source.
you can extract a bootloader from another nbf file using
Code:
perl splitrom.pl yournbf.nbf -wl bootloader.nb0
you must make very sure that your nbf really contains a bootloader, if it doesn't and programme a overwrites it with junk, you will have your self a brand new hightech paperweight.
a safer way to burn unknown images, is via an sd card + xdarit + bootloader mode.
What is the command to convert to NBF once I got the bootloader? When I try to extract the bootloader, I got the following message: "80000000 - 80040000 -- bootloader 0 files 1 modules". Does that mean no bootload information inside the NBF file?
that means you are looking at a file containing just a bootloader, no OS.
Code:
perl splitrom.pl yourfile.bin -rl bootloader.nb0 -wo outfile.nbf -t nbf -n PW10A1-ENG-3.17-001
to convert .bin + bootloader to .nbf
you can check the result again using
Code:
perl splitrom.pl outfile.nbf
Sorry about having so many questions. How can I make sure that the nbf really contains a bootloader? I use the NBF file from O2 UK RUU 3.17.03 to extract bootloader which under PROGRAM A folder. Can I use "perl splitrom.pl yourbin.bin -wl bootloader.nb0" to
extract the bootloader from my BIN file? I use UltraEdit to view the BIN file, I notice some information about bootloader 5.22 (not 5.17). The person give me this ROM said it's the PPC 2003 final. Actually I was given a HTC tool to flash the BIN file. But when I load the bin file, it checks my SD card and tells me invalid card. So I cannot flash directly.
well, that is a difficult question. in an ideal world we would have ready a list of bootloaders, and md5sums of these. for easy idendification. but not done that yet. su currently I look at the binary. and see if I see this line in the hexdump:
0000060: 4543 4543 0010 0a8c 0000 0000 0000 0000 ECEC............
and at about 0001580 there should be some lines with '*' and 'init debugserial...'
then it at least resembles something that looks like a bootloader, and not accidentally an os image. ( yes, that is a mistake we made fore you, leading us to abother intersting development : jtag flashing
5.22 is the latest I saw too.
so does your .bin file start with 'b000ff' ? can you maybe upload this file to
ftp://xda-developers.com ?
actually we noticed that somehow for recent roms the bootloader was not flashed by programme A. even though we managed to overwrite it with crap with one of our own experiments. possibly a different version of programme A. we have not researched this yet.
I would be interested in that htc program too.
you can only extract a bootloader from your .bin file if it contains one. .bin files may contain any memory region. so I don't know if yours does.
I saw the following information. So I believe it has bootloader.
0000060: 4543 4543 0010 0a8c 0000 0000 0000 0000 ECEC............
about 0001580 there should be some lines with '*' and 'init debugserial...'
I've done the following. I don't know if I'm right.
1. I run "perl splitrom.pl yourfile.bin -wl bootloader.nb0 -t nb0" to extracted the bootloader.
2. Run "perl splitrom.pl yourfile.bin -wo outfile.nb1 -t nb1" to extract OS.
3. Run "perl splitrom.pl yourfile.bin -rl bootloader.nb0 -wo outfile.nbf -t nbf -n PW10A1-ENG-4.00-001" to get NBF file. I got error message said romimage already has bootloader. So I run "perl splitrom.pl yourfile.bin -wo outfile.nbf -t nbf -n PW10A1-ENG-4.00-001" to convert to NBF file directly. I dont' know if this the right command to convert BIN to BNF file, but I didn't see any error.
4. I run "perl splitrom.pl outfile.nbf" to check and below is the result.
rommap: 80000000-81f00000
no xipchian found
no operator rim found
80000000 - 80040000 -- bootloader 0 files 1 modules
80040000 - 8015c5c8 -- kernel 5 files 5 modules
80180000 - 80376bd0 -- kernel 10 files 14 modules
80380000 - 8064306c -- kernel 20 files 36 modules
80670000 - 80be66a8 -- kernel 107 files 88 modules
80c80000 - 8102ce98 -- kernel 11 files 36 modules
81050000 - 813ef114 -- kernel 95 files 44 modules
81400000 - 815d2238 -- kernel 34 files 7 modules
815f0000 - 8171bc7c -- kernel 56 files 19 modules
817c0000 - 81adf390 -- kernel 109 files 40 modules
81980000 - 81925800 -- bitmap :30000be5 .. 010000ea
I tried to upload the file to your FTP. But no permission. Please PM your MSN Messenger ID, so that we can discuss more baout this ROM.
Thanks
I don't have msn, but you can find me on irc in #xda-developers on ircnet
( if you don't know a server: irc.nl.uu.net )
3: yes, that should work.
if you want to replace the exsisting bootloader, you can type "perl splitrom.pl outfile.nb1 -rl bootloader.nb0 -wo outfile.nbf -t nbf -n PW10A1-ENG-4.00-001"
4: ah, ppc2003 roms have a different structure splitrom cannot yet find
the xipchain in its new location. that is why it says 'kernel' on all lines.
also the bitmap it mentions is not the bitmap.
another issue may be that the nbf it creates has the wrong size, since
the xipchain in ppc2003 roms is in a location which was not originally
present in nbf files, I am not sure if programme a can write it correctly.
forgot to tell you the password: user=xdaftp pass=xdaftp
Replacing a corrupted bootloader via ActiveSync
I have a T-Mobile PPC Phone on which I have installed the AT&T radio stack and the XDA-Developers 1.1 ROM. All works well except for the fact that I appear to have corrupted the bootloader. The device now jumps directly into Windows CE and ignores any keys which I press when performing a soft reset.
From reading the rest of this thread it seems that I may be able to replace my corrupted bootloader via ActiveSync if I prepare an image file correctly. Is this true, or am I misunderstanding the ActiveSync upgrade process? As I can't reload from SD card, I'd be grateful for some expert advice before I go ahead - I can't afford to get it wrong!
Thanks,
Malcolm
Hi,
I've already upload the PPC2003 for XDA to your FTP. Please check your private message for the password for the ZIP file.
Thanks
I’m trying to run the dumpxip.pl perl script..
I Installed activestate Perl (maybe you recommend a better perl?)
I also downloaded the win32 patch at http://www.xs4all.nl/~itsme/projects/perl/Win32-API-0.41-wj2.tar.gz
And ran makefile.pl
Then nmake
I get several errors saying it cant find API.pm struct.pm etc etc
I put the files in the places it expects and I get:
Can't locate loadable object for module Win32::API in @INC (@INC contains: C:/Perl/lib C:/Perl/site/lib .) at C:\DOCUME~1\ADMINI~1\Desktop\N1 sw\dumpxip.pl line 9
Compilation failed in require at C:\DOCUME~1\ADMINI~1\Desktop\N1\sw\dumpxip.pl line 9.
BEGIN failed--compilation aborted at C:\DOCUME~1\ADMINI~1\Desktop\N1 sw\dumpxip.pl line 9.
I’m sure I’m not installing it properly.
Any ideas? Has anyone else sucesfully run this?
im following the guide -
http://wiki.xda-developers.com/index.php?pagename=Typhoon_downgrade_to_WM2003
could someone tell me how to sort out the nbfutils in perl as i havent a clue how to make the object thingy work with perl i get
cant locate loadable object for module xdadevelopers::nbfutils in @inc (@inc contains: c:/perl/lib c:/perl/site/lib .) at typhoonnbfdecode.pl line 47. begin failed--compilation aborted at typhoonnbfdecode.pl line 47.
i dont have a clue how to make the tool work in perl
help appreciated
ta
andy
Why would you want to go back from WM5 to 2003 ? WM5 is faster and more stable !
Cheers
hrb
Look at:
http://www.smartturk.info/modules.php?name=Forums&file=viewtopic&p=3675#3675
Hi all, I have problems using osnbtool: when I open it it closes immediatly...
Can somebody tell me how to use it? I'm using Windows 7
Never used it but try right click and run as administrator.
It is a console tool. You need to run it from the Command Prompt in admin priviledge.
Ok I managed to run It, the problem now is that the program crashes after some time... what should I do now?
Please somebody answer
Didn't you get this if you just type "osnbtool" on the command prompt? The built-in help is good enough. What exactly do you want to use it for?
$ ./tools/osnbtool.exe
OS ROM Partition Tool V1.59 By Weisun :> PDAclan.com
A powerful tool for de-pack partitions from OS.NB!(RAW-OS-IMAGE)
*** Decompress & compress SRPX partitions,unpack & pack partitions.
*** Support to re-structure OS.NB when insert a resized partition.
====Command for decompress,compress,unpack & pack partitions:
-d <OS.NB> <Num> <OUT.BIN> Decompress Num of part from OS image to OUT.BIN
-c <OS.NB> <Num> <IN .BIN> Compress or insert IN.BIN to OS image
====Command for split to a RAW-OS-IMAGE form srcFile & repack:
-sp <fName.ext> Split source file to fName.ext.PRE & fName.ext.OS.NB
----'fName.ext.OS.NB' means that RAW-OS-IMAGE.
----it can remove extra-data(SECTOR_ENTRYs) or B000FF struc.
-extra <fName.ext> [0x"intBlocksToFill" | 0x"dwBlockSize"] Insert extra fields (SECTOR_ENTRYs) & get fName.ext.EXA
-2bin <fName.ext> [0x"StartADDR"|-CutHeader] Pack fName.ext to BIN(B000FF)
-FixBinHeader <fName.ext> [0x'intRecordsToAdd'] Fix 'B000FF' header-entry.
====Command for unmask src file :
-x <fName.ext> <0x"dwKeyWord"> [outFile] Unmask source file to outFile
====Command for PagePool value changing in XIP.BIN:
-pp <XIP.BIN> <0x"dwOFFSET"> <decVal"MB"> [-y] Change PagePool Value at OFFSET in source XIP file
-ap <XIP.BIN> <decVal"MB"> [-y] Auto search & change PagePool Value in source XIP file.
Here the link to the newest roms for the doogee x3
www.needrom.com/category/doogee/x3-doogee/
I am using linux and use the sp flash tool with wine with looks good so far,i have to study it first before starting,but i want to start the thread already.
first problem is unpacking the rar file ..... syntax error nearby unexpected symbol 'newline' after the command #unrar e <DOOGEE-X3-6.0.rar >solved,installing unrar and reboot system(!)...
second problem rooting phone after installing ...BETA-SuperSU-v2.50.zip... recovery said installation aborted...
Than smart phone flash tool wont recognice the doogee x3...
phone is connected through usb and connected as usb storage...(i am googling for advice...)
thanks for some advice
(SOLVED see post from 9okt)rooting DOOGEE X3
After putting BETA-SuperSU-v2.50.zip. on my sdcard i went in recovery mode,volume up and power button pressed, than choosed update system by sdcard,pressed power button,choose BETA-SuperSU-v2.50.zip and pressed power button.... recovery said installation aborted..
what to do...
thanks for some advice
after flashing the recovery i got the following result...
a red line(download DA 100%) and an popup telling ERROR: S_ TIMEOUT (1042)
on the terminal....
[[email protected] SP_Flash_Tool_exe_Linux_v5.1632.00.100]# ./flash_tool.sh
QGtkStyle was unable to detect the current GTK+ theme.
Qt: Session management error: None of the authentication protocols specified are supported
QMetaObject::connectSlotsByName: No matching signal for on_pushButton_browser_clicked()
QThread::setPriority: Cannot set priority, thread is not running
"07-30-2016"
QObject::moveToThread: Cannot move objects with a parent
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:13.2/usb2/2-5
[email protected]/devices/pci0000:00/0000:00:13.2/usb2/2-5/2-5:1.0
[email protected]/devices/pci0000:00/0000:00:13.2/usb2/2-5/2-5:1.1
[email protected]/devices/pci0000:00/0000:00:13.2/usb2/2-5/2-5:1.1/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 2000
device pid = 2000
com portName is: /dev/ttyACM0
Total wait time = -1472583651.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
connect DA end stage: 2, enable DRAM in 1st DA: 0
COM port is open. Trying to sync with the target...
Failed to Connect DA: S_TIMEOUT
Disconnect!
BROM Exception! ( ERROR : S_TIMEOUT (1042)
[HINT]:
)((ConnectDA,../../../flashtool/Conn/Connection.cpp,131))
thanks for some advice...
connecting not as root but as user after setting gtk theme in user dir
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-4
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-4/1-4:1.0
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-4/1-4:1.1
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-4/1-4:1.1/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 2000
device pid = 2000
com portName is: /dev/ttyACM0
Total wait time = -1472900250.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
Connect BROM failed: S_COM_PORT_OPEN_FAIL
Disconnect!
BROM Exception! ( ERROR : S_COM_PORT_OPEN_FAIL (1013)
[COM] Failed to open COM port.
[HINT]:
)((ConnectBROM,../../../flashtool/Conn/Connection.cpp,85))
solved,i installed ubuntu followed al the instructions put the flashtool on upgrade connectthe phone and android 6.0 was installed after a few minutes.
devrieshh said:
solved,i installed ubuntu followed al the instructions put the flashtool on upgrade connectthe phone and android 6.0 was installed after a few minutes.
Click to expand...
Click to collapse
I made it in Windows yesterday successfully. There is also a way to flash TWRP on Doogee X3 running Android 6.0.
Look here: http://4pda.ru/forum/index.php?showtopic=713470&st=100#entry51434308
The Problem is, I don't understand russian and I even can't type it. Also the Captcha is a major problem. I think there is an account needed to be able to download the board attachments. Otherwise "404" error. Could anyone Download TWRP for Android 6.0 from this site + the scatter file there ? Would be awesome :highfive:
EDIT: I got it and already installed it. it works ! twrp on doogee x3 running android 6.0. just flash it with sp flash tool. you know how if you had flashed 6.0 already
link: http://www18.zippyshare.com/v/yAM5FXOt/file.html
have fun
EDIT: don't try to root it. doesn't work. neither supersu, kingo root nor kingroot. i tried it and my nvram was corrupt after trying with supersu. had to flash back imei and wifi mac address. i'm back on android 5.1 for this device.
Flashing didnt work,it said coudnt find files or path wasnt right,a red line...
after a wile the flash window got black and wite got frosen,i closed it started to reload and then the flash window didnt showed up and the message in the therminal was ...
:~/Desktop/SP_Flash_Tool_exe_Linux_v5.1520.00.100$ ./flash_tool.sh
QGtkStyle was unable to detect the current GTK+ theme.
QObject::moveToThread: Cannot move objects with a parent
so i dont know what to do now for the moment
solved,reinstalled ubuntu.. flashed TWRP_3.0.2_Doogee-X3_Android-6.0.zip
Ok i managed to root our doogee X3,tryed it with an old root tool used with my samsung gio,flashed with the TWRP 3.0.2.
SOLVED (file is already .img ,not .dat) trying to port cm-13.0-20160817-UNOFFICIAL-TECNO W4-nana (MTK 6580) i got a problem after the ./sdat2img.py command .../S2603_DG_A42_PUBLIC_M_V0.2.8_S160628$ sudo ./sdat2img.py system.transfer.list system.new.dat sys
tem.img
Traceback (most recent call last):
File "./sdat2img.py", line 131, in <module>
main(sys.argv)
File "./sdat2img.py", line 75, in main
version, new_blocks, commands = parse_transfer_list_file(TRANSFER_LIST_FILE)
File "./sdat2img.py", line 43, in parse_transfer_list_file
trans_list = open(TRANSFER_LIST_FILE, 'r')
FileNotFoundError: [Errno 2] No such file or directory: 'system.transfer.list'
anybody know what to do...
doing the same with the cm 13 rom...
/cm-13.0-20160817-UNOFFICIAL-TECNO W4-nana$ sudo ./sdat2img.py cm-13.0-20160817-UNOFFICIAL-TECNO
%20W4-nana .transfer.list system.new.dat system.img
Traceback (most recent call last):
File "./sdat2img.py", line 131, in <module>
main(sys.argv)
File "./sdat2img.py", line 75, in main
version, new_blocks, commands = parse_transfer_list_file(TRANSFER_LIST_FILE)
File "./sdat2img.py", line 43, in parse_transfer_list_file
trans_list = open(TRANSFER_LIST_FILE, 'r')
FileNotFoundError: [Errno 2] No such file or directory: 'cm-13.0-20160817-UNOFFICIAL-TECNO%20W4-nana'
devrieshh said:
Ok i managed to root our doogee X3,tryed it with an old root tool used with my samsung gio,flashed with the TWRP 3.0.2.
Click to expand...
Click to collapse
[at first for everyone to know: it affects Android 6.0 for the Doogee X3. Android 5.1 is no problem.]
root checker told me my device is rooted after I flashed your zip. The problem I experienced was, I got no asking for root triggered by any app which uses root permission. And also when I try to update SuperSU binary inside the app it tells me there is no "su data" and it couldn't update it. I think to get a flawless root permission it would take a while
SOLVED $mkdir working and than.... $ sudo mount -t ext4 -o loop /img-tools/sys.raw working/
so i did succeed to format the system.img to sys.raw but after trying to mount the sys.raw image i got the following response after the in the tortual suggested command
Am I right that you are already working in the directory "/img-tools" and want to mount the sys.raw file in it ? So then, if you determine to mount "/img-tools/sys.raw" that this could be interpreted as mount "/img-tools/img-tools/sys.raw", a directory that doesn't exist ?
Or am I seeing something wrong ?
i have compiled the system.img file to sys.raw and i want the sys.raw folder so that you can swich framework,apps and other folders with roms to port
i want to have the outcom from the sys.raw ext4 file mounted in the /base home/working folder..
see .http://forum.xda-developers.com/chef-central/android/guide-how-to-port-lollipop-marshmallow-t3283452
mounting system.img should do the job ,so you do not have to format it to sys.raw.
i made a map working in the img-tools map,but with the command below i got ...mount point working/ does not exist
base home/img-tools$ sudo mount -t ext4 -o loop system.img working/
mount: mount point working/ does not exist
devrieshh said:
i have compiled the system.img file to sys.raw and i want the sys.raw folder so that you can swich framework,apps and other folders with roms to port
i want to have the outcom from the sys.raw ext4 file mounted in the /base home/working folder..
see .http://forum.xda-developers.com/chef-central/android/guide-how-to-port-lollipop-marshmallow-t3283452
mounting system.img should do the job ,so you do not have to format it to sys.raw.
i made a map working in the img-tools map,but with the command below i got ...mount point working/ does not exist
base home/img-tools$ sudo mount -t ext4 -o loop system.img working/
mount: mount point working/ does not exist
Click to expand...
Click to collapse
I'm more familiar with DOS. But the principle should be the same.
i will try to understand the link you posted...will keep you informed
EDIT: if i'm right, then you are inside the "img-tools" folder and trying with this command to mount system.img to a folder named "working" in it.
e.g.: /base home/img-tools/working
but you want to mount it to the folder /base home/working, right ?
so you have to type it in another way. try: sudo mount -t ext4 -o loop system.img /base home/working/
I'm not sure what Linux expect. maybe the slash before "base home" in my example is not needed.
fixt it http://stackoverflow.com/questions/8663891/how-to-mount-the-android-img-file-under-linux
/Downloads/doogee x3 porting/base/base home/img-tools$ mkdir sys
[email protected]:~/Downloads/doogee x3 porting/base/base home/img-tools$ sudo mount -t ext4 -o loop sys.raw sys/
[email protected]:~/Downloads/doogee x3 porting/base/base home/img-tools$
i had to use my sys.raw file and make a sys map with ...mkdir sys ... command
How to convert .img to .raw... download img-tools extract it in a folder (http://forum.xda-developers.com/chef-central/android/guide-how-to-port-lollipop-marshmallow-t3283452) put the system.img from base rom with it and run the command... ./simg2img system.img sys.raw
I sat the whole night to find any supersu which roots flawless our doogee x3 on android 6.0. and i found it ! i flashed, installed, reflashed about hundred of times another supersu version by version downwards. it's the version 2.61 which works properly ! and yes, you can still use the playstore update of supersu + binary update inside the app without losing root or getting a boot stuck. see linked zip for working supersu you'll better save it safely
http://www89.zippyshare.com/v/iUH99ub0/file.html
EDIT: I'm not sure it could be important, but I kept the system partition as read only as I installed SuperSU. Maybe you want to do it also.
i bought a doogee x5 so i am no longer active in this forum