yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Q&A, Help & Troubleshooting] rhipone:
Hi, i got a Nexus 7 2012.

I try to flash rom but doesnt work and the next time that i tried to power on it doesnt do anything.

I connect my devide to my PC and I see that is in APX mode.

I read a lot about this issue but I cant find nothing that works, so, there is any way to unbrick my nexus or is just a nice paperweight?

I try everything...
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Hi, rhipone...

I really hate writing posts like this.

APX mode suggests you likely have a corrupted or erased bootloader on your Nexus 7... and without a working bootloader, the Nexus 7 is Hardbricked, or to use your metaphor, "a nice paperweight":(.

-----

However... although APX mode is the default mode the Nexus 7 NORMALLY enters into in the absence of a working bootloader, it's feasibly possible the device may have entered APX 'accidentally', and your bootloader is actually still 'good':) (...there is a way of forcing APX mode, for nvFLASH purposes, and so it's conceivably possible your Nexus 7 may entered into APX mode inadvertantly).

----

So, try the following key press combinations... if the bootloader is still good, then, AND ONLY if your device has entered APX accidentally, then these may work...

LONG PRESS POWER BUTTON... (hold for 30 seconds)...

-or-

VOLUME DOWN (hold 5 secs), & then simultaneously hold POWER BUTTON (hold both for 30 seconds)...

----

Your ideal goal here, is get the device to boot into the bootloader... with that goal attained, you should be able to fastboot back to factory stock.

Very best of luck...

Rgrds,

Ged.
[Xperia Z3 Q&A, Help & Troubleshooting] kuass:
Hi.

I have a yellow spot on the display. It seems to be the same like many people had it on the HTC One X. I had it too, on the One X.

I read, it was something with some glue in the display.

Cheers
[Xperia Z3 Q&A, Help & Troubleshooting] raviboy100:
factory warranty covers it so bring it back and if its whitin 28 days of purchase, demand a new sealed box as consumer right entitles you on.
[Xperia Z3 Q&A, Help & Troubleshooting] hanime:
That looks like a manufacturer defect right there. Get it exchanged ASAP.
[Xperia Z3 Q&A, Help & Troubleshooting] The_Rick:
Display Issues

Forgive me, but what's wrong with These Displays These days? Or am I doing something wrong?

I've been having Trouble with spots on Displays for years.

When it came out I bought a HTC One X. After a month there appeared a yellow spot on the left edge. I brought it back, waitet for 1,5 months and then became back my device with a replaced Screen and battery.

After another month i got again a yellow line... It was always the same, at first there is a slightly yellow line on the left or right edge, after a while it gets darker and darker and turns violet/Brown.

I returned my htc one x 3 times, after the 4th attempt to repair i became the Money back.

After that i bought a HTC One X Plus. Same Story! I returned it 3 times for the same Screen issues, in the end after another year struggling I became again the Money back.

Then i bought a Xperia Z2: Believe it or not, again same pain :( 3 attempts to repair and then Money back.

The good Thing is, I always got the Money back. But i buy a device for using and working with it, not for having this Trouble.

In december 2014 i bought a Xperia Z3. Yesterday I noticed a yellow line on the left edge ...

In the meanwhile i bought a Surface Pro 2 also... and had the same Trouble, I had to send it in because of yellow lines ("just" one time, for now...)

What is going wrong here? :(
[Xperia Z3 Q&A, Help & Troubleshooting] abhinav.tella:
Its probably the glue, I guess you are just very unlucky. I went through two One Xs and luckily no yellow spots, in fact I have never gotten any device with that. Just get a warranty replacement, nothing else you can do. Its pretty bad on your phone, I believe its UV cured glue.
[Xperia Z3 Q&A, Help & Troubleshooting] Geeks Empire:
Info

where r u living?

u should select better retailer
[Xperia Z3 Q&A, Help & Troubleshooting] The_Rick:
Well it's getting difficult, i live in Switzerland and bought the 5 mentioned Devices from 3 different retailers :(
[Xperia Z3 Q&A, Help & Troubleshooting] blakechan:
Bad luck, dude

It seems that yellow spots do happen in some of the phones manufactured in a certain period of time and cause mainly by the OCA(Optical Clear Adhesive) glue between the glass and digitizer
[Xperia Z3 Q&A, Help & Troubleshooting] The_Rick:
Thanks for your replies, i'm gonna return the phonre for repair again.

Could this Problem be connected with heat issues? All the Devices ( well, except maybe the xperia z3) could get very hot.
[Xperia Z3 Q&A, Help & Troubleshooting] abhinav.tella:
Yeah that can also cause that, do you live in a very hot area? I went to med school in a place where it commonly reached 45C/113F+ in the summer and I still never got this issue with my LG Optimus 2X, HTC One X and HTC Butterfly
[Xperia Z3 Q&A, Help & Troubleshooting] The_Rick:
Well no, it's not that warm here, it barely gets to 30C in Summer, and I got the issues also in winter... But my htc's and the z2 were itself good heaters :)
[Xperia Z3 Q&A, Help & Troubleshooting] unclesem:
Did you solve this issue ? Did you need to replace screen ?
[Xperia Z3 Q&A, Help & Troubleshooting] The_Rick:
Yeah, unfortunately I had to replace the screen.

Actually they replaced the screen 3 times and after that (and after quite a bit of fight :rolleyes: ) I returned the phone to the seller.

:p I seem to have some kind of bad luck in that regard, here is my statistic for the past few years:

Yellow spots on HTC One X -> screen replaced 3 times

Yellow spots on HTC One X + -> screen replaced 3 times

Yellow spots on Sony Xperia Z2 -> screen replaced 3 times

Yellow spots on Sony Xperia Z3 -> screen replaced 3 times

Yellow spots on Microsoft Surface Pro 2 -> screen replaced 1 time, it's yellow again and has to be replaced but I need it for work

And now:

Yellow spots on Microsoft Lumia 1520, have to send it in

I thought that I do something wrong (although I never had these Issues before HTC One X), then a few weeks ago I went to an electronics reseller to take a look at an exposed Surface Pro 3 and saw that picture... Look at that the yellow line on the left edge :silly:
[Xperia Z3 Q&A, Help & Troubleshooting] AlvinZahran98:
You're very very unlucky mate.... :(

3 different retailers and 5 different devices, with similar/same problems? There's something wrong happening there..
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] cheetah81:
I flash CWM recovery many time with help odin every time after reboot cwm remains same as Stock CMW recovery...

:confused:

Stock version 4.3

Plz give solution .

:banghead:
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] cheetah81:
Ok I found the solution

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

[CWM][GT-I9305] CF-ROOT CWM Recovery Ported + SuperSu + BusyBox

ツ
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] prqek:
Hi,

I9305 is not officially supported by towelroot. So I searched for some details about the exploit and found this pastebin.com/A0PzPKnM (which seems to be decompiled and cleaned - made more readable towelroot v1) and some articles about how its supposed to work (blog.nativeflow.com/the-futex-vulnerability and tinyhack.com/2014/07/07/exploiting-the-futex-bug-and-uncovering-towelroot/). I have to admit that I don’t understand it fully, but well enough to modify it to this pastebin.com/1fdmC4Xv , which is working exploit on my i9305 with Android 4.3, kernel 3.0.31. I didn’t make any big changes – I made few modifications to compile the code, added lots of debugging output, changed what happens when the hack is successful and added the iov_index variable, which is the most important change. The original code is not nice and my changes are not nice neither, please be lenient while reading it. If you want to use it, compile it with android ndk, push to /data/local/tmp and run. There can be one argument, number from 0 (default) to 7 (you can use bigger, but it makes no sense). If it succeeds, you’ll get root prompt. Otherwise it can freeze or reboot the phone. You can check the kernel panic reason in /proc/last_kmsg. If you see that it crashed in plist_add because “Unable to handle kernel NULL pointer dereference at virtual address 0000000c”, subtract 0xc from the address and use as the argument (iov_index) next time. Don’t give up, it doesn’t work always. Note that, the phone will reboot after you quit the root shell. Its up to you what you do with this, but AFAIK successful execution of this exploit doesn`t change the KNOX warranty bit, at least my phone still says that the system is “official”.

Remember to be careful, when doing anything of this and don’t blame for any damage.

If you want to play with it in debugger, you don’t have to use the android emulator as suggest in the article mentioned above – I used vanilla kernel 3.0.31 compiled with exynos4_defconfig, buildroot userspace and latest qemu with the machine smdkc210.

Pavel

P.S. I don`t have enough posts here, so you have to use the links manually :(
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] schizyk12:
Hi! I use I9305 with android 4.4.4 - without any branding. Could U help me with root this device without knox flag? Thank u, I'm from polish and my english is soo bad ;/ I want ready aplication to install if u could do this for me ;)
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] Galaxy S3 VietNam:
wow thanks you
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] prqek:
Hi schizyk12,

