Related
I don't take the responsibility for any damage caused by the information included.
This is not my intention to reveal any secrets of HTC Company. All this information was known earlier. I've just collected it in one place and used it for repairing my broken HTC device.
Although it was successfully tested on Herald from Dopod, it should work on any Herald and as far as I know this is the only hope, especially for Heralds with low SPL number, broken by flashing with HardSPL
If you find this tutorial useful, do it on your risk.
I've spent a lot of time in searching of a solution for my bricked Dopod C858. It has been bricked after Hard-SPL by Olipro. When this Hard-SPL was first introduced, there wasn't any warnings about minimum SPL and GSM versions requirements. That's why there is a lot of people with their Heralds stuck in the bootloader mode without a possibility of successful flashing in any way.
One of the symptoms was Invalid Update Tool 300 Error when I was trying to flash even with the official RUU. The other symptom was "GetDeviceCID: Error - InitDecoder" when getdevinfo command was typed at MTTY console.
Finally I was able to recover from this state. I successfully created the goldcard - a micro SD card with the special header, which gives us a temporary SuperCID status (security level 0). In this way we are able to flash the new ROM via SD card, instead of using the official RUU (ROM Update Utility). If it is not enough to flash successfully, we can use a wonderful service tool included in Herald's diagnostic image (heradiag.nbh).
All the credits goes to "itsme" and his hard work. It wouldn't be possible without his knowledge, his help and his great software. Willem agreed to make this tutorial and share this knowledge on the forum.
Thank you Willem!
I would also like to thank "pof" for his effort and although he couldn't find a solution, he tried to help me, so thank you Pau!
The other person I would like to thank is "canonyang_China". I know he is accused of stealing Olipro's ideas of Hard-SPL. I only want to thank him for posting heradiag.nbh file. This is the great tool which together with the goldcard can do a lot.
I would also like to mention one person. It's "jockyw". He has almost identical solution but he has found it by himself. If you find this tutorial too hard to deal with I recommend to contact "jockyw" and he will help you for a small paypal donation.
TUTORIAL:
***********************************************************
Requirements (not tested on other configurations):
1) Windows XP with SP3
2) ActiveSync 4.5
3) ActivePerl 5.8.8.822
4) Crypt-DES and XdaDevelopers-NbfUtils PERL packages
5) typhoonnbfdecode.pl PERL program
6) itsutils tools
7) working mobile device with any Windows mobile OS (2003, 5.0, 6.0)
8) any .nbh ROM file from the official Herald's RUU
9) heradiag.nbh file
10) micro SD card (tested on 512MB and 1GB)
Ad.2) download your language verion of ActiveSync and install it:
Ad.3) download and install MSI installer of ActivePerl 5.8.8.822 from http://www.activestate.com
http://www.activestate.com/store/download_file.aspx?binGUID=e5c71329-b7a6-4563-8199-e1483f751c4f
Ad.4) run Perl Package Manager from Windows Start Menu
change PPM Preferences (run Preferences from the Perl Package Manager menu and switch to the repository tab):
- Add repositories:
Name: itsme
Location: http://www.xs4all.nl/~itsme/projects/perl/ppm
- Add repository:
Name: theoryx
Location: http://theoryx5.uwinnipeg.ca/ppms/package.xml
After database synchronization install those packages (at the main window of Perl Package manager find those packages, mark them for install (the icon with green plus, next to the search bar) and run marked action(green arrow icon)):
-Crypt-DES
-XdaDevelopers-NbfUtils
If you can't find those packages on your list, please make sure you have selected "All packages" from "View" menu in Perl Package Manager main window.
Ad.5) download typhoonnbfdecode.pl from http://www.nah6.com/~itsme/cvs-xdadevtools/xda2nbftool/
Save it to "C:\itsutilsbin"
Ad.6) download itsutilsbin package from http://www.xs4all.nl/~itsme/projects/xda/tools.html. Unpack it to "C:\itsutilsbin"
http://nah6.com/~itsme/itsutilsbin-20080602.zip
Ad.7) Find a working Windows mobile device and use it to format your micro SD card as FAT32. It's important to do this on working mobile device with any Windows mobile OS (2003, 5.0, 6.0) because PC USB card readers causing troubles with making a goldcard because of a different MBR interpretation.
- Activesync your working Windows mobile device with SD card inside
- On your PC enter windows command mode (Start->Run... cmd)
- Choose your itsutilsbin directory (cd C:\itsutilsbin),
- Run this command (l means a letter 'el' - not a digit 'one'):
psdread -l
If you have problems with running psdread -l you probably have problems with the security configuration of your mobile device. There are many options to change it. In my case I was using Device Security Manager PowerToy for Windows Mobile 5.0
It is recommended to save your security configuration, then change it to the Security Off level and after the whole goldcard preparation process, load saved configuration preset if you don't want to leave your Windows mobile device Security Off. You should have your mobile device ActiveSync with your PC when you are using this tool.
- If everything went OK, look at the result at the cmd window after psdread -l and find something like that:
remote disk 1 has 1984000 sectors of 512 bytes - 968.75Mbyte
SerialNr: 75 63 00 49 8a f2 00 80 47 31 30 55 53 44 53 03
- in the next step you will have to replace the first byte ( in this case '75' ) with '00' and write this ID without spaces between numbers - this will be your modified cardid
In this example your modified cardid will be 006300498af200804731305553445303
(Thank you "hookcard" for reporting troubles in this step)
Run this command, where <cardid> is your modified cardid:
perl typhoonnbfdecode.pl -p cardid=<cardid> -p keys=tornado -p seclevel=0 -d goldcard.img
- Your goldcard image will be saved in your current directory (C:\itsutilsbin)
- If you have error message connected with msvcr71.dll file, please download this file or try to find it somewhere on your system partition and then copy it to the directory containing typhoonnbfdecode.pl (C:\itsutilsbin)
Then repeat the previous step with running typhoonnbfdecode.pl
If everything went OK, run this command, where <number> is a number under which you have your SD card during psdread -l command, for example, "remote disk 1 has 1984000 sectors of 512 bytes - 968.75Mbyte" means that your <number> is 1:
psdwrite -<number> goldcard.img 0 0x120
Now you have a card which gives you SuperCID - you can test it with MTTY and see that g_cKeyCardSecurityLevel = 0
Ad.8) Remember to have more than a half of the battery capacity available before you start this step!
- download any official Herald's RUU and extract it to the directory, where you should find RUU_signed.nbh ROM file. (It was tested with Dopod's ROM). Copy this .nbh file to your goldcard changing its name to heraimg.nbh
- Enter the bootloader mode. When you will see on your Herald's screen the question: "Update SD image?" you will have 10 seconds to press Volume Down button and this way to start flashing
Unfortunatelly, if something will go wrong and i.e. you will see SD update failed you will have to use heradiag.nbh file to enter special menu during the start of the bootloader mode. If you have problems with flashing, please read the step below:
Ad.9) download and unpack heradiag.zip file from this thread:
http://forum.xda-developers.com/showthread.php?t=332413&highlight=heradiag.nbh&page=6
Remember to have more than a half of the battery capacity available before you start!
- Copy heradiag.nbh on your goldcard together with any official .nbh ROM from ROM Update Utility from the previous step.
- boot your Herald in bootloader mode and you will see the diagnostic menu where you will have Reflash Image option. Choose Reflash Image and after the flashing process (about 5 minutes) please softreset your device.
That's all! You should see your Herald properly booting Windows OS.
Good luck!
Anyone had any luck with this?
I tried.
Everything is O.K.
ok first of all thank you very much for as a hope gain to bring our herald to live again.
but there is some point at this thread i didnt get it so plz if u could help me
1-
run Perl Package Manager from Windows Start Menu
change PPM Preferences:
- Add repository: itsme http://www.xs4all.nl/~itsme/projects/perl/ppm
- Add repository: theoryx http://theoryx5.uwinnipeg.ca/ppms/package.xml
After database synchronization install those packages (mark them for install and run marked action):
-Crypt-DES
-XdaDevelopers-NbfUtils
what is crypt -des
and when i open the link (add rep.by itsme )
there is too many files to download.
which one is that files u mean
i download them all but it seems they work on linux not in windows
so plz if u make that point more clear or at least post some pictures..
2-
does any official room will work .or it must be the exact cid room.
I've updated this tutorial and now it should be more clear.
According to your question about the ROMs - if you successfully create the Goldcard you will be able to flash any ROM, not only those matching your original CID.
halder said:
...............
what is crypt -des
and when i open the link (add rep.by itsme )
there is too many files to download.
which one is that files u mean
i download them all but it seems they work on linux not in windows
so plz if u make that point more clear or at least post some pictures..
2-
does any official room will work .or it must be the exact cid room.
Click to expand...
Click to collapse
how come i cant find XdaDevelelopers-NbfUtils package?
i have added the repository correctly.
i can see from the status screen:
Synchronizing Database ...
Downloading ActiveState Package Repository packlist ... done
Updating ActiveState Package Repository database ... done
Downloading itsme packlist ... redirect
Downloading itsme packlist ... done
Downloading itsme Win32-API-0.41WJ PPD ... done
Downloading itsme XdaDevelopers-CompressUtils PPD ... done
Downloading itsme XdaDevelopers-NbfUtils PPD ... done
Downloading theoryx packlist ... not modified
but i just can find the module (ie. XdaDevelopers-NbfUtils)
i have also tried the command line installation but no luck..
anyone??
maybe someone can post the perl folder, with the required modules installed?
Do you have "All Packages" chosen through View Menu?
klikman said:
how come i cant find XdaDevelelopers-NbfUtils package?
i have added the repository correctly.
i can see from the status screen:
Synchronizing Database ...
Downloading ActiveState Package Repository packlist ... done
Updating ActiveState Package Repository database ... done
Downloading itsme packlist ... redirect
Downloading itsme packlist ... done
Downloading itsme Win32-API-0.41WJ PPD ... done
Downloading itsme XdaDevelopers-CompressUtils PPD ... done
Downloading itsme XdaDevelopers-NbfUtils PPD ... done
Downloading theoryx packlist ... not modified
but i just can find the module (ie. XdaDevelopers-NbfUtils)
i have also tried the command line installation but no luck..
anyone??
Click to expand...
Click to collapse
Hi there! I also have a bricked Herald. I'm in Brazil and a store wants around 200 US dollars to fix the phone and it's too high.
I saw that the file itsme XdaDevelopers-NbfUtils PPD has just a text indicating an e-mail adress.
I saw in another site that this file has another content.
May be this is why we cannot find the package to install.
If i find a way to fix my Herald here i will do a very good donate!!
Thanks,
Alencar
alencarfr said:
Hi there! I also have a bricked Herald. I'm in Brazil and a store wants around 200 US dollars to fix the phone and it's too high.
I saw that the file itsme XdaDevelopers-NbfUtils PPD has just a text indicating an e-mail adress.
I saw in another site that this file has another content.
May be this is why we cannot find the package to install.
If i find a way to fix my Herald here i will do a very good donate!!
Thanks,
Alencar
Click to expand...
Click to collapse
Go to this thread, it will explain how to fix your phone....
http://forum.xda-developers.com/showthread.php?t=345411
Hi Mkoz,
Tried your procedure but when start bootloader it do not read the SDcard. I copied Heradiag to the card but it do not run. The bootloader remains the same as before.
No Signal. With MTTTy I gave the command set 32 1 and get the message:
================================================
+ SD Controller init
- SD Controller init
+StorageInit
SDInit+++
PL_SDSetSlotNumber() - MPUIO_SDIF_SEL1=0, MPUIO_SD_IF_SEL=0
SDCmd8 Command response time-out. MMC_STAT = 80
SDCmd8 Command response time-out. MMC_STAT = 80
SDCmd8 Command response time-out. MMC_STAT = 80
SDInit - SD ver1.0
SDCmd1 Command response time-out. MMC_STAT = 80
SDCmd1 Command response time-out. MMC_STAT = 80
SDCmd1 Command response time-out. MMC_STAT = 80
SD clock to 24MHz
***** user area size = 0x79280000 Bytes
SDInit---
SDInit OK
Unlimited time!
GetDeviceCID: Error - InitDecoder
g_cKeyCardSecurityLevel = 0
HTCE
=======================================================
So, please could you help me ? Thanks! Alencar
Hi,
Where did you format your SD card before preparing Goldcard? In Windows Mobile device or in laptop or PC card reader?
alencarfr said:
Hi Mkoz,
Tried your procedure but when start bootloader it do not read the SDcard. I copied Heradiag to the card but it do not run. The bootloader remains the same as before.
g_cKeyCardSecurityLevel = 0
So, please could you help me ? Thanks! Alencar
Click to expand...
Click to collapse
Hi Mkoz,
I formatted using Pocketmechanics in my HTC universal in mode FAT32.
I'm really looking forward to see the mobile working.
Thanks!! Alencar
please SIR how can i change cardid ?
and witch tool i use ?
Hi,
I've sent you my private message but you haven't answered so I have to ask you in this thread:
- What is the size of your SD card? I successfully tested it with 512MB and 1GB cards.
alencarfr said:
Hi Mkoz,
I formatted using Pocketmechanics in my HTC universal in mode FAT32.
I'm really looking forward to see the mobile working.
Thanks!! Alencar
Click to expand...
Click to collapse
Sucessfully tested with 2gb card
BTW, HardSPL'd devices doesn't want to load heradiag!
i can see from the status screen:
Synchronizing Database ...
Downloading ActiveState Package Repository packlist ... done
Updating ActiveState Package Repository database ... done
Downloading itsme packlist ... redirect
Downloading itsme packlist ... done
Downloading itsme Win32-API-0.41WJ PPD ... done
Downloading itsme XdaDevelopers-CompressUtils PPD ... done
Downloading itsme XdaDevelopers-NbfUtils PPD ... done
I found -Crypt-DES but not found -XdaDevelopers-NbfUtils
Please help me! Thanks
same here
already try restarting my windows still no luck
I guess you are doing something wrong because there are people who were successful with this tutorial. Maybe you don't have "All packages" chosen from the menu.
I have updated point 4 of my tutorial so please take a look.
I've also posted in this thread my answer to someone who had the same problem like you and he didn't answered anymore so I guess as a result he created Goldcard successfully.
If it will help you, please let us know.
TINDUNG10 said:
i can see from the status screen:
Synchronizing Database ...
Downloading ActiveState Package Repository packlist ... done
Updating ActiveState Package Repository database ... done
Downloading itsme packlist ... redirect
Downloading itsme packlist ... done
Downloading itsme Win32-API-0.41WJ PPD ... done
Downloading itsme XdaDevelopers-CompressUtils PPD ... done
Downloading itsme XdaDevelopers-NbfUtils PPD ... done
I found -Crypt-DES but not found -XdaDevelopers-NbfUtils
Please help me! Thanks
Click to expand...
Click to collapse
please help me delete 1 post
Hi !!
I'm sorry if I write about talking before but I search for 2 dayes internet (Most link coming from xda ) without success.
I'm pretty sure that is not possible to do on Trinity due to bootloader limitation but I want a last confirm before to flash my device.
My boot loader is a Des' Crash-Proof SPL:
TRIN100
IPL-0.50
TRIN100
SPL-9.99 CP
After I play with the WM6 registry it don't load th OS after reset.
I wondering if is it possible to dump the ROM (The mass storage part) to mount in a linux box from the boot loader.
I read that the Trinity lack of the s2d command and also the rbmc didn't work.
There is any other way to do it
Off course I can't use pdocread.exe due to the OS is not loaded on the Trinity.
Thanks in advance and sorry for my english.
Carlo.
Hi again.
I was able to read ROM whit the rbmc command using the follow command:
password BsaD5SeoA
set 1e 1
task32
rbmc >/tmp/dump.bin 0x3100 0x17900
The problem is that the output is show on the screen and not writed in the file.
I tried on linux using HTCFlasher and mtty on WIndows whit the > and without.
Any Idea ?
Carlo
Try QMAT too, although it's not meant to be used with Trinity, it supports rbmc dumping.
Thanks, I'll try it tonight.
Here's an rbmc partition dumper I've created for dumping os, storage and ext rom. Storage partition doesn't seem to be readable this way...
You need to have a security unlocked device or HSPL that allows rbmc when device is not security unlocked.
Hope this helps...
Thanks for the command, I tried and it don't work.
I have the Des' Crash-Proof SPL on my Trinity and the rbmc command work but I have to give the follow commands before use it.
password BsaD5SeoA
set 1e 1
task32
is your command supplied it before to dump or there is any command line option to pass it to the command ?
Works on my trinity allright... task 32 is not required, btw.
Did you manage to get QMAT working/dumping?
I tried more times but I have allways this message:
C:\Temp2>rbmc.exe
HTC RBMC reader version 1.0, Dec 19 2008
Reading OS.nb...
WARNING: rbmc OS.nb command failed!
Reading Storage.nb...
WARNING: rbmc Storage.nb command failed!
Reading ExtROM.nb...
WARNING: rbmc ExtROM.nb command failed!
Read 0xC1B144 bytes in 0d:00h:00m:01s.953ms
HTCSBye!>.L.HTCE
I switch the Trinity to the bootloader screen and then I plug the usb and ru the command with no args.
Where I wrong ? I tried without ActiveSync open and with it opne with the usb connection disbled.
No, I was unable to use QMAT, the manuals is little different from the version and don't explain the very first operation to recognise the PDA to the program.
Instend I was able to capture the rmbc output on my linux box and minicom on usb but I get error after a while the program is dumping (The same I got on the screen using mtty) and then I'm little confusing about partition dimension showed by the "info 8" command
Bye.
What happens when you manually issue "rbmc c:\temp\os.bin OS" in mtty or minicom?
I start minicom with the capture option active then I use the command
Cmd>rbmc a 0x3100 0x17900
Then the dump start
Cmd>rbmc a 0x3100 0x17900
GetExtRomData+(): *pszPathName=a, dwStartAddress=57600000, dwLength=8C08DAA0
:F=a :A=57600000 :L=8C08DAA0 :rbmc= HTCS¼Ñÿÿùÿ0ÖÿÿùÿRPQQ"RTP¤QP>Öÿÿùÿ¤ìÿÿùÿÔÿÿùÿ9Öÿÿùÿ<Öÿÿùÿ=Öÿÿùÿina
condominiale
[.....]
,(*"(B+&*0ùÿNANDFlashReadSectorWithSectorInfo: dwBlockIndex=0x400
NANDFlashReadSectorWithSectorInfo: Address over boundary!!!
rbmc: read data error at 0x8000000
In the [...] I got about 1 MByte of data.
My I was to dump th user partition to recover same data, not the OS.
This syntax is not valid:
rbmc a 0x3100 0x17900
1. Do not use 0x prefix for offset and length
2. Use actual flash offsets (starting at 50000000 (hex))
Can you try this exact command?
rbmc c:\temp\os.bin OS
This is the command rbmc.exe executes and it seems to be failing on your Trinity.
I tried and that is what I had:
C:\temp>rbmc c:\temp\os.bin OS
HTC RBMC reader version 1.0, Dec 19 2008
Reading OS.nb...
WARNING: rbmc OS.nb command failed!
Reading Storage.nb...
WARNING: rbmc Storage.nb command failed!
Reading ExtROM.nb...
WARNING: rbmc ExtROM.nb command failed!
Read 0xC1B144 bytes in 0d:00h:00m:02s.031ms
HTCSBye!>.L.HTCE
C:\temp>
cybor said:
I tried and that is what I had:
C:\temp>rbmc c:\temp\os.bin OS
HTC RBMC reader version 1.0, Dec 19 2008
Reading OS.nb...
WARNING: rbmc OS.nb command failed!
Reading Storage.nb...
WARNING: rbmc Storage.nb command failed!
Reading ExtROM.nb...
WARNING: rbmc ExtROM.nb command failed!
Read 0xC1B144 bytes in 0d:00h:00m:02s.031ms
HTCSBye!>.L.HTCE
C:\temp>
Click to expand...
Click to collapse
Can you do it in mtty?
Ok, sorry, I missunderstand.
Cmd>password BsaD5SeoA
Pass.
HTCST ÚÈÒHTCEPassWord: BsaD5SeoA
Cmd>set 1e 1
Cmd>rbmc c:\temp\os.bin OS
Command error !!!
Ok, it looks like your SPL doesn't support rbmc command, but if you do "rbmc 50000000 1" in mtty that works?
Yes, it work.
Cmd>rbmc 50000000 1
GetExtRomData+(): *pszPathName=50000000, dwStartAddress=1, dwLength=8C08DAA0
rbmc=8DAA0
Cmd>
But it work only if I supply the "task 32" command after the "password .. " and "set 1e 1"
Colud you modify your command to supply the "task 32" command, maybe by a switch ?
Finally it work !!
I mean your command.. after the message before I tried this way.
I connect to the bootloader with the patched version of TeraTerm (To have the copy and paste function ), then I supply the three commands like the message above and finally I close the Teraterm and lunched your command with no parameters and here what I get:
C:\Temp0\rbmc>rbmc.exe
HTC RBMC reader version 1.0, Dec 19 2008
Reading OS.nb...
0x4d50800 bytes read
Reading Storage.nb...
WARNING: rbmc Storage.nb command failed!
Reading ExtROM.nb...
WARNING: rbmc ExtROM.nb command failed!
Read 0x55628D8 bytes in 0d:00h:02m:02s.125ms
HTCSBye!>.L.HTCE
How you can watch it don't read the Storage.nb and the ExtROM.nb, but now I can get OS.
So I think that the "task 32" is mandatory in with the HardSPL I got in my Trinity.
Witch HardSPL do you use for test your command ?
cybor said:
So I think that the "task 32" is mandatory in with the HardSPL I got in my Trinity.
Witch HardSPL do you use for test your command ?
Click to expand...
Click to collapse
Yeah, well, this seems to be the way HardSPL works, you only get access to locked commands after faking security lock status with "task 32". I've added this command to rbmc.exe, however I want to make it more generic before I post the updated version, because dumping storage doesn't work so far.
I'm using MFG SPL 1.05 patched to allow rbmc, this shouldn't be relevant though.
Ok, so attached is an updated version of rbmc.exe.
It will work just like the old version without any parameters, but you can specify the same parameters as you would feed to rbmc command too now.
E.g. to dump storage you can do
C:\>rbmc.exe storage.bin Storage
However due to a bug in SPL this won't work, it will produce an error message showing the starting offset of storage partition though.
Grab that offset, substract it from 0x60000000 to get the correct storage size and rub rbmc.exe again with parameters:
C:\>rbmc.exe storage.bin 0x53540000 0xACAC0000
You should have a dump of storage partition (albeit not excatly 0xACAC0000 bytes) in storage.bin file as a result. Note that resulting dump has NAND flash block status data (0x10 bytes every 0x200 bytes) that you may need to strip to get an image of storage partition you can work on.
Good luck!
Thanks for this new realese, it work fine.
I have a problem to understand how to calculate the offset.
When I run
rbmc.exe storage.bin Storage
I get:
Dumping rbmc storage.bin Storage to storage.bin...
ERROR: rbmc storage.bin Storage command failed; last message:
"Storage address error.(0x54DC0000, 0xB301000) "
What I must subtract from 0x60000000 to get the offset and which is the other value in the last example you write.
C:\>rbmc.exe storage.bin 0x53540000 0xACAC0000
I'm sorry to waste your time, but I tried to understand but I fail, but I want to reach the end because in future a tool like this will be very usefull to recover data froma crashed Trinity.
09/01/2012:
this tutorial may work for those who are having encryption issues on ics or jb roms (the error is related to mmcblk0p2(data))
well, after some months of work, here´s an tutorial about how to fix the mostly common sdcard issues.
1º Of all :***Be sure of what you´re doing,or else you can corrupt the partition table of you sdcard/brick your phone,and I´ll not be responsible of it***
2º-Do Not send me PMs, post here so everyone that have the same problem can now how to fix it.
3º-If you are an starter, you can post here your questions,but be sure that you haven´t found answers on Google or other threads.
and 4º-Read ALL topic before start and try one solution than the other,they´re in order of difficulty and risk of get an "permanent" brick.
0 - Always backup your EFS folder, maybe its not related to this thread but it´s also very important to remember.
I -If you have a folder called "voodoo" in your sdcard, you may have voodoo enabled on your ROM, so be sure of disabling it before trying a new rom or a stock rom.
if you´re on another rom already and having problems in mounting partitions, try to flash you last rom or a kernel that supports voodoo and it´s compatible with your new rom.
II-If you´re getting problems in mounting DBDATA,Download a full rom that contains DBDATA to flash with odin(or only flash dbdata,but you´ll have to do a full wipe later). To see if it haves dbdata.rfs by opening your .tar file in 7zip or others.
III-If you´re getting Can´t mount data (dev/block/mmcblkl0p2) File exists, try to flash an kernel with voodoo suport,if it still the same, format data in the menu of your recovery.
IV-If you´re getting can´t mount sdcard (/dev/block/mmcblk0p1)File exists, try to access it via ADB and send pull file command to recover your files(must have root),if you could do that, so try to format it via recovery.If not work,Download gparted, burn it on cd (it´s an CD with a tool of linux) and go to ADB shell to run this command:
su
echo /dev/block/mmcblk0 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
now
reboot your PC in gparted and format mmcblk0p1(it´s the first partition) in FAT32.
Done
V-If you´re getting cant mount sdcard (/dev/block/mmcblk0p1) with (invalid argument) You can try the fix IV and see if it works,if not, proceed to VI.
VI-If you´re getting cant mount data(dev/block/mmcblk0p2) or can´t mount sdcard (/dev/block/mmcblk0p1) with (invalid argument) or (no such file or directory) you may have to do this:
***search on google for 'fdisk' commands first***
You MUST*¹ remake your partition table manually,so the phone have the /data partition back to boot.
*¹
In some cases you can use gparted to do this, without doing it manually,
you shoud only mount mmcblk0 before.
you can run this command line on adb shell to mount it:
echo /dev/block/mmcblk0 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
You Will have to format it and it MUST have the partitions as said below.
YOU SDCARD MUST HAVE THE FOLLOWING PARTITION TO BOOT ON AND RECOGNIZE INTERNAL SDCARD:
/dev/block/mmcblk0p1
AND
/dev/block/mmcblk0p2
Start:
Open ADB,comnect your phone and proceed.
run adb shell
su
fdisk /dev/block/mmcblk0
p (you should see your partition table,POST HERE BEFORE CONTINUING)
YOU ARE NOW ABOUT TO REMAKE YOUR PARTITIONS:
partition 1 will correspond to mmcblk0p1(SDcard) and partition 2 will correspond to mmcblk0p2 (DATA)
**DO ONLY AS I SAY HERE, UNLESS YOU MAY GOT I/O ERROR ON YOUR SDCARD AND ITS ALL OVER. I say because it happened to me and i had to dissolder the internal sdcard an use only the external.**
**********IF YOU DONT HAVE ANY IDEA OF LINUX COMANDS: DO NOT PROCEED !!!!!!!!!*************
tap on adb:
n (will create a new partition)
1 (partition number)
press enter on keyboard so it selects the first block
get a calculator and estimate the size of the partition 1.IT MUST HAVE around 2GB left.
write the block number you got in calculator(BE SURE OF WHAT YOU TAPE HERE)
t
b (partition 1 is done and formatted as fat 32)
Now again:
n
2
enter on keyboard
enter again so it select the last block
(DO NOT TYPE COMMAND "T" FOR PARTITION 2, IT BY DEFAULT SET TO LINUX EXT FORMAT)
p (you will see you new partition table)
****IT MUST HAVE 2 partitions, partition 1 is in fat 32 format and partition 2 is in linux format(AND MUST HAVE AROUND 2GB)****
w (IT WILL WRITE YOU NEW PARTITION TABLE ON YOU SDCARD,SO BE SURE IT's ALL CORRECT)
Done,
now tap:
q
fdisk /dev/block/mmcblk0
p (you should see your new partition table, if ok reboot your phone, flash an stock rom for vibrant (I sugest an T959UVJFD ROM only to correctly format your partitions),root it,backup it,and enjoy,You can put a custom rom if you want so.)
If You have an error That does not appear here and you think it may me related to you sdcard just ask. In one or two days I or others developers may post here a possible solution.
Thanks For Google and some XDA users who indirectly helped me doing this.
You can try Paragon Hard Disk Manager in place of gparted
but remember: mmcblk0p1 is FAT32 and mmcblk0p2 in EXT2 (in truth it´s not EXT2, its in rfs, but the stock rom T959UVJFD is the only that I have absolute sure that will do the conversion).
Sorry for my bad english, it´s not my native language.
Great post doiiido!
Hay doiiido, you have been thanked and this post has been added to the [REF][KERNEL] ✰ The Official Vibrant Kernel ßible Thread ✰ → 07/05/12.
Great post!
News
Original pos by: ferhanmm
link to it:
http://forum.xda-developers.com/showthread.php?t=1665123
[FIX] Data wipe error or Can't mount /dev/block/mmcblk0p1
Data wipe error, Can't mount /dev/block/mmcblk0p1, or Vibrant screen boot loop even after flashing stock odin JFD phone will not boot. Phone will only boot Eugenes JK2 but internal and external storage will still list as corrupted and Lists 0.00 MB in storage.
Internal storage has been destroyed, I’ve been able to fix a phone using this technique to be mostly working. The external SD card will always have to be in the phone for this to work.
1. Partitioning the MicroSD Card
Get an 8gb(or larger) micro sd card. Class 10 would be better here. Put it into a Card Reader, then run Gparted.
Gparted (usb method is easiest) - http://gparted.sourceforge.net/liveusb.php
Using Gparted, delete everything else and create 2 partitions and :
6000mb FAT32 as PRIMARY
1607mb(remainder) Reiser as PRIMARY
2. Flash to Stock
Open up Odin flash stock JFD with pit file and repartition checked.
After phone boots completely, power off.
3. Flashing CM9
Take MicroSD out of phone an put it in pc, then copy update.zip, GAPPS, Cyanogenmod Rom all to the FAT32 partition that we created earlier. In Windows it should show up where all of your drives are listed in.
update.zip (https://www.dropbox.com/s/ju5eg5ernxcaqpt/update.zip),
GAPPS (http://www.goo-inside.me/gapps/gapps...317-signed.zip)
CyanogenMod Rom Zip(http://download.cyanogenmod.com/get/...mtd-signed.zip)
Enter recovery mode with volume buttons and power.
Reinstall packages twice.
Install zip from sd card select update-cm-9-20120520-nightly-vibrantmtd-signed.zip phone will boot loop on vibrant screen so take out the battery then enter recovery a second time installing the cm9 update again.
Then flash Gapps zip the same way.
When phone boots up camera, and gallery will not work until the next step.
4. Edit Vold.Stab file
Downlad ES File Explorer from play store.
Hit Menu button, settings, Check box for Root Explorer, Check box for mount file system, check box for Up to Root
Press Up once, you should now be at "/"
Open system directory, open etc directory, scroll to bottom and select Vol.fstab, select Text, Select ES Note Editor, update text to the following:
#internal sdcard dev_mount emmc /mnt/sdcard 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0
#external sdcard dev_mount sdcard /mnt/emmc auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
After edits, click back and click yes to save changes. Exit out of es file explorer and restart phone. Post results:
Should work with any version of CM9, newer nightlies would obviously be preferred. Will make more detailed guide soon.
Credit to these guys for providing the solution -
http://www.youtube.com/watch?v=zdMhYYdMB08
http://forum.xda-developers.com/show....php?t=1447303
Samsung Vibrant
News
Original post by:
draikz
Link to original post:
http://forum.xda-developers.com/showthread.php?t=848737
** [GUIDE] FIX AND RESCUE YOUR VIBRICK + ODIN SUPPORT! N00b Friendly **
Fixing so-called "Bricks"/Odin Errors
This guide is open to contribution/editing/correcting
I DO REALIZE THAT MOST OF THESE LINKS ARE BROKEN, PLEASE SCAN THE THREAD TO FIND UPDATED LINK. I'M NOT VERY ACTIVE ANYMORE, SORRY!
-----------------------------------------------------------------------------------------------------
BOOT CYCLE
This is where you get the annoying Samsung Screen/Galaxy S screen.
DOWNLOAD REQUIRED (CREDITS TO JUSTANOTHERCROWD):
Quote:
Originally Posted by justanothercrowd
JFD ODIN Images from Samsung (PDA)
www.justanotherdev.slackdev.com/T959UVJFD.tar
MD5:632730f6b637f53e5b10e5cbc8b966a7
512 PIT File (PIT Extract first!)
www.justanotherdev.slackdev.com/s1_odin_20100512.rar
MD5:b5628c8e183fdd8f4c703321ca40e33a
ODIN
www.justanotherdev.slackdev.com/Odin3.rar
ALL 3 Files plues the root update.zip
http://tinyurl.com/2bc5b6r
thx to KopyKatKiller
1. Get into Download Mode (WITH THE PHONE PLUGGED IN) by following the steps below
*Turn off the phone until you get to the charging battery screen (keep in mind, your phone is currently PLUGGED IN)
*Press volume up and down, and power all at once.
*As soon as the screen turns black, release your power button.
2. Unplug phone from USB
3. Open Odin (in Administrator if you're running W7 or Vista), try one of the ones I attached to this post, at least one of them is bound to work, some don't work for me, but works for others, some doesn't work for others, but works for me, whatever floats your boat
4. Load in the files into Odin that you have downloaded from above Just load in the files corresponding to the text field.
DO NOT CHECK REPARTITION.
5. Plug in your phone with the DL mode
6. Click start and wait for the magic
-----------------------------------------------------------------------------------------------------
NO-BOOT PHONES
This is where your phone does NOT turn on, no combo of buttons works and power button does nothing.
DO THIS ONLY WHEN YOU PLUG IN YOUR PHONE AND NOTHING SHOWS UP ON THE SCREEN!!! If else, follow the steps from above.
This method is basically same as above, EXCEPT the way you get into Download Mode as your phone is HARD BROKEN.
1. Download all the files required in the "BOOT CYCLE" section of this post.
2. Remove everything from your phone (SD card, sim, battery).
3. Plug your phone into your computer WITHOUT the battery, as you have already taken it out in the last step.
4. Press and HOLD vol. up and vol. down.
5. As you are HOLDING these buttons, reattach your battery.
6. You should be in Download Mode.
7. Unplug phone from USB
8. Follow steps 4-8 from the "BOOT CYCLE" section.
Troubleshooting:
-Odin stuck at some random process?
*Switch to another odin
*Make sure you did NOT check repartition, if you did, just repeat all the steps over again, except for the downloading parts, obviously.
-Phone not responsive?
*Try "NO-BOOT PHONES"section of this guide
-Phone stuck at Galaxy S logo screen?
*Put it in to DL mode, and run Odin again, it's just a bad install.
-All three ODIN is nonfunctional, stuck or giving "FAILED" errors?
*DO NOT CLOSE ODIN ONCE IT HAS FAILED!
*Unplug your phone
*Replug in your phone, get it into DL mode
* Unplug once it is in DL mode
*Replug and ODIN should recognize your phone
*Leave all the settings the same, then click "Start" again.
-Cannot get into download mode using the method I listed? Use the method(s) below:
Soldering Method
More methods coming soon
-----------------------------------------------------------------------------------------------------
I know how much of a pain posting in the Q/A section can be and the wait time is pretty bad, so if you need help regarding UNBRICKING and ONLY UNBRICKING feel free to post in here.
Hope you enjoy, this is my first guide, please don't flame. Any comments or suggestion is suggest, or if you have your own method I'll also post it
POST YOUR RESULTS!
-Steven
The only forums this guide should be posted on is XDA, DZ, and PHANDROID under the username DRAIKZ and EXPLOSIVE. If it helped you, feel free to donate a coke or two!
Hello!
This is my first time posting, i normally am able to solve problems by looking through the forums, but this time not so i created an account and posted.
Any help that could be offered would be greatly appreciated.
The Story:
I have had the nook for around a year running CM7 or CM9, and last semester i took a programming class and programmed apps for android and ran them on my nook. i got acquainted to adb and am somewhat familiar with it. i remember when i started the serial number which adb used to Id the device was normal, but then around halfway through it simply became a string of zeros. so that is when the device lost its serial number I assume. Sadly this is not the main issue.
A week or so ago i was attempting to return my nook back to the stock Rom, and got it booting fine but it would not register because it was missing the serial number and Mac address. I looked through the forums and tried to fix it. i figured out it was stored in partition 2. looking in to it i could easy reflash other roms and they would work fine, and i tried restoring an old backup i had, which did not fix the problem ( i didn't think they affect that partition at all). eventually i stumbled upon lepinars repair partitions zip, and with nothing else working, i flashed the repair partition 2 zip in hopes the backup from partition 3 would have the correct serial number in it and restore the serial number. This put my device in a recovery bootloop. i am able to boot into cwm and talk to the device over adb, and i can flash new roms, but it will ONLY boot into recovery, no matter what rom it is ( i have tried CM7, CM9, sdcard install of CM7, and stock 1.0.1) . i figured out that it is because of a file on the mmcblk0p2 which i think was BCB, but there might be some other things affecting it.
So now you know what has happened, can anyone help me? I would like to get a Rom to boot into the normal mode, and then restore serial number / mac address so that it could be registered.
Once again, Thank you so much.
The problem is that without a valid serial number on partition 2, no rom will boot even if the recovery flag is set properly. It will just keep going to recovery.
If you have adb working, look at p2 and see if you have a devconf folder. If you do, look in it to see what files are there. There should be simple text files that have data in them. Like SerialNumber that has a 16 digit serial number in it (but the file is 17 bytes long so must have a linefeed on the end.) MACAddress is another, with a 12 digit number and no linefeed. 17 files total. All of them with rw-rw---- permissions.
Those files are usually backed up in partition 3 in a file named rombackup.zip. Unzip that zip manually and place them all in the devconf folder in partition 2. Set permissions as above.
Also you said you flashed my repair zip. Did it give you the message that it completed successfully? I have it set to abort if everything is not right.
Edit: Your serial number is stamped on the little flap that covers the micro SD card. It is also on your box the NC came in. If you cannot find the SerialNumber file in the backup zip, you could try manually creating it and putting in the right place.
Thanks. A week ago i was more familiar with this because i had just done a day or two of reading, but sadly a bit has slipped my mind.
ADB is working just fine when i boot into CWM, but i am having trouble finding partition 2. For some reason I recall a rom folder on the root level, but when i do an ls while in adb shell, all i see is this:
boot etc sd-ext
cache init sdcard
data init.rc sys
datadata proc system
default.prop res tmp
dev root ueventd.goldfish.rc
emmc sbin ueventd.rc
more random info still in adb shell)
when i do an fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 965 7301542+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 236 979933+ 83 Linux
/dev/block/mmcblk0p7 237 281 361431 83 Linux
/dev/block/mmcblk0p8 282 965 5494198+ c Win95 FAT32 (LBA)
just in case any of that helps.
i have heard of partition two being /dev/block/mmcblk0p2 but that is not a directory, or at least it appears so to me and i cannot get any files from it. I recall when the nook was booting fine i did look into the rom folder and the serial number was there and was correct, but in the settings/about Tablet it was simply a string of zeros.
when i try to pull the rombackup.zip from p3, i get the error message "adb pull /dev/block/mmcblk0p3/rombackup.zip
remote object '/dev/block/mmcblk0p3/rombackup.zip' does not exist" , so i am assuming i am barking up the wrong tree there.
when i flashed the repair zip there were no error messages and i am fairly certain it completed successfully as i was not alarmed and simply tried to reboot it as normal. after I flashed the repair zip it would not boot into anything but recovery, and this is when the more serious issue ( it seems to me) arose.
I probably am simply doing something wrong here, still the same situation on my end.
you have to mount the partitions...
rom should have been automatically mounted to /dev/block/mmcblk0p2 but you can try to manually do it:
adb shell busybox mount /dev/block/mmcblk0p2 /rom
adb shell mkdir /backup
adb shell busybox mount /dev/block/mmcblk0p3 /backup
adb pull /backup/rombackup.zip
unzip rombackup to a folder..
push the files to /rom/devconf
DizzyDen -
Thank you for telling me about the partition mounting. this explains a lot.
i had to create the /rom folder as it was not there. when i mounted it and did an ls -a command, in /rom there was only a BCB file. in /backup there was only factory.zip and an empty folder called lost+found. so there was no rombackup.zip for me to pull and extract.
sert57 said:
DizzyDen -
Thank you for telling me about the partition mounting. this explains a lot.
i had to create the /rom folder as it was not there. when i mounted it and did an ls -a command, in /rom there was only a BCB file. in /backup there was only factory.zip and an empty folder called lost+found. so there was no rombackup.zip for me to pull and extract.
Click to expand...
Click to collapse
That probably is why my repair failed. Try creating the SerialNumber file I mentioned in my last post and put it in the folder devconf. You may have to make that directory first. Mkdir /rom/devconf.
leapinlar said:
That probably is why my repair failed. Try creating the SerialNumber file I mentioned in my last post and put it in the folder devconf. You may have to make that directory first. Mkdir /rom/devconf.
Click to expand...
Click to collapse
I successfully created the file SerialNumber and it was 17 bytes, i moved it to /rom/devconf and looked at its permissions, and for some reason a chmod wouldn't let me remove rwx from others and x from user and group, so the permissions were rwxrwxrwx (not sure if this would create an issue). i tried to re-install the repair zip. the text displayed is
(after finding, opening, and installing update)
Repair /rom partition (P2)
found /factory - be patient this could take a while
Done.
This is the same message i received earlier when i did this. so no failure message but i guess it aborted or something. After this is done the devconf folder is gone. rom is still there and i mount it, and once mounted the only file in Rom is the BCB file.
I did some testing and the SerialNumber file by itself is not enough to get it going. There are 16 others and one or more may be critical. I will keep playing and see if I can find which one it needs. I don't know why you don't have that backup file. It is really critical. I modified my partition 2 zip to give a little more information to the user.
Edit: I did some more testing and it booted only to recovery when I removed a file named BootCnt. It is a file with four bytes in it which are all null (00's). Try making one and pushing it to /rom/devconf and see if it will boot. There is also another file named BootCount also with four null characters, but it is still there and it is not booting to the rom. I think that is the one for 8 failed boots. (When I rebooted again it was ok, that file was back).
Edit2: I think I found it. There is a file named DeviceID that is identical to the SerialNumber file. When I delete that file it will no longer boot to a rom, only recovery. Try putting that file in /rom/devconf. I deleted everything in that folder but BootCnt and DeviceID and it booted to the rom.
Thank you so much!! The nook is finally able to boot successfully to a ROM. Major problem finished! I was originally intending to return it to stock, but I am not sure if that is now possible as I am missing all but 2 of the very important files. I'll give an update when I get closer to getting stock back. Hopefully it will work, but we will see. Thanks for helping me get at least this far.
I have a CWM flashable 1.4.3 stock zip here:
http://d01.megashares.com/index.php?d01=CiYdDmP
sert57 said:
Thank you so much!! The nook is finally able to boot successfully to a ROM. Major problem finished! I was originally intending to return it to stock, but I am not sure if that is now possible as I am missing all but 2 of the very important files. I'll give an update when I get closer to getting stock back. Hopefully it will work, but we will see. Thanks for helping me get at least this far.
Click to expand...
Click to collapse
I .have a complete recovery.zip file available when I get my PC monitor working again... complete with infllo about what files are edited... and how to edit them
I think they are in my deposit files share
That would be spectacular if you could provide that. I'm still attempting leapinlars download ( 3 failed times, WiFi here is VERY slow right now). Let you know what happens.
So I installed 1.4.3 to the nook. it got stuck at the silver n screen, so i did a volume up, power, and n button reset. after this it reset to factory and intalled an update. it booted sucessfully to the stock firmware. now when i try to register it it is missing the model number and mac address. im assuming i am just supposed to create the two files for the nook and place them in /rom/devconf. Could some more assistance be had for me about what goes into the files and such? Mac address has been missing since the problem began, so that is nothing new, but this is the first time ive booted to stock that model number was not there.
Model number is BNRV200 in ModelNumber. Product ID begins with P11 and ends with a linefeed and is 11 bytes total in ProductID. Event Type is Manufactured in EventType. Date manufactured is just a date. Mine was 01/29/2011 in DateManufactured. Device attribute is New in DeviceAttribute for me. MAC address is a 12 digit number in hex in MACAddress. Main board serial number is a 12 digit alphanumeric number in MainboardSN. Mine starts with QI11M. Backlight is a 6 digit alphanumeric number in backlight. Mine is 1476AY. Ean is a 13 digit number in ean. Mine starts with 97814005. There is an empty Platform file. There is BootCnt and BootCount, both with four nulls (00). There is a SerialNumber file identical to DeviceID. There are three other files. WiFiBackupCalibration with 468 bytes, PublicKey with 333 bytes and HashOfPrivateKey with 28 bytes.
Some of these you can make and some you can put phony info in them. Others, I don't know.
Could you provide more info on obtaining the Mac address and how to write it? After that I should be good, but we will see.
[edit]
install cm7.2 and it was in the settings, so i copied it down and put it on the device. reverting back to stock, i will see if it takes. i am assuming by your description the semicolons are not placed in the MACAddress file, so i did not do it.
[edit2]
looks like all i need is the hashprivatekey. when i went to the factory area a few were null, but that one said Not Okay. is there any way i can create this file? i tried registering but it would not, so i am assuming this is needed.
Unblock your private messaging on XDA. I want to send you a message. Or send me a private message with your email address in it.
Sent from my NookColor using Tapatalk
ok. it boots fine. when i register it will not let me, with the typical error, i look into the details and everything is green except battery percentage (which is low) and username which is nonexistant. when i check the factory tab it says that the battery type and backlight are !null, so i dont thing that would affect it. besides that i have everything.
One more thing to try. You can reset some of your settings like wifi calibration, etc by following this procedure. It may just re-populate some of those files in devconf. Use the one that resets things. Back up devconf first though.
http://nookdevs.com/NookColor_Factory_Mode/Skip_Out_of_Box_Experience
done that a few times. it doesnt really do anything but erase known wifi networks. would the fact its missing battery type and backlight mean anything for registration?
I would not think so. But I have a Nook Tablet that has different things in devconf, like BatteryType is MCNAIR and Backlight is 070B16730338ZN4AC15-4J8D6Y01577C5. (Notice it has a capital B in the name. I think I made a mistake in the earlier post.) The Tablet I think has the same screen as the newer Nook Colors.
This thread is part of customizing the Windows Phone OS or ROM, which includes altering of the target files and no nothing else. Do not go sideways on this tutorial as you might brick your phone. PLEASE TAKE RESPONSIBILITY. I am not responsible to any damage caused by this tutorial. Also, do this if you want to personalize your device.
CUSTOMIZING THE OEM BOOT SPLASH IMAGE WITH SOMETHING HILARIOUS OR EPIC
What you need:
- Windows Phone Internals (for booting Windows Phone into Mass Storage Mode)
- Photo Editor <optional> (for editing the oem boot splash image. If you made one with as large as your phone's screen resolution, please disregard this)
- Administration Account (for DISKPART)
- CAUTIOUS MIND (of course)
- and a Windows Phone (obviously)
Procedure:
Getting Ready
1. Boot your Windows Phone into Mass Storage Mode. To do this, either shut down first your phone then boot it up whilst holding down the camera button (if any), or use Windows Phone Internals (https://wpinternals.org/) to boot into MSM manually. If you haven't unlocked the bootloader and enable root access yet, please do.
2. Using DISKPART, select the appropriate disk number from the list of disks (list disk) and do select partition 20 to select the target partition.
3. Then type in this command:
Code:
detail partition
This will show the default Partition Type ID. Save this GUID for a later step.
4. After saving to notepad or a sticky note, do:
Code:
set id=ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 (to make it read-and-write-able)
5. To assign the drive with a letter:
Code:
assign
Now your done with PART 1! Proceed for more.
The Main Thing
1. On the file explorer, go to PLAT Drive. Then edit the two files, namely: boot1.bmp, boot2.bmp. Make sure the photo is as big as the default screen resolution of your device. (e.g. Nokia Lumia 520 = Screen Resolution: 480x800) If you made custom ones already, replace them with no problems.
P.S.: Mostly recommended: 32-bit bmp image export setting (on Photoshop).
2. Once done, proceed to the next stage. Make sure no other files is altered. If the image format is different, a System File Integrity error may occur when you boot up the device after this procedure, causing it to display a black screen without letting you to boot it normally.
File Info:
Code:
******[BOOT1.BMP]******
This is displayed or splashed when the device is booted up from powered off state.
******[BOOT2.BMP]******
This is displayed right after the first one in 0.1 second delay. It is also shown after the "Charging on Low Battery" screen when it has enough minimal power to boot up normally.
Packing Things Up
1. Go back to Command Prompt. Set the Partition Type ID back to default by pasting in back the GUID code you copied in Stage 1 step 3.
2. After these steps, finally reboot your device to exit Mass Storage Mode.
3. You will eventually see the result when it boots up. Voila!
General Questions:
My device boots into black screen. What to do?
A: Make sure the Partition has these information:
Code:
File System: FAT12
Partition Type ID: <the default GUID, not the GUID given here>
Partition Size: 8 MB
If not, please fix those problems yourself.
Can I use an animated GIF instead?
A: Impossible. It only accepts bitmap-still images, not animated ones. This is because it is on a BIOS environment (maybe?).