yashsingh1/xdaforums huggingface dataset:
[Desire General] slurdge:
Ok the first step worked, but unyaffs does not want to open my imgs.

The size are as follow:

3*145*728 boot.img
3*145*728 boot_ro.img
41*943*040 cache.img
41*943*040 cache_ro.img
655*360 misc.img
655*360 misc_ro.img
4*718*592 recovery.img
4*718*592 recovery_ro.img
262*144*000 system.img
262*144*000 system_ro.img
154*796*032 userdata.img
154*796*032 userdata_ro.img

which seems good (I also made images from the mtdXro). However I should be able to extract userdata and system from my understanding. I tried with unyaffs both on linux and on windows, on both I get a segmentation fault.

Do I have a way to verify that theses images are good ? I do not want to trash the new phone I will buy with a faulty image...
[Desire General] mercianary:
Flash the same rom from recovery on your new phone, then flash the data image from fastboot, if it works the first boot should take a while as it builds the cache. If it doesn't work just clear data and it wont have done any damage to your new phone.

You will have to zip the data image before you fastboot flash it because it's too big for fastboot to receive.

If you have s-off on your old phone I would flash amon-ra recovery from fastboot then use the nandroid script over adb.

As long as you don't try to flash the recovery you backed up I don't think there's any chance of damaging your new phone doing this.
[Desire General] slurdge:
Ok the final solution was to use the new phone (rooted and with clockworkmod) as a reference.

I did the same backup sequence on the two phones, and have been able to restore the backup on the new phone.

Thank you everyone for your help ! :)
[Desire General] mercianary:
Glad you got it sorted...don't drop your phone under a car again. :)
[Touch Diamond2, Pure Android Development] CageOff:
Unfounded claim work is dead.
[Touch Diamond2, Pure Android Development] Crembo:
Where's the report button?

EDIT: Nevermind, found out. Others - report too.
[Touch Diamond2, Pure Android Development] xrshwy:
what??? base on data, fact...
[Desire General] dazz0r:
When I boot my Desire it's stuck at the android logo.

When I use reboot bootloader en then restart it boots, but then when I let the screen turn itself of and then press the start button at the top it just restarts (when it just gets stuck at the boot screen again)

Anyone an idea what i can do about it?
[Android] IzaacJ:
Hello.

I'm one of those with an device which can't get Android on NAND (yet, waiting for MAGLDR)

So I got an idea (which I guess is discussed or tried, but didn't find anything about it).

Why put the stuffs in different img's, why not in ext partitions on the SD-card, if it even is possible...

So, does anyone know how this could be accomplished, or if it isn't possible, why?

Regards :)
[Nexus One Q&A, Help & Troubleshooting] xrepo:
how do you forward a text message to another phone

thanks

??
[Nexus One Q&A, Help & Troubleshooting] meechto:
Long press the message you want to forward and you should get the options ;)
[Galaxy Tab  Android Development] TheGrammarFreak:
I'm sorry about your Tab man. :(
[Galaxy Tab  Android Development] codewisp:
After flashing JM6, I have "zImage" and "Sbl.bin" but no "boot.bin" in my internal SD. Am I affected?

Also, is it safe to delete these files from my internal SD? I'm guessing they were put there temporarily and are now stored somewhere else already?
[Galaxy Tab  Android Development] DubZyy:
hey chainfire,

i'm sorry about the brick :/

my english seems to be very bad... could u explain me why ur tab is bricked now?

i think i understood why its not possible to flash to another firmware but why ur tab is bricked now? yesterday i flashed to jm6 from an old arabic fw (i think it was JJ1) with pit p1 and code, modem and csc file with re-part. on. so is anything there i have to look out now?
[Galaxy Tab  Android Development] Chainfire:
You could be affected, I can't say for sure. The only way to be sure is trying to flash a custom kernel and see if Odin gives an error. See the CF-Root thread for screenshots of the error that is produced if you are affected. If there's no error and it boots, you have probably not been affected. Note that you can flash back the original JM6 kernel with both the "protected" as well as the "original" bootloaders.

