My N10 with stock 5.1 previously had root with TWRP 2.8.6, but for some reason it recently lost root. In addition, it seems that TWRP has been corrupted because whenever I try to boot into recovery I get a dead bootloader with a red exclamation mart. After I flashed the most recent version of TWRP 3.0.0-1 using "fastboot flash recovery twrp-3.0.0-1-manta.img" (bootloader still unlocked), I still get a dead bootloader when booting into recovery.
Then I flashed back to TWRP 2.8.6, but the problem remains!
How to fix the problem? Thanks!
I hope you can go to bootloader mode... Revert to stock by flashing the factory images and then start over again
nitin.chobhe said:
I hope you can go to bootloader mode... Revert to stock by flashing the factory images and then start over again
Click to expand...
Click to collapse
Thanks!
Just flashed an even older version (2.8.5) of TWRP, and now suddenly it can boot into recovery without any problem. I have also gained root now after flashing SuperSU.
I was planning to flash the most recent version of TWRP (3.0.0-1), and then try out CM13, but for some reason my N10 with stock 5.1 does not like those newer versions of TWRP. Do you know why?
mj56gt said:
Thanks!
Just flashed an even older version (2.8.5) of TWRP, and now suddenly it can boot into recovery without any problem. I have also gained root now after flashing SuperSU.
I was planning to flash the most recent version of TWRP (3.0.0-1), and then try out CM13, but for some reason my N10 with stock 5.1 does not like those newer versions of TWRP. Do you know why?
Click to expand...
Click to collapse
No, I do not konw that. Are you flashing correct version of TWRP made for manta?
nitin.chobhe said:
No, I do not konw that. Are you flashing correct version of TWRP made for manta?
Click to expand...
Click to collapse
I downloaded all the three versions (2.8.5, 2.8.6, and 3.0.0-1) of TWRP I've flashed so far from here:
https://dl.twrp.me/manta/
This is weird. Is it because I didn't have root during the time I flashed 2.8.6 or 3.0.0-1? I thought that flashing TWRP would not require root.
Can I flash CM13 with TWRP 2.8.5? I'll definitely make a Nandroid backup before proceeding.
mj56gt said:
I downloaded all the three versions (2.8.5, 2.8.6, and 3.0.0-1) of TWRP I've flashed so far from here:
https://dl.twrp.me/manta/
This is weird. Is it because I didn't have root during the time I flashed 2.8.6 or 3.0.0-1? I thought that flashing TWRP would not require root.
Can I flash CM13 with TWRP 2.8.5? I'll definitely make a Nandroid backup before proceeding.
Click to expand...
Click to collapse
With nandroid, you are good to go.
Should be possible :fingers-crossed:
nitin.chobhe said:
With nandroid, you are good to go.
Should be possible :fingers-crossed:
Click to expand...
Click to collapse
I did factory reset in TWRP 3.0.0-1 and then flashed CM 13.0-20160309 on my N10 with the dynamic Gapps. Now I get this error Unfortunately Google Play Services Has Stopped. Is it because the default factory reset is not good enough or something else? If it needs a full wipe, what exactly should I wipe, system and data? And after a full wipe, do I need to reflash CM13 or just Gapps?
Thanks!
mj56gt said:
I did factory reset in TWRP 3.0.0-1 and then flashed CM 13.0-20160309 on my N10 with the dynamic Gapps. Now I get this error Unfortunately Google Play Services Has Stopped. Is it because the default factory reset is not good enough or something else? If it needs a full wipe, what exactly should I wipe, system and data? And after a full wipe, do I need to reflash CM13 or just Gapps?
Thanks!
Click to expand...
Click to collapse
Problem solved: Just flashed the pico Gapps, and now everything works fine. For some reason the dynamic Gapps didn't work for me.
mj56gt said:
Problem solved: Just flashed the pico Gapps, and now everything works fine. For some reason the dynamic Gapps didn't work for me.
Click to expand...
Click to collapse
May be there isn't enough space to flash them.
Happy that is working now
Sent from my Nexus 4 using XDA Free mobile app
Related
Hello!
Previously I've had PA 3.99 but today I downloaded stock 4.4 from google site and flashed it via fastboot. System works perfectly, but always when I want to flash CWM or TWRP (newest) phone stuck on boot (but recovery works)
Anyone knows the reason?
Cheers!
Try...
Colourkey said:
Hello!
Previously I've had PA 3.99 but today I downloaded stock 4.4 from google site and flashed it via fastboot. System works perfectly, but always when I want to flash CWM or TWRP (newest) phone stuck on boot (but recovery works)
Anyone knows the reason?
Cheers!
Click to expand...
Click to collapse
Try wiping data/cache after flashing recovery in this recovery.
I'm stupid. Worked. Thanks!
But
Colourkey said:
w8
Click to expand...
Click to collapse
I mean after you stuck at boot logo and already installed TWRP enter TWRP and wipe those If it not work flash zip of an 4.4 thats already rooted.
msihp said:
I mean after you stuck at boot logo and already installed TWRP enter TWRP and wipe those If it not work flash zip of an 4.4 thats already rooted.
Click to expand...
Click to collapse
Sorry for misunderstood. I answered before fact that phone finally boot. Wipe helped, I'm stupid, because I forgot about that ;D
Dzięki!
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
Hi!
EDIT: Never mind, problem solved. Sorry.
I have finally decided to root my G900F (6.0.1). I flashed TWRP through Odin without problems, booted to TWRP to make it permanent, booted normally to check that all is well. After that I made a full backup in TWRP and flashed the BETA-SuperSU-v2.49.zip. After that, my phone no longer boots (hangs on the Galaxy S5 screen with a blue indicator LED).
I can still boot to TWRP.
How can I fix my phone? Please help. What did I do wrong?
I did try wiping the cache partition but nothing else.
Hopefully the solution does not require a full wipe.
EDIT: I see what I did wrong. I have accidentally flashed an old SuperSU.
Can I use a backup I made with a TWRP?
EDIT2: Luckily the restore did work! Will try to flash a more recent SuperSU.
flash it again but with latest version of supersu. It will work
Spawnknight said:
flash it again but with latest version of supersu. It will work
Click to expand...
Click to collapse
Yup, it did work beautifully. Lucky for me that I remembered to make a backup before rooting.
Heyy,
as i had some problems with my g2 i had to flash stock rom kitkat 4.4.2.
I rooted with ioroot, downloaded lineage and gapps files, flashed custom recovery with autorec but if i then go to twrp and install lineage os and gapps, i always get "your device does not appear to have root. do u want to install supersu?", althoug ive checked root with "root checker" before... i cant find the mistake
I WANT LINEAGE OS
Quicka said:
Heyy,
as i had some problems with my g2 i had to flash stock rom kitkat 4.4.2.
I rooted with ioroot, downloaded lineage and gapps files, flashed custom recovery with autorec but if i then go to twrp and install lineage os and gapps, i always get "your device does not appear to have root. do u want to install supersu?", althoug ive checked root with "root checker" before... i cant find the mistake
I WANT LINEAGE OS
Click to expand...
Click to collapse
Autorec is just the first step to twrp. Go to https://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705 and get the bumped version 3.1.0-1.
Then put it in your phones memory, boot into twrp you got from autorec and flash the new version.
Jan Philipp said:
Autorec is just the first step to twrp. Go to https://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705 and get the bumped version 3.1.0-1.
Then put it in your phones memory, boot into twrp you got from autorec and flash the new version.
Click to expand...
Click to collapse
i have done it... but after i wiped data,... etc. flashed lineage os and gapps and reboot system, phone screen gets black... and i can only go to download mode to flash again stock rom ive tried it about 5 times
Problem fixed
problem fixed: flashed lollipop firmware, then rooted with LGoneClickRoot and installed TWRP with autorec
Quicka said:
problem fixed: flashed lollipop firmware, then rooted with LGoneClickRoot and installed TWRP with autorec
Click to expand...
Click to collapse
How did you flashed your phone? Your display have been black and you haven't seen anything. How did you entered into download mode?
djsasha78 said:
How did you flashed your phone? Your display have been black and you haven't seen anything. How did you entered into download mode?
Click to expand...
Click to collapse
just held the volume up button and then connected with pc. then using lg flash tool to flash lollipop stock rom
1. Root + TWRP : https://www.dropbox.com/s/2shvozzbu29xjfu/LGG2-D802-OneClickRootRecoveryV1.1.zip?dl=0
2. Update TWRP to 3.1 by flashing zip file and then rebooting recovery: http://www.gregtwallace.com/lgg2-projects/twrp/?version=3.1.0-1
3. LineageOS by flashing rom zip file and gapps: https://download.lineageos.org/d802 + http://opengapps.org/ (ARM + Android 7.1)
easiest method to flash lineageOS on LG G2 https://www.youtube.com/watch?v=BoPjGM0nrak (Video tutorial)
Hi,
It seems I have the same issue :
I tried to install LineAge, using TWRP 3.2.1 (from CM12.1), but nothing is working (I tried 20180425 and 20180404 nightly versions). After reboot I can see the backlight on the lcd screen but nothing else. Then I tested the installation of a CM12 version, all is right, normal boot. No error message written in the console. i tried also a CM13 install, same as Lineage.
Do you think I have to flask back to LG "OS" ?
JackSparreau said:
Hi,
It seems I have the same issue :
I tried to install LineAge, using TWRP 3.2.1 (from CM12.1), but nothing is working (I tried 20180425 and 20180404 nightly versions). After reboot I can see the backlight on the lcd screen but nothing else. Then I tested the installation of a CM12 version, all is right, normal boot. No error message written in the console. i tried also a CM13 install, same as Lineage.
Do you think I have to flask back to LG "OS" ?
Click to expand...
Click to collapse
Are you clean flashing? Make sure to factory reset, wipe system, data and cache before flash. Never wipe internal storage. Swipe factory reset again after flash. Try flashing gapps later after confirming that Rom boots fine.
cropsroth said:
Are you clean flashing? Make sure to factory reset, wipe system, data and cache before flash. Never wipe internal storage. Swipe factory reset again after flash. Try flashing gapps later after confirming that Rom boots fine.
Click to expand...
Click to collapse
Hi,
yes I wiped Dalvik, system, data & cache through TWRP, before flash. But I don't wipe after, I rebooted without GApps...
Maybe, because I read that somewhere, I need to flash a bootstack. I don't know when I have to di it, if I have to do.
Thanks
JackSparreau said:
Hi,
yes I wiped Dalvik, system, data & cache through TWRP, before flash. But I don't wipe after, I rebooted without GApps...
Maybe, because I read that somewhere, I need to flash a bootstack. I don't know when I have to di it, if I have to do.
Thanks
Click to expand...
Click to collapse
Yes, you don't wipe after flash, but you swipe the factory reset, it does not wipe but resets the flashed Rom. Give it a clean shot again. Check MD5 of the all files you downloaded with original MD5 to confirm the file didn't get corrupt.
Boot stack flash not needed. Please read the first post thoroughly in lineage thread
"""
Requirements:
Custom recovery (TWRP or any other)
KitKat (KK) bootloader (included in the lg-devs LP bootstack)
KitKat (KK) bootstack minimum; Please read the entire FAQ for important bootstack information. Installation of bootstacks is NOT recommended.
Clean flash if coming from another ROM or CM 13 (no dirty flash, wipe system too check you bootstack(needen bump support)
"""
crophs said:
... but you swipe the factory reset, it does not wipe but resets the flashed Rom. Give it a clean shot again. ...
Click to expand...
Click to collapse
Hi,
what do you mean by "you swipe the factory reset", I'm not sure what it is, either "give it a clean shot again".
Sorry I'm not very aware of all those processes ^_^, and I'm french so not very aware of some vocabulary words
Thank you
Okay so I've tried Pixel experience, lineage os , omni rom treskmod and couple of other custom android 10 roms, all stable and official and also updated ones, the wifi just simply doesn't work, wifi hotspot won't turn on either. I've tried every solution on the internet. I've even factory reset my phone using msm download tool and no luck(did this countless times).
I'm back in OOS 10.3.2 and there's no issue apparently.
At one point , i flashed a custom rom and the wifi didn't work, so I flashed OOS in the two slots and checked , the wifi works in OOS apparently, and never in custom roms.
Has anyone got this issue before and knows a solution?
How is your installation procedure?
onliner said:
How is your installation procedure?
Click to expand...
Click to collapse
I flash OOS and twrp on both slots, reboot recovery,
And then flash the rom and twrp, reboot recovery,then format data and factory reset, reboot recovery, if needed for some gapps, then reboot system
ivanthomas said:
I flash OOS and twrp on both slots, reboot recovery,
And then flash the rom and twrp, reboot recovery,then format data and factory reset, reboot recovery, if needed for some gapps, then reboot system
Click to expand...
Click to collapse
That's a lot of unnecessary steps. OOS on both slots, reboot to bootloader, boot twrp, format data and flash the custom rom, reboot bootloader, boot twrp and flash gapps, don't install twrp permanently if you are not going to install Magisk.
onliner said:
That's a lot of unnecessary steps. OOS on both slots, reboot to bootloader, boot twrp, format data and flash the custom rom, reboot bootloader, boot twrp and flash gapps, don't install twrp permanently if you are not going to install Magisk.
Click to expand...
Click to collapse
I need magisk too, I usually permanently install twrp
Also you think it's the way I'm installing at fault here? Or the rom? Or is it something wrong with my device?
ivanthomas said:
it's the way I'm installing at fault here?
Click to expand...
Click to collapse
This.
I always install roms with the procedure i said above and have never had any problems.
onliner said:
This.
I always install roms with the procedure i said above and have never had any problems.
Click to expand...
Click to collapse
Alright so got one doubt, I used OOS 10.3.2 to flash, should it be oos 10.0 only?
Thought that didn't make a difference.
I am also facing the same issue. Were you able to find any solution ?
So I found out treskmod omni rom and Paranoid android quartz 2 work perfectly , try those out, it still doesn't solve the problem in the other roms though. So not exactly a solution.