I recently upgraded to Cyanogen, gave it a go and am trying to go back to the stock SPL and ROM. However, when trying to apply the original G1 SPL via update.zip on the SD card it complains:
E:No signature (5 files)
E:Verification fauled
Installation aborted.
any ideas?
The best way to go to stock (including radio, SPL, recovery and ROM) is to flash the appropriate DREAIMG.nbh to your device; this will replace everything at once.
There are copies of RC29 (and RC30, IIRC) for T-Mobile USA, as well as RC8 for T-Mobile UK, floating about the internet. Just place the DREAIMG.nbh on your FAT32 formatted SD card, and boot into SPL (holding down camera and power to power on), and follow the on-screen prompts. Couldn't be much easier.
(Of course, a quick search would have pulled up this existing thread: [HOW TO] UNROOT, get phone to STOCK firmware.)
I found this link for the RC29 DREAIMG.nbh. Maybe it's the right one. I have the original one but I'm at work right now so I have no access to it.
http://forum.xda-developers.com/showthread.php?p=3108766
DREAIMG.nbh does not include the SPL...
the SPL is in the form of an update.zip
the instructions you linked explain this.
I would say try downloading the update.zip SPL again
Oh...I just saw rpcameron mentioned the DREAIMG.nbh. The "Informative Links" thread has the SPL link http://forum.xda-developers.com/showthread.php?t=455860
ekeefe41 said:
DREAIMG.nbh does not include the SPL...
the SPL is in the form of an update.zip
the instructions you linked explain this.
I would say try downloading the update.zip SPL again
Click to expand...
Click to collapse
the DREAIMG.nbh does include the spl........
if you want to get to stock...you flash the .nbh file. it sets EVERYTHING to stock and its what HTC uses in their service center. the only thing that it doesnt replace is splash2.img, which if you have the .2005 spl, is not there
B-man007 said:
the DREAIMG.nbh does include the spl........
if you want to get to stock...you flash the .nbh file. it sets EVERYTHING to stock and its what HTC uses in their service center. the only thing that it doesnt replace is splash2.img, which if you have the .2005 spl, is not there
Click to expand...
Click to collapse
Now i could be wrong but...
I thought the SPL managed the way the ROM is partitioned. So people with the "danger" SPL have more room to install apps or larger rom's (all hero roms).
I think it does this by borrowing space from the partition that is normally used to download OTA updates.
So is someone had the "danger" SPL installed, then apply DREAIMG.nbh everything would look normal to the user, but the partition normally used to DL OTA updates may be too small for future OTA updates.
correct me if i am wrong
Edit: no need to correct me, i may be a little off about the partitioning, but SPL and DREAIMG.nbh are 2 very separate things read thread below
http://forum.xda-developers.com/showthread.php?t=455860
ekeefe41 said:
Now i could be wrong but...
I thought the SPL managed the way the ROM is partitioned. So people with the "danger" SPL have more room to install apps or larger rom's (all hero roms).
I think it does this by borrowing space from the partition that is normally used to download OTA updates.
So is someone had the "danger" SPL installed, then apply DREAIMG.nbh everything would look normal to the user, but the partition normally used to DL OTA updates may be too small for future OTA updates.
correct me if i am wrong
Click to expand...
Click to collapse
Part 1) Haykuro's SPL(Danger) uses the space from the OTA partition which is correct.
Part 2) The Drea makes your radio and SPL stock so you lose out on root.Root users dont need to worry about not enough space and 2.0 has been announced its no secret.
Ace42 said:
Part 1) Haykuro's SPL(Danger) uses the space from the OTA partition which is correct.
Part 2) The Drea makes your radio and SPL stock so you lose out on root.Root users dont need to worry about not enough space and 2.0 has been announced its no secret.
Click to expand...
Click to collapse
i can vouch for this as i reflashed the nbh recently and it downgraded my spl to 0.95.0000
Ace42 said:
Part 1) Haykuro's SPL(Danger) uses the space from the OTA partition which is correct.
Part 2) The Drea makes your radio and SPL stock so you lose out on root.Root users dont need to worry about not enough space and 2.0 has been announced its no secret.
Click to expand...
Click to collapse
Cool, thanks for the info
ekeefe41 said:
Now i could be wrong but...
I thought the SPL managed the way the ROM is partitioned. So people with the "danger" SPL have more room to install apps or larger rom's (all hero roms).
I think it does this by borrowing space from the partition that is normally used to download OTA updates.
So is someone had the "danger" SPL installed, then apply DREAIMG.nbh everything would look normal to the user, but the partition normally used to DL OTA updates may be too small for future OTA updates.
correct me if i am wrong
Edit: no need to correct me, i may be a little off about the partitioning, but SPL and DREAIMG.nbh are 2 very separate things read thread below
http://forum.xda-developers.com/showthread.php?t=455860
Click to expand...
Click to collapse
haha your exactly right about the dangerSPL but when you flash the DREAIMG.nbh, it replaces everything to stock, including the stock spl. the stock SPL readdresses the space so the ota partition is back to normal.
the DREAIMG.nbh is an image of the flash memory of the stock Dream when it has a certain os installed on it. the one we use is RC29's DREAIMG.nbh
B-man007 said:
haha your exactly right about the dangerSPL but when you flash the DREAIMG.nbh, it replaces everything to stock, including the stock spl. the stock SPL readdresses the space so the ota partition is back to normal.
the DREAIMG.nbh is an image of the flash memory of the stock Dream when it has a certain os installed on it. the one we use is RC29's DREAIMG.nbh
Click to expand...
Click to collapse
so is it right, when i flash the DREAIMG.nbh form a GoldCard it will flash RADIO/SPL/ROM/RECOVERY (and also the custom first bootscreen) to full stock.
and than i only have to apply this:
Rooting RC29 or Lower Phone
1. Download Cyanogen's Recovery and copy it to your SD card (see the previous instructions on how to copy from your computer to your Phone's SD card).
2. Download the latest Radio and copy the zip file to the SD card.
(3. Download the Hard SPL and copy the zip file to the SD card.) MUSTHAVE???????
4. All files must be on the root of your SD card.
5. Restart your phone. Wait for your phone to start up fully and show the home screen.
6. After your phone starts up, hit the enter key twice, type "telnetd" and press enter. (Yes, it will start up a contact search, don't worry. Just type it.)
7. Download an Android "Telnet" application from the Market and connect to localhost.
8. If you connect successfully, you will have a root prompt "#".
9. Type the following into Telnet (these commands will give you root access easier in the future):
Code:
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# cd sdcard
# flash_image recovery cm-recovery-1.4.img
# cat cm-recovery-1.4.img > /system/recovery.img
Now you have root!!
# Power off your phone.
# Start up in recovery mode by holding home and pressing power.
# You will now enter recovery mode.
# Press Alt+A to see the .zip files
# Select the Radio file.
# After the update is complete, hold Home and press Back to restart.
Than flash CyanogenMod 4.1.999 or The Official Donut Build Rooted like this:
1. Download the image
2. Copy it to your phone's SD card.
3. Turn your phone off
4. Start up in recovery mode by holding Home and pressing Power.
5. Press Alt+W to wipe your device. (You need to do this, or the device may hang at the flashing Android screen)
6. Press Alt+A and select your ROM file to apply the update.
is that all right? please correct me if there is something wrong.
Hi,
Recently decided to upgrade to the 2.2 to see what its all about.
I have got my Nexus to the 27 build needed, but when I go to apply sdcard:update.zip I get the error:
"E:Can't open/cache/recovery/command"
And it aborts. Then I have to reboot and it goes back to 2.1. I definatly have the file as "update.zip" (i dont hide extensions)
Cheers,
Gradu
when you change the zip file name just type update and not update.zip, i had the same problem.
Thanks for the input, but no cigar.
I have noticed however, when I plug my nexus to the PC, its registered as F drive.... but my phone fault says that E: cant open /cache/recovery/command just as I get into the recovery mode as well.
There is no need to unroot. Get the pre root zip and flash like normal. 2.2 has new radio so will flash that first then the next reboot will be 2.2
I have been working on flashing my wife's Nexus One to CM 6.0 but keep running into a problem where after I select the .zip file to flash and it verifies the update, it always fails due to a corrupt file with the message "E:Corrupt File: <filename here>" followed by "E:Verification failed". I tried multiple images and downloads, including Kang-O-Rama and the stripped down CM 6.0 as well as eViL's Sense ROM. All of them fail, not necessarily on the same file within the .zip either which leads me to believe it is a problem with the phone and not the images.
I have checked the md5s, they all work out and I also tried a different SD card but to no avail. Anybody know what could be causing this?
I had that problem once and finally just disabled the checksum verification. I'm not sure all recoveries have that option but if I remember correctly, it's in the same menu where you select "flash zip from sdcard".
Luckily, I never had the problem again. Whatever it was must have been due to something being messed up with the system that I had on it that day.
Thanks Fubaya, I am using Amon's RA which doesn't seem to be able to disable checksums. I'll search out a different one. Is there a preferred recovery image to be using?
Looks like the Clockwork Recovery did the trick, thanks for the pointer in the right direction!
I put the package on my SDcard and renamed it to update.pkg and then tryed to install it by the Software Update via update.pkg option in the recovery and then as it was going it suddenly says SDCard not enough space, I cleared up the SD and then put it in and then the next run it says FOTA Model Name Mismatch or something like that.
I'd like help, my build is 19534, I want to get it to the new 21700 build that would occur from updating...
Did you do the recovery.img using the "fastboot" method..?
I did the recovery.img as you said and then installed the package it went through
Thanks.
I'm trying to install HC 3.2 from the stock Froyo install on a T-Mobile Streak 7.
I'm pretty sure I've followed all of the posts correctly, but I seem to get hung up and am hoping someone can point out the obvious (I hope) mistake.
First off, I'm using the flashing guide at:
http://forum.xda-developers.com/wiki/Dell_Streak_7/Flashing_Guide
And the files found at:
http://forum.xda-developers.com/wiki/Dell_Streak_7#Official
Specifically, I'm using these files (US 4G 514 build):
http://mirror2.streakdroid.com/manii/Streak7/514/recovery.img
http://mirror2.streakdroid.com/manii/Streak7/LG7_514_21700_30.pkg
I seem to have no problem installing the recovery image and installing the rom package on the SD card.
But, when I try to go into the Recovery mode and select to update via update.pkg, I get the message "Booting recovery kernel image" and then it just hangs.
I've downloaded both files twice in case there was a problem with one of the downloads and that did not fix it.
As a test, I installed the old recovery image:
http://mirror2.streakdroid.com/manii/Streak7/336/recovery.img
And tried to update to the 514 package, and it failed (gave the FOTA error - as expected).
Any ideas on what is going wrong? Thanks.
You can try to open your .pkg simply when device is power on - from downloads or with file manager. I installed HC official update (but i have wifi version) this way, without recovery
I cannot get it from the update section because it is a T-Mobile version.
As for running it from the file manager, it is an "unknown" type. Not sure how you can install a .pkg file direct from the OS.
Download XPlore File Manager and try Open in a system in submenu on long tap