[q] please help me boost moto g xt1031 uber noob - Moto G Q&A, Help & Troubleshooting

I bootloader on my moto g XT1031 BOOST MOBILE
i accidently deleted something wrong obviously when trying to delete bloatware
i have been trying to access a link for the STOCK settings... Unfortunately my backups were erased/never saved/non existent.
I am completely frustrated and would really appreciate someones help.
I am currently able to use the mobile device but with no wifi, no data connection, no apps on the phone. I am unable to do anything data/wireless on my handset.
Here is My situation as is....
I have windows computer, i have power cord for phone ( USB?) i can not access the ever popular link that says is currently unavailable, and thats it. PLEASE take me through every step assuming that i know absolutely nothing because i DO NOT. I cant afford a new phone. I need all WORKING links and to be taken through every single little step. I am on day two of trying to do this myself and have given up. Please help me before i lose my mind.
p.s I do have internet acces via my Windows computer.

Assuming you have a custom recovery already installed, simply download a custom ROM via PC, drag and drop it on to the SDcard of your phone where you can easily find it via recovery.. Boot to custom recovery, do a wipe and flash the ROM./Gapps. There are several basically stock ROMs with slight tweaks in the Dev section. There also may be stock flashables. This will at least get your phone back operational until you can do the research in to recovering stock firmware.
There are many helpful people here, but for the most part you are encouraged to do your research and know how to recover from situations such as this without asking questions. All the info can be found on these forums with a few mins of research. I don't mean to come off as rude... But if you're dabbling into the world of BL unlock, rooting,flashing, modding, things happen and you will need to know your way around your device.

mbj731 said:
Assuming you have a custom recovery already installed, simply download a custom ROM via PC, drag and drop it on to the SDcard of your phone where you can easily find it via recovery.. Boot to custom recovery, do a wipe and flash the ROM./Gapps. There are several basically stock ROMs with slight tweaks in the Dev section. There also may be stock flashables. This will at least get your phone back operational until you can do the research in to recovering stock firmware.
There are many helpful people here, but for the most part you are encouraged to do your research and know how to recover from situations such as this without asking questions. All the info can be found on these forums with a few mins of research. I don't mean to come off as rude... But if you're dabbling into the world of BL unlock, rooting,flashing, modding, things happen and you will need to know your way around your device.
Click to expand...
Click to collapse
Like i said i have been trying to accomplish this for two days now. I really feel like there is nothing i can do. I just simply dont understand what im doing given my current level of knowledge pertaining to the aforementioned query. I do not think you are coming off as rude and i appreciate you taking the time to share you imput with me. Its just that when you say "flashables" and "Boot to custom recovery" i become confused as to what that means. sigh
as i have previously mention my level of patience has grown thin which in turn has raised my level of frustration. If you wouldnt mind taking the time to point me in the right direction it would very much be appreciated.
thank you very much
-DR

1.) Follow this guide to unlock bootloader/flash a custom recovery via PC: http://forum.xda-developers.com/showthread.php?t=2684234
2.) Here is a link to obtain a STOCK flashable zip for the Boost Mobile XT1031, along with a "optimized" version which has already been debloated. Whichever you choose. Download the ROM and move it to your phones SD. Boot into the custom recovery (above guide tells how). Once in recovery, do a wipe or factory reset. Install/flash the .zip you put on your SD:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
Hopefully this helps and you can also learn along the way. All of the information you need is on this forum. It can all be confusing and frustrating at first, but once you get the hang of it there's really not much to it.
There may be a better way of going about this, but these steps will get you back to stock in the easiest way I can think of with little to no knowledge of customizations. Once you get more familiar with everything and do your research on whatever result you're trying to obtain, it will get easier and easier to understand and do.

Related

[Q] how 2 b pr0 leik u guys

Okay. Ignore the title, I couldn't think of anything to put. In short, I want to know about roms, about clockworkmod, cyanogen mod, and stuff like that. What they do, how to put them on, and I pretty much wanna know about the general stuff you do past rooting your phone. And I know that the section says No Noobs, but technically, I'm a newb, as far as I know i'm not annoying anyone or being completely nooblike.
Mainly with cyanogen. I read the instructions, and they seem too, I dont know, simplistic. I'd prefer exact details. Like, after I have clockwork mod installed, and I flash cyanogen, can i restore all the stuff I had on it? And once cyanogen is on there, is it already rooted, or must i root again? And if someone would explain to me how clockworkmod works in the first place. And how would I flash cyanogen? I thought it'd be through clockworkmod, but if I wipe everything and factory reset, wouldn't clockworkmod be gone?
My phone is a Samsung Galaxy S (Vibrant or not vibrant, I dont even know) It's a GT-i9000M. Running android 2.2.1, Rooted, I have clockworkmod installed, but still no idea what to do past that point. Also, my Kies isn't telling me about any 3.x upgrade, so how would i go about manually installing a new version of android? I know it has to do with Odin, but whenever i tried i ended up not doing anything.
And one last thing about MetaMorph. Where could i find themes for it? And do i need to have a certain Rom running in order to use metamorph themes?
I'm mainly used to iPhones and such, where there isnt really much to do besides jailbreaking and such, and moving on to android phones is pretty intense. XD So much more to do with Android phones.
Well uh, thats about all i can think of at the moment. Also please post anything you feel that a (somewhat) newb to android modding should know.
Sorry for all the questions, and to those that help me, I love you. <3
And if any moderators deem this thread as against the 'No Noobs' rule, at least send me a message telling me you deleted it, or else I'll end up looking endlessly through the forums for my thread. I've done that before, not fun. LOL (Couldn't find a 'My Threads' thingy on the forum i was using.
Gutana said:
Okay. Ignore the title, I couldn't think of anything to put. In short, I want to know about roms, about clockworkmod, cyanogen mod, and stuff like that. What they do, how to put them on, and I pretty much wanna know about the general stuff you do past rooting your phone. And I know that the section says No Noobs, but technically, I'm a newb, as far as I know i'm not annoying anyone or being completely nooblike.
Mainly with cyanogen. I read the instructions, and they seem too, I dont know, simplistic. I'd prefer exact details. Like, after I have clockwork mod installed, and I flash cyanogen, can i restore all the stuff I had on it? And once cyanogen is on there, is it already rooted, or must i root again? And if someone would explain to me how clockworkmod works in the first place. And how would I flash cyanogen? I thought it'd be through clockworkmod, but if I wipe everything and factory reset, wouldn't clockworkmod be gone?
My phone is a Samsung Galaxy S (Vibrant or not vibrant, I dont even know) It's a GT-i9000M. Running android 2.2.1, Rooted, I have clockworkmod installed, but still no idea what to do past that point. Also, my Kies isn't telling me about any 3.x upgrade, so how would i go about manually installing a new version of android? I know it has to do with Odin, but whenever i tried i ended up not doing anything.
And one last thing about MetaMorph. Where could i find themes for it? And do i need to have a certain Rom running in order to use metamorph themes?
I'm mainly used to iPhones and such, where there isnt really much to do besides jailbreaking and such, and moving on to android phones is pretty intense. XD So much more to do with Android phones.
Well uh, thats about all i can think of at the moment. Also please post anything you feel that a (somewhat) newb to android modding should know.
Sorry for all the questions, and to those that help me, I love you. <3
And if any moderators deem this thread as against the 'No Noobs' rule, at least send me a message telling me you deleted it, or else I'll end up looking endlessly through the forums for my thread. I've done that before, not fun. LOL (Couldn't find a 'My Threads' thingy on the forum i was using.
Click to expand...
Click to collapse
Well, I guess to first start off, here's a few pointers:
1. don't put the title in 1337 (people will most likely not click on it, thus no help)
2. you're right about this being the wrong thread. You should post this under the Samsung Galaxy S section (google your model number and you'll see it instantly) and should probably try the Q&A moreso than a general area (but it doesn't really matter all too much)
3. no matter how nooblike you may or may not be, you're still a noob XD
Now that we've gotten past the anally parts and all (hate doing that, but gotta =P), let's talk about what you came here for: answers.
Let's start with some definitions:
ROMs - these are the (usually modded) softwares that you flash to your phone. Depending on which phone you have, you can only flash ROMs made for your phone. Of course, if you have root/custom recovery, you can also install custom ROMs.
ClockWorkMod (CWM) is a recovery system made in order to allow people more features while they're in recovery mode. Of course, this is one of a few out there, but people stick to CWM cause of its huge support plus it's popularity. When you think of CWM, think of custom features being installed in (almost) one step (modding files and such will be taken care of for you, so you don't have to do it yourself). You can usually also fix a bricked system this way by reflashing either the entire ROM or the boot.img/other files (we'll get to this in a second)
CyanogenMod (CM) is an example of a very popular custom rom. They have a great team and usually is available for most devices, which in turn makes them so popular. It is widely supported and has a lot of extra features like updating to the latest OS and features not previously available on your phone. It's skinned, but usually follows the stock Android look for the OS in which they've skinned.
lol The reason why the instructions look so simple is because they've taken out all the hard work and all the stuff where you can possibly screw up your phone, so that they don't get a million messages saying "OMG MY PHONE BRICKED WHAT HAPPENED" and stuff like that. Protects them, makes it easier for you. If you had made a backup before you flashed CM (usually you only have to back up whats on the phone if it has internal and external memory, but back up your sd card always just in case. never hurt to), then yes. If you backed it up with your previous ROM, then you'll probably need to revert to get it back. If you didn't, chances are whatever you didn't backup and didn't sync, is safe to say gone. You can try recovering it using a recovery software on the computer like i detailed here for another person, but of course you'd skip the whole trying to save the phone part and just start with mounting the phone to your computer and running the software.
CM is a custom rom, and so most (if not all) custom roms have root preinstalled (besides, who wouldn't want root?!) As for CWM, it works by being (usually) flashed into the recovery partition of your phone. The nice thing about the phone is that it's split up into parts: boot, recovery, system, and some other ones i can't think of off the top of my head. Those three are important, as if you get a softbrick, you might still be able to recover all your data simply by using CWM/fastboot (a dev-tool used to flash/unlock, but only available in certain phones, as it is disabled usually) to reflash the boot.img (one requires command line, whereas CWM only needs you to flash a created/pre-made package). Also, since they're in separate partitions, even if your system and boot.img doesn't work, you can probably still access recovery (unless you screwed up really REALLY bad, and in that case I can't help >.<)
Observant you are =] Yes, if you were to flash CM, your CWM will be gone (i don't understand why most people don't just bake it into the ROM in the first place) but, not all is lost. Just go back into the Android Market and redownload ROM Manager. Of course you'll need to open it up and flash the same exact recovery again (annoying, isn't it?) but unless you know how to mod zip/img files and edit the script, you'll just have to make do with that. If you do, you could just (usually) take out the recovery partition and just leave the one you have already in there (but its usually safer and better to just redownload/reflash it as annoying as it is). But yes, you would use CWM to flash it. It's as simple as "Install from SD Card" which is why custom recoveries like CWM are popular. So simple
At this point, I would look into a few things. One is skinning your phone (though you probably can't do too much if you don't want to touch system files). If you find a psuedo-rom (slightly modded) that themes it, that's your best bet. Another is gaining access to certain features in apps you didn't have before (i.e. androidLost, LBE Privacy Guard, titanium backup) and of course more control by the ability to control your system files (if you know what you're doing, of course). Lastly, you can use stuff like MetaMorph to theme out certain sections of your rom (provided that they give you one compatible with your phone model/rom), minus having to flash it and having more fine-tuned controlled. Usually, Metamorph will run on all ROMs, but it doesn't guarantee that there'll be stuff for every ROM. Also, want themes? google it (google is your best friend!)
Kies won't tell you that you have an upgrade because it is ROM-dependent. It looks for their official ROM and says "Hey, this guy has our ROM. Check for an update". Think of owning a custom rom like being kicked out of your family. You won't get anymore updates from them XD. However, if you're looking to get the latest updates, check out the Samsung Galaxy S Dev threads. They will usually have another method of loading in the new ROM into your phone. And if you want to stick with ROM Manager, shell out for premium and they'll include "Check for Updates" in ROM Manager, along with several other functions (though you can check for free via computer/browser ). Mostly, manually updating the software requires the "Install from SD Card" feature in CWM/other recoveries, so you don't have much to worry about.
Odin is, as you stated, most likely your best bet. Not too many people repackage official ROMs into easy-to-flash zips. Odin is the Samsung equivalent to Motorola's RSD Lite from what I googled (i have motorola, so no exp. on odin >.<) It's mostly like a dev tool allowing you to flash/re-flash phones and is also usually your one-way ticket out of a semi/full brick (assuming you didn't mess up the hardware and you can get into download mode). It's the flashing tool that can access the core system of the phone even without root and allows you to reflash OFFICIAL ROMs. Should you use Odin (should be your last resort), you WILL lose root and all your data. No questions asked. Its like reinstalling everything to the state in which you got it in when you bought the phone. Word of advice: BACK UP OFTEN! (did i forget to mention Titanium Backup? )
Yeah, the transition from Apple to Android is so different and had I not had experience with my PSP, i'd be dying with the information overload. However, just read a lot of stuff on the forums (*cough*general android forums*cough*) and you should be just fine. We have an excellent community here that will try our best to fix whatever problems you encounter (note the key word: try. we're not gods XD) You'll get the hang of it soon enough.
Oh, well, I don't want to keep you for much longer, but since you mentioned something that any noob should know, it's definitely ADB (Android Debugging Bridge). This is where you'll probably spend a lot of time, as people's fixes usually involve shell (terminal for your phone). If anything, get acquainted with it, as it might save your butt in the future/unlock a few extra features for you ;D .
Well, that's all i can think of, and honestly, after typing this thing up for about an hour now, I think I'm going to grab me some breakfast Good luck to you and welcome to the Android commmunity! (and next time, remember to post in the right place! XD)
~jojojohnson7410
P.S. PM me if you need anything. =]
Observant you are =] Yes, if you were to flash CM, your CWM will be gone (i don't understand why most people don't just bake it into the ROM in the first place) but, not all is lost. Just go back into the Android Market and redownload ROM Manager. Of course you'll need to open it up and flash the same exact recovery again (annoying, isn't it?) but unless you know how to mod zip/img files and edit the script, you'll just have to make do with that. If you do, you could just (usually) take out the recovery partition and just leave the one you have already in there (but its usually safer and better to just redownload/reflash it as annoying as it is). But yes, you would use CWM to flash it. It's as simple as "Install from SD Card" which is why custom recoveries like CWM are popular. So simple
Click to expand...
Click to collapse
Just to nit-pick a bit. CWM is part of the recovery partition, and unless the Galaxy S is different from every other android device, flashing will not remove it. ROM Manager and CWM are two different things. ROM manager will allow you to download the roms, which will then instruct CWM to flash the rom (when it reboots).
jojojohnson7410 said:
Well, I guess to first start off, here's a few pointers:
1. don't put the title in 1337 (people will most likely not click on it, thus no help)
2. you're right about this being the wrong thread. You should post this under the Samsung Galaxy S section (google your model number and you'll see it instantly) and should probably try the Q&A moreso than a general area (but it doesn't really matter all too much)
3. no matter how nooblike you may or may not be, you're still a noob XD
Now that we've gotten past the anally parts and all (hate doing that, but gotta =P), let's talk about what you came here for: answers.
Let's start with some definitions:
ROMs - these are the (usually modded) softwares that you flash to your phone. Depending on which phone you have, you can only flash ROMs made for your phone. Of course, if you have root/custom recovery, you can also install custom ROMs.
ClockWorkMod (CWM) is a recovery system made in order to allow people more features while they're in recovery mode. Of course, this is one of a few out there, but people stick to CWM cause of its huge support plus it's popularity. When you think of CWM, think of custom features being installed in (almost) one step (modding files and such will be taken care of for you, so you don't have to do it yourself). You can usually also fix a bricked system this way by reflashing either the entire ROM or the boot.img/other files (we'll get to this in a second)
CyanogenMod (CM) is an example of a very popular custom rom. They have a great team and usually is available for most devices, which in turn makes them so popular. It is widely supported and has a lot of extra features like updating to the latest OS and features not previously available on your phone. It's skinned, but usually follows the stock Android look for the OS in which they've skinned.
lol The reason why the instructions look so simple is because they've taken out all the hard work and all the stuff where you can possibly screw up your phone, so that they don't get a million messages saying "OMG MY PHONE BRICKED WHAT HAPPENED" and stuff like that. Protects them, makes it easier for you. If you had made a backup before you flashed CM (usually you only have to back up whats on the phone if it has internal and external memory, but back up your sd card always just in case. never hurt to), then yes. If you backed it up with your previous ROM, then you'll probably need to revert to get it back. If you didn't, chances are whatever you didn't backup and didn't sync, is safe to say gone. You can try recovering it using a recovery software on the computer like i detailed here for another person, but of course you'd skip the whole trying to save the phone part and just start with mounting the phone to your computer and running the software.
CM is a custom rom, and so most (if not all) custom roms have root preinstalled (besides, who wouldn't want root?!) As for CWM, it works by being (usually) flashed into the recovery partition of your phone. The nice thing about the phone is that it's split up into parts: boot, recovery, system, and some other ones i can't think of off the top of my head. Those three are important, as if you get a softbrick, you might still be able to recover all your data simply by using CWM/fastboot (a dev-tool used to flash/unlock, but only available in certain phones, as it is disabled usually) to reflash the boot.img (one requires command line, whereas CWM only needs you to flash a created/pre-made package). Also, since they're in separate partitions, even if your system and boot.img doesn't work, you can probably still access recovery (unless you screwed up really REALLY bad, and in that case I can't help >.<)
Observant you are =] Yes, if you were to flash CM, your CWM will be gone (i don't understand why most people don't just bake it into the ROM in the first place) but, not all is lost. Just go back into the Android Market and redownload ROM Manager. Of course you'll need to open it up and flash the same exact recovery again (annoying, isn't it?) but unless you know how to mod zip/img files and edit the script, you'll just have to make do with that. If you do, you could just (usually) take out the recovery partition and just leave the one you have already in there (but its usually safer and better to just redownload/reflash it as annoying as it is). But yes, you would use CWM to flash it. It's as simple as "Install from SD Card" which is why custom recoveries like CWM are popular. So simple
At this point, I would look into a few things. One is skinning your phone (though you probably can't do too much if you don't want to touch system files). If you find a psuedo-rom (slightly modded) that themes it, that's your best bet. Another is gaining access to certain features in apps you didn't have before (i.e. androidLost, LBE Privacy Guard, titanium backup) and of course more control by the ability to control your system files (if you know what you're doing, of course). Lastly, you can use stuff like MetaMorph to theme out certain sections of your rom (provided that they give you one compatible with your phone model/rom), minus having to flash it and having more fine-tuned controlled. Usually, Metamorph will run on all ROMs, but it doesn't guarantee that there'll be stuff for every ROM. Also, want themes? google it (google is your best friend!)
Kies won't tell you that you have an upgrade because it is ROM-dependent. It looks for their official ROM and says "Hey, this guy has our ROM. Check for an update". Think of owning a custom rom like being kicked out of your family. You won't get anymore updates from them XD. However, if you're looking to get the latest updates, check out the Samsung Galaxy S Dev threads. They will usually have another method of loading in the new ROM into your phone. And if you want to stick with ROM Manager, shell out for premium and they'll include "Check for Updates" in ROM Manager, along with several other functions (though you can check for free via computer/browser ). Mostly, manually updating the software requires the "Install from SD Card" feature in CWM/other recoveries, so you don't have much to worry about.
Odin is, as you stated, most likely your best bet. Not too many people repackage official ROMs into easy-to-flash zips. Odin is the Samsung equivalent to Motorola's RSD Lite from what I googled (i have motorola, so no exp. on odin >.<) It's mostly like a dev tool allowing you to flash/re-flash phones and is also usually your one-way ticket out of a semi/full brick (assuming you didn't mess up the hardware and you can get into download mode). It's the flashing tool that can access the core system of the phone even without root and allows you to reflash OFFICIAL ROMs. Should you use Odin (should be your last resort), you WILL lose root and all your data. No questions asked. Its like reinstalling everything to the state in which you got it in when you bought the phone. Word of advice: BACK UP OFTEN! (did i forget to mention Titanium Backup? )
Yeah, the transition from Apple to Android is so different and had I not had experience with my PSP, i'd be dying with the information overload. However, just read a lot of stuff on the forums (*cough*general android forums*cough*) and you should be just fine. We have an excellent community here that will try our best to fix whatever problems you encounter (note the key word: try. we're not gods XD) You'll get the hang of it soon enough.
Oh, well, I don't want to keep you for much longer, but since you mentioned something that any noob should know, it's definitely ADB (Android Debugging Bridge). This is where you'll probably spend a lot of time, as people's fixes usually involve shell (terminal for your phone). If anything, get acquainted with it, as it might save your butt in the future/unlock a few extra features for you ;D .
Well, that's all i can think of, and honestly, after typing this thing up for about an hour now, I think I'm going to grab me some breakfast Good luck to you and welcome to the Android commmunity! (and next time, remember to post in the right place! XD)
~jojojohnson7410
P.S. PM me if you need anything. =]
Click to expand...
Click to collapse
Wow, thanks a lot. I still have a question or two, bear with me.
Well for one, is flashing roms made for different firmwares alright, or no? Since I have 2.2, and im assuming the latest cyanogen is made for 3.x, would I have to upgrade my firmware to the corresponding firmware.
And about Clockwork, if my phone bricks, I'd have to restore using odin, right? But if the phone still works, i can just root and cwm and restore it using rom manager?
And uh, I'm not sure if this is a problem or im just doing something wrong, but in RomManager, i click Backup Current ROM, and it goes into recovery mode, and theres no new options, there's just like, format, factory reset, clear cache, reboot, but nothing involving rom manager. And when i check for the recovery file in my sd card, it's not. Wut do.
WoZZeR999 said:
Just to nit-pick a bit. CWM is part of the recovery partition, and unless the Galaxy S is different from every other android device, flashing will not remove it. ROM Manager and CWM are two different things. ROM manager will allow you to download the roms, which will then instruct CWM to flash the rom (when it reboots).
Click to expand...
Click to collapse
lol true true that would be my mistake. XD Nice catch
~jojojohnson7410
Gutana said:
Wow, thanks a lot. I still have a question or two, bear with me.
Well for one, is flashing roms made for different firmwares alright, or no? Since I have 2.2, and im assuming the latest cyanogen is made for 3.x, would I have to upgrade my firmware to the corresponding firmware.
Click to expand...
Click to collapse
No, you wouldn't have to upgrade to the latest firmware to get the ROM installed. So long as the ROM is confirmed to work for your device, you can flash any ROM you want (which is convenient in my case since I have an Atrix 4G and it was oh-so-lonely without some Gingerbread XD)
Gutana said:
And about Clockwork, if my phone bricks, I'd have to restore using odin, right? But if the phone still works, i can just root and cwm and restore it using rom manager?
Click to expand...
Click to collapse
Well, the thing is, you really only need that usually if you're on a stock rom or some official version and either you want to flash a new stock ROM from Samsung or you want to pull your phone out of a brick. Most of the time, however, even if you bricked it, so long as you can get into the recovery menu, you'll be alright. Just re-flash the ROM that you want (or in my case yesterday when I was dealing with an Inspire, I had to use a different ROM to unbrick the phone. I don't know why this happen, but it was being nit-picky >.<)
Gutana said:
And uh, I'm not sure if this is a problem or im just doing something wrong, but in RomManager, i click Backup Current ROM, and it goes into recovery mode, and theres no new options, there's just like, format, factory reset, clear cache, reboot, but nothing involving rom manager. And when i check for the recovery file in my sd card, it's not. Wut do.
Click to expand...
Click to collapse
lol nooo this is not a problem at all. See, like the guy above me posted, the Recovery Menu is completely separate from anything in the ROM. It's located in the recovery partition rather than the system and the boot partitions, so they usually don't touch the recovery. ROM Manager is just a means of providing GUI to CWM so then you can either flash the CWM to your phone or help download ROMS into your SD card. Stuff like backup and everything needs you to boot into recovery as you can't be backing up the system while your system is mounted on, so they send you to CWM. From there, there's an option called "backup and restore". In this place, you can choose where to save the backup. And since the backup is made by CWM, it will be recognized by CWM if you want to restore it. I think it saves it in a zip file, but im not 100% positive, so take that one with a grain of salt.
Hope this answers the questions! Let me know if you need more help (or just PM me. I check that regularly )
~jojojohnson7410
jojojohnson7410 said:
No, you wouldn't have to upgrade to the latest firmware to get the ROM installed. So long as the ROM is confirmed to work for your device, you can flash any ROM you want (which is convenient in my case since I have an Atrix 4G and it was oh-so-lonely without some Gingerbread XD)
Well, the thing is, you really only need that usually if you're on a stock rom or some official version and either you want to flash a new stock ROM from Samsung or you want to pull your phone out of a brick. Most of the time, however, even if you bricked it, so long as you can get into the recovery menu, you'll be alright. Just re-flash the ROM that you want (or in my case yesterday when I was dealing with an Inspire, I had to use a different ROM to unbrick the phone. I don't know why this happen, but it was being nit-picky >.<)
lol nooo this is not a problem at all. See, like the guy above me posted, the Recovery Menu is completely separate from anything in the ROM. It's located in the recovery partition rather than the system and the boot partitions, so they usually don't touch the recovery. ROM Manager is just a means of providing GUI to CWM so then you can either flash the CWM to your phone or help download ROMS into your SD card. Stuff like backup and everything needs you to boot into recovery as you can't be backing up the system while your system is mounted on, so they send you to CWM. From there, there's an option called "backup and restore". In this place, you can choose where to save the backup. And since the backup is made by CWM, it will be recognized by CWM if you want to restore it. I think it saves it in a zip file, but im not 100% positive, so take that one with a grain of salt.
Hope this answers the questions! Let me know if you need more help (or just PM me. I check that regularly )
~jojojohnson7410
Click to expand...
Click to collapse
But theres no backup and restore options, its jut the recovery options you'd get if you were on a brand new phone.

n00b to rooting and CWM for P3113

First off love the N00b video at sign up that was hysterical, nice work to whoever made it.
Ok on to what I need to know:
I understand HOW TO root/flash a rom, my issue is kind of different than most peoples. I have scoured the web and this site for the files I need to accomplish this with my GT-P3113 build ending in LG5 however I am confused to hell.
1 place will say that CWM 6.0.1 is not usable on my device, another will say that it works fine and another will say to use TWRP (which might I add looks cool to use). Some will say that I need the expresso_wifi file to root my device, others will say use update.zip, and others will say a totally different file all together.
I know what ROM to get, I understand the steps:
Download drivers
Boot to download
use odin to install CWM
back up everything with CWM (which goes to the MicroSD I am guessing? since I wipe the device in a later step)
wipe the device
wipe the cache
wipe the Dalvik cache
flash the rom
flash the root
is all that correct? (just to make sure I got it right) so my biggest question is, which files do I really use? There is a thread from back in June before the 4.0.4 update OTA came through) saying to use instead of that if you have LG3 or etc.
Help would be greatly appreciated, I am a smart guy, just want to have my facts straight before I make this happen.
PS sorry if this is in the wrong place, figured this was the best place for it.
Please be sure and thank the person who decides to do your homework for you.
:laugh:
FlynnErik said:
First off love the N00b video at sign up that was hysterical, nice work to whoever made it.
Ok on to what I need to know:
I understand HOW TO root/flash a rom, my issue is kind of different than most peoples. I have scoured the web and this site for the files I need to accomplish this with my GT-P3113 build ending in LG5 however I am confused to hell.
1 place will say that CWM 6.0.1 is not usable on my device, another will say that it works fine and another will say to use TWRP (which might I add looks cool to use). Some will say that I need the expresso_wifi file to root my device, others will say use update.zip, and others will say a totally different file all together.
I know what ROM to get, I understand the steps:
Download drivers
Boot to download
use odin to install CWM
back up everything with CWM (which goes to the MicroSD I am guessing? since I wipe the device in a later step)
wipe the device
wipe the cache
wipe the Dalvik cache
flash the rom
flash the root
is all that correct? (just to make sure I got it right) so my biggest question is, which files do I really use? There is a thread from back in June before the 4.0.4 update OTA came through) saying to use instead of that if you have LG3 or etc.
Help would be greatly appreciated, I am a smart guy, just want to have my facts straight before I make this happen.
PS sorry if this is in the wrong place, figured this was the best place for it.
Click to expand...
Click to collapse
From someone relatively new to this as well, this is basically correct. Here are some tips from someone who has recently done it.
Make a backup.
Research the files you intend to flash, make sure they are right for your device
Verify the guide you are using has been tested and known to work.
This may seem elementary, but I didn't follow #3 and it cost me a lot of headache un-bricking my SGT 2.
ryphil said:
From someone relatively new to this as well, this is basically correct. Here are some tips from someone who has recently done it.
Make a backup.
Research the files you intend to flash, make sure they are right for your device
Verify the guide you are using has been tested and known to work.
This may seem elementary, but I didn't follow #3 and it cost me a lot of headache un-bricking my SGT 2.
Click to expand...
Click to collapse
Fully agreed! That's why I came to the experts. I have done my homework but the thing is my homework leads me to several different files from before the ICS update. There has only been 1 thread on 1 forum that has been post ICS update, and no real feedback on it. I think I even found one that uses ADB (I understand that concept, but would prefer not to use it since I don't know Linux well enough).
I would love to know what files to use, which ones to stay away from. As I said I have the concepts, I have the understanding, its the actual files that I want to verify, I can rattle off tons of files from tons of sites, but they may or may not be correct (and may have the same name as a correct one but still be incorrect, ie "update.zip" appears a few times on different threads from different time frames).
There is only post in the teamhacksung CM10 wiki that was last edited 8/12/2012, but that could have been anything that was updated, not the files/links to be used.
So I thank you in advance for your help, and you will certainly get a thank you in the forum for help you are providing, I always give credit where credit is due.
Well here goes nothing, going to reboot (to ensure the Kies drivers are installed and loaded into the system 100%), and try the instructions from this link http://forum.xda-developers.com/showthread.php?t=1788625
It seems to work for most, the only concern I have is that I have a different end to the build than most others do (and I am not sure why?)
Did I screw myself?
I rooted, and have CWM installed.
Is it to late to create a ROM backup of my device for when i go to install CM10 (I need a drink for now, so I might install it tomorrow night lol).
That link I posted in the last post is good to go if anyone else needs a safe bet set of directions.
Seriously though, I didn't do a backup, am I screwed now?
EDIT: I just did a back up and it said no sdcard/.android secure found, skipping of backup of apps
and
no sd-ext found skipping backup of that.
is that normal? Did it backup to my microSD?
Still hope I didn't screw myself by backing it up after rooting.

How does a non-techy get Cyanogenmod installed on a Samsung Galaxy Ace 3?

Apologies if this is not really the place for this question but I don't know where else to go for an answer. I have just purchased a Z1 after years of putting up with Samsung bloatware etc and it has changed my life! I would like to transform my wife's phone experience as well. She can only really use a small phone and has been happy with her Ace 3 until recently, when it started to get slow and erratic. In desperation she has bought an iPhone 5 but this has not been a happy experience at all! I cannot find any new small Android phones that come with Cyanogen pre-installed so I am wondering if we can get it installed on her old Ace 3. From the discussions in this forum I guess this can be done but, not having any technical training in this subject, I really dont understand much of what is being said. I have no idea how to go about this.
So is there either a very simple manual on what to do or else a UK-based expert who can do this for me (for a fee, obviously)?
you can look from the android development section. but, it may vary to your phone model. there is a instructions to on how to install a cyanogenmod os on your ace 3. at least you are familliar with custom recoveries like cwm or twrp, you should install it first on your phone via odin in your pc.
You guys know so much
Hi, PAPlinskie, and thanks so much for getting back to me. I really appreciate it. I have looked at the page you refer to and I just don't understand it! (I don't know what cwm or twrp or Odin are) I guess you guys don't realise just how much you know. I suspect that the answer to my question is probably that there isn't an absolute layman's guide so I will probably have to look for someone to do it for me. Thanks for trying anyway.
Garth Horigan said:
Hi, PAPlinskie, and thanks so much for getting back to me. I really appreciate it. I have looked at the page you refer to and I just don't understand it! (I don't know what cwm or twrp or Odin are) I guess you guys don't realise just how much you know. I suspect that the answer to my question is probably that there isn't an absolute layman's guide so I will probably have to look for someone to do it for me. Thanks for trying anyway.
Click to expand...
Click to collapse
At first I didn't want to flash Custom ROM's on my phone for fear of breaking it... But All I had to do was just follow instructions to the "T" and I had no hiccups...
Okay, so lemme clear some things up for you.
Odin is an Application which you run on a Windows machine, (Your PC). It serves as a bridge to allow you to put custom software such as custom recoveries and allows you to fix a broken device (If the software is the problem)
TWRP & CWM are both custom recoveries. You can think of the stock recovery mode in Android like Safe Mode in Windows, It allows you to Wipe your entire phone or perform other recovery options if you are unable to access the phone when you turn it on. A custom recovery allows all these functions, but on top of that, allows you to flash (install) files to your phone, Like your CyanogenMod.
In a nutshell, if you want CyanogenMod on your Ace 3, you will have to:
1. Install drivers on your PC so that it recognises your phone
2. Using ODIN, flash a custom Recovery
3. Download a CyanogenMod port found here on the forums.
4. Install (Flash) it in your Custom recovery.
The guides here on XDA are really good, all you have to do is do your homework, read, understand and you will have no problems.
Good Luck with your quest on Custom ROMS:good:
The coward's way out!
Sayrian said:
At first I didn't want to flash Custom ROM's on my phone for fear of breaking it... But All I had to do was just follow instructions to the "T" and I had no hiccups...
Okay, so lemme clear some things up for you.
Odin is an Application which you run on a Windows machine, (Your PC). It serves as a bridge to allow you to put custom software such as custom recoveries and allows you to fix a broken device (If the software is the problem)
TWRP & CWM are both custom recoveries. You can think of the stock recovery mode in Android like Safe Mode in Windows, It allows you to Wipe your entire phone or perform other recovery options if you are unable to access the phone when you turn it on. A custom recovery allows all these functions, but on top of that, allows you to flash (install) files to your phone, Like your CyanogenMod.
In a nutshell, if you want CyanogenMod on your Ace 3, you will have to:
1. Install drivers on your PC so that it recognises your phone
2. Using ODIN, flash a custom Recovery
3. Download a CyanogenMod port found here on the forums.
4. Install (Flash) it in your Custom recovery.
The guides here on XDA are really good, all you have to do is do your homework, read, understand and you will have no problems.
Good Luck with your quest on Custom ROMS:good:
Click to expand...
Click to collapse
I have taken the coward's way out. I went into my local neighbourhood PC techie shop and asked if they knew of a reliable local phone engineer who could install Cyanogen for me. The boss' assistant said he does that sort of thing for a hobby and was happy to do it for me in return for a donation to his drone fund! He seems to made a cracking job of it and my wife is overjoyed to have her Ace back in a turbo-charged state.
Many thanks for your help and I am only sorry I was not brave enough to act on it.
Garth Horigan said:
I have taken the coward's way out. I went into my local neighbourhood PC techie shop and asked if they knew of a reliable local phone engineer who could install Cyanogen for me. The boss' assistant said he does that sort of thing for a hobby and was happy to do it for me in return for a donation to his drone fund! He seems to made a cracking job of it and my wife is overjoyed to have her Ace back in a turbo-charged state.
Many thanks for your help and I am only sorry I was not brave enough to act on it.
Click to expand...
Click to collapse
It's okay. We all know how daunting these things can be because you don't want to brick your device.
Maybe in the future you will be able to try it yourself.

mob30p to mob30m help (total newb)

hi,
my phone is practically useless with this latest update. the issues are well documented, so i won't go into that. what i would like to do is get my phone back to mob30m, or anything else that will fix the volume issues. google is taking forever to get this fixed.
my problem is, i am a complete novice, when doing these kinds of things. i have been looking around at forum threads to try to get the skinny, but a lot of this is contradictory. my specific aim is to do the following.
unlock bootloader
root
install twrp (or similar)
download the appropriate file to get back to mob30m.
and install that.
i need to know what is the most current (tried) methods of doing these steps.
any help would be greatly appreciated. i'm assuming there might be multiple links i have to look at to get these results, but just perusing these fora is baffling me.
thanks
All you need to do is download the appropriate stock rom and flash it to your phone using fastboot commands.
You'll need an unlocked bootloader which will cause a full wipe of your data on the phone.
You can also use this if you have a PC - http://www.wugfresh.com/nrt/
It can unlock the bootloader, flash a recovery, flash a ROM, root and other technical stuff.

Already rooted Samsung J5 - general inquiry

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

Categories

Resources