yashsingh1/xdaforums huggingface dataset:
[Sony Xperia T, TL, TX, V] dew4noberic:
can it used on Xperia VL (sol21 Firmware?)
[ONE Q&A, Help & Troubleshooting] McSvenster:
Hi there,

Today I tried to get back from cm12 to stock rom. I flashed, then tried to reboot ... nothing.

The phone is absolutely dead. No light when connected to power, no vibration when pressing the power button, no fast boot, no recovery mode. I tried to press power button over one minute, I tried to press for 20 seconds five times... nothing.

The device is absolutely dead. "adb devices" / "fastboot devices" show nothing, my Mac does not even see anything on the usb-port.

I cannot imagine how this is even possible. Is it really possible to destroy a device with flashing?

Has anybody have a hint for me?

S.
[ONE Q&A, Help & Troubleshooting] Heisenberg:
It's entirely possible to brick a device with flashing, in fact it's the most likely way to brick a device. Exactly what did you flash? And using what method?

Transmitted via Bacon
[ONE Q&A, Help & Troubleshooting] McSvenster:
I used the method described here (xda-dev forum) with the stock rom from cygn.com : cm-11.0-XNPH44S-bacon-signed-fastboot.zip

all the flashes went fine, then I gave : "fastboot reboot" and got back " rebooting... finished. total time 0.005s". (And a black screen)...

What a pitty
[ONE Q&A, Help & Troubleshooting] Heisenberg:
Did you use a toolkit or did you do it manually?
[ONE Q&A, Help & Troubleshooting] ek69:
//edit

Wow somehow I got threads mixed up while switching back and forth from Tapatalk and chrome. Sorry ignore what I wrote lol.

From what I've read, the colorOS stuff is the way to recover from a bricked phone. I don't have any experience in it though :( so I can't help much there. I would seek advice from that colorOS thread and hopefully you're able to recover

Sent From Lollipopified Bacon Goodness!
[ONE Q&A, Help & Troubleshooting] Heisenberg:
The stock images contain the firmware so that isn't the issue.
[ONE Q&A, Help & Troubleshooting] McSvenster:
The phone is practically dead, so colorOS seems to be no solution as I don't know how to flash it without usb connection. But thanks for the hint.

What I do not understand: What could have gone so wrong that the whole power circuit is damaged? I thought, that flashing only affects the internal "hard disk".

Does anyone know what exactly happens on powering on a working phone?
[ONE Q&A, Help & Troubleshooting] Heisenberg:
Nobody said anything about the power circuit being damaged, and it almost definitely isn't. That isn't the cause of a brick, what's most likely wrong is the partitions are corrupted, so it has no information telling it how to boot, what to boot into, or even to boot at all.

You didn't answer my question earlier though, diff you flash manually or via a toolkit?

I'd suggest you try this out:

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

Transmitted via Bacon
[ONE Q&A, Help & Troubleshooting] Quiche:
Well, I'm not entirely sure but I think that when you press the power button, you connect two ends, one end has a signal and the other end doesnt, when those two connect, the one without the signal gets a signal which will result in a battery going on maybe? Of this last battery part I'm not sure but that's how I guess it works...
[ONE Q&A, Help & Troubleshooting] traysteel:
I did the same as you - This fixed it for me.

http://xdaforums.com/showpost.php?p=55024864&postcount=136

Basically you have to use a Windows computer and the original ColorOS firmware to fix your partitions. Follow this guide and it will flash your One with ColorOS, then you can flash TWRP and go on to flash CM11S.

It worked for me but it was a bit of a pain.
[ONE Q&A, Help & Troubleshooting] McSvenster:
Sorry, I mixed up two answers... I did it all with the fastboot commands (e.g. fastboot flash userdata cm11s\userdata_64G.img)

Thank you all a lot for your hints - I will try to fix it with a windows computer and keep you informed.
[ONE Q&A, Help & Troubleshooting] McSvenster:
Well, that did the trick, thank you very much! Using Windows the phone was detected as a Qualcom mass storage. I could then use the tool that directly flashed the stock cm11.

Again, thanks a lot!

All the best,

Sven
[ONE Q&A, Help & Troubleshooting] Heisenberg:
Awesome news.

Transmitted via Bacon
[General Paranoid Android Discussion] GaboWinter:
Hi, probably I'm a little rusty but I can't find anything related to this:

Installed the latest alpha on my N4 and I can't set a user picture from the gallery, I know that it's a little detail but I like the details :p All I wanna know it's if this is a bug or something else, on stock I didn't have that issue.

As always thanks a lot and continue the awesome work, we miss you guys!
[General Paranoid Android Discussion] Pirateghost:
It pulls from your g+ profile

#stayparanoid
[General Paranoid Android Discussion] plegdroid:
Morning Matey?

As a workaround.

If you don't have a g+ profile, just set it manually, tap the image/more settings, pick owner/tap the owner image, pick a image for yourself,press ok .?

ⓐⓝⓓⓡⓞⓒⓛⓓⓔ ⓘⓢ ⓝⓞⓣ ⓐ ⓢⓘⓝ
[General Paranoid Android Discussion] elpeterson:
There does seem to be some sort of issue, it isn't pulling in my photo either.
[General Paranoid Android Discussion] plegdroid:
Not dismissing what you've stated, but on ma N4 it just dragged it thru once it asked me if I wanted to reinstall a previous Google setup. Not sure if you dismissed that option or not after your first boot.:)

ⓐⓝⓓⓡⓞⓒⓛⓓⓔ ⓘⓢ ⓝⓞⓣ ⓐ ⓢⓘⓝ
[General Paranoid Android Discussion] elpeterson:
I don't understand what you are saying...
[General Paranoid Android Discussion] plegdroid:
After flashing and the first boot, google askes you to log into a Google account, part of doing that gives the option to restore a previous setup that Google has saved, I let Google restore everything for me and it installed the user icon with it.

ⓐⓝⓓⓡⓞⓒⓛⓓⓔ ⓘⓢ ⓝⓞⓣ ⓐ ⓢⓘⓝ
[General Paranoid Android Discussion] elpeterson:
Right. But I didn't want to restore anything. The user profile pic should pull from G+ automagically.
[General Paranoid Android Discussion] plegdroid:
Not wanting to cause offence, but is Google+ sync ?

ⓐⓝⓓⓡⓞⓒⓛⓓⓔ ⓘⓢ ⓝⓞⓣ ⓐ ⓢⓘⓝ
[General Paranoid Android Discussion] elpeterson:
Haha I understand. No offense taken. It is synced though.
[General Paranoid Android Discussion] plegdroid:
Only other thing I can think to get it to set, would be to reset contacts from within G+.

Settings/your Google account/contacts/ untick keep contacts upto date, then retick keep contacts update .:)

ⓐⓝⓓⓡⓞⓒⓛⓓⓔ ⓘⓢ ⓝⓞⓣ ⓐ ⓢⓘⓝ
[General Paranoid Android Discussion] elpeterson:
That did it! Thanks!
[General Paranoid Android Discussion] GaboWinter:
Thanks for your answers guys!

Also, thanks for the workaround [MENTION=4259944]plegdroid[/MENTION] but even following those steps I can't have my pic, it i doesn't matter really, but just to keep digging :p [MENTION=1744130]elpeterson[/MENTION] which gapps package are you using? I don't know maybe it's something related.
[YU Yureka Original Android Development] sooorajjj:
[IMG="YU"]http://i57.tinypic.com/rw5qgy.jpg[/IMG]

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.​

#include <std_disclaimer.h>

/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/

CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.

Official CyanogenMod Wiki:http://wiki.cyanogenmod.org/w/Main_Page​

WHAT IS WORKING?

