Gapps - Nexus 6 Q&A, Help & Troubleshooting

Hello! Just had a question, might even be a stupid question, but curiosity is a thing. What exactly happens if you flash wrong gapps for your device? I don't mean Android version, I mean for a different CPU architecture? Like, if I were to flash gapps for arm64 or x86 on my Nexus 6 that is actually arm? Does it just not boot and can be restored easy? Or is that a much more in depth fix? Just curious. Thanks guys!

H4X0R46 said:
Hello! Just had a question, might even be a stupid question, but curiosity is a thing. What exactly happens if you flash wrong gapps for your device? I don't mean Android version, I mean for a different CPU architecture? Like, if I were to flash gapps for arm64 or x86 on my Nexus 6 that is actually arm? Does it just not boot and can be restored easy? Or is that a much more in depth fix? Just curious. Thanks guys!
Click to expand...
Click to collapse
If the gapps package is the incorrect version it should run an installation check of your ROM version and fail to flash. In the event that it doesn't contain this check and the packages are installed, it would be a lot like installing a debian package in an rpm environment--it just won't work. Whether this means getting stuck at the boot screen because it is trying to access apps that aren't there or if it actually boots seeing force closes when you attempt to access the installed packages.
It just depends on whether you clean flashed, dirty flashed, what package you tried to install, what services try to run, etc etc etc.

AlkaliV2 said:
If the gapps package is the incorrect version it should run an installation check of your ROM version and fail to flash. In the event that it doesn't contain this check and the packages are installed, it would be a lot like installing a debian package in an rpm environment--it just won't work. Whether this means getting stuck at the boot screen because it is trying to access apps that aren't there or if it actually boots seeing force closes when you attempt to access the installed packages.
It just depends on whether you clean flashed, dirty flashed, what package you tried to install, what services try to run, etc etc etc.
Click to expand...
Click to collapse
Oh alright! So worst case scenario, just soft brick and can be easily recovered with a nandroid or a fastboot flash? Nothing beyond that?

H4X0R46 said:
Oh alright! So worst case scenario, just soft brick and can be easily recovered with a nandroid or a fastboot flash? Nothing beyond that?
Click to expand...
Click to collapse
It's no worse or better than just flashing ROMs over top of other ROMs because it is only installing files to the system partition. Wiping system undoes any wrongfully flashed Gapps or mods.

AlkaliV2 said:
It's no worse or better than just flashing ROMs over top of other ROMs because it is only installing files to the system partition. Wiping system undoes any wrongfully flashed Gapps or mods.
Click to expand...
Click to collapse
Cool dude thanks! It's these simple little curiosity questions that we over look and never try ourselves just in case it's a huge mistake! haha thanks again!

H4X0R46 said:
Hello! Just had a question, might even be a stupid question, but curiosity is a thing. What exactly happens if you flash wrong gapps for your device? I don't mean Android version, I mean for a different CPU architecture? Like, if I were to flash gapps for arm64 or x86 on my Nexus 6 that is actually arm? Does it just not boot and can be restored easy? Or is that a much more in depth fix? Just curious. Thanks guys!
Click to expand...
Click to collapse
Earth would implode then plummet into the Sun. Twice.
But really nothing worse than what can occur during development. Either bootloop, or endless FCs, that you can't acknowledge as fast as the system is throwing them at you. I've tried all. So you boot to bootloader, flash your system again, then boot to recovery, and flash the good gapps this time.

Related

[Q] Install Android only

