yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] Johnatan90:
worked for me

http://xdaforums.com/showthread.php?p=47034652#post47034652

working for me with 4.3.1 cm10.2
[Xperia Tablet Z Q&A, Help & Troubleshooting] Zb134:
Is there any kernel out there that will let me change the black levels using gamma settings.
[MDA, XDA, 1010 Software Upgrading] halfmanhalfmachine:
Hi,

I have a QTek 1010 (ARM) running windows mobile 2003.

I need to put the compact framework 2.0 on it but I cannot get the cabs to install.

I have tried all the cabs in the redistribution package but none work, on install I get an invalid device error.

All of the ARM cabs are ARMV4 and not just ARM, perhaps its just not meant to be....
[MDA, XDA, 1010 Software Upgrading] *Gir*:
Thats alright don't all rush to answer.

We have solved the problem by using the 2003SE Rom insteed which allows use to install and run CF2.0 without any issues so far
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] bejunk:
HEY XDA!

B'CUZ MANY HAD PROBLEM'S WITH CM10.2 (4.3) & SONY'S MEDIA APP'S BY [MENTION=4458293]iiandskater[/MENTION] I REWORKED THEM A BIT.

THANK'S OR BETTER NOT TO MY FRIEND AS HE STRESSED ME TO DO IT :P I THINK ITS WORTH TO SHARE, PEACE.

/// CREDITS: [MENTION=4458293]iiandskater[/MENTION]
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] DeathStroke:
Thanks alot mate, will check soon..

sent from Gotham City
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] *Jonny*:
I not see you hard work

I install latest walkman for cm 10.1 on cm 10.2 and walkman working but without eq by sony, on you port eq by sony is deleted.
[Verizon HTC One (M7)] d11dog11:
Am I missing something or are there no kernals compatible with the Verizon version of this phone. I really want tap to wake but all I see are gsm variant kernals.
[Verizon HTC One (M7)] woznet:
That is correct at this time there are no custom kernels for the Verizon HTC One, this is due to kernel source not being released yet.

I should note that the Vanir AOSP rom in the Originial Development section mentions that it has a custom kernel in the title "[ROM][4.3.1][Nightlies][CUSTOM KERNEL] VanirAOSP", you might want to check into that thread and see if you can get any specifics on the custom kernel they claim to have.

Link - [ROM][4.3.1][Nightlies][CUSTOM KERNEL] VanirAOSP
[Verizon HTC One (M7)] brymaster5000:
A little search goes a long way: http://xdaforums.com/showthread.php?t=2478700

Sent from my Oney Bone.
[Motorola Droid and Milestone Q&A, Help & Troublesh] liquid_b:
Hi,

I have an old droid just sitting there doing nothing since I upgraded a year or so ago.

It has Gingerbread and was fine at the time but sluggish as anything. It works fine and I feel like its being wasted doing nothing.

Now that they announced KitKat and that it can run on lower spec devices, would it be possible to upgrade the Droid?

What I understand is that the Droid has 512MB or ram and at is what KItKat has been designed to run on as its minimum specs, so yea.

Any idea at all anyone?
[Motorola Droid and Milestone Q&A, Help & Troublesh] Eiertschik:
Droid 1 has 256MB RAM...
[Motorola Droid and Milestone Q&A, Help & Troublesh] Erovia:
Imho, the main problem is not the size of ram, but the lack of drivers. The GNex suffers from the same, although it's a more capable hardware, it won't get the official KK because Texas Instruments left the mobile business and there are no proper drivers. As far as I know, the latest driver for the OMAP3 SoC was for ICS, so it pretty outdated.

(There are KK build for the GNex, but because of the lack of proper drivers, it is very buggy.)
[Motorola Droid and Milestone Q&A, Help & Troublesh] liquid_b:
Blast. I was hopping that it could be done.

Also my bad, I had always thought it ran 512Mb.
[Motorola Droid and Milestone Q&A, Help & Troublesh] panther90:
OG

