yashsingh1/xdaforums huggingface dataset:
[ONE Q&A, Help & Troubleshooting] ConEP:
Hi all new here,

Just got my OnePlus One and updated to cyanaogen 12, while simply using the phone it crashed forcing me to reboot the device, after this the phone would not turn on (asssuming it was hard bricked), luckily following some guides on this forum I was able to get it back up and running again.

I reflashed 12 after and exactly the same thing has happened this time, unfortunately I am unable to unbrick it using the ColorOS method like before, the phone just remains dead and I cannot get it into fast boot mode to rectify the problem.

I am out of luck already? OnePlus seem absolutely useless over support and just plain rude.

EDIT:

I am now able to get into fastboot, but still cannot see it on screen, but fastboot is appearing in device manager as windows ADB, what can I do from here?
[XDA Assist] XDA Visitor:
Device specification

Intex aqua power

Google play services 7.5.74

" " store 5.6.8
[XDA Assist] Razvan:
Hi there,

Do you mean Google Play store auto update? If so, launch Google Play -> Settings -> Auto update, set to "Do Not Auto-update apps".

For more questions please register an account on XDA and ask directly here:

> Android Development and Hacking > Android Q&A, Help & Troubleshooting

Good luck
[XDA Assist] Razvan:
Please see this thread: Delete, Disable, Downgrade and prevent update of Google Play Services [ROOT]

For more questions please register an account on XDA and ask directly here:

> Android Development and Hacking > Android Q&A, Help & Troubleshooting

Good luck

Thread closed
[Galaxy Note 3 Q&A, Help & Troubleshooting] mus7ii:
Background:

So my wifes screen on her Samsung Note 3 is completely smashed, and I believe the digitizer is too as the screen does not respond either. the phone turns on as the buttons has lights and I also get a heptic feedback when I hold down the power button on the phone to turn it on.

I need the the photos, photos were not backed up, not on the SD, and USB Debuggin I believe was off. I tried to connect the phone to 3 different PCs and with different cables, but the pcs do not allow me to see the phones camera folder.

replacing the screen would cost more than the phone cost, and the phone is anyway only being used as a second phone so don't want to shed out that much money.

QUESTION:

I have another Samsung Note 3, so my question was, can I take the screen and digitizer from that one and put it on the broken one and then get the photos and then swap the screen and digitizer back?

Also at work we have a Cellebrite device, but when I tried to extract all the data out of the phone with that, the device asked me to press on "allow this computer" on the phone, but as the screen is broken I can't do this :/

I would really appreciate if anyone can shed some light! thanks guys

Sorry I just realised I should not be posting questions on this forum, I will do it on the other part of the forum, please delete
[Galaxy Note 3 Q&A, Help & Troubleshooting] nijom:
Based on what you say, you have another Note 3. So its easy to replace the Display Assembly (glass+digitizer+frame) and backup the data and again replace them back.

Don't try to remove Glass and Digitizer alone, do it with frame... There are tutorials in Youtube.
[Android Q&A, Help & Troubleshooting] Pranay_619:
Micromax a106 have got the officialy lollipopnd customization is going on. Bt how to solve the nvram error in lollipop roms
[Android Q&A, Help & Troubleshooting] koli84:
Hi, can anyone help me root GOCLEVER Tablet quantum 1010n?

Unfortunately I can not find any information on how to root this model.

The following is the specifications for this tablet:

Manufacturer: GOCLEVER

Model: QUANTUM_1010N

Brand: GOCLEVER

Board: TQ1010N

Device: QUANTUM_1010N

Hardware: mt8127

Product: TQ1010N

Serial: 0123456789ABCDEF

Installed RAM: 1 GB

SoC Model: MediaTek MT8127

Core Architecture: 4x ARM Cortex-A7 @ 1300 MHz

Manufacturing Process: 28 nm

Instruction Set: 32-bit ARMv7

CPU Revision: r0p3

CPU Cores: 4

CPU Clock Range: 598 - 1300 MHz

Screen Resolution: 1024 x 600

GPU Vendor: ARM

GPU Renderer: Mali-450 MP4

GPU Cores: 4

Android Version: 4.4.2 (KitKat)

API Level: 19

Rooted Device: No

Android ID: 99dab8c295a9a5a5

Build ID: GOCLEVER_20141219

Codename: REL

Fingerprint: GOCLEVER/TQ1010N/QUANTUM_1010N:4.4.2/GOCLEVER/1418970964:user/release-keys

ID: GOCLEVER

Incremental: vK302T

