Related
Hi,
I'm currently using Koush's ICS Alpha 11, I've downloaded the official 4.0.3 version and tried to rename it "update.zip" and flash but it fails.
I'd really appreciate any help.
Thanks!
Did you go back to stock 2.3.6 and flash in stock recovery
BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
Oh, so I should download this:
Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
... rename it to update.zip and then back into CWR and then ICS?
Download stock 2.3.6 and flash it you will loose clockwork mod.you have to do this to apply the official
Rename it to update.zip
In fastboot mode go to recovery and select it with your power button
When you see the android question mark hold up and power again
Choose apply update.zip and bam your done
I forgot get voodoo ota root keeper from the market and run it before flashing the stock rom
Good luck and keep ne posted
BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
Can't seem to find FULL stock 2.3.6 for nexus S, some links floating around the web are just the update packs (around 12mb), not full.
ibr4him said:
Can't seem to find FULL stock 2.3.6 for nexus S, some links floating around the web are just the update packs (around 12mb), not full.
Click to expand...
Click to collapse
There's a stickied post right here on the forums (this forum, in fact). It has every OTA released.
- chris
You do not need to go back to stock recovery. Do it all from cwm recovery.
Full wipe and flash the 2.3.6 from
Flash the ota file.
Reboot. The reboot into the os will flash the stock recovery
Sent from my Nexus S using XDA App
Hey guys, I'm in a similar situation too, I'm on Carbon ROM and I was waiting for a Stock update. So is there any way that I can update and keep the root? Because I think when I'll flash the stock 2.3.6, I'll lose root.
ok so I went back to 2.3.6 stock, and susprisingly I didn't lose my root/cwr or anything, then I went into recovery again and tried installing update.zip (which is ICS official stock) but the same error:
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
When you go back to stock you need to do a wipe.
Sent from my Nexus S using XDA App
I did wipe partition as well as cache. let me try again though.
Format everything but sdcard. Flash the official 2.3.6 T-Mobile rom. Flash the official ota update for said rom and your good. You would have to have a the 9020t model of course
Sent from my Nexus S using XDA App
albundy2010 said:
Format everything but sdcard. Flash the official 2.3.6 T-Mobile rom. Flash the official ota update for said rom and your good. You would have to have a the 9020t model of course
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
How do I format? from PC? delete everything from the mounted usb volume?
From cwm recovery. Mounts and storage. Just DONT format your sdcard. Your backups are there.
Sent from my Nexus S using XDA App
I don't have clockwork anymore. I see limited options now, and the title on top is "Android System Recovery <3e>", but I do see an unlock icon when the phone boots.
You need to reflash clockwork from fastboot. When you load a stock os it overwrites the recovery
Sent from my Nexus S using XDA App
I have no clue how I did it couple months back, can you please point me to a guide that shows how to flash cwr on 2.3.6? many thanks
What rom that is on the phone does not matter . You just need to get your phone recognized on a computer with fastboot. Then flash the recovery from there. Or just boot the recovery directly from fastboot.
Sent from my Nexus S using XDA App
hmmmmmmmmmmmmmmmmmmmmmmm
are you going to go around and say stupid crap in every thread now?
Sent from my Nexus S using XDA App
Hi everyone. After 5 months, I decided to come back and try to root my phone again.
First, I'm on JB 4.1.2 with my VZW GS3.
I get to this step in the process.... Step 4 - Rooting Your Device and Unlocking Your Bootloader and every option I choose, tells me that the signature failed and the installation is aborted. Can someone tell me what I did wrong, if it can be fixed, and how?
I was once rooted before, and went back to stock using ODIN in the past. Will that have an effect on it?
When I got to Step 3, I used these instructions: •Flash the VRALEC Bootchain using ODIN v3.07 - My phone shows VRBMB1 - should I have used that boot chain instead? Can I still flash it using ODIN, over what is already there?
I can get my phone to boot normally, but when it boots it just shows custom at the bottom. I haven't bricked it or anything, I'm just concerned I haven't messed up the root process all together.
Thanks for the help...
Did you choose to install the zip in recovery or did you pick a different option? First make sure your zip is good and you didn't get a bad download. You can flash the VRALEC Bootchain whenever, and you must do it before flashing your recovery. If installing your zip isn't working in CWM try installing TWRP and flash the zip on that recovery instead. And no restoring back to stock with Odin won't affect anything.
Sent from my Verizon Samsung Galaxy SIII
joshua5683 said:
Did you choose to install the zip in recovery or did you pick a different option? You can flash the VRALEC Bootchain whenever, and you must do it before flashing your recovery. If installing your zip isn't working in CWM try installing TWRP and flash the zip on that recovery instead. And no restoring back to stock with Odin won't affect anything.
Sent from my Verizon Samsung Galaxy SIII
Click to expand...
Click to collapse
I chose to install the zip in recovery, and I did it after flashing my recovery.
Can I install TWRP using ODIN, right over the CWM installation? Will it hurt anything?
Thanks for your help!!
lou1210 said:
I chose to install the zip in recovery, and I did it after flashing my recovery.
Can I install TWRP using ODIN, right over the CWM installation? Will it hurt anything?
Thanks for your help!!
Click to expand...
Click to collapse
Here's what I did:
1. Booted into ODIN, Flashed VARELC
2. Booted into ODIN again, Flashed Recovery (following ALL directions exactly) Pulled battery, put back in, went back into ODIN
3. Attempted to install the Update -> Download SuperSU + Unlocked Bootloader (showed FIXED in the file name)
4. Got this process: finding update package, opening update package, verifying package, signature verification failed, Installation Aborted.
lou1210 said:
Here's what I did:
1. Booted into ODIN, Flashed VARELC
2. Booted into ODIN again, Flashed Recovery (following ALL directions exactly) Pulled battery, put back in, went back into ODIN
3. Attempted to install the Update -> Download SuperSU + Unlocked Bootloader (showed FIXED in the file name)
4. Got this process: finding update package, opening update package, verifying package, signature verification failed, Installation Aborted.
Click to expand...
Click to collapse
Yeah you're doing everything right I don't know why it's saying that. Try installing with TWRP - you can flash it at anytime and overwrite the old recovery.
Sent from my Verizon Samsung Galaxy SIII
lou1210 said:
Here's what I did:
1. Booted into ODIN, Flashed VARELC
2. Booted into ODIN again, Flashed Recovery (following ALL directions exactly) Pulled battery, put back in, went back into ODIN
3. Attempted to install the Update -> Download SuperSU + Unlocked Bootloader (showed FIXED in the file name)
4. Got this process: finding update package, opening update package, verifying package, signature verification failed, Installation Aborted.
Click to expand...
Click to collapse
Your second and third step are wrong. You need to flash SuperSU in recovery NOT download mode. Download mode handles "tar" files, recovery handles "zips."
Edit: well, the latter half of your second step is wrong, pull battery then boot into recovery mode...home, volume UP, and power
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Your second and third step are wrong. You need to flash SuperSU in recovery NOT download mode. Download mode handles "tar" files, recovery handles "zips."
Edit: well, the latter half of your second step is wrong, pull battery then boot into recovery mode...home, volume UP, and power
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I'm sorry, I am doing the supers in recovery, not ODIN. I tried both CWM now and TWRP and still have the same exact error messages. Not sure what to do to fix this, but I'm almost ready to try to reverse what I did. I have been wanting to remove the bloatware and now I saw the Carbon ROM that looks pretty cool. If you can get me past this issue, it would be great.
Oh I just noticed you chose update. You have to choose to install in CWM not update. But if it didn't work in TWRP either it sounds like there is something wrong with the zip file. Have you tried redownloading the zip file?
Sent from my Verizon Samsung Galaxy SIII
lou1210 said:
I'm sorry, I am doing the supers in recovery, not ODIN. I tried both CWM now and TWRP and still have the same exact error messages. Not sure what to do to fix this, but I'm almost ready to try to reverse what I did. I have been wanting to remove the bloatware and now I saw the Carbon ROM that looks pretty cool. If you can get me past this issue, it would be great.
Click to expand...
Click to collapse
Here is another interesting thing....
Should I have an install or is Apply Update the same thing. When I boot into recovery, here are my choices:
reboot
apply update from adb
apply update from external storage
wipe data/factory reset
wipe cache
apply update from cache
Do I have the right version of recovery? Does this help any?
Ok. So I decided to download a new recovery file for CWM and this time it worked.
I'm not sure what told me to do it, but I decided to give it a go.
Next question, I remember the root processing being very involved with clearing cache, clearing dalvik cache, etc.
Is there a link to the newest process on how to root exactly and apply new ROMs? I of course will be backing up my existing ROM first.
lou1210 said:
Ok. So I decided to download a new recovery file for CWM and this time it worked.
I'm not sure what told me to do it, but I decided to give it a go.
Next question, I remember the root processing being very involved with clearing cache, clearing dalvik cache, etc.
Is there a link to the newest process on how to root exactly and apply new ROMs? I of course will be backing up my existing ROM first.
Click to expand...
Click to collapse
That's odd someone else had that issue where install wasn't an option. He ended up using TWRP. That clearing thing is for flashing roms. The way you flash every rom is wipe data/factory reset, clear cache, clear dalvik cache, and wipe /system. Make a backup before. I recommend using TWRP cause there have been times in CWM where I would try to restore and I would get an MD5 mismatch error, which I've never gotten on TWRP
Sent from my Verizon Samsung Galaxy SIII
I was thinking of using the carbon ROM. I realized that I didn't install the md5 file extension for cwm using ODIN so I went back and flashed it with one i was able to find, and it worked. I'm ok with using twrp but I haven't been able to find an md5 file for ODIN. Can you give me a link to one? I've only found .tar files and that seems to have been my problem. I might still try to use cwm now that I have my existing stock ROM backed up. Still debating.
On a side note, if I decide to unroot again, since I have not flashed, is there a method for that so I don't lose what I've got?
Sent from my SCH-I535 using Tapatalk 2
lou1210 said:
I was thinking of using the carbon ROM. I realized that I didn't install the md5 file extension for cwm using ODIN so I went back and flashed it with one i was able to find, and it worked. I'm ok with using twrp but I haven't been able to find an md5 file for ODIN. Can you give me a link to one? I've only found .tar files and that seems to have been my problem. I might still try to use cwm now that I have my existing stock ROM backed up. Still debating.
On a side note, if I decide to unroot again, since I have not flashed, is there a method for that so I don't lose what I've got?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
What do you mean you can't find the md5? You can flash the .tar twrp recovery in Odin the same way you flash md5s. And no sorry I don't know of any way to unroot without flashing a factory image. But to get your apps back you can use App Backup and Restore. It won't recover the app data obviously cause you need root for that but it's faster for restoring your apps so you don't have to make a list and download each one off the Play Store.
The file I had used didn't have an md5 filename and I think that's why it failed. I found one and downloaded it so it worked for me after that. Thank you for the unroot info too.
Sent from my SCH-I535 using Tapatalk 2
lou1210 said:
The file I had used didn't have an md5 filename and I think that's why it failed. I found one and downloaded it so it worked for me after that. Thank you for the unroot info too.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
No problem glad you got things working
Sent from my SCH-I535 using xda app-developers app
Hello,
Here is I want to share my work of latest AOSP Jelly Bean 4.3 with build number JSS15J for Nexus 7 (WIFI).
I have do this from the source on google.
This ROM can be flash via CWM (TWRP not tested). Make sure you have installing CWM first (I have 6.0.3.3 on my tablet).
Let's to the point .
Download Link : https://www.dropbox.com/sh/x2wov7n2f8m7eze/5rzHYlV4tq/grouper43-gapps.zip
Instruction :
Please backup your current ROM first before execute this.
Make sure you have upgrade Bootloader v4.23 and Radio 1231_0.18.0_0409
1. Download and put them in your internal SDCard.
2. Reboot into your recovery mode.
3. Wipe Data/Factory.
4. Wipe Cache Partition.
5. Wipe Dalvik Cache.
6. Installing from ZIP
7. Reboot and enjoy.
Features :
1. ROM already Deodexed.
2. Dual Panel Settings.
3. Combined with Latest Gapps.
4. Latest Kernel 4.3 (MR2)
5. Advanced Power Menu
Android 4.3 Version :
JWR66V is 4.3_r1
JSR78D is 4.3_r2
JSS15J is 4.3_r2.1
DO WITH YOU OWN RISK
Credits :
Google
Thank you .
Reserved .
First...downloading now.......
No root?
Sent from my Nexus 7 using xda app-developers app
_-..zKiLLA..-_ said:
No root?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, You must installing latest Superuser/SuperSU after that if you want to root them .
This is pure stock with zero customization and tweak am I right?
Sent from my GT-I9100 using Tapatalk 4
infatality said:
This is pure stock with zero customization and tweak am I right?
Sent from my GT-I9100 using Tapatalk 4
Click to expand...
Click to collapse
It's pure stock who have compile from the source on Google. But, I have add power menu and combining with latest Gapps.
why there is a bootloader requirement?
Sent from my Nexus 7
1Q84 said:
why there is a bootloader requirement?
Sent from my Nexus 7
Click to expand...
Click to collapse
Actually, that was optional. I said in that above because their stock ROM include with new Radio and Bootloader. Only keep they can working properly .
failed to install?
podagee said:
failed to install?
Click to expand...
Click to collapse
Can you specific about the error message ?
tried installing it through twrp and it says failed right at the end.is this for grouper?
TWRP says:
extracting system...
set_perm: some changes failed
E:Errror executing updater binary in zip '/sdcard/download/aosp43-grouper-gapps.zip
Error flashing zip '/sdcard/download/aosp4-grouper-gapps.zip
I think your source is for tilapia no radio in grouper I tried install same errors
Sent from my Nexus 7 using Tapatalk 4
_-..zKiLLA..-_ said:
TWRP says:
extracting system...
set_perm: some changes failed
E:Errror executing updater binary in zip '/sdcard/download/aosp43-grouper-gapps.zip
Error flashing zip '/sdcard/download/aosp4-grouper-gapps.zip
Click to expand...
Click to collapse
jimchee said:
I think your source is for tilapia no radio in grouper I tried install same errors
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
podagee said:
tried installing it through twrp and it says failed right at the end.is this for grouper?
Click to expand...
Click to collapse
I am sorry, Please hold on while I checking to fix and reupload them.
The file has been examining and corrected. You can download them now.
Any chance for an Odexed base?
I tried again to install and just sat on the boot screen and tried again after booting back into recovery and clearing dalvik cache same result, has anyone else successfully booted? If so tell me how you proceeded on install, I formatted data and cache then wiped boot and did clean install, it did install but just stayed on boot animation, let it run for at least 10 minutes but never booted into Rom,
Sent from my Nexus 7 using Tapatalk 4
jimchee said:
I tried again to install and just sat on the boot screen and tried again after booting back into recovery and clearing dalvik cache same result, has anyone else successfully booted? If so tell me how you proceeded on install, I formatted data and cache then wiped boot and did clean install, it did install but just stayed on boot animation, let it run for at least 10 minutes but never booted into Rom,
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
same here no success with boot, it just hangs. ill just stick to cm10.2
First, I did search XDA and even Google. Maybe I didn't find it. Maybe cause you can't. Idk.
Anyways, I want to revert to 100% stock via twrp ..... Can I ? If so. Where Is the correct .Zip for this.
Thanks.
Sent from my Nexus 5
Dude you don't need twrp to return to stock..... Just flash the factory images ....
You can find the link in the general section
I have twrp. My pc is currently not working. That's why I asked for a zip to use in twrp......
Sent from my Nexus 5
myturbo1 said:
I have twrp. My pc is currently not working. That's why I asked for a zip to use in twrp......
Sent from my Nexus 5
Click to expand...
Click to collapse
There is more to it than that.
Download stock rooted rom (Resources section of sticky in my signature)
Download Stock recovery zip (Resources section of sticky in my signature)
Install "BootUnlocker"
1) Flash rooted stock zip
2) Flash stock recovery zip
3) Reboot to check you have stock recovery
4) Lock bootloader and reset tamper via BootUnlocker
5) Check bootloader locked
6) Full unroot via SuperSU
So Just received my 2.2 Update, and was going to install it when I remembered, "Wait! I am rooted!"
My question is can I update too 2.2 and not have anything "bad" happen.(Root Lost, System Boot Loop, etc)
I am running Stock Update 2.1 with Root.
EDIT: I have CWM set as my recovery.
Another user did it in general forum and it doesnt flash because of mismatch
Just like the last Lollipop update, if you're rooted, you'll need to return to stock.
Otherwise, wait until the full rom .zip is available and then download it and flash it in your custom recovery followed by re-flashing the latest SuperSU .zip.
Sent from my SHIELD Tablet using XDA Free mobile app
An Droid said:
Just like the last Lollipop update, if you're rooted, you'll need to return to stock.
Otherwise, wait until the full rom .zip is available and then download it and flash it in your custom recovery followed by re-flashing the latest SuperSU .zip.
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Im on Philz
Can I flash recovery image via "fastboot flash recovery recovery.img", then reboot the tablet, install the OTA and then with Flashify flash Philz again?
EDIT: I just re-read what I posted. Can I use flashify to flash stock recovery, updating with OTA and then reflash Philz?
NaminatoR1254jaime.sier said:
Im on Philz
Can I flash recovery image via "fastboot flash recovery recovery.img", then reboot the tablet, install the OTA and then with Flashify flash Philz again?
EDIT: I just re-read what I posted. Can I use flashify to flash stock recovery, updating with OTA and then reflash Philz?
Click to expand...
Click to collapse
The "full" 2.2 OTAs are available everywhere on xda right now...Just flash the appropriate one, reflash recovery (if you have to) and then reflash supersu.
ailima said:
The "full" 2.2 OTAs are available everywhere on xda right now...Just flash the appropriate one, reflash recovery (if you have to) and then reflash supersu.
Click to expand...
Click to collapse
I already updated hahaha, I didnt remember this post. Thanks anyway!!