I was trying to flash the following ROM to my Magician, I did nothing and there was a sudden Reboot in my computer.
ftp://xda:[email protected]/Magician/Shipped_ROMS/CHT_11106_902_11100.zip
NOW, I don't have any backup .nb1 roms to flash back to my magician. I only have couple of .nbf files extracted from "CHT_11106_902_11100.zip
". AND I got a "cht10606_bigstorage.nb1" - "not sure if it's a complete rom.
The ROMUpgradeUt.exe was able to reach stage 3 of the flashing. If I start the magician now, I can see it stuck at the splash screen; that's it.
I WONDER if there is any extisting rom that I can ntrw.exe back and restore to the state I can apply ROMUpgradeUt.exe.
THANKS ALL
MARTIN :shock: :shock:
One more question
I first attempted to hack bigstorage by directly ntrw-write the cht10606_bigstorage.nb1 to my 1GB SD (I don't have small SD card).
But I can't get the "Serial V1.00" in the bootloader mode switch to "SD downloading", even I waited for more than hour an hour.
P.S. I can't verify if I successfully ntrw-write the .nb1 file, coz I see nothing inside my SD.
thanks everyone.
MARTIN
Not sure if big / Small discovery
I solved my own problem, after spending hours and hours on the bootloader screen with that "SD Download" Sections = 1 Not Allow Update screen :twisted:
I realized that Using a different bigstorage verison Rom from the original Version Rom to hack/flash into BigStorage CREATES the "Not Allow Update" screen.
It seems to be a limitation for flashing rom by bootloader, in which the flashing-rom has to be the same version the rom within the magician.
So, I THINK, it's not recommanded to flash ANY modified-bigstorage-rom to an existing rom, if u r sure about the verion difference. I think it's better to use Hex editor to do the hack.
Hope this post help many with the same problem.
MARTIN
When you're stuck in bootloader mode, MaUpgradeUt_noID.exe will help you. It's modified original which won't ask about language etc. and most importantly it can be run even in bootloader mode so you can flash it anyway.
How to get back to RC29? by modifying the update script?
I' chose to update to RC30 while didn't know that update fixed up the permission problem.
I wanted to roll back to RC29 then I tried to do update to the RC29 package.
Failed at the first line of update script:
assert getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC29/115247:user/ota-rel-keys,release-keys"
|| getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC28/114235:user/ota-rel-keys,release-keys"
|| getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC19/109652:user/ota-rel-keys,release-keys"
|| getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC29/115247:user/ota-rel-keys,test-keys"
|| getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC28/114235:user/ota-rel-keys,test-keys"
|| getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC19/109652:user/ota-rel-keys,test-keys"
Click to expand...
Click to collapse
I'm gonna try to append one condition to this line: "|| 1"
But is there any side effect by doing this?
And, I don't know if this will work, since I don't quite know the update package's format.
I think is kind of sun's jar file, and plus a update script in META-INF folder, two cert files(one of this also keeps the sha1 of the manifest file's sha1sum).
Can someone give me some advice?
fluke.l said:
I' chose to update to RC30 while didn't know that update fixed up the permission problem.
I wanted to roll back to RC29 then I tried to do update to the RC29 package.
Failed at the first line of update script:
I'm gonna try to append one condition to this line: "|| 1"
But is there any side effect by doing this?
And, I don't know if this will work, since I don't quite know the update package's format.
I think is kind of sun's jar file, and plus a update script in META-INF folder, two cert files(one of this also keeps the sha1 of the manifest file's sha1sum).
Can someone give me some advice?
Click to expand...
Click to collapse
As soon as you change one byte in the update.zip folder, the update won't verify against the signature, and will fail.
I've tried.
How did you modify the update.zip?
Did you package it in jar way -- which will count the sha1sum of each file and put into MANIFEST.MF?
How do the phone verify the update.zip? by cert files or just check the sha1sum?
Question: what happens, if I try to apply rc29 from SD card (i.e. signed-kila-ota-115247-prereq.TC4-RC19_RC28) after getting RC30 OTA on my G1?
1. update fails
2. update bricks the phone
3. I can have my root back
Does the name _really_ mean that TC4-RC19 is the only thing it will install over?
What checks are actually made before it bootstraps a SD card update.zip?
Can someone comment on the likely result before I get impatient and discover it is #2, please
Doesn't work but doesn't brick
I just tried it. The update will fail, but you won't brick the phone.
this may be a dumb question but why can't the modded RC30 update just be signed with the OTA keys and then used as an update.zip from the SD card?
dagentooboy said:
this may be a dumb question but why can't the modded RC30 update just be signed with the OTA keys and then used as an update.zip from the SD card?
Click to expand...
Click to collapse
Because only {Google,T- Mobile,HTC} have the OTA private keys needed for creating an OTA signed file.
I guess the only hope is google/t-mobile releasing a full update
Downgrade from RC30 to RC29
I have been reading up on the modded RC30 and haven't seen anyone mention this, so here it goes:
My phone had been taking forever to get OTA updates - I didn't get any notifications until the 11th. I wanted to keep root access so I never applied it, but downloaded the RC29 update and installed that manually. I was planning on updating to the modded RC30 once I had some free time. This morning I accidentally allowed the OTA update - damn thing popped up as I was clicking something else. I figured I was stuck with the official RC30 update.
At the end of the first part of the update it gives you the normal recovery prompt - reboot, install update from sdcard, or show/hide text, so I figured I'd try to install RC29 over RC30 (even though I'd heard it's impossible). It worked! I guess until the phone has fully installed the update, you can re-flash whatever update you have on the card. This probably won't help too many people, but if you accidentally allow the OTA update like I did and still have an update on the card this could save you!
Nice to know. Thanks
so if i let it reboot after it installed the update than im pretty much screwed for now?
ChrisAshton84 said:
I have been reading up on the modded RC30 and haven't seen anyone mention this, so here it goes:
My phone had been taking forever to get OTA updates - I didn't get any notifications until the 11th. I wanted to keep root access so I never applied it, but downloaded the RC29 update and installed that manually. I was planning on updating to the modded RC30 once I had some free time. This morning I accidentally allowed the OTA update - damn thing popped up as I was clicking something else. I figured I was stuck with the official RC30 update.
At the end of the first part of the update it gives you the normal recovery prompt - reboot, install update from sdcard, or show/hide text, so I figured I'd try to install RC29 over RC30 (even though I'd heard it's impossible). It worked! I guess until the phone has fully installed the update, you can re-flash whatever update you have on the card. This probably won't help too many people, but if you accidentally allow the OTA update like I did and still have an update on the card this could save you!
Click to expand...
Click to collapse
U Said your Phone taking foreever to get Update
This means you must be on RC19 and phone was trying to get Full RC30 from google.
Becuase of Full update it paused some where and ask you to reboot, Becuase Patch RC30 Update dont ask for it.
Please Explain you Full Situation !!
yup i got stuck with the RC30 update about an hour ago. was dialing a number and it popped up and i accidentally pressed update now! it bites, oh well
I had a great reply written up but the server timed out and lost it :-/
Basically:
I had RC19. I got a system update prompt on the 11th, which led me to think it was the RC30 update. Not wanting it, and not having time to do the modded RC30 update, I installed RC29 via update.zip on my sdcard.
After the update to RC29, I kept getting the update prompt, further leading me to believe it was RC30. I tried to avoid the update but accidentally approved it, since the update screen can pop up at any time.
After the update was unpacked & verified, it prompted me to reboot, install from the sdcard, or hide the text (I may have hit ALT+L or whatever to show the text during the update, I can't remember). Given the option, I chose to install from the sdcard.
It went through a few steps (fewer then the initial unpack, oddly) and again had me reboot. I did, it did went through the update reboots, and when I got back to the system it was RC29. I'm still getting prompts to update, so I still think the update was to RC30 then reversed to RC29, but there's a chance I'm wrong and haven't done anything unusual here.
Short version: If you don't want the official RC30 but don't have time to install the mod, just keep RC29's update.zip on your sdcard. Even if you accidentally approve the install this will let you revert to RC29.
I'm mad that I didn't decline the update to rc30!!!!!!!
ChrisAshton84 said:
I had a great reply written up but the server timed out and lost it :-/
Basically:
I had RC19. I got a system update prompt on the 11th, which led me to think it was the RC30 update. Not wanting it, and not having time to do the modded RC30 update, I installed RC29 via update.zip on my sdcard.
After the update to RC29, I kept getting the update prompt, further leading me to believe it was RC30. I tried to avoid the update but accidentally approved it, since the update screen can pop up at any time.
After the update was unpacked & verified, it prompted me to reboot, install from the sdcard, or hide the text (I may have hit ALT+L or whatever to show the text during the update, I can't remember). Given the option, I chose to install from the sdcard.
It went through a few steps (fewer then the initial unpack, oddly) and again had me reboot. I did, it did went through the update reboots, and when I got back to the system it was RC29. I'm still getting prompts to update, so I still think the update was to RC30 then reversed to RC29, but there's a chance I'm wrong and haven't done anything unusual here.
Short version: If you don't want the official RC30 but don't have time to install the mod, just keep RC29's update.zip on your sdcard. Even if you accidentally approve the install this will let you revert to RC29.
Click to expand...
Click to collapse
Thanks for your reply
hmm, possible reasons
it seems to me (very close to a complete moron) that the updates get copied to a "ramdisk"(4 lack of a better term) then when you see that arrow going into the chip after reboot is when its written from this "ramdisc" to the flash?
maybe its just the hash talkin take it for what it is an educated guess... AKA a theory.
bhang
ChrisAshton84 said:
I had a great reply written up but the server timed out and lost it :-/
Basically:
I had RC19. I got a system update prompt on the 11th, which led me to think it was the RC30 update. Not wanting it, and not having time to do the modded RC30 update, I installed RC29 via update.zip on my sdcard.
After the update to RC29, I kept getting the update prompt, further leading me to believe it was RC30. I tried to avoid the update but accidentally approved it, since the update screen can pop up at any time.
After the update was unpacked & verified, it prompted me to reboot, install from the sdcard, or hide the text (I may have hit ALT+L or whatever to show the text during the update, I can't remember). Given the option, I chose to install from the sdcard.
It went through a few steps (fewer then the initial unpack, oddly) and again had me reboot. I did, it did went through the update reboots, and when I got back to the system it was RC29. I'm still getting prompts to update, so I still think the update was to RC30 then reversed to RC29, but there's a chance I'm wrong and haven't done anything unusual here.
Short version: If you don't want the official RC30 but don't have time to install the mod, just keep RC29's update.zip on your sdcard. Even if you accidentally approve the install this will let you revert to RC29.
Click to expand...
Click to collapse
great tip this is bound to help many others, anybody by any chance know when the next update is coming out?
I tried to Simulate Same thing
1. I already had Updated the phone to Stock RC30 and
2. I Copied RC30 on to SDCard as update.zip
3. Started into Recovery Modem and Pressed ALT+S
4. The Phone Started Verifying the File
5. Then i have Format Boot, System Partition
6. Copied some thing to Phone and asked me to Press Home+Back
7. I pressed it and its flahed Radio Image and reboot in recovery ode twice and did something.
In your Case the Phone might have Extracted the Images into Ramdisk but it might didnt flashed it to phone really and between that u got that Reboot Option and Reflashed the Full RC29 again.
We can reflash the same Version as many time we like but we can not flash lower version as the Recovery command dont allow.
If we keep RC30 as Update and remove the SDCard in between and put a new Card with Update.zip of RC29 the phone unmount the SDCard and then it dont detects the new SDCard is inserted and flashes error so Simulating your Process by Swapping 2 SDcard with RC30 and later on RC29 dont work for me.
If i could place RC30 into Phone and then Try to Simulate that it got the RC30 update frmo Internet and in between flash it with RC29 from SDcard might help me. But i am still not sure.
Downgrade from official RC30 to RC29 ?
My try to change some file on my system then my font was brick . But I use recovery mode, update to official RC30 then I phone worked again. But I want to acess my phone again. Please tell me how to downgrade to RC29 from official RC30 ?
I am a complete newbie. I tried to update to the ADP1.1, but it error'd out on the boot image. The phone now shows a triangle with and exclamation point and a graphic of a phone. I got advice on another community to try and install update.zip from the sd card. I downloaded the original ADP1 update.zip, and I tried to install. Here is what I got:
Installing from sdcard
finding update package
opening update package
verifying update package
installing update
copying files
copying files
formatting BOOT
writing BOOT
E:No space left on device
E:Error writing BOOT
E:Failure at line 8
write_raw_image PACKAGE:boot.img
BOOT
Installation aborted
Thoughts on where to go from here?
No thoughts? Is it now a paperweight?
Please post information regarding your device (brand, model, carrier, OS, etc, etc) That way, we might be able to help you.
I have the Android Dev Phone
Carrier: AT&T
It had the original version ADP1
Tried to update to ADP1.1, but it error'd on the Boot.img portion
Let me know if you need more information.
Thanks.
Mark.
Hindsight ~ 20/20
You probably needed to wipe it before flashing it. For the fix, listen to the experts. [here]
I am more than happy to listen to the experts. Any of them have an idea of what to do next?
Any thoughts?
Bricked Phones
Yeah, I do actually. I noticed a thread with the same topic somewhere else and its active. Check this thread out. http://forum.xda-developers.com/showthread.php?t=475244. Leme know if it does not help. Mail me direct if you wish.
Del
I am not sure this helps. The problem I am having is that once I start the update it stall out when trying to write the boot portion saying the phone is out of space. I have wiped the data/cache, but to no avail. Has anyone seen this before?
Mark. I am not ignoring you, I just don't have net access where I live, so unless I get out and come to my favorite parking lot, I can not email. No I have never heard of it either. Some one here should be able to help. I am NOT an expert, but if you want to hear my only idea here it is. Go way back and start by flashing the old rc29 bios on the phone. Then follow the directions to give yourself root access (i know you do not need to do this with a Developer phone), then flash the Jesus Freke's Android developer bios 1.0 then the 1.1. Try and contact Jesus Freke directly. I wish I could help more, but I am really new at this, and with out having your phone to play with, I doubt I could come up with a fix for you.
Is there anyone that can help with this?
Here is the error message I am getting when I try and install the update.zip from the sd card
E:No space left on device
E:Error writing BOOT
E:Failure at line 8
write_raw_image PACKAGE:boot.img
BOOT
Installation aborted
I have wiped the data, but to no avail. I would really like to get this resolved so I can go back to using my phone. If not, I am more than happy to sell this at a good discount.
hi, i was updating my g1 to ADP1.5Hr3-A2SD, but than show the next message:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
And now, I can't start my phone, it's still showing the boot message.
I write my nandroid backup, with fastboot. but it doesn't fix anything (also still showing the boot message).
I can access to recovery mode and spl.
What should I do?
Thx
Try flashing to RC29/RC7or RC8 NBH
how did you mean?
can you give me some link please?
I think,you downgraded to RC29 to root.
Redo this procedure, put the RC29 DREAIMG,NBH on the SDCARD (format it before) , shut down phone.
Start it while holding camera + power.
YOu should see the bootloader.
There has to be a promt to press power to flash. Press power.
Now you're on rc29 again and you can update to 1.5
First off, check the "About Phone" status in your G1. Then, follow the guide as if you're getting root on your phone for the first time:
http://forum.xda-developers.com/showthread.php?t=442480
What the previous guy said was to flash your phone to the DREAMIMG.nbh image posted on the website above and go from there.
thanks
now, i have a German g1, also there wasn't RC.., witch RC should I install?
Edit: can i copy DREAMIMG.nbh in recovery-mode? because I haven't any mini-sd card reader xP or I need one?
Have you flashed a Hard SPL before?
If not, you must use the goldcard method. Just use the search-function
Go, buy a cardreader
If you have problems, just email me: [email protected] (I support you in german language, of course )
I succesfully used the goldcard-method, worked great!
Yes, you can push the file to your sdcard through the bootloader. To determine which RC to install AFTER YOU HAVE ROOT, again check your "About Phone". If the build number has RC in front of it, download either RC33 or RC8 (I'm guessing the latter since you're in Europe).
If you're choosing between RC29 or RC7 to root your phone, go with RC7.
yes, i have root (gold-card method) and i have hard SPL .
I will try tomorrow with the card-reader
Thx