WHAT IS NOT WORKING?

Installation Instructions

DOWNLOADS

Unofficial Builds

​

Google Apps

PA Gapps: http://xdaforums.com/paranoid-android/general/gapps-official-to-date-pa-google-apps-t2943900

SOURCES:https://github.com/YU-YUREKA

Other issues?

Before posting in this thread, make sure of a few things:

You used the search function of the forums.

If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and now wipe cacche and dalvik-cacche Boot up and see if the problem persists.

Make sure your post is relevant to this thread.

Logs! You can use this: https://play.google.com/store/apps/d....tortel.syslog

Contributors

fergy and my team

CM Team
[YU Yureka Original Android Development] sooorajjj:
NOTE: this is not stable for daily use

i do not recommend any one to flash this

this is just initial test build :)

For more Screenshots HERE
[YU Yureka Original Android Development] sooorajjj:
CHANGELOG​

*"UNOFFICIAL-BUILD-1"

Initial TRY(to get CM-12.0 - booting )
[YU Yureka Original Android Development] sooorajjj:
last one
[YU Yureka Original Android Development] ##W4TCH0UT##:
Great work!!!

Regards
[YU Yureka Original Android Development] Santhosh M:
Very good work :) Bug fixes and other stuff should start kicking on :)
[YU Yureka Original Android Development] Faaiz Puthawala:
good work bro
[YU Yureka Original Android Development] Rohit Gupta @123:
Wow Good Work :)
[YU Yureka Original Android Development] siddhartha51997:
I will install this rom today .i can help yu in beta testing!

---------- Post added at 08:07 PM ---------- Previous post was at 08:03 PM ----------

Are there any serious Bugs? Asking Coz i am going to install It
[YU Yureka Original Android Development] sooorajjj:
Thanks :)

Sure :)

Thanks :)

I tested my build for say like 5-10 mins so i didnt find much
[YU Yureka Original Android Development] asim.sidz:
I could do without RIL and Camera at the moment but Wi-Fi is a must have for me i think. But still, the work is applaudible enough. Eagerly waiting for the next update. Good work! :good:
[YU Yureka Original Android Development] sooorajjj:
Thanks ..... Will fix all bugs :)
[YU Yureka Original Android Development] siddhartha51997:
Really Great Work Bro!...Can I Repost This In YU forum (With all credits to you). And Help Others Track development of this ROM?
[YU Yureka Original Android Development] sooorajjj:
I already posted there ..... Lol :)
[YU Yureka Original Android Development] asim.sidz:
hey

hey mate, do you mind if i post your work on my blog @ www.itechnozoo.com ?
[YU Yureka Original Android Development] sooorajjj:
Sure can post there :)
[YU Yureka Original Android Development] nickhil90490:
Hey buddie nice work hope u will cleared out allbthe bugs....thanks
[YU Yureka Original Android Development] sooorajjj:
Irritating..............!

been doing about 48 and + builds from last few days couldnt fix ril wifi and camera :mad:

relly pissed up right now and starting to give up .... Maybe i think i should wait for official cm:(
[YU Yureka Original Android Development] siddhartha51997:
Did you Check the CM ROM on You forum.There Are very Less Bugs in it
[YU Yureka Original Android Development] sooorajjj:
Ya i know cdesai's build but its closed sources ...... Ie i don't see any links to his sources in that thread u can use things from his build as proprietary binaries btw then it fails the initiative of build from source and furthermore can be called as ported rom ....lol
[YU Yureka Original Android Development] k2wl:
@sooorajjj

service ril-daemon1 /system/bin/rild -c 1
class main
socket rild1 stream 660 root radio
socket rild-debug1 stream 660 radio system
user root
disabled
group radio cache inet misc audio sdcard_r sdcard_rw diag qcom_diag log

change above from your init.qcom.rc to

service ril-daemon1 /system/bin/rild -c 2
class main
socket rild2 stream 660 root radio
socket rild-debug2 stream 660 radio system
user root
disabled
group radio cache inet misc audio sdcard_r sdcard_rw diag qcom_diag log

apparently new sources use next number socket for ril. :)

and dont give up!!!

i have built tons of builds for devices for months...with no ril and data untill i fixed it...so keep on doing it...eventually when cm team releases it...make some more new roms...:)
[YU Yureka Original Android Development] sooorajjj:
seems fesible ....... will try with those changes

i have got slimlp booted and trying omini 5.0 btw same bugs will be reprodused in all of them

i will not give up on development ......... btw i was thinking about stopping for a while untill LP propritary blobs for yureka released

to narrow down the ril issue i did a lot of builds by changing blobs mostly got bootloop cause of com.qualcomm.location.apk it is made for kk and LP framework ie cm12 framework doesnt support old MSIM implimentation so gives a fatal error and falls in a loop

for some wierd reason wifi dosnt compile properly camera is a mess i tried 2 or 3 days on it and no luck
[YU Yureka Original Android Development] rahulsingh616:
[MENTION=943196]k2wl[/MENTION]

Feeling so good to see you here bro!

fan of ua work

i had galaxy grand duos and u made that device so good for us with all ua custom roms!!

Recently switched to Yu yureka!
[YU Yureka Original Android Development] varun.chitre15:
We didn't release the device tree source because we don't want the forum filled with broken builds of other CM based ROMs which will be a big mess to deal with once official update lands, not because we don't support the 'open source initiative' you claim we do.
[YU Yureka Original Android Development] sooorajjj:
Ok .. I didn't expect a reply like that from you

What i said is if i use stuffs from your build as proprietary (as prebuild binaries ) and maybe get things working then it fails my initiative of build from sources ..... Ofcourse i know you have built from source also i do appreciate it as a great work :)

I have no complaints for you keeping stuffs proprietary .
[YU Yureka Original Android Development] Sudeep Duhoon:
Can I have build.prop of your build? For sim related purpose.
[YU Yureka Original Android Development] sooorajjj:
Sure https://drive.google.com/file/d/0B1WuJuN7p2ihcGJab3NHSTNTZ00/view?usp=sharing
[YU Yureka Original Android Development] 123xodus123:
Wow! This is really appreciated. Waiting for RIL and WiFi fix.

Hats off to you! Way to go!!
[YU Yureka Original Android Development] Sudeep Duhoon:
Can you try this edit?

# Radio

#persist.radio.multisim.config=dsds

persist.radio.apm_sim_not_pwdn=1

ro.dual.sim.phone=false

persist.dsds.enabled=false

rild.libargs=-d /dev/smd0

rild.libpath=/system/vendor/lib/libril-qc-qmi-1.so

ril.ecclist=112,911,999,110,122,119,120,000,08,118
[YU Yureka Original Android Development] sooorajjj:
Build.prop editing will not work lol we have a diffrent kind of MSIM implementation in cm12 so iam unable to use cm11 ril blobs for cm12 ................ we need new blobs or rework OPT_TELEPHONY-MSIM to support old blobs
[YU Yureka Original Android Development] Sudeep Duhoon:
I don't know that but your build.prop is different from another cm12 build for yureka and is similar to stock.

Also see this: http://xdaforums.com/moto-g/general/guide-cm12-moto-g-t2952031

I have tried in that cm12 build to edit these entries as stock cm 11 rom and both sim didn't worked. After editing them back, 1 worked.
[YU Yureka Original Android Development] sooorajjj:
ya single sim works with old baseband
[YU Yureka Original Android Development] atharvac:
[MENTION=225651]op[/MENTION] is this a 64-bit build or 32 bit one? just curious as there is another cm12 in yu forums thats 32bit and almost stable. Thanks for cm12 aynway :D
[YU Yureka Original Android Development] sooorajjj:
32Bit build
[YU Yureka Original Android Development] sooorajjj:
[MENTION=6107824]dumtara[/MENTION] [MENTION=5480061]Santhosh M[/MENTION] [MENTION=5722563]Siddhesh.K15[/MENTION] if anyone wants to do Mokee

Just pull this and compile https://github.com/YU-YUREKA/local_manifests/tree/kk_mkt

https://github.com/YU-YUREKA/androi...mmit/32c8485048b01a8b55958e5eed827ada1240edd4

it should be booting right away

the reason iam not building it is bcs i dont have any space left for Mokee sources :(
[YU Yureka Original Android Development] Santhosh M:
Not interested in mookee or i would have put it up long back.

Last device where I compiled and used mookee didn't find anything interesting.
[YU Yureka Original Android Development] sooorajjj:
Ohk
[YU Yureka Original Android Development] devilex94:
Please do Ubuntu Touch

Or any chances of Miui made from patchrom?
[YU Yureka Original Android Development] sooorajjj:
will do once i have enough time

also have plans for multi rom
[YU Yureka Original Android Development] ela1103:
We need multi rom .because so many apps could not support ANDROID L .
[YU Yureka Original Android Development] devilex94:
What is the priority of MIUI? :p

I guess its high :D

---------- Post added at 12:47 PM ---------- Previous post was at 12:45 PM ----------

Which apps don't support Android L?
[YU Yureka Original Android Development] ela1103:
Which apps don't support Android L?[/QUOTE]

Some Apps and no stable for few month
[YU Yureka Original Android Development] atharvac:
Multi ROM would be awesome. Thank you very much!
[YU Yureka Original Android Development] pkdlca:
Dear Dev

Please rebuild cm12 and fix bugs. I am eager to port on my yureka because no date of official announcement about release of cm12.
[YU Yureka Original Android Development] matwaking:
lol man if this was that easy as writing then it would have been done already,building w/o any correct base is a hard job requiring time

and for official update ,we know cm team will do when they will do:fingers-crossed::fingers-crossed:
[YU Yureka Original Android Development] sooorajjj:
this is a dirty hack btw will fix single sim

and sorry i was wrong on last reply :(
[YU Yureka Original Android Development] Sudeep Duhoon:
Something is better then nothing [emoji56]
[YU Yureka Original Android Development] patelsavan:
So the bug of wifi is fixed or not ....?

If it is solved then i am eager to use this rom....???
[YU Yureka Original Android Development] shashank.msuresh:
Hi can u tell me how to get single Sim functionality pls.:D:):)
[YU Yureka Original Android Development] dumtara:
I build this ROM using [MENTION=5138607]sooorajjj[/MENTION] cm-12 sources.

wifi is working

sim,camera not working.

Note: Device heats-up issue. Please use with caution. Only for testing purpose. Not for daily use.

ROM link: [url=https://www.androidfilehost.com/?fid=95916177934549590]cm-12-20150401-UNOFFICIAL-tomato.zip 246 MB[/url]
[YU Yureka Original Android Development] abhifx:
sooraj also seems to be working on sokp for tomato. so yeah great work. also, is this most updated cm12 build? the nighlies at cm12 are almost berserk with tons of commitments everyday.
[YU Yureka Original Android Development] dumtara:
yes updated to latest cm-12 source.
[YU Yureka Original Android Development] sooorajjj:
For dual sim fix revert my system.prop changes and use aosp 5.1 hardware/ril
[YU Yureka Original Android Development] dumtara:
Thnx... I am trying that.... :fingers-crossed:

-edit-

RIL not fixed with above method.
[YU Yureka Original Android Development] abhifx:
HI!

just to report that the build is working fine. very smooth. camera is kind of working with strange colors (gpu binaries update required maybe?) but pics are not getting saved.

wish RIL was working, that should have made it a daily driver. and thanks for the build
[YU Yureka Original Android Development] shomil49:
any progress developers....

coz u r the only hope now.

cm or yu no one gonna release official cm12 in near future..
[YU Yureka Original Android Development] dumtara:
Waiting for vendor proprietary blob for Yu-Yureka branch CM-12

Its closed source.

CM12 with old blobs giving memory error.:(
[YU Yureka Original Android Development] abhifx:
have you tried considering other sources like from zte blade s6? Although i know its too far fetched, but hey if its the same then why not.
[YU Yureka Original Android Development] shomil49:
ok bro

it mean we have to wait for yu to release cm12.
[YU Yureka Original Android Development] shomil49:
bro any success???
[YU Yureka Original Android Development] shomil49:
yupzzzzz ota rollout started..... cheerss guyzz
[YU Yureka Original Android Development] Iqbal641:
If i flash original 444 factory image my device bootloder relock.?
[Nexus 7 (2013) Q&A] sparkplugDev:
Hello, all.

I have a friend with a Nexus 7 2013 (WiFi) that she recently purchased refurbished. After some issues with the charger that they originally sent with the device, she finally got it charged and now it always says that it's "charging" even when it's unplugged. She tried doing a factory reset, but even after going through all that, it still says that it's charging regardless of whether it's plugged in or not. I also recommended she try letting it drain totally to zero and then charge it again to see if it was something it could be tricked into forgetting. I also went into the stock recovery and cleared the cache, to no avail. It is fully updated to Lollipop 5.0.2 with a locked bootloader and stock recovery and seems to be in good physical condition. If anyone has any suggestions I would really appreciate it.
[Nexus 7 (2013) Q&A] fury683:
Curious if something could be goofed up with the wireless charging coil.

When you go into the Battery screen (two finger swipe down from the notification shade, tap the battery icon) what does it say at the top? If the battery icon shows charging, it should list how it is charging in the battery screen, AC, USB (I think) or wireless.

Another suggestion might be to unlock the bootloader and flash the factory images direct from Google. I know you said that a factory reset was done, but I'm guessing it was done "onboard" without a PC. Reflashing the entire image could help clear up any cobwebs.

Unlocking the bootloader will induce a factory reset, but if one was already done, it seems like your friend would be OK with trying it again.
[Nexus 7 (2013) Q&A] sparkplugDev:
[MENTION=3351823]fury683[/MENTION] I tried checking the battery stats for which charging type it believed it had and it says "over USB" so I guess it thinks it's plugged into a computer (probably due to the low (lol) amperage). I'll talk to her and see what she thinks about unlocking the bootloader and flashing the factory image, but she bought it from Amazon so I think, unless someone else can think of anything to try, I'm going to recommend she tries to get it replaced because Amazon's CS is awesome. Thanks for the pointers. If she doesn't have any luck with Amazon, I'll proceed from there.
[Nexus 7 (2013) Q&A] fury683:
If a return/exchange is possible, I'd go that route. As for unlocking the bootloader, it can be relocked when you're done flashing the factory image. However once it is locked, unlocking it again will require another factory reset.

Having it unlocked allows for flashing of other ROMs and recovery, as well as easy rooting. If that isn't needed and the user is OK with waiting for OTAs (the 5.0.2 one seems to be taking quite a while for some users), relocking it would be fine.
[Nexus 7 (2013) Q&A] jsnow222:
Did anyone figure out this issue? My nexus 7 started with this exact problem this week. Always shows charging (usb). It will never fully charge, via wall charger or wireless.
[Nexus 7 (2013) Q&A] fosser2:
I had a 2013 Nexus 7 and it did this when I took it out of the box. It seemed to be a hardware issue. I was able to warranty it with Google. Sorry this is probably not helpful to you since the warranty period is probably over, but at least it probably brings conclusion to your issue.

fosser2
[Nexus 7 (2013) Q&A] jsnow222:
I was luckily still under warranty, hopefully the issue will be resolved.