Hello All;
I have decided to try and male my HP touch pad an Android only touch pad.
I need help though as i am a novice at best.
I am looking for help on the files i will need. Want to install CM 10 recent and CWM.
Do i need a boot loader or will that be in the ROM?
And what other files will i need?
i am assuming i need a ROM, Recovery, and GAPPS. Other than that i am not sure.
Found someone on the WebOS Nation who is willing to help so i dont want to go into this like and idiot, i want to have my ducks in a row.
Any help will be appreciated
thanks
This is a good guide: http://forum.xda-developers.com/showthread.php?t=2147284. As for Android-only, I don't recommend it. WebOS has gotten me out of Android trouble before.
Install Android only
bananagranola said:
This is a good guide: http://forum.xda-developers.com/showthread.php?t=2147284. As for Android-only, I don't recommend it. WebOS has gotten me out of Android trouble before.
Click to expand...
Click to collapse
Good point, Hey let me ask you something.
I like flashing ROMs but I always end up with a mess. Moboot, i dont think updates as grub2 does. So, i have thought the best way to switch ROMs would be treating the ROM as a first install, does that make sense and do you agree?
Or do you know a method to change ROMs that works well for you?
geomonroe said:
Good point, Hey let me ask you something.
I like flashing ROMs but I always end up with a mess. Moboot, i dont think updates as grub2 does. So, i have thought the best way to switch ROMs would be treating the ROM as a first install, does that make sense and do you agree?
Or do you know a method to change ROMs that works well for you?
Click to expand...
Click to collapse
Android doesn't update the way Linux does, it only updates apps; the bootloader isn't going to update neatly from a package manager. At the same time, updating the TP's bootloader (moboot) is usually unnecessary. On the other hand I usually like to keep my recovery (TWRP/CWM) up to date. When I switch ROMs I just wipe and flash from recovery. Never had a problem.
Install Android only
bananagranola said:
Android doesn't update the way Linux does, it only updates apps; the bootloader isn't going to update neatly from a package manager. At the same time, updating the TP's bootloader (moboot) is usually unnecessary. On the other hand I usually like to keep my recovery (TWRP/CWM) up to date. When I switch ROMs I just wipe and flash from recovery. Never had a problem.
Click to expand...
Click to collapse
I wander what i am doing wrong? i had skizoid and wanted to go back to cyanogenmod. followed the rules for flashing a rom and at the bootloader i had an entry still on the list for skiziod and the cyanogen entry, when i clicked the cyan entry i got the eternal loading screen.
geomonroe said:
I wander what i am doing wrong? i had skizoid and wanted to go back to cyanogenmod. followed the rules for flashing a rom and at the bootloader i had an entry still on the list for skiziod and the cyanogen entry, when i clicked the cyan entry i got the eternal loading screen.
Click to expand...
Click to collapse
What rules are you following? Full wipe? Leaving extra stuff in moboot is normal. You can delete the extras if they really bother you.
wipe cache and dalvik and factory reset
geomonroe said:
wipe cache and dalvik and factory reset
Click to expand...
Click to collapse
You should wipe system as well and if the extra uimage is still there you can delete it using a file manager after booting
4catalyst2cI said:
You should wipe system as well and if the extra uimage is still there you can delete it using a file manager after booting
Click to expand...
Click to collapse
As far as I know, most ROM install scripts automatically wipe system for you. Can't hurt to try, though.
Thankfully I have this zip again thanks to sstar posting it the other day. This zip will wipe your ulmage clean. Just flash it as you would a rom, than flash rom and gapps after.
https://copy.com/3F9kE

Nexus 6 forced encryption questions.

