Related
a few weeks back i got an update from t-mobile i think it was 2.2.1. i was running a custom rom by evil, I think it was sense. it never fully installed as it came up with a black scrren with a exclamation mark and a little android guy. every time i go into recovery now, i get the same thing. this also converted the phone back to stock rom.
im sorry, but i am a newbie when it comes to flashing new recovery images. do you think this is what needs to be done? i had clockworkmod's on there before, had a buddy do it for me.. and he didnt explain to me how to fix install it lol. i do install roms etc.
any way i should go with this?
You guessed right, you need to reflash the recovery, and possibly re-root before that.
You can follow the guides in Wiki, found in my signature.
did it, having a problem installing roms now :| gonna post in that roms thread.
I'm pretty new to this, and I didn't fully understand the whole rom, flash, kernel stuff but I did it anyway, seeing as I jailbroke my ipod when I knew next to nothing about that kinda stuff...
Well, I rebooted into recovery using rom manager, and it didn't reboot. It shut off, but didn't turn back on.. I tried to turn it back on myself and only the lg logo would appear..
So I googled what was happening to my phone. It's either in the 'boot loop' or bricked... i don't know the difference, or if there's even one but what the hell do I do to fix it? ..
I tried holding down the power, 3D and volume down button but the recovery menu doesn't come up... and I really don't wanna download any more programs to fix it :/
Im sorry but you must now have to download some programs to fix. You follow this guide http://forum.xda-developers.com/showthread.php?t=1491870
And Flash your firmware using the kdz files. If you have anymore problems feel free to ask.
Sent from my LG-P925 using xda app-developers app
This worked for me
Sorry about the phone. This worked easier for me:
http://forum.xda-developers.com/show....php?t=1448803
BUT I already had .bin and .fls files on my computer, not .kdz. I suppose either way is about the same. It does feel like you are groping in the dark for a while, then it all comes together. And when you are done learning all about it you can fix all your friends' Androids for a bunch of Starbucks coffee or whatever.
:cyclops:
Also, be careful with custom recovery (CWM/TWRP); just be sure it works with your particular phone first. That's what 'bricked' mine; I had custom recovery not really compatible with the setup I have going on my Thrill and got bootloop. I had to reflash the ROM image as in above link or the one in the other poster to get out of it.
whoops
sorry guys ive been busy with work lately ill have to give that first option a go seeing as i basically have nothing left of the old system
ill update after i try it.
That last post of mine is old. This is my LG Flash Tool guide:
http://forum.xda-developers.com/showthread.php?p=39269819
Drivers are tricky to set up the first time you try it, but Flash Tool is more reliable in my opinion.
BTW P920 and P925 are the same device. Thrill is just the US AT&T branded version (who I have never used; I unlocked mine with a Straight Talk SIM). I have a Thrill and some small numbering inside the battery cover says "P920."
update
ok i just now have the time to try to restore my phone.
id like to get it back to rooted stock ics as its sole purpose will be games/other non important junk and id like to still have the 3d.
the phone currently has no os and boot to twrp i also dont have any of my old recovery files so im essentially starting from scratch on my new laptop.
where do i go from here?
can i just download a zip or recovery and and use the restore/install feature on twrp?
Follow the guide to install rooted stock ICS by way of LG Flash Tool.
bricked lg thrill 4g
my phone is bricked the only thing it has is cwm recovery
i need to be able to get an os on it ..i dont can if it stock or rooted gb or ics i just need it done.and the above link's files no longer work... i need a no bs way to get this fixed ..any takers?
Hi all,
I have been using CM11 (http://forum.xda-developers.com/showthread.php?t=2494684) for awhile and hoping that they'd fix it so I wouldn't have to go back to stock or install a new ROM, but it seems that isn't going to happen. I guess I'm a beginner with this stuff, only because I only really dig in about twice a year and so I forget everything I learned the last time I had dealt with it.
I'm currently using a nightly from a few weeks ago (haven't bothered updating since... I don't think they're updating them) and I would like to either go back to completely stock and get OTA updates again, or move to another stable ROM. I had a backup from when I first rooted, but have since lost it. I have tried to find out what steps I need to take, but everything in these forums is all over the place and IF this THEN this, and Verizon specifically has to follow these steps, blah blah blah. Long story long, it's very confusing to me and at this point I think I have to follow 4 different guides entirely to get back to something that works (Which makes me think I'm missing something very simple). I figured I'd post and get a direct response to my specific situation.
Android version 4.4.4
Baseband version 11A
Recovery ClockworkMod 6.0.4.4
(Not sure this will help or not, but figured it's worth adding)
I did at one point have TWRP installed, but I had changed it at some point for... Some reason, no idea at this point. I think part of my frustration with trying to fix this is that some instructions tell me to have at least some specific version of TWRP (2.7?) installed, but I could never get it to work. The files for earlier versions were .img and the newer versions were .zips I think, and the process would always error out, no matter what I tried. (extracting contents, using the .img within, changing .zip to .img, maybe others, this was months ago)
Ultimately, I'd like to go to a stable ROM rather than stock, but I really don't want to have to spend hours working on this. I have already spent time looking at different threads piecing together what I need to do and I'm not at all confident that what I've come up with is the easiest or correct way for me to do this. Some people may say "the instructions are on the first post of whatever ROM you want". While that is true, when I have to be on a specific baseband or some such and directions are referenced but aren't linked, and I have to start digging, I lose confidence.
Aaaannyway, if anyone could help I would VERY MUCH APPRECIATE IT. I have been dealing with daily crashes for way too long.
Nicholo said:
Hi all,
I have been using CM11 (http://forum.xda-developers.com/showthread.php?t=2494684) for awhile and hoping that they'd fix it so I wouldn't have to go back to stock or install a new ROM, but it seems that isn't going to happen. I guess I'm a beginner with this stuff, only because I only really dig in about twice a year and so I forget everything I learned the last time I had dealt with it.
I'm currently using a nightly from a few weeks ago (haven't bothered updating since... I don't think they're updating them) and I would like to either go back to completely stock and get OTA updates again, or move to another stable ROM. I had a backup from when I first rooted, but have since lost it. I have tried to find out what steps I need to take, but everything in these forums is all over the place and IF this THEN this, and Verizon specifically has to follow these steps, blah blah blah. Long story long, it's very confusing to me and at this point I think I have to follow 4 different guides entirely to get back to something that works (Which makes me think I'm missing something very simple). I figured I'd post and get a direct response to my specific situation.
Android version 4.4.4
Baseband version 11A
Recovery ClockworkMod 6.0.4.4
(Not sure this will help or not, but figured it's worth adding)
I did at one point have TWRP installed, but I had changed it at some point for... Some reason, no idea at this point. I think part of my frustration with trying to fix this is that some instructions tell me to have at least some specific version of TWRP (2.7?) installed, but I could never get it to work. The files for earlier versions were .img and the newer versions were .zips I think, and the process would always error out, no matter what I tried. (extracting contents, using the .img within, changing .zip to .img, maybe others, this was months ago)
Ultimately, I'd like to go to a stable ROM rather than stock, but I really don't want to have to spend hours working on this. I have already spent time looking at different threads piecing together what I need to do and I'm not at all confident that what I've come up with is the easiest or correct way for me to do this. Some people may say "the instructions are on the first post of whatever ROM you want". While that is true, when I have to be on a specific baseband or some such and directions are referenced but aren't linked, and I have to start digging, I lose confidence.
Aaaannyway, if anyone could help I would VERY MUCH APPRECIATE IT. I have been dealing with daily crashes for way too long.
Click to expand...
Click to collapse
There isn't any developers for cm11 unless you go to some of the unofficials. There is no one to do the work. If your wanting a stable rom check out mahdi works great.
simple_fear85 said:
There isn't any developers for cm11 unless you go to some of the unofficials. There is no one to do the work. If your wanting a stable rom check out mahdi works great.
Click to expand...
Click to collapse
If I'm reading things correctly, in order to use Mahdi I need to...
1) Wipe everything but internal storage.
2) Flash the 11A Kitkat modem for the JB baseband. (I think that makes sense?) (Based on this post) Or maybe I'm supposed to use Cloudyfa's KK modem?
3) Flash Mahdi.
4) Flash patch.
5) Flash Gapps.
Am I close or way off? I guess the modem and baseband stuff is confusing me the most.
If you want to stick to CM11, you can upgrade your baseband to 24A and use jackpotclavin's build, it works well but it hasn't been updated past 4.4.2 I believe.
Nicholo said:
If I'm reading things correctly, in order to use Mahdi I need to...
1) Wipe everything but internal storage.
2) Flash the 11A Kitkat modem for the JB baseband. (I think that makes sense?) (Based on this post) Or maybe I'm supposed to use Cloudyfa's KK modem?
3) Flash Mahdi.
4) Flash patch.
5) Flash Gapps.
Am I close or way off? I guess the modem and baseband stuff is confusing me the most.[/QUOTE
no go to xdabbes follow his stock method then go back to twrp flash mahdi, the patch, and then gapps
All aosp roms now that are 4.4.4 are running the 24a bootstack or kitkat.
Click to expand...
Click to collapse
no go to xdabbes follow his stock method then go back to twrp flash mahdi, the patch, and then gapps
Click to expand...
Click to collapse
Okay, now this is where I run into the TWRP problem I mentioned. I can't get TWRP 6.3.3+ installed because the file is a zip, and no matter what I do with it (extracting contents and using the .img within, changing .zip to .img) I get some error. I don't actually know what it is off the top of my head, but I tried to do it more than once in the past and always ran into the same problem.
Nicholo said:
Okay, now this is where I run into the TWRP problem I mentioned. I can't get TWRP 6.3.3+ installed because the file is a zip, and no matter what I do with it (extracting contents and using the .img within, changing .zip to .img) I get some error. I don't actually know what it is off the top of my head, but I tried to do it more than once in the past and always ran into the same problem.
Click to expand...
Click to collapse
You use autorec for twrp?
Sent from my LG-VS980 using XDA Free mobile app
Nicholo said:
Okay, now this is where I run into the TWRP problem I mentioned. I can't get TWRP 6.3.3+ installed because the file is a zip, and no matter what I do with it (extracting contents and using the .img within, changing .zip to .img) I get some error. I don't actually know what it is off the top of my head, but I tried to do it more than once in the past and always ran into the same problem.
Click to expand...
Click to collapse
Do you have a custom recovery? If so, flash the 2.7.x.x zip within your current recovery, then reboot recovery. If you don't have a custom recovery, then use autorec or freedom tool to install one.
Sent from my VS980 4G using XDA Premium 4 mobile app
Q&A for Modified Stock Rom - D41510c (Root, Polish, De-Bloat) (Flashable Zip)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Modified Stock Rom - D41510c (Root, Polish, De-Bloat) (Flashable Zip). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
DevoutDevelopment said:
I am trying to flash this to pull some files off of it and test some thing but for whatever reason it fails to unpack system and skips straight to set_perm then fails. I can't flash the ROM however I try it any ideas?
Click to expand...
Click to collapse
The only way that this works on my d415 is flashing first the stock kdz and then install recovery and install this rom. On recovery it says that the installation fails but when you reboot system it works and all the blotware has been removed and some other changes. If I try to install this comming from another custom rom it fails. I believe that.
ml21 said:
The only way that this works on my d415 is flashing first the stock kdz and then install recovery and install this rom. On recovery it says that the installation fails but when you reboot system it works and all the blotware has been removed and some other changes. If I try to install this comming from another custom rom it fails. I believe that.
Click to expand...
Click to collapse
I found the same thing, i think when flashing this rom it has an issue flashing the boot.img so when coming from certain roms it fail but when oming from stock rom it should work e ith the correct boot.img already being installed.
aerdely said:
I found the same thing, i think when flashing this rom it has an issue flashing the boot.img so when coming from certain roms it fail but when oming from stock rom it should work e ith the correct boot.img already being installed.
Click to expand...
Click to collapse
Maybe u are right. I will try to back up the boot.img of the lg stock rom and then try to install this first restoring the back up to see it works. Thank you
stock rom
hey, im excited to try this rom! but does anything not work as of right now? camera? video recording? and does xposed work? Thankyou for your hard work!
Solenz said:
Hi, can anyone post pictures of this modified stock ROM? I really hated the software skin of the LG stock ROM and saw that the OP removed "foo foo" themes. Did he modify the software skin?
If so, then I just found all the right reasons to switch back from CM 11 to stock. CM 11 is amazing but there is no video recording for me on D415 or video playback for anything above 360p which is a MAJOR disappointment.
EDIT: If anyone knows of a way for me to modify the stock skin of the LG stock ROM to make it more like Lolipop or CM 11, please let me know.
Click to expand...
Click to collapse
The L90 comes with LGHome and is it's own themer. There's a couple preinstalled ones that have probably removed. There's also a couple available for download on the play store Marketed as Lollipop.
Are there any mirrors to the Megaupload zip file? It's extremely slow download (11KBps average) for a 700MB file.
<Can't delete this post =/>
I installed the knock code from this post and now Towelroot says the phone is unsupported. Any fix for this? Thanks.
Help!!!! I tried flashing this and it gave me an error and it aborted. Now I'm stuck at the boot logo and I can't get into CWM!!!! Also, I erased my download mode. Is there a way for me to flash the laf partition using fastboot? I need this phone so I am sweating bullets here! :crying:
SOLVED: Okay. I flashed laf using fastboot. Now, I successfully flashed the stock kdz with the LG Tool and recovered completely. The answer was simple. I just panicked....lol. BTW, I attached the LG root zip for those that run into this situation. Just follow the instructions in the root.txt file.
I need some help here, and I need to stop bothering the guys in the ROM forum about it so I'm asking here instead.
It's a t-mobile note 4. I was running Dynamic Kat on it and it was suggested I update the modem and bootloader with a partial flash file. Now my phone is stuck in a bootloop.
I CAN get into both download mode and TWRP, however, so it seems like this should be fixable. I'd be happy with even going back to fully stock and rerooting it.
I found this thread: http://forum.xda-developers.com/not...to-downgrade-cod6-to-nk4-upgrade-nk4-t3095585 which seems to about flashing back to stock NK4 or cod6. I know those are bootloaders, but I don't really understand what they mean beyond that.
Or can I just flash to the new stock lollipop t-mobile put out this week? If so, how? If anyone has the time to help me with this, I would really appreciate it.
Edit: I found instructions on sammobile.com. Going to try them. *fixed
Caelrie said:
I need some help here, and I need to stop bothering the guys in the ROM forum about it so I'm asking here instead.
It's a t-mobile note 4. I was running Dynamic Kat on it and it was suggested I update the modem and bootloader with a partial flash file. Now my phone is stuck in a bootloop.
I CAN get into both download mode and TWRP, however, so it seems like this should be fixable. I'd be happy with even going back to fully stock and rerooting it.
I found this thread: http://forum.xda-developers.com/not...to-downgrade-cod6-to-nk4-upgrade-nk4-t3095585 which seems to about flashing back to stock NK4 or cod6. I know those are bootloaders, but I don't really understand what they mean beyond that.
Or can I just flash to the new stock lollipop t-mobile put out this week? If so, how? If anyone has the time to help me with this, I would really appreciate it.
Edit: I found instructions on sammobile.com. Going to try them.
Click to expand...
Click to collapse
Easy fix. ODIN flash the stock COD6 software. Then start over again with cf auto root. There is a thread that had all of the files you need in one zip.
Sent from my SM-N910T using XDA Free mobile app
Yayyy I think it worked! Stock Lollipop is booting up. It's in the Optimizing apps phase.
Caelrie said:
Yayyy I think it worked! Stock Lollipop is booting up. It's in the Optimizing apps phase.
Click to expand...
Click to collapse
Are you the same one who renamed the tar.md5 file to tar? If so, when you ask for help you really should mention all the steps you took to get there. Where it went wrong, etc.
When in doubt, Odin flash full firmware to get back to stock. There are other steps you could have taken as well but Odin is almost always a surefire bet.
(Also remember to hit the thanks button for those who have helped you get things sorted, like that fella above and the people who helped you in the rom thread- not me of course because I didn't do anything but for those who did I'm sure they would appreciate it)
absinthesummer said:
Are you the same one who renamed the tar.md5 file to tar? If so, when you ask for help you really should mention all the steps you took to get there. Where it went wrong, etc.
When in doubt, Odin flash full firmware to get back to stock. There are other steps you could have taken as well but Odin is almost always a surefire bet.
(Also remember to hit the thanks button for those who have helped you get things sorted, like that fella above and the people who helped you in the rom thread- not me of course because I didn't do anything but for those who did I'm sure they would appreciate it)
Click to expand...
Click to collapse
Yah, that was me. I came over here to ask for help instead because I shouldn't be bothering you guys in the ROM thread. I was making progress though. By the time I made this thread, I'd figured out that if I could get into TWRP or download mode, I could odin my way out of it. Just needed some help on that doing that, but then I figured that out too thanks to sammobile
Caelrie said:
Yah, that was me. I came over here to ask for help instead because I shouldn't be bothering you guys in the ROM thread. I was making progress though. By the time I made this thread, I'd figured out that if I could get into TWRP or download mode, I could odin my way out of it. Just needed some help on that doing that, but then I figured that out too thanks to sammobile
Click to expand...
Click to collapse
Cool, glad you got it sorted. Yeah as long as you can access download mode you're golden, and a bonus if you can get into recovery as well.
Excellent job actually searching and reading and fixing your problem, far too many people want answers just handed to them, so kudos to you for that.
Just for the future if you need help, try to remember and list all steps you took (even if you don't know where you went wrong) in excruciating detail because it helps us troubleshoot and figure out what the problem is. Without certain pertinent info it could take a lot longer to solve it.
Overall good job, glad you're up & running.
Go to rapture download the rom and load it to sd card. Then follow directions exactly and u will be ok. No loading anything. Fresh start
BAD ASS NOTE 4
I am in the same boat with the boot loop. I flashed the partial firmware file as well and I did not rename it and the flash went fine. After that it boot to the screen that says powered by Android then it reboots over and over. Currently downloading the stock cod so I can odin that.
ElAguila said:
I am in the same boat with the boot loop. I flashed the partial firmware file as well and I did not rename it and the flash went fine. After that it boot to the screen that says powered by Android then it reboots over and over. Currently downloading the stock cod so I can odin that.
Click to expand...
Click to collapse
Technically you shouldn't be flashing just the partial firmware. It sets up a base so that you can flash a lollipop rom in recovery without issues. I'm not sure why someone is recommending just flashing the partial firmware only. I guess they figured it wouldn't cause issues.
Anyway, here is how the partial firmware should be used:
Flash partial firmware in Odin
Flash flashable stock lollipop in recovery.
Set up rom, make a backup.
From here you can restore your old kitkat backups without the problems that some are seeing (those who Odin the full firmware are having problems restoring kitkat backups/flashing kitkat roms without Odining ank4 first). The partial firmware prevents that but it's designed to be flashed right before flashing a lollipop rom.
I hope that helps some of you who are having issues.