yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Q&A, Help & Troubleshooting] elspanish88:
Yeah and that... Forgot to write that :p
[Galaxy S III Q&A, Help & Troubleshooting] k6?:
and you're using the latest triangle away?

maybe post in this thread to find out more..

http://xdaforums.com/showthread.php?t=1494114
[Galaxy S III Q&A, Help & Troubleshooting] kurpter:
Top man, after 2 days of doing it myself, its now sorted. All I was missing was CF-Auto-Root.

:good:
[Galaxy S III Q&A, Help & Troubleshooting] kurpter:
Whats the stock Kernel i should be using?

I have the stock recovery,

My Kernel is = 3.0.31-625388

se.infra@SEP-120 #1

SMP PREEMPT fri nov 30 19:46 KST

2012

If this isnt the correct kernel, where do i get it from and flash it?

Cheers
[Galaxy S III Q&A, Help & Troubleshooting] elspanish88:
If you flashed a stock ROM with Odin and haven't flashed any kernels then your on a stock kernel... From the info you have posted I'd say it is a stock kernel
[Galaxy S III Q&A, Help & Troubleshooting] k6?:
Have you followed this?

http://xdaforums.com/showthread.php?p=27407556
[Galaxy S III Q&A, Help & Troubleshooting] AndroidPlant:
Here's a short tutorial on how.

http://xdaforums.com/showthread.php?t=2219755

Drop a comment and thanks!
[Galaxy S III Q&A, Help & Troubleshooting] k6?:
There's plenty of them already. But thanks for taking the time.
[Galaxy S III Q&A, Help & Troubleshooting] vonniel:
I'm also trying to return to stock, I'm dual booting paranoid Android 3.15 and wanam lite and I was wondering if I would lose all my app data, text messages and what not if I unroot and flash stock rom
[Galaxy S III Q&A, Help & Troubleshooting] k6?:
App data yes. Unless you use titanium backup and reroot.

Sms backup from the playstore can back up and restore your sms no problem.
[Galaxy S III Q&A, Help & Troubleshooting] Glebun:
yes, you will. back the data up. Carbon backup (renamed to Helium) can manage app backups without root
[Galaxy S III Q&A, Help & Troubleshooting] vonniel:
Thank you very much for such a quick reply!

This phone is the very first I root, so I am very afraid to brick it, so sorry to bother you guys but last thing I want is a f*****d phone because I didn't bother to ask a question. Do I need to deactivate dual boot before starting the wo=hole process or is it irrelevant, also the tutorials given above work fine on my phone right?
[Galaxy S III Q&A, Help & Troubleshooting] k6?:
if you flash a stock rom it will also give you a stock kernel.

Read, then read again if unsure.
[Samsung Epic 4G Touch] tangjun188988:
I flashed Shadow God Jellyverse v3.0{GB27} , but it said 'Unfortunately,System UI has stopped' I tried reset , with no help,
[Samsung Epic 4G Touch] graydiggy:
Dirty flash the ROM over itself. Should clear up your issue.
[Samsung Epic 4G Touch] tangjun188988:
But I had flash the' format all.zip'
[Samsung Epic 4G Touch] leaderbuilder:
I think what graydiggy was saying is to just 'reflash' again, without wiping first.
[Samsung Epic 4G Touch] tt281gt:
And if that ^^ doesn't help download ROM again, wipe cache/dalvik , flash ROM.

Sometimes you get a bad download.
[Samsung Epic 4G Touch] tangjun188988:
Thanks . I will try ，next time . Now it's OK , the SYSTEM UI will come back a few minutes after my flashing.
[HTC One X+] Nihilus2010:
Hey Guys,

Currently I'm trying to flash a kernel for my One X+ (Maxwen's BLADE, the latest version), and yet fastboot and ADB seem unable to find my device either when

I have PdaNet installed, and Windows recognizes my device apparently without error as you can see here: hxxp://i.imgur.com/ox7RyPz.jpg. I've also used ADB and fastboot before without issue, no system changes have occurred that I can think of since then.

When connected via USB, with USB debugging and ADB over network enabled, adb devices and fastboot devices simply return nothing.

Please find my current PC configuration and phone setup below:

PC OS: Windows Vista (Don't ask, not my computer)

AOKP Version: 20130331

Kernel Version: Blade 201304100118
[HTC One X+] Nihilus2010:
Also, after reading this thread I attempted to specify vendor ID to see if this would help.

Is this correct? Or even useful?

fastboot -i 0x0bb4 flash boot boot.img
[HTC One X+] TheJokah:
I believe Vista need administration rights to use adb and fastboot. Are you running as admin?
[HTC One X+] Nihilus2010:
Just tried it as admin, no luck :( It is a very odd problem, I've also reinstalled the drivers to no avail.

Could it be related to changing the ROM itself, my previous ROM was the HTC default? Seems unlikely as I suspect it would be a common forum topic if so, but on the computer and the phone the ROM and Kernel are the only things that have changed since I last used ADB and fastboot.
[HTC One X+] TheJokah:
This may sound silly, but did you make sure that USB Debugging was enabled on the device?
[HTC One X+] Nihilus2010:
Heh, yeah it's enabled :D

Just trying to flash it with TWRP now, getting error status 7 on my zip though so guess updater-script is wrong. Can anyone spot the mistake?

Zip is signed, updater-script is in unix format, so pretty sure it's a problem with the script itself?

Anyone got any spare updater-scripts laying around with a kernel part in? :D

*EDIT: The syntax for TWRP I found in a different thread seems to be considerably different :/

http://xdaforums.com/showthread.php?t=641223
[HTC One X+] Nihilus2010:
Possibly the most annoying issue ever, not knowing what the issue was is going to bug me for quite some time. However I popped home, flashed the kernel on my own computer. Worked perfectly, same drivers and all.

I'm going to chalk this up to Vista being temperamental, either that or the USB ports on my girlfriend's PC being a little dodgy. They do tend to chime in with "connect to a USB 2.0 connection for faster speeds!" occasionally, despite being USB 2.0.

Anyway, thanks for trying to help :good:
[HTC One X+] TheJokah:
No problem, Glad you got it worked out! :victory:
[Galaxy S I9000 Q&A, Help & Troubleshooting] Thorston13:
Hello i have a Samsung Galaxy S1 (SGH-T959V), i had the cm-9-20120830 installed.

Yesterday after i tried to turn on the bluetooth the phone shut down and stopped at the Cyanogen Mod logo after rebooting.

I tried to run the recovery just to clear the cache and restore to factory settings but it didn't solved anything, after some time of reading through the forums i came up to a post that said that it could be firmware problem, so i tried to update via the Odin tool

(Odin v1.82_and_512.pit_513.pit_803.pit_files) but it failed and the phone just froze on the download mode page with a bar that said "Downloading" and from there it just turned off itself and now it won't turn on at all, it won't power up, if i try to put to charge no icon is displayed or anything.

Might there be a Fix for this?

Thank you for your time and help.
[Galaxy S I9000 Q&A, Help & Troubleshooting] slow--welder59:
have a read here http://xdaforums.com/showpost.php?p=30415128&postcount=1 if nothing there helps you may need to read here http://xdaforums.com/showthread.php?t=1330491&highlight=usb+jig
[Android Themes] Caldair:
Screenshots:

Galaxy Tab 2 7.0: CM10.1 (for more see here)

Galaxy Tab 2 7.0: SlimBean

Galaxy Tab 2 10.1: CM10.1 (for more see here)

Nexus 10: CM10.1

Nexus 10: AOSP

Asus Transformer TF101: CM10.1
[Android Themes] Caldair:
one more just in case
[Android Themes] i9apps:
Thank you but still getting the same error with Team EOS4 rom (tf101)

http://codepad.org/S3qVlSss
[Android Themes] Caldair:
That's because there aren't patches for Team EOS roms. Right now your choices are either AOSP, CM10.1, or Slim.
[Android Themes] SGH-i200:
"Recent Apps" style?

Maybe I didn't get it right but after patching my CM 10.1 on my Nook Color the "Recent Apps" button still shows the phone style not the tablet one Recent Apps view!? Maybe this should be added to "Known Issues".
[Android Themes] Caldair:
Thank you for the report. :) I guess to be honest I don't really think of this as an "issue" but I guess that you are right. At best it is still a shortcoming in acheiving what you would expect as tabletUI. I will have to see if I can get it to look like in Honeycomb, where it was a column view, pushed to the left of the screen. That is the way that you mean, right?
[Android Themes] Caldair:
[MENTION=1995555]SGH-i200[/MENTION]

I think that I got it all sorted out the way you would like. I will try to include this fix in the auto-patcher the next time I update the tabletUI patches. It does look better this way, thanks for the push!:D
[Android Themes] mateorod:
Awesome work Caldair!
[Android Themes] Didgesteve:
Well done. Thanks for helping us Slimbeaners keep our phones secure.

Do you know what the GsmServiceStateTracker.smali does?

I see this error when I am compiling the latest Slim 4.2.2 build 4 patch.

It still completes the patch, and the patch works with no problems. Some people on the Slim thread have reported problems with Google maps, but as I have maps & network location disabled, I can't say.

Oddly it wasn't there on build 2.5

Anyways, thanks again for all your help in making Slimbean a safe rom.
[Android Themes] Caldair:
Sorry, I don't know anything about that. I saw your post at the auto-patcher main thread as well and I think you have the wrong impression. This thread is meant to be for discussion of the tabletUI mod part of the auto-patcher. Your question would be better in the main thread, and trust me, those guys are way smarter than me anyway.:p
[Android Themes] Caldair:
Updates were just pulled into auto-patcher. ApG users can try the newest patches right now, otherwise you could pull from Mateor/auto-patcher on github or wait for the next auto-patcher release.

Huge thanks to tuxafgmur for all the work he did on streamlining these patches!:good::good:

These changes help reduce the extra load that tabletUI seems to put on the gpu!

Also fixed the 'latest' symlink in the CM patch so you should be able to use multiple auto-patcher mods together with tabletUI (ie. pdroid)

And I changed the appearance of the recent apps panel so it is more similar to the old style tablet recent apps (similar to the pictures I posted a couple posts back), hope you like it!
[Android Themes] LQQKS:
hey mate,

i'm trying to patch this mod into my cm10.1 rom on Xoom MZ601 everest.

i've already seen that someone did it successfully on the Xoom wingray.

but when i try : it fails to extract the build prop

hopefully the attached AP log will tell you something

this is on the most recent version of APG
[Android Themes] Caldair:
From the look of your log I think there is something wrong with your ApG installation.

I have never used ApG, as I don't use windows, so unfortunately I can't really be very helpful with this issue. :o But the patcher really should be working for that rom.

Maybe you could try completely removing ApG and starting fresh, that may help. I hope!
[Android Themes] LQQKS:
OK I will try that when I get home :)

