Develop Bugs

Power button

My power button seems to be stuck. I'll push it and instead of powering off the screen, it acts like a long press and goes to the power off menu. I've noticed it with any of the roms I'm using too. Any ideas?
Sent from my PC36100 using XDA App

It's also not working when the screen is in sleep mode. Takes like seven presses for the unlock screen to show
Sent from my PC36100 using XDA App

Your power button is bad need to take it to sprint. Hardware issue fixed 0004 and 0003

I was afraid of that. So when the screen is sleeping it works fine now. Trying to get an awake screen to sleep is nigh impossible. Am I just SOL and have to unroot and take it into a service center?
Sent from my PC36100 using XDA App

richdogg112 said:
I was afraid of that. So when the screen is sleeping it works fine now. Trying to get an awake screen to sleep is nigh impossible. Am I just SOL and have to unroot and take it into a service center?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Pretty much just don't try to fix it your self other wise you will void your warranty. I never had that issue just a squeaky button on the past. I have a brand new evo right now tho no problems.

What are your radios and prl? Did you mess with the latest leaked radios ? If not then it is a power button issue not hard to unroot.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm testing out MIUI and checking how to update my PRL. But that's the current stuff. Thanks for your help by the way. Just did some research and I'll have to flash back to a sense based rom to update it which won't be hard at all to test that
Sent from my PC36100 using XDA App

I have used miui before cool rom. Looks like your using old prl. Update that. See if that fixes it what recovery are u using. Try amon 2.3
Amon is sweet for me I never have issues using it. Wipes everything correctly .

Using clockwork right now. I'll update the prl and get amon. I'll keep you posted on the result. In Ryder's eternal prophecy thread I found a zip that I keep on my sd that deletes everything so I run that too along with clockworks.
Sent from my PC36100 using XDA App

richdogg112 said:
Using clockwork right now. I'll update the prl and get amon. I'll keep you posted on the result
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
My guide has the link for it.
If all still fails I would try the latest Sprint lovers rom it updates everything for you radios and such. If still a no go then your button is messed up.

richdogg112 said:
Using clockwork right now. I'll update the prl and get amon. I'll keep you posted on the result. In Ryder's eternal prophecy thread I found a zip that I keep on my sd that deletes everything so I run that too along with clockworks.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
No need for it amon does it for you when you click on wipe scroll down on each part you wanna wipe and it will do it. No need for a script.

So I'm in clockwork (yes yes, I know, I'm about to switch over in three seconds if that's what it takes) and when I try to install the radio file from my sd it's giving me an installation aborted message.
"Amend scripting is no longer supported. Please switch to Edify scripting to create working update zip packages."
I have no idea what that means...
Update, until I find the time to take my phone in, I downloaded "No lock" which lets me turn the screen on from sleep mode with my volume buttons, then I downloaded "Screen off and Lock" which puts a command in my notification menu that if I click on it, it will make the phone sleep

K all you need is amon 2.3 rename it PC36IMG.ZIP boot into bootloader and it will install . To update prl just need a sense rom. Hope you get it fixed

Ok so I've unrooted and taking my phone in tomorrow. Should I wipe my SD too? I have my clockwork folder with backed up roms and other things that point to me having rooted.

richdogg112 said:
Ok so I've unrooted and taking my phone in tomorrow. Should I wipe my SD too? I have my clockwork folder with backed up roms and other things that point to me having rooted.
Click to expand...
Click to collapse
To be on the safe side i would tranfer everything to the computer. Then wipe the sd just in case.
Sent from My Nissan S14

I used Astro to go through and delete the folders. Didn't have time before work to copy them all over. I'll keep my fingers crossed

richdogg112 said:
I used Astro to go through and delete the folders. Didn't have time before work to copy them all over. I'll keep my fingers crossed
Click to expand...
Click to collapse
Next time just take it out, they dont need. (I used to be a tech)

I was looking for a spare micro SD around my place but I couldn't find one in time. Tech has my phone right now I'm about to go check on it in about an hour. Thanks for the heads up for next time though.

Follow up:
Either I deleted all signs or they didn't care. Either way they had to order another Evo and it will be here in a couple days. Thanks again for all the replies and can't wait to get my other Evo so I can root again. This standard look is for the birds.

Help Please - Bricked sprint gs3

hey guys hope someone can help. i tried to return my gs3 to stock after rooting it and putting a rom on it, so i used odin and i downloaded the stock tar file from the stock rom thread, and all seemed to go alright but when it rebooted in got stuck on the samsung screen. it shows the sprint bootup thing and galaxy s3 but then gets stuck on samsung screen. i can access download mode and i can install a custom recovery using odin but when i try to just flash a regular custom rom using custom recovery it does the same thing, it boots but gets stuck on samsung screen.
hope someone can help, thanks

Issacbourne said:
hey guys hope someone can help. i tried to return my gs3 to stock after rooting it and putting a rom on it, so i used odin and i downloaded the stock tar file from the stock rom thread, and all seemed to go alright but when it rebooted in got stuck on the samsung screen. it shows the sprint bootup thing and galaxy s3 but then gets stuck on samsung screen. i can access download mode and i can install a custom recovery using odin but when i try to just flash a regular custom rom using custom recovery it does the same thing, it boots but gets stuck on samsung screen.
hope someone can help, thanks
Click to expand...
Click to collapse
Boot into recovery and wipe data/factory reset

and, if you need to start over
http://forum.xda-developers.com/showpost.php?p=32172292&postcount=165

Naddict said:
and, if you need to start over
http://forum.xda-developers.com/showpost.php?p=32172292&postcount=165
Click to expand...
Click to collapse
I doubt he needs ro start over. Its seems he did everything right and just didnt wipe. Bet it boots right up if he wipes/resets

billard412 said:
I doubt he needs ro start over. Its seems he did everything right and just didnt wipe. Bet it boots right up if he wipes/resets
Click to expand...
Click to collapse
yes, but the information can only help ...just in case

Naddict said:
yes, but the information can only help ...just in case
Click to expand...
Click to collapse
Lol not like it matters. 100 bucks says this is one of them posts that never gets a confirmation from the op. Just have that feeling lmao :laugh:

billard412 said:
Lol not like it matters. 100 bucks says this is one of them posts that never gets a confirmation from the op. Just have that feeling lmao :laugh:
Click to expand...
Click to collapse
yuup,
you can either give them too much info, or not enough and there are like, one million posts about something that has already been posted about.
I see you constantly providing the same answers to very similar questions in the Q and A threads...People just don't search..nor read.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

thanks alot worked. i was gettin a little scared there for a sec lol.

billard412 said:
Lol not like it matters. 100 bucks says this is one of them posts that never gets a confirmation from the op. Just have that feeling lmao :laugh:
Click to expand...
Click to collapse
Looks like you lost $100 Sir :laugh:

dbenney said:
Looks like you lost $100 Sir :laugh:
Click to expand...
Click to collapse
Lol.. Did you get your issue worked out?
Sent from my SPH-L710 using xda premium

Naddict said:
Lol.. Did you get your issue worked out?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
yeah i did, it was such a simple thing, i was getting so frustrated cause ive rooted a million phones ya know, thought i knew what i was doing lol...but anyway, thanks again

Thanks from me too. I ran into this after trying to go to LI3 from the LIF JB leak. (LIF worked great for me but I need tethering so I'll have to wait a bit.)

no help so far-please think this through before shooting from the hip
Naddict said:
Lol.. Did you get your issue worked out?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I'm stuck with the dwonload mode showing. No combination of button strokes or battery removals seems to change the screen. The PC cant see the phone anymore. The only thing I can think of to do is let the battery discharge or put another battery in. I could write to the external sd card for whatever help that could offer. I don't know where the internal sd card is, do you? Why there is an sd card and an external sd card? My PC sees the so-called sd card as "phone." I'm feeling totally discouraged and disenchanted.

ODIN is your best friend
alt230 said:
I'm stuck with the dwonload mode showing. No combination of button strokes or battery removals seems to change the screen. The PC cant see the phone anymore. The only thing I can think of to do is let the battery discharge or put another battery in. I could write to the external sd card for whatever help that could offer. I don't know where the internal sd card is, do you? Why there is an sd card and an external sd card? My PC sees the so-called sd card as "phone." I'm feeling totally discouraged and disenchanted.
Click to expand...
Click to collapse
If you have download mode, then you are only soft bricked. You will need to download one of these oneclicks to make things as simple as possible: http://goo.im/devs/billard412/d2spr/ODIN-ONE-CLICKS/LJ7_Jellybean
Attach phone to computer usb, make sure your still in download mode and make sure it says COM (some number). Go take a 10 minute break or so and it will be working again. THANKS TO billard412 for uploading those files

My S3 says "upgrading" all the time

After updating the phone with an ATT update, every time I restart or boot up my device it says that "Android is upgrading". Does anyone have the same issue? How do I get rid of that?

MickeyS said:
After updating the phone with an ATT update, every time I restart or boot up my device it says that "Android is upgrading". Does anyone have the same issue? How do I get rid of that?
Click to expand...
Click to collapse
I suspect that the update didn't go quite right. It says that when the system is rebuilding your cache/dalvik cache. It sounds like maybe one or both of those is getting cleared when you shut down or they may not be getting built properly in the first place. I'd suggest backing up whatever you care about and doing a factory wipe. It can be a bit of a pain, but it'll probably solve your problem.
Also, bring on the details yo. Phone? Android version you came from/upgraded to? Aaaaaanything at all.

I has Android 4.0.4 and the latest update. It's a rooted phone and AT&T is my provider.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

Are you running a custom ROM? I agree, you should do a factory reset. Just be sure to back up your data beforehand.

smartnphone said:
Are you running a custom ROM? I agree, you should do a factory reset. Just be sure to back up your data beforehand.
Click to expand...
Click to collapse
No, I am not running a custom rom, all I have done to the phone is root it. What's the best way to back up your data? I useTitanium backup. How do I do a factory reset? I am new to the Android world and don't know much, any help will be greatly appreciated.

MickeyS said:
No, I am not running a custom rom, all I have done to the phone is root it. What's the best way to back up your data? I useTitanium backup. How do I do a factory reset? I am new to the Android world and don't know much, any help will be greatly appreciated.
Click to expand...
Click to collapse
What phone do you have? Titanium backups are fine. Make sure the backups are on an external SD card or get them off the internal flash. If you need to shuffle files around, you can use ES File Explorer but BE CAREFUL if you give it root privs for some reason. No offense, but since you're kinda new to this if you screw up and erase the wrong thing, stuff's gonna break. Without knowing who makes your phone, the best I can tell you is to go into settings and dig around for the factory reset. Good luck!

I fixed the first problem with the factory reset but now I can't connect the phone to my Mac using Android file transfer. Could the update had something to do with it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

MickeyS said:
I fixed the first problem with the factory reset but now I can't connect the phone to my Mac using Android file transfer. Could the update had something to do with it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I don't mean to be a jerk, but for god sake man/woman/person... For the 3rd time, what phone do you have? And yes, that's a good possibility...

He has said a S3 and ATT...I don't understand your question of what phone does he have?
Sent from my SGH-I747 using Tapatalk 2

m3741 said:
I don't mean to be a jerk, but for god sake man/woman/person... For the 3rd time, what phone do you have? And yes, that's a good possibility...
Click to expand...
Click to collapse
He did say s3 att my man.... And if not its in the s3 forum so it'd be a safe assumption it'd be an s3, and carrier for the steps he needs is regardless.
Sent from my SGH-I747 using Tapatalk 2

Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

Edit: ignore post.

corythug said:
He did say s3 att my man.... And if not its in the s3 forum so it'd be a safe assumption it'd be an s3, and carrier for the steps he needs is regardless.
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Apologies... I'm blind as hell apparently. No more late night XDA...

MickeyS said:
I fixed the first problem with the factory reset but now I can't connect the phone to my Mac using Android file transfer. Could the update had something to do with it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Like the other guy said, the update could be a possibility.
Reminds me when I had iPhones before I discovered Android. If you wanted to stay jailbroken, you'd have to make sure it's safe to do so before you update. Like you had to make sure it was iTunes safe, etc.

Did you install Google wallet?
Sent from my SAMSUNG-SGH-I747 using xda premium

So if AT&T has an update and your phone is rooted, don't update? I went ahead and updated without thinking about it. I am an iPhone user and didn't think that ATT had anything to do with Android OS. I took care of the upgrading issue, before the update I was able to use Android File Transfer with my Mac and I would connect to the phone, now forget about it. I can only do it now using VMware Fusion. Kies works but it's kind of limited. My next thing will be to install a ROM, but I can't find exactly what kind of phone I have. I know it's a Galaxy S3 from AT&T.
This is the information:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://forum.xda-developers.com/attachment.php?attachmentid=1402926&stc=1&d=1350272265
What kind of specific rom's I have to look for, I've herd that if you install the incorrect rom you will brick your phone.

Im not very familiar with mac or iOS but your problem sounds like a driver issue on the mac, not android. Is usb debugging enabled by chance? Settings>developer options>android debugging....if its on try turning off then reconnect your phone. If its off try turning it on and reconnect and see if it changes. Beyond that i would suggest deleting any samsung/android usb device druvers from the mac and reinstalling....although someone with more iOS experience will have to offer some advice in exactly how to do that if you dont know, i certainly dont.
As far as installing AT&T OTA updates with root, its generally not a good idea, especially if you do install a custom ROM. Even on a stock rooted ROM there is a pretty good chance the update will 'fix' your root access and if you are on a custom ROM there is probably an even better chance of screwing up the operating system to the point that it doesn't boot properly, or even brick. Only install updates to your ROM from the developer, and follow any instructions they give on how to apply the update.
Lastly, you are looking for AT&T i747 roms and you also have to pay attention to which version of android you are on as to how you go about installing the ROM. For instance if you are running the stock AT&T ROM and try to install an AOSP based rom without formatting the device you are more than likely to have all kinds of issues, IF the OS even boots properly. I would suggest you take some time to read up and become familiar with the terminology, differences in versions, etc with android before you just dive in. If you are unsure about something ASK SOMEONE...much better to look like a noob than standing in line at AT&T with a bricked phone.

I was under the impression that all of these show that when rebooting, its just a matter of how long it shows this message. I dont think anyone with a stock rom does NOT see this when they boot for a couple of seconds.

Any good place to begin looking for stock ROMS?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

[Q] R800x to R800i

Hi,
I just converted my R800x to an R800i by swapping the motherboards and the antennas on the middle housing. I got most of the pointers from 216Monster's excellent tutorial here-
http://forum.xda-developers.com/showthread.php?t=1547756
So here's the story; I bought a R800i from Australia that was an 'ex demo' model which doesn't read SIMs, but what I received was a beautifully mint Verizon R800x in a R800i box! After contacting the seller regarding her mistake, she vehemently denied the existence of the R800x, Verizon USA and CDMA technology in general :laugh: I was offered a full refund through eBay but since posting the phone back to Australia was troublesome, I decided to keep it with me and see what I could do with it. After reading 216Monster's tutorial, I decided to track another R800i down for parts. I found one that was essentially a motherboard and the middle housing for a decent amount and swapped the parts out last week. As a bonus, the previous owner had already rooted the phone and installed xdarkICS V0.1!:good:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This "chip" was loose on the R800i motherboard and subsequently fell off. I still have it but I don't know how it will be soldered on to the board again. What is it and what does it do? The phone works fine though.
I'll be updating to xdarkICS V0.2 as soon as I get a microSD.
Regards.
Jay.

What clock app is that in the screen pic? It looks nice
Sent from my Xperia Play (r800x)

It's an option offered in the widget. I'm still new to the whole Android scene so I can't say what's what. I'll post a photo of it if you like. This is my first 'SMART' phone after a Nokia 6600!:laugh: I still couldn't get over the fact that I had to retire my trusty Nokia 3310 though, I used it for nine years straight!

So...after using the Xperia for a couple of days, I've come across some faults that I need your help on.
1. Once the battery is low (30% or less/one quarter of battery life remaining), the touch screen becomes unresponsive and I can't unlock the homescreen.
2. I removed the battery to restart it after the touchscreen froze and the phone keeps loading to the CWM recovery screen. I reboot it through recovery but it always ends up at this screen. This has happened twice and the first time it booted properly after some time.
3. Sliding the gamepad out causes the phone to reboot.
I'm on V0.1 at the moment and I'm going to update to V0.2 tomorrow, anything special I need to know? I can't recall what Kernel version I've got though.
Regards.

JAY48 said:
So...after using the Xperia for a couple of days, I've come across some faults that I need your help on.
1. Once the battery is low (30% or less/one quarter of battery life remaining), the touch screen becomes unresponsive and I can't unlock the homescreen.
2. I removed the battery to restart it after the touchscreen froze and the phone keeps loading to the CWM recovery screen. I reboot it through recovery but it always ends up at this screen. This has happened twice and the first time it booted properly after some time.
3. Sliding the gamepad out causes the phone to reboot.
I'm on V0.1 at the moment and I'm going to update to V0.2 tomorrow, anything special I need to know? I can't recall what Kernel version I've got though.
Regards.
Click to expand...
Click to collapse
You should download flashtool if you havent already and download the stock ftf for your version. You can use this to get back to stock and you should flash it if you need to do a fresh install. That way there will be less problems and the Rom will be smoother.
Off topic: How is xdark ics Rom so far? Have you tried any games ion it? Are they smooth playing?
Sent from my Xperia Play (r800x)

Thanks for replying. This time the phone is stuck on DooMLorDs CWM-based recovery screen. I've been trying to get it to work all morning and it still comes back to this screen. I read online that a zip named "exitrecovery.zip" can be used to solve the CWMrecovery boot loop but it didn't work on mine. I downloaded Flashtool and R800i_4.0.2.A.0.58_Enhanced FTF so I'm just going to bring it back to stock for now.
I've read FMAs tutorials on this but is there anything I should know regarding kernels? I'm running DooMLord Kernel I think (The DooMLord logo appears when I boot the phone)

JAY48 said:
Thanks for replying. This time the phone is stuck on DooMLorDs CWM-based recovery screen. I've been trying to get it to work all morning and it still comes back to this screen. I read online that a zip named "exitrecovery.zip" can be used to solve the CWMrecovery boot loop but it didn't work on mine. I downloaded Flashtool and R800i_4.0.2.A.0.58_Enhanced FTF so I'm just going to bring it back to stock for now.
I've read FMAs tutorials on this but is there anything I should know regarding kernels? I'm running DooMLord Kernel I think (The DooMLord logo appears when I boot the phone)
Click to expand...
Click to collapse
Well you should just pull the battery and flash the ftf then do a fresh install of everything then you probably won't have any problems
Sent from my Xperia Play (r800x)

abdel12345 said:
Well you should just pull the battery and flash the ftf then do a fresh install of everything then you probably won't have any problems
Sent from my Xperia Play (r800x)
Click to expand...
Click to collapse
Hi,
Thanks for replying. I used flashtool and flashed the enhanced 0.58 ftf but I still get the recovery screen. I then continued to flash the V0.2 xDark ICS ROM but still no improvement. I followed this tutorial for the ftf flash-
http://forum.xda-developers.com/showthread.php?t=2054486
Did everything it says and checked the "exclude kernel" box. Is my problem something to do with my kernel? At this moment I just want the phone to work!
Regards.

I would try changing the kernel, see if it solves the cwm problems, then go back to stock.
Sent from my R800at using xda app-developers app

korrectmethod said:
I would try changing the kernel, see if it solves the cwm problems, then go back to stock.
Sent from my R800at using xda app-developers app
Click to expand...
Click to collapse
Yeah try using lupus ics and gb v5 kernel. Im using it now and it works fine
Sent from my Xperia Play (r800x)

korrectmethod said:
I would try changing the kernel, see if it solves the cwm problems, then go back to stock.
Sent from my R800at using xda app-developers app
Click to expand...
Click to collapse
Yes, that occurred to me as well. I don't know what kernel to flash though. I will be attempting to flash this kernel (DooMLorD's)
http://forum.xda-developers.com/showthread.php?t=1176502
I'm open to suggestions so let me know if you know of a different/appropriate kernel.
I'm also downloading "R800i_4.0.2.A.0.58_Generic Hong Kong Trade.ftf" as well in case the "R800i_4.0.2.A.0.58_Enhanced.ftf" I've been flashing through Flashtool has something wrong with it.
Regards.
EDIT: Just saw abdel12345's reply. Is this the kernel you mentioned?
http://forum.xda-developers.com/showthread.php?t=2167766
I'll give it a go. How do you go about flashing it? The instructions are a bit complicated! Also, what are the two MD5 versions mentioned there?

Flash the ftf again, but don't check the exclude kernel box, because if you check it, it will keep your Kernel and the phone won't boot
Sent from my R800i using xda app-developers app

Thanks for the suggestion, funnies7. So what will the current kernel be replaced with if I don't check the "exclude kernel" box? Stock or a Custom Kernel?
Regards.

So, after flash the ftf, before turn on the phone I recommend you to flash doomkernel v14 and then turn on the phone, on first boot don't touch it for 5 minutes, after that reboot it, complete the setup wizard, you will notice some lag, don't worry just download no frills app from playstore give it root permissions and change the max voltage to 1,1Ghz and this is it :thumbup:
Sent from my R800i using xda app-developers app

But he wants xdark ics so yes you should flash the kernel I told you about. Do what he said and flash the ftf then flash lupus kernel. After that wipe data, cache, and dalvik cache with cwm then flash the xdark ics Rom you wanted with cwm. Let it sit for a little to settle in and you'll be fine. But ics isn't that good for gaming so heavy games like gta will probably give you lag
Sent from my Xperia Play (r800x)

abdel12345 said:
But he wants xdark ics so yes you should flash the kernel I told you about. Do what he said and flash the ftf then flash lupus kernel. After that wipe data, cache, and dalvik cache with cwm then flash the xdark ics Rom you wanted with cwm. Let it sit for a little to settle in and you'll be fine. But ics isn't that good for gaming so heavy games like gta will probably give you lag
Sent from my Xperia Play (r800x)
Click to expand...
Click to collapse
Thank you both! I found out what MD5 is and how to check it and the Lupus kernel I downloaded matched. Now my question is, how do you flash this Lupus kernel? I re-read the thread over and over again and I still can't figure out how it's done.
Can it be done through Fastboot? (similar to DoomKernel flashing)?
Regards.

Yes You can flash it the same way as doomkernel :thumbup:
Sent from my R800i using xda app-developers app

Thanks. So the phone boots up after the enhanced FTF was flashed along with the stock kernel. Now it seems my touch screen isn't working! I don't understand it, it was working fine on Sunday just before it froze on me and started booting to the CWM recovery. Do you think it's a software related issue? Is it because I flashed 0.58.?
EDIT: I flashed LuPuS Stock GB+ICS kernel through Fastboot and I can get to the home screen. Problem is my touch screen is still unresponsive! It started working once but that's it. I'll be flashing xDarkV0.2 or ICS Express in the afternoon, I'll post my results here. I got into LuPuS CWM recovery and did a factory reset but still no touchscreen! Very frustrating.
I'm about to flash xDark now because I can't download ICS express through the xda page (mega.co.nz won't work).
Regards.

JAY48 said:
Thanks. So the phone boots up after the enhanced FTF was flashed along with the stock kernel. Now it seems my touch screen isn't working! I don't understand it, it was working fine on Sunday just before it froze on me and started booting to the CWM recovery. Do you think it's a software related issue? Is it because I flashed 0.58.?
EDIT: I flashed LuPuS Stock GB+ICS kernel through Fastboot and I can get to the home screen. Problem is my touch screen is still unresponsive! It started working once but that's it. I'll be flashing xDarkV0.2 or ICS Express in the afternoon, I'll post my results here. In the meantime, I tried getting into recovery but I couldn't. I tried holding the 'Back' key while powering up and volume down while powering up. I get two small vibrations while holding the 'back' key but no recovery. Am I missing something?
Thanks for replying!
Regards.
Click to expand...
Click to collapse
I don't know what's up with the touchscreen. It deems like a digitizer problem. But for recovery keep pressing the volume down button when the phone vibrates while turning on.
Sent from my Xperia Play (r800x)

Thanks for that! I flashed xDark V0.2 without a problem but still no touchscreen. I'm going to take the phone apart and see why it's unresponsive.
So going through system information, I am told that my device is a R800x! It's supposed to say R800i, isn't it? The SIM is in and I can take/receive calls though. Here's what it says-
Model Number R800x
Android version 4.0.3
Kernel Lupus stock gb+ics-v5
Build number XDark ICS V0.2
Why is it identifying my device as an R800x?

N5X shows only colorful static when turned on

Hi,
I am having a serious problem with my Nexus 5x:
After installing the new AOSPA today, I wiped data, cache and dalvik and then tried to boot the phone (up to that point, everything was ok). Instead of showing the usual "google" logo with the warning about the unlocked bootloader , the screen just shows some colorful static (i'll attach a photo of that).
So, I can't boot the phone. It's recognized in fastboot mode by the computer, but the screen doesn't show anything. Same goes for recovery (TWRP), I can talk to the phone via ADB but the screen remains black.
I've tried everything I can, including reverting the software to stock (see Heisenberg's guide) but without wiping the personal data.
Do you have any idea what I could do to get my phone back except relocking the bootloader and sending it in for repair?
Thanks a lot!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: RMA'd the phone, they had to replace the screen / touch unit (obviously) and the camera (?) for some reason

dbahn25 said:
Hi,
I am having a serious problem with my Nexus 5x:
After installing the new AOSPA today, I wiped data, cache and dalvik and then tried to boot the phone (up to that point, everything was ok). Instead of showing the usual "google" logo with the warning about the unlocked bootloader , the screen just shows some colorful static (i'll attach a photo of that).
So, I can't boot the phone. It's recognized in fastboot mode by the computer, but the screen doesn't show anything. Same goes for recovery (TWRP), I can talk to the phone via ADB but the screen remains black.
I've tried everything I can, including reverting the software to stock (see Heisenberg's guide) but without wiping the personal data.
Do you have any idea what I could do to get my phone back except relocking the bootloader and sending it in for repair?
Thanks a lot!
Click to expand...
Click to collapse
This looks like a display failure unfortunately. I don't know if there's anything more you can do except RMA since you flashed the factory image. Could you post the file name of the AOSPA rom zip that you flashed?
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
This looks like a display failure unfortunately. I don't know if there's anything more you can do except RMA since you flashed the factory image. Could you post the file name of the AOSPA rom zip that you flashed?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Oh no :crying: how could that be from just flashing a new rom (+ gapps)? I didn't do anything differently from all the other times I flashed my ROM..... Was it really just bad luck?
I flashed the AOSPA build from 6/6/16 (pa_bullhead-6.0-20160606-signed.zip) with BaNkS gapps (BaNkS_Dynamic_GApps_6.x.x_6-7-16_23_51.zip)
I guess it'd be best to lock the bootloader for the RMA, wouldn't it?

dbahn25 said:
Oh no :crying: how could that be from just flashing a new rom (+ gapps)? I didn't do anything differently from all the other times I flashed my ROM..... Was it really just bad luck?
I flashed the AOSPA build from 6/6/16 (pa_bullhead-6.0-20160606-signed.zip) with BaNkS gapps (BaNkS_Dynamic_GApps_6.x.x_6-7-16_23_51.zip)
I guess it'd be best to lock the bootloader for the RMA, wouldn't it?
Click to expand...
Click to collapse
On the P.A website and Google post it says they highly recommend using open gapps perhaps Ur issue is related to that??? I'm no expert is there anyway u can sideload the ROM and open gapps via adb ???
Sent from my Nexus 5X using XDA-Developers mobile app

dog121 said:
On the P.A website and Google post it says they highly recommend using open gapps perhaps Ur issue is related to that??? I'm no expert is there anyway u can sideload the ROM and open gapps via adb ???
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
No... they say you should use banks instead of open gapps since those might make problems. That's the reason I didn't use the open gapps
I'm not sure about the sideloading though, I've never done that. Do you have a guide for me?

dbahn25 said:
No... they say you should use banks instead of open gapps since those might make problems. That's the reason I didn't use the open gapps
I'm not sure about the sideloading though, I've never done that. Do you have a guide for me?
Click to expand...
Click to collapse
Have a look at this...
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
I suggest you get the latest update that just came out via Google updates for Nexus 5x and give that a whirl....
I hadn't realised that P.A changed the gapps yesterday they were using open gapps...
Sent from my Nexus 5X using XDA-Developers mobile app

dog121 said:
Have a look at this...
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
I suggest you get the latest update that just came out via Google updates for Nexus 5x and give that a whirl....
I hadn't realised that P.A changed the gapps yesterday they were using open gapps...
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
Alright, thanks! Unfortunately, I've already shipped my phone back to repair / replacement. But I wonder, is there any advantage of using sideload over using fastboot to flash the stock image?
Also I don't think it would've worked since I couldn't have enabled sideload without seeing anything on screen (it was completely black while in recovery).

dbahn25 said:
Also I don't think it would've worked since I couldn't have enabled sideload without seeing anything on screen (it was completely black while in recovery).
Click to expand...
Click to collapse
It can be done, just need to look at screenshots someone else posts of the recovery menu and count.