I'll update the first post to add a bit more information.

Also yes, those files on your internal SD are temporary, you can delete them.

The brick is a result of a bad bootloader flash... it's not something any of you are likely to encounter (unless you are trying to fix this issue).

If you successfully flashed to JJ1 - Odin did not produce any errors - you are probably safe!
[Galaxy Tab  Android Development] chinchen:
Thanks for the information, but a little bit late for me :D --> bricked

My luck: Next samsung repair center is 5 kilometers away.

But I don't know what i should tell him.

The truth? ;)
[Galaxy Tab  Android Development] Jesterz:
@chainfire

Have your tried hexediting the version of the SBL to a "fake" newer version? or does the check only care about the checksum ? on older phone we used to be able to do this....

I'm unpacking my dev. tab as we speak so I hope to have some time to play between x-mas dinners ;)
[Galaxy Tab  Android Development] Chainfire:
Damned lucky the repair center is close!

You wouldn't happen to be living near me and I just never heard of this service center, would ya ? ;)

How exactly is it a brick ? It's only a brick if it doesn't turn on at all anymore (like mine). If you can get anything on screen, you can bring it back to life (although maybe with protected bootloaders).

As far as I have been able to deduce (I have not done a full decompile yet, and not sure if I'm going to) it's only the checksum that matters. But I could be wrong there.

I'll upload some files for you in a minute, so you can look at them yourself as well.
[Galaxy Tab  Android Development] faust86:
Anything besides truth - tell them that you turn off Tab at evevning, and at the morning he doesnt start... they believe :)

Chainfire - my condolence... i also cannot flash CF-Root on JMC so i think i have new bootloader - im waiting for next steps when yours Galaxy Tab alive

sorry for my english;)
[Galaxy Tab  Android Development] Chainfire:
@Jesterz:

Some files you might want to look at attached to first post.
[Galaxy Tab  Android Development] faust86:
Is there any way to check what version of bootloader i have installed? I cannot install CF-Root on JMC -its enough to say i upgrade bootloader in my Tab?
[Galaxy Tab  Android Development] Chainfire:
If you get the same error as in the screenshot linked to in the first post, yes, you have the protected bootloaders.
[Galaxy Tab  Android Development] kromosto:
good to know i am not effected. and for people who has effected roms i think as we know the reason there will be a quick solution for this.
[Galaxy Tab  Android Development] faust86:
So i install this *** bootloader... maybe i brick my Tab and take it to service point... i have 100 meters :>
[Galaxy Tab  Android Development] patomas:
Me too

I have the error and I cant change ROM (a part from switching between JM6, JMA and JMC)... Hope someone soon find a fix!

My tab some ago was in a similar state (complete black and didnt show in ODIN).

My luck was that it was stuck in some kind of download mode. Leaving it connected to the computer has made a miracle: after more than 15 minutes it has appeared as connected in ODIN and was possible to flash back a ROM).
[Galaxy Tab  Android Development] Chainfire:
I'll just try that. I have no hope of it working, but hey, it's not like I'm using the Tab for anything else right now :P
[Galaxy Tab  Android Development] rotohammer:
While the Tab was at a black screen, did you ever press the power button or did you just leave it alone for Odin to eventually find it?
[Galaxy Tab  Android Development] Chainfire:
While you're here... any chance of both STL and BML dumps of your (hopefully proper) PBL and SBL ?
[Galaxy Tab  Android Development] rotohammer:
Of course. I have dumps of everything. I'm just about to run some diffs to make sure my current bootloaders are ok, I can't remember what Ive flashed :)
[Galaxy Tab  Android Development] acolwill:
Well,

Here's my results :)

SGT-BootloaderCheck v1.0 - Copyright (C) 2010 Chainfire

boot.bin: SIGNED !
sbl.bin: Unsigned
zImage: SIGNED !
[Galaxy Tab  Android Development] faust86:
All three files signed:

SGT-BootloaderCheck v1.0 - Copyright (C) 2010 Chainfire

boot.bin: SIGNED !
sbl.bin: SIGNED !
zImage: SIGNED !

I had JM6 (after Orange branding firmware - i dont check version) and upgraded it into JMC :/
[Galaxy Tab  Android Development] irkkso:
I'm so happy that I was too busy at work for all last weeks.

SGT-BootloaderCheck v1.0 - Copyright (C) 2010 Chainfire

boot.bin: Unsigned

sbl.bin: Unsigned

zImage: Unsigned

Assessment:

-- Bootloaders: Unprotected, can flash all bootloaders and kernels

-- Kernel: Unsigned, can only be flashed on unprotected bootloaders

Press any key to continue . . .
[Galaxy Tab  Android Development] Jesterz:
@chainfire,

What's the status of this? maybe we can pool resources with more people looking into this.

also, I assume (?) you played around with bmlunlock by koush ?

https://github.com/CyanogenMod/android_device_samsung_bmlunlock

Precompiled binary here: http://koush.tandtgaming.com//samsung/bmlunlock

After running bmlunlock on the samsung device, one can flash the kernel using the following command: dd if=/sdcard/zImage of=/dev/block/bml7 bs=4096

(yes i'm catching up, didn't read through 19 pages so excuse me if double posting ;) )
[Galaxy Tab  Android Development] leonreijnders:
Here is mine results.

SGT-BootloaderCheck v1.0 - Copyright (C) 2010 Chainfire

boot.bin: Unsigned

sbl.bin: Unsigned

zImage: SIGNED!
[Galaxy Tab  Android Development] kromosto:
if signed parts are also encrypted with sign? otherwise can just adding sign part of a signed for example zimage to an unsigned one work?
[Galaxy Tab  Android Development] clubtech:
Interesting:

I was on full flashed from JM6 through JMD and all my files yesterday we signed.

Today i fully flashed to JMF(E) and i got different results:

boot.bin: SIGNED

sbl.bin: Unsigned

zImage: SIGNED !

It looks like my sbl.bin file just got unsigned...
[Galaxy Tab  Android Development] kromosto:
or the mechanism to determine if sbl is signed or not not working well. also can be a nethod for forceing flash that might be our solution if we can find it.
[Galaxy Tab  Android Development] paulshields:
The question is - has anyone plucked up the courage to try this? :D. I'm tempted but anything involving dd'ing an image over /dev/block/... scares me :).
[Galaxy Tab  Android Development] Jesterz:
I've played with dd fun before in the "old" days, somewhat scary, however bml7= kernel, which should be still reflashable using odin etc. bml1&2 is the scary part as that contains the bootloaders.

Edit:

Maybe a better way is to use the samsung OTA tool, redband_ua, didnt have time to dig in, however its in heavy use on the Galaxy S, might work on Tab

http://xdaforums.com/showthread.php?t=765724&page=2

However i'm assuming ChainFire is this far and I don't want to duplicate work, but detailing what is done already is useful
[Galaxy Tab  Android Development] rotohammer:
Looks like my jtag box will be in next week, so let me do the flashing to bml1, bml4 and bml5 as I will be able to recover from bricking.
[Galaxy Tab  Android Development] kromosto:
So the solution is near good luck
[Galaxy Tab  Android Development] blacklevel:
I also have the situation with a signed PBL and an unsigned SBL:

boot.bin: SIGNED !
sbl.bin: Unsigned
zImage: SIGNED !

This combination only allows to flash signed kernels. That somewhat confirms the suspicion that the PBL might indeed enforce that only signed kernels can be flashed. Of course it is also possible that the SBL does the signature verfication of the kernel. The SBL itself does not need to be signed for this. But it seems odd for Samsung not to protect the SBL but everything else.