and I've found a patched version that I'm running but I'd like to do it myself as I update CM10.1 frequently :)

Thanks for the help

Edit: working now \o/ I had a bad download of the rom, everything else was sweet :) feels like a complete n00b

You can add Xoom MZ601 Everest to list of confirmed working devices (CM10.1) thanks heaps Caldair for the awesome mod \o/

Sent from my rooted Xoom MZ601

running Elemental CM10.1

using XDA Premium app \o/
[Android Themes] Caldair:
Glad to hear it!

And don't worry we all fall victim to the simplest mistakes. They are never simple until you find the solution, and they are usually the most frustrating to solve!

Thanks for sharing your success:highfive: I will add the Xoom to confirmed devices!
[Android Themes] Caldair:
[MENTION=4241322]i9apps[/MENTION] [MENTION=2660242]rafal.k[/MENTION]

For all you teamEOS users out there I have put together a test build of the Auto-Patcher that will patch your EOS roms for tabletUI!

I made test patches for Asus Transformer tf101. These zips are based on the build dated: 2013-05-05 from http://goo.im/devs/teameos/roms/eos4/nightlies/tf101 and

must be used on that build and only on the tf101

: The top 2 attachments are for the tf101.

I also made test patches for the Motorola Xoom Wingray model. These are based on the build dated 2013-05-04 from http://goo.im/devs/teameos/roms/eos4/nightlies/wingray and

must be used on that build date and only on the Wingray

: The bottom 2 attachments are for the wingray.

I don't have either of these devices to test and there is no EOS rom for the tablets that I do have so be warned:

These are completely UNTESTED! Be sure to download both the update and restore file and have them both on your device before flashing the update.zip in recovery. This way if you have issues like boot loops all you need to do is get back in recovery and flash the restore.zip to have all the original rom files back.

I hope to get some feedback on whether these patches work or not and then I can procede with getting EOS roms supported in the Auto-Patcher for TabletUI. Then EOS users with any device should be able to make these patches for any build!

I anxiously await your feedback:fingers-crossed:

Edit: Well I got my feedback... and it was not good:crying: To make matters worse I have since read in one of the EOS threads that bigrushdog is working on bringing tabletUI back into these roms anyway, so I am just going to leave this for now. You EOS users should have your tabletUI back before you know it anyway!

ATTACHMENTS REMOVED.
[Android Themes] drewski_1:
I tried the Xoom version and as soon as it enters the OS I get a neverending "Unfortunately System UI has stopped"

I click OK and it immediately pops up again.

Let me know if there's something specific you'd like me to try that will help you debug.
[Android Themes] Gatak:
Tried with nightly 112 for TF101. Did not work. System UI kept crashing and I could not use the pad. Had to wipe system and reinstall without this.
[Android Themes] Caldair:
Thanks to you both for testing this! I am sorry that it failed so miserably and you had to wipe and reinstall.

