Database Users

[Q] stock kitkat 4.4.2 rom zip

Hi everybody,
does anyone have or can do a flashable zip with the latest stock android 4.4.2 image?
If not, even the flashable zip with just the stock kernel would be enough.
Thanks a lot

Flashable stock rom 4.4.2 KOT49H , odex & deodex are posted HERE.

jase33 said:
Flashable stock rom 4.4.2 KOT49H , odex & deodex are posted HERE.
Click to expand...
Click to collapse
Well, i forgot to say i need the tilapia rom.
However, thanks for taking the time to answer.

andreapier said:
Well, i forgot to say i need the tilapia rom.
However, thanks for taking the time to answer.
Click to expand...
Click to collapse
I'm bumping this up (only for this time)...
It seems strange that nobody can help with my request...

Doesn't seem like anyone has created a flashable zip for the latest KOT49H build for Tilapia. You could just as easily download the latest factory image and flash it via fastboot

Eregoth said:
Doesn't seem like anyone has created a flashable zip for the latest KOT49H build for Tilapia. You could just as easily download the latest factory image and flash it via fastboot
Click to expand...
Click to collapse
Do i need to wipe data if i flash it via fastboot?
Or is it just like plain ota?

andreapier said:
Do i need to wipe data if i flash it via fastboot?
Or is it just like plain ota?
Click to expand...
Click to collapse
If you using a custom kernel and want to revert back to stock kernel, you only need to flash the boot.img from the factory image archive. This does not wipe your data.
If you are on a custom ROM, then it would probably be wise to wipe your data. Flash boot.img, system.img and userdata.img (the last file wipes user data automatically). Remember to also format the cache partition.
If you are on a stock ROM with a custom kernel, root access or any modified system files, you only need to flash system.img and boot.img. Formatting the cache partition wouldn't hurt either, just to be safe. This does not wipe your data.
Keep in mind that not wiping data ("dirty flashing") is generally a bad idea if you are flashing from one version to another, e.g. 4.4 (KRT16S) to 4.4.2 (KOT49H).
If this is the case, then you should first download the correct factory image for your current version and flash the system.img and boot.img (if you have made any changes to the system partition or kernel), and then flash the right OTA update, either with a custom recovery or with the stock recovery via ADB. This also does not wipe your data.
Hope this wasn't too confusing

Eregoth said:
If you using a custom kernel and want to revert back to stock kernel, you only need to flash the boot.img from the factory image archive. This does not wipe your data.
If you are on a custom ROM, then it would probably be wise to wipe your data. Flash boot.img, system.img and userdata.img (the last file wipes user data automatically). Remember to also format the cache partition.
If you are on a stock ROM with a custom kernel, root access or any modified system files, you only need to flash system.img and boot.img. Formatting the cache partition wouldn't hurt either, just to be safe. This does not wipe your data.
Keep in mind that not wiping data ("dirty flashing") is generally a bad idea if you are flashing from one version to another, e.g. 4.4 (KRT16S) to 4.4.2 (KOT49H).
If this is the case, then you should first download the correct factory image for your current version and flash the system.img and boot.img (if you have made any changes to the system partition or kernel), and then flash the right OTA update, either with a custom recovery or with the stock recovery via ADB. This also does not wipe your data.
Hope this wasn't too confusing
Click to expand...
Click to collapse
this is not confusing at all!
Infact thanks to your explaination i just understood what i have to do!
Thanks

andreapier said:
this is not confusing at all!
Infact thanks to your explaination i just understood what i have to do!
Thanks
Click to expand...
Click to collapse
Great! Glad I could help

What have I done!!

I woke up this morning and in a daze decided to flash beanstalk6.17. For what ever reason it seemed to have made apps disappear and was lagging out my 6p. I was rushing out the door and in a state of panick I flash purenexus back on. This caused constant booklooping. I restored from a nandroid backup from earlier today but now I can pulldown my settings from the top and constantly have "Unfortunately, the process android.process.acore has stoppped. I reset all apps and it stopped for a while but as soon as I went into any app it began again.
Any help will be appreciated.

