Hello everyone and thanks for taking the time to read this and help me out.
I had rooted my LG G2 D801 using a method which I can no longer seem to find. Let alone remember what it even was.
After attempting to revert from Lollipop to Kit Kat in order to flash a custom ROM(after countless hours of trying to figure out a way) , I hard Bricked my phone.
Then(after countless more hours of trying to figure out how to fix), I somehow managed to bring my G2 back to life.
Now, I'm unable to boot into any recovery whatsoever. Download mode works, however my computer states that no Serial Port Service is running on the phone. I happened to stumble across Auto-Rec Lollipop which states that it is currently installed. Although I can't seem to find it. Not sure if that's relevant or not but there you have it.
I'm not sure what's wrong, just looking for some guidance so I can maybe attempt rooting and /or flashing a custom ROM again.
Any help would be appreciated.
Related
I own a HTC Explorer. I rooted it a few months back. This is the tutorial I used (just for your reference) : http://forum.xda-developers.com/showthread.php?t=1415223
I have not used the factory reset option yet but somehow, when I restarted my phone today it got stuck in boot loop. Can anyone suggest a good ROM which is the closest to the stock ROM? It should just be closest to the stock ROM as I don't care for any extra feature, just the basic functionality of the phone. Also link me the tutorial that I should refer to when doing this. If it is the same one that I used for rooting, let me know what's different that I must do since I know that some steps will be different cause I'm installing a new ROM and previous tutorial I used was only to root the phone.
Thank you. Ill be getting online back in 8-9 hours so if you need any details regarding the phone I shall be able to do it then.
ThePsych0naut said:
I own a HTC Explorer. I rooted it a few months back. This is the tutorial I used (just for your reference) : http://forum.xda-developers.com/showthread.php?t=1415223
I have not used the factory reset option yet but somehow, when I restarted my phone today it got stuck in boot loop. Can anyone suggest a good ROM which is the closest to the stock ROM? It should just be closest to the stock ROM as I don't care for any extra feature, just the basic functionality of the phone. Also link me the tutorial that I should refer to when doing this. If it is the same one that I used for rooting, let me know what's different that I must do since I know that some steps will be different cause I'm installing a new ROM and previous tutorial I used was only to root the phone.
Thank you. Ill be getting online back in 8-9 hours so if you need any details regarding the phone I shall be able to do it then.
Click to expand...
Click to collapse
Bump, please help. Ill also search for threads that might have the needed answer.
Someone please please help me. I am in desperate need of a solution. And before I lay out the issue I am having, I would like to thank everyone for taking their time to read through my post and give their input. I truly appreciate it everybody. Much much thanks.
Just as a disclaimer, I've looked all over the internet, everywhere I can possibly find for days on end, and none of what I found worked for me. It feels like I tried everything there could be, and that is why I am coming here. Again, thank you.
So here's a little background information: I have a Verizon Samsung Galaxy S4 (SCH-I545). I got the phone over the summer, and as soon as I received the phone I was updated to the apparently dreadful VRUMAE7 update. There afterwards, I tried rooting the phone. I've had rooting experience before with decent success, and never ran into problems like I did. It took awhile for me root my S4, but after awhile I was able to successfully root it. Although, I'm pretty sure I may have done something wrong. You will see why shortly.
So a week or two back, my S4 prompted me to update to the next update. I believe it was Android 4.3 (VRUEMJ7). I was very excited for the update and tried running it. But every time I accepted the update and tried updating, my phone went into Recovery to download the new update and stalled out with an error. Thereafter I would have to reboot the phone to get it working again. After failing to update multiple times, I realized that it is probably because I messed up my root. So without doing much research, I simply tried flashing the stock firmware that came with my phone thinking it should work pretty flawlessly.
I have a Mac OS, so using VmWare Fusion with Windows 7, I downloaded Odin and booted up my phone on Recovery mode, downloaded the stock VRUMAE7 firmware I found online, and began flashing. But Odin threw me a error, so I tried rebooting my phone thinking it would go back to normal. BUT this time, it kept going into recovery mode with a yellow Triangle saying firmware was installed incorrectly, etc. I was so frustrated at this point, thinking that I truly may have bricked my phone.
I began on this long journey of going through all the sources I could find online possible, downloading every type of Verizon S4 firmware I can find, trying every Odin method possible, and spending long long hours of the night biting my fingers at my dreadful fate. I even tried flashing the stock PIT File along with my stock firmware, to see if that would fix it. But no luck. I also tried using a standard windows machine rather than VMware, still with no luck.
I ask you all to please suggest any ideas, thoughts, or inputs you possibly can. I am willing to try anything and everything at this point. Please do help. I appreciate you guys reading through my lengthy question, sorry for that. Just wanted to lay everything out.
Thank you very very much.
muazra said:
Someone please please help me. I am in desperate need of a solution. And before I lay out the issue I am having, I would like to thank everyone for taking their time to read through my post and give their input. I truly appreciate it everybody. Much much thanks.
Just as a disclaimer, I've looked all over the internet, everywhere I can possibly find for days on end, and none of what I found worked for me. It feels like I tried everything there could be, and that is why I am coming here. Again, thank you.
So here's a little background information: I have a Verizon Samsung Galaxy S4 (SCH-I545). I got the phone over the summer, and as soon as I received the phone I was updated to the apparently dreadful VRUMAE7 update. There afterwards, I tried rooting the phone. I've had rooting experience before with decent success, and never ran into problems like I did. It took awhile for me root my S4, but after awhile I was able to successfully root it. Although, I'm pretty sure I may have done something wrong. You will see why shortly.
So a week or two back, my S4 prompted me to update to the next update. I believe it was Android 4.3 (VRUEMJ7). I was very excited for the update and tried running it. But every time I accepted the update and tried updating, my phone went into Recovery to download the new update and stalled out with an error. Thereafter I would have to reboot the phone to get it working again. After failing to update multiple times, I realized that it is probably because I messed up my root. So without doing much research, I simply tried flashing the stock firmware that came with my phone thinking it should work pretty flawlessly.
I have a Mac OS, so using VmWare Fusion with Windows 7, I downloaded Odin and booted up my phone on Recovery mode, downloaded the stock VRUMAE7 firmware I found online, and began flashing. But Odin threw me a error, so I tried rebooting my phone thinking it would go back to normal. BUT this time, it kept going into recovery mode with a yellow Triangle saying firmware was installed incorrectly, etc. I was so frustrated at this point, thinking that I truly may have bricked my phone.
I began on this long journey of going through all the sources I could find online possible, downloading every type of Verizon S4 firmware I can find, trying every Odin method possible, and spending long long hours of the night biting my fingers at my dreadful fate. I even tried flashing the stock PIT File along with my stock firmware, to see if that would fix it. But no luck. I also tried using a standard windows machine rather than VMware, still with no luck.
I ask you all to please suggest any ideas, thoughts, or inputs you possibly can. I am willing to try anything and everything at this point. Please do help. I appreciate you guys reading through my lengthy question, sorry for that. Just wanted to lay everything out.
Thank you very very much.
Click to expand...
Click to collapse
Hi there,
it seems an easy problem but do it at your own risk I don't take responsibility of bricked device,etc
so lets go with what you need:
A- Odin [I believe you already have it]
B- stock rom go to this site:
androidayos.com/samsung-galaxy-s4-odin-stock-firmware/
and choose the suitable stock rom based on your Baseband version
C- Drivers installed for your device [if your mac/laptop recognizes your device then skip this step if not google it,download the drivers and install them]
IMPORTANT:Make sure you have 80% or more on battery
after you get these stuff install the device drivers as mentions in C then turn your device off and power it while holding volume up it should take you to download.now open odin and navigate it to the rom which you downloaded from B and flash it .wait for green color to appear and your back to your stock now it should open normally hope that I helped
Hello All,
Well Ive had my head buried in the xda forums for about a week and a half, two weeks now so I decided to post my issue hoping someone could advise me, I rooted my phone LG G2 D80220c-HKG-XXX, kitkat 4.4.2, Ive tried flashing a couple different roms but it would not take, ( I am sure its rooted ) and the last one cm12 I had to abort and at that point I decided I would just go back to stock and unroot, well to my great pleasure (lol) the ota for lollipops push came to my phone and guess what!!! I left it with my dad, and not knowing what it was excepted it thinking it was a app update of some kind, no problem, it was stuck in cwm recovery loop, after researching the forum I used Minimal ADB and Fastboot from 'shimp208' and ADB shell code to boot from 'thecubed'' post [fix] Installed TWRP and now you're stuck OTA, To shorten this long story, Im operating on basic os 4.4.2 now and discovered that my imei # is that of a D800 but my build number is KOT49I.D80220c, baseband version is M8974A-AAAANAZM-1.0.190084 and of course the software is in the above text, so now I have no clue what firmware to use to go back to stock, I'm thinking D800 but I dont no where or even if what I need exists, Ive searched where, does anyone have any ideas, thanks for reading and for any help.
Hi, Nice phone - should be able to find help here lg-g2/help
Hope this helps !!
I am stuck in a bootloop "mismatch_sig_len" and I have tried putting it into download mode, factory reset and a couple of recovery tools that can't find my device. I have read something about having to "short" two pins with tweezers or copper, to get out of this. Are there any successful methods anyone knows of? Thanks in advance.
Hey,
Haven't seen this issue before so I did a bit of searching around (my v10 is my first lg phone since nexus4) and it appears these phones may be (close to) unbrickable - similar to Samsung's of the past (I did this to an old sidekick)
At least phones like the g2 and g3 (maybe g4?) Have a way to force it into the Qualcomm download mode and use lg tools to flash back to stock
http://forum.xda-developers.com/showpost.php?p=65002893&postcount=17
This may be a start for you, and hopefully with your tests we can find out if these phones truly are unbrickable
Keep us posted if you find your way!
Sent from my LG-H901 using XDA-Developers mobile app
Same issue here. I spent 4 hours looking at every post there is on this matter and can not fix it. With the exception I CAN boot into the bootloader and issue commands, however I get "unknown command" all the time. I think this is a result from bad directions on the mm update recently posted. I tried everything I can think of and even tried the batter trick. I figure if I can get into TWRP or load it back I might have some success and moving forward.
I also had this problem after LG UP to 6.0 w/ twrp(tot file) flashed.
unlock bootloader will solve this issue.
This happened because new 6.0 FW modify check. I believe any mod on BL locked status will have this softbrick.
So following the instructions here I rooted my LG Tribute 5 when I got it with Kingroot. And everything was fine for months. Until System Updates started to pop up regularly but I could never get them to install(they would error out). After a quick search I learned the updates won't install cuz the device was rooted. And a quick unroot would get the install to work.
I just unrooted through the kingroot app and started the updated. Before, when I tried the update it would error out about a quarter of the way through. This time the bar made it all the way to the end and then error'd out. I didn't think much of it. So since the device was stuck I took my battery out and back in. The device went through the boot process, then a No Command error popped up. Never saw that before.
So I tinkered with it a bit and kept getting the error. So I got into the Recovery Menu to do a full wipe and factory reset. I did that, but the No Command still popped up.
I know I can put a custom rom file on my external sd card and install that through recovery, right? The thing is I would like to install Slimrom, but there are a ton of downloads on the sites download page. So I'm asking for a little help on directions on a slimrom that will work on the LG Tribute 5.
And if there isn't a custom rom that works with a tribute 5,can I get a recommendation of one a custom rom that does? I'm into lightweight and minimalistic. By the way, I didn't have a custom rom on my phone, just had it rooted.
Thank you so much in advance for any and all help
No-one has any advice for me?
A little more info, the phone was on Android 5.1.1 before it started erroring out.
No-one has any advice for me?
A little more info, the phone was on Android 5.1.1 before it started erroring out.
Do you have a custom recovery as well? If it is only the stock recovery, which blocks most zips, your very option may be to use LG UP and the stock dz file and return the device to stock. The process to update can be done from that point.
I'm pretty sure I only have the stock recovery. I knew i should have installed TWRP...
So just search for LG UP and the stock firmware and they should be easily accessible?
Thanks for the reply xanscorp.
https://drive.google.com/folderview?id=0B0KV4b0_G1PQZW95ZmloejU5dFk
The LG UP program and .dz file are in there.
That's awesome! Thank you very much for linking the files for me.
I'm gonna do this in a couple hours when I get home and I'll let you know how it went.
Much appreciated xanscorp
One last stupid question... Just the LG Up and.dz files are the only two I need right?
I'm guessing so, but just wanna be sure.
Yes. It'll put you back to stock.
Unfortunately I haven't yet found how to get the ZV5 firmware fully rooted (i.e. a custom recovery) but it can be partially rooted with KingRoot. (http://www.kingroot.net/wap)
I just finally got around to giving this a shot. Sheesh....
Anyways I downloaded the files, put them on my external SD card, popped my SD card into my phone, then booted my phone to recovery. I went to install update from SD, and the phone didn't find any files. Hmmm....
I'm definitely doing something wrong. The .msi file looks like an executable. So I hopped onto Windows to install it. It installed, but when I run the program it can't find my phone when I plug it in.
I'm about to just give up, trash this thing, switch to a different provider and get another new phone. This time I won't mess with Kingroot. I'm pretty positive that's the app that screwed things up. I've had three different phones, rooted all three through different methods, and never had a problem.
Things files are to restore from a pc using LG Up for Windows... that's why it's a Microsoft Installer (.msi) file.
Yeah I figured that. But when I plug my phone into the computer my phone isn't recognized. I'm assuming because it boots straight to a No Command screen.
So since the computer doesn't recognize it neither does LG Up. Any trick to get around this?
Still haven't gotten this phone back to working. This is the first time I've really been stumped after a brick.
Please...anymore help?
Sent from my KFFOWI using Tapatalk
You find annything cause my same phone did the same thing
Sure haven't bud.
I've tried the help in the thread with no success