Related
I am running JB Codenamedroid 3.3.2 on my Nexus S4g when I flash the newer version 3.4.1 and on system reboot, it updates all the apps and then instead of starting it shows updating apps and goes to restart into that loop..I have tried just updating the rom and not gapps with the same problem. I have removed a lot of my apps and tried and get the same problem.. I have to pull the battery and do a nandroid restore. Any help is appreciated
Try doing a fresh install with ROM and gapps
bmuseed said:
I am running JB Codenamedroid 3.3.2 on my Nexus S4g when I flash the newer version 3.4.1 and on system reboot, it updates all the apps and then instead of starting it shows updating apps and goes to restart into that loop..I have tried just updating the rom and not gapps with the same problem. I have removed a lot of my apps and tried and get the same problem.. I have to pull the battery and do a nandroid restore. Any help is appreciated
Click to expand...
Click to collapse
there are many changes so i suggest you titanium backup everything and then wipe/factory reset, then flash the rom without flashing kernels and other add-ons. then after the first boot, flash the kernels and gapps, and then restore all your apps via titanium.
Billchen0014 said:
there are many changes so i suggest you titanium backup everything and then wipe/factory reset, then flash the rom without flashing kernels and other add-ons. then after the first boot, flash the kernels and gapps, and then restore all your apps via titanium.
Click to expand...
Click to collapse
100 % Agreed,..:good:
Thats wok for me, and should be work for you either.
<DELETED>
I just updated from an old cm 10.2 unofficial build from sometime in september to the latest nightly of cm 10.2. I used the update feature in cm to get the latest nightly and install it. I am running twrp recovery and wipe data cache and delvik after flashing then reboot. this all works fine and the rom boots up and starts re installing my apps. however after I reboot the device it just sits at the tab boot logo and I end up having to wipe data again to boot up and start all over. how can I fix this? I am just not having the best of luck with roms these days. Soon I want to update to kitkat but I am having trouble with that as well. (see other thread)
Edit: it's now having the same issue with my restored backup of my previous rom. Basically my backup is now doing the exact same thing where it just freezes up at the galaxy tab logo after first reboot.
mikee286 said:
I just updated from an old cm 10.2 unofficial build from sometime in september to the latest nightly of cm 10.2. I used the update feature in cm to get the latest nightly and install it. I am running twrp recovery and wipe data cache and delvik after flashing then reboot. this all works fine and the rom boots up and starts re installing my apps. however after I reboot the device it just sits at the tab boot logo and I end up having to wipe data again to boot up and start all over. how can I fix this? I am just not having the best of luck with roms these days. Soon I want to update to kitkat but I am having trouble with that as well. (see other thread)
Edit: it's now having the same issue with my restored backup of my previous rom. Basically my backup is now doing the exact same thing where it just freezes up at the galaxy tab logo after first reboot.
Click to expand...
Click to collapse
Maybe it´s a problem with your emmc. We have a MAG2GA type with a known bug called "MAG2GA TRIM bug" and like i know cm 10.2 runs the trim command once a day. There is a possible patch for this problem, but i think it´s not merged to our device.
Please can you check the emmc memory with the tool eMMC Brickbug Check from Market?
I have encountered a strange problem. Please help.
1. I was running CM12 nightly (April 10 build). I also have TWRP backups of Apr 8 image and my old CM11S (44R) image.
2. I downloaded OxygenOS to try it out. Booted the phone into TWRP and tried flashing the ZIP.
3. Got an error while flashing the ZIP.
4. Rebooted the phone into recovery and tried restoring the Apr 10 image.
5. Restore says it is successful.
6. On reboot, the phone stays on the "Powered by Android" screen. It does not boot up into the ROM image. It boots up into recovery instead.
7. I tried the same process with Apr 8 image and the same issue.
8. Finally, I restored the backup image of CM11S and that works well.
Can someone please advise how can I get my backup ROMs to work?
I have now tried backing up ROMs for Cyanogen CMOS12 as well as Oxygen. None of the restores are working. I am backing up all partitions. Where am I going wrong? The restore does not give any error, but the boot is stuck at the logo. When I restore CMOS12, it gets stuck on the screen that says "Cyanogen". When I restore Oxygen, it gets stuck at the boot animation of Oxygen.
I am using TWRP 2.8.6 for restore and Online nandroid manager for backing up.
Is it possible that OnlineNandroid manager uses a different version of recovery for backup?
Please help.
.
I'm new to the CM 12 stuff but I thought I read that TWRP had an issue with compression during a certain range of weeklies, and due to that, would/could not restore from that range.
I think I also read to make sure you have the most up to date TWRP, and a weekly after 4/22, or so. I don't recall the exact date of the compressed weeklies causing the issue,but I think the compression problem began in April, sometime. Hopefully someone will come by and further clarify or identify your issue.
What version of TWRP do you have and what's the date of your weekly?
JeffDC said:
I'm new to the CM 12 stuff but I thought I read that TWRP had an issue with compression during a certain range of weeklies, and due to that, would/could not restore from that range.
I think I also read to make sure you have the most up to date TWRP, and a weekly after 4/22, or so. I don't recall the exact date of the compressed weeklies causing the issue,but I think the compression problem began in April, sometime. Hopefully someone will come by and further clarify or identify your issue.
What version of TWRP do you have and what's the date of your weekly?
Click to expand...
Click to collapse
I am using TWRP 2.8.6. I have tried restoring Oxygen, CM12, CM12S backups and none of them are working. Restore takes reasonable time and says it was successful.
indoliya said:
I am using TWRP 2.8.6. I have tried restoring Oxygen, CM12, CM12S backups and none of them are working. Restore takes reasonable time and says it was successful.
Click to expand...
Click to collapse
see if this link has any relationship to your general issue
https://forums.oneplus.net/threads/...cm12-1-nightlies.300277/page-78#post-11010591
read around a bit as some folks seem to have had the same issue as you, there is also an xda topic for the nightlies, as well which may be a good place to search
indoliya said:
I am using TWRP 2.8.6. I have tried restoring Oxygen, CM12, CM12S backups and none of them are working. Restore takes reasonable time and says it was successful.
Click to expand...
Click to collapse
Did you wiped cacha/Dalvik? I personnaly do these wipes before and after flashing/restoring.
If I were you, I'd try to flash the latest cm12 nightly "on" you restore, maybe it could help..
You might have to flash the right firmware for the CM 12/11 you want to restore. TWRP doesn't backup firmware by default, only ROM/Data. So flash the right formware for the ROM you want to restore and then restore your nandroid.
real_sl4cker said:
You might have to flash the right firmware for the CM 12/11 you want to restore. TWRP doesn't backup firmware by default, only ROM/Data. So flash the right formware for the ROM you want to restore and then restore your nandroid.
Click to expand...
Click to collapse
Thank you! Previously, I was switching between CM11 and CM12 without any problem. Are you sure about this?
indoliya said:
Thank you! Previously, I was switching between CM11 and CM12 without any problem. Are you sure about this?
Click to expand...
Click to collapse
Not sure as in "Yes, that's the way to go, do it!" but it's worth a try. I haven't switched back to CM11 from CM12 (updated to CM12 just yesterday) up to now.
What I'm pretty sure about is that TWRP (by default) only backs up system and data, no modem and stuff. And CM11 and CM12 come with different firmware. Flashing the right firmware for your build won't do any harm anyway
real_sl4cker said:
Not sure as in "Yes, that's the way to go, do it!" but it's worth a try. I haven't switched back to CM11 from CM12 (updated to CM12 just yesterday) up to now.
What I'm pretty sure about is that TWRP (by default) only backs up system and data, no modem and stuff. And CM11 and CM12 come with different firmware. Flashing the right firmware for your build won't do any harm anyway
Click to expand...
Click to collapse
Finally resolved this by going to Online Nandroid app and changed the shell to default and busybox to default. Now the backups taken with these settings are getting restored successfully.
Magisk 17 (Stable) was just released. I am uninstalled 16 via the official uninstall. I then rebooted to TWRP and flashed 17. The phone kept going back to recovery. I uninstalled and reinstalled 16 and I'm back up. Anyone else get 17 to work on the latest OOS?
same here, can not get it to work
I downloaded it, then flashed it in twrp, but i never uninstalled the older version, I just flashed over the older one. Mine booted up fine,
I'm on OOS 5.1.11
Updated from 16.7 beta to 17.0 via Magisk Manager (direct installation).
Everything worked fine, except the warning pop-up on boot that was also on 16.7.
I was on Magisk 16.4. After installed v17, root was broken. I had to uninstall it and redo V16.4.
I wound up having to wipe data. Now 17 seems to be OK. Time will tell.
Even after running the uninstaller and reinstalling 16, after about 5 minutes running fine, the system would just randomly reboot.
Be prepared if you install 17, you may have to wipe data
Mike02z said:
I wound up having to wipe data. Now 17 seems to be OK. Time will tell.
Even after running the uninstaller and reinstalling 16, after about 5 minutes running fine, the system would just randomly reboot.
Be prepared if you install 17, you may have to wipe data
Click to expand...
Click to collapse
How come you uninstalled magisk before reinstalling the newer version? Is that normal, i always flash over the older version without uninstalling the older version & reinstalling the newer version & never had any problems.
I'm running xxx module with ex kernel, i downloaded the update zip, flashed in twrp & rebooted, everything worked but i did get that boot internal storage message, so reflashed ex kernel & the message was gone. I'm not sure, maybe it was cause you uninstalled your older version of magisk that messed things up, or maybe it's that i had ex kernel already installed that helped me not have any problems.
Rebel7022 said:
How come you uninstalled magisk before reinstalling the newer version? Is that normal, i always flash over the older version without uninstalling the older version & reinstalling the newer version & never had any problems.
I'm running xxx module with ex kernel, i downloaded the update zip, flashed in twrp & rebooted, everything worked but i did get that boot internal storage message, so reflashed ex kernel & the message was gone. I'm not sure, maybe it was cause you uninstalled your older version of magisk that messed things up, or maybe it's that i had ex kernel already installed that helped me not have any problems.
Click to expand...
Click to collapse
I tried flashing right over 16.0. It just kept dumping me back into TWRP.
Rebel7022 said:
How come you uninstalled magisk before reinstalling the newer version? Is that normal, i always flash over the older version without uninstalling the older version & reinstalling the newer version & never had any problems.
I'm running xxx module with ex kernel, i downloaded the update zip, flashed in twrp & rebooted, everything worked but i did get that boot internal storage message, so reflashed ex kernel & the message was gone. I'm not sure, maybe it was cause you uninstalled your older version of magisk that messed things up, or maybe it's that i had ex kernel already installed that helped me not have any problems.
Click to expand...
Click to collapse
I did that. That is always the way I update it as well. It just booting back into TWRP.
1N1ghth4wk said:
Everything worked fine, except the warning pop-up on boot that was also on 16.7.
Click to expand...
Click to collapse
In Magisk Manager select Uninstall -> Restore images -> Flag the option "Preserve AVB 2.0/dm-verity" -> install -> direct install -> reboot.
Warning pop-up should not appear anymore
Mike02z said:
I tried flashing right over 16.0. It just kept dumping me back into TWRP.
Click to expand...
Click to collapse
Flash a kernel, I like ex kernel , It probably will fix it
I just let the Magisk app update itself and direct install the update and reboot. I always do that, works fine.
Sent from my ONEPLUS A6003 using Tapatalk
brossovitch said:
I just let the Magisk app update itself and direct install the update and reboot. I always do that, works fine.
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
Same for me, and everything works fine with the latest version.
I am on H2 os ob 02, Magisk 16.7.
I got message to update Magisk aplication. I did, then, message to update to Magisk 17.
Everything works fine.
I just let it update the Magisk Manager and now i'm without root (no idea how i ended like this i swear i just updated the Manager) and the Manager doesn't have the ability to install Magisk directly, just download zip only or patch boot image. Guess i'm up to reinstall TWRP and flash the Magisk zip manually, right?
Flashed Directly over 16.7 (H2os beta 2) without wipe or issues :good:
Happened to me too I got stuck in bootloop to twrp didnt need to wipe data. I used flash all partitions fastboot.bat from https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 to get back to normal without losing data. I had to reinstall twrp and magisk though. Now I'm on magisk 17.0 all fine.
So I do it just let it update the Magisk Manager. CustomRom AospExtended ROM V5.8
And running
Also got stuck in a bootloop after installing 17 over 16. Using the uninstaller fixed the issue, and when I re-tried installing 17 in TWRP it worked fine.
Installed 16.4 yesterday and it would not pass Safety Check, got the notification to install 17 which I did via the app
Installed without a hitch and Safety Check all passed with no issues
I have a Shield Tablet K1 running LineageOS 14.1 9/1 update(very nice) and cannot get TiBU to run keeps crapping out "Titanium Backup has stopped". Not sure why i did it but i deleted SuperSU.
Tried flashing Supersu (UPDATE-SuperSU-v2.82-20170528234214) from TWRP and it installs correctly but still no supersu app. Tried flashing again after wiping caches no help.
Also which version of the supersu should we flash the 32 or 64 bit?
Ultimately trying to get TiBu running again to restore and app & data. Also cannot get Helium to work stuck in "Checking Superuser".
I have been able to verify that i have root via TWRP and FX File explore.
Thanks for the help in advance.
You can download and install the SuperSU application and run it. Go into the settings and select "install SuperSU as a system app". That should do it. You can also switch to magisk which works just as well.
Dirty flash Lineage and start over (flash SuperSU again). Things can get a little quirky when trying to re-flash root to a device that is already rooted. Try Magisk for that matter. It tends to give less problems than SuperSU. I migrated to Magisk a year or so ago, an haven't looked back.
I went ahead and reflashed everything and started from scratch. Working correctly now.
Thanks for the replies!