Related
Does clockworkmod overwrite the stock recovery? If it does then to me it is not a safe method to root a phone. If something goes wrong while flashing clockwork you will lose the stock recovery and can never reflash anything else. Is my understanding correct? This is why I am hesitant to root my phone. Please advice.
Thanks.
datzstr8 said:
Does clockworkmod overwrite the stock recovery? If it does then to me it is not a safe method to root a phone. If something goes wrong while flashing clockwork you will lose the stock recovery and can never reflash anything else. Is my understanding correct? This is why I am hesitant to root my phone. Please advice.
Thanks.
Click to expand...
Click to collapse
Its fairly safe. You could always flash the recovery thru odin found here:
http://forum.xda-developers.com/showthread.php?t=1332103
Has anyone tried to flash clockwork and failed? What happened afterwards? I assume odin won't work anymore because it requires a recovery partition to work.
I guess what I am still confused about is if clockwork writes over the stock recovery or does it keep the stock recovery in-tacked. I would prefer the later since then you can never break your phone.
With my dilemma would it be best for me to not install clockwork and just use an insecure kernel? Thanks.
It does overwrite the stock recovery i believe. But its very safe to flash. Ive never heard of someone borking a phone installing cwm recovery.
I have literally NEVER had a problem with clockworkmod, it's one of the best pieces of mobile software I've ever used.
kabuk1 said:
I have literally NEVER had a problem with clockworkmod, it's one of the best pieces of mobile software I've ever used.
Click to expand...
Click to collapse
Whole heartedly agree.
Sent from my SGH-T989 using xda premium
datzstr8 said:
Has anyone tried to flash clockwork and failed? What happened afterwards? I assume odin won't work anymore because it requires a recovery partition to work.
I guess what I am still confused about is if clockwork writes over the stock recovery or does it keep the stock recovery in-tacked. I would prefer the later since then you can never break your phone.
Click to expand...
Click to collapse
Odin has NOTHING to do with the recovery partition. ODIN only works in download mode on your phone. You can have a blank recovery partition and it'll still work, as well as the rom, and flashing other things too. The recovery partition stock has one function, to do a factory reset incase of problems. (Not to be confused with the one from inside android, that only formats /data. This one replaces the system partition as well.) CWM is very safe, I really wouldn't worry about it. Just follow the instructions carefully and you'll be fine.
Also, once you get cwm installed on there, I'd suggest doing a backup before you make any changes. Always handy to have your stock image at hand, just incase.
And also, even with stock recovery, you can still break your phone. It's not easy to brick a GS2, but it can be done. Just remember, as long as you can get the phone into download mode, it's not bricked. You can always odin back the stock partitions if you run into issues.
I was a little worried about using it with this phone. No problems to report. Just had to make backup in recovery.
Sent from my SGH-T989 using xda premium
Thanks mstrk242 for the great explanation. I thought the "download" and "recovery" were two states of a single program. It is clear now that they are separate. You just cleared all my worries.
You said "It's not easy to brick a GS2, but it can be done," can you tell me how this can happen? Just curious. Thanks much.
If you're going to be rooting/flashing at all, you'll have to get comfortable with cwm, Odin, and the other tools that are available for the phone.
This is my second Android phone, both have been rooted with custom roms, and at any point I've run into trouble (which is rare) I've found the tools and the help I need on here by searching a little bit. If you're willing to spend the time doing a bit of reading and know your way around a computer a bit, you won't have a problem. Just make sure you're 100% sure whatever you're flashing is for YOUR phone hardware.
It's not nearly as scary as it sounds once you get going on it and there's a lot to benefit from it.
Cheers and good luck.
Sent from my SGH-T989 using xda premium
datzstr8 said:
Thanks mstrk242 for the great explanation. I thought the "download" and "recovery" were two states of a single program. It is clear now that they are separate. You just cleared all my worries.
You said "It's not easy to brick a GS2, but it can be done," can you tell me how this can happen? Just curious. Thanks much.
Click to expand...
Click to collapse
Easiest way is to flash a rom for the wrong phone and mess up the partition table. (IE flash an international version of the gs2 rom, you'll brick.)
As long as you get cwm installed on there, and flash the correct roms, you should really be ok.
You can go back to the stock recovery easily. You can do it through Odin or flash an unroot rom
Sent from my SGH-T989 with ClockworkMod ★Touch★ Recovery 5.8.1.3
Here is a stock rom backup for the Sprint G S III. I made the backup after doing a data wipe, so the rom is pure, no lingering data, ect.
Instructions:
-unzip the .zip file
-move the backup folder into your existing CWM folder on the S III internal memory
-restore in recovery
Again, this is a stock backup as some people need it.
https://dl.dropbox.com/u/19699565/fresh_GSIII_backup.zip
From my dropbox, so hit it easy.
Nice, know of some that will appreciate this.
bizdady said:
Nice, know of some that will appreciate this.
Click to expand...
Click to collapse
Me too
Sent from my SPH-D700 using XDA Premium App
<3
Warning: if you flash this make sure you clear Google wallets data as shown in a qbking77 video so you don't brick the secure element
Sent from my SPH-L710
How is this in any way a stock rom?
nabbed said:
How is this in any way a stock rom?
Click to expand...
Click to collapse
Give him a break. At least this isn't in development.
And he at least did something that could be useful until we get a real stock rom .zip or .tar
~E.R.A.
nabbed said:
How is this in any way a stock rom?
Click to expand...
Click to collapse
You have been in every thread criticizing everyone else s contributions...what the hell have you contributed?
nabbed said:
How is this in any way a stock rom?
Click to expand...
Click to collapse
It's not, it's a backup. That's not the point, it's still useful to many users that have possibly screwed their device but still have access to recovery. Especially until something official comes out.
will there be a stock package on odin different than just the stock boot image? my phone is bricked for no apparent reason(see my thread here http://forum.xda-developers.com/showthread.php?t=1731416) and flashing the stock boot image in odin does nothing. i Also cant get into CWM to flash my backup...
pizzlewizzle said:
will there be a stock package on odin different than just the stock boot image? my phone is bricked for no apparent reason(see my thread here http://forum.xda-developers.com/showthread.php?t=1731416) and flashing the stock boot image in odin does nothing. i Also cant get into CWM to flash my backup...
Click to expand...
Click to collapse
Eventually there will be, but a lot of people [to include major developers] still don't have the phone yet, so we'll have to be patient. I looked over it, though currently are you able to get into recovery still or no? Additionally did you try re-flashing the cwm recovery in odin?
I can get into download mode but not into CWMR. The only thing i have tried flashing since it bricked is boot-stock-sprint-sph-l710.tar (which sort of worked the first time). I'm at work and don't have my phone on me so i guess i could try flashing CWMR again later but this is really weird. Thanks for the reply. This is my first Sprint phone, but on my Droid X we had a program similar to Odin where you could push a .sbf file that included everything stock and basically just reset your phone to stock. Do these exist for Sprint phones? The . SBF files were usually rather large(around 350mb or so) but the boot-stock-sprint-sph-l710.tar is around 10 or 15 mb so i know it doesn't include all the system files...
Thanks again
teh roxxorz said:
Eventually there will be, but a lot of people [to include major developers] still don't have the phone yet, so we'll have to be patient. I looked over it, though currently are you able to get into recovery still or no? Additionally did you try re-flashing the cwm recovery in odin?
Click to expand...
Click to collapse
Lol i just replied the same thing over on another thread he posted in. Stop jumping around pizzle! if you can get into Odin chances are good you can flash cwm and then restore the backup
hahaha sorry about that. When I try and boot into recovery it looks like its about to go to Recovery and then freezes on the Galaxy S III screen. I'll try reflashing CWMR when I get home...Thanks for the advice
So is a back up a nandriod?
I have made a few but never resorted one, you just flash it same as a ROM and your done?
I misplaced my stock nandroid when I flashed CM10 build 2 and my extFs SD card had to be formatted to use again, I was sure I had in on PC but can't find it.
Thanks!
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
SectorNine50 said:
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
Click to expand...
Click to collapse
Is it possible that your hosts file needs modifying when installing the AT&T ROM? If the LG Support tool connects to LG's servers instead of your local http you set up, it will load the official ICS and completely wipe your phone to install that ROM... With my limited amount of knowledge, that's about all I could see if the process removes CWM Recovery.
Also, CWM 6.x is working fine for me, even manually flashed the touch recovery a few minutes ago, backed up my ROM and installed an updated ROM. No problems at all.
SectorNine50 said:
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
Click to expand...
Click to collapse
I don't know if anyone has tried the unbrick method with the new version of cwm but you might try twrp. When a similar version of cwm was in beta there were all sorts of issues. So maybe they haven't been fixed. Also are you installing cwm from GB? ICS has a locked boot loader so that might also be an issue.
http://forum.xda-developers.com/showthread.php?t=1888910
Now I would start with the unbricking guide for a 16th time but follow the directions to install twrp instead of cwm. You might also find you like it better. Good luck.
Sent from my LG-P930 using xda app-developers app
lordcheeto03 said:
Is it possible that your hosts file needs modifying when installing the AT&T ROM? If the LG Support tool connects to LG's servers instead of your local http you set up, it will load the official ICS and completely wipe your phone to install that ROM... With my limited amount of knowledge, that's about all I could see if the process removes CWM Recovery.
Also, CWM 6.x is working fine for me, even manually flashed the touch recovery a few minutes ago, backed up my ROM and installed an updated ROM. No problems at all.
Click to expand...
Click to collapse
I don't believe that the unbricking process would work if the hosts file was wrong, but I checked it again anyway, and it appears to be correct.
The AT&T ROM gets pushed via the abd shell after the unbrick and rooting process. The root appears to work, as the AT&T ROM that I push works fine, it's just not the ROM I want!
Swetnes said:
I don't know if anyone has tried the unbrick method with the new version of cwm but you might try twrp. When a similar version of cwm was in beta there were all sorts of issues. So maybe they haven't been fixed. Also are you installing cwm from GB? ICS has a locked boot loader so that might also be an issue.
http://forum.xda-developers.com/showthread.php?t=1888910
Now I would start with the unbricking guide for a 16th time but follow the directions to install twrp instead of cwm. You might also find you like it better. Good luck.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
After the unbricking process (after I get through all the nonsense on the Korean ROM), the phone is running the GB AT&T ROM, from there I push the CWM recovery.img to the phone using the abd shell. All seems to be working perfectly up until I go to flash the custom ROM! I don't get any errors when I flash the .zip either.
Initially I had installed CWM 6.x.x.x using the ROM Manager application. That's before all this nonsense started, and the phone was on the stock (but rooted) AT&T ICS ROM, so I know that's why I "bricked" my phone the first time.
I'll give TWRP a shot, hopefully that will work.
SectorNine50 said:
I don't believe that the unbricking process would work if the hosts file was wrong, but I checked it again anyway, and it appears to be correct.
The AT&T ROM gets pushed via the abd shell after the unbrick and rooting process. The root appears to work, as the AT&T ROM that I push works fine, it's just not the ROM I want!
After the unbricking process (after I get through all the nonsense on the Korean ROM), the phone is running the GB AT&T ROM, from there I push the CWM recovery.img to the phone using the abd shell. All seems to be working perfectly up until I go to flash the custom ROM! I don't get any errors when I flash the .zip either.
Initially I had installed CWM 6.x.x.x using the ROM Manager application. That's before all this nonsense started, and the phone was on the stock (but rooted) AT&T ICS ROM, so I know that's why I "bricked" my phone the first time.
I'll give TWRP a shot, hopefully that will work.
Click to expand...
Click to collapse
Ok so we know it's not the boot loader issue of ICS after dozens if not hundreds of successful installs using the unbricking guide the only thing left is the new version of cwm. Hopefully twrp will do the trick for you. Has anyone out there successfully completed the unbricking guide with the new version of cwm?
Sent from my LG-P930 using xda app-developers app
Swetnes said:
Ok so we know it's not the boot loader issue of ICS after dozens if not hundreds of successful installs using the unbricking guide the only thing left is the new version of cwm. Hopefully twrp will do the trick for you. Has anyone out there successfully completed the unbricking guide with the new version of cwm?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I haven't tried the TWRP recovery a shot yet, since I haven't been home, but I figured it was worth pointing out that the CWM 5.x.x.x (can't remember exact version numbers right now) didn't work for me either. Every time I flashed a ROM, I'd end up with a boot loop on first boot, and then when I'd try to go back into recovery, I'd find that it wouldn't go back in there either.
It was basically acting like when I flashed the ROM that it overwrote the recovery partition, except no one else seems to have this same issue. Yet, if I didn't flash a ROM, I was able to go in and out of CWM recovery as often as I wanted.
Bah.
SectorNine50 said:
I haven't tried the TWRP recovery a shot yet, since I haven't been home, but I figured it was worth pointing out that the CWM 5.x.x.x (can't remember exact version numbers right now) didn't work for me either. Every time I flashed a ROM, I'd end up with a boot loop on first boot, and then when I'd try to go back into recovery, I'd find that it wouldn't go back in there either.
It was basically acting like when I flashed the ROM that it overwrote the recovery partition, except no one else seems to have this same issue. Yet, if I didn't flash a ROM, I was able to go in and out of CWM recovery as often as I wanted.
Bah.
Click to expand...
Click to collapse
Can you clarify exactly what method you are using to flash the ROM? I just can't imagine a scenario where flashing a ROM would overwrite the recovery. What ROM are you flashing?
Also, please confirm what phone you have.
drumist said:
Can you clarify exactly what method you are using to flash the ROM? I just can't imagine a scenario where flashing a ROM would overwrite the recovery. What ROM are you flashing?
Also, please confirm what phone you have.
Click to expand...
Click to collapse
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
SectorNine50 said:
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
Click to expand...
Click to collapse
You are correct, the Nitro is P930. And I'm sure this doesn't need pointing out, but when you download the ROM, make sure it's for P93x and not SU640. Most of the ROMS in the developer section have versions for both models.
Also, when you say you can't access CWM after flashing a ROM, how are you trying to access it? Holding Power+Volume down until the Factory Reset screen pops up? It still shows that screen even with CWM installed, but when you press the power button to perform the factory reset it SHOULD take you into CWM Recovery instead.
SectorNine50 said:
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
Click to expand...
Click to collapse
To access recovery, turn the device completely off. (If you're in a bootloop, pull battery or hold power button for ~20 seconds until screen stays off.) Then when phone is off, press and hold volume down and power buttons at the same time, not releasing until you see text asking if you want to factory reset. Press power button twice to confirm and you'll get to recovery.
Is this the method you're using to try to get to CWM?
My guess as to why you are getting bootloops is that you aren't wiping data first.
Yup, that's how I'm accessing CWM. After the flash, after I press the power button twice, I get something similar to a boot loop. A recovery boot loop, if you will.
Well, I've tried a couple ways now. I've tried using the "factory reset/wipe user data" menu item in CWM, and I've tried going into each partition and wiping them individually before flashing as well.
Just got home, I'll try flashing using the TWRP and let you guys know.
SectorNine50 said:
Yup, that's how I'm accessing CWM. After the flash, after I press the power button twice, I get something similar to a boot loop. A recovery boot loop, if you will.
Well, I've tried a couple ways now. I've tried using the "factory reset/wipe user data" menu item in CWM, and I've tried going into each partition and wiping them individually before flashing as well.
Just got home, I'll try flashing using the TWRP and let you guys know.
Click to expand...
Click to collapse
Good luck. Other possible things to try:
1) Check zip MD5 hash (or just redownload and replace) to make sure it's not corrupted.
2) Reformat entire SD card.
Interesting update:
I decided to give getting back into CWM recovery one more shot before I went through the process of re-unbricking again, and this time it managed to get in (for whatever reason).
So, I did a factory wipe, cleared dalvik cache, flashed the ParanoidAndroid ROM, backed out, did another factory wipe, and tried to reboot into the newly flashed ROM.
No luck. Boot looped, and didn't even get to the ROM animation. Following that, I had trouble getting back into the CWM recovery. Managed to try about 5 times and finally got in, however CWM stated:
Code:
CWM-based Recovery v5.0.2.7
E:Error in /cache/recovery/last_log
(Read-only file system)
So... my phone may have potentially unrooted it's self, somehow... Interestingly, it still shows the file systems as mounted.
So, now I'm doing a full SD card reformat. Figured I'd get that variable out of the way before I go any further.
SectorNine50 said:
Interesting update:
I decided to give getting back into CWM recovery one more shot before I went through the process of re-unbricking again, and this time it managed to get in (for whatever reason).
So, I did a factory wipe, cleared dalvik cache, flashed the ParanoidAndroid ROM, backed out, did another factory wipe, and tried to reboot into the newly flashed ROM.
No luck. Boot looped, and didn't even get to the ROM animation. Following that, I had trouble getting back into the CWM recovery. Managed to try about 5 times and finally got in, however CWM stated:
Code:
CWM-based Recovery v5.0.2.7
E:Error in /cache/recovery/last_log
(Read-only file system)
So... my phone may have potentially unrooted it's self, somehow... Interestingly, it still shows the file systems as mounted.
So, now I'm doing a full SD card reformat. Figured I'd get that variable out of the way before I go any further.
Click to expand...
Click to collapse
You are installing the wrong version of CWM. Never use anything older than 5.8.2.0. This is the one you want: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.2.0-p930.img
Anything older than that is known to not work.
Second thing: You seem to have an incorrect understanding of what "root" means. Having "root" simply means you have administrator access to your current ROM. When you install a new ROM, whether you had root access to your old ROM is meaningless frankly.
drumist said:
You are installing the wrong version of CWM. Never use anything older than 5.8.2.0. This is the one you want: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.2.0-p930.img
Anything older than that is known to not work.
Second thing: You seem to have an incorrect understanding of what "root" means. Having "root" simply means you have administrator access to your current ROM. When you install a new ROM, whether you had root access to your old ROM is meaningless frankly.
Click to expand...
Click to collapse
Ah, thank you! I must've been viewing an old thread. Now that I look at the version number, it appears that's the version I had been hunting for since the newest one didn't work.
Interesting, I most certainly misunderstood, I was under the impression that "rooting" the device was a filesystem level permission change. Good to know!
It seems like we are getting closer to a solution here. Thanks for your patience!
Well, that appears to have been my problem the whole time! That's kind of embarrassing, considering how much time I sunk into this and how simple the solution was!
Anyway, thank you all very much! I assume that TWRP would have also solved my problems as well. It would seem that both the older and newest versions of CWM have some problems (at least for me!).
SectorNine50 said:
Well, that appears to have been my problem the whole time! That's kind of embarrassing, considering how much time I sunk into this and how simple the solution was!
Anyway, thank you all very much! I assume that TWRP would have also solved my problems as well. It would seem that both the older and newest versions of CWM have some problems (at least for me!).
Click to expand...
Click to collapse
Yeah, the new one (6.0.1.5) just came out. I'll have to test it to see if it works for me.
For what it's worth, I haven't had any issues with 6.0.1.5 yet. The touch version is a must, though.
Malnilion said:
For what it's worth, I haven't had any issues with 6.0.1.5 yet. The touch version is a must, though.
Click to expand...
Click to collapse
Have you had a chance to compare to twrp?
Sent from my LG-P930 using xda app-developers app
Swetnes said:
Have you had a chance to compare to twrp?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I really enjoy the integration Rom Manager/CM Updater has with CWM. If twrp is capable of running the install scripts those two use, I might consider trying it out, but I don't really like manually going through the steps to flash a rom every day.
Hello,
As many of you might already know of the app "Flash Image Gui"and that it alows the user to flash a kernel without having to unlock the bootlader. I had contacted the creator of the application to ask whether it would be possible for the Xperia Play!!!!!!!! He replied fairly short after saying
"To add support I need a tester with ADB and custom recovery knowledge to help me test, If you think you fit these criteria, let me know and we can work on testing!"
If anyone does fill the criteria could you please email [email protected] so that we can attempt to get Flash Image Gui for Xperia Play!!!!:laugh:
>.< Do you really need to multipost...
i dno if this can work, because the kernel partition is hidded, so not visible without fxp's kernel.
and then when it is visible, it is protected
It doesn't hurt to try. Maybe this guy has found a back door..... So to speak, if I knew more about it I'd definitely be down my xplay isn't doing anything but collecting dust
Sent from my SGH-I747M using xda premium
I have talked with the developer, and he has told me this method is for flashing kernels without fast boot, but am unlocked boot loader is required.
This does seem like an interesting concept, and hopefully it will make life easier for those that do nit have access to a computer 100% of the time.
Sent from R800x
Interesting
Well I will find out Saturday if this will work as I have a meeting with him will let u guys know if it does
Sent from my R800x using xda app-developers app
Is it possible to flash a kernel with CWM? Because I've never seen it done with the play yet while flashing CM10 on my Galxay S3 its the easiest thing I've ever done with android, I just flash CWM and flash cm10 and its done... So is it possible?
TheCraig said:
Is it possible to flash a kernel with CWM? Because I've never seen it done with the play yet while flashing CM10 on my Galxay S3 its the easiest thing I've ever done with android, I just flash CWM and flash cm10 and its done... So is it possible?
Click to expand...
Click to collapse
Flashing a kernel from CWM is not possible for the Play. The reason is because recovery is within the kernel.
Solar.Plexus said:
Flashing a kernel from CWM is not possible for the Play. The reason is because recovery is within the kernel.
Click to expand...
Click to collapse
Not on stock play. It's booted from SD.
DubleJayJ said:
Not on stock play. It's booted from SD.
Click to expand...
Click to collapse
Well, on stock ROM and kernel, recovery is usually installed to the /system partition.
Just curious, where's the information about recovery from SD?
That's all wrong
Recovery is loaded from ramdisk.
We can't flash a kernel from recovery because sony ericsson protected the /boot partition
nickholtus said:
That's all wrong
Recovery is loaded from ramdisk.
We can't flash a kernel from recovery because sony ericsson protected the /boot partition
Click to expand...
Click to collapse
Isn't /boot the location of the kernel?
Yes, but that's only accisble when the phone is in fastboot
Does this thread is suggesting to flash a kernel using a flashable .zip with "write raw image" method?? Honestly it "CAN'T" be done. Nick already explain it but still.. Meh... Just so to get the whole idea of this suggestion, i tried it on mine. It just abort it coz there's no boot partition to load & write the boot.img(kernel). It can only be done if the recovery were not part of the boot partition. So...this is a pointless arguement. Mybe this thread oughta be closed. Just saying
Regards,
Sdojoin
nickholtus said:
Yes, but that's only accisble when the phone is in fastboot
Click to expand...
Click to collapse
And just so I have my facts straight, doesn't XParts install CWM to /system on stock ROM? Since the Play has no recovery partition?
It can only be done if the recovery were not part of the boot partition
Not true, look at xperia 2012. Recovery included in kernel and you can flash from recovery
What about overclock with stock kernel then?
if this will happened, psxperia developer, will be enable to install ICS or JB or any other platform and make the psxperia available to ICS or JB or any other platform (he has r800at with lock bootloader so he can't test psxperia on other platform, and that's why he stooped the project. i asked him for port for ics, and he told me that he can't test it on xperia play with ics with full gamepad+touchpad support)
oc on stock kernel locked bootloader is higly possible.
i saw someone posted the modules on arc forum.
ask if he wants to make them for play stock 2.3.4 too
So I appear to be the only person as far as I can tell whom is left softbricked and forced to CWM recover after installing chronickernals .zip from Sd card and rebooting in recovery mode. Are there any apps, configurations, or anything of interest that a noob like me should consider as to why my phone wont start after flashing the Kernal? Perhaps I should nandroid, re-root and try again before installing apps? Im dealing with a T-mobile galaxy s4. Sgh-m919.
Grimzoso said:
So I appear to be the only person as far as I can tell whom is left softbricked and forced to CWM recover after installing chronickernals .zip from Sd card and rebooting in recovery mode. Are there any apps, configurations, or anything of interest that a noob like me should consider as to why my phone wont start after flashing the Kernal? Perhaps I should nandroid, re-root and try again before installing apps? Im dealing with a T-mobile galaxy s4. Sgh-m919.
Click to expand...
Click to collapse
i dont see that kernel in our development forums, so i assume its from the i9505 forum, in which case that is why your not booting. you can only flash roms from those forums, not kernels.
TheAtheistOtaku said:
i dont see the kernel in our development threads, so im assuming you found it in the international versions development. while we can flash roms and kernels from the i9505, they are not guaranteed to work with our device, and we flash at our own risk. So it seems like this may be the case.
If you found the kernel in the i9500 forums, well then theres your problem
Or, you just need to go into advanced setting in clockwork mod and hit fix permissions.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2279099
I found it here. I notice the AOSP/CM on the thread. So.. I Suppose its either because im not using a i9500 or because of this Aosp/CM stuff. Are those rom managers or something? Because I have ClockworkMod's rommanager.
Grimzoso said:
http://forum.xda-developers.com/showthread.php?t=2279099
I found it here. I notice the AOSP/CM on the thread. So.. I Suppose its either because im not using a i9500 or because of this Aosp/CM stuff. Are those rom managers or something? Because I have ClockworkMod's rommanager.
Click to expand...
Click to collapse
oh chronic kernel, didnt recognize it since you spelled it with a k. Try fixing permissions recovery and see if it boots then
also, i wouldnt recommend using rom manager and goo manager for flashing and stuff, ive had problems with them in the past, though thats just personal preference and experience
TheAtheistOtaku said:
oh chronic kernel, didnt recognize it since you spelled it with a k. Try fixing permissions recovery and see if it boots then
also, i wouldnt recommend using rom manager and goo manager for flashing and stuff, ive had problems with them in the past, though thats just personal preference and experience
Click to expand...
Click to collapse
What should I flash with?
Grimzoso said:
What should I flash with?
Click to expand...
Click to collapse
TWRP has never given me problems...cant say the same for others.
The Illest 619 said:
TWRP has never given me problems...cant say the same for others.
Click to expand...
Click to collapse
Thanks abunch. Since TWRP has an install option does that mean I can flash kernals without booting into recovery mode. Because ClockWorkMod still boots my recover, even without the app.
Grimzoso said:
Thanks abunch. Since TWRP has an install option does that mean I can flash kernals without booting into recovery mode. Because ClockWorkMod still boots my recover, even without the app.
Click to expand...
Click to collapse
Pretty sure you have to boot into recovery mode to flash anything.