Hello! So I just have some questions about the forced encryption on the Nexus 6. I will be getting a Nexus 6 very soon here, and I like custom ROMs and custom software. Questions are:
1) Can I install a custom ROM without even messing with the forced encryption? In other words, can I ignore that it's there and just unlock bootloader, install custm recovery, and flash a ROM and gapps? Will it just run with the encryption on?
2) If I do disable the encryption, can I use the normal software update? (with no custom ROM of course in this case) Or will I have to reflash the encrypted kernel to system update?
3) Do some custom ROMs just disable the encryption by default?
And
4) If it get stuck in a boot loop because of a kernel issue, is this easy fixable? Or is it a hard brick that can't be recovered?
Thanks in advance everyone!
H4X0R46 said:
Hello! So I just have some questions about the forced encryption on the Nexus 6. I will be getting a Nexus 6 very soon here, and I like custom ROMs and custom software. Questions are:
1) Can I install a custom ROM without even messing with the forced encryption? In other words, can I ignore that it's there and just unlock bootloader, install custm recovery, and flash a ROM and gapps? Will it just run with the encryption on?
2) If I do disable the encryption, can I use the normal software update? (with no custom ROM of course in this case) Or will I have to reflash the encrypted kernel to system update?
3) Do some custom ROMs just disable the encryption by default?
And
4) If it get stuck in a boot loop because of a kernel issue, is this easy fixable? Or is it a hard brick that can't be recovered?
Thanks in advance everyone!
Click to expand...
Click to collapse
1. Yes
2. You can't update with any modifications to the system. Meaning you must have stock recovery, no root, etc.
3. Yes (They don't FORCE encryption meaning if your unencrypted already you will stay unencrypted.)
4. Yes
Sent from my Nexus 6 using Tapatalk
Thanks for the quick response! Much appreciated. On my fourth question, did you mean that's easily fixable? Or like, yes that's a hard brick? And also, (question 3) you say that a custom ROM won't force it, but if you're still encrypted when you flash the ROM, does that mean you can just turn it off in your settings with a ROM? Or do you stay encrypted? Or how does that work?
EDIT: (question 2) if I used a toolkit to reflash a stock image, that's clean enough for a normal system update right? After that and relocking the bootloader?
Sorry for all the questions, I just wanna know these things before I go fork out $600 for a device that I intend to mod!
H4X0R46 said:
Thanks for the quick response! Much appreciated. On my fourth question, did you mean that's easily fixable? Or like, yes that's a hard brick? And also, (question 3) you say that a custom ROM won't force it, but if you're still encrypted when you flash the ROM, does that mean you can just turn it off in your settings with a ROM? Or do you stay encrypted? Or how does that work?
EDIT: (question 2) if I used a toolkit to reflash a stock image, that's clean enough for a normal system update right? After that and relocking the bootloader?
Sorry for all the questions, I just wanna know these things before I go fork out $600 for a device that I intend to mod!
Click to expand...
Click to collapse
To be unencrypted, you must format data. Do not use toolkits unless you know how to use ADB/fastboot. Yes this phone is hard to brick as long as the bootloader is unlocked.
H4X0R46 said:
Hello! So I just have some questions about the forced encryption on the Nexus 6. I will be getting a Nexus 6 very soon here, and I like custom ROMs and custom software. Questions are:
1) Can I install a custom ROM without even messing with the forced encryption? In other words, can I ignore that it's there and just unlock bootloader, install custm recovery, and flash a ROM and gapps? Will it just run with the encryption on?
2) If I do disable the encryption, can I use the normal software update? (with no custom ROM of course in this case) Or will I have to reflash the encrypted kernel to system update?
3) Do some custom ROMs just disable the encryption by default?
And
4) If it get stuck in a boot loop because of a kernel issue, is this easy fixable? Or is it a hard brick that can't be recovered?
Thanks in advance everyone!
Click to expand...
Click to collapse
3. its the kernel, not rom, that makes you be abke to decrypt, not rom. it might be added to a rom as well, but it would be in its kernel. also, ot doesnt decrypt, it gives you the option to decrypt. but you have to do it, decrypt.
4 easily fixable. you have to learn the very basics of it though. rrally. but its extremely easy to fix.
---------- Post added at 09:49 PM ---------- Previous post was at 09:46 PM ----------
H4X0R46 said:
Thanks for the quick response! Much appreciated. On my fourth question, did you mean that's easily fixable? Or like, yes that's a hard brick? And also, (question 3) you say that a custom ROM won't force it, but if you're still encrypted when you flash the ROM, does that mean you can just turn it off in your settings with a ROM? Or do you stay encrypted? Or how does that work?
EDIT: (question 2) if I used a toolkit to reflash a stock image, that's clean enough for a normal system update right? After that and relocking the bootloader?
Sorry for all the questions, I just wanna know these things before I go fork out $600 for a device that I intend to mod!
Click to expand...
Click to collapse
learn to do it right the first time. it sounds hard and complicated, but its extremely easy after you do it all manually the first time. after that, feel free to use a toolkit. it wont save you time btw, doing it right takes just 3-5 minutes after the first time
Thanks guys! Much appreciated! If things were to go horribly wrong with the kernel if I did decrypt it and it bricked because of a kernel issue, would flashing a stock image still be a fix for a kernel problem? (with the bootloader unlocked of course). I'm not new to Android modding, I have a phone running a CM nightly right now, but this encryption thing and messing with a phones kernel scares me a bit haha
H4X0R46 said:
Thanks guys! Much appreciated! If things were to go horribly wrong with the kernel if I did decrypt it and it bricked because of a kernel issue, would flashing a stock image still be a fix for a kernel problem? (with the bootloader unlocked of course). I'm not new to Android modding, I have a phone running a CM nightly right now, but this encryption thing and messing with a phones kernel scares me a bit haha
Click to expand...
Click to collapse
Flashing any rom also flashes a kernel, so you've already done it before. Its no different here
danarama said:
Flashing any rom also flashes a kernel, so you've already done it before. Its no different here
Click to expand...
Click to collapse
Alright, custom ROMs contain kernels. I've heard that before but wasn't sure haha Thanks everyone!
H4X0R46 said:
Alright, custom ROMs contain kernels. I've heard that before but wasn't sure haha Thanks everyone!
Click to expand...
Click to collapse
every rom haa a kernel in it. a rom can not run without a kernel. a kernel is like what will connect the cpu and hardware with the os.
H4X0R46 said:
If things were to go horribly wrong with the kernel if I did decrypt . . .
Click to expand...
Click to collapse
The first question you need to answer is:
'Why decrypting?'
When the answer contains words like 'speed' or 'performance' than you may consider to leave your N6 encrypted.
NLBeev said:
The first question you need to answer is:
'Why decrypting?'
When the answer contains words like 'speed' or 'performance' than you may consider to leave your N6 encrypted.
Click to expand...
Click to collapse
right :good:
chavonbravo said:
Try Ultimate Theft Alert v3.5 and W.I.M.P. Both have ability to track via GPS when your phone gets stolen as well.
Click to expand...
Click to collapse
Well, I've heard from many sources that the encryption in the phone just KILLS battery life, and if you turn off the encryption, it nearly triples the battery life. Is this true? Because it would be a waste if the phones battery is abysmal for such a great device! From anyone's experience here, should I not worry about it and just leave the device encrypted?
H4X0R46 said:
Well, I've heard from many sources that the encryption in the phone just KILLS battery life, and if you turn off the encryption, it nearly triples the battery life. Is this true? Because it would be a waste if the phones battery is abysmal for such a great device! From anyone's experience here, should I not worry about it and just leave the device encrypted?
Click to expand...
Click to collapse
I wouldn't say it triples battery, just increases the NAND read/write speed performance. Battery could take a hit as opening apps takes longer when encrypted.
Choristav said:
I wouldn't say it triples battery, just increases the NAND read/write speed performance. Battery could take a hit as opening apps takes longer when encrypted.
Click to expand...
Click to collapse
Apps aren't encrypted. If they were we couldn't pull them from phone to decompile and mod them. Only your data is and it is only a few KBs per app. Only notice encryption on large personal files and downloads.
H4X0R46 said:
Well, I've heard from many sources that the encryption in the phone just KILLS battery life, and if you turn off the encryption, it nearly triples the battery life. Is this true? Because it would be a waste if the phones battery is abysmal for such a great device! From anyone's experience here, should I not worry about it and just leave the device encrypted?
Click to expand...
Click to collapse
im encrypted, and my n6 sees between 5.5-7 hours sot. thats more than most unencrypted phones see!
---------- Post added at 08:28 PM ---------- Previous post was at 08:26 PM ----------
battery life is all about how you personally use the device, how you set it up, which apps you use, and your phone/data signal quality. everything else plays a minor role for battery.
Alright! So if I just ignore the encryption and install a ROM, it won't pose a problem at all? I can say, leave it encrypted and install a cm ROM without issue? And because of the encryption, do operations like installing a zip and formatting the device take a lot longer? I'm using a Galaxy Note 2 right now and the ROM installations take mere seconds to install, so a Nexus 6 might be something different.
H4X0R46 said:
Alright! So if I just ignore the encryption and install a ROM, it won't pose a problem at all? I can say, leave it encrypted and install a cm ROM without issue? And because of the encryption, do operations like installing a zip and formatting the device take a lot longer? I'm using a Galaxy Note 2 right now and the ROM installations take mere seconds to install, so a Nexus 6 might be something different.
Click to expand...
Click to collapse
Only problems you will notice is all the CM bugs.
H4X0R46 said:
Alright! So if I just ignore the encryption and install a ROM, it won't pose a problem at all? I can say, leave it encrypted and install a cm ROM without issue? And because of the encryption, do operations like installing a zip and formatting the device take a lot longer? I'm using a Galaxy Note 2 right now and the ROM installations take mere seconds to install, so a Nexus 6 might be something different.
Click to expand...
Click to collapse
formatting is how you decrypt. besides decrypting, theres no need to ever format your device. installing a zip it depends on the zip, generally its fast. flashing a zip is fast. what will be slowed down is tranafering a large file to your computer to or from a pc.
oh, and cm does get many bugs, often.
Oh yea! Bugs for sure! I'm running a cm nightly right now on my Note 2 and it's buggy as hell haha I just like messing with ROMs really, I will probably leave it stock and rooted for the most part Just like to see new ROMs and tweaks and stuff. Thanks guys! You all helped a ton! I will probably buy a Nexus 6!
H4X0R46 said:
Well, I've heard from many sources that the encryption in the phone just KILLS battery life, and if you turn off the encryption, it nearly triples the battery life. Is this true?
Click to expand...
Click to collapse
.
I have tried decryption with the Chroma and CM Roms. I did not notice more performance in daily use.
Then 5.1.1 arrives with some confusion because Google presented several factory images for the N6. I went back to stock and waited for the OTA.
After flashing the OTA and Franco's kernel my battery life was about the same.
Of course it depends on the daily use, but for me it was clear that not decrypting causes better battery life but the kernel.

