CyanogenMod is a free, community built distribution of Android 4.2 (Jelly Bean) which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
HOWTO
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm10 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
ENJOY AN UNOFFICIAL CM10 RELEASE BROUGHT TO YOU BY FreeXperia Team
PLEASE DONT MIRROR OUR ROMS
DOWNLOAD
http://unrestrict.li/FXP
thanks to all who made this possible supporting us
contributing with code, donations or even trusting us
thanks to SONY that made all this possible !
Changelogs
FXP214
- latest cm 10.1
- InCall audio Fix (T,V)
- Reduce audio gain (T,V)
FXP213
- latest cm 10.1
- Fix GPS (Xperia T,TX,V,Z,ZL)
FXP212
- latest cm 10.1
FXP211
- latest cm 10.1
- FMRadio (S,AcroS,Ion,T,TX,V,Z,ZL)
FXP210
- latest cm 10.1
FXP209
- latest cm 10.1
- SURPRISE (T,V,Z,ZL)
FXP208
- latest cm 10.1
- switch to sony 3.4 kernel (T,V)
- new wlan driver (T,V)
- alpha release (Xperia V)
FXP204-FXP207
- latest cm 10.1
FXP203
- latest cm 10.1
- external recovery support (T, V)
Flashed boot.img with fastboot, but i can't seem to access recovery with pressing vol+ or vol-.. Also no boot logo seems to appear.
Did i do something wrong?
NuriJ said:
Flashed boot.img with fastboot, but i can't seem to access recovery with pressing vol+ or vol-.. Also no boot logo seems to appear.
Did i do something wrong?
Click to expand...
Click to collapse
I'm going to try out the same myself now. Will report back
Edit: Having the exact same issue. No boot logo, and no CWM. It does boot however. Seems smooth, but the phone signal came after 3-4 minutes of having booted the phone. And it needed a few minutes to get full bars. Still seems that my signal is kind of poor, but still usable.
WIFI is working fine tho. Havent found anything else yet either thats not working.
Currently its blazing fast, and I will most likely use this from now on.
Going to fix CWM myself.
Keep it up guys!
Edit2: For those who didnt try it. Just flash the CM10 on your current CWM, dont flash the boot.img first
Edit3: Is there a reason to why the boot.img isnt adb root enabled?
Have been trying for quite some while now to implement it myself, but results in a bootloop.
I'm giving up on it. Assuming CWM will be implemented soon anyways
Edit4: Dumb me didnt test the camera before writing that everything worked.
FXP201 released (test build)
NuriJ said:
Flashed boot.img with fastboot, but i can't seem to access recovery with pressing vol+ or vol-.. Also no boot logo seems to appear.
Did i do something wrong?
Click to expand...
Click to collapse
dmbardal said:
I'm going to try out the same myself now. Will report back
Edit: Having the exact same issue. No boot logo, and no CWM. It does boot however. Seems smooth, but the phone signal came after 3-4 minutes of having booted the phone. And it needed a few minutes to get full bars. Still seems that my signal is kind of poor, but still usable.
WIFI is working fine tho. Havent found anything else yet either thats not working.
Currently its blazing fast, and I will most likely use this from now on.
Going to fix CWM myself.
Keep it up guys!
Edit2: For those who didnt try it. Just flash the CM10 on your current CWM, dont flash the boot.img first
Edit3: Is there a reason to why the boot.img isnt adb root enabled?
Have been trying for quite some while now to implement it myself, but results in a bootloop.
I'm giving up on it. Assuming CWM will be implemented soon anyways
Edit4: Dumb me didnt test the camera before writing that everything worked.
Click to expand...
Click to collapse
to reach recovery:vol- + power works
in recovery: did not recognize external-sd, give me error message obviously not possible to mount storage either
funiewski said:
to reach recovery:vol- + power works
in recovery: did not recognize external-sd, give me error message obviously not possible to mount storage either
Click to expand...
Click to collapse
ext sdcard is a work in progress and not yet done with the new mako kernel port. (mako dont have ext sdcard) so they need to implement sdcard support.
Skickat från min Nexus 4 via Tapatalk 2
After flashing 201 My phone won't boot
Need some quick help fixing this!
All I did was flash the boot.img (Which was placed together with fastboot.exe) and waiting for it to be done. Then I tried booting it.
xVenator said:
After flashing 201 My phone won't boot
Need some quick help fixing this!
All I did was flash the boot.img (Which was placed together with fastboot.exe) and waiting for it to be done. Then I tried booting it.
Click to expand...
Click to collapse
read post #2...... it saids exactly what to do after flashing boot.img
Skickat från min Nexus 4 via Tapatalk 2
I should have mentioned that's the problem. The purple light comes on, but nothing happen when I press the vol+ key
xVenator said:
I should have mentioned that's the problem. The purple light comes on, but nothing happen when I press the vol+ key
Click to expand...
Click to collapse
Just flash a stockrom with CWM, then put the CM10.1 .zip and the gapps file on the SD-Card \ Internal storage and flash the CM.zip and gapps.
Thats the way I did it. Works like a charm.
The bugs are still there tho ofcourse
dmbardal said:
Just flash a stockrom with CWM, then put the CM10.1 .zip and the gapps file on the SD-Card \ Internal storage and flash the CM.zip and gapps.
Thats the way I did it. Works like a charm.
The bugs are still there tho ofcourse
Click to expand...
Click to collapse
Can you link me to the one you used. I want to make sure everything goes as it should go
xVenator said:
Can you link me to the one you used. I want to make sure everything goes as it should go
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2081148
If you scroll down to the end of the pictures you'll see whats needed to get a custom rom up and running.
You can click the links there to get each and every step working.
But I can only assume you have done the most of it since you have flashed the CM10.1 kernel.
Feel free to /pm me aswell if you are having issues or dont know where to start \ what to do.
Edit:
as long as you have unlocked the bootloader, you can just do it in this order:
1: http://forum.xda-developers.com/showthread.php?t=2024299 to get an unlocked kernel that can handle root and CWM.
2: http://forum.xda-developers.com/showthread.php?t=2060815 Just follow step 3 since you have done the first two. (Remember to install superuser).
3: http://forum.xda-developers.com/showthread.php?t=2012738
Then you'll have CWM on a stock ROM.
Copy CM10.1 .zip and gapps .zip, flash both, reboot and enjoy!
xVenator said:
I should have mentioned that's the problem. The purple light comes on, but nothing happen when I press the vol+ key
Click to expand...
Click to collapse
to reach recovery in cm10.1 see #8
And for the record:
Hold the powerbutton when the pink\purple light turns on until it's orange. That will get you into CWM.
Not any of the volume-buttons.
Thanks a lot for your efforts. Just tried 201 for a couple of hours and I'm impressed so far. Will try it as a daily driver when camera is working.
May I ask for change logs?
Sent from your backyard...
Slender watches what you do...
-SlenderMan- said:
May I ask for change logs?
Sent from your backyard...
Slender watches what you do...
Click to expand...
Click to collapse
http://freexperiaproject.com/
The changelogs can be found in the above link. On the left side there will be a panel. Click on ChangeLog.
Related
Hi there,
I noticed I can't get in download mode anymore. Whatever I try it won't show the yellow triangular download sign. It just boots into cyanogen.
I have tried the 3 button trick but recovery nor download works. That's when I had the idea to apply the 3-button fix. adb reboot recovery brings me in the cwm recovery mode. adb reboot download just reboots the phone. I even tried the 300k ohm jig which always seemed to work as a failsafe. That also just boots the phone into cm.
I have checked with my brother who also runs CM nightly 101 and for him the download mode works fine so it is my phone, not CM.
The phone works fine now, is rooted too so I wondered if there's any way to fix this by rewriting the bootloaders. I want to have this fixed as a failsafe is flashing ever fails or if one of the nightlies gets corrupted.
Is there anyone who can confirm the download mode is in the primary bootloader (boot.bin from a stock rom) and is it safe to just flash_image that to the boot partition or will that be a guarantee to brick. The idea is that I still have root console access so I have to fix it from there.
Any help is appreciated.
Christiaan
Galaxy S
CyanogenMod 7 Nightly #101
Their is a chance that whenever u tried to go into download mode your phone was connected into charging and phone doesn't go into download mode when charging , please reply and tell Me that did I helped!
Sent from my GT-I9000 using XDA Premium App
BHuvan goyal said:
Their is a chance that whenever u tried to go into download mode your phone was connected into charging and phone doesn't go into download mode when charging , please reply and tell Me that did I helped!
Click to expand...
Click to collapse
Thanks for the quick reply.
Tried the tricks with and without pc-usb/charger and it made no difference. The 300k ohm jig trick can't be done with power or computer connected since you have to use the usb connection on the phone for it. It usually was my ever working failsafe.
I also tried the quickboot app without any luck. It seems it is responding to the download command but the code isn't there anymore.
Hey try going into download mode by touch controls although I haven't ever used cyanogen but i assume as every custom rom has this feature cyanogen must also have this! The download mode option in quick network options when u press the power button for 2 seconds ! Although it isn't safe but you cab try this and then if it goes into download mode then their must a way to go into download mode manually!
Sent from my GT-I9000 using XDA Premium App
BHuvan goyal said:
Hey try going into download mode by touch controls although I haven't ever used cyanogen but i assume as every custom rom has this feature cyanogen must also have this! The download mode option in quick network options when u press the power button for 2 seconds ! Although it isn't safe but you cab try this and then if it goes into download mode then their must a way to go into download mode manually!
Click to expand...
Click to collapse
Holding the power button for two seconds indeed brings up the profile/reboot/shutdown options. Selecting reboot only gives two additional options, reboot and recovery which do as they say. I can boot cwm recovery but from there I can't go into download mode either.
Try downloading terminal emulator and then reboot download or ADB reboot download
Nitro_123 said:
Try downloading terminal emulator and then reboot download or ADB reboot download
Click to expand...
Click to collapse
Tried it from the terminal with reboot download. Also tried adb reboot download long before that. It just reboots and starts. I have the feeling the piece of bootblock that's holding the download mode isn't there anymore.
There is an option in recovery to boot into download mode, Have you tried that ?
It sounds to me like that part of the bootloader is corrupt / missing.
Does the phone still work normally ? can you still continue to use it daily without the download mode option ?
azzledazzle said:
There is an option in recovery to boot into download mode, Have you tried that ?
It sounds to me like that part of the bootloader is corrupt / missing.
Does the phone still work normally ? can you still continue to use it daily without the download mode option ?
Click to expand...
Click to collapse
The phone works fine otherwise. I just want to fix this before it stops working fine and I need the download mode.
Recovery boots into CWM-based Recovery v4.0.1.5 which I got with CM7 with no option to return to the stock recovery or download mode as far as I can see. Also zipped updates from sd-card install fine from CWM recovery mode. If I just knew where to find a cwm ready zipped bootloader that will fix this.
cvdveer said:
The phone works fine otherwise. I just want to fix this before it stops working fine and I need the download mode.
Recovery boots into CWM-based Recovery v4.0.1.5 which I got with CM7 with no option to return to the stock recovery or download mode as far as I can see. Also zipped updates from sd-card install fine from CWM recovery mode. If I just knew where to find a cwm ready zipped bootloader that will fix this.
Click to expand...
Click to collapse
Thats a good idea, I think that should be made, Would save a lot of hassle...
In my recovery under 'advanced features' the option is there to reboot into android or reboot into download..
In order to go from CM7 - Stock, do you need re-partition with all 3 files ? or can you flash it through recovery ?
If so, flash it to stock and sell it to someone who has no idea about Custom ROMs / Hacking. (like me 12 months ago )
EDIT: is this issue not kernel related by any chance ?
azzledazzle said:
Thats a good idea, I think that should be made, Would save a lot of hassle...
In my recovery under 'advanced features' the option is there to reboot into android or reboot into download..
In order to go from CM7 - Stock, do you need re-partition with all 3 files ? or can you flash it through recovery ?
If so, flash it to stock and sell it to someone who has no idea about Custom ROMs / Hacking. (like me 12 months ago )
EDIT: is this issue not kernel related by any chance ?
Click to expand...
Click to collapse
Well I have no clue to make any package and I don't dare to flash_image some random boot.bin.
My recovery -> advanced only has reboot recovery which brings it back into recovery.
I'm afraid bringing it back to stock also needs odin/heimdall, that brings me back to the initial problem.
Selling it gives me the money for half a new phone. As long as its working fine I'd like to stick with it. My worst case scenario so far is that I'm stuck with CM7 nightly #101 for the coming 1.5 year which is annoying but far better than the slow stock samsung hands out.
The issue can't be directly kernel or CM7 related. My brother has CM7 #101 running and download mode works fine with him. (And no I can't secretly swap phones ) He doesn't know how to work with odin so I arranged everything for him. Exactly the same steps as I did my own phone. Perhaps a glitch in flashing or something.
cvdveer said:
Well I have no clue to make any package and I don't dare to flash_image some random boot.bin.
My recovery -> advanced only has reboot recovery which brings it back into recovery.
I'm afraid bringing it back to stock also needs odin/heimdall, that brings me back to the initial problem.
Selling it gives me the money for half a new phone. As long as its working fine I'd like to stick with it. My worst case scenario so far is that I'm stuck with CM7 nightly #101 for the coming 1.5 year which is annoying but far better than the slow stock samsung hands out.
The issue can't be directly kernel or CM7 related. My brother has CM7 #101 running and download mode works fine with him. (And no I can't secretly swap phones ) He doesn't know how to work with odin so I arranged everything for him. Exactly the same steps as I did my own phone. Perhaps a glitch in flashing or something.
Click to expand...
Click to collapse
Hmmm... tricky one to fix..
I have no more ideas i think flashing bootloaders through recovery would work like you said, But unless its a tried and tested method i wouldnt recommend it at all.
Have you posted this issue in the CM thread ? perhaps you could PM one of the Devs for assistance, or whether the whole 'flashing bootloader in recovery' idea would work at all.
You have nothing to lose by asking them.
Hope you get a solution... But until them im out of ideas.
Keep us updated if you get a fix.
Good luck man !!
EDIT: one more idea, Sounds risky but.... What if you made a nandroid backup on your brothers phone and restore it on yours ?? Thats if nandroid does back up bootloaders im not sure
azzledazzle said:
Hmmm... tricky one to fix..
I have no more ideas i think flashing bootloaders through recovery would work like you said, But unless its a tried and tested method i wouldnt recommend it at all.
Have you posted this issue in the CM thread ? perhaps you could PM one of the Devs for assistance, or whether the whole 'flashing bootloader in recovery' idea would work at all.
You have nothing to lose by asking them.
Hope you get a solution... But until them im out of ideas.
Keep us updated if you get a fix.
Good luck man !!
EDIT: one more idea, Sounds risky but.... What if you made a nandroid backup on your brothers phone and restore it on yours ?? Thats if nandroid does back up bootloaders im not sure
Click to expand...
Click to collapse
Thanks for thinking with me. I'll give the nandroid solution a go if there are no other replies within a reasonable time.
I'll post the same question in the CM forum but contacting the CM devs could be hard. They don't give any official support to nightlies and I can't say I'm convinced it has anything to do with CM at all. Though they do have the knowledge to answer the question or build a package to repair it. But you're right there's nothing to lose in asking.
Ofcourse I searched the forum before posting and found out I seem to be the only one ever with this problem. The solution could be as rare so I'll keep you posted if I make any progress beside here. That's what the whole idea behind this forum is for right?
True man !!
And if you get a solution or a dev to make a flashable bootloader. It could help other people in future
Good luck. Keep us posted
http://forum.xda-developers.com/showthread.php?t=1236273
Nitro_123 said:
http://forum.xda-developers.com/showthread.php?t=1236273
Click to expand...
Click to collapse
Interesting but that project still needs a bricked i9000 to tear apart. I don't have a captivate. Well if it ever becomes really bricked I'll consider donating mine.
And I'm okay with handling computers (yes I consider the phone a small computer about 400 times faster than my first pc) but when actual soldering is involved I give up.
fixable?
i have a samsung here the S GT I 9000 and i tryed to use odin on it and now this pops up every time i try to up load an os
--installing package...
finding package...
opening package...
verifying update package...
installing update...
successfully install update...
--copy media files...
successfully copied media files..
formatting /data...
E:format_volume: rfs format failed on / dev/block/mmcblk0p2
formatting /dbdata...
formatting /cache..
deleting meta data
data wipe fail.
-- appling multi-csc...
installing multi-csc..
cant access to '/system/csc/bmc/system/' . sucessfully applied multi-CSC
Help!
Hi! If it still doesn't work, try downloading ROM Manager from the market and install the latest CWM. It sounds like your bootloader got modified/locked.
Erahgon said:
Hi! If it still doesn't work, try downloading ROM Manager from the market and install the latest CWM. It sounds like your bootloader got modified/locked.
Click to expand...
Click to collapse
Errr talking to me or adonai? Sounds like two seperate problems for two seperate topics.
cvdveer said:
Interesting but that project still needs a bricked i9000 to tear apart. I don't have a captivate. Well if it ever becomes really bricked I'll consider donating mine.
And I'm okay with handling computers (yes I consider the phone a small computer about 400 times faster than my first pc) but when actual soldering is involved I give up.
Click to expand...
Click to collapse
I REALLY liked your answer
BTW , same here
Shabbypenguin and the OUDHS
presents to you
OUDHS Touch CWM-based Recovery 1.0.3.3
for your Sprint Samsung Galaxy S 4
Read this whole post before doing anything
Enjoy
OUDHS CWM-based Recovery 1.0.3.3
Odin 3.04
Directions:
1) Download the above files
2) Extract Odin3-3.04.zip and copy the tar that you downloaded into the folder
3) Run Odin as an administrator
4) Power your device off
5) Press and hold volume down, home, and power to enter download mode
6a) Connect your phone to your computer
6b) Wait for drivers to finish installing if they need to be
7) You should see Odin find your device by marking a blue square in the ID COM box
8) Click on PDA and choose the recovery tar you downloaded
9) Click start
10) when it says finished you need to beat your phone in a race
11) you need to unplug it and press and hold volume up and power until the blue text appears
12) let go
13 once you have booted into recovery it will handle the script that installs stock recovery if its present.
-------------------------------------------------------------------------------------------------------------------------------------------------
Congrats you now have CWM now if you wish to root youll need to follow these instructions
-------------------------------------------------------------------------------------------------------------------------------------------------
Superuser-1.0.1.1.zip
Directions:
1) Download the above file
2) Connect your phone and copy them to your phone
3) Once they are copied power down your device
4) Hold volume up and power to enter recovery
5) Navigate recovery by using the volume keys and power to select
6) Choose install zip from sdcard, then pick internal or external (where you copied it to)
7) Scroll down to the Superuser.zip and select it to install
-------------------------------------------------------------------------------------------------------------------------------------------------
Congrats you are rooted! this procedure will work on any firmware update you guys get
-------------------------------------------------------------------------------------------------------------------------------------------------
With the SGS4 samsung has introduced a setuid kernel, which will block root access. you will need to flash a source compiled kernel in order to fully root.
Source for jfltespr
Credits:
Members of the Official Unloved Devices Hit Squad (OUDHS) for being the best we can for those whom need us
garwynn for helping with setting up jflte-common stuff
MoHoGalore for testing so many times
Awesome! Thanks to the devs!
Awesome! Good to see ya around here Shabby!
Sent from my SPH-L720 using Tapatalk 2
Good deal. Thanks Shabby!
Sent from my SPH-L710 using Xparent Skyblue Tapatalk 2
Just successfully flashed OUDHS CWM-based Recovery 1.0.3.0 successfully...haven't tried much of the functionality until I fix my phone from the bootloop I put it in.
Something I did notice while navigating around the menu using my volume keys was that the screen was only refreshing every other keypress. I know that the state of the program was changing but the screen was only redrawing every other input.
harrybozack said:
Just successfully flashed OUDHS CWM-based Recovery 1.0.3.0 successfully...haven't tried much of the functionality until I fix my phone from the bootloop I put it in.
Something I did notice while navigating around the menu using my volume keys was that the screen was only refreshing every other keypress. I know that the state of the program was changing but the screen was only redrawing every other input.
Click to expand...
Click to collapse
yea was an issue on the note 2 at launch as well, they fixed it so i just gutta figure out how. mind testing twrp?
shabbypenguin said:
yea was an issue on the note 2 at launch as well, they fixed it so i just gutta figure out how. mind testing twrp?
Click to expand...
Click to collapse
Not at all...in fact it was the first one I tried. The graphics were completely screwed up and unable unfortunately
harrybozack said:
Not at all...in fact it was the first one I tried. The graphics were completely screwed up and unable unfortunately
Click to expand...
Click to collapse
possible for you to take a picture? i cant go forward with fixing it til i have an idea of what might be the hangup :/
http://forum.xda-developers.com/showthread.php?t=2254323 This CWM based recovery also has the same redraw problem yours does.
harrybozack said:
http://forum.xda-developers.com/showthread.php?t=2254323 This CWM based recovery also has the same redraw problem yours does.
Click to expand...
Click to collapse
yea thats because i made mine while he worked on the common stuff. he is trying to get cm going while i want to get cwm/twrp. i leave the roms and stuff to people who are invested in the device
shabbypenguin said:
possible for you to take a picture? i cant go forward with fixing it til i have an idea of what might be the hangup :/
Click to expand...
Click to collapse
http://img12.imageshack.us/img12/1061/img20130428102510.jpg
harrybozack said:
http://img12.imageshack.us/img12/1061/img20130428102510.jpg
Click to expand...
Click to collapse
recompiling with teh fix now
www.shabbypenguin.com/OUDstuff/Samsung/Sprint/jfltespr/Recovery/TWRP-jfltespr-Test-2.tar
should fix slanty graphics
Flashed fine, graphics good but can't navigate anywhere.
lafester said:
Flashed fine, graphics good but can't navigate anywhere.
Click to expand...
Click to collapse
twrp? or cwm? a bit more info please
lafester said:
Flashed fine, graphics good but can't navigate anywhere.
Click to expand...
Click to collapse
I got this same result. Seems to freeze right away. TWRP-jfltespr-Test-2.tar
k can you get /tmp/recovery.log pulled for me please
edit: test 3 to see if this fixes anything:
www.shabbypenguin.com/OUDstuff/Samsung/Sprint/jfltespr/Recovery/TWRP-jfltespr-Test-3.tar
shabbypenguin said:
k can you get /tmp/recovery.log pulled for me please
edit: test 3 to see if this fixes anything:
www.shabbypenguin.com/OUDstuff/Samsung/Sprint/jfltespr/Recovery/TWRP-jfltespr-Test-3.tar
Click to expand...
Click to collapse
sorry been testing cwm but yeah I was talking about twrp. its just the touchscreen not registering will test again in a sec
I had the same problem as the guy above and tried the test 3 tar and it fixes the screen but no touch function.
also just tried CWM recovery and it was only letting me go to every other selection then rebooted all on its own.
LG710S34LYFE said:
I had the same problem as the guy above and tried the test 3 tar and it fixes the screen but no touch function.
also just tried CWM recovery and it was only letting me go to every other selection then rebooted all on its own.
Click to expand...
Click to collapse
Please don't forget to post in the CWM thread as well so no information is lost to the that effort.
LG710S34LYFE said:
I had the same problem as the guy above and tried the test 3 tar and it fixes the screen but no touch function.
also just tried CWM recovery and it was only letting me go to every other selection then rebooted all on its own.
Click to expand...
Click to collapse
confirmed test 3 did not fix the touch screen issue. cwm will sometimes double click and is tricky to navigate with the graphics issue but functions normally otherwise. did a full wipe and restore booted fine both times with no permissions issues. this was garwyns version btw.
This is an old unofficial version. Please go to THIS thread for the updated, official version.
All information below this line pertains to the old, unofficial version. Use the link above to get the official version.
Updated (v2) Slow recovery bootup fixed.
This is an unofficial version of CWM Advanced/PhilZ Touch recovery. Main thread located HERE. Go to the main thread to learn about all the features.
It uses the zImage and ramdisk provided by @ketut.kumajaya with a few tweaks to get it working made by myself.
Please take a moment to say thanks and/or donate to @ketut.kumajaya for helping us out.
It takes a few seconds longer for CWM based recoveries to boot than the stock recovery, so be patient.
Credits go to:
@Phil3759 for the advanced features
@ketut.kumajaya for the working zImage
and of course Koush and the CyanogenMod team
Link to kernel source https://github.com/kumajaya/android_kernel_samsung_lt02
~~~~~~~~~~~~~~~~~~~~~~~~~~~
If the on-screen menu doesn't show, hit one of the up/down buttons at the bottom to get it to appear. This is the same issue seen with CWM recovery and is caused by booting into recovery with the key combo. I highly recommend using the Quick Boot app or another software method of booting recovery.
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Instructions:
1. Download ODIN on your computer.
2. Power off the device.
3. Restart in "Download Mode" by holding the "HOME" button, "Volume Down" and "Power" all at the same time (for about 5 seconds).
4. Hit the "Volume Up" to enter download mode.
5. Start the ODIN exe program. Un-check Auto Reboot. See notes about ODIN below.
6. Connect the device via USB to your computer. Verify the device shows as "Added" in the Message box. If it doesn't show then you need the Samsung USB drivers (just install KIES to get them).
7. Select "PDA" then choose the recovery file you want to flash.
8. Hit "START". Wait for Odin to finish (~10-15 seconds). The message area will display "RES OK" when finished.
9. Wait for device to restart. Skip this step if you unchecked auto reboot.
10. Restart directly to recovery mode before rebooting into OS.(Hold POWER, Volume UP, and the HOME button all at the same time. When you see the Samsung Logo, let go of the POWER button, but keep holding the Volume UP and HOME until you see the recovery screen).
11. To get the Internal SDcard to be recognized properly, choose the Advanced option; then touch the "Storage set to" option. It should change from "/data/media/0" to "data/media/". Then reboot recovery using the "Power Options".
I also recommend adjusting the Menu Height to a smaller value using the PhilZ settings option.
Notes about ODIN
--Make sure that "Re-Partition" is NOT checked.
--Auto Reboot can be un-checked if the recovery doesn't flash correctly on your device. Some have reported that un-checking Auto Reboot fixes this issue. If you un-check Auto Reboot, you will need to reboot the device yourself (refer back to step 10).
Instructions for recovery flashable version:
Boot into your previously installed custom recovery.
Select the Install Zip option.
Find the recovery zip.
Flash.
Reboot recovery.
Enjoy your new recovery.
Main Menu
Downloaded and installed. What i found so far is that it reacts little slow and the time in the status bar is gone in lockscreen.... After unlocking clock comes back in status bar.
Cant change GUI height correctly, all the time i touch GUI it increases the value only...
batman08 said:
Downloaded and installed. What i found so far is that it reacts little slow and the time in the status bar is gone in lockscreen.... After unlocking clock comes back in status bar.
Click to expand...
Click to collapse
I'm not sure what you mean about the time. It is not supposed to be in the status bar on the lock screen, and that has nothing to do with this recovery.
Sent from my DROID RAZR MAXX HD
gr8nole said:
I'm not sure what you mean about the time. It is not supposed to be in the status bar on the lock screen, and that has nothing to do with this recovery.
Sent from my DROID RAZR MAXX HD
Click to expand...
Click to collapse
Ok, haven't paid much attention to that to be frank.
batman08 said:
Downloaded and installed. What i found so far is that it reacts little slow and the time in the status bar is gone in lockscreen.... After unlocking clock comes back in status bar.
Cant change GUI height correctly, all the time i touch GUI it increases the value only...
Click to expand...
Click to collapse
In regards to it reacting slowly, since you complained about that with TWRP also, I believe that is a problem with your tablet. I can't imagine it working any faster on mine. Every selection is immediate.
Keep increasing the gui height until it goes to a lower value (around 100 it switches).
Sent from my DROID RAZR MAXX HD
gr8nole said:
In regards to it reacting slowly, since you complained about that with TWRP also, I believe that if a problem with your tablet. I can't imagine it working any faster on mine. Every selection is immediate.
Sent from my DROID RAZR MAXX HD
Click to expand...
Click to collapse
Some other users also experienced slow reaction with latest TWRP. I used TWRP 2.5.0.0 and speed and reaction was ok, on 2.6.xx reaction is slow...
Awesome job. Like how this is all coming together slowly for this tablet...
gr8nole said:
This is an unofficial version of CWM Advanced/PhilZ Touch recovery. Main thread located HERE. Go to the main thread to learn about all the features.
Since your in the recovery mood you should check out shabbyPenguins recovery OUDHS I think
Click to expand...
Click to collapse
my phone is samsung GT-I8268 Marvell PXA988 kernel
please Compile CWM Recovery for I8268
@ketut.kumajaya
Can we have cwm flashable zip please.
Regards.
Sent from my GT-N7100 using xda premium
nitol said:
Can we have cwm flashable zip please.
Regards.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Done. Flashable zip in OP.
After flashing one of the custom ROM's, I still get Android System recovery in Recovery mode. Tried 3 different ones, not working... Anyone? In Download mode it however says Custom...
/edit: turning off auto-reboot fixed it!
OP updated with v2. Slow recovery bootup fixed.
Ive tried this with auto reboot checked and unchecked.. and im still getting android recovery. I have Kies installed.. do i need to install drivers on my pc?? I waited several minutes but all i get is leave cs...
freak69ize said:
Ive tried this with auto reboot checked and unchecked.. and im still getting android recovery. I have Kies installed.. do i need to install drivers on my pc?? I waited several minutes but all i get is leave cs...
View attachment 2418355
Click to expand...
Click to collapse
Hit START
Ohhh.. DUHHH... hahaha i should have know that seeing thats how i rooted my S3. So i take it i have root also now right?? Or do i have to flash something else?
freak69ize said:
Ohhh.. DUHHH... hahaha i should have know that seeing thats how i rooted my S3. So i take it i have root also now right?? Or do i have to flash something else?
Click to expand...
Click to collapse
Flash the root.zip from the cwm or twrp thread.
Sent from my DROID RAZR MAXX HD
Hi, i have a t217A tab 3 7.0 and it has a msm8960 cpu not the msm8930 you mentioed earlier, which shows up under cpuz as a Krait 1.73 gighz
when i boot to recovery it says encrypted and the flash fails. im guessing i need a diffrent version. is there a current build for the touch screen recovery for this version already made and in place ? if so could someone link me ?
and i had a q , you mention that this should be flashed via already flashed recovery , is this mandatory or can i flash the touch version via odin straight away ? do i need to flash the regular non touch recovery then flash the touch or can i get away with directly flashing the touch recovery without first flashing the non touch?
I have rooted already , the method on this forum worked for the t217A
thanks
spydergt said:
Hi, i have a t217A tab 3 7.0 and it has a msm8960 cpu not the msm8930 you mentioed earlier, which shows up under cpuz as a Krait 1.73 gighz
when i boot to recovery it says encrypted and the flash fails. im guessing i need a diffrent version. is there a current build for the touch screen recovery for this version already made and in place ? if so could someone link me ?
and i had a q , you mention that this should be flashed via already flashed recovery , is this mandatory or can i flash the touch version via odin straight away ? do i need to flash the regular non touch recovery then flash the touch or can i get away with directly flashing the touch recovery without first flashing the non touch?
I have rooted already , the method on this forum worked for the t217A
thanks
Click to expand...
Click to collapse
No , it has msm8930 it will still show as 8960 it's a qcom thing. Also this isn't for your device.
READ THIS POST BEFORE INSTALLING ANY CUSTOM RECOVERY
Updated to version 2.7.1.0.KK on 10-28-14. Now works with KitKat (and older JB) bootloaders.
Now properly supports all set_metadata functions in newer updater-scripts.
Click HERE for the latest version.
Please report any bugs here in this thread.
Please take a moment to say thanks and/or donate to @ketut.kumajaya for helping us out.
I have a T210R, so I haven't tested on a T211.
Credits go to:
@ketut.kumajaya for working kernel
@Jamison904 for giving us root
@hkjr for getting ketut to help
and of course the Team Win group
Instructions for ODIN
1. Download ODIN on your computer.
2. Power off the device.
3. Restart in "Download Mode" by holding the "HOME" button, "Volume Down" and "Power" all at the same time (for about 5 seconds).
4. Hit the "Volume Up" to enter download mode.
5. Start the ODIN exe program. Un-check Auto Reboot. See notes about ODIN below.
6. Connect the device via USB to your computer. Verify the device shows as "Added" in the Message box. If it doesn't show then you need the Samsung USB drivers (just install KIES to get them).
7. Select "PDA" then choose the recovery file you want to flash.
8. Hit "START". Wait for Odin to finish (~10-15 seconds). The message area will display "RES OK" when finished.
9. Wait for device to restart. Skip this step if you unchecked auto reboot.
10. Restart directly to recovery mode before rebooting into OS.(Hold POWER, Volume UP, and the HOME button all at the same time. When you see the Samsung Logo, let go of the POWER button, but keep holding the Volume UP and HOME until you see the recovery screen).
After you get the custom recovery working, you can flash the latest SuperSu zip to get root.
Your internal SDcard will get mounted as "/data/media". So look there for any files saved to the internal card.
Notes about ODIN
--Make sure that "Re-Partition" is NOT checked.
--Auto Reboot can be un-checked if TWRP doesn't flash correctly on your device. Some have reported that un-checking Auto Reboot fixes this issue. If you un-check Auto Reboot, you will need to reboot the device yourself (refer back to step 10).
Instructions for recovery flashable version:
Boot into your previously installed custom recovery.
Select the Install Zip option.
Find the recovery zip.
Flash.
Reboot recovery.
Enjoy your new recovery.
Flash at own risk!!!!
+++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++
Click HERE for the latest version.
Reserved
sormat1 from 4PDA reported:
Sorry, qiuck Translate by Google:
Loaded, but the buttons do not match the strong places of pression, which will invoke the appropriate menu button.
The same is within of menu: you press on an arbitrary place, but opens something another.
Click to expand...
Click to collapse
See: http://4pda.ru
Dasdranamin said:
sormat1 from 4PDA reported:
Sorry, qiuck Translate by Google:
See: http://4pda.ru
Click to expand...
Click to collapse
Thanks for the report, will look into it.
Hey @ketut.kumajaya, it seems the touchscreen needs to be rotated for this one. I would attempt to fix it, but we all know you can do it much, much better (and I don't want to start all over without your kernel source)
EDIT: I used the new zImage from the 1.8 T210(R) version in my T210(R) TWRP and the touchpoints are off in it as well. Looks like the previous touch orientation fix you made got overwritten with the new update.
Looks like it only needs to be rotated clockwise 90 degrees (not flipped, just rotated).
gr8nole said:
Hey @ketut.kumajaya, it seems the touchscreen needs to be rotated for this one. I would attempt to fix it, but we all know you can do it much, much better (and I don't want to start all over without your kernel source)
EDIT: I used the new zImage from the 1.8 T210(R) version in my T210(R) TWRP and the touchpoints are off in it as well. Looks like the previous touch orientation fix you made got overwritten with the new update.
Looks like it only needs to be rotated clockwise 90 degrees (not flipped, just rotated).
Click to expand...
Click to collapse
Did you set the touchscreen orientation to landscape?
Code:
write /sys/devices/virtual/sec/tsp/orientation 6
ketut.kumajaya said:
Did you set the touchscreen orientation to landscape?
Code:
write /sys/devices/virtual/sec/tsp/orientation 6
Click to expand...
Click to collapse
How do I set that for the recovery? init.rc?
Sent from my DROID RAZR MAXX HD
gr8nole said:
How do I set that for the recovery? init.rc?
Sent from my DROID RAZR MAXX HD
Click to expand...
Click to collapse
Like this: http://forum.xda-developers.com/showpost.php?p=39935850&postcount=89
ketut.kumajaya said:
Like this: http://forum.xda-developers.com/showpost.php?p=39935850&postcount=89
Click to expand...
Click to collapse
Ha...it was already in there, but it was commented out.:laugh:
Dasdranamin said:
sormat1 from 4PDA reported:
Sorry, qiuck Translate by Google:
See: http://4pda.ru
Click to expand...
Click to collapse
New version uploaded with touchscreen orientation fixed.
gr8nole said:
New version uploaded with touchscreen orientation fixed.
Click to expand...
Click to collapse
Thank You.
All works properly! :good:
It works for me.
Thank you very much.
only worked with external sd attached....without it, the recovery cannot read internal sdcard...cmiiw...
godh3ll said:
only worked with external sd attached....without it, the recovery cannot read internal sdcard...cmiiw...
Click to expand...
Click to collapse
Not true...your internal SDcard is mounted as "/data/media". Navigate to that folder and you will find everything on your internal card. You will have to hit the "Up one level" button to find it.
EDIT: I will add a note to the OP about this.
Now that there's root and recovery, has anyone flashed a successful ROM for the T211?
gr8nole said:
Not true...your internal SDcard is mounted as "/data/media". Navigate to that folder and you will find everything on your internal card. You will have to hit the "Up one level" button to find it.
EDIT: I will add a note to the OP about this.
Click to expand...
Click to collapse
Yup my mistaken...the zip was there in media folder..
BiG JeW said:
Now that there's root and recovery, has anyone flashed a successful ROM for the T211?
Click to expand...
Click to collapse
Off course, I flashed the only ROM for T211, infamous combined with black hawk kernel..
Sent from my SM-T211 using Tapatalk 4 Beta
godh3ll said:
Yup my mistaken...the zip was there in media folder..
Off course, I flashed the only ROM for T211, infamous combined with black hawk kernel..
Sent from my SM-T211 using Tapatalk 4 Beta
Click to expand...
Click to collapse
you did how does this rom work any performance improvements any issues .. i want to flash it myself
jetboss said:
you did how does this rom work any performance improvements any issues .. i want to flash it myself
Click to expand...
Click to collapse
Didnt test all the function yet...but stable for daily use, still laggy sometimes, I wonder when we got official 4.2 or skip to 4.4? Anyhow, just test the rom yourself based on cuŕiosity..
Sent from my SM-T211 using Tapatalk
godh3ll said:
Didnt test all the function yet...but stable for daily use, still laggy sometimes, I wonder when we got official 4.2 or skip to 4.4? Anyhow, just test the rom yourself based on cuŕiosity..
Sent from my SM-T211 using Tapatalk
Click to expand...
Click to collapse
might just have to do that well from seeing the requirements on kit kat i believe we will get an official update but when i dont know Samsung kinda slow when releasing updates so just hoping some devs do something soon
sorry sir, i try using this cwm but fail in progress. Now my startup just say "firmware upgrade encountered an issue. please select recovery mode in kies & try again".
Would shut i do sir.
Thanks
Here is a hacked cm rom for the t-800. I am NOT a dev, or anywhere near one. This rom has some issues that I CANT fix. Camera is rotated 90 degrees, and some other little ones i cant remember. ALL credit goes to @lonespeaker for the boot.img to make the t800 boot, and @eousphoros for his rom for the t-700. Please dont contact me with issues, as i wont be able to fix them. Im just sharing this, as I have had tons of pm asking for it.
You also need to install latest GAPPS
Rom
https://drive.google.com/file/d/0BwPAGUQCA8FDQVhiVU9GSGwyaVE/view?usp=sharing
BIG thanks to @eousphoros and @lonespeaker
Source code
* CyanogenMod
https://github.com/CyanogenMod
* Device specific repos
https://github.com/eousphoros/androi..._klimtwifi.git
https://github.com/eousphoros/androi...exynos5420.git
https://github.com/eousphoros/androi...exynos5420.gi
Ah thank you for this, looking forward to what the future holds.
Edit: I thought I'll add a list of bugs I've found so users know about them and know that suzook also knows but as said he is not a dev and can't fix them.
So if you can live with the following then download away:
Artifacts with animations - rotation of device animation and recents tab animation. Reduce animations in developer settings to 0.5 to make it hardly noticeable.
Recents button does not work at all, does light up though. Map action to home button long press.
Camera is rotated 90° off. Sometimes FC's
Softkeys do not vibrate, can't find the setting to turn on so assume the feature is missing.
That's all I've found for now.
Still better than touchwiz.
Thank you very much for your work!
I tried it and CM11 installs and boot up very well on my T-800.
Only one issue (besides of the things that are written) I have found is that there is no support for exfat for the external sdcard.
I think CM11 is really possible on the T-800 and T-805.
@suzook:
Have you tried repackaging CM11 from the Tab Pro 10.1 (https://download.cyanogenmod.org/?device=picassowifi) for the Tab S?
I think if you remap the target partitions in the installer script, it could flash correctly.
Perhaps you could ask @crpalmer for help on this one.
He's maintaining CM11 for the tab pro 10.1 which is quite similar to the tab s.
Dr. Hurt said:
@suzook:
Have you tried repackaging CM11 from the Tab Pro 10.1 (https://download.cyanogenmod.org/?device=picassowifi) for the Tab S?
I think if you remap the target partitions in the installer script, it could flash correctly.
Perhaps you could ask @crpalmer for help on this one.
He's maintaining CM11 for the tab pro 10.1 which is quite similar to the tab s.
Click to expand...
Click to collapse
Yes I have, it works perfectly except camera and ext SD card doesn't mount. If anyone wants, they can download nightly,replace boot.IMG from this ROM, along with the WiFi folder. It boots and works.
What we REALLY need is a custom kernel, as I believe that is our camera issue.
suzook said:
Yes I have, it works perfectly except camera and ext SD card doesn't mount. If anyone wants, they can download nightly,replace boot.IMG from this ROM, along with the WiFi folder. It boots and works.
What we REALLY need is a custom kernel, as I believe that is our camera issue.
Click to expand...
Click to collapse
Excellent news... Now we can stay up to date with CM11 upstream since the Tab Pro 10.1 is officially supported by CyanogenMod.
I think this is the start of something big for the Tab S users.
The Tab Pro kernel (boot.img) doesn't work?
Dr. Hurt said:
Excellent news... Now we can stay up to date with CM11 upstream since the Tab Pro 10.1 is officially supported by CyanogenMod.
I think this is the start of something big for the Tab S users.
The Tab Pro kernel (boot.img) doesn't work?
Click to expand...
Click to collapse
Well, I didnt try it. Im away from comp. Do you wanna give it a try? Worse case scenario is it wont boot, but you might have to odin back.
suzook said:
Well, I didnt try it. Im away from comp. Do you wanna give it a try? Worse case scenario is it wont boot, but you might have to odin back.
Click to expand...
Click to collapse
I also don't have access to a PC right now (vacation) for a few days.
The Tab Pro is using a generic exynos 5420 kernel so it will probably work. And if not, you should still have access to CWM to reflash the T800 kernel back.
I'd still strongly recommend that any testers have a PC with Odin and a stock ROM ready, just in case.
So any volunteers?
Sorry guys, new link up. The link i had was actually the latest nightly for the tab pro. New link up. Cam should be sorta working at 90degrees, and ext card should now be seen.
PS. The device specific repo links are truncated.
I try tomorrow to flash a Tab pro 10.1 nightly on my Tab S 10.5. I trust in a good TWRP Backup.
Edit: directly flashing from cm-11-20141011-NIGHTLY-picassowifi.zip (that's the actual nightly for the Tab pro 10.1) does not work. I get promptly the message "the rom is for picassowifi but this is chagallwifi". So the zip-file must be modified before flashing in any case.
hurray said:
I try tomorrow to flash a Tab pro 10.1 nightly on my Tab S 10.5. I trust in a good TWRP Backup.
Edit: directly flashing from cm-11-20141011-NIGHTLY-picassowifi.zip (that's the actual nightly for the Tab pro 10.1) does not work. I get promptly the message "the rom is for picassowifi but this is chagallwifi". So the zip-file must be modified before flashing in any case.
Click to expand...
Click to collapse
I think you'll need to replace the updater-script in the picassowifi.zip\META-INF\com\google\android with the T800 one (from the first post).
You can use 7-zip or winrar for this.
Didn't work for suzook.
Just tried flashin picaaso cm, it doesnt boot. gets stuck at samsung logo. This is why we need a custom kernel.
DO NOT FLASH>>>I HAVE A BRICK>>CANT GET INTO ODIN!
Can you get back into CWM?
Are you trying correctly?
Put tablet into download mode. [Hold power and vol down until text shows, then press vol up]
Dr. Hurt said:
Can you get back into CWM?
Are you trying correctly?
Put tablet into download mode. [Hold power and vol down until text shows, then press vol up]
Click to expand...
Click to collapse
Not sure wtf i was thinking flashing a boot.img from another device. As of now im bricked, and cant get into dl mode, so no odin for me. Bummer.
Dr. Hurt said:
Can you get back into CWM?
Are you trying correctly?
Put tablet into download mode. [Hold power and vol down until text shows, then press vol up]
Click to expand...
Click to collapse
Not sure wtf i was thinking flashing a boot.img from another device. As of now im bricked, and cant get into dl mode, so no odin for me. Bummer.
any updates?
Got into CWM or Download mode?
Edit:
vol up + vol down + power for 10 seconds = restart
As soon as it restarts quickly press and hold:
vol down + home = download
Dr. Hurt said:
any updates?
Got into CWM or Download mode?
Edit:
vol up + vol down + power for 10 seconds = restart
As soon as it restarts quickly press and hold:
vol down + home = download
Click to expand...
Click to collapse
Nope. just stuck at samsung screen, reboot to samsung screen.
Thats very sad and strange..
Download mode, when requested, starts before the kernel is even loaded so this is just strange.
Try some of those things listed here:
http://forum.xda-developers.com/showthread.php?t=1069032
- Connect via USB
- Make sure all USB drivers are installed
- Try different versions of odin
As a last resort, take it to a samsung service centre to get the software restored.
I've had that done once before (a few years back)!!
At my tests I am every time able to enter download mode or reset the Tab via power & vol down (and maybe the home button, but I'm not sure for this) for about 10-20 seconds (it was a very long time...).