So after flashing rooted tot file to my h961s I've tried to change dpi and got this message "Unfortunately system ui has stopped" comming all the time. Tried to hard reset but no change. Could someone help me with advice?
adb into it, if you can (ie: authorized a computer) and do this:
wm density 640
then reboot
otherwise you'll likely need to reflash stock
---------- Post added at 03:54 PM ---------- Previous post was at 03:54 PM ----------
additionally, there are threads in tmobile lg v10 about the dpi changes
edit: since the tot file is prob the system/ it too might reset the lcd back to 640...
garfield1022 said:
adb into it, if you can (ie: authorized a computer) and do this:
wm density 640
then reboot
otherwise you'll likely need to reflash stock
---------- Post added at 03:54 PM ---------- Previous post was at 03:54 PM ----------
additionally, there are threads in tmobile lg v10 about the dpi changes
edit: since the tot file is prob the system/ it too might reset the lcd back to 640...
Click to expand...
Click to collapse
Hi there, thank you for the response. The problem is that I can't reach any settings because of constant errors. When I flashed that rooted tot file previously I ticked oem unlock and usb debugging. Now I can't do that and lg up utility doesn't recognize the phone.
can't you go into download mode (volume up) and reflash?
Sayttpls said:
So after flashing rooted tot file to my h961s I've tried to change dpi and got this message "Unfortunately system ui has stopped" comming all the time. Tried to hard reset but no change. Could someone help me with advice?
Click to expand...
Click to collapse
Hi I to flashed the rooted tot file to my h961, then moments after I changed dpi and got the same message. Did you ever find a fix?
Related
Well, I don't know what to do.
A day ago my phone was running the Optimus Bean custom rom based on v10i and it was running perfectly.
When I flashed this rom I had no problems with the kdz flasher. So yesterday I decided to flash the SimpleBlue rom by snx based on v10k, but everytime I get this error: "wparam 100 lparam 4010" or "MOD UptestEX MFC application has stopped working". I thought it might be the custom rom that was corrupt or something so I tried to flash my phone back to stock v10i. Still getting the same errors (with every .kdz file I use). Since my phone is stuck in the emergency screen I can't do anything but use the kdz flasher.
Please, somebody help!
me too!
well mine was running at V10i as well but not on bean, did everything that was said at this post
http://forum.xda-developers.com/showthread.php?t=2176430
then my phone went to the same state as yours, if you have any solution that we could work this out hopefully,
---------- Post added at 04:22 PM ---------- Previous post was at 03:39 PM ----------
cherudim1 said:
well mine was running at V10i as well but not on bean, did everything that was said at this post
http://forum.xda-developers.com/showthread.php?t=2176430
then my phone went to the same state as yours, if you have any solution that we could work this out hopefully,
Click to expand...
Click to collapse
how could we solve this problem?
how?
cherudim1 said:
well mine was running at V10i as well but not on bean, did everything that was said at this post
http://forum.xda-developers.com/showthread.php?t=2176430
then my phone went to the same state as yours, if you have any solution that we could work this out hopefully,
---------- Post added at 04:22 PM ---------- Previous post was at 03:39 PM ----------
how could we solve this problem?
Click to expand...
Click to collapse
i tried updating it online but nothing still gets to work, it wont update or flash, so frustrating!
I don't know how, but I repaired it!
cherudim1 said:
i tried updating it online but nothing still gets to work, it wont update or flash, so frustrating!
Click to expand...
Click to collapse
I used every PC in our household and it still didn't work. My mum kept telling me "It's a virus bla bla". I didn't belive her 'cause the kdz flasher wasn't infected. My mum did a scan anyway and deleted malware. I tried it again and IT WORKED! Very weird though.
I don't use the kdz flasher now since our phone now has CWM. We can flash .zip now, it's easier ad faster. I would recommend doing a full PC scan and turning off any virus or firewall software running in the background. Then try it again If it worked, flash CWM as soon as possible, then you can always go into recovery and you won't have to worry about that old yellow emergency screen!
I'm quite worried I soft bricked my phone. I am new to a rooted android device. I am more used to an unlocked windows mobile. Here is what I did...
I rooted my handset using blackwofls guide, it worked perfectly. I then installed adfree android from the market, it also worked perfectly.
After that, I went and got font installer, it installed like any other app, opened fine. I chose a font I wanted to use, previewed it, and installed it.
It had prompted me to reboot for the font to take effect. After rebooting my phone will no longer go past the AT&T splash screen. I am very worried since I do not know how to fix it, I don't have a backup of my ICS of any sort. I can however get into ODIN and the recovery mode of clockwork.
I reset my cache and data numerous times, and i did a factory reset, it didn't help me. It just sits at the splash screen and vibrates often. Please help me.
I got you covered man.
---------- Post added at 02:47 AM ---------- Previous post was at 02:44 AM ----------
http://d-h.st/ozL
thanks
ian577416 said:
I got you covered man.
---------- Post added at 02:47 AM ---------- Previous post was at 02:44 AM ----------
link removed due to being a new member
Click to expand...
Click to collapse
This is actually what I had used to fix it. I appreciate your response and help in solving my issue.
Me too
brallyn said:
This is actually what I had used to fix it. I appreciate your response and help in solving my issue.
Click to expand...
Click to collapse
The link was deleted. Could someone please tell me what it was/where it went?
Thanks in advance.
After several frustrating attempts I have finally unlocked the bootloader, rooted the phone, and installed CM 10.1 However, the touch screen is still messed up. I have flashed both Lelu's fix and the v20f u-boot fix from recovery but neither seemed to have corrected the problem. I didn't see any security errors while flashing them either. So where do I go from here?
ozlo said:
After several frustrating attempts I have finally unlocked the bootloader, rooted the phone, and installed CM 10.1 However, the touch screen is still messed up. I have flashed both Lelu's fix and the v20f u-boot fix from recovery but neither seemed to have corrected the problem. I didn't see any security errors while flashing them either. So where do I go from here?
Click to expand...
Click to collapse
u need to go into cwm and flash the touch screen fix i had that same issue and i got it working .
Which touch screen fix are you referring to? The Lelu ts fix? I've already tried that to no avail. The screen is displaying correctly but the sensor for the touch screen is still inverted.
I solved my problem, thanks in part to this thread here: http://forum.xda-developers.com/showthread.php?t=2182867&highlight=radio&page=10&nocache=1
Basically I copied v6.bin onto the sd card. I then was able to connect to the phone via adb and issued the following commands:
Code:
adb shell
su
cat /sdcard/v6.bin > /sys/devices/virtual/input/lge_touch/firmware
reboot
I flashed a cwm file to fix my touch screen. It was the cmw touch file that came with the l9 9769 folder.
Sent from my LG-P769 using xda app-developers app
---------- Post added at 07:04 AM ---------- Previous post was at 07:03 AM ----------
The file I flashed was called "cwm_ts_fix_p769." It was a zip file.
---------- Post added at 07:05 AM ---------- Previous post was at 07:04 AM ----------
Just read where you said you solved your problem. Sorry.
I need your help big time guys!! I edited my build.prop file. Now when I boot into my phone, its stuck and wont go past the Samsung galaxy logo. I read that i could use ADB. I got 2 questions:
1) I got the original copy of the build.prop file on my PC. How do I transfer it from my PC to the phone?
2) Is it possible to flash the same rom without affecting any of the data on my phone? If so, how?
If you have custom recovery installed in your device, flash the ROM that you are using, clear cache and dalvik cache and you would be good to go
---------- Post added at 08:03 AM ---------- Previous post was at 08:01 AM ----------
If you do push the old build.prop and restart, you may again stuck in black screen. Push it to system via adb
utsha.saha.58 said:
If you have custom recovery installed in your device, flash the ROM that you are using, clear cache and dalvik cache and you would be good to go
---------- Post added at 08:03 AM ---------- Previous post was at 08:01 AM ----------
If you do push the old build.prop and restart, you may again stuck in black screen. Push it to system via adb
Click to expand...
Click to collapse
I copied a stock rom onto the sd card. then I put the sd card back in my phone. I then tried to flash it through TWRP. But I that didnt work. I dont know if I'm doing this right, FYI. It just just doesnt go past the samsung logo.
I got ADB installed. But I dont know how exactly to use it. But my PC and Odin dont recognize the phone. I really dont understand why. This is getting to be insane. I need some serious help. What do you suggest i do?
Please reinstall drivers again and try odin
utsha.saha.58 said:
Please reinstall drivers again and try odin
Click to expand...
Click to collapse
I did! But again, the PC and Odin dont recognize my phone! What do I do?
Hmn.... You got yourself quite a trouble! Can you grab a logcat and send it?
utsha.saha.58 said:
Hmn.... You got yourself quite a trouble! Can you grab a logcat and send it?
Click to expand...
Click to collapse
I fixed it. Appreciate your time and attentions.
Good job!! mind to tell how you fixed it?
utsha.saha.58 said:
Good job!! mind to tell how you fixed it?
Click to expand...
Click to collapse
It just rebooted on its own.. very strange!
Hahaha, you are very lucky man! Have fun!
utsha.saha.58 said:
If you have custom recovery installed in your device, flash the ROM that you are using, clear cache and dalvik cache and you would be good to go
---------- Post added at 08:03 AM ---------- Previous post was at 08:01 AM ----------
If you do push the old build.prop and restart, you may again stuck in black screen. Push it to system via adb
Click to expand...
Click to collapse
Hey I got one more question for you. Do you know where I can get the most updated black themed play store apk? I want to make the play store dark. Thanks man, looking forward to your reply.
There you go
http://androidcommunity.com/google-...-back-to-black-color-theme-download-20130410/
utsha.saha.58 said:
There you go
http://androidcommunity.com/google-...-back-to-black-color-theme-download-20130410/
Click to expand...
Click to collapse
Hey thanks man. I actually got the TBO updater that lets me download dark gapps. But I'll keep your link handy in case the TBO dark theme becomes obsolete. Thanks!!!
You are welcomed!
Hi guys,
My nexus 9 WIFI is stuck at the loading screen after I attempted an OTA update. I'd like to get it back to the way it was without wiping data.
I have TWRP as recovery and a custom kernel.
Because of this. my tablet stopped flashing the monthly security updates.
I installed FlashFire to install an OTA. which I downloaded from:
https://developers.google.com/android/nexus/ota#volantis
I picked the MOB30G version as I have the MOB30D currently installed.
Anyway, I ran FlashFire and selected the OTA zip and ran the process. It looked like it worked and then it rebooted.
It then got stuck on the loading screen.
I can still get into recovery if I want to flash a clean install but I'd rather not lose my date. Is there a way I can get this working? Maybe flash stock recovery and then install the OTA via ADB (instructions?)?
Thanks for any help.
Get the latest factory image and use fastboot to flash it. Can be done without wiping data.
Just don't use flash-all script without modifying it, so it doesn't wipe.
---------- Post added at 08:09 PM ---------- Previous post was at 08:03 PM ----------
The link you provided have full OTA images and you could have picked the latest MOB30M
OK I fixed it by flashing the FIRE-ICE kernel again. I think the OTA flash did something to it.
Can you help me?
corkiejp said:
Get the latest factory image and use fastboot to flash it. Can be done without wiping data.
Just don't use flash-all script without modifying it, so it doesn't wipe.
---------- Post added at 08:09 PM ---------- Previous post was at 08:03 PM ----------
The link you provided have full OTA images and you could have picked the latest MOB30M
Click to expand...
Click to collapse
can you help me with my phone i have the same problem and i really need help my phone keeps vibrating when its on the bootscreen. can you pls get back to me asap pls! Thanks
---------- Post added at 08:11 AM ---------- Previous post was at 08:04 AM ----------
mykiller454 said:
can you help me with my phone i have the same problem and i really need help my phone keeps vibrating when its on the bootscreen. can you pls get back to me asap pls! Thanks
Click to expand...
Click to collapse
forgot to mention that my phone is samsung galaxy core prime
@mykiller454 You would be better off posting and looking for help in your device forum. If there is one.