Can nuts lollypop be installed on rooted lollypop without causing bootloop now.
Related
Tab s t705 singapore updated to hong kong lolipop 5.0.2.
Been using it for a month without problems till suddenly started freezing in certain situations.till now i think its isolated to charging!
Device rooted supersu/twrp.
Ive read about it on internet couldnt find aolution and happened to other tab s (800..700..etc) no solution found and some said linked to lollipop but ive used it a while before anything happened.
What i did and did NOT work.
1.with without sim/
2. Delete cashe/dalvik and wipe to factory
3, restore a previous backup twrp where the issue want there
4. Installed other rom ..blissrom
5.flashed seperal kernels and updated twrp to latest for tab s
6.using other charger
Can be hardware? What can go wrong? Maybe from a drop something happened?
It keeps freezing with wtever last on screen. Lockscreen/app opened/home screen..mostly on lockscreen as it seems to happen a while after starting charging.
Please help this problem is driving me crazy since i lose all my work when it happens and im on stock rooted lolipop rom
Anyone ??
No1
8.4 models have been known to have problems with the battery connector which causes issues. There is a video on YouTube for the fix.
i think its solved !
rolled back to stock 4.4.2 od3 that came with the tab s. rooted backup.
i dont know what app/update/root/kernel might cause it but seems it was actually from lollipop and confirmed now !
AND SEEMS TO WORK BACK NORMALLY NOW !
I doubt it's lollipop itself but more a rogue app if that is the case.
I would make a backup of your current system with flashfire then reinstall lollipop and see if it happens again.
If it does restore your flashfire backup.
As title says when I flash or install a recovered LG based rom the handset gets into a bootloop. Lollipop or MM doesn't matter.
I see the BIOS type of screen for a few seconds then 3 seconds of boot animation and back to BIOS.
Cyanogenmod 13 based roms work just fine.
background: After receiving MM ota update rooted and downgraded to lollipop. Installed a modem file in the process as well.
Then I decided that I don't like it either. FLashed cyanogenmod straightaway.
Then flashed genesys rom which is LG based 6.0.1.
Still no problems.
Installed xposed framework and the bootloops started.
Then I run the xposed uninstall script, wipe everything and install LG MM rom. bootloop again.
Sorry for the long post. Didn't know which detail is relevant so wrote it all
Any help would be much appreciated as I am stuck with cyanogen...
Try to go back to stock with lgup
lgup doesn't recognize the handset when CM is installed.
Anyway finally found a solution after trying every trick in the book. Basically flashing modem, boot and bootloader solved the problem.
Now I need to find a way to flash xposed framework without bricking the phone.
Hey guys,
im currently struggeling with hot reboots and bootloops on my G3 16G. The intervalls this happens ar getting closer and meanwhile the phone is barely usable.
This happened first on TWRP 2.8.7 and Fulmics 6.7. Then I changed the ROM to Fulmics 6.5, Fulmics 5.0 and cloudyG3. Getting the same results....
After that I went back to stock MM (v30b) and even did a TOT-flash (LGD855AT-V10e-EUR-16G).
Im still getting hot reboots and bootloops when Im trying to reboot. only thing that helps is a wipe... Then its ok for a few minutes.
Anyone experienced similar problems? Any solutions?
best,
ralf
Battery?????
UPDATE:
I gave up and installed the stock Samsung ROM. For any germans on "open" A3s: The Austrian open version of 7.0 works fine. Not network related or other issues for me.
Hu guys,
I installed TWRP, rooted and tried installing xposed installer from here.
After that I got stuck in bootloop. Tried formatting data and a factory reset various times now, but I always get stuck in bootloop again.
Any idea how I can fix my messing up?
Thanks!
timbohenry said:
UPDATE:
I gave up and installed the stock Samsung ROM. For any germans on "open" A3s: The Austrian open version of 7.0 works fine. Not network related or other issues for me.
Hu guys,
I installed TWRP, rooted and tried installing xposed installer from here.
After that I got stuck in bootloop. Tried formatting data and a factory reset various times now, but I always get stuck in bootloop again.
Any idea how I can fix my messing up?
Thanks!
Click to expand...
Click to collapse
Why do you install an Xposed version for L and M on N?
Anyway, you have to flash stock again since a factory reset does not repair damaged system partitions. I would use SmartSwitch for returning to the latest official firmware.
edisso10018 said:
Why do you install an Xposed version for L and M on N?
Anyway, you have to flash stock again since a factory reset does not repair damaged system partitions. I would use SmartSwitch for returning to the latest official firmware.
Click to expand...
Click to collapse
I only flashed 7 after being stuck in bootloops. Before that I was running 6 and installed Xposed for 6.
Any reason in pareticular for not running Austrian 7 in Germany? Seems to work just fine.
Thanks!
Your post was misleading... And no. If it works use it.
Hi all.
I have a Note 8 GT-N5110 that's still running Stock 4.4.2. It's rooted and has Xposed 2.6.1 installed along with some modules. Last night I flashed TWRP 3.0.2-0 with the intention of flashing Magisk, forgetting at the time that it only works on Lollipop and up. I did not do a backup (I know) and rebooted back to the Stock OS just fine. I updated some Xposed modules and rebooted. Then I added some new Xposed modules, updated AdAway and its host files, and rebooted.
Now I cannot boot past the Samsung logo screen no matter how long I wait. I've gone into TWRP and wiped Dvalik and Cache, which lets me boot past the Samsung logo and get to a screen that says "Android is upgrading, starting the apps." It's been sitting on this screen for about 1 hour, which makes me think I can't boot past it. Any ideas how to easily fix this? If I need a full refresh, can anyone point me to the US version of the Stock 4.4.2 ROM?
This may help: https://updato.com/firmware-archive-select-model?q=gt-n5110&exact=1