Related
I’m trying to take the system and user folders from an update.zip I’ve built in dsixda’s kitchen, and convert them to system.img and userdata.img images. Reason is, I want to take the .img files and zip them into a PC36IMG.zip file that I can flash from hboot. I’ve searched everywhere, but I can’t find an answer. Any help would be appreciated.
bver said:
I’m trying to take the system and user folders from an update.zip I’ve built in dsixda’s kitchen, and convert them to system.img and userdata.img images. Reason is, I want to take the .img files and zip them into a PC36IMG.zip file that I can flash from hboot. I’ve searched everywhere, but I can’t find an answer. Any help would be appreciated.
Click to expand...
Click to collapse
What you could do is do a nandroid backup, and then take the system.img and data.img (rename data.img to userdata.img) and then put into your PC36IMG.zip
AssassinsLament said:
What you could do is do a nandroid backup, and then take the system.img and data.img (rename data.img to userdata.img) and then put into your PC36IMG.zip
Click to expand...
Click to collapse
Thanks for the quick reply. I'm actually trying to make an easily-distributable, all-in-one PC36IMG.zip, complete with the Wimax, Radio, NV, System, etc. Basically, I want to include all the 3.70.65.1 updates in one package. Since a NAND backup shouldn't be used on other devices, I'm looking for an alternative method. Any other suggestions?
Thanks.
bver said:
Thanks for the quick reply. I'm actually trying to make an easily-distributable, all-in-one PC36IMG.zip, complete with the Wimax, Radio, NV, System, etc. Basically, I want to include all the 3.70.65.1 updates in one package. Since a NAND backup shouldn't be used on other devices, I'm looking for an alternative method. Any other suggestions?
Thanks.
Click to expand...
Click to collapse
Well, if you're sharing the PC36IMG.zip with others, just make sure to use stock images except userdata.img and system.img, here is basically what I did:
I take the original rom.zip from the 3.70.65.1 ruu, remove system.img and userdata.img, then I make a custom rom and flash it, test it. If it works the way I want it to, I then wipe everything, then reflash it and nandroid backup even before booting it. This should leave system.img and data.img (userdata.img) untouched and should not have any of your personal info. Also, since you're using the original 3.70 PC36IMG.zip, it will have the latest everything including wimax (which won't be your personal wimax image). Do I make sense?
Basically use stock everything from PC36IMG.zip, and just replace the system.img and userdata.img (Just make sure you nandroid those two images before you even boot into it so they won't have any personal data)
AssassinsLament said:
Well, if you're sharing the PC36IMG.zip with others, just make sure to use stock images except userdata.img and system.img, here is basically what I did:
I take the original rom.zip from the 3.70.65.1 ruu, remove system.img and userdata.img, then I make a custom rom and flash it, test it. If it works the way I want it to, I then wipe everything, then reflash it and nandroid backup even before booting it. This should leave system.img and data.img (userdata.img) untouched and should not have any of your personal info. Also, since you're using the original 3.70 PC36IMG.zip, it will have the latest everything including wimax (which won't be your personal wimax image). Do I make sense?
Basically use stock everything from PC36IMG.zip, and just replace the system.img and userdata.img (Just make sure you nandroid those two images before you even boot into it so they won't have any personal data)
Click to expand...
Click to collapse
Okay. I get what you're saying. I'll give it a shot and try it on my wife's EVO. Thanks again for your help.
I wanted to flash a custom ROM and decided to do a nandroid backup first. Every time i did one it did not contain the system.img file which means that the stock ROM wasn't backed up. It only backed up recovery and boot. I have the official CWM from clockwordmod.com.
Please help.
BTW. I know that i can use the stock system image from google, but it's much easier to just recover a nandroid backup.
painfactory said:
I wanted to flash a custom ROM and decided to do a nandroid backup first. Every time i did one it did not contain the system.img file which means that the stock ROM wasn't backed up. It only backed up recovery and boot. I have the official CWM from clockwordmod.com.
Please help.
BTW. I know that i can use the stock system image from google, but it's much easier to just recover a nandroid backup.
Click to expand...
Click to collapse
What version of CWM are you running?
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
I believe the system.img from a TWRP backup itself does not contain any user specific information, maybe a dev can confirm that. I unfortunately factory reset and it wiped mine out. I have the system data backup but apparently I need the full image including the free space included on the partition.
I am sure many besides myself would be appreciative of this. Thanks in advance.
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