Love the OG droid.
[Motorola Droid and Milestone Q&A, Help & Troublesh] MrObvious:
Even the Droid 3, which has 512MB of RAM, is stuck on GB. It's a TI based chipset (OMAP4430), and the camera is closed source so that's why they haven't really been able to get a good healthy solid upgrade to newer 4.x versions. The sad part is Google has access to source code buying Motorola, they would have drivers they could build for ROMs and such. Nope, not happening.
[Motorola Droid and Milestone Q&A, Help & Troublesh] Erovia:
Google has only Motorola's source codes. The drivers are the property of the manufacturers. For example, the chipset driver is the property of TI, so Google has nothing to do with that.
[Motorola Droid and Milestone Q&A, Help & Troublesh] !blackram:
Goooood Times !

I love to see a new rom for my dear milestone, however unfortunately I have to admit that his era has long passed, and the hardware can not handle any more ... despite being even better than very low-end cell phone sold today.
[Android Q&A, Help & Troubleshooting] kid evo:
sup guys i have a question i sent back my phone to sprint it was rooted and it had an unlocked bootloader i got a replacement from the sprint store.. the guys over at the store took it. i uninstalled the root using the SU app in the setting full unroot.. what will happen the bootloader is still unlocked.. i got the new one.. will it be a problem will i walk ?? or will it come back to me.. can someone give me an answer please thanks...
[Android Q&A, Help & Troubleshooting] -fluffy-:
no u wont be blaimed just say u got it like that htc has sent many phone out with unlocked bootloader
[Android Q&A, Help & Troubleshooting] kid evo:
But i forgot to mention i never went back to stock rom it had a costum rom viper4g. i'v just removed the root and SU in the app draw.. i was having problems installing the RUU.. so i took it back to a guy i know at the sprint store they didnt even checked it out he just swap it out for me and orded me another one it came in 2 days i gave him mine and now i got the replacement phone.. will i have a problem when they get it at sprint and check it..o and i have the insurance they offer a walk in at any repair center
[Android Q&A, Help & Troubleshooting] -fluffy-:
yes if they found out that u have custom rom on the phone u wont have any warrenty anymore then they will claim the ammount off money from u

so lets hope they wont check it
[Android Q&A, Help & Troubleshooting] kid evo:
WOW.. i hope they dont check thanks for the response..
[G2 Q&A, Help & Troubleshooting] Suprash:
Hi,

I would like to know if someone already experienced this kind of bug.

Whenever I try to wipe data or cache with TWRP or CWM Recovery, first step (wiping data) goes ok, then it totaly freezes at the second step, and if I hard reboot the phone, none of the data has been wiped away.

Any help would be grateful, thank you. :victory:
[G2 Q&A, Help & Troubleshooting] tdevaughn:
Let it run..... it takes 10 to 15 minutes to complete.
[G2 Q&A, Help & Troubleshooting] x714x:
+1 or go into settings and change it to rm -rf and it will be a lot quicker.
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] IReadYourEmail:
I was wondering if anyone else was having this issue. When I create a folder in the app drawer and add apps to it,

1. I cant add any more apps to the folder once I have added the apps for the first time and

2. when I reboot the phone, the folder is empty.

I have not rooted my device and had my first one replaced because of some bad pixels and I did not test the other one.

Thanks
[Android Software/Hacking General [Developers Only]] dazza9075:
Kobo

Arc, Arc 7, Arc 7HD and Arc 10HD​

With the release of not 1 but 3 new devices from Kobo and no specific device forum I thought it time we consolidated any and all root / development available information on them under one roof. All credit for others work will be acknowledged if known.

If anyone has any info they feel should be added please post it and ill add it

The following devices and development status are list below

Kobo Arc - Root + recovery (POSSIBLE PROBLEM WITH NEW SYSTEM UPDATE, Arctic may no longer work)

Kobo Arc 7 - Root

Kobo Arc 7HD - Root + recovery

Kobo Arc 10HD - Root + recovery

Please support development on these projects, sign up to XDA and join in, we need all the help that we can get!​
[Android Software/Hacking General [Developers Only]] dazza9075:
Kobo Arc

Root

Enable unknown sources In security options

Download arctic.apk to your tablet from http://zhuoweizhang.net/Arctic.apk and install, it will do the rest and install Chainfires SU

Enjoy your root access

Please note, the Arctic patch for the original arc may no longer work after a recent system update, possible solution would be to use fiddler to check what response the device receives to with the update, then hardreset device, connect to an access point directed to a proxy with fiddler running and change the response it gets, going to be a pure pain in the bum but it should work, ill maybe add that info later. Or work on a way to flash a ROM from stock recovery....