Thanx for help!
[Android Q&A, Help & Troubleshooting] trivjednom:
??? help
[Android Q&A, Help & Troubleshooting] MiensnyJesz:
Download Kingo Root from official site. I rooted my Quantum 1010n in 15 seconds with this good app
[Moto X Q&A] mundofeliz:
Hi, First off, I'm super rusty in the custom rom and kernell scene so explain things as easily as you can please.

Now, I have a moto x XT1053, the unlocked variant that they sold on the moto website that came with a net10 chip.

The thing is that I obviously unlocked the bootloader and installed the TWRP recovery. I have (almost) stock android and by that I mean stock with Xposed. I want to know if any of you guys could point me in the right direction, I mean, do I install the OTA update or do I return my phone to stock, and if it's the later, How do I return my phone to stock to do a proper OTA update?

Thanks in advance!
[Moto X Q&A] varxx:
I have the same phone and was in pretty much your situation, including being rusty in flashing roms, kernels and such. I went with the OTA and am very glad I did. My subjective impression is that it's faster and at least as stable.

I thought my phone was close-to-stock, as I had removed some stuff (Xposed, notably) a while back to receive the 4.4.2 OTA. But the new Lollipop OTA wouldn't install, so I took the bull by the horns and flashed stock system.img that I got from Motorola's official firmware repository. I had to request access, and it took about 12 hours for that to come through.

After I downloaded the firmware zip file, I unpacked it and located the system.img file. Search on Google or this forum for the way to flash an img file to your phone, if you've forgotten (as I had). When I have time later today, I'll try to post a link to some clear instructions. I don't want to try to tell you from memory, as this is something I do about once or twice year since I got a Moto X (I tinkered a *whole* lot more when I had an HTC Sensation, but I've decided that if I want to keep my wife, I'd better stop playing with my mobile phone.)

