FlashFire! - Google Pixel Questions & Answers

Hey guys, has anybody seen that the flashfire app has been updated to work for our pixels? I've installed and can confirm that it sees both boot slots and everything seems good but I havent had time to actually attempt flashing anything with it. Still, with the silly number of steps we have to go through to flash mods and updates to this device, I feel like this app could really cut back on some of the hassle. Thoughts?

https://forum.xda-developers.com/showpost.php?p=70793032&postcount=589

Oface82 said:
Hey guys, has anybody seen that the flashfire app has been updated to work for our pixels? I've installed and can confirm that it sees both boot slots and everything seems good but I havent had time to actually attempt flashing anything with it. Still, with the silly number of steps we have to go through to flash mods and updates to this device, I feel like this app could really cut back on some of the hassle. Thoughts?
Click to expand...
Click to collapse
Yes I was going to try to do a back up. When I pick slot b it shows double of every partition is that normal? I never have used FlashFire

If I pick slot a it looks normal I think

To be honest I'm pretty that I've never seen it list two of everything like that with another device but not positive. I'm running a backup right now then I'm going to try flashing stuff

]
Oface82 said:
To be honest I'm pretty that I've never seen it list two of everything like that with another device but not positive. I'm running a backup right now then I'm going to try flashing stuff
Click to expand...
Click to collapse
just did one. I did a reboot and opened it up and it shows it just one time. But if I close FlashFire and reopen it. It shows double or triple partitions. If I reboot system it's OK again. Might just be a glitch.

Oface82 said:
Hey guys, has anybody seen that the flashfire app has been updated to work for our pixels? I've installed and can confirm that it sees both boot slots and everything seems good but I havent had time to actually attempt flashing anything with it. Still, with the silly number of steps we have to go through to flash mods and updates to this device, I feel like this app could really cut back on some of the hassle. Thoughts?
Click to expand...
Click to collapse
Just tried to update 7.1.2 OTA with flashfire on a rooted Pixel with Adaway.
Major fail. It put the device into a boot loop.

Download 7.1.1 April security patch zip and flash OK
Then download 7.1.2 zip and flash OK
Root access intact for all time.
Now I want to stretch for other mods like WETA audio MOD.
Is it possible?
P.S. WETA mentioned that only support TWRP

Related

[Q] Can Only Boot to Recovery

About 30 minutes ago my phone was working fine, the last thing I remember doing was sending a text. A few minutes later I look down at my phone and notice it is in recovery. At this point I'm confused wondering how it got there, but figure it's whatever and reboot into system. It reboots back into recovery and at this point I'm kinda freaking out. I do a backup, wipe, and restore from a backup ~2 weeks ago. Again, rebooting just causes my phone to go into recovery.
Earlier today there was a notification on my phone about an update but I just ignored it as I didn't have time to deal with it. I assume that it automatically was applied and that is what caused this problem.
edit: If you have this problem, try this: http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
Same thing just happened to me.
I turned off OTA from earlier today and also removed the notification using AppOps and now I can't boot to anything but TWRP
nest75068 said:
Same thing just happened to me.
I turned off OTA from earlier today and also removed the notification using AppOps and now I can't boot to anything but TWRP
Click to expand...
Click to collapse
I'm about to try this, http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508, if it works I'll let you know.
elguy said:
I'm about to try this, http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508, if it works I'll let you know.
Click to expand...
Click to collapse
Was coming here to say this worked - I was already doing this.
I'm back up and running again.
Not sure wtf caused the issue - I didn't take the OTA and have been fine on the phone all day until just now
nest75068 said:
Was coming here to say this worked - I was already doing this.
I'm back up and running again.
Not sure wtf caused the issue - I didn't take the OTA and have been fine on the phone all day until just now
Click to expand...
Click to collapse
Yeah, worked me too. Not sure what happened either, phone says its still on KVT49L.D85010d.
Rooted, bumed TWRP. All of the above applies to me. Recovered, but back to stock. Annoyed that I have to start all over
gpgon said:
Rooted, bumed TWRP. All of the above applies to me. Recovered, but back to stock. Annoyed that I have to start all over
Click to expand...
Click to collapse
I was the same - the zip file fixed my issue - didn't have to start over
Gotta love XDA.. i was getting ready for bed.. saw a bright light, it was my phone. Same thing as mentioned. only rooted and bumped. Have been denying the OTA. Even did the hidden menu trick, but still got notifications for some reason. Flashing the ZIP showed success; trying to restore my back up now.
esoteric1311 said:
Gotta love XDA.. i was getting ready for bed.. saw a bright light, it was my phone. Same thing as mentioned. only rooted and bumped. Have been denying the OTA. Even did the hidden menu trick, but still got notifications for some reason. Flashing the ZIP showed success; trying to restore my back up now.
Click to expand...
Click to collapse
Once you flash the zip you shouldn't need to restore. I just clicked on reboot system and was back in
nest75068 said:
Once you flash the zip you shouldn't need to restore. I just clicked on reboot system and was back in
Click to expand...
Click to collapse
Well i had to restore the newest back up, because I restored an old back up to see of it would reboot correctly. All works fine now. Still very weird.
gpgon said:
Rooted, bumed TWRP. All of the above applies to me. Recovered, but back to stock. Annoyed that I have to start all over
Click to expand...
Click to collapse
I mean I still have Root and TWRP, I might have factory reset in my panic last night before finding the fix above. Probably the cause of losing all my apps and data
ATTT Forced UPDATE
It would appear after cruising the forums this morning that ATT forced an update to all users last night. It happened to me and many others like yourself. even people that had turned off updates in the hidden menu. It is total crap and not to happy about it obviously. good thing it sent me into a boot loop, and @autoprime zip fixed me up, even though i was back up on stock rooted, I took this opportunity to move over to the PoweruserV1 international rom to attempt to keep this from happening again. Luckily our DEVS are getting development moving and soon this will be a thing of the past....
I froze Software Update with TB and did not get auto updated last night and have not gotten any new nags today. I did try to update yesterday and got the stuck in TWRP thing and flashed the fix to get back working.
KennyG123 said:
I froze Software Update with TB and did not get auto updated last night and have not gotten any new nags today. I did try to update yesterday and got the stuck in TWRP thing and flashed the fix to get back working.
Click to expand...
Click to collapse
whats the name of the apk to freeze? Thanks
Just adding to this, that it was 'forced' onto me as well, and also sent me to soft brick loop (TWRP), so I'm having to use the get out of jail thread. THANKS LG!! YOU GUYS ROCK!!! (#[email protected]%&*!!!!) This is the LAST time I trust another corporate BS liar's announcement that they care about the 'community' and are going to try and be nice 'from here on out'. Moving forward, it will be NEXUS and nothing else for me.
esoteric1311 said:
whats the name of the apk to freeze? Thanks
Click to expand...
Click to collapse
It is called Software Update in TB. I only have it frozen since last night so hopefully this does the trick...it also removes update option from settings FYI.
Anyone else have this happen again last night? Phone was fine at 5am, woke up at 8:30 to recovery. Flashed the same zip and now it's all fine again.
Freeze software update with titanium backup so your phone doesn't try to install the update agian
wow att and their updates f*** with everything, currently having a locked s4 with old firm of mf3. i plan on upgrading my device but on the fence with all this lock down bs. switching to tmobile seems like a decent option...... so confused and undecided

OnePlus One Malfunction? Help please