Credit to

zhuowei @ http://zhuoweizhang.net/ for Arctic.apk

Chainfire for SU

Recovery Mod

Root needed first!

And something like ROM Toolbox for all the various apps needed

Install the android SDK on your computer, you will need to add the google usb drivers, you will find them in the "extras"

Enable usb debug on the arc and install the generic google adb usb drivers

Plug in the device and let it install drivers, it WILL fail one device, manually install drivers for the failed "arc" device that's highlighted with an error, click on it and update the driver, browse, let me pick my own, show all devices, click next and have disc. Click browse and navigate to your android SDK>extras>google USB driver, for the correct drivers, select "ADB interface"

Delete or rename the file on the device located at /etc/install-recover.sh this will make the custom recovery persistent

Copy the recovery.img to the SDCard, either by using drag and drop in windows ( to root of "internal storage") or by adb push "adb push recovery.img /sdcard/

The next job is to open up a command window on your computer and navigate to adb folder, SDK>platform-tools. Type the following exactly, even better copy and paste them!

adb shell

su

cat /sdcard/recovery.img > /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery

exit adb shell (ctrl+C) and type

adb reboot recovery

and bobs your uncle, one happy new recovery

Original ROM files

recovery Recovery

xloader Xloader

system System

misc Misc

logos Logos

crypto Crypto

cache Cache

bootlogo Bootlogo

bootloader Bootloader

boot Boot

efs Efs

Custom ROM files

Credit to

Me for recovery mod
[Android Software/Hacking General [Developers Only]] dazza9075:
Kobo Arc 7

Root

Fully setup device

Download impactor on PC from http://www.cydiaimpactor.com/

Download android SDK on PC, from http://developer.android.com/sdk/index.html

Run SDK manager and acquire the google USB drivers

Enable dev mode on device by going to settings, about kobo, and tap build number 7 times

Enable USB debug mode in developer options

Enable unknown sources in security options

Plug in device and let it install a USB composite device and a arc 7hd drive, it will fail on the third, go to device manager, and manually install drivers for the "arc" device that's highlighted with an error.

Click on it and update the driver, browse, let me pick my own, show all devices, click next, have disc. click browse and navigate to your android SDK>extras>google usb driver\android_winusb.inf, for the correct drivers, select ADB interface

Run the impactor program downloaded earlier, once loaded, click on start

Check your device screen, you should see an error message, click on decline then decline again and finally decline again, (not sure that makes any difference)

Go to the market place and download SU by Chainfire

EDIT: Impactor was updated which will now make the above work

Credit to

http://www.cydiaimpactor.com/ for the rooting tool

Chainfire for SU

howlinwolf430 for trying the unlock with the new impactor available above

Recovery Mod

howlinwolf430 has a working Recovery img up and running, tests continue but we look forward to seeing this soon!
[Android Software/Hacking General [Developers Only]] dazza9075:
Kobo Arc 7HD

Root

Fully setup device

Download impactor on PC from http://www.cydiaimpactor.com/

Download android SDK on PC, from http://developer.android.com/sdk/index.html

Run SDK manager and acquire the google USB drivers

Enable dev mode on device by going to settings, about kobo, and tap build number 7 times

Enable USB debug mode in developer options

Enable unknown sources in security options

Plug in device and let it install a USB composite device and a arc 7hd drive, it will fail on the third, go to device manager, and manually install drivers for the "arc" device that's highlighted with an error.

Click on it and update the driver, browse, let me pick my own, show all devices, click next, have disc. click browse and navigate to your android SDK>extras>google usb driver, for the correct drivers, select ADB interface

Run the impactor program downloaded earlier, once loaded, click on start

Check your device screen, you should see an error message, click on decline then decline again and finally decline again, (not sure that makes any difference)

Go to the market place and download SU by Chainfire

Credit to

http://www.cydiaimpactor.com/ for the rooting tool

Chainfire for SU

Recovery Mod

Ensure SU is working and you can get SU access with adb shell

download the recovery.img attached in to your adb folder

with the device connected to computer type the following

adb push recovery.img /sdcard/

adb shell

su

dd if=/sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS

ctrl-c

adb reboot recovery

Make sure you allow recovery to make changes when prompted or it will automatically revert to stock recovery

Kobo 7HD notes

Fastboot and Bootloader modes are

