Related
I have recently rooted my Nexus S, and I want to flash the latest version of cyanogenmod. The only thing is I want to keep my bootscreen stock. Can anyone tell me how to do this. I need the easiest way and i am using am mac if that makes a difference. Thanks in advance.
cvv1984 said:
I have recently rooted my Nexus S, and I want to flash the latest version of cyanogenmod. The only thing is I want to keep my bootscreen stock. Can anyone tell me how to do this. I need the easiest way and i am using am mac if that makes a difference. Thanks in advance.
Click to expand...
Click to collapse
you could install CM and then flash the stock boot screen animation over it,
Or you could create your own custom CM build with the stock boot animation
slowz3r said:
you could install CM and then flash the stock boot screen animation over it,
Or you could create your own custom CM build with the stock boot animation
Click to expand...
Click to collapse
Im a noob to this so I need more detailed directions, or where can I get the stock boot screen. Thanks
cvv1984 said:
Im a noob to this so I need more detailed directions. Thanks
Click to expand...
Click to collapse
Then google or search the forum. Not sure if the Nexus S works like other phones but you normally would.....
You would first have to find the Nexus One bootanimation.zip (they're the same)
Place it in one of the system folders /system/media/
Reboot and see if it works.
zephiK said:
Then google or search the forum. Not sure if the Nexus S works like other phones but you normally would.....
You would first have to find the Nexus One bootanimation.zip (they're the same)
Place it in one of the system folders /system/media/
Reboot and see if it works.
Click to expand...
Click to collapse
So Its safe to say dont just flash from the root of the sd?
cvv1984 said:
So Its safe to say dont just flash from the root of the sd?
Click to expand...
Click to collapse
there are different ways it can be done
slowz3r said:
there are different ways it can be done
Click to expand...
Click to collapse
^^ some don't need to be flashed... some do
it depends on the ROM, the method I posted above would probably not do any harm. If it works, it works.. if it doesn't then nothing will change.
Again, I'm not responsible for anything that happens to your phone. Just passing the message by.
As the name implies this the unsecure stock kernel boot.img
You can use the adb remount command to push files to system now!
YOU MUST HAVE AN UNLOCKED BOOTLOADER FOR THIS! See here for more info: http://forum.xda-developers.com/showpost.php?p=30274025&postcount=317
If you dont know what this then it may not be for you. This is more so developers can use in there ROMS.
No need to ask to use it, just give credit if you do.
Download HERE
Chang Log
v3 - Corrected incorrect adbd in /sbin for proper colors when using screen capture while in Dalvik Debug Manager.
v2 - Added Lib folder for that need it.
New clean ROM soon then?
Sent from my SCH-I535 using xda app-developers app
Would it be too much to ask for an AOSP kernel (ICS)? I'd do it myself, but I don't know much about kernels lol
Nopi45 said:
New clean ROM soon then?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Well, this is more for developers.
It just unlocks the /system partition so you can push files. I mean, yeah, it will be in the next CleanROM but its not urgent from a user perspective.
PureMotive said:
Would it be too much to ask for an AOSP kernel (ICS)? I'd do it myself, but I don't know much about kernels lol
Click to expand...
Click to collapse
This is a Stock kernel. I just modified the RAM Disk to remove security and to add init.d support and set up the script so it can be flashed.
I didint build the kernel. Its just stock.
How come your user name is in italics BTW?
Not sure on run parts... Need to check. Unsecure is still a go!
scrosler said:
This is a Stock kernel. I just modified the RAM Disk to remove security and to add init.d support and set up the script so it can be flashed.
I didint build the kernel. Its just stock.
How come your user name is in italics BTW?
Click to expand...
Click to collapse
I know it's stock. I was just wondering whether you were able to get an unsecured AOSP kernel for all of the AOSP ROMs out there. It'd also help with Sense 4.
To get your username in italics (RDs only):
Go to User CP
Select "Group Membership" from the side bar
Select "Recognized Developer - Identify me as a member of this group"
Save
Well this work on lf2?
Neverendingxsin said:
Well this work on lf2?
Click to expand...
Click to collapse
Are you a dev?
No?
Keep moving
VERIZON GALAXY S 3
PureMotive said:
I know it's stock. I was just wondering whether you were able to get an unsecured AOSP kernel for all of the AOSP ROMs out there. It'd also help with Sense 4.
To get your username in italics (RDs only):
Go to User CP
Select "Group Membership" from the side bar
Select "Recognized Developer - Identify me as a member of this group"
Save
Click to expand...
Click to collapse
To make it unsecure its just some changes in the RAM Disk. Im sure if the AOSP guys are out they know how to do that. If not they can reach out to me for help but they tend to know more than I do about kernels and all
Thanks for the heads up the italics!
Neverendingxsin said:
Well this work on lf2?
Click to expand...
Click to collapse
DROID3R said:
Are you a dev?
No?
Keep moving
VERIZON GALAXY S 3
Click to expand...
Click to collapse
Click to expand...
Click to collapse
This is mostly for developers that want to do things that having a locked boot.img normally stops you from doing. An average user will gain little value...
But lets say you were making a theme and had to "push" files to the /system folder you can NOW do that with this boot.img. It makes Dev's lives a LOT more easy now, lol
scrosler said:
To make it unsecure its just some changes in the RAM Disk. Im sure if the AOSP guys are out they know how to do that. If not they can reach out to me for help but they tend to know more than I do about kernels and all
Thanks for the heads up the italics!
This is mostly for developers that want to do things that having a locked boot.img normally stops you from doing. An average user will gain little value...
But lets say you were making a theme and had to "push" files to the /system folder you can NOW do that with this boot.img. It makes Dev's lives a LOT more easy now, lol
Click to expand...
Click to collapse
yes it does, copying files to my sdcard and then moving them with root explorer, or packaging them in a flashable zip and copying to sdcard and flashing everytime is frustrating. specially if your doing it every 10-15 mins.
nosympathy said:
yes it does, copying files to my sdcard and then moving them with root explorer, or packaging them in a flashable zip and copying to sdcard and flashing everytime is frustrating. specially if your doing it every 10-15 mins.
Click to expand...
Click to collapse
Tell me about man, tell me about it!
And I confirmed init.d support is functional as well!
I know this is just a simplification process for devs and it helps skip the extra step of moving files somewhere else first then move to /system with root explorer if you're rooted, so please don't ask if I'm a dev, the answer is: no, I'm not. I would appreciate if someone could only answer this question without getting into other details. I would like to know if it would harm or break anything if I have VRALF2 rom and radio/stock kernel and I flash a VRALG1 kernel, but keep the rest as it is? Would this newer kernel work with my older version rom, or do I have to flash the whole package first? I basically don't want to renew my rom to the new G1 version since there is no apparent improvement (it's actually worse) over the older F2 version rom, since it downgrades certain things.
Thanks
newuser134 said:
I know this is just a simplification process for devs and it helps skip the extra step of moving files somewhere else first then move to /system with root explorer if you're rooted, so please don't ask if I'm a dev, the answer is: no, I'm not. I would appreciate if someone could only answer this question without getting into other details. I would like to know if it would harm or break anything if I have VRALF2 rom and radio/stock kernel and I flash a VRALG1 kernel, but keep the rest as it is? Would this newer kernel work with my older version rom, or do I have to flash the whole package first? I basically don't want to renew my rom to the new G1 version since there is no apparent improvement (it's actually worse) over the older F2 version rom, since it downgrades certain things.
Thanks
Click to expand...
Click to collapse
When you say no improvement are you talking the Modems? If you are only flashung a rom and havent changed the kernel then it would be the same as just flashing the g1 modem with a different rom correct.
Hey scrosler how can I identify that the flash worked. The ROM booted normally but in the kernel name I don't see any change.
wooddale said:
When you say no improvement are you talking the Modems? If you are only flashung a rom and havent changed the kernel then it would be the same as just flashing the g1 modem with a different rom correct.
Click to expand...
Click to collapse
I'm not talking about the modem, I'm asking about the kernel, if I flash THIS unsecure (G1) kernel, but otherwise have ALL F2 stuff (modem, rom, etc), will it mess up anything? I think u misunderstood my question, I don't want to flash a G1 rom or modem, just the kernel, because the modems are same, so no improvement there, and the F2 rom is better than the G1 rom, so I'm keeping everything as F2 like it was, but flashing this G1 kernel. Will that be compatible/ok?
Try it??? If it fails just restore from backup?
Sent from my Nexus 7 using Tapatalk
newuser134 said:
I'm not talking about the modem, I'm asking about the kernel, if I flash THIS unsecure (G1) kernel, but otherwise have ALL F2 stuff (modem, rom, etc), will it mess up anything? I think u misunderstood my question, I don't want to flash a G1 rom or modem, just the kernel, because the modems are same, so no improvement there, and the F2 rom is better than the G1 rom, so I'm keeping everything as F2 like it was, but flashing this G1 kernel. Will that be compatible/ok?
Click to expand...
Click to collapse
I tried this out and did not see ANY difference. But then again it's midnight and I won't know if anything will be wonky until I use it at work tomorrow
sent from a locked downloader
newuser134 said:
I know this is just a simplification process for devs and it helps skip the extra step of moving files somewhere else first then move to /system with root explorer if you're rooted, so please don't ask if I'm a dev, the answer is: no, I'm not. I would appreciate if someone could only answer this question without getting into other details. I would like to know if it would harm or break anything if I have VRALF2 rom and radio/stock kernel and I flash a VRALG1 kernel, but keep the rest as it is? Would this newer kernel work with my older version rom, or do I have to flash the whole package first? I basically don't want to renew my rom to the new G1 version since there is no apparent improvement (it's actually worse) over the older F2 version rom, since it downgrades certain things.
Thanks
Click to expand...
Click to collapse
Well, you can try it but my experieince tells me that you may loose LTE and WiFi because yo dont have matching modules. The modules (aka drivers if it were windfows) hare specific to a kernel. If you took the /system/lib/modules folder from a G1 ROM like mine or nosympathy and pushed them in I bet it would work just fine. But why on earth are you on older build?
wooddale said:
When you say no improvement are you talking the Modems? If you are only flashung a rom and havent changed the kernel then it would be the same as just flashing the g1 modem with a different rom correct.
Click to expand...
Click to collapse
No, Gerneally ROMS dont include the radios from my experience. BUt I heard int he samsung world Devs do things differently so I dont honestly now.
jb_alphamale said:
Hey scrosler how can I identify that the flash worked. The ROM booted normally but in the kernel name I don't see any change.
Click to expand...
Click to collapse
Thats easy... Before you flashed the boot.img was USB deggign turned on? If not it would be turned on now.
If USB degging was already on or not on turn it on... Then... connect phone and wait for the connection to finish. Then type "adb remount" (assuming you have ADB handy) and it should say "remount succeeded" If it says operation not permitted then it did not take.
newuser134 said:
I'm not talking about the modem, I'm asking about the kernel, if I flash THIS unsecure (G1) kernel, but otherwise have ALL F2 stuff (modem, rom, etc), will it mess up anything? I think u misunderstood my question, I don't want to flash a G1 rom or modem, just the kernel, because the modems are same, so no improvement there, and the F2 rom is better than the G1 rom, so I'm keeping everything as F2 like it was, but flashing this G1 kernel. Will that be compatible/ok?
Click to expand...
Click to collapse
Hipcatjack said:
I tried this out and did not see ANY difference. But then again it's midnight and I won't know if anything will be wonky until I use it at work tomorrow
sent from a locked downloader
Click to expand...
Click to collapse
What difference did you expect? Its a STOCK kernel and will behave like a stock kernel except give full and true root access to the device. Its not for the end user its for developers. Of course this ramdisk will also allow us to start modifying and shutting off services, tweak things at the kernel level, etc... But right now, this is just bone stock with init.d support and root level access to the file system via ADB.
Hope that explains it some.
Hey, I have got a problem with my OnePlus One for quiet some time..
It started about 2 months ago - Whenever I'm on a call, the other side can barely hear me unless I'm on speaker.
I did some reading and there are suggestions that this is because of some mis-written code or something, that makes the input of the microphone low, so that only a small precent of the sound is being transferred to the one I'm talking to.
this may or may not be the problem, but I wanted to ask you fellows if anyone has any suggestion on what's causing this and how to try & solve it.
I'm Running a Stock 5.0.2 Cm12s with the latest OTA update, and this problem started when I had Stock 4.4.4 CM11s.
Device isn't rooted & never was.
Locked Bootloader.
Please help if you can
Lidor167 said:
Hey, I have got a problem with my OnePlus One for quiet some time..
It started about 2 months ago - Whenever I'm on a call, the other side can barely hear me unless I'm on speaker.
I did some reading and there are suggestions that this is because of some mis-written code or something, that makes the input of the microphone low, so that only a small precent of the sound is being transferred to the one I'm talking to.
this may or may not be the problem, but I wanted to ask you fellows if anyone has any suggestion on what's causing this and how to try & solve it.
I'm Running a Stock 5.0.2 Cm12s with the latest OTA update, and this problem started when I had Stock 4.4.4 CM11s.
Device isn't rooted & never was.
Locked Bootloader.
Please help if you can
Click to expand...
Click to collapse
try to flash this http://forum.xda-developers.com/oneplus-one/development/fix-low-mic-call-t3055661
I had the same problem and it fixed it.
The only thing is that i had to flash it after every rom change.
solokiller11 said:
try to flash this http://forum.xda-developers.com/oneplus-one/development/fix-low-mic-call-t3055661
I had the same problem and it fixed it.
The only thing is that i had to flash it after every rom change.
Click to expand...
Click to collapse
Does it not require a root access?
Lidor167 said:
Does it not require a root access?
Click to expand...
Click to collapse
it requires a custom recovery but not sure about root, i guess its required but not sure
solokiller11 said:
it requires a custom recovery but not sure about root, i guess its required but to sure
Click to expand...
Click to collapse
I don't even know what costum recovery means..
Lidor167 said:
I don't even know what costum recovery means..
Click to expand...
Click to collapse
read this thread, its a great one and explains everything you need to know
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
you don't have to read everything (although recommended)
solokiller11 said:
read this thread, its a great one and explains everything you need to know
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
you don't have to read everything (although recommended)
Click to expand...
Click to collapse
So in order to install a custom recovery ( say TWRP ) I do not need root acess? do I only need to follow step no.2 at the guide you gave me?
Lidor167 said:
I don't even know what costum recovery means..
Click to expand...
Click to collapse
Lidor167 said:
So in order to install a custom recovery ( say TWRP ) I do not need root acess? do I only need to follow step no.2 at the guide you gave me?
Click to expand...
Click to collapse
Yes, But it is also recommended to root the phone. Root is a great thing to have
I bought this nexus 5 from a previous user, noticed bootloader unlocked, diferente kernel(althought i flashed another already), but something caught my eye, im not sure if i have the stock rom, as i get an update of 16mb and fails.
"devcheck app"
Under system = Codename: Hammerhead
5.1.1
Build: LMY48I
Is this stock?
Help?
Sent from my Nexus 5 using XDA Free mobile app
I think nobody wants help a KILLER
HIGKILLER said:
I bought this nexus 5 from a previous user, noticed bootloader unlocked, diferente kernel(althought i flashed another already), but something caught my eye, im not sure if i have the stock rom, as i get an update of 16mb and fails.
"devcheck app"
Under system = Codename: Hammerhead
5.1.1
Build: LMY48I
Is this stock?
Click to expand...
Click to collapse
It is not stock. Unlocked bootloader is fine, everything else is a no-go. The different kernel is the glaring problem, you can not apply an OTA with that non-stock kernel. The first, most complete, easiest option is to flash the latest factory image. Seeing as this is a new phone to you, I can't imagine that you have a ton of personal info to save. For me personally, I'd flash the image just so I know that I'm starting with a fresh clean slate. Then you can read up and root/mod how you'd prefer.
Yaz75 said:
It is not stock. Unlocked bootloader is fine, everything else is a no-go. The different kernel is the glaring problem, you can not apply an OTA with that non-stock kernel. The first, most complete, easiest option is to flash the latest factory image. Seeing as this is a new phone to you, I can't imagine that you have a ton of personal info to save. For me personally, I'd flash the image just so I know that I'm starting with a fresh clean slate. Then you can read up and root/mod how you'd prefer.
Click to expand...
Click to collapse
I have experience with custom roms all that, i did flash this kernel, but the room, is what bothers me. and thank you, i was kinda sure this wasent stock rom! Thank you
HIGKILLER said:
"devcheck app"
Under system = Codename: Hammerhead
5.1.1
Build: LMY48I
Is this stock?
Click to expand...
Click to collapse
Not enough information from this to say. The custom kernel you installed is enough to prevent OTA updating.
Wakamatsu said:
Not enough information from this to say. The custom kernel you installed is enough to prevent OTA updating.
Click to expand...
Click to collapse
i can never find a decent post, how can i be sure this is stock rom, without having to flash the stock one?
HIGKILLER said:
i can never find a decent post, how can i be sure this is stock rom, without having to flash the stock one?
Click to expand...
Click to collapse
It would be easy to say if the build didn't match a legit N5 image. If the build info in build.prop isn't informative, look for apps/features that shouldn't be in a stock image, eg. AOSP apps replacing the Google versions. Unfortunately, you do have to have some familiarity with stock Google to be able to spot something that's out of place.
Wakamatsu said:
It would be easy to say if the build didn't match a legit N5 image. If the build info in build.prop isn't informative, look for apps/features that shouldn't be in a stock image, eg. AOSP apps replacing the Google versions. Unfortunately, you do have to have some familiarity with stock Google to be able to spot something that's out of place.
Click to expand...
Click to collapse
thank you sir
Hey,
what would u guys recommend me to do with my xperia z3?
Install another ROM or just root?
Maybe something totally different?
I guess neither Ubuntu touch nor Kali Nethunter are working :/
so what is the best option now for me ?
I found 5.1.1 version .264 the best, you can have root, Xposed and a great battery.
6.0.1 brought only a 33% lower battery life for me, with no apparent benefit (except security fixes that is)
If you have Xposed you can put the Nougat nav bar ( http://forum.xda-developers.com/xposed/modules/xposed-pixel-navigation-bar-pixel-t3502987 ) and the N-ify quick toggles/reply ( http://forum.xda-developers.com/xposed/modules/xposed-android-n-ify-features-t3345091 ) and you're done, looking like Nougat, but with the great Lollipop battery life.
I dont like to give up security :/
Is there a security or privacy based rom for xperia z3 ?
sashpta said:
I dont like to give up security :/
Is there a security or privacy based rom for xperia z3 ?
Click to expand...
Click to collapse
Try this one http://forum.xda-developers.com/z3/orig-development/rom-jaguar-leo-lp-5-1-1-official-t3482840
trainpunk said:
Try this one http://forum.xda-developers.com/z3/orig-development/rom-jaguar-leo-lp-5-1-1-official-t3482840
Click to expand...
Click to collapse
Was about to recommend that too, @sashpta remember your need an unlocked bootloader though.
Hmm oke,
Is the a detailed guide on how to do all those things? That jaguar guy also said I need LP or MM first and an unlocked bootloader etc...
I don't want to break my phone so a detailed guide would be nice.
And are still all apps working on that phone? Like WhatsApp, Firefox etc.?
sashpta said:
Is the a detailed guide on how to do all those things? That jaguar guy also said I need LP or MM first and an unlocked bootloader etc...
I don't want to break my phone so a detailed guide would be nice.
Click to expand...
Click to collapse
They're all here: http://forum.xda-developers.com/z3/general
Although, if you don't already know what those mean, things can get tricky.
Eg. unlocking the bootloader will invalidate your warranty, if you care
sashpta said:
And are still all apps working on that phone? Like WhatsApp, Firefox etc.?
Click to expand...
Click to collapse
Yes, that's a given.
Warranty is gone sincd this month, that's why I want to do something now. So that wont be a problem.
Thx for the link. I hope it all works when I try to do it.
Is there a high chance of my phone breaking?
Or is there even a way to make a backup or something so that I can recover it everytime I fail?
Do make a backup because you need to wipe all (!!) for unlocking and flashing.
Hmm k
I guess there is also a guide for those backups isnt it?
sashpta said:
Hmm k
I guess there is also a guide for those backups isnt it?
Click to expand...
Click to collapse
I'd rather save media from Download/DCIM/Whatsapp/Telegram/Music/Movies/etc.
A backup app like TItanium might work, not sure on the details though.
Licaon_Kter said:
I'd rather save media from Download/DCIM/Whatsapp/Telegram/Music/Movies/etc.
A backup app like TItanium might work, not sure on the details though.
Click to expand...
Click to collapse
Does such an app also safe the OS?
Nope, not sure what you want.
when u install that rom, then u do changes in ur current os (that is installed on ur mobile), maybe u even delete it (not sure, that's how i imagine it hehe)
so when u fail u can't go back to how it is by default (the default android version)
so i wonder if u can backup that android version that's given by sony. so no matter what happens u can just go back to it
What version do you have now? ( About-> last text down 23.something??
U mean that?
sashpta said:
U mean that?
Click to expand...
Click to collapse
Yes, you can just go back to that (and then obtain root afterwards if you want that).
And the backups for this are explained in 'general'?
There is no backup, per se, you flash whatever you want, and if you don't like it you can go back to your version.
Yes, you will probably wipe everything from your device, so MAKE A BACKUP of your stuff on your PC or something, and then play with these.
Not sure what you mean by "backup" though?!
Licaon_Kter said:
There is no backup, per se, you flash whatever you want, and if you don't like it you can go back to your version.
Not sure what you mean by "backup" though?!
Click to expand...
Click to collapse
Ah oke, I thought it's like when u change the OS on a PC.
Then the old OS is gone, so either u need a 'recovery backup' or the .iso of ur old OS. Or u hardly can go back to ur old OS.
But I guess it isnt like that with a mobile.
So is the version i have now on my android still 'under' jaguar then ? or can i just download my actual version somewhere and 'install' it on the device ?