Database Info

Possibly soft bricked.

I did search, but in all honesty Im not really sure what Im looking for. Yesterday I rooted with the Ace Hack. Then today I was looking through Rom Manager, and I downloaded cyanogenmod, and when it finished it wanted to load it, so I let it. Ive done two backups prior to this. Now when I turn it on the white HTC screen comes up, then it goes to the cyanogenmod 7 screen, skateboarding android with a ring around him and a loading arrow. And thats all it does, over and over. Is there a way to boot to the backups? A certain button combonation I should be using? Specific terms I should search for? Please, at least, point me in the right direction.

slipmagt said:
I did search, but in all honesty Im not really sure what Im looking for. Yesterday I rooted with the Ace Hack. Then today I was looking through Rom Manager, and I downloaded cyanogenmod, and when it finished it wanted to load it, so I let it. Ive done two backups prior to this. Now when I turn it on the white HTC screen comes up, then it goes to the cyanogenmod 7 screen, skateboarding android with a ring around him and a loading arrow. And thats all it does, over and over. Is there a way to boot to the backups? A certain button combonation I should be using? Specific terms I should search for? Please, at least, point me in the right direction.
Click to expand...
Click to collapse
You'll need to do a complete wipe to install CM over an existing sense build. Sense stores the dalvik on the data partition and CM7 stores it on the cache partition. If you don't do a full wipe, then the dalvik never gets set up properly.
You should still be able to get into cwm recovery via hboot. Make sure phone is off (pull battery if necessary). Hold VOL-DOWN button while pressing power for about a second. You should end up in the HBOOT screen. Select recovery and press power. Hopefully CWM recovery will boot up and you can just do a "Wipe data/Factory Reset" and be good.

I had just found out how to boot to recovery seconds before I checked the thread again. Instead I went to backup and recover, and restored from a backup, and it didnt work. So I am trying what you suggested, I really appreciate you giving me all the steps required.
I may have told it to not delete the dalvik when it wanted to start up cyanogenmod.

So what is the best way to download roms and switch between them?

slipmagt said:
So what is the best way to download roms and switch between them?
Click to expand...
Click to collapse
1 suggestion...ditch rom manager. I've had issues before where it messed up my downloads. Not everyone has this issue I will say, but I would try not using it. All the devs update their threads here on xda with the latest versions in their threads. Download them from the site, boot into recovery,back up your current rom, and flash away!
I got your 10 char right here

cwhitney24 said:
1 suggestion...ditch rom manager. I've had issues before where it messed up my downloads. Not everyone has this issue I will say, but I would try not using it. All the devs update their threads here on xda with the latest versions in their threads. Download them from the site, boot into recovery,back up your current rom, and flash away!
I got your 10 char right here
Click to expand...
Click to collapse
Agreed. I've never used RomManager with the Inspire, but I had nothing but problems with it on my Aria.

It gone. How do you switch between roms then?

slipmagt said:
It gone. How do you switch between roms then?
Click to expand...
Click to collapse
Like I said above...use the threads to find the roms. Download them and flash them in recovery. ALWAYS create a back up so you can flash back to your back ups if you want. All that can be done in recovery.
If you do not know how to do this then my thoughts on why rom manager exists are true. Search the threads and learn how to do all the fun stuff without rom manager and without needing someone to hold your hand. (Wasn't being mean just a figure of speech)
I got your 10 char right here

[Q] Which CWM should I be installing

I have a rooted Rogers 727R. Installed CWM 5.0.2.7 a few months ago after I rooted it. Installed with ROM manager I think.
However I've found a file called recovery-clockwork-touch-5.8.1.3-hercules which seems to be a later version.
And now, I see people are talking about a touch version, ClockworkMod TOUCH 5.5.0.4 v2. I note from the instructions in the OP you have to use the DD commands, I assume no ROM manager install on top of the current version?
I like to keep up to date. What version should I have?
Thanks

i suggest you go to this thread
http://forum.xda-developers.com/forumdisplay.php?f=1383
and then take your time to review the pros and cons... there are no straight answers for your question.

I just use ROM Manager, use the latest Clockwork recovery using ROM Manager.

That takes me to the forum home page, not a thread.
Do you know if this one:
Recovery-clockwork-touch-5.8.1.3-hercules
is even legit? The version number sounds too high.

that place is where all the custom roms are located... just look over what other people complement or complain about that specific rom. and look for pictures too!
i am not sure about the version you have there. it would be nice if you place a link for us to review it.

its just fakeflash for now, and the Hercules cement is just that, a hercules recovery image. Our phones r similar, but no guarantee it will work. I wouldn't flash it personally

harry_fine said:
I have a rooted Rogers 727R. Installed CWM 5.0.2.7 a few months ago after I rooted it. Installed with ROM manager I think.
However I've found a file called recovery-clockwork-touch-5.8.1.3-hercules which seems to be a later version.
And now, I see people are talking about a touch version, ClockworkMod TOUCH 5.5.0.4 v2. I note from the instructions in the OP you have to use the DD commands, I assume no ROM manager install on top of the current version?
I like to keep up to date. What version should I have?
Thanks
Click to expand...
Click to collapse
Well, CWM and CWM Touch are two different things. If you flashed CWM from rom manager, open rom manager back up and you will see you have the option to also use CWM Touch (It's at the bottom). But from what I've read, there is no official CWM Touch for the skyrocket, but ports have been made. CWM Touch allows swiping rather then using the volume button, but in my opinion, I'd rather just stick to the basics so i don't mess anything up then try to mess with Touch. Just use Rom Manager and update CWM to the latest update...

I'm using the touch port for the SR and it works well the one in Tom manager theoretically should function like cwm for the t989 but remember certain functions don't work as well with the 989. the port has been built for our phones using our trees so should have better functionality on top of not wearing out physical buttons.
Sent from my SAMSUNG-SGH-I727 using Tapatalk

[RECOVERY/BOOTSTRAP] Safestrap for Kindle Fire HD 7" (ON HOLD)

I've decided to put this project on hold as the bootloader has been fixed for the HD8.9/7 (and in theory can be fixed for the KFire2's)
SAFESTRAP v3.05 BETA (2nd-System Bootstrap / Recovery)
** DISCLAIMER: THIS IS A SERIOUS HACK YOU ARE ABOUT TO PERFORM TO THE DEVICE.
DUE TO THE WAY THIS BOOTSTRAP WORKS, THERE IS A POSSIBILITY OF SOFT-BRICKING.
I'M NOT RESPONSIBLE FOR ANY DAMAGE YOU DO TO YOUR KINDLE BY USING THIS TOOL.
YOU DO SO AT YOUR OWN RISK.
If you bypassed the BIG RED letters above, make sure you re-read it and understand that you're installing a hijack which affects the normal boot process of the Kindle Fire HD. If that process is changed in anyway it could lead to a soft-bricked device which will need to be fastboot restored.
FOR NOW THIS IS FOR THE KINDLE FIRE HD 7", LATER I ALSO HAVE A VERISON WHICH WILL WORK ON THE KFIRE2.
Download the APK Here
md5sum: 9e409cf3a9d7d510b5bf19262ecfb6d5
Brief Overview / Instructions for how to use Safestrap:
http://blog.hash-of-codes.com/how-to-safestrap/
KNOWN ISSUES:
Currently there's a bug where when you create and activate a rom-slot, the /sdcard is pointed at the rom-slots "/data" partition. This of course won't have all of your content in it. I'll release an update once that's fixed.
CHANGES:
[11/14] Initial release for KFireHD7
[10/30] Begin testing tablet interface for Kindle Fire's
[10/17] (3.05) Fixed SD card / emmc sharing in recovery (UMS)
[10/17] (3.05) Fixed recovery installation/removal from ROM-slots
[10/14] Updated to v3.04 BETA.
[10/14] Recovery is now based off TWRP 2.2.2.1 (fully featured touch-based recovery)
[10/14] Can create up to 4 Virtual ROM-slots to flash ROMs to and when "Active" ALL TWRP functions affect that ROM-slot (For example: Flashing .zips, Backup and Restore)
[10/14] Nearly instant swapping from ROM to ROM
[10/14] User selectable data partition sizes during ROM slot creation: 1GB, 2GB or 3GB
[10/14] ROM slots are saved on the internal emmc space so that preinstall and webtop partitions are no longer used and shouldn't break OTAs.
[10/14] Charging in recovery
[10/14] Supports "Reboot Recovery" from Android OS
Entry to recovery via Splashscreen on boot-up. The screen stays up for around 8-10 seconds and if you hit the "Recovery" button, it takes you to Safestrap Recovery. You can skip the wait by touching the "Continue" button.
KNOWN ISSUES:
Stock flashing is currently disabled. And this will probably remain this way for the foreseeable future.
SPECIAL THANKS TO:
The entire TWRP team who has built an AMAZING recovery system.
The testers which have helped in past and present versions of Safestrap, knowing that it could mean they brick their devices.
[ SCREENSHOTS COMING SOON ]

Anxiously waiting...

I'll know more shortly once my tester gets back with me.
The proof of concept runs perfectly on my 1st gen KFire where I mocked up the hijack and was able to walk through it w/o fear of bricking.
Sent from my XT894 using Tapatalk 2

Hashcode said:
I'll know more shortly once my tester gets back with me.
The proof of concept runs perfectly on my 1st gen KFire where I mocked up the hijack and was able to walk through it w/o fear of bricking.
Sent from my XT894 using Tapatalk 2
Click to expand...
Click to collapse
Thank you for the hard work as I'm sure you have spent quite a bit of time on this.

For us non tech guys, exactly what is the purpose of this recovery be? To make a backup of what currently have? The ability to flash?
Sent from my SPH-L900 using xda premium

This is custom recovery for flash ROMs and backup/restore.
Sent from my XT894 using Tapatalk 2

This is the best news i ever heard since i bought my KFHD a week ago. I hope it passed the test.

Just to reiterate...
Users cannot go and flash any ROM on their devices...ROMs must be made with the 2nd gen. kernels in mind and any attempt at flashing ROMs made for 1st gen. devices will most assuredly brick one's device, correct?

soupmagnet said:
Just to reiterate...
Users cannot go and flash any ROM on their devices...ROMs must be made with the 2nd gen. kernels in mind and any attempt at flashing ROMs made for 1st gen. devices will most assuredly brick one's device, correct?
Click to expand...
Click to collapse
Yes. No flashing 1st gen device ROMs. Insta brick. Safestrap can't save you from that.
Good news and Bad news on the 1st tests:
1. Good: I found a better hijack point in the new 7.2.1 ramdisk. So I'm adjusting some things and doing some more tests.
2. Bad: The screen is rotated differently on the KFireHD, than it is on the KFire 1st gen. So my touch buttons and stuff aren't working correctly. The next few tests I do will be to show where and how the screen is rotated in relation to the touch controller.
So for now still nothing public.

In the meantime, if any ambitious devs want to start slopping together a ROM to use once this is completely working, that would probably be a good idea. :laugh:

Hashcode said:
Yes. No flashing 1st gen device ROMs. Insta brick. Safestrap can't save you from that.
Click to expand...
Click to collapse
How hard would it be to add a check that makes sure no 1st gen. ROMs, or any ROMs that have modified files that would normally include signed headers, get accidentally installed?
For the most part I'm sure it wouldn't be a problem, but there are those who will try anyway, no matter how many warnings are given in bold red letters.
Not to mention there may be inexperienced (or heaven forbid, malicious) "devs" that might, inadvertantly or otherwise, modify a file with a signed header.

soupmagnet said:
How hard would it be to add a check that makes sure no 1st gen. ROMs, or any ROMs that have modified files that would normally include signed headers, get accidentally installed?
For the most part I'm sure it wouldn't be a problem, but there are those who will try anyway, no matter how many warnings are given in bold red letters.
Not to mention there may be inexperienced (or heaven forbid, malicious) "devs" that might, inadvertantly or otherwise, modify a file with a signed header.
Click to expand...
Click to collapse
I believe that the final product will have such a check.

Well that idea sounds like something twrp would have to integrate. But all the same, hash code, do you have a donation button, you are clearly a valuable member of this device development.
Sent from my Fire HD with root!

Testing Update: We have a solid boot after Safestrap installation which is a plus since we're now injecting the recovery splashscreen into the boot process.
My last test (#3) didn't have a working touch controller during the splashscreen, but I have test #4 ready which *could* load the touch driver and allow for entry, but since it's Halloween and we all have families, I won't know how that works till later tonight.
TODO: I'm working on re-doing the Safestrap theme for 800x1280. I had previously been running a 1280x800 theme but the screen is vertical not horizontal. So the layout will be more phone-style than tablet looking.
But even if it's the default TWRP theme with a few missing images, I'll know if we're in a usable state soon.
Verifying Device: I think we can turn on asserts before flashing ROMs. However, it could be that every single Kindle Fire device is named "blaze_tablet" or "blaze" so that might be less than useful. It will take some testing probably to come up with a solution. The Safestrap APK performs a model check when you click "Install Recovery" (KFTT == KindleFireHD-7) and instantly bails if that's not true, so at least you can't install the wrong devices' recovery.
On the donations: There should be a button under my name on any post which links to my paypal.
However, let's hold off donations till we see some actual results and have a working stock-based ROM to flash which devs can tweak w/o fear of bricking. At that point I'll call it a successful bootstrap/recovery and we can move on to AOSP builds.
I'm not against donations (tho I don't do this for money obviously), I just feel you should already have something in your hands and be happy with it before you give any hard earned money to a dev.

First of all, thanks a lot for your effort. Wish I could donate but Im a minor and live outside US... so its hard to ask for "dollars" here..
One question: this will allow OTG usb somehow or not?
Sent from my KFTT using xda premium

Thanks a lot for working so hard, Hashcode. The updates are really appreciated and I really hope you are successful in opening up the Kindle Fire HD/2,

This is something to look forward to, hope it works out.

So you don't own the HD, hashcode? I will def. send a donation your way if you get this working!
I am trying to understand the way this will work. Is it a bit like a dual boot except with 4 roms? And one must always be running stock? And you can backup and restore all of them with twrp?

Yes, on all of the above.
I should point out that you may not actually want to run 4 ROMs due to emmc size limits (especially KF2).
I keep the stock ROM pure to protect our path to recovery.
Sent from my XT894 using Tapatalk 2

Hashcode said:
Yes, on all of the above.
I should point out that you may not actually want to run 4 ROMs due to emmc size limits (especially KF2).
I keep the stock ROM pure to protect our path to recovery.
Sent from my XT894 using Tapatalk 2
Click to expand...
Click to collapse
Awesome work Hashcode. This sounds similar to how Android is run on the Touchpad. Keeps Webos in its own environment and dual boots Android. Can't wait! :good:

[GUIDE][INFO] The beginner's info thread (aka. the noob helper)

This guide is intended to be an all-in-one resource for people coming to Samsung phones after using other devices. It is a general introduction to the S4 and a glossary/explanation of terms you may see here in the forums.
This thread is slightly out of date but the info is still good, I will be updating again soon!!! Remember to hit thanks if this was useful
Disclaimer "Just because I am trying to be helpful does not make me responsible for anything that you do to your phone. Playing with any of this stuff could destroy your phone"
The layout of this post is as follows:
Welcome
FAQ
Glossary of terms
First off, welcome to XDA
The XDA community is home to the most talented and helpful phone developers on the planet.
These developers spend lots of their free time working on making all of our phones better. You should be nice and respectful to them and follow the rules. WHY? If the statement above isn’t enough reason then think selfishly, the less time they are dealing with redundant questions, the more time they have to develop stuff for all of us!
Help them help you by following the following basic rules:
1.If you are confused or have a question, the first thing to do is READ! Read lots, look things up both on xda and using google.
2.If after searching you still have not answered your question, then post in the Q&A forum.
3.Asking for ETAs on ROMs, updates, etc. is considered rude.. DON’T DO IT!
4.Don’t report bugs to a developer unless:
a.You know 100% that it hasn’t already been reported,
b.You know how to reproduce it
c.You can get a logcat of the problem (more on this later)
Some advice if you are new to all this and don’t want to ruin your phone:
1.Be patient. Don’t be the first or even the tenth person to flash anything. Wait until you see others using whatever Rom or kernel with success.
2.If you have any doubts about what you are doing, read more. Don’t flash.
3.Make sure you are in the forum for your device, not some similar or related device.
FAQ:
Q. Is my bootloader locked?
A. Only if you have an AT&T or Verizon phone
******* Info for AT&T users *******
Q. What is LOKI?
A. Loki is an exploit for phones with locked boot loader that allows us to bypass the locked boot loader in order to install custom roms or recoveries. More Loki info down below
Q. Whats the deal with MF3?
A. MF3 is the current firmware from AT&T that comes on any new phone. Your phone may also auto update to MF3 if you are not careful. MF3 patched the ability to use Loki to install custom roms/recoveries so if you are on MF3 things are much more difficult.
Q. How can I keep my phone from updating to MF3?
A. If you want to avoid the update, you should root your phone and freeze the following three apps using titanium backup or some similar app.
1. AT&T Software update Vxx_x_xxxx_x_x
2. FWUpgrade x.x.x
3. LocalFOTA vx_xxxx_x_x​
Why flash?
by flashing your device you can make your phone act differently, look different, and enable new or disabled options. you could ,for example:
enable native tethering
enable call recording
change the look of your phone
add custom toggle buttons
overclock or undervolt
increase battery life
etc..
Kernel vs Rom vs Recovery vs Modem
Kernel is the layer between the phone hardware and the rom. it controls things like Wi-Fi power, touch sensitivity, possible range of screen brightness, phone logging, and processor max and min speed. kernel must be designed not only for your device but also for the type of rom you are using (Sammy rom or Aosp) some kernels support all roms, others are specific.
Rom is the operating system of your phone. there are three main categories of roms.
roms that are based off of the Samsung stock rom (Sammy rom)
roms that are based off of Android open source project aka AOSP (AOSP, AOKP)
roms based off of the miui project (these used to be a branch of AOSP but recently they have also used Sammy base for miui)
recovery is a partition that you can access at boot by holding down a combination of keys. (volume up and home button in the case of our sgs4) every phone has recovery stock but it doesn't do much. you can replace stock with clockwork mod recovery which is extremely useful for flashing all kinds of things and making backups before you do. There are other alternative recoveries besides clockwork but that seems to be the most common. TWRP is also gaining popularity these days. You can easily switch between recoveries and or upgrade your current recovery. All that needs to happen is for a new image to be flashed onto the recovery partition. See the rooting guide for more info on how to flash a custom recovery.
modem is a file that controls the cell radio of the phone. Helps determine what frequencies to use and settings for a particular network. It is important when flashing a radio that you flash a radio that is for the AT&T sgs4
Methods for flashing files - Odin vs mobile Odin vs. clockworkmod(cwm) vs adb
Odin is the internal Samsung tool for flashing. I believe it only exists on Windows platform. This tool is mostly used to initially flash an insecure kernel or rooted kernel, OR to return to completely stock rom.. Files for flashing in odin generally should end in .tar or .tar.md5 although sometimes they come zipped and the tar is inside the zip. Read more about Odin before using it as it can easily break your phone. !!!as a general rule make sure you never check the "partition" checkbox EVER!!!
Mobile Odin (THIS TOOL DOES NOT SUPPORT ALL S4 MODELS...make sure you check that it specifically works with yours first. I think at this time it works on your phone unless you have locked bootloader but STILL DOUBLE CHECK) is a phone based version of Odin made by the very talented developer Chainfire. It can be installed on a rooted phone and used to flash the same .tar based files as the desktop version. Mobile odin has a few advantages. 1 you can use it from your phone. 2 it can auto root a stock rom (nice if you want to try out a brand new update that has not been rooted yet)
clockworkmod(cwm) or TWRP is recovery based tool that can make backups of your entire phone, flash new roms, kernels etc.., and do many other useful tasks. Once you have this on your phone my guess is that most of your flashing will be done through this tool. The files for flashing through clockworkmod are .zip files.
ADB is the android develpment bridge. It allows for command line interface with your phone through its debugging options. ADB can do most anything as I understand it. In my several years of flashing I have only had to use it once, and i could have waited for someone to come up with another solution. In general as a noob i recommend you stay away from ADB.
open source vs Samsung base(aka Touchwiz or TW) vs miui
Open Source Roms such as AOSP/AOKP are built using Google's open source android code as a base. The developers then add functionality specific to the device. The advantages of these builds are that they often have tons of options built in to the rom that change the behavior and look of the phone. They usually allow you to change the toggles in your notification pull down, change the battery display, make all kinds of adjustments to sounds, vibration etc... Some people also prefer the "vanilla" android look and feel. These roms often provide "bleeding edge" concepts, design, and modifications. The Disadvantages of these roms is that some of the hardware coding is done closed source by the phone manufacturers, which means that things like Infrared, bluetooth, camera, video recording, and MHL video out often don't work or take much longer to get working by the developers. Basically anything that relies on the Samsung framework will not work in an open source build. This means Svoice, Snote, and the Samsung camera app will not work.
Samsung based roms (aka Touchwiz/TW) are taken from the Samsung original phone software and modified by the developer. Usually, these roms are modified in order to be faster and to make changes to some of the features. Expect to see changes to the stock rom like: debloated (ATT and samsung software removed), de-odexed (explained later), enable tethering, unlimited sms recipients, added notification toggles, etc. Most of these changes are made to: make the phone faster, improve battery life, make the phone easier to theme. The advantage of these roms is that they still use the Samsung framework so all the proprietary stuff like camera, bluetooth, MHL still work, the disadvantage is that they will never be as customisable as open source roms.
MIUI is a rom that focuses on theming. Official MIUI (Chinese) gets updated weekly on Friday and then there are lots of miui developers who adapt it to other languanges and make some tweaks to it. MIUI can be built from AOSP source or Samsung source and depending will have different features. The first MIUI rom for our phone just appeared in these forums and it is based off of AOSP. MIUI has a unique look and is also highly customizable through theming. There are tons of themes available for download through the rom itself and you can mix and match any part of any theme you want. This includes icons, lockscreen style, etc.. Some people criticize while others praise MIUI for being very "iphone like". This is because the icons look more iphone like and there is no app drawer in the MIUI launcher. However, you can still use any launcher you like within MIUI.
odexed vs de-odexed
odexed is how the phone comes stock from Samsung. Odexed means that system files and apps are split into two pieces and kept in different places on the phone. This is done to speed things up a bit. However, it makes it harder to theme the phone because the apps are split up. Most custom roms choose to de-odex (basically regroup the files back into one) so that custom themers can make themes more easily for the phone.
Flashing "dirty" vs flashing "clean"
Clean
Doing a clean install of a rom means erasing or formatting all the data from the previous rom before you flash the new one. This is the prefered way to flash a rom to ensure that it will run smoothly. It is necessary if you are switching from one rom type to another (CM to Samsung base). In order to do a clean flash you need to boot into recovery and select the following options: wipe user data (this wipes all apps and personal data, but not your photos/videos), wipe cache, advanced>wipe dalvik cache, storage/mounts>format system. This will ensure that no trace of the former rom is left on the phone. Beware that at this point your phone will not boot until you install a new rom. I suggest using titanium backup to backup apps and smsbackup+ for texts to make getting your new rom configured easy.
Dirty
Doing a dirty install means just flashing a new rom right over the top of the old one without wiping any data. The advantage to this is that you don't lose any apps or account info. The disadvantage is that you open up the possibility for problems. Generally you only want to flash this way if you are upgrading a rom (CM10 nightly to the next nightly, or from one samsung based rom to another). If you decide to flash over the top and have any issues, you should not report bugs, but try flashing clean first.
Logcat
Logcat is a way to access the android system log for everything that is going on behind the scenes. This tool is used to help developers pinpoint problems in a rom. If you want to actually be helpful to a dev when reporting a bug, you should really learn to use this tool. I am no expert on logcat but you can find some good information in this post: http://forum.xda-developers.com/show....php?t=1726238
What is the Bootloader?
The bootloader is basically what it sounds like...it loads the boot image of the device. Basically it is one of the first things to run on the phone and it shows the phone where to find the boot image and how to start. The bootloader is also responsible for allowing access to the recovery part of the phone.
Locked Bootloader?
This seems to confuse a lot of users so here goes: The AT&T and Verizon versions of our phone have a locked bootloader. What does this mean? To the noob, it means that the devs had to figure out how to bypass or unlock this part of the phone in order to be able to boot custom recoveries such as CWM and TWRP. Getting a custom recovery means being able to backup the phone as well as flash custom roms. Luckily for us, Djrbliss (make sure and thank him! his thread is here:http://forum.xda-developers.com/showthread.php?t=2292157) figured out how to bypass the locked bootloader. The exploit he used is known as Loki. Please remember that the loki exploit is not the same thing as unlocking the bootloader, it is a bypass/trick. AT&T and Verizon have fixed the exploit that allowed loki to work in there newest firmware. Loki patch will not work for MF3 firmware or later.
Loki
refers to the exploit that allows us to run custom recoveries as well as custom roms. You only need to have a loki'd rom if you have a model with a locked bootloader (AT&T). Thankfully, you can install a custom recovery that will auto-Loki any rom you flash so that you can install almost any rom built for our model phone (see below). I strongly recommend flashing an auto loki recovery if you have a phone with locked bootloader. I use this one here: http://forum.xda-developers.com/showthread.php?t=2291956
Compatible Roms
you should be able to run any rom built for AT&T, TMobile, or the I9505 international model (NOT I9500!!) as long as you flash with an auto loki recovery. You can check out this thread for more info. Make sure and thank TheAxman! http://forum.xda-developers.com/showthread.php?t=2295557
You may have to manually set the APN. If you encounter problems with the rom look in that roms thread for answers.

Sticky!!

Well damn, I thought I knew a lot, but after reading this thread, I really didn't. Well done. :good:

Incredible resource for those coming in from a different ecosystem.
Thanks much!!

Thread stuck!! Nice work!

Got my new At&t Samsung Galaxy S4 and this will definitely help me!!

this is another thread that really helped me as well these two have really helped me so far i have rooted several divices and just relied on everyone else and not i am starting to take a lot more of an interest ant these threads have been the most helpful
http://forum.xda-developers.com/showthread.php?p=42055644#post42055644

WoW
Great work! I'm sure this thread will be very helpful to a lot of people (Myself included). Tanks bro! :victory:

More! More! :d

I've been searching high and low ive read everything and maybe im not understanding but after I root my phone how do I do the whole loki thing??... I'm eager to start flashing roms... Ive read of some recoveries that do this is that an accurate assessment??

KINGDROID25 said:
I've been searching high and low ive read everything and maybe im not understanding but after I root my phone how do I do the whole loki thing??... I'm eager to start flashing roms... Ive read of some recoveries that do this is that an accurate assessment??
Click to expand...
Click to collapse
What exactly are you trying to do?
If you want to install a custom ROM or kernel, you need a custom recovery. The ROM or Kernel developer will have LOKI-fied it for you.
For TWRP (my custom recovery of choice) Download GooManager from the Play Store and install.
Inside the goo.im app, go to menu>Install OpenRecovery Script
then you can boot into recovery to apply kernels, ROMs, etc to your hearts desire

joeybear23 said:
What exactly are you trying to do?
If you want to install a custom ROM or kernel, you need a custom recovery. The ROM or Kernel developer will have LOKI-fied it for you.
For TWRP (my custom recovery of choice) Download GooManager from the Play Store and install.
Inside the goo.im app, go to menu>Install OpenRecovery Script
then you can boot into recovery to apply kernels, ROMs, etc to your hearts desire
Click to expand...
Click to collapse
Its tht ez just root and add custom recovery??.. The whole loki thing is what's been throwing me off
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

KINGDROID25 said:
Its tht ez just root and add custom recovery??.. The whole loki thing is what's been throwing me off
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Yes... the difficult part is if you are a developer. They make our lives much easier.

joeybear23 said:
Yes... the difficult part is if you are a developer. They make our lives much easier.
Click to expand...
Click to collapse
Thanx ima root tonight I jus need to get a copy of the stock firmware
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

KINGDROID25 said:
Thanx ima root tonight I jus need to get a copy of the stock firmware
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Stock Firmware:
http://forum.xda-developers.com/showthread.php?t=2261573
That is a HUGE download, but the process is simple.

im not a newb but i need to boost my post count lol...soooo spam

KINGDROID25 said:
I've been searching high and low ive read everything and maybe im not understanding but after I root my phone how do I do the whole loki thing??... I'm eager to start flashing roms... Ive read of some recoveries that do this is that an accurate assessment??
Click to expand...
Click to collapse
I have updated the OP to explain Loki, hope that helps :good:

Noob here first time posting I rooted my phone and installed cwm using casual method, created backup and installed mint rom love it but after a couple of post I see I didn't backup EFS should I be worried?

I'm not sure what the deal is with backing up the IMEI number on our phones yet. I have not seen anyone post about losing their IMEI yet so I wouldn't be too worried. On the s3 only the international model phones could be backed up by saving the efs folder. The backup process for AT&T phones was much more complex. I assume the same holds true on the s4. Will update when I find out more
Sent from my GT-I9505 using xda premium

I wanted to make sure Thx. Is it to late to back EFS or can I just restore my backup and do it?

Question TWRP coming?

Just saw the following article from XDA regarding TWRP v3.5 being released. I'm hopeful that this means that for devices that ship with Android 10 that TWRP will be able to decrypt the data partition in order to facilitate a complete backup.
That said, does anyone know how long it typically takes for TWRP to be supported on a new device (i.e. G-Stylus 2021)? Just curious what the norm is. Thanks!

That's a good question. I don't know how long it should take, but after reading the article you linked it seems that successfully porting TWRP to these newer phones will take a lot longer than on the older ones. Hopefully someone's already started working on TWRP 3.5 for the 2021 models, but I haven't heard any actual news on that yet.
I would love to be able to get a full backup of my device in case I really screw something up later on. If I had any level of programming skills I would certainly make an attempt at it myself.

DM.IDOL said:
That's a good question. I don't know how long it should take, but after reading the article you linked it seems that successfully porting TWRP to these newer phones will take a lot longer than on the older ones. Hopefully someone's already started working on TWRP 3.5 for the 2021 models, but I haven't heard any actual news on that yet.
I would love to be able to get a full backup of my device in case I really screw something up later on. If I had any level of programming skills I would certainly make an attempt at it myself.
Click to expand...
Click to collapse
I'd look around on github

THIS is a TEST build for the Moto G stylus XT2115-1 minsk_t
(please mind that i have never done this before and i am at least trying to figure out how to create custom recoveries. i just need a good teacher with a little time. .)​
*Touch Screen does not work. OTG mouse necessary.*
(not too sure how to fix this error)
*Mount points were for testing*
(modied fstab files in ramdisk to fix mount points)
*modified ramdisk and split_image from Moto G 9 plus unofficial 3.5.1 twrp*
https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-g9-plus-odessa.4195729/
i tried to put a recovery together for this device but im not sure where i went wrong or what to do next. booting into this recovery works but /vendor and /system_root have denied permissions. when it is flashed within twrp and rebooted to recovery or system the screen says no OS installed press power to power off. If anyone can help me figure this one out i would be greatly appreciative. If you need anything i can pull from my device just let me know. Anyone willing to help work on this recovery and figure out what needed to be fixed i would greatly appreciate it!
*EDIT*
i got /data to back without digest verification. Was not able to try to restore the backup as i got NO OS error when i rebooted to restore.
*EDIT*
i was able to figure out pretty much everything except the touch part of the recovery. it has a novatek_ts (NVT-ts)
not sure what to do to enable the drivers for twrp. any feed back would be great.
*EDIT*
Found the driver. I'll post it here and see what you can do. I'll also work on it as I'm still learning where stuff should go in the recovery. And also seems to b that i cannot access external sd from twrp either.
*EDIT*
resolved sd card issues. mountpoint was incorrect. only thing left to get working is touchscreen and not have to use otg mouse.
updated twrp for minsk_t is in files now.
*EDIT*
I found the proper elements to configure the recovery's touchscreen capabilities. Will be recompiling later on today. After I have tested it I will post the new working TWRP recovery. Thanks everybody.

*deleted*

sosthenisRR said:
*deleted*
Click to expand...
Click to collapse
So this is fully functioning now right? Is there any reason to use this over the OrangeFox recovery that has been posted?
Also, if I did install OrangeFox, and decided I wanted to install this later, would it be as simple as flashing using fastboot from ADB, overtop of OrangeFox? Or would the procedure be a little more complex?