What's the proper way to dirty flash? I used to be able to dirty flash on my OnePlus One by just flashing the ROM and Gapps and it'll boot right away. But with the 5T, half the time this method doesn't work anymore and I get stuck on the splash screen. I don't use passwords or pins so there should be no encryption, but even when I flash no-verity.zip, my phone still gets stuck on the splash screen.
geokilla said:
What's the proper way to dirty flash? I used to be able to dirty flash on my OnePlus One by just flashing the ROM and Gapps and it'll boot right away. But with the 5T, half the time this method doesn't work anymore and I get stuck on the splash screen. I don't use passwords or pins so there should be no encryption, but even when I flash no-verity.zip, my phone still gets stuck on the splash screen.
Click to expand...
Click to collapse
wipe dalvik art cache, cache and system
I do that just like with all my other phones, but it just hangs on the splash screen. Dirty flashing used to be so simple but now even clean flash doesn't work 100%.
geokilla said:
I do that just like with all my other phones, but it just hangs on the splash screen. Dirty flashing used to be so simple but now even clean flash doesn't work 100%.
Click to expand...
Click to collapse
Don't wipe Dalvik / ART cache, you will have problems. Factory Reset will I usually make it boot again. If you do a clean flash boot once before installing things like Magisk.
Wipe cache, Flash ROM, Gapps, Kernel if you run a custom ROM.
Make sure you are not using the official TWRP, either codeworkx or blu_spark (eng.stk). Having. a password or pin is NOT a problem.
OhioYJ said:
Don't wipe Dalvik / ART cache, you will have problems. Factory Reset will I usually make it boot again. If you do a clean flash boot once before installing things like Magisk.
Wipe cache, Flash ROM, Gapps, Kernel if you run a custom ROM.
Make sure you are not using the official TWRP, either codeworkx or blu_spark (eng.stk). Having. a password or pin is NOT a problem.
Click to expand...
Click to collapse
Factory Reset and even wipe data doesn't boot. Only way I got it to boot was to wipe internal storage. It would however flash stock OxygenOS fine though. It's just every time I tried to dirty flash or even clean flash Havoc OS without wiping internal storage I'd get issues it seems.
geokilla said:
Factory Reset and even wipe data doesn't boot. Only way I got it to boot was to wipe internal storage. It would however flash stock OxygenOS fine though. It's just every time I tried to dirty flash or even clean flash Havoc OS without wiping internal storage I'd get issues it seems.
Click to expand...
Click to collapse
I would ask in the Havoc OS thread then. That would seem out of the ordinary. For Lineage most people dirty flash every week. I clean flash every so often, but I basically never clean flash my wife or sons phone, no issues. So these issue might be isolated to the ROM you are trying to run.
Not to mention wiping internal storage all the time would be very annoying...
OhioYJ said:
I would ask in the Havoc OS thread then. That would seem out of the ordinary. For Lineage most people dirty flash every week. I clean flash every so often, but I basically never clean flash my wife or sons phone, no issues. So these issue might be isolated to the ROM you are trying to run.
Not to mention wiping internal storage all the time would be very annoying...
Click to expand...
Click to collapse
I've asked in the Havoc OS thread but the instructions to clean and dirty flash are the same as when I first played with custom ROMs back in the Samsung Galaxy S days. Wipe system, wipe data, wipe the two caches, etc etc.
If you're using a Substratum theme, make sure to disable all overlays before flashing.
Sorry for digging this post, but with android 10 there is no way to decrypt the data partition.
So how do you dirty flash android 10 "properly" ?
Related
Hey guys,
I always have to pull my battery out multiple times on reboots, or after flashing a rom.
When I change roms, I do a fact. reset and wipe cache/dalvik, on updates of same rom I only do a wipe of cache/dalvik. I tried fixing permissions.
How is this caused ? It eventually boot up every time, just very annoying.
Does wiping system help ? I've read that most rom dev's include it anyway in flashing rom.
Phone: Samsung Galaxy Nexus
Rom: AOSP Paranoid Android 2.99 beta 5
Recovery: TWRP 2.3.2.1
Thnx for your help!
Firewalker1980 said:
Hey guys,
I always have to pull my battery out multiple times on reboots, or after flashing a rom.
When I change roms, I do a fact. reset and wipe cache/dalvik, on updates of same rom I only do a wipe of cache/dalvik. I tried fixing permissions.
How is this caused ? It eventually boot up every time, just very annoying.
Does wiping system help ? I've read that most rom dev's include it anyway in flashing rom.
Phone: Samsung Galaxy Nexus
Rom: AOSP Paranoid Android 2.99 beta 5
Recovery: TWRP 2.3.2.1
Thnx for your help!
Click to expand...
Click to collapse
I haven't encountered this but I sometimes get bootloop when I flash Gapps without wiping cache and dalvik. Whenever I flash a new ROM, I do factory reset, wipe system, cache, and dalvik. So you may try wiping all of them and make a fresh install of the ROM then see if this problem keeps affecting you. Just make a nandroid backup in case this does not help so you restore your whole data easily
ahmadallica said:
I haven't encountered this but I sometimes get bootloop when I flash Gapps without wiping cache and dalvik. Whenever I flash a new ROM, I do factory reset, wipe system, cache, and dalvik. So you may try wiping all of them and make a fresh install of the ROM then see if this problem keeps affecting you. Just make a nandroid backup in case this does not help so you restore your whole data easily
Click to expand...
Click to collapse
Hey thx for your suggestions!
I always flash a "new" rom that way though. But an update of the same rom, I "dirty" flash, which should be fine according to everyone.
No matter what Rom/Kernel I use, I still frequently have to pull the battery out.
It's never from locking up within Android. It just freezes/loops on the Google bootlogo.
I once wiped everything, even the storage space, and it helped for a little while, but did not make it go away for good.
Could it be related to certain apps ? Maybe PGM or Seeder or smth ?
All input welcome
---------------------------------------------------------------
Phone: Samsung Galaxy Nexus Maguro
Rom: AOSPA 2.99 latest
Kernel: AK Purity v20
Recovery: TWRP 2.3.3.0
Ok, so i was using the cyanogenmod nightlys just fine until i decided to want to try other roms (Pac-man, exodus, etc.) when i loaded the first i used clockwork recovery and it seemed to go smoothly and installed the Gapps, and BAM boot loop, i can still access the recovery menu and the Odin mode menus with the boot sequence, ive successfully side-loaded other roms and Gapps and nothing seems to work, everything just gives me the boot loop, Any help is much appreciated.
Edit: forgot to mention, sometimes it loads the rom but only for a few seconds and reboots again
Assume you did clean flash? Wiping data, cache, dalvik cache.
Also twrp recovery works a little better flashing lollipop roms.
madbat99 said:
Assume you did clean flash? Wiping data, cache, dalvik cache.
Also twrp recovery works a little better flashing lollipop roms.
Click to expand...
Click to collapse
yes, i did a clean flash, do you think it could be as simple as using twrp?
Could even be the gapps you're using. If you're using a very recent build of a rom, make sure you're using new gapps. Try open gapps.
It's also sometimes necessary to wipe internal storage.
madbat99 said:
Could even be the gapps you're using. If you're using a very recent build of a rom, make sure you're using new gapps. Try open gapps.
It's also sometimes necessary to wipe internal storage.
Click to expand...
Click to collapse
ive tried different versions of gapps but ill give open another shot, whats the best way to wipe the internal storage?
Shadow00f said:
ive tried different versions of gapps but ill give open another shot, whats the best way to wipe the internal storage?
Click to expand...
Click to collapse
In twrp. Wipe/advanced wipe/ internal storage. Make sure you have anything you need from internal backed up.
After flashing TWRP with Odin, I boot into recovery and wipe the dalvik cache. I then go to install the CM13 zip file, and it works. I wipe Dalvik again and reboot in the os. This is where it just shows the CM boot screen infinitely. Nothing else. What is up. I am using the latest TWRP and CM13 release.
Try this:
1. Wipe cache, dalvic cache, data, system
2. Install CM13 again, along with your gapps(google apps if you didn't know, custom ROMs never come with them, optional)
3. Boot it, it should work
You cannot switch ROMs without wiping data. Bad things happen.
You must clean flash when:
1. Switching between a stock ROM to a custom ROM
2. Downgrading Android versions (5.1 to 5.0)
3. Switching custom ROMs (I.E. CM13 to AICP)
4. When the ROM's thread warns to (switching keys)
5. Switching between nightly builds and stable.
When you're updating nightlies, you shouldn't have to though.
RDChase said:
Try this:
1. Wipe cache, dalvic cache, data, system
2. Install CM13 again, along with your gapps(google apps if you didn't know, custom ROMs never come with them, optional)
3. Boot it, it should work
You cannot switch ROMs without wiping data. Bad things happen.
You must clean flash when:
1. Switching between a stock ROM to a custom ROM
2. Downgrading Android versions (5.1 to 5.0)
3. Switching custom ROMs (I.E. CM13 to AICP)
4. When the ROM's thread warns to (switching keys)
5. Switching between nightly builds and stable.
When you're updating nightlies, you shouldn't have to though.
Click to expand...
Click to collapse
Just did it, it still seems to be booting like it previously was. Wiped cache, dalvic, data, and system and then installed CM13 and gapps. Still booting as I write this.
Since that failed, check your download, make sure nothings bad. If its bad, redownload, if not, idk.
If you post your recovery logs, or what the console says, that will help me figure out what's going on.
Also, is your phone the triband model (l710t)?
Are you flashing anything else at the same time?
The more info you give, the better.
RDChase said:
Since that failed, check your download, make sure nothings bad. If its bad, redownload, if not, idk.
If you post your recovery logs, or what the console says, that will help me figure out what's going on.
Also, is your phone the triband model (l710t)?
Are you flashing anything else at the same time?
The more info you give, the better.
Click to expand...
Click to collapse
I've kind of given up at this point. Even CM12 doesn't work. The only thing that seems to work is the stock rom. My phone is the regular SPH-L710 model. I didn't even know the L710t was a thing.
I have the same problem, and sometimes it boot in the system setup mode, but the sensor is not working, i can turn on airplane mode, reboot or power off, and sensor works, what happend i dont know((
ovil101 said:
After flashing TWRP with Odin, I boot into recovery and wipe the dalvik cache. I then go to install the CM13 zip file, and it works. I wipe Dalvik again and reboot in the os. This is where it just shows the CM boot screen infinitely. Nothing else. What is up. I am using the latest TWRP and CM13 release.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2755793
helped)))
1vankill1 said:
http://forum.xda-developers.com/showthread.php?t=2755793
helped)))
Click to expand...
Click to collapse
That just seems to be a stock rom.
yes it stock rom, after it was installed, I was able to install 13 cm
I'm having some issues flashing any ROM. TWRP will not wipe data, or internal SD
For some reason, when I go to wipe data and factory reset, TWRP will say it was successful, but nothing ever gets wiped. It will only wipe system if I choose to. I've gotten a ROM to flash but when it boots up, all of the old apps and user data are still there and it makes everything crash. I've gotten into settings to do a reset, it reboots into recovery, runs the script, and still nothing wipes.
What I have tried:
Old TWRP, newest TWRP
CWM (seems to wipe but it won't get past the note 2 screen after flashing anything)
Wiping with CWM, flashing TWRP, then flashing a ROM (still loops after the note 2 screen)
Is there a terminal command I can use in TWRP to manually wipe things?
Thanks for any help I can get, I've flashed so many phones I can't remember but I've never had this issue
Maybe flash back to a stock ROM, factory wipe using stock recovery, then flash TWRP?
audit13 said:
Maybe flash back to a stock ROM, factory wipe using stock recovery, then flash TWRP?
Click to expand...
Click to collapse
Well when it bootloops t the Note 2 screen, I have to flash a ROM with Odin to get it working again. I've flashed a stock ROM with Odin, flashed TWRP with Odin, tried the wipes and it never wipes anything... I'm lost...
Isn't there a format function in TWRP that is seperate from the factory reset or advanced wipes? I was also trying to find a terminal command to type in the terminal in TWRP... I'm a little stumped...
I'm sorry, I read that too fast... That may actually work, wipe it in the stock recovery, and just don't let it boot into the system before flashing other stuff... I'm gonna try that out... Thanks man, I'll post back about it...
Since you are flashing the phone with Odin, is it a stock 4.1.1 ROM you're flashing? Which custom ROM are you flashing to the phone?
audit13 said:
Since you are flashing the phone with Odin, is it a stock 4.1.1 ROM you're flashing? Which custom ROM are you flashing to the phone?
Click to expand...
Click to collapse
The stock ROM I used is I317-ODIN-UCUCNJ1-Stock without the booloader packaged in, I'm still on the old bootloader. It's 4.4.2
The ROMS I've tried to flash was
Cyanide (Error 7, says incompatible data, please wipe the phone)
Resurrection Remix (Error 7, says incompatible data, please wipe the phone)
Latest CM10 Nightly
I got CM10 and Resurrection Remix to flash a couple times, but the phone boots and all the old apps and data, including the AT&T ones are still there, and the system keeps crashing. Then I change the recovery to CWM because it seems to wipe, change back to TWRP, flash the ROM and gapps again, but it bootloops at the Note 2 screen.
Should I try the 4.1.1 ROM and CWM? Whenever I'm going from a stock TW to non-TW I like to format everything, data, cache, system, and internal SD, but of course TWRP won't wipe the data or the internal SD.
It's probably because the bootloader and modem are too old for the roms. Recent roms will need updated bootloaders.
Ok, I had some more time to mess around with this today and figured it out. I feel kind of dumb but oh well, I got it.
TWRP was already loaded on, so I went to messing with it again. The 'Swipe to factory reset' was not wiping the data, and there was the 'Format Data' button right there in front of me. I did the factory reset, format data, rebooted recovery, wiped dalvik, cache, and system, then flashed the ROM and everything booted up just fine.
Thanks for all of the help!
So here is my problem:
My OnePlus 5T is stuck in a bootloop. The device was stock when it started, and is now back to the latest stock ROM.
In between I tried serval custom ROM's and a custom kernel to solve my bootloop issue. Flashing other ROM's, kernels or recovery's didn't do it. The device still is in a bootloop. It goes as far as the boot logo, then freezes and then reboots. Sometimes I can acces the operating system, but that only lasts for a few seconds before it also freezes and reboots.
Is there anyone who can possibly help me with this issue?
Thanks in advance.
u may have to wipe system, data, and both caches also u may have to format data (will wipe internal storage, so make backup to PC or OTG) and install a clean official Oxygen OS from their site, do u have TWRP?
also if you have overlays from substratum can cause issues if u have not wiped system and data.
Bradl79 said:
u may have to wipe system, data, and both caches also u may have to format data (will wipe internal storage, so make backup to PC or OTG) and install a clean official Oxygen OS from their site, do u have TWRP?
also if you have overlays from substratum can cause issues if u have not wiped system and data.
Click to expand...
Click to collapse
Thanks for the reply.
I have wiped system, data and both caches and formatted data. I clean installed the lastes build of oxygen(5.1.2).
Unfortunatly this still gives the same result. The phone crashes on boot. For now I have tried these OS:
Oxygen OS: Gets stuck on boot logo
TheOne5TOS: Gets stuck on boot logo and goes back in TWRP.
Android Open Source Project Extended: Loads OS. crashes after a while. Gives me a black screen with a purple notification light.
For TWRP I use Blu Spark for the 5T
Added: I don't use substratum
Try the unbrick tool. Its my last resort and always works if u can get it into dl mode.
Woodrow256 said:
Try the unbrick tool. Its my last resort and always works if u can get it into dl mode.
Click to expand...
Click to collapse
I tried the unbrick tool. Connected the phone and downloaded the stock firmware. But this gets the same result as previously. It loops.
It's a hardware issue, u need to contact oneplus, someone else had that issue too, not sure the outcome though