I was trying to flash another ROM and messed up somewhere along the way. So I figured I'd pull out ol' reliable and call up google and do a factory image flash to the device. The device REFUSES to take it. Sometimes I get errors about the file size being too big, sometimes the error just says too many commands.. I've tried multiple different USB ports, I went and bought another cable and tried that still no luck...
I can't even boot the device into recovery. It doesn't want to do anything at all other than sit in the bootloader taunting me, making me regret ever tinkering with my phone. I've tried reinstalling the drivers for the phone as well... Any tips?
duzzqqqq said:
I was trying to flash another ROM and messed up somewhere along the way. So I figured I'd pull out ol' reliable and call up google and do a factory image flash to the device. The device REFUSES to take it. Sometimes I get errors about the file size being too big, sometimes the error just says too many commands.. I've tried multiple different USB ports, I went and bought another cable and tried that still no luck...
I can't even boot the device into recovery. It doesn't want to do anything at all other than sit in the bootloader taunting me, making me regret ever tinkering with my phone. I've tried reinstalling the drivers for the phone as well... Any tips?
Click to expand...
Click to collapse
Hello,
What rom/file did you flash to end up in this situation?
What did you try to flash (factory image) to solve your issue?
Is your platform-tool up to date? (ADB, Fastboot, etc...). If not, you'll find them here:
https://developer.android.com/studio/releases/platform-tools
Sometimes outdated ADB or fastboot can cause issue with new Android version.
Good luck...
Sébastien.
Related
Hey guys! I bought a couple Kindles off Amazon and I'm having some trouble rooting and rom'ing them. I assume they are on the latest software since they came from Amazon, but the KFU does not do anything. If I tried to flash recovery, root or install FFF but it just reboots and comes back on like nothing happened. I ended up getting Ubuntu installed on a USB drive so I could try the soup kit but my Linux knowledge is limited. I was able to finally see both in ADB devices (one would never show up no matter what I did), but again, no matter what I try flashing it just reboots like nothing happened.
Am I missing something here? I can't find anyone having this same issue. I do have a fastboot cable and when I use it and put one into fastboot, it will say fastboot up top and a green and red light below it. Flashing does nothing.
Thanks!
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:
Hello, I've ran into an issue where my phone keeps turning off while in the boot screen. I'm using stock 7.0. What makes it worse is that I can't seem to get ADB connection between PC and phone.
Now I regret my decision of not flashing TWRP earlier, as I wouldn't be making this thread if I had and I could've tried flashing a different rom.
This happened after the phone felt a bit slow, I restarted and then it wouldn't boot anymore.
I have S-OFF if that helps with anything.
Thank you for your help!
_____________________________
Edit:
Right, apparently I can get the adb to work in download mode, but the battery is a bit too low to flash TWRP. I'll see if I can do when it charges a bit.
Edit: So I flashed TWRP, tried flashing a rom and twrp rebooted during the flash.
Edit: I can't even get into download mode anymore. Phone's rebooting and vibrating all the time.
Edit: Welp, can't even get in recovery now. Only place I can access really is the bootloader. Is there anything I can do about it now or is bricked?
So, I tried flashing ruu, getting this -
load_file: could not allocate -2093772439 bytes
error: cannot load 'update.zip'
Click to expand...
Click to collapse
Tried flashing recovery, which did work but I can't boot to it. Getting reboot loops before getting to TWRP.
So I suppose this is it then for this phone unless anyone can help me with it. It's been definitely the most frustrating phone I've owned.
Seems buggered to me. If no download mode then there's not a lot you can do.
Beamed in by telepathy.
Ehh... It's kinda weird how the phone just did that. Tried to flash ROM and it just went.
I kinda feel like it could've been faulty flash all along as I had issues with it where "app has stopped working" was spammed. I factory reset it and it was unusable. Went to O2 for repairs (note that I hadn't meddled with software yet) and they still charged me for it. It worked fine for two weeks and then same issue appeared. Stupid me thinking that trying to fix it by myself could've worked, which I thought I managed to do for a month. Then this happened.
Is there really nothing I can do from the bootloader? fastboot seemed quite functional from it.
Either way, thank you for this answer, even though it was one nobody likes to hear...
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.
Not 100% sure of best place to post this, but I'm getting desperate now...
I'm pretty worried I've killed my device. After following the guide on how to root with Magisk, my phone is stuck on the white "loading" screen with a G logo. I've since tried to restart, but I can either go into fastboot mode or get the white screen when attempting to boot into android.
Tried to flash the latest factory image to fix it, but that couldn't get that to work. Now the phone isn't showing up on adb devices either. panicking a little bit here.
Does anyone know what to do?
ADB won't work unless the phone is booted into Android or in stock recovery for a sideload.
Does your computer recognize the device when you are in Fastboot mode and type "fastboot devices"? Try flashing the factory image again but make sure you have the most up to date platform tools from Google. Old versions are a common cause of issues.
Did you flash TWRP recovery or just boot to it to root? If you still have stock recovery you can try a factory reset from there but any modified images you installed might be the issue.
like Fury said, your platform tools need to be updated, same thing happened to me.
What didn't work when you flashed the factory image? Do you have the latest sdk tools version of fastboot and adb?
Sent from my [device_name] using XDA-Developers Legacy app
fury683 said:
ADB won't work unless the phone is booted into Android or in stock recovery for a sideload.
Does your computer recognize the device when you are in Fastboot mode and type "fastboot devices"? Try flashing the factory image again but make sure you have the most up to date platform tools from Google. Old versions are a common cause of issues.
Did you flash TWRP recovery or just boot to it to root? If you still have stock recovery you can try a factory reset from there but any modified images you installed might be the issue.
Click to expand...
Click to collapse
Thanks so much, this is where I was going wrong. Have gone into recovery and rescued it.
Tried the process again to get Magisk working, but ended up the same although this time the white screen only went on for a while before I got an error saying my data was corrupted. Tbh, after all the stress I'm just going to give up on this and live with the phone in stock. All my drivers and adb were installed and setup today, so everything is up to date.
edit...
Not out of the woods yet. After restarting the phone and going through the setup, it's not detecting the SIM card or any wifi networks. I've installed the OTA and wiped data once more after having this problem, still not resolved.
Nick676 said:
Thanks so much, this is where I was going wrong. Have gone into recovery and rescued it.
Tried the process again to get Magisk working, but ended up the same although this time the white screen only went on for a while before I got an error saying my data was corrupted. Tbh, after all the stress I'm just going to give up on this and live with the phone in stock. All my drivers and adb were installed and setup today, so everything is up to date.
Thanks again for helping.
Click to expand...
Click to collapse
It sounds like you are trying to install Magisk v17.1 like I tried. If so you need to use v17.3 beta. If you follow this thread you should be fine. It even tells you what to do for your original problem, just takes some reading and patience.
Misterxtc said:
It sounds like you are trying to install Magisk v17.1 like I tried. If so you need to use v17.3 beta. If you follow this thread you should be fine. It even tells you what to do for your original problem, just takes some reading and patience.
Click to expand...
Click to collapse
I tried it with both 17.1 and 17.3, so not sure what the issue is. Seem to have finally booted up properly with wifi and signal working, so hopefully it's all good now. Gonna give up on rooting.
Nick676 said:
Not 100% sure of best place to post this, but I'm getting desperate now...
I'm pretty worried I've killed my device. After following the guide on how to root with Magisk, my phone is stuck on the white "loading" screen with a G logo. I've since tried to restart, but I can either go into fastboot mode or get the white screen when attempting to boot into android.
Tried to flash the latest factory image to fix it, but that couldn't get that to work. Now the phone isn't showing up on adb devices either. panicking a little bit here.
Does anyone know what to do?
Click to expand...
Click to collapse
you may want to try to totally uninstalling Magisk frist with the official latest Magisk uninstaller and reboot and then do a complete factory reset. this has helped me in the past.
my new pixel 3XL will be the first Android phone that I owned that will not be rooted.