ONLY

available via

adb/fastboot

commands, there are

NO

hardware button combos.

adb reboot bootloader / fastboot reboot-bootloader

adb reboot recovery / fastboot reboot recovery

Recovery can be accessed by turning off the device, holding down "VOL DOWN" and turning on, keep VOL DOWN pressed until booted

APX mode can be accessed by plugging in a USB cable connected to a computer, turning off the device, holding down "VOL UP" and turning on, keep VOL UP pressed until booted, note that the screen remains BLACK and as far as I have worked out it is completely useless without certain files we do not have access to.
[Android Software/Hacking General [Developers Only]] dazza9075:
Kobo Arc 10HD

Root

Fully setup device

Download impactor on PC from http://www.cydiaimpactor.com/

Download android SDK on PC, from http://developer.android.com/sdk/index.html

Run SDK manager and acquire the google USB drivers

Enable dev mode on device by going to settings, about kobo, and tap build number 7 times

Enable USB debug mode in developer options

Enable unknown sources in security options

Plug in device and let it install a USB composite device and a arc 7hd drive, it will fail on the third, go to device manager, and manually install drivers for the "arc" device that's highlighted with an error.

Click on it and update the driver, browse, let me pick my own, show all devices, click next, have disc. click browse and navigate to your android SDK>extras>google usb driver, for the correct drivers, select ADB interface

Run the impactor program downloaded earlier, once loaded, click on start

Check your device screen, you should see an error message, click on decline then decline again and finally decline again, (not sure that makes any difference)

Go to the market place and download SU by Chainfire

http://www.cydiaimpactor.com/ for the rooting tool

Chainfire for SU

Recovery Mod

Ensure SU is working and you can get SU access with adb shell

download the recovery.img attached in to your adb folder

with the device connected to computer type the following

adb push recovery.img /sdcard/

adb shell

su

dd if=/sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS

ctrl-c

adb reboot recovery

Make sure you allow recovery to make changes when prompted or it will automatically revert to stock recovery

Kobo 10HD notes

Fastboot and Bootloader modes are

ONLY

available via

adb/fastboot

commands, there are

NO

hardware button combos.

adb reboot bootloader / fastboot reboot-bootloader

adb reboot recovery / fastboot reboot recovery

Recovery can be accessed by turning off the device, holding down "VOL DOWN" and turning on, keep VOL DOWN pressed until booted

APX mode can be accessed by plugging in a USB cable connected to a computer, turning off the device, holding down "VOL UP" and turning on, keep VOL UP pressed until booted, note that the screen remains BLACK and as far as I have worked out it is completely useless without certain files we do not have access to.

EDIT: 16th Feb 2014

Arc 10HD received an OTA update "update-ota832-ota932.zip" around the 10th of Feb. Initial look in to this suggests not only are there some system updates the but the bootloader is updated too, its only about 17MB
[Android Software/Hacking General [Developers Only]] dazza9075:
Edit 6

10HD received a OTA update

Edit 5

thanks to howlinwolf430 Arc 7 now has root, I need to confirm this and the method but I believe the new impactor has added another vulnerability that allows ROOT Thus the guide for the 7HD and the 7 is the same

Edit 4

Recovery img is now complete for the Arc 10HD and 7HD! There are some small configuration changes needed to fix some mounting issues but it backs up and restores just fine

Edit 3

Source code now available for all arcs, git for everything available https://github.com/dazza9075

Recovery Roms for Arc 7HD and 10HD almost complete, just testing to see if it restores correctly

Edit 2

Please note, the Arctic patch for the original arc may no longer work after a recent update

Bootloaders on the 7HD and 10HD appear to be unlocked.

Edit 1

Development on the Arc 7 has stagnated and I no longer have one to directly play with although I do have access if need be.
[Android Software/Hacking General [Developers Only]] dazza9075:
Support needed!

Hi everyone, if your reading this and have some experience in building custom ROMs for

unsupported

devices and wish to give us a guiding hand please jump on board and help where you can. We currently have working custom recovery's on all devices ( Arc 7 needing a little bit of testing ) but we are needing some support for the next steps!

Many thanks!
[Android Software/Hacking General [Developers Only]] kayge:
Arctic,apk

I have ordered a Kobo Arc online. Any idea if the Arctic.apk does or does not work on them with the system update. Just looking for confirmation
[Android Software/Hacking General [Developers Only]] Ipse_Tase:
Nice work...I hope it won't remain an isolated effort

[MENTION=547180]dazza9075[/MENTION]: I just ordered the Arc 10HD - can I safely update the software once I get it and root it AFTER? I didn't see any notes indicating otherwise, but I know from my other Android devices that usually the root/recovery methods are tied to a specific version.

Note I don't even know yet if it will require an update - I'm super-new to the Kobo ecosystem.

BTW: thanks for the work done - I never use an Android phone/tablet/media device that does not have root access and a recovery mechanism to save the day.
[Android Software/Hacking General [Developers Only]] dazza9075:
after the most recent and probably last system update it is disabled. I stopped my arc from updating so cant confirm without a full reset but the original author of the arctic apk has said it no longer works, I cant see any reason for him to lie.

ok, Kobo will do a system update as soon as you turn the thing on, you cant even get around that (although some fiddling with fiddler might fool it if we can ID what is going on). however, to date there hasn't been an update that disables it. and if there was we can simply flash my stock ROMs which already have root and are flashable.

what we are lacking however is a custom ROM for any of the arcs. More importantly than that we are lacking people to help us!
[Android Software/Hacking General [Developers Only]] Ipse_Tase:
Weird, I could not install the ADB drivers from the SDK (Win 7 64-bit Enterprise). Had to use my trusted Nexus Root Toolkit and worked fine with that.

I'm liking it so far....appreciate your work to document the rooting procedure.

Let's hope development will pick up at some point, it's a good device (I have the ARC 10HD - got it on sale + coupon in Canada).
[Android Software/Hacking General [Developers Only]] Ipse_Tase:
Been meaning to ask: have any of you guys found a good screen protector for the Arc 10HD?

I realize this is off topic (sorry OP) but I feel there is ZERO chances I would get an answer elsewhere than in this thread - the only valuable one on XDA re Kobo.
[Android Software/Hacking General [Developers Only]] dazza9075:
Actually I don't, I have a leather case for mine that acts as a stand and protector,i don't sell them either but I suspect that will change soon
[Android Software/Hacking General [Developers Only]] dazza9075:
Bazaar, I thought they were the same drivers, well I'm glad it worked eventually, if you or anyone else wants to help with dev you could try searching if there are other devices with the same SoC , we are looking for same gpu/CPU combo that already has a working custom ROM.
[Android Software/Hacking General [Developers Only]] Ipse_Tase:
Yep...I am looking in the Transformer TF-701t forums. I'm not on the software side of Hi Tech, so I'll have to do some reading as I am as frustrated as you with the lack of interest in this platform.

BTW: you may want to add to your tutorial that after booting in Recovery for the first time, the user should accept to make boot.img changes - as otherwise all the frequent updates will wipe the recovery you installed. I was too quick to reboot and now I have to push recovery again.

Or if you think this is not safe to make permanent (I did it on every other Android device I own) maybe that should be stated too. People might want to get OTA updates and it is my understanding that with a custom recovery you won't be getting them. Hell, I'm still hoping we will get a stock KitKat at some point.

Thanks...for being the only one that cares :D

PS. From what I read about Netflix (big user....I "cut the cord" a year ago) it seems we need 4.3 for Netflix to run in HD (DRM ****). All I can say is that I don't get HD now - so it seems true.

One good reason to hope for a Kobo upgrade. I am already plagued with Ouya being stuck at 4.1.2
[Android Software/Hacking General [Developers Only]] JoshReuben:
Very surprised at the pack of interest in the Kobo tablets, given the impressive combination of awesome specs and very low price. Have an Arc 7 32gb and an Arc 7 16gb in the family and gathering my forces to root em both.

I've read the forum but am a bit thick. Bottomline, are the root guides here conformed working on the latest updates since November 2013?
[Android Software/Hacking General [Developers Only]] Ipse_Tase:
I just rooted my ARC 10HD 2 days ago, AFTER it got the last update (something one cannot prevent when setting it up for the first time).
[Android Software/Hacking General [Developers Only]] dazza9075:
Should work fine, they updated the bootloader a couple of days ago on the 10HD but nothing appears to have changed, some system updates, some app updates, not a lot else from first impression

it updated the other day. ive been away for a bit so cant be sure when.