Got a N7 2012 runing 5.1 - finally got fed up with it being so slow as almost unuseable so decided to install CM12 ... and am stuck in a boot loop.
I followed the instructions I found (I cant post the link) so I've listed them below:
Deploy ROM image
adb devices
adb push YOURROMZIP.zip /sdcard/
adb reboot bootloader
fastboot devices
fastboot oem unlock
cd Download
#or whenever you have downloaded files
fastboot flash recovery your_recovery_image.img
Choose Recovery
Now use your volume buttons to change selected item from the Menu and pick "Recovery mode"*and select it with Power button.
Right now ClockworkMod recovery should start!
Now with the same buttons navigate in recovery and select:
1. backup and restore
2. wipe data/factory reset
3. install zip from sdcard
4. choose zip from sdcard (you should find it in folder named "0", not in the root of sdcard!)
5. reboot system now
Cyanogen Mod should be installed!
did a full wipe at fastboot oem unlock .. then realised i'd have to re-push the ROM as I don't have an sdcard ... so I did that.
Managed to flash TWERP onto it (rather than CW) and got it to boot into Recovery Mode but ... the Recovery Mode and Restart Bootloader are in RED and don't do anything when I tap them.
When I try to power off and back on it gets stuck in the boot loop...
Google screen show with a padlock at the bottom, goes away and then shows up again
Teamwin logo shows up
says 'Running OpenRecovery script'
things then happen too quicly for me to track but it seems there are a list of red error messages like:
E: unable to mount data and could not find crypt footer
I'm running Ubuntu 14.04 and the device doesnt appear i the list when I type
adb devices
fastboot devices
Can anyone tell me what to do to get CM12 on the m/c and working???
btw, managed to break out of the bootloop but it will just start again when turned off and on.
Thanks in advance.
From what you said, you're not in recovery mode. You're in bootloader mode.
In bootloader mode device doesn't support touchscreen, you need to use volume up/down and power to select option.
To get out of bootloop and go to recovery:
1. Power down your device (hold power for few seconds)
2. Boot into recovery mode (hold Volume Down + Power)
3. Navigate to recovery (Using Vol up/down and selecting option by pressing power button)
I am running the latest OOS 10.0.1 Stable on my OP6T
I installed the Riru-Core module from magisk manager, rebooted perfectly fine. Afterwards installed the EdXposed module. Now I am stuck in a bootloop. Is there a way to uninstall the module without having TWRP? or factory resetting.
edit: I am unable to boot into fastboot or recovery
Please help me out
Thank you
Press volume up + power button to force reboot then press volume down + power to get into stock recovery. Then you can boot to fastboot through stock recovery...
2 Options ,
1. Try flashing stock boot.img on fastboot to remove Root so EdExposed won't work. (Recommended)
Then you'll have the option to remove EdExposed modules.
2. msmdownloadtool , But it will REMOVE all your data and will put your phone on Android 9.
As far as I know OTA updates will not work if devices is rooted (Magisk/TWRP installed).
Very likely it checks unlock state of bootloader.
How to update? I wan't lose my data.
Firmware updates and keeping your data, for phones Magisk rooted without TWRP.
[Magisk] Root for the Galaxy S10 Series
Here comes official Magisk support for the Galaxy S10! Let's get Magisk to kick start the development of these Samsung devices! Link to Instructions Carefully read through everything in the page linked above! Follow the instructions closely so...
forum.xda-developers.com
Just download new firmware, copy the AP file of the new firmware to your phone.
Open Magisk Manager, ensure Magisk is up to date, if not, update it.
When Magisk is up to date, if you have any Magisk Modules running, go into Modules and disable them (no need to uninstall them). Then reboot and go back into Magisk Manager.
Hit the _top_ INSTALL, select INSTALL again then select 'Select and Patch a File'
Locate the new AP file from your new firmware and patch it. Then copy the *magisk_patched.tar* (find it in /sdcard/Download - do not forget to delete it here after everything is done; otherwise Magisk will choke on the next patch) back to your computer, preferably with adb pull to minimize corruption during transfer.
Power off phone and reboot to *Download mode* (switch off, Vol-Down + Bixby and plug USB cable).
Open Odin 3.13.1 or later on your computer, and deselect Reboot under Options tab.
Now use the new magisk_patched file in the AP slot, the BL and CP from your new firmware into their respective slots and importantly *HOME_CSC* into the CSC slot.
Press start and let Odin do it's stuff.
When flashed, do not wipe.
Press and hold Vol-down and Power, when screen goes off, quickly change to Vol-up, Bixby button and Power.
As soon as screen appears, let go of all buttons.
Within moments without any further user intervention your phone will reboot into your updated Magisk rooted mode, data intact.
Just re-enable your previously disabled Magisk modules.
Last edited by robbo1947; 2019-08-30 at 04:28.
Alle Bootvorgänge im Überblick, nach der Installation von Magisk:
(Normales Einschalten) → (System ohne Magisk)
(Power + Bixby + Volume Up) → (Bootloader-Warnung) → (Alle Tasten loslassen) → (System mit Magisk)
(Power + Bixby + Volume Up) → (Bootloader-Warnung) → (Haltet nur noch Volume Up) → (Aktuelles Recovery)
Hard Power Off
Volume down and Power/Lock keys on the device for about 10-20 seconds
then it reboots again into recovery menu
last edited by ew 2020-07-07
Be warned though: I had a severe soft brick when upgrading Android 10 to 11 on my S10e!
Half+ day (hard reset did not work, battery had to run out) to get out of the boot loop another two hours to get everything back up running with the help af my backup via restore function of TitaniumBackup.
Yesterday and the day before I had smooth sailing upgrading my S10e and Tablet S7+ using that method as I am used to it since two years.
EDIT: it just worked as expected in UPGRADING my T725 from Android 10 to 11!
Thanks for this. Will give it a go.
I went back to stock firmware from Lineage 18.1 cause I missed the Atmos DSP - couldn't quite get the same effect using JamesDSP - and the finger scanner didn't function.
Stock is mostly ok, but I do miss some root stuff like host file ad blocking and a few other things.
Currently on Stock 11 Rom
shaitan667 said:
I went back to stock firmware from Lineage 18.1 ..... and the finger scanner didn't function
Click to expand...
Click to collapse
The fingerprint sensor works in LOS?
OhioYJ said:
The fingerprint sensor works in LOS?
Click to expand...
Click to collapse
Wasn't for me
shaitan667 said:
Wasn't for me
Click to expand...
Click to collapse
It should, that's something else going on. I use it to unlock / wake my tablet all the time never an issue.
It may have just been an old rom.
I can't go back to LIneage though - the Atmos DSP is just too good.
DHGE said:
Firmware updates and keeping your data, for phones Magisk rooted without TWRP.
[Magisk] Root for the Galaxy S10 Series
Here comes official Magisk support for the Galaxy S10! Let's get Magisk to kick start the development of these Samsung devices! Link to Instructions Carefully read through everything in the page linked above! Follow the instructions closely so...
forum.xda-developers.com
Just download new firmware, copy the AP file of the new firmware to your phone.
Open Magisk Manager, ensure Magisk is up to date, if not, update it.
When Magisk is up to date, if you have any Magisk Modules running, go into Modules and disable them (no need to uninstall them). Then reboot and go back into Magisk Manager.
Hit the _top_ INSTALL, select INSTALL again then select 'Select and Patch a File'
Locate the new AP file from your new firmware and patch it. Then copy the *magisk_patched.tar* (find it in /sdcard/Download - do not forget to delete it here after everything is done; otherwise Magisk will choke on the next patch) back to your computer, preferably with adb pull to minimize corruption during transfer.
Power off phone and reboot to *Download mode* (switch off, Vol-Down + Bixby and plug USB cable).
Open Odin 3.13.1 or later on your computer, and deselect Reboot under Options tab.
Now use the new magisk_patched file in the AP slot, the BL and CP from your new firmware into their respective slots and importantly *HOME_CSC* into the CSC slot.
Press start and let Odin do it's stuff.
When flashed, do not wipe.
Press and hold Vol-down and Power, when screen goes off, quickly change to Vol-up, Bixby button and Power.
As soon as screen appears, let go of all buttons.
Within moments without any further user intervention your phone will reboot into your updated Magisk rooted mode, data intact.
Just re-enable your previously disabled Magisk modules.
Last edited by robbo1947; 2019-08-30 at 04:28.
Alle Bootvorgänge im Überblick, nach der Installation von Magisk:
(Normales Einschalten) → (System ohne Magisk)
(Power + Bixby + Volume Up) → (Bootloader-Warnung) → (Alle Tasten loslassen) → (System mit Magisk)
(Power + Bixby + Volume Up) → (Bootloader-Warnung) → (Haltet nur noch Volume Up) → (Aktuelles Recovery)
Hard Power Off
Volume down and Power/Lock keys on the device for about 10-20 seconds
then it reboots again into recovery menu
last edited by ew 2020-07-07
Be warned though: I had a severe soft brick when upgrading Android 10 to 11 on my S10e!
Half+ day (hard reset did not work, battery had to run out) to get out of the boot loop another two hours to get everything back up running with the help af my backup via restore function of TitaniumBackup.
Yesterday and the day before I had smooth sailing upgrading my S10e and Tablet S7+ using that method as I am used to it since two years.
EDIT: it just worked as expected in UPGRADING my T725 from Android 10 to 11!
Click to expand...
Click to collapse
I think I followed the instruction but there is no Bixby at S5e, right? After flashing the pathed AP I try to go to Recovery, but it doesn't seem to work. It just boots. If I keep Power+Vol+ pressed it loops ...
So something I do wrong.
Even if I do an adb reboot recovery it boots into Android ?!?
Edit:
I could get it managed by "adb restart recovery". Again I didn't see somewhat like recovery, but after that Magisk is shown to be installed. So it seems not of importance to reboot to recovery DIRECTLY after flashing patched AP, but before you actually want to get Magisk enabled.
Does someone know Vk_Wakelock ? That eats up my battery...
After that update I have problems. It seems that wifi can't find any nets. Looking to Wifi-Mac ... it is empty. Anyone has a tip for me?
Hello Everybody. I am trying to install magisk to my J5 (J510FN) for the past few days. I am writing down what i am doing. I did that procedure 5-10 times with no results. Please let me know
To start the phone was bricked and i downloaded a samsung firmware to install.
https://ava4.androidfilehost.com/dl/Sj1K2v_P2Tk05YLBFZTc9g/1634062127/1899786940962603729/J510FNXXS3BSH2_J510FNDBT3BSH2_DBT.zip?
Download ODIN
https://samsungodin.com/download/Odin3_v3.13.1.zip
I had the Samsung/framework drivers from previous phones.
Press Vol Down+ Home+ Power Buttons and i enter download mode. I select AP -> go to the official Samsung firmware on the PC and select it.
Connecting the USB and i see the added on odin. Press Start.
It taking a while and then See the green Pass. Disconnect the phone. The phone is booting. I follow the instruction. select Not send diagnostic data and no google account. The phone is on.
Then settings> About phone> Software information> Tap on build number until the developer modem is on.
Back to settings>developer options OEM UNLOCK on, Auto update system off, USB Debugging on and ok.
Turning off the phone.
https://eu.dl.twrp.me/j5xnlte/twrp-3.3.1-0-j5xnlte.img and downloading the twrp recovery
Press Vol Down+ Home+ Power Buttons to enter download mode. Select AP -> go to the twrp on the PC and select it.
Connecting the USB and i see the added on odin. Deselect Auto Reboot from the options menu on odin.
Press Start. Its taking a second. Unplugging the battery. Putting on the battery.
Press Volume UP Home+ Power Buttons enter recovery mode. I go to wipe and select only the cache. Go to reboot and select to system> Don't install twrp.
Phone is booting.
Downloading latest magisk from
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
https://ava2.androidfilehost.com/dl/UpyKzryZOrpj1yhppDX8kA/1634373961/8889791610682932422/RMM-State-Bypass-v3-corsicanu.zip?
extract the official firmware above and take the boot image.
Connecting the phone with usb. Drag and drop on the phone the 3 files above.
Install magisk (allow unknown sources). Open magisk. next to magisk select install, next, select and patch a file. In top right show internal storage. In the top left 3 lines then galaxy. select the boot.img. Patched succesfully. Turn off the phone.
Press Volume UP Home+ Power Buttons enter recovery mode. install > install image> select the magisk_patched-***_**. flashing succesfully
select
https://ava2.androidfilehost.com/dl/UpyKzryZOrpj1yhppDX8kA/1634373961/8889791610682932422/RMM-State-Bypass-v3-corsicanu.zip?
flashed succesfully. Reboot system.
Opening magisk installed N/A
Can anybody help?
edit: after downgrading the magisk it appears installed. When i upgrade to the latest version it shows again not installed. When i install a module from smalipatcher it stays in a bootloop.
does anyone use magisk on android beta 13?
MyRaVEi said:
does anyone use magisk on android beta 13?
Click to expand...
Click to collapse
I can't get magisk to work on android 13. after flashing the boot, I get a bootlap
I was able to fix it.
1) flash the stock boot and install the Magisk application (if removed)
2) press and hold the reset button, press "reboot to safe mode"
3) immediately press the power + volume down to get into fastut and prevent the phone from turning on
4) we get into fastubt
5) flash the patched magisk image, after that the phone should boot in safe mode
6) reboot the phone in normal mode
7) go to magisk and remove the "nothing mod" module
it was a surprise to me that even after deleting the Magisk application, the modules of the old modules cause a bootlap