G'day people I've run into something pretty weird with my OnePlus One. I installed the CM12 nightly and booted it up, ran it for a few hours then got ghost touches and the screen became unresponsive at times.
So, having my usual backup of CM11S, I wiped and restored to the latest backup I had and everything was weird. I kept getting ghost touches and reduced responsiveness, and sometimes it would just randomly malfunction and not unlock and just keep the screen off.
Rebooting clears up the problem for about 5 minutes and then it comes back at full blast.
I tried installing the last CM11S update via flashing Calkunins stock XNPH44S zip and still I have all these weird issues that wasn't there before I flashed the CM12 nightly.
Has anyone come across this problem or is it just me and my device? It's seriously a cause for concern, and I'm posting this to both XDA and the OnePlus forums in hopes of getting some sort of help and relief in this situation.
Any assistance is appreciated and I thank you in advance for taking the time to read this.
reflash cm12 nightly and try again.
perhaps use fastboot to flash the partitions .
You might need to find a copy of the first cm11s rom and try that one. I have a feeling your one of the unlucky with firmware sensitivity.
Which date is your phone from? (its on the box)
Sent from my A0001 using XDA Free mobile app
GO back to completely factory fresh, via fastboot commands.
If you still have problems, it's a hardware issue then.
kthejoker20 said:
GO back to completely factory fresh, via fastboot commands.
If you still have problems, it's a hardware issue then.
Click to expand...
Click to collapse
not entirely true, there are different screens, that could be the issue. It was reported in boeffla kernel thread. sesrch throught it and it might contain something useful to try.
also open a support question, Oneplus needs to know how annoying their poor choice of different lcds are
Sent from my A0001 using XDA Free mobile app
bachera said:
reflash cm12 nightly and try again.
perhaps use fastboot to flash the partitions .
You might need to find a copy of the first cm11s rom and try that one. I have a feeling your one of the unlucky with firmware sensitivity.
Which date is your phone from? (its on the box)
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I'll try to flash CM11S via fastboot to see if it clears up the issue. For now, the date I got mine is 2014-07-16. Shipped to me after 12 days (International shipment via courier)
UPDATE
Flashing CM11S via fastboot resolved all issues as far as I can tell.
Will remain on the lookout for the bugs in the future but for now I'm happy to say it worked for me.
Thank you all again for the advice and guidance, it was appreciated.
GLad it worked for you.
I love when other posters try to punk you when you try to help people.
kthejoker20 said:
GLad it worked for you.
I love when other posters try to punk you when you try to help people.
Click to expand...
Click to collapse
Nobody was trying to "punk" you. There are usually several different potential causes for the same symptom, all he was doing was highlighting that and adding extra information in order to help further (in the case that flashing the stock images didn't help, which has happened many times). He was also trying top help the OP. Calm down.
Transmitted via Bacon
timmaaa said:
Nobody was trying to "punk" you. There are usually several different potential causes for the same symptom, all he was doing was highlighting that and adding extra information in order to help further (in the case that flashing the stock images didn't help, which has happened many times). He was also trying top help the OP. Calm down.
Transmitted via Bacon
Click to expand...
Click to collapse
I thought it was the partition thing too because I had almost the same problem on my HTC Amaze back in 2014, and flashing the OEM RUU helped with sorting things out.
But as for the random screen touches, flashing everything from fastboot helped for only a few hours. The symptoms came back after a while, specifically when I replaced my music and pictures. I'm thinking that I may have a corrupted file on it somewhere but I doubt it'll cause a malfunction like that.
So I tried flashing Franco Kernel, and it seems to have cleared it up..... for now.
It's so frustrating thinking that my device may be defective
UPDATE #2
Flashing Franco Kernel didn't help. Symptoms came back within a couple hours. Will try a custom ROM, specifically AOPK (because I want to )
If that doesn't fix the issue then I've just got to face the fact that I have a defective device (somehow)
Bump
Nothing worked. I contacted the manufacturer but they seem to think doing a factory reset will help. It didn't.
Flashing CM11S via fastboot doesn't help
I really think this is a hardware issue that just emerged from nowhere, probably due to lack of premium or standardized quality adhesive.
There's a really long thread over at the OnePlus forums about a guy who found it was a grounding issue and took some adhesive tape to insulate the area near the proximity sensor (I think? I'll include the link in here somewhere)
Honestly, OnePlus impressed me....at first. But I cannot use a phone that's not working properly.
https://forums.oneplus.net/threads/...-hint-it-was-never-a-software-problem.186235/
Same problem here... I had the first ghost touches after having installed CM12 Nightly.
I was using CM12 built by Daleski75 so far without any issue. The problem does not appear on a regular basis and when it does, a reboot seems to fix it, at least for a few minutes/hours.
I'll try a clean install when the stable version is out (don't really want to wipe now and once more in two/three weeks).
@rdar_93: Did you find a solution? Are you going to send the device back to OnePlus? If it is actually a hardware issue, that will be enough for me, no more OPO. Sending the device back to China after 2 months of use and having to pay for the shipping is not acceptable.
Edit: It's getting worse... I am gonna wipe soon. Here is a short video: drive.google.com/file/d/0B-EYHGTB15_wS1JXdXlmZXVsT0k/view?usp=sharing
I can't post link for now so you'll have to copy and paste it in your browser.
Edit2: After a full wipe and the installation of the latest nightly, the situation seems to be better, even though I will have to use the phone a bit more to see if it happens again. By the way, I lost dt2w and the gestures don't work well, if not at all... When I draw a V, nothing happens, when I draw a circle, the phone behaves as if I did a double tap. Weird. Again, this happens after a wipe+latest nightly installation+wipe again (to be sure ).
sylvain15250 said:
Same problem here... I had the first ghost touches after having installed CM12 Nightly.
I was using CM12 built by Daleski75 so far without any issue. The problem does not appear on a regular basis and when it does, a reboot seems to fix it, at least for a few minutes/hours.
I'll try a clean install when the stable version is out (don't really want to wipe now and once more in two/three weeks).
@rdar_93: Did you find a solution? Are you going to send the device back to OnePlus? If it is actually a hardware issue, that will be enough for me, no more OPO. Sending the device back to China after 2 months of use and having to pay for the shipping is not acceptable.
Edit: It's getting worse... I am gonna wipe soon. Here is a short video: drive.google.com/file/d/0B-EYHGTB15_wS1JXdXlmZXVsT0k/view?usp=sharing
I can't post link for now so you'll have to copy and paste it in your browser.
Edit2: After a full wipe and the installation of the latest nightly, the situation seems to be better, even though I will have to use the phone a bit more to see if it happens again. By the way, I lost dt2w and the gestures don't work well, if not at all... When I draw a V, nothing happens, when I draw a circle, the phone behaves as if I did a double tap. Weird. Again, this happens after a wipe+latest nightly installation+wipe again (to be sure ).
Click to expand...
Click to collapse
I contacted them and they sent me a program to use. It uses fastboot to flash CM11S and probably fix the partitions that are messed up (I'm making an assumption)
UNFORTUNATELY I'm stuck in a bootloop.
I'm so angry, disappointed and depressed at the same time. I paid about $2500 TTD (in my country) which is probably the equivalent to somebody's rent. I had to work a month to save up the money to buy this and it turns out that the device is faulty after a certain amount of time (or at least mine was)
This is BS.
They said to send them a snapshot of what went on with the fastboot thing, so I figure I"ll upload it here too.
rdar_93 said:
I contacted them and they sent me a program to use. It uses fastboot to flash CM11S and probably fix the partitions that are messed up (I'm making an assumption)
UNFORTUNATELY I'm stuck in a bootloop.
I'm so angry, disappointed and depressed at the same time. I paid about $2500 TTD (in my country) which is probably the equivalent to somebody's rent. I had to work a month to save up the money to buy this and it turns out that the device is faulty after a certain amount of time (or at least mine was)
This is BS.
They said to send them a snapshot of what went on with the fastboot thing, so I figure I"ll upload it here too.
Click to expand...
Click to collapse
I guess you didnt unlock bootloader first
Which when you do wipes the phone so you loose all your stuff.
possible workaround is fasboot on custom recovery and then flash the zip that sets unlock status and circumvents the whole format thing
Sent from my A0001 using XDA Free mobile app
bachera said:
I guess you didnt unlock bootloader first
Which when you do wipes the phone so you loose all your stuff.
possible workaround is fasboot on custom recovery and then flash the zip that sets unlock status and circumvents the whole format thing
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I actually did unlock my bootloader.
PS I also got tired of seeing CM11S try to boot up so I flashed ColorOS (because it's the only rom I had on my laptop. Why not download another 4.4.x AOSP rom? Unstable wifi at school)
So yeah, wifi is not turning on. Gonna try the program again. I wonder if it would work this time?
The conditions aren't as different as before, could work, right?
Honestly I want to wait but they take so long to reply.
UPDATE
After flashing ColorOS I decided to go back and try doing the CM11S via fastboot commands. Still got a bootloop but hey I got the correct fastboot logo now in case if it made a difference.
So I did the compulsory flashing commands when I went from Color to CM11S and still bootlooped.
So I booted into fastboot again
fastboot oem unlock (supposed to unlock bootloader and reboot if it's locked, no reboot if unlocked [assumption])
then rebooted into fastboot again, ran the batch files OnePlus sent to me which essentially flashed CM11S just like you would over fastboot, but with added modems etc.
Successfully booted into CM11S without issues, WiFi works again and so far no symptoms as yet.
Will keep this post updated if anything happens.
My screenshots of the batch file commands OnePlus sent would be found in the attachments.
UPDATE 2
So I think it's fixed permanently this time.
I'm not sure though. It hasn't done anything weird. I will copy my music and photos to see if that would cause anything to happen
I would stay away from os since it messes up partition and people ran into data drop out and modem issues.
Cm11s Roms are the way to go on this hardware.
FYI, when you flash CM12 the radio is overwritten with an alpha/beta radio which causes (well, caused for me) THE EXACT issues OP was having in CM11/S. The CM12 radio (as far as I can tell) ONLY works with CM12 - making going back a PITA.
If you have the baseband in this thread (see screenshot in first post) then that means you are on the experimental radio and are going to have a bad time if you aren't on CM12.
I flashed the latest OTA radio found here and all was right with the world (at least where my OPO was concerned ).
hp13 said:
I would stay away from os since it messes up partition and people ran into data drop out and modem issues.
Cm11s Roms are the way to go on this hardware.
Click to expand...
Click to collapse
I would like to go back to CM11s to check if the situation is better. I tried to flash the lastest CM12 build and it seems to be better but still not as good as before
When I do a wipe and then flash the ROM in TWRP, there are some "folder already up to date", which I would like to avoid. What I would like to do is doing a complete clean install of either CM12 or CM11s plus rewriting the partitions,... So that I'm sure if the problem is still here it is due to an hardware issue.
Is there any chance someone can help me with this? Even with a link... I searched for "write partition" without any luck :-/
Thanks !
EDIT: Do you think the OnePlusRecovery Tool can help me with this?

How to stop lollipop from installing automatically?

I have just noticed my G3 is taking the ota without asking for my approval. How can I stop it from doing it again? Thanks in advance.
Secret Menu
I went to the dialer keypad and typed in 3845#*850#, the 850 is my model number. Change it to your model # and secret menu will appear. Tap on WLAN settings and it will show OTA updates and pick disable. That's it. Worked for me.
Did that but the phone will still try to install. The reason I know is because my phone will be boot looping in twrp. At first I thought I did something crazy until this morning I saw a message saying phone will install update and will reboot in 10 seconds. Good thing is that I have the boot loop fix zip file in my sdcard.
I kept having this happen to me as well, even after disabling the option in the secret menu. I ended up installing the 855 minus 5 ROM.
I actually had that happen as well. My whole system was gone and stuck in twrp. I downloaded the copy of the 10f stock file and the zip fix file. Thought everything was good, then the update popped up again in the notifation bar, so I made a backup in twrp and tried disabling notifications. The next morning it started to auto install and it failed. Stuck in twrp again, ran my backup then disabled notifications again. Haven't seen the update again in the notifications. Hopefully it won't come back.
Using TiBu, I disabled/froze com.leg.lgfota.permission and Software Update and I have not had any issues.
Sent from my LG G3 D850
So I tried Titanium Backup. Couldn't figure out how to do it. I also noticed I couldn't send or receive MMS pics. Did some searching and on Google Play, there is an app called Disable Service. Download the app, open it, click on system at the top, scroll down to Google Play Services and click on it. Scroll down to SystemUpdateService and uncheck the box. I also went down to software update and unchecked all 3 of those boxes. Restart your phone and you're done. I also re enabled the setting in the secret menu. Now my pics come through again and the update disappeared when I restarted the phone.
Can the OTA be undone?
auky said:
I have just noticed my G3 is taking the ota without asking for my approval. How can I stop it from doing it again? Thanks in advance.
Click to expand...
Click to collapse
This may be a dumb question but I had something similar happen and I'm desperately looking for a way to reverse things. My D850 was rooted, still stock but tweaked to PERFECTION, and I was under the false impression that the OTA checked for root and wouldn't proceed, so when I got the notification that the update was available I dismissed it and didn't think about it. Next morning I woke up to find the OTA happened without any action from me and of course I lost root. The phone is now really sluggish with numerous nuisances and I hate it. AT&T really f'd up my perfect G3. I chose not to factory reset or clear the cache as some have suggested to improve performance. I guess I was hoping that with everything still installed there might be some hope to regain root.
I'm reading about people going back back and flashing zip files but I don't get how it's being done. I did not have a custom recovery installed but I did have a backup with Titanium, although I obviously can't get into that now without root. The really odd thing is that Softcard still thinks it's rooted and won't run. Anybody have any ideas?
Thanks,
...Joe K.
jkovacs89 said:
This may be a dumb question but I had something similar happen and I'm desperately looking for a way to reverse things. My D850 was rooted, still stock but tweaked to PERFECTION, and I was under the false impression that the OTA checked for root and wouldn't proceed, so when I got the notification that the update was available I dismissed it and didn't think about it. Next morning I woke up to find the OTA happened without any action from me and of course I lost root. The phone is now really sluggish with numerous nuisances and I hate it. AT&T really f'd up my perfect G3. I chose not to factory reset or clear the cache as some have suggested to improve performance. I guess I was hoping that with everything still installed there might be some hope to regain root.
I'm reading about people going back back and flashing zip files but I don't get how it's being done. I did not have a custom recovery installed but I did have a backup with Titanium, although I obviously can't get into that now without root. The really odd thing is that Softcard still thinks it's rooted and won't run. Anybody have any ideas?
Thanks,
...Joe K.
Click to expand...
Click to collapse
I'm afraid you wont be able to go back to rooted kitkat without having to clean install as there is no root for Lollipop yet.
aybarrap1 said:
Using TiBu, I disabled/froze com.leg.lgfota.permission and Software Update and I have not had any issues.
Sent from my LG G3 D850
Click to expand...
Click to collapse
Hey aybarrap just curious if the TiBu freezing has held up. Took your advice and did the same. Just curious if you've had any issues so I can be on the lookout.
adosin said:
Hey aybarrap just curious if the TiBu freezing has held up. Took your advice and did the same. Just curious if you've had any issues so I can be on the lookout.
Click to expand...
Click to collapse
I have NOT received a single nag or download for OTA. I have had these frozen for over two months without seeing any issues in the phone's operations. In fact I waited 10 days after the 10f was released before installing and had no issues.

Recovered from boot loop but constant crashes with older ROM

I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Jst flash a newer modem in recovery
mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.
Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.

Noble rom nougat running on g920v !

Dont use noble nougat ! Use ultimate nougat under the unified development . There are 3 different versions either one is okay. Everything works on ultimate nougat but noble lags a good bit.
Each one has a description on what it does and has. All are bebloated + custom tweaks. Check them out. Any touchwiz rom should work. As long as ported to sg g920f.
You have to be on nougat stock firmware. At least thats all ive tried. You can try on 5.1 as long as you follow my guide. Go to this site - https://forum.xda-developers.com/verizon-galaxy-s6/general/root-nougat-s6-verizon-t3710864 and download the files he has on his post. Thats how you root on nougat.
If you are on nougat, switch to bootloader mode, open odin, and click on ap and select the eng root. Then reboot and go to settings/security and tick unknown sources. Then extract the unroot file you downloaded and run the file that says root.bat and give your phone a few minutes. It will restart and supersu will be installed. If it doesnt work the first time try again
Now you need to download flashfire. And download the custom touchwiz rom you want. Again you can find them under unified developement. And gapps if you want. I use aroma installer to pick what apps i want to be system apps.
Once you are rooted have supersu and flashire, youll need to set you year on the date back to 2013 or flashfire wont open correctly. It does that on my phone atleast you can try it out. When u have flashire open click on the + at the bottom right and click flash zip or ota. Click on the ron youve downloaded and then select the box next to mount system read and write . Then press the + button again and add a wipe action. Just leave it on what it automatically tics. Make sure you hold down on the wipe action before hitting the flash button at the bottom and put it above the rom installation. So youre phone restores first. Do not tick internal storage on the wipe action you will brick your phone bc no sd card.
Flashfire should take you through an aroma installer for the rom depending on the one youve downloaded. Make sure to pick g920f kernel.
Go through chek what you want and then install. As long as you hit the mount system read and write button on the wipe action back in flashfire it will install and not get stuck on %20 or %25. Once its done let it reboot your phone will come to a crash screen. A blue one with a warning sign saying software failure or something. You need to hold the power button volume down and homd button until it cuts off. The do the same thing to turn it on in download mode and flash the eng root file in ap again from odin and your phone will boot. It takes about 10 to 15 minutes to boot.
I installed xposed and all kinds of other tweaks to this rom as well. Let me know how it works out for you . Im going to upload photos in the replies.
Able to flash and open twrp but no function.
Just Google a touchwiz rom ported to galaxy s6 and follow my instructions. I've tried 2 others. Everything seems to be working other than if you are not rooted there is intense lagging from time to time.
I have some questions, is this on 5.1.1 rooted with mrmikes root? Is the rom pre-rooted? Is it debloated? And does it have s health?
this needs a more in-depth description, when i tried it, i flashed it on 5.1.1, i got to the setup of the rom, i chose the international s6, i didnt know which one to choose, then the CSC variant, i chose one of them which had a description like "multi us, it started installing, it got to 25%, then the screen just went black, i opened rootatboot, it succesfully worked, but my phone screen is still black, what are we supposed to do?
Arethmetik said:
this needs a more in-depth description, when i tried it, i flashed it on 5.1.1, i got to the setup of the rom, i chose the international s6, i didnt know which one to choose, then the CSC variant, i chose one of them which had a description like "multi us, it started installing, it got to 25%, then the screen just went black, i opened rootatboot, it succesfully worked, but my phone screen is still black, what are we supposed to do?
Click to expand...
Click to collapse
Sorry i updated my op check it out ^^
And if you have black screen then boot to odin mode and flash nougat. I know for sure it works on there. And if you follow my steps i suggest using ultimate nougat note fe rom. Its bloatware free and smooth as butter. Has aod edge screen and alot more tweaks.
Shaden Stewart said:
Sorry i updated my op check it out ^^
And if you have black screen then boot to odin mode and flash nougat. I know for sure it works on there. And if you follow my steps i suggest using ultimate nougat note fe rom. Its bloatware free and smooth as butter. Has aod edge screen and alot more tweaks.
Click to expand...
Click to collapse
Thanks!
---------- Post added at 03:24 AM ---------- Previous post was at 03:00 AM ----------
Shaden Stewart said:
Sorry i updated my op check it out ^^
And if you have black screen then boot to odin mode and flash nougat. I know for sure it works on there. And if you follow my steps i suggest using ultimate nougat note fe rom. Its bloatware free and smooth as butter. Has aod edge screen and alot more tweaks.
Click to expand...
Click to collapse
For me the note fe rom downloads at 700kb/s why? roms usually download at like 7-8 mb/s
Not able to do it, When i flash stock nougat with odin, it gets stuck on the galaxy s6 logo after reboot. Then i factory reset and wiped cache partition, and its still stuck there. So i had no choice but to downgrade to 5.1 again. Now i flashed the pre rooted official nougat rom with flashfire, and once i was on nougat i was gonna flash the custom rom. But, when you try to flash something in flashfire on the pre rooted nougat rom it gives me an error saying an unknown error has occured. Now im back at rooted 5.1. Help anyone?
Arethmetik said:
Not able to do it, When i flash stock nougat with odin, it gets stuck on the galaxy s6 logo after reboot. Then i factory reset and wiped cache partition, and its still stuck there. So i had no choice but to downgrade to 5.1 again. Now i flashed the pre rooted official nougat rom with flashfire, and once i was on nougat i was gonna flash the custom rom. But, when you try to flash something in flashfire on the pre rooted nougat rom it gives me an error saying an unknown error has occured. Now im back at rooted 5.1. Help anyone?
Click to expand...
Click to collapse
Would you like me to upload a backup of my rom that you can just flash in flashfire? Or post a video of me showing how to do this.
Shaden Stewart said:
Would you like me to upload a backup of my rom that you can just flash in flashfire? Or post a video of me showing how to do this.
Click to expand...
Click to collapse
I'd reccommend video and flashfire, you can make a video of how to do it and make it easier by flashing it in flashfire, so a tutorial on how to flash it on flashfire correctly.
Followed the procedure but flashfire just remains blank on boot... why?
Arethmetik said:
I'd reccommend video and flashfire, you can make a video of how to do it and make it easier by flashing it in flashfire, so a tutorial on how to flash it on flashfire correctly.
Click to expand...
Click to collapse
I can do that. I will edit op with link when im done.
Jewizzle said:
Followed the procedure but flashfire just remains blank on boot... why?
Click to expand...
Click to collapse
Did you check the box that said mount system read and write when clicking on the file to flash ? And did you add a wipe action before adding the rom ? And are u rooted with super su ?
Shaden Stewart said:
Did you check the box that said mount system read and write when clicking on the file to flash ? And did you add a wipe action before adding the rom ? And are u rooted with super su ?
Click to expand...
Click to collapse
yes... followed everything to the letter. Was having issues with the flashfire but i downloaded the pro apk and it acquired root permission without crashing... I used flashfire .57 pro to flash the pre rooted rom but the flashfire in the pre rooted rom also crashed after aquiring root so I uninstalled it and downloaded the .73 pro apk and that worked but it doesn't flash the rom no matter what options I choose. Tried so many combinations... I put the wipe before the flash and i also tried vice versa, tried with flash procedure set to normal, recovery, download and all still came out with the same outcome = Blank flashfire with 2015-2017 screen. So i just restart the device and everything is normal. Using the pre rooted rom for now
Jewizzle said:
yes... followed everything to the letter. Was having issues with the flashfire but i downloaded the pro apk and it acquired root permission without crashing... I used flashfire .57 pro to flash the pre rooted rom but the flashfire in the pre rooted rom also crashed after aquiring root so I uninstalled it and downloaded the .73 pro apk and that worked but it doesn't flash the rom no matter what options I choose. Tried so many combinations... I put the wipe before the flash and i also tried vice versa, tried with flash procedure set to normal, recovery, download and all still came out with the same outcome = Blank flashfire with 2015-2017 screen. So i just restart the device and everything is normal. Using the pre rooted rom for now
Click to expand...
Click to collapse
Okay do everythig you did again but before opening flashfire you need to turn off wifi. Go to settings and date and time. Turn off automatic date and time and set year to 2013 then re open and use flashfire. That was my original problem.
I've tried everything to get mobile data and service to work that is the only bug but makes this thread a complete bust until I can find a work around or fix for it.
Shaden Stewart said:
I've tried everything to get mobile data and service to work that is the only bug but makes this thread a complete bust until I can find a work around or fix for it.
Click to expand...
Click to collapse
Good luck, this phone badly needs something custom
Shaden Stewart said:
I've tried everything to get mobile data and service to work that is the only bug but makes this thread a complete bust until I can find a work around or fix for it.
Click to expand...
Click to collapse
I use my s6 as a backup phone but something is wrong with my s7 so i use my s6 more, and i dont use a verizon sim so i use my s6 with no sim. So, if you can, can you make still make a video for it? other people who flash it might find a way to get service to work.
Arethmetik said:
I use my s6 as a backup phone but something is wrong with my s7 so i use my s6 more, and i dont use a verizon sim so i use my s6 with no sim. So, if you can, can you make still make a video for it? other people who flash it might find a way to get service to work.
Click to expand...
Click to collapse
Yes I made one but I've been having trouble uploading it internet has been very bad
Shaden Stewart said:
Yes I made one but I've been having trouble uploading it internet has been very bad
Click to expand...
Click to collapse
Do you mean uploading very slowly or you cant upload it
Arethmetik said:
Do you mean uploading very slowly or you cant upload it
Click to expand...
Click to collapse
I haven't been able to upload it but I'll get to internet wither today or tomorrow to upload it. Sorry for the long wait

Categories

Resources