Clear the cache for Contacts and Contacts Storage. That should do it.
Sent from my Nexus 6P using XDA-Developers mobile app

Cleared contact cache and still get the notification when I open phone or messages. Also cant slide down to view my quick settings.

Have you tried doing a full wipe, and fresh install of a ROM?

https://www.youtube.com/watch?v=TlvKydE0EVA

pepsal said:
I woke up this morning and in a daze decided to flash beanstalk6.17. For what ever reason it seemed to have made apps disappear and was lagging out my 6p. I was rushing out the door and in a state of panick I flash purenexus back on. This caused constant booklooping. I restored from a nandroid backup from earlier today but now I can pulldown my settings from the top and constantly have "Unfortunately, the process android.process.acore has stoppped. I reset all apps and it stopped for a while but as soon as I went into any app it began again.
Any help will be appreciated.
Click to expand...
Click to collapse
Did you clean flash? Sounds to me like you didn't wipe properly.

Okay so I managed to resolve the issue but now have created a even greater one. I needed to update my vendor image and when installing I accidentaly chose boot image. Now my 6p boots straight to recovery and my twrp data is encrypted and it wont accept my unlock code so I cant access my data to recover. I have a copy of a backup on my pc if that helps. Any guidance would be apprieciated.

pepsal said:
Okay so I managed to resolve the issue but now have created a even greater one. I needed to update my vendor image and when installing I accidentaly chose boot image. Now my 6p boots straight to recovery and my twrp data is encrypted and it wont accept my unlock code so I cant access my data to recover. I have a copy of a backup on my pc if that helps. Any guidance would be apprieciated.
Click to expand...
Click to collapse
Taking a guess, but I think you need to flash proper Vendor img. Can you adb reboot bootloader while phone is in TWRP? If so then at boot loader, reflash the vendor.img.

pepsal said:
Okay so I managed to resolve the issue but now have created a even greater one. I needed to update my vendor image and when installing I accidentaly chose boot image. Now my 6p boots straight to recovery and my twrp data is encrypted and it wont accept my unlock code so I cant access my data to recover. I have a copy of a backup on my pc if that helps. Any guidance would be apprieciated.
Click to expand...
Click to collapse
dratsablive said:
Taking a guess, but I think you need to flash proper Vendor img. Can you adb reboot bootloader while phone is in TWRP? If so then at boot loader, reflash the vendor.img.
Click to expand...
Click to collapse
You'll need to flash the correct boot.img back to the device.
EDIT: Unless I'm misunderstanding you. Did you flash the boot.img to the vendor partition or flash the vendor.img to the boot partition?

Heisenberg said:
You'll need to flash the correct boot.img back to the device.
EDIT: Unless I'm misunderstanding you. Did you flash the boot.img to the vendor partition or flash the vendor.img to the boot partition?
Click to expand...
Click to collapse
I flashed the vendor.img to the boot partition.
Edit: Going to attempt flashing the boot.img now
Edit2: Worked! Thanks for your help

Booting issue -

I used Flashfire to flash a radio.img without checking flash bootloader.
I can get into the bootloader and twrp.
When wiping the device and flashing another rom or restoring a backup my 6p does not get passed the custom rom splash screen.
I was thinking of trying to fastboot flash system/data/cache of the March update and see if it boots.
I know I messed up. don't even know if it was because I didn't check the bootloader option in Flashfire. Just my guess because everything was working fine beforehand.
Any help or ideas would be welcome.