A ROM question

Not gonna ask the best ROM, as everyone gets a bit uptight about those, and feel the need to defend "their team" and all that...
My question is more generic, in that I am wondering if there is even a ROM out there that will meet MY needs... so if I list those things that I would need in a ROM, maybe someone can simply answer yes or no and point me in the right direction?
Here is what I would be looking for in a ROM:
1) Stability, has to be as stable as stock, no screens of dead or random reboots
2) Speed, zero lag, fast and fluid
3) Everything has to work. If it works on stock, be it apps like VZW Visual VM or whatever, it needs to work on the ROM
4) More polish and eye candy, nice animations, make the device beautiful to use without being buggy or laggy
5) Battery life at least as good as stock
If there is a ROM that gives you all that, has a bit more customization but not so much that it takes half a day to set it up, what would it be? Or would I be better served just using a different launcher?
I have not installed a ROM in a couple years... I was a flashaholic for awhile, but a few phones that I had in a row worked really well in stock form, and some had locked bootloaders that never got cracked, so I kinda gave up on them for while and so my knowledge is a bit rusty...
What I don't want to do is go to the trouble of installing a new ROM and having it not work, or be buggy, etc... This has to be daily driver quality and I want to USE it, no spend too much time fiddling with it.
Ideas?
SquireSCA said:
Not gonna ask the best ROM, as everyone gets a bit uptight about those, and feel the need to defend "their team" and all that...
My question is more generic, in that I am wondering if there is even a ROM out there that will meet MY needs... so if I list those things that I would need in a ROM, maybe someone can simply answer yes or no and point me in the right direction?
Here is what I would be looking for in a ROM:
1) Stability, has to be as stable as stock, no screens of dead or random reboots
2) Speed, zero lag, fast and fluid
3) Everything has to work. If it works on stock, be it apps like VZW Visual VM or whatever, it needs to work on the ROM
4) More polish and eye candy, nice animations, make the device beautiful to use without being buggy or laggy
5) Battery life at least as good as stock
If there is a ROM that gives you all that, has a bit more customization but not so much that it takes half a day to set it up, what would it be? Or would I be better served just using a different launcher?
I have not installed a ROM in a couple years... I was a flashaholic for awhile, but a few phones that I had in a row worked really well in stock form, and some had locked bootloaders that never got cracked, so I kinda gave up on them for while and so my knowledge is a bit rusty...
What I don't want to do is go to the trouble of installing a new ROM and having it not work, or be buggy, etc... This has to be daily driver quality and I want to USE it, no spend too much time fiddling with it.
Ideas?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
Evolution_Tech said:
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
Click to expand...
Click to collapse
Hmmm... that might be what I am looking for...
Does the latest version have the stagefright fix built in?
SquireSCA said:
Hmmm... that might be what I am looking for...
Does the latest version have the stagefright fix built in?
Click to expand...
Click to collapse
Yes.
Evolution_Tech said:
Yes.
Click to expand...
Click to collapse
Cool. And I am sorry if this is a dumb question, but like I said, it has been a couple years since I installed a ROM...
I can use Wug's Nexus toolkit to install a custom recovery, and then take the downloaded ROM and recommended GAPPS files, go into Recovery, install ROM, install Gapps, then factory reset and I am good to go?
SquireSCA said:
Cool. And I am sorry if this is a dumb question, but like I said, it has been a couple years since I installed a ROM...
I can use Wug's Nexus toolkit to install a custom recovery, and then take the downloaded ROM and recommended GAPPS files, go into Recovery, install ROM, install Gapps, then factory reset and I am good to go?
Click to expand...
Click to collapse
I don't personally recommend toolkits unless you have ADB/fastboot knowledge and experience but otherwise yes. You don't need to factory reset after ROM installation, just do the required wipes, generally listed in the OP of the ROM you choose, in TWRP, prior to flashing.
Evolution_Tech said:
I don't personally recommend toolkits unless you have ADB/fastboot knowledge and experience but otherwise yes. You don't need to factory reset after ROM installation, just do the required wipes, generally listed in the OP of the ROM you choose, in TWRP, prior to flashing.
Click to expand...
Click to collapse
Which is the better/easier Recovery to use?
SquireSCA said:
Which is the better/easier Recovery to use?
Click to expand...
Click to collapse
TWRP recovery is THE recovery for shamu.
Evolution_Tech said:
TWRP recovery is THE recovery for shamu.
Click to expand...
Click to collapse
Got it, just installed it. Put the ROM and Gapps in a folder and I will first make a Nandroid of my current setup... Then I will try it out.
The OP for that ROM doesn't have any instructions, but you said that in TWRP that I need to wipe cache and stuff PRIOR to installing the ROM? I always thought you did that last? Am I remembering it wrong or did something change?
SquireSCA said:
Got it, just installed it. Put the ROM and Gapps in a folder and I will first make a Nandroid of my current setup... Then I will try it out.
The OP for that ROM doesn't have any instructions, but you said that in TWRP that I need to wipe cache and stuff PRIOR to installing the ROM? I always thought you did that last? Am I remembering it wrong or did something change?
Click to expand...
Click to collapse
For your first installation, wipe, used advanced wipe, then select dalvik, cache, data, and system. Then flash your ROM. Updates to the same ROM can usually be "dirty flashed" by simply wiping cache and dalvik prior to installation.
Tried it out, but found that it was slower in Antutu by 3,000 points and it was a bit laggy at times... Weird.
I wouldn't hold a ton of value or base anything off Antutu.
Sorry if I didn't pay attention to time stamps between your posting. I did look at your stats and see you have plenty of experience here. May just need to give a bit of time for ROM to settle.
I have tried several ROMs here and consider there to be a BIG 3, or the most popular. I won't say the names due to the fact that I don't want to place any one above the other. However, I would recommend a ROM with Layers.
When you go to wipe prior, wipe all but internal storage. I wipe twice, just because I am OCD. Flash all necessaries and sometimes an alternate kernal will help, but give baked in kernal a chance. At least a cylcle or two. Wipe the Davlik and Cache after flash, as TWRP suggests.
There are a few to choose from which are close to stock without overdoing it. Most things folks want to do to customize can be done with apps in Play Store without over loading file size of ROM.
OK, I'll say it, but I don't want you to think I am partial. Try Chroma
Sent from my Nexus 6 using XDA Free mobile app
captemo said:
I wouldn't hold a ton of value or base anything off Antutu.
Sorry if I didn't pay attention to time stamps between your posting. I did look at your stats and see you have plenty of experience here. May just need to give a bit of time for ROM to settle.
I have tried several ROMs here and consider there to be a BIG 3, or the most popular. I won't say the names due to the fact that I don't want to place any one above the other. However, I would recommend a ROM with Layers.
When you go to wipe prior, wipe all but internal storage. I wipe twice, just because I am OCD. Flash all necessaries and sometimes an alternate kernal will help, but give baked in kernal a chance. At least a cylcle or two. Wipe the Davlik and Cache after flash, as TWRP suggests.
There are a few to choose from which are close to stock without overdoing it. Most things folks want to do to customize can be done with apps in Play Store without over loading file size of ROM.
OK, I'll say it, but I don't want you to think I am partial. Try Chroma
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Oh trust me, I have no concerns with people being partial. Some people get bent out of shape in "best ROM" debates, but I don't. I WANT to know which ones are top tier, and why, from people that have used them.
I know that Antutu is not the end all be all... But when I saw it was laggy, I run that to see if it is just placebo, and sure enough, it was slower and there was a little stuttering and lower frame rates in the final 3D game test... I just use it as a reference point, that's all...
I played with Layers a little and didn't really get much out of it... It just seemed to change the color a bit on menus and things, so I didn't see a lot of benefit.... or am I missing something?
I will take a look at Chroma and see how that looks, thanks.

