Related
Hi,
I ran doctest on my prophet which ended up corrupting the doc. I managed to get the doc fixed except for binary partition 1. Now I have a prophet which boots into the OS, but has a corrupt CID, IMEI, SIMLOCK, GSMDATA, etc- which means my prophet is now a PDA without a phone...
In short, 0x0-0x44000 area on binary partition 1 is corrupt and I don't have a backup of it.
Can a dump of this block from another prophet be used directly on my device? What all would have to be reconstructed in this block to make it run successfully on my device?
Pls help!
slickdick said:
Hi,
I ran doctest on my prophet which ended up corrupting the doc. I managed to get the doc fixed except for binary partition 1. Now I have a prophet which boots into the OS, but has a corrupt CID, IMEI, SIMLOCK, GSMDATA, etc- which means my prophet is now a PDA without a phone...
In short, 0x0-0x44000 area on binary partition 1 is corrupt and I don't have a backup of it.
Can a dump of this block from another prophet be used directly on my device? What all would have to be reconstructed in this block to make it run successfully on my device?
Pls help!
Click to expand...
Click to collapse
for people reading this, DO NOT RUN DOCTEST ! EVER !
for sidekick, what do you have ? G3/G4?
if you have a G3 it should be possible to fix with itsme tools if you know what you are doing.
I have a G3 IPL 1.0 SPL 2.15.0000 (+gold card)
I have managed to get 0x00000-0x10000 from a wizard (cid locked/sim unlocked). Updated it with superCID using typhooncidedit.pl and flashed it on my doc using pdocwrite.
However, I am still getting a "GetDeviceCID: Error - InitDecoder" on running 'info 2', IMEI is still the default 44xxxx... and am getting Simlock.exe error-"Data error: contact service....." on inserting a SIM
I can think of the following three reasons why this hasn't worked for me:
1. wizard and prophet have different CID blocks and one from prophet might work
2. CID block contains a unique device specific identifier (docuniqueid maybe) apart from what is not mentioned in typhooncidedit.pl
# 0x0000-0x0004 - version
# 0x0010-0x0018 - checksum cryptkey
# 0x0140-0x0148 - imei
# 0x0160-0x0180 - cid
# 0x01a0-0x01a8 - keyindex at byte +3
# 0x1200-0x1a00 - cid cryptkey
# 0x1c80-0x1c88 - lockflag
# 0x1d00-0x1f00 - lockcodes
# 0x4000-0x4400 - mccmnc ??
# 0xfff8-0xffff - checksum of 0-0xfff8
3. the device looks at information in 0x10000-0x40000 at least for IMEI & simlock
Am I on the right track or are there any easier alternatives? Either ways, I think it is important for me to get 0x00000-0x44000 of a G3 prophet in order to investigate further.
It would of GREEEAAAT help if someone can provide me a dump of this area
pdocread -n 1 0 0x40000 cidblock.bin
pdocread -n 1 0x40000 0x4000 -b 0x4000 gsmdata.bin
(pls also mention your docuniqueid from 'pdocread -l')
slickdick said:
I have a G3 IPL 1.0 SPL 2.15.0000 (+gold card)
I have managed to get 0x00000-0x10000 from a wizard (cid locked/sim unlocked). Updated it with superCID using typhooncidedit.pl and flashed it on my doc using pdocwrite.
However, I am still getting a "GetDeviceCID: Error - InitDecoder" on running 'info 2', IMEI is still the default 44xxxx... and am getting Simlock.exe error-"Data error: contact service....." on inserting a SIM
I can think of the following three reasons why this hasn't worked for me:
1. wizard and prophet have different CID blocks and one from prophet might work
2. CID block contains a unique device specific identifier (docuniqueid maybe) apart from what is not mentioned in typhooncidedit.pl
# 0x0000-0x0004 - version
# 0x0010-0x0018 - checksum cryptkey
# 0x0140-0x0148 - imei
# 0x0160-0x0180 - cid
# 0x01a0-0x01a8 - keyindex at byte +3
# 0x1200-0x1a00 - cid cryptkey
# 0x1c80-0x1c88 - lockflag
# 0x1d00-0x1f00 - lockcodes
# 0x4000-0x4400 - mccmnc ??
# 0xfff8-0xffff - checksum of 0-0xfff8
3. the device looks at information in 0x10000-0x40000 at least for IMEI & simlock
Am I on the right track or are there any easier alternatives? Either ways, I think it is important for me to get 0x00000-0x44000 of a G3 prophet in order to investigate further.
It would of GREEEAAAT help if someone can provide me a dump of this area
pdocread -n 1 0 0x40000 cidblock.bin
pdocread -n 1 0x40000 0x4000 -b 0x4000 gsmdata.bin
(pls also mention your docuniqueid from 'pdocread -l')
Click to expand...
Click to collapse
you are on the right track, as you have a G3 it should be possible to fix as pdocwrite can write a G3 DOC
as you can see from my signature, my G3 is bricked so I can't help at the moment
however, I see you have a gold card !? care to explain how you made it ?
Thanks
Prophet Goldcard
I just followed the instructions in typhoonnbfdecode.pl with slight modifications to some checks in IPL & OS
you have a bricked G3.... stuck in bootloader I presume? There are two ways you can fix it with the help of a gold card.
1. Cardid is known and docuniqueid is not known
use tornado keys and xxx magic and '00' as first two chars in cardid to generate a securitylevel=0 non-flashable sd image.
>perl typhoonnbfdecode.pl -d prophet_gold.img -p magic=xxx -p cardid=00610032DF69A01947323044534D5402 -p keys=tornado -p seclevel=0
using this card I get a the normal bootloader screen but with a security level of 0
Cmd>set 32 0
+ SD Controller init
- SD Controller init
+StorageInit
***** user area size = 0x7AC00000 Bytes
Unlimited time!
GetDeviceCID: Error - InitDecoder <<<<< due to corrupt bin partition 1
g_cKeyCardSecurityLevel = 0 <<<<< Voila!
now use the l or lr command in bootloader!!!
2. both Cardid and and docuniqueid are known
use tornado keys and '00' as first two chars in cardid to generate a flashable sd image.
however, for this to work, comment out all the checks in validate_os and the BIPO check in validate_ipl in typhoonnbfdecode.pl
>perl typhoonnbfdecode.pl -d sd80.img -p cardid=00610032DF69A01947323044534D5402 -p keys=tornado -p seclevel=0 -p docuniqueid=00000000a440020420380318130b0571 -r os=OS.nb
no more "Not Allow Update" 's
I'm so busy now in the college exams, this is my graduation year, and I only look at the posts like checking my mail without replying.
But at least I find a guy understand what he is doing, and has no ego, and polite, not like others in this very impolite, and the problem they are stupid, and think themselves understand, all what they do, reading and repeating without understanding or try to improve.
After this long story you don't have to read it, trying to help you if I can.
About the IMEI block => try to use IMEI wizard for changing the IMEI for prophet it will overwrite the old block. It uses pdocwrite.exe =pdocread.exe
About the other blocks I have a G3 prophet IPL 2.10 SPL 2.20 and I have back up with r2sd all and unlocked CID.
I'll pdocread any block you want but I'm going to send it by e-mail in parts, because I can't guarantee the net in big files, so just read your private messages.
slickdick said:
I just followed the instructions in typhoonnbfdecode.pl with slight modifications to some checks in IPL & OS
you have a bricked G3.... stuck in bootloader I presume? There are two ways you can fix it with the help of a gold card.
1. Cardid is known and docuniqueid is not known
use tornado keys and xxx magic and '00' as first two chars in cardid to generate a securitylevel=0 non-flashable sd image.
>perl typhoonnbfdecode.pl -d prophet_gold.img -p magic=xxx -p cardid=00610032DF69A01947323044534D5402 -p keys=tornado -p seclevel=0
using this card I get a the normal bootloader screen but with a security level of 0
Cmd>set 32 0
+ SD Controller init
- SD Controller init
+StorageInit
***** user area size = 0x7AC00000 Bytes
Unlimited time!
GetDeviceCID: Error - InitDecoder <<<<< due to corrupt bin partition 1
g_cKeyCardSecurityLevel = 0 <<<<< Voila!
now use the l or lr command in bootloader!!!
2. both Cardid and and docuniqueid are known
use tornado keys and '00' as first two chars in cardid to generate a flashable sd image.
however, for this to work, comment out all the checks in validate_os and the BIPO check in validate_ipl in typhoonnbfdecode.pl
>perl typhoonnbfdecode.pl -d sd80.img -p cardid=00610032DF69A01947323044534D5402 -p keys=tornado -p seclevel=0 -p docuniqueid=00000000a440020420380318130b0571 -r os=OS.nb
no more "Not Allow Update" 's
Click to expand...
Click to collapse
Create, Let me try some things here, In my gold card thread I've started outlining this.
I used the same steps as you did, however I got stuck in getting the cardid, for some reason the memdump didnt contain the cardid.
which route did you use to get the cardid ?
(I used my second prophet to get that, but failed)
Thanks for the explaining so far.
paradis_pal said:
I'm so busy now in the college exams, this is my graduation year, and I only look at the posts like checking my mail without replying.
But at least I find a guy understand what he is doing, and has no ego, and polite, not like others in this very impolite, and the problem they are stupid, and think themselves understand, all what they do, reading and repeating without understanding or try to improve.
After this long story you don't have to read it, trying to help you if I can.
About the IMEI block => try to use IMEI wizard for changing the IMEI for prophet it will overwrite the old block. It uses pdocwrite.exe =pdocread.exe
About the other blocks I have a G3 prophet IPL 2.10 SPL 2.20 and I have back up with r2sd all and unlocked CID.
I'll pdocread any block you want but I'm going to send it by e-mail in parts, because I can't guarantee the net in big files, so just read your private messages.
Click to expand...
Click to collapse
Nice to see you back on the board, I've read some of your early posts and they were a great help !
If you could help out that would be great, I know what it is like during exams
Id would be great if you guys could help me find the cardid, I'm trying to get this, but im guessing i'm looking at the wrong section:
Using memmap on my G4 i've dumped the memory section of device.exe
pmemmap -s 0x06000000 -w deviceexe.mem -p 0x10000000-0x12000000
However when searching through it, I can't find the SBDS/ Memory Card section, only a RSDS section at 0x1101C.
Am I dumping the wrong section ?
try to search for memory card using unicode character set ((winhex)), because it's writtin in unicode
I'm not sure, if you are using any other ROM but try to use original qteck s200 rom 2.20 without insalling anyother programs, and try again without installing the ext rom,
try any debuger manger to find out the memory section of device.exe cause it is not always 0x06000000
paradis_pal said:
try to search for memory card using unicode character set ((winhex)), because it's writtin in unicode
I'm not sure, if you are using any other ROM but try to use original qteck s200 rom 2.20 without insalling anyother programs, and try again without installing the ext rom,
try any debuger manger to find out the memory section of device.exe cause it is not always 0x06000000
Click to expand...
Click to collapse
Thanks for the advice, I did use winhex in unicode, I will try with the qtek rom,I will post an update soon, getting my card reader at work now
hope your exams are going ok !
How to find Cardid on Prophet
For CardID, on my G3, I did not find the SBDS signature in the memory dump of device.exe. However, there were two occurances of Unicode "Memory Card". 73 (0x49) bytes after one of them was what I could recognize as the cardid.
From what I can make of the codes (ASCII) mentioned in typoonnbfdecode.pl
'UE...c.U821DSDS.' for minisd
'[email protected]' for kingston
'?<.e.Gd.821DSMT.' for daneelec
All three have 821, which is reverse of 128!!! size 128MB!!! Ring-a-bell?!? Can we interpret similar structure for all other cards < 1GB?
'DSMT' seems to be standard for Dane Elec cards. same can be interpreted for other types like DSDS looks to be standard(maybe somone can confirm this)
If you analyze the ASCII of card id of my 2GB Dane Elec- '%a.2ßi..G20DSMT.'
you will see 'G20' representing size (representation for size seems to be different for cards > 1G. Again, someone needs to confirm this observation) and 'DSMT' standard signature for Dane Elec.
All in all, if you are not able to find the 'Memory Card' pattern, depending upon card make and size, search for any of the CardID ASCII patterns in the memory dump.
(btw, To find the starting offset of CardId- third character of CardId seems to be 0x00. If you are familiar with using grep, finding cardid in the memory dump could be easier)
Let me know if this helps.
Reverse of cardids is shown below:
minisd in typoonnbfdecode.pl
03 53 44 53 44 31 32 38 55 00 63 CF AC 00 45 55 SDSD128U cϬ EU
kingston in typoonnbfdecode.pl
18 49 4E 31 32 38 4D 42 03 40 1F 53 09 00 51 3F IN128MB @ S Q?
Dane Elec in typoonnbfdecode.pl
02 54 4D 53 44 31 32 38 07 64 47 BA 65 00 3C 3F TMSD128 dGºe <?
and finally my 2GB Dane elec
02 54 4D 53 44 30 32 47 19 A0 69 DF 32 00 61 25 TMSD02G *iß2 a%
Makes sense? I think you can directly search for the cardid pattern in the memory dump.
slickdick said:
Reverse of cardids is shown below:
minisd in typoonnbfdecode.pl
03 53 44 53 44 31 32 38 55 00 63 CF AC 00 45 55 SDSD128U cϬ EU
kingston in typoonnbfdecode.pl
18 49 4E 31 32 38 4D 42 03 40 1F 53 09 00 51 3F IN128MB @ S Q?
Dane Elec in typoonnbfdecode.pl
02 54 4D 53 44 31 32 38 07 64 47 BA 65 00 3C 3F TMSD128 dGºe <?
and finally my 2GB Dane elec
02 54 4D 53 44 30 32 47 19 A0 69 DF 32 00 61 25 TMSD02G *iß2 a%
Makes sense? I think you can directly search for the cardid pattern in the memory dump.
Click to expand...
Click to collapse
Great ! thanks, I'm dumping right now, after looking for the memory adress of device.exe using pps
will update in a moment
uhmm, I think we have a winner ??
at 00729EC0
23 61 00 3D 92 68 10 80 32 31 35 52 53 44 53 03
#a.=’h.€215RSDS.
for a 512 MB sandisk sd card
created the image, I now have sec level 0.
I've downloaded mtty and want to upload a new SPL using the L or LR command, however I don't know what parameters L or LR takes ?
is it just L <filename>
or do I have to specify the memory adress or the SPL ?
Jesterz said:
is it just L <filename>
or do I have to specify the memory adress or the SPL ?
Click to expand...
Click to collapse
Code:
l <path_name> <startAddr offset>
You have to specify the address of the SPL, if you don't specify it most probably will default to OS address.
pof said:
Code:
l <path_name> <startAddr offset>
You have to specify the address of the SPL, if you don't specify it most probably will default to OS address.
Click to expand...
Click to collapse
ok thanks ! i'm going to give this a go
l spl.nb 0x91000000
fingers crossed, lol
Cmd>l spl.nb 91000000
clean up the image temp buffer at 0x8C100000 Length 0x03900000
BOOTLOAD_PAGE_TABLE_BASE_C_VIRTUAL= 0x8C080000
Clear image temp buffer done .
MTTYDownloadImage "spl.nb"
:F=spl.nb
start download
SAddress A0000000h Length 000C0000h, pszImageTempBuffer = 8C100H000h
OEMGetFlashIndex()- dwVaddr = 0xA0000000
OEMGetFlashIndex()- iIndex = 0xFFFFFFFF
Start flashing new image!!!
<CE-31><CE-1167><CE-995>
weird, the screen then goes all white, and I hear the usb disconnect, for the rest nothing happens.
which format does the spl file need to be ? i've used the "standard" nb file
i'm trying more stuff, but right now, i'm clueless
Jesterz said:
BOOTLOAD_PAGE_TABLE_BASE_C_VIRTUAL= 0x8C080000
Click to expand...
Click to collapse
This seems good, as it is the virtual address from where the bootloader expects to be executed.
Jesterz said:
weird, the screen then goes all white, and I hear the usb disconnect, for the rest nothing happens.
Click to expand...
Click to collapse
Weird... I believe command "l" auto-launches code once downloaded, probably this is the reason.
Jesterz said:
which format does the spl file need to be ? i've used the "standard" nb file
Click to expand...
Click to collapse
I think it should be a BIN file with "l" command... maybe try "lnb" command? (I don't know if prophet has it, I don't have a prophet). Hope the previous "l" command hasn't screewed things more than they where.
Just out of curiosity, tell me how the story ends
pof said:
I think it should be a BIN file with "l" command... maybe try "lnb" command? (I don't know if prophet has it, I don't have a prophet). Hope the previous "l" command hasn't screewed things more than they where.
Just out of curiosity, tell me how the story ends
Click to expand...
Click to collapse
as far as i know, "l" is for .bin only (at least on wizard)... I hope Jesterz did not just nuke his bootloader.
ok so ive been messing with the partitions of the phone for a little while messing things up quite a bit (supprized i havent bricked yet lol)
so the screen shot is the default way the partitions are set.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i've tried deleting partition 2 & 3 using
Code:
rm 2
rm 3
then i try to make the partitions like
Code:
mkpartfs primary ext4 538 5638 userdata
mkpartfs primary fat32 5638 15.9GB media
i get errors and then my storage isnt accessable so i re root with one click and try agian.
what im trying to do is make internal storage around 5GBs
can anyone help me out with this?
it has to be possible i've read that the whole 16gbs of the phone is all the same chip so it has to be possible to partition it differentlly and i think #1 is the like were CWM is so i dont want to risk deleting that partition without knowing exactally what im doing.
any help would be appreciated
links tips anything
thanks
I don't know if it's possible but it would be really interesting if it would.
I'm having issues replicating your situation which makes it hard to help you profoundly, which errors are you getting?
And, wouldn't it be better to use mkpart instead of mkpartfs?
Greetz
well im new to SDK and tools like this is the first thing ive tried with it im not familliar with all the commands and stuff. but im about to mess with some more stuff and ill try your suggestion
i may be new to android but im not new to computers, i learn quickly and this is the first thing i need to get going before i move forward
were can i get commands and stuff for trying this
facts i know -
the whole 16 gb's of the phones memory is 1 chip, partitioned (by default into 3 partitions)
though not specifically specified -
1. system (i assume recovery and stuff thats not safe to mess with)
2. internal memory (app contacts ect..)
3. external memory (sd card)
since its all one 16gb chip it is possible to re-partition it IE
without messing with option 1
say combine 2 & 3 or make 2 (internal) bigger and 3 (sdcard) smaller
i just need to learn the proper commands and once i have figured this out i will share
the reason i want this -
being able to have say 5 gbs of internal storage, will ensure i will never run out of space for apps games and what not that leave aprox. 10 gbs left for sd card
wich is MORE then enough for my music pictures docs and whatnot
and thus doing this i wouldnt have to move apps to sd with say apps 2 sd or anything and it would leave my external storage cleaner not putting a bunch of misc folders on it
this is getting pretty long so ill wrap it up for now
these are the only 2 things remotely close to what im trying to do
http://androidandme.com/2009/08/news/how-to-manually-partition-your-sd-card-for-android-apps2sd/
&
http://www.simplehelp.net/2009/09/28/how-to-partition-your-androids-sd-card-to-install-apps-on-it/
in simple easy to understand terms what im trying to accomplish is
(refer to pic in 1st post)
1. delete 2 and 3
2. remake 2 so its along the lines of
Code:
2 538MB 5868MB ????MB ext4 userdata
3. and 3 like...
Code:
3 5868MB 15.9GB 10??GB fat32 media
so i need to delete ext4 userdata and fat32 media and re create them with my own defined storage
abd messed up with the sdk update so im done for the night hurting my head trying to get this working so ill be back on it tomorrow, please any help or refrence would be appreciated
Alright so after a few hours of trying I managed to resize all the partitions using Parted. However, it seems that either Android is recreating the partitions or that the internal memory values aren't being read correctly in Android itself.
Know that the first partition contains your system files (ROM, kernel). The second partitions is the /data folder which is basically what is removed when you do a factory reset.
The parted output (after several commando's) is the following (PS: I would've resized my pictures if it wasn't 5AM, sorry):
Unfortunately my Android shows this:
And after a reboot, parted does this:
So now basically I'm not sure if my internal memory has been altered to 2GB and that the Android readings are wrong, or that Android has a safe mechanism and reverts these changes after reboot. Someone with more insight needs to answer that question. I'm leaning towards the latter, unfortunately. Maybe there's a flag somewhere that has be changed (if it were that simple).
Tips to you; make sure you are in your recovery mode when using parted, otherwise you won't be able to access the partitions.
Use (in parted)
resize 3 2612MB 15.9GB - to resize your third partition and shrink it with 1GB
rm 2 - to remove secondary partition (parted can't access ext4)
mkpartfs 2 primary ext2 538 2612 - to make the secondary partition (= internal memory?) 2GB.
Then quit parted and upgrade your ext2 to ext3 and then ext4.
ext2 - ext3:
Code:
tune2fs -j /dev/block/mmcblk0p2
ext3 - ext4
Code:
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p2
e2fsck -fpDC0 /dev/block/mmcblk0p2
Check parted again and you'll see your updated info... until the next reboot.
Anyone else willing to share some knowledge?
Greetz
maybe this will help you figure it out.. http://androidcommunity.com/forums/...egarding-cupcake-21347/index9.html#post223974
its a post i made on androidcommunity.com 2years and 3 months ago for partitioning an sd card, in the G1, through the recovery(there was a terminal included in the recovery then) of the phone. maybe itll help you put this puzzle together with some hints. good luck!
well its progress, atleast were getting somewere. i have a few things to do firste then i have to get my adb working agian and ill get right back on this,
so you were able to resize it but theres a safty precaution prenting it from applying upon reset? hmm ok ill check that out ill do your method above just give me a little while to get around to it.
oh and should i boot into ubuntu doing this? or is windows ok?
You can continue using Windows. If you run "adb shell", adb 'connects' to the shell of your device anyway (which is Linux-based).
If your adb isn't working, make sure you're not in the bootloader menu because that's fastboot. Being in the recovery is the ideal environment to mess around with your phone.
Maybe the fat32 partition (sdcard) has to be removed as well, I just resized it because I figured that since it exists already, it shouldn't be deleted.
Good luck and keep me/us updated
Greetz
Alright a small addition;
Unfortunately I need my phone tonight and tomorrow so I can't mess around with it, so I'll leave you some things to look at and maybe they can help us further.
I've been digging through the filesystem and found partition specification files in /sys/block/mmcblk0/ and sys/devices/mmcblk0. It are directories that contain the classification of devices.
I pulled them to take a closer look and what I found was rather interesting.
It contains 3 folders, one for each partition. Inside those folders are the specifications for the partition. Let me tell you that I'm not sure how Android treats these files (ergo; are they static and loaded on reboot, causing the revert of the partitions - or dynamic and created somehow else).
Here's a quick rundown of the files, I'll use mmcblk0p2 because that's the internal memory, same logic applies to mmcblk0p1 and 3:
Code:
-r--r--r-- 1 root root 4096 Oct 22 18:52 alignment_offset
-r--r--r-- 1 root root 4096 Oct 22 18:52 dev
-r--r--r-- 1 root root 4096 Oct 22 18:52 discard_alignment
drwxr-xr-x 2 root root 0 Oct 22 18:52 holders
-r--r--r-- 1 root root 4096 Oct 22 18:52 inflight
-r--r--r-- 1 root root 4096 Oct 22 18:52 partition
-r--r--r-- 1 root root 4096 Oct 22 18:52 partition_name
drwxr-xr-x 2 root root 0 Oct 22 18:52 power
-r--r--r-- 1 root root 4096 Oct 22 18:52 size
-r--r--r-- 1 root root 4096 Oct 22 18:52 start
-r--r--r-- 1 root root 4096 Oct 22 18:52 stat
lrwxrwxrwx 1 root root 0 Oct 22 18:52 subsystem -> ../../../../../../../../../class/block
-rw-r--r-- 1 root root 4096 Oct 22 18:52 uevent
There's a start and size file. The size file contents are:
2097152
2097152 is equal to 1GB, it is the sector size. Multiplying this value by 2 would set the size to 2GB.
If that is done, I would assume that the value mmcblk0p3/start has to be shifted by 2097152 and the size reduced by 2097152, if that makes sense to you.
There's also a weird symlink to a subsystem, /class/block, of which I can list and cat its contents but I have no idea how to access it properly, can't cp it either. Looks like Android protects this area somehow. Basically it contains copies (or originals?!!) of the files in /sys/block.
I know that in the Linux kernel all three classification directories (sys/block, sys/class, sys/bus) are merged into one place at /sys/subsystem, following the layout of the bus directories. All buses and classes, including the converted block subsystem, will show up there. But unfortunately my knowledge of the Android kernel is far too limited to know what exactly is going on.
So maybe changing the contents of all these files and then using parted to partition the partitions, making them exactly the same as the values that these files imply, could make the changes the the internal memory stick.
Once again, if anyone has another idea, please let us know.
Greetz
well ive done alot of messing around to no avail anyone have any useful info on this matter?
On the Hero we would use firerat mod. It required a change to recovery for it to work as well as a change to the boot partition. I'm not sure what phone it was developed under but there should be a thread/link in the hero cdma section. Not sure if it will help, but it's purpose was to allocate cache to system for the same purpose on phones without much internal storage.
Sent from my Nexus S 4G
dpeeps74 said:
On the Hero we would use firerat mod. It required a change to recovery for it to work as well as a change to the boot partition. I'm not sure what phone it was developed under but there should be a thread/link in the hero cdma section. Not sure if it will help, but it's purpose was to allocate cache to system for the same purpose on phones without much internal storage.
Sent from my Nexus S 4G
Click to expand...
Click to collapse
https://github.com/Firerat/CustomMTD
I found that too, will that work for the Nexus S internal NAND memory though?
If yes, it'll be awfully simple to implement what we're trying to achieve.
Greetz
You just have to go through the source and make it all nexus-s-specific. It should work once all the specs are changed to our partitions and such
I'll look into that next week, should be possible.
Thanks,
Greetz
so this might be possible with that old method?
you guys figure anything out?
bump - any progress?
Below is a guide on how to Create your own custom ODIN packages.
You will need:
-Terminal emulator app
-linux computer or Cygwin for windows or shell command line
-ODIN program
-create folder on your external sd card named "backup"
-if you want backup to go on your internal SD card you will change the code line to mnt/sdcard/backup/.........
HOW TO:
- In the terminal emulator app on your phone enter the code line for the item you want a dump of and this code will make an image on your sdcard.
**NOTE** performing a system dump will take 5 minutes to execute as the system file is in the 1 to 1.5 gig range. BE PATIENT!!!
- Once you have the image files that you need then proceed to the shell command line below to package your ODIN bundle.
-You will want to copy all of these image files over to your computer for easier bundling from your command line.
SYSTEM
Code:
dd if=/dev/block/mmcblk0p14 of=/mnt/extSdCard/backup/mmcblk0p14_system.img bs=4096
RECOVERY
Code:
dd if=/dev/block/mmcblk0p18 of=/mnt/extSdCard/backup/mmcblk0p18_recovery.img bs=4096
USER DATA
Code:
dd if=/dev/block/mmcblk0p15 of=/mnt/extSdCard/backup/mmcblk0p15_userdata.img bs=4096
CDMA MODEM
Code:
dd if=/dev/block/mmcblk0p1 of=/mnt/extSdCard/backup/mmcblk0p1_modem.img bs=4096
LTE_MODEM
Code:
dd if=/dev/block/mmcblk0p12 of=/mnt/extSdCard/backup/mmcblk0p12_modemst1.img bs=4096
LTE_MODEM2
Code:
dd if=/dev/block/mmcblk0p13 of=/mnt/extSdCard/backup/mmcblk0p13_modemst2.img bs=4096
CACHE
Code:
dd if=/dev/block/mmcblk0p17 of=/mnt/extSdCard/backup/mmcblk0p17_cache.img bs=4096
BOOT
Code:
dd if=/dev/block/mmcblk0p7 of=/mnt/extSdCard/backup/mmcblk0p7_boot.img bs=4096
How to package into a flashable ODIN package:
From a terminal command line:
Code:
tar -H ustar -c "INSERT_.IMG FILE HERE" mmcblk0p14_system.img > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
Add any combination of image files you want after the "-c" and before the ">"
Make sure each .IMG file has a space between the next one.
DISCLAIMERS
1. I am not responsible if you brick your phone using these system dumps.
2. Do not monkey around with BOOT or MODEMS unless you are really sure what you are doing
3. Always make sure you package your ODIN bundles with a .Md5 checksum to prevent corrupted data dumps from screwing your phone up.
4. Stay away from flashing .tar only files as these will flash no matter what and have no error checking
5. If you plan to package ODIN bundles for distribution of your ROM, only package SYSTEM, RECOVERY, etc etc. Do not package USER DATA or CACHE for distrobution as this could contain your personal information. Only package CACHE and USER DATA if this is a personal backup or you know what you are doing.
6. Flashing ODIN packages without a samsung signature will increase your flash counter. The refurbishing companies that work with AT&T, Verizon, and T-mobile all use the same company in coppell TX and they do not check for the flash counter. Only Samsung does. Most phones are disassembled before they even go to Samsung and once the phone makes it there they bill the carrier back for the phone and not the customer. (Trust me, I run a warranty center for one of the big 4 carriers) This comes directly from senior personnell from Samsung.
I can't believe someone rated this post a 1 star.... really? I thought this was very useful. lol. If you think its useful don't hesitate to give it an appropriate star rating. Thanks
So I can basically capture everything needed to odin my phone back to whatever point I am at when I dump all the files?!? Basically a way to create a restore point that I can flash from my pc. Sounds like a winner to me.
Jiggity Janx said:
So I can basically capture everything needed to odin my phone back to whatever point I am at when I dump all the files?!? Basically a way to create a restore point that I can flash from my pc. Sounds like a winner to me.
Click to expand...
Click to collapse
Absolutely!
Sent from my SCH-I535 using xda app-developers app
this is awesome, Thanks for the write up!
I'm new to Samsung, when I want to flash lets say user data.... am I still selecting "PDA" from the Files section? Like I did for the root access? Or does "PDA" do the system?
tprouty said:
this is awesome, Thanks for the write up!
I'm new to Samsung, when I want to flash lets say user data.... am I still selecting "PDA" from the Files section? Like I did for the root access? Or does "PDA" do the system?
Click to expand...
Click to collapse
Just remember... always use PDA.
Sent from my SCH-I535 using xda app-developers app
Very good write up.. Voted 5 stars and sent 'Thanks'..
Hypnosis4U2NV said:
Very good write up.. Voted 5 stars and sent 'Thanks'..
Click to expand...
Click to collapse
Thank you sir!
A couple of questions.
1. Can these Odin packages be used in Heimdall as well? (I assume so since they're both pretty straight forward, but ya never know...)
2. How well, if at all, do these instructions translate over to other devices?
ChromWolf said:
A couple of questions.
1. Can these Odin packages be used in Heimdall as well? (I assume so since they're both pretty straight forward, but ya never know...)
2. How well, if at all, do these instructions translate over to other devices?
Click to expand...
Click to collapse
Yes in heimdall.
Translates perfectly except each phone has different partition block locations
Sent from my SCH-I535 using xda app-developers app
das7982 said:
Yes in heimdall.
Translates perfectly except each phone has different partition block locations
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
thanks for the write up great read, but i have a problem im stuck at the 4g lte screen and nothing is working i odin to stock then to stock rooted and back to stock but still stuck at the screen can anyone help please
Great info, thank you....STARS ADDED!
Man I should have done this before I flashed a recovery on my updated SGS3. Either way, very nice write-up and thank you!
Marcismo55 said:
Man I should have done this before I flashed a recovery on my updated SGS3. Either way, very nice write-up and thank you!
Click to expand...
Click to collapse
Thanks
Sent from my SCH-I535 using Tapatalk 2
cleblanc92 said:
Great info, thank you....STARS ADDED!
Click to expand...
Click to collapse
Thank you!
Sent from my SCH-I535 using Tapatalk 2
Reference Partitions
dunno if its posted anywhere, but if someone needs it for reference:
Code:
major minor #blocks name
179 0 15388672 mmcblk0
179 1 61440 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 10240 mmcblk0p10
179 11 13952 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 1536000 mmcblk0p14
179 15 12832768 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 860160 mmcblk0p17
179 18 10240 mmcblk0p18
179 19 10240 mmcblk0p19
179 20 6144 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 8 mmcblk0p22
179 23 5120 mmcblk0p23
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
hmmm stuck.
so I pulled just system and boot, and using cygwin turned them into a tar package and added the md5.
Tried flashing through Odin and get a unsupported dev_type error on the phone.
is their a specific order to add these .img files to the .tar?
nosympathy said:
hmmm stuck.
so I pulled just system and boot, and using cygwin turned them into a tar package and added the md5.
Tried flashing through Odin and get a unsupported dev_type error on the phone.
is their a specific order to add these .img files to the .tar?
Click to expand...
Click to collapse
Don't flash boot.img as the locked bootloader will throw back errors. You will need to reflash the stock Odin image. Also, before reflashing the stock image, try booting into recovery and factory reset
Sent from my SCH-I535 using Tapatalk 2
das7982 said:
Don't flash boot.img as the locked bootloader will throw back errors. You will need to reflash the stock Odin image. Also, before reflashing the stock image, try booting into recovery and factory reset
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
i gotcha, so even though it is a stock boot.img from samsung I cannot flash it in a custom package?
I am just trying to get my rom into an odin image for people that wanted it.
nosympathy said:
i gotcha, so even though it is a stock boot.img from samsung I cannot flash it in a custom package?
I am just trying to get my rom into an odin image for people that wanted it.
Click to expand...
Click to collapse
That's right. Since its a locked boot loader everything flashed has to be digitally signed by samsung
Sent from my SCH-I535 using Tapatalk 2
Hello everybody,
I'm from Holland, and am starting a project on a B-rank device which is being sold here in Holland in the Aldi supermarkets.
Now as a challenge for myself I wan't to try and get CWM to these devices, but it's not as simple as it looks.
The phones make use of MediaTek hardware, and many of you know that MediaTek unfortunately is not very opensource.
The phone I'm starting to work with holds a MTK6577T SOC.
Now I was able to get a copy of all partitions the device has, respectively:
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
I suspect the mmcblk0boot0 and boot1 partitions to hold the kernel, but when using mkbootimg the program tells me:
File mmcblk0boot0.img not a plain boot image, seeking for embedded image ... not found.
Also when I execute a command file mmcblk0boot0.img from shell it tells me:
mmcblk0boot0.img: data
Btw, the files mmcblk0boot0.img and mmcblk0boot1.img are both around 2.1Mb, which in my opinion is very small, maybe somebody can shed some light on this opinion?
Can somebody point me in the right direction?
I already have some knowledge in porting and kernel related stuff, but I can't seem to figure this one out.
Greetings PsychoGame
Greetings dears XDA members!
I read out many many many of posts before postings, and also used "search" feature in order to find a topic like mine, but with no success.
Well, I start to explain my problem..
====
A few days ago, my Samsung Galaxy Tab 2 (10'1)'s tablet caused some reboots without really beings really very common, but now .. reboot frequency has greatly increased since yesterday day.
A quick check using the "Reboot Checker" (you can find it through the Google Playstore: https://play.google.com/store/apps/details?id=jp.chau2chaun2.rebootchecker), and I can see that reboots are really common now as showed by the log reports showed in "RebootCheckerLogReports.png"'s file attachment to my post.
So.. What I do of specials before reboots are produced??
Hmm.. Really nothing, really:
I always deactivate the "AutoUpdate" for Apps from Google Play
Before reboots are encountered, I not installed any applications
I never install applications and Games out of Google Play official market
I just play to few games (like usually I do): Fantasica, Rage of Bahamut, Legends of Cryptids, Arcana Magic, DarkLords, Bingo Blitz, Chaos Drive, and that's all..
All applications I install from Google Play are recommanded/unlocked by AppGratis (and other websites like this)..
I never rooted my system (And I see now, I'll have to do on Day 1 of the purchase of the tablet ... since no-rooted an Android System doesn't permit recovery things at an advanced state..)
So, due to that reboot, I firstly thought that was a memory storage issue like, not enough diskspace. (with all that AppGratis applications, I have less disk storage memory indeed xD).. Then, I uninstalled some apps which I installed some months ago and I less used..
Bad Tought: Reboots hasn't been discontinued... ** sigh **
I think then it was update of Google Apps (like Google+, Google Talkback, Google Mail, Google Youtube etc..), so I updated them from Google Play..
Again, Bad Toughts: Reboots still here.. ** big sigh **
Well.. my hope was then at this state ported to Internet...
So I read many topics on "Unattended Reboots"..
And I finally found something of VERY useful.
On here: http://android.stackexchange.com/qu...-determine-the-cause-of-random-device-reboots
Glad I find that StackExchange question, I now that the "su" (Linux SuperUser if I well understand my Linux course), is not possible under a non-rooted Android (that a stupid behavior for an Operating System that.. But.. Well.. I continue)..
So, I started to think how I will be able to catch this file... and save in a readable folder..
Hopefully, 1 year ago I installed an app named: "ES Explorateur de fichiers" (find out this here: https://play.google.com/store/apps/details?id=com.estrongs.android.pop)
And this great apps was letting me accessing to the wanted file: /proc/last_kmsg
(I shared it to my DropBox linked account, and then I was able to open it on my Windows 7 Computer).
I then provide the log here: https://www.dropbox.com/s/u9ble2ui30io5x8/last_kmsg
So.. In the meantime, I started to analyze the log, and visiblely, my main (and sad) problem is that my Internat Flash Drive is dead.. Since I/O errors are the only main reason to Kernel Panic and reboots..
Well.. My warranty is void since months now.. (well well.. well..)
I then can't RMA the product (the tablet if I understand well).
I don't want wipe datas/cache and anything before try some new XDA tricks.. (I don't expect do much like that, but hey.. Hope is Hope.. my datas aren't important, it's true, it's mainly Game Saves and Unlock keys for AppGratis recommanded applications, but then, if I wipe datas, I will lose ALL of theses free unlocked apps.. This is a thing I doesn't really want, if you mean what I want mean..)
... so... I started to think what we can do for fix bad sectors on Linux (since Android is based on Linux and Dalvik if I (again) understanded well).
I hink that fixing bad sectors allocations it will fix the problem, since if I analyze my Internal storage (called sdcard0) there is sometimes the scan is finished without reboots!
So I was directed on XDA-Developers (which I know that you are famous for your system hacks and morever) here by Google : http://forum.xda-developers.com/google-nexus-5/help/reboot-due-to-kernel-panic-t2553949
I saw this post: http://forum.xda-developers.com/showpost.php?p=48250638&postcount=3
And then a quick search on Google again on the words "Android + fsck the filesystems through adb shell" redirected me to that excellent post: http://forum.xda-developers.com/showthread.php?t=2165870
This is a great information, but... I don't know how to go in recovery mode from my Galaxy Tab 2. So.. I searched on the web for it, and found that: http://forums.androidcentral.com/sa...ing-into-recovery-mode-galaxy-s2-s3-tab2.html
So.. I started blink my eyes, and go for hard work, and since I already in the past installed the Android SDK (for develop personal mobile apps with Titanium Studio, Adobe Cordova, PhoneGap), and do all update especially installed adb..):
Once plugged to my PC and booted in recovery mode, I was able to access to the famous recovery mode
(This was so exciting due to the fact I like the way of it look: especially the Android bot unfixed in the background ^_^).
So, on my PC I started to open a command line in the folder: C:\SpecialAppDevelopper\Google Android SDK\platform-tools
(this is where I installed the Android SDK)
and typed this:
Code:
C:\SpecialAppDevelopper\Google Android SDK\platform-tools>adb devices
This showed me that:
List of devices attached
c16073dc82dc68f recovery
Click to expand...
Click to collapse
So it worked! My device was successfuly attached to ADB !! What an excitation !
I then continued typing other commands:
Code:
C:\SpecialAppDevelopper\Google Android SDK\platform-tools>adb shell
This output that:
[email protected]:/ $
Click to expand...
Click to collapse
Good. Now In this shell access I typed :
Code:
mount /system
Not good here since all I get is a USAGE warning with options recommanded. (like a return of a MAN command..)
[email protected]:/ $ mount /system mount /system Usage: mount [-r] [-w] [-o options] [-t type] device directory
Click to expand...
Click to collapse
Well.. tryied the next command in order to listing report file system disk space usage:
Code:
df
all I got as output was occuped space, not the path of the mounted images...
Well...
Now, I started to reanalyze my last_kmsg log in order to find which path they are..
I found it!
[ 94.965454] C1 [jbd2/mmcblk0p10]
So... I started to return to my ADB commandline window and typing:
Code:
ls -l /dev/block/mmcblk0p10/
This outputed that:
/dev/block/mmcblk0p10/: Not a directory
Click to expand...
Click to collapse
So as it looks a good path, I started typing this:
Code:
e2fsck -n /dev/block/mmcblk0p10
And even if it is the right path (one of the right path, I don't tryied with others...), I got this output:
e2fsck -n /dev/block/mmcblk0p10
e2fsck 1.41.11 (14-Mar-2010)
e2fsck: Permission denied while trying to open /dev/block/mmcblk0p10
You must have r/o access to the filesystem or be root
Click to expand...
Click to collapse
Yeah... I'm not root, cool, even in a Recovery Mode on a non-rooted Android Operating System (Logic in a way, but very difficult to fix problems then occuring then )..
Ok.. So, My mind blinked in an idea when looking at this: You must have r/o access to the filesystem or be root
So.. This is not needed to be root for executing a e2fsck command in Recovery Mode, but in that case I need having access to the filesystem in a READABLE mode. OK.
So, Hope started to bringed back, and I made new Google research, on "mount an android filesystem in recovery mode"
I was then directed here:
- http://forum.xda-developers.com/showthread.php?t=1396864 - Very complex for me, I don't want brick my system.. So I skipped.
- http://androidforums.com/droid-all-...tem-when-trying-adb-push-app.html#post6347416 -
So.. For being root in recovery mode, I can also type the simple command: adb root
Ok... What I do..
And, as expected it doesn't worked for me:
C:\SpecialAppDevelopper\Google Android SDK\platform-tools>adb root
adbd cannot run as root in production builds
Click to expand...
Click to collapse
Ahaha.. Well starting to be hopeless now.. I'm finally just an user of my OWN tablet.. How it's ridiculous.
This is a bit tedious, because all my future Google research in order to find how to simply "mount" a filesystem as readable (and then replace it as it was after the process..) aren't really efficient, I founded nothing of useful..
Nothing usefull but that: http://android.stackexchange.com/a/69307
So, it seems I will be able to mount as readable a filesystem through Production Recovery Mode (the one I'm forced to use then..)..
BUT..
Well.. Now, since I don't know what I can type for mounting my filesystem... as readable just for make a e2fsck... Seriously..
Help me dear gurus, i'm completely lost because my Linux knowledge stop here !
New informations..
I tryied an another method in order to list devices symlinks names:
Another way to check is to use adb to view the devices file system.
Related to this thread: http://forum.xda-developers.com/showthread.php?t=1463756
Thanks to it (even if it isn't how mounting in RW)
So, when plugged in Recovery Mode I typed:
Code:
adb devices
adb shell "ls -R /dev/block"
The -R is because I want have the realpath of each items listed
Well, this was the output:
/dev/block:
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
platform
ram0
ram1
ram10
ram11
ram12
ram13
ram14
ram15
ram2
ram3
ram4
ram5
ram6
ram7
ram8
ram9
/dev/block/platform:
omap
/dev/block/platform/omap:
omap_hsmmc.1
/dev/block/platform/omap/omap_hsmmc.1:
by-name
by-num
mmcblk0
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
/dev/block/platform/omap/omap_hsmmc.1/by-name:
CACHE
DATAFS
EFS
FACTORYFS
HIDDEN
KERNEL
MODEM
PARAM
RECOVERY
SBL1
SBL2
/dev/block/platform/omap/omap_hsmmc.1/by-num:
p1
p10
p11
p2
p3
p4
p5
p6
p7
p8
p9
Click to expand...
Click to collapse
Also, I read from here: http://forum.xda-developers.com/showpost.php?p=44328873&postcount=10
That E2FSCK will better be secure when executed on a named partition, can you confirm me it or no?
Now, I think..
Since, I know on my Windows when a sectors in corrupted or broken state, I can simply tell to the OS (Windows so) that I want it IGNORE it !
How I can do the same things to my Galaxy Tab 2?
It certainly fix my problem like that no?
Well well..
It is not better than it was, I really need advices and moreover help to know what I can do with the "mount" command and plus..
I was at 4'th page of the forum, so I think my thread just goes skip from your eyes, this is why I want up it..
Anyway, I read somewhere there is a lot of commands available.. due to the fact I'm not aware suffisely with Linux, and due to the fact Android recovery commands (and moreover the System) is based on Linux.. I prefer ask here..
So please, please.. answer me