So before my phone got bricked, I first had been notified that there was an update for it's OS. So while I updated it, I noticed that it took quite a while. I fell asleep. When I woke up, it was on recovery mode. I tried wiping data & cache, but it doesn't work and says "Wipe data and cache failed".
I tried fastbooting. It worked when I flashed boot.img but when I tried on recovery.img it says that:
sending 'recovery' (5612 KB)...
OKAY [ 0.203s]
writing 'recovery'...
FAILED (remote:
partition 'recovery' not support flash)
finished. total time: 0.234s
I can somehow flash the recovery.img but that's about it.
Note that when I try to enter USB Mass Storage Mode and connect it to my PC, it somehow gets detected, but when I try to get in through internal storage it'll say "Please insert a disk to Removable (H".
I also tried removing the battery and then connecting it to my computer and the phone vibrates nonstop. It gets detected in the computer for a few seconds (I checked in the Device Manager and yes, I already installed drivers) and then vanishes. I also tried using SP Flash Tool
What do I do?
Note: Phone is rooted.
Related
After I rooted my phone with LGPwn, I was attempting to set partitions on my sd card so that I would be able to use Link2SD. However, after I partitioned my phone, link2sd did not recognize my second partition, saying that it wasn't mounted, so I decided to reboot. After my phone shut off, It never turned back on. I have tried home, vol down, power, taken out battery, etc. When it is plugged into my pc, the computer seems to recognize it for a few seconds, and then disconnects. How do I fix this?
Have the same problem. Please HELP !
1pan1 said:
After I rooted my phone with LGPwn, I was attempting to set partitions on my sd card so that I would be able to use Link2SD. However, after I partitioned my phone, link2sd did not recognize my second partition, saying that it wasn't mounted, so I decided to reboot. After my phone shut off, It never turned back on. I have tried home, vol down, power, taken out battery, etc. When it is plugged into my pc, the computer seems to recognize it for a few seconds, and then disconnects. How do I fix this?
Click to expand...
Click to collapse
I have the exact same problem. Was using an app to create an ext2 partittion on my SD card, to use Link2sd. Ended up formating my phone. Now it wont do anything, it does not turn on in any way. My computer recognizes the phone when I connect it ( had to install some drivers). Im able to boot into fastboot mode. Now my question is how do i fix my partions. I have tried the following comands and this is what I get.
C:\fastboot\yours>fastboot erase system
erasing 'system'...
OKAY [ 0.173s]
finished. total time: 0.176s
C:\fastboot\yours>fastboot erase recovery
erasing 'recovery'...
FAILED (remote: : partition doesn't exist)
finished. total time: 0.007s
C:\fastboot\yours>fastboot erase boot
erasing 'boot'...
FAILED (remote: : partition doesn't exist)
finished. total time: 0.011s
C:\fastboot\yours>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.289s]
finished. total time: 0.292s
C:\fastboot\yours>fastboot erase splash
erasing 'splash'...
FAILED (remote: : partition doesn't exist)
finished. total time: 0.007s
C:\fastboot\yours>fastboot erase cache
erasing 'cache'...
OKAY [ 0.127s]
finished. total time: 0.130s
I guess my question is, what are the command to reformat and fix my partition . Please Help, This is my first brick.
Simply try to restore it through LG official tool :
http://forum.xda-developers.com/showpost.php?p=40423549&postcount=2
OperationNT said:
Simply try to restore it through LG official tool :
http://forum.xda-developers.com/showpost.php?p=40423549&postcount=2
Click to expand...
Click to collapse
I would.... but the thing is that to use the LG Software you need to put the phone in " S/W mode" and like I said before the phone does not turn on in any way (not even in S/W mode) because i formated the partitions. All I'm able to do is put on the phone in fastboot mode (the screen with the inverted LG logo, that says fastboot v5.0 on the top).
Thank for the suggestion though.
Are you sure ?
For example, if you remove the battery, then plug your phone in your computer USB without battery and finally maintain the Vol+ button while it's plugged, the device doesn't turn on in "S/W Upgrade" ?
I always thought "S/W Upgrade" mode was a very low level feature but maybe I am wrong.
OperationNT said:
Are you sure ?
For example, if you remove the battery, then plug your phone in your computer USB without battery and finally maintain the Vol+ button while it's plugged, the device doesn't turn on in "S/W Upgrade" ?
I always thought "S/W Upgrade" mode was a very low level feature but maybe I am wrong.
Click to expand...
Click to collapse
Nope, already tried it. I think I formatted the partition that had the img file for S/W Update .......
The only solution I have found is to boot into fastboot mode... All I need is the command or way to reformat or fix the partitions using fastboot.
Bump .. Found I guy who had the same problem and created a guide on how to fix it, here is a link http://forum.cyanogenmod.com/topic/71825-hard-brick-to-hell-and-back-guide-to-recovery/.... Now if we can just find a way to apply the same method to our LG L9, then maybe we could fix the phone.
I hope you can find a solution to your issue. But, while I was reading the solution for E730, I see one issue : when you extract KDZ files from P760 firmware, you only get ".bin" and ".fls" files.
I don't know how those files can be extracted again to get the real final files. I saw this issue with V20I_00.kdz, maybe you could try an older version such as V10A_00.kdz.
Good luck !
EDIT : Did you try this solution ?
http://forum.xda-developers.com/showthread.php?t=2612356
Try flashing ics x and u in fastboot. See if you're able to get a boot to s/w upgrade mode.
I downloaded a stock firmware (V20a D618) and at installation via LG Flash Tool, the USB cable was left with bad contact and gave installation error; After that when I turn on my phone it is only showing the logo of LG and the upper right corner appears:
"[710] fastboot_init()
[810] USB init ept @ 0x1001d000
[830] udc_start()"
I can't enter in download mode, fastboot, recovery, bootloader, nothing...
Any solution???? :crying:
(sorry to my english.)
You need to reflash your system.
But first, try to flash proper boot.img for your device.
Search on XDA.
If you done it correctly, your phone boots up straight to the bootloader.
Try also this trick :
0. Turn off your phone (dOH!), take out battery pack for about 20sec and re-insert battery.
1. Hold VOLUME DOWN and POWER BUTTON.
2.After LG logo, right away, LET DOWN POWER BUTTON and PRESS IT AGAIN AND HOLD.
3. Maybe that will put into download mode.
(It should'nt because its for factory reset, but who knows?)
SuperBadGateway502 said:
You need to reflash your system.
But first, try to flash proper boot.img for your device.
Search on XDA.
If you done it correctly, your phone boots up straight to the bootloader.
Try also this trick :
0. Turn off your phone (dOH!), take out battery pack for about 20sec and re-insert battery.
1. Hold VOLUME DOWN and POWER BUTTON.
2.After LG logo, right away, LET DOWN POWER BUTTON and PRESS IT AGAIN AND HOLD.
3. Maybe that will put into download mode.
(It should'nt because its for factory reset, but who knows?)
Click to expand...
Click to collapse
I tried send the command "fastboot flash boot boot.img" but I always have message
"C:\Users\David\Downloads\LG>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (15872 KB)...
OKAY [ 0.703s]
writing 'boot'...
FAILED (remote: unknown command)
finished. total time: 0.719s"
however when I run the command, the phone receives, but it does not know how to execute, how do I make him accept commands???
(sorry to my english)
bieldobaixo said:
I tried send the command "fastboot flash boot boot.img" but I always have message
"C:\Users\David\Downloads\LG>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (15872 KB)...
OKAY [ 0.703s]
writing 'boot'...
FAILED (remote: unknown command)
finished. total time: 0.719s"
however when I run the command, the phone receives, but it does not know how to execute, how do I make him accept commands???
(sorry to my english)
Click to expand...
Click to collapse
I don't know why your phone doesn't accept the boot.img (maybe try another boot.img ?).
But in case that won't work, you can always try to enter download mode by this method :
http://forum.xda-developers.com/g2-mini/general/guide-unbrick-bricked-wrong-aboot-img-t3128896
In summary : let your battery goes 0%, then try to power the phone, it won't and will show you the low battery icon : at this moment, press and hold the volume low button, and connect it to you computer, the phone should enter in download mode. Then you can flash a .kdz .
It worked for me when a realy bricked my phone and cannot acces either the recovery or fastboot .
Hi,
I got my Oneplus X three days back and when booted, the first thing it showed was to update the phone. When I clicked on download, it did download and asked me to install. When I clicked install, it restarted the phone and stayed at "1+" logo for ever without updating or restarting the phone. When I force restarted it (10 seconds power hold), it started, but the update was not applied. I did not have any other option, but to return the phone for a replacement.
Yesterday I received the replacement and to my surprise, it still does not update and stays on the same "1+" icon. To set things right, I thought of installing TWRP and reflash the bootloader, or better install any custom ROM's. While installing TWRP, I unlocked the bootloader and the result was:
Code:
J:\Mobile\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 0.011s]
finished. total time: 0.012s
Once unlocked, it goes back into its own weird "1+" icon and stays there (exiting from fastboot mode). Then when I try to boot into twrp, it says:
Code:
J:\Mobile\Minimal ADB and Fastboot>fastboot boot twrp-2.8.7.0-onyx.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.498s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.498s
Should I now send this device back assuming that this is also a buggy phone, or is there solution to this? Kindly help.
I too have the same device but never came across this prob. Better you replace asap!
Just flash TWRP Recovery and install full 2.1.3 ROM. Do not try to boot it.
bioan said:
Just flash TWRP Recovery and install full 2.1.3 ROM. Do not try to boot it.
Click to expand...
Click to collapse
Thanks for the response guys. Problem solved!
For those of you who are in any case facing this problem, the issue was with SD Card. I removed the SD card (which was formatted using my previous Galaxy S3) and tried updating it and it worked. Now, I formatted the SD card and tried again and I was able to get into bootloader mode.
Hi there. A couple of weeks ago my phone just restarted while writing an e-mail. First I didn't bother, but since then it keeps restarting.
As soon as Android is booted up (at the lockscreen) I got like 2-90 seconds (random), before the phone reboots itself. It does not matter whether I do any type of input or do nothing with it. It just restarts.
Starting the bootloader / recovery does not lead to a restart, the phone keeps active for hours without restarting.
Since the phone has never been modded / rooted / unlocked it is still as it left the factory: Locked Bootloader, S-On, Stock android, no root.
So far, so good, here are three ways with which I tried to make my phone reusable:
Number 1: Flashing RUU via fastboot.
What I did: starting Bootloader -> Fastboot -> Smartphone via USB connected to PC -> starting cmd -> "fastboot oem rebootRUU"
Normally, as far as I know, the phone should restart into the bootloader, what it is NOT doing. It just restarts to the OS. So I restarted it into the bootloader, retyped the fastbood command and kept holding vol- to make sure it is re-entering the bootloader this time. worked BUT without the cmd-notification.
fastboot flash zip firmware.zip (using matching RUU for my branding)
Follwed by this output:
E:\Program Files\ADB>fastboot flash zip firmware.zip
target reported max download size of 1542111232 bytes
sending 'zip' (1294516 KB)...
OKAY [ 42.641s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 144.410s
I tried several times, does not change. I also tried other and older zips from htcdev, didn't change a thing.
Number 2: Firmware-Upgrade w/o PC via 0P6BIMG.zip
Following a HowTo flash a RUU without a PC, I renamed the above mentioned zip to 0P6BIMG.zip and stored it on my external sd card, put it in my phone and started the bootload, which should result in automatically flashing the zip.
The result was:
SD Checking...
Not gift file...
Loading [0P6BIMG.zip]
No image !
Loading...[0P6BIMG.nbh]
No image or wrong image !
Loading... [0P6BIMG.zip]
No image or wrong image !
Of course, I also tried the above mentioned diffenrent zip files, all leading to the same result.
Number 3: Factory Reset.
Ok, after the two solutions above didn't work anyhow, I just tried to do a usual factory reset from the stock recovery.
Bootloader -> recovery -> wipe data/factory reset -> yes, erase all -> done.
Did this two times (just to ensure its wiped) and wiped the cache afterwards. When restarting back to the OS everything was still as I left it, the wipe didn't work...
All my trials let me think about a malfuntioning internal storage? Or what do you guys think I could try before dumping the phone into the trash?
Regards
As I tried nearly everything I will send my One Max to HTC for repair.
Hi,
I'm newb in this forum and i'm looking for your advice and help,
my situation is as titled in the thread...my phone stuck on huawei logo...the situation starts when i'd tried to flash TWRP recovery..but it seems that was a wrong one...after then i erased system (stupid i was :crying: ) trying a factory reset (i'd downloaded the original stock)....this is when things gets worst ...now i can't get into recovery mode and the phone stuck on the logo...one last detail when the phone is turned on and usb connected to the PC the Hisuite seems identifying the phone but couldn't connect...
any help would be very appreciated
thank you all for your time,
BoFar said:
Hi,
I'm newb in this forum and i'm looking for your advice and help,
my situation is as titled in the thread...my phone stuck on huawei logo...the situation starts when i'd tried to flash TWRP recovery..but it seems that was a wrong one...after then i erased system (stupid i was :crying: ) trying a factory reset (i'd downloaded the original stock)....this is when things gets worst ...now i can't get into recovery mode and the phone stuck on the logo...one last detail when the phone is turned on and usb connected to the PC the Hisuite seems identifying the phone but couldn't connect...
any help would be very appreciated
thank you all for your time,
Click to expand...
Click to collapse
FYI,
now i can get into bootloader but without a recovery...
with the already downloaded stock rom i'd extracted all IMG files from the UPDATE.APP.
the step where i'm stucking is that flashing system with fastboot gives this :
target reported max download size of 266338304 bytes
erasing 'system'...
OKAY [ 1.094s]
sending sparse 'system' (259466 KB)...
OKAY [ 17.422s]
writing 'system'...
FAILED (remote: size too large)
finished. total time: 18.547s
the system.img is 2.39 Go.
same things and messages happens with recovery & boot files [ FAILED (remote: size too large) ]
I thank you advising how to resolve this
[SOLVED]
Here's steps that I made (after a long search with Dr. GOOGLE ):
1- Download & install the Android Studio and its SDK tools (that include fastboot and adb latest version). when having the famous message of FAILED (....TOO LARGE) use the -S switch and be patient with SYSTEM.IMG since file size is big (first tries gave me the error message but after many try it works),
2- Download the official stock ROM from Huawei webpage,
3- Download Huawei Update extractor,
4- Extract BOOT.IMG & RECOVERY.IMG & SYSTEM.IMG from the UPDATE.APP extracted file,
5- flash sequentially : RECOVERY then BOOT then SYSTEM (Remember the reboot after each flash),
That's all...Folks