Fastboot question.

Hello guys! I have a simple and probably obvious question for you all! So, when a new update comes out and it's the same Android version, can you get away with just flashing the Bootloader, Radio, and System partition? Leaving your userdata intact and keeping your apps? Thanks!
H4X0R46 said:
Hello guys! I have a simple and probably obvious question for you all! So, when a new update comes out and it's the same Android version, can you get away with just flashing the Bootloader, Radio, and System partition? Leaving your userdata intact and keeping your apps? Thanks!
Click to expand...
Click to collapse
yes. you don't have to flash the bootloader nor the radio either
Not required. If you look inside the factory image files, often times, the bootloader and radio are just being recycled from prior versions.
Thanks guys! So just the system is required for an update? I can leave my custom kernel alone, with systemless root? You guys are so helpful! Thanks again!
H4X0R46 said:
Thanks guys! So just the system is required for an update? I can leave my custom kernel alone, with systemless root? You guys are so helpful! Thanks again!
Click to expand...
Click to collapse
Personally, I've never gotten the "flash-all" command to work, maybe some of you here have, but it never works for me, so I open the factory image and fastboot each component in. The wiping of data is in the flash-all script which I don't use. In your case, I'd just pull the system image and flash it, then delete everything else. I haven't checked to see if there is a new bootloader or radio. I'm downloading right now.
mikeprius said:
Personally, I've never gotten the "flash-all" command to work, maybe some of you here have, but it never works for me, so I open the factory image and fastboot each component in. The wiping of data is in the flash-all script which I don't use. In your case, I'd just pull the system image and flash it, then delete everything else. I haven't checked to see if there is a new bootloader or radio. I'm downloading right now.
Click to expand...
Click to collapse
Cool thanks! From now on, I'll probably md5 check the radio and Bootloader files to see if they match between versions. And I've always flashed my images manually, I like to know what's being done to my phone, I don't trust the flash-all script and never used it before lol
H4X0R46 said:
Cool thanks! From now on, I'll probably md5 check the radio and Bootloader files to see if they match between versions. And I've always flashed my images manually, I like to know what's being done to my phone, I don't trust the flash-all script and never used it before lol
Click to expand...
Click to collapse
I just checked. The most recent version has the same bootloader and baseband. Save yourself the 1GB download LOL. No need.