I did this at the advice of a Motorola technician, who said the "most definitive way to return to unroot" was to flash stock system.img for 4.4.4. (I was part of last week's U.S. soak test, so Moto techs were handling questions from people like me who were wrestling with the OTA.)

I had worried that I might lose apps and data by flashing system.img, but I didn't lose a thing. I *did*, though, lose root, and I haven't re-rooted yet. Before I root, I'm waiting for the stock Lollipop 5.1 firmware to be made available on the Motorola repository so that I can have a backup of stock recovery.img.

Meanwhile, I'm enjoying Lollipop, which is like having a new phone.
[Moto X Q&A] mundofeliz:
So, should I:

Delete GravityBox and Xposed

Install the .img file found within the zip for the Moto X dev Edition

Then I'll be able to install the OTA withouth losing data?
[Moto X Q&A] varxx:
The sequence you describe worked for me, assuming "deleting" GravityBox and Xposed is the preferred way of removing them. I can't remember.

The .img file to flash is system.img. You need to know how to get to fast boot/bootloader mode and perform the flash, of course.

If your experience is like mine, after receiving and installing the OTA, you'll have Lollipop without having lost any apps or data.

But you may want to wait for someone whose more up on this procedure to weigh in. When I updated, I proceeded as if I might lose all my apps and data, so I was pleasantly surprised.

BTW, I've since re-rooted, and I haven't had any problems. It's reassuring that the 5.1 ROM image is now available officially from Moto and elsewhere (info courtesy of dtg7: http://xdaforums.com/showpost.php?p=61800775&postcount=11).
[Moto X Q&A] mundofeliz:
I'll do a Nandroid just in case. I'll do the steps above too, since all I've done is unlock bootloader, root and xposed I think this'll work for me. Kinda did only that originally for that reason but that was sooooo long ago. And also because the Moto X is such an amazing phone to begin with, I never saw the need to install other roms. Did you flash just the system.img, the recovery.img or both? I requested the firmware from moto and they approved but in the meantime I also downloaded the original too from filefactory, the exact same firmware I'm running (without modifications I mean.
[Moto X Q&A] varxx:
IIRC, you'll need to do the Nandroid backup before you unroot, right?

I just flashed system.img. Won't that effectively restore the stock recovery? EDIT: According to the readme.txt file bundled in the stock ROM's zip file, recovery.img is flashed separately from system.img, so system.img will *not* restore the stock recovery.

I always feel safer running official firmware from Moto. For one thing, the labeling on the Moto dl site is very explicit, so you know exactly what you're getting.

I agree that the Moto X is a cool enough phone with a stock ROM that there's little need for custom ROMs. I was a flash-aholic when I had an HTC Sensation. But the Moto X pretty much has everything I need. Under KitKat, I did use XPosed to kill the Google search box, but otherwise I've been happy with the stock ROMs.

Oh, and I usually eventually run a custom recovery (TWRP) so I'll have more boot options. But I don't see that as essential now. I find I'm actually using my phone more than tweaking it, which is a change from previous phones.
[Android Q&A, Help & Troubleshooting] HansEberhart:
Hello,

my problem is that i cant enter the recoverymode on my Xperia S Lt26i.

I flashed TWRP first and than Android 5.0.2 to my phone but when i try to instal a new version of my ROM i cant enter the recovery mode.

I have also tryed to flash a new recovery but the phone goes just about 5sec in the fastboot mode and than boots to android.

Any ideas how to fix that problem?

BTW thats my first thread here.:o
[LG Optimus G Pro] QA Bot:
Q&A for Lollipop SUPER LTE V6.2 Port App G4

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for Lollipop SUPER LTE V6.2 Port App G4. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[LG Optimus G Pro] Alibabara:
this rom is great!

Is there any possibility to make the original Smart Cover working? Its not mentioned in the Accessiores Topic...
[Galaxy Note 3 Q&A, Help & Troubleshooting] mus7ii:
Background:

So my wifes screen on her Samsung Note 3 is completely smashed, and I believe the digitizer is too as the screen does not respond either. the phone turns on as the buttons has lights and I also get a heptic feedback when I hold down the power button on the phone to turn it on.

I need the the photos, photos were not backed up, not on the SD, and USB Debuggin I believe was off. I tried to connect the phone to 3 different PCs and with different cables, but the pcs do not allow me to see the phones camera folder.

replacing the screen would cost more than the phone cost, and the phone is anyway only being used as a second phone so don't want to shed out that much money.

QUESTION:

I have another Samsung Note 3, so my question was, can I take the screen and digitizer from that one and put it on the broken one and then get the photos and then swap the screen and digitizer back?

Also at work we have a Cellebrite device, but when I tried to extract all the data out of the phone with that, the device asked me to press on "allow this computer" on the phone, but as the screen is broken I can't do this :/

I would really appreciate if anyone can shed some light! thanks guys
[Galaxy Note 3 Q&A, Help & Troubleshooting] nayanwaghmare:
Yes I believe it is possible to do such a thing as long as you are prepared to spend enough time on this. Look on YouTube and ifixit and the internet for screen replacement videos and guides and instead of replacing with new screen use the guide to put that other good note 3 screen on your broken one, then use the same guide again to disassemble it and then do as you please by either leaving the broken screen phone or putting the broken screen back into the phone. So yes it is possible but be careful and look at guides carefully.
[8125, K-JAM, P4300, MDA Vario ROM Development] mattk_r:
I need some help debugging the kitchen with the touchflo files.

For those who are sent the new kitchen; as you test and find solutions, please post what you did.

I wanted a sperate thread for just these specific objecives.

Here is the objectives:

To retain the ability to build a ROM with or without TouchFlo

To have only ONE seperate camera package that will work in any configuration

To allow portions of the touch software to work seperately should TouchFlo not be installed

I know there are other threads dedicated to debugging the touch software, however this is targeted at just the kitchen integration.

Current issues (v2):

Streaming Media isn't showing up in Programs, won't open.

Speed Dial hasn't been confirmed working or not.

No images for Beam - still need pictures!!!

Windows Live won't connect. Cab fixes issue. Need to find missing entries

Black Keyboard doesn't show numbers across top row. Need to find setting.

The power button will put phone into "standby" mode (basically screen and Wifi off), but won't power down.
[8125, K-JAM, P4300, MDA Vario ROM Development] theloon:
318

I'll be glad to test. I was working on a 318 Kitchen but didn't get very far.
[8125, K-JAM, P4300, MDA Vario ROM Development] theloon:
Too many Duplicate files.

Going back to work on my own kitchen I was much further along than what you have here.

My suggestions:

1) You should at start by deleting duplicate files. I can build a rom and flash it with my kitchen, I can't build with yours w/o getting one dup file error after another.

Please update, I will try to devote some time to your kitchen.

Thanks
[8125, K-JAM, P4300, MDA Vario ROM Development] mattk_r:
NP. I'll update shortly.
[8125, K-JAM, P4300, MDA Vario ROM Development] theloon:
My Files

I deleted dup files in my kitchen but I think I deleted one to many, now I can build, and I can flash using shelltool but it gets stuck at splash screen. Damm where did I go wrong??? I feel like a dumbass!
[8125, K-JAM, P4300, MDA Vario ROM Development] mattk_r:
Hopefully this one will work a bit better. another 30 mintues till it's up.

The boot issue is probably related to the files in the OEMAPPS folder. There are some dll's in there that I found are super sensitive to this build - too bad I wasn't more careful in documenting what they were.
[8125, K-JAM, P4300, MDA Vario ROM Development] theloon:
Documenting.

Started documenting now! Too much going on now not to, especially after my last mistake.
[8125, K-JAM, P4300, MDA Vario ROM Development] theloon:
Test

So have you actualy built and started testing a rom with your kitchen?
[8125, K-JAM, P4300, MDA Vario ROM Development] mattk_r:
I've been doing that for days... but I've tried a number of different combinations and this one seems most promising - though by no means is it ready. 1413 has by far been the easiest, but I still believe the 318 is the best choice.

I'm gonna be out until Monday night, so this is my last attempt for a few days :)
[8125, K-JAM, P4300, MDA Vario ROM Development] Whiterat:
I have 318 with touchflo working.

Keep the original OEMAPPS im afraid, literally just the touchflo components (Audiomanager,etc) and then use recmod on touch.dll and throw it in OEMDRIVERS.

Ive just finished my refined version of the DOPOD touch rom, very well tweaked, it is as close to OEMWizard as it will ever get.

Going to give that a test burn tonight hopefully.

I will post my OEM folder for 318 if you need it.
[8125, K-JAM, P4300, MDA Vario ROM Development] mattk_r:
If you could, it would be much appreciated. Anything to help get closer to a fully functioning setup :)
[8125, K-JAM, P4300, MDA Vario ROM Development] nottoosmart:
Ok, so i tested the oem folder from the reTouched Beta thing. I included everything in there but my problem is that TouchFLO does not function the way it is supposed to. With what you guys are doing, have you verified that TouchFLO even operates correctly?
[8125, K-JAM, P4300, MDA Vario ROM Development] ANTC:
I thnk the touch flo isn't all its cracked up to be..I ran the reTouch wasn't a fan..its not as fast as any rom..only thing I like is the dialer and the cube
[8125, K-JAM, P4300, MDA Vario ROM Development] mattk_r:
I actually have a good feeling about it. I ran the french rom for a couple days - and other than not knowing most of what it said (glad I know the OS and took 2 years of french in high school) I was very pleased with the performance. Specifically the speed at which the screen "rotated", responsiveness, and how quickly the contacts scrolled on the screen was impressive. Enough to keep me interested well into the night :)
[8125, K-JAM, P4300, MDA Vario ROM Development] nottoosmart:
so matt, think you can make a cab from it? the cube that is lol.
[8125, K-JAM, P4300, MDA Vario ROM Development] Whiterat:
Here you go:

Works perfectly but does need some cleaning up to fit your needs (Whiterat and OEMOPERATORS folders)
[8125, K-JAM, P4300, MDA Vario ROM Development] nottoosmart:
So if what you are saying is true I should be able to create cabs from the correct?
[8125, K-JAM, P4300, MDA Vario ROM Development] Whiterat:
AFAIK It wont be possible due to the touch driver not being replacable, you might be able to rename touch.dll and then update the registry entry.
[8125, K-JAM, P4300, MDA Vario ROM Development] hanzieman:
cleaning up

Hello, can i just copy this oem-folder to the kitchen and then remove the whiterat-folder. Which folders do i also need to delete to flash the rom?!
[8125, K-JAM, P4300, MDA Vario ROM Development] masr1979:
For what I see whiterat folder are some reg tweaks that you'll probably use anyways, and as far as folders to remove it might be less of a hassle to simply add the packages that you use that are not there.
[8125, K-JAM, P4300, MDA Vario ROM Development] hanzieman:
cube-package in core2.0n

Hello, i have put the oem package posted in this thread in the core-kitchen for making a core2.0n rom with the cube.

I deleted the duplicate files wich buildrom quoted. After that the rom builds normally but when I flashed it after te boot the rom sticks at the ipl-screen.

Does somebody know how this can happen.

What does this mean: deleting modules (what are modules?)
[8125, K-JAM, P4300, MDA Vario ROM Development] hanzieman:
Cube in 318 rom

Is this the rom where you were able to insert the cube: InGeNeTiCs' 15.2.318 OS v3.5.??

I wan't to insert it in the core2.0n-rom (very stable) but i didn't succeed.

So no i wanna try youre rom.
[8125, K-JAM, P4300, MDA Vario ROM Development] masr1979:
Well I can't help you much with the ipl/screen problem, I usually get this when I mix packages from different kitchens. Try building using only the OEM packages in whiterat's .rar file, e.i move your current OEM folder out of the kitchen and place whiterat's in it.

Modules as far as I know are those folders that have names like files (touch.dll, fexplorer.exe) I'm sure there's a better explanation, but I don't know it myself.
[8125, K-JAM, P4300, MDA Vario ROM Development] mattk_r:
Sorry, been off playing in the woods for a few days.

So I've got Whiterat's files, and will try adding them into the latest kitchen post (uploading 318 v3.6 now) and will see what it takes to get it in and working.
[8125, K-JAM, P4300, MDA Vario ROM Development] 4irm:
great news, thx for the info...
[8125, K-JAM, P4300, MDA Vario ROM Development] mattk_r:
So here's the OEM package as it's set to go into the kitchen: OEM v3.7 beta

And the link to the 318 kitchen from the main thread: 318 v3.6

Everything seems to work except the Audio Manager; it gets the cert error. If someone has a working copy of it, please try/post it.
[8125, K-JAM, P4300, MDA Vario ROM Development] theloon:
Testing

Is anyone else having problems adding picture contacts to the "picture contact" cube screen?
[8125, K-JAM, P4300, MDA Vario ROM Development] mattk_r:
yep, that's the big issue at the moment. I'm scratching my head, cause I had it working in an earlier attempt. I wish I could go back, cause know how to fix the issues that that build had... :o
[8125, K-JAM, P4300, MDA Vario ROM Development] theloon:
Good Job!

Well I applaud your efforts and I am picking things apart also, so you are not alone. I am using your ROM, SYS and OEM with Ed Haas's kitchen 1.2 and shelltool. All flash like a dream. It's so simple a grown up can do it! maybe I can devote more time this weekend.
[8125, K-JAM, P4300, MDA Vario ROM Development] Whiterat:
I have an almost perfect stripped version now :) (Very proud of myself)

Literally I only have 1 problem now, Phone settings page wont close!

Nor will the phone ringtone settings under sounds and notifications.

The ringtone path is complete, ringtone will play and yes I have tried removing the HTC Ringtone Plugin.

Please help guys!
[8125, K-JAM, P4300, MDA Vario ROM Development] ADB100:
I had a similar issue which I resolved by re-encoding my preferred Ringtone to a .wma file and leaving a space between the end of the name and the extension - 'Cellular2.wav' was the original file. I re-encoded this to a wma file and renamed it 'Cellular4 .wma'. I also added this to the registry as a default ringtone:

[HKEY_CURRENT_USER\ControlPanel\Sounds\RingTone0]
"Category"="Ring"
"Script"="apw3r"
"Sound"="Cellular4 .wma"

[HKEY_CURRENT_USER\ControlPanel\Sounds\RingTone2]
"Sound"="Cellular4 .wma"
"Category"="Ring"
"Script"="apw3r"

[HKEY_CURRENT_USER\ControlPanel\SoundCategories\Ring]
"InitVol"=dword:4
"Speaker"=dword:1
"Directory"="\\Windows\\"
"AttenuationCategory"=dword:2
"DefaultSound"="Cellular4 .wma"

[HKEY_CURRENT_USER\ControlPanel\SoundCategories\RingPreview]
"DefaultSound"="Cellular4 .wma"
"AttenuationCategory"=dword:1

[HKEY_CURRENT_USER\ControlPanel\Sounds]
"Ringtones"=multi_sz:"Ring-WindowsMobile .wma", "Ring-Standard .wma", "Ring-Vision .wma", "Cellular4 .wma"

I did exactly the same previously with the 'Cellular4.wav' file and I had the problem you descibe. I am not sure whether it was the re-encoding or the space that fixed it, however it is working now.

HTH

Andy
[8125, K-JAM, P4300, MDA Vario ROM Development] mattk_r:
I heard of the same issue - having to add a space. I'll see if I can find any more out.

Whiterat - so you've made a bunch more changes? Have you got the touch dialer (quickdial) to work? I'm flashing a new mix now to test it, but I'm curious if you've got it fixed.
[8125, K-JAM, P4300, MDA Vario ROM Development] Whiterat:
Hey,

Thanks for the tip but Im afraid I am still suffering the same problem, it just wont close!

Its not even a problem with X_button.

So frustrating......

EDIT:

Matt: Yep everything works perfectly (incl quickdial) except that bloody ringtone page!

Once I am happy that this rom works I will upload the packages for all.

I fully stripped the touch's OEMAPPS,etc and truely seperated the files.
[8125, K-JAM, P4300, MDA Vario ROM Development] mattk_r:
You've got quickdial working? That's friggin awsome! I'll wait to upload any updates then. Whoohoo!

I was going to just update the 1413 to work with it, but if you've got 318 going - even better!
[8125, K-JAM, P4300, MDA Vario ROM Development] Whiterat:
Matt:

Have you got MSN Messenger?

Wouldnt mind having someone else to talk to about this, might just be something really stupid on my rom eheh :)