Folks, I have seen some threads on here so I will understand that you will probably hate me but seriously none of those did well for me. So that's why I am creating mine. As an owner of LG G2 mini I had been closely focusing on CM12 progress re lollipop that InvaderJohn was working on. There was a camera overexposure issue so I tried to use some working lib files and vendor/lib files and created a flashable file for TWRP recovery. I screwed it up as upong the flash my phone with CM12 didn't boot up. I wasn't able to get into recover thru adb so I pressed volume down and middle button and got myself into factory mode. I did factory reset and was in TWRP recovery again. Good. Then I reflashed the phone and there was an error saying that secure booting unsuccessful. I have LG Flashtools and tot file with dll for my LG D620fr on my laptop. This method I used once when getting the phone bricked and it worked and I was able to install stock 4.4.2 ROM. But this time... not sure why but the tot flash got stuck with 94% and while the phone was supposed to get restarted it didn't and the message above of the secure etc. popped up. I am able to get into my TWRP recovery (weird) but nothing else. I suspect I got my bootloader locked. Is there any way how to figure this out, please? I was trying the fastboot method but my phone is unrecognizeable. Any help is much appreciated.
enzo_cz said:
Folks, I have seen some threads on here so I will understand that you will probably hate me but seriously none of those did well for me. So that's why I am creating mine. As an owner of LG G2 mini I had been closely focusing on CM12 progress re lollipop that InvaderJohn was working on. There was a camera overexposure issue so I tried to use some working lib files and vendor/lib files and created a flashable file for TWRP recovery. I screwed it up as upong the flash my phone with CM12 didn't boot up. I wasn't able to get into recover thru adb so I pressed volume down and middle button and got myself into factory mode. I did factory reset and was in TWRP recovery again. Good. Then I reflashed the phone and there was an error saying that secure booting unsuccessful. I have LG Flashtools and tot file with dll for my LG D620fr on my laptop. This method I used once when getting the phone bricked and it worked and I was able to install stock 4.4.2 ROM. But this time... not sure why but the tot flash got stuck with 94% and while the phone was supposed to get restarted it didn't and the message above of the secure etc. popped up. I am able to get into my TWRP recovery (weird) but nothing else. I suspect I got my bootloader locked. Is there any way how to figure this out, please? I was trying the fastboot method but my phone is unrecognizeable. Any help is much appreciated.
Click to expand...
Click to collapse
Sounds like the bootloader is locked.
Check this thread: How to check for locked bootloader? ... but it's for the LG G3.
Best place to ask is the G2 Mini Q&A, Help & Troubleshooting.
Thread closed and thank you.
Related
Hi everyone, I need a help on my LG G PRO 2. Basically what I did is being one of the biggest dickhead on the earth. I was so excited about gettin lollipop on this phone that I didn't noticed it was NOT for my phone.
So, before it happened i had d838v10f on it, rooted and recovery installed (it was an apk with a pharaoh...)
Then I get into recovery and flash this zip:
http://forum.xda-developers.com/lg-g-pro-2/development/b-futurev3-0-lolipop-walkman-f350l-s-k-t3001632
While flashing in recovery it says something went wrong, I reboot and it keeps staying in the boot screen. I noticed that the "powered by android" text in the bottom has changed, android L style, but it does not go forward.
So, I tried to go in download mode: Before it was in english, now it's in KOREAN. I tried to flash d838v10f kdz, and it goes on until 49%. It just stops and won't go on. So I also tried to push some .tot files, but this thime it doesn't even start. Part of the log says:
IMEI:NULL
Error: CrossDL [F350L] to [D838].
So, it's actually a F350L now, a NOT WORKING F350L.
If you have any question, or suggestion about it, don't hesistate!
THANKS!!!
Hi, eagle93. The same happened to me yesterday. Go here:
http://forum.xda-developers.com/showthread.php?t=3004653
And read from post #5 on... Good luck!
Hello guys.
I apologize for making yet another "my phone is soft-bricked" thread, but I have been through at least 20-25 of the other threads, seemingly tried everything, and I can't get past my problem. Also, most of the other threads I saw are pretty old and not really active anymore. A few of the tools there can't even be downloaded anymore because the links are dead.
Anyway, here's my story.
I have a 16 GB US retail XT1032 that I bought mostly to give tech support to my parents, whom I also bought a 8GB each. Theirs, I left untouched. Mine, I unlocked bootloader and rooted right away. All went well for a long time.
My parents kept receiving OTA's and it took them all the way to Lollipop. Me being rooted, I got stuck in KitKat somewhere (I'm not 100% sure whether that was in 4.4.2 or 4.4.4), but since it wasn't my daily driver, I let it lie as stock rooted KitKat. Recently I wanted to go to Lollipop in order to keep seeing "the same things" as my parents, and I installed TWRP in preparation to flash a "stock enhanced" version of Lollipop. TWRP flashed fine but there was something funny all along: I could use ADB or a root app to boot into recovery from the ROM, but I could never manage to get the phone to go into recovery by booting into fastboot (vol down+power) and then choosing recovery. Screen would go black and recovery would never load.
So I copied a "stock" Lollipop image and booted into TWRP from the ROM and wiped everything and tried flashing the Lollipop ROM. It got stuck somewhere part way, and a few hours later there was no more progress.
Ever since then, I am stuck in fastboot. Fastboot seemingly works correctly, recently I was able to flash an OG animation to get rid of the nasty "your bootloader is unlocked" warning. I can flash recoveries (TWRP and/or CWM) without error on the phone or the computer, but when I try to then boot into recovery using the bootloader, I get stuck on the black screen and go nowhere.
As others in the various threads have commented, when I try to boot "normally", I get the boot animation and a vibration and then it gets stuck.
I have tried so many things by reading different threads I couldn't tell you anymore what all of them were. I've gotten errors about downgrading, I've gotten stuck in fastboot reason: "failed flash", I've gotten flashing errors about the size of recovery or boot or gpt. What I've never managed to do again is to boot into anything other than bootloader. No recovery and no ROM.
Could someone with a bit of experience please point me to some working links and/or when you have the time, help me look at a couple of logs or something that can help me figure out where my problem lies and how to get out of it? my daily driver phablet died a gruesome death and I wanted to go back to my trusty moto g, to no avail.
Thank you very much to whomever can help.
Ruben.
Try to reflash full stock firmware for your device according to your bootloader version. Hope it helps....
Try typing in fastboot devices
I successfully rooted my LG G Stylo (MetroPCS) using this guide: http://forum.xda-developers.com/lg-g-stylo/how-to/guide-lg-g-stylo-how-to-root-t-mobile-6-t3333916
but I did something I shouldn't have.
I changed the permissions for my system folder using a file explorer and as soon as I confirmed the changes my screen went black but my phone was still on because when I pressed the sleep button it would vibrate. I couldnt get it to turn off or start working again so I took out the battery and put it back in. Then when I booted it up it would take me to TWRP and I started messing around in there. I accidently wiped everything, including my OS so now my phone wont even boot to TWRP it just stays at the LG Logo. I read you can flash OS to phones but I don't know how to do that now that I can't boot to recovery! Any help please?
XDA Visitor said:
I successfully rooted my LG G Stylo (MetroPCS) using this guide: http://forum.xda-developers.com/lg-g-stylo/how-to/guide-lg-g-stylo-how-to-root-t-mobile-6-t3333916
but I did something I shouldn't have.
I changed the permissions for my system folder using a file explorer and as soon as I confirmed the changes my screen went black but my phone was still on because when I pressed the sleep button it would vibrate. I couldnt get it to turn off or start working again so I took out the battery and put it back in. Then when I booted it up it would take me to TWRP and I started messing around in there. I accidently wiped everything, including my OS so now my phone wont even boot to TWRP it just stays at the LG Logo. I read you can flash OS to phones but I don't know how to do that now that I can't boot to recovery! Any help please?
Click to expand...
Click to collapse
You have already received a response here:
http://forum.xda-developers.com/general/xda-assist/help-asap-phone-booting-to-twrp-t3425480
Do not create duplicate posts.
Thread closed.
It's stuck at the ASUS logo. A friend gave it to me to fix since it wouldn't download apps from google play which led me to believe that it had software problems so I decided to update it. It's worth noting that it kinda bricked itself after factory resetting before the current brick. It wouldn't boot and it was stuck at the ASUS logo, but somehow it fixed itself after several reboots. After it fixed had itself, the problem with not being able to download apps was still present. One time I turned it off and it wouldn't turn back on. I tried to go into recovery, but then I realized that the recovery was gone too. It was stuck at "no command" screen, so the only way to modify the files was through the bootloader. I found a firmware zip with the .bin files in it, so I flashed them one by one and I got the recovery back. Installed the update via a good sd card and it was stuck at the ASUS logo. I sideloaded it through recovery and got the same result. I also tried sideloading it through the bootloader which also gave me the same result. I'm all out of options I can think of. If anyone has any idea, please share it.
Thanks in advance!
Hi !
I see that you have posted here as well https://forum.xda-developers.com/an...oot-method-t3311752/post71149052#post71149052 and that`s the best section from where you can receive more help , keep an eye on it
Good luck !
Hello.
First of all, i'm sorry if this question have been asked before. Believe me, i've tried searching even through Google's 2nd page but still no luck in finding answer.
I had a OPO 64GB version. It was working fine until i decided to do ROM update. My previous working ROM is "CM13-20160812-somethingsomething-SNAPSHOT.zip". It is rooted with Xposed installed
I tried to update it using TWRP. the update is "CM13-20161216-somethingsomething-SNAPSHOT.zip". It got stuck at "Patching system image unconditianally"(probably wrong spelling there) for more than one hour. So, i decided to force reboot it and it is now stuck at boot logo(not bootanimation)
Thing is, i cant get it into fastboot, nor recovery. it just stuck there and i've tried to Power Cycle but still no result. I tried to plug it into my computer and it does detect it in "Device Manager" under "Portable Devices" with name "A0001".
I wonder if it soft brick or hard brick. I'm asking brilliant mind in here, if there's a way to restore it. I just revived it from broken screen since 2016(talk about bad luck) and i don't want to completely replace as the device is still in good condition.
Also, if there's no other choice then i had no other way than to follow this guide here, which completely unbrick my phone(also losing me 30+ apps)
http://www.androidbrick.com/unbrick-oneplus-one-two-3-3t-qualcomm-hs-usb-qdloader-9008/
or
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Nevermind. i got it to work by installing QPST driver. for some reason it enable adb at boot logo(yes at boot logo). got into recovery and recover my system partition(which is broken).
I ask the mod to delete this thread. Thank you