For now I will take a closer look at the patches themselves and the sources. There is definitely more going on in EOS roms than other AOSP/based roms, especially in SystemUI.apk.

Gatak, I would have said your issue could have been caused by the fact that you tried to flash the update over a newer build than the modded files came from, but since drewski_1 had the same exact issue I think the patches are probably not right.

Drewski_1, I am assuming that you did flash the update on a wingray model and that you were running the corresponding build of the rom, dated 2013-05-04. If that is not the case, and you are also using a newer (or older) build, please let me know.

These patches can really screw up when used on different nightly (or weekly or whatever the build frequency is for EOS) builds than they were based on. Devs can change a lot in a week, and these patches contain important core files.

Thanks again to you both, I really want to get EOS working. I see how many downloads there are of these roms from goo.im, just for these 2 devices, so I know a lot of people would benefit from this.
[Android Themes] drewski_1:
Yes, I'm on the 2013-05-04 build.

Flashing the restore Zip worked for me so didn't have to do a full wipe / reinstall.

I don't know if the Kernel would matter, but I'm not on Stock EOS. I'm using the Elemental-X 1.2 Kernel.
[Android Themes] bultras:
Works fine on NOOK Tablet 16GB with CM10.1!

10x
[Android Themes] karipari95:
Awesome mod!

Looks cool on my galaxy grand!

Thanks a lot [MENTION=1449163]Caldair[/MENTION]

Screens-
[Android Themes] Caldair:
FYI: It appears that TabletUI patching is broken for CM10.1 builds after May 30, including RC3 releases.

I will work on fixing the patches this weekend and report back when they're working again.
[Android Themes] Caldair:
Turns out it wasn't just CM that was broken. It was all tabletUI patching.

But lucky for us mateorod swept in and saved the day!!:D

Auto-patcher 2.9.8 is up on github and all is well for us tabletUI users again!! So get patching!:good:
[Android Themes] hanspampel:
Hi caldair, i want to introduce you that your TabletUI dindt work on the newest CM10.1. Tried it for my N10 and the GTab 10.1.

And can you take a look at this ROMs for Nexus 10. They based on AOSP with some strings of CM10.1, but the UI didnt work correctly. I can patch them, and i got the TabletUI, but when i press on the right side to the notifications or the clock etc. i got a SytemUI FC. For patching i must choose CM10, AOSP didtnt work.

Links to the N10 ROMs.

SaberMod

Purity V5.6.1

rasbeanjelly

Thx for your effort.
[Android Themes] Caldair:
I pushed a fix for CM tabletUI just now. It should work for manta. Unfortunately the cost for now at least is the circle battery indicator. It will not work with the tabletUI patch and you just see a grey ring if you activate it. I will try to get it working again when I have some more time.

I took a quick look at the first 2 roms you linked and they seem full of framework modification, and not really that close to aosp or cm. I have tried before to create working patches for rasbeanjelly without success for that reason as well. It would be easier if I had a nexus 10, or if those roms were available for the devices I do have, Galaxy Tab 2's. I might get a chance to take a more in depth look later, but you shouldn't hold your breath!:)
[Android Themes] hanspampel:
Hi caldair

Thx for you effort, but didnt work with my N10. I got SystemUI FCs all the time and didnt see any navbar. Your patch didnt work. I didnt test it with GTab, but i think its the same.
[Android Themes] Caldair:
Thanks.... and Crap! Well that was sweet while it lasted.:silly: Patching works on the 0626 build, but is broken again on today's 0627. I might take a couple days off as there are so many changes going into the framework files of CM. I'm tired of chasing my tail since last friday!:)
[Android Themes] hanspampel:
OK mate. I hope you sorted it out in couple of days. Take your time.;)
[Android Themes] Caldair:
You should be able to patch CM builds based on the latest official sources again as long as you're using the latest Auto-Patcher (v2.9.895). Hopefully it will last a couple of days at least.:p
[Android Themes] hanspampel:
Hi

Have you update your github? I cant see any 2.895. Its still 2.89.
[Android Themes] Caldair:
The patches are updated in my github but not the versioning. Check out Mateor's github, the upstream master:

https://github.com/mateor/auto-patcher

That's where the Auto-Patcher and ApG pull updates from.
[Android Themes] hanspampel:
I was there. but auto-synch doesnt work at the moment. I changed it by myself. Maybe i give him a try today or tomorrow.
[Android Themes] hanspampel:
So after some testing, TabUI works but circle battery shows still 0%. And the MOD didnt work with ehe stable oft CM 10.1.0 in nexus 10. It causes a bootloop. But works with nightly Form 07/02 with same circle error like on GTab 10.1. Maybe i must revert your last commit and test with your last settings for the stable one.
[Android Themes] Caldair:
Could you post the log produced by auto-patcher when you tried to patch the stable CM 10.1.0 build for nexus 10? That may help me see the issue.

