Whenever I restart my phone the brightness automatically goes to 100% rather than sticking to whatever percentage I left it before restarting it. My screen timeout also goes back to 5 minutes (original) rather than whatever I have changed it to. Is this a bug in my phone or is this the standard feature for the G2? Sorry couldn't find anything in the search results. I am using the D802 variant.
100% Stock?
LenAsh said:
100% Stock?
Click to expand...
Click to collapse
Stock ROM, phone is rooted and no custom recovery installed. I am using Xposed Modules but even after disabling all of them the brightness went to 100% after rebooting. I just noticed, the brightness stays the same as before until I unlock the phone, then it automatically goes up to 100%.
All I would say is, Stock doesn't do this.
Since you don't have custom recovery, you cannot try a Cache wipe. You could try a factory reset though.
LenAsh said:
All I would say is, Stock doesn't do this.
Since you don't have custom recovery, you cannot try a Cache wipe. You could try a factory reset though.
Click to expand...
Click to collapse
Thank you. Also, I may as well get this question here since I've been meaning to ask it.
I have only used Nexus/Samsung devices before where the bootloader could be unlocked/locked easily, therefore I could quickly unroot and go back to stock recovery for OTA updates and such. I have read here that if I install a custom recovery I cannot use OTA updates. My question is how can I go back to unrooting and stock recovery? I have seen the stock firmware thread which I think would unroot the device but will it also make the recovery go back to stock?
You just flash one of the stock kdz files. See stickie in General
Sent from my LG-D802 using XDA Premium 4 mobile app
LenAsh said:
You just flash one of the stock kdz files. See stickie in General
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK that's a relief then, thanks for your help and I'll try a factory reset or using a stock kdz file.
Sometimes disabling the exposed modules alone isn't enough, have to use return option disabling exposed entirely. Flash file is in sd parent directory. Flash the zip. OTA isn't currently worth the troubles. Block em atm. Xposed (everything really) plays much nicer with SuperSU btw.
Insert Sim Card?
jayzfan1 said:
Whenever I restart my phone the brightness automatically goes to 100% rather than sticking to whatever percentage I left it before restarting it. My screen timeout also goes back to 5 minutes (original) rather than whatever I have changed it to. Is this a bug in my phone or is this the standard feature for the G2? Sorry couldn't find anything in the search results. I am using the D802 variant.
Click to expand...
Click to collapse
That's not what's supposed to be. Does it happen every reboot?
My G2 brightness jumped to max or fell to min brightness only for a couple of times within the first a few days after activation. I used AndroSensor and Lux auto brightness to find out its light sensor and inertia sensors were shut down when that happened (yes screen auto rotation went off, too). Maybe that's due to indoor/outdoor steep temperature changes. A power off and on solves that.
http://forum.xda-developers.com/showthread.php?t=2570189
Mine does it as well. It is not full brightness but the auto brightness that takes a long time to kick in.
Sent from my LG-D802 using Tapatalk
I searched on Google about this exact behavior and found this post.
I just got an LG G2 before yesterday from someone else who bought it in January (I checked warranty info) and it was fully stock and not rooted. I factory reset it 3 times and each time I reboot it still goes to 100% brightness even though I had it around 50%. At least it doesn't go to 100% while using it normally! phew lol. Then I'd be worried. But it's only after a reboot. That's a weird behavior. I had lots of phones and none did that.
I had the same problem only when the simcard wasn't inserted.
me too had same problem before, now it is disappeared, maybe virus problem
Xenovias said:
Insert Sim Card?
Click to expand...
Click to collapse
That was the reason on my situation. Thanks!
Related
Something strange happened today.
My N4 changed a lot of things with no reasons:
1) home button stopped working
2) no notifications at all on notification bar
3) when i hold power button only show "turn off" and no more the other options
What may be the cause of that?
campanate said:
Something strange happened today.
My N4 changed a lot of things with no reasons:
1) home button stopped working
2) no notifications at all on notification bar
3) when i hold power button only show "turn off" and no more the other options
What may be the cause of that?
Click to expand...
Click to collapse
have you tried rebooting?
also, you will have to give us more info, like what rom, kernel, any mods/themes, your setup, etc..
simms22 said:
have you tried rebooting?
also, you will have to give us more info, like what rom, kernel, any mods/themes, your setup, etc..
Click to expand...
Click to collapse
already rebooted a few times..
I am all stock, but rooted.
Very strange what is going on...
campanate said:
already rebooted a few times..
I am all stock, but rooted.
Very strange what is going on...
Click to expand...
Click to collapse
I have no notification icons on the top bar as well, but i have some apps running on background that should appear there.
Is there a reboot method like when we remove the battery?
If you have a custom recovery and can get into it have you tried wiping cache and dalvik? Or a factory reset?
Sent from my Nexus 4 using xda app-developers app
I dont have a custom recovery.
How do i do a factory reset?
campanate said:
I dont have a custom recovery.
How do i do a factory reset?
Click to expand...
Click to collapse
BTW, do i lose root factoring reset?
In settings it is under backup and restore I believe will have the option. Keep in mind it erases your data so if you have anything you want to keep back it up first.
Sent from my Nexus 4 using xda app-developers app
I think i know what happened. This is a very strange bug but it happens once in a while.
Whenever you flash gapps or flash the stock rom your phone boots up into a setup mode which blocks alot of things and limits itself . Once your all done with the setup your phone then changes a file in the system or deletes it that keeps the phone from going into setup mode again. Your phone seems to be in this so called setup mode because the home button doesnt work, only power off option, and no notifications, this is the behavior of the setup. Your phone might have changed that file or replaced it.
I dont think a factory reset will help anything as its in the system, i might be wrong but you should try it first and if you cant get it to work then just flash stock again. This has happened to me a few times before and i have resolved it by just reflashing the stock rom. Im not sure what the cause is but i guess its just a random chance that you get this.
Also no you dont loose root if you factory reset.
That is a strange bug I've never heard of that you may be right but a factory reset should force him to go through set up again which could fix that. I didn't suggest re flashing since he stated he didn't have a custom recovery.
Sent from my Nexus 4 using xda app-developers app
Hyperrunner said:
I think i know what happened. This is a very strange bug but it happens once in a while.
Whenever you flash gapps or flash the stock rom your phone boots up into a setup mode which blocks alot of things and limits itself . Once your all done with the setup your phone then changes a file in the system or deletes it that keeps the phone from going into setup mode again. Your phone seems to be in this so called setup mode because the home button doesnt work, only power off option, and no notifications, this is the behavior of the setup. Your phone might have changed that file or replaced it.
I dont think a factory reset will help anything as its in the system, i might be wrong but you should try it first and if you cant get it to work then just flash stock again. This has happened to me a few times before and i have resolved it by just reflashing the stock rom. Im not sure what the cause is but i guess its just a random chance that you get this.
Also no you dont loose root if you factory reset.
Click to expand...
Click to collapse
forvrknight said:
That is a strange bug I've never heard of that you may be right but a factory reset should force him to go through set up again which could fix that. I didn't suggest re flashing since he stated he didn't have a custom recovery.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I appreciate both tips.
I am trying a factory reset this afternoon.
After that i am going to post a feedback right here.
Thanks.
No matter what I do... no matter what ROM I flash to, and I have tried 4 different ROMs, I keep getting the UI Stops Working error and then my phone is virtually non-functional. The notifications, navigation, and launcher bars go away and I cannot do anything. The only thing that I can do is boot into recovery and then flash a new ROM, BUT I have been doing this a couple times a day.
I even formatted my entire phone, internal storage and all, started completely over AND YET I still get the issue. What can I do???
System UI errors
alwaysbelieve1 said:
No matter what I do... no matter what ROM I flash to, and I have tried 4 different ROMs, I keep getting the UI Stops Working error and then my phone is virtually non-functional. The notifications, navigation, and launcher bars go away and I cannot do anything. The only thing that I can do is boot into recovery and then flash a new ROM, BUT I have been doing this a couple times a day.
I even formatted my entire phone, internal storage and all, started completely over AND YET I still get the issue. What can I do???
Click to expand...
Click to collapse
Did you freeze any of your system apps?
mcapozzi said:
Did you freeze any of your system apps?
Click to expand...
Click to collapse
The only ones that I can think of are the live wallpaper ones, Email Exchange since I don't need it, and face unlock. I also froze the NFC. I wouldn't think that would cause it. I was reading on the internet that the Facebook app can cause it so I deleted the app and we will see.
---
Sent using my Droid Razor M- THE BEST SMARTPHONE ON THE PLANET!
Heard about Kettlebells... learn more: http://synergykettlebell.com
Launcher
alwaysbelieve1 said:
The only ones that I can think of are the live wallpaper ones, Email Exchange since I don't need it, and face unlock. I also froze the NFC. I wouldn't think that would cause it. I was reading on the internet that the Facebook app can cause it so I deleted the app and we will see.
---
Sent using my Droid Razor M- THE BEST SMARTPHONE ON THE PLANET!
Heard about Kettlebells... learn more: http://synergykettlebell.com
Click to expand...
Click to collapse
What launcher are you using?
-Mike
mcapozzi said:
What launcher are you using?
-Mike
Click to expand...
Click to collapse
Nova Prime
alwaysbelieve1 said:
Nova Prime
Click to expand...
Click to collapse
You didn't by chance accidentally freeze the stock launcher?
-Mike
mcapozzi said:
You didn't by chance accidentally freeze the stock launcher?
-Mike
Click to expand...
Click to collapse
No
Here is a thread regarding the issue, but none of the "fixes" worked for me: http://forums.androidcentral.com/sa...0371-unfortunately-system-ui-has-stopped.html
I deleted Facebook so we shall see if that does the trick.
When this happened to me I used Matt's utility option 1... rooted it updated it n made a TiB of everything... now when I tinker n it gets wonky I restore the systemui.apk n reboot... I know you said that you started over does that mean you used rsd and flashed stock... or did you go through a recovery to do the wiping formatting n what not?
Sent from my XT907 using xda app-developers app
Had this happen the other day and this is what I did. I rebooted the phone WHILE HOLDING THE VOLUME DOWN KEY. it boots into safe mode. While in there make a TiBu of your apps. Then boot into recovery and factory data/reset like 3 times, flash back to a ROM and restore your apps. This way you don't lose your stuff.
Sent from my XT907 using Tapatalk 4
ezknives said:
When this happened to me I used Matt's utility option 1... rooted it updated it n made a TiB of everything... now when I tinker n it gets wonky I restore the systemui.apk n reboot... I know you said that you started over does that mean you used rsd and flashed stock... or did you go through a recovery to do the wiping formatting n what not?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
When I meant started over I was yes referring to the booting to recovery and then wiping/formatting everything, then reflashing a ROM. That works, but I just am nervous now because the issue persists no matter the ROM. Sometimes it takes a day or two or sometimes it happens even quicker than that. I think it might be Facebook so I am not installing that app again. Why FB works on my Nexus 7 tablet and my wife's phone just fine is beyond me.
I didn't know I can make a backup of systemui.apk and restore it to make it work. I wish we could find the main issue to begin with so we can resolve this once-and-for-all.
evastonian said:
Had this happen the other day and this is what I did. I rebooted the phone WHILE HOLDING THE VOLUME DOWN KEY. it boots into safe mode. While in there make a TiBu of your apps. Then boot into recovery and factory data/reset like 3 times, flash back to a ROM and restore your apps. This way you don't lose your stuff.
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Yes that is exactly what I do every time. Today I started completely fresh and installed everything manually so I can better narrow down any issues.
alwaysbelieve1 said:
When I meant started over I was yes referring to the booting to recovery and then wiping/formatting everything, then reflashing a ROM. That works, but I just am nervous now because the issue persists no matter the ROM. Sometimes it takes a day or two or sometimes it happens even quicker than that. I think it might be Facebook so I am not installing that app again. Why FB works on my Nexus 7 tablet and my wife's phone just fine is beyond me.
I didn't know I can make a backup of systemui.apk and restore it to make it work. I wish we could find the main issue to begin with so we can resolve this once-and-for-all.
Click to expand...
Click to collapse
Yea I backup everything on my external hard drive (that after I back anything up I bubble wrap and put in my fire safe< a bit paranoid) every week, so that if anything happens I can just wipe it clean and start fresh (I have never used rsd lite but I'm guessing its somewhat like option one of Matt's utility) that restores your phone to a moto flashed like state... ready to be sold as a certified like new device (as Verizon would call it)...
Sent from my XT907 using xda app-developers app
Are you mounting system in TWRP, before you wipe data? For some reason, I stopped doing this when I updated to the newer TWRP. There was a thread on here where someone said they mounted prior to wiping and it solved their 4.3 issues. I tried it and it worked for me. I would suggest you try the same.
RikRong said:
Are you mounting system in TWRP, before you wipe data? For some reason, I stopped doing this when I updated to the newer TWRP. There was a thread on here where someone said they mounted prior to wiping and it solved their 4.3 issues. I tried it and it worked for me. I would suggest you try the same.
Click to expand...
Click to collapse
Don't even know how to do this or what this means exactly...
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
If I were you I would go back and read a little information about mf3 and what kind of recovery can be used. It sounds to me like you might be very confused. In order to correctly keep from bricking your phone you may want to read up on things. Good luck.
ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Since you are rooted, take a look in the /cache/recovery directory. Read the log file. It will tell you where things messed up.
For example, I had forgotten that I did something with csc and had replaced the feature.xml file. Luckily, I had a back up of the original file. I renamed it, fixed is file permissions to rw-r--r--, advanced my clock one day, and then was able to install MJ9.
Good luck, and remember you won't have root anymore when you install this (for the time being)
Yrs,
dkephart
Sent from my SAMSUNG-SGH-I337 using Tapatalk
ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I had the same problem. The only way I was finally able to upgrade to 4.3 was to use Odin to revert to stock (unrooted) 4.2.2 MF3 using the files on this thread: http://forum.xda-developers.com/showthread.php?t=2502003 Once I did that I ran the OTA update to 4.3 and it worked without any problems
To able to keep your root and upgrade from 4.2.2 to 4.3 you have to change your param file back to the stock. Thats all the information that I have so far so... not completely sure. But I think that is what you're supposed to do.
Because you have a custom param file, when you try to upgrade to 4.3 it's telling you there is an issue with your phone.
I may be wrong.
Is there a copy of the correct feature.xml? Im having the same issue
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
According to the log its stopping when it can't find the chat on apk. I did remove it using titanium.
Will restore it try again andbipdate the thread. Thanks for pointing out the correct log file to look at.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
I checked again and found my backup feature.xml. Typed this from mj9.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I had the same problem happen to me on Wednesday night and last night. Today I used Odin to go back to stock MF3, however, then I couldn't get the OTA update. It kept saying my firmware was up to date each of the three times I restored it.
Now I'm finally on MJ9 after copying "update-mf3-mj9.zip" to my SD card, going into recovery mode, and updating from external SD card. Now I can use my Galaxy Gear!
Cause I want to sound like a noob.
How did you install CWM on what reads to me a MF3 S4.
Those on MF3 have been using Safestrap cause CWM hasn't been possible.
Sent from my ATT S4 MF3 using Tapatalk
jball said:
Cause I want to sound like a noob.
How did you install CWM on what reads to me a MF3 S4.
Those on MF3 have been using Safestrap cause CWM hasn't been possible.
Sent from my ATT S4 MF3 using Tapatalk
Click to expand...
Click to collapse
I was excited when I rooted the phone, then installed ROM manager premium. It allowed me to install the recovery. You can even boot into the recovery from ROM Manager.
However since the S4 is locked down tight, you can do any thing from there. So i can't flash anything. It even gives me a message saying as much.
However it is partially installed I can boot into it at will.
I will post a video of it. So that you all have an idea of what im talking about.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Don't waste your time with a video,its your stock recovery.your not the first to have done this.lets jump ahead a bit and just install Safestrap.whats Safestrap you might ask?search for it and READ please sir.
Sent from my ATT S4 MF3 using Tapatalk
jball said:
Don't waste your time with a video,its your stock recovery.your not the first to have done this.lets jump ahead a bit and just install Safestrap.whats Safestrap you might ask?search for it and READ please sir.
Sent from my ATT S4 MF3 using Tapatalk
Click to expand...
Click to collapse
While I was preparing to record it, I did notice that you are correct. Although Rom Manager goes through the motions of flashing the recovery, when you attempt to boot into the Recovery, you are faced with an Error, and default back into Android Recovery.
Although I know all about Safestrap...I think we've all missed the point. The OP was meant to get help about why the 4.3 OTA was failing 25% into the install.
I've got what I needed by being pointed to the location of the install log.....and while reading through it, I noticed that the install is failing because I removed the Chat On APK. I will install from backup and move forward.
Thank you all who provided the necessary guidance to solve the original problem.
Thank you as well to those who helped clear up the whole Clockwork vs Android recovery part. Although a minor part of the original post, it's good that we don't spread misinformation.
Cheers
ckalantzis said:
While I was preparing to record it, I did notice that you are correct. Although Rom Manager goes through the motions of flashing the recovery, when you attempt to boot into the Recovery, you are faced with an Error, and default back into Android Recovery.
Although I know all about Safestrap...I think we've all missed the point. The OP was meant to get help about why the 4.3 OTA was failing 25% into the install.
I've got what I needed by being pointed to the location of the install log.....and while reading through it, I noticed that the install is failing because I removed the Chat On APK. I will install from backup and move forward.
Thank you all who provided the necessary guidance to solve the original problem.
Thank you as well to those who helped clear up the whole Clockwork vs Android recovery part. Although a minor part of the original post, it's good that we don't spread misinformation.
Cheers
Click to expand...
Click to collapse
You handled this all very well.
ITNV said:
I had the same problem. The only way I was finally able to upgrade to 4.3 was to use Odin to revert to stock (unrooted) 4.2.2 MF3 using the files on this thread: http://forum.xda-developers.com/showthread.php?t=2502003 Once I did that I ran the OTA update to 4.3 and it worked without any problems
Click to expand...
Click to collapse
Did you use all files? I mean, I've been trying the same for the past couple of days, and I even asked in that thread if I could use just the PDA file, nobody replied so I went ahead and did it, it removed the root and I kept all my files and settings (That was the idea) but just after that I can't connect anymore to Kies ( I could without issues, I did a full backup moments before) and trying to do the sideload it always gives me the Error 7, I even tried the full SD card update,it erased everything and guess what, when it rebooted for my surprise I was still at 4.2.2 MF3, so it just did the Wipe Data and then rebooted, so I lost almost 6 hours getting everything back as it was and then, I had the Damaged SD card error so I also lost all my pictures and videos withoout back up.
So, as you can see half a day later I'm still at the same point I was this morning and with a huge loss, so, please, Did you use all the files? If you did, doing this erase everything also?
Thanks in adavance.
erasat said:
So, as you can see half a day later I'm still at the same point I was this morning and with a huge loss, so, please, Did you use all the files? If you did, doing this erase everything also?
Thanks in adavance.
Click to expand...
Click to collapse
Yes. I used all the files. The result was a completely stock unrooted 4.2.2 so, yes, it reset the phone and erased everything that I had on there. (It left my external SD card intact but I would still advise removing it if there is anything on there you don't want to lose.)
ITNV said:
Yes. I used all the files. The result was a completely stock unrooted 4.2.2 so, yes, it reset the phone and erased everything that I had on there. (It left my external SD card intact but I would still advise removing it if there is anything on there you don't want to lose.)
Click to expand...
Click to collapse
Yep, that was the reason why I just used the PDA I didn't want to lose my data, and then I did it anyways, my mistake was not doing the Odin Restore just after I realized that it erased everything and I was still at 4.2.2, that's was the perfect time to do it, but now, after I finally put everything back as it was, I simply don't see myself by my own choice, doing all this again.
Thanks.
erasat said:
Did you use all files? I mean, I've been trying the same for the past couple of days, and I even asked in that thread if I could use just the PDA file, nobody replied so I went a head and did it, it removed the root and I kept all my files and settings (That was the idea) but just after that I can't connect anymore to Kies ( I could without issues, I did a full backup moments before) and trying to do the sideload it always gives me the Error 7, I even tried the full SD card update,it erased everything and guess what, when it rebooted for my surprise I was still at 4.2.2 MF3, so it just did the Wipe Data and then rebooted, so I lost almost 6 hours getting everything back as it was and then, I had the Damaged SD card error so I also lost all my pictures and videos withoout back up.
So, as you can see half a day later I'm still at the same point I was this morning and with a huge loss, so, please, Did you use all the files? If you did, doing this erase everything also?
Thanks in adavance.
Click to expand...
Click to collapse
It was mentioned several times in that thread exactly what files to use and how to use them. There were also several pictures provided that showed EXACTLY what the ODIN screen should look like before the flash.
scott14719 said:
It was mentioned several times in that thread exactly what files to use and how to use them. There were also several pictures provided that showed EXACTLY what the ODIN screen should look like before the flash.
Click to expand...
Click to collapse
In the thread, there are tons of instances where it explains where to use each file and even pictures, I know because I read every single post, but none of them explains if I could use just the PDA one if I wanted to keep my settings while unrooting the phone, that's why I asked about it, because nobody replied to my question I decided to be the guinea pig, and yes, it works, you keep your settings, and I was glad, but as you can see, what I wanted to accomplish didn't work after all. Without all the files it doesn't fix the issue that causes the error 7 when doing the sideload.
help with mf3 to mj9
Having the same issue and formatted card with backup image.
Update got to 23 % and failed
now phone refuses to flash in odin.....and im missing factory apps preventing me from doing anything to get it back to stock
anyone have a stock restore image I could use in kies?
Would that work properly?
[Resolved]
Help, I downgraded from 2.3 to 2.2 for various reasons,but now when I try to upgrade again I just get the pink screen ,if I try using the option from settings/storage,it says key data couldn't be backed up , the installation will stop. Also if I boot into the system it runs fine for about a minute then locks up completely so I can't even continue to use it in 2.2 can anyone advise ?
Sent from my Nexus 7 using XDA Free mobile app
Try to put the 2.3 dload folder to a sd card, then remove the battery, plug in a USB cable to the computer and the phone, volume up+down+power (if I remember right lol). See if it will update that way.
no, that's the usual way I've been flashing it, I can get to the image folder ,but it won't boot into recovery either
Sent from my Nexus 7 using XDA Free mobile app
totsy1972 said:
no, that's the usual way I've been flashing it, I can get to the image folder ,but it won't boot into recovery either
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Odd. Maybe try to flash the ICS pink screen unlocker? I had weird issues at some point too, then I flashed that and the problems went away. Afterwards flash ICS.
Just tried that,still no luck,it doesn't even get to the unpacking screen,it just stays pink. beginning to think its beyond repair
Sent from my Nexus 7 using XDA Free mobile app
totsy1972 said:
Just tried that,still no luck,it doesn't even get to the unpacking screen,it just stays pink. beginning to think its beyond repair
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
I think it's still possible to fix it. I was loosing hopes too, but I messed around with it anyway and got it working. Just try different dload's, different methods and maybe you'll get it running. Maybe other users will have some ideas too.
CrysisLTU said:
I think it's still possible to fix it. I was loosing hopes too, but I messed around with it anyway and got it working. Just try different dload's, different methods and maybe you'll get it running. Maybe other users will have some ideas too.
Click to expand...
Click to collapse
I've been trying all different ways, this is what I get when trying it from storage menu
Sent from my ST15i using XDA Free mobile app
@Moihack maybe you have any ideas? You've written this to me before:
Moihack said:
As long as your phone still gets power and pink/blue screen shows there is nothing to be afraid of yet,since this isn't a hardbrick.
Contact me on hangouts telling me what you have done resulting in the above issue.
I have bricked my u8800pro in every possible way both soft and hard brick (thank god warranty was still active back then).
Click to expand...
Click to collapse
Hi there!
I think when you upgrade from software menu there is an option for data back-up.
Uncheck this option and the error should go away.
Also what do you mean with this: "Also if I boot into the system it runs fine for about a minute then locks up" ?
What do you mean it locks up? Touchscreen is not responsive for example?
My suggestions:
1) Do a factory reset and then check if you can upgrade
2) Try re-installing your recovery(use cwm 5.0.27 by geno for best compatibility) or even replace the whole image folder with the froyo one from here: http://forum.xda-developers.com/showthread.php?t=2146856
Your phone is not beyond repair that's for sure. Since it boots fine.
Moihack said:
Hi there!
I think when you upgrade from software menu there is an option for data back-up.
Uncheck this option and the error should go away.
Also what do you mean with this: "Also if I boot into the system it runs fine for about a minute then locks up" ?
What do you mean it locks up? Touchscreen is not responsive for example?
Click to expand...
Click to collapse
I haven't noticed an option for data backup,will check again later on. And yes when it locks up touch screen becomes unresponsive and none of the buttons respond either. Also when I try to enter recovery ,both custom and stock, it displays the kernel logo then vibrates with a black screen for a second then back to kernel logo and continues to boot.
Sent from my Nexus 7 using XDA Free mobile app
Ok guys,I copied over the stock image folder and now it works ok, however I still can't upgrade from froyo. At least I can use it again though so thanks for your help, its much appreciated. Incidentally, there wasn't an option to back up data when upgrading, but that error has now gone, except it now just reboots instead, so I will just keep trying.
Sent from my U8800Pro using XDA Free mobile app
[Edit] Finally I've managed to upgrade to GB , had to put both step 1 and step 2 in the same dload folder and it worked. So cheers for the tips
You've put all steps in one folder?
DarkSkyGhost said:
You've put all steps in one folder?
Click to expand...
Click to collapse
Steps 1&2 in dload folder ,step 2 renamed to UPDATE_G.APP.
Didn't use step 3 as I was updating to ICS after that
Sent from my Nexus 7 using xda app-developers app
Every time I reboot my phone, the top menu bar does not drop down when swiped and icons placed towards the top near it I cannot press. If I turn off the screen and turn it back on, it will work, but only for a few seconds. My phone will have to sit for 2-5 minutes after reboot before the top menu bar starts to work, and then it never stops working until, yes, I reboot the phone.
I haven't seen any threads on this so I'm wondering if I have a faulty phone? It's only a few months old but I'm assuming I'm able to exchange it for the same unit considering this seems to be a functionality error. I was hoping upgrading to the latest 5.1.1 version would solve the problem but it has not.
Any advice and/or recommendations? The phone is stock and not rooted or anything.
BoostinBen82 said:
Every time I reboot my phone, the top menu bar does not drop down when swiped and icons placed towards the top near it I cannot press. If I turn off the screen and turn it back on, it will work, but only for a few seconds. My phone will have to sit for 2-5 minutes after reboot before the top menu bar starts to work, and then it never stops working until, yes, I reboot the phone.
I haven't seen any threads on this so I'm wondering if I have a faulty phone? It's only a few months old but I'm assuming I'm able to exchange it for the same unit considering this seems to be a functionality error. I was hoping upgrading to the latest 5.1.1 version would solve the problem but it has not.
Any advice and/or recommendations? The phone is stock and not rooted or anything.
Click to expand...
Click to collapse
Try factori reset and if don't work you have to install stock firm again and start fron scratch
jah2110 said:
Try factori reset and if don't work you have to install stock firm again and start fron scratch
Click to expand...
Click to collapse
Install stock firmware? I am not rooted or anything - the phone is bone stock.
BoostinBen82 said:
Install stock firmware? I am not rooted or anything - the phone is bone stock.
Click to expand...
Click to collapse
Sometimes stock firmware fail and that is the reason to install again.
jah2110 said:
Sometimes stock firmware fail and that is the reason to install again.
Click to expand...
Click to collapse
So how does someone unrooted go through the process of installing the stock firmware again?
BoostinBen82 said:
So how does someone unrooted go through the process of installing the stock firmware again?
Click to expand...
Click to collapse
Odin?
Sent from my SM-G928V using Tapatalk
thornev said:
Odin?
Sent from my SM-G928V using Tapatalk
Click to expand...
Click to collapse
Are you asking me a question or trying to be witty?
Unsure reply
Sent from my SM-G928V using Tapatalk
thornev said:
Unsure reply
Sent from my SM-G928V using Tapatalk
Click to expand...
Click to collapse
I see. Not much out there for us Verizon folks, then. I'm perfectly fine with having an unrooted phone, to be honest (though Titanium Backup would be great to have again). I may try Verizon/Samsung's default program that you can install on your PC that lets you "fix" your phone and such.
that's what Odin is.. An app with which to install firmware, rom, etcetera.
Sent from my SM-G928V using Tapatalk