Hi guys,
Download links for ClockWorkMod Recovery both touch and non touch.
Now moved here
Bugs : You tell me.
Thanks,
Dark Passenger
Credits : People who made this possible.
Lloir(base tree).
Claudy(bug fixes).
Cobje(bug fixes and major porting).
neXus PRIME(major porting and finishing touches).
Dark Passenger(finishing touches and final bug fixes).
Gweedo767(clockworkmod maintainer and the person to make us official).
Note:This thread shall be moved to development forum once rom manager integration is complete
How to install.
prerequisites
unlocked bootloader.
fastboot
a usable brain.
>reboot to bootloader/fastboot mode
>open a fastboot terminal and type
>fastboot flash recovery <recovery_name>.img
>fastboot reboot-bootloader
>fastboot erase cache(precaution)
Thanks guys.
I have tested flash, wipes and it works (I tried flashing AromaFM and it worked, not an entire ROM) but if I select mount storage it doesn't work!
Also, I'm in ICS (1.14) ROM not JB
pfff.....why is that...?
this recovery : http://forum.xda-developers.com/showthread.php?t=2076245
has the same bug... i cant mount sd :S
gbueno6 said:
I have tested flash, wipes and it works (I tried flashing AromaFM and it worked, not an entire ROM) but if I select mount storage it doesn't work!
Also, I'm in ICS (1.14) ROM not JB
Click to expand...
Click to collapse
mhb92 said:
pfff.....why is that...?
this recovery : http://forum.xda-developers.com/showthread.php?t=2076245
has the same bug... i cant mount sd :S
Click to expand...
Click to collapse
same tree.
so except ums no other bugs ? graphics okay ...
also adb and adb sideloading.
Can some one give me a log for the ums behaviour.
Thanks.
Dark Passenger said:
Can some one give me a log for the ums behaviour.
Thanks.
Click to expand...
Click to collapse
I can't because I don't know how to :crying:
All I can do is confirm you that all wipes are working and that no graphic glitches were found!
I'm sorry
gbueno6 said:
I can't because I don't know how to :crying:
All I can do is confirm you that all wipes are working and that no graphic glitches were found!
I'm sorry
Click to expand...
Click to collapse
Advanced-Copy Log to SD.
xpirt
gbueno6 said:
I can't because I don't know how to :crying:
All I can do is confirm you that all wipes are working and that no graphic glitches were found!
I'm sorry
Click to expand...
Click to collapse
alternative to what @xpirt told
Code:
adb pull /cache/recovery/last_log
EDIT do this after you try UMS(if on windows wait for sometime for the drivers to install like atleast 10 min) and boot into the rom.
xpirt said:
Advanced-Copy Log to SD.
xpirt
Click to expand...
Click to collapse
I can't "copy log to sd" it just says "show log".
Dark Passenger said:
alternative to what @xpirt told
Code:
adb pull /cache/recovery/last_log
EDIT do this after you try UMS(if on windows wait for sometime for the drivers to install like atleast 10 min) and boot into the rom.
Click to expand...
Click to collapse
Ok, I have copied the last_log file (i tried usb mass storage and waited for some minutes before copying the file). I'm unrooted so I picked up the file with AromaFM.
I hope it helps!
PD: There's also something weird that happened to me with the other CWM recovery: when I switched off the phone to charge it, the orange light blinks for 15 seconds and the phone starts again! It doesn't happen with TWRP recovery (the "starting process", not the blinking). EDIT: The restart issue does NOT happen with this recovery. Yeyyyy!!
@OP, why panicking? ums will work just fine
you need to add proper lines in BoardCOnfig.mk and ramdisk. You should have waited for me to fix it as i gave you my tree. Anyways Try uncommenting the line for UMS_LUNFILE which is commented, and delete the next two lines after it. Compile it with that and tell me.
neXus PRIME said:
@OP, why panicking? ums will work just fine
Click to expand...
Click to collapse
I'm a generally panicky sort of person...
neXus PRIME said:
you need to add proper lines in BoardCOnfig.mk and ramdisk. You should have waited for me to fix it as i gave you my tree. Anyways Try uncommenting the line for UMS_LUNFILE which is commented, and delete the next two lines after it. Compile it with that and tell me.
Click to expand...
Click to collapse
Yes its your tree and actually the fix became apparent with the log.
Thank you for everything you have done for this devices recovery and I have no plans of changing that.The recovery is now fully functional and bugfree as soon as Gweedo767 is free he will be doing an official build(dont hold your breadth may take a while).
Post that official builds shall be available on clockworkmod.com and this thread will cease to exist(at least it will be locked).
And @neXus PRIME will you be updating your thread with this info since you will be the main maintainer.
Thank you ,
Dark Passenger.
Thanks for all your work making CWM official.:good::good:
btw, i said the "panic" thing in a light-hearted way.
The recovery tree is originally LLOIR's, later on modified by cobje(therbom), Clauddy, and then final fixed tree by neXusPRIME (me). Please give credits to all of them.
Secondly, i like TWRP far more than CWM, so i invite you to be the official CWM maintainer if you are willing. We can work on recoveries together.
I currently have JB and ICS TWRP 2.5.0.0 ready to be released but only do it when i receive JB OTA.
Lastly, NOTE that the tree you are using for OFFICIAL CWM is only ICS COMPATIBLE. You will need to modify the recovery.fstab for JB compatible recovery by changing the mount points for SYSTEM,DATA,CACHE as they are in JB ROM proc/emmc. Then you will rebuild and CWM will be able to flash ROMs for people with hboot 1.25.0.0
Regards
Yasir
neXus PRIME said:
Thanks for all your work making CWM official.:good::good:
btw, i said the "panic" thing in a light-hearted way.
The recovery tree is originally LLOIR's, later on modified by cobje(therbom), Clauddy, and then final fixed tree by neXusPRIME (me). Please give credits to all of them.
Secondly, i like TWRP far more than CWM, so i invite you to be the official CWM maintainer if you are willing. We can work on recoveries together.
I currently have JB and ICS TWRP 2.5.0.0 ready to be released but only do it when i receive JB OTA.
Lastly, NOTE that the tree you are using for OFFICIAL CWM is only ICS COMPATIBLE. You will need to modify the recovery.fstab for JB compatible recovery by changing the mount points for SYSTEM,DATA,CACHE as they are in JB ROM proc/emmc. Then you will rebuild and CWM will be able to flash ROMs for people with hboot 1.25.0.0
Regards
Yasir
Click to expand...
Click to collapse
1. Its my pleasure.
btw so was mine
2.all credits will be present once official builds are online and I open a thread for it.(maybe you could make your thread jb version so there are both versions present for those who want it).
3.wat a coincidence I like cwm better than TWRP. no offence seem to work.Also the recovery tree as always is open for anyone with a github account to modify.
4.Same here the tree submited is for ics and will be updated only when i get the jb update(knew about the mount points from the various thread actually from your post I think).
PS do you know whats needed and/or where I can get the sources for touch recovery.
PPS in your recovery.fstab(cwm version) the internal sdcard(emmc) is mounted as vfat where as in cm its emmc.
gbueno6 said:
Ok, I have copied the last_log file (i tried usb mass storage and waited for some minutes before copying the file). I'm unrooted so I picked up the file with AromaFM.
I hope it helps!
PD: There's also something weird that happened to me with the other CWM recovery: when I switched off the phone to charge it, the orange light blinks for 15 seconds and the phone starts again! It doesn't happen with TWRP recovery (the "starting process", not the blinking). EDIT: The restart issue does NOT happen with this recovery. Yeyyyy!!
Click to expand...
Click to collapse
so there are no problems other than UMS.
can you please confirm.
thanks.
Dark Passenger said:
so there are no problems other than UMS.
can you please confirm.
thanks.
Click to expand...
Click to collapse
Yes, other than UMS, no more issues!
PD: I won't be able to test it again because I upgraded to JB!! ^^
Thank you very much for your work!
gbueno6 said:
Yes, other than UMS, no more issues!
PD: I won't be able to test it again because I upgraded to JB!! ^^
Thank you very much for your work!
Click to expand...
Click to collapse
cool :jealous: i might have to wait a tad bit longer for that
also if possible can you hold out on the update for a few more days might be the first to try out official builds.
Dark Passenger said:
cool :jealous: i might have to wait a tad bit longer for that
also if possible can you hold out on the update for a few more days might be the first to try out official builds.
Click to expand...
Click to collapse
I'm afraid I can't! I was very excited watching that my operator updated to JB (they never updated our ROM before) that I made it and now I'm in JB.
I'm sorry!
Also, if you want me to test it in JB, let me know it and I'll be very happy to help!
Have a great day
gbueno6 said:
I'm afraid I can't! I was very excited watching that my operator updated to JB (they never updated our ROM before) that I made it and now I'm in JB.
I'm sorry!
Also, if you want me to test it in JB, let me know it and I'll be very happy to help!
Have a great day
Click to expand...
Click to collapse
aye aye aye I just got an official build hot off jenkins.
Any one willing to test and let me know if ums is good and alls well.
latest built
@gbueno6 cab you test ums (yes in JB) it should work fine don't try anything else wont work.
Related
Okay so I received an Asus Transformer Prime tf201 yesterday. This morning I was able to unlock it, root it, and then I wanted to install the latest nightly of CM10 (24th). After I saw that it was indeed rooted I booted into twrp and in Wipe I did Factory Reset, System, Internal Storage (wanted to get rid of the pictures, etc. from previous owner). I had CM10 latest nightly and gapps both on my External SD Card so I knew I wasn't removing those.
Anyway after clicking on Install and then Using external SD I selected the zip of CM10 and swiped to confirm flash. It does well for about 2 or 3 minutes (the blue bar even shows progress) and then it comes up with the message E:Unable to mount '/staging'.
Please please tell me I did not mess up my Prime when I just got it???!!! Anyone that can help please help as soon as possible as I am really wanting to play with this after all the fantastic reviews I have heard. You would have my eternal gratitude and if it is not wrong to do this I will even donate via PayPal to the person that can help me "fix" my Prime.
Please KNOW I have been looking for answers to this for HOURS today and still haven't found anything to help me. I am really hoping some genius on XDA can help me.
alias4ever said:
Okay so I received an Asus Transformer Prime tf201 yesterday. This morning I was able to unlock it, root it, and then I wanted to install the latest nightly of CM10 (24th). After I saw that it was indeed rooted I booted into twrp and in Wipe I did Factory Reset, System, Internal Storage (wanted to get rid of the pictures, etc. from previous owner). I had CM10 latest nightly and gapps both on my External SD Card so I knew I wasn't removing those.
Anyway after clicking on Install and then Using external SD I selected the zip of CM10 and swiped to confirm flash. It does well for about 2 or 3 minutes (the blue bar even shows progress) and then it comes up with the message E:Unable to mount '/staging'.
Please please tell me I did not mess up my Prime when I just got it???!!! Anyone that can help please help as soon as possible as I am really wanting to play with this after all the fantastic reviews I have heard. You would have my eternal gratitude and if it is not wrong to do this I will even donate via PayPal to the person that can help me "fix" my Prime.
Please KNOW I have been looking for answers to this for HOURS today and still haven't found anything to help me. I am really hoping some genius on XDA can help me.
Click to expand...
Click to collapse
Did you check in twrp under the mounts button? I don't have my prime with me atm but I know there is a mounts section either on the first screen or under advanced may be....
Gage_Hero said:
Did you check in twrp under the mounts button? I don't have my prime with me atm but I know there is a mounts section either on the first screen or under advanced may be....
Click to expand...
Click to collapse
Yeahup I tried mounting everything and then unmounting everything to try and get it to work. What should be mounted/unmounted and selected on either SD Card or Internal? THANKS!
alias4ever said:
Yeahup I tried mounting everything and then unmounting everything to try and get it to work. What should be mounted/unmounted and selected on either SD Card or Internal? THANKS!
Click to expand...
Click to collapse
Mine, the radio button for external is on, you could try the terminal under advanced button...command would be something like su then enter and then mount /staging or something like that.... you may want to check the command exactly, my terminal skills are limited...
alias4ever said:
Yeahup I tried mounting everything and then unmounting everything to try and get it to work. What should be mounted/unmounted and selected on either SD Card or Internal? THANKS!
Click to expand...
Click to collapse
Probably running TRWP 2.3.x.x, right? Some others had this same problem with the TF300 and switched back to TWRP 2.2.2.1 and their ROM flashed just fine. Might be worth a shot.
tedr108 said:
Probably running TRWP 2.3.x.x, right? Some others had this same problem with the TF300 and switched back to TWRP 2.2.2.1 and their ROM flashed just fine. Might be worth a shot.
Click to expand...
Click to collapse
Isn't 2.3 for the JB bootloader and 2.2 for ics though?
Gage_Hero said:
Isn't 2.3 for the JB bootloader and 2.2 for ics though?
Click to expand...
Click to collapse
No, there is a 2.3 for both ics and jb bootloaders ... I THINK that 2.2 was ics only (can't remember for sure). If he was loading the CM10 nightly, he should have had an ics bootloader, or it would not have run.
---------- Post added at 04:16 PM ---------- Previous post was at 04:12 PM ----------
Gage_Hero said:
Isn't 2.3 for the JB bootloader and 2.2 for ics though?
Click to expand...
Click to collapse
You do bring up a good point, though ... if his TFP had a JB OTA, he could have the jb bootloader! Alias, you need to check these types of things out before moving forward.
tedr108 said:
No, there is a 2.3 for both ics and jb bootloaders ... I THINK that 2.2 was ics only (can't remember for sure). If he was loading the CM10 nightly, he should have had an ics bootloader, or it would not have run.
---------- Post added at 04:16 PM ---------- Previous post was at 04:12 PM ----------
You do bring up a good point, though ... if his TFP had a JB OTA, he could have the jb bootloader! Alias, you need to check these types of things out before moving forward.
Click to expand...
Click to collapse
I had the JB OTA before starting I do know that. Would have kept it if I didn't love CM so much! So would I just install twrp 2.2 through fastboot then like I did the 2.3.1.0 that I have now? Or is there another way I can do this? Thank you BOTH for your help! It is much appreciated! :good:
alias4ever said:
I had the JB OTA before starting I do know that. Would have kept it if I didn't love CM so much! So would I just install twrp 2.2 through fastboot then like I did the 2.3.1.0 that I have now? Or is there another way I can do this? Thank you BOTH for your help! It is much appreciated! :good:
Click to expand...
Click to collapse
If you had the JB bootloader before, then you surely still have it. You would not change your bootloader by flashing a CM10 nightly ROM. The only way that I know of for you to go back to an ICS bootloader is with nvflash. If nvflash was not on your TFP when you got it, you won't be getting it anytime soon, because it cannot be installed with a JB bootloader on your TFP.
Which TWRP 2.3.1 did you load? The JB version?
The CM10 nightlies are not currently compatible with a JB bootloader, so you had no hope of running it. That may very well have caused your staging error, but I am not sure. Since you apparently have a JB bootloader, you would have to flash an appropriate ROM, like Craig Gomez' (here). But, only the JB version of TWRP 2.3.1 will work for you, as far as I know. So, I'm thinking you must have loaded the correct one.
I cannot be 100% sure that you have the JB bootloader. I hope you are sure that your TFP was updated to JB by an Asus update (OTA).
If I were you, I'd make a plan of action and post it here. Be patient and wait for a response, before moving forward. Good luck with this.
alias4ever said:
I had the JB OTA before starting I do know that. Would have kept it if I didn't love CM so much! So would I just install twrp 2.2 through fastboot then like I did the 2.3.1.0 that I have now? Or is there another way I can do this? Thank you BOTH for your help! It is much appreciated! :good:
Click to expand...
Click to collapse
the only way back to an ics bootloader it through nvflash... if you didn't do nvflash before you started with JB then you are stuck using jb roms only I think.....you could try hairy bean .....
tedr108 said:
If you had the JB bootloader before, then you surely still have it. You would not change your bootloader by flashing a CM10 nightly ROM. The only way that I know of for you to go back to an ICS bootloader is with nvflash. If nvflash was not on your TFP when you got it, you won't be getting it anytime soon, because it cannot be installed with a JB bootloader on your TFP.
Which TWRP 2.3.1 did you load? The JB version?
The CM10 nightlies are not currently compatible with a JB bootloader, so you had no hope of running it. That may very well have caused your staging error, but I am not sure. Since you apparently have a JB bootloader, you would have to flash an appropriate ROM, like Craig Gomez' (here). But, only the JB version of TWRP 2.3.1 will work for you, as far as I know. So, I'm thinking you must have loaded the correct one.
I cannot be 100% sure that you have the JB bootloader. I hope you are sure that your TFP was updated to JB by an Asus update (OTA).
If I were you, I'd make a plan of action and post it here. Be patient and wait for a response, before moving forward. Good luck with this.
Click to expand...
Click to collapse
Okay let's see if I can get this is all right. I have The JB version of TWRP 2.3.1. As for running a different ROM I tried the Unofficial one you listed and it still gives me the Unable to mount 'staging/' error. It first says it is verifying the signature then update package, then it says Updating partition details and that is when it comes to the staging error. :crying:
I am 110% positive that my TFP was updated to JB by the Asus update (OTA). Thanks again for the suggestions hopefully someone out there will suggest something.
What about doing the PRIME FULL WIPE that someone suggests here: http://forum.xda-developers.com/showthread.php?t=1670824 Then trying to install the Unofficial CM10 with the JB Bootloader? Anyone know if this would work?
alias4ever said:
Okay let's see if I can get this is all right. I have The JB version of TWRP 2.3.1. As for running a different ROM I tried the Unofficial one you listed and it still gives me the Unable to mount 'staging/' error. It first says it is verifying the signature then update package, then it says Updating partition details and that is when it comes to the staging error. :crying:
I am 110% positive that my TFP was updated to JB by the Asus update (OTA). Thanks again for the suggestions hopefully someone out there will suggest something.
What about doing the PRIME FULL WIPE that someone suggests here: http://forum.xda-developers.com/showthread.php?t=1670824 Anyone know if this would work?
Click to expand...
Click to collapse
I wouldn't try the full wipe... what I would try is the fix permissions button under advanced.... failing that... I would try fastboot install of twrp 2.3 again (instructions on the twrp OP).... it is like you don't have rights to write to the staging partition...
Read this thread... this guy was in the same boat... page 2 post 19 is where he fixed it....
http://forum.xda-developers.com/showthread.php?t=1942927&highlight=unable+to+mount+staging&page=2
@Alias -- I was really hoping the JB bootloader ROMs would do it for you.
This right here is excellent advice from Gage_Hero:
Gage_Hero said:
I wouldn't try the full wipe... what I would try is the fix permissions button under advanced.... failing that... I would try fastboot install of twrp 2.3 again (instructions on the twrp OP).... it is like you don't have rights to write to the staging partition...
Click to expand...
Click to collapse
If this does not work, I am at a loss of how to recreate the Staging partition (and perhaps others), but there is probably a way.
Gage_Hero said:
I wouldn't try the full wipe... what I would try is the fix permissions button under advanced.... failing that... I would try fastboot install of twrp 2.3 again (instructions on the twrp OP).... it is like you don't have rights to write to the staging partition...
Read this thread... this guy was in the same boat... page 2 post 19 is where he fixed it....
http://forum.xda-developers.com/showthread.php?t=1942927&highlight=unable+to+mount+staging&page=2
Click to expand...
Click to collapse
You are an ABSOLUTE GENIUS! I remember reading that post of the guy in the same boat and honestly did not think it would work for me because I kept trying to install the different ROM's but it WORKED! Thank you, thank you, THANK YOU to you and everyone else for their suggestions! @Gage, can I send you a little thank you on PayPal??? Thank you so MUCH AGAIN! I can't thank you enough...
Now do I dare flash the CM10 Unofficial with the JB Boatloader through GooManager??? :silly:
alias4ever said:
You are an ABSOLUTE GENIUS! I remember reading that post of the guy in the same boat and honestly did not think it would work for me because I kept trying to install the different ROM's but it WORKED! Thank you, thank you, THANK YOU to you and everyone else for their suggestions! @Gage, can I send you a little thank you on PayPal??? Thank you so MUCH AGAIN! I can't thank you enough...
Now do I dare flash the CM10 Unofficial with the JB Boatloader through GooManager??? :silly:
Click to expand...
Click to collapse
Glad to get you up and running again just do yourself a favor before you try cm10.... make a backup... or 2 I never used cm on my tab but did it on my phone.... when I restored... I had to do it twice... not sure if that is the case with the prime or not ... but if it is a JB bootloader then you should be okay... I like flashing through twrp though .. never did a rom through goo... but I am sure it works...
I need a little more help now. I went to boot into TWRP last night and I just got the dead Andy. Does that mean that putting this stock JB back on my TFP I have lost my TWRP recovery?
My TFP is rooted though as I have SU in my app drawer and I installed Titanium Backup just fine. I just wanted to make a couple of backups of my TFP (one to save on my PC and one to save on my TFP's External SD. So my question is can I reinstall my TWRP through Fastboot like I did before even with it rooted? First time I did it I followed these instructions:
http://www.youtube.com/watch?v=-pW05Jf87dg&feature=plcp
But upon further reading it states that people have had problems installing JB ROMs with using the 2.3 or 2.3.1 version so should I install the 2.2 version? Please someone help me yet again possibly??? THANKS!
alias4ever said:
I need a little more help now. I went to boot into TWRP last night and I just got the dead Andy. Does that mean that putting this stock JB back on my TFP I have lost my TWRP recovery?
My TFP is rooted though as I have SU in my app drawer and I installed Titanium Backup just fine. I just wanted to make a couple of backups of my TFP (one to save on my PC and one to save on my TFP's External SD. So my question is can I reinstall my TWRP through Fastboot like I did before even with it rooted? First time I did it I followed these instructions:
http://www.youtube.com/watch?v=-pW05Jf87dg&feature=plcp
But upon further reading it states that people have had problems installing JB ROMs with using the 2.3 or 2.3.1 version so should I install the 2.2 version? Please someone help me yet again possibly??? THANKS!
Click to expand...
Click to collapse
I think people have had issues installing 2.2 on the JB bootloader I would fastboot install 2.3.1 there is no reason it shouldn't work..... I think there is some disconnect between twrp and some of the jb roms as some devs are including twrp in their install like Mr.Wookie over at team wookie.....
Gage_Hero said:
I think people have had issues installing 2.2 on the JB bootloader I would fastboot install 2.3.1 there is no reason it shouldn't work..... I think there is some disconnect between twrp and some of the jb roms as some devs are including twrp in their install like Mr.Wookie over at team wookie.....
Click to expand...
Click to collapse
Okay so I went ahead and have redone TWRP 2.3.1 via Fastboot. I then did a backup of my ROM twice onto my External SD card. After that I did a a Factory Reset through TWRP of course and then installed the Unofficial CM10 with JB Bootloader. I still got the E:can not mount '/staging' but I went ahead and installed the Gapps that was listed on the thread as well and then wiped davlik cache and regular cache. Rebooted and I am VERY HAPPY to say it FINALLY worked this time!
I was ecstatic to see that CyanogenMod symbol come up. I made sure to wait 10 minutes to let the ROM settle before doing anything and it looks very nice!
I am confused as to why it worked the second time or even worked with the staging error as well when it didn't last time. Maybe because I didn't do the wipe Internal in TWRP? Who knows all I know is my Asus is working wonderfully and I am SO HAPPY to have it back! Thank you again everyone for all your help, I LOVE THIS FORUM! :laugh: :good:
alias4ever said:
Okay so I went ahead and have redone TWRP 2.3.1 via Fastboot. I then did a backup of my ROM twice onto my External SD card. After that I did a a Factory Reset through TWRP of course and then installed the Unofficial CM10 with JB Bootloader. I still got the E:can not mount '/staging' but I went ahead and installed the Gapps that was listed on the thread as well and then wiped davlik cache and regular cache. Rebooted and I am VERY HAPPY to say it FINALLY worked this time!
I was ecstatic to see that CyanogenMod symbol come up. I made sure to wait 10 minutes to let the ROM settle before doing anything and it looks very nice!
I am confused as to why it worked the second time or even worked with the staging error as well when it didn't last time. Maybe because I didn't do the wipe Internal in TWRP? Who knows all I know is my Asus is working wonderfully and I am SO HAPPY to have it back! Thank you again everyone for all your help, I LOVE THIS FORUM! :laugh: :good:
Click to expand...
Click to collapse
Good to hear.... not sure if your aware or not but with a decent backup ( I do one everytime I think I am going to try something foolish) even if you do a wipe, as long as you can reach twrp you can restore the prime to it's state before you started messing with it....
neXusRecoveryCWM based recovery with touch controls
NOTICE: UMS MOUNTING IS A DRIVER ISSUE, FORCE YOUR WAY THROUGH IT !!!
See this for Help:
http://forum.xda-developers.com/showpost.php?p=36703043&postcount=58
http://forum.xda-developers.com/showpost.php?p=36705993&postcount=62
Features:
All CWM options + more
Navigation via swipe up down gestures.
Select and Back via Swipe Right and Left.
Battery Level and Time Display
All options working. UMS, graphic, no reboot
HOW TO FLASH:
Download "recovery.img"
Use "fastboot flash recovery recovery.img" in Fastboot mode
Reboot to recovery
DOWNLOADS
v1.1 Beta
SPECIAL EDITION V1.1: Link: http://d-h.st/8FS
NORMAL RELEASE:
DL Link:
http://d-h.st/AFe
v1.0 Initial Build
DL Link:
http://d-h.st/4R7
BUGS:
NONE YET
Code:
Special credits:
- Koush
- Lloir
- Claudyy
- TeamUtterChaos
- frostincredible
- Talatus
- cobje
OLD VERSION(Discontinued):
http://d-h.st/NBc
Nice one, added to Index.
Please put date of release in headline, and do it in future with next releases so we can track it.
Cheers mate, and thanks in for your work.
nlooooo said:
Nice one, added to Index.
Please put date of release in headline, and do it in future with next releases so we can track it.
Cheers mate, and thanks in for your work.
Click to expand...
Click to collapse
you're welcome. But it seems everyone is busy in new year celeb so no one testing
Thanks for that. I have the version that came with hasoon toolkit but it jumps left and right as you go down and up! Is this on the same?
Yasir Javed Ansari said:
you're welcome. But it seems everyone is busy in new year celeb so no one testing
Click to expand...
Click to collapse
I'm using your recovery and I like touch recovery. Backup and restore works flawlessly
Don't you want to continue your TWRP ?
ckpv5 said:
I'm using your recovery and I like touch recovery. Backup and restore works flawlessly
Don't you want to continue your TWRP ?
Click to expand...
Click to collapse
I always want an alternative to CWM coz it has bare basic features. TWRP was an option which had open source code so i tried it. But cant seem to be able to boot it. Something important is missing. But i may abandon it coz madmaxx said he might support desire X with 4EXT. and once 4ext comes, all the others will be rendered useless(kidding of course)
Regards
Yasir
So mount USB storage still doesn't work?
give me 1 more day
@Yasir Javed Ansari
Very happy with the progress of this Recovery, expecting more from you
Very happy with the progress of this Recovery......nice work
awesome ! i suppose the usb mount issue is the "e: unknown volume for path /sd-ext thing ?
Any progress my friend?
Syncing the jellybean tree is taking HELL more time than i imagined. But cobje is working on the device tree.
You can expect these in next release:
- graphic fixed
- sdcard mount (un-mounting has bugs if u guys have noticed or not)
- random reboot (still testing)
Regards
Noob question: what is the easiest way to flash a recovery without dozens of adb commands?
Only way now is
"fastboot erase cache"
"fastboot flash boot boot.img"
Sent from my awesome fridge
MaartenXDA said:
Only way now is
Sent from my awesome fridge
Click to expand...
Click to collapse
You mean
fastboot flash recovery recovery.img-path
fastboot reboot-recovery
fastboot erase cache
nlooooo said:
You mean
fastboot flash recovery recovery.img-path
fastboot reboot-recovery
fastboot erase cache
Click to expand...
Click to collapse
Ops yeah, thought he said kernel :3
Sent from my awesome fridge
swissly said:
Noob question: what is the easiest way to flash a recovery without dozens of adb commands?
Click to expand...
Click to collapse
MaartenXDA said:
Ops yeah, thought he said kernel :3
Sent from my awesome fridge
Click to expand...
Click to collapse
Are you sure?
Read my lips...
Graphic has been fixed , but as the recovery is closed source, I can't feed custom board config to fix UMS. That's why I'm also working on twrp.
Sent from my HTC Desire X
Hi Yasir, thank you so much for the fixes.
Graphics are working %100.
Backing up is working, will test restore soon.
What else would you like me to test?
Clockworkmod Recovery for the SM-G900H Exynos S5
Note: No one but yourself is responsible for what you do to your device.
People to Thank
Clockworkmod/Koush - for thier awesome recovery
Phil3759 - for hooking me up with his repo
Known Issues
Let me know.
How to install with Odin
(USB) Disconnect your phone from your computer
Start Odin3-vX.X.exe
Click the PDA button, and select CF-Auto-Root-....tar.md5
Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
(USB) Connect the phone to your computer
Make sure Repartition is NOT checked
Click the Start button
Wait for Android to boot
Done (if it took you more than 30 seconds, you goofed)
The Goods
k3gxx.tar - Please post feedback in this thread if you download(ed) and install this.
XDA:DevDB Information
Clockworkmod Recovery SM-G900H Exynos, a Tool/Utility for the Samsung Galaxy S 5
Contributors
PlayfulGod, Phil3759
Version Information
Status: Testing
Created 2014-04-19
Last Updated 2014-04-20
Tried the flags we discussed
You end up with a zImage-dtb, but it has no DTB embedded data
You can verify by comparing it to the zImage: they are same
Also, no DTB files were created during compiling
The end is a zImage without the DTB info
Phil3759 said:
Tried the flags we discussed
You end up with a zImage-dtb, but it has no DTB embedded data
You can verify by comparing it to the zImage: they are same
Also, no DTB files were created during compiling
The end is a zImage without the DTB info
Click to expand...
Click to collapse
Yea I noticed that b4 I broke mine from compiling. lol Not overly concerned with it atm. I'm sure the kernel gurus will work their magic.
Haven't installed it yet.
But I am dying hard to get a kernel for exynos with Boeffla or Faux audio driver.
Thank you for the CWM recovery!
Getting my Galaxy S5 tomorrow! And only have this one SM-G900H variant in my country. I will be replacing the recovery with this as soon as I get it!
ODIN v3.09, in case anyone needs it: http://www.devfiles.co/download/CAHmXM6c/Odin_v3.09.zip
thank you very much.it works perfect
Hello
Tks for this CWM ! What's the version of the CWM ? And anyone have tried this -->> http://forum.xda-developers.com/showthread.php?t=2726186
Whats the difference ?
Tks
scumpicule said:
Hello
Tks for this CWM ! What's the version of the CWM ? And anyone have tried this -->> http://forum.xda-developers.com/showthread.php?t=2726186
Whats the difference ?
Tks
Click to expand...
Click to collapse
prolly no difference, would have to compare device trees. lol
Mine is version 6.0.4.8 as yours should be if you synced cm src b4 building.
Nice OP btw.
PlayfulGod said:
prolly no difference, would have to compare device trees. lol
Mine is version 6.0.4.8 as yours should be if you synced cm src b4 building.
Nice OP btw.
Click to expand...
Click to collapse
Thanks
But It's the @Chenglu work. I've just write the thread. I would like to be a developper, but it requires time & knowledge... But now, I don't have.
Maybe later . There is no age to learn
scumpicule said:
Thanks
But It's the @Chenglu work. I've just write the thread. I would like to be a developper, but it requires time & knowledge... But now, I don't have.
Maybe later . There is no age to learn
Click to expand...
Click to collapse
nope sure isnt, I didnt get into computers until I was in my early 30's and only been messing with android for almost 4 years now.
Has nay1 install it yet? is it working for 900H?
I`m guessing the recovery doesn't work for the SM-G900M model as I've tried the process a couple of times and can't seem to be able to boot into recovery mode, only download?
blustosa said:
I`m guessing the recovery doesn't work for the SM-G900M model as I've tried the process a couple of times and can't seem to be able to boot into recovery mode, only download?
Click to expand...
Click to collapse
this one would not work on the G900M no
try here
http://forum.xda-developers.com/showthread.php?t=2697523
PlayfulGod said:
this one would not work on the G900M no
try here
http://forum.xda-developers.com/showthread.php?t=2697523
Click to expand...
Click to collapse
Couldn't get that one to work either
blustosa said:
Couldn't get that one to work either
Click to expand...
Click to collapse
I know at least 1 or 2 reported it working on the K900M.
(not this one ppl)
PlayfulGod said:
I know at least 1 or 2 reported it working on the K900M.
(not this one ppl)
Click to expand...
Click to collapse
Might be different for the SM-G900M perhaps? Shame...
blustosa said:
Might be different for the SM-G900M perhaps? Shame...
Click to expand...
Click to collapse
I meant G900M.
PlayfulGod said:
I meant G900M.
Click to expand...
Click to collapse
Could it perhaps have anything to do with the fact it was already rooted? If so, anyway to go back and redo the process?
blustosa said:
Could it perhaps have anything to do with the fact it was already rooted? If so, anyway to go back and redo the process?
Click to expand...
Click to collapse
shouldnt matter.
PlayfulGod said:
shouldnt matter.
Click to expand...
Click to collapse
Gave another go without the auto boot. Ran the whole thing, then it was left at the blue reset on Odin. So I pulled the cable, pulled the battery, and did the recovery reset with the volup, menu and power thing.
Goes then to the message "recovery is not seandroid enforcing " and then just reboots the phone regularly without ever going through recovery.
Something wrong in the process or the way I did it?
Download
Mega
Installing
You can't flash this yet (I'm working on that, I promise) but you can boot from it!
NOTE: THIS IS A WIP. Not a lot has been really tested yet and this is posted merely for your enjoyment atm.
I don't suggest flashing anything yet, not that there is anything to flash heh.
Also, I take no responsibility if you break your watch, yada, yada.
To do this, make sure you have Android's tools (for fastboot), an unlocked bootloader, and the watch connected to your computer in Debug mode.
> adb reboot bootloader
<wait for the reboot to happen>
> fastboot boot /path/to/recovery.img
Click to expand...
Click to collapse
Enjoy!
Did u push the tree to github?
1st built for me was a no go
wouldn't twrp make more sense since its touch based?
D-FUSE said:
Did u push the tree to github?
1st built for me was a no go
Click to expand...
Click to collapse
Nope, though I'll try to get to it tomorrow after work! If you want, I can give you an overview of what I did:
1. Pull the source for CM11.
2. Dump boot and recovery images using dd.
3. Ran makevender.sh using lge and dory.
4. lunch'd it up.
5. Replaced the recovery.fstab with the fstab from the recovery ramdisk.
6. Ran makerecovery.sh.
7. fastboot boot'd the recovery.img
This is all off the top of my head and missing some random files you had to hack around with, of course. Hope you get it working and more progress is made because I can't get to it for another day!
ptesmoke said:
wouldn't twrp make more sense since its touch based?
Click to expand...
Click to collapse
I explained in the post that I thought CWM had touch built-in and have since switched over to Philz.
Smith7018 said:
Nope, though I'll try to get to it tomorrow after work! If you want, I can give you an overview of what I did:
1. Pull the source for CM11.
2. Dump boot and recovery images using dd.
3. Ran makevender.sh using lge and dory.
4. lunch'd it up.
5. Replaced the recovery.fstab with the fstab from the recovery ramdisk.
6. Ran makerecovery.sh.
7. fastboot boot'd the recovery.img
This is all off the top of my head and missing some random files you had to hack around with, of course. Hope you get it working and more progress is made because I can't get to it for another day!
I explained in the post that I thought CWM had touch built-in and have since switched over to Philz.
Click to expand...
Click to collapse
I wasn't trying to shoot you down just suggesting if it would be easier to iron out since its built to be touch based...that's all
ptesmoke said:
I wasn't trying to shoot you down just suggesting if it would be easier to iron out since its built to be touch based...that's all
Click to expand...
Click to collapse
Heh, don't worry, you didn't seem like you were shooting me down at all! Anyway, I tried TWRP but it wouldn't boot for some reason (it's extremely hard to debug at the bootloader level). So, I went back to CWM and got swipe control working! Here's a build of the recovery image
NOTE: To boot this do NOT flash it; you need to "fastboot boot" it. Also, don't blame me if your watch breaks, yadda, yadda.
As per the source, I'll tell you the truth, it's pretty ugly and I'm deathly afraid of git so give me a few days until I get around to uploading it.
Download: https://mega.co.nz/#!ctMGgb4T!1g3m2PxsXH3LEoF0GuCaxFcfvrUBHc1_IW3nXDdGQbA
Smith7018 said:
Nope, though I'll try to get to it tomorrow after work! If you want, I can give you an overview of what I did:
1. Pull the source for CM11.
2. Dump boot and recovery images using dd.
3. Ran makevender.sh using lge and dory.
4. lunch'd it up.
5. Replaced the recovery.fstab with the fstab from the recovery ramdisk.
6. Ran makerecovery.sh.
7. fastboot boot'd the recovery.img
This is all off the top of my head and missing some random files you had to hack around with, of course. Hope you get it working and more progress is made because I can't get to it for another day!
I explained in the post that I thought CWM had touch built-in and have since switched over to Philz.
Click to expand...
Click to collapse
Interesting.
I was/am working on TWRP, but my first build wouldn't boot.
EDIT: Where did you get that strap? I really like it.
Smith7018 said:
Heh, don't worry, you didn't seem like you were shooting me down at all! Anyway, I tried TWRP but it wouldn't boot for some reason (it's extremely hard to debug at the bootloader level). So, I went back to CWM and got swipe control working! Here's a build of the recovery image
NOTE: To boot this do NOT flash it; you need to "fastboot boot" it. Also, don't blame me if your watch breaks, yadda, yadda.
As per the source, I'll tell you the truth, it's pretty ugly and I'm deathly afraid of git so give me a few days until I get around to uploading it.
Download: https://mega.co.nz/#!ctMGgb4T!1g3m2PxsXH3LEoF0GuCaxFcfvrUBHc1_IW3nXDdGQbA
Click to expand...
Click to collapse
Thanks man. Got it to boot up and backup worked. Guess that's about all u can do for now
Sent from my Nexus 5 using XDA Premium 4 mobile app
dude1981 said:
Thanks man. Got it to boot up and backup worked. Guess that's about all u can do for now
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Awesome! You can technically flash mods; I flashed the iOS emoji mod so now my hangout messages don't have the ugly Google ones :victory:
jamcar said:
Interesting.
I was/am working on TWRP, but my first build wouldn't boot.
EDIT: Where did you get that strap? I really like it.
Click to expand...
Click to collapse
Same, and I gave up; TWRP's UI won't really work out too well at 280x280, IMO, and CWM swipe is already working heh. I got the watch strap from eBay. It was super cheap and easy to adjust!
Why just booting it via fastboot instead of flashing it?
and have you push your device tree to github??
Smith7018 said:
Heh, don't worry, you didn't seem like you were shooting me down at all! Anyway, I tried TWRP but it wouldn't boot for some reason (it's extremely hard to debug at the bootloader level). So, I went back to CWM and got swipe control working! Here's a build of the recovery image
NOTE: To boot this do NOT flash it; you need to "fastboot boot" it. Also, don't blame me if your watch breaks, yadda, yadda.
As per the source, I'll tell you the truth, it's pretty ugly and I'm deathly afraid of git so give me a few days until I get around to uploading it.
Download: https://mega.co.nz/#!ctMGgb4T!1g3m2PxsXH3LEoF0GuCaxFcfvrUBHc1_IW3nXDdGQbA
Click to expand...
Click to collapse
just zipping your device tree and uploading it would work too.
And how you build a recovery and git look skeery?? lol
Smith7018 said:
Awesome! You can technically flash mods; I flashed the iOS emoji mod so now my hangout messages don't have the ugly Google ones :victory:
Same, and I gave up; TWRP's UI won't really work out too well at 280x280, IMO, and CWM swipe is already working heh. I got the watch strap from eBay. It was super cheap and easy to adjust!
Click to expand...
Click to collapse
Good deal. Do u happen have any links to mods or did u create them yourself?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Smith7018 said:
Awesome! You can technically flash mods; I flashed the iOS emoji mod so now my hangout messages don't have the ugly Google ones :victory:
Click to expand...
Click to collapse
This is exactly why I've rooted my watch! Well, that and the Gohma ROM.
The issue I'm having is pushing the .zip file to the sdcard. Getting an error saying it's read-only. Can't do it via adb because the second I boot into CWM my laptop forgets it's connected to anything.
PlayfulGod said:
Why just booting it via fastboot instead of flashing it?
and have you push your device tree to github??
Click to expand...
Click to collapse
It's only booting because it doesn't work when flashed to recovery. The file size is around 8 mb whereas the legitimate recovery is 23 mb, which I'm sure is an issue. Is it possible that I'm only creating a ramdisk that gets paired with the watch's kernel and I need to make an image with both of them? Sorry, this whole uBoot stuff confuses me a bit.
PlayfulGod said:
just zipping your device tree and uploading it would work too.
And how you build a recovery and git look skeery?? lol
Click to expand...
Click to collapse
Heh, I'm not actually afraid of git, I guess, I'm afraid of the whole "making a device-specific git repo that can be easily pulled while building CM." I guess I just don't have the time atm to set it up properly, but dw, I'll get to it this weekend! :fingers-crossed:
dude1981 said:
Good deal. Do u happen have any links to mods or did u create them yourself?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, the iOS mod is something I downloaded awhile ago for my N5. I'm afraid I don't have the link anymore. Sorry, man.
Pepski said:
This is exactly why I've rooted my watch! Well, that and the Gohma ROM.
The issue I'm having is pushing the .zip file to the sdcard. Getting an error saying it's read-only. Can't do it via adb because the second I boot into CWM my laptop forgets it's connected to anything.
Click to expand...
Click to collapse
Try pushing the zip to the sd card while it's normally booted and then restart. I think that's what I did, IIRC.
Smith7018 said:
Try pushing the zip to the sd card while it's normally booted and then restart. I think that's what I did, IIRC.
Click to expand...
Click to collapse
Getting:
Code:
C:\fastboot>adb push emoji.zip \sdcard
failed to copy 'emoji.zip' to '\sdcard': Read-only file system
This was just done while the watch is booted normally and plugged in via USB. It almost seems as though the root permission hasn't worked. I'm at a loss.
Pepski said:
Getting:
Code:
C:\fastboot>adb push emoji.zip \sdcard
failed to copy 'emoji.zip' to '\sdcard': Read-only file system
This was just done while the watch is booted normally and plugged in via USB. It almost seems as though the root permission hasn't worked. I'm at a loss.
Click to expand...
Click to collapse
Weird... I don't even think you need root to push to /sdcard/ but I could be wrong. I'd suggest trying /sdcard/emoji.zip so it knows where to resolve. Also, I don't use Windows, but does the backslash work on adb as a file separator?
what happened to development on this?
Hi all! I just finished porting Paranoid Android Beta 5 (Oct 22, 2014) to our beloved Vibrant. My only problem is my Vibrant is my daily driver. Can any kind soul whose Vibrant is not your daily driver (or if you just like to live on the bleeding edge) please test this out for me?
ROM *EDIT: Wi-Fi not working yet. Wi-Fi working now, but took down link to wait for original dev's permission. I have permission now, but I keep getting "No SD card" error
PA Gapps
Official PA5 xda link of the Rom I ported (i9000/galaxysmtd)
Permission from the official Rom maintainer is still pending, hopefully I'll get it soon.
Thank you so much!
Edit: I suppose I should include these steps (copied from xda thread above):
Installation Instructions
Coming other ROM
1. You must be rooted!
2. You must have a custom recovery installed.
3. Wipe your device if you are not coming from PA 4.+ already.
4. Flash the ROM zip, it could appear a warning (all data will be wiped due different partition table)
5. Reflash the ROM zip, it will continue now.
6. Flash the GAPPS.
7. Reboot. (It can take up to 5 min.)
8. Enjoy
Coming from AOSPA 4.0+
NOTE: I'm not responsible of crashes due kernel changes.
1. Flash the ROM zip.
2. Reboot.
3. Wait the upgrading android dialog.
4. Enjoy!
Click to expand...
Click to collapse
I don't know why I was hesitating - I could just take a Nandroid backup before flashing. I just did this, and I'm happy to report that everything went just fine! The only snag I had was a Wi-Fi problem - it says "Turning Wi-Fi on", but just stays like that. I remember seeing this problem somewhere before, maybe the kernel. Will investigate and report back
------
Edit (4.41pm cst):
SIGH... Been researching and trying out solutions all this time, and nothing's working Tried NeatKernel, Semaphore kernel, neither worked. Will keep at it and report back.
raddatt said:
I don't know why I was hesitating - I could just take a Nandroid backup before flashing. I just did this, and I'm happy to report that everything went just fine! The only snag I had was a Wi-Fi problem - it says "Turning Wi-Fi on", but just stays like that. I remember seeing this problem somewhere before, maybe the kernel. Will investigate and report back
------
Edit (4.41pm cst):
SIGH... Been researching and trying out solutions all this time, and nothing's working Tried NeatKernel, Semaphore kernel, neither worked. Will keep at it and report back.
Click to expand...
Click to collapse
you need to copy over system/lib/modules from base to port or from custom kernel if that what you're using, in order to get wifi working. I could of sworn PA was patched a certain way and would only run with its provided kernel or maybe something has changed since i last tried to port it for personal use. Also not a great idea posting ones work with out getting full permission yet may cause you trouble later on down the road...
dzee206 said:
you need to copy over system/lib/modules from base to port or from custom kernel if that what you're using, in order to get wifi working. I could of sworn PA was patched a certain way and would only run with its provided kernel or maybe something has changed since i last tried to port it for personal use. Also not a great idea posting ones work with out getting full permission yet may cause you trouble later on down the road...
Click to expand...
Click to collapse
Omg, that worked beautifully! Thank you so much, kind sir! I've also taken down the Rom download link and will put it back up again once I have full permission. Thanks for prompting me to do it. This is my first time at porting a Rom, so I'm not fully caught up on the etiquette yet. I've asked him for permission, and thought I could put it up only for testing purposes in the meantime, and then post it fully in our development forum once I have his full permission. He has been pretty great so far with granting a few people permission on that thread, so hopefully I can become one of them soon Thanks again so much!
Okay, it seems like I'm having another problem/bug. My phone's not detecting its SD card. When I tried to download a file it said, "No SD card". When I went to Settings/Storage, there are 2 areas of storage as usual, but it only lasts for about 3 seconds, then all the rows collapse and all I'm left with is "Internal Storage" and a couple of rows - no sight of an SD card. Is this something you've come across?
raddatt said:
Okay, it seems like I'm having another problem/bug. My phone's not detecting its SD card. When I tried to download a file it said, "No SD card. When I went to Settings/Storage, there are 2 areas of storage as usual, but it only lasts for about 3 seconds, then all the rows collapse and all I'm left with is "Internal Storage" and a couple of rows - no sight of an SD card. Is this something you've come across?
Click to expand...
Click to collapse
Try flashing one of the custom kernels we have and see if that works, if it doesn't help solve the issues it may just be kernel related. If all else fails give this a shot http://forum.xda-developers.com/showpost.php?p=51293597&postcount=151<br /> and if that doesn't help try porting a previous version of PA and see if the SD will mount properly.
For some reason whenever I flash a kernel, everything goes well until the "Android is upgrading" point. All apps are updated, then it says "starting apps" or something and it doesn't go anywhere after that, just stuck on that stage Then when I tried to reboot into recovery, it would be really difficult for some reason (like holding the buttons down would cause boot looping, very finicky). When I finally did get into recovery, it turned out to be Twrp, and not the Cwm I was used to. I have no idea where it came from, esp since I believe both port and base were cwm! I got really scared for a few minutes because twrp didn't have my backups. Finally, after a few more reboots, I got back the familiar cwm. I've never been so relieved in my life lol. I'm back to my old state, and will try again tomorrow morning. That's what I get for trying to play hero haha
Sent from my Vibrant using ugly ass xda app.
raddatt said:
For some reason whenever I flash a kernel, everything goes well until the "Android is upgrading" point. All apps are updated, then it says "starting apps" or something and it doesn't go anywhere after that, just stuck on that stage Then when I tried to reboot into recovery, it would be really difficult for some reason (like holding the buttons down would cause boot looping, very finicky). When I finally did get into recovery, it turned out to be Twrp, and not the Cwm I was used to. I have no idea where it came from, esp since I believe both port and base were cwm! I got really scared for a few minutes because twrp didn't have my backups. Finally, after a few more reboots, I got back the familiar cwm. I've never been so relieved in my life lol. I'm back to my old state, and will try again tomorrow morning. That's what I get for trying to play hero haha
Sent from my Vibrant using ugly ass xda app.
Click to expand...
Click to collapse
Its fine you ended up with twrp that happens when you flash a kernel that comes with twrp, see our device recovery image is within the kernel. I actually prefer twrp over cwm due to it being touch screen and putting less stress/abuse on the volume and power button/s. I checked the i9000 thread of PA and didn't see any users with the SD not mounting so I'm guessing it could be kernel related. If i can get my hands on my wife's vibrant I'll do a personal port and let you know of the results.
dzee206 said:
Its fine you ended up with twrp that happens when you flash a kernel that comes with twrp, see our device recovery image is within the kernel. I actually prefer twrp over cwm due to it being touch screen and putting less stress/abuse on the volume and power button/s. I checked the i9000 thread of PA and didn't see any users with the SD not mounting so I'm guessing it could be kernel related. If i can get my hands on my wife's vibrant I'll do a personal port and let you know of the results.
Click to expand...
Click to collapse
Ah, yes, from the kernel, that makes sense. Yeah, I'm glad more people are switching to Twrp because I like the touchscreen too instead of hurting the physical buttons. There's also a kernel (Semaphore?) that uses touchscreen scrolling in Cwm, which is cool too. Thank you, I'd really appreciate that!
Also, can you please show me how to properly bring an outside kernel into a Rom? I have been following this guide. It says to replace:
bml_over_mtd
bml_over_mtd.sh
erase_image
file_contexts
flash_image
make_ext4fs
boot.img
Plus system/lib/modules per your suggestion. However, I was about to try Iyahman's kernel, but it doesn't have:
file_contexts
flash_image
make_ext4fs
system/lib/modules
How would that work?
Btw, I just tried pulling the kernel resources of the kernel used by SlimKat into PA5 rom, but I still get the No SD card error
Our SlimKat rom uses the "samsung kernel aries", which is also used by the i9000 PA rom, so I thought it would work this time, but nope.
@dzee206 - Sorry for the spamming, man, but I just wanted to clarify the SD card problem I'm having, because I'm a bit confused as to what exactly it is. So when I try to download an .apk off of an xda thread using Browser, I get the error:
"No SD Card
An SD card is required to download ...apk"
But I am able to successfully download an app from the Play Store and use it well.
When I open Gallery, I get this error:
"No Storage
No external storage available"
Sorry I'm a big noob, but is the phone saying I don't have an external card or an internal card? I've never had these problems on this phone before, and I've never used an external SD on it. Thanks.
raddatt said:
Also, can you please show me how to properly bring an outside kernel into a Rom? I have been following this guide. It says to replace:
bml_over_mtd
bml_over_mtd.sh
erase_image
file_contexts
flash_image
make_ext4fs
boot.img
Plus system/lib/modules per your suggestion. However, I was about to try Iyahman's kernel, but it doesn't have:
file_contexts
flash_image
make_ext4fs
system/lib/modules
How would that work?
Click to expand...
Click to collapse
You only need the files in the root of the kernel (zip) not the folders though, don't worry about the modules with semaphore that's just how it is. Just leave file_contexts, flash_image, make_ext4fs that came with PA while porting they should suffice. Sorry man I ported PA yesterday while at my in-laws but didn't get a chance to transfer it over. I'd do it while at home but my PC exhaust fan crapped out on me and I won't have time to replace it till the beginning of next week. For now the best I can do is give advice base on my experience porting. May wanna give a different ROM a shot at porting such as DU or Mackay.
Sent from my SGH-I717 using XDA Premium 4 mobile app
dzee206 said:
You only need the files in the root of the kernel (zip) not the folders though, don't worry about the modules with semaphore that's just how it is. Just leave file_contexts, flash_image, make_ext4fs that came with PA while porting they should suffice. Sorry man I ported PA yesterday while at my in-laws but didn't get a chance to transfer it over. I'd do it while at home but my PC exhaust fan crapped out on me and I won't have time to replace it till the beginning of next week. For now the best I can do is give advice base on my experience porting. May wanna give a different ROM a shot at porting such as DU or Mackay.
Sent from my SGH-I717 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks man, I really appreciate your advice and efforts. Will try a couple more things and report back.
I tried putting Iyahman's Semaphore kernel stuff into PA5 and using SlimKat as base, but it didn't work I got the error 7, that the ROM was for i9000 and not for T959. I don't get why it happened... I deleted the i9000 lines from updater-script and everything, just like previous attempts (the rom had actually loaded properly in previous attempts, so the difference here must lie in the using of the kernel or SlimKat as base).
raddatt said:
I tried putting Iyahman's Semaphore kernel stuff into PA5 and using SlimKat as base, but it didn't work I got the error 7, that the ROM was for i9000 and not for T959. I don't get why it happened... I deleted the i9000 lines from updater-script and everything, just like previous attempts (the rom had actually loaded properly in previous attempts, so the difference here must lie in the using of the kernel or SlimKat as base).
Click to expand...
Click to collapse
Never use a ported ROM as base it be best to use the unofficial cm11 or spirit ROM, since those are the only ROMs we have that's built from source. Honestly if it was me I'd give up on PA and look for something else to run there's plenty of i9000 ROMs that have yet to be ported over or hasn't been updated I a while.
Sent from my SGH-I717 using XDA Premium 4 mobile app
dzee206 said:
Never use a ported ROM as base it be best to use the unofficial cm11 or spirit ROM, since those are the only ROMs we have that's built from source. Honestly if it was me I'd give up on PA and look for something else to run there's plenty of i9000 ROMs that have yet to be ported over or hasn't been updated I a while.
Sent from my SGH-I717 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ahh, thanks! I read somewhere that both base and port should both be either CM-based or AOSP-based, so I guess I started looking for AOSP-based roms and decided to try SlimKat. But I'll make sure not to use ported roms anymore. I tried the cm11 one, I might try Spirit as a last ditch effort, then see what else is on i9000. When Paranoid updated their website this week, I had checked it out, and when I saw galaxymtd as one of the legacy devices, I had gotten excited at the prospect of a new-ish rom. But lemme see what else is on i9000 after I try a couple more things here. Thanks again!
raddatt said:
Ahh, thanks! I read somewhere that both base and port should both be either CM-based or AOSP-based, so I guess I started looking for AOSP-based roms and decided to try SlimKat. But I'll make sure not to use ported roms anymore. I tried the cm11 one, I might try Spirit as a last ditch effort, then see what else is on i9000. When Paranoid updated their website this week, I had checked it out, and when I saw galaxymtd as one of the legacy devices, I had gotten excited at the prospect of a new-ish rom. But lemme see what else is on i9000 after I try a couple more things here. Thanks again!
Click to expand...
Click to collapse
It's some what true about using the same type of based ROMs when it comes to porting but pickings are slim. Myself and a bunch of other porters have been using cm as base and haven't had any issues porting different type ROMs.
Sent from my SGH-I717 using XDA Premium 4 mobile app