Hi, this is My first post here, so be gentle.
My old Oneplus died and I bought a used Samsung Galaxy S9. I tested the phone with an original OS and it worked fine.
Yesterday I decided to root it (there are a few features that need root and I need those features almost daily). I searched for information about the procedure (this wasn't My first root) and found a few threads where this guide was suggested:
How to Root Samsung Galaxy S9 and Galaxy S9 Plus (Exynos)
Do you want to root your Galaxy S9/S9 Plus flagship? Well, you just landed in the right place for the job. This tutorial will help you install TWRP recovery and root Samsung Galaxy S9 and Galaxy S9…
www.thecustomdroid.com
Long story short: I followed those instructions and managed to root my S9. It booted up as it should and everything was working fine. I used Magisk V25.0 and root checker informed that the phone was rooted successfully.
Today I decided to debloat it and after that, I would start to use it as my main phone.
I ran across many threads that suggested using the "ADB + Fastboot" method for debloading the device. At this point, I started to feel uncomfortable because I had some issues with ADB back in the day when I was rooting my Oneplus. I decided to try it and guess what - it didn't work. I still don't know why, but ADB fastboot wasn't able to find my S9. I double-check that everything was as it should be, usb-debugging was ON and my PC did see my phone when connected to the PC via USB cable.
So I gave up on that and decided that maybe I'll just shut those unwanted apps down from the phone's settings (settings ---> apps etc).
At this point, I power off the phone. Just a basic thing to me when sleeping or something like that.
Now, the phone is in bootloop.
I can boot in the TRWP mode and flash magisk/wipe data etc. but nothing seems to help. It won't boot to OS. I've tried to root it again with the instructions above and everything went fine, but bootloop stays. I've wiped cache partition and performed a factory reset - did not help.
Can someone help me...? Is there a way to flash stock OS or somehow get the device work again? My experience with rooting is low, but I've successfully rooted five phones before this. I've experienced a few bootloops before, but those were my mistakes that were fixed with re-flashing magisk or something similar. Now I simply don't know what is the issue. =(
PS. This is a great forum and I've found tons of help from the XDA forum. Thank you to everyone, who has shared his/her information and helped with smartphones in the past! Great society.
Slerba said:
Hi, this is My first post here, so be gentle.
My old Oneplus died and I bought a used Samsung Galaxy S9. I tested the phone with an original OS and it worked fine.
Yesterday I decided to root it (there are a few features that need root and I need those features almost daily). I searched for information about the procedure (this wasn't My first root) and found a few threads where this guide was suggested:
How to Root Samsung Galaxy S9 and Galaxy S9 Plus (Exynos)
Do you want to root your Galaxy S9/S9 Plus flagship? Well, you just landed in the right place for the job. This tutorial will help you install TWRP recovery and root Samsung Galaxy S9 and Galaxy S9…
www.thecustomdroid.com
Long story short: I followed those instructions and managed to root my S9. It booted up as it should and everything was working fine. I used Magisk V25.0 and root checker informed that the phone was rooted successfully.
Today I decided to debloat it and after that, I would start to use it as my main phone.
I ran across many threads that suggested using the "ADB + Fastboot" method for debloading the device. At this point, I started to feel uncomfortable because I had some issues with ADB back in the day when I was rooting my Oneplus. I decided to try it and guess what - it didn't work. I still don't know why, but ADB fastboot wasn't able to find my S9. I double-check that everything was as it should be, usb-debugging was ON and my PC did see my phone when connected to the PC via USB cable.
So I gave up on that and decided that maybe I'll just shut those unwanted apps down from the phone's settings (settings ---> apps etc).
At this point, I power off the phone. Just a basic thing to me when sleeping or something like that.
Now, the phone is in bootloop.
I can boot in the TRWP mode and flash magisk/wipe data etc. but nothing seems to help. It won't boot to OS. I've tried to root it again with the instructions above and everything went fine, but bootloop stays. I've wiped cache partition and performed a factory reset - did not help.
Can someone help me...? Is there a way to flash stock OS or somehow get the device work again? My experience with rooting is low, but I've successfully rooted five phones before this. I've experienced a few bootloops before, but those were my mistakes that were fixed with re-flashing magisk or something similar. Now I simply don't know what is the issue. =(
PS. This is a great forum and I've found tons of help from the XDA forum. Thank you to everyone, who has shared his/her information and helped with smartphones in the past! Great society.
Click to expand...
Click to collapse
I manage to solve this all by my self.
I flashed to stock firmware using frija and odin. After flashing updated all the apps and rebooted couple of times (just to be sure that phone works). After that flashed TWRP with odin, rebooted to recovery and rooted with Magisk (followed step-by-step guide fron xda forum).
Now this works like a dream.
Related
After tinkering with my Androids over the years, (Infuse, Captivate, G2, and now G3) I have finally decided to become a member of the forum that I primarily use as a source of information and links to downloads. I'd like to first say thank you to all those that have unknowingly help me over the years with my roots. Great place you've got here.
Now the fun part, after two days of ownership, I have experienced the first issue was not able to resolve on my own, what appears to be a hard brick. I downloaded Flashify after my initial root, installed TWRP Manager, ran the patch for writing to the SDcard, and installed TWRP Recovery from AutoRec. All appeared to go well and it said the instal was successful. I followed the instructions I found online that had great results for my particular model and version 5.0.1. Well, when I went to boot into recovery to make my initial backup, the phone shut down and would not come back up. No response at all. It wont power up by any method, tried letting the capacitors drain, still no go. After tinkering with it for a few hours (I've owned this phone for a total of 2 days now), I finally came to the conclusion that it would need JTAG and the original boot image flashed over the one that I mucked up.
Any ideas on where I made my mistake? I'm near 100% certain I downloaded the proper files for my phone model.
Also forgot to mention, I have not changed anything else on the phone. Only installed apps and root browsers I planned on using. So stock kernel, stock ROM, nothing until I started getting ready to make myself a save point, ironic really!
jamguitarist said:
After tinkering with my Androids over the years, (Infuse, Captivate, G2, and now G3) I have finally decided to become a member of the forum that I primarily use as a source of information and links to downloads. I'd like to first say thank you to all those that have unknowingly help me over the years with my roots. Great place you've got here.
Now the fun part, after two days of ownership, I have experienced the first issue was not able to resolve on my own, what appears to be a hard brick. I downloaded Flashify after my initial root, installed TWRP Manager, ran the patch for writing to the SDcard, and installed TWRP Recovery from AutoRec. All appeared to go well and it said the instal was successful. I followed the instructions I found online that had great results for my particular model and version 5.0.1. Well, when I went to boot into recovery to make my initial backup, the phone shut down and would not come back up. No response at all. It wont power up by any method, tried letting the capacitors drain, still no go. After tinkering with it for a few hours (I've owned this phone for a total of 2 days now), I finally came to the conclusion that it would need JTAG and the original boot image flashed over the one that I mucked up.
Any ideas on where I made my mistake? I'm near 100% certain I downloaded the proper files for my phone model.
Also forgot to mention, I have not changed anything else on the phone. Only installed apps and root browsers I planned on using. So stock kernel, stock ROM, nothing until I started getting ready to make myself a save point, ironic really!
Click to expand...
Click to collapse
Post the guide that you followed
You would have to kick your phone into Qualcomm USB Loader 9008 in order to fix it
http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-all-variants/
Hey guys!
I followed the android guy on youtube, showing how we could easily root any (almost) device with Kingroot
I've had already did it with my Samsung Galaxy S4 Active and even thought I never found the way to replace kingroot by supersu... it worked.
Then I wanted to do the same with my SGTab Pro 10.1 and actually it also worked but after 5 minutes (after reboot) i think i have seen that the system was updating (but I didn't accept any request) and now there is no way to make it work!
I've tried to remove kingroot (maybe it was because of the root) but the tab doesn't stay turned on long enough to do this (last time a I checked it still there anyway)
Then i've tried a factory reset wipe and everything and now it's always rebooting, saying" Process system isn't responding" do i want to wait or no? The only other message i have seen (during the reset) was "Android is urgrading)
Now it's dead... Do you think you could help? This is the model,SM-T520/ Kitkat 4.4.2 (if my memory is okay)
I don't find any answer, all I can understand about reading others is that it's bricked... thank you for your help!
Sylvie
This solved my problem with being stuck in a boot loop. I went on a deep search of things and stumbled on this post. worked like a charm. read down to reply #10 and that is where the magic will happen.
http://forum.xda-developers.com/galaxy-tab-pro-12-10-8/help/help-softbricked-sm-t520-t2805605
Hi folks,
I'm after some information. My Nexus 4 is about kaput now with the battery lasting about 4 hours or so with a full charge so I am looking to move over to my S4 mini for a while before buying an upgrade.
However i don't fancy rolling back to 4.4.2 from 5.1.1 as have got accustomed to it now. so there for I am looking to upgrade/flash it or whatever.
I am quite the novice and have not done this on any phone before so I am looking for a bit of help,
I have looked over xda and read some bits but think someone just telling me would be better, i'm not a tech dunce but I am not 100% confident in this at the moment as there seems to be more than one way of doing this.
What do i need to do first and foremost to make the process go as planned?
I take it I need to "root" the phone first (what does this do ? give me access to the firmware level? is that it?) using a "recovery tool" as they are called (is that right?)
Then after I have done that I can install a fresh ROM onto the phone and basic app's etc.
I have seen these guides:
http://forum.xda-developers.com/showthread.php?t=2364980
and
http://forum.xda-developers.com/gal...i9190-i9195-cyanogenmod-13-0-s4-mini-t3276141
Is it just a matter of following them or are there other things I need to do first, in between or after?
I am not bothered about anything being saved on the s4 mini it can be wiped clean and start a fresh, I don't need any of my data on it backed up
A quick bullet guide or acknowledgement of the two threads above or pointing me towards some better ones would be great and any pointers or descriptions of the acronyms or places in menu's which may have had their names changed or have been moved.
Many thanks Everyone,
Dahools
Hi!, you dont need to worry about anything, the only thing that you need is follow these guides, but make sure if you have the correct variant.
First Install Kies and connect your phone to it( For correct phone drivers). And after phone connect wells, Close kies from task manager.
You Need Odin to install a recovery software in your phone(TWRP, Clock Recovery, Philip). I only used twrp now.
Here is link below with instruction. Download recovery for your variant(i9190,i9192 or i9195 base on your model).
http://forum.xda-developers.com/showthread.php?t=2678420
Suppose if you install TWRP. Boot into recovery, And click Wipe, Do a factory reset , Clear Devil cache, Then go back and install your Firmware(cm12.1 or cm13 for your intended model). And flash Gapps as well. Then reboot. And you are done.
I have tried TWRP for both i9190 and i9192 model. and installed custom roms. Work fine.
Good Luck.
thanks fellas
I went for it with the original links and it worked. (eventually) A bit of user error on my part missing recovery mode on reboot first time and thinking it was done when it wasn't. Only putting the first bit in (root kit v2) then not realising how to flash the next parts. A bit of persistence paid off.
I have a I9195 model and rooting with that clockwork worked then loading the CM13 and then the Gapps. All one after the other in one go finally worked for me! so so far so good, just getting used to Android 6 now I think everything is working though, not put my sim in yet. will do that tomorrow.
If anyone was to follow what I did the big tip I would say is copy everything onto the SD card before you start anything, not as I did at first just putting the first bit on then thinking I can copy the next bit on later . . .
Hey guys,
I've had this phone for a while; bootloader unlock/rooted a few months ago without any issues. I'm looking to sell the phone, and wanted to restore everything back to stock:
So I ODIN'd to stock CPF3. I noticed that the phone was suspiciously laggy, and found out that it's caused by spyware left behind by KingRoot, and is fixable by clearing the EFS folder from root.
So I went back to BPA1, unlcocked BL/rooted, and deleted everything from the efs folder. After reboot, phone was running good as new without any hitches.
The issue arised when I tried to ODIN flash the CPF3 full firmware provided by hsbadr. ODIN would go fine, but when the phone would reboot into the recovery, I'd get a dead Android bot saying "DRK is not installed. Please install DRK" or something along those lines. I ignored it, and the phone booted with no issues.
When I tried to factory reset from within the OS, however, I'd face the DRK and dm-verity verification failure when the phone would boot into the recovery, and it would'nt continue with the factory reset.
Now alarmed, I backed down to BPA1, and when the phone would boot back into recovery after a successful ODIN flash, the process would restart the phone when the progress bar would hit ~1/3 of completion (this happens in the recovery).
Rebooting into the recovery would show an orange "dm-verity failed," and when I try to OTA to CPD1 via external sd, It gives the "cannot update from external sd" error.
Googling the DRK keyword showed that it is KNOX being tripped that caused the issue. So far, neither Google nor the xda-forums have showed how to fix the issue on the 910-V.
I really want to restore the phone to as close-to-factory as possible, and removing this DRK issue would be a great help. Any help is greatly appreciated.
Edit #1: I have tried both this guide and this one to absolutely no avail. What am I missing? DM-Verity refuses to go away
EDIT #2: My brother also has a 910-v, and he hasn't cleared his EFS folder (stupid me for not making a back-up, eh?). Is it safe to clear mine again, and copy-paste his EFS folder into my phone? What are some adjustments I should make to avoid a corrupted IMEI? Any help is appreciated.
EDIT#3: I've tried this method, and it removes DM-verity on the first boot. It returns after factory reset. Currently trying a few different combos of flashing kernels/recoveries etc. to see if I can get it to stick. Permanently. Is it still OK to get by bro's EFS folder?
dm-verity and lagginess
HELP!!!!!!
It is annoying to see the dm-verity failed. The phone works fine but its just at the recovery boot. I am not sure what to do. I have a Galaxy S7 on Verizon. I rooted my phone using ODIN. I unrooted it already and it did not work. I did the Verizon recovery and it did not work either. However, I am not able to access to the recovery menu in my phone. I am rooted and the phone is working fine. It is just slow and it has some glitches on some apps like Snapchat... The video is so laggy it is not even funny. I am not sure if that has anything to do with the dm-verity but I need this 3 issues fixed ASAP. I will forever be grateful. I used my friends S7 that is not rooted and it was SO FAST! I am not sure if the root has anything to do with the lagginess but I doubt it because I have read here in XDA that root actually makes your phone faster.
1) Remove and fix the dm-verity
2) Fix laggy snapchat
3) Laggy phone overall.
My phone is Galaxy S7 on Verizon. SM-G930V
notsonerd said:
HELP!!!!!!
It is annoying to see the dm-verity failed. The phone works fine but its just at the recovery boot. I am not sure what to do. I have a Galaxy S7 on Verizon. I rooted my phone using ODIN. I unrooted it already and it did not work. I did the Verizon recovery and it did not work either. However, I am not able to access to the recovery menu in my phone. I am rooted and the phone is working fine. It is just slow and it has some glitches on some apps like Snapchat... The video is so laggy it is not even funny. I am not sure if that has anything to do with the dm-verity but I need this 3 issues fixed ASAP. I will forever be grateful. I used my friends S7 that is not rooted and it was SO FAST! I am not sure if the root has anything to do with the lagginess but I doubt it because I have read here in XDA that root actually makes your phone faster.
1) Remove and fix the dm-verity
2) Fix laggy snapchat
3) Laggy phone overall.
My phone is Galaxy S7 on Verizon. SM-G930V
Click to expand...
Click to collapse
You might want to go to the verizon S7 forums for that. These are the 910-V forums. Sorry for not being able to help.
Look for how to ODIN flash full stock recovery/firmware in the S7 forums. That is all I can say.
SirLaughsalot said:
You might want to go to the verizon S7 forums for that. These are the 910-V forums. Sorry for not being able to help.
Look for how to ODIN flash full stock recovery/firmware in the S7 forums. That is all I can say.
Click to expand...
Click to collapse
I have a vzw note 4 and I'm getting the dm verity verification failed when I try to a factory reset...been at this for a week so I'm pleading for help.
I posted on dr.cools attempt to fix this before I saw this post. sorry for double posting.
edit--I'm attempting the OP's number 3. will report back. Downloading BOG5 because that's what my version shows on the phonw
Question--Right now I'm stuck at BOG5. Do I need to do anything special to get to PA1 so I can start the root/unlock process again?
edit--just flashed firmware and modem and was able to do a factory reset...now back to rooting and bootloader unlock, hopefully.
Okay, so I'm having a real b**** of a time getting root or even TWRP on my Moto G Fast (Boost mobile) and I really don't understand what it is I'm doing wrong. I've carefully gone through pretty much every thread available on XDA (and basically everywhere else) pertaining to getting root/TWRP on this device and from what I've gathered its been a pretty simple process for most other people with this device but for some reason nothing has worked for me. I should also note that my phone has had the most recent OTA update, which I was led to believe would make things easier but apparently not lol. So far the only thing that's gone off without a single hitch was unlocking the bootloader. Beyond that nothing I've tried has seen much success.
I was able to flash TWRP and get it to boot a couple times, but only from the fastbootd menu and even when I was able to boot TWRP and attempt flashing Magisk it failed every time (far to quickly for me to even read the red text in the log) and would immediately reboot TWRP, taking me back to the recovery lock screen. I'm also not used to having two different bootloaders on a phone so I'm still not quite sure which one I'm supposed to use for flashing (although fastbootd has so far been the only one I've achieved any success with) and the stock recovery has been a dead end at least 50% of the time I was able to get to it (I just get the dead Andy with the "no command" dialog and the hard buttons do nothing) So I eventually gave up flashing the Magisk zip and decided to try patching the boot.img instead. I used fastboot to flash the patched img to both the boot_a and boot_b partition, which seemed to work at first, until I realized I had no mobile signal and my touch screen was unresponsive. I just spent the last hour or so unbricking it with Lenovo's Rescue & Smart Assistant. I've read plenty of threads where these same exact issues happened to others but I've yet to find any kind of effective work-around or an explanation as to why its happening.
Even when I was able to get TWRP to boot it never seemed to survive a reboot. I'd have to flash it again every time in order to get into it. It's also been quite a while since I've rooted a phone so I'm still pretty new to treble enabled devices and their surplus of confusing partitions, a few of which I wasn't even able to mount/unmount in TWRP, which was a bug I thought was fixed a while ago, but to my knowledge I have the most recent version and I'm still getting these same bugs
Basically at this point I'm at a loss for ideas so any and all advice or suggestions would be much appreciated. I apologize if this post just sounds like a long winded complaint or I didn't provide enough info for anyone to work with (I'm running late for work and I'm mentally exhausted lol) but hopefully someone on here can provide me with some answers. I'll try to post more specific info and maybe some logs after work but until then godspeed.
AMShiech said:
Okay, so I'm having a real b**** of a time getting root or even TWRP on my Moto G Fast (Boost mobile) and I really don't understand what it is I'm doing wrong. I've carefully gone through pretty much every thread available on XDA (and basically everywhere else) pertaining to getting root/TWRP on this device and from what I've gathered its been a pretty simple process for most other people with this device but for some reason nothing has worked for me. I should also note that my phone has had the most recent OTA update, which I was led to believe would make things easier but apparently not lol. So far the only thing that's gone off without a single hitch was unlocking the bootloader. Beyond that nothing I've tried has seen much success.
I was able to flash TWRP and get it to boot a couple times, but only from the fastbootd menu and even when I was able to boot TWRP and attempt flashing Magisk it failed every time (far to quickly for me to even read the red text in the log) and would immediately reboot TWRP, taking me back to the recovery lock screen. I'm also not used to having two different bootloaders on a phone so I'm still not quite sure which one I'm supposed to use for flashing (although fastbootd has so far been the only one I've achieved any success with) and the stock recovery has been a dead end at least 50% of the time I was able to get to it (I just get the dead Andy with the "no command" dialog and the hard buttons do nothing) So I eventually gave up flashing the Magisk zip and decided to try patching the boot.img instead. I used fastboot to flash the patched img to both the boot_a and boot_b partition, which seemed to work at first, until I realized I had no mobile signal and my touch screen was unresponsive. I just spent the last hour or so unbricking it with Lenovo's Rescue & Smart Assistant. I've read plenty of threads where these same exact issues happened to others but I've yet to find any kind of effective work-around or an explanation as to why its happening.
Even when I was able to get TWRP to boot it never seemed to survive a reboot. I'd have to flash it again every time in order to get into it. It's also been quite a while since I've rooted a phone so I'm still pretty new to treble enabled devices and their surplus of confusing partitions, a few of which I wasn't even able to mount/unmount in TWRP, which was a bug I thought was fixed a while ago, but to my knowledge I have the most recent version and I'm still getting these same bugs
Basically at this point I'm at a loss for ideas so any and all advice or suggestions would be much appreciated. I apologize if this post just sounds like a long winded complaint or I didn't provide enough info for anyone to work with (I'm running late for work and I'm mentally exhausted lol) but hopefully someone on here can provide me with some answers. I'll try to post more specific info and maybe some logs after work but until then godspeed.
Click to expand...
Click to collapse
You saw my thread
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
sd_shadow said:
You saw my thread
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Click to expand...
Click to collapse
Yeah I tried following exactly that procedure and it bricked.
Dude. I have this phone. Same Carrier.
I know, it can be a pain in the ass. I've been on medical leave for 3 years though and needed a project to work on so I've been coming up with my own methodologies to fix this process...
Like, I've got a script that should de-brick your phone back to stock no matter what, and then we can move forward.
Are you on discord? This is going to be a bit too slow. I can just create us a channel or something though.
Lanlost said:
Dude. I have this phone. Same Carrier.
I know, it can be a pain in the ass. I've been on medical leave for 3 years though and needed a project to work on so I've been coming up with my own methodologies to fix this process...
Like, I've got a script that should de-brick your phone back to stock no matter what, and then we can move forward.
Are you on discord? This is going to be a bit too slow. I can just create us a channel or something though.
Click to expand...
Click to collapse
I appreciate the reply man, and sorry for the late response (I only get one day off a week), but I fortunately got it figured out finally. My main issue was that this is the first A/B treble enabled phone I've ever tinkered with, and most everything I read claimed I had to boot to fastbootd in order to flash twrp but that never seemed to work.
My computer would recognize the phone as a fastboot device while in fastbootd but that's about it. Everytime I tried to flash in fastbootd the output either claimed there was 'no such file' or it appeared to work, but when I tried booting to recovery I still got stock recovery. I was finally able to get TWRP to stick by just booting it initially from the normal bootloader and using TWRP to flash itself to the recovery partition.
Then I was able to install magisk in TWRP by formatting data and flashing v21 instead of the latest version (Everytime I tried flashing v22 from TWRP it failed). Then after booting system, going through setup, and installing magisk manager I found Id successfully achieved root and was able to update to magisk v22 via MM without bricking.
After all that trouble I'm a little nervous to try a custom ROM cuz stock with root is basically perfect so far. Now the only thing I'm struggling with is figuring out how to set selinux to permissive so I can install BusyBox to xbin.