I am caught in a bootloop after attempting to root using the following process.
Using Odin3 v3.10.6, I flashed the following:
n915t-cwm-recovery-6.0.5.1(1128).tar - THIS MAY HAVE BEEN AN ERROR. SHOULD I HAVE USED "openrecovery-twrp-2.8.1.1-trltetmo.img.tar"
I did a full backup to my phone's external SD card from cwm-recovery-6.0.5.1.
I then flashed both the files below without rebooting in between. I did not wipe any cache or data.
Emotion-TW-nightly-r23-RC1-SM-N915T
UPDATE-SuperSU-v2.46
The phone locked when I rebooted and would not move past the first black screen.
I pulled the battery and rebooted to recovery.
I did a restore of my backup that appeared to complete successfully.
I got a message asking to root the phone. I said yes, then rebooted.
Now stuck in a bootloop.
Hoping I can recover from this?
Root only with extra Kernel
When recovery asks to install root at the end, hit no. Thats your issue. You already installed supersu, so you've already got root. Personally I prefer stock kernel, with the latest beta supersu, you can still get root. With Universal init.d app, you can still get init.d support. With a custom build of xposed for Samsung lollipop, you can still get xposed. There's even a special version of viper audio. So yeah all you lose is the overclock ability.
Thank you. I ended up reflashing the firmware and got it working again. I'm still in the same situation, without root. My goal is to install a custom rom but I'm concerned about trying The Root process again. I read that a security patch was done in November for lollipop. Could that have impacted my ability to root and cause me to get into a boot loop? Wondering if there is a more current root method than the one I used.
rootnooby said:
Thank you. I ended up reflashing the firmware and got it working again. I'm still in the same situation, without root. My goal is to install a custom rom but I'm concerned about trying The Root process again. I read that a security patch was done in November for lollipop. Could that have impacted my ability to root and cause me to get into a boot loop? Wondering if there is a more current root method than the one I used.
Click to expand...
Click to collapse
There have been reports that the emotion r23 kernel is finicky, some work soem dont. Try another kernel or older version. That could be toir problem.
Sent from my SM-N915T using Tapatalk
Related
Hello
I have a problem with my Mate. I will try and list the things i did to get to this problem and I hope the information helps solve it.
I wanted to install xposed (first thing I did wrong) so I rooted using King Root (ver 4.8.2) successfully
then unlocked the bootloader using Huawei website
Using Flashy, I flashed TWRP recovery to install xposed (regrets).
After creating back up on TWRP, I tried to flash xposed, didnt work.
I gave up and rebooted phone to android, and i saw i had lost Nav buttons and Notification bar.
Booted back into TWRP and tried to restore my backup. It kept failing at 33% (would post logs but I lost them), I then thought a factory reset would help and it did.
I got the navigation and notification bar, but I soon realised I cannot install apps. I couldn’t install from my SD (apk’s) or from the Play Store.
I can’t install anything on it now. I’ve learnt my lesson not to mess with the inner workings of my device but now I am stuck with EMUI (no Nova or other 3rd party launcher).
Is there any way I can get it back to installing apps as usual? I saw another thread with similar problem (can’t install apps) but I wasn’t sure if I should post there (its old and unattended thread). If I should post this in another thread please point me in the right direction and thank you in advance.
:crying:
I would clear cache and Dalvik cache in recovery then flash back to a stock kitkat recovery, put the correct stock complete kitkat ROM in the dload folder in SD card and do a force update from stock recovery. Once it runs properly again, update to the right ROM you want to run, in the correct order of updates, make sure bootloader is unlocked, root the correct way (not kingroot, use ADB) then seek guidance on what mods work with what ROM. Do not try to root without unlocked bootloader! That ruined it I think.
If you want Xposed, it only partially works in Kitkat, not at all in Lollipop. What do you need with Xposed? I'm running B331 Lollipop now, no Xposed and no real need for it. I do have unlocked bootloader, root and Viper4android and it runs great. I use Smart Launcher Pro but kept Huawei Home (launcher) and theming apps installed so the system is happy but it looks how I want and is good to use.
Thanks for your quick response RobboW, will try that method and let you know if I make any improvement to my situation.
So I have to get a stock KitKat recovery and stock KitKat ROM for that recovery. Do I force an update from TWRP or what? I'll read up on recovering stock Roms and let you know if I make any progress. Thank you for the response though.
Force update with a stock ROM needs to be done from stock recovery. TWRP stops the phone from updating the stock way. The bootloader can stay unlocked if it already is.
It worked exactly like you said. I'm back on Lollipop B324. I can install apps and got the motion control settings back.
Thank you so much RobboW!
You're welcome
OS faults are not so bad if you have access to recovery. It's the ones that make using recovery and ADB difficult that cause the big dramas.
Hi guys, in the last days I had lost my root after the annoying security patch that have affected many of us.
Re-rooting with CF Auto Root seems to be ineffective for devices that have lost the stock boot image backup, as explained by Chainfire here: https://plus.google.com/+Chainfire/posts/XMFgencRR11
In theory, fixing root is as simple as flashing the new SuperSU v2.74 BETA ZIP file in TWRP, or using the updated CF-Auto-Root for your device.
In practice, this will not work for a fair share of users. To re-systemless-root using SuperSU ZIP's or CF-Auto-Root, if you have already been rooted, requires the stock boot image to be restored. Both methods create a backup of the stock boot image before applying root. During testing of this fix however, it became clear that a lot more users than I had expected managed to somehow lose this backup (clearing cache, factory reset, etc).
If this backup is no longer on your device, neither flashing the SuperSU ZIP nor re-applying CF-Auto-Root will fix the issue, as both installations will fail.
Click to expand...
Click to collapse
There is a solution here but before that I want to be sure that the stock boot image isn't on my device.
I have only carried two factory reset before rooting with CF Auto Root and never after so in theory I still have the backup of the stock boot image maked from CF Auto Root during my first root on my phone, is that correct or have I misunderstood?
Can I use the latest CF Auto Root (BETA-SuperSU-v2.74) with Odin like in my first root in order to try that or I could have problems?
Thank you very much for your help, I'm pretty new in the Android world and my english is not so good...
Hello.
I have a Pixel with stock Android that was rooted with Chainfire SuperSU 2.78SR3
Last night I've noticed that the phone isn't rooted anymore and has installed the Feb security update OTA. (I only had the Nov update installed).
I've tried rerooting using the same method (Fastboot boot) and got stuck in a bootloop.
I had to flash a clean stock rom to get it out of the bootloop.
Next I installed TWRP. That worked.
Next I tried installing a ZIP version of SuperSU 2.78SR4. The Zip installs but when I boot into Android SuperSU says that the phone isn't rooted.
Anyone had anything similar happen to them?
Borrisl said:
Hello.
I have a Pixel with stock Android that was rooted with Chainfire SuperSU 2.78SR3
Last night I've noticed that the phone isn't rooted anymore and has installed the Feb security update OTA. (I only had the Nov update installed).
I've tried rerooting using the same method (Fastboot boot) and got stuck in a bootloop.
I had to flash a clean stock rom to get it out of the bootloop.
Next I installed TWRP. That worked.
Next I tried installing a ZIP version of SuperSU 2.78SR4. The Zip installs but when I boot into Android SuperSU says that the phone isn't rooted.
Anyone had anything similar happen to them?
Click to expand...
Click to collapse
You might need to flash back to stock to fix this. If you do let us know so we can help you save your data and apps.
You used the wrong SU. You need 2.79 SR3. Note the 9 on there, you used 2.78.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Copy it to your phone and boot to TWRP. Then INSTALL it from TWRP.
Hello, I currently have a G920T that had been working alright for quite some time. The problem is that yesterday while using it normally, it suddenly froze. Thought it was the app, but saw it was the phone itself. Thus, I decide to turn it on again. When I do that, the phone does not continue after the logo and has the LED light white, while blinking on an off. When I manage to enter the Android Recovery menu it gives me the error shown in the title. The phone's rooted and was unlocked, so I could use it with AT&T.
I attempted doing a full reset, upgraded it to Nougat, and I am still stuck. Any help's appreciated in advanced.
Would like to say, when I installed the official Nougat Upgrade for my phone, upon starting, it began installing some things and then preceded to start Deleting. Afterwards, it just froze again. Did I do something wrong?
To get past this issue you have to Root with SuperSU, this will patch the Kernel to disable DM-Verity and will allow you to boot normally.
If you don't want to get rooted then reflash stock firmware via odin. never do OTA updates as i have always say the come "Dirty"
EDIT: Sorry didn't read you were rooted, just re-root again with SuperSU (To get your Kernel patched again) for DM-Verity
Starnel said:
To get past this issue you have to Root with SuperSU, this will patch the Kernel to disable DM-Verity and will allow you to boot normally.
If you don't want to get rooted then reflash stock firmware via odin. never do OTA updates as i have always say the come "Dirty"
EDIT: Sorry didn't read you were rooted, just re-root again with SuperSU (To get your Kernel patched again) for DM-Verity
Click to expand...
Click to collapse
So I use (what I previously used) cf-autoroot again? I ask this, since it seems their website have the recovery for marshmallow version and not for nougat (if I am not able to downgrade to 6).
Junito72 said:
So I use (what I previously used) cf-autoroot again? I ask this, since it seems their website have the recovery for marshmallow version and not for nougat (if I am not able to downgrade to 6).
Click to expand...
Click to collapse
Root with TWRP and superSU zip, i don't recommend CF-AutoRoot
Before flashing the Zip do the following on a Terminal in TWRP
Mount o- bind /dev/urandom /dev/random
Junito72 said:
So I use (what I previously used) cf-autoroot again? I ask this, since it seems their website have the recovery for marshmallow version and not for nougat (if I am not able to downgrade to 6).
Click to expand...
Click to collapse
You can use CF-AutoRoot for 6.0.1 and 7.0.
forumber2 said:
You can use CF-AutoRoot for 6.0.1 and 7.0.
Click to expand...
Click to collapse
When I use CF-Autoroot and attempt to boot it into recovery I get the following message, "recovery is not seandroid enforcing".
So I'd take I try installing a custom ROM first before attempting to start it in recovery?
Junito72 said:
When I use CF-Autoroot and attempt to boot it into recovery I get the following message, "recovery is not seandroid enforcing".
So I'd take I try installing a custom ROM first before attempting to start it in recovery?
Click to expand...
Click to collapse
Oh, that means CF-AutoRoot has not updated to work on 6.0 & 7.0 bootloader for G920T (It is updated and working on 6.0.1 & 7.0 for G920F)
Flash the stock ROM again. After that, flash TWRP and than flash latest SuperSU zip via TWRP.
forumber2 said:
Oh, that means CF-AutoRoot has not updated to work on 6.0 & 7.0 bootloader for G920T (It is updated and working on 6.0.1 & 7.0 for G920F)
Flash the stock ROM again. After that, flash TWRP and than flash latest SuperSU zip via TWRP.
Click to expand...
Click to collapse
I tried doing that, but wouldn't get past the main ROM's screen. I tried a custom ROM then (I think nemesis or such) and lasted longer, but again froze and loops with the white LED light on.
Any suggestions?
This is the first phone where I don't plan to install a custom ROM, and I don't know how OTA updates work while rooted.
Can they still be downloaded/installed normally while rooted? If so do I need to re-apply root each update? Does updating while rooted, or reapplying root afterwords wipe apps/settings?
I'm not sure if these are questions that can even be answered now, before anything has shipped, but worth a shot.
I might be wrong but I believe once you root you have to side load any OTA updates that come along and you may have to reroot and no this won't wipe ur phone
Flash Fire will be the way to go....
On rooted 2016 pixel never got flashfire to work for an ota. As for sideloading, that didn't work either. Had to download latest full image and use minimal adb to flash the full image. That can be done without wiping the phone and the detailed instructions are on XDA. I wonder if the pixel2 will be rootable by the same method to root the 2016 pixel. If I trade in for the pixel2 I will try it.
me_droid said:
On rooted 2016 pixel never got flashfire to work for an ota. As for sideloading, that didn't work either. Had to download latest full image and use minimal adb to flash the full image. That can be done without wiping the phone and the detailed instructions are on XDA. I wonder if the pixel2 will be rootable by the same method to root the 2016 pixel. If I trade in for the pixel2 I will try it.
Click to expand...
Click to collapse
I started with full image and removing the w.
Then Google started releasing OTA So I used flashfire and it worked fine.
I tried sideloading and it worked also.
During the whole period, I never lost root or hotspot accept for the last update I lost hotspot because of an update changing Carrier entitlement. So I had to go about modding system file but. My hats off to developers. I suggest everyone donates to the people who make things available.
Thanks,
There is a tutorial for using Magisk Manager with OTA Updates and A/B partition. I hope this will work with Pixel 2?
github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
FSMcas said:
There is a tutorial for using Magisk Manager with OTA Updates and A/B partition. I hope this will work with Pixel 2?
github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Click to expand...
Click to collapse
Nice tutorial. Is there a way to install magisk any easier if I don't care about OTA's? Can't I just flash magisk and carry on or do I still have to worry about the A/B partitions?
I did this and now I'm stuck in a bootloop!
FSMcas said:
There is a tutorial for using Magisk Manager with OTA Updates and A/B partition. I hope this will work with Pixel 2?
github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Click to expand...
Click to collapse
I followed this procedure and everything seemed to be fine until reboot. At first it would attempt to boot, get to the screen with the G logo, and then after a few seconds reboot again, showing the unlocked bootloader warning screen. i interrupted the loop with the power button, and now I get to the G logo with the small grey animated progress bar going back and forth, but it hangs there and never completes booting..