Well, as usual, I've managed to mess things up and here I am again. Somehow, I installed something or other that required rebooting. When I did, I kept getting an error that the systemui was messed up. So I decided to try to flash a custom ROM since it appeared this thing was already FUBAR and that's where the fun began. It WAS running stock 4.4.2. I wiped everything in preparation to flash the stock .tot file. Went to flash a zip from the external sdcard, and it refused telling me it couldn't mount the card! The only hopeful thing is that it powers up, I can get into download/recovery, and it's recognized by the PC through LGFT and ADB.
I can't flash anything, can't push or install through ADB, can't sideload anything. LG flash tools gets to about 38 seconds and then fails. It's like the devices permission were all changed to read only. The device is rooted and has CWM recovery. Is there a way to completely slick this thing (except for recovery - I'd do that too if need be) to reset permissions.
Any/all suggestions gladly accepted.
gjtoth said:
Well, as usual, I've managed to mess things up and here I am again. Somehow, I installed something or other that required rebooting. When I did, I kept getting an error that the systemui was messed up. So I decided to try to flash a custom ROM since it appeared this thing was already FUBAR and that's where the fun began. It WAS running stock 4.4.2. I wiped everything in preparation to flash the stock .tot file. Went to flash a zip from the external sdcard, and it refused telling me it couldn't mount the card! The only hopeful thing is that it powers up, I can get into download/recovery, and it's recognized by the PC through LGFT and ADB.
I can't flash anything, can't push or install through ADB, can't sideload anything. LG flash tools gets to about 38 seconds and then fails. It's like the devices permission were all changed to read only. The device is rooted and has CWM recovery. Is there a way to completely slick this thing (except for recovery - I'd do that too if need be) to reset permissions.
Any/all suggestions gladly accepted.
Click to expand...
Click to collapse
Surprisingly, there was nothing wrong with the phone nor the software nor the PC. After screwing around with this for a couple of days, I had a thought to try a different USB cable. So, I popped it on and, lo & behold, I'm able to flash to stock! Lesson learned: Don't use cheap cables and try changing cables when you're have weird problems like this. :good:
Related
Hello,
I had a problem I posted about earlier and I had no replies, so I stupidly tried to fix it myself. Here's the original post
"I'm in a bit of a pickle. I'm running gummy 1.0, and I was just messing around with the lockscreens that are native on the rom, and I changed back to the stock ics one and now my phone won't unlock without rebooting. As soon as I Hello,touch the padlock it restarts.
This would be no more than a minor inconvenience if I hadn't recently had to wipe my SD card due to memory issues (and after forgetting to add any new backups and any rom zips). So I cannot reinstall a back up or reinstall the rom from recovery. I've tried putting a rom back onto the SD via usb but the phone connects as a media device and the computer won't sync. hmm"
I've just done the factory reset from adb and now the phone is stuck in a bootloop. When I start fastboot it says "downloading do not turn off target!!" What in God's name have I done?!
I know this is totally my fault for trying to fix something when I'm in well out of my depth, but I'd really appreciate some help.
Thanks
James, the idiot
First thing I'd suggest is downloading the GNex toolkit located here:
http://forum.xda-developers.com/showthread.php?t=1392310
To re-flash CWM to be on the safe side, then use the adb push feature to push a rom .zip onto the phone. Then boot into CWM and re-flash it.
See if that works.
EchoVelocity said:
First thing I'd suggest is downloading the GNex toolkit located here:
http://forum.xda-developers.com/showthread.php?t=1392310
To re-flash CWM to be on the safe side, then use the adb push feature to push a rom .zip onto the phone. Then boot into CWM and re-flash it.
See if that works.
Click to expand...
Click to collapse
That sounds about right.
Boot to bootloader, flash CWM, boot to recovery, adb push a new ROM to /sdcard, flash ROM, profit.
Hello and thanks for your reply!
It was the Gnex toolkit that I was using, and without it I would be even more lost!
I'm not sure if you're some good omen or something but just as I read your reply, after leaving the phone in a bootloop for about 10 minutes, it just started up by itself!
Hopefully this is the end of my problems
Thanks again for your reply!
James
Hello everyone!
First of all, I would like to apologize, as these kind of issues have probably been talked about and solved a gazillion of times before, but the thing is, I'm having a hard time grasping the start and the end of this issue myself, as the phone that is stuck in a boot-loop isn't mine - it belongs to a friend of mine who somehow managed to get the whole thing bricked.
Anyhow, I'll start off with what I know;
His goal was to flash a new ROM (http://forum.xda-developers.com/showthread.php?t=1601543). He unlocked the bootloader and rooted the phone using these instructions; http://onexroot.com/one-x-root/how-to-root-one-x/). He succeeded in doing so and decided to move onto flashing the rom.
But the problems started when he read that he's first supposed to flash "Android Fastboot kit 2.1" onto the device, prior to flashing the device. And so he did. Or well, tried - what he told me was that he booted the phone into fastboot mode, then ran the "Install Boot.img" bat file inside the Fastboot Kit folder he downloaded and after that, the phone got bricked.
Now, my knowledge in this area isn't too great either, but I've flashed a few ROMs in my life before, so, I decided I'd do my best to help. But I have no clue on what steps he should take from here on.
To my understanding, he was running the official 1.29 version and he is still able to access the boot-loader as well as Clockwork Recovery mod. To my understanding, he didn't create a back-up of his previously working ROM and the phone won't show up in Windows Explorer while connected via USB either.
To my limited understanding, I should now try and install the rom onto his phone and once done, the whole thing should work - the only problem with that is the fact I can't get the ROM zip onto the SD Card right now, as explorer won't recognize it. So far, I tried using ADB to push the ROM file onto the phone, but every time I use the command "adb shell mount /sdcard" I get a "Device not foound" error. So, I'm kinda stuck here right now. If this even is the right way to solve the issue, that is.
So, like I said, I'm having a hard time grasping the start and the end of this issue myself, and if there is any additional information needed, I'll do my best to find out more about it - I do have the phone in my possession at the moment as well.
Thanks a lot to anyone who'll offer any kind of help!
Atraeh said:
Hello everyone!
First of all, I would like to apologize, as these kind of issues have probably been talked about and solved a gazillion of times before, but the thing is, I'm having a hard time grasping the start and the end of this issue myself, as the phone that is stuck in a boot-loop isn't mine - it belongs to a friend of mine who somehow managed to get the whole thing bricked.
Anyhow, I'll start off with what I know;
His goal was to flash a new ROM (http://forum.xda-developers.com/showthread.php?t=1601543). He unlocked the bootloader and rooted the phone using these instructions; http://onexroot.com/one-x-root/how-to-root-one-x/). He succeeded in doing so and decided to move onto flashing the rom.
But the problems started when he read that he's first supposed to flash "Android Fastboot kit 2.1" onto the device, prior to flashing the device. And so he did. Or well, tried - what he told me was that he booted the phone into fastboot mode, then ran the "Install Boot.img" bat file inside the Fastboot Kit folder he downloaded and after that, the phone got bricked.
Now, my knowledge in this area isn't too great either, but I've flashed a few ROMs in my life before, so, I decided I'd do my best to help. But I have no clue on what steps he should take from here on.
To my understanding, he was running the official 1.29 version and he is still able to access the boot-loader as well as Clockwork Recovery mod. To my understanding, he didn't create a back-up of his previously working ROM and the phone won't show up in Windows Explorer while connected via USB either.
To my limited understanding, I should now try and install the rom onto his phone and once done, the whole thing should work - the only problem with that is the fact I can't get the ROM zip onto the SD Card right now, as explorer won't recognize it. So far, I tried using ADB to push the ROM file onto the phone, but every time I use the command "adb shell mount /sdcard" I get a "Device not foound" error. So, I'm kinda stuck here right now. If this even is the right way to solve the issue, that is.
So, like I said, I'm having a hard time grasping the start and the end of this issue myself, and if there is any additional information needed, I'll do my best to find out more about it - I do have the phone in my possession at the moment as well.
Thanks a lot to anyone who'll offer any kind of help!
Click to expand...
Click to collapse
The latest Clockwork jobby will allow you to mount the sdcard as USB drive.
Other than that, you seem to be on the right track.
^ he's right
What you want to do is first download the 5.8.4.0 version of the endeavoru CWM recovery.
reboot to your bootloader, make sure you're in fastboot and flash the new recovery img.
After you have successfully flashed the new recovery, well... go to the recovery
On the recovery, tap mounts and storage, then tap Mount USB. VOILA!!!!!
Yeah, I forgot to mention that I've already tried mounting the SD Card via Clockwork Recovery - I get an error saying "Unable to open ums lunfile (No such file or directory exists). So that doesn't seem to be an option either, unless you have an idea on how to counter this?
EDIT: Ah, I see - he's using an older version. I'll get the latest one on board and give it a go. Will have to wait a bit for the phone to charge up first it seems though. Not enough battery to do it right now .
Thanks!
And voila! The phone is operational.
Thanks a lot for the help and, I just hope I never manage to half-brick my own HOX .
Hello. I've spent about the past 2 hours trying to figure this out. So, how this started was, a while back when I first got the phone, I wanted 4.4, so I rooted my phone, and tried to flashify a recovery like CWM and TWRP. Both of these failed. I tried many times, and no matter what I tried, flashing always failed. But guess what, my stock recovery was erased in the process. I forgot about it until today, where I found the OTA update to 4.4 was released, and attempted to do it. To my dismay, I forgot I had no recovery mode, and instantly got the "boot certification verify" error screen. Now All I can access is download mode, to my knowledge. So I've been trying to fix this, either by installing stock recovery, or another way to install a custom. All to no avail. When I use the lg flash tool for the stock recovery, it fails at "BIN CRC Check". Every.... Single.... Time. Despite downloading multiple replacement files. I would be perfectly content with installing a customer recovery, but the ways I see require the phone to be on, and use the built in recovery mode. At this point, my phone is bricked, and I am looking for any and all ways to either A) boot back up normally without installing a recovery and fix it later, or B) install a recovery, even if it's the hard way.
Update:
I followed this thread:
http://forum.xda-developers.com/show....php?t=2582142
It looked like it was going to work. I am using a Xubuntu virtual machine. I was copying the files over, and every time it finished copying a file, it unmounted and remounted my phone (I don't know if that was suppose to happen, just worth mentioning if it wasn't suppose to). I was super excited to do it. Hard rebooted my phone. And now it's just a blank screen. I have no logo, no error, and no download mode like I had before. Seriously need some help here.
Update#2:
I have the flash tool correctly working. Awesome! But..... I still have no download mode here.... So I can't use the tool....
Update
I followed the thread:
http://forum.xda-developers.com/showthread.php?t=2582142
It looked like it was going to work. I am using a Xubuntu virtual machine. I was copying the files over, and every time it finished copying a file, it unmounted and remounted my phone (I don't know if that was suppose to happen, just worth mentioning if it wasn't suppose to). I was super excited to do it. Hard rebooted my phone. And now it's just a blank screen. I have no logo, no error, and no download mode like I had before. Seriously need some help here.
I'm decently surprised NO ONE has replied here.
EDIT: SOLVED. After some hours at work I was able to boot back to the bootloader and flash the images individually.
TL;DR at the bottom.
Hi, I've been rooting and ROMming for a while now, and last night I made a mistake that set forth a chain of depressing events. I have a N7 2013 LTE, and was running AOKP up until last night. I wanted to flash the 9001 L preview, despite having no access to data. Simple right? Wrong, you forget to realize I'm a tired idiot last night. I downloaded the zip no problem, rebooted to TWRP and commenced my advanced wipe. Some how, I mistakenly checked off "wipe internal storage" during the process. So I go back to the Install screen, and my heart sinks. F***. At this point I decide to let it lie in recovery until tomorrow (today) and keep it charged.
Fast forward to this morning, I'm at the office. My device is charged and waiting in recovery. I decide I'm just going to flash the factory image to stock 4.4 and start with a clean slate, wiping all (even though it's wiped). Reason for factory image and not just adb push the ROM is that I'm having a seemingly-unsolvable issue of incorrect storage. It tells me my 32gb device only has 11.6 gb total storage. This has persisted through multiple clean-wiped installs of various ROMs, but I don't know if it started out like that when I bought it, since I didn't think to check before unlocking and putting a ROM on it.
So I get the SDK and images on my work PC, and commence flash-all.bat. Working great until it gets to system.img, then it fails. Try again twice, same thing. Open the image zip and extract the files, then try to flash one by one, now it's saying the commands are invalid (fastboot flash system system.img, etc). So I wonder, because sometimes these devices are wonky in ADB, maybe it installed and just said it failed? F*** it, I'll try to boot. Google logo for an hour. Ok, cool, I'll go back to the bootloader. NOPE. The device either won't power on at all, or it will get stuck at the splash screen and hang there. Any idea where to begin to fix this?
TL;DR: No OS on phone, failed flashing system.img in flash-all.bat, now device won't boot to bootloader or (missing) OS. Any ideas?
Expert advice needed please. This is a puzzle that someone might enjoy solving.
Although I have a fair bit of experience with flashing, I tried to flash my 8.0 for the first time and it has dramatically failed. It was probably my fault - not an uncommon story.
What is less common is that I am struggling to figure out how to undo the damage I've done. What's really making this difficult is that no computer recognises the device as USB any more so I can't use Odin, Kies, etc to repair or return to stock. I have tried everything I can think of to deal with the USB issue, the usual cable, driver, port nonsense. I don't think the USB problem is Windows now.
I suspect one of these things may have happened:
The USB port just went bad coincidentally during this flash process (charge, no data). I have ordered a new port but it will take weeks to arrive.
Has the device come out of Developer/USB debugging mode somehow? I can't tell because I can't boot to an OS.
I wonder if the ROM flash has corrupted the firmware the deals with USB - is that possible? Where is the devices USB drivers located? Is it in the bootloader, something like BIOS?
I'm suspicious of the bootloader, as the screen is weirdly corrupted now when I turn on or reboot the device - fuzzy white lines rather than a logo - but that disappears when OS tries to load, or I go into Recovery/Download.
I actually did do a backup of the original ROM to the SD card; but restoring it doesn't work, just produces an endless Samsung boot, even if I then wipe and reset.
I can get into Download mode, and a Recovery (Philz for N5120) but since I can't connect to the devise with USB in any way, it's very hard to get the Recovery to flash anything new and useful. I did put my SD Card in another phone and copied over the stock ROM zip from Samsung, but it refuses to flash - I think because it doesn't like Philz Recovery? I can't think how to replace Philz Recovery with another by flashing, without USB.
I may have to wait to replace the USB port, but I fear that won't fix it. Until then, I can only think of one other thing to try, and that is to copy a ROM onto the SD Card through another phone, and try to flash it. Lineage doesn't flash, and nor does the stock zip I got from Samsung. Would anything else work?
Can I flash an alternative recovery from within the recovery? Philz only lets me flash zips, not img or tars.
So it's quite a mess, but if anyone has a brilliant idea of how to get out of this, I'd love to hear it.
THANK YOU if you have a genius idea.
So after a few days of working on this, I did manage to resolve it, and I thought I'd just add a note about how I escaped this obscure problem.
The device went bad because I stupidly flashed an incompatible Recovery to the device and somewhere between doing this, backup and restoring and flashing, it corrupted mostly everything including something in the bootloader.
Oddly enough, the solution seemed to be to mess up the Recovery even more by flashing something even more random - it seems this provoked the device into restoring its own basic Recovery. Using this to wipe and reset the device somehow enabled Download mode's USB interface to start working again so I was able to use Kies to return to stock, which repaired everything including the bootloader.
Finally, I flashed the correct Recovery for this device, and then managed to flash the ROM I wanted. A happy ending to a stressful story; the device now works better than it ever has done before.