dirtyreturn said:
I used Flashfire to flash a radio.img without checking flash bootloader.
I can get into the bootloader and twrp.
When wiping the device and flashing another rom or restoring a backup my 6p does not get passed the custom rom splash screen.
I was thinking of trying to fastboot flash system/data/cache of the March update and see if it boots.
I know I messed up. don't even know if it was because I didn't check the bootloader option in Flashfire. Just my guess because everything was working fine beforehand.
Any help or ideas would be welcome.
Click to expand...
Click to collapse
Hey... You said you wiped your device? What did you wipe in TWRP?
Try to install a ROM from TWRP. Once it's over go in wipe and do a factory reset. Reboot. It should likely fix your issue.
Good luck...

5.1 said:
Hey... You said you wiped your device? What did you wipe in TWRP?
Try to install a ROM from TWRP. Once it's over go in wipe and do a factory reset. Reboot. It should likely fix your issue.
Good luck...
Click to expand...
Click to collapse
Hey thanks for the reply.
Yeah, I wiped data, system, cache. Just the standard - I still have internal storage intact.
Its just strange, I've used Flashfire before but not for flashing a radio and it worked out fine.
I am on 3.79 and used Flashfire to flash 3.78. Went to the bootloader just to check and it still shows 3.79. Just my fault . I didn't check flash bootloader in the Flashfire settings. Atleast that's what I am guessing. Things were just fine before
Sent from my LG-E980 using Tapatalk

dirtyreturn said:
Hey thanks for the reply.
Yeah, I wiped data, system, cache. Just the standard - I still have internal storage intact.
Its just strange, I've used Flashfire before but not for flashing a radio and it worked out fine.
I am on 3.79 and used Flashfire to flash 3.78. Went to the bootloader just to check and it still shows 3.79. Just my fault . I didn't check flash bootloader in the Flashfire settings. Atleast that's what I am guessing. Things were just fine before
Click to expand...
Click to collapse
Well, if nothing work, maybe backup your internal storage and flash a factory image... Then in recovery do a factory reset afterward. Who knows. Going back to stock shouldn't hurt anyway.
Good luck...

@dirtyreturn
I've used FF to flash only radio files to the modem partition many times without issue. You untick all but modem, and you untick inject SU and preserve recovery. Not sure what went wrong for you. As mentioned , you should be able to manually flash stock and if you're careful, you'll still have your data. All your settings will be reset, but the userdata will be there. You can even use flash-all.bat, but open it in a text editor and remove the "-w" flag so it will not wipe your userdata. The Google page where you get the full factory image will have instructions.

v12xke said:
@dirtyreturn
I've used FF to flash only radio files to the modem partition many times without issue. You untick all but modem, and you untick inject SU and preserve recovery. Not sure what went wrong for you. As mentioned , you should be able to manually flash stock and if you're careful, you'll still have your data. All your settings will be reset, but the userdata will be there. You can even use flash-all.bat, but open it in a text editor and remove the "-w" flag so it will not wipe your userdata. The Google page where you get the full factory image will have instructions.
Click to expand...
Click to collapse
Thanks. It was obviously my fault somehow.
I do remember there being only one option to tick.
Using fastboot back to stock did the trick and made me realize maybe I should hold off on using Flashfire for a bit.
Sent from my Nexus+6P using Tapatalk

dirtyreturn said:
Thanks. It was obviously my fault somehow.
I do remember there being only one option to tick.
Using fastboot back to stock did the trick and made me realize maybe I should hold off on using Flashfire for a bit.
Click to expand...
Click to collapse
Nah, FF is awesome and a major time-saver. Just read up on the documentation here and become familiar with it.

Can't get back to Stock ROM (what am I doing wrong?)

History of what I did:
I first installed the first small OTA Update to 4.5.1 then unlocked the Bootloader and flashed TWRP v46 from xdvs23. And made a full TWRP Backup and flashed Magisk afterwards.
Everything worked fine until I debloated the System and wanted to make the OTA Update to 4.5.2 (1,5 GB), which didn't work. After I flashed it, the phone didnt boot anymore. So I restored the TWRP Backup, which doesn't work either.
Current status:
TWRP v58 is flashed and works. I can flash ExcperienceOS from Jamal, which works fine, too. But flashing the OTA file doesn't work and restoring my backup wont work either -_-
I would really appreciate help to get back to an OTA updatable version of OxygenOS!

