Hello guys,
a few days ago I dared to root my Xperia X10 Mini Pro with SuperOneClick and flashed a Cyanogenmod 7 Android 2.3.3 ROM. All in all, it worked pretty well.
After doing some apps installation stuff I rebooted in the Recovery (Clockworkmod which obviously came along with the ROM) and made a backup, just for the case. Afterwards, I selected "power off" in the CWM menu because I wanted to go to bed.
Then, immediately, CWM said something like "Error - This recovery seems to be bad" and something with a "risk". I managed however to power off. Can't remember if that worked via CWM or if I pushed the power off hardbutton or removed the battery.
Yet - the ROM seems to work. Now I'm a bit anxious because of the CWM error.
Is there really a risk? I planned to dare unlocking the bootloader soon. Is it dangerous to do this with a "bad recovery" or doesn't that matter at all?
Is there a possibility to repair CWM? Can I just install a new CWM? If yes - how?
Sorry - pretty noobish questions, I know.
Can you help me anyway?
Thanks a lot!
deleted post
Thank you for your help! I already thought that no one would answer because the thread disappered on page 3 of this forum
I've never heard from Odin before and therefore googled it. It only occured in connection with Samsung devices. Are you sure it is compatible to my Sony Ericsson?
Anyway, can I also install a new CWM via ROM Manager or wouldn't you recommend this?
Warning: I'm a noob. Take my advice at your own risk!
From what I understand, flashing CWM via Rom Manager is exactly the same as manual flashing (perhaps better, since the Rom Manager presumably keeps up to date). So I think you should be able to do so and make another recovery (without going through any of that manual flashing stuff). You should get a second opinion just because I'm so noobish, but I think this is the case.
However, from my limited understanding, I don't think the recovery will make any difference when dealing with the bootloader. The bootloader is, more or less, the very first set of instructions executed when the phone turns on. If you mess that up, your phone won't even be able to get into recovery mode. Also, the recovery images are stored on your sd card, which is wiped upon unlocking. Once again, I could be wrong.
deleted post
Dude, what are you talking about? You can't use ODIN on a non-Samsung phone.
trich025 said:
don't use rom manager just use the odin for your safety, you can bet that samsung users are the one benefiting on odin but as you can see erricson and samsung are both android phones and if you examine them both device have similar programs, and one thing, always keep in mind that you have to back up your current rom for emergency uses so you can still get back to were you started in case something went wrong.
if i helped you with this problem you could click the thanks button >>>>
Click to expand...
Click to collapse
OK now this is flat out wrong. Each Android device has a different program used. Samsung has Odin, HTC has an RUU. Not sure about SE. But never use a software made for one device on another unless you want a brick. Just because they both use android doesn't mean they are the same.
Thanks to everyone, especially Product F(RED)!
No offence, trich025, but I guess you were wrong.
Can I destroy something by re-installing or updating CWM via ROM-Manager just in case my CWM has a bug?
Hey guys, I'm having a pretty annoying issue with my Galaxy S3 (Verizon variant), and even though I'm pretty sure I know what the problem is, and that I screwed myself, I wanna know if there's another answer to what's going on.
As the title of this thing says, I tried installing Clockworkmod Recovery on my GS3, but I did it via the ROM Manager app, since I'd totally forgotten how to do it on my computer, and Odin 3.09 wouldn't use the .tar or .img files I tried using to install the damn thing (still haven't figured that out).
Anyway, I flashed the CWM file on the phone, installed it, and whenever I try booting into recovery, it says some unauthorized software is on the phone, and I need to take it to a Verizon store.
I'm pretty sure Verizon locked us out of our bootloader, and we need to unlock it before we can make mods like this, but, being that I haven't had a GS3 for two years, I didn't know that, and didn't look it up, like a n00b.
So, I think I just partially bricked my phone. So, yeah. That sucks.
Is there any way around this? Is there a way to revert back to the stock recovery mode, so I can try doing this whole thing again?
Some phone info:
It's the Verizon, I535 variant
Running 4.4.2, Kitkat
Build number: KOT49H.I535VRUDNE1
Any help would be appreciated.
Hi, thank you for using XDA Assist. The best place to look for answers and ask questions is in your device specific forum. Please see this,http://forum.xda-developers.com/verizon-lg-g3
Thread closed.
First of all, I'd like to say that I know very little about how Android, electronics or mobile phones work in general, so everything I've done has been from internet tutorials. Please don't use any jargon as I probably won't know what you mean. ELI5.
A few days ago, I tried to root my phone and it didn't work. As a result the phone went into a boot loop and I didn't know how to fix it. The long and short of it was that I ended up flashing the stock firmware onto my phone and basically doing a complete factory reset. After some time trying this I managed to get the phone to start up and I was able to access the interface and all that. Unfortunately, my WiFi wasn't working (the button would simply turn off whenever I turned it on) so I had no way to download the most recent updates or apps or anything like that. After following several tutorials on how to fix this, such as flashing the modems and bootloader, I still wasn't having any luck. So I tried something that proved to cause even more problems - I tried to install a new kernel. Now my phone won't even boot past the logo. I probably didn't install the right one, but what can I say, it's not very clear which one I need.
Now I'd like to point out that as a layman who just wants his phone to work again, half of the time I don't understand what I'm doing or whether or not I'm doing it right. In other words, I realise that I've probably messed up my phone, but what can I do? I can't take it to a technician because I don't have the money for that, I can't buy a new phone for the same reason and I can't phone up and ask for a replacement because the warranty expired ages ago and I don't have the original documents here.
I've installed the Team Win Recovery Project on my phone and I have Odin installed on my PC as well.
TLDR; yes, I know I'm an idiot and I don't appreciate you telling me. I'd like to reset my phone to how it was before - the normal firmware, the normal kernel and all that, but I'd still like to have root access and keep the TWRP recovery mode too.
Model: Samsung Galaxy S4 GT-I9505
Model name: GALAXY S4 LTE
Country: UK
Version: Android 5.0.1
You'll probably need more information, so if you do just let me know and, if possible, where I can find it.
I have some good news. I managed to flash the firmware again and now I can access the phone again. However, the WiFi problem persists. I've tried looking on the internet for a solution, but I can't find one. I've tried flashing the modem and all that stuff, but it still doesn't work.
Oh, and by the way, I no longer have TWRP and I don't think I have root access anymore either (I had to do a data partition wipe as well).
I'd really appreciate a reply from someone. I've tried everything, but to no avail.
einwaliser said:
First of all, I'd like to say that I know very little about how Android, electronics or mobile phones work in general, so everything I've done has been from internet tutorials. Please don't use any jargon as I probably won't know what you mean. ELI5.
A few days ago, I tried to root my phone and it didn't work. As a result the phone went into a boot loop and I didn't know how to fix it. The long and short of it was that I ended up flashing the stock firmware onto my phone and basically doing a complete factory reset. After some time trying this I managed to get the phone to start up and I was able to access the interface and all that. Unfortunately, my WiFi wasn't working (the button would simply turn off whenever I turned it on) so I had no way to download the most recent updates or apps or anything like that. After following several tutorials on how to fix this, such as flashing the modems and bootloader, I still wasn't having any luck. So I tried something that proved to cause even more problems - I tried to install a new kernel. Now my phone won't even boot past the logo. I probably didn't install the right one, but what can I say, it's not very clear which one I need.
Now I'd like to point out that as a layman who just wants his phone to work again, half of the time I don't understand what I'm doing or whether or not I'm doing it right. In other words, I realise that I've probably messed up my phone, but what can I do? I can't take it to a technician because I don't have the money for that, I can't buy a new phone for the same reason and I can't phone up and ask for a replacement because the warranty expired ages ago and I don't have the original documents here.
I've installed the Team Win Recovery Project on my phone and I have Odin installed on my PC as well.
TLDR; yes, I know I'm an idiot and I don't appreciate you telling me. I'd like to reset my phone to how it was before - the normal firmware, the normal kernel and all that, but I'd still like to have root access and keep the TWRP recovery mode too.
Model: Samsung Galaxy S4 GT-I9505
Model name: GALAXY S4 LTE
Country: UK
Version: Android 5.0.1
You'll probably need more information, so if you do just let me know and, if possible, where I can find it.
Click to expand...
Click to collapse
Hi
We have a dedicated help section for the S4, you'll need to start a new thread and ask there, providing as much info as you can:
http://forum.xda-developers.com/galaxy-s4/help
A [HELP THREAD] Galaxy S4 | Ask any question | Noob friendly thread is also available for you if you dont want to start a new thread.
Good luck.
engloa said:
Hi
We have a dedicated help section for the S4, you'll need to start a new thread and ask there, providing as much info as you can:
http://forum.xda-developers.com/galaxy-s4/help
A [HELP THREAD] Galaxy S4 | Ask any question | Noob friendly thread is also available for you if you dont want to start a new thread.
Good luck.
Click to expand...
Click to collapse
Hi engloa,
It's OK, I've fixed the problem now; I installed a different ROM and now it works fine. Thanks anyway though.
Hey first time posting on xda devs and would like to know how to unlock bootloader, root the phone, and install custom ROM.
Now I have spent entire day backing up and searching the different people root but if someone can help me and point me in the right direction that would be great.
So I have a S3 from ATT Model: SGH-I747, Version: 4.1.2 JellyBean, BaseBand Version: I747UCDMG2, Kernel: 3.0.31 - 1300972. It is a stock ROM, I have never done anything to the phone at all before.
Now I will admit I followed a youtube video call "How to Root AT&T Galaxy S3 SGH-I747!" by High on Android and I did everything in the video. I used odin v1.85, I did the PDA to the CWM.tar file, phone rebooted and I added the CWM superuser file and that is when I tried to get to CWM recovery mode and all I got was the phone's default recovery mode and not the CWM one.
From what I understand I believe I need to unlock bootloader first, but again this is a my first doing this and I hoping someone can point me in the right direction. Forum post state that you should follow guides that is exactly the same to the phone you would like to install custom ROMs.
Honestly I would like to ultimately be able to install a recovery mode that works with my phone that I am able to create snapshot image of my stock phone in case anything happens or I would like to go back to my stock image (which I highly doubt if everything goes fine) and install a custom ROM (I know there are different ROMs if someone can point me to where I can check out all the custom ROMs and not necessarily install those custom ROMs that would be awesome) and finally get rid of ATT loading screen when booting up the phone and install a custom boot loading screen, but of course I care more about getting the custom ROM install first.
If anyone can help that would be great.
Hi
Please use the below link to register a XDA Account first, prior to start posting and replying onto our forums.
Join the Experts
When you complete your registration, I would invite you to post your request in the below forum as our team mates there should be able to help you:
AT&T Galaxy S III Q&A, Help & Troubleshooting
Best regards and good luck.
.
XDA Visitor said:
Hey first time posting on xda devs and would like to know how to unlock bootloader, root the phone, and install custom ROM.
Now I have spent entire day backing up and searching the different people root but if someone can help me and point me in the right direction that would be great.
So I have a S3 from ATT Model: SGH-I747, Version: 4.1.2 JellyBean, BaseBand Version: I747UCDMG2, Kernel: 3.0.31 - 1300972. It is a stock ROM, I have never done anything to the phone at all before.
Now I will admit I followed a youtube video call "How to Root AT&T Galaxy S3 SGH-I747!" by High on Android and I did everything in the video. I used odin v1.85, I did the PDA to the CWM.tar file, phone rebooted and I added the CWM superuser file and that is when I tried to get to CWM recovery mode and all I got was the phone's default recovery mode and not the CWM one.
From what I understand I believe I need to unlock bootloader first, but again this is a my first doing this and I hoping someone can point me in the right direction. Forum post state that you should follow guides that is exactly the same to the phone you would like to install custom ROMs.
Honestly I would like to ultimately be able to install a recovery mode that works with my phone that I am able to create snapshot image of my stock phone in case anything happens or I would like to go back to my stock image (which I highly doubt if everything goes fine) and install a custom ROM (I know there are different ROMs if someone can point me to where I can check out all the custom ROMs and not necessarily install those custom ROMs that would be awesome) and finally get rid of ATT loading screen when booting up the phone and install a custom boot loading screen, but of course I care more about getting the custom ROM install first.
If anyone can help that would be great.
Click to expand...
Click to collapse
Hello guys. I just bought a used Samsung Galaxy J5 (SM-J500FN) with android version 5.1.1. The previous owner told me that it is rooted. Nothing seems weird with the phone other than when i try to factory reset it it takes me to a "bios" kind window where i have to manually choose to delete all data (hard delete i think its called), that and when i normally turn on the phone, at the top left corner it says "set warranty bit kernel". I was just wondering how do i go about installing custom roms since its already rooted, and can i unblock the default carriers (T-mobile) block for other sim cards. When asked how he rooted it (what method was he using) he said he just used Odin. I dont know much about rooting so, whatever you can tell me as to the handling of the phone would be amazing. Any other guides to installing some custom roms and making the phone easier and faster ( i only want functionality, don't care much about the UI) would be greatly appreciated. Thanks in advance.
luan96 said:
Hello guys. I just bought a used Samsung Galaxy J5 (SM-J500FN) with android version 5.1.1. The previous owner told me that it is rooted. Nothing seems weird with the phone other than when i try to factory reset it it takes me to a "bios" kind window where i have to manually choose to delete all data (hard delete i think its called), that and when i normally turn on the phone, at the top left corner it says "set warranty bit kernel". I was just wondering how do i go about installing custom roms since its already rooted, and can i unblock the default carriers (T-mobile) block for other sim cards. When asked how he rooted it (what method was he using) he said he just used Odin. I dont know much about rooting so, whatever you can tell me as to the handling of the phone would be amazing. Any other guides to installing some custom roms and making the phone easier and faster ( i only want functionality, don't care much about the UI) would be greatly appreciated. Thanks in advance.
Click to expand...
Click to collapse
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
That's what I love about Samsung, as long as you have your ducks in a row, the files and tools are extremely easy to use, a 4 year old could do it.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
Thank you, ill be sure to check them out. Although, i would like to do the entire process from the beginning (root it again myself since i have no idea what the previous owner has done) and then try to install custom roms and other cool features rooting offers. I read that the KNOX security on samsung phones can pose some problems, any thoughts on that ?
Thank you again for your response.
ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
luan96 said:
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
Click to expand...
Click to collapse
I've got no experience with Linux, sorry. SuperSU disables knox so there's nothing to worry about.
luan96 said:
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
Click to expand...
Click to collapse
If you're a Linux user and you have knowledge of using terminal commands then you should have no trouble setting up Hiemdall. Getting full USB functionality set up for the device in Hiemdall can be a pain if you aren't familiar with that kind of thing.
But, having a Windows PC will make a lot of things very simplified for you. A Windows/Linux dual boot system would be very handy to you if you can set that up. Then you could also use Kies/SmartSwitch if it ever comes to a point that you need it.
There are some handy rarely used instances with Linux when it comes to Samsung. They have no fastboot like other devices so only adb is usable. I think they primarily centered around Windows being the preferred OS to interact with their devices.
Droidriven said:
If you're a Linux user and you have knowledge of using terminal commands then you should have no trouble setting up Hiemdall. Getting full USB functionality set up for the device in Hiemdall can be a pain if you aren't familiar with that kind of thing.
But, having a Windows PC will make a lot of things very simplified for you. A Windows/Linux dual boot system would be very handy to you if you can set that up. Then you could also use Kies/SmartSwitch if it ever comes to a point that you need it.
There are some handy rarely used instances with Linux when it comes to Samsung. They have no fastboot like other devices so only adb is usable. I think they primarily centered around Windows being the preferred OS to interact with their devices.
Click to expand...
Click to collapse
Thank you for the info. I already have a dual boot on my pc with windows. I am an experienced Linux user and setting up Hiemdall should not pose a problem, but i opted to go for Windows since as you said makes things simpler.
Still looking for guides and tutorials on how exactly the root process goes. Doing research, so i guess its going to be a late night. If you have any links or pages you can guide me to for my Samsung J5 it would be amazing. Right now am looking around this forum and wherever the links lead me.
Thank you again.
luan96 said:
Thank you for the info. I already have a dual boot on my pc with windows. I am an experienced Linux user and setting up Hiemdall should not pose a problem, but i opted to go for Windows since as you said makes things simpler.
Still looking for guides and tutorials on how exactly the root process goes. Doing research, so i guess its going to be a late night. If you have any links or pages you can guide me to for my Samsung J5 it would be amazing. Right now am looking around this forum and wherever the links lead me.
Thank you again.
Click to expand...
Click to collapse
First, just to make sure that you are not walking blindly into some potential traps.
1) download the root checker app from Playstore, use it to verify whether the device is actually rooted.
2) power the device off, wait 5 seconds, hold volume up+home+power, when it boots past the logo, let go. It should boot to recovery, tell me what you see. Does it say TWRP with grey buttons on a black screen? Or does it have an android lying on his back and have options listed?
3) verify whether or not the bootloader is unlocked or not on your specific device model number with your specific build number/android version, if it's locked it will create problems if you try to flash custom recovery. Though you can flash CF autoroot with locked bootloader.
Then I'll help find what you need to do what you are looking to do. It may be simpler than you think.
If he in fact used Odin and the device is rooted, he did one of three things.
1) flashed custom recovery(TWRP) via Odin then flashed SuperSU.zip to root, not possible with locked bootloader.
2) flashed CF auto root via Odin, potentially leaving stock recovery if your bootloader is locked.
3) flashed a pre-rooted stock firmware via Odin, not likely though.
The first 2 being more likely than the last one, the second one being the most likely if your bootloader is locked.
Edit: @luan96, edited for more information.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
1. Turn on OEM Unlocking and USB Debugging from developer versions
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
luan96 said:
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
Click to expand...
Click to collapse
I would recommend using the command line to flash the twrp instead of the GUI if you want a simple process in linux
Run a terminal as a superuser (sudo)
heimdall flash –RECOVERY filename.img
Do step 1 and 3 you gave before before doing this
Or just flash the twrp image using Odin
J500FN twrp
https://dl.twrp.me/j5nltexx/
-Hope- said:
I would recommend using the command line to flash the twrp instead of the GUI if you want a simple process in linux
Run a terminal as a superuser (sudo)
heimdall flash –RECOVERY filename.img
Do step 1 and 3 you gave before before doing this
Or just flash the twrp image using Odin
J500FN twrp
https://dl.twrp.me/j5nltexx/
Click to expand...
Click to collapse
I'm going to use Odin for this. Since I'm quite new to the rooting community I dont want to mess things up on the first try. I'd rather get comfortable with some standard stuff before I proceed to try different variations. Thank you for your input. Though I would still like to know if I should use cm auto root or do a manual root. The difference is not quite clear to me yet. Again, thank you for your input, it is appreciated.
luan96 said:
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
1. Turn on OEM Unlocking and USB Debugging from developer versions
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
Click to expand...
Click to collapse
Flashing CF autoroot will simplify rooting, again, just make sure you have the correct autoroot for your specific model number and firmware, flashing the wrong one can softbrick or hardbrick your device, this would require flashing stock firmware via Odin to repair if softbricked and more serious methods to restore if hardbricked. There isn't much difference in effect with the different rooting methods. They all get the job done about equally.
Just make sure that you verify that your bootloader is in fact unlocked BEFORE you flash TWRP. As stated earlier, if it is locked, it will certainly cause issues and you'll have to restore stock recovery and/or stock firmware.
As long as your bootloader is unlocked then your outlined plan should be good to go.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Flashing CF autoroot will simplify rooting, afain, just make sure you have the correct autoroot for your specific model number and firmware, flashing the wrong one can softbrick or hardbrick your device, this would require flashing stock firmware via Odin to repair if softbricked and more serious methods to restore if hardbricked. There isn't much difference in effect with the different rooting methods. They all get the job done about equally.
Just make sure that you verify that your bootloader is in fact unlocked BEFORE you flash TWRP. As stated earlier, if it is locked, it will certainly cause issues and you'll have to restore stock recovery and/or stock firmware.
As long as you're bootloader is unlocked then your outlined plan should be good to go.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Well, looks like i messed up somehow. I was fiddling around the recovery mode and Odin mode. Those were the only two screens i could view besides normal booting, so i was looking for any info.
Recovery Mode https://ibb.co/hotYZ5
Odin mode 1 https://ibb.co/nFfVE5
Once on the recovery mode, i selected "reboot to bootloader" hoping to find info if its locked or not. I got redirected to this screen
Odin Mode 2 https://ibb.co/kqhtZ5
And then i did what i think is the dumbest thing this year....i removed the batery and now when i try to turn on my phone -
Blocked https://ibb.co/kkOd1k
Please tell me i did not brick my phone without even trying to root it first. My understanding is that i accidentally wiped the current OS (softbrick?) and now i have to flash a new one and then continue with what i had planned. Or is this a small problem that can be fixed easier? Or a more serious one ? Good news tho maybe, i think that the bootloader is unlocked ?
Thank you @Droidriven for your info so far, you have been extremely helpful.
*EDIT* - Pictures didnt link correctly.
luan96 said:
Well, looks like i messed up somehow. I was fiddling around the recovery mode and Odin mode. Those were the only two screens i could view besides normal booting, so i was looking for any info.
Recovery Mode https://ibb.co/hotYZ5
Odin mode 1 https://ibb.co/nFfVE5
Once on the recovery mode, i selected "reboot to bootloader" hoping to find info if its locked or not. I got redirected to this screen
Odin Mode 2 https://ibb.co/kqhtZ5
And then i did what i think is the dumbest thing this year....i removed the batery and now when i try to turn on my phone -
Blocked https://ibb.co/kkOd1k
Please tell me i did not brick my phone without even trying to root it first. My understanding is that i accidentally wiped the current OS (softbrick?) and now i have to flash a new one and then continue with what i had planned. Or is this a small problem that can be fixed easier? Or a more serious one ? Good news tho maybe, i think that the bootloader is unlocked ?
Thank you @Droidriven for your info so far, you have been extremely helpful.
*EDIT* - Pictures didnt link correctly.
Click to expand...
Click to collapse
It looks to me like they attempted to root the device but didn't do it correctly.
FRP can be a pain to deal with. Some can be bypassed easily, those that have trouble bypassing must sign in with the original owner's original Gmail and password used to activate the device.
The method of bypassing FRP varies from device to device.
Did you factory reset in recovery? If so, that's why you FRP blocked you.
If you have stock recovery then you should not have been able to wipe out the OS using stock recovery, typically, only custom recovery can do that, unless you did something accidentally that somehow corrupted/wiped your OS.
If the OS is gone, you'll have to flash your stock firmware via Odin and start over from the beginning.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
It looks to me like they attempted to root the device but didn't do it correctly.
FRP can be a pain to deal with. Some can be bypassed easily, those that have trouble bypassing must sign in with the original owner's original Gmail and password used to activate the device.
The method of bypassing FRP varies from device to device.
Did you factory reset in recovery? If so, that's why you FRP blocked you.
If you have stock recovery then you should not have been able to wipe out the OS using stock recovery, typically, only custom recovery can do that, unless you did something accidentally that somehow corrupted/wiped your OS.
If the OS is gone, you'll have to flash your stock firmware via Odin and start over from the beginning.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Thank you. At least its not just a paperweight. I'm installing new software on it with Kiesk 3 right now. Hope that works so i can do the rooting and TWRP install soon. I pressed "reboot to bootlader" to try and find out if its locked or not, but then it got me in download mode (without having to press up volume to contionue). After i turned off my phone by removing the battery, the OS was gone.
luan96 said:
Thank you. At least its not just a paperweight. I'm installing new software on it with Kiesk 3 right now. Hope that works so i can do the rooting and TWRP install soon. I pressed "reboot to bootlader" to try and find out if its locked or not, but then it got me in download mode (without having to press up volume to contionue). After i turned off my phone by removing the battery, the OS was gone.
Click to expand...
Click to collapse
Did you get this restored with Kies?
Droidriven said:
Did you get this restored with Kies?
Click to expand...
Click to collapse
Yes, i did. Worked like a charm, and even got the new 6.0.1 android on it. Also installed TWRP, and just finished installing Xposed Framework, now waiting for it to boot up ( i hear it takes some time). Seems all well so far. If any problems pop out ill be sure to post about it. Also thinking about making a new thread just to help newbies like me who really just want to remove some bloatware, and install some nice modules and not heavily mod the phone. You have been very helpful during this process. Many thanks to you ^-^ .
luan96 said:
Yes, i did. Worked like a charm, and even got the new 6.0.1 android on it. Also installed TWRP, and just finished installing Xposed Framework, now waiting for it to boot up ( i hear it takes some time). Seems all well so far. If any problems pop out ill be sure to post about it. Also thinking about making a new thread just to help newbies like me who really just want to remove some bloatware, and install some nice modules and not heavily mod the phone. You have been very helpful during this process. Many thanks to you ^-^ .
Click to expand...
Click to collapse
If you have issues with Xposed causing a bootloop, you can flash the Xposed uninstaller zip in TWRP to remove it, then troubleshoot why it bootlooped and try again.
Are you using the Touch wiz marshmallow Xposed framework?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE