I have Phil Touch 6.0.4.5 CWM installed.
I put this on to try CM11. Didn't like it so re-flashed the the latest official ROM and its been running fine for a while now.
Theres a new official update out I wanted to try but flashing via CWM it says "Installation aborted".
I then tried the older official ROM and this too aborts hower CM11 installs fine.
Any ideas? I am Wiping ROM and clearing Cache.
You cannot flash official updates with custom recovery. You need the stock recovery for it.
A word of caution. The new OTA update most likely has knox. If you plan to try out other custom roms, refrain from flashing. If you are only a stock rom user, flash away.
Silesh.Nair said:
You cannot flash official updates with custom recovery. You need the stock recovery for it.
A word of caution. The new OTA update most likely has knox. If you plan to try out other custom roms, refrain from flashing. If you are only a stock rom user, flash away.
Click to expand...
Click to collapse
Thats odd. I could have sworn I reflashed the official rom using CWM.
Thanks for clearing that up.
Can I still enter standard recovery having CWM on there or do I need to reflash via a standard recovery via odin?
You need to flash one using Odin. If you have a flashable recovery zip file, you can replace the recovery image in the zip file with a stock one.
Sent from my GT-I9205 using Tapatalk
Related
Hello,
I am really a beginner with flashing roms and I just flashed my first CWM and CM 10.1 rom.
But the version I chose has a few bugs, so I want to flash a different CM version. should I do it the same way as I changed from the stock ROM to CM 10.1, by moving it to root path and then via recovery choose install zip from sd card? What I also don't know is what will happen with the GAPPS. I flashed it right away the first CM flashing. but will I need to flash GAPPS again?
Also, If I want to change from non-touch CWM to touch-CWM, I do it via Odin in the same way I first flashed the non-touch CWM? Will that over-write the existing CWM?
Sorry I am really a beginner, but at least I flashed the first rom
Thanks to everyone who helps :good:
verynoob said:
Hello,
I am really a beginner with flashing roms and I just flashed my first CWM and CM 10.1 rom.
But the version I chose has a few bugs, so I want to flash a different CM version. should I do it the same way as I changed from the stock ROM to CM 10.1, by moving it to root path and then via recovery choose install zip from sd card? What I also don't know is what will happen with the GAPPS. I flashed it right away the first CM flashing. but will I need to flash GAPPS again?
Also, If I want to change from non-touch CWM to touch-CWM, I do it via Odin in the same way I first flashed the non-touch CWM? Will that over-write the existing CWM?
Sorry I am really a beginner, but at least I flashed the first rom
Thanks to everyone who helps :good:
Click to expand...
Click to collapse
Yes, all you said is the correct way. Its that way itself.
To sum it up, if you want to flash a different CM, reboot into CWM recovery, Wipe Data/Cache/Dalvik cache and flash the zip package and flash the gapps and do a wipe data/cache/dalvik cache again. Yes you need to flash GAPPS each time when you install CM.
For changing recovery, if you have another version installable via Odin, then you can go on with it, and it will replace your existing recovery.
Be sure to check this Table to know which GAPPS should be installed for which CM version.
Happy Flashing!
I have Galaxy note 1 i717D from Telus canada. it was giving me some troubles so i decided to download stock firmware from this link
http://androidromupdate.com/2013/05...elly-bean-upgrade-on-telus-galaxy-note-i717d/
Everything went okay but after restart its showing me these errors
https://share.htc.com/3mq2dJEj7
Could anybody please let me know what is this and how can i go from here. I tried wipe device, wipe cache but all are coming back with red error lines.
I took out the battery to restart it its showing me android sign with ball spinning in its tummy
Thanks
Update your recovery to TWRP 2.5.
rangercaptain said:
Update your recovery to TWRP 2.5.
Click to expand...
Click to collapse
Could you please let me know how can i do this, I am trying to find it myself too but if anycase you have tried please let me know, Do i need to do it even when I am trying to do stock recovery ?
I don't see what installing TWRP 2.5 has anything to do with this install. OP is installing stock ROM with odin which means stock recovery.
You should be using Odin to do the install as instructed in the link. I don't understand why the stock recovery is even showing after a restart or why the you would toggle it after a flash.
Agoattamer said:
I don't see what installing TWRP 2.5 has anything to do with this install. OP is installing stock ROM with odin which means stock recovery.
Click to expand...
Click to collapse
Let me draw you a picture. Flash TWRP with Odin. Let it root the phone. Use TWRP to flash the rom, stock or custom.
Installing stock anything doesn't mean stock recovery. Odin is used when phone is in download mode.
But the ROM he is flashing is a stock.tar. That can only be flashed with odin. Custom recovery has nothing to do with it and will not help him achieve what he is wanting to do. OP has even mentioned he wants stock recovery. What he is doing in stock recovery after flashing the ROM with Odin has me baffled.
I don't know why "Install TWRP" is the answer to all problems on this forum. Running the updated CWM has suited me just fine and has been able to flash any ROM I wanted to try.
I'm new to this forum and find the i717 a wee bit more complicated than my old phone. (a Galaxy S 4g.)
I've managed to get CWM touch 5.5.0.4 on the phone and have successfully flashed the deodexed stock jelly bean rom. However when I try to flash any of the "quincy.att" based rom, CWM gives me an error, which I imagine means that I need a more recent CWM. Before I flashed stock jelly bean, I was able to get the 6.0.3.6 quincy.att CWM on the phone using the terminal but when I tried using it, it did not see the external sdcard and I could not get there to flash any rom. I tried using ODIN to flash CWM 5.8.4.3 but ODIN just sat there and nothing got loaded onto the phone at all.
So it is kind of a chicken and egg situation here. What is the minimum version of CWM I need to flash any of the quincy.att roms and how do I get it on there and working? Or am I supposed to use TWRP? I haven't tried that. I remember it from the 4g and it was a pain to use on that phone. I have tried to flash the 10.1 quincy.att plain Cyanogen and the chameleon rom and I just get error messages from CWM,
Just use twrp.....your probably getting error 7 ...install twrp
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
TWRP is piece of cake here. you will never look back
I'm having issues getting cwm 6.0.4.4 to work.... 6.0.4.3 touch or regular work just fine, but the few times I've tried flashing 6.0.4.4 in order to flash the latest Kit Kat I get stuck in a bootloop. The only way to fix it is to remove my battery, flash twrp with Odin, wipe everything, flash cwm (earlier than 6.0.4.4) and reflash a ROM. I've tried: updating through ROM manager, flashing 6.0.4.4 in recovery, converting a zip to a tar (thinking maybe the file was corrupted). I'm beginning to think my phone just doesn't like Kit Kat.... Now I'm back on Padawan because it's like literally the most stable ROM for my phone. Any ideas?
longhairdaddy said:
I'm having issues getting cwm 6.0.4.4 to work.... 6.0.4.3 touch or regular work just fine, but the few times I've tried flashing 6.0.4.4 in order to flash the latest Kit Kat I get stuck in a bootloop. The only way to fix it is to remove my battery, flash twrp with Odin, wipe everything, flash cwm (earlier than 6.0.4.4) and reflash a ROM. I've tried: updating through ROM manager, flashing 6.0.4.4 in recovery, converting a zip to a tar (thinking maybe the file was corrupted). I'm beginning to think my phone just doesn't like Kit Kat.... Now I'm back on Padawan because it's like literally the most stable ROM for my phone. Any ideas?
Click to expand...
Click to collapse
If 6.0.4.3 touch works "fine", why don't you just use that?
veningTrMarchal
tube517 said:
If 6.0.4.3 touch works "fine", why don't you just use that?
Click to expand...
Click to collapse
cwm 6.0.4.4 is recommended for the Unofficial AOKP 4.4.2 flash and I couldn't get it to install with 6.0.4.3. It installs with 6.0.4.4 but ends up in a bootloop.
longhairdaddy said:
cwm 6.0.4.4 is recommended for the Unofficial AOKP 4.4.2 flash and I couldn't get it to install with 6.0.4.3. It installs with 6.0.4.4 but ends up in a bootloop.
Click to expand...
Click to collapse
Try CM11 for KitKat. It's very stable.
tube517 said:
Try CM11 for KitKat. It's very stable.
Click to expand...
Click to collapse
I actually did try CM11 Kit Kat and liked it but about ten minutes after everything boots up it will force close and go into a boot loop. I've tried the various gapps packages, installing without gapps then flashing them, wiping dalvic before and after and in between, I dunno.
4.3 ROMs run like a diesel, it just seems I can't get 4.4s to be stable. I just now flashed the Beanstalk 4.4.2 along with the updated gapps and can't get past the beanstalk animation. Sat there for an hour.
I appreciate the input though.
longhairdaddy said:
I actually did try CM11 Kit Kat and liked it but about ten minutes after everything boots up it will force close and go into a boot loop. I've tried the various gapps packages, installing without gapps then flashing them, wiping dalvic before and after and in between, I dunno.
4.3 ROMs run like a diesel, it just seems I can't get 4.4s to be stable. I just now flashed the Beanstalk 4.4.2 along with the updated gapps and can't get past the beanstalk animation. Sat there for an hour.
I appreciate the input though.
Click to expand...
Click to collapse
I had the same issues with 4.4 kitkat roms. Did you format system in CWM when wiping? This solved my bootloop issues. Also, make sure you have a clean download of the ROM. Flash the ROM twice back to back when flashing a new kitkat rom
My son's S4 is rooted, and a while back he loaded GooManager, and tried to install recovery with it. Phone still works, but tries to load code over the USB on power-up.
What does GooManager do to the system, and how can we undo it? Or should the phone just be wiped and odin flashed to 4.3?
Jim
jmdearras said:
My son's S4 is rooted, and a while back he loaded GooManager, and tried to install recovery with it. Phone still works, but tries to load code over the USB on power-up.
What does GooManager do to the system, and how can we undo it? Or should the phone just be wiped and odin flashed to 4.3?
Jim
Click to expand...
Click to collapse
That's a common problem. You can't install a custom recovery using GooManager. At best, if you're running MDK, you can use Loki to flash a custom recovery.
The best fix for your situation is to flash a stock ROM. At the very least, grab the recovery from the stock ROM and flash that.
k1mu said:
That's a common problem. You can't install a custom recovery using GooManager. At best, if you're running MDK, you can use Loki to flash a custom recovery.
The best fix for your situation is to flash a stock ROM. At the very least, grab the recovery from the stock ROM and flash that.
Click to expand...
Click to collapse
Do you know what GooManager does before rebooting? I'd like to manually remove it.
Where is the stock ROM for Verizon 4.2.2? Or can I just Odin 4.3?
Thanks much!
Jim
Hello everyone,
I recently picked up a couple GS2's for dirt cheap just to mess around with. I am having a very hard time getting any custom recovery installed on them and I was wondering if there is a trick to it that I am not seeing. I've tried flashing various CWM modified kernels using odin with no luck. They flash successfully but still boot to 3e when I boot into recovery. I tried flashing a modified update.zip from the CM website and it fails with the error "failed to verify whole-file signature". Most recently I did a complete restore using odin with a rooted image, then used Rom manager to install CWM. Rom managed says it is successful, but when I reboot into recovery it launches 3e and attempts to do something that returns the same error "failed to verify whole-file signature". Any input of suggestions would be appreciated.
Bklynrx7 said:
Hello everyone,
I recently picked up a couple GS2's for dirt cheap just to mess around with. I am having a very hard time getting any custom recovery installed on them and I was wondering if there is a trick to it that I am not seeing.
Click to expand...
Click to collapse
The recovery is compiled into the kernel on this phone, but it seems that you understand that already. The kernel and system must match. You probably need to be rooted. You have not given any specifics about the firmware, what is already installed, what specific item you are trying to install, etc.
I've tried flashing various CWM modified kernels using odin with no luck. They flash successfully but still boot to 3e when I boot into recovery.
Click to expand...
Click to collapse
This does not actually seem logical. I'm wondering if you are not mentioning something that I would need to know to determine why you are getting this result. If you install a custom kernel containing a custom recovery, you should then be able to boot into the custom recovery. If you still have 3e recovery, it indicates that you still have the stock kernel installed.
I tried flashing a modified update.zip from the CM website and it fails with the error "failed to verify whole-file signature".
Click to expand...
Click to collapse
I would not expect that to be successful. Among other things, it is probably not specific for the I777.
Most recently I did a complete restore using odin with a rooted image, then used Rom manager to install CWM. Rom managed says it is successful, but when I reboot into recovery it launches 3e and attempts to do something that returns the same error "failed to verify whole-file signature". Any input of suggestions would be appreciated.
Click to expand...
Click to collapse
Do not use Rom manager. It does not work with the I777, and can cause unrecoverable damage in some cases. There is a sticky post about it here in the forums.
You can find various resources in the Download Repository. See the link in my signature.
Here's what I would do:
Flash the latest stock Jellybean firmware, UCMD8, from the Repository.
Root using Framaroot with the Aragorn exploit.
Flash the AJK v4.9 NoSwap kernel using Mobile Odin Pro or Mobile Odin Lite. You have to extract the boot.img from the kernel zip and flash that, but don't let it boot into system. Instead, you can boot directly into CWM and flash the AJK v 4.9 NoSwap kernel zip, or if you prefer, you can flash some other custom firmware at this point.
creepyncrawly said:
The recovery is compiled into the kernel on this phone, but it seems that you understand that already. The kernel and system must match. You probably need to be rooted. You have not given any specifics about the firmware, what is already installed, what specific item you are trying to install, etc.
This does not actually seem logical. I'm wondering if you are not mentioning something that I would need to know to determine why you are getting this result. If you install a custom kernel containing a custom recovery, you should then be able to boot into the custom recovery. If you still have 3e recovery, it indicates that you still have the stock kernel installed.
I would not expect that to be successful. Among other things, it is probably not specific for the I777.
Do not use Rom manager. It does not work with the I777, and can cause unrecoverable damage in some cases. There is a sticky post about it here in the forums.
You can find various resources in the Download Repository. See the link in my signature.
Here's what I would do:
Flash the latest stock Jellybean firmware, UCMD8, from the Repository.
Root using Framaroot with the Aragorn exploit.
Flash the AJK v4.9 NoSwap kernel using Mobile Odin Pro or Mobile Odin Lite. You have to extract the boot.img from the kernel zip and flash that, but don't let it boot into system. Instead, you can boot directly into CWM and flash the AJK v 4.9 NoSwap kernel zip, or if you prefer, you can flash some other custom firmware at this point.
Click to expand...
Click to collapse
Sorry if I want clear. The phones are currently on 2.3.6. I tried using framaroot but it was not successful. The app said it was successful, but there was no supersu after I rebooted. I successfully got the phone rooted using one of the one-click odin flashers posted on these forums that are said to return it to factory + root. I then tried to use rom manager which said it was successful, but wasn't. That makes sense now that you're telling me its not compatible. Ill try upgrading to the JB firmware first, then ill try framaroot. Thanks for the suggestion
I just wanted to update the thread and say that this worked. Thanks again. I'm having an issue getting Gapps flashed but that's another topic. My big concern was that the phones wouldn't charge without boot looping because they had the wrong battery installed. The Stock Jellybean with the kernel you suggested fixed that.
Bklynrx7 said:
I just wanted to update the thread and say that this worked. Thanks again. I'm having an issue getting Gapps flashed but that's another topic. My big concern was that the phones wouldn't charge without boot looping because they had the wrong battery installed. The Stock Jellybean with the kernel you suggested fixed that.
Click to expand...
Click to collapse
Maybe I could help. What error does it give when you flash gapps?