If you still have the TWRP installed I would download the full 4.5.2 zip (Listed elsewhere on these forums) and use adb sideload to install it, then proceed again from there.

djsubterrain said:
If you still have the TWRP installed I would download the full 4.5.2 zip (Listed elsewhere on these forums) and use adb sideload to install it, then proceed again from there.
Click to expand...
Click to collapse
I did that several times. It doesn't work sadly... I get into a bootloop

You didn't erase your userdata partition by mistake did you? You could try going into fastboot mode and use the command:
fastboot format userdata
Obviously this will wipe the userdata partition but the phone is acting like there's no userdata partition anyway

djsubterrain said:
You didn't erase your userdata partition by mistake did you? You could try going into fastboot mode and use the command:
fastboot format userdata
Obviously this will wipe the userdata partition but the phone is acting like there's no userdata partition anyway
Click to expand...
Click to collapse
I might have, I will try that, thanks

Or just wipe everything, flash stock recovery, and flash Full OxygenOS zip.
https://forum.xda-developers.com/showpost.php?p=72799046&postcount=2

I formated the userdata and flashed the .zip from the link, but I still get a bootloop...
I still don't understand what I am doing wrong...

How about trying to wipe everything from wipe menu except internal storage and then flash the oos zip followed by lazy flasher zip from here - bit.ly/lazyflasher
If this doesn't work then try changing to a different version of TWRP!

Casual_Max said:
I formated the userdata and flashed the .zip from the link, but I still get a bootloop...
I still don't understand what I am doing wrong...
Click to expand...
Click to collapse
You didn't do these steps wrong by any chance?
Steps To Disable Forced Encryption i.e, Decrypt Data
1. At first time when you open twrp, it will ask you to allow system modification.
2. Allow it and then flash the no-verity-opt-encrypt.zip file .
3. Then Go to Wipe-->Format Data.
4. Type Yes to confirm wiping of Internal Storage.
5. Now you have decrypted the data sucessfully.
Note: Dont try to restore the nanodroid backup which you have taken before. It may end in bootloop.
Click to expand...
Click to collapse
From here:
https://forum.xda-developers.com/on...der-intall-t3626122/post72777899#post72777899

ok, there I see what caused my first bootloop. Thanks
But why doesn't flashing the Stock ROM .ZIP work on an wiped (fastboot format userdata) phone? What else do I have to do?
EDIT:
*** solved ***
I failed hard. Luckily the OnePlus Support is excellent and was able to fix my issue with a remote session using their official tools. The Phone and I are both happy again.
Thanks for all the help, though. I learned quite a lot while dealing with this issue. It's a very kind and nice community here

Erase userdata. Unable to boot into any ROM except aicp ROM

Can anyone help. I performed a userdata erase and formatted the data partition. The problem is I can flash the ROMs but can't boot into it. It keeps coming back to twrp and does some check and reboots again to do the same thing again and again. I don't know what's wrong. The only ROM i can boot into is the AiCP Rom. I'm in need of a desperate help. Help me guys.

Since u erased userdata u decrypted ur device. If u wanna stay decrypted u need to flash no verity zip after rom and root method and gapps.

Cyclops Maran said:
Can anyone help. I performed a userdata erase and formatted the data partition. The problem is I can flash the ROMs but can't boot into it. It keeps coming back to twrp and does some check and reboots again to do the same thing again and again. I don't know what's wrong. The only ROM i can boot into is the AiCP Rom. I'm in need of a desperate help. Help me guys.
Click to expand...
Click to collapse
Solution found guys. Just follow the instructions on this thread. https://forum.xda-developers.com/oneplus-5/how-to/guide-how-to-flash-encrypted-roms-t3659126