Hi everyone
i have been 2 weeks with Lineage 14.1 now and it works fast and without problems.... But the 4k is not supported... I downgraded to Marshmallow again but I've lost the recovery mode.... I've tryed to install again the recovery with flasify but that did not work either... When I tryed to reboot in the recovery mode the screen turns black and the led starts flashing in red and blue.
jose_fley said:
Hi everyone
i have been 2 weeks with Lineage 14.1 now and it works fast and without problems.... But the 4k is not supported... I downgraded to Marshmallow again but I've lost the recovery mode.... I've tryed to install again the recovery with flasify but that did not work either... When I tryed to reboot in the recovery mode the screen turns black and the led starts flashing in red and blue.
Click to expand...
Click to collapse
already solved.
However: There is chance that Lineage 14.1 will support 4k in the future?
Hey, can tell me how u managed to install TWRP recovery ?
I've been trying to do that for few hours but nothing seems to work. Tried flashing normal TWRP, BUMP method, Autorec but nothing seems to work. I still get blinking red/blue when trying to access recovery. Running rooted stock 5.0 right now.
armido15 said:
Hey, can tell me how u managed to install TWRP recovery ?
I've been trying to do that for few hours but nothing seems to work. Tried flashing normal TWRP, BUMP method, Autorec but nothing seems to work. I still get blinking red/blue when trying to access recovery. Running rooted stock 5.0 right now.
Click to expand...
Click to collapse
It's so funny because my phone comes with Marshmallow and Kingroot never worked and I've tried it many times in every way.
Then I did donwgrade it to the lollipot version (you have the link in this post)
Then I made the root very easy, after upgrading to Lineage14.1 and when I returned to Marsmallow the KingRoot..... Surprise!! worked perfectly!. I think that when already having TWRP installed in the phone is when KingRoot really works with Marhmallow ... I think some people have problems rooting the phone with the Marsmallow version when is the first time they root the phone, but once the phone has been rooted before with TWRP instaled, then the Marsmallow Kingroot works perfectly.
Related
Hey,
I had AOSP installed on my ascend p6, everything working no problems at all.
Suddenly when I was a week on vacation when my battery died it wouldn't get passed the rom loading screen.
I have TWRP 2.7 and have wiped everything and everything over and over but nothing is working. I am now trying to install The lastest aosp sincde OMNI and CM11 didn't work.
Any help how to fix this? it keeps happening at every rom I install.
Little update:
I just tried reverting from twrp 2.7 to stock boot and recovery and I think I just bricked my device Can;t get passed the huawei ascend screen.
I wanted to reinstall the 118cn from stock recovery. is there anyway to fix this? Thank you!
UPDATE: Okay somehow after rebooting it around 20 times with fastboot, recovery and other combinations it is now booting I think. Praise the lords. It is now optimizing the apps
I have no idea what I did but I will post an update when it is done optimising
UPDATE UPDATE: Okay the weirdest thing just happened and I don't get this at all... I have wiped my whole phone like 5 times. with itsto and exsto. but somehow I now boots with all my apps, settings and launcher intact and inplace... I even installed multiple roms trying to make it work. WHAT IS THIS MAGIC?!
I know I shouldnt do this but I am going to re-install twrp 2.6.*.* and then pushing it to 2.7. Wish me luck! (following the excact instructions to make it work haha)
UPDATE UPDATE UPDATE: Okay, After seeing the wi-fi not turning on I tried rebooting my phone now it is stuck at the huawei ascend screen.
TomTheTiger said:
Little update:
I just tried reverting from twrp 2.7 to stock boot and recovery and I think I just bricked my device Can;t get passed the huawei ascend screen.
I wanted to reinstall the 118cn from stock recovery. is there anyway to fix this? Thank you!
Click to expand...
Click to collapse
Jelly Bean China stock roms can brick device (lots of users on xda got their device bricked). If you wanted to unlock, best to use KK China.
warea said:
Jelly Bean China stock roms can brick device (lots of users on xda got their device bricked). If you wanted to unlock, best to use KK China.
Click to expand...
Click to collapse
Will try! I thought I was passed this haha. When It starts i'll try to figure out a way to install it probs trough adb fastboot. since I can't get to the recovery screen with buttons
Update: Okay I managed to boot recovery up trough adb, It automatically started installing the update.app package.
I am now hoping for the best, one good thing... My phone was luckily already in unlock state
UPdate: Succesfully flashed my phone the stock with unlocked bootloader!
UPDate: And now on omni rom Everything is working fine!
Ok guys I am pretty sure I fubar'd my tablet.
I am stuck in a recovery loop. When I start the tablet it just goes back into recovery. Which if I still had TWRP I think I could still do something, but I flashed cyanogen recovery trying to flash cm13 since I cold not get anything else to work. I cannot boot into download/firmware update screen. The screen just flickers a little and goes dark.
A little background:
Started when tablet forced install of 5.0 update and I was in a recovery loop. I flashed 410 test build, rooted, flashed twrp, installed stock rooted ROM. Everything was fine. Then tablet did it again, this time I just flashed rooted ROM and factory reset. Even took the steps to fix the white lines and storage issues. Was working fine. Got home a few days ago and I was in a recovery loop again. But now I don't have the bootloader screen/download mode/firmware update screen (whatever you want to call it) so last night i tried to download cm13, Gapps and cyanogen recovery with no avail.
I can access adb on my PC while in recovery, but when I try to access ADB shell I get unauthorized something or other. Because I cannot authorize USB debugging, because ROM won't boot. I tried to flash stock rooted ROM from cyanogen recovery and it says not signed or something like that.
Does anyone have any ideas? I really think I have screwed the pooch here.
sent from a device using an app
title
if you have a stock recovery image flashing it is easy, i had a LOT of troubles with my v410 and still am working with it. i have mine rooted, just with TWRP though, i cant use xposed framework, which negates why i rooted this in the first place. anyway, through much grit and determination flash your stock image after wiping what needs to be wiped and doing all other necessary things. Then, you must download kingo root, supersu, superuser. flashify would help with the flashing i hear, but it has troubles with the v410. kingo root was an apk i managed to find buried under a million viruses on the 34th page of google..or something. rooted mine in one click, from stock to reboot to twrp root.. many glitches.
I need help myself, deleted my "Phone" system app, causing me to lose connectivity with my data plan. cant seem to restore it, and flashify nor twrp has been able to flash a custom recovery, or a backup, im at a loss.
Help? We seek the same thing.
Ok but how do I flash the stock recovery image. I can't use fastboot. ADB says I am unauthorized.
sent from a device using an app
Anyone have any other ideas?
I am at a complete loss. I am by no means a developer, but I do know my way around. I really think I have FUBAR'd this one.
Kind of stinks, I give up. Anyone want a bricked v410?
Sent from my Galaxy Tab 2 using Tapatalk
Hi,
My H815 always suffered from this problem: http://forum.xda-developers.com/g4/help/fastboot-download-mode-problem-t3466649 - the only way I could have fastboot was from an adb shell.
Well, that was not a problem until today: CM14's nightly broke (booting just loops at the moving logo) and now I have no way to go back to fastboot. And if I try the recovery mode, I just have a blurry circle saying "erasing" for a few seconds, then a looping CM logo.
Anyone has a way out of this mess ?
bestouff said:
Hi,
My H815 always suffered from this problem: http://forum.xda-developers.com/g4/help/fastboot-download-mode-problem-t3466649 - the only way I could have fastboot was from an adb shell.
Well, that was not a problem until today: CM14's nightly broke (booting just loops at the moving logo) and now I have no way to go back to fastboot. And if I try the recovery mode, I just have a blurry circle saying "erasing" for a few seconds, then a looping CM logo.
Anyone has a way out of this mess ?
Click to expand...
Click to collapse
When you say you try the recovery mode how do you try to get into it? Btw do you have twrp installed?
Same thing happened to me, tried to install, just got put straight back in to TWRP after boot. Tried installing a stock ROM, CM ROM & using LG Bridge to recover, to no avail. Help appreciated, (i'm assuming LGUP is going to come up a lot)
Tycoon282 said:
Same thing happened to me, tried to install, just got put straight back in to TWRP after boot. Tried installing a stock ROM, CM ROM & using LG Bridge to recover, to no avail. Help appreciated, (i'm assuming LGUP is going to come up a lot)
Click to expand...
Click to collapse
The OP has another issue pls do not hijack.
steadfasterX said:
The OP has another issue pls do not hijack.
Click to expand...
Click to collapse
Sorry, it's nearly the same issue though, CM14.1 broke phones today.
Today's update broke mine as well. Looking for solutions. Will follow your thread and progress.
Same for me. Tried download mode with lgup to flash stock which worked once - but I kind of bricked it again by trying to install cm14.1 again. Then i tried to go back to stock using lgup again, but now lgup it just crashes. The phone now goes automatically to download mode after turning it on, the progress bar stays at 0%, the phone says "633A B100" and lgup crashes after 9% "prepare dlmode" or something similar. any ideas? :/
Some people seem to have fixed this issue by flashing the official Cyanogenmod Recovery.
thewild said:
Some people seem to have fixed this issue by flashing the official Cyanogenmod Recovery.
Click to expand...
Click to collapse
After flashig the CM Recovery via TWRP, i can't use the recovery anymore. If i boot into CM-Recovery the display shows "Ereasing" and start the system. After that i got a bootloop.
Is it possible to use fastboot??
You guys should also check CM14.1 thread because people there are talking about the same problem. The latest post says the only solution was to flash an official kdz with LGUP.
thewild said:
You guys should also check CM14.1 thread because people there are talking about the same problem. The latest post says the only solution was to flash an official kdz with LGUP.
Click to expand...
Click to collapse
Did that. Worked once. Then i tried to flash cm again and had the same problems, so i wanted to flash stock again... now lgup crashes at 9% and the phones goes directly to download mode after turning it on.
onlyolli said:
Did that. Worked once. Then i tried to flash cm again and had the same problems, so i wanted to flash stock again... now lgup crashes at 9% and the phones goes directly to download mode after turning it on.
Click to expand...
Click to collapse
And the two times you tried to flash CM, that was with the same recovery ?
Can you go into fastboot mode ?
thewild said:
And the two times you tried to flash CM, that was with the same recovery ?
Can you go into fastboot mode ?
Click to expand...
Click to collapse
Yes, it was with cm recovery 20161130, if i remember correctly.
Sadly now, i can not go into fastboot. The phone goes directly into download mode. My windows vm detects the phone, and tries to flash a recent kdz, but lgup crashes at 9%. The phone still shows "0%".
Oh that's bad. What about another kdz ?
thewild said:
Oh that's bad. What about another kdz ?
Click to expand...
Click to collapse
Already tried like 3-4.... Its always the same. If the tool would at least give me a little bit more information, but it just stops.
I don't know then. Some users seem to have had the same problem (stuck at 9%) : http://forum.xda-developers.com/search/forum/4233?query=lgup 9%
I had the same issue, tried several things, my final solution was:
- Start in download mode (Volumen up and then plug in cable)
- use "LG Brigde" on Mac to install stock Rom ( Software update tab in APP ) guess should also work with Windows
- Boot original android
- enable usb debug
- Start bootloader via ADB
- fastboot flash recovery to twrp 3.0.2
- Boot in recovery via power and vol down (first factory reset from stock appears but after this twrp is starting)
- install cm nighty of 1 DEC via ADB sideload
- reboot and done
In the meantime i updated to twrp 3.0.2-1., installed gapps etc. everything is now working fine again.
Hope this is also working for you.
Which version of cm14 did u download and install? Can u please post the exact version?
Mmh ... LGUP is the Windows utility right ? How do I do if I only have a Linux machine ?
steadfasterX said:
When you say you try the recovery mode how do you try to get into it? Btw do you have twrp installed?
Click to expand...
Click to collapse
I'm trying to get to it via power+down, I get to the double "do you want to factory reset ?" question, but then :
- sometimes the CM recovery just says "erasing" for a few seconds and reboots to (non-working) CM
- sometimes it just plainly boots to (non-working) CM
I used to have TWRP installed but it didn't work with CM update, so I let CM install its own recovery.
So two days before Android Oreo update released (RETEU channel). I tried to flash Magisk cause i needed root access but then i realized that the Bootloader was locked and i unlocked it. Everything was ok until i tried to flash a custom recovery (TWRP) but after that everything was way too complicated. I flashed TWRP but everytime i was trying to restart my phone and get there it was replaced with the stock recovery. I tried to find something online and i did here in XDA. Everything was working and i said that is time to flash Magisk, i rebooted my phone in recovery mode and after that i flashed Magisk, but after that my ROM was destroyed and i didnt even had a backup (yes i know i should have done that, but i totally forgot about it). I said ok, the phone was released almost a year ago and there should be a Stock or Custom ROM online, i did find a couple of them but everytime i tried to flash them i was getting an error, i found the problem, my TWRP was a 32bit version and i changed that to a 64bit, but no other ROM except Lineage 15.1 was working. After flashing Lineage Os I found out that my fingerprint sensor wasn't working, my flashlight too and the camera was awful. I went back online and tried to find a stock ROM but i couldn't find anything, i tried a stock 7.1.1 and stock 8.0 but none of them was working. The last thing that i did was trying to flash it with ADB and after that my phone was working for 10 min until i got a security update that after the installation my phone didnt even boot again, i cant boot it, it isnt showing anything, no vibration, no sound, nothing Please help!
Hi everyone,
this is crazy. I followed different guides on how to root my phone but I get the idea I really have to wait for 7 days to have another chance at rooting, or is this just a myth?
I installed twrp, flashed resurrection remix. I had problems with my camera when trying to record video. I always got green flickering on screen. also not able to record more than 60fps (why? isn't s9 supposed to?).
But what struck me most was the fact that my phone wasn't rooted. When installing supersu in the recovery I get the message "sepolicy failed" or something. I guess this is why I cannot root my phone? Installing superuser from the playstore shows me also that I am indeed not rooted.
What can I do? I am all out of ideas and websites...
Should I reflash stock and do the OEM and odin procedure again, and wait 7 days?
Nairozed said:
Hi everyone,
this is crazy. I followed different guides on how to root my phone but I get the idea I really have to wait for 7 days to have another chance at rooting, or is this just a myth?
I installed twrp, flashed resurrection remix. I had problems with my camera when trying to record video. I always got green flickering on screen. also not able to record more than 60fps (why? isn't s9 supposed to?).
But what struck me most was the fact that my phone wasn't rooted. When installing supersu in the recovery I get the message "sepolicy failed" or something. I guess this is why I cannot root my phone? Installing superuser from the playstore shows me also that I am indeed not rooted.
What can I do? I am all out of ideas and websites...
Should I reflash stock and do the OEM and odin procedure again, and wait 7 days?
Click to expand...
Click to collapse
Try use magisk 16.6 for root issues, ofc when you use custom rom you dont get full camera potential and these green flickers are just minor cosmic bugs.
"Myth" might want to read up more.
You need to flash twrp and flash the no verity file then flash the custom rom
Or even better, flash soldiers rom instead of the resurrection remix. Didnt you read that theres a camera problem?
Better use magisk for rooting btw, use the 16.6
Now I am in a never ending boot sequence loading resurrection remix. I can only hard reset and enter twrp.
I don't know if the installation or magisk did it, because I cannot boot to the system.
anyideas?
Nairozed said:
Now I am in a never ending boot sequence loading resurrection remix. I can only hard reset and enter twrp.
I don't know if the installation or magisk did it, because I cannot boot to the system.
anyideas?
Click to expand...
Click to collapse
try flash rom + gapps and boot system after that boot recovery and flash magisk 16.6 and boot system
Thanks for the advice. I flashed back to stock firmware to have the zerocam mod working perfectly. But now my lockscreen freezes after a few minutes. So I tried to deactivate my phone going into lockscreen. I get the Black screen of Death now instead when the display turns off into sleep mode. Only way out is rebootingby hard reset, power button+volume down.
What can I do?.... Thanks for Any further advice.