Hey guys,
so, a lot of my quetstions will be already posted, but i can´t find them all.
So i hope i annoy no one here ;-).
Ok, now to the important:
I have a SGS until 6 month. over the time i learnd a lot of android and i´m very lucky with them.
Then i heard from cyanogenmod. and all i read about it is great.
i have knowledges about root of linux an so of android.
So, during my research i have a lot of question before i flash my sgs:
- i found only one forum enty where i read i have to format all partitions.
So, how do i flash a sgs?
i have a modded boot rom with root and clockwork mod.
I tried a backup of the system.
the rom manager don´t show ne the cm7 mod for my device.
Do anyone know why? because the RC status?
When i get an error, how can i rollback my firmware with the backup?
Which pc software i need?
my plan ist to flash the sgs with the experimental version, no nightly build.
CWM makes al lot if IMG files. the cm7 zip has only one IMG.
So, i hope anyone can tell some or send my some nice links.
thanks a lot :-D
ravn
Use this
Boom, that's how it's done folks.
Sent from my I9000m running Cyanogen Mod Nightly
Hey,
thanks guys.
So, can anyone explain me how i can go back to the original rom if i got any probs or even i want?
So, i made a backup with Titanium Backup (premium user) and secondly with CWM.
So, i copied them to my PC.
CWM makes some IMG files. So, how can i rollback them to my device?
Also if i try to create a rom image with the rom manager the recovery manager makes a error.
:-D
So, i get by saving my rom the following error:
-- Installing package ...
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Why do the rom manager want to install a package by making an backup?
PS: i have the rooted bootloader: PDA_XXJVK_Sbl.tar installed.
to revert back to you need to revert to a stock rom. using odin and a full PDA froyo will do the job.
Hey,
so u mean, i have to download the offical rom and install them over odin.
then i have to root them and install CWM and reverse the backup.
is that right?
ravn83 said:
Hey,
so u mean, i have to download the offical rom and install them over odin.
then i have to root them and install CWM and reverse the backup.
is that right?
Click to expand...
Click to collapse
yes.. that will be the proper way to do it.
Related
The update in conventional zip format, with root options is here!
P
Works mint! I was running Modoco 1.3 ROM, heres the steps I performed:
recovery install: update-nexusone-ERE27-signed.zip
recovery install: update-nexusone-radio-32.24.00.22U_4.03.00.21_2-signed.zip
./fastboot-linux boot boot.ERE27.superboot.img
./fastboot-linux flash zimage zImage-2.6.29.6
./adb remount
./adb push bcm4329.ko /system/lib/modules/bcm4329.ko
Can I flash this manually WITHOUT being rooted?
I posted a thread on updating without root: http://forum.xda-developers.com/showthread.php?t=627533
Modaco's page confused me a little.
Does the "Main update" include the radio update, or did he split that off and they're completely separate?
Can the main update be installed using a rooted, but stock, rom and recovery?
In other words, if I just want exactly what the OTA would give me, on my rooted (by superboot) but stock N1, what do I need to do?
Thanks!
I'm completely stock rom / not rooted and I just did this:
http://androidforums.com/nexus-one/41504-how-force-2-2-2010-ota-update.html#post316090
1. Get the update from Google: http://android.clients.google.com/updates/passion/signed-passion-ERE27-from-ERD79.a487b405.zip
2. Put the update on your SD card & rename it to update.zip
3. Boot in recovery mode (hold down trackball + power)
4. Go to bootloader -> recovery
5. Now there's a picture of a droid with a triangle
6. Press the power button + volume up
7. Apply sdcard:update.zip
8. Updating
9. Reboot system now
10. Enjoy the multitouch
Click to expand...
Click to collapse
Worked great.
Thanks Paul. That's what I first tried, and it failed. I posted the details here, but haven't heard anything back yet.
http://forum.xda-developers.com/showpost.php?p=5528501&postcount=118
Mine is ROOTED, but stock, so.....
tonyx3 said:
Modaco's page confused me a little.
Does the "Main update" include the radio update, or did he split that off and they're completely separate?
Can the main update be installed using a rooted, but stock, rom and recovery?
In other words, if I just want exactly what the OTA would give me, on my rooted (by superboot) but stock N1, what do I need to do?
Thanks!
Click to expand...
Click to collapse
I'm in the same exact boat as you. I rooted my phone last week because i was eager to get multitouch working, so i followed this tutorial:
theunlockr[dot]com/2010/01/21/how-to-enable-multitouch-browsing-on-your-nexus-one-using-the-native-browser/
So now when i try to apply the OTA update manually in recovery mode i get:
Code:
E:Can't open /cache/recovery/command
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/Browser.apk" , "68a23e4ac9d6a783b6166b24ab79d12c6544e8f4" , "4da6d3fd306ef7fc81e19147da395f13221e70307")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Does anyone know what i can do to get this OTA up and running? Im rooted but i havent flashed any custom roms or recoveries either.
This is my first android phone so i'm a bit of a noob and new to the scene. Any help would be greatly appreciated
Paul22000 said:
Can I flash this manually WITHOUT being rooted?
Click to expand...
Click to collapse
yes, just did it 5 min ago
PhantomRampage said:
I'm in the same exact boat as you. I rooted my phone last week because i was eager to get multitouch working, so i followed this tutorial:
theunlockr[dot]com/2010/01/21/how-to-enable-multitouch-browsing-on-your-nexus-one-using-the-native-browser/
So now when i try to apply the OTA update manually in recovery mode i get:
Code:
E:Can't open /cache/recovery/command
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/Browser.apk" , "68a23e4ac9d6a783b6166b24ab79d12c6544e8f4" , "4da6d3fd306ef7fc81e19147da395f13221e70307")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Does anyone know what i can do to get this OTA up and running? Im rooted but i havent flashed any custom roms or recoveries either.
This is my first android phone so i'm a bit of a noob and new to the scene. Any help would be greatly appreciated
Click to expand...
Click to collapse
http://www.nexusforum.net/nexus-one-help-forum/493-how-manually-retrieve-new-update-your-nexus-one.html#post2000
check that guide out, it was simple and easy to follow...
Thanks JHaste.
But those are pretty much the exact instructions I followed that gave me the error.
My phone is rooted, but running the stock rom.
No custom rom, no patched browser.
The only changes I've made since rooting it are to copy some Thai fonts into the fonts directory.
The exact specifics of my error are posted in:
http://forum.xda-developers.com/showpost.php?p=5528501&postcount=118
Very similar to what PhantomRampage listed, but a slightly different cause, I think... (his is an error on Browser.apk)
JHaste said:
-Removed quoted link since i cant post them yet-
check that guide out, it was simple and easy to follow...
Click to expand...
Click to collapse
Thanks for trying but as i said before, i tried that and it fails because i have an unlocked bootloader.
Sorry if my first post was confusing, ill try again.
I unlocked my bootloader and rooted my N1 the other day, i also modified and added some files to get pinch-to-zoom working on the native browser. To do that i followed some tutorial on theunlockr, i cant post direct links so google it and you'll find it easily.
So, now i want to apply the new OTA update but it fails, either because i have root access or because i tampered with the browser files im guessing.
Knowing all that, what can i do to install the new update?
Also, will i have to download patched updates from now on since i rooted my phone? I'm really hoping i dont have to; i'd prefer to install the ota updates as they come out officially.
might have found a solution
check out:
forum (dot) androidcentral (dot) com / google-nexus-one/6469-will-my-n1-receive-ota-ere27-update-cyanogen-mod (dot) html
seems to be just what i was looking for but i think i want to re-flash the stock firmware instead, i want to stay as stock as possible so i can install future OTA updates without having to go through all this trouble. Can anyone help me with that please?
Anyways, i hope my link will help some people. Sorry for the double post
Closing Double Thread (it's also at Development).
Please do not duplicate threads if not necessary.
i accidentally deleted my stock os in my nexus one. i found some stock roms but i keep getting this error every time when i try to install them
E:signature verification failed
What recovery are you currently using?
If it is stock recovery you will need to use the official google file and rename it "update.zip" and place it on the root of your SD card. Make you sure you visit the development section and read up on the procedures, as your radio version and recovery are not listed, its hard to tell from your post. If you are indeed in stock recovery...
Here is the original, official ROM http://forum.xda-developers.com/showthread.php?t=614057, make you sure you load it correctly. And of course...I am not responsible for anything that may go wrong. You will soon get the OTA update to 2.2 Froyo.
If your on a custom recovery, you should download a custom ROM. Some are based on the stock AOSP so if that's what you want you can find one like that and flash it through custom recovery after the triple wipe (factory/cache/dalvik). If that doesn't work try switching to the other custom recovery image. Aman-Ra is one, ClockWork is the other.
cheers
Hey guys,
I am pretty new with the android OS but I am trying my hardest to read up on it and wrap my head around it. so please bear with me.
I have a verizon fascinate that was purchased a week ago and I rooted it.
I have the Rom Manager installed and the OS is running smoothly. I was going to install a custom Rom on my phone but when I tried to back up the current Rom using the Rom manager. it will boot into the Android system recover (2e) and this is what shows up on my phone:
-- Install from Package...
Finding update package...
Opening update package...
verifying update package...
E:faield to verify whole-file signature
E:signature verification failed
Installation aborted.
with that massage I dont think that I have my current Rom backed up any where...
does any one know how I can get passed this step?
I dont have much knowledge about the android operating system so if some one can help me out with this it would be freaking awesome!
---
I have not installed anything crazy, Rooted with the One click root. and Used the Titanium back up software.
You have to flash the Clockwork kernel/recovery onto it to run the update.zip that activates the backup stuff. See here.
MAKE SURE YOU FLASH INTO THE "PDA" SECTION OF ODIN AND NOT THE "PHONE" PART. "Phone" will brick your device.
Works perfect now!
Thank you very much!
i'm having the same problem, but i've already flashed clockwork? did i miss something?
fail fail
E:faield to verify whole-file signature
E:signature verification failed
Installation aborted.
Runing pt Litening_Rom_v1-5.rar tried Litening_Rom_v3-2.rar same isue .
Rom Manager (pro) fails to backup every time. When useing CWM (comeing with Litening_Rom no probelem at all)
And today I tried Litening_Rom_v4.1 same problem
jesterdallas said:
i'm having the same problem, but i've already flashed clockwork? did i miss something?
Click to expand...
Click to collapse
Which version of cwm are you using, and what are you trying to flash?
HI all,
Ca you help me in flashing RCmixHD [2.3.3,SENSE 2.1,720p video,tb unlock] v1.0.1 ROM. I need to know which are the files I have to download and flash. Thanks in Advance.
With regards
<Manic>
There is a whole section titled ROM links, it shouldn't be that hard to work out :/
If you're generally referring to flashing a custom rom then have a good read at the Nexus One wiki, it'll help you understand a little more.
manicsen said:
HI all,
Ca you help me in flashing RCmixHD [2.3.3,SENSE 2.1,720p video,tb unlock] v1.0.1 ROM. I need to know which are the files I have to download and flash. Thanks in Advance.
With regards
<Manic>
Click to expand...
Click to collapse
ill upload it. the rom seems to be only showing up as 1.01mb on the OP thread. ill post link when im done
charlieb620 said:
ill upload it. the rom seems to be only showing up as 1.01mb on the OP thread. ill post link when im done
Click to expand...
Click to collapse
It might help if you read the posting fully. You need to download all three files.
1. RCmixHD 1.0
2. USB Fix
3. 1.0.1 Update
Install them in this order, reboot between each install. And make sure you fully wipe your device first.
What about for Version 1.1.. I think i can download that single file and flash the ROM..
hi,
i downloaded RCmixHD [2.3.3,SENSE 2.1,720p video,tb unlock] v1.1 ROM and flashed it after full wipe..
During the time of flashing i am getting this message.. Kindly help me in clearing this problem
E:Missing file:
ext/system-VR/0419/libCBLexMgr.0419.so
E: Verification failed
zip verification failed
zip isn't signed correctly.
Installation aborted..
manicsen said:
hi,
i downloaded RCmixHD [2.3.3,SENSE 2.1,720p video,tb unlock] v1.1 ROM and flashed it after full wipe..
During the time of flashing i am getting this message.. Kindly help me in clearing this problem
E:Missing file:
ext/system-VR/0419/libCBLexMgr.0419.so
E: Verification failed
zip verification failed
zip isn't signed correctly.
Installation aborted..
Click to expand...
Click to collapse
Disable signature verification(If you're using RA Recovery, you can see 'toggle signature...', and I think Clockwork also has such option) and try it again.
Hi,
Is it Safe to flash Unsigned ROM.. or i have to wait for Signature once full ROM is there..
<Manic>
manicsen said:
Hi,
Is it Safe to flash Unsigned ROM.. or i have to wait for Signature once full ROM is there..
<Manic>
Click to expand...
Click to collapse
Although it warns about unsigned ROM/updater, I think if it is from reliable developer, it's usually OK, though I feel developers should sign their .zip files after packing is done.
thanks.. i have flashed already
I just got a I9505. I was able to successfuly root it using CF-Auto, and also install TWRP. However, when booting into the recovery to install the latest nightly build, I get this error:
Finding update package...
Opening update package...
Installing update...
set_perm: some changes failed
(status 7)
Installation aborted.
I'm not able to mount the system after doing so, which forces me to flash the stock ROM via Odin. Anybody else who encountered this problem?
re: flashing issues
jorel000 said:
I just got a I9505. I was able to successfuly root it using CF-Auto, and also install TWRP. However, when booting into the recovery to install the latest nightly build, I get this error:
Finding update package...
Opening update package...
Installing update...
set_perm: some changes failed
(status 7)
Installation aborted.
I'm not able to mount the system after doing so, which forces me to flash the stock ROM via Odin. Anybody else who encountered this problem?
Click to expand...
Click to collapse
This should fix the problem, here is CWM Recovery for the i9505 phone,
You will need to Odin flash this recovery: http://downloadandroidrom.com/file/GalaxyS4/GT-i9505/recovery/CWM/i9505-cwm-recovery-6.0.3.2-4.tar
I would suggest that instead of flashing those nighties flash the so called "stable" ones.
Sometimes with CM10 CWM recovery works a lot better than twrp if flashing with CM10.
Be sure that the rom zip file is in your internal sdcard before flashing.
I still cannot see why anyone would want to flash CM10/AOSP/AOKP roms......
By doing that most all the bells and whistles which normally come with the
Galaxy S4 phones will no longer be found after flashing any of those roms..
Sadly, instead of bells and whistles there will be many issues with those roms like the audio
during video playback will be so quiet that you will need a headset to hear it, that's if you
have good hearing.
Other issues will arise like bluetooth not working properly and the camera in general will be
degraded not only in the quality of the photos and videos but in the actual user interface it
will look like some home made app which does not even resemble the stock camera + you
will find it only has about one half as many options for picture taking and video recording.
Good luck!
Misterjunky said:
This should fix the problem, here is CWM Recovery for the i9505 phone,
You will need to Odin flash this recovery: http://downloadandroidrom.com/file/GalaxyS4/GT-i9505/recovery/CWM/i9505-cwm-recovery-6.0.3.2-4.tar
Sometimes with CM10 CWM recovery works a lot better than twrp if flashing with CM10.
Be sure that the rom zip file is in your internal sdcard before flashing.
I still cannot see why anyone would want to flash CM10/AOSP/AOKP roms......
By doing that most all the bells and whistles which normally come with the
Galaxy S4 phones will no longer be found after flashing any of those roms..
Click to expand...
Click to collapse
I hope flashing using CWM would resolve the issue. The so called bells and whistles are the ones that annoy me most about Samsung. But then again, it's just my personal preference.
I was able to successfully install CM10.1 by flashing it repeatedly until it installed. Dunno if this is a bug in the ROM or recovery, but I do hope that this gets settled soon.
jorel000 said:
I was able to successfully install CM10.1 by flashing it repeatedly until it installed. Dunno if this is a bug in the ROM or recovery, but I do hope that this gets settled soon.
Click to expand...
Click to collapse
Had the same thing too, did you use the official release?
I had it with official, but it was fixed in hazanwars unofficial release just so you know