While trying ti install CM 11 from TWRP i managed to brick the phone. I dont want to waste time sharing the details unless it's need to solve the problem. The main thing is that my phone is now stuck at the LG logo. Previously i was running the CM 10.2 Stable Build.
How can i get back to working condition? Either CM or Genuine LG Rom, I just want my phone to be up and running.
Please Help. I am really scared at this moment.
You don't share any details so I have to guess...
Enter recovery like this http://www.youtube.com/watch?v=ifi-ArGeTzQ , restore your Backup or flash another ROM, done.
muEcke* said:
You don't share any details so I have to guess...
Enter recovery like this http://www.youtube.com/watch?v=ifi-ArGeTzQ , restore your Backup or flash another ROM, done.
Click to expand...
Click to collapse
I can enter both the modes shown in the video.
The thing is i was running CM 10.2 with a TWRP installed of version 2.6.3.2. I downloaded the CM 11 and went into TWRp to flash it but it couldnt flash the CM11. Then after searching the net i found out that TWRP 2.6.3.3 or higher is required to install CM11. The problem is that i wiped my dalvic, data, cache and system and did not keep a backup. So when the Cm11 wont install i was stuck in the TWRP as i didn not have the 10.2 rom file in the phone.
Then downloaded the TWRP 2.6.3.3 and also a CWM zip (just in case). Using ADB i tried to update the TWRM but still some other error shows up. Tried installing the CWm still some error shows up. i tried installing again and this time the recovery asked me to install superuser (though i was rooted). I selected YES and after that i am boot looping in the lg logo.
Anyways thats basically what happened. Now how do i get further and make my phone work again?
Please help brother. I am in deep trouble.
Thank You
Man... always keep a backup, you know, just in case
Shouldn't be a problem at all. You have ADB access right? So here is TWRP 2.6.3.4 those are flashable ZIPs.
Push the file, flash with recovery, reboot to recovery again and you should be on 2.6.3.4. Then flash CM11 and you are good to go...
http://forum.xda-developers.com/showthread.php?t=2469995
muEcke* said:
Man... always keep a backup, you know, just in case
Shouldn't be a problem at all. You have ADB access right? So here is TWRP 2.6.3.4 those are flashable ZIPs.
Push the file, flash with recovery, reboot to recovery again and you should be on 2.6.3.4. Then flash CM11 and you are good to go...
http://forum.xda-developers.com/showthread.php?t=2469995
Click to expand...
Click to collapse
But I am stuck in the LG logo now as i mentioned. I cannot access custom recovery mode (as in TWRP).
in_core said:
But I am stuck in the LG logo now as i mentioned. I cannot access custom recovery mode (as in TWRP).
Click to expand...
Click to collapse
So you can't enter the recovery like shown in the video? And the command adb reboot recovery doesn't work either?
At this point your only option is to return back to stock and start over but with a recovery from the link I provided in the other thread.
http://forum.xda-developers.com/showthread.php?t=2432476
LG G2 Stock Firmware (Go Back to Stock)
Follow the instructions in this thread
Sent from my LG-LS980 using Tapatalk
hellot1M said:
At this point your only option is to return back to stock and start over but with a recovery from the link I provided in the other thread.
http://forum.xda-developers.com/showthread.php?t=2432476
LG G2 Stock Firmware (Go Back to Stock)
Follow the instructions in this thread
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
Ok then i will follow this process and hopefully be successful in getting my phone up and running.
Thanks for the help. Downloading 2Gb will take some time. So will post the result tomorrow.
Regarding rooting and installing custom recovery again, i will do that later. For now i just want my phone alive.
Anyways Thanks again everyone for the helpful information
Try getting to download mode right now. Because if you can't get to download mode you can't use the back to stock method
from my Note Thrizzle
Thanks everyone for the help and support. I have successfully reverted back to Stock LG Firmware.
I have some questions.
1. Do i have root access anymore?
2. Is my previous custom recovery still in my system?
3. If no for both then please help me with the appropriate article to root, install custom recovery and then install CM11, as my previous recovery was not able to install CM 11.
Thank You
Related
Hi i make the mistake of erasing all partitions without backup in philz touch recovery on my lg d803 and now im i can just go in recovery..i flashed twrp 2.6.3.2 and now the phone boot only in twrp..no download mode no rom i flashed a lot of roms but always boot in twrp ..help plz i have no idea what to do ..i can do adb commands...tanxs in advance.
demon66678 said:
Hi i make the mistake of erasing all partitions without backup in philz touch recovery on my lg d803 and now im i can just go in recovery..i flashed twrp 2.6.3.2 and now the phone boot only in twrp..no download mode no rom i flashed a lot of roms but always boot in twrp ..help plz i have no idea what to do ..i can do adb commands...tanxs in advance.
Click to expand...
Click to collapse
If you have ADB access, you are in a good spot.
You'll have to ADB sidelaod a ROM, and flash it. shouldn't be hard to find info on.
Good luck.
congratulations for not saying your bricked.
you probably get an error when flashing right ?!
you need a newer version of twrp... get a flashable zip and update itself in twrp. then you will be able to flash roms.
Yep. darkobas is correct.
I missed your TWRP version. find 2.6.3.3 push it (I mistakenly said sideload above) and a ROM to your 'SDcard', then flash TWRP, restart to recovery, and flash ROM (and any other required packages (Gapps, system patch, etc).
adb push path/filename /sdcard/filename
re
CxanDroid said:
Yep. darkobas is correct.
I missed your TWRP version. find 2.6.3.3 push it (I mistakenly said sideload above) and a ROM to your 'SDcard', then flash TWRP, restart to recovery, and flash ROM (and any other required packages (Gapps, system patch, etc).
adb push path/filename /sdcard/filename
Click to expand...
Click to collapse
sorry but i try it and no matter what the phone is always restarting in twrp no download mode no system no nothing everytime rebooting in recovery twrp 2.6.3.3
So.... Twrp is fine... Flash a rom now
Sent from my LG-D802 using Tapatalk
I rooted my phone installed twrp via autorec--> http://forum.xda-developers.com/showthread.php?t=2715496 . Then I backed up my phone through twrp and then I rebooted and put the newest cm11 stable build --> http://download.cyanogenmod.org/?type=snapshot&device=vs980 on my phone. (I put it in the download file of my phone if that makes any difference), then I went to twrp and wiped everything but internal storage and proceeded to flash cm11 which i found in my download file where I put it (it was a zipped file) and I flashed it, then it went into a boot loop! Currently installing the recovery in twrp that I just made. I do not know what I did wrong could someone please enlighten me? This is the first time doing this sorry if its a noob question.
Thanks.
FYI the recovery worked my phone booted up fine. Also it is a VS980. I do have the verizon variant.
UPDATE:
Tried flashing again, this time with gapps as well (forgot to the first time) same results, flashing the recovery again rn. I AM CLUELESS!!!!
bobberserker said:
FYI the recovery worked my phone booted up fine. Also it is a VS980. I do have the verizon variant.
UPDATE:
Tried flashing again, this time with gapps as well (forgot to the first time) same results, flashing the recovery again rn. I AM CLUELESS!!!!
Click to expand...
Click to collapse
Would uninstalling autorec do anything?
flash the latest recovery from here. Then afterwards check if you have the right version for your variant and check the md5
Krenol said:
flash the latest recovery from here. Then afterwards check if you have the right version for your variant and check the md5
Click to expand...
Click to collapse
Again this is my first time getting this far so here are some noob questions: Would I just flash the zipped folder in twrp? Would I need to wipe anything? Would I need to create another recovery? Would it delete my old recovery?
Thanks.
EDIT:
Also why would updating twrp make such a big difference?
Just Flash the zip File for your variant then Reboot the recovery and go to settings and hit restore default. Don't wipe anything for changing the recovery. And this will just update the rec nothing else
Hello,
I've rooted my own note 3 and flashed Temaseks unofficial cm 12 rom. Everything works perfect so I decided to do the same thing for my father. It all went well, first I rooted his phone, then I flashed CWM and flashed cm 12 by temasek. The rom works fine but I forget to install the Gapps. So I tried to install Gapps but I got an error "Failure Status 6". I googled on that error and someone told it has to do something with CWM. I tried to flash a different version of CWM but now I can't reboot into recovery mode anymore. So I can't flash anything.
I flashed another version of CWM but this one also doesn't work. Whenever I try to boot the phone into recovery mode, the blue line shows up. Rebooting into recovery mode, but after a few secs, the phone just boots the normal way. Is there anyone that can help me to get CWM back to work? In the mean time I'll try to flash TWRP by Odin.
Thanks in advance!
So I flashed latest version of CWM: Buildversion; 6.13.0, CWM Base Version V6.0.4.7. I can reboot into recovery now but still can't install Google Apps due to failure status 6. On my own Phone I run a different version of CWM, but when I try to flash it, the phone won't boot into recovery mode anymore. It only boots into recovery when I flash this V6.0.4.7 . How can I get rid of this version and flash an older version of CWM?
You'll probably have to Odin back to stock and start over...
Morningstar said:
You'll probably have to Odin back to stock and start over...
Click to expand...
Click to collapse
You mean If there is no other way to get the Google Apps on the phone, I have to go back to stock. I did make a backup with CWM on the while it was running custom firmware. Now I have 4 files on my comuter, 3.tar and 1.md5 . If I recover them, I will still have this not working CWM version on my phone right? Isn't there a easier way to delete CWM, can I flash TWRP over CWM and see if it will install these Gapps?
Yeah, you should be able to flash TWRP over it. TWRP is much better anyway, in my opinion. Once you get the recovery issue sorted, I really wouldn't't recommend trying to flash just the gapps. It would probably work, but it's also quite likely to cause some weird issues. It's always best to flash gapps immediately after flashing a ROM, without leaving recovery.
I would flash TWRP, wipe everything but your internal SD, re-flash the ROM, flash the gapps, and everything should be cherry.
Edit: here is the link to download TWRP.
Morningstar said:
Yeah, you should be able to flash TWRP over it. TWRP is much better anyway, in my opinion. Once you get the recovery issue sorted, I really wouldn't't recommend trying to flash just the gapps. It would probably work, but it's also quite likely to cause some weird issues. It's always best to flash gapps immediately after flashing a ROM, without leaving recovery.
I would flash TWRP, wipe everything but your internal SD, re-flash the ROM, flash the gapps, and everything should be cherry.
Edit: here is the link to download TWRP.
Click to expand...
Click to collapse
I appreciate your effort, thank you. The recovery issue is solved. I flashed Chainfires Root script and that installed the stock recovery. However, when I tried to install and older CWM version I got back in the recovery reboot cycle. But once I installed the latest CWM it booted in recovery. So I flashed Chainfires Root once again and had the stock recovery back. From there on I tried to install TWRP but got the recovery boot cycle again. My phone is now running android 5.0.2 and I think that's the problem.... :S I'll try again to flash Chainfires Root script to get the stock recovery back. From there on I will try to flash the link you gave to me with Odin and hope that will fix it. Do you have any ideas on what I'm doing wrong?
Your version of TWRP works so far. It reboots into RecoveryMode. Now I'll wipe and try to install Temaseks Cm 12 followed by Gapps! Thanks so far!
Okay, it's solved. Can't thank you enough for you help. Bless you!!
No problem. Glad you got it figured out!
[emoji106]
I decided today to try and root my phone and followed the steps on this tutorial: http://forum.xda-developers.com/nexus-4/general/nexus-4-guide-unlock-bootloader-root-t2266654
I had unlocked my phone and installed the latest version of TWRP. Now I can only boot into TWRP and bootloader. My phone is not being picked up by my PC. I tried a factory reset and format of data on TWRP but my phone still only boots into TWRP.
Is my phone permanently bricked?
Any help will be greatly appreciated
I actually have just made some progress now. I've managed to get the phone connected to the computer by going into ADB sideload and installing the ADB drivers again on my computer.
Typing ADB devices in CMD now shows my device as connected.
Any advice on what I should do now?
What happens when you try to boot it normally? Is it stuck at the boot animation or does it go directly to the bootloader or recovery? Since you already had to wipe everything you could try flashing a factory image via fastboot.
theminikiller said:
What happens when you try to boot it normally? Is it stuck at the boot animation or does it go directly to the bootloader or recovery? Since you already had to wipe everything you could try flashing a factory image via fastboot.
Click to expand...
Click to collapse
Booting the phone normally loads it into TWRP. Booting the phone with the volume key pressed down loads the bootloader. I think I may have just wiped the OS present on the Phone.
I want my phone to be rooted running CyanogenMOD (phone is currently unrooted). Should I first install a stock rom then root by installing SuperSU and CyanogenMOD or can I just skip installing a stock rom and install SuperSU and CyanogenMOD?
Thanks for the help
You could try flashing a cyanogenmod zip from TWRP, and if that doesn't work I would suggest flashing I factory image.
theminikiller said:
You could try flashing a cyanogenmod zip from TWRP, and if that doesn't work I would suggest flashing I factory image.
Click to expand...
Click to collapse
But my phone is not rooted yet. Can I install SuperSU by copying onto my phone and installing it through TWRP?
umair_ said:
But my phone is not rooted yet. Can I install SuperSU by copying onto my phone and installing it through TWRP?
Click to expand...
Click to collapse
Yes, if it is a zip file. But I'm pretty sure installing cyanogenmod will automatically root it for you.
theminikiller said:
Yes, if it is a zip file. But I'm pretty sure installing cyanogenmod will automatically root it for you.
Click to expand...
Click to collapse
I installed SuperSU then CyanogenMOD and lastly GApps. It still only boots into TWRP and it doesn't look like there has been any files added to the phone's storage. Should I first flash a stock rom and then try to install CyanogenMOD?
umair_ said:
I installed SuperSU then CyanogenMOD and lastly GApps. It still only boots into TWRP and it doesn't look like there has been any files added to the phone's storage. Should I first flash a stock rom and then try to install CyanogenMOD?
Click to expand...
Click to collapse
Yes, try flashing a factory image. If it boots then you could try flashing cyanogenmod.
EDIT: here is a guide on how to flash a factory image: http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
theminikiller said:
Yes, try flashing a factory image. If it boots then you could try flashing cyanogenmod.
EDIT: here is a guide on how to flash a factory image: http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Click to expand...
Click to collapse
I've managed to get it all working by first flashing the stock ROM and starting all over again.
Thanks for your help.
Is there a workaround to this other than flashing factory images...?
hwweiler said:
Is there a workaround to this other than flashing factory images...?
Click to expand...
Click to collapse
@hwweiler, No friend there is no other way.Please before do this as is one direction way take the pain to look on my post #180 on zaclmon's thread http://forum.xda-developers.com/nexus-4/orig-development/wip-aosp-7-0-nougat-t3448444/page18 and keep in mind that is impossible to return back on any nandroid backup u kept e.g to 5.1.1 or M furthermore its also impossible to flash any rom zip if u use this N (WIP) rom,the only way to have a workable phone again is to flash the stock rom from scratch.Exceperienced with and never again untill we have the appropriate solution..The twrp used and i still use on M is TWRP 3.0.2.0.The possibility to return on LP ffrom M and reverse still exists but not when u flash this rom.
Regards,Christos
Hey guys,
so I tried flashing Omni 8.0 rom and I was stuck at the boot screen. so I went back into twrp tried to reflash still nothing. I flashed a new version of twrp the one that can use multirom and it erased all my data. I flashed back the twrp I started with and now I can not sideload the full OTA zip to get back to stock. It says "cannot load one.zip" which is what I have it labeled as. I tried to download the recovery tool and I can't seem to figure out how to get the driver to work so it will see me on my comm port. Does anyone have any ideas on what to do or what happened? I'm stuck in twrp.
almost looks like it can't mount the system
IDK, maybe a broken download. I'd try to restore a backup if you have one, if not Wipe > Factory Reset. If it still doesn't boot after 20 minutes, refer to this thread: https://forums.oneplus.net/threads/i-have-to-go-back-to-oxygen-os.649947/#post-16907420. Basically, download the OOS ROM onto your computer and use an ADB/USB Sideload in TWRP recovery (you can flash Oxygen Recovery from TWRP if TWRP doesn't work) to install it. May take a while to boot.
I have no idea how it happened but I got my system mounted again that was my problem. I'm back.
thread can be closed
keeganjk said:
IDK, maybe a broken download. I'd try to restore a backup if you have one, if not Wipe > Factory Reset. If it still doesn't boot after 20 minutes, refer to this thread: https://forums.oneplus.net/threads/i-have-to-go-back-to-oxygen-os.649947/#post-16907420. Basically, download the OOS ROM onto your computer and use an ADB/USB Sideload in TWRP recovery (you can flash Oxygen Recovery from TWRP if TWRP doesn't work) to install it. May take a while to boot.
Click to expand...
Click to collapse
thanks for the reply mate
snipeez1987 said:
thanks for the reply mate
Click to expand...
Click to collapse
yw
snipeez1987 said:
Hey guys,
so I tried flashing Omni 8.0 rom and I was stuck at the boot screen. so I went back into twrp tried to reflash still nothing. I flashed a new version of twrp the one that can use multirom and it erased all my data. I flashed back the twrp I started with and now I can not sideload the full OTA zip to get back to stock. It says "cannot load one.zip" which is what I have it labeled as. I tried to download the recovery tool and I can't seem to figure out how to get the driver to work so it will see me on my comm port. Does anyone have any ideas on what to do or what happened? I'm stuck in twrp.
Click to expand...
Click to collapse
Easy fix for "Cannot load xxx.rom": you have to patch the adb.exe with a large address awareness program. Google it, I found one in another XDA thread.
Reason: the ROM filesize is too large. For small ROMs (like custom ROMs) adb would recognise it without any problems.
ipredatorv said:
Easy fix for "Cannot load xxx.rom": you have to patch the adb.exe with a large address awareness program. Google it, I found one in another XDA thread.
Reason: the ROM filesize is too large. For small ROMs (like custom ROMs) adb would recognise it without any problems.
Click to expand...
Click to collapse
Awesome. I'll keep that in mind. I'm sure I'll mess it up again lol. Hopefully not though.