I was able to upgrade JMD to JMF -- including the kernel (JMD: 2.6.32.9 root@SEP-42 #1 *** JMF: 2.6.32.9 root@SEI-26 #1). I could also downgrade to the JMD kernel. Since both kernels are signed this is not really surprising.

For kicks I tried to flash the unsigned kernel from JK5. That failed and is also not surprising.

$ heimdall flash --kernel zImage

Heimdall, Copyright (c) 2010, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au

(...)

Claiming interface... Success
Setting up interface... Success
Beginning session...
Handshaking with Loke... Failed!
[Galaxy Tab  Android Development] Jesterz:
Ahh, guinea pig heaven :)
[Galaxy Tab  Android Development] abuser0815:
you should definitely be able to flash jk5 kernel, because i have the same constellation, and it works like this:

EDIT: I´m not responsible if it fails, as this is just decribing what I did...

1. backup everything.

2. factory reset and formatting internal sd

3. repartition with odin (just pit file which is adecuate for jk5)

4. don´t reboot go straight back to downloading screen by holding vol down after flashing pit

5. heimdall graphical frontend (sorry geeks, it works and its comfortable) everything from jk5; but i would go to a former firmware as jk5 which includes all, also boot.bin and sbl.bin; put in heimdall everything from your firmware you like to flash except pit and recovery-->

6. press start in heimdall; the process on the computer should go without any error

AND NOW

7. your tab get stucked at aproximately 87 % :p update process; NO Panic

8. disconnect your device from your pc and start it, you should come to a very basic bootscreen "tab---warning---computer"

9. start odin and do just the step 3 again

10. while rebooting hold volup to make sure it starts installing the rest

11. voila, you should have your wished firmware installed.

ATTENTION, it might show again that the primary bootloader and kernel is still signed, but .....

12. flash your dbdata and install your tab new

that was how i made it working, can somebody confirm it please??:cool:
[Galaxy Tab  Android Development] KarlMarsh:
Here is the output from a stock ATT ROM. Probably no surprises here.

Edit: Noob question: Why does the output say it transfered the file successfully but then says it can't find the files? Did I do something wrong?

========================================================
= Samsung Galaxy Tab Bootloader Check v1.0 =
= Copyright (C) 2010 Chainfire =
= =
= Please make sure your device is connected, rooted, =
= and USB debugging is enabled ! =
= =
= Accept the SuperUser prompt when it shows up ! =
========================================================

Press any key to continue . . .

========================================================
= Dumping PBL, SBL and kernel ... =
========================================================

su
rm /sdcard/bml1.bin
rm /sdcard/bml4.bin
rm /sdcard/bml7.bin
dd if=/dev/block/bml1 of=/sdcard/bml1.bin bs=4096
dd if=/dev/block/bml4 of=/sdcard/bml4.bin bs=4096
dd if=/dev/block/bml7 of=/sdcard/bml7.bin bs=4096
exit
exit
$ # # # # 64+0 records in
64+0 records out
262144 bytes transferred in 0.050 secs (5242880 bytes/sec)
# 320+0 records in
320+0 records out
1310720 bytes transferred in 0.171 secs (7665029 bytes/sec)
# 1920+0 records in
1920+0 records out
7864320 bytes transferred in 0.699 secs (11250815 bytes/sec)
# $
========================================================
= Retrieving files ... =
========================================================

Could Not Find C:\Documents and Settings\Karl\My Documents\Android\SGTBootloader
Check-1.0\boot.bin
Could Not Find C:\Documents and Settings\Karl\My Documents\Android\SGTBootloader
Check-1.0\sbl.bin
Could Not Find C:\Documents and Settings\Karl\My Documents\Android\SGTBootloader
Check-1.0\zimage
331 KB/s (0 bytes in 262144.000s)
384 KB/s (0 bytes in 1310720.003s)
374 KB/s (0 bytes in 7864320.020s)

========================================================
= Here come the results ... =
========================================================

SGT-BootloaderCheck v1.0 - Copyright (C) 2010 Chainfire

boot.bin: Unsigned
sbl.bin: Unsigned
zImage: Unsigned

