I'm having a serious problem with my note 2.
I'm running omegaromv30, and for some reason i seem to encounter a returning error (com.android.systemui stopped working) and it keeps looping. Normally i just booted to recovery and reinstalled omegarom. But now i have another problem on top of that which is that my power button died and is unusable (ordered a new one).
So i cant boot into recovery with the 3 key combo, i cant boot into recovery with the use of some app, becasue my phone is unusable with this error loop. I'm trying to use adb, however it tells me "device not found". I'm not sure if it should find my note 2 when it isn't in recovery mode and is having some error loop. (edit: found out that i must enable usb-debugging, which i'm unable to do) I really need to get into recovery mode to fix at least this error.
Any tips how to get into recovery in a different way?
Or how to enable usb-debugging without being able to go into settings...
many thanks in advance!
Related
Hello, first I'd like to thank you for your time reading this.
Note: I've searched the forums a lot, even for other LG Devices (G2 for ex) but I couldn't find a solution.
Trying to flash CM12 by _infected (amazing rom, working as a daily driver on my other lg pad btw) and messed up something on TWRP.
-First trying to do a Factory Reset via TWRP gave me "failed to mount /data" and "/system" I rebooted and the device went straight to TWRP Recovery, I rebooted again, this time making sure I selected "Reboot to System" and it went again to TWRP Recovery...
- I did another wipe, this time wiped everything (all checkboxes in TWRP), reboot and... no boot...
Now my LG Pad is at the following State:
- Black Screen (No LG Logo)
- Connecting USB to Windows gives the "connected sound"
- Adb doesnt find device (driver was installed and working).
- Device Manager "refreshes" on USB plug but doesnt show the device (or I can't find it?).
- Holding Power on the tablet while USB plugged to Windows gives the "disconnected sound" -> "connected sound" -> "connected sound".
- Can't boot into Download Mode.
- Can't turn off the Tablet... only Reboots holding Power key.
Please? Any help?
What can I do?
Is warranty void at this point?
Thank you very much for any help you can provide.
I have a G pad in the same situation, and I wasn't able to fix it. I managed to pick up another cheap one, but I'll follow this thread in case you get an answer.
You have to find a way to get it into download mode or you wont be able to fix it with LG Tool
What did you mess up, and how did you install twrp ? Also what twrp version abd base.
mekoneko said:
What did you mess up, and how did you install twrp ? Also what twrp version abd base.
Click to expand...
Click to collapse
For me personally, I assumed it'd be as easy as the twrp page makes it out to be , or my nexus 4 was, so I just went for it. I ran into that secure boot error with twrp, and rebooted back into stock. There was an OTA update, so I did it (stupid I now realise) and that bricked it on reboot. It won't turn on at all. If i plug into USB on a computer it OCCASIONALLY brings something up on the screen, the LG logo I think or something, but I cannot for the life of me get it into download mode. It's at home right now, so ic anot remmeber the exact thing it shows on screen, but almost certainly not download mode, and none of the hardware buttons seem to be responsive for doing factory resets or download or anything.
I managed to send the LG G Pad to warranty and got a new one... Lucky me...
Guess that if we can't get into DL mode they can't either.
However after much investigation I've realized that the problem was a corrupted system partition...
Hi everybody,
ok I will try to make this short
I have an experienced user level ROM, recovery, boot, ..
My phone is BRICKED! Is it?
AT THE MOMENT:
- I get into fastboot mode
- I get into odin downloading mode
- I can't start in recovery mode
- I can't start bootloader mode
- I have a connection with a laptop (win XP, as win8.1 didnt work for me)
- The computer can communicate with the phone in fastboot mode
- The computer cant communicate with the phone in Odin mode (at the moment Odin PC SoftWare doesn't recognize the phone)
- I am sure the drivers are installed correctly now. Thanks to the guide with fully stripped drivers.
- Using different, multiple different, no thousand different methods I tried flashing the stock OS (Yakju 4.3)
- I like SkipSoft Android ToolKit (Although I used fastboot and adb commands, I find the toolkit to do the same thing..)
- I always get an Error, when the process of flashing starts.
> PC says : Error
> Phone (in fastboot mode) says: FAILWrite Fail
INTERESTING:
- While I still was able to get into Recovery, the phone couldnt mount the sdcard (=> the internal drive)
- Some of the methods I use make the phone CRASH
> means the screen stops at its position and slowly turns completely purple
- The phone power button doesnt start the phone, to get the phone doing something at all I have to trick it:
..> I plug it into the wall charger
..> I take the battery out
..> I put the battery back in
..> I wait
..> I can get into 3 routines:
^Normal starting routine (of course stuck at google start up, since no Rom is installed)
^fastboot mode (VOL + & - & Power)
^odin mode (VOL - & Power)
..> Then I can just plug the USB cable into the PC
- 2 days ago I had (every single version) of Odin PC Software recognizing the phone (phone was in Odin mode), but it also failed after trying the recommended and unrecommended settings. Ended with an error message.
HOW:
I left my phone overnight in the car (Temp: -2 deg C), while Im sure spotify and maybe other consuming apps were playing.
Next day, my phone battery was empty and I couldnt start my normal ROM. (I had Slim Rom installed)
It was stuck at the "Google" start up display.
First intentions showed that it might be more than just the Software :/
Many days and so many hours of work, research and reading in forums, I decided to take a shot and ask here.
I appreciate everything xda-members have done for me already. Though I never needed to register for my earlier questions.
Phone data:
Product Name - tuna
Variant - maguro 16gb
HW version - 9
Bootloader Version - primemd04
baseband version -
carrier info - none
serial number - -a3c208 ***
signing - production
lock state- unlocked
BUMP!!! I have absolutely the same problem!! I can access everything, i enter the recovery trying to WIPE every single thing data,system,cache,storage etc.. but it seems it doesnt work. The information stays. I tried to "softbrick unroot & stock" with a nexus kit, everything seems ok, but after it finishes installing, it boots up on GOOGLE and after 10-15 min it starts to BOOT MY OLD CUSTOM ROM THAT I HAD BEFORE, after another 15-20 min it finally boots up and the system is EXTREMELY choppy and unresponsive and after a few minutes it restarts itself. I tried ODIN and I faced the same problem, it goes well to ~45% and then it freezes, and after a short delay odin gives FAILED. I tried several more things that i found on the internet and xda but nothing helps. Probably a corrupted partition or something. THE DAMN STORAGE DOESNT WANT TO DELETE ITSELF FFS!! PLEASE IF YOU KNOW ANY FIX/ALREADY FIXED YOURS PLEASE HELP!!! I need my phone!
can you give us more information about the error message?
valkata1212 said:
Click to expand...
Click to collapse
your issue sounds like this one, can you confirm?
Soulaysahmi said:
can you give us more information about the error message?
your issue sounds like this one, can you confirm?
Click to expand...
Click to collapse
Similar, only difference is with fastboot i can successfully flash system.img but nothing happens. With odin it fails at around 45% and then freezes. Only difference is that i cannot boot to old stock and i dont have this pulpish problem. I simply reboot on my old custom ROM configuration with all my last known icons widgets.. but the phone is choppy and unresponsive as hell.
I only get an error without any further message after flashing any of the images...
Any idea anyone? Isn't it some hardware issue?
Noo man i dont think its hardware problem, for me it all happened when my phone suddenly restarted itself and after that it bootloops forever and i have those problems
Anyone?
does erase work?
yes
can you get into recovery?
oxxomexico said:
AT THE MOMENT:
- I get into fastboot mode
- I get into odin downloading mode
- I can't start in recovery mode
- I can't start bootloader mode
- I have a connection with a laptop (win XP, as win8.1 didnt work for me)
- The computer can communicate with the phone in fastboot mode
- The computer cant communicate with the phone in Odin mode (at the moment Odin PC SoftWare doesn't recognize the phone)
- I am sure the drivers are installed correctly now. Thanks to the guide with fully stripped drivers.
Click to expand...
Click to collapse
ka
how do you know that erase works, I mean that what you erased has really been erased?
One of the erase command in the toolkit was succesful, I guess. But I will recheck every error or successful message later tonight.
still NOT working
2 months have passed and I was too busy with other things.
now back to it. the problem hasnt changed.
i try fastboot flash command:
[fastboot flash bootloader x.img]
- in Computer Terminal: 'FAILED(remote:Write Fail) '
- on phone: ' FASTBOOT STATUS - FAILWriteFail '
any idea, please?
I recently replaced my Cracked Screen on a Verizon m8. I was on a custom rom with twrp installed. After the initial boot, I was having problems with a speaker and went to try to boot to the bootloader to do a RUU, when I noticed that I can no longer access the bootloader screen. It was then when I noticed that not even my computer was recognizing the phone no more. It's as if the phone won't debug no more. I can still access my TWRP by rebooting straight to recovery thru a app or the apm it has on the custom rom im using. I've tried to flash other roms with no success to get access to these two things. I was wondering if anyone had a stock twrp of Verizon version. As for all my twrp are from custom roms. Or if anyone has had this problem before or if any suggestions im open to anything to try and get to the bootloader screen. It also doesn't even boot the two or 3 second boot up screen until you get to the roms boot up screen. It also doesn't goto the bootloader screeen when it try's to access the bootloader. Even when booting straight to recovery stays black until twrp actually shows up. So it's as if bootloader is completely being bypassed. You cant use the volume keys to access the recovery cause everything is blank. Although on first attempt to access bootloader screen when I was stuck there in black. I had to figit the keys a bunch of times to reboot, hoping that I didn't activated something in that screen that caused the phone not to debug. Any suggestions is more then welcome and if someone has a stock twrp of recent stock rom 4.605.9 I believe it is would be more then great. Cant find one other then in zip or exe version. Hoping maybe that might reactivate those two things. Thanks for taking the time to read my problem.
Debugging or adb works within OS, and its not a mode in itself. I think you mean you can't access bootloader-fastboot mode.
Casetheace said:
I was wondering if anyone had a stock twrp of Verizon version. As for all my twrp are from custom roms.
Click to expand...
Click to collapse
You mean stock recovery. TWRP is a specific custom recovery, therefore always a custom one.
I don't think stock recovery will change anything. Bootloader is on a completely different partition.
Its odd that you can't access bootloader. It must still abe intact, otherwise the phone would not work at all.
Did you try (in OS): adb reboot-bootloader
Are you s-off or s-on?
The phone is S off. I was able to get the phone to USB debug. I took it out of the shell and plugged in the USB cord and it debug instantly . So I'm guessing with that I had to damage something when I either took the phone out of the shell originally or when I replaced the screen. Cause you literally have to take every piece of the phone off and then reasamble the phone from scratch. Once i put the phone back in shell, i couldnt get it to usb debug no more. But I still can't access the bootlader, nor is the first boot screen on power up before the main boot up screen starts. Also has no display if I reboot to recovery using a app from the phone. You don't see the screen where the red text would show up saying rebooting to recovery, display starts when it begins to show twrp on display. But when I had the shell off, and was able to access USB debug, I was able to use adb commands from my computer from fastboot mode , but phone had no display. Was able to run a RUU, was able to use adb to reboot to boot loader, then was able to fastboot get varall command. Even flashed a twrp recovery install in fastboot under command prompt . So that tells me that the boot loader is operational. That it has to be some sort of power failure in booting that nots powering the display on initial boot for 2 to 3 seconds , no power on bootliader display, no power rebooting to boot loader or rebooting to recovery until it boots recovery. Any ideas what would cause this failure of power of display during boot loader processes? By the way , have twrp 2.87 . Its a Verizon build, but I'm on a T-Mobile sim.
I've installed live boot and attached a log. If anyone can help or maybe know why this might happen. Believe there is two boots, each with a separate power. Main boot is the initial power up last two or three seconds, and then system boot.. Believe main boot is sending power off display and then power on display on system boot.
Hello,
I seem to have really messed up my G3 and after days of research I have not been able to get anywhere with it. I've read posts of people having similar issues, but their solutions do not seem to work for me.
What I tried to do is flash the ROM, starting with TWRP. After installing TWRP and rebooting I was getting the "no command" message on the screen. I believe (this was days ago), I used ADB to remove laf and reboot the phone (for some reason I could not back it up). The phone rebooted in fastboot and it has been downhill from there.
No download mode. When normally started the phone just hangs on the LG logo. Vol- and power gets me to the "Factory data reset", but if I do that, it flashes "erasing" for a second and it goes back to the LG logo screen.
I can get to fastboot, however, any command that I enter in CMD or Linux terminal just shows up on the phone's screen and it does not do anything. Fastboot devices shows the device as "????????" in Linux and as "?" in Windows. I have tried multiple drivers for Windows.
I tried BoardDiag (3 or 4 different versions running as admin) and shorting the pins, but any time I try to run the checks, I get an error - "No response from device" or "Device was not found in dload trying flash programmer"
I also tried SmartBootDiag, but once it detects the phone, it does its checks and it disconnects the device, without giving me an option to flash anything. Looking at the logs, it does not find any anti-rollback issues.
Any suggestions would be greatly appreciated as I am not sure what else to try.......
Thank you.
Anyone??
Hello,
I bought a "bricked" Galaxy Tab S4 on ebay. The only info I got was, that it is stuck in a bootloop since the last automatic update.
The bootloop is similar to this one. The tablet starts with the Samsung logo, then nothing happens and after a while I end up in recovery mode. Further, if I restart or hardreset the tablet, the screen stays black. The only way to boot it up again is to empty the battery while it is stuck in the bootloop. Afterwards I can enter download mode by holding "vol up and down" and plugin the usb cable.
In download mode this text appears at the bottom left:
#reboot recovery cause [unknown]
API: 3
manual mode 1.0.0
(Similar to this thread.)
OEM lock is on and of course I can't change this being stuck in the bootloop, or can I?
I successfully flashed the stock rom T830XXU5CUE2 with Odin3_v3.14.4 and latest samsung drivers. Unfortunately it does not help or fix anything. (I used virtualbox, but it worked and said "PASS" at the end).
After some research I would like to try my luck with a combination rom, but I can't find a U5 version which I should use because of T830XXU5CUE2, is that correct?
Any ideas how I could proceed from here? With OEM lock I guess there is no chance to flash TWRP on it?