SPLs for DREA100 & DREA110 (Orig, Eng, Hard) [updated 2009-05-12]
- Thread starter jashsu
- Start date
I don't see why not. You would need a copy of the original bootloader though.
As far as I know, no-one has packaged the original bootloader into a convenient fastboot image, or nbh file yet. But I don't see any reason it's not possible.
There isn't one. At least not yet. You have to use linux or mac. You can download vmware server and install ubuntu, and use fastboot from there to connect to your G1.
I have used linux to run fastboot...
When I execute "./fastboot devices", no devices showed and not any result
I think maybe the usb driver in windows is needed, so I installed vmware player to run a ubuntu vm, and I got the same result
So I really don't know how can I connect to my G1...
When I execute "./fastboot devices", no devices showed and not any result
I think maybe the usb driver in windows is needed, so I installed vmware player to run a ubuntu vm, and I got the same result
So I really don't know how can I connect to my G1...
Last edited:
I did this to my dream an it worked perfect,but someone tryed putting a AT&T Sim an it did'nt work. My Q: is what else does the dev 1 do that my phone does not do even with update installed?
of course you can put it back.
I'll make a NBH file that should flash it back.
Cool. Thanks
K
korndub
Guest
of course you can put it back.
I'll make a NBH file that should flash it back.
Thanks!!! we appreciate it!! would we just put the NBH on the sd card and fastboot?
of course you can put it back.
I'll make a NBH file that should flash it back.
Would it not be possible to make a NBH of the Engineering Boot Loader?
Just a thought.
How so? As long as the SPL isn't damaged, you should just be able to go back in and flash a different image.
cut out old spl from original nand dump
I took an entire nand dump and found where the spl started for the original bootloader. I saw how big the spl.bin is in the spl update zip file, took that many bytes out of my nand dump and I think I have an old_spl.bin now that can be put into a zip file for flashing it onto the phone... obviously would have to re-sign the package... anyone think this would be a good thing to have?
I took an entire nand dump and found where the spl started for the original bootloader. I saw how big the spl.bin is in the spl update zip file, took that many bytes out of my nand dump and I think I have an old_spl.bin now that can be put into a zip file for flashing it onto the phone... obviously would have to re-sign the package... anyone think this would be a good thing to have?
I took an entire nand dump and found where the spl started for the original bootloader. I saw how big the spl.bin is in the spl update zip file, took that many bytes out of my nand dump and I think I have an old_spl.bin now that can be put into a zip file for flashing it onto the phone... obviously would have to re-sign the package... anyone think this would be a good thing to have?
That would be cool. Did the dumping utility handle bad blocks?
sounds promising
Since you basiclly need a full dump with the start and end of the flash, now how to sneak it in on the OTA RC30s then use an JF RC30 .nbh file, I'm just theorizing as that is all I have the ability to do, besides testing sh1t like crazy.
Bhang
Since you basiclly need a full dump with the start and end of the flash, now how to sneak it in on the OTA RC30s then use an JF RC30 .nbh file, I'm just theorizing as that is all I have the ability to do, besides testing sh1t like crazy.
Bhang
??
Dumping utility? I used dd to write all of nvram out to a file on the SD card, then transfered that nvram image to my linux box and edited with a hex editor... I was not aware people had bad blocks. I would assume dd does a good copy.
Dumping utility? I used dd to write all of nvram out to a file on the SD card, then transfered that nvram image to my linux box and edited with a hex editor... I was not aware people had bad blocks. I would assume dd does a good copy.
Well... here's the update on my latest discovery...
I took an nvram dump of my phone, looked for the spl code and extracted it thinking that it should match up to the bin file for the engineering bootloader (since I've already flashed it)... and lo and behold... binaries differ... I'm thinking the nvram driver doesn't work in kernel all the way, or maybe something in hardware is messing up the dump... or maybe it's something else
I took an nvram dump of my phone, looked for the spl code and extracted it thinking that it should match up to the bin file for the engineering bootloader (since I've already flashed it)... and lo and behold... binaries differ... I'm thinking the nvram driver doesn't work in kernel all the way, or maybe something in hardware is messing up the dump... or maybe it's something else
never mind, I'm a newb... I did the math wrong and accidentally made the extracted spl from the nvram different than the spl.bin from the zip file in the engineering bootloader package... they actually do match!!!! this means (I'm 99% sure) that I have a spl.bin for the original bootloader (which I took from an nvram dump before I flashed the engineering bootloader)!!!
Similar threads
