Related
I've got a rooted (Super SU, but the original root manager was Superuser) LG C800 that I was having problems with. To be specific, I installed some apps on to the system. Some of these apps would be Titanium Backup for root, Avast Mobile Security, ROM Tool Box Lite, Super SU, and a quite a few others. From day one they seem to be kicked right back to my S.D. card, but not all at the same time, and some would stay on the system. I read where I should move the apps back to my S.D. card and try to re-install them on the system minus the data. When I did, the phone went nuts. Now it stays in a restart mode but never fully boots up. Can I salvage it, and if so, please tell me how?! I have tried the hard reset/recovery boot where you hold down the power button, volume, and a few other keys, but it did not work. I'm a broke college student and can't really afford to buy a new phone. I used this one for everything including tethering it to get my assignments done at home and turned in on time. Please help! I'm open to suggestions....... My phone will be completely off. When I plug it into my computer, via U.S.B., it automatically turns it on whether I want it to be on or not. Then it starts off in "reboot recovery" mode, will boot all the way to the point to where the home screen would normally turn on, but then it starts in that "boot loop" all over again but never fully boots up before going back to the beginning of that "boot loop" yet again. I can't even get it to register on my laptop as being plugged in. The reason I took the apps I placed on the system off was because sometimes when I'd re-boot the system the apps would be on the system and sometimes back on my S.D. card without my involvement of any kind other than rebooting my phone. Is completing a Nandroid recovery or re-installation of my ROM even possible with my computer no longer recognizing it as even being plugged in? From what I can tell it won't be. Am I fighting a lost cause or is it salvageable?
Rooted myTouch Q 4G, a.k.a. LG C800
I believe it has a 2.3.4 GRJ22-perf, and then something like 2.6.35.7? I can't remember off the top of my head, and I can't pull it up on my phone anymore or else I'd double check.
Have you tried booting into recovery?
(More about my phone from the original post) Honestly.........I'm not what you may consider technologically inclined. I have however done about as much research online concerning this matter as any one person can do. I've looked it up on all major sites, and many smaller ones too, that post remedies for phone, or "human" if you'd rather, malfunctions. They all talk about still being able to reach a home screen or doing the whole holding the power and volume decrease buttons until I "reboot recovery" screen appears (if that's what you're referring to as doing a recovery reboot as). Don't forget the one where you hold hold the power and volume decrease buttons along with the "A" and "F" keys as well. I even tried one from here where you're supposed to push the genius button after the Android figure leaves the screen. My phone won't allow me to do either. Basically if it's online, I myself, or this girl that's been staying with me, have tried it without any results. On the initial boot the Android figure and the box with the arrow coming out of it show up and it boots until just about the point that it use to switch over to the home screen and it will start the whole "boot loop" over again. The thing is though that the Android figure and box aren't there any other time after the first boot, and with every boot loop it makes after that, the time is reduced from the beginning of the loop to the end when it starts all over again. The phone won't shut off unless I remove the battery and even though my laptop no longer recognizes the device, when I plug my phone into it or another power source and it's off, it automatically turns itself on and begins that boot loop all over again. there is one thing I have yet to try. I read on one site where I could download a custom ROM on my S.D. and then try reboot it, but it never makes it to the point in which the files on my S.D. card are ran, much less scanned. I am still 100% open to any and all suggestions in the diagnosis of this issue. I may record and place a video on one of the more popular "tube" sites to better show or further explain what's happening and then come back on here to post the link?! Feel free to reply back if it's possible you can help before I'm able to complete that later this evening. And thanks for any and all help in advance to everyone.
So, right away today I decided I would format my TF-101 and start fresh to try and fix a weird sound issue that I had. In a lapse of judgement, I installed (which I now know I should not have done) CWM and now I'm in a bootloop...Which would seem easy enough to fix, but I have an even stranger issue...
When I try to push files to my device, anything over a few MB will fail. The things I have been able to push haven't helped me...
When I go to APX mode, the device shuts down whenever I enter a command or run a program that tries to interact with it. So, for instance, I put it in APX mode, tried to run EasyFlasher and it turns off. I know its off because I hear the device removal notice, and the devices drops from my device manager...Try to run Rootkit 8, it turns off...
I don't know what else I can do...Unless I have the wrong driver installed, I seem to be stuck. I can not enter any other modes besides the CWM screen v.5.8.3.4 btw, and the Power+Vol Down mode. If I choose cold-boot linux, my laptops call it "Android MTP Device" but by tablet never boots or leaves that screen...
I'm pretty stumped, waving my flag at this point...
Any help is appreciated..!
AYHJA said:
So, right away today I decided I would format my TF-101 and start fresh to try and fix a weird sound issue that I had. In a lapse of judgement, I installed (which I now know I should not have done) CWM and now I'm in a bootloop...Which would seem easy enough to fix, but I have an even stranger issue...
When I try to push files to my device, anything over a few MB will fail. The things I have been able to push haven't helped me...
When I go to APX mode, the device shuts down whenever I enter a command or run a program that tries to interact with it. So, for instance, I put it in APX mode, tried to run EasyFlasher and it turns off. I know its off because I hear the device removal notice, and the devices drops from my device manager...Try to run Rootkit 8, it turns off...
I don't know what else I can do...Unless I have the wrong driver installed, I seem to be stuck. I can not enter any other modes besides the CWM screen v.5.8.3.4 btw, and the Power+Vol Down mode. If I choose cold-boot linux, my laptops call it "Android MTP Device" but by tablet never boots or leaves that screen...
I'm pretty stumped, waving my flag at this point...
Any help is appreciated..!
Click to expand...
Click to collapse
** Edit **
I knew that I would figure this out the minute I posted it...I'm still having issues, but PERI-V0.4 broke the ice and at least allowed me to get some type of on CWM boot thing going...I'll post details for the next troubled soul with a similar issue, though I am still curious about why it kept disengaging...
Hello, my Photon started acting up really weird. First of all, it was really slow. I thought it's because I had like 150MB left and it was nearly full data-wise. However, I erased most of the data, and left it with 3GB left. Didn't work and it got worse.
I have these stripes around the display (just at sides, not at middle), while phone is turned on. Doesn't matter if in system, or at boot logo. Doesn't matter, because whenever I get to system, I can be in system for like 1 minute, then every application starts crashing (Apex launcher, Google play, whatever you pick) and I basically can't get anywhere. Also if I go to sleep mode, phone is basically dead and it's pure luck when I will turn on phone again. I am trying every few minutes and it's worthless, because any time I get to system anyway, I crash after few seconds.
What to do? I was planing to install custom ROM yesterday, but never got to that, because this all started to act up. So what should I do? Reset system? Any other ideas? Is phone dead?
Sorry for bad english, no bully please.
Thanks in advance
Update - now when I am trying to start up my phone, I have just black screen with white lines in the middle. Then phone shuts down. I will give more info when I will be at home and can get phone on charger
Well definitely try to charge the device up. You might try re-flashing the stock ROM using RSD Lite... Although from your description I fear your issue may be hardware related.
Could turn device on. Apparently that black screen with white lines was just discharged phone. When I put it on charger, I could again boot into system and it was working until I pressed power button to go to sleep mode and phone is again dead. Will try to flash RSD Lite later today and will post what happened
kanek06 said:
Could turn device on. Apparently that black screen with white lines was just discharged phone. When I put it on charger, I could again boot into system and it was working until I pressed power button to go to sleep mode and phone is again dead. Will try to flash RSD Lite later today and will post what happened
Click to expand...
Click to collapse
Charge the device as much as you possibly can before doing anything with RSD. Ideally you should have at least 50% battery in the device when flashing anything.
This is really miserable. I can't really get into bootloader. Because phone after that 'crash' or whatever you want to call it is dead and I can't even see if it's turned on or not. Basically I am randomly waiting when it's gonna restart and then I just get into system. Even if I fully discharge it, it will have black screen with white lines first, it flashes quite couple times and then it will finally boot into system. Also I remember it was ***** in past to get into recovery. Can I do anything from system? Because as soon as I don't turn off my screen by power button, phone is working, though it has those lines on side of LCD (I will try to borrow camera from someone and post it here today).
I set automatic turning screen off for 10 minutes and I am really careful about pressing power button. Sucks there is only option for just 10 minutes, so I have to tap on screen at least for once every 10 minutes or I will not have working phone. **** my life, really.
kanek06 said:
This is really miserable. I can't really get into bootloader. Because phone after that 'crash' or whatever you want to call it is dead and I can't even see if it's turned on or not. Basically I am randomly waiting when it's gonna restart and then I just get into system. Even if I fully discharge it, it will have black screen with white lines first, it flashes quite couple times and then it will finally boot into system. Also I remember it was ***** in past to get into recovery. Can I do anything from system? Because as soon as I don't turn off my screen by power button, phone is working, though it has those lines on side of LCD (I will try to borrow camera from someone and post it here today).
I set automatic turning screen off for 10 minutes and I am really careful about pressing power button. Sucks there is only option for just 10 minutes, so I have to tap on screen at least for once every 10 minutes or I will not have working phone. **** my life, really.
Click to expand...
Click to collapse
Why can't you turn the phone off and charge it while off, or boot to recovery and charge the phone in recovery?
arrrghhh said:
Why can't you turn the phone off and charge it while off, or boot to recovery and charge the phone in recovery?
Click to expand...
Click to collapse
About charging it while turned off - Can't because when I try to turn it on again, it's roulette when I get finally bootloader logo and not black screen with white stripes.
And boot to recovery. Is it possible to like download some command prompt application and boot to bootloader from there? I know when I had my G1 (and when I actually understood android ) you could boot to recovery or bootloader via console. I have astro installed on phone, so downloading some console application and installing it shouldn't be problem.
Btw as we are speaking, I tried to call someone and I basically get same thing like when I am going to sleep mode, I get black screen and now I am just waiting, when phone will eventually want to restart itself.
kanek06 said:
About charging it while turned off - Can't because when I try to turn it on again, it's roulette when I get finally bootloader logo and not black screen with white stripes.
And boot to recovery. Is it possible to like download some command prompt application and boot to bootloader from there? I know when I had my G1 (and when I actually understood android ) you could boot to recovery or bootloader via console. I have astro installed on phone, so downloading some console application and installing it shouldn't be problem.
Btw as we are speaking, I tried to call someone and I basically get same thing like when I am going to sleep mode, I get black screen and now I am just waiting, when phone will eventually want to restart itself.
Click to expand...
Click to collapse
Still sounds like some sort of a hardware issue, is the phone new to you?
You can certainly force bootloader mode, in several ways. When it's off you can hold power + camera and it will give you a choice of what to boot. When it's in Android you can do "adb reboot recovery" or "adb reboot bootloader" depending on where you want to end up. There are various apps which can also do this for you, if you are on the stock ROM but rooted.
arrrghhh said:
Still sounds like some sort of a hardware issue, is the phone new to you?
You can certainly force bootloader mode, in several ways. When it's off you can hold power + camera and it will give you a choice of what to boot. When it's in Android you can do "adb reboot recovery" or "adb reboot bootloader" depending on where you want to end up. There are various apps which can also do this for you, if you are on the stock ROM but rooted.
Click to expand...
Click to collapse
Phone is not new. I bought it used about one year ago.
I am not entirely new to android, but I didn't have android phone for 2 years and then I got this one. So I am really pretty **** with android atm
I will try reboot to bootloader from some console application.
I am rooted, opened bootloader, stock rom
Finally got into recovery, what now?
Also, when I once booted to system, I downloaded some root checking app, and root apparently isn't here. Well cornholio told me it is rooted back when I gave him my phone to perform sim card mod, but whatever. However, I am in recovery, but device is not detected by RSD Lite.
kanek06 said:
Finally got into recovery, what now?
Also, when I once booted to system, I downloaded some root checking app, and root apparently isn't here. Well cornholio told me it is rooted back when I gave him my phone to perform sim card mod, but whatever. However, I am in recovery, but device is not detected by RSD Lite.
Click to expand...
Click to collapse
Well reading back thru this thread, I was suggesting RSD Lite back to stock. I'm not really sure what you want to achieve tho, what your "final" goal is here.
I'm not even sure what kind of recovery you are booted into - stock recovery? CWM?
Either way, if you want to RSD the phone back to stock, you need to boot into fastboot/bootloader mode - not recovery. Just make sure the phone is charged up as much as possible before flashing in RSD.
Oh, sorry - misunderstanding from my side, thought I can switch to fastboot from recovery, oh well.
Also yeah, stock recovery.
To spread more facts - in case somebody would have similiar problems, when I try to just turn phone on, I have zero success what so ever. There's just this blank black page flashing every few seconds. However, when I remove back cover, I somehow force phone to load to bootloader logo, then I finally get chance to force phone to get to recovery. I will try to get to fastboot
kanek06 said:
Oh, sorry - misunderstanding from my side, thought I can switch to fastboot from recovery, oh well.
Also yeah, stock recovery.
To spread more facts - in case somebody would have similiar problems, when I try to just turn phone on, I have zero success what so ever. There's just this blank black page flashing every few seconds. However, when I remove back cover, I somehow force phone to load to bootloader logo, then I finally get chance to force phone to get to recovery. I will try to get to fastboot
Click to expand...
Click to collapse
Not sure if stock recovery has adb enabled, but if you have adb you can 'adb reboot bootloader'.
Otherwise do the power+cam trick I mentioned earlier.
http://i.imgur.com/3XYLngJ.png
kanek06 said:
http://i.imgur.com/3XYLngJ.png
Click to expand...
Click to collapse
Did you remove the getvar lines from the xml file...?
Yes
Weird. I only recall seeing that when people were trying to downgrade... but you are flashing 4.1.2.
The phone is in fastboot mode? What happens when you click "show device"? The "Device Properties" section is eerily empty.
I know it sounds shady, when I am coming back here again in few weeks, just been a bit busy lately, sorry about that.
However, somehow I got phone to flash it. The white graphical lines on sides dissapeared, however I got some new bug - I can't use phone in portrait mode, just in landscape - aka I need to swipe keyboard to have phone working. Also, that thing when phone completely stops working now occurs only when I am in that portrait mode, but I can restart phone this time.
When I finished this, it was midnight so I went to bad, so I tried to set up alarm, if it's gonna randomly shutdown like before and unfortunately, yes it did. I was waken up with this classical white line graphical bug black screen and had to reboot the phone. Oh well, managed to boot to system and it takes 5 minutes to fetch sim card (I have sim card mod from cornholio) and as I said, those white lines on side aka mysterious graphical bug is back.
Unfortunately for me, starts looking like real hardware issue now
I did search my terms and didn't come up with anything close to my situation, which is this: I got this phone in 2013, rooted it successfully, but was never able to get TWRP flashed properly, but I was happy with the root, so I sort of ignored the TWRP thing. Now I am getting a replacement phone, LG-V20 VS995 next week, so I decided yesterday to tinker around again with TWRP, as I wanted to put this on the V20.
On the G3 when I flashed(Or so I thought) TWRP and rebooted to recovery, I would get an error message (Very small) in the top left of the screen, then would disappear and I would have to pull the battery to reset and then it would boot fine back to the OS, but not to TWRP.
I made sure I had/have the updated Windows LG drivers, ADB, etc.... and I could see my G3 in Windows properly, the internal device and the microSD, I even pulled up the terminal emulator on the G3 while attached to the PC and ran an ID command I think, successfully. I pulled up a CLI in Windows in my ADB directory and my G3 device showed up as well. Then I tried flashing TWRP, first using Flashify; I started with an older version, like 2.8.6, but it didn't seem to work, so I started going towards the newer versions, but still, Flashify kept saying they failed to flash. So I tried the official TWRP app, and it seemed to be doing the same thing. So I went back to review what I had already done, then disconnected my phone from the PC, rebooted normally and tried again with the TWRP app. I think I was successful with one of the newer versions, 3.1.x so I did the reboot after it said it was successful, but I got that boot error message again, then blank screen and red/blue flashing lights; removed battery and replaced, powered on for normal boot and back in the phone OS again. I checked some YT videos on flashing TWRP on VS985 and it appeared I was doing everything correctly, but then I saw this one video that stated to use the Vol+ and Pwr button (I guess I thought when I selected "boot to recovery" the phone was going to do that automatically), then once you see the LG logo, release the Pwr button, then continue to press the Pwr button all while still holding the Vol+ button down, and then you would go into Recovery mode.
His next words sort of came as a shock - you had to select the option to reset your phone to factory defaults, and THEN, and IF you were successful flashing TWRP, it would take you to TWRP. I thought about this and and decided to do another TWRP flash, and if successful, would try this method. I did and I was able to get into the stock recovery menu, and I did see the option to "Reset phone to factory defaults", but decided just to cancel and went back to the phone OS, and that worked. Later on, I decided to try the "Reset" option on another phone boot, but I've now run into a different issue/error. When I boot the phone, I immediately get the error message (The boot certification verify error), and no matter how many times I remove the battery or for how long, each time the phone boots, I get this error message. The only thing I have been able to do is get into the Hardware Key Control Mode using Vol+Vol-Pwr and just continuing to press them. No matter what option I choose, either Cancel, Mode On, or Mode Off, the phone immediately reboots to the error message; it's like it's stuck in the Recovery boot mode somehow. I'm not sweating it too badly, as I've got a V20 coming next week and I have a work cell I can use for important things, but has anyone run into this type of thing? The way it is now, I cannot view the phone on my PC and cannot seem to get past this boot certification verify error.
EDIT: I am now able to consistently boot into the System Recovery by way of Vol+Pwr button held down until the SR menu shows. HOWEVER, no matter what choice I select, phone reboots and I get the "Boot certification verify" error................ oh well, at least I got an email that my V20 is coming this Thursday.
EDIT: I must be somewhat dyslexic, as the method to get to the SR menu is VOL- (Not Vol+) and Pwr button held down until SR menu entry. Sorry about that
EDIT: I've also seen the "fix" where you remove the back cover, battery, and then remove the top plastic cover over the battery/power/volume, then also remove the metal shield. This is the point where it gets confusing; the author(s) want you to "ground" 2 of the contacts, but it's not clear which ones they are referring to, even with the screenshot, and I'm not electrical engineer, so not exactly sure what they mean by grounding. As I'm getting a replacement tomorrow, I decided not to even explore this technique, although I did dissassemble the phone down to removing the metal plate, so I could try and see if I could figure out what they were talking about (I couldn't). Gotta say, I've had my G3 for over 7 years and for the most part, really loved it; it came in handy during home power outages when the Internet (Cable) went out.
3 days ago I've woken up to my "supernatural" work-out to find out the light on the side of the oculus is RED, which was funky cause it was plugged in all night.
SO, I've looked inside and saw that it's "Updating' I was all happy to get the latest version, but then it just finished, showed the logo blinking as usual and then - NOTHING!
Blank screen, after a couple of seconds - Again started up, Logo, Updating, Logo, Dead. -->> Over and over again and again!!!
I can't connect to it via the phone APP as it keeps restarting and going to update like mentioned, computer doesn't connect as well!
I tried holding down the buttons and factory reset the thing, it goes to Erasing -> Update - > Logo - DEAD! same loop, looks like the "Basic" upgrading is faulty so it can't even factory reset.
Tried to choose 'sideload' option from the "USB update menu" - no good! reboots to loop again.
I can get it to stay stiil if I pop up the 'USB UPDATE MENU' with the buttons and just leave it there, USB Connection to PC shows up 'Oculus ADB Interface' in device manager but I can't get the device to show on "Adb devices" Probaby because it's not on 'developer mode', maybe.
Tried to update drivers and to re'install adb.
PC app shows oculus as connected but I can't do anthying through there...
Contacted support 3 days ago - Nothing! they will look into it... NOTHING! sooooo angry!
EDIT>>
I have managed to pair once from the phone APP but as it "finished' the setup it went straight back into that update boot loop and can't connect again on phone.
Was hoping to manage to get it to developer mode and maybe force an update via adb.
I've been coding for most of my life, playing around with android phones software and such... so i'm not a complete idiot when it comes to these things but this one looks like there is no other choice but just sending it back for repair.
But these guys don't answer or anything... don't even know If I can send it or not, where to etc...
Boot loop:
https://photos.app.goo.gl/zsh8gws7eD8yRR4z6
Tried factory reset:
https://photos.app.goo.gl/h8GC7nurrkQnNsLe6
ANY IDEAS?
come on you guys!!! nothing?!
OK,
Found out I can make the device show in ADB Devices list if I manually load the USB Update menu (volume+power) and then choose sideload option.
However, this won't help much it disconnects from ADB as soon as it finishes loading the logo and restarts the update loop.
I tried to start the sideload as soon as it pops up in the device list, got to 4% serving and then connection was cut off...
If there was a mini update file (couple of KB\MBs) with some settings to make the oculus reset into sideload mode and stop looping i could sideloap a proper version and make it work again maybe.
Please someone help me fix the oculusssss pleaseee!
I same!!!
and oculus support said
"With that in mind, Oculus will not be able to offer warranty replacment/repair for this headset. I can only suggest that you consider purchasing a replacement device from our online store or an authorized retailer. "
fxxxk!!!!!!!!
You're great man. I didn't have such an issue, but I also didn't know the Quest had a menu like this.
Hey @Shlomikalfa - did you ever come back to this and make any progress? With the Quest 2 situation now, and FB logins required, I suspect a LOT more people are going to get interested in this idea.
Just to add, my Quest2 has being working just fine since I got it at launch from Amazon. I was playing beatsaber last night until it ran out of battery and shutdown. I plugged it in to charge and went to bed. This morning, I tried to turn it back on, and it went straight to the USB UPDATE MENU!!
I tried every single option in the USB UPDATE MENU, including factory reset, and it reboots and goes immediately back to the USB UPDATE MENU again. The only option that doesn't take you back to that menu, is POWER OFF! (LOL)
But if I power off, as soon as I power it back on, I got the same menu!
The volume buttons are not stuck at all... since I can use then to navigate the options in the menu.
So I just created a ticket at Oculus support to see what they say!
Good thing is that Amazon.ca gave me until January 31/2021 to return the headset... so if Oculus doesn't sort it out, I'll be returning to amazon for a refund!
Funny thing though. While in this "USB UPDATE MENU", I plugged it in my linux box, and it shows as a fastboot device! I can even run "fastboot reboot" and it indeed does reboot the headset!
I tried "fastboot flashing get_unlock_ability" just to see if it would say 0 or 1... but got an error: "FAILED (remote: 'unknown command')"
Does anyone want me try anything? (as long as the warranty is not voided since I'm waiting support answer! )