I am afraid, that I will disappoint you. I don`t have any other phone than my i9305 with 4.3, so it would be a blind shot to create such an application. Even if I had some more devices, I am not sure if I have time to do this. Another problem is that I am not even sure whether this would work on 4.4.4. What kernel does it use? See this www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3153 , if your kernel version is higher than 3.14.5 then the bug this is exploiting is fixed. If you kernel is build after May 26th, 2014, it is also probably fixed.

I am attaching the binary that worked for me. You can try it - unzip it and pull it into /data/local/tmp using adb (if you don`t know how to do it, search the web, it`s not difficult) and execute from adb shell as /data/local/tmp/tr_c 1 (or some other integer, see my original post). Keep trying, it may not work for the first time. If it succeeds, you will see something like this:

cpid3 resumed.
hack.
/system/bin/sh
shell@m3:/data/local/tmp #

If your phone reboots, it is a good sign – the bug is probably not fixed.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] MATORAX:
I also have i9305 with Android 4.3 (kernel 3.0.31) and everything seems to work fine - when I execute tr_c 1 it displays a lot of lines but there are few, which look exact same like in your post above. Now the problem - this method doesn't give me root access... I don't know what is wrong. Can you help me with this? Maybe you know how to get it working? Thanks for all of your work :) PS: Sorry for my english.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] prqek:
What do you mean by root access? This is not one the “one click root” applications, this is only the exploit. If you see at the end what I posted in my previous post, you have root access, but only in that one session. If you want to have rooted device, you have to do the rest manually. Unfortunately I didn`t find any article describing what this means. There are only lots of “one click” apps. Finally I used Koushiks Superuser – it is simple and opensource, so it was quite easy to find how the installation (“rooting”) works. Take a look at this script github.com/koush/Superuser/blob/master/Superuser/assets/update-binary . Don`t execute it, it is supposed to be run from recovery. Here are briefly the steps to be done (I hope I didn`t forget anything, don`t do it if you don`t understand it):

1) mount -oremount,rw /system

2) copy su to /system/xbin

3) chown it 0:0 and chmod it to 6755

4) create link from /system/bin/su to /system/xbin/su

5) modify (or create) /system/etc/install-recovery.sh (see github.com/koush/Superuser/blob/master/Superuser/assets/install-recovery.sh)

6) sync and reboot

I actually used the disabled ssh service from /init.rc and I am enabling it install-recovery.sh, so if the su daemon is killed, it is restarted automatically. The daemon is needed because of bypassing SELinux, the suid bit is not enough (I suppose I can chmod to 755 in step 3).

You don`t have to compile the whole supperuser, you can download it from here www.koushikdutta.com/post/superuser .

But there is one problem with this version – if the selinux is enforcing, the su works only from adb shell. It is because the socket used for communication between su and daemon is in /dev, which is not accessible by applications. So I moved it to /data/local/tmp/. Now it works for apps and not for adb shell. But you have to compile the su binary to do this. I should report a bug to Koushik.... Also adding setenforce 0 to install-recovery.sh should help, but it turns off SELinux.

Pavel
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] MATORAX:
Yeah, I thought it will be something like "one-click root". Now I understand - I had root access from adb but not normally rooted phone :) I read your instructions and I have more questions. Did you do this on your phone? Is the warranty void still 0 after these operations? I don't want to change it to 1 :)

PS: I'm not sure if I can make this work, so I must live without root on this device since it'll be easier to do :D
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] prqek:
I*did all of this on my phone :) I don`t see any triangle like here www.mobot.net/samsung-galaxy-s2-removing-yellow-triangle-37410 . The know warranty void in download mode says 0, so I guess it is OK. But the device status in settings says custom, but this happened after I removed knox related applications. I didn`t try to put them back. It may fix it. If I remember well, the step I described didn`t change any of these bit and statuses.

It`s not so difficult, you just need some understanding how Linux system works.
[Upgrading, Modifying and Unlocking] beltype:
Hi there,

first of all, many thanks to all the talented people here, who give their time and energy to serve pda enthusiasts! I'm new to the htc smartphone world, just bought a Magician, a Prophet (G4:)), and a Universal to get a nice introduction into the mobile world. So far, I've read tons of materials before first deciding on changing ROM on my Magician, with success:). Well, it's a risky business, and so many times you read alarming posts from people who wracked their nice working devices just by lack of knowledge. In fact, it all reminds me of walking on a ground stuffed with landmines. There are leaders who find a safe path (write an instruction), tell the others to follow, but never miss saying "remember, we don't take any responsibility".

I think the instructions are fine, but what I would really appreciate is to have some light shed on how the things work, so that I know what I'm doing, not just following the footsteps of someone who knows. I'm desparate to see some real piece of knowledge, but they are scarce. Take, e.g. a paragraph I found here (http://wiki.xda-developers.com/index.php?pagename=FAQ#faqOsPhone) on IPL/SPL:

"IPL: Initial program load - usually paired with Secondary Program Load (SPL), is the boot loader of your phone, much like the BIOS is the boot loader for your PC. Note: IPL/SPL are highly hardware dependent, flashing the wrong IPL/SPL is much more serious than a flashing the wrong ROM. It may be noted that, sometimes a ROM package also contains the IPL/SPL which will be flashed into your phone. Hence be extra careful what you are flashing. Note: although a ROM may also contains the IPL/SPL, `ROM` usually refers just to the OS (eg. the Windows Mobile 5, not the IPL/SPL) and the ExtRom."

Well, it looks like this stuff is absolutely vital to anyone who ventures beyond entering the bootloader screen of their device, but why the fundamental questions raised there are left without answers? Some of such questions are:

1. Why do some ROMs contain IPL/SPL, if IPL/SPL are hardware dependent?

1. How do I know if a specific ROM I'd like to flash on my device contains the IPL/SPL? And then - can I flash its IPL/SPL on my original IPL/SPL?

2. What does it mean "flashing the wrong IPL/SPL"? How do I find out which ROM is suited for the IPL/SPL on my phone?

3. How do I find out the IPL/SPL for my Magician, if it's not desplayed neither on the spash screen, or in device information tab?

Please have some understanding for those newbe's questions:). Maybe they are naive, but I don't want to learn the hard way... My question is: do you know any good site (or hardcopy materials) with regular knowledge to learn from about the mentioned and other important issues on pda modding/upgrading? I'll be really grateful for some guidance tips on how to guide myself:)

Many thanks in advance,

greg
[Galaxy Note 3 Q&A, Help & Troubleshooting] thirdempire:
H!i Can someone tell me if I'm doing it right?

Ahmm I want to root and flash a rom on my note 3 sm-n9005

can you guys tell me if my sequence are correct

1st: ROOT my phone

2nd: Flash a RECOVERY

3rd: Flash a CUSTOM ROM

and lastly Flash a KERNEL

I'd really appreciate your feedbacks!

Thank you so much!!
[Galaxy Note 3 Q&A, Help & Troubleshooting] vndnguyen:
Root is not necessary as many custom rom come with pre-rooted.

The sequence should be:

1- Flash a RECOVERY

2- Flash a CUSTOM ROM

3- ROOT my phone (optional, depending on ROM)

4- and lastly Flash a KERNEL
[Galaxy Note 3 Q&A, Help & Troubleshooting] thirdempire:
THANK YOU! This helps a lot..

Ahmm can I ask one more question..

Is it okay if ill replace the kernel of a custom rom into a different kernel?

Ex. I have this ROM(gummyrom) which has it's own Kernel, then i downloaded 'Lean Kernel' is it okay just to replace the kernel of 'GummyRom' into 'Lean Kernel'?
[Galaxy Note 3 Q&A, Help & Troubleshooting] vndnguyen:
Sorry I cannot answer to this question.

You should consult in the supporting thread of the specific rom/kernel.
[Galaxy Note 3 Q&A, Help & Troubleshooting] thirdempire:
Alright, thanks tho!
[Galaxy Note 4 Accessories] LeoNote4:
Do we have anything out in the market to choose from?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] QA Bot:
Q&A for How to root without knox

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 How to root without knox. 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! :)
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] prqek:
See this http://xdaforums.com/galaxy-s3/help-i9305/towelroot-exploit-i9305-source-code-t2937169
[Xperia Z3 Compact Android Development] edcarsky:
great! can't wait to test it... i'll see what the result is :)
[Xperia Z3 Compact Android Development] schnidex:
Thanks for this. Also, I donated to Doomlord lately, in the hope he might end up buying a Z3C (and also just a general thank you for all he's done for the Android development community).
[Xperia Z3 Compact Android Development] shafiq01:
It doesn't work, it goes into bootloop, i couldn't even boot into cwm afterwards

i had the to reflash CWM thrugh fastboot and then i could boot my device.

firast i thought it could be related to cooperate mail, so i removed password and account

and tried to flash the kernel again, same bootloop again. so i'll wait to there is a stable one

or am i doing something wrong?

fw xxx.105 rooted with cwm on it and all kinf of other stuff
[Xperia Z3 Compact Android Development] edcarsky:
What happened, I don’t experienced anything but seamlessly perfect… I love this kernel and my experience now in my z3c is absolutely great! Try to re download maybe you got the corrupted downloaded.
[Xperia Z3 Compact Android Development] AndroPlus:
One member confirmed it's working on his D5803 .105, so it might be corrupted download.

Please redownload from mirror (mega).
[Xperia Z3 Compact Android Development] edcarsky:
Indeed, I believed it is corrupted copy… for me .105, I highly recommend using this kernel, truly awesome! the graphic really works very well now, the battery perform very fine as well, I liked the new version of the cwm too! I think a lot of benefits will provide this to your z3c device, many thanks [MENTION=5169444]AndroPlus[/MENTION] you rock men! Cheers :)
[Xperia Z3 Compact Android Development] snrbobo:
flashed on my z3c with .105. no bootloops, haven't come across any other issues yet. I will say that my battery life seems to be lasting a bit longer. i'll keep an eye on it for the next couple of days and report back! I still haven't played with any kernel settings. thank you for porting this over!! if you have any suggestions for the kernel settings let us know!
[Xperia Z3 Compact Android Development] shafiq01:
it is working now, you guys were correct, it was a corrupt download. I could see the first file downloaded was 8mb the next one was 18mb

thank you xda members, appreciated
[Xperia Z3 Compact Android Development] tansy:
Thanksss
[Xperia Z3 Compact Android Development] spida_singh:
When i use Trickster to amend sound control, device reboots, anyone else get the same, also get the same when adjusting voltage, tried -25mv, same thing occurred.

Ill post a logcat shortly

Cheers
[Xperia Z3 Compact Android Development] Dsteppa:
[MENTION=5169444]AndroPlus[/MENTION]

Could you please post the MD5 hash in the OP or upload the files to a site that shows the MD5 so we can confirm the file, because flashing a corrupted kernel could harm our devices.:good:
[Xperia Z3 Compact Android Development] wind0zer:
Yes please. Or a zip file will do because Winzip or 7zip usually shows error while extracting.

OP says sound control driver isn't working. Use undervolt at your own risk. If it rebooted, try a lower value like -5 mv

Btw how do I get into Philz recovery? Up is for CWM, down is for TWRP. found it... camera button : )
[Xperia Z3 Compact Android Development] AndroPlus:
Changed to flashable zip and uploaded to BasketBuild which can show MD5;)
[Xperia Z3 Compact Android Development] wrwr:
Hello, is it possible to get the stock original kernel for Z3 Compact D5803 23.0.A.2.105 img (Not modified or rooted one ) to flash it via fastboot without restoring the whole stock ROM again? Thanks!
[Xperia Z3 Compact Android Development] AndroPlus:
You can create stock kernel flashe zip by extracting jernel.sin from ftf, then rename to boot.img and overwrite boot.img in the zip.
[Xperia Z3 Compact Android Development] wrwr:
Thanks AndroPlus, but there is two files: kernel.sin and fotakernel.sin, which one, and can I flash it via fastboot after renaming to boot.mg? easier than to include in a zip and flash via recovery.
[Xperia Z3 Compact Android Development] AndroPlus:
Oh I forgot to say you have to decrypt kernel.sin (not fotakernel) with Flashtool.

You can decrypt kernel.sin by "Tools" -> "Sin Editor" and select kernel.sin, then "Extract data".

Then you can flash kernel via fastboot:

fastboot flash boot kernel.elf
[Xperia Z3 Compact Android Development] wrwr:
Hey AndroPlus, I did all the steps OK, but when flashing (fastboot flash boot kernel.elf) I got this error via fastboot: FAILED (remote: image is not a boot image) ?
[Xperia Z3 Compact Android Development] AndroPlus:
hmm...I thought it can be done with fastboot, but it seems I'm wrong...

so you have to rename kernel.elf to boot.img and overwrite boot.img in zip, then install it.