Hey Guys,
I did a few searches and can't seem to find much information on this. But how often do you clean flash? How many dirty flashes do you do before you opt for a full clean flash? Thanks for the feedback.
If you're updating your existing ROM you can usually do as many dirty flashes as you like, do clean flashes if you run into issues. I've been dirty flashing Exodus since it switched to 5.1.1, I clean flashed then only due to the Android version change.
Thanks for the response! I am still stuck with the Windows mentality where the OS gets bogged down over time and a full reload is necessary.
Maybe switch across to Linux on your PC. I dual boot Windows 8.1 and Linux Mint 17.2 Rafaela, I basically never use Windows because I've gotten so used to Linux being incredibly responsive and fast, switching to Windows every so often just crushes my soul.
Related
Hello,
I've been using Android 4.4 since I got my OPO, and I decided to try out Lollipop.
1. Updated recovery to TWRP 2.8.7.0.
2. Flashed ROM
3. Flashed GApps
4. Flashed SuperSU 2.46
5. Wipe dalvik/cache
6. Reboot
7. Unlock phone with pincode
My phone now says that I need to insert my simcard. It is really strange that it is asking for my PIN code (It detects my SIM), and then afterwards saying that I need to insert a SIM Card.
I tried 3 different ROMs; Paranoid, OxygenOS and CM12.
You also flashed an updated firmware package for Lollipop, yes?
davebugyi said:
You also flashed an updated firmware package for Lollipop, yes?
Click to expand...
Click to collapse
No I did not. I have not been active in these forums nor in OPO forums. Did I screw up by not flashing a firmware package first?
People with similar issue said they restored their EFS backup, but I have no backup of these, I do not even remember people recommending it back when I got my phone.
Did I screw up big time?
PhillyPhong said:
No I did not. I have not been active in these forums nor in OPO forums. Did I screw up by not flashing a firmware package first?
People with similar issue said they restored their EFS backup, but I have no backup of these, I do not even remember people recommending it back when I got my phone.
Did I screw up big time?
Click to expand...
Click to collapse
First of all see if an updated firmware package helps. Try to flash this one (with TWRP 2.8.6.0 or older, neeer versions won't flash it correctly):
https://www.androidfilehost.com/?fid=23991606952604019
Be aware that for this firmware you must have a newer ROM (built > 15.05.2015)
In Case your EFS got corrupted, try to look at this guide:
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
One more thing to do is to check a different SIM, it happened to me that the card just died on me out of nowhere.
davebugyi said:
First of all see if an updated firmware package helps. Try to flash this one (with TWRP 2.8.6.0 or older, neeer versions won't flash it correctly):
https://www.androidfilehost.com/?fid=23991606952604019
Be aware that for this firmware you must have a newer ROM (built > 15.05.2015)
Click to expand...
Click to collapse
I flashed this with Paranoid Android, and it is all working now. Thanks alot, saved me alot of headache!
Any threads up about the Firmware I can read about?
PhillyPhong said:
I flashed this with Paranoid Android, and it is all working now. Thanks alot, saved me alot of headache!
Any threads up about the Firmware I can read about?
Click to expand...
Click to collapse
You can try and look at these:
http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734
http://forum.xda-developers.com/oneplus-one/general/cm11-cm12-firmware-repository-t3019881
and general (from Cyanogen):
What's a "firmware", anyway?
Okay, here's a little history:
In the past, many simple appliances and electronics-- everything ranging from advanced toasters to microwaves to industrial machines ran on "embedded", limited-purpose computer chips (micro-controllers and such) to control their operations and user interfaces. Those embedded systems would require miniature, specialized software to, say, let someone program the VCR or to receive input from a remote control to change a TV's channel.
Traditionally, this software would be written on small-capacity memory chips, usually to be written once during manufacturing and never upgraded during the life of the product. This embedded software was known as "firmware" (halfway between software and hardware), and it still exists on many electronic products, containing the programming/logic stuff that makes much of the electronic gizmos you own work. Sometimes this firmware can be updated and new functions or bug fixes may be added. For something like a refrigerator or microwave, updating the firmware is usually a torturous process, and for most electronic things, it isn't necessary.
In the case of Android phones and tablets, as well as iOS devices-- despite the fact that they may appear simply to be a phone that can run apps, what you actually have in your hand is a full-fledged, general-purpose computer. So while in the past, the "firmware" was just the simple software to make a mobile phone work, the name "firmware" has stuck to describe the software you load onto your phone, much like you'd load any operating system onto a computer.
So to be clear-- today, your Android devices are in fact very similar to your laptop and desktop computers. Because they are now based on so-called SoCs, or "system on a chip"s, modern Android devices are effectively tiny, low-power laptops, only with touch screens instead of keyboards. CyanogenMod, based on Android, is a full-fledged operating system, just like Windows, OS X, or Linux are on laptop computers. In fact, Android runs on a version of the Linux kernel, and you can even run a full Linux desktop on many Android devices just as you would on a regular laptop.
The term "firmware", then, is just a legacy terminology to refer to the software you put on your handheld devices. But speaking realistically, you may as well think of it as "software, particularly an operating system and apps, that can be put on my device."
Hope that helps.
Click to expand...
Click to collapse
Just signed up here first post to the threads but you guys been helping me out for years different devices programs huge thanks to everyone here.
New to this device I'm starting to really dig it ran couple stable 8.1 ROMs got magisk+systemless xposed running. I previously dualbooted lineage nougat with stock on my droid bionic using safestrap(wanted to add a gingerbread) before getting this phone. I flashed the Multirom Twrp but app said I was having kexec kernel issues then ended up bootlooping os or getting black screen few times ended up just full reflashing cm firmware putting regular twrp back up.
Seen video of multibooting many ROMs( but I assume older non Oreo ROMs) and Ubuntu touch from a flash drive. Is it possible for me to bootup with a safe stock, ubuntu, and a 8.1 ROM(read Aosp extended is compatible but couldnt flash a kernel on top of it)? Couldnt find stock cm 6.0.1 bacon zip was gunna try and flash think it was ap kernel again over that but I tried a couple kernels didn't know which one was the right one.
Is there any newer Multirom alternatives or proper current kernel patch link? Does EFI droid work better could I still get ubuntu? Any advice would be appreciated pointers in the right direction tried to do some digging trying to really superpower my device if I can before I log into my all apps and stuff again. Is this a wild goose chase? Or was I like one step away
*SOLVED: see reply*
The ROM I used before was LineageOS [10.0] and used a custom ROM with Android 9 before that. Needed to unlock my phone, and couldn't do that on Lineage, and had troubles flashing firmware with Odin, so I ended up using FrankensteinS6. The Stock kernel seems to let me input the NCK, and unlock the phone. So that's luckily finally over.
For about 4 days now I've been formatting phone and trying again and again. FrankensteinS6 works, some other 6.0/7.0 ROMs work. But LineageOS now enters a bootloop, and Pixel Experience (9.0 and 10.0) and Evolution X 10.0 don't detect the SIM. The ones that don't detect SIM also show no IMEI, which was worrying at first because I though I lost a partition.
Possibly related, the ROM of Pixel Experience Android 10.0 for G920W8 will not install because (paraphrasing) "This device is zeroflte, this file is for zerofltecan, zeroflte***, zeroflte***" claiming that my phone isn't one of those models. I got this S6 from Bell Canada, and I still have even the sticker that says it is a G920W8, not G920F. However, the Pixel Experience ROM for G920F flashes fine (sans the main problem).
I don't know the exact LineageOS ROM I used before, but I've tried all of their 10.0 releases, tried redownloading, and I get the bootloop every time. I see some info online of flashing modem firmware, but... I don't even know where to start with that. As I mentioned at the start, Odin is crapping out. I couldn't flash firmware with it, because it would reject the phone right after I started flashing. Anything I could do within TWRP would be great. I moved it back to FrankensteinS6 for my sanity, I started doing this Sunday and I'm starting to repeat steps over and over hoping that it just solves itself.
I tried to keep this straightforward, and I'm sure I did a bad job. I can extrapolate on what I have attempted. Please tell me what I have to do to get an android 10 ROM working on this old beauty again.
I do not have all the solutions. As per my tests with my SM-G920W8. I have managed to find ROMS and try them out. I have only seen Nougat 7.0 ROMS to work almost flawlessly. NOT 7.1.2, important, 7.0 only.
I have also tested some Pie and v10 ROMS like Pixel Experience. The ROMS boot nicely but since I do not use a SIM card to call as I use SIP phone numbers and require WiFi. But that left asside, I came upon serious camera issues no matter what I try. Up to now, SamStock ROM is pretty much the best Stock ROM I found but I always need to run the Magisk UNINSTALLER before re-installing the latest Magisk version..
As for Kernels, well, Anything that is oriented with Lineage OS, I've had camera issues even with Nougat v7.0. So basically, the only ROMS I found good, as of today, for now, are stock ROMS v7.0. But, to do your tests, Even if you have a 920F ROM, you can download a 920W8 kernel as long as you download a kernel which supports your installed Android version. Also make sure to download the proper Stock or AOSP kernel (AOSP for LineageOS). There's not many but there's a few ones that work properly.
Another option is to download an AOSP ROM that works for W8 phones, unzip the file and grab the boot file inside corresponding to the W8 or T-Mobile version. You simply unzip your real ROM you want top install, replace the boot file for the one you got and rezip it. This made my phone boot properly for some F version ROMS but again, not without issues. That's why, I really suggest v7.0 Srock ROMS. I hope this helps you a bit. Again, you can have your own tests and other users may have other answers, but this is based off over 30 bootloops in my case of trying to mod a ROM for the W8 model. It's not easy to find a good one for Canada, I admit!!!
I flashed TWRP years ago, and I found out that I had a G920F version flashed. I don't know why Lineage allowed me to use SIM before, but rectifying this issue seems to made the SIM work in newer versions.
I don't know what the S6's predisposition to having crashing cameras is, but I have avoided this in the past by using custom camera apps, like Open Camera. This has saved me every time.
As for the boot loops... I think another thing that helped is that "format data" doesn't wipe the OS. When you are in recovery, having issues with bootloops in various ROMs, try advanced wipe, and wipe the system. It didn't fix right away, but the time I got Pixel Experience 10 up and running that was the trick.
I have a regular OnePlus 7 PRO (GM1913)
My bootloader is unlocked and I am rooted with Magisk on Android 10, with Oxygen 10.3.4 Stock.
something got funky with switching between apps and keyboard gets stuck sometimes and camera crashes, could be Nova launcher, could be Swiftkey, idk really
but I guess its time for a refresh to see if that fixes the problem (which I believe it will).
My Questions are:
1: How would I go on about flashing a custom ROM / latest Stock (recommendations welcome) without wiping data and keeping everything intact?
2: do I need a PC for that or can I do it "Over the air"? (sorry not fluent in this stuff since a long time)
Thank you!
Well, I'm not an expert but I've done that for the same reason as yours; ended up with the stock OxygenOS. Actually it started with stock OTA updater, ended with a brick(then unbrick)...
I've tried several custom roms, but
stock camera app is irreplaceable (Custom OS got more options, but Android 10+ is difficult to tinker with)
Even the most popular custom OS's may crash with an upgrade (especially if you tinker with your system). So whatever is wrong with it now, may got worse, or better.. Or it may get worse later(or not, who knows).
OTA doesn't do downgrades and check the signature of the package, so if something goes wrong or if you want oos back, you may need to use EDL with MSM Tools(Which, unfortunately requires a PC)
Thats why your safest bet is to:
Backup everything you can't afford to lose, then prepare an unbrick tool image if you can. You can backup without pc, but using edl or fastboot requires PC or other android device as a host device.
By the way, It's not that fun after a hundreds of reboot and flashes, so I use Linux now
I've had a strange issue with my LG V20 ever since I got in last year and installed LineageOS 18.1 after rooting my H990 on LG firmware 10d (H990ds10d_00_OPEN_AU_DS_OP_1216.kdz) with DirtySanta and installing TWRP. Whenever I left the range of my Wi-Fi network, I would cause the System UI to become unresponsive while doing certain tasks - Unlocking, going to Settings -> Wi-Fi, expanding the Wi-Fi quick toggle in notifications, and probably a few more things.
This doesn't happen on the aforementioned stock firmware, nor on 10g AU 0117 stock firmware either.
For a while, I dealt with it by simply not using Wi-Fi. This sucked because I couldn't access computers over LAN, mobile data was slower, and it also had a data cap that I had to be wary of.
However, I decided I wanted to fix it.
I saw some recommendations involving installing every Lineage version since 14.1 sequentially until the latest. This didn't make sense to me, as clean flashing shouldn't leave any remnants behind, but dirty flashing that many versions went against everything I'd ever heard of regarding custom ROMs.
I also heard that it could be a modem firmware issue. Since I started on the last version of the stock OS for my region vulnerable to DirtySanta I thought surely not.
I later found out about KDZWriter, and used that to install the latest Nougat version of the stock rom available (also mentioned above). After installing that, I tried installing the latest LOS on top, which constantly informed me that com.android.media had stopped, I still had the LG sounds and wallpapers, and I didn't go through the initial setup - A sign of a dirty flash. I was still crashing in the same way too.
I formatted my data partition in TWRP (the "type yes to confirm" way), and tried again. Same crashes.
I've been awake for a little too long trying to fix this, but :
What I believe ended up working was backing up my /efs and /firmware partitions in TWRP while on rooted 10g firmware, dirty flashing LOS on top, formatting data as before, then flashing my /firmware backup in TWRP.
I'm hoping for this thread to document this issue as well as the fixes that worked for people. I saw tidbits of information spread out everywhere, so I'd like a central repository for it.
I hope this caffeine-induced writeup will help someone else with the same or similar issues.
If I have any more experiences with it, I'll do my best to write them down. Please share your experiences too!