Yesterday i brick my phone when try flash this beta TSS ROM in my X02T
http://forum.xda-developers.com/showthread.php?t=657694&page=3
Soo after fail i try with anothers ROMS too, like Mod-TG01TSS01.7z, Mod-TG01TSS02.7z (flash error, say invalid file), TG01TSS01.7z, TG01TSS02.7z (flash error, say invalid file), T01A_to_SP50_wm65.tsd, T01A_to_SP50_wm65-theduyet.enc and TG01WP-WM6.5-Orange-UK (flash error, say invalid file).
I still can use the SD downloader, i can flash "any" ROM whith pin method,
Before i brick my phone i make a RAW file of my phone and there is here:
http://cid-5bf4bd469b8aef18.skydrive.live.com/browse.aspx/X02T
txt is here:
------------------------------------------------------------------------------------
9.63M (0x9a0000) DSK1:
| 9.62M (0x99f000) Part00
423.00M (0x1a700000) DSK2:
| 1.62M (0x19f000) Part00
| 3.75M (0x3c0000) Part01
| 159.88M (0x9fe0000) Part02
| 257.75M (0x101c0000) Part03
7.42G (0x1daf80000) DSK3:
| 7.42G (0x1dab80000) Part00
STRG handles:
handle#0 8dda3d4a 7.42G (0x1dab80000)
handle#1 6e1e7b2e 257.75M (0x101c0000)
handle#2 ee1ed89e 159.88M (0x9fe0000)
handle#3 4e1ed87a 3.75M (0x3c0000)
handle#4 4e1ed832 1.62M (0x19f000)
handle#5 ee4ac72e 9.62M (0x99f000)
disk 8dda3d4a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 6e1e7b2e
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk ee1ed89e
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 4e1ed87a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 4e1ed832
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk ee4ac72e
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
------------------------------------------------------------------------------------
Please someone could help me Revive my phone !!!
Thanks alot
Toshiba make a new update for X02T, a small update i think with SMS, this file is X02T_from_SP00_to_01_000.tis, soo is TIS file, maybe this file have the key for revive my phone.
link is here:
http://toshibamobile.com/cgi-bin/softbank/x02t/update/uprom.cgi?sp=00
or
http://update.toshibamobile.com/update/x02t/sp00/X02T_from_SP00_to_01_000.tis
You flashed TG01TSS01.7z, don't you?
Your situation is the same as "xandetonetti".
Please the following Pin method.(from Orange in T01A case)
--------------------------------------------
This Pin method is short Pin 1 and Pin 2.
And, You can The power button pushed with the state maintained.
Then, Your T01A screen displays your ROM after five seconds.
--------------------------------------------
Did it work? If not, can you try as naxt.
We now know that the TSS Encryption Key of X02T is 44460046.
However, The Encryption of your device is tsw,
because you flashed tsw bootloader ROM into your X02T,
You can try the following ROM.
*Official Orange UK ROM
http://www.toshiba-europe.com/mobile/Images/TG01WP-WM6.5-Orange-UK.zip
[TG01WP_5005000176.tsw → TG01.tsw]
*Official docomo JP ROM (T01A_to_SP50_wm65.tsd is extracted by zip. )
http://update.toshibamobile.com/update/t01a/wm65/T01A_to_SP50_wm65.exe
--------------------------------------------------
tgtool -t01a -sp T01A_to_SP50_wm65.tsd os.nb.payload
tgtool -t01a -mp os.nb.payload T01A_to_SP50_wm65.tsd T01A_to_SP50_wm65.bin
--------------------------------------------------
You can download TSW TOOLS by cotulla from
this URL(http://cotulla.pp.ru/Misc.html), and
convert bin to tsw by this tool in TG01 mode.
[T01A_to_SP50_wm65.tsw → TG01.enc]
You can flash those ROM, maybe.
yamadori said:
You flashed TG01TSS01.7z, don't you?
Your situation is the same as "xandetonetti".
Please the following Pin method.(from Orange in T01A case)
--------------------------------------------
This Pin method is short Pin 1 and Pin 2.
And, You can The power button pushed with the state maintained.
Then, Your T01A screen displays your ROM after five seconds.
--------------------------------------------
Did it work? If not, can you try as naxt.
Click to expand...
Click to collapse
Thanks for you quick reply friend. i have 2 news!!
1 - The good news, is the short Pin 1 and 2 work!!! phone is alive again thanks very much friend..
2 - Bad news, my last try i flash the T01A ROM, soo my phone is DOCOMO now, but in english, and the TG01TSS01.7z dont flash anymore, say File is invalid!!!
I un7zip and rename for TG01.enc, after copy to PRG folder (this work in first time, but dont work more, maybe because i flash T01A for last)
But i need short the pin 1 and 2 any time when reset right? Soo how i can puth the SIM card, without revome the batery and Short pins 1 and 2?
1
I finaly able to insert the SIM card to phone after short pin 1 and 2, but now WM ask me for a Password for unlock my SIM? have you any idea what is this? or any way for flash the TG01TSS01.7z again?
2 - Bad news, my last try i flash the T01A ROM, soo my phone is DOCOMO now, but in english, and the TG01TSS01.7z dont flash anymore, say File is invalid!!!
Click to expand...
Click to collapse
Is the bootlogo of your X02T docomo?
If yes, the Encryption of your device is tsd,
You can flash tsd ROM and can not flash tss ROM.
You can try T01A_to_SP50_wm65-theduyet.tsd ROM.(rename to TG01.enc)
And, is the Pin method both Docomo and Orange ROMs necessary for
your X02T?
If yes, We can not do anything. Because we only have bootloder of
TG01 and T01A, not have X02T.
Sorry.
I finaly able to insert the SIM card to phone after short pin 1 and 2, but now WM ask me for a Password for unlock my SIM? have you any idea what is this? or any way for flash the TG01TSS01.7z again?
Click to expand...
Click to collapse
You must be use SoftBank SIM, or delete SIMUnlockP.exe in windows folder.
yamadori said:
Is the bootlogo of your X02T docomo?
If yes, the Encryption of your device is tsd,
You can flash tsd ROM and can not flash tss ROM.
You can try T01A_to_SP50_wm65-theduyet.tsd ROM.(rename to TG01.enc)
And, is the Pin method both Docomo and Orange ROMs necessary for
your X02T?
If yes, We can not do anything. Because we only have bootloder of
TG01 and T01A, not have X02T.
Sorry.
You must be use SoftBank SIM, or delete SIMUnlockP.exe in windows folder.
Click to expand...
Click to collapse
Yes the bootlogo is DOCOMO and the T01A ROM work good, but i only can flash ROM with .tsd, when i try with .enc say invalid file.
i will try delete this file for skip the password.
i cant find SIMUnlockP.exe in windows folder, have another way for evade the password?
With my Hermer i have a program called "Connection Setup" for easy config the phone, i just choise japan and Vodafone, you know where i can find this program or another like this?
and if my phone now is tsd Encryption, why o still need short pin? if i rename the TSS file for tsd i can turn she back to SoftBank?
Thanks very mush...
eekthecat said:
i cant find SIMUnlockP.exe in windows folder, have another way for evade the password?
With my Hermer i have a program called "Connection Setup" for easy config the phone, i just choise japan and Vodafone, you know where i can find this program or another like this?
and if my phone now is tsd Encryption, why o still need short pin? if i rename the TSS file for tsd i can turn she back to SoftBank?
Thanks very mush...
Click to expand...
Click to collapse
It seems that you have flashed a english rom on X02T sucessfully.
Congratulations！
i cant find SIMUnlockP.exe in windows folder, have another way for evade the password?
Click to expand...
Click to collapse
Your X02T can use only softbank SIM, because we do not find
the method of X02T SIM unlock as well as T01A.
and if my phone now is tsd Encryption, why o still need short pin? if i rename the TSS file for tsd i can turn she back to SoftBank?
Click to expand...
Click to collapse
No. The bootloader of X02T is not the same as T01A it.
There is no ROM of X02T bootloader yet. Therefore, method of PIN(1&2) is needed in ROM of T01A and TG01 bootloader.
By the way,
I will pass you this ROM, because your device bootloader is docomo.
http://www.mediafire.com/?qmznk0ygzxj
This ROM might be able to use "X02T_from_SP00_to_01_000.tis", or not.
Please enjoy it.
Thanks very much friend, but i think the file is corrupted, i try download 3 times, and get a error when try un7zip. Could you upload the ROM again plz
Thanks very much friend, but i think the file is corrupted, i try download 3 times, and get a error when try un7zip. Could you upload the ROM again plz
Click to expand...
Click to collapse
Please delete Cash and do download again.
And, please do unzip by this tool http://www.7-zip.org/.
I can not upload it because I can't use Broadband today.
yamadori said:
Please delete Cash and do download again.
And, please do unzip by this tool http://www.7-zip.org/.
I can not upload it because I can't use Broadband today.
Click to expand...
Click to collapse
Cash is deleted, i try with another with IE, firefox and Freedownload manager, also use 7zip for unzip, but the file is realy corrupted.
Don't worry if you cant upload again today, i will wait thanks alot.
upload again.
http://www.mediafire.com/?rwnm2wzjrnj
yamadori said:
upload again.
http://www.mediafire.com/?rwnm2wzjrnj
Click to expand...
Click to collapse
Thanks for upload friend, now work fine, but i cant flash this ROM. SD Downloader say : File Open Error!!!
I copy to prg folder, and try with .enc and .tsd, but both get the same error.
I still can flash ROM's like " [ROM][ENG] 6.5.5 (23563)+Sense 2.5(2011) v0.012.2 (26/04/10) Radio 5005.1600.05" but my SIM Card is SoftBank and i think the ROM Radio another, because i cant connect with SoftBank services.
OBS: I use the Convetion too for convert TG01 rom to T01A ROM
Now i able to flash you ROM, just rename the file for TG01WP_00.tsd, this is with Docome bootlogo, with my SoftBank Japanese Windows, but my i still can't use my SIM Softbank, windows report a SIM error and the Windows power off after seconds.
If i start the phone without my SoftBank SIM, widows work fine (in japanese, and with DOCOMO bootlogo) but if i start with SIM card, windows report something about SIMUnlockP and dont connect, after secs power off.
If i can only flash ROMS with TSD, is because my bootloader is Docomo now right? this make my phone only work with DOCOMO SIM'S?
hi,eecat, I have the same problem as you. I flashed a chinese rom to x02t, with pin 1 and 2 shorted method, I can boot the phone, otherwise, green light sparkle once then off. after the Chinese wm65 started, I inserted the softbank sim card, no signal. I am wondering have you solved that problem or do you have any idea to flash back to official softbank rom that I can use softbank sim card as normal? your Prompt reply will be highly appriciated.
Related
hello ther every one seeking for help with the ht 1100 neon from japan
i try to dump the rom with a niki kitchen
and also try to backup the spl with spl backup kit,thanks to jocky...
i dont know if i did it well ?
looking for someone that can guide me what to do ??
and to tell if what i do is usefull ?? can we do with it something ??
and how to make what i did to a flashebl rom??
what i do with the nikikitchen are based on a neon300
here are the links for what i did please look at it.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\orgad>pdocread.exe -l
211.13M (0xd320000) FLASHDR
| 3.12M (0x31f000) Part00
| 3.75M (0x3c0000) Part01
| 85.38M (0x5560000) Part02
| 118.88M (0x76e0000) Part03
1.83G (0x75400000) DSK1:
| 1.83G (0x753eee00) Part00
STRG handles:
handle c74f0f7a 1.83G (0x753eee00)
handle 4741ad4e118.88M (0x76e0000)
handle 6748c356 85.38M (0x5560000)
handle 6748c332 3.75M (0x3c0000)
handle 2748c06e 3.12M (0x31f000)
disk c74f0f7a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 4741ad4e
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 6748c356
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 6748c332
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 2748c06e
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
C:\orgad>pdocread -w -d FLASHDR -b 0x800 -p Part00 0 0x31f000 Part00.raw
CopyTFFSToFile(0x0, 0x31f000, Part00.raw)
C:\orgad>pdocread -w -d FLASHDR -b 0x800 -p Part01 0 0x3c0000 Part01.raw
CopyTFFSToFile(0x0, 0x3c0000, Part01.raw)
C:\orgad>pdocread -w -d FLASHDR -b 0x800 -p Part02 0 0x5560000 Part02.raw
CopyTFFSToFile(0x0, 0x5560000, Part02.raw)
C:\orgad>pdocread -w -d FLASHDR -b 0x800 -p Part03 0 0x76e0000 Part03.raw
CopyTFFSToFile(0x0, 0x76e0000, Part03.raw)
ERROR: ITReadDisk: outbuf==NULL
- 確立された接続がホスト コンピュータのソウトウェアによって中止されました。
C:\orgad>pdocread -w -d FLASHDR -b 0x800 -p Part03 0 0x76e0000 Part03.raw
CopyTFFSToFile(0x0, 0x76e0000, Part03.raw)
http://www.megaupload.com/?d=WHUK14XW
http://www.megaupload.com/?d=VQXMHUSG
http://www.megaupload.com/?d=HJ6LXD1J
http://www.megaupload.com/?d=7ZXIPD8V
wating for more instruction,and your opinion.
best regards
I've got part01.raw and part02.raw dumped using "Dump My Phone". I'm trying to get a flashable exe of this stupid japanese rom
Now I need to find a kitchen and compile an XIP? Any suggestions?
I tried rebuilding the rom dump last night with a raphael kitchen.... epic fail.
Here is a link to the raw dump if anyone is a wizard at rebuilding roms.
http://www.smithforest.com/DoCoMo_HT1100-Raw_Dump.zip
arasarn said:
I tried rebuilding the rom dump last night with a raphael kitchen.... epic fail.
Here is a link to the raw dump if anyone is a wizard at rebuilding roms.
http://www.smithforest.com/DoCoMo_HT1100-Raw_Dump.zip
Click to expand...
Click to collapse
EDIT: Updated post with model info but the file & readme still show 'unknown'. I will update that once someone tests this & let's us know if it works or not.
OK I rebuilt a rom from your dump files & can post it up but someone needs to be brave enough to test it. I followed the same procedure I used when rebuilding the WWE stock rom (which definitely works) so it SHOULD work but I don't want to be responsible if you brick your phone or overwrite a good rom you can't get back so don't say you haven't been warned!
The Rom is from the NTT DoCoMo Foma HT1100 device ID: Neon100 Japanese language NEON but I have no idea what ROM version this is so assuming it works then we should be able to get ROM version from Device Info once someone flashes it on their phone.
OK here's the good stuff: (I will update this post as more information arrives)
Rebuild Release date: 12/09/09
Thread: http://forum.xda-developers.com/showthread.php?t=520711
Download: http://www.megaupload.com/?d=TB0045FR
PASSWORD: neon
HTC Touch Dual NEON100 NTT DoCoMo Foma HT1100 'stock' (straight rebuild from original dump with no intentional changes made)
ROM: Unknown
ROM date: Unknown
Radio: NOT INCLUDED (Stock was Radio: Unknown Protocol: Unknown)
IMPORTANT: Since this is not true stock rom your NEON *MUST* have hardSPL. I use OliPro's Hard-SPL (Thanks!):
http://forum.xda-developers.com/showthread.php?t=377260
WARNING!! DO NOT INSTALL ON A NIKI! THIS IS *UNTESTED* so use at your own risk! DO NOT flash this ROM unless you are comfortable trying to recover your phone and understand the risks! Check the thread for updated info.
Either way the standard disclaimer applies: USE AT YOUR OWN RISK & be sure to check out the thread to see other's experiences.
Note: Even though I made no changes to the ROM it seems rebuilding it (in particular ImgfsToNb's bigstorage mode) should give more storage available than true stock.
Storage:
Total: ?? MB
In use: ?? MB
Free: ?? MB
Program
Total: ?? MB
In use: ?? MB
Free: ?? MB
Thanks to NetrunnerAT for the NIKI Kitchen I used as a base: http://forum.xda-developers.com/showthread.php?p=1837580
Thanks to seth2006 for NIKICustomRUU.exe from SETHS V3 FINAL Neon_V3: http://forum.xda-developers.com/showthread.php?t=419892
Super thanks goes out to all those who contributed NEON/NIKI info, those who made possible all the kitchens & related tools I used to get this ROM built.
Obviously if HTC would ever get their act together & release a RUU of a true stock rom this will be obsolete but until then this is the best bet for anyone looking for as close to stock for the NEON100 TOUCH DUAL NTT DoCoMo Foma HT1100.
Please share your results so I can update the post & hopefully others find this rebuild useful.
Bill
The Rom is from the NTT DoCoMo Foma HT1100
device ID: Neon100
I succesfully flashed the stock telstra rom (WWE) to input the SIM unlock code, now I am hoping this rom will work to put the phone back into japanese.
Unfortunately the phone now thinks it has 20 keys on the hardware keyboard instead of 16, so at this point my text entry with the phone is no good.
arasarn said:
The Rom is from the NTT DoCoMo Foma HT1100
device ID: Neon100
I succesfully flashed the stock telstra rom (WWE) to input the SIM unlock code, now I am hoping this rom will work to put the phone back into japanese.
Unfortunately the phone now thinks it has 20 keys on the hardware keyboard instead of 16, so at this point my text entry with the phone is no good.
Click to expand...
Click to collapse
Ok thanks arasarn, I'll get the post & readme updated but won't upload a new version until we've had people test the one posted.
Bill
bill rules
worked like a charm!
Now this thing is SIM unlocked and back to the original software.
Bill is the man.
grabbed some of the info off the rom we were looking for. bold and red
Windows mobile build 18553.0.7.6
bill48105 said:
HTC Touch Dual NEON100 NTT DoCoMo Foma HT1100 'stock' (straight rebuild from original dump with no intentional changes made)
ROM: 1.26.731.01
ROM date: 05/06/08
Radio: NOT INCLUDED (Stock was Radio: Unknown Protocol: Unknown)
IMPORTANT: Since this is not true stock rom your NEON *MUST* have hardSPL. I use OliPro's Hard-SPL (Thanks!):
http://forum.xda-developers.com/showthread.php?t=377260
WARNING!! DO NOT INSTALL ON A NIKI! THIS IS *UNTESTED* so use at your own risk! DO NOT flash this ROM unless you are comfortable trying to recover your phone and understand the risks! Check the thread for updated info.
Either way the standard disclaimer applies: USE AT YOUR OWN RISK & be sure to check out the thread to see other's experiences.
Note: Even though I made no changes to the ROM it seems rebuilding it (in particular ImgfsToNb's bigstorage mode) should give more storage available than true stock.
Storage:
Total: 126.29 MB
In use: 33.90 MB
Free: 92.39 MB
Program
Total: 100.83 MB
In use: 34.14 MB
Free: 66.69 MB
Obviously if HTC would ever get their act together & release a RUU of a true stock rom this will be obsolete but until then this is the best bet for anyone looking for as close to stock for the NEON100 TOUCH DUAL NTT DoCoMo Foma HT1100.
Please share your results so I can update the post & hopefully others find this rebuild useful.
Bill
Click to expand...
Click to collapse
arasarn said:
worked like a charm!
Now this thing is SIM unlocked and back to the original software.
Bill is the man.
Click to expand...
Click to collapse
arasarn said:
grabbed some of the info off the rom we were looking for. bold and red
Click to expand...
Click to collapse
That is GREAT NEWS! I'm glad it worked!
Thanks, I'll get the post upated with the info and hopefully other people will test it & I'll repackage the rar.
Bill
Hi,
I'd like to get this Japanese ROM working on my Neon 200 (Aus).
I tried it, and it got through the screen alignment and customising, but it got stuck on the boot screen after that.
Would anyone be able to help me with this?
Thanks!
Is the link for the flashable rom broken now?
Thanks.
RElease soon.Have a look here
http://www.youtube.com/watch?v=-BafG8GS_TI
---------------------------------------------------------------------------------------
How to dump/backup original ROM
Microsoft Windows [Version 6.1.7100]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
E:\PocketPC\ROMs\its>pdocread -l
Copying E:\PocketPC\ROMs\its\itsutils.dll to WCE:\windows\itsutils.dll
410.75M (0x19ac0000) DSK1:
| 1.62M (0x19f000) Part00
| 3.25M (0x340000) Part01
| 90.63M (0x5aa0000) Part02
| 315.25M (0x13b40000) Part03
7.61G (0x1e6e00000) DSK2:
| 7.60G (0x1e6a00000) Part00
STRG handles:
handle cd904882 7.60G (0x1e6a00000)
handle 4f634f6e315.25M (0x13b40000)
handle 2f6aeea6 90.63M (0x5aa0000)
handle 4f6aee82 3.25M (0x340000)
handle 8f6aee3a 1.62M (0x19f000)
disk cd904882
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 4f634f6e
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 2f6aeea6
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 4f6aee82
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 8f6aee3a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Dump :
pdocread -w -d DSK1: -b 0x800 -p Part00 0 0x19f000 Part00.raw
pdocread -w -d DSK1: -b 0x800 -p Part01 0 0x340000 Part01.raw
pdocread -w -d DSK1: -b 0x800 -p Part02 0 0x5aa0000 Part02.raw - imgfs
pdocread -w -d DSK1: -b 0x800 0x19ac0000 OS.nb
-------------------------------------------------------------------------------------------------------------------------------------------------
dl link
http://rapidshare.com/files/304417770/EUUs_Acer_S200_23506_WWE.7z
Thanks to : Deadman2k, xplode, stark wong, cmonex, fabio and all other friends here
I hope this will be usful
How to flash :
1) Unzip using 7zip.
2) it works on vista and windows 7, but i recommend xp service pack 2 with net cf 20. sp2.0
3)Important step : After unzip, look for a text file called as verion.txt.Edit it as per your device version, and then flash.
4) Follow the instructions and wait for, finish.Allow EXT ROM to install, but one can stop it by pressing camera button.
Known Issues :
SMS Fix.cab is attached as well.PLs install, next release i will integrate it in ext rom
Pls report any other if u face.
TF3D can be installed externally and cab is available here on the forum.Pls search
Kitchen info :
I will also release my scripts, so that anyone can cook their own versions.Pls bear for 2-3days for that
-------------------------------------------------------------------------------------------------------------------------
kitchen info :
How to cook own versions :
I have some scrip of my batch files.Pls follow and make your own kitchen.Please note that, one has to use EXTReloc for reallocation of modules, from deadman2k.I also atach the procedure to use EXTReloc.
@ECHO Off
TOOLS\BuildOS.exe
pause
ECHO Reloc MOdules
EXTReloc.exe
pause
copy flash.bin temp\flash.bin
copy xip_out.bin temp\xip.bin
cd temp
..\TOOLS\osnbtool -sp flash.bin
..\TOOLS\osnbtool -sp flash.bin.bin.nb0
..\TOOLS\osnbtool -d flash.bin.bin.nb0.os.nb 2 imgfs.bin
..\TOOLS\imgfsfromdump imgfs.bin imgfs-new.bin
..\TOOLS\osnbtool -c flash.bin.bin.nb0.os.nb 2 imgfs-new.bin
..\TOOLS\osnbtool -c flash.bin.bin.nb0.os.nb.new 1 xip.bin
..\TOOLS\osnbtool -extra flash.bin.bin.nb0.os.nb.new.new
..\TOOLS\osnbtool -2bin flash.bin.bin.nb0.os.nb.new.new.exa 0x00121200 -cutheader
copy /b /y flash.bin.header+flash.bin.bin.nb0.os.nb.new.new.exa.bin flash_new.bin
pause
How to use EXT Reloc
Hello in first place in some folder with extreloc xipport and xip bit, make a old kitchen style
\oem
\rom
\rom\xip <--- to this folder place a flat xip dump, you can dump it trought dumprom, is need only for build registry
\sys
start packagetoolsbuildos from ervious, make with it flat dump (his create it in \temp\dump)
now you can need to make new xip, dump original and donor xip with xipport (press dump button, after this make pkg (in example in orig folder you got original xip in donor folder you got donor xip) make out folder, move to this folder all files and modules except MSxip* and you got somesing like that
\out\romhdr.txt
\out\parthdr.txt
\out\files\OEMXIPKernel\*.* <---files
\out\modules\OEMXIPKernel\*.* <--modules
now move all files and modules except OEM and romhdr.txt parthdr.txt from donor xip
after this in xipport press undo button to got flatdump of new xip
now start extreloc, goto setting page in imgfs path, point it to \temp\dump set apporitate nk.exe type (wm6.1 or wm6.5) all other setting you can use but default
now goto work page, press import xipport and xipport start, press ReallocV in extreloc, goto xipport and press realoc P, after this press write map in xipport, goto extreloc and dublclick on physlast number, press realloc nk.exe gsiir ... button, goto xipport and press realloc P again. xip ported
in extreloc drag the vertical white line to the left and press realloc imgfs, close extreloc
in xipport press Build xip_out.bin this is is new xip
use imgfsfromdump to make new imgfs from \temp\dump folder
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
How to dump/rebuild EXTROM.bin
Once again stark wong has created a wonderful tool to dump and he;lp us create our own ext rom.Attached is the link to programe
usage : f1extromtool extrom.bin -> dump the cabs and other files
f1extromtool /b extrom.bin [your version] -> builds the extrom.bin with the files in the extrom folder which u dumped recently
How to add replace cab file names for customisation
- AFter dumping EXTROM.bin, open the folder and look for the file " CABPIACB.pil"
- open it in hex editor and change the names by editing it.Save the file.Make a backup of original CABPIACB.pil in case to be used for making original EXTROM.bin
dl link : http://www.studiokuma.com/tools/?section=misc-e
That's good news. Can't wait to flash. I use to be a TouchPro flashaholic and now I feel sic
ohhhh!
doesn Acer allow flashing WWE roms on region specific devices? I have a german ROM so...btw. A German 6.5.1 would be tres sexy
anyhow, looks great, looking forward to enjoying your work!
Great, I can't wait till this comes out. Please keep us informed here
What is the expected release for this?
Woot nice to know il have custom roms for my acer f1 =], now you just need to port a leo rom with manila 2.6, shoulndt be that hard, since the xperia has leo roms, which is not a htc branded phone, just htc manufactured, ask one of the cookers over at xperia they should give you an idea, that is if you dont have the knowledge but from what i've seen that you have already ported and cooked a rom for the acer f1 i bet you do, anyways good luck mate.
rafyvitto
Looks awesome!!!
Nice to see a custom rom developing so quickly. Good work hdubli.
Looks wicked, congrats hdubli : )
wow....that's great..
thanks for the good work hdubli....
will you consider releasing a kitchen for neo touch? i want to cook a chinese version rom for neo touch.
That means you also have a Hard SPL for the F1 ??????
Can't wait the French version
hdubli, you are the man! can't wait. i was hoping this would happen. all we need is good hardware, and the great cookers will take care of the rest!
Damn! I just watch that again (with polarized glasses), and that is just a sweet program. Thanks for all the work. I can't wait to try it out!
I don't know if I can wait to try this out. I'm out of town most of next week, so I hope I have it to play with while I'm gone. If not, It better be ready by the time I get back ;p
Nice work, releasing kitchen would be a good step.
Thank you my friend, can't wait to flash your rom. Only one question:which version of manila do you use? Is it 2.1?
tsourisg said:
Thank you my friend, can't wait to flash your rom. Only one question:which version of manila do you use? Is it 2.1?
Click to expand...
Click to collapse
manila 2.5 90% working.Just trying 2.6 if i can.
hdubli said:
manila 2.5 90% working.Just trying 2.6 if i can.
Click to expand...
Click to collapse
Exciting news hdubli, keep up the good work
hdubli said:
manila 2.5 90% working.Just trying 2.6 if i can.
Click to expand...
Click to collapse
You are my hero
woa great news!
the current shipping roms are not available to reflash them if needed, right?
also, if you are willing to make a German ROM, I could do a romdump on mine, if you tell me what to do
it would be nice if we had original acer roms to flash if needed.
thanks a lot for your work, will donate 100%!
very true bommel. Having the orignal rom for waranty purposes is pretty important I believe.
From the video, i can see acer f1 can run manila 2.5.
i think your f1 should have an opengl drivers(ES 1.1? ES 2.0 ? ) for running.
i have search many post, but it seem f1 with original rom don't come with the drivers.
can you give me the drivers ?
btw the newer builds would also be great, like 23502.
hdubli, no paypal account for donations?
Hello everyone.
With the development of the New ROM, I decided to describe this and that.
-How to Prepare files and packages.
-How to create stable SYS and OEM.
-XIP Porting (Kernel) - if it succeeds.
-Build/Mod. BLDR/BOOT Section
-Change PagePool
-Etc
Small introduction:
Subject shows the structure of folding and unfolding ROM.
Everything described here are doing at your own risk.
I do not answer with any damage to the device.
Please read carefully and proceed with caution.
Topic applies only Toshiba devices Tsunagi: TG01
Execute Image System:
This step tutorial will be further developed.
Once, I'll add this feature in my kitchen.
Add OEM Apps:
OEM - This package is derived from the *. cab file.
It must include:
- The *. dsm guid the value of the name,
- The *. RGU with the same value in the name, it must be in Unicode encoding.
It must also be free, the last line in the content of the text.
- Application *. exe, *. dll, or library
- A shortcut to the program / library - if it is needed. It is not mandatory.
- Content may be more developed (in the files / programs)
Such a package can be easily added to the root of the OEM.
If, of course, is properly filed
Dependence of the Application, the memory devices.:
How can you distinguish the memory which will hit your application / library?
This differs from the rule:
- Module - that is, a file that looks like a directory goes to RAM.
- File - normal-looking, *. exe or *. dll file, going to Storage memory
Porting XIP (Kernel) and insert this file to Image System:
[TUT][UTIL]Remote Porting XIP
Working good in my kitchen for Toshiba TG01
XPR to LZX Compression:
Open the file os.nb.payload in HEX Editor. Find this Lines:
Code:
F8 AC 2C 9D E3 D4 2B 4D BD 30 91 6E D8 4F 31 DC ř¬,ťăÔ+M˝0‘nŘO1Ü
01 00 00 00 01 00 00 00 01 00 00 00 34 00 00 00 ............4...
08 00 00 00 00 02 00 00 00 10 00 00 58 50 52 00 ............XPR.
And change to:
Code:
F8 AC 2C 9D E3 D4 2B 4D BD 30 91 6E D8 4F 31 DC ř¬,ťăÔ+M˝0‘nŘO1Ü
01 00 00 00 01 00 00 00 01 00 00 00 34 00 00 00 ............4...
08 00 00 00 00 02 00 00 00 10 00 00 58 50 52 00 ............LZX.
Save this file. Get this library -> cecompr_nt.dll, then insert to TOOLS folder from your Kitchen ROM.
Download cecompr.dll and overwrite it in your XIP. Build XIP, build ROM, see results. Now Image System takes less memory.
Small Support
Changes PagePool:
Use PagePool Changer
Porting/build BLDR/BOOT and insert this file to Image System:
[UTIL][UPG] buildbldr
Build Image System:
This function, have a my Kitchen.
Ultra Kitchen Edition - ROM Builder for Toshiba TG01
Modyfications SYS Directory
Remove TimeBomb:
Open file *.rgu from location ->SYS/Shell/, and remove two keys from this registry:
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\DeviceBeta]
"Today"="Beta"
"Expiry"="Expires: %02d/%02d/%04d"
[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\DeviceBeta]
"About"="- BETA"
Now, Go to location -> SYS/Shell/, open file form module shell32.exe/S000 in HexEditor.
Search string 02 EB 7D 3E, and in both instances 7D change to BB.
from:
Code:
02 EB 7D 3E
to:
Code:
02 EB BB 3E
Remember, this sequence occurs twice
Thanks for Camelio
good idea, may be i'll try to understand something and build an italian version too, even if we are quit lucky with our tg01 'cause it's no brand at all.
Thanks for your great job with developement
Hey Nokser do you create wm6.1 rom for tg01?
Nokserze can you writa Polish version too?
here or in pdaclub forum, but I wont to understand anything, so it's more simple in our's language
Thanks for your job
Yes, of course
When you will to make this tourial? or you can write the tourial for stabil oem's now I want to make a rom but i can't create a stabil oem or a oem that's works... or you can tell me how i must put the oem.
Greats ALcAtRas
I give all my work in this, but first I must port WM6.5.5
Nokser, could we use the information you have gained about our device to port android?
Wm first, then we'll see Android
Nokser said:
Wm first, then we'll see Android
Click to expand...
Click to collapse
You think that is posible?There are a lot of people ho want that.
Everything is possible, but we shall see
Is this guide close to completion or has this been forgotten about?
I not forget.... I must gen. all options build structure ROM
Nokser said:
I not forget.... I must gen. all options build structure ROM
Click to expand...
Click to collapse
MAny of us are waiting for your light...
I know My friend
Small Update Thread
Nokser said:
Small Update Thread
Click to expand...
Click to collapse
Very good: I'm waiting for the next update impatiently. Do you know a good general tutorial, not device specific?
super_sonic said:
Very good: I'm waiting for the next update impatiently. Do you know a good general tutorial, not device specific?
Click to expand...
Click to collapse
You'll see ... if i end this tutorial
@Nokser:Can you help us to unlock t01a .It likes tg01 but it don't have code for unlocking .
Please...
Hello all,
I installed the CONROMv6 on my Verizon HTC Rezound. Everything went fine except that I was not able to receive SMS. Somewhere in google I found a solution: write some NV_stuff using cdmaware; didnt work. I also found in some HTC forum a kind of update that some HTC developer posted, I installed but didnt work either. Without finding a solution, I sitted my phone for a couple of days while taking care of my biz.
When I took my phone again, I realized that all the CDMA setting were gone. I tried to re-program the phone using QPST 2.7 366, but everytime I try to write to the phone, I receive an error saying "Roaming list file contains no data". I even tried to write some values at the time, but I keep receiving the same error or "NV_ACCOLC_I(0) NV_READONLY_S". I also tried to use CDMA Workshop to write the PRL file and even when it says it succeded, keep saying there is not PRL.
I cannot find the information about the solutions I tried for the SMS problem, and I am not sure about when the problem appeared, but I think I messed up with the NV stuff and i have not idea about how to fix it. Can anyone point me in the right direction? Does anyone have an NV backup that I can use for my phone?.
If you are S-OFF it is probably best to run the RUU for 4.3.605.2 and bring the phone back to stock, at least to get it working... Most of that stuff you were messing with is just bad news for 4G phones.
acejavelin said:
If you are S-OFF it is probably best to run the RUU for 4.3.605.2 and bring the phone back to stock, at least to get it working... Most of that stuff you were messing with is just bad news for 4G phones.
Click to expand...
Click to collapse
Thank you for your answer. I already flashed back to stock, but I guess that the NV_items are not modified by any ROM. Anyways, I am downloading the RUU you sugested to give it a try; will let you know.
acejavelin said:
If you are S-OFF it is probably best to run the RUU for 4.3.605.2 and bring the phone back to stock, at least to get it working... Most of that stuff you were messing with is just bad news for 4G phones.
Click to expand...
Click to collapse
Already tried with no avail. I flashed the latest RUU and did a factory reset after that, but still having the same problem. Any other ideas?
PortOS_76 said:
Already tried with no avail. I flashed the latest RUU and did a factory reset after that, but still having the same problem. Any other ideas?
Click to expand...
Click to collapse
switch the phone to cdma only. boot into recovery and wipe dalvik:
dial *22899
a popup should appear, then turn your 4g back on and test please.
synisterwolf said:
switch the phone to cdma only. boot into recovery and wipe dalvik:
dial *22899
a popup should appear, then turn your 4g back on and test please.
Click to expand...
Click to collapse
I followed your directions, but no popup appeared dialing *22899. Is there another way to turn the 4g back on?.
PortOS_76 said:
I followed your directions, but no popup appeared dialing *22899. Is there another way to turn the 4g back on?.
Click to expand...
Click to collapse
just turn it back on via the menu in mobile network
synisterwolf said:
just turn it back on via the menu in mobile network
Click to expand...
Click to collapse
I already did, but same problem, I cannot change the CDMA settings.
Found it! The file I wrote to my Rezound is the NV_Thunderbolt_Verizon.txt. Yes! I know this is a file for the Thunderbolt, but I dont know what I was thinking in that moment. The point is, can someone tell me if this is the source of the problem and what was the original values for this NV_Item?. The file content is the next:
[NV Items]
[Complete items - 1]
0855 (0x0357) - OK
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Also found the hotfix I used. Im afraid this is a hotfix for the Incredible, again the wrong device. Well, the hot fix is:
http://dl3.htc.com/misc/inc8049.apk
Any ideas?.
Well, let see.
You used CONROM on top of the latest ICS RUU leak? Con stopped supporting his ROM and it is not made for the latest ICS RUU leak.
You installed Thunderbolt and Incredible nvRam files on a Rezound phone?
You think installing things either not meant for your phone or not meant for your version of the operating system RUU were good ideas to try?
You installed something without researching first how to un-do it?
acejavelin: Yes, I used to think an RUU and factory reset will put everything back to normal. But, when I played with a T-Mobile SIM card (with 4.03.605.2) and ended up with a messed up Verizon APN, I discovered that the APN is stored in some unknown location where even an RUU and factory reset will not touch. I did manage to fix the Verizon APN problem. It is possible to really screw a phone up to the point that RUU will not fix it.
Anyway, I do hope someone has a solution to your phone's problems. I hope you realize now that installing things not meant for your phone or your version of the operating system is not a great idea. In the future, start with your phone on an RUU that the ROM is intended for, make a nandroid backup before installling the ROM, and if you don't like the ROM, then restore the nandroid backup to go back to stock.
Start with completely stock system - so everything matches and works together right.
Only install customized things that are meant for your phone and your version of the operating system RUU.
If you aren't sure, ask the author of whatever you are considering installing.
Think about: Do I really want and need what I am about to install? How risky is it? How will I be able to uninstall/undo it?
I don't intend this post to make you feel bad, it is more to make everyone else think a little.
P.S. You might try the LTE ON OFF app or HZUtils app to enter the hidden 4636 menu and select "CDMA+LTE/EvDo auto". But I wouldn't go experimenting as there are many options in hidden menus I do not understand. HZutils also has the ##778# hidden menu. You can also just dial ##778# to bring up the EPST menu with code 000000, but I wouldn't go changing things unless one understands it. Maybe you can compare your EPST values with those in someone's working Rezound phone. Then with a list of what the values are in a working phone, along with the list of what is stored in YOUR phone, you can cautiously change the EPST values in your phone?
The EPST hidden menu does have a submenu called PRL, so maybe this is something for you to investigate.
I know that I did something stupid by installing things that were not meant for my phone. Good news, I learned my lesson. About the solutions you proposed:
I cannot enter some of the hidden menus like ##4636#, however I was able to enter that menu using the tweaks app included in the ROM.
I also tried to enter to the ##778# menu, fortunatelly is working and i know how to modify every parameter in it. Unfortunatelly I cannot modify any of the options in the NAM Settings nor the PRL menus; they appear like in the View Mode.
Seems like all the NAM settings and PRL options are read only, how can this happened?.
I am out on a ledge, talking about PRL because I am not very knowledgeable about it.
I think PRL is updated by *228 for older phones and for the rezound it is via the SIM card.
http://www.verizonwireless.com/care/popups/prl.html
When the phone goes through a sim card activation, I think you get the PRL information into the phone.
Go to a Verizon store and talk them into giving you a replacement SIM card.
Maybe it dropped into the grass while changing your battery?
See if a new SIM card will set things right. Maybe also do a factory reset. If a new SIM card doesn't help, well it didn't cost you anything.
I already tried the *228 and nothing happens. As there is no PRL in the phone, it has no service, therefore, it cannot connect anywhere to update any data. About the Verizon simcard, the phone is not activated in Verizon, so I cannot ask for help from them.
I think the funny thing here is that all the NAM information is read only, while this must be writable in order to set the user information.
Have you tried writing the PRL with and without the SIM card installed? You could try using DFS to write some of your NV data too. I used workshop, Qpst, and DFS to program my Rezound on PagePlus.
I installed ConRom also and the stock RUU and only had to re-program the PRL, just so you know that the other settings shouldn't change after you get it going again. Cheers
Nam setting became write only
Looking for a solution to my problem I found this thread in which someone with a Droid has the same issues as me. I cannot use this solution as that folder is not present in my Rezound (this may be present only in Droids I guess). Any sugestions that may help me to write my NAM/PRL settings?
http://forum.xda-developers.com/showthread.php?t=651475
ckuke4 said:
Have you tried writing the PRL with and without the SIM card installed? You could try using DFS to write some of your NV data too. I used workshop, Qpst, and DFS to program my Rezound on PagePlus.
I installed ConRom also and the stock RUU and only had to re-program the PRL, just so you know that the other settings shouldn't change after you get it going again. Cheers
Click to expand...
Click to collapse
I already tried all of these programs, but, even when CDMA WS and DFS says that succeded to write the parameters, there is not cange on them.
PortOS_76 said:
Looking for a solution to my problem I found this thread in which someone with a Droid has the same issues as me. I cannot use this solution as that folder is not present in my Rezound (this may be present only in Droids I guess). Any sugestions that may help me to write my NAM/PRL settings?
http://forum.xda-developers.com/showthread.php?t=651475
Click to expand...
Click to collapse
The suggested solution was to remount the system partition as writable. ES File Explorer app can do that for you if you have root.
Also, that thread shows no feedback whether the proposed solution helped.
HowardZ said:
The suggested solution was to remount the system partition as writable. ES File Explorer app can do that for you if you have root.
Also, that thread shows no feedback whether the proposed solution helped.
Click to expand...
Click to collapse
That is why I would like to try to see if works, but I dont know how to remount the system partition in a Rezound (there is no mtdblock3 folder). Someone willing to give some help?
From terminal emulator app
su
mount -o remount,rw /dev/block/system /system
Be careful because until you remount it readonly or reboot your are capable of modifying or deleting important system files.
Hi
I just changed some stuff like images in a kernel using Android Kernel Kitchen 0.3.1.
Now I wanna test my changes.
My questions is->
What are worst case scenarios possible?
I am ready to go for boot loops and etc. but are there any consequences that may cause real hard brick of my phone? (Like---> it will never start again! or you need to take it to service center for repair!)?
Jaskaran498 said:
Hi
I just changed some stuff like images in a kernel using Android Kernel Kitchen 0.3.1.
Now I wanna test my changes.
My questions is->
What are worst case scenarios possible?
I am ready to go for boot loops and etc. but are there any consequences that may cause real hard brick of my phone? (Like---> it will never start again! or you need to take it to service center for repair!)?
Click to expand...
Click to collapse
What you can expect are boot loops, inability to get even see the boot splash, non-working wifi/ USB / touch / camera/ anything that needs a driver, random reboots. Personal experience: yesterday I was playing with changing part of the initramfs without changing the whole boot.img. It turns out that I needed to update the header size and checksum. Without this, it would hang for some seconds and then reboot (or not start at all). This was all fixable from recovery.
What can happen if you are not careful is a brick because you flash the wrong partition. Otherwise, you can always enter recovery mode and flash the kernel (for the i9300, it is mmcblk0p5). If you are not sure, look for the magic ANDROID! header:
Code:
# dd bs=64 count=1 if=/dev/block/mmcblk0p5 2>/dev/null | hexdump -C
00000000 41 4e 44 52 4f 49 44 21 80 bc 44 00 00 80 00 40 |[email protected]|
00000010 2e 1e 05 00 00 00 00 41 00 00 00 00 00 00 f0 40 |[email protected]|
00000020 00 01 00 40 00 08 00 00 00 00 00 00 00 00 00 00 |[email protected]|
00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000040
So, the absolute worst-case scenario is when you accidentally flash the wrong partition. If you picked your EFS partition and do not have a backup, then your IMEI and stuff are gone.
Note: be sure not to wipe your recovery partition (mmcblk0p6), that requires you restore the recovery using download mode (I have not experienced this yet).
Lekensteyn said:
What you can expect are boot loops, inability to get even see the boot splash, non-working wifi/ USB / touch / camera/ anything that needs a driver, random reboots. Personal experience: yesterday I was playing with changing part of the initramfs without changing the whole boot.img. It turns out that I needed to update the header size and checksum. Without this, it would hang for some seconds and then reboot (or not start at all). This was all fixable from recovery.
What can happen if you are not careful is a brick because you flash the wrong partition. Otherwise, you can always enter recovery mode and flash the kernel (for the i9300, it is mmcblk0p5). If you are not sure, look for the magic ANDROID! header:
Code:
# dd bs=64 count=1 if=/dev/block/mmcblk0p5 2>/dev/null | hexdump -C
00000000 41 4e 44 52 4f 49 44 21 80 bc 44 00 00 80 00 40 |[email protected]|
00000010 2e 1e 05 00 00 00 00 41 00 00 00 00 00 00 f0 40 |[email protected]|
00000020 00 01 00 40 00 08 00 00 00 00 00 00 00 00 00 00 |[email protected]|
00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000040
So, the absolute worst-case scenario is when you accidentally flash the wrong partition. If you picked your EFS partition and do not have a backup, then your IMEI and stuff are gone.
Note: be sure not to wipe your recovery partition (mmcblk0p6), that requires you restore the recovery using download mode (I have not experienced this yet).
Click to expand...
Click to collapse
Kk, thanks.
But what do i do if it does not start at all like u said (what i want is that it should at least be able start in recovery or download if possible).
Since its my first time messing with kernel, i am total n00b then
If it cannot proceed to the "normal" boot, then get into recovery by holding Volume Up + Power + Home for ten seconds while booting (I usually do that when I see the Samsung logo end release when it has restarted, showing the logo again (about ten seconds).
From there, use Install from zip (if you have a "update zip" that contains boot.img and some metadata) or (what I do) use adb push to put the image in /tmp/. Then use dd to write the boot image. Example (I use Linux):
Code:
laptop$ adb push boot-new.img /tmp/boot.img
laptop$ adb shell
# cat /tmp/boot.img > /dev/block/mmcblk0p5
Just in case of hardware failure, I also verify the md5sum:
Code:
laptop$ md5sum boot-new.img
laptop$ du -b boot-new.img # determine file size, say 1234
(android) # dd if=/dev/block/mmcblk0p5 bs=1234 count=1 | md5sum
The two outputs must match, otherwise something went wrong (unlikely, but still).
Lekensteyn said:
If it cannot proceed to the "normal" boot, then get into recovery by holding Volume Up + Power + Home for ten seconds while booting (I usually do that when I see the Samsung logo end release when it has restarted, showing the logo again (about ten seconds).
From there, use Install from zip (if you have a "update zip" that contains boot.img and some metadata) or (what I do) use adb push to put the image in /tmp/. Then use dd to write the boot image. Example (I use Linux):
Code:
laptop$ adb push boot-new.img /tmp/boot.img
laptop$ adb shell
# cat /tmp/boot.img > /dev/block/mmcblk0p5
Just in case of hardware failure, I also verify the md5sum:
Code:
laptop$ md5sum boot-new.img
laptop$ du -b boot-new.img # determine file size, say 1234
(android) # dd if=/dev/block/mmcblk0p5 bs=1234 count=1 | md5sum
The two outputs must match, otherwise something went wrong (unlikely, but still).
Click to expand...
Click to collapse
I know all this but what i m saying is that can there be conditions where neither i will be able to boot recovery nor download (even by volume+power+home method)?
Unless you do really stupid things like overwriting /dev/block/mmcblk0 or other partitions on http://cleanimport.xda/index.php?threads/2362743/, you will be safe.
Jaskaran498 said:
I know all this but what i m saying is that can there be conditions where neither i will be able to boot recovery nor download (even by volume+power+home method)?
Click to expand...
Click to collapse
Recovery has it's own kernel. It doesn't use the one you're modifying
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit