yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] stuartv:
I got my GTP 8.4 on Friday. There was immediately an OTA available. It came with build NAI on it. I took the OTA and now it says ND3.

Is ND3 really the latest? I thought I saw some references to a build NE5. Is NE5 for the 10.1 or 12.2 or something? Or did I just not get the latest latest?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] rholm:
I have ND3 too. When I check for updates, it says I'm up to date. I have seen people reference a stability update. Not sure if that's ND3 or not.

Cheers,

Rich
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] stuartv:
Yeah, mine says I'm up to date, too. But, I know that these OTAs seem to usually roll out in waves, so it's possible that others could have a newer build while ours still says "up to date". That's why I'm asking. In case others have gotten a newer build already.

But, I'm glad to know you're on ND3, too, so I know TowelRoot will work with that. And you said it worked without flashing an updated kernel, right? You just downloaded and ran the TowelRoot app and that's it.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] rholm:
Correct. No kernel needed. I ran towel root and then installed SuperSu.

The first time I disabled knox with SuperSu. I had a few random reboots. And, when I checked for updates, it complained that the OS wasn't stock and said no updates were allowed. So, I unrooted and wiped. After running towel root, I installed SuperSu and left Knox running. No problems this time.

I like this tablet, fast and a great screen. I will install CM at some point. I just don't want to do it in the first week.

Cheers,

Rich
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] stuartv:
Gotcha. I'm pretty much in the same boat. I don't want to mess with my warranty in the first week. :)

I can see how disabling Knox might prevent it from installing updates. But, do you think disabling Knox was causing the random reboots? Or was it something about your process when you rooted the first time?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] rholm:
I don't believe that the disabling of Knox was causing the reboots. When I restored my apps with TB, I got rid of a few. That list included Greenify, GSam Battery Monitor, and a few other system type apps. I haven't installed xposed yet (all in good time). I want to establish a stable platform first.

Cheers,

Rich
[Sprint Samsung Galaxy Note II] WhiteReign:
First off I should have left the sprint phone alone. NOPE had to help a friend. The phone is on 4.4.2 I attempted to use "[SPH-L900] CF-Auto-Root" Link Then got NFC errors and could not get into the phone. Next I tried "[Galaxy Note2 TOOLKIT V5.0.0 SPRINT] Drivers, Backup, Root, Recovery, Flash to Stock" Updated every thing. I did how ever use the wrong android version "Yes I know" So I lost the recovery TWRP. So last chance and boot into normal android recovory and did a wipe and stuff. Only thing now 4G cuts in and out. How can I just root the phone with smoothness like my S5?

Thanks all!
[Sprint Samsung Galaxy Note II] sludge1121997:
Just leave it alone.

??Thank Me Up If I Helped You ??
[Sprint Samsung Galaxy Note II] WhiteReign:
I would love to but his phone wont work and he is out or warranty :(
[Sprint Samsung Galaxy Note II] thecoolster:
Dude look...... Why cant U just use the normal. ODIN way
[Sprint Samsung Galaxy Note II] WhiteReign:
It won't see the phone any more. :(
[Transformer TF300T Q&A, Help & Troubleshooting] savvymom:
Need some guidance, I have a Transformer 300 and having terrible visibility with screen. Screen Brightness is on 100% and have auto brightness turned off. Can view inside okay not great. Outside impossible even under shade. Only visible with complete darkness. Is this a hardware issue that I can fix? My eyes are starting to strain. I had to have screen replaced a few months ago. Could damage now be showing up?
[Transformer TF300T Q&A, Help & Troubleshooting] amebiasis:
Try an apk called Lux. It will over ride your tablets normal max screen brightness and Max it out to the device's true max. I use it on about 4 devices including my TF300T it's awesome
[JAMin, XDA Neo, S200 Software Upgrading] laleyandasvivenporsiempre:
After I mistakelt upgrade my s200 with a Kjam rom, the device will not turn on again, now I need to boot from the sd card has anyone an OS backup which work on Sd card?

I ll try to alive the device from sd card but I dont know how I copy the os to the sd card.
[JAMin, XDA Neo, S200 Software Upgrading] J.Walker:
Do you have the bootloader alive?
[JAMin, XDA Neo, S200 Software Upgrading] laleyandasvivenporsiempre:
thanks for your help, no I could only reach to Bootscreen when the wall charger plugged, but naturally I could not update the rom from the charger, so I think the only solution is using a backup image from the sd card.
[JAMin, XDA Neo, S200 Software Upgrading] J.Walker:
AFAIK, it means that your battery is empty. Try to charge the battery with any working S200/100/110/9100 and you will be able to run the bootloader, then you will restore the device. Correct me, if I wrong.
[JAMin, XDA Neo, S200 Software Upgrading] laleyandasvivenporsiempre:
the problem is not about the charger or battery, although the battery 100% it still cant be opened the problem is after load the Kjam ROM, the device reject to open, it could onyl turn on if the wall charger is pluged however I could plug the USB data cable at the same time. I send it to the service center hope they could recover the device...
[JAMin, XDA Neo, S200 Software Upgrading] J.Walker:
This behaviour is typicel for a device with both broken image and discharged battery. The battery WAS at 100%, but the Prophet does not charge it if has no working OS, so the batery was drained until you tryed to reanimate the device. Ensure that the pattery is full with other, working device.
[JAMin, XDA Neo, S200 Software Upgrading] laleyandasvivenporsiempre:
Walker;

I charge the battery with an other prophet I ll wait untill the light become green and battery is 100% then after when I tried with the boken prophet it did not reanimate the device. it is very interesting to see that wizard could work with prohet's rom but not vice versa
[JAMin, XDA Neo, S200 Software Upgrading] buyaoxiao:
Flash wrong ROM consequences

Let me relate my experiences; exactly the same problem.

Update KJAM rom on DOPOD 818Pro ... Damn phone could not power on at all, at most on bootloader, plugin USB cable --> no USB word displayed at bottom.

Try to flash any RUU also no go ...

ON battery, could not power up at all, only plug in wall charger then managed to get to bootloader ... so all was lost.

Send to EBAY (where i bought from) and they flash the bloody Dopod 830 ROM..

During collection, plugin my own battery, same cannot power up... evidently the flash to Kjam killed my battery too !

The good thing was that with the 830 rom, my IPL became 2.16 (from 1.00).

So i reflashed to Dopod latest 2.15 ROM ok... further flash to AKU 2.3 hacked ROM also no problem.

SO, ultimately the cause was a killed battery from the ROM update.

Use a meter to measure contact pt 1 & 2 from top edge of battery, (supposed to be min 4.7V) I believe it's 0V or totally shorted out.

This battery cannot power on the phone, but still can be used as spare battery by power up with wall charger first, the battery still has it's 3.7V available to sustain operation.

So u can go buy a new battery and Flash to the correct ROM now.

Good Luck
[JAMin, XDA Neo, S200 Software Upgrading] laleyandasvivenporsiempre:
to buyaoxiao;

Thanks for your comments but;

I think there is something more serious than the battery; I have two prophets, and I also try with the other's battery and still nothing happened, more than that, both of the batteries work with the non-broken prophet.
[JAMin, XDA Neo, S200 Software Upgrading] buyaoxiao:
Flash wrong ROM

Hmm.. that may be true also.

I cannot really conclude as i was lucky the ebay shop i bought from agree to flash my S200.. i believed they had some trouble too as it took them a week to get it to Dopod 830 rom ... when normally they say 1 day will do. They refused to go into specifics though... (afraid that i demand for 1-1 exchange)
[JAMin, XDA Neo, S200 Software Upgrading] cidriver:
I have had the same problem, so that's why I decide to sent to dealer to try to fix it. Now I'm expect to have a call to pick it up. Hope they can improve my prophet to the new chip G4.

I tryed several times, hours to fix it, but no way. Sorry I can not tell you something good.
[JAMin, XDA Neo, S200 Software Upgrading] laleyandasvivenporsiempre:
I am sure that there should be a way to fix those devices Jtag should not be the only way( if it really works) it is meaningless to loose a device only because of a wrong rom update:(
[Galaxy Note 3 Q&A, Help & Troubleshooting] gobraves00:
I am stuck at red Verizon screen.

Someone please advise
[Galaxy Note 3 Q&A, Help & Troubleshooting] sludge1121997:
Elaborate

??Thank Me Up If I Helped You ??
[Galaxy Note 3 Q&A, Help & Troubleshooting] gobraves00:
I boot phone up and it goes to only red Verizon screen. I am rooted and have safe strap installed with no issues. Then I use Odin and flash a kernal that I thought was needed due to my version. Flash worked but it will not boot. I tried to install a back up and no luck
[Sprint HTC One (M7)] Belac77:
Does the ROM here have automatic OTA updates, or would i have to flash the updates myself each time?

http://xdaforums.com/showthread.php?t=2371960
[Sprint HTC One (M7)] StormyNight:
This is a question for the ROM thread, but to answer your question, I think so, because in post 2 of the thread, under Kitkat Update V3.0, it says that it has an updater in TN settings.
[Sprint HTC One (M7)] Belac77:
I couldn't actually post in the ROM thread, since I'm a new user :/ haha
[Sprint HTC One (M7)] StormyNight:
Sorry, my bad, I forgot.
[Galaxy S 4 Q&A, Help & Troubleshooting] watekeke:
hi i just bought s4 lte i9505..

1.9ghx quad core

base band i9505xxufnbe

my main usage of the phone is for gps, camera function, movie playback, social site

so my main concern is camera function (HDR, low light camera) and also battery performance..

no need all the bloatwares.. can download later

now im on stock rom 4.4.2.. the battery performance is bad..

easily drain battery.. and im not playing any games on it..

so hoe that u guys can recommend me the suitable rom for me..

thanx in advance..

:good::fingers-crossed::laugh::D
[Galaxy S 4 Q&A, Help & Troubleshooting] MAX 404:
Hi mate ,

If you like the stock look and feel try Omega rom , stable , fast , good battery life.....that is my recomendation . There are other that are working good like Echo Rom... try and see which one fits your need better
[Galaxy S 4 Q&A, Help & Troubleshooting] watekeke:
thnx bro..will look into it..this rom can be use on my i9505 rite?

will be no brick or other issues?
[Galaxy S 4 Q&A, Help & Troubleshooting] MAX 404:
Hi mate,

Omega has I9500 and I9505 versions for you it will be this one:

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

The other one ECHOE would be:

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

Do not know about the other but with Omega if you follow the instruction should be no problem...fast and ease.
[Galaxy S 4 Q&A, Help & Troubleshooting] spamtrash:
Sorry, mate, "best ROM" threads are not warmly welcomed here.... read specs, feedbacks, flash and taste by yourself...:rolleyes:
[Motorola Atrix HD] mt021322:
my problems http://xdaforums.com/showthread.php?t=2704426

and today was solved.

first thanks to all people on xda,devilsking for the mythool and specially for lwg45714 who give advise to use Android 4.1.1 Blur_Version.98.5.38.MB886.ATT.en.US to people who have problem with AHD bricked because flashing another sbf without unlocking bootloader first,and make a downgrade error,flashing boot.img failed etc..

just flash that sbf using mythool and the problems fixed,my AHD live again...thanks u.

on my case,i was on at&t 4.1.1 and try to flashing mexico retail without unlocking bootloader first,and bamm bricked is come..

* download mythool and extract it (prefer to Desktop),i'm using windows 7

* download 4.1.1 Blur_Version.98.5.38.MB886.ATT.en.US (http://sbf.droid-developers.org/phone.php?device=7) and place it on firmware folder on mythool

* run the mythool : instal adb and then choose flash stock firmware

* let it go (on my case there's no progression report on display,only like a hang but the process is running)

* in the end,there's option to flash recovery (stock or cwm) but in my case,if i choose cwm,still stock recovery that's installed on my AHD (no big deal,as long my AHD is back to the track) - i think i forgot to unlock bootloader first to instal this cwm hehe -

* your phone will reboot and you're ok.
[Motorola Atrix HD] raro3d:
gives full steps because or have one in the same condition but not found to restore and
[Desire 816 General] v_superuser:
Hello All,

I have been working CyanogenMod bring up for Desire 816 since a few weeks now. Currently, I have prepared the device tree and the vendor tree that I guess should be enough to get it booted(Or bootloop atleast :p ), except one thing -

> I'm having troubles implementing dt.img in the device tree to use with kernel/recovery and I did used the flag to use the dtb but, when I tested it with recovery, it got stuck on "Entering Recovery" screen for a few seconds and then rebooting and I'm pretty sure that it'd be a single silly mistake stopping from it to boot. And if recovery boots, theb most probably kernel boots(Using a prebuilt one) amd therefore increasing the chances for the ROM to boot! :)

EDIT - We are using prebuilts but we got recovery to boot. Here are the latest trees - https://github.com/desire816-dev
[Desire 816 General] bhanuteja200bc:
Great... Im no developer but..... Thanks for ur efforts.. And all the best for further development...
[Desire 816 General] dummie999:
Not sure, but I think you are using the wrong recovery fstab style. This is the cm 10.1 style, not cm 11

It needs to looks somewhat more like this

You don't have the kernel source, right?
[Desire 816 General] v_superuser:
This is the fstab that my boardconfig links to - https://github.com/v-superuser/android_device_htc_a5dwg/blob/cm-11.0/rootdir/etc/fstab.qcom

The other one's useless. :p
[Desire 816 General] dummie999:
My mistake.

Try tearing :p apart your current recovery and check for differences.
[Desire 816 General] JackpotClavin:
Make sure you have the correct offsets for the ramdisk and devtree image

https://github.com/JackpotClavin/an...72f80986171c7e401528457942/BoardConfig.mk#L34
[Desire 816 General] v_superuser:
Sorry for a late reply but, ramdisk offset and other stuff is right. Must be something else. Wondering why [MENTION=2228241]kinghunki[/MENTION] doesn't shares his trees.
[Desire 816 General] JackpotClavin:
View /proc/last_msg after it reboots
[Desire 816 General] v_superuser:
Here is the last_kmsg - https://www.mediafire.com/?m2h8f54qbic6llz
[Desire 816 General] JackpotClavin:
That doesn't look like the last kmsg of the failed boot
[Desire 816 General] v_superuser:
IDK, I flashed recovery, it got stuck on Entering Recovery, rebooted, and I pulled the last_kmsg just after it rebooted to system.
[Desire 816 General] JackpotClavin:
Okay then it seems that the kernel never booted far enough to initialize the ram console. I'd double check your devtree offsets.
[Desire 816 General] zeyadhan:
i will pm Grarak he is great developer maybe he can help you
[Desire 816 General] Grarak:
Is the kernel source already available? If yes please upload it to github

Can anyone send me stock boot.img?
[Desire 816 General] v_superuser:
There's no kernel source yet. Here's the stock boot.img http://www.androidfilehost.com/?fid=23501681358558515 !
[Desire 816 General] JackpotClavin:
you don't have any devtree offset, that's your problem

should be:

BOARD_MKBOOTIMG_ARGS := --ramdisk_offset 0x02008000 --dt device/htc/htc_a5dwg/prebuilt/dt.img --tags_offset 0x01e00000
[Desire 816 General] v_superuser:
Oh, well, I'll check and post. Thanks a lot. :)
[Desire 816 General] Grarak:
I just forked your tree

https://github.com/Grarak/android_device_htc_a5dwg

You really need a clean up

Almost all files are useless and you should also use 8960-common tree

I will send you some pull request or you can just pick my commits if you want
[Desire 816 General] v_superuser:
The device uses MSM8226 chipset!

Thanks for your efforts. :)
[Desire 816 General] Grarak:
Yes I know

But I checked other htc snapdragon 400 (actually only found htc one mini msm8930) they use msm8960 common tree

But I guess you're right

I will try to put everything in one single tree
[Desire 816 General] v_superuser:
Great. I'm thinking of putting all the trees in one organization on git so that we both could do stuff together. :)

EDIT - Here - https://github.com/a5dwg/

:D
[Desire 816 General] Grarak:
Please at me on hangouts

williye97@gmail.com
[Desire 816 General] v_superuser:
[MENTION=3727492]JackpotClavin[/MENTION] Me and Grarak(Mostly him) are working on new trees over here! We're facing an issue that you can help us out with -

When we switched to kernel source for building, the dt.img in the 'out' folder is a few 100 kBs(And also, recovery doesn't boots with it) whereas the dt.img in stock images is around 1.87 mB in size.

Any reason why the output size is smaller and what could fix it? :D

TIA! :)
[Desire 816 General] v_superuser:
See Post #23 please! :)
[Desire 816 General] cute_prince:
[CM11 Device Tree]

[MENTION=5044750]v_superuser[/MENTION], Just use the CM11 device tree of One Mini 2. Desire 816 and One Mini 2 are exactly the same device internally like our old pico and desire c. CM11 device tree of One Mini 2 is already stable and everything is working. Just compile CM11 with mini 2's device tree (make minor changes like device name etc) and you will have a fully working CM11 on desire 816 :)

EDIT: One Mini 2 and Desire 816 are insanely same :eek: . I just compared the kernel defconfigs of both devices and found that not only the chipset but also their peripheral devices are same ( Same WiFi, BT, Camera etc). :)
[Desire 816 General] v_superuser:
Thanks for the support. Me and Grarak made the device tree for desire 816 and it compiles fine. If it doesn't boots, I'll try stuff from One Mini 2!

Thank You! :)
[Desire 816 General] cute_prince:
One Mini 2 and Desire 816 are insanely same . I just compared the kernel defconfigs of both devices and found that not only the chipset but also their peripheral devices are same ( Same WiFi, BT, Camera etc). This means that even the compiled build of One Mini 2's CM11 will boot on Desire 816 with working BT, WiFi, Camera etc ( ofcourse you need to replace kernel )

Here is the device tree https://github.com/u-ra/android_device_htc_memul
[Desire 816 General] v_superuser:
That's some good news. Thanks! :D
[Desire 816 General] cute_prince:
About your dt.img problem, this could be the fix: https://github.com/u-ra/android_device_htc_memul/commit/3c13ac94830ca2c0e5c9e81c904d03f68b405b0b

This fix is already included in Mini 2's CM11 device tree. Just compile CM11 with its device tree AND vendor tree. You dont need to change anything except the device name :)
[Desire 816 General] v_superuser:
This error in the end -

----- Making recovery image ------
error: could not load device tree image '/home/vaibhav/cm11/out/target/product/a5dwg/dt.img'
make: *** [/home/vaibhav/cm11/out/target/product/a5dwg/recovery.img] Error 1

And also while making dt.img, it says, "Found 0 Unique DTBs" which I think is wrong. :(
[Desire 816 General] cute_prince:
Use this device tree for making TWRP recovery https://github.com/u-ra/twrp-htc-memul

EDIT: Also you need to rename every instance of "memul" with "a5dwg" in the device tree (especially in the mkbootimg.mk (https://github.com/u-ra/twrp-htc-memul/blob/cm-11.0/mkbootimg.mk#L11)

Before that, your kernel source needs some work, to make it work with a5dwg variant.
[Desire 816 General] Grarak:
This ain't be that easy

Device tree itself doesn't need any modifcations anymore

Problem is that DTB sources might be aborted

Since I don't have this device it's just too hard to fix it for me

An option would be to take the dtb files from one mini 2
[Desire 816 General] jithumon:
Kernel sources for our cell have been added in HTC dev site. :)

http://www.htcdev.com/devcenter/downloads
[Desire 816 General] v_superuser:
[MENTION=4443334]Grarak[/MENTION] [MENTION=4649424]cute_prince[/MENTION]

Have a look. We have proper kernel sources for a5dwg variant now. I'm downloading them and will push it after testing. :)
[Desire 816 General] tpr0:
Best news I've heard since the mAtrix leaked ROM released :good:

CM11 would be epic on our desire.
[Desire 816 General] Grarak:
I wish that would be a good news. The dts files seem to be corrupted. A source builded kernel doesn't boot...
[Desire 816 General] tpr0:
Hope they didn't read our thread, trollers :angel:
[Desire 816 General] n70shan:
i have heard that desire 816 is coming at virgin U.S.. i hope some American developers also take interest in our devices...i.e desire 816... plzzzzzzzz
[Desire 816 General] v_superuser:
Got the kernel from source booting. Seems like HTC derped dts files in some sources.

Thanks to [MENTION=4443334]Grarak[/MENTION] and his luck :p
[Desire 816 General] Grarak:
mhhhhh
[Desire 816 General] v_superuser:
Made my day.
[Desire 816 General] bballzeroone:
cm11 for desire 816 dual sim only ?
[Desire 816 General] v_superuser:
Me and Grarak have dual sim variants, but it should work, maybe a unified build.
[Desire 816 General] tpr0:
YOU IZ EPIC!:laugh::good:

My new wallpaper ;)
[Desire 816 General] Grarak:
If anyone is interested about the working state, Bluetooth is the only thing yet which works, so don't expect an early release
[Desire 816 General] tpr0:
Hope dual sim functionality won't be the long way.

Edit: I can see that cm11 supports dual sim natively ..
[Desire 816 General] bballzeroone:
i think it should work because i just installed custom rom for dual sim it worked on my phone.

how long does it take o get the official rom ?
[Desire 816 General] Grarak:
Why are you asking for ETA?
[Desire 816 General] tpr0:
Cause everything is free :P

Time is cheap :P
[Desire 816 General] Grarak:
can anyone send me the build.prop of SINGLE sim variant?
[Desire 816 General] bballzeroone:
build.prop of SINGLE sim is here.

https://www.dropbox.com/s/qwx1yls0vjkhghv/build.prop of single sim.rar

---------- Post added at 09:50 PM ---------- Previous post was at 09:48 PM ----------

sorry for asking.
[Desire 816 General] Grarak:
can you upload it somewhere else?

dropbox doesn't load here
[Desire 816 General] bballzeroone:
here

https://drive.google.com/file/d/0B85iO4fkpB6KQWFod0lVQ0xfVEU/edit?usp=sharing
[Desire 816 General] Grarak:
Google doesn't work either
[Desire 816 General] bballzeroone:
try this link

http://www.mediafire.com/download/ez5fkazb6wjphdp/build.prop_of_single_sim.rar
[Desire 816 General] Grarak:
no mediafire doesn't work either

upload it on d-h.st

that should work
[Desire 816 General] bballzeroone:
http://d-h.st/Cx8
[Desire 816 General] Grarak:
Good news

Camera, RIL and HW encoder are the only things which are broken right now

If I get RIL to work then I will open a CM thread

currently I am working alone, because v_superuser is busy with school etc.
[Desire 816 General] Grarak:
anyone with a single variant device can do this for me?

Open terminal (adb shell or download from play store):

type in:

su
find /firmware

and send me the output? thanks
[Desire 816 General] Grarak:
Well I gues I bricked my desire after playing with hboot....

That's the end for me
[Desire 816 General] v_superuser:
You can try flashing RUU,
[Desire 816 General] v_superuser:
I'm working on RIL too. :)
[Desire 816 General] Grarak:
nope doesn't work

i can't boot that phone anymore

black screen
[Desire 816 General] Grarak:
I just brought my desire HTC service center they replaced my main board for free :D
[Desire 816 General] zeyadhan:
that's is great news :D
[Desire 816 General] Grarak:
Can anyone do this for me? It's urgent
[Desire 816 General] afiqq:
tmp-mksh: find: not found