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.
Related
I have come across several posts the are identical or very similar to my issue. However, I am having an additional issue which seems to be the cause of my not being able to unbrick. I'll try to provide enough details, but let me know if I missed something important.
My prime appears to be completely bricked, because I tried to fix another problem. When I tried to upgrade a stock ICS prime to JellyBean, I had many problems because the recovery kept error out with the droid guy with the red triangle and ! symbol. Somehow, I ended up actually do it and ended up with the US_epad-user-10.4.2.15.zip rom (US_epad-10.4.2.15-20120917). Because I am overseas, I had problems installing some things in the market and was considering root or a custom rom. At some point, I unlocked the device, which still displays clearly every time I boot. While look through several things that appeared very straight-forward, I ultimately ended up with a brick. The device is stuck on the splash screen. I have access to fastboot. However, adb doesn't recognize the device.
When trying to RCK (or wipe data) from the bootloader, I get:
Code:
Booting Recovery kernel image
Booting failed
[COLOR="Red"]Unrecoverable bootloader error (0x00000000).[/COLOR]
This post:
[Q] Transformer Prime possibly bricked. Help?
appeared identical to my current problem. The suggested use of universal drivers has not helped, however.
This post:
[SOLVED] Can access fastboot but can't get past splash screen
also appears identical...
These two also appears to provide hope:
[GUIDE] nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]- TF201
[ROOT] Urkel's Fresh Start 1.0 (Jelly Bean - Unlocked bootloaders only)
...but ultimately, continue to evade my tablet.
Why? you may ask...
Well, it seems that I can boot into fastboot. When I manually run any command, it seems to work fine. But the prime becomes unresponsive to all subsequent commands. It requires that I force reboot and re-enter fastboot. When I try to run Urkel's Fresh Start, the wiping all runs smoothly, and the staging command
Code:
fastboot -i 0x0b05 flash staging system.blob
run smoothly. From that point, it becomes unresponsive again. It appears that although the flashing completes without errors, it doesn't take...or perhaps is inaccessible because the bootloader is jacked. Here's the output from Urkel's Fresh Start, for example:
Code:
Press any key to continue . . .
.: Now cleaning the TF201 partitions :.
erasing 'cache'...
OKAY [ 2.160s]
finished. total time: 2.160s
******************************
erasing 'userdata'...
OKAY [ 39.644s]
finished. total time: 39.645s
******************************
erasing 'recovery'...
OKAY [ 1.953s]
finished. total time: 1.954s
******************************
erasing 'staging'...
OKAY [ 0.948s]
finished. total time: 0.948s
******************************
erasing 'system'...
OKAY [ 2.208s]
finished. total time: 2.209s
******************************
.: Partitions now clean, continuing to reboot back into bootloader. Do not miss
selecting FASTBOOT with VOL+D and then VOL+U on the USB Icon. If you miss it no
big deal reboot back into FASTBOOT before continuing :.
Press any key to continue . . .
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
.: Confirm you are in FASTBOOT before continuing to flash a fresh image/blob. Th
is will take 3-5 minutes because of the size of the image :.
Press any key to continue . . .
sending 'staging' (537604 KB)...
OKAY [ 94.723s]
writing 'staging'...
OKAY [ 1.329s]
finished. total time: 96.054s
rebooting...
finished. total time: 0.548s
.: No need to set up the tablet but let the tablet fully boot to welcome screen
then hold down the power to shut if off. When off turn it back on and enter FAST
BOOT. Once at FASTBOOT then continue :.
Press any key to continue . . .
It appears fine...however, it doesn't reboot, even thought the command said it was successful. So, I try manually rebooting and get stuck at the welcome screen again. It's a vicious cycle... Anyhow, this type of situation is the same for all of the other workarounds that I have found to this problem.
It seems that fastboot is semi-responsive, but no actions that I take are recognized upon reboot. I would love to try and figure out why fastboot is having these issues... and unbrick my tablet. So, please let me know if I have missed any threads that have exactly this solution (ie. fastboot works...but not really).
Thanks in advance, and let me know if I missed details that are necessary.
flueterflam said:
I have come across several posts the are identical or very similar to my issue. However, I am having an additional issue which seems to be the cause of my not being able to unbrick. I'll try to provide enough details, but let me know if I missed something important.
My prime appears to be completely bricked, because I tried to fix another problem. When I tried to upgrade a stock ICS prime to JellyBean, I had many problems because the recovery kept error out with the droid guy with the red triangle and ! symbol. Somehow, I ended up actually do it and ended up with the US_epad-user-10.4.2.15.zip rom (US_epad-10.4.2.15-20120917). Because I am overseas, I had problems installing some things in the market and was considering root or a custom rom. At some point, I unlocked the device, which still displays clearly every time I boot. While look through several things that appeared very straight-forward, I ultimately ended up with a brick. The device is stuck on the splash screen. I have access to fastboot. However, adb doesn't recognize the device.
When trying to RCK (or wipe data) from the bootloader, I get:
Code:
Booting Recovery kernel image
Booting failed
[COLOR="Red"]Unrecoverable bootloader error (0x00000000).[/COLOR]
This post:
[Q] Transformer Prime possibly bricked. Help?
appeared identical to my current problem. The suggested use of universal drivers has not helped, however.
This post:
[SOLVED] Can access fastboot but can't get past splash screen
also appears identical...
These two also appears to provide hope:
[GUIDE] nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]- TF201
[ROOT] Urkel's Fresh Start 1.0 (Jelly Bean - Unlocked bootloaders only)
...but ultimately, continue to evade my tablet.
Why? you may ask...
Well, it seems that I can boot into fastboot. When I manually run any command, it seems to work fine. But the prime becomes unresponsive to all subsequent commands. It requires that I force reboot and re-enter fastboot. When I try to run Urkel's Fresh Start, the wiping all runs smoothly, and the staging command
Code:
fastboot -i 0x0b05 flash staging system.blob
run smoothly. From that point, it becomes unresponsive again. It appears that although the flashing completes without errors, it doesn't take...or perhaps is inaccessible because the bootloader is jacked. Here's the output from Urkel's Fresh Start, for example:
Code:
Press any key to continue . . .
.: Now cleaning the TF201 partitions :.
erasing 'cache'...
OKAY [ 2.160s]
finished. total time: 2.160s
******************************
erasing 'userdata'...
OKAY [ 39.644s]
finished. total time: 39.645s
******************************
erasing 'recovery'...
OKAY [ 1.953s]
finished. total time: 1.954s
******************************
erasing 'staging'...
OKAY [ 0.948s]
finished. total time: 0.948s
******************************
erasing 'system'...
OKAY [ 2.208s]
finished. total time: 2.209s
******************************
.: Partitions now clean, continuing to reboot back into bootloader. Do not miss
selecting FASTBOOT with VOL+D and then VOL+U on the USB Icon. If you miss it no
big deal reboot back into FASTBOOT before continuing :.
Press any key to continue . . .
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
.: Confirm you are in FASTBOOT before continuing to flash a fresh image/blob. Th
is will take 3-5 minutes because of the size of the image :.
Press any key to continue . . .
sending 'staging' (537604 KB)...
OKAY [ 94.723s]
writing 'staging'...
OKAY [ 1.329s]
finished. total time: 96.054s
rebooting...
finished. total time: 0.548s
.: No need to set up the tablet but let the tablet fully boot to welcome screen
then hold down the power to shut if off. When off turn it back on and enter FAST
BOOT. Once at FASTBOOT then continue :.
Press any key to continue . . .
It appears fine...however, it doesn't reboot, even thought the command said it was successful. So, I try manually rebooting and get stuck at the welcome screen again. It's a vicious cycle... Anyhow, this type of situation is the same for all of the other workarounds that I have found to this problem.
It seems that fastboot is semi-responsive, but no actions that I take are recognized upon reboot. I would love to try and figure out why fastboot is having these issues... and unbrick my tablet. So, please let me know if I have missed any threads that have exactly this solution (ie. fastboot works...but not really).
Thanks in advance, and let me know if I missed details that are necessary.
Click to expand...
Click to collapse
If you don't have universal naked drivers downloaded and installed, do that.... also you should install twrp as your recovery, just make sure you get the right one.... I think I read at the top you installed JB so your bootloader is probably JB...... don't install the ics twrp over the jb bootloader or you will have a unrecoverable mess I think.....
Gage_Hero said:
If you don't have universal naked drivers downloaded and installed, do that.... also you should install twrp as your recovery, just make sure you get the right one.... I think I read at the top you installed JB so your bootloader is probably JB...... don't install the ics twrp over the jb bootloader or you will have a unrecoverable mess I think.....
Click to expand...
Click to collapse
Hey thanks for the help. Unfortunately, as I mentioned, I already tried the naked drivers to no avail. Just to be safe, I tried once more, removed/deleted/uninstalled the drivers and even force turned off driver installation for good measure to make sure. I have the same behavior with both the ASUS drivers and the Universal Naked drivers.
I think I forgot to mention explicitly that I tried installing twrp as recovery. I was careful to get the JB bootloader. It hasn't helped. I tried it again today after the re-install of naked drivers. Same behavior as before. Fastboot appears to flash the blob successfully,, but then the prime becomes unresponsive, will not reboot via fastboot, and sticks at flash screen and no RCK.
Any other things that I could have missed or done incorrectly?
Bootloader Error
Hi,
any solution to this yet? I do have the exact same problem!
It seems to me the procedure is locked and it accepts only one comand (maybe the key) then rejects al subsequent comands.
.
From everything I have seen "Unrecoverable bootloader error" means exactly what it says. its unrecoverable. You need a new motherboard
Bootloader Error
Well, that's exactly what Asus wants us to think. My logical thinking tells me there is no defect other than a software failure in connection with Asus locking down bootloaders in order to torture their customers.
I can still access Fastboot, it is just locked down. I guess the first comand (which it always accepts should be a key to unlock the fastboot procedure, without that key nothing is possible. Why can they not recover it at the service center? Maybe they do not want the key to get public.
It's all business after all.
Still, they use open source software for free and then neglect warranty...
I just cannot understand. Well, not Asus for me again I guess...
whycali said:
From everything I have seen "Unrecoverable bootloader error" means exactly what it says. its unrecoverable. You need a new motherboard
Click to expand...
Click to collapse
Same problem, posted http://forum.xda-developers.com/showthread.php?t=2154851
Hi @all!
I just 'tried' to root my ASUS Memopad FHD 10 16GB (WW-version).
I post here because I simply think that you guys at XDA are certainly the ones who know the solution, if there is one.
It seems as if the userdata+cache partitions are "destroyed" or something like that.
Having Android 4.3 it was not possible to flash the rooted system-image, so I first wanted to "downgrade fastboot" to the version from the "WW_ME302C-V4.7.3-0-ota-user.zip" firmware and then try again flashing the 4-7-3 firmware. But after flashing fastboot, when I tried wiping all data I got this:
-----------------------
fastboot erase system
fastboot erase cache
fastboot flash fastboot fastboot.img
fastboot -w
erasing 'userdata'...
OKAY [ 15.292s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 1.634s]
erasing 'cache'...
OKAY [ 3.607s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 1.186s]
finished. total time: 21.729s
-----------------------
Since then I cannot format the partitions or userdata. Flashing the firmware 'supposedly' works (console output on PC says 'finished').
But after "fastboot flash update WW_ME302C-V4.7.3-0-ota-user.zip" is done the device restarts immediately, then
1. shows the android figure with opened hatch and a green progress bar
2. figure changes to one having a red triangle inside
3. reboot and then showing the ASUS bootscreen for like 10min.
4. The last step repeats like 4 times, then the android figure with red triangle appears again, then bootscreens again ... (endless loop)
So as you can see I cannot boot into android again. I think the problem lies with the "File system type not supported" but.
When I try to format directly I get:
-----------------------
fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type ''.
FAILED ()
finished. total time: 2.303s
-----------------------
Does anyone know how I can fix this and reinstall any firmware?
My ideas were
- format the partitions to ext2/ext3 directly (there should be a way to specify the filesystem, right?)
- flash the userdata/cache partition with someone else's partition content
- use a custom-recovery for the tablet which does this - though I cannot find one anywhere
Thanks XDA! =)
-------------------------------------------------------------------------------------------
SOLVED
-------------------------------------------------------------------------------------------
Thanks to perpe and wakatu the problem has been solved by flashing the original recovery, as specified here:
http://www.android-hilfe.de/asus-me...0-9-4-3-fehlgeschlagen-brick.html#post7005266
Plzzzzzzzzz help meee
hi guys
i have asus memo pad fhd 10 302KL with soft bricked problem ( stuck at asus logo ) i try to use Volume UP + Power to go to recovery but nothing at all only asus logo...
so i try Volume Down + Power i got fast boot screen i use fastboot devices got answer from fastboot i try to flash with fastboot from original aSUS image files but nothing...
i think boot loader is locked only way to unlocking boot loader is apk from asus website? i don't have any os to install apk what should i do now plzzzzz help me.
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 .
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.
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.