Related
Upgraded to Dop ROM form original Imate ROM. Now I can't get back. Upgrade is stuck at 95%..or I get Error [296] "Upgrade only This NBF cannot be used on your PDA Phone.. Please get newrer NBF file" . If flash Dop again it works, but refuses to flash any Imate. I guess I'm not the only one here having this problem...many have posetd this problem in different ways but now one gave a concrete answer.
Please let try to solve this.
Thanks
whehe, i'll ask someone who flashed mine back to a JAMin (thought he did it with a-wizard, hope he can help you out).
only the OS itself can be flashed back, you manually have to replace the extended ROM with the JAmin one (total commander, delete existing extended ROM, transfer files through IR to exdended ROM, hard reset to install the extended ROM, bla).
the GSM ROM and the bootloaded itself cannot be flashed to an older version.
yeah, i know, it sucks
Thanks tCC for replying with this goosd news. As for the extended ROM replacment, that's OK and can be easely done.
I realy appreciate your assistance in this and awaiting your next post.
Hi,
i'm the one who flashed the JAMin of tCC. In fact, it's not that difficult. Just follow these steps:
- execute enablerapi.cab on your device (search on the forum for this cab file)
- download awizard, extract
- copy the jamin os rom to awizard\rom\Jamin\
- start awizard.cmd, make sure your device is connected through activesync
- select option 'w' to write the os rom. just follow the instructions.
- the flashing can take up to 30 minutes so be patient
-if the flashing has finished hard reset your device
I've uploaded the jamin os and ext rom to
ftp.xda-developers.com/Uploads/Prophet/JaminAwizard/
tya
swartb said:
Hi,
i'm the one who flashed the JAMin of tCC. In fact, it's not that difficult. Just follow these steps:
- execute enablerapi.cab on your device (search on the forum for this cab file)
- download awizard, extract
- copy the jamin os rom to awizard\rom\Jamin\
- start awizard.cmd, make sure your device is connected through activesync
- select option 'w' to write the os rom. just follow the instructions.
- the flashing can take up to 30 minutes so be patient
-if the flashing has finished hard reset your device
I've uploaded the jamin os and ext rom to
ftp.xda-developers.com/Uploads/Prophet/JaminAwizard/
Click to expand...
Click to collapse
First let me thank you swartb for replying and trying to help by posting and uploading. And of course tCC who offerd to help in the first place.
Second, the link for the file you uploaded is not correct, and if you allow me i think this is the right one:
ftp://ftp.xda-developers.com/Uploads/Prophet/JaminAwizard/
And as far as enablerapi.cab here is the thread for it:
http://forum.xda-developers.com/viewtopic.php?t=50768&highlight=enablerapi+cab
Currently I'm downloading them and will let you know the result.
Thank you both again
swartb said:
Hi,
i'm the one who flashed the JAMin of tCC. In fact, it's not that difficult. Just follow these steps:
- execute enablerapi.cab on your device (search on the forum for this cab file)
- download awizard, extract
- copy the jamin os rom to awizard\rom\Jamin\
- start awizard.cmd, make sure your device is connected through activesync
- select option 'w' to write the os rom. just follow the instructions.
- the flashing can take up to 30 minutes so be patient
-if the flashing has finished hard reset your device
I've uploaded the jamin os and ext rom to
ftp.xda-developers.com/Uploads/Prophet/JaminAwizard/
Click to expand...
Click to collapse
can you cid unlock after installing an older rom?
still it's not working...
Dear swartb,
I tried it many times over and over and I still get this error after waiting of 14-15 min. every time.
CopyFileToTFFS(acidunlocked.bin:0, 0, 00010000)
ERROR: ITWriteDisk - An internal error occured.
Please see the attached images.
Any solution? Thanks
Hi,
I don't remember if I did see that error message. But if do a hard reset after this error the os rom is not updated?
And be sure just to update the OS rom and not the other roms (radio, spl & extended) because that doesn;t work.
I have just completed this aWizard process and now need to hard reset, but the program "clear storage"is not there anymore.
How can I hard reset the prophet without the software?
I will post the steps here when it is done :wink:
Could ran the aWizard with the OS rom in the aWizard folder (not \aWizard\rom\jamin\ ) but could not find way to hard reset the prophet, so reflased back to Dopod.
Hope another person continues from here :wink:
Re: still it's not working...
ahegazi said:
Dear swartb,
I tried it many times over and over and I still get this error after waiting of 14-15 min. every time.
CopyFileToTFFS(acidunlocked.bin:0, 0, 00010000)
ERROR: ITWriteDisk - An internal error occured.
Please see the attached images.
Any solution? Thanks
Click to expand...
Click to collapse
Its because the CID of your device is still locked. And certainly you have IPL/SPL 2.00. or higher. Swart did it with no problem because he has an unlocked CID.
You have to downgrade your IPL/SPL to 1.xx (I still dont know the correct method) and then unlock CID and then you can flash any ROM you want
Re: still it's not working...
ahegazi said:
Dear swartb,
I tried it many times over and over and I still get this error after waiting of 14-15 min. every time.
CopyFileToTFFS(acidunlocked.bin:0, 0, 00010000)
ERROR: ITWriteDisk - An internal error occured.
Please see the attached images.
Any solution? Thanks
Click to expand...
Click to collapse
Its because the CID of your device is still locked. And certainly you have IPL/SPL 2.00. or higher. Swart did it with no problem because he has an unlocked CID.
You have to downgrade your IPL/SPL to 1.xx (I still dont know the correct method) and then unlock CID and then you can flash any ROM you want
Thanks. Guess I can live with it for now. The Dpod rom is quite stable. No soft reset for 2 days and response looks like quicker than after soft-reset 8)
Re: still it's not working...
Tamagochi said:
ahegazi said:
Dear swartb,
I tried it many times over and over and I still get this error after waiting of 14-15 min. every time.
CopyFileToTFFS(acidunlocked.bin:0, 0, 00010000)
ERROR: ITWriteDisk - An internal error occured.
Please see the attached images.
Any solution? Thanks
Click to expand...
Click to collapse
Its because the CID of your device is still locked. And certainly you have IPL/SPL 2.00. or higher. Swart did it with no problem because he has an unlocked CID.
You have to downgrade your IPL/SPL to 1.xx (I still dont know the correct method) and then unlock CID and then you can flash any ROM you want
Click to expand...
Click to collapse
Thanks Tamagochi, Yes you are right, I have I IPL 1.00 and SPL 2.15.0000
The problem now is how to dowgrade form 2.xx to 1.xx. What are those methods that would help? I can try all of them and see if it works.
Finally it's resolved
I'm back to my imate ROM. Detailes in here:
http://forum.xda-developers.com/viewtopic.php?t=52244&start=25
i have a g1 that i installed Jesusfreaks 1.31 to and also flashed hardspl to it.. im having serious battery issues so i am going to return my phone for another one.. im trying to find a how-to on reversing everything i have done along with the stock rc30 image... can someone please point me at a tutorial or in the right direction...
i have googled it for the past 30 mins and have found nothing..
thanks
Download the G1Orig SPL here, flash that. Then download one of the revert update packages here and flash that. Remember to Alt+W to wipe the user and cache partitions too.
Edit: By the way are you having recurring serious battery charge loss or was it just one event?
You could flash the original bootloader (image is in the SPL thread) and then load the stock t-mobile rc29 onto your phone. Then take your phone to T-Mobile for warranty.
This way it just seems as though your phone never got the OTA rc30 update
I brought my phone in to ask a question about a clicking noise my phone had (the arm that the display moves on feels loose) when open. The guy behind the counter asked to see my phone and I was not thinking...he took it and noticed the clicking but said it was normal; he showed me his phone and a few display phones that did the same. Then he fired up "About phone" and suddenly became quite...he turned quite confused and told me that this was not a Dev phone. I played dumb and told him "I don't know, this is how it came from the store when I got it last month..." He then rebooted my phone to see both custom spash screens and the engineering boot loader...I wish I had a camera for the look on his face.
Oddly enough, both he and his manager were reluctant to give me my phone back.
So yeah, I recommend putting a stock rc29 on your phone before taking it in
i downloaded the origSPL and when i go to flash it with alt s it says verifying update package
no signature
verification faield
installation aborted
its renamed to update.zip and im assuming because i have done this before that i am doing it correctly .. any advice?
Did you already revert back to official Android? The SPL updaters are signed with test keys, so if you have already reverted to official Android then anything signed with test keys will fail to flash.
this is my build and kernel version..
would this be the updated rc30? i thought that i updated it correctly and i assume that i could not have flashed hard spl if i hadnt
Kernel version
2.6.25-01843-gfae26b0
[email protected] #19
build numberer kila-user 1.0 tc4-rc30 116143 ota-rel-keys,release-keys
When you enter recovery mode do you see JF's custom background or is it the standard recovery?
its JF's recovery screen.. im thinking to flash the test key recovery.img and then downgrade.. flash the new orig spl then the orig rc30.. witll that work?
If you're seeing JF's recovery screen then you already are running on test keys; there is no need to flash a different recovery.img
i have reformatted the sd card a bunch of times... only thing i can thnk of is that when i download the files from here to my mac it comes as a folder and then i zip them and rename them.. can this be the problem?
Comes as a folder? Sorry, I have no idea how macs work (or don't). You should not need to be zipping anything. If it worked before in the past i'm sure you got it working somehow. The MD5 of the file as it appears on the sdcard should be the identical to what I posted in the SPL sticky.
honestabe said:
i downloaded the origSPL and when i go to flash it with alt s it says verifying update package
no signature
verification faield
installation aborted
its renamed to update.zip and im assuming because i have done this before that i am doing it correctly .. any advice?
Click to expand...
Click to collapse
just use the RC29 NBH file and flash it from SD card. this will make it like it was out of the box.
but the spl will be the hardspl not the orig spl correct?
NBH file doesn't overwrite the SPL though, does it?
honestabe said:
i have a g1 that i installed Jesusfreaks 1.31 to and also flashed hardspl to it.. im having serious battery issues so i am going to return my phone for another one.. im trying to find a how-to on reversing everything i have done along with the stock rc30 image... can someone please point me at a tutorial or in the right direction...
i have googled it for the past 30 mins and have found nothing..
thanks
Click to expand...
Click to collapse
Just flash the Dream file here : http://forum.xda-developers.com/showthread.php?t=463779
It will go back to RC29 and back to that tri-color boot screen, then get the OTA RC30 here : http://forum.xda-developers.com/showthread.php?t=451090
ok.. i figured it out.. here was the problem.. on my mac when using safari in the preferences it has an option to auto open trusted files ..ex. pdf zips etc..
so it was unzipping the zips into folders.. then when i was re-zipping them it was messing it up.. i now have it working..
hope this helps others with this problem
and thanks to you guys for trying to help me trouble shoot it
honestabe said:
my mac when using safari
Click to expand...
Click to collapse
There's your problem
that brings up the question...
to make thing simple for people.
Does anyone have the orignal G1 recovery.img image so for those who want to revert back to orignal firmware with ORIGNAL keys it would be nice.
for some people its better for them to know that thye are reversing their steps them.
what I know from all the threads above is just loading loading firmwares with test keys....
now how about the original recovery.img. Provding a reverse would be nice.
=)
Getting the original recovery.img is easy. Just download the original RC30/RC8 file from any mirror and open it up with your favorite archiving program. However in order to revert the SPL you would still need to be using test keys.
recovery I can do
the reverting of SPL..hell I dont know how to do that....
I decided to try and root my stock G1 this morning. The bootloader does not allow me to flash down to RC29. It gives the "Update Terminate" after it fully flashes it, but before it checks the flash. Then it only loads into the bootloader and stops.
However i just successfully flashed to RC30. None of the guides on here specify that I had to load another spl or bootloader first.... Am I missing something?? Thanks for your help.
Bootloader:
DREA100 PVT 32B RUUNBH
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
SEP 2 2008
Solved!!!: Apparently I was on the right track. My US T-Mobile G1 was locked somehow to only accept only RC30 and above. I made a goldcard for my SD card and the image no longer failed (same sd, same image file) at the flashing the .nbh. If anyone has been having issues flashing a US G1... try a goldcard... It instantly fixed the problem! I guess its not only for German and UK?!
BTW.. thanks to pk at codeandroid.org for his guide to make the goldcard without a WM device or linux... http://www.codeandroid.org/forum/?wpforumaction=viewtopic&t=9.2 (in broken english... lol)
Thanks to Viper and revskills.de for their work on goldcard images
Thanks to JesusFreke for this bada$$ ROM (1.5)
Thanks to Haykuro for his android 101 guide.
Great work everyone really...
you need to make sure that your sd card is formatted fat32 and checksum on the DREAIMG.NBH
then try again. should work.
thanks for replying did that. The md5 checksum matched perfectly I have 3 different sd cards all formatted in fat32 only. still no go. I have tried 3 different links to the dreaimg.nbh. made sure it was in all caps and everything. nothing.
It will find the file.
It will flash the file to 100%.
When it would normally check the integrity of each portion it says...
"dreaimg.nbh - FAIL"
"Update Terminate"
"Update FAIL".
The odd part is it will flash the RC30 nbh just fine... same sdcard, same instructions.
try a different sd card- my stock one didnt flash either, same error over and over.
use this nbh -
http://www.mediafire.com/?sharekey=78b87e4b3d9bce857f7ec40ada4772a691de501fd3b9a6eb5be6ba49b5870170
tried all 3 cards with your file. same thing. Why will it so willingly let me flash rc30 the exact same way?
you got me.....
this was the confusing part. so im sitting on rc 30 right now for the 5th time. i have had 30 or so unsuccessful flashes of RC29 and EVERY flash of RC30 was successsful... this is my barrier to Haykuros and/or JF roms...
The file names are case sensitive. It must be DREAIMG.nbh . All caps for the prefix, no caps in the suffix.
thanks for your response... i tried both ways. most of my 30 attempts was changing caps... no caps... on file name and extension. reformatting... downloading from new sources... clearing my temp folder so windows wasn't transferring the same file every time since they are names the same (trust me windows does that with same named and same sized files...)
The only thing I can come up with is a modded bootloader. My G1 is not the one i had from launch date... so this phone never had any lower than RC33 (got the phone 5 weeks ago, came pre-loaded with RC33). This maybe one of T-Mo's tactics in the "War on Root".
That may not be the issye... I had RC30 when I bought the phone. I was able to get to RC29 with no issues... I don't think tmobile did anything to the phone.
i wish it wasnt but how can this phone reject rc29 but accept rc30. does anyone have a rc28, rc19, or below .nbh?
Can you try flashing the engineering Bootloader or HARDSPL first, then fastboot?
I'm not sure if you can use those without having root first though.
ICBM said:
Can you try flashing the engineering Bootloader or HARDSPL first, then fastboot?
I'm not sure if you can use those without having root first though.
Click to expand...
Click to collapse
no i cant. from what i've seen the first step to installing any bootloader is accessing SU... which is root... which means i'm shot down again... getting depressed.
Has anyone tried loading HardSPL without root?
crushsuitandtie said:
no i cant. from what i've seen the first step to installing any bootloader is accessing SU... which is root... which means i'm shot down again... getting depressed.
Has anyone tried loading HardSPL without root?
Click to expand...
Click to collapse
You are right, you need root to be able to load a different boot loader. I got a replacement sent to me from T-Mobile with RC33 on it maybe 3 weeks ago and i had no problems with obtaining root. If i were you i would call up T-Mobile and tell them the Menu button is not working every time on your replacement. They may send you an express replacement...
makes me wish i had kept my launch phone... I got it with RC17 or 18... but i remember getting rc19 ota... this sucks. The only reason i traded it in is because GPS wouldnt ssync anymore unless i did a wipe... so i knew it was a software problem... if i had just rooted it I bet i wouldnt be in this crap. i couldbe on haykuros... right now...
Sounds like a hardware issue to me. The data from the SD card isn't being written to flash properly so the SPL can't verify it. I would try calling T-Mobile to see if they can send you another unit. Obviously don't tell them you tried to flash an unsupported ROM, just make up a story and they will likely believe it.
Just to exclude the obvious. Shouldn't the file be called DREAMIMG.nbh not DREAIMG.nbh as you've written.. Or is that just a typo in your posts?
crushsuitandtie said:
thanks for your response... i tried both ways. most of my 30 attempts was changing caps... no caps... on file name and extension. reformatting... downloading from new sources... clearing my temp folder so windows wasn't transferring the same file every time since they are names the same (trust me windows does that with same named and same sized files...)
The only thing I can come up with is a modded bootloader. My G1 is not the one i had from launch date... so this phone never had any lower than RC33 (got the phone 5 weeks ago, came pre-loaded with RC33). This maybe one of T-Mo's tactics in the "War on Root".
Click to expand...
Click to collapse
ok i received my phone like a month ago an it came with Rc33 install and my phone when try to flash Recovery, i get a error EveryTime, look at all My Topic you see
I just keep on trying and i get it on my 7th try lol I'm not lien
bp8575 said:
Just to exclude the obvious. Shouldn't the file be called DREAMIMG.nbh not DREAIMG.nbh as you've written.. Or is that just a typo in your posts?
Click to expand...
Click to collapse
The correct image name is DREAIMG.nbh. looks wrong but its right... I think it IS a hardware issue. The is writing but not verifying certain images... and its now giving me checksum errors on rc30 after 8 successful loads, but when i retried without doing anything to the file it completed. I would say its my card but I have 3 different cards...
bump for anyone else having trouble...
Hi,
I flashed my O2 XDA orbit with a HTC Artemis rom long back. Yesterday while using Route 66 GPS software I got a message that some .config file was corrupted and now the touch screen is not working. I tried to flash the ROM but its giving me an error at 3% saying "Image file is corrupted". Trying to flash from the SD card is not working either.. Need help. I am out of my home country currently and need my phone to work desperately cause of my GPS software to find my way around
Thanks in advance Gurus..
Update -
I am trying to flash the original rom onto the device and I am getting an error "Invalid Model ID"...heeellllpppp
re download the rom and flash, assume you have access to a pc?
new_login1 said:
Hi,
Update -
I am trying to flash the original rom onto the device and I am getting an error "Invalid Model ID"...heeellllpppp
Click to expand...
Click to collapse
you sure you have a CID unlocked device??
yup I am sure I did that. I had installed a ROM on it earlier downloaded from this forum. I remember I had downloaded one ROM from this forum quite some time back which updated the device without restarting(the device) from the cmd prompt of the PC. WE had to manually type the commands to update the ROM. Dont remember more details...Can anyone tell me where I can find that ROM...
Ok to start off... Hi im new here and to rooting in general so if I ask something stupid please forgive me... So here goes, I have gained perm s-off root for my Sensation using revolutionary and im attempting to install a rom/kernel but I keep getting the same error while trying to flash it "write_raw_image ("/tmp/newboot.img" , "boot"... I got the rom/kernel from this site and placed the file in my root directory as well as download directory and went into clockwork recovery to install from sdcard and this error keeps popping up? Ive tried searching but all I can find is something about an evo for sprint... PLEASE HELP im trying to overclock this thing to see what its really capable of and I cant get past this part... Thanks in advance, Travis
what ver of CWM are you running? also, which rom/kernel?
not sure how to tell the version of clockwork but the LeeDrOiD kernels and also the RCmix kernels... getting the same error msg. Thanks for your quick responce ive been messing with this since 5am this morning
when u load CWM, it will say the ver @ the top...
also, try re-downloading the kernel or match the MD5's to make sure they are complete...also try unity kernel and see if it happens with that one
ahh got it... ClockworkMod Recovery v4.0.1.5 match the md5's? like i said im new to this so im not really sure what that is
same error using the unity kernel
chances are its either a bad sd card, or you might have to update your radio, most of the new roms require the latest one...
THERE IS A GREAT RISK IF IT FAILS, BUT THERE SHOULD BE NO PROBLEM WHEN FLASHING FROM SD
EDIT* are you rooted?
before you try this, try using another SD card to eliminate the possibility of a faulty/corrupt sd card!
instructions: http://forum.xda-developers.com/showthread.php?t=1178143
Recommended Radio: 10.56.9035.00U_10.14.9035.01
the easiest way to flash a new radio is to copy the PG58IMG.zip to root of sd card, go into recovery, it will load automatically, say yes to update, and when it reboots, and asks to update onse more (its automatic), pull the battery and then remove the file PG58IMG.zip from the sd card.
boot back into CWM and try flashing again
hopefully that helps
standard tool to verify MD5 sums
http://154.ca/otr/iso/md5sum.shtml
just drag the zip onto the exe, and match the MD5 from the cmd prompt with the MD5 listed on the thread
i wish there was a way to chat realtime and have someone walk me through this... i feel like im gonna mess it up