And yes, sorry, the circle battery is not working.
[Android Themes] hanspampel:
I'm at work at this moment. But gimme a hour or 2. But i can post that log.
[Android Themes] hanspampel:
Ok mate, here is the log. Hope it helps. Click me
[Android Themes] Caldair:
Aha! Thanks that is very helpful!

The problem is that your stable came a day after the ones that I had seen and based the patch date on. When I am home from work later I will push the dates of the new patches ahead another day to catch Manta and any other stragglers.

If you want you can try to run the auto-patcher with this command:

tabletUI cm 20130403

Which will make it use the correct patch for the stable builds!

Thanks again for the troubleshooting.

EDIT: [MENTION=4373586]hanspampel[/MENTION] - I just checked get.cm/manta and the file there definitely has same the build date as the other stable builds, june 24. I downloaded it to be sure and ran it through the auto-patcher and it patches using the correct patch set, 20130403.

Did you or someone else build that from source on June 25 perhaps, or did you download it somewhere else? I think I will not make any changes to the dates in auto-patcher, unless you can convince me with your answer.

Specifying the date in the auto-patcher command, as I said above, has the same effect as my changing the date of the patch anyway. Hopefully that works for you. :) And I am interested where your build originated.

Thanks again.
[Android Themes] hanspampel:
Hi again

I didnt compile it myself. I download it from "get.cm". When i try to patch the stable, it shows me the date of 06/25. Can you tell me exactly how i can run this with other date. Im not confirm in this.:p
[Android Themes] Caldair:
You are using ApG right?

In ApG use the "Manual Patching" button and then run this in the command line:

(putting in the full path to where the rom.zip is located, and correct file name, if different)

./auto_patcher "/[I][U]PATH TO WHERE YOUR FILE IS[/U][/I]/cm-10.1.0-manta.zip" tabletUI cm 20130403

That is how it is supposed to work anyway. I have actually never used ApG myself.

And, what the heck, I have the files here anyway, so if that doesn't work I'll attach the mods that I made yesterday. But you should try and get it working yourself, in case there is a second stable release for your device or something.

MANTA ONLY TabletUI Mod for CM10.1.0 Stable
[Android Themes] Caldair:
Update:

I pushed a commit earlier today that fixes the Circle Battery on CM nightlies!

Check it out:

For those of you watching on github I didn't advance auto-patcher's version, just the patch version. But as long as you auto update to todays commit before you patch you should be good to go!

[MENTION=4373586]hanspampel[/MENTION]: While I was at it I pushed ahead the new patch date in auto-patcher to 20130627, since that is the actual date where this new patch is effective from anyway. This means you should be able to patch your CM10.1.0 Stable build automatically now in ApG, without any extra work. (provided of course it updates to the latest patches) Better late than never, I hope.:laugh:
[Android Themes] hanspampel:
Hi

So i tried to patch the stable one, but it fails with ApG. It runs all the tim with the latest date. I tried it manually wiht 20130403 and it works. But im not at CM at the moment, so cant test if it works. But it was compiled without any errors. Have no clou if the circle works.

But i hope the newest one works better. Maybe i try it out when its available on ApG. Or i try it by meyself. Saw your changes on git.;) Anyway, thanks for your work.:good:

Edit: Seems to with patching. Changed the stuff from your git and ApG seems to work. Patches the "stable" without errors. But i must test if the circle works. Maybe tomorrow. Thx.
[Android Themes] hanspampel:
So i can confirm that the MOD works now. Stable works and the latest nightly too.
[Android Themes] Caldair:
Just pushed a fix that should stop the "Unfortunately SystemUI has stopped" message that some users were getting just after booting. Big thanks to [MENTION=1972990]fanoush[/MENTION] for tracking this down and suggesting the fix. :good::good:

I wasn't having this issue on my tablet so without him this would probably not have been fixed anytime soon.

Thanks again [MENTION=1972990]fanoush[/MENTION], great job man!:highfive:
[Android Themes] hanspampel:
The problem didnt seemed to solve. Ive heard that with the newest commits the SystemUI still crashes on GTab 10.1. The same was with previous changes.
[Android Themes] Caldair:
OK.:( If you can provide me the logs, both from the Auto-Patcher and logcat of the SystemUI crash I might be able to do something about that.
[Android Themes] hanspampel:
Hi

I only have this logcat for a couple of days and the APG Log from today. But the probs are the same.