Hi it's my first post on here and I recently rooted my Samsung galaxy s5 via towel root and I've been trying to change my bootanimation
It wouldn't work on theme changer in rom toolbox pro. So I tried doing it myself I still have all stock files but it seems that I erased my whole boot animation. When I reboot my phone it just takes me straight to my home screen. Any help would be appreciated thanks!
Simply restore your backup.
If you don't make backups that is a bad habit that you ought to change immediately. In the alternative, then manually revert the files that you changed and your bootanimation will work again. If it doesn't seem to, then wipe your system cache from recovery mode.
If the problem persists, I would suggest that you didn't really revert all of the files that you changed. Check the file permissions and investigate what else your app may have changed on your behalf. In the worst case you can start over by writing a full stock firmware image to your phone. A lot more painful than restoring a backup that would reflect how your phone was four hours ago. But a certain lack of planning will limit choices that way.
As to the boot animation per se, Samsung requires a .qmg animation file, while most apps use a bootanimation.zip formatted file. Ergo you usually need to convert your .zip file to a qmg. Or modify your kernel to use the .zip format. There are lots of existing threads that explain in detail how to do either which you would know if you had done a search before posting. I would suggest that it is always in your own interest to do at least a quick search first, if only so that you can pose more informed questions.
.
fffft said:
Simply restore your backup.
If you don't make backups that is a bad habit that you ought to change immediately. In the alternative, then manually revert the files that you changed and your bootanimation will work again. If it doesn't seem to, then wipe your system cache from recovery mode.
If the problem persists, I would suggest that you didn't really revert all of the files that you changed. Check the file permissions and investigate what else your app may have changed on your behalf. In the worst case you can start over by writing a full stock firmware image to your phone. A lot more painful than restoring a backup that would reflect how your phone was four hours ago. But a certain lack of planning will limit choices that way.
As to the boot animation per se, Samsung requires a .qmg animation file, while most apps use a bootanimation.zip formatted file. Ergo you usually need to convert your .zip file to a qmg. Or modify your kernel to use the .zip format. There are lots of existing threads that explain in detail how to do either which you would know if you had done a search before posting. I would suggest that it is always in your own interest to do at least a quick search first, if only so that you can pose more informed questions.
.
Click to expand...
Click to collapse
yeah its okay I just reverted everything and it works fine. I still want to but I don't wanna mess it up again. But yes I just reverted the files back and I'm okay. But I wanted a custom boot animation but there's really no clear tutorial on how to.
lgillen14 said:
But I wanted a custom boot animation but there's really no clear tutorial on how to.
Click to expand...
Click to collapse
Not true. You need to search better as I have seen several of them. And if memory serves, written at least one myself.
.
fffft said:
Not true. You need to search better as I have seen several of them. And if memory serves, written at least one myself.
.
Click to expand...
Click to collapse
do I need a different rom? I don't even know how do do any of that lime I've rooted all my phones but not gone seriously in depth about it. I don't know what I did wrong the first time and when I tried following directions and it almost messed me up. So could you guide me toward the appropriate thread I need to get to? Thanks
lgillen14 said:
do I need a different rom?
Click to expand...
Click to collapse
No, you simply need to do a search and read the existing boot animation guides. A lot of people claim to search when they really didn't. Or did one simplistic search and gave up, thinking it's easier if someone spoon feeds them. If you try a few different keywords you'll find the guides and everything you need.
You don't need a different ROM. Root is sufficient to change the boot animation file. If you want to make a qmg animation from scratch you can use Samsung's theme designer software.
.
Related
Well hello everyone.
I am an application development student from Belgium.
I am proficient in Java, VB.NET, some c/c++ and also PHP/JS/HTML/CSS
Anyways, my recent interest has been going out to creating custom roms for the galaxy S!
The problem now is though, I was able to find some guides and such, but most were incomplete, and for HTC(and other) devices.
I have no idea what is different between making a ROM for galaxy S or a ROM for an HTC device.
If anyone would like to link me to some good resources that can help me on my way, or would like to collaborate (and in the meanwhile teach me a bit) I would be more than happy! (I am open for collaboration as I am pretty proficient in Java and I'm always happy to code and learn more about coding!)
I think the question is really want you want to do!
Custom ROMs for Android are as simple as using recovery console to replace files on the system with your own versions.
ie. Replace the framework.apk which contains all theme images with your own modified one, which you can use to skin the device. Same for replacing other system apps.
Unfortunately, most of these apps are closed source, so modifying them is difficult. The stock android system has open source versions of most of them though, and you can modify those and build them, and then replace the ones on the device. I'm not entirely sure how to build them up though, but it probably isn't too hard.
Then there are custom kernels, which let you actually change the underlying linux system underneath android - Samsung has an open source version of the kernel available that you can compile, and then flash to your phone using Odin or other tools. Compiling the kernel is pretty tricky though.
Well i'm really talking about stuff like SamSet, MoDaCo, Doc's ROM and others.
I'm not saying I want to create a pro ROM in a day or anything, but i'd really love to learn more to get better (always looking for more stuff to put on the resume, I guess?!)
Thanks a lot,
Kenny
Bump for some help
(sorry for the double post but i'm really eager to learn)
I don't have time to give a detailed response right now. However you will want to read up on yaffs (file system) and odexing/deodexing ROMs.
Thank you I will definately do that,
I am following a guide now to start out creating custom ROMs for android, however it was written for Motorola Droid and I have no idea what you have to do different for a samsung galaxy s.
I am a good coder, even though I say so myself, with a lot of experience. I also have a lot of linux experience, you name it
Only the problem is the old, and much known "where do I get started?"
So if anyone can point me out in the right direction on that, tell me how/where you started out, I would appreciate it greatly!
Thanks!
Very sorry to bump again
I set up my environment in ubuntu today to get started (just gotta fix a few errors, didn't know android wouldn't compile on java 1.6, only on 1.5)
Anyways, still need some help here! thanks!
Again I am awefully sorry for the bump here but i'd really like some help.
Note that i'm not a newbie at coding whatsoever and i'm not unfamiliar with some hardcore java, c/c++ and other languages, I'm just having trouble getting started when it comes to modding an existing android release (there are tutorials on HTC and other devices but some methods do not apply to the galaxy S)
If you're trying to create a ROM from scratch then unfortunately you're out of luck at the moment. No one has really managed to do so yet. By "from scratch" I mean the Android Open Source Project (i.e. official Android git repository).
What you can do is grab an existing firmware. Extract the contents, de-odex the apks, modify them or add new apks, optionally you can also compile a custom SGS kernel using Samsung's kernel source. Then you can re-odex the ROM, pack it back up and distribute it.
There's no real "starting place" as such and you won't yet find any tutorials about how to create SGS ROMs. Just give it a go and see where you get.
Yes, I do mean creating a ROM from stock samsung firmware, of course.
So my next logical question would be now:
How do I go over extracting contents from the existing samsung firmware, de-odexing and so on?
Any links/guides/tips are greatly appreciated, as long as they are applicable to this cell phone and not totally crap, thanks!
Samsung uses rfs, I think you should know. There is a thread somewhere in this forum regarding extracting .rfs file. Understood you need Debian though.
For some readup, go search for a famous guy named JesusFreke. Tons of materials...
Hope that from here onwards, this can lead you on, and to find out more. Google is your friend too...
I'm afraid my biggest problems already occur in setting up the environment, so it's really the very beginning that gets me stuck, i'm sure coding would be a bikeride compared to setting up the environment for me (i'm no hero in linux,not at all, i'm afraid)
How the hell do I get from point A (being downloading the full source) to point B (starting to create a custom ROM?)
thanks
of course if anyone has the time, and wants to, you can PM me your msn or something, if anyone is up to it
Raykoid666 said:
I'm afraid my biggest problems already occur in setting up the environment, so it's really the very beginning that gets me stuck, i'm sure coding would be a bikeride compared to setting up the environment for me (i'm no hero in linux,not at all, i'm afraid)
How the hell do I get from point A (being downloading the full source) to point B (starting to create a custom ROM?)
thanks
of course if anyone has the time, and wants to, you can PM me your msn or something, if anyone is up to it
Click to expand...
Click to collapse
Agreed completely! Getting a full cross-compilation to Samsung's Android going is seriously difficult! There have been some promises for tutorials and guides for setting things up though, but none have appeared yet. Probably because it's hard!
Well thank you for agreeing with me on that.
I am really hoping for anyone that can help me out here, either on here or in private, and give some detailed instructions on how to get started.
Hell there is enough information on creating roms alread, deodexing, adding/removing apps etc etc etc... The real problem lies in setting everything up properly.
I think I have gotten to the point where I'm compiling the android source (without samsung specific files)
note i'm saying "i think i am compiling" because i'm hoping it won't error out on me again after an hour of compiling!
But once that is done... I have no idea where to go next, where to get the samsung specific files, or what to do with them whatsoever once i have them
thanks!
Android generic source won't actually help you much. Samsung has made a huge number of changes to it, and while it is all open source, backporting their changes to get your stock source running on the phone is a major undertaking. I believe cyanogenmod was actually working on this, but it seems without much success so far.
What the other rom makers you see are doing is taking a snapshot of a running rom, copying over all of the APKs and the files on a running device, and then tweaking those. ie. Opening up framework-res.apk and changing the image files inside.
The update.zip roms that are what most people are doing are really just using the Android recovery to replace files on the phone with their own versions. Since the underlying system is linux, and everything is a file, this actually works pretty well.
The kernel development effort is completely separate from the rest of the system though, and Samsung has provided the entire source tree that just has to be compiled. I'm a bit stumped myself on all the details of setting it up, but I have seen some threads on this forum about it, and it didn't seem too bad to set up. Apparently you shouldn't use the codesourcery toolchain though, or something. Not too clued up on it, sorry. Hopefully someone with the details can chime in, or give us a link to the old post on it (I'm failing to find it using the search function! )
Alright sounds good!
So these recovery files you are talking about (the contents of /system) how do i retrieve those from a base ROM such as JM7 or the likes after a clean flash?)
Raykoid666 said:
Alright sounds good!
So these recovery files you are talking about (the contents of /system) how do i retrieve those from a base ROM such as JM7 or the likes after a clean flash?)
Click to expand...
Click to collapse
Root your phone, zip them up onto the sdcard, and then copy them off.
There are probably better methods, but this works fine.
Also, with credits to Unhelpful, he has told me that the correct toolchain to be using is 'uClibc or eglibc toolchain with ct-ng'. I have no idea what to do with that yet, but it's a start.
RyanZA said:
Root your phone, zip them up onto the sdcard, and then copy them off.
There are probably better methods, but this works fine.
Also, with credits to Unhelpful, he has told me that the correct toolchain to be using is 'uClibc or eglibc toolchain with ct-ng'. I have no idea what to do with that yet, but it's a start.
Click to expand...
Click to collapse
You don't even need to root your phone to pull /system Ryan
adb pull /system <random folder>
is all you need ^^
Alright thank you, I managed to get all the /system files using abd pull /system
now next thing up would be de-odexing right, before I go editing stuff?
Now before I go de-odexing. Can anyone tell me what exactly de-odexing is and why I need it?
and what do I need to do to create an update.zip again?
thanks a lot all!
Tayutama said:
You don't even need to root your phone to pull /system Ryan
adb pull /system <random folder>
is all you need ^^
Click to expand...
Click to collapse
Haha cool, didn't know you could pull whole folders!
Raykoid666 said:
Alright thank you, I managed to get all the /system files using abd pull /system
now next thing up would be de-odexing right, before I go editing stuff?
Now before I go de-odexing. Can anyone tell me what exactly de-odexing is and why I need it?
and what do I need to do to create an update.zip again?
thanks a lot all!
Click to expand...
Click to collapse
The apk files in Android are odexed - that means they have a special index applied for dalvik that speeds them up somehow! I don't know how, I haven't checked how it actually works.
The important point is though:
odexed is faster, but you can't edit it because of signatures or something technical
deodexed means you can change it however you want
More useful info can be found from google - lots of it!
update.zip is easy - it's a zip file in a special format that can be understood by Android's recovery console. The easiest way to do it is to grab an existing update.zip and modify it as needed. Tayutama has millions of em around, so use his!
Then you need to sign it once you're finished with it so that the SGS will accept it. Samsung made a boo-boo and didn't disable the test keys for the 2.1 SGS firmwares. That makes it easy!
http://www.londatiga.net/it/how-to-sign-apk-zip-files/
Just use the test keys to sign it, and then copy it to /sdcard/update.zip and reboot into recovery and it'll work.
Ok so I picked up my Droid X about a month ago and haven't been able to put this thing down, I never thought about rooting it because it did everything I needed/wanted it to do, then one day I log into my car forum and all the OT guys are posting cool print screen's of their phones. I was intrigued, so I rooted my phone and have been trying to figure out a few things but I'm not really up on the terminology and/or logic behind doing certain things. I would greatly appreciate any help in regards to explaining the following:
1) Rooting - Takes off restrictions on the phone so that developer apps can be installed... Is there more to this or is that pretty much it?
2) Flashing - I see this term often but I'm not sure what it is exactly, I tried installing a theme once and the directions said to flash something somewhere and looked at it the same way my dog looks at me while I'm working out at home.. lol
3) ROM - !?
4) apk's - What are they, what do they do, and how do you install them!?
5) Installing themes - I'm thinking has to do with all of the above...
6) Locating and moving downloaded content...
7) How do all of these things tie together? I'm completely clueless as to what does what on the phone and would like to become as knowledgeable as I was when the iPhone first came out and I figured out how to jailbreak/unlock it...
As a reward for your time and effort I leave you Final Fantasy VII fan's with a cool wallpaper I found at work today.. Thanks for any/all input and again, your time is most appreciated!!
Initial GT3 said:
Ok so I picked up my Droid X about a month ago and haven't been able to put this thing down, I never thought about rooting it because it did everything I needed/wanted it to do, then one day I log into my car forum and all the OT guys are posting cool print screen's of their phones. I was intrigued, so I rooted my phone and have been trying to figure out a few things but I'm not really up on the terminology and/or logic behind doing certain things. I would greatly appreciate any help in regards to explaining the following:
1) Rooting - Takes off restrictions on the phone so that developer apps can be installed... Is there more to this or is that pretty much it?
2) Flashing - I see this term often but I'm not sure what it is exactly, I tried installing a theme once and the directions said to flash something somewhere and looked at it the same way my dog looks at me while I'm working out at home.. lol
3) ROM - !?
4) apk's - What are they, what do they do, and how do you install them!?
5) Installing themes - I'm thinking has to do with all of the above...
6) Locating and moving downloaded content...
7) How do all of these things tie together? I'm completely clueless as to what does what on the phone and would like to become as knowledgeable as I was when the iPhone first came out and I figured out how to jailbreak/unlock it...
As a reward for your time and effort I leave you Final Fantasy VII fan's with a cool wallpaper I found at work today.. Thanks for any/all input and again, your time is most appreciated!!
Click to expand...
Click to collapse
First off- that is a lot to bite off as an opener. lol. I have to get in a minute- plus I am a newb as well but here a couple of things...
1) You sound pretty on track. Root gives you access to more options with your phone. It also voids your warranty.
2) Flashing. A term used loosely. Normally it is used in conjunction with "flashing a rom". It simply means to install something (basically).
3) Rom. It is the image (not in the photo-graphical sense) that is embedded/burned on your phones hard drive with all the information of your operating system. For instance: you are on the stock 2.2 ota "rom". But you could "flash" the new "AOSP rom" that was just released. That means you would be removing the factory image that came on your phone and replacing it with a modified image. Theme's and .apk's -those are not "burned" into the phone. If you do a factory reset- those will be wiped. The rom image stays put. If you flash from 2.2 ota to AOSP and then did a factory reset- you would not return to the original state your phone came from Motorola bc that image is completely removed and replaced by the new image you flash. Instead you would return to a clean AOSP.
4) .apk's - .apk is simply the name of the file extension used for android applications. I came from Windows Mobile and they were called .cabs. So any app can be referred to as an .apk. You can download an apk from XDA, place it on your sdcard, tap the file, and i think you will be prompted with "do you want to install" (some where along those lines). There is a setting in the "Settings" that allows you to install 3rd party (non-market) .apk's.
5)Installing themes. This refers to modifying the images (and this time I do mean in the graphic sense) of certain .apk's and other whatchamajiggies. You can install a simple theme that just changes your lockscreen, or you can install a huge theme that changes almost every part of every image so the entire phone looks similar. Here is the tricky part about using themes- your phone has to be deodexed.
deodexed. When you get your phone all of the system files come with a few different parts to them. One of those parts is an odexed file. Apparently the theme building types do not like working with these files so they run this process called de-odexing in which all of the system files are somehow manipulated in a way where they no longer need their odex file. So you end up "de-odexed". There is a program called "xultimate 2.2" that enables regular folk like you and me to deodex our phones. I tried running it yesterday and it errored out on me. So I used another method that worked fine. There are some threads on here about deodexing- if you want themes you will have to do it.
6) locating and moving downloaded content. When you have root you can get Root Explorer from the market. I am sure there are other good file exploreres- but I can't speak to them- I use Root Explorer. As far as locating downloaded content- whenever I download something from my phone, it always (normally) goes to /sdcard/downloads. If it is not there, I guess you just do a search for it. If you want to move it- long press the item, copy, move.
And you will need to google "ADB" (android device bridge). Many of these activities will require the use of ADB. You plug in your phone through USB (make sure phone settings are set to "USB debugging") and... well there is just way to much on this one. Google this one and you will find a lot of stuff- or search it here on XDA
have a great weekend. got to go.
So i am here with a new idea. A rescue.zip which can be used to rescue any android device which have a recovery like the famous cwm.
So here is it..
Some times we people screw up our android os like hell, and to reboot the device we usualy do a recovery flash of a new os, flash back our nandroid backup ( both on worst conditions) or even do permission fix, clean cache or dalvic cache( those in 'not that worse' conditions) . So thats are all the options we got. Rit?
Although flashing recovery backups, new roms can fix all, it will also eatup our apps, current setups, contacts, msgs, etc( in case we dont have backups) and will probably screw us. All we can do is say " WTF..WTF..WTF.."
SO here is my idea,
Find out the causes of what causes a reboot, non-boot, hang,fc etc.
And keep a zip that can be flashed through recovery, that has a solution for our problem. They may be including..
1) fix permission of system, data, and user data.
2) zipalign the apps
3) fix the default clock speed of processor
4) defragment memory
5) flash a new copy of su and busy box
6)wipe data or system or ext or cache or dalvic cache
7) flash a new copy of framework.res, system-ui.apk, settings.apk with default permissions( those files are kept in separate "custom" folder on the zip, so that end user can put their own files to that "custom" folder for flashing., the reason behind it is known to all, yap. Not all devices have them in common, every device have its own files)
These are all i got for now, pls post ur ideas and knowledge for any possible cure about any problem u faced/ cured. So that we can make it an ultimate rescue.zip that have a cure for 99% problems android os have. The rest 1% will go with a clean flash.( well we cant avoid that if we did something that bad).
So my plan is to use aroma installer( now on hard learning to find how it works). Throw in some scripts, files etc. Into the zip.
And since its not a device specific .zip file, i want to know how and why any problems are caused in any device( there are many common problems, but that is not what i ask for. I ask for device/os specific problems, and not for a problem that we can cure after booting, but for a problem that can make the device un-bootable) . So u people may help me to find those problems and cures for it. For my knowledge i have experience with wildfire and hd2.
Well i will keep this thread for a week or two, so that u can post ur knowledge, and info. after that i will release the file for u.
To the admin. Of the forum, pls keep this thread as announcement so that all can take a look.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.
showlyshah said:
So i am here with a new idea. A rescue.zip which can be used to rescue any android device which have a recovery like the famous cwm.
Click to expand...
Click to collapse
good idea however there are SOOOO many variations of the files that would be needed, that basicaly it would be easier to consider what ever ROM you are using as the OMG_RECOVER.zip
Just my 2 cents.
Pvy
pvyParts said:
good idea however there are SOOOO many variations of the files that would be needed, that basicaly it would be easier to consider what ever ROM you are using as the OMG_RECOVER.zip
Just my 2 cents.
Pvy
Click to expand...
Click to collapse
mmmmm variables.... tasty
Un-Bricking by Unlocking & Flashing CWM+CM7 (was: Accidentally deleted MediaProvider)
Hi!
When removing Bloatware with Titanium Backup a while ago, I accidentally missed a click (never used a touch screen...) and uninstalled MediaProvider, which I have not been able to recover since.
I tried putting the files back from a friend's HTC, which didn't work; after that I was told even the packages differ between manufacturers, so I tried getting them from a stock Bell Atrix .zip posted on these very forums, which didn't help either. Neither #android-root nor AndroidForums were able to help, thus I ask here: Can anyone tell me how to either make my system accept Bell's files, or where I can find a "vanilla" Motorola build?
(Problem is, the phone didn't come from a phone company, a friend of mine got it pre-release from his uncle who is with Motorola, so it may even be different from what hit the market later on...)
I guess the following information will help, it's a Titanium Backup info file for another componend I backupped shortly after:
#Titanium Backup
#Sat Feb 25 03:28:43 MEZ 2012
app_gui_icon=[...]
sys_ro.build.date.utc=1302536066
app_version_code=8
sys_ro.product.model=MB860
has_prefsdata_jpu=0
sys_ro.serialno=<xxx>
sys_ro.build.description=olympus-user 2.2.2 OLYEM_U4_0.44.0 578673 ota-rel-keys,release-keys
has_prefsdata=0
app_gui_label=com.android.providers.applications 2.2.2
sys_ro.build.version.release=2.2.2
app_apk_md5=1989ff2476ee73ad445760b9bef5f44e
has_dbdata=0
app_apk_codec=GZIP
app_is_forward_locked=0
app_is_system=1
app_label=com.android.providers.applications
app_version_name=2.2.2
generation=1
app_apk_location=internal
(Most of this is unnecessary, I guess, but I can't really be sure what you might need to judge what I would have to to...)
I would be very grateful for any help, it is extremely limiting not to be able to use any media capabilities.
So, thanks in advance,
David
maybe flash a new rom if your contacts are all backed up?
Hm, well, that would really be the last resort :\ In addition to losing all my data, I fear the risk of bricking it completely. Can't really be that I'd have to flash it just because two files are missing...?
Edit: I neglected to say that the files in question are MediaProvider.apk and MediaProvider.odex. I do only need to copy these to /system/app, right?
Intelensprotient said:
Hm, well, that would really be the last resort :\ In addition to losing all my data, I fear the risk of bricking it completely. Can't really be that I'd have to flash it just because two files are missing...?
Edit: I neglected to say that the files in question are MediaProvider.apk and MediaProvider.odex. I do only need to copy these to /system/app, right?
Click to expand...
Click to collapse
Yes, but you have to set the permissions same the other files in .system/app folder.
I have attached the missing files to this post. My gingerbread version is 2.3.4.
Good Luck!
Huh. Setting right permissions for the files from Bell had no effect; installing yours soft bricks it in an interesting way: Even with Early USB Enumeration, all I see is
# adb devices
List of devices attached
???????????? no permissions
Even with root. The LED flashes red, and after a minute it reboots. I had expected things not to work out, resulting in the deletion of your files, but that I screwed up _that_ bad after it didn't even seem to notice the right (?) files when they were there is kinda surprising.
The standard workarounds (adb kill/start server, MODE=0666 to udev or being root) change nothing about this. Time for hard reset?
Intelensprotient said:
Huh. Setting right permissions for the files from Bell had no effect; installing yours soft bricks it in an interesting way: Even with Early USB Enumeration, all I see is
# adb devices
List of devices attached
???????????? no permissions
Even with root. The LED flashes red, and after a minute it reboots. I had expected things not to work out, resulting in the deletion of your files, but that I screwed up _that_ bad after it didn't even seem to notice the right (?) files when they were there is kinda surprising.
The standard workarounds (adb kill/start server, MODE=0666 to udev or being root) change nothing about this. Time for hard reset?
Click to expand...
Click to collapse
I would hard reset too at this stage. I'm sorry it didn't work out.
Now, that's interesting. Factory reset didn't change anything.
Sorry for reply to self, but I was less than clear, so - help?
My next step would be to try to unlock the bootloader, then flash CWM and see if anything can be fixed that way; then, I would try flashing CM7 (or, more specifically, the Neutrino GT ROM) by CWM; then, I would try flashing it without. Is that a safe progression of attempts? Or have I possibly broken anything that would hard-brick it by any of these methods? And can you recommend any finer increments what I could do before / between / after those mentioned? I still have the option to apply an update in Recovery - is it possible, for instance, to put a .zip onto my SD that has 0 Byte MediaProvider files in it?
(I have thought about installing Neutrino for a while, and this seems to be a good time to flash it, as my data is cleared now anyways. To my understanding, this should not be any more dangerous than just re-flashing the Froyo that was there before, right?)
As an additional fact, ADB now doesn't detect any devices any more, even with Early USB. This could be because USB Debug is not a factory standard setting, though, as I reset it to factory defaults.
Also, the startup Moto screen behaves differently: It doesn't go to the point where the logo disappears in a flash, the background light switches off before that. As far as I can tell, the display still shows the animation, though, but it is not lit. Furthermore, the reboot seems to happen immediately after the animation has ended, and not 1-2 minutes later, like it was before the reset.
I would be grateful if anyone could explain what happened. To my understanding, a factory reset should clear /system, and the error started when I put some non-compatible .apks there, so I thought this would fix things. Is it possible something broke on the hardware side, when (for instance) 2.2.2 called a function that has had its parameters changes in 2.3.4?
[If a moderator reads this - does this qualify as a general Android question? I have no experience with different devices, so I'd be glad if you could decide if this thread has to stay here or if it can go to a sub-forum with a wider audience - General Android Q&A, for instance.]
Bump...
Success Neutrino up and running!
hi guys ,
i saw the recent post about "TWRP v3.2.2 for Xperia X Compact" released and many positive commend on the post,
anyone can simple tell me what are the benefit of Flashing with TWRP ,(sorry for my stupid question, not a techie ) for normal users ,
thanks & regards
Br
ameerali19 said:
hi guys ,
i saw the recent post about "TWRP v3.2.2 for Xperia X Compact" released and many positive commend on the post,
anyone can simple tell me what are the benefit of Flashing with TWRP ,(sorry for my stupid question, not a techie ) for normal users ,
thanks & regards
Br
Click to expand...
Click to collapse
Nothing wrong with the question, but it's in the wrong place. Should be posted in 'Troubleshooting, Help, Q&A, etc'...
TWRP is what's called 'custom recovery'. Most phones these days have recovery, which is a partition, separate from the phone's other partition, which the phone can boot to, in order to repair or modify the other partitions. Usually you don't have much control over a stock recovery, (it's set up by the manufacturer to function certain ways at certain times), but developers have learned how to design custom recoveries that users can use to do just about anything they want to any partition on their phone. Some people like to do that - anything from UI modifications to speed improvements to removing things from system that you don't want, etc...
levone1 said:
Nothing wrong with the question, but it's in the wrong place. Should be posted in 'Troubleshooting, Help, Q&A, etc'...
TWRP is what's called 'custom recovery'. Most phones these days have recovery, which is a partition, separate from the phone's other partition, which the phone can boot to, in order to repair or modify the other partitions. Usually you don't have much control over a stock recovery, (it's set up by the manufacturer to function certain ways at certain times), but developers have learned how to design custom recoveries that users can use to do just about anything they want to any partition on their phone. Some people like to do that - anything from UI modifications to speed improvements to removing things from system that you don't want, etc...
Click to expand...
Click to collapse
thanks for your valuable reply,
other than partition is there any other benefit for normal user ,
like most of our guys are using for what kinda purposes ,
i use Jailbroken iphone for years , im mainly using JB for multiple social messenger account ,video/audio download,3rd party apps install, location faker etc (without adds)
ameerali19 said:
thanks for your valuable reply,
other than partition is there any other benefit for normal user ,
like most of our guys are using for what kinda purposes ,
i use Jailbroken iphone for years , im mainly using JB for multiple social messenger account ,video/audio download,3rd party apps install, location faker etc (without adds)
Click to expand...
Click to collapse
Partition is a noun here, not a verb. You don't use recovery to partition anything, (although probably could) - it is a partition. It's basically a place where you can boot the phone to be able to modify things in the other places where you use the phone, like phone system files. It can also create and restore backups, flash firmware, etc...