I cant flash Super Su or new rom TWRP

Cant flash Super SU or Any rom as it goes into bootloop.
I have been following the procedure quite thoroughly .
Need Help ..
aka70698 said:
Cant flash Super SU or Any rom as it goes into bootloop.
I have been following the procedure quite thoroughly .
Need Help ..
Click to expand...
Click to collapse
So, TWRP is properly installed?
What kind of errors do you receive?
Unleashed by ONEPLUS 3T rooted
no error it just stucks...everything installs without any error
aka70698 said:
no error it just stucks...everything installs without any error
Click to expand...
Click to collapse
Sounds like you forgot to format the data partition between ROM swap, or flashed ROM for wrong Oneplus device.
Agreed, you probably didn't wipe data.
Miracles don't really exist in Android land. It works for everyone else.
Mate, we need more information;
What ROM's have you tried flashing it over?
Anything you've flashed recently?
Have you tried flashing Magisk or another SuperU method?
Have you tried a clean flash, without GAPPS or other bloat, and simply just flashing the package and the ROM?
Have you tried wiping your entire storage and then flashing?
aka70698 said:
Cant flash Super SU or Any rom as it goes into bootloop.
I have been following the procedure quite thoroughly .
Click to expand...
Click to collapse
Posting that you "followed the procedure quite thoroughly" doesn't' tell us anything, if you don't actually describe what you did.
Similar to another response, I'm wondering if you did a clear flash (default wipe in TWRP) before flashing a ROM. For that matter (like another asked) what ROMs did you try specifically. Or what version TWRP or version SuperSU?
Using old versions of TWRP or SuperSU is a really common mistake, and will lead to boot loops, or no boot. Folks will often assume they are using the "right version" and then when you ask for more info, it turn out they are using something totally obsolete, old guide, etc.
Good rule of thumb: when asking for help, provide as much detail as possible. Exact steps taken (step by step, in chronological order), with file names and version numbers. Asking for help, with a post consisting of 2 or 3 sentences, is never going to be enough.

Categories

Resources