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...).
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
I find my newly purchased tab 8.9 very laggy with the stock TouchWiz
Before returning it I wanted ti try the Overcome rom to see if it can get any smoother.
I carefully followed there instructions but I am unable to go past the downloading droid. once I validate with the right button volume, the tablet simply reboots.
Does anyone else have this issue?
josibarns said:
I find my newly purchased tab 8.9 very laggy with the stock TouchWiz
Before returning it I wanted ti try the Overcome rom to see if it can get any smoother.
I carefully followed there instructions but I am unable to go past the downloading droid. once I validate with the right button volume, the tablet simply reboots.
Does anyone else have this issue?
Click to expand...
Click to collapse
Let me get this right: you sucessfully flashed Overcome, and want to ODIN but when you try to get in Download Mode, it reboots, is that it? If so, that's the first time I've heard this issue. How are you trying to enter Download Mode?
nirogu325 said:
Let me get this right: you sucessfully flashed Overcome, and want to ODIN but when you try to get in Download Mode, it reboots, is that it? If so, that's the first time I've heard this issue. How are you trying to enter Download Mode?
Click to expand...
Click to collapse
I am still with the Samsung original
I wanted to try the overcome ROM see if the lag disapears.
I am stuck in the first step when I need to flash CWR using Odin. I can't get into the download menu
josibarns said:
I am still with the Samsung original
I wanted to try the overcome ROM see if the lag disapears.
I am stuck in the first step when I need to flash CWR using Odin. I can't get into the download menu
Click to expand...
Click to collapse
I see. The Overcome thread also has the CWM Recovery as a .zip file which is flashable through Stock Recovery (same procedure as flashing Root). You just put the file in your internal SDcard and flash away. If you still have doubts, read a little bit here, as I'm sure that will clear any doubts you might have.
josibarns said:
I find my newly purchased tab 8.9 very laggy with the stock TouchWiz
Before returning it I wanted ti try the Overcome rom to see if it can get any smoother.
I carefully followed there instructions but I am unable to go past the downloading droid. once I validate with the right button volume, the tablet simply reboots.
Does anyone else have this issue?
Click to expand...
Click to collapse
u have to press the power and the left-volume button for about 15sec
nirogu325 said:
I see. The Overcome thread also has the CWM Recovery as a .zip file which is flashable through Stock Recovery (same procedure as flashing Root). You just put the file in your internal SDcard and flash away. If you still have doubts, read a little bit here, as I'm sure that will clear any doubts you might have.
Click to expand...
Click to collapse
Perfect it worked! And I was also able to install the Overcome ROM It seems to be more battery hungry and a bit faster
DonKomposto said:
u have to press the power and the left-volume button for about 15sec
Click to expand...
Click to collapse
Yes I have done that and I get to the menu with the droid blinking with "downloading" written under it. The issues is when I validate instead of showing the dowload menue it simply reboots...
josibarns said:
Perfect it worked! And I was also able to install the Overcome ROM It seems to be more battery hungry and a bit faster.
Click to expand...
Click to collapse
Don't expect perfection from a port, ever (port = a ROM that's not native to the device). The motley kernel, along with UV can help you in the battery department.
Sent from my GT-P7310
Sorry to comeback to it but after having flashed a couple or ROM with CWM I want to come back to the stock rom using ODIN and I cannot enter the dowload menu.
My system right now is a stock ROM us retail P7310UEKHA flashed with CWM and CWM and I want to install a 3.2 stock ROM using ODIN.
The way I try to access the download menu is
1. Turn off the tab
2. wait 30 sec
3. restart with the down volume pressed
4. when the reaching the menu between recovery and dowloading. Select dowloading with the down volume button and validate with the up volume button.
Result: a black screen for 3 seconds and then the tab reboots
josibarns said:
Sorry to comeback to it but after having flashed a couple or ROM with CWM I want to come back to the stock rom using ODIN and I cannot enter the dowload menu.
My system right now is a stock ROM us retail P7310UEKHA flashed with CWM and CWM and I want to install a 3.2 stock ROM using ODIN.
The way I try to access the download menu is
1. Turn off the tab
2. wait 30 sec
3. restart with the down volume pressed
4. when the reaching the menu between recovery and dowloading. Select dowloading with the down volume button and validate with the up volume button.
Result: a black screen for 3 seconds and then the tab reboots
Click to expand...
Click to collapse
A corrupt bootloader that may be. Reflash KHA (CWM version alterbridge posted) to see if it solves it.
Sent from my SGH-T959.
Just to precise this issue was present out of the box when I got it from best buy...
josibarns said:
Just to precise this issue was present out of the box when I got it from best buy...
Click to expand...
Click to collapse
flash a stock bootloader and a stock recovery using nvflash, im in a hurry now and dont have time to explain, use google, you will find all the info in the tab 10.1 forum.
lupu666ro said:
flash a stock bootloader and a stock recovery using nvflash, im in a hurry now and dont have time to explain, use google, you will find all the info in the tab 10.1 forum.
Click to expand...
Click to collapse
Thanks lupu666ro. I've tried installing stock Rom with CMW but nothing works. I have found very sparse info about nvflash. It looks like the solution but I'm a bit wary about tring this without a instructions. Could give me more info or point me to a tutorial
Thanks!
Still no luck...
So I have tried reflashing the stock US retail ROM and ran the EULA3 OTA update over it. I can't seem to figure this out.
The OTA update entered the download mode for a few seconds during the update so I am wondering if I don't simply have a locked bootloader.
I have made a video to show the problem: http://youtu.be/b09-x31ldbs
josibarns said:
So I have tried reflashing the stock US retail ROM and ran the EULA3 OTA update over it. I can't seem to figure this out.
The OTA update entered the download mode for a few seconds during the update so I am wondering if I don't simply have a locked bootloader.
I have made a video to show the problem: http://youtu.be/b09-x31ldbs
Click to expand...
Click to collapse
here is a tutorial on how to use nvflash, this will repair you tablet. http://forum.xda-developers.com/showthread.php?t=1130574
On the download warning screen you are hitting volume down, not up. Volume up is the button closest to the headphone jack..
josibarns said:
So I have tried reflashing the stock US retail ROM and ran the EULA3 OTA update over it. I can't seem to figure this out.
The OTA update entered the download mode for a few seconds during the update so I am wondering if I don't simply have a locked bootloader.
I have made a video to show the problem: http://youtu.be/b09-x31ldbs
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I957 using XDA App
neubauej said:
On the download warning screen you are hitting volume down, not up. Volume up is the button closest to the headphone jack..
Click to expand...
Click to collapse
Ok I am really ashamed on this one, you were right I've been hitting the wrong button for all my attempts
Thanks a lot neubauej!!!!!
Lol, no problem, glad it was simple.
Sent from my SAMSUNG-SGH-I777 using XDA App
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.
OK... so a couple of days ago a friend of mine screwd my phone when he tried to install clockwork recovery without rooting, I was stuck at Samsung logo, no recovery, only download mode... so today after going through tons of threads so I could use Odin with ace on win8.. I finnaly managed to un**** it... so I could re**** it again... so I followed this thread after reviving the phone. http://forum.xda-developers.com/showthread.php?t=1034145
After rooting and instaling cw, I tried to install a ROM on it, namely nightly cm (found somewhere here: http://forum.xda-developers.com/showthread.php?t=2188679)... I got a status 7 error cause of the assertion, which in removed, after successfully installing the ROM (or so recovery mode said) I tried reboting and it no longer turned on. Doesn't seem to charge and it won't boot...
The only things I can think of that i did wrong were:
Having under 50% battery life
Not removing sim card
PS: also before installing ROM I cleared caches and reset to fact. Settings
Any ideas on how to fix this? If not, what did I do wrong here?
EDIT: ok so i think i figured out what i did, i wanted to download this rom: http://forum.xda-developers.com/showthread.php?t=2199575 ... i went to the "external webstie" to download, and i think i downloaded this rom "android cm_skate-userdebug-cm-10.2 (stable)" which it seems its not for my phone :S ...
Is it possible to boot into download mode now? would a usb jig work? something like this: http://forum.xda-developers.com/showpost.php?p=8822843&postcount=1
Or is it a lost cause?
Thanks...
PS: oh god, to think i removed the assertion that was saving my phone... ahh **facepalm** , why didnt i read the damn assertion...
wrong man said:
Is it possible to boot into download mode now? would a usb jig work? something like this: http://forum.xda-developers.com/showpost.php?p=8822843&postcount=1
Or is it a lost cause?
Click to expand...
Click to collapse
If you want to use stock rom again then flash stock rom via odin through download mode. to get to download mode, press volume down + home + power button at the same time until it shows a small "downloading..." word. For further info, How to upgrade, root & flash Samsung Galaxy Ace S5830
-BRK- said:
If you want to use stock rom again then flash stock rom via odin through download mode. to get to download mode, press volume down + home + power button at the same time until it shows a small "downloading..." word. For further info, How to upgrade, root & flash Samsung Galaxy Ace S5830
Click to expand...
Click to collapse
Thanks for the answer, i know the "shrotcut", as i said in the op i used odin allready, but the big issue is the phone does not react to the power button, idk what the rom i installed did, if its bricked or if its just expecting a different input rather than the supposed power button, in which case the jig should work...
Hello
I was testing an auto reboot app in my tablet (cf-autoroot rooted Tab S2 T815) when it rebooted and it got stuck in download mode but as if I had initiated a new upload. No matter what I do, it doesn't reboot to anything else I have tried flashing various stock roms (even MM) ODIN sees it starts to upload but fails I dont know where to get a .PIT file to try and repartition. I have also tried pressing multiple button combinations to no avail Only by pressing Power and Volume down it instantly reboots to the same screen
Any ideas before I have to resort to official service (and be financially skinned)? All help will be greatly appreciated
Thank you
MarketElf said:
Hello
I was testing an auto reboot app in my tablet (cf-autoroot rooted Tab S2 T815) when it rebooted and it got stuck in download mode but as if I had initiated a new upload. No matter what I do, it doesn't reboot to anything else I have tried flashing various stock roms (even MM) ODIN sees it starts to upload but fails I dont know where to get a .PIT file to try and repartition. I have also tried pressing multiple button combinations to no avail Only by pressing Power and Volume down it instantly reboots to the same screen
Any ideas before I have to resort to official service (and be financially skinned)? All help will be greatly appreciated
Thank you
Click to expand...
Click to collapse
Remove the USB cable. Press and hold the Home, Vol Down and Power buttons for about ten seconds. The tablet should power off.
lewmur said:
Remove the USB cable. Press and hold the Home, Vol Down and Power buttons for about ten seconds. The tablet should power off.
Click to expand...
Click to collapse
It did THANK YOU VERY MUCH
Problem is when I try to power it on, it doesnt boot normally. If I try to reflash a ROM (by pressing Home+Power+Vol) it shuts off (it seems that battery is at or near at 0%?)When I try to charge it, it boots instantly and goes to that screen again Have I bricked it somehow?
Thank you
UPDATE Somehow I managed to get it into "normal" download mode and ODINflash a stock ROM With 4% battery!!!! Anyhow now it seems to work fine When it'll be fully charged I shall make a full control
Any ideas what this incident was? Should I post the incident somewhere for future reference to any who might face the same situation?
Thank you
PS Is, by any chance, there a way to untrip KNOXX counter that I have missed?
MarketElf said:
UPDATE Somehow I managed to get it into "normal" download mode and ODINflash a stock ROM With 4% battery!!!! Anyhow now it seems to work fine When it'll be fully charged I shall make a full control
Any ideas what this incident was? Should I post the incident somewhere for future reference to any who might face the same situation?
Thank you
PS Is, by any chance, there a way to untrip KNOXX counter that I have missed?
Click to expand...
Click to collapse
There is a BIG difference between "autoboot" and "autoroot". The app you tried to install attempted to ROOT your tablet. Had you used the Power, Vol Down and Home buttons BEFORE trying to download what were apparently the WRONG ROMs for your tablet, there might not have been a problem. But there is no telling what the cf-autoroot app did. (Except trip your Knoxx flag.)
If flashing the CORRECT stock ROM didn't restore Knoxx, then nothing will. But if you tell Sansung you "accidentally" entered the download mode and didn't know how to get out of it without attempting to download something, then they might honor your warrantee anyway. Just make sure you tell them you WERE NOT trying to root your tablet or install a custom ROM.
lewmur said:
There is a BIG difference between "autoboot" and "autoroot". The app you tried to install attempted to ROOT your tablet. Had you used the Power, Vol Down and Home buttons BEFORE trying to download what were apparently the WRONG ROMs for your tablet, there might not have been a problem. But there is no telling what the cf-autoroot app did. (Except trip your Knoxx flag.)
If flashing the CORRECT stock ROM didn't restore Knoxx, then nothing will. But if you tell Sansung you "accidentally" entered the download mode and didn't know how to get out of it without attempting to download something, then they might honor your warrantee anyway. Just make sure you tell them you WERE NOT trying to root your tablet or install a custom ROM.
Click to expand...
Click to collapse
No it did not I had installed https://play.google.com/store/apps/details?id=simple.reboot.com Which requires preexisting root And NO I did NOT try the wrong ROMs I might be a noob but NOT THAT much of one
The Download "mode" that this bugger of an app got my S2 in is NOT true download mode after all...
Knox has NOTHING to do with the incident Was tripped when I firstly rooted the tablet some months ago Just asked if there is a way of untripping it that I had missed
Thanks so much for your effort to help, anyway.
PS Tablet now running with rooted MM and everything (but Knox ofc) looks fine
MarketElf said:
No it did not I had installed https://play.google.com/store/apps/details?id=simple.reboot.com Which requires preexisting root And NO I did NOT try the wrong ROMs I might be a noob but NOT THAT much of one
The Download "mode" that this bugger of an app got my S2 in is NOT true download mode after all...
Knox has NOTHING to do with the incident Was tripped when I firstly rooted the tablet some months ago Just asked if there is a way of untripping it that I had missed
Thanks so much for your effort to help, anyway.
PS Tablet now running with rooted MM and everything (but Knox ofc) looks fine
Click to expand...
Click to collapse
Well forgive me for misinterpreting your OP which stated "I was testing an auto reboot app in my tablet (cf-autoroot rooted Tab S2 T815)". That does say "cf-autoroot" doesn't it? My interpretation of that sentence was that the "reboot app" you were "testing" was actually "cf-autoroot". Can you possibly see how someone could make that mistake?
So what actually took place was that you installed an "autoboot" app on your rooted Tab S2, which was rooted via cf-autoroot, and when you tested, using the new autoboot app, it booted to a non-working download mode. When you then tried to flash a legitimate ROM via Odin from this bogus download mode, it simi-bricked you tablet. Is this correct? I have seen this happen when a multi-boot app tries to boot the stock recovery download mode when you have TWRP installed. Stock recovery download mode no longer works once you have flashed TWRP. The Power, Vol-, Home key combination will exit from the non-functional stock download mode.
lewmur said:
Well forgive me for misinterpreting your OP which stated "I was testing an auto reboot app in my tablet (cf-autoroot rooted Tab S2 T815)". That does say "cf-autoroot" doesn't it? My interpretation of that sentence was that the "reboot app" you were "testing" was actually "cf-autoroot". Can you possibly see how someone could make that mistake?
So what actually took place was that you installed an "autoboot" app on your rooted Tab S2, which was rooted via cf-autoroot, and when you tested, using the new autoboot app, it booted to a non-working download mode. When you then tried to flash a legitimate ROM via Odin from this bogus download mode, it simi-bricked you tablet. Is this correct? I have seen this happen when a multi-boot app tries to boot the stock recovery download mode when you have TWRP installed. Stock recovery download mode no longer works once you have flashed TWRP. The Power, Vol-, Home key combination will exit from the non-functional stock download mode.
Click to expand...
Click to collapse
Well "cf-autoroot rooted Tab S2 T815" was in brackets and AFTER "my tablet" wasnt it? Anyhow, I can understand misreading, no worries
Pretty much what you describe, yes. Differences: A. I had never installed TWRP B. Still dont know how exactly I managed to get it to "normal" download mode! I had managed to shut it down with the button combo you suggested only to find out that it was almost out of battery Trying to find a way to charge it, it started rebooting even after pressing "your button combo" In the effort to stop that I got in "normal" dnload mode again Without losing a second flashed the first stock ROM I've found on my HD and, voila, it was up and running After I had it charged I flashed MM(it's blazing fast Way faster than Lolli) and rooted it with cf-autoroot Everything seems to go smoothly now
I'd like to come to the bottom of this and post problem and solution to the appropriate thread as I havent found any other references and it might occur to somebody else (that app has over 100K of downloads)
I thank you once more
Most of what I've read was user error.
You obviously selected to boot to download mode from the app.
Nothing wrong with that as that is exactly what it did. Nothing bogus about it.
The problem started when you panicked and ended up half flashing something with a flat battery.
All you really needed to do was hold POWER + VOL DOWN to exit down load mode.
You would have rebooted just fine. Your OS would have still been intact.
You eventually got to 'Real' (as you call it) download mode by pressing the right button combo after at least getting some charge in the device.