Hey all,
I have an LE2115 OnePlus 9, running the C.62 version of ColorOS 12. I followed a guide I had found and seen posted by members here to root my OnePlus 9. I originally was trying to boot into TWRP to perform a full backup, however someone here mentioned that TWRP no longer works for this device. I followed this guide exactly step by step, however now my phone will show the splash screen, vibrate and show it once more, and then boot into recovery. The boot reason states: "fs_mgr_mount_all". Just to clarify, I patched the boot.img and vendor_boot.img via Magisk on my device, and flashed the two boot files along with the vbmeta.img, as shown in this guide.
Is there any hope getting my data back? I am aware I can use MSM tool to restore functionality to my device, but I am much more concerned about the data as I have a lot of important 2FA information on here. Any help would be insanely appreciated!!
Edit:
After 7 hours of flashing different images and trying different methods, I finally got it to boot again! I had been trying many things, but for some reason it worked after I repeated something I had done many times already. I simply flashed dtbo.img, then vendor_boot.img, and lastly boot.img, and it magically worked! I used the C.62 images created with this amazing tool! The issue was that I flashed the C.48 images, which were provided in the article. They didn't consider some people might be running on C.61-C.62.
joshcantcode said:
Edit:
After 7 hours of flashing different images and trying different methods, I finally got it to boot again! I had been trying many things, but for some reason it worked after I repeated something I had done many times already. I simply flashed dtbo.img, then vendor_boot.img, and lastly boot.img, and it magically worked! I used the C.62 images created with this amazing tool! The issue was that I flashed the C.48 images, which were provided in the article. They didn't consider some people might be running on C.61-C.62.
Click to expand...
Click to collapse
If it isn't a bother, can you explain what kind of commands did you run to extract files from the incremental OTA? I already have python and the latest PIP for it, I also downloaded the tool folder you linked but have no idea which commands to run and where do I put the OTA payload.bin. This tool isn't as simple as the one I've been using to extract from full OTA zips back in the OnePlus 6 days.
Yes of course. I used the OnePlus OS Update Tracker to get the downloads for the firmware.
C.48
C.61
C.62
Dump the C.48 payload and place the dumped images into a folder called "old" in the update_payload_extractor tool. I ran this on Linux so it made me remove the .img extension from each image, but it might be different for you. Place the payload.bin of the C.61 firmware into the root of update_payload_extractor, and perform
Code:
py extract.py payload.bin
After it finishes, you will have a new folder called output. which contains the upgraded C.61 images. In my case, some of the upgraded images were 0 bytes. Copy all of the files that have a normal size from output, and paste them into the "old" folder again, overwriting the C.48 images from earlier. Then place the C.62 payload.bin into the root again, and run the same command. Now the output folder will have the C.62 images!
You can repeat these steps if you have C.63, simple copy from output -> old and extract the new payload.
Related
Hi folks.
I have an unusual smartphone from a Brazilian manufacturer, CCE, who have been bought for Lenovo.
This manufacturer are not exactly knowed for their support our product quality and I'm prety sure my device will not be updated or suported for any longer.
It's the SK504 and I want to try to customize the rom, build tunning apps (battery consumption sucks) and things like that. I have a good programming backgroung but not for mobile devices so I'm stepping on eggs for now.
The first thing I tried to do was get a backup from my actual rom so if I mess with something I shouldn't I would be able to come back to a working version through fastboot.
long story short, I managed to obtain through romdump 5 files; checksum.md5, config.gz, system.info.gz and system.tar
but, in the posts I been reading, it gives me the idea that I should get a boot.img, a recovery.img and a system.tar.gz
And with this I would be able to generate my own system.img through a different process.
Since I'm not being able to find what I did wrong, can anyone tell me if there are a different way to get those boot.img and recovery.img?
I tried the "adb backup -f boot.img boot" but it generates a 1kb .img file and I don't believe this is a valid boot.img.
rhodesbauer said:
Hi folks.
I have an unusual smartphone from a Brazilian manufacturer, CCE, who have been bought for Lenovo.
This manufacturer are not exactly knowed for their support our product quality and I'm prety sure my device will not be updated or suported for any longer.
It's the SK504 and I want to try to customize the rom, build tunning apps (battery consumption sucks) and things like that. I have a good programming backgroung but not for mobile devices so I'm stepping on eggs for now.
The first thing I tried to do was get a backup from my actual rom so if I mess with something I shouldn't I would be able to come back to a working version through fastboot.
long story short, I managed to obtain through romdump 5 files; checksum.md5, config.gz, system.info.gz and system.tar
but, in the posts I been reading, it gives me the idea that I should get a boot.img, a recovery.img and a system.tar.gz
And with this I would be able to generate my own system.img through a different process.
Since I'm not being able to find what I did wrong, can anyone tell me if there are a different way to get those boot.img and recovery.img?
I tried the "adb backup -f boot.img boot" but it generates a 1kb .img file and I don't believe this is a valid boot.img.
Click to expand...
Click to collapse
Instead of making a backup, have you tried to find original restore image? Usually it is a an .IMG file.
qwertyu123 said:
Instead of making a backup, have you tried to find original restore image? Usually it is a an .IMG file.
Click to expand...
Click to collapse
I used Root Explorer to look for both, recovery.img and *.img.
No result.
try this http://forum.xda-developers.com/showthread.php?t=2450045
Note: OTA updates don't work on my Nexus 5 due to TWRP blocking them. Now my phone doesn't recognize the OTA update anymore (When my phone went to install the OTA updated and rebooted, it rebooted into TWRP instead and completely ignores the updates existence since then). To fix this I plan to simply push the factory img of 5.0.1 to my device directly. I downloaded the factory .img from Google's website .
However instead of a .img file i'm used to, I got a .tgz. I extracted that and got a .tar and then extracted that to finally get my folder with the .img files. However now I'm not sure which one to push to my device. There is a img file called "radio-hammerhead-m8974a-2.0.50.2.22.img" but judging by the file size, I don't think that's the correct one (only 45MB). There is a .zip file called "image-hammerhead-lrx22c.zip" but this contains multiple .img files, the largest one called "system.img". I'm guessing this is the correct one to push to my device via adb since it's about 1GB in size?
I suspect pushing the entire .zip file to my phone and flashing that would be bad as it looks like it'll overwrite TWRP?
Any help would be greatly appreciated.
Here's a lot of useful information about OTA's Check it out: http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
You'll need boot and system at least,
If you plan on keeping twrp and root, you may as well just flash one of the flashable zips already available in the development forum
Actually you should have a radio and bootloader img file. First one is - as the name says - the latest radio software (which is needed for GPS, WiFi, cellular network and so on). Second one is the latest bootloader. I'd update them both.
From the zip archive you should only flash certain imgs - if you flash all your data will be wiped (factory reset). What img files does the zip contain?
Why are you pushing them to your phone? You need to flash with fastboot from your computer. There is not just one img file for the update, there are several for different partitions on the phone. Have a look through some of the guides in the general section. Also, flashing one of the stock flashable zips would be much faster, but why not learn a little as you update.
Vomer has a thread of flashable 5.0 and 5.0.1 stock Google ROMs. Don't worry about factory images because you will lose everything once you flash these and it's a much bigger pain imo to back everything including internal on your phone up.
snappycg1996 said:
Don't worry about factory images because you will lose everything once you flash these
Click to expand...
Click to collapse
Not necessarily true.
You can flash bootloader, radio, and system without losing anything. You'll just have to reroot afterward.
Hello,
My device is the Mate 9 (MHA-L29C185B110) and I seem to have a problem with the camera.
When pressing the button to take a photo, the camera app restarts itself. I try again, but didn't work, to no avail.
I also tried to record a video. It seems to work, but the camera freezes but it's still counting, otherwise recording.
I have just recently flashed a custom recovery img (TWRP), the boot img on another thread that prevents the device from being automatically encrypted, and SuperSU root.
Do any of you have a solution to this problem?
Would this be because I haven't flashed Public_data.zip and Full_HW_data.zip?
And will this problem fix if I completely install the MHA-L29C185B172's firmware?
SeanPHTRPW said:
Hello,
My device is the Mate 9 (MHA-L29C185B110) and I seem to have a problem with the camera.
When pressing the button to take a photo, the camera app restarts itself. I try again, but didn't work, to no avail.
I also tried to record a video. It seems to work, but the camera freezes but it's still counting, otherwise recording.
I have just recently flashed a custom recovery img (TWRP), the boot img on another thread that prevents the device from being automatically encrypted, and SuperSU root.
Do any of you have a solution to this problem?
Would this be because I haven't flashed Public_data.zip and Full_HW_data.zip?
And will this problem fix if I completely install the MHA-L29C185B172's firmware?
Click to expand...
Click to collapse
It could be a problem if you flashed a boot image for a different model. You need boot image for C185B110. It should work without hw and Public zips, but a lot of other things break without flashing those. Updating to C185B172 will fix it.
By the way, which supersu did you use?
If the one from the "Decrypt" thread in Guides you don't need to flash a pre-decrypted boot image, the installer does it for you.
ante0 said:
It could be a problem if you flashed a boot image for a different model. You need boot image for C185B110. It should work without hw and Public zips, but a lot of other things break without flashing those. Updating to C185B172 will fix it.
By the way, which supersu did you use?
If the one from the "Decrypt" thread in Guides you don't need to flash a pre-decrypted boot image, the installer does it for you.
Click to expand...
Click to collapse
As for the SuperSU, I think I took it from the full root guide w/o decrypt img, but obviously I had to use a decrypt img because of stock
SUPERSU-2.79-MATE9-init.d_support
For the boot (No force encryption boot)
This is probably where things went wrong. I flashed the wrong build image.
https://forum.xda-developers.com/mate-9/development/stock-boot-img-library-t3573312
I had to use above link because I couldn't flash SuperSU since I don't have an external sd to extract it from (Since you have to format your data before flashing it)
I couldn't find the hw and public zips for C185B110, so if you have it, a link would be generous.
Would flashing stock boot img for MHA-L29C185B110 fix it?
and what would happen if i flash stock boot.img?
and do you have a decrypt boot.img for C185B110?
Thanks!
SeanPHTRPW said:
As for the SuperSU, I think I took it from the full root guide w/o decrypt img, but obviously I had to use a decrypt img because of stock
SUPERSU-2.79-MATE9-init.d_support
For the boot (No force encryption boot)
This is probably where things went wrong. I flashed the wrong build image.
https://forum.xda-developers.com/mate-9/development/stock-boot-img-library-t3573312
I had to use above link because I couldn't flash SuperSU since I don't have an external sd to extract it from (Since you have to format your data before flashing it)
I couldn't find the hw and public zips for C185B110, so if you have it, a link would be generous.
Would flashing stock boot img for MHA-L29C185B110 fix it?
and what would happen if i flash stock boot.img?
and do you have a decrypt boot.img for C185B110?
Thanks!
Click to expand...
Click to collapse
It would probably fix it yes, but no boot image or hw/public exist for B110 so I'm guessing it shipped with that build.
You'd have to update, using https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
I don't think you can use Firmware Finder as you're probably missing the System Update feature.
Either that one I linked or FunkyHuawei, but Funky cost money to use.
Thanks,
I will try using the link you used.
although it is not clear.
On manual update step A, do you need to download all three?
the base, the OS(windows) and the model?
and where do i put these files?
and on b and c on update zip
do i have to download two update.zip?
for example, C185B110 and C185B172
do i also need to download full ota instead of just ota? fullota is incompatible, says firmware finder on mobile
SeanPHTRPW said:
Thanks,
I will try using the link you used.
although it is not clear.
On manual update step A, do you need to download all three?
the base, the OS(windows) and the model?
and where do i put these files?
and on b and c on update zip
do i have to download two update.zip?
for example, C185B110 and C185B172
do i also need to download full ota instead of just ota? fullota is incompatible, says firmware finder on mobile
Click to expand...
Click to collapse
Yes, download base, os and MHA. Extract all to the same folder. You should only have one folder named HWOTA and the files/folders in that. If it extracts to a folder with the same name as the zips, enter the folders and copy hwota folder then go back one folder and paste/merge so you end up with one folder named HWOTA. Easiest way is putting it directly in C:\hwota\, if your windows version allows it. Else place it on desktop. (long file paths or a path containing spaces might make hwota not function correctly).
You need to download all 3 files (fullota update.zip, hw zip and Public zip), easiest way is using firmware finder to download. Either mobile or the pc version. For pc go to the common base tab and search for your model and then download the build you want including public and HW zips.
You only need to download the fullota update, hw and Public zip of the build you're updating to. If you're on b110 and going to update to B172 you only need to download B172.
Rename the files according to the guide (update.zip, update_all_hw.zip and update_data_public.zip), place them in either hwota/update folder or make a HWOTA folder on your sdcard and put the renamed files there.
When running hwota, select script update folder or sdcard update folder depending on where you put the files. Select same model update.
One last question:
Does it have to be FULLOTA, not just OTA?
Hello,
First post here though in the past I have read discussions on many occasions in search for information and it was always to my benefit, thank you.
My question revolves around the TWRP installation files for Fairphone 3.
On the TWRP website (https://twrp.me/fairphone/fairphone3.html#) are given 2 files, a twrp-installer-.......zip and a matching version of a twrp- ........img, and from the instruction given it is not clear to me what is the purpose of the .img file - are both used concomitantly during the installation, or not.
At one early and critical stage the TWRP instduction reads:
"...Download the correct image file and copy the file into the same folder as your platform-tools as well as device's storage. Rename the image to twrp.img."
Since the file needs to be renamed to .img apparently it is the original installer.zip.
The entire instruction afterwards refers to this downloaded and renamed file.
What then is the the purpose of the matching .img file? Is it used at all? The TWRP installation instruction doesn't even mention it.
Sorry for asking if this is common knowledge, but I did several searches all to no avail.
Thank you
Hey,
I'm kinda in a limbo where I'd like to enjoy the customizability from a custom ROM, but still enjoy some of the look from the original OOS.
So far without any luck, though. I've tried downloading both OOS 12 and a 13 beta for OnePlus 10, just to grab its data. I can successfully dump whatever is in payload.bin but when I try to look inside the .img-files, I'm just shown either an apex_payload split in two (I assume) in the system .img's. And a classes.dex-file in where I'd normally look in product.img.
If I try to extract (7zip) any of the mentioned, I get a CRC error.
Is there any method that allows me to grab the /media folder from the original stock ROM?
Thanks.
I'm also facing the same issue but if you only need media file I'll upload it