Develop Bugs

Ox's noob corner (work in progress)- everything you need to get started right here

Well everyone the dinc2 community has treated me well but I have moved on to the htc rezound please do not hesitate to still pm questions though I'm hoping I can find a volunteer to take over this thread. I'll miss you guys cuz for the most part it was a very mature forum and ill pop in once in awhile to say hello. Good luck if anyone would like to give back to this community and take over this thread pm and ill pm a mod. god bless
I thought it maybe fun to have a light and humorous side to this also so everyone keep your eyes out for funny posts that can make our quote of the day:
if you guys see any posts that make you chuckle pm me and I will put it here and credit you for finding it
Anyone looking to root your incredible2 that is on 2.3.4 with the.98 hboot please see here: http://forum.xda-developers.com/showthread.php?t=1298990 then after your hboot is downgraded follow the instructions on rivera82falcons thread,linked below
hey guys I'm attempting to get a thread started to get all the basic info out to the newcomers that they will need to start there modding a flashing journey. I'm also hoping this will help cut down on the repetitive questions and useless posts mucking up our forums. This is and always will be a work in progress, so this is just a start there will be much more info added as time goes on.
First thing if your not rooted yet everything you need to know is in this thread by rivera82falcon http://forum.xda-developers.com/showthread.php?t=1219246
Next up is how to flash a custom rom: http://forum.xda-developers.com/showthread.php?t=1263756 by AgalychnisCallidryas
Another thing is the gingerbread ruu. If your phone comes with froyo I would reccommend following the directions on this page before trying to root because unrevoked is becoming increasingly harder to find. Also this can get you out of some pretty sticky situations if you mess up badly enough: http://www.androidpolice.com/2011/0...8-605-4-same-as-the-official-gingerbread-ota/
wanna try a different radio? Head over to gu1dry's thread: http://forum.xda-developers.com/showthread.php?t=1134451
Its my opinion that every flasher should have adb setup on their computer, it will bail you out of a bootloop, tell you why its happening and do all kinds of other awesome stuff. here is an excellent thread from nephron to get you on your way, its from another phones forums but everything except the drivers apply to us, obviously install the correct drivers for your phone: http://forum.xda-developers.com/showthread.php?t=532719
for those of you who use aosp roms, just about everyone prefers the miui camera over the aosp stock one and here it is with instructions. Thanks pacerguydon: http://forum.xda-developers.com/showpost.php?p=17691395&postcount=11
if your market is missing apps, check this out: http://forum.xda-developers.com/showthread.php?t=1275574 thanks knipp
those of you who want to learn java and general scripting here is a few good tutorials that artvandelay440 dug up:http://forum.xda-developers.com/showpost.php?p=17691710&postcount=13
for the up and coming themers here is where to get brut.alls apktool:http://code.google.com/p/android-apktool/ if anyone can find me a good noob friendly tutorial for apktool let me know and I'll post it.
tommytomato created a fantastic super tool called android utility, you can decompile apks sign them and do all kinds of good stuff. Really the ultimate themeing tool: http://forum.xda-developers.com/showthread.php?t=1167623 if your thinking of doing mods and themes of your own you should check this out, tommy is a modding master and extremely helpful to new themers
wanna changer your splash screen or boot animation? Have a look at 06stangs thread here: http://forum.xda-developers.com/showthread.php?t=1161543
if your running an aosp rom you can change the carrier label here's how: http://forum.xda-developers.com/showthread.php?t=1221882 thanks to artvandelay440
running a sense rom? Go here for a new lockring: http://forum.xda-developers.com/showthread.php?t=1260128 thanks to jwhetstone02
our friend knipp21 has started modding miui lockscreens check it out: http://forum.xda-developers.com/showthread.php?t=1288566
before getting my incredible2 I had an inspire, the one thing I missed about the inspire was 4ext recovery,well now we have it. Big thanks to madmaxx80 for the awesome recovery: http://forum.xda-developers.com/showthread.php?t=1267540
here is a great tool for undervolting, it provides an easy to use gui, please read up on the pros and cons of undervolting before attempting and remember you must have a kernel that supports undervolting to use this. It will not work on the stock kernel. Thanks to chad0989 for this: http://forum.xda-developers.com/showthread.php?t=1190004
here is setcpu a tool for overclocking, your kernel must support overclocking and this should not be used in conjunction with any other overclocking apps. Thanks to coolbho3000 for this, and please guys consider purchasing the donate version of this: http://forum.xda-developers.com/showthread.php?t=505419
here is a very educational thread similar to this one, its from the thunderbolt forums but most of the info applies to us as well. Its a very well put together thread and super informative. I reccommend you guys check it out because its a good read. Big thanks to loonatik78 for putting it together: http://forum.xda-developers.com/showthread.php?p=16695064#post16695064
another thing I would like to stress to the new people, xda has a thanks button, and now you can even use it right from the xda app, don't be greedy with it guys if someone helps you click thanks.
I would like this thread to become a community effort, if there is anything you guys feel should be here dont hesitate to let me know. This is my small effort to give back to a community that gave me so much so I will gladly try to answer any and all questions in an effort to keep our forums clean. No matter how stupid you think the question may be pm me and I'll try to help. I may not always have your answer but will most likely be able to point you in the right direction. see post three for frequently asked questions

Pm me for any and all questions as well.
Sent from my Incredible 2 using xda premium

this q and a section will be a work in progress as well. If anyone has suggestions for questions that you think should be here, by all means let me know.
Q: I think I bricked my phone what should I do?
A: calm down 99 percent of the time people think they are bricked they really aren't. If your device shows any sign of life your chances are good that your ok. If you can access hboot by holding volume down and power while the device is off your in good shape you can still flash the ruu and get back to stock.
Q: I put the ruu on my sdcard but hboot cannot find it
A: when flashing anything from hboot it must be named exactly PG32IMG.zip and yes it is case sensitive. Also if you have to rename the file, if doing it on a computer be careful because a computer will automatically add a .zip to the end of it and hboot will not recognize it.
Q: I flashed a kernel a now my "insert issue here" don't work
A: did you flash an aosp kernel on a sense Rom or vice versa? If so things will not work as they should always make sure the kernel you are flashing is compatible with your Rom.
Q: will sense apps and widgets work on aosp roms?
A: short answer is no
Q: my phone is stuck in a bootloop what should I do?
A: some time in your flashing career you will encounter a bootloop, there are a couple of ways to fix this number one is start adb (which every Rom flasher should have set up in my opinion) and type adb reboot recovery and hit enter then once in recovery you can reflash and try again. Your other option is to pop the battery out, put it back in then hold volume down and power to get into the bootloader once there select recovery. If you can not navigate in the bootloader that means the PG32IMG.zip is on your sdcard still. Remove that and it will let you navigate the bootloader. If you have no way to remove that .zip pop out your sdcard boot into bootloader select recovery then pop your card back in.
Q: what is the best Rom out there?
A: there is none its all a matter of opinion. Just a warning, don't start a new thread asking this question you will be flamed into oblivion and the mods will lock it. I've seen it a million times
Q: I just flashed an aosp Rom (miui, cm7, omgb) why is my earpiece volume so low?
A: as of now this is a known issue for our aosp Roms, the tiamat kernel is said to fix it.
this is the start of my q and a and it is far from complete, if you think there is something important that is not here by all means let me know.
Ok guys here is some basic terms you should be familiar with before rooting and flashing
1. Flash or flashing, basically just means to install something from recovery or bootloader
2. Rom- the word rom is kind of an outdated term (read only memory) because we can in fact write to it, nonetheless a rom in the simplest of terms is basically your operating system.
3. Kernel- the kernel is the heart of your o.s. It basically communicates with your software and hardware, wifi and processor speed are a few examples of things your kernel controls among many other things. Sense kernels should not be used on aosp roms and vice versa things will not work as they should.
4. Overclocking- to increase your processors stock speed to increase performance
5. Underclocking- pretty self explanatory underclocking is used to help save battery
6. Undervolting- to decrease your voltage to save battery. Undervolting is a slightly controversial topic some people swear by it and others say it can actually decrease your battery life. Undervolting can cause stability issues so educateyourself before attempting.
7. Radio- basically the software that works with your hardware to give you your signal and mobile network, on other phones they are also reffered to as modems
8. Aosp- android open source project, aosp roms are roms built from the original google source code, some examples of these are cm7, miui, omgb, these are typically lightweight roms that you can customize yourself, they are preffered by many users because of the great battery life and performance
9. Sense roms- these are roms based on an original htc rom, sense is th ui that htc adds to android, sense roms have many nice apps and widgets, and usually are packed with eyecandy, however many people say that sense it a resource hog and needs a lot more ram to run than aosp roms
10. Port- a port is a rom or theme originally made for another device but made to work with ours
11. Wipe- it is usually recommended to wipe before flashing a rom, but not always mandatory, read the forum of the rom your flashing to see if a wipe is recommended or not. Some roms will wipe data automatically some will not. A wipe is just basically giving you a clean start like when you first got the device and is done in the recovery menu. When in doubt wipe, you will run into less issues.
12. Ruu- an ruu is a stock signed rom that is flashed in hboot, an ruu is your get out of jail free card, if you mess your phone up too bad an ruu will bring your device back to its stock state
13. Hboot_ this is basically your bootloader from hboot you can enter recovery, do a factory reset, and flash an ruu, a radio, and other things not flashable in recovery
there is some more basic definitions that I overlooked, see post 28 by artvandelay440

How about some basic definitions? Sense, AOSP, Rosie, kernel, recovery, md5 sum, etc.
How, when, and why to wipe.
How to perform a battery calibration.
Don't restore system data when moving to a different ROM or updating to a new framework.

ontophantoms said:
How about some basic definitions? Sense, AOSP, Rosie, kernel, recovery, md5 sum, etc.
How, when, and why to wipe.
How to perform a battery calibration.
Don't restore system data when moving to a different ROM or updating to a new framework.
Click to expand...
Click to collapse
yes good idea. Definitely will do. I also plan to add a miscellaneous goodies section including commonly used apps like miui camera. And links to kernels and other good stuff. Like I said this thread is a wip I just wanted to get a start on it tonight. I'm not at home now and I'm doing this on my touchpad so its quite tedious. Will work on it a lot more tomorrow. Thanks for the input

Love this idea for a thread. I know this will be a stop that noobs and even seasoned vets will make. Thanks for taking the time to put something like this together!

Thanks for setting this up!
It's really helpful to us newcomers, who inevitably ask a question that will annoy the seasoned members. There is so much info buried in threads with many pages that it's hard to read it all and not overlook something along the way.
Having all the start-up info, and maybe a list of well-known bugs for each rom, in one place will be great!

Woot! Got a sticky!
Sent from my Incredible 2 using xda premium

+1 For the best idea ever. Great job.

I think you should spice it up a bit I'll add more later lol. Good thread guys.
For the first post you can start it like this:
Rooting your phone (Achieving S-OFF)
Please read and re-read rivera82falcons execellent write up located here:
http://forum.xda-developers.com/showthread.php?t=1219246
Flashing a custom ROM to your device
Please read AgalychnisCallidryas thread on how to manually flash a ROM located here:
http://forum.xda-developers.com/showthread.php?t=1263756
Please note that you don't need to back up every user app with titanium backup, some people only like to backup apps that have data, such as games.
It's also important not to back up system apps (apps that came with the phone). Restoring those apps may cause system failure.
Setting up ADB
Nephron has a full set of instructions on how to set up ADB, you can find the thread here:
http://forum.xda-developers.com/showthread.php?t=532719
Finding the ROM that's right for you
This is one of those threads that may be sensitive to some. I find that finding the best ROM depends on your tastes. When ROMs are released they generally have bugs. Some may be deal breakers, like not having MMS working, or something small like not having a particular tweak installed or an application force closing. You really have to download the ROM and take it for a test drive.
Read through the threads on feedback. Generally, if you see the same bug being mentioned it probably is plagued through every ROM install.
GSM functionality of the phone is important to some, but not most. Generally, if you download a ROM that's based off of the original ROM it should work fine. But if you are downloading a port from another device expect that feature not to work.
Don't be afraid to flash a ROM. The worst that can happen is it will throw your phone into a soft brick (bootloop). Simple way to fix it is restore a backup you made or flash a ROM that you know is solid.
Creating a backup (nandroid) of your device
Your phone at this point must be rooted, and the ROM you are running has to be rooted.
Get Rom Manager from the market. Install the latest recovery that it prompts you with - If you've already installed clockwork mod then proceed.
In ROM Manager:
1. Scroll down to Backup Current ROM
2. Name it what you like, like backup_09192011
3. Let it back up. The more data you have the longer it takes.
In recovery: (You cannot assign names in recovery)
1. Boot into recovery
2. Go to backup and restore
3. Choose backup
To restore a nandroid backup - Wiping data, cache, and dalvik isn't necessary.
1. Boot into recovery
2. Go to backup and restore
3. Choose restore
Useful Applications:
http://androidcommander.com/ great for deleting or replacing apps on the fly. Windows interface, simple to use.

Here are a few more additions:
Replacement camera app for those that don't like to use the stock camera that came with CM 7 or other AOSP Roms.
This Click me Miui camera app works great, just remember to go into the camera settings after installing and select 8mp as the picture size. It can be installed as either a separate camera app or as a replacement to the stock camera.
To install as a add on, just install the apk as a you would any other app. Download to your sd card and install.
To replace the stock camera app, rename the downloaded apk to "camera" (without the quotes) and using root explorer (make sure and select R/W) move the renamed apk to system/app and replace the stock camera apk (first though, make a copy of the stock camera app and add .bak onto the end and store this copy on your sd card, I make a folder named storage so I know where my .bak files are at).
Now that the camera apk is in the system/app folder, the permissions and ownership will need to be changed.
Long press on the camera apk and in the popup menu select permissions,
You will want to change it to look like this:
Read Write Execute
Owner x x
Group x
Others x
After changing the permissions, scroll to the bottom of the popup menu and select "change owner"
You will want to change the ownership so that it reads"
Owner 0 - root
group 0 - root
Select OK and your done. Reboot and you will know have the Miui camera installed.
Wallpapers:
Click me
More to follow later.

Awesome guys keep em coming. I didnt expect this thread to explode so quickly great job guys. Anyonr tutorials or info you guys add i will link to in the op. I will typically update the thread every night around midnight eastern time. Thanks guys.
Sent from my Incredible 2 using xda premium

I always see lots of beginning android users who want to learn Java/xml/whatever to begin building. I made a list of some coding tutorials-they might be of some help to a newcomer who wants to learn.
JavaScript for Android:
http://www.youtube.com/playlist?list=PL34F010EEF9D45FB8
General Introduction to learning Android development:
http://developer.android.com/guide/developing/index.html
General Coding:
http://www.codecademy.com/#!/exercise/0
From around XDA:
making your own boot animations: http://forum.xda-developers.com/showthread.php?t=1096068
ADB workshop and guide, including edited path variables: http://forum.xda-developers.com/showthread.php?p=9959449
How to decompile/edit/sign/recompile apks with APK Manager:http://forum.xda-developers.com/showthread.php?t=695701
how to use APK Edit (apk tool with custom GUI): http://forum.xda-developers.com/showthread.php?t=890199
Editing with NinePatch (.9.png) images: http://forum.xda-developers.com/showthread.php?t=1192207

Great thanks!
Sent from my Incredible 2 using xda premium

Add how to change boot animations and splash screens? (my thread)
Sent from my ADR6350 using Tapatalk

Sure will thanks
Sent from my Incredible 2 using xda premium

oxlong27 said:
Sure will thanks
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Maybe the how to on hulu? I dont think many use it...but it won't take up too much space right and the how to for renting movies from the market (posted somewhere as changing permissions to mu from Su temporarily)
But seriously this is a great job. I didn't expect all this lol. I'm glad we are trying to save our community.
I came to the Eris and it already had a community. We built this one and it needed some leadership. Way to take charge bro
Unlike the Eris all our devs would rather have their own site and that's ok. But ppl haven't been mature about it. I like the devs like tazz and the way he does things. Just the way I am lol.
Sent from my Incredible 2 using xda premium

I never expected it to take off like this either, but im definately glad everyone likes this and will continue to work hard on it thanks again guys. Will update tonight with links to your suggestion
Sent from my Incredible 2 using xda premium

Another thing.
Some questions would be answered of you tried it yourself.
Like "how does this app work" open the darn thing and find put...if you're still lost in the sauce come ask here. Please research and try yourself first.
Sent from my Incredible 2 using xda premium

knipp21 said:
Another thing.
Some questions would be answered of you tried it yourself.
Like "how does this app work" open the darn thing and find put...if you're still lost in the sauce come ask here. Please research and try yourself first.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
yes very good point knipp I want this thread to be informative and educational not a hand holding experience. I have no problem helping anyone that is willing to help themselves but it makes my skin crawl when I see a post that says “wanna root someone please give me detailed instructions" and I have seen a lot of them.

[DEVELOPERS] TWRP Touch Recovery for Epic Touch

Since a lot of people have asked me about TWRP 2 for Epic Touch and SGS2 devices, here's the deal:
1) I don't own an Epic Touch or a SGS2 device of any kind.
2) As some may be aware, many Samsung devices do not have and/or properly use a recovery partition. Instead the recovery is packed as a second ramdisk or as a separate recovery.rc in the same ramdisk in the boot image. This means that every time you install a new ROM or kernel, you will get stuck with whatever recovery is included with the boot image.
3) We do have a process that lets you inject TWRP into boot images that are still using the dual ramdisk setup typically found in CM7 boot images. I believe that somewhere along the development path of CM9, the boot image packing method changed to a single ramdisk with 2 init files (recovery.rc). This type of setup is much more difficult (if not impossible) to do "injection" and since I don't have a device in hand to work with I have no plans to attempt to create an injection method for this new type of boot image. The injection process still appears to work on CM7 boot images and some kernel devs for SGS2-type devices have not moved to the new method (yet).
4) We now have code that compiles in CM9. This new code base is much simpler to get started with - you just replace the bootable/recovery folder with the TWRP source code and grab a copy of our slightly modified 1.20 busybox code and you're ready to compile TWRP after adding a few build flags to your BoardConfig.
5) The TWRP source code is all public, including the GUI. It's pretty easy to compile and work with and we have a nice guide to help you out here: http://tinyw.in/nP7d
If you need help integrating TWRP into your builds or have questions about compiling TWRP, feel free to find us in #twrp on Freenode. TWRP works very well with thew GooManager app and if you host your ROM on http://goo.im, your users can receive notifications of ROM updates and easily download and flash the update almost like a regular OTA update. In addition, http://goo.im now supports automatic differential zip creation. You upload an update to your ROM and goo will create a zip with just the changes. Your users get smaller downloads, faster installs, and less wear and tear on the device since only the updated / deleted files get replaced, but this functionality is only easy to use with a supported recovery like TWRP. Please consider adding TWRP to your builds and using http://goo.im and GooManager! All of this functionality is free to you and your users!
If you're feeling really adventurous, you're welcome to install this for the Epic Touch after installing a copy of CM7. I was told by a tester that it was working fine but use at your own risk and be prepared to Odin / heimdall a working boot image if something goes wrong! Note that backups and restores done in TWRP / CWM are not easily interchangable!
http://goo.im/devs/OpenRecovery/epictouch/openrecovery-twrp-2.1.2-epic4gtouch-signed.zip
I can probably create the same kind of a zip for SGS2 International if someone is willing to stop by #twrp on Freenode to test it. I do know that someone has successfully tested a ramdisk on the SGS2 with Exynos so TWRP should work on this device with relative ease.
Also note that it appears for the time being that most Samsung devices released in the USA where all team win members live, are going to be using Qualcomm chipsets instead of Exynos. This means that the only Samsung device that's readily available in the USA that uses the new boot image methods is the Epic Touch. We have a release for the AT&T Galaxy Note and Skyrocket but both of these devices use the Qualcomm chipset which uses a "normal" and separate recovery partition.

No idea what this is about but I got the second post! Woot

Thanks for letting us know about this but we don't have a working cm7 anyway.... do we? I haven't seen one. Also, if I'm reading this correctly, it seems to me any dev who wanted to could repack twrp in any Rom at release. But why would they? Not to take away from the work done by all the twrp team but when I had it on my evo shift it was buggy and rarely formatted everything properly. Has this been fixed or was it a device specific issue?
Sent from my SPH-D710 using xda premium

abadasstanker69 said:
Thanks for letting us know about this but we don't have a working cm7 anyway.... do we? I haven't seen one. Also, if I'm reading this correctly, it seems to me any dev who wanted to could repack twrp in any Rom at release. But why would they? Not to take away from the work done by all the twrp team but when I had it on my evo shift it was buggy and rarely formatted everything properly. Has this been fixed or was it a device specific issue?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
There is a working CM7 for the E4GT. It's posted over at Rootzwiki. TWRP worked fantastically on my Evo and Evo 3D. Glad to see we have another option besides CWM. Hopefully we can get past the bricking issue with ICS roms and I can throw this on my phone permanently.
Thanks Dees_Troy!

Agree worked awesome on my e3d looks to be great
Thanks for this
Sent from my SPH-D710 using xda premium

Team win ftw!!
Sent from my SPH-D710 using xda premium

I love using TWRP and goo.manager on my cm9 touchpad. So easy to use. Glad our amazing devs have more options.

Just wanted to say I used TWRP on my 3D and Nexus S and was my favorite recovery hands down. Would love to see it come to the Epic Touch.
Sent from my SPH-D710 using Xparent ICS Blue Tapatalk 2

I'm going to second everyone that likes twrp. I also enjoyed the recovery very much and it was the one thing I missed when moving to e4gt. I can't wait for source on ICS. If someone doesn't build it into a kernel, I'll be doing some kernel research and building it for myself.
Sent from my SPH-D710 using Tapatalk 2

This is great news I'm tired of not having a working recovery on ics

abadasstanker69 said:
Thanks for letting us know about this but we don't have a working cm7 anyway.... do we? I haven't seen one. Also, if I'm reading this correctly, it seems to me any dev who wanted to could repack twrp in any Rom at release. But why would they? Not to take away from the work done by all the twrp team but when I had it on my evo shift it was buggy and rarely formatted everything properly. Has this been fixed or was it a device specific issue?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
first off the evo shift is an older lower end phone, so performance on any recovery besides cwm which is so basic is probably iffy. TWRP has been pretty amazing on the evo3d and also on my Gnex, and if it gets ported in any working for on the e4gt id be happy to use it for my wife's phone.
if i understood this correctly, twrp recognized the issue with a constant recovery on the e4gt, and they are basically giving us the source to build it into our roms instead of the the stock recovery, so its atleast there on install. it would be nice to see the developers working on cm9 on this phone integrate it into the rom.

This does sound like a step in a good direction but I have to ask....
How do we not have working recovery? It takes literally 45 seconds extra to flash EL26 and then reflash current after the backup is made...sure it isn't "ICS recovery" but it's the result I'm interested in..
are we this lazy that a less-than-one-minute procedure is worth whining about?
Not taking a shot at anybody.. just sayin. I see people complain about this more than anything and they could have made 10,000 backups with the time that they were posting complaints about it.
Especially now that stock kernels can flash...let's let it go.

Kebetz said:
This does sound like a step in a good direction but I have to ask....
How do we not have working recovery? It takes literally 45 seconds extra to flash EL26 and then reflash current after the backup is made...sure it isn't "ICS recovery" but it's the result I'm interested in..
are we this lazy that a less-than-one-minute procedure is worth whining about?
Not taking a shot at anybody.. just sayin. I see people complain about this more than anything and they could have made 10,000 backups with the time that they were posting complaints about it.
Especially now that stock kernels can flash...let's let it go.
Click to expand...
Click to collapse
i want a working one already because i dont have the means to get mobile odin, and im rarely home, i came from the og epic and most of my flashing was done on the go. Now im lucky to update my rom once a week. A working recovery that wont brick my phone is a huge plus for people on the go

Kebetz said:
This does sound like a step in a good direction but I have to ask....
How do we not have working recovery? It takes literally 45 seconds extra to flash EL26 and then reflash current after the backup is made...sure it isn't "ICS recovery" but it's the result I'm interested in..
are we this lazy that a less-than-one-minute procedure is worth whining about?
Not taking a shot at anybody.. just sayin. I see people complain about this more than anything and they could have made 10,000 backups with the time that they were posting complaints about it.
Especially now that stock kernels can flash...let's let it go.
Click to expand...
Click to collapse
I don't mind flashing the EL26 Stock CWM kernel at all. With Mobile Odin it literally takes a minute tops. But I like having the best on my phone and IMO the best recovery out right now is TWRP. It's always worked REALLY well for me. Not one single issue ever. Add in the other features, like compressing backups to save space which may not be a big deal with this device but anyone who's used Sense 3.0 could testify how awesome that feature is. Along with being able to theme every aspect of the recovery and as a themer I just love that option. That's just to name a few. So again, in my case it's not about being lazy but more about wanting the best available for my phone. So if TWRP is a possibility I would love to see it.

I have to agree with tiffany. It is more about the recovery itself. I use mobile odin and take no issue with the current methods but I also would like to have TWRP running on my phone. Hopefully source is released soon and we can take advantage of this. Thank you for posting the links for it and hopefully one of our devs can help to make this happen.

Ok, I admit, odining back to el26 isn't something to complain about for normal flashing. But when trying to alter system files to get the result you are looking for can become somewhat frustrating when a boot loop occurs. Normally a battery pull and a quick flash gets you back in the game. In my experience though, as I'm sure other cracks flashers can agree, sometimes you just have to flash something new, right before you step out the door. Lo and behold you realize you have just set yourself up for failure, failure to boot that is. As I stated in another thread, a lot of folks have busy lives and don't spend every moment reading xda, all they want to do is grab what's hot and flash it with the same procedure as every other Android device that they have come to know and love. In my opinion, working recovery = happy forums. And soon enough we will, and when we do, I want to be sporting TWRP.
Sent from my SPH-D710 using Tapatalk 2

Why all the fuss over something that you use for 5-10 minutes when you flash a ROM, theme, etc.? How much time are you spending in Recovery?
The next thing you know people will want the "Download" mode to be themed and "prettied up" too.
Does anyone remember what it took to customize phones 4-5 years ago? Oh wait, this is XDA, I forgot it's the land of "gimme gimme gimme" and hardly ever about "thank you" or "how can I help you with that?". Users just want to be "alpha" testers so that they can have the newest, hardly do they ever upload logcats, dmesg logs, or help in troubleshooting.
-Daryel

daryelv said:
Why all the fuss over something that you use for 5-10 minutes when you flash a ROM, theme, etc.? How much time are you spending in Recovery?
The next thing you know people will want the "Download" mode to be themed and "prettied up" too.
Does anyone remember what it took to customize phones 4-5 years ago? Oh wait, this is XDA, I forgot it's the land of "gimme gimme gimme" and hardly ever about "thank you" or "how can I help you with that?". Users just want to be "alpha" testers so that they can have the newest, hardly do they ever upload logcats, dmesg logs, or help in troubleshooting.
-Daryel
Click to expand...
Click to collapse
Sure this is true of some but I get thanked all the time for the work I do. There will always be the gimmie gimmie gimmie people, no matter what your doing.
And yeah if I could theme download mode I probably would. Just the way I am.

graffix31 said:
I love using TWRP and goo.manager on my cm9 touchpad. So easy to use. Glad our amazing devs have more options.
Click to expand...
Click to collapse
For those who haven't seen this in action, its worth a look. It is nice to open up goomanager and see all of the latest ROMs and versions that are hosted in goo. You can select the ROM you want and the script flashes it for you and IT WORKS! It is very slick. I would love for a dev to take this on!

Would love to see a themed download mode
Sent from my SPH-D710 using Tapatalk

A way to change roms without having to install everything again

ok so i know you can backup your apps through titanium or rom toolbox or something else but what i want to know is there a nandroid like backup that backups everything but the rom...so i can freely switch the rom as i like and then tap 1 thing and have all my apps, data, settings, lock screen / background photos, etc etc back in place. basically what i want to accomplish is to be able to swap roms...is that something that is out there or at least an idea that is the works / maybe something someone would see and have the motive/skill set to make for us. i believe it would be an amazing tool. just go into cwm and not have to wipe data or anything else, just select new rom and the cwm would take care of everything, deleting the rom you have installed and replacing it with the new rom.
any information would be greatly appreciated.

Unless the rom you're running has an update based on the same build and all its features on the update are compatible with your current rom, what you're asking is not possible, every rom or software our devs make made by compiling files and scripts, that take tame to decompile then put back together to make things work properly if not close to it unless you read, if you read the installation suggested methods and it says DO A FULL WIPE, in order to have a successful installation, unless you want a 500$ paperweight, keep on dreaming on your cool idea
Sent from my SGH-T989 using Tapatalk 2

It would be a nice idea and make things a lot easier, but as suprakarma said it's unfortunately not possible. This is probably the biggest reason I don't flash custom ROM's. It's fast to wipe, format and install a new ROM. But then takes time reinstalling and setting up everything again, just like if you were to get a brand new phone.
If I have time on a weekend or am bored then I have given it a try in the past, but with 2 kids and always being on the go it's just not an option to play around with my settings so I just stick with stock. Everything works, everything is set the way I like and I don't have to keep wiping/installing and reconfiguring everything again.
I am missing out on a lot of great ROM's though and would love to give some a try even if for a couple days. Just not in the cards at the moment. Peace.

thank you i didnt think it was possible but was just thinking that it would be cool, like when you go to install a new rom, it would do a backup of your info/data on to your sd card then do a full wipe, install the new rom and then insert your info/data so everything is the way it was (when i say info/data i mean like photos, music, contacts, texts, wifi passwords, apps, so basically combine titanium with cwm and have it all run together in nice move)

suprakarma said:
Unless the rom you're running has an update based on the same build and all its features on the update are compatible with your current rom, what you're asking is not possible, every rom or software our devs make made by compiling files and scripts, that take tame to decompile then put back together to make things work properly if not close to it unless you read, if you read the installation suggested methods and it says DO A FULL WIPE, in order to have a successful installation, unless you want a 500$ paperweight, keep on dreaming on your cool idea
Click to expand...
Click to collapse
I actually don't really agree with this post. First of all, I don't think you can create a paperweight by restoring a /data partition.. this just sounds like fear-mongering (I often try doing an advanced restore of /data just in case - It often causes problems, but sometimes it works perfectly and everything is as it was before I flashed).
I think the OP has a great idea, and I think it is entirely possible. In all honesty though.. although I am a software developer, I am not an android dev, so I could just be talking tripe.
We all know that some apps can be restored along with their data across roms and even across roms with a different Android OS. The problem is that there is some data that is not. What we need is a mechanism (perhaps an app) that will identify and 'export' metadata for the system data that is potentially not compatible. Of course, it wouldn't be able to export passwords for accounts etc, but those could be easily re-entered during an "import" of this metadata and could in fact perform all the manual installation and data entry (usually done by the end-user) in an automatic way.
Theoretically, data content shouldn't need to be changed, just the way its stored/read/written, so it might just need to get reformatted with each new rom (there may be exceptions of course).
Practically speaking, this is a beast of a project, and may not be feasible for any dev to undertake. It will likely cause more grief to end-users than anything until all the bugs are worked out (which may be never) and will be difficult to maintain across many devices.
Just wanted to point out that it could be possible in thoery. I would love to hear arguments to the contrary though (love to learn!)

As long as new devices keep on merging they become less development Friendly, and in order for this to be possible, every ROM would need to be equal, meaning no room for development choices, and this feature would need to be on a specially made recovery, what this idea means is to disclosure a nandroid backup, leaving only what is needed for the new ROM, this may have been plausible on gingerbread, and there are much more rom development in progress for developers in order to make what we have to work properly if not close to it instead of working on a project like this, therefore, at least for our device is not possible and there are many threads of users bricking their devices by not following instructions, whipping correctly, not reading etc and I stand for my statements without meaning to flame
Sent from my SGH-T989 using Tapatalk 2

[OFFICIAL][RECOVERY] Cannibal Open Touch v3.0 Alpha Builds (latest: Alpha 9)

Cannibal Open Touch 3.0 Alpha 9
Disclaimer:
While we try to test our work as much as possible, it is always a possibility that something could go wrong and screw up your phone. We are not responsible for any damage that is done to your device, either directly or indirectly, as a result of using Cannibal Open Touch or any other Project Open Cannibal projects. Any damage done to your device is your responsibility and your responsibility only. We do this for fun, and we simply like to share our work.
What is Cannibal Open Touch?
Cannibal Open Touch is a custom recovery (like ClockworkMod or TWRP), created purely out of love for the platform and the desire to contribute something cool to the community. The name embodies everything that Cannibal Open Touch is. We take what we believe are the best features of popular recoveries like TWRP and ClockworkMod and, well, cannibalize them along with rolling out our own features.
Features:
Full Touch UI
Complete theme support, including app for management of themes (we'll get to that in a sec)
On-device backup and restore
Backup and restore via ADB
Much much more planned!
Bugs:
During installation, the standard Android installing icon gets displayed instead of the custom dialog box.
If you find a bug, please do not report it here! Instead, report it in the GitHub repository!
Screenshots
See the Screenshots tab above. (Or click me if you're using Tapatalk!)
Nandroid has been replaced!
Nandroid is in fact gone, and has been replaced with a much more robust backup solution. Backups can now be made either with ADB (the recommended way) or via the new Backup and Restore item in the main menu. Backups made via the built-in menu can be copied to a PC and restored via ADB, and backups made via ADB can likewise be copied to your device and restored using the Backup and Restore menu.
Code:
adb backup -f mybackupfilename.ab boot system data cache
You can also restore said backup by using adb, like so:
Code:
adb restore mybackupfilename.ab
Downloads:
Cannibal Open Touch hlte builds (latest: CannibalOpenTouch-2.99.9a_hlte.img)
How to install:
Download the latest Alpha image
Copy the image to your sdcard
Flash the image with dd using adb shell or a terminal emulator
Code:
dd if=/sdcard/<path to image> of=dev/block/platform/msm_sdcc.1/by-name/recovery
(may require entering su prior to running dd depending on rom and configuration)
Boot into recovery mode
Alternatively, you may flash using the zip option (available at the same download location) from pre-existing recovery.
Changelog:
3.0 Alpha 9 (2.99.9)
Real menu scrolling! (but volume keys still work)
All backup/restore operations now verify that you want to take action
Resized UI to be more usable on all device resolutions
Themes can now display a battery charge indicator (depends on individual theme settings)
3.0 Alpha 8 (2.99.8)
Not released
3.0 Alpha 7 (2.99.7)
On-device backup and restore
3.0 Alpha 6 (2.99.6)
Complete theme support
Recovery settings (Theme settings and Unsigned ZIP flashing)
The preceding list is not 100% complete. See the project source code page for the full commit list.
Cannibal Open Touch themes app:
We are currently seeking Alpha testers for an app that will let users download and choose themes without rebooting to recovery mode. Currently there are 20 slots open. If you wish to join please PM me. The only requirement is you must have a Google+ account and are willing to submit proper bug reports, should any arise.
Cannibal Open Touch Themes:
You can now make your own themes for Cannibal Open Touch! See the example themes (it's pretty self-explanatory). Themes must be installed in /sdcard/cot/themes/theme_name (or /data/media/cot/themes/theme_name) in order to work. Please feel free to submit pull requests to have your custom themes added to the theme repository. They will also be packaged and made available to download via the Cannibal Themes app (mentioned above)!
Contribute to Project Open Cannibal
If you like our work and want to see more, consider a donation to the project!
Project Open Cannibal gerrit: http://review.projectopencannibal.org
Credits:
tdm, for the superb touch code (and lots more)
drewwalton19216801, for helping to spearhead the project and forward porting most of our old functions
thenameisnigel, for picking up our webhosting while Drew was gone and assisting with device ports
anyone else who has ever contributed to any Android-related project
XDA:DevDB Information
Cannibal Open Touch, Tool/Utility for the T-Mobile Samsung Galaxy Note 3
Contributors
Sblood86, drewwalton19216801, thenameisnigel, tdm, CyanogenMod, Koush and many others
Version Information
Status: Alpha
Created 2014-10-28
Last Updated 2014-10-27

You will notice the image and zip are marked with an a after 2.99.9, this is because I had to re-enable overlays for qualcomm devices to display a screen (they were disabled for screenshots), the version is still 2.99.9
I'm not opposed to uploading an odin package but honestly do not know how to create one (not being an odin person) if someone would like to assist with this I'm available.
Heimdall could also be used to flash the image, if someone has the exact syntax I will add this to the OP.
I understand gsm builds for the Note3 are unified so I would expect this will work on other versions but am not posting it to the others until someone can confirm this. I only have a tmo tester at this time.

Looks interesting will test later

Did anyone test?

So far it made a backup on my sprint note 3 but didn't restore the data correctly. I had to reboot recovery after wiping the phone for the backup to show up
Sent from my SM-G900P using Tapatalk

wormy987123 said:
So far it made a backup on my sprint note 3 but didn't restore the data correctly. I had to reboot recovery after wiping the phone for the backup to show up
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
Yeah I saw Drew and Ryan were discussing this in our dev hangout earlier. Not sure if they figured anything out yet or not; will catch up here in a bit. Sorry for the delay on my part, I was sleeping.
Edit:
Just spoke with Drew, we need a backup log to troubleshoot this (for some reason I thought they got one already).
After running a backup, before rebooting you can pull the log using adb.
Connected to your computer (with working adb drivers) please run the following
Code:
adb pull /tmp/bu.log
Since the logs are stored in tmp you have to pull it before rebooting or it will get erased.

Ok I'll do that when I get home
Sent from my SM-G900P using Tapatalk

I can confirm that it works on the international version (N9005).
Didn't play around much. But it successfully flashed a couple of zips I tried.

I like this a lot. Really great job you guys did
Sent from my SM-N900T using XDA Free mobile app

Fantastic job guys! I'm intrigued... making some quick backups now (just to be safe), then I'll be trying this out. I wish I had the dedication to make something like this, but sadly, all my projects seem to end up half-finished and forgotten lol.
Just to be sure, since it is an Alpha, this is reversible, right? No permanent changes, can always go back to another Recovery? Not that I doubt you guys or the work you've put into this, just gotta ask....
edit: "Created 2014-10-28, Last Updated 2014-10-27".....
This Recovery can time travel??? [emoji15]
Now I'm really impressed! Lol
~★astra petas★~

Morningstar said:
Just to be sure, since it is an Alpha, this is reversible, right? No permanent changes, can always go back to another Recovery?
Click to expand...
Click to collapse
Flash Cwm recovery via ODIN and you are good to go

joluke said:
Flash Cwm recovery via ODIN and you are good to go
Click to expand...
Click to collapse
Figured as much, just had to make sure. Downloading now...
~★astra petas★~

Well, it looks like a decent Recovery, but unfortunately I ran into a serious problem, which I'm still trying to recover from (an hour and a half in). Here's what happened....
I flashed Cannibal, no problems there, booted into it and was just kind of poking around. Then I figured I'd go ahead and do a quick backup/restore, just to see how well it worked. In hindsight, I'm almost positive there wasn't enough open space on my internal storage to back up my Data partition (which is approaching 5gb), so I'm thinking that may have been the cause of things. That's just a guess though.
Anyway, it seemed to be backing up just fine. I watched it go all the way from 0% to 100% on System, and from 0% to 18% on Data, at which point I set the phone next to me and went to work on something on my computer. Around 30 seconds later I noticed the screen flash out of the corner of my eye, so I looked at it and it was back to the main Cannibal screen, even though it should've taken 8-10 more minutes, assuming the percentage rate shown is accurate. I didn't see any sort of errors or warnings or anything, so I figured what the hell, and started to restore the backup I had just made.
System seemed to restore just fine, but as soon as it started restoring Data, the phone reboot itself back into Recovery. Trying to restore the backup again had the same results, so next I tried just booting normally. It looked like it was booting alright for a minute, my boot animation played, and the LED was doing it's thing (gotta love Shinto kernel), but that's as far as it went. It just kept replaying the boot animation, never actually booting into Android (and the LED stopped doing it's thing). Let it sit like that for 15 minutes, then gave up.
Next thing I did, was Odin'ed TWRP back on, figuring I'd just restore one of my TWRP backups (I have 2 recent ones that I've restored more than once, so I know they're good). It flashed fine, booted up into Recovery, did a factory reset, since it was now saying I had 0mb free on my internal storage, and did a restore. Things looked alright, watched my boot animation play through then on to the 'Android is updating' screen, which went through all my apps, only to flash that SystemUI force closed for a fraction of a second, then went back into my boot animation, did the updating thing again (showing 13 fewer total apps this time), rinse and repeat. As I said, I'm positive the backup is good, as I've restored from it 4 or 5 times.
So...back to Recovery (TWRP now), and everything I try to do fails; install a clean ROM, fix permissions, wipe, you name it. Finally, after dicking around with various things in TWRP, trying to restore partial backups, manually copying system files, etcetera, I was able to get a ROM to install. Now I'm just in the long, arduous process of putting the ROM I was using back, and restoring things item by item to make sure nothing else funky is going on.
I'm not new to this, by any means, so I know it wasn't due to something stupid I might have done. The only thing I can figure that might've caused it is trying to do a backup without having enough free space on my internal storage, which, ok, is kind of stupid of me, but I would've expected an error or a failure or something, rather than the almost 2 hour debacle I've now been through. lol
Anyhoo, sorry for the novel. I figure'd it would be best just to describe everything thoroughly, in the hopes that someone might read it and figure out what caused it, so others don't have to go through the same thing.

Morningstar said:
Well, it looks like a decent Recovery, but unfortunately I ran into a serious problem, which I'm still trying to recover from (an hour and a half in). Here's what happened....
I flashed Cannibal, no problems there, booted into it and was just kind of poking around. Then I figured I'd go ahead and do a quick backup/restore, just to see how well it worked. In hindsight, I'm almost positive there wasn't enough open space on my internal storage to back up my Data partition (which is approaching 5gb), so I'm thinking that may have been the cause of things. That's just a guess though.
Anyway, it seemed to be backing up just fine. I watched it go all the way from 0% to 100% on System, and from 0% to 18% on Data, at which point I set the phone next to me and went to work on something on my computer. Around 30 seconds later I noticed the screen flash out of the corner of my eye, so I looked at it and it was back to the main Cannibal screen, even though it should've taken 8-10 more minutes, assuming the percentage rate shown is accurate. I didn't see any sort of errors or warnings or anything, so I figured what the hell, and started to restore the backup I had just made.
System seemed to restore just fine, but as soon as it started restoring Data, the phone reboot itself back into Recovery. Trying to restore the backup again had the same results, so next I tried just booting normally. It looked like it was booting alright for a minute, my boot animation played, and the LED was doing it's thing (gotta love Shinto kernel), but that's as far as it went. It just kept replaying the boot animation, never actually booting into Android (and the LED stopped doing it's thing). Let it sit like that for 15 minutes, then gave up.
Next thing I did, was Odin'ed TWRP back on, figuring I'd just restore one of my TWRP backups (I have 2 recent ones that I've restored more than once, so I know they're good). It flashed fine, booted up into Recovery, did a factory reset, since it was now saying I had 0mb free on my internal storage, and did a restore. Things looked alright, watched my boot animation play through then on to the 'Android is updating' screen, which went through all my apps, only to flash that SystemUI force closed for a fraction of a second, then went back into my boot animation, did the updating thing again (showing 13 fewer total apps this time), rinse and repeat. As I said, I'm positive the backup is good, as I've restored from it 4 or 5 times.
So...back to Recovery (TWRP now), and everything I try to do fails; install a clean ROM, fix permissions, wipe, you name it. Finally, after dicking around with various things in TWRP, trying to restore partial backups, manually copying system files, etcetera, I was able to get a ROM to install. Now I'm just in the long, arduous process of putting the ROM I was using back, and restoring things item by item to make sure nothing else funky is going on.
I'm not new to this, by any means, so I know it wasn't due to something stupid I might have done. The only thing I can figure that might've caused it is trying to do a backup without having enough free space on my internal storage, which, ok, is kind of stupid of me, but I would've expected an error or a failure or something, rather than the almost 2 hour debacle I've now been through. lol
Anyhoo, sorry for the novel. I figure'd it would be best just to describe everything thoroughly, in the hopes that someone might read it and figure out what caused it, so others don't have to go through the same thing.
Click to expand...
Click to collapse
Easiest solution is to odin back to stock then flash twrp via odin. Then restore your backup. Would have been much faster.

pyraxiate said:
Easiest solution is to odin back to stock then flash twrp via odin. Then restore your backup. Would have been much faster.
Click to expand...
Click to collapse
As I have quated from his post, he did do that.
Morningstar said:
Next thing I did, was Odin'ed TWRP back on, figuring I'd just restore one of my TWRP backups (I have 2 recent ones that I've restored more than once, so I know they're good).
Click to expand...
Click to collapse
That was quite an interesting read, man.
Glad you got out of it.
I would personally have just got fed up and flashed a stock rom through odin.

FeralFire said:
As I have quated from his post, he did do that.
That was quite an interesting read, man.
Glad you got out of it.
I would personally have just got fed up and flashed a stock rom through odin.
Click to expand...
Click to collapse
I would've too, but didn't feel like downloading a stock ROM, and thought it would be a fairly quick fix. I've messed things up plenty of times, but I've never had anything quite like that happen.
And just to be clear, I'm not saying it was due to any problem or bug in Cannibal, nor do I want to dissuade anyone else from using it. As far as I can tell though, the only "mistake" I made was trying to do a backup to the internal storage without having enough free space, so the devs may want to take a look at things just to be sure there isn't some nasty bug lurking there. :good:

Morningstar said:
I would've too, but didn't feel like downloading a stock ROM, and thought it would be a fairly quick fix. I've messed things up plenty of times, but I've never had anything quite like that happen.
And just to be clear, I'm not saying it was due to any problem or bug in Cannibal, nor do I want to dissuade anyone else from using it. As far as I can tell though, the only "mistake" I made was trying to do a backup to the internal storage without having enough free space, so the devs may want to take a look at things just to be sure there isn't some nasty bug lurking there. :good:
Click to expand...
Click to collapse
They are aware of the bug and I believe are working with a dev up stream to fix it. I to encountered the same error
Sent from my SM-N900P using Tapatalk

no update?

It is in T-mobile forum but download link says HLTE... Can i flash this to HLTE? i mean international hlte SM-N9005?
Also, i saw it an .iso file, whereas other recoveries i flashed like cwm and philz are .zip file (like all flashable android files i've flashed till now).
Can you enlighten me, plz?

ryanrazer said:
It is in T-mobile forum but download link says HLTE... Can i flash this to HLTE? i mean international hlte SM-N9005?
Also, i saw it an .iso file, whereas other recoveries i flashed like cwm and philz are .zip file (like all flashable android files i've flashed till now).
Can you enlighten me, plz?
Click to expand...
Click to collapse
The .IMG file you would use while the phone is booted up. Using an app like Flashily
Sent from my SM-G900P using Tapatalk

Question Opinions about preferred custom roms differences and why do you choose it ?

Wanted to keep a thread for each one opinion on custom roms and why do you choose the rom you are using?
i have tried al custom roms and i always love to flash different ones,
What do you notice regarding stability? performance? battery ? bugs? etc in the rom you are using.
Love to hear all your opinions on this matter.

last time i flashed a custom ROM 10years ago. No need to flash anything since. All factory stock.
All i did for every phone is bloatware removal via ADB

I've only ever used the stock rom since I've had this phone. Using A11, A12 and now A13.
Only 1 annoyances during my time with this phone and stock ROM. ( Camera related blue light bleeding in a very bright artificially lit scenario )

Always stock rom with Root these days

Holy smokes. It's ok to not answer a question if it doesn't apply. Pardon my double negative.
I've been contemplating moving on from to stock to custom, when I came across this thread and thought, well this will be great; several viewpoints about several custom roms, but instead came across a few responses that didn't answer the question that was asked.
It's hard to sift though the roms' threads because, in most cases, you'll see "this is a great rom, everything works perfectly", almost immediately followed by "stuck in a boot loop", "looks like msm again", or "xyz is borked, please fix".
So, to reiterate og's question, what are the thoughts on the custom roms (not stock) for the 1+9pro (not a device from your past)?

Nameless seems to be the most stable out of the custom roms, but lacks more in depth customization. CrDroid and Watchdog are better for customization, but more features usually means more bugs.
I've tried tons of the roms on here and will probably continue to do so as stock OOS just doesn't do it for me. Battery isn't ideal, and aesthetically it's hard to configure to what I like. It definitely works for a lot of people as it has many features and is mostly stable.

kodayoda713 said:
Nameless seems to be the most stable out of the custom roms, but lacks more in depth customization. CrDroid and Watchdog are better for customization, but more features usually means more bugs.
I've tried tons of the roms on here and will probably continue to do so as stock OOS just doesn't do it for me. Battery isn't ideal, and aesthetically it's hard to configure to what I like. It definitely works for a lot of people as it has many features and is mostly stable.
Click to expand...
Click to collapse
You favor nameless I'm guessing?

It depends on the day honestly. I have a disease, haha. As of right now that's what I'm using. But I'm sure I will flash something else here in the next week.

kodayoda713 said:
It depends on the day honestly. I have a disease, haha. As of right now that's what I'm using. But I'm sure I will flash something else here in the next week.
Click to expand...
Click to collapse
I'm currently on stag os 13, beta from october with a pair of important bugs... however probably I will flash another one tomorrow. I have to decide first which one xD
However I would ask you what are the steps now for flashing another android 13 rom, considering I'm on android 13 and I prefer not do a clean install (dont want to do any wipes as I have my phone tweaked and fully oriented for privacy)

Los20 Google free
Without gapps, store and ps apps

been on nameless for about 6 months, no complaints

Running my own fork of LineageOS 19 with features cherry-picked from other ROMs (nothing against them but I don't need the extra 30 fazillion features they offer when a handful of features I want does the job just fine). Once LineageOS 20 builds resume with fixes for some of the major issues in place (see the LOS 20 thread for OP9Pro), I'll be upgrading to the New Hotness (I've already made the necessary changes and tested them on my OP7Pro test phone, I'm just waiting for the all-clear for the OP9Pro).

spamerobaldomero said:
I'm currently on stag os 13, beta from october with a pair of important bugs... however probably I will flash another one tomorrow. I have to decide first which one xD
However I would ask you what are the steps now for flashing another android 13 rom, considering I'm on android 13 and I prefer not do a clean install (dont want to do any wipes as I have my phone tweaked and fully oriented for privacy)
Click to expand...
Click to collapse
Oof, that's a tough one. You could *attempt* to do a dirty flash of the rom you're wanting to flash. Although, I wouldn't recommend. I've read that people do it with little side effects, but I've also seen people with lots of bugs.
What I typically do is use swiftbackup for SMS and apps, then just restore those on the new rom. But, depending on what tweaks you've applied, that might make things more difficult. As far as I know, there's not a way to restore everything, especially if the tweaks are specific to the rom. Maybe someone else might know a way?

I kept mine as stock w/root since I got it. Just reflashed and I was blown away with how much nicer it feels. Even with the amount of work I'd done to kill bloatware, background processes, etc on the stock rom.

kodayoda713 said:
Oof, that's a tough one. You could *attempt* to do a dirty flash of the rom you're wanting to flash. Although, I wouldn't recommend. I've read that people do it with little side effects, but I've also seen people with lots of bugs.
What I typically do is use swiftbackup for SMS and apps, then just restore those on the new rom. But, depending on what tweaks you've applied, that might make things more difficult. As far as I know, there's not a way to restore everything, especially if the tweaks are specific to the rom. Maybe someone else might know a way?
Click to expand...
Click to collapse
thanks for your answer mate
I didn't touch anything specific to the rom nor kernel. Only much app config and some processes freezing.
So I will save apps+data with my old friend titanium backup pro, don't know another method to do :/
By the way, I will lose root if I do clean flash or can I save that any way?
I guess a clean flash instructions should be something like this?
Extract recovery package zip
Reboot to bootloader & connect your phone to PC
Double click on flash.bat
Reboot to recovery home page & tap Factory reset > Format data/factory reset
Back to recovery home page & tap > Apply update > Apply from ADB
Now sideload rom using command adb sideload <rom_filename>.zip
Now reboot to system.

spamerobaldomero said:
thanks for your answer mate
I didn't touch anything specific to the rom nor kernel. Only much app config and some processes freezing.
So I will save apps+data with my old friend titanium backup pro, don't know another method to do :/
By the way, I will lose root if I do clean flash or can I save that any way?
I guess a clean flash instructions should be something like this?
Extract recovery package zip
Reboot to bootloader & connect your phone to PC
Double click on flash.bat
Reboot to recovery home page & tap Factory reset > Format data/factory reset
Back to recovery home page & tap > Apply update > Apply from ADB
Now sideload rom using command adb sideload <rom_filename>.zip
Now reboot to system.
Click to expand...
Click to collapse
Of course, glad I could contribute. Swiftbackup will do data for apps as well, but titanium backup should work too if that's what you prefer.
Yep, there's a couple ways to do it, and that will work. As far as root, you will definitely lose it, but you can either sideload magisk:
- download magisk APK and rename to .zip file
- after sideloading rom finishes, reboot to recovery
- sideload magisk.zip
Or
- follow root guide on this forum

Tried about every rom posted that I can find. A lot of nice roms, depends on what you want for customization. The one I prefer is Xtended. Been back and forth since A11 each one a little nicer. The latest -- v5 is best for me. I always go back to it. Currently on stock OOS13. Not all that bad with little tweaking. My disappointment is the lack of kernel development for the phone after A11. I guess the sources released by OnePlus a mess. Waiting for Ancient to be released. Could be nice.

kodayoda713 said:
Of course, glad I could contribute. Swiftbackup will do data for apps as well, but titanium backup should work too if that's what you prefer.
Yep, there's a couple ways to do it, and that will work. As far as root, you will definitely lose it, but you can either sideload magisk:
- download magisk APK and rename to .zip file
- after sideloading rom finishes, reboot to recovery
- sideload magisk.zip
Or
- follow root guide on this forum
Click to expand...
Click to collapse
really appreciate your help man, I had forgotten the steps to do root in only 3 months hahaha, my memory is awesome
I followed the method u mention and worked fine
For my words seems I am a newbie but only old hahahah, don't blame on me. I'm on this world of customization/tweaking phones since the old htc one and the first iPhone, so every day it costs me more as I increase my laziness year every passing year xD

spamerobaldomero said:
really appreciate your help man, I had forgotten the steps to do root in only 3 months hahaha, my memory is awesome
I followed the method u mention and worked fine
For my words seems I am a newbie but only old hahahah, don't blame on me. I'm on this world of customization/tweaking phones since the old htc one and the first iPhone, so every day it costs me more as I increase my laziness year every passing year xD
Click to expand...
Click to collapse
Haha, glad I could help! Memory is my biggest downfall as well, so you're not alone lol

Other backup options I like - tarb and Neo Backup. Swift I don't like because it only stores the latest backup, and the google play tied licensing is annoying when bouncing between various devices.
Used to love titanium backup but it never works successfully for me anymore