yashsingh1/xdaforums huggingface dataset:
[Microsoft Surface] theonegeneral:
Thanks for the reply :)

Unfortunately, the store which I bought it from won't take it back. They can give me a 30% refund At Best since they can't re-sell it anymore, because I already opened and started up the product (this also classifies under ''customer mistakes'').

Hopefully someone knows! Currently looking for stores who can fix surfaces, but it's still relatively unknown here it seems.
[Microsoft Surface] GoodDayToDie:
Um... just checking, is it a Pro or an RT? There is no such thing as a "Windows Pro RT 8.0". That wouldn't even describe any kind of device!

Windows is an operating system family.

Windows RT is an operating system product line that runs on ARM tablets.

Windows RT 8.0 is the release of the Windows RT line that was present on the original Surface RT from Microsoft.

Windows 8[.0] is an operating system that runs on x86 and x64 CPUs powering desktop, laptops, tablets, and so on.

Windows 8.0 Pro is a specific edition of Windows 8.

There is no Pro edition of Windows RT.

Surface is a line of tablets from Microsoft.

Surface RT is an ARM tablet by Microsoft that comes with Windows RT 8.0 and is upgradable to Windows RT 8.1.

Surface Pro is an x64 tablet by Microsoft that comes with Windows 8 Pro and is upgradable to Windows 8.1 Pro.

There are a bunch of other things, but hopefully you can now speak more clearly about the problem...

Anyhow. So, you have a Surface. It's either RT or Pro. It's bootlooping. I feel compelled to point out at this time that XDA is *NOT* a product support forum! Unless what happened was the result of applying some hack you found on here, this is probably not the best place to look for help. There are actual support forums, not to mention real tech support options where you can talk to people who have the ability to do things like issue warranty replacements. That is where you should be. But, with that said...

First of all, unless consumer protection laws are *way* weaker in the Netherlands than the rest of Europe, you should be covered. One day would fall under lemon laws even in the US, I think.

Second, considering that you tried putting the ISO files on the flask drive you talk about using, I'm skeptical that you have "applied them both in a good way" as that is never, so far as I'm aware, the correct way to do it. For example, you may have neglected to make the drive bootable.

Third, have you tried connecting a keyboard (via USB) and using that to access the recovery options? Holding the volume buttons *should* work (although I forget exactly which ones you hold for which effect) but it's possibly work trying a keyboard as well/instead. The Touch or Type Cover keyboards would not work here; the EFI doesn't have drivers for them (only for USB, which they do not use).
[HTC Desire C] tekken 2:
I download some theme,when I trying to install it says"This theme was improperly compiled and cannot be applied"
[HTC Desire C] Quasar:
Change DPI to 158. It looks good, and all themes will work also then. Use the LCD density modder pro app.
[HTC Desire C] aashay960:
Or you can flash the theme fix. Look for it in the CM10 thread.
[HTC Desire C] Quasar:
Here's the link: http://xdaforums.com/showthread.php?t=2050438

Hit thanks! :p
[HTC Desire C] tekken 2:
I will thanks you for again helping me,Now themes are working properly:D
[Sprint Samsung Galaxy S 4 General] deeja303y:
resresize piok here is exactly what i did to make Stock rooted NAE Rom working with DATA and WIFI

(I USED ODIN 3 TO FLASH PHILZ RECOVERY TAR)

FULL WIPE

NEED TO BE ON MK2

flash MK2 STOCK ROOTED

FOR SOME REASON IT ONLY WORKS WHEN I FLASH TRI FORCE ROM...

INSTALL TRI FORCE ROM 5.4 WITH CURRENT PHILZ TOUCH RECOVERY

LET IT BOOT

AS SOON AS IT DOES REBOOT INTO RECOVERY

INSTALL NAE ROM...NO WIPE...REBOOT SYSTEM....IT SHOULD GET STUCK AT SPRINT BOOT ANIM....ALL GOOD....NOW....

REBOOT TO DOWNLOAD MODE

FLASH NAE MODEM (FIRMWARE) UNCHECK AUTO REBOOT AND F. RESET

AFTER IT SAYS PASS....REBOOT PHONE USING POWER BUTTON....

SHOULD SAY ANDROID IS UPGRADING ...OPTIMIZING APPS .....ONCE ITS DONE.. UR GOOD

POSTED SCREEN SHOT
[Sprint Samsung Galaxy S 4 General] optimummind:
Which bootloader are you on? MF9, MJA, MK2?
[Sprint Samsung Galaxy S 4 General] deeja303y:
MK2

MK2
[Sprint Samsung Galaxy S 4 General] legasus233:
How can I tell which bootloader I have?
[Sprint Samsung Galaxy S 4 General] optimummind:
You can use an app like Root Checker or Phone Info from the Playstore.
[Sprint Samsung Galaxy S 4 General] SayWhat10:
does this knox void?
[Sprint Samsung Galaxy S 4 General] anees02:
You can do that from terminal emulator by entering this command getprop ro.bootloader
[Sprint Samsung Galaxy S 4 General] xfullmetal17:
Flashing the custom recovery will trip KNOX.
[Sprint Samsung Galaxy S 4 General] samjam91:
This method worked for me on the MF9 bootloader.

Wifi and data (LTE at least) are working.

Only thing is that I'm constantly getting a "Sprint ID stopped working" popup notification.

Update:

Apparently factory reset/wipe data breaks wifi
[Sprint Samsung Galaxy S 4 General] SayWhat10:
That's not good
[Sprint Samsung Galaxy S 4 General] doby-nut:
samjam keep us posted. Were you able to get wifi restored?

Data connection still holding?
[Sprint Samsung Galaxy S 4 General] samjam91:
Turns out wifi wasn't working because my router was on the fritz. I kept getting force closes using the NAE rom from Uknownforce after I restored with TiBu, so I had to flash back to MK2, at least until a newer NAE rom comes out. Still on NAE firmware with MF9 bootloader. Everything is working fine for now.
[Sprint Samsung Galaxy S 4 General] kujanme:
dumb question

Anyway I can tell what my current bootloader is ? I am lost and I realize this is a dumb q just lost my wifi is not working i see all these fixes but of course lost ...
[Sprint Samsung Galaxy S 4 General] xfullmetal17:
Either in an adb shell or terminal emulator, type this:

getprop ro.bootloader

It should then return your current bootloader. If it's MJA/MK2/NAE you CANNOT downgrade it, because of KNOX.
[Windows RT General] Penguini:
My friend upgraded my surface to 8.1.....

So I decided to downgrade my Surface RT to 8.0.

And I found 8.0 Recovery file for Surface.

However, my Surface is KO-KR version, but can I use this EN_GB version ?

And, if it won't work, where can I download it ?

Plz help me. Cuz as I'm a programmer, I have to use SharpDevelop, PuTTY, Python RIGHT NOW...

Sry for my bad English..
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] rootcid:
Hi. I am new to safestrapping and i rushed into it. Instead of creating a rom slot before flashing gapps, i just backed up the stock slot and flashed gapps onto it. Everything works fine of course, but:

1. can i just restore the backed up data for the slot to get back to stock?

2. should i restore and flash onto a new slot to be safe if possible?

Thanks in advance.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] rootcid:
100 views and no comments? Pretty please :)
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] rootcid:
Wish i could ask in the safestrap thread of the development section :(

I need to know because i want to exchange it for a new one (the screen has light bleed and shop said theyd exchange it so thats good)... but i cant bring this one back before restoring it to a normal state...
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] rootcid:
Maybe if i keep quoting myself ill pass the 10 post limit and be able to write in the safestrap thread!

No but really. I would appreciate some insight soon... question was asked 4 days ago and still no replies... the clock is ticking on that rma.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] rootcid:
Thanks for the help.guys...
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] StAlfonzo:
Why not post in the gapps or safestrap thread? Those get replies all the time. I get my questions answered within a few hours normally. This entire help section of the forums gets almost no traffic, because everyone posts their problems in whatever tutorial thread they are using to update their kindles.

I have been coming to the hdx forums for months now, and I only ever check HDX General, and HDX Android Development. This is my first time in the help section.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] rootcid:
It was the ten post limit, so now I will :)
[G Pad 8.3 General] kyomagi:
If it does, what is the best slimport to use?
[G Pad 8.3 General] astromark:
It works for me, I picked up a cheap cable from Amazon
[G Pad 8.3 General] kyomagi:
how do you deal with the black bars? do you use that one app that overscans?
[G Pad 8.3 General] astromark:
Haven't figured that out yet!

Anyway I am likely to be using the mirroring/streaming features that are starting to come to Chromecast now
[LG Optimus G (International)] faizigenious:
I have a LG OPTIMUS G E975 Korean edition

I have bought a pre-rooted phone from a friend with Jelly Bean 4.1.2 running on it. I want to install a recovery and then a KitKat running custom ROM but I can't install a recovery OR my device's bootloader is locked. As i reboot into recovery I get this error message

"Secure Booting Error

Cause:boot certification verify"
[LG Optimus G (International)] ShazZ94:
install "freegee" from market ,choose a recovery"cmw o twrp" and select mako option,,when it finished you will have bootloader unlocked and recovey installed
[LG Optimus G (International)] yogivin:
hey bro..i followed your method..however i sucessfully installed kitkat custom rom...But mako is a nexus 4 bootloader..so now if m trying to revert back to original Rom..it says phone model E960 and DLL model E975..so now i cant install Original E975 on my cell..m stuck with mako(nexus 4)

...plz help me bro...thanks in advance
[Miscellaneous Android Development] Legojr:
I am currently attempting to port Cyanogenmod as well as Clockworkmod to a device known as the Samsung DoubleTime SGH-I857. It is a very unique end of life handset that I think needs a little hacking attention. So far I have found most of the partitions names and sizes on the device, and I have pulled the boot.img and recovery.img out of a firmware file for it that I found online. I am confident in my skills but I am often running into trouble when it comes to building with Cyanogenmod source. I am currently using the Froyo branch as I believe it might be easier to build with the same version that is currently on the phone. I eventually plan to some how build gingerbread for it but i am trying to build what I can as of right now.

I am making this thread to report progress and hopefully get advice from those who are more experienced than me. Any help or advice is deeply appreciated.
[Miscellaneous Android Development] Legojr:
Update*

I finally got my build enviornment figured out, I chose Gingerbread because Froyo didn't like me for some reason...

I used the mkvendor.sh method as recommended on the Cyanogenmod Wikipage for porting. I looked through all of the files and everthing seems to be correct except the recovery.fstab which is saying that the system, cache, data, etc. partitions are in all sorts of diffrent file systems; and are mounted in places called the same name as them. The sdcard partition seems to be correct and I'm assuming that I need to manually put in the data. You can look at the files below and tell me if I'm on the right track. I cannot locate any recovery boot or misc partitions using shell commands. There were however there were loop and bml partitions, but they did not appear in the mount or df command.
[Miscellaneous Android Development] Legojr:
Update*

I got sick of getting errors regarding my device not existing and random stuff about an HTC ACE. So I plugged the recovery.img from the firmware package into builder.clockworkmod.com and gave it a go. It built sucessfully but I am afraid of the recovery.fstab not being correct.

Upon inspection of sibiling phones most followed a similar pattern or stl## partitions for cache, data and system. Though they all have boot defined as boot and recovery as recovery; both of which with a BML file system. I also noticed the sibilings said their cache, data and systems were ext4 with a 2nd file system of rfs. This is just confusing to me...

I am unsure if I should flash it. I'm confident that the recovery.fstab's recovery and boot partitions are correct but what will happen if I get one of the partitions wrong.

The CWM recovery builder output is here: http://jenkins.cyanogenmod.com/job/recovery/56329/

A sibiling phone example would be: https://github.com/CyanogenMod/android_device_samsung_fascinate/blob/gingerbread/recovery.fstab

Anything other files I am happy to give out.

How I feel about my progress:
[Miscellaneous Android Development] Legojr:
Due to my lack of experience, and fear of hardbricking my new DoubleTime, I will be postponing my developement of the Gingerbread port to the Doubletime. My priority now will be learning as much as possible about the device.

To Do List (In Order)

1. Find correct Odin version for flashing.

2. Create Froyo ROM that will maximize freespace.

3. Create working recovery.

4. Build Gingerbread kernel.

5. Port over Gingerbread.
[Miscellaneous Android Development] Legojr:
I've recently been looking comparitivly at custom ROMs and so far I think the best option might be stock AOSP. I have also been looking into ways to flash onto the phone but ODIN 1.85 doesn't seem to work. It can't be my antivirus as far as I know because I've added firewall exceptions to Odin.

To Do List (in order)

1. Find way to flash things to Doubletime

2. Make Froyo based AOSP

3. Build Gingerbread kernel.

4. Port Gingerbread

(Porting CWM should probably be in there somewhere)
[Miscellaneous Android Development] Teknodad1974:
Progress?

did you give up on this?
[Miscellaneous Android Development] Legojr:
No I haven't but my schedule has not allowed for a lot of time to be dedicated to this. I also am very new to this and I'm taking a lot of baby steps.

