Hi guys, this morning I decided to root ny tablet. I flashed CWM custom recovery and then installed universal android root zip file through the recovery. My goal was to unlock the full potential of Lucky Patcher by having unlocked Root permissions. I succeeded in installing the zip file, and everything was perfect. Unfortunately after custom patching Google play with LP, it kept crashing on startup. So (my bad) I decided to revert to factory settings. By doing this I'm now stuck in this never ending bootloop. I tried reinstalling .zip file through the use of ADB sideload, but when I exit that menu to reboot the device after having installed the .zip the device boots in CWM recovery mode. I really need your help as I'M very new to these type of things. Thand you
Back to stock ROM and start all over again
Related
I have no idea what I'm doing wrong here. Started with a completely stock/unbranded phone, EasyRoot v8 and backup TA, unlocked the bootloader through Sony, installed the .108 unbranded UK FTF, verified that bootloader was still unlocked, EasyRoot v8 again and installed dual recovery 132 and managed to have it boot into TWRP on that first instance and installed SuperSu 2.01...and I haven't been able to get into recovery since. I've tried through an Xposed power menu mod, through the NDR Utilities bundled with the dual recovery, and through ADB - and they all just go through the standard boot process instead, never giving me the purple light either. I tried re-flashing the dual recovery as well, no dice.
I haven't tried a custom kernel other than DoomKernel, which gets the phone stuck at boot (seems incompatible with .108); I don't want to deal with re-flashing the FTF and setting my phone up all over again if the kernel fails to boot again.
And another issue I'm having - I can't get access to /system to do stuff like remove/replace system apps. Everything root that involves system-related stuff seems to install fine and doesn't throw errors, but any file explorer I've tried isn't able to do anything with system files.
Is this something to do with the .108 update, or am I doing something wrong? I've searched and read all over and can't seem to find what I'm doing wrong.
EDIT: And I just tried installing AdAway hosts and wasn't able to. Interesting how I have root like half-working...
Had my Tab S 8.4 wifi (t700) rooted and working but decided I didn't like the custom rom I was on so went back to stock.
Now I can't seem to get TWRP working properly. Everytime I try to use it to install a rom or make a backup the tab reboots but only into stock recovery which then throws up E: Footer errors when I try to use it.
Anyone seen this before and have a solution? I am currently stuck on stock
hefilump said:
Had my Tab S 8.4 wifi (t700) rooted and working but decided I didn't like the custom rom I was on so went back to stock.
Now I can't seem to get TWRP working properly. Everytime I try to use it to install a rom or make a backup the tab reboots but only into stock recovery which then throws up E: Footer errors when I try to use it.
Anyone seen this before and have a solution? I am currently stuck on stock
Click to expand...
Click to collapse
You will see E: Footer errors at stock recovery mode because stock recovery allows only samsung signed archive to sideload.
Or did you mean something different with E: Footer? You sentence is inaccurate.
For stock recovery image, I prepared a patched[/] stock recovery image, which will allow unsigned archives to sideload.
I was actually trying to find out why TWRP recovery is no longer available on my tablet. It was working but since loading a stock rom I no longer get the TWRP recovery only the stock one.
I have tried lots of combinations to try and get TWRP recovery working but nothing appears to work - I just get stock recovery.
I am using:
T700XXU1ANF9_T700BTU1ANG1_BTU stock rom
CF_AutoRoot_Port_T700_BeansTown106.tar.md5 to get root access with Super SU
TWRP 2.7
TWRP Manager from Play store with the recommended Busy Box installed
I am sure I am missing something but cannot see what it is - I obviously got it right before as I had it working but I have missed a step somewhere.
Try using Flashify from the playstore and flash the TWRP .img or .zip
The "dd" method is the most flawless method if your familiar with using terminal
http://teamw.in/project/twrp2/238
Nexus 5 via Tapatalk
Finally got things working. It would appear that it is all about the sequence you do things in.
1. Use odin to load stock rom
2. Set up tablet and let everything download and update
3. Use odin to get root
4. Ensure that root is working and up to date
5. Use odin to add TWRP
6. Install TWRP manager from play store
7. Install Busybox from play store and run installation in busybox
If you deviate from this sequence TWRP does not appear to work in recovery. Have now made successful backup and can start playing with custom roms again.
Thanks for all the advice.
Not to much excitement I hope. Limited to a couple Roms
Nexus 5 via Tapatalk
Just FYI twrp IS recovery, when u restore to stock twrp is overwritten by the stock recovery. Twrp is not overwritten when you flash custom roms because recovery is not packaged in the zip file. But remember stock firmwares overwrite your recovery. Also please remember not to take ota's if you are using a custom recovery like twrp
I have a Pixel C, rooted using the Nexus Rootkit, TWRP and SuperSU.
All was fine and was on build N2G48C.
I had an OTA notification for Oreo, so I downloaded the OPR6.170623.010 Oreo OTA file, and used FlashFire to apply this.
Now everytime it reboots it goes past the Google logo, then to the "waiting for fastboot command" screen. I've tried rebooting to Recovery and I get the same thing!
Google didn't seem to help, so please can anyone else help?
I was manually flashing rather then using flashfire, but I was getting the same problem. First, flash just the stock room (no root or TWRP) and check that it boots. Mine would, but every time I tried to flash TWRP, it would bootloop to fastboot.
You may want to download the full rom, not just the ota. You can modify the flash batch file to not wipe the tablet, or just flash the components.
What was finally successful for me was to flash TWRP and NOT let it finalize. It should ask if you want to mount R/W so it can keep the rom from overwriting the recovery. I told it no, then flashed the Magisk zip for root. I haven't tested SuperSU, but just replace it here to try. This got me a proper boot to Oreo, with Magisk working correctly.
If I understand it right, and I haven't booted to recovery to check, the rom will likely have overwritten TWRP. Worst case, I have to reflash recovery whenever I want to do a backup or update my rom, but that isn't something I do often on this tablet.
Backgrond: Fresh new device. I unlocked bootloader through the all in one toolbox here (http://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711) to unlock bootlaoder successfully and install twrp ( I chose this version TWRP 3.2.1 Blu Spark OP5T).
I unlock my bootloader successfully and then tried to install superSU through twrp. I realized at the time of TWRP installation, that I didnt have SUPERsu on my device so I booted up my phone, downloaded Super SU from (http://www.supersu.com/download) and then went back into recovery mode. I was able to install the file through twrp but now I'm stuck on the OnePlus Screen.
On the toolkit screen there was a message saying
"if you flash a modified recovery and you dont root your stock rom (or flash another rom) you will brick you phone.
Is that what I did? Should I flash a custom rom?
I can access fastboot, recovery, etc and use adb sideload. I thought maybe I installed the wrong super user file so I flashed a new one through adb sideload (this file SR5-SuperSU-v2.82-SR5-20171001224502) but that didnt do anything either.
What should I do?
Hey guys,
Hope someone can help me or point me in the right direction, I am having serious issues trying to root my 1952-1.
I followed the guide in this post to install TWRP
https://forum.xda-developers.com/g7-play/how-to/how-to-successfully-install-twrp-g7-play-t3979701
I followed all the guidelines but when i tried rebooting to recovery I ended up in having TWRP splash screen bootlooping, but was still able to fastboot boot twrp.
I then flashed Magisk, it completed and then i booted the phone back up, no magisk was in the app drawer. So i installed the Magisk Manager apk and this told me I was not rooted. Repeated the whole thing and still the same result.
I have also tried patching the boot.img file using magisk but same as before the phone is not rooted, on top of this I have also clean flashed the stock rom but again still not rooted.
Anyone got any ideas ?
Yeah the rooting process can be a little bit frustrating. You will have to copy the original boot.img file to your phone. In the magisk app make sure you enable recovery mode. Then you can patch the boot.img file. Copy it back to your computer and flash it via fastboot. But there is a catch. The phone will be rooted only if you boot the phone through recovery.