Assessment:
-- Bootloaders: Unprotected, can flash all bootloaders and kernels
-- Kernel: Unsigned, can only be flashed on unprotected bootloaders

Press any key to continue . . .
[Galaxy Tab  Android Development] msgfromside3:
maybe because you ran it under path with space(s) and the tool does not quote the entire path? you can try to run the script from the path without space (like c:\tmp\) and see if it goes away.
[Galaxy Tab  Android Development] KarlMarsh:
Yep good call. That was the problem. Here is the corrected output. Thanks for your help.

========================================================
= Samsung Galaxy Tab Bootloader Check v1.0 =
= Copyright (C) 2010 Chainfire =
= =
= Please make sure your device is connected, rooted, =
= and USB debugging is enabled ! =
= =
= Accept the SuperUser prompt when it shows up ! =
========================================================

Press any key to continue . . .

========================================================
= Dumping PBL, SBL and kernel ... =
========================================================

su
rm /sdcard/bml1.bin
rm /sdcard/bml4.bin
rm /sdcard/bml7.bin
dd if=/dev/block/bml1 of=/sdcard/bml1.bin bs=4096
dd if=/dev/block/bml4 of=/sdcard/bml4.bin bs=4096
dd if=/dev/block/bml7 of=/sdcard/bml7.bin bs=4096
exit
exit
$ # # # # 64+0 records in
64+0 records out
262144 bytes transferred in 0.017 secs (15420235 bytes/sec)
# 320+0 records in
320+0 records out
1310720 bytes transferred in 0.151 secs (8680264 bytes/sec)
# 1920+0 records in
1920+0 records out
7864320 bytes transferred in 0.390 secs (20164923 bytes/sec)
# $
========================================================
= Retrieving files ... =
========================================================

287 KB/s (0 bytes in 262144.000s)
384 KB/s (0 bytes in 1310720.003s)
440 KB/s (0 bytes in 7864320.017s)

========================================================
= Here come the results ... =
========================================================

SGT-BootloaderCheck v1.0 - Copyright (C) 2010 Chainfire

boot.bin: Unsigned
sbl.bin: Unsigned
zImage: Unsigned

Assessment:
-- Bootloaders: Unprotected, can flash all bootloaders and kernels
-- Kernel: Unsigned, can only be flashed on unprotected bootloaders

Press any key to continue . . .
[Galaxy Tab  Android Development] heythorp:
Ok I have a bigger noob question. Are the files you posted a current ATT dump?

If so what do I need if I want to go back to the ATT rom. Thanks
[Galaxy Tab  Android Development] KarlMarsh:
Yes those are stock ATT bootloader and kernel files but for you to return to a stock ATT rom, you will need much more than those. There is another thread around here somewhere with Roto's ATT rom. I suggest you look there.
[Galaxy Tab  Android Development] NGP:
Don't do that! I know the man who get a brick this way...
[Galaxy Tab  Android Development] Sparkle1975:
Thanks for the idea - got my Tab back alive again. However, I did not follow this suggestion. Instead, I just tried a CODE/MODEM/CSC combo, and... IT WORKED!

I used this:

Odin3 v. 1.0 (don't know if Odin 1.3 or Odin 1.7 is better, but I used the old one)

909.pit

P1000OXAJM6(PAR).tar (JM6 firmware)

MODEM_P1000XXJID.tar.md5 (from XXJID firmaware)

GT-P1000-CSC-SERJJ2.tar.md5 (from XXJID firmaware)

And now the beast is alive.

Baseband version P1000XXJID

Kernel 2.6.32.9 root@sep-53 #1

Build: FROYO.XXJM6

EDIT:

Worked, booted, but just one small problem: The backlight won't turn off automatic. But then I flashed these files:

http://xdaforums.com/showpost.php?p=9468220&postcount=1

And now it works perfect - backlight turns off, it's quite snappy.

I don't know if the firmware (boot/kernel) are signed or not, so right now I don't know which firmwares I am able to flash.

Next step: Is there any point in rooting the device? And are there no signs of custom ROM's ?
[Galaxy Tab  Android Development] blacklevel:
Now, that is interesting. If your procedure can be reproduced it would show at least one thing.

The failure to flash an unsigned kernel is because somehow the partitioning does not work for an unsigned kernel. Thus the flashing fails.

According to your procedure the flashing of an unsigned kernel works if the Tab is first repartitioned to a layout which matches the unsigned kernel.

I still have my doubts whether this procedure also allows to downgrade/replace the PBL to an unsigned version (or works at all for that matter).

If that is indeed the result of your procedure

it simply means that the flashing of the PBL (boot.bin) and the kernel were both unsuccessful, even if the flashing of the other parts worked okay.

I will check and post my findings.
[Galaxy Tab  Android Development] psxsnake:
if I have all signed (flashed with samfirmware JMD) what's mean?
[Galaxy Tab  Android Development] NGP:
It means you can't flash unsigned boot, sbl and kernel (from JK5 and older)
[Galaxy Tab  Android Development] abuser0815:
@blacklevel,

Heimdall is not stating an error on flashing those parts as kernel, pbl and sbl.
[Galaxy Tab  Android Development] m.tom59:
Have you compared the kernel?

I have done it as you have described it. But the kernel is still the same.

Here is what i think:

it is the same kernel as before, this is why it stucks at 87%, the kernel can not be flashed.

You can go easyer to an older firmware, remove the boot.bin, sbl.bin, and zImage from the firmwarefile, and flash it.

In my oppinion, is the way that you described a very dangerous way.

m.tom59
[Galaxy Tab  Android Development] blacklevel:
can you post the kernel info from the settings menu? Maybe heimdall does not recognize if the Tab has refused to accept the new kernel.
[Galaxy Tab  Android Development] paulshields:
Heimdall doesn't really say anything one way or the other when flashing. These kinds of tools are always very blunt and "dumb" in information terms. I suspect like others that you're not flashing an equivalent kernel when rolling back to whatever previous version you're choosing. Simple way to tell is to run chainfire's script. If you've managed to get to an unencrypted kernel/bootloader then that is significant but we will need proof :).
[Galaxy Tab  Android Development] abuser0815:
Paul...

I assumed also that its not really changed. But under*#1234# it shows me the firmware i flashed and i wanted. Kernel, pbl and sbl i do not really know wht heimdal is doing on it or not.
[Galaxy Tab  Android Development] m.tom59:
I have try to flash an unsigned sbl with the foolowing command:

adb shell su -c "dd if=/sdcard/Sbl.bin of=/dev/block/bml4 bs=4096"

but with no working result. After reading the sbl again:

adb shell su -c "dd if=/dev/block/bml4 of=/sdcard/Sbl.bin bs=4096", it is still the same as before.

Also i have flashed an unsigned zImage in this way.

The kernel can flashed, but after flashing, the Tab don't start up.

I must flash an signed kernel again to reactivate the Tab.

m.tom59
[Galaxy Tab  Android Development] xIllu:
so my tab is SIGNED, what does that now actually mean ? which roms can be flashed and which can not ? tnx
[Galaxy Tab  Android Development] Volker1:
In order to get a useful log out of Heimdall, you need to flash from the command line and pass the --verbose option

[user@localhost]$ ./heimdall
Usage: heimdall <action> <arguments> [--verbose] [--delay <ms>]

action: flash
arguments:
--repartition --pit <filename> --factoryfs <filename>
--cache <filename> --dbdata <filename> --primary-boot <filename>
--secondary-boot <filename> --param <filename> --kernel <filename>
--modem <filename>
or:
[--pit <filename>] [--factoryfs <filename>] [--cache <filename>]
[--dbdata <filename>] [--primary-boot <filename>]
[--secondary-boot <filename>] [--secondary-boot-backup <filename>]
[--param <filename>] [--kernel <filename>] [--recovery <filename>]
[--efs <filename>] [--modem <filename>]
description: Flashes firmware files to your phone.