The number one problem right now is there doesn't seem to be any way of flashing CWM to the phone as all of the Odin versions/cables/computers I've tried have failed.
[Miscellaneous Android Development] Teknodad1974:
Well no better way to learn than hands on and on your own... Good luck! I have one of these worthless phones laying around to give to my youngest girl 6. It's just sucks it's stick on Froyo 2.2
[Miscellaneous Android Development] Legojr:
I believe I may have a correct recovery.fstab now I'll run this through Clockworkmod Builder now and hopefully get Odin 1.87 to flash it. If at anytime anyone thinks I'm doing something wrong PLEASE TELL ME. I'd rather not have another hardbricked Doubletime.
[Miscellaneous Android Development] Legojr:
Honest to goodness I need some help here I'm trying really hard but I can't seem to get anything right... Odin doesn't seem to work, CWM Builder doesn't even identify the name of the phone, and all of the code available for the Doubletime from Samsung makes almost no sense to me. I do enjoy doing this but I've made almost no progress at all.

As of right now the primary effort needs to be on finding a way to flash CWM onto the Doubletime. The issue being if CWM builder is giving out KitKat level recoveries I doubt the Doubletime could handle it. The only way I can see a reliable CWM img getting built is if we use Cyanogenmod 6, which will require proprietary blobs, and those will be a pain to get since extract-files.sh doesn't seem to be available for the Doubletime as far as I know.

I've started manually finding the blobs by finding files that are similar to those found in the device-vendor-blob.mk of some other Samsung Froyo devices. The link to it is here

If I'm going in the right direction someone please tell me...:crying:
[Miscellaneous Android Development] Legojr:
​

Well it finally feels nice to know what your doing! While going file by file through the phones system directory might do it, I can't deny that I may have absolutely no idea what I'm doing. So with that lovely feeling in my heart I will be finding each of the parts inside of the DoubleTime and will looking at other phones that have those same parts and copy the blobs specific for them over to the github page I made. Anything that's on the DoubleTime but not in the blobs that I copied I'll put in a miscellaneous section in the vendor-blobs.mk file. So far here is what I know we'll need part wise, and what I know part wise.

List o' part we might need (totally could be wrong):

Bluetooth: ???

Wi-Fi: ???

Camera: ???

Sensors: ???

Audio: ???

Graphics: Qualcomm Aderno 205

GSM: ???

GPS: ???

Media: ???

DRM: ???

DSP: ???

USB: ???

​

The chipset is a Qualcomm MSM7230, looking at apps that gather information about the device I've come to the conclusion that the phone is running on an extremely generic Android build and is not even really optimized for the devices hardware. The phone seems to think that it has an ARMv6 processor while in fact it has a v7.

​

That adds to my other phone binary preference. Add anything you thing might be helpful! I'm a total noob at this and I need all the help I can get. :|
[Miscellaneous Android Development] migui0401:
I have this phone and would like a little of hacking on it. Have you gotten anything?
[Miscellaneous Android Development] Legojr:
So far all I got is a plan. Although I do have a recovery.img of CWM 6 from the Clockworkmod builder but the issue is it might not even work. Also as of right now I haven't found a way to flash anything to the DoubleTime. Although I have a theory that Odin on Windows XP might work. If you know anyways of flashing that are universal or something I'm all ears.
[Miscellaneous Android Development] migui0401:
Can you create a flashable zip file for flashing via stock recovery, i mean a recovery which just opens flashing it everytime you need it, there some like this.
[Miscellaneous Android Development] Legojr:
I've heard about that but I'm not sure if a stock recovery can flash a recovery on itself.

Besides a recovery.img that we know will work is needed for that and well... we don't really have one. :(

Being a noob I'm not sure how much is testable before flashing but I believe that those binary files are going to be needed. Do we just need the vendor-blobs.mk file to copy everything in system/lib, system/bin and system/etc directories?
[Miscellaneous Android Development] migui0401:
Search for guide for creating the flashable zip, this is the better way to get a fast recovery working in any device, about the vendor-blobs.mk, i have not tried to create a recovery, so i can't help.
[Miscellaneous Android Development] Legojr:
How much experience at Android hacking do you have?
[Miscellaneous Android Development] migui0401:
I'm not a great here just like the contributors or reconigzed, but I can do something, do you need help?
[Miscellaneous Android Development] Legojr:
Well I'm no expert but we're eventually going to need to find a way to build Gingerbread for the DoubleTime. If you know the basics of a Cyanogenmod build enviornment that would be cool! If you could maybe look for any source code for the DoubleTime that would also be the best! Those are the only things I can think of. I don't really know much...
[Miscellaneous Android Development] migui0401:
I have the stock firmware extracted, the boot.img and recovery.img.
[Miscellaneous Android Development] Legojr:
Awesome sauce! How did you do it?
[Miscellaneous Android Development] migui0401:
Using 7-zip for extracting the tar.md5 firmware and MagicIso for extracting the system.rfs file.
[Miscellaneous Android Development] Legojr:
I assume you got the firmware from a site like Sammobile. I think I have a similar tar.md5 we have to find away to flash it if we want to flash anything in the future.
[Miscellaneous Android Development] migui0401:
There is our problem, this phone has a firmware problem i guess, cause it doesn't flash anything, I've noticed this already.
[Miscellaneous Android Development] Legojr:
There is a way to flash to it. I soft bricked my DoubleTime once and I played dumb to the AT&T store and they flash stock firmware to it.

If I had to make an assumption, I would say they used Odin. I'm just not sure which version, or if they even used the same firmware image as us.
[Miscellaneous Android Development] migui0401:
There is not other way to flash the device, Just kies. This means there is a possibility to flash it! Could you make a research to know which tool they used to flash it?
[Miscellaneous Android Development] Legojr:
I actually can't even get Kies to work unfortunately. I could just walk up and ask them, but I'd doubt they'd tell me. We could also try Hiemdall;it might even be easier.
[Miscellaneous Android Development] migui0401:
I haven't tried it, even seen it. I've always used odin to flash, restore and make money ;) but we don't have anything to lose. And you don't lose anything asking them :laugh:
[Miscellaneous Android Development] Legojr:
First off I'd like to apologize for the time this has been taking but I've taken apart my hard-bricked DoubleTime and I've compiled a list of all of the parts inside:

CPU: Qual MSM7227

Cellular Radio/GPS: Qualcomm RTR6285

Wi-Fi: Atheros 6003G-AC2B

Power Management IC: Samsung MAX8899G

Audio: Audience A1026A0F

Bluetooth: Broadcom BCM2070

Charging IC: Samsung 9280a

eMMC: Samsung KAT007012C

This is different than what some sites have said were inside but this is good because this means the DT is similar to the Samsung Galaxy Ace, so we can look at that code to help build a recovery and we can make a Froyo ROM using some copy-paste magic.
[Miscellaneous Android Development] migui0401:
Hey man! Have you followed this? I still have my DoubleTime. Give me good news :fingers-crossed:
[Miscellaneous Android Development] Oascany:
RIP thread. Man, you did this in 2014.

Is it even worth asking if there's any progress?
[Theme Screenshots and ZIPs] leonardoaraujo:
* Lightning Launcher Home

* Media Utilities

* Zooper Widget

My new creation with zooper and Lightning Launcher Home in portrait and landscape ... enjoy and do not forget click thanks ...:p

​

Download & Instructions:

* Copy the widgets (. zw) to the folder in (mnt/sdcard/ZooperWidget/Templates).

* Copy my backup and restore of Lightning Launcher Home, in (mnt/sdcard/LightningLauncher).

if you can not find the folder, create a backup any, lightning launcher will create the path. (copy to the same folder where the backup is done for you).
[Theme Screenshots and ZIPs] leonardoaraujo:
video demo

http://youtu.be/wLglsSUP_tg

[YOUTUBE]<iframe width="480" height="360" src="//www.youtube.com/embed/wLglsSUP_tg" frameborder="0" allowfullscreen></iframe>[/YOUTUBE]
[Theme Screenshots and ZIPs] alldroid:
wrong forum m8 this is Themes created for themer
[Theme Screenshots and ZIPs] yoda_13:
omg awesome!
[Theme Screenshots and ZIPs] kpirnie:
dorsnt install...

Rockin it from my Blue Chrome Themed Deadly Venom SS 3.0.2 NC1 S4 (team: [MENTION=4631220]Venom0642[/MENTION] [MENTION=2284570]ted77usa[/MENTION] [MENTION=833788]rebel1699[/MENTION]) ~ 20GB free cloud https://copy.com?r=vtiraF
[Theme Screenshots and ZIPs] leonardoaraujo:
I do not know what you you mean by "do not install", this is not to install it is to copy the location indicated by me, I think the problem for some is not familiar with creating zooper widgets, and where is saved widgets .. I guarantee it works perfectly, but things do not miraculously appear on your screen, you have to "call" the widgets ..