Hi,
first of all: My Galaxy S is just a "play phone" for me. Some time ago I tried to install CMW touch (or however it is called) but somehow it didn't work. Due to lack of time I didn't took a deeper look into it.
Now - as I am having a little more time - I want to bring TWRP onto my old charm.
Currently I am running CWM recovery v6.0.3.3 and an AOKP build from July 22nd (Android 4.2.2).
Is there even a TWRP version for the Galaxy S I9000 running on 4.2.2?
Using Goo Manager or the TWRP Manager I just see that there is no TWRP for my device - which is not true as I've read that there is a version for I9000 in several threads/forums.
Best regards,
Manuel
flash mckay kernel or didhey's..
Sent from my GT-I9000 using Tapatalk
Related
Hi,
I have tried to install both AOSP Beta 8 and 9 for P7300. I get the error the same error message both times, status 7 which is guess is due to that I'm using the wrong CMW file (version 5.5....). Reading the forums it seems like cmw 6.0.1.0 works pretty well. Is there a repository where I can download these CMW files? I have search but not really found any good place. What combination of AOSP version and CMW is best? Do I need to change the kernal also?
Any help is welcome!
Kind regards,
Mikael Hagström
I recomand you to install the cwm 6.0.0.8, i think it's the best and this should fix your problem.
Sent from my GT-I9300 using Tapatalk 2
Don't think recovery version is to blame.
Do you have the 7300 or 7310 galaxy tab?
What was the last Rom / recovery that you flashed with Odin?
IIRC status 7 is an assert failure, so you could also turn off assert verification in the recovery, before flashing... Or remove offending assert from the update script in aosp ROM zip. (probably a line like test for p5 or p7300)
Or you can flash CWM 6.0.0.8 from the thread on cm9 (kallt_kaffe) , post #2. Although file is named 6008, it really is 6010... If you insist on that route
Sent from mobile app...
Thanks for your replies.
I have the P7300.
I'm back on the stock ROM now since I could not get the AOSP ROM to work.
I tried removing the assert lines. The tablet hang on the X (Nexus) screen when I rebooted.
I will try both again with the new Clockwork Recovery file.
Hi,
I tried again his morning. With CWM 6.0.0.8 from the thread on cm9 and the ROM from http://forum.xda-developers.com/showthread.php?t=1789464. It now installs but when I reboot is gets stuck at the black screen with the colourful Nexus X. I left it like that for 25 min but no change just the X. This is how I do it.
I start of with the stock ROM (Build number HTJ85B P7300XWKL4)
I root the device and install superuser and root check (that tells me it have been rooted)
I install CWM 6.0.0.8 from boot by running the ZIP file
I boot up into Clockwork Recovery and install the AOSP ZIP. The tablet restarts after install but gets stuck at the screen with the X.
Do I need to do a wipe?
I'm I missing some steps?
g3blv said:
Hi,
I tried again his morning. With CWM 6.0.0.8 from the thread on cm9 and the ROM from http://forum.xda-developers.com/showthread.php?t=1789464. It now installs but when I reboot is gets stuck at the black screen with the colourful Nexus X. I left it like that for 25 min but no change just the X. This is how I do it.
I start of with the stock ROM (Build number HTJ85B P7300XWKL4)
I root the device and install superuser and root check (that tells me it have been rooted)
I install CWM 6.0.0.8 from boot by running the ZIP file
I boot up into Clockwork Recovery and install the AOSP ZIP. The tablet restarts after install but gets stuck at the screen with the X.
Do I need to do a wipe?
I'm I missing some steps?
Click to expand...
Click to collapse
Try to fully wipe also format your /system in cwm recovery 6.0.0.8 and then try installing again and reboot it should work man!
Works now! Thanks!
Hi, i just wanted to update my ParanoidAndroid ROM (i had 2.14 ver.) so i made a full wipe, installed new nightly, full wipe, installed gapps and installed hydracore kernel. When i was rebooting my phone i noticed it's just showing Galaxy Note on the screen and after that phone rebooted very fast. Finally i booted it into recovery (download mode does not work). Now, what should i do? I don't have a backup of my old ParanoidAndroid ROM, but i have only backup with my RocketRom (an old one). What should i do? I am affraid if i will exit from recovery, my phone will never wake up. Please, help me guys. Sorry for my English.
If you have nandroid backup of your rom then use it.and please in future whenever flash any rom.first backup efs and then nandroid then titanium
Sent from my GT-N7000 using xda app-developers app
smea said:
Hi, i just wanted to update my ParanoidAndroid ROM (i had 2.14 ver.) so i made a full wipe, installed new nightly, full wipe, installed gapps and installed hydracore kernel. When i was rebooting my phone i noticed it's just showing Galaxy Note on the screen and after that phone rebooted very fast. Finally i booted it into recovery (download mode does not work). Now, what should i do? I don't have a backup of my old ParanoidAndroid ROM, but i have only backup with my RocketRom (an old one). What should i do? I am affraid if i will exit from recovery, my phone will never wake up. Please, help me guys. Sorry for my English.
Click to expand...
Click to collapse
You're not bricked, the new pa roms have updated Mali chip drivers and no other kernel supports it so you have to stick with the stock kernel provided. Just reflash rom and use the kernel provided.
Sent from my GT-N7000 using xda premium
yes correct. Go back to the original PA kernel. flash the rom again it will be fine
Please edit the title of this thread!! The last thing that we need on Note forum is a brick bug hoax on safe kernels!!
Sent from my GT-N7000 using Tapatalk 2
Hi there,
I have a Samsung Galaxy Tab 10.1 WiFi/3G (first edition). Right now there is stock ROM on it. I flashed CWM on it, booted in recovery mode and followed some guide I found.
At first I had an older version of CWM (5), after some playing around I installed CWM version 6. I wanted to flash the CM10 ROM, but version 5 of CWM gave me some error, So I flashed a newer version.Followed the guide again, installed ROM from ZIP file with CWM, no errors, flashing is done, reboot Tab, and now the only thing I see is the "Samsung Galaxy Tab 10.1" logo/boot screen.
When I restore the backup I created earlier, the tablet boots in the stock ROM again...
So I was wondering what is going wrong... I have read some thread but could not find anything similar to this...
Thanks!
Hi,
You are on the wrong forum, but I guess that you will need to re- stock your device using Odin or hemindall.
Regards
Sent from my GT-P1000
Heyy Everyone..
I am running DDLSC(4.1.2) on my Galaxy Note. When I checked the version of the CWM Recovery installed on my device (Philz Kernel), it shows 6.0.3.2 but when I checked on the CMW Website, it shows the latest version of CWM for N7000 as 6.0.4.3.
Now, can anyone tell me how to update my phone to this CWM Recovery Version? I don't mind using some other Kernel or anything, but I want it to be a Safe Kernel for my device..
Please help me!
aneesh.techhive said:
Heyy Everyone..
I am running DDLSC(4.1.2) on my Galaxy Note. When I checked the version of the CWM Recovery installed on my device (Philz Kernel), it shows 6.0.3.2 but when I checked on the CMW Website, it shows the latest version of CWM for N7000 as 6.0.4.3.
Now, can anyone tell me how to update my phone to this CWM Recovery Version? I don't mind using some other Kernel or anything, but I want it to be a Safe Kernel for my device..
Please help me!
Click to expand...
Click to collapse
There is absolutely no point in upgrading from your current version t a more recent one, it won't be any safer, it won't introduce better performance nor any new features. Second of all, you would have to change the kernel to change your recovery and there aren't any other kernels with a newer CWM recovery version.
Okkay! So, can you tell me a way to install CM 11 on my device??
Check the cm11 beta 7 by herna on the android development section.
Sent from my LG-E410
Hey guys. I finally got my P880 working again.
I had it on Stock 4.1.2 which I really don't like. I want to upgrade it to KitKat 4.4 (Cyanogen 11)
However whenever I try and flash the 'cm-11-20141224-NIGHTLY-p880.zip' with 'TWRP 2.8.3.0' I get:
E:Error: executing updater binary in zip
Click to expand...
Click to collapse
This is apparently due to something to do with how permissions or something were changed in 4.4 and that TWRP (for our P880) doesn't apparently work for flashing KitKat.
I don't understand this as other people have complained that CWM doesn't work for flashing KitKat 4.4 but the latest TWRP does work.
Any ideas?
Currently I have the P880 now without ANY firmware installed :/ and I will no longer have access to a computer after tomorrow for about a month
I had the P880 working with Stock 4.1.2 like I said, but it's pretty bland vs. KitKat 4.4 which my S5 is rocking.
So...
Is there an easy way to get Cyanogen 11 KitKat 4.4 working on my P880? I've been trying to get this done for days after flashing PhilZ Recovery that bricked my phone (even though it was for my Model (P880)).
I just got TWRP 2.8.3.0 installed on my phone and it seems to be the ONLY recovery that actually works. CWM 6.0.4.5 doesn't work on my phone. It installs fine, but whenever I try and press something, or select an option like (Install .zip) nothing works. Absolutely nothing works. Because I have no firmware installed now, I'm also at a bit of a loss as to risk installing a different Recovery in case it also has this problem. As both PhilZ and CWM have not remotely worked and I have been unable to perform any action what-so-ever with either of them. Only TWRP seems to work.
Please help me get Cyanogen 11 on my phone
EDIT:
I flashed SlimKat 4.4 instead of Cyanogen 11. I've never really liked Cyanogen anyway and I loved SlimBean on my S4.
Downloaded and flashed the 24th December UNOFFICIAL build and it worked perfectly.
However I got a little issue with /storage and /data not mounting properly so I had to flash again by wiping /data (using the 'yes' wipe, not standard factory wipe). I think I had this problem because the phone was mounted to my laptop when I did the .zip install from TWRP.