I was going to install a new rom with TWRP, so I formatted data, cache, dalvik cache and system, but I accidentally formatted my micro SD card too, where I kept the rom zip and the previous rom backup. I couldn't do anything, so I powered off the phone, took the micro SD and put the rom in it.
But now I can't access the recovery (I've tried many button combinations, and none of them has worked). I can boot into fastboot, but it's not recognised by my computer (Win8.1 x64).
I've tried with the LGFlashTool offline kdz flashing guides here at xda, but unfortunately, none of them has worked.
My phone is softbricked now. Any help, please?
Try to go to download mode and flash kdz firmare (I said it a lot today, hah). Did you try to install artas recovery? I remember I had similar issue on it.
You can also try to reinstall l9 driver and try to connect by fastboot and install another recovery.
Rammar515 said:
Try to go to download mode and flash kdz firmare (I said it a lot today, hah). Did you try to install artas recovery? I remember I had similar issue on it.
You can also try to reinstall l9 driver and try to connect by fastboot and install another recovery.
Click to expand...
Click to collapse
I've tried several guides for flashing KDZ, but none of them has worked yet
It was artas' TWRP
If could enter the recovery, it would be solved, but I don't know if I can after formatting /system
Related
I wanted to install a custom ROM for my TF201. So I downloaded the Energy ROM and placed it within the SD Card as update.zip
I flashed CWM and ran the Asus Bootloader Unlocker.
Then using Rom Manager rebooted into CWM, following on screen prompts I installed from SD Card the ROM. The install completeted successfully, the tablet restarted and showed the Eee Pad logo, but got stuck. I've tried cold booting from recovery mode, tried reinstalling the ROM but nothing is working. It is refusing to boot up properly.
Have I bricked the tablet, if so how do I fix it if at all possible?
geon106 said:
I wanted to install a custom ROM for my TF201. So I downloaded the Energy ROM and placed it within the SD Card as update.zip
I flashed CWM and ran the Asus Bootloader Unlocker.
Then using Rom Manager rebooted into CWM, following on screen prompts I installed from SD Card the ROM. The install completeted successfully, the tablet restarted and showed the Eee Pad logo, but got stuck. I've tried cold booting from recovery mode, tried reinstalling the ROM but nothing is working. It is refusing to boot up properly.
Have I bricked the tablet, if so how do I fix it if at all possible?
Click to expand...
Click to collapse
Did you do an MD5sum check on your download? Also have you tried flashing another rom? And my third and final question did you wipe Dalvik cache, cache, and factory reset before you installed?
And this is more of a preference thing but I'd suggest TWRP over CWM. I've had issues on other devices with CWM but TWRP on the Prime is perfect.
McJesus15 said:
Did you do an MD5sum check on your download? Also have you tried flashing another rom? And my third and final question did you wipe Dalvik cache, cache, and factory reset before you installed?
And this is more of a preference thing but I'd suggest TWRP over CWM. I've had issues on other devices with CWM but TWRP on the Prime is perfect.
Click to expand...
Click to collapse
I did a factory reset, then selected wipe Dalvik cache and cache.
How would I flash another ROM? I'm not sure how I can get another ROM onto the device as CWM cannot search external storage, only internal?
I was going to use TWRP but wasn't sure how to get it flashed onto the device, where as CWM was simpler. I didn't do an MD5 check on the ROM
EDIT:
Just tried using Fastboot USB to flash the official ASUS ROM(Tried latest JB and ICS 4.0.3), both write to the device okay but both fail
It says "FAILED <Remote: <>"
On the device it shows: Failed to process command flash:system error(0x170003)
geon106 said:
I did a factory reset, then selected wipe Dalvik cache and cache.
How would I flash another ROM? I'm not sure how I can get another ROM onto the device as CWM cannot search external storage, only internal?
I was going to use TWRP but wasn't sure how to get it flashed onto the device, where as CWM was simpler. I didn't do an MD5 check on the ROM
EDIT:
Just tried using Fastboot USB to flash the official ASUS ROM(Tried latest JB and ICS 4.0.3), both write to the device okay but both fail
It says "FAILED <Remote: <>"
On the device it shows: Failed to process command flash:system error(0x170003)
Click to expand...
Click to collapse
IT LIVES!!!
Don't know how I did it, but I managed to get TWRP installed on it. Using Fastboot somehow or ADB. It booted into TWRP and mounted external SD card, then flashed an official JB ROM(the Prime was on ICS before) and it has now booted up fine
I will now try and re-flash a custom ROM again(a different one) using TWRP but it is all looking superb
I was worried i'd have to claim on the extended insurance I took out with the retailer
I was trying to flash CM and made the stupid mistake of only flashing the boot.img and now my dna repeatedly restarts and won't get past the droid light thing. The rom files and gapps are not on my sd card. I can't get a connection to adb and my computer doesn't see the device. ADB will recognize the device at one part during the bootloop but says "offline" right next to it. I'm s-off (moonshine), rooted, and have CWM recovery. I've tried wiping the cache, dalvik cache, and tried a factory reset. None of those worked. If I lose this phone I'm really screwed, is there no way to get out of this?
mistahthron said:
I was trying to flash CM and made the stupid mistake of only flashing the boot.img and now my dna repeatedly restarts and won't get past the droid light thing. The rom files and gapps are not on my sd card. I can't get a connection to adb and my computer doesn't see the device. ADB will recognize the device at one part during the bootloop but says "offline" right next to it. I'm s-off (moonshine), rooted, and have CWM recovery. I've tried wiping the cache, dalvik cache, and tried a factory reset. None of those worked. If I lose this phone I'm really screwed, is there no way to get out of this?
Click to expand...
Click to collapse
Boot in CM recovery and there is an option to connect the phone to the computer as a USB. There you can put the rom files etc and flash it again.
abhi897 said:
Boot in CM recovery and there is an option to connect the phone to the computer as a USB. There you can put the rom files etc and flash it again.
Click to expand...
Click to collapse
I ended up fixing the problem by finding out what sideloading is and sideloading the rom/gapps. Thanks for the help though!
Maybe someone can help me here. Using TWRP 2.8.0.1 I am unable to fully install any rom.
I had slimkat on my phone and decided I wanted to try regular CM 11. So I wiped everything in advanced wipe so I could start fresh.
Put the Rom and Gapps on my phone then tried to flash.
However while installing CM, it just goes about its business until the progress bar hangs at updating partition details.
It also appears I cannot move files to the internal memory from the sd card.
Are my partitions messed up?
All that happens now is getting stuck at the samsung boot logo or rebooting into TWRP...
Any help?
Gorkytje said:
Maybe someone can help me here. Using TWRP 2.8.0.1 I am unable to fully install any rom.
I had slimkat on my phone and decided I wanted to try regular CM 11. So I wiped everything in advanced wipe so I could start fresh.
Put the Rom and Gapps on my phone then tried to flash.
However while installing CM, it just goes about its business until the progress bar hangs at updating partition details.
It also appears I cannot move files to the internal memory from the sd card.
Are my partitions messed up?
All that happens now is getting stuck at the samsung boot logo or rebooting into TWRP...
Any help?
Click to expand...
Click to collapse
Yes partitions could be mixed up but my first port of call would be to return to stock with odin and if that boots and works then start again and don't use twrp try PhilZ recovery.
If partitions are corrupt there are things you can try but I would first try to get your phone to boot then report back.
tallman43 said:
Yes partitions could be mixed up but my first port of call would be to return to stock with odin and if that boots and works then start again and don't use twrp try PhilZ recovery.
If partitions are corrupt there are things you can try but I would first try to get your phone to boot then report back.
Click to expand...
Click to collapse
Thanks for your help! Because of you I tried PhilZ, which then told me it couldn't successfully open/read the rom from the SD card. (Something twrp didn't tell me).
I then changed my SD card for another one I had laying around and it worked. (Strange the old one failed since I formatted it atleast a few times)
Once again, thanks for your tip!
This is now solved!
First let me explain what I did to my device, then I'll explain what I did to get my device back. I was on the latest ZVE build, and decided to flash the new Lollipop update. I flashed it with TWRP, but was supposed to flash it with CMW. so I got stuck on the LG screen. Then I flashed Philz Advanced recovery. so I could flash Lollipop again, so I wiped, data, system, cache, and went to flash, but the rom was not in storage, so I decided to restore my backup, and realized my entire device including device storage had been wiped clean. So, now I could boot into recovery, and download mode, but had nothing to flash to fix the problem, and since I never booted into the OS, I didn't get to enable debug mode. It rendered my flashtool application useless. because it wouldn't install the necessary drivers that you need for download mode to work. I read a topic that explained how to fix a hard brick with Linux, so I tried that but was unable to mount device, but when I used ADB command it recognized the device in recovery. Philz recovery doesn't mount in recovery, but TWRP recovery does, so that was the goal. I used sideload to flashed TWRP through ADB and It worked. Once I got TWRP flashed with sideload the rest is history. Now I can go back to Windows and use my flashtool program to get back to stock ZVE, because now I will be able to install the necessary drivers for flashtool to work. Hope this works for someone else, that gets in the same situation. Happy flashing, and enjoy your New Year.
Ok... So...
I installed fulmics through TWRP and all worked great
After that, I installed a v30 Rom also with TWRP and that worked great, too, but i decided i like fulmics more and wanted to go back
Retried TWRP and kinda worked, but some errors were popping up all the time, so i decide to reinstall it
Now here i am. When it boots, goes straight in TWRP. I tried a stock zip to flash with TWRP, no luck.
When in TWRP I can see the phone on pc, internal storage in empty.
Fastboot works.
When i load up LGUP, under the version tab, it shows fulmics mod and i can't take any action
How fried is it?
Roti23 said:
Ok... So...
I installed fulmics through TWRP and all worked great
After that, I installed a v30 Rom also with TWRP and that worked great, too, but i decided i like fulmics more and wanted to go back
Retried TWRP and kinda worked, but some errors were popping up all the time, so i decide to reinstall it
Now here i am. When it boots, goes straight in TWRP. I tried a stock zip to flash with TWRP, no luck.
When in TWRP I can see the phone on pc, internal storage in empty.
Fastboot works.
When i load up LGUP, under the version tab, it shows fulmics mod and i can't take any action
How fried is it?
Click to expand...
Click to collapse
Try doing a complete wipe, wipe cache, Dalvik, data, system. Then wipe internal storage via the format data option and reboot recovery. I am guessing that you're on the h850 variant so Flash the 20s complete firmware zip then flash SuperSU or magisk. See if it boots into system.
I do still suggest hooking it up to your PC and flashing stock firmware kdz 20s using uppercut. If if it is recognizing fastboot commands then you should have no issue flashing a new recovery image after you load the stock kdz, you may even be able to flash a new recovery image instead of going through all the other steps that I listed. Which may some your issue. But it's best to format data entirely before flashing anymore ROMs, and use lgup via uppercut to flash stock firmware and let it boot entirely before reflashing fulmics.
But formatting data is key to reset the system folders which were leftover from other ROMs and likely the cause of the issues you experienced.