I have an LGG3 D855 and after flashing the new cm 14.1 it wont boot to system... I have tired restoring a back up and the old system and different systems and stock roms but nothing is working.
Hi why dont you flash back to stock http://forum.xda-developers.com/showthread.php?t=2785089 then go back and root it this happened to me about a mth ago to and the ToT method was the only one that worked. Hope this helps ?
Sent from my LG-D855 using XDA-Developers mobile app
KJMckenzie said:
I have an LGG3 D855 and after flashing the new cm 14.1 it wont boot to system... I have tired restoring a back up and the old system and different systems and stock roms but nothing is working.
Click to expand...
Click to collapse
Which version is your twrp?...
Sent from my LG-D855 using XDA Free mobile app
i had similar problem after installing techcafe's rom..... all i did was a full format of the NAND memory (more than a factory reset) and flashed the rom again thru TWRP of course and Bam!!! i got normal boot
I think you should used LG up to come back stock
Related
So i have an OGP AT&T E980. Rooted awhile back with no problems. Last night, I tried flashing my first ever ROM (beanstalk 4.3 unofficial in the OGP forum). Silly noob me didn't make an image of the stock rom before I flashed Beanstalk. Got to beanstalk fine but didn't like it so i tried recovery mode to go back to stock. No go. Now I'm stuck in bootloop/pulsing LED with
Secure Booting Error
Cause: Device UnLock, so boot success!!
I can get into CWM-based recovery v6.0.3.7 and I've wiped data/factory reset, cache partition, and davlink cache several times and still in bootloop. I've also entered download mode but it doesn't give me the option to download anything. And I've done hard factory resets to no avail.
I have the stock ROM downloaded on my mac (only computer available to me) but android file transfer doesn't register that the phone is plugged in. If I could get it at least back onto Beanstalk, I'm sure I could put the stock ROM on and flash it then.
Does my logic seem right and can anyone point me in the right direction? Any help would be greatly appreciated
I backed to stock in download mode with lg update tool .
Sent from my LG-E989 using Tapatalk 4
raber111 said:
I backed to stock in download mode with lg update tool .
Sent from my LG-E989 using Tapatalk 4
Click to expand...
Click to collapse
I don't think LG update tool supports Mac computers.
Thats i don't know
Sent from my LG-E989 using Tapatalk 4
FIXED
OKAY I GOT IT.
So what happened was that when I hard reset, it deleted the Bean Stalk ROM and I didn't have anything to go back to since I didn't make a backup of the initial stock ROM. It was purgatory for my OGP lol. So I had to find a ROM backup (in my case I used the debloated stock ROM) and put it on an external SD card. Then restore from backup and boom goes the dynamite.
Thanks for your help!
Always keep a backup of at least one ROM to revert to at anytime.
Sent from my LG-E980 using XDA Premium 4 mobile app
---------- Post added at 08:19 AM ---------- Previous post was at 08:19 AM ----------
I know I've had some close calls back in the past. Lol.
Sent from my LG-E980 using XDA Premium 4 mobile app
I was using the latest alpha of CM11, then i i wanted to get back to CM10.2, i did all i had to do (wipes, and stuff) and when starting up, the phone frezees and keep on doing this...
I also have searched about this issue and found no answer.
tpag02 said:
I was using the latest alpha of CM11, then i i wanted to get back to CM10.2, i did all i had to do (wipes, and stuff) and when starting up, the phone frezees and keep on doing this...
I also have searched about this issue and found no answer.
Click to expand...
Click to collapse
Have you tried booting to recovery, then doing an advanced wipe (system/data/cache/dalvik) and reflashing rom/gapps?
What version of recovery are you using?
Almite said:
Have you tried booting to recovery, then doing an advanced wipe (system/data/cache/dalvik) and reflashing rom/gapps?
What version of recovery are you using?
Click to expand...
Click to collapse
yes, i have. I also got back to stock, used an older recover, flashed with an older version of CM and nothing. I first was using CWM 6.0.3.7., after that I used 6.0.4.3, then an older version of TWRP but nothing. I also tried booting to system without flashing gapps.
With stock ROM everything works just fine.
Just wipeout internal and external card once and than install with twrp 2.6.1.0. And don't forget to say thanks
Sent from my SGH-T989 using xda app-developers app
iamdofus said:
Just wipeout internal and external card once and than install with twrp 2.6.1.0. And don't forget to say thanks
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Well, thank you, but it didn´t work.
it happened to me the same thing months ago. never had solution. still in waiting. attempt internal and external SD format. and followed the same. I hope someday they can come up with the solution! : (
i have the same problem too
I try to install multiple ROM 4.2.2 and I could only install one version AOKP Milstone JB1. I also worked the other. however all 4.1.2 rom if I worked. I could not install any 4.3 and 4.4 now does not know what is the problem but I've tried everything! anyone found the solution yet but I see I'm not the only one! (excuse my bad English, not my language )
Well you all are right, I am also using shadow mastery (stock rooted rom). Just because I had the same problem sometimes stucking and rebooting and sometimes after going in gallery. Even I can't use 4.3 and 4.4 roms. Anyone have to contact with room developer or someone who know about this problem.
Sent from my SGH-T989 using xda premium
You might want to find an Official T-Mobile or Telus 4.1.2 or 4.0.3/4.0.4 rom that is Odin flashable, not one that has been custom made/flashable from recovery - then just start over after getting back to true stock, change to TWRP or CWM recovery that is 4.3+ compatiable, root and then flash rom/gapps etc.
So, I'm having this strange issue where I can't boot into Recovery Mode.
I've been a flashaholic for a little over a year now, but I've never had this problem.
I wanted to get off of Philz because it wasn't wiping my phone correctly while flashing new roms, so I decided to go back to good 'ol TWRP.
I downloaded Goomamager and tried to install, no luck.
So I hopped on my laptop to flash via ODIN, still a no go.
Only after that, it doesn't boot into Recovery at all.
I tried to use ROM Manager to install CWM, because at this point I'm willing to use anything, still a no go.
Anyone got any ideas?
I can get into Download Mode, but no Recovery is sticking.
I try to boot into Recovery, but the device just reboots itself.
Any help is appreciated, thanks.
Sent from my SM-N900T using XDA Premium 4 mobile app
devynbf said:
So, I'm having this strange issue where I can't boot into Recovery Mode.
I've been a flashaholic for a little over a year now, but I've never had this problem.
I wanted to get off of Philz because it wasn't wiping my phone correctly while flashing new roms, so I decided to go back to good 'ol TWRP.
I downloaded Goomamager and tried to install, no luck.
So I hopped on my laptop to flash via ODIN, still a no go.
Only after that, it doesn't boot into Recovery at all.
I tried to use ROM Manager to install CWM, because at this point I'm willing to use anything, still a no go.
Anyone got any ideas?
I can get into Download Mode, but no Recovery is sticking.
I try to boot into Recovery, but the device just reboots itself.
Any help is appreciated, thanks.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Depends on the android version. Also go back to stock with Odin and start all over. Make sure you using right recovery ? As far as philz cwm not wiping properly. Not to sure about that one. A wipe is a generic thing. What do you mean not wiping the right way?
TWEAKED 2.0 ELEMENT V3.0 NOTE 3
BACARDILIMON said:
Depends on the android version. Also go back to stock with Odin and start all over. Make sure you using right recovery ? As far as philz cwm not wiping properly. Not to sure about that one. A wipe is a generic thing. What do you mean not wiping the right way?
TWEAKED 2.0 ELEMENT V3.0 NOTE 3
Click to expand...
Click to collapse
Alright, I was gonna do that tomorrow on my day off, since the device seems to function properly mostly.
With Philz, I mean that I would Factory Reset, Wipe Data and "Wipe for new ROM", but when I would flash the new ROM, it would still have everything I had before on the device's SD memory, (which to me, is not a clean flash).
I am on Temasek's 4.4 CM11 v50.
I've been using this ROM for a long time and I've never had this problem in the past.
Sent from my SM-N900T using XDA Premium 4 mobile app
devynbf said:
Alright, I was gonna do that tomorrow on my day off, since the device seems to function properly mostly.
With Philz, I mean that I would Factory Reset, Wipe Data and "Wipe for new ROM", but when I would flash the new ROM, it would still have everything I had before on the device's SD memory, (which to me, is not a clean flash).
I am on Temasek's 4.4 CM11 v50.
I've been using this ROM for a long time and I've never had this problem in the past.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK I am not familiar with asop so I don't know what to say. But best bet is Odin back then flash twrp as you would like
TWEAKED 2.0 ELEMENT V3.0 NOTE 3
just connect fastboot
fastboot flash recovery (recoveryname).img
Hi man,i also have a sm n900t and im having this problem to,tried with every kind of recovery but no1 made it possible to boot into recovery,did you find an answer?
Hi,
What is the best way to kitkat when youre rooted with dalingrin method and you want no data loss and sd card problems ?
Sent from my LG-V500 using xda app-developers app
Flash this: http://forum.xda-developers.com/showthread.php?t=2707363
all prerequisites and instructions are in the link.
For me it didn't work 100% the first time, had some weird keyboard issues.
Just flashed it another time and now it's been 100% stable for a week.
Thanks for the answer. Didn't you have any issues with mounted games and the foldermount ? Because I've got many games on the sdcard.
And did you flash twrp 2.7.0.1 for ota or 2.7.0.0 ?
Sent from my HTC One X+ using xda app-developers app
You need 2.7.0.1, it says so in the instructions. I think 2.7.0.0 will also work but you get dim screen issues in twrp.
The new KOT49I.V50020B OTA already includes "External SD R\W Fix"
Features:
Official Stock 4.4.2 LG build KOT49I.V50020B GB EU+ Stock 4.4.2 Kernel
NO Data Wipe
Doesn't flash over existing Recovery or ABOOT (you keep TWRP and retain loki-exploit)
SuperSU 1.94 + su binary Installed
BusyBox 1.22.1-Stericson Installed
Wipes Dalvik-Cache and Cache partition
Working English QVoice and Q Apps
External SD R\W Fix
Click to expand...
Click to collapse
So you keep all your data, you keep root, you keep TWRP, and no SDcard issues.
Just make a full back up first and try it, you can go back if you don't like it.
As said I had to flash it a second time but it has been flawless since.
It's preferable over taking the official OTA as you won't have to reroot, reinstall recovery and fix sd card permissions.
Only issue is with icons for LG apps in 3rd party launchers, but that is the same in the official update.
Thanks again...just one more "stupid" question, can I flash the new twrp over the old one without deinstalling it ? I have the 2.6.2.3 or something like that...
Sent from my HTC One X+ using xda app-developers app
Yes, just download the new twrp, boot into recovery and install the new twrp from the old twrp.
Reboot into recovery and check if you're on 2.7.0.1
Sent from my LG-V500 using Tapatalk
Also no problems without random unmounted sd cards?
Sent from my LG-V500 using xda app-developers app
Nope.
Sent from my LG-V500 using Tapatalk
Thanks again for the answers. .. Everything is ready here but I still hesitate. ... What are the big differences? Battery, is it faster, ...
Sent from my LG-V500 using xda app-developers app
Why hesitate?
Boot into recovery, make a full backup and then flash the new rom.
If you don't like the new rom, restore your backup like nothing ever happened.
New rom is smoother, and the sound from the speakers is better.
Damn...I get com.android.systemui stopped... I can do nothing,not even get to the app twrp to boot in recovery. I managed with the hardware buttons and I'm restoring the backup...fingers crossed... What went wrong ? Backup worked !!
But what could be the reason for stopped systemui ? Is it because I live in Belgium (EU-rom ?) or do I have to wipe dalvik cache and data cache after flashing the rom ?
Edit: downloaded the file again and flashed and did manually wiped data and dalvik cache.... now it works like a charm.... till now ?
Sent from my HTC One X+ using XDA Free mobile app
Hello, I got the lollipop update on OTA on my LG G3 and as soon as installed the Home Launcher crashed with this message "System UIDs Inconsistent" you need to wipe your data partition. I even tried to flash the mobile again with a stock ROM using the CSE Flash option in the Flasher 2014, as it suppose to format the data partition and installs a clean copy, but even after the flashing the HOME still crashes with the same message " as if was only upgraded not newly installed, I even got a message "Android Upgrading" when first booted, I have been searching for a way to completely format or clear the phone partition as i think it is the solution for the problem, do I have to root to clean up the partition or there is a way to format the phone without rooting?
NB: I couldn't find a way to root it on Lollipop
Maybe u should try to downgrade to kitkat first using the tot method then u can install the lollipop again
Sent from my LG-F460S using XDA Premium 4 mobile app
Falcon51 said:
Maybe u should try to downgrade to kitkat first using the tot method then u can install the lollipop again
Sent from my LG-F460S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry but what is the difference between the kdz and the tot way?
Solved: Finally
The SOLUTION is: You HAVE to downgrade to kitkat 4.4.2 then upgrade your RUNTIME to ART instead of Dalvik then clear cache and restore factory settings then DO THE FLASHING to Lollipop v. 5.0... Thanks falcon51
:laugh: