Hello.
I need help or if anyone was able to fix this error root failed me and SP Flash didn't detect the device after that I searched the internet for my error it gave me and it said it would detect it if I gave it : "remove all+download" I made a copy of security with PBRP of the important sectors of the phone but they are encrypted, when I rebooted the device again I got the error 0x99256658Download not completed.
Looking for information, I need a file called oppo_custom.img from the device but unfortunately I can't find it on the internet.
I wanted to know if anyone has that file or knows someone who could repair it online, even if you have to pay
And if someone was able to solve it, could you help me by telling me how, I currently have another phone in use but I don't want to lose this one.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TOLL10 said:
Hello.
I need help or if anyone was able to fix this error root failed me and SP Flash didn't detect the device after that I searched the internet for my error it gave me and it said it would detect it if I gave it : "remove all+download" I made a copy of security with PBRP of the important sectors of the phone but they are encrypted, when I rebooted the device again I got the error 0x99256658Download not completed.
Looking for information, I need a file called oppo_custom.img from the device but unfortunately I can't find it on the internet.
I wanted to know if anyone has that file or knows someone who could repair it online, even if you have to pay
And if someone was able to solve it, could you help me by telling me how, I currently have another phone in use but I don't want to lose this one.
View attachment 5765767
View attachment 5765769
Click to expand...
Click to collapse
Remember that, usually, SPFT don't flash oppo_custom images, you should, need, firstly, edit the scatter file, where it names that partition, and set it from false to true, using some of your oppo_custom images, available on the ofp extracted ROM.
This was just a first attempt, just in case, one of those files can fix the issue.
Going to the next, as the probabilities to find, a specific modded oppo_custom image, specifically for your device, it´s unlikely, then you can pick up from some of the lot of them, available from the net, in case one of them can fix it. It doesn't matter for the model is coming from.
SubwayChamp said:
Remember that, usually, SPFT don't flash oppo_custom images, you should, need, firstly, edit the scatter file, where it names that partition, and set it from false to true, using some of your oppo_custom images, available on the ofp extracted ROM.
This was just a first attempt, just in case, one of those files can fix the issue.
Going to the next, as the probabilities to find, a specific modded oppo_custom image, specifically for your device, it´s unlikely, then you can pick up from some of the lot of them, available from the net, in case one of them can fix it. It doesn't matter for the model is coming from.
Click to expand...
Click to collapse
Thanks for the reply.
I have downloaded several roms and extracted the opf of this model and none of them brings the oppo_custom.img, I tried an oppo_custom that I found on the net but it didn't work, I don't know if when trying to flash the first time the bootloader was closed and SPFT cannot overwrite those partitions, I can't get into the bootloader to confirm it.
Related
Hello guys, this is what i have on my htc m9
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Could I restore Stock rom on my htc m9 and how to do that?
And how I now which RUU to chose?
https://www.google.com/url?q=https:...134000&usg=AFQjCNGdzDwYjWYwYr-RSW3t2U9j47aOJw
Download this file. Copy it to your ext sdcard and rename it to 0PJAIMG.zip
Connect your phone to fastboot and type fastboot oem lock
Boot into download mode. Phone will prompt you to install. Press volup and wait.
Before u start backup ecerything
If you're already linking one of my files you could've linked my instructions, too, since what you wrote isn't completely correct. Re-locking the bootloader is unnecessary if you use the SD card method. In the worst case (e.g. if the RUU fails and OEM unlock isn't activated in the developer options) you could end up with a non-booting phone that can't be re-unlocked. The M9 has security checks that prevents it from booting if it isn't completely stock and the bootloader gets (re-)locked. And although I tested that RUU there can always be reasons why it fails to flash.
Could you be more specific please, I am new with htc and I dont know anything about it, What is fastboot? And if you have some time to tell me step buy step how to do that i would be greatiful. Sorry for bad english
Im sorry Flippy498 i just want to help him. You are a genious and i respect you. You are a life saver.
https://docs.google.com/spreadsheets/d/15K6xhb6wtosp9j8yu4xHBZ6n9v5OaFSW6ZVWxC4u_qc/pubhtml
My bad. I didn't notice that my signature isn't visible in this thread.
Edit: I don't know why the link gets broken as soon as I save this post. You'll need to copy'n'paste the link.
THX a lot, now I'm gonna to try to restore stock rome!
@Flippy498 I have just one question, I followed your instructions and it worked perfectly but I still have Software Status marked as Modified. Would I be able to receive software updates ?
Yes, you will. And you'll be able to install them, as well. (Receiving updates is not the problem, it's being able to install them if the system has been modified. However, a RUU reverts every modification you made.)
It's just strange that the flag still says that your system is modified. Normally the SD card method should reset it to original. But that shouldn't be a problem. OTAs don't check that flag. They compare whether the checksum of the system is the same as the reference value. Since a RUU overwrites the current system with the stock one you won't face any problems here.
Thanks a lot dude for your great work and quick reply !
I had a Nexus 5X and a while ago it went to bootloop issue. Currently the device does not turn ON, but when it connects to PC it's showing in the device manager as Qualcomm HS-USB QDLoader 9008 device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have done some search and found a guide to follow to fix this issue. Here the guide I followed https://forum.xda-developers.com/google-nexus-5/general/fix-unbrick-nexus-5-stucked-qualcomm-hs-t3043301.
But when I'm doing the steps, it stuck in the step that finding a device and give me this error saying no response from device.
Then I searched some another way around and found another tool call QFIL. In that case my device is detected to that tool as a device.
My problem is when using this tool there should be a file in .mbn format and some other files in .XML etc. that matches with Nexus 5X. I have search and couldn't find any of matching sources for that. I do not have any deeper knowledge in this case and if somebody can explain the current situation that cause this issues, it will be very helpful for me. And if any sources or another methods to try out also very helpful
+1 looking for the same help
sathindukavneth said:
I had a Nexus 5X and a while ago it went to bootloop issue. Currently the device does not turn ON, but when it connects to PC it's showing in the device manager as Qualcomm HS-USB QDLoader 9008 device.
I have done some search and found a guide to follow to fix this issue. Here the guide I followed https://forum.xda-developers.com/google-nexus-5/general/fix-unbrick-nexus-5-stucked-qualcomm-hs-t3043301.
But when I'm doing the steps, it stuck in the step that finding a device and give me this error saying no response from device.
Then I searched some another way around and found another tool call QFIL. In that case my device is detected to that tool as a device.
My problem is when using this tool there should be a file in .mbn format and some other files in .XML etc. that matches with Nexus 5X. I have search and couldn't find any of matching sources for that. I do not have any deeper knowledge in this case and if somebody can explain the current situation that cause this issues, it will be very helpful for me. And if any sources or another methods to try out also very helpful
Click to expand...
Click to collapse
Did you find a solution?
链接：https://pan.baidu.com/s/1TmQ9jmdAym2NYt_YGyt2Cg 引脚：g5cg
linzifu577 said:
链接：https://pan.baidu.com/s/1TmQ9jmdAym2NYt_YGyt2Cg 引脚：g5cg
Click to expand...
Click to collapse
Hello!
Could you upload here? https://roxorkiller.hu/index.php/s/yiEfEqZiDN4joDL
Tnanks
csihama said:
Hello!
Could you upload here? https://roxorkiller.hu/index.php/s/yiEfEqZiDN4joDL
Tnanks
Click to expand...
Click to collapse
i'm trying to download it, but it's all in chinese language, so i'm not sure if i'm doing it right on baidu desktop client
the name of the file is something like nexus5x_9008(BRICK SOLVE).rar according to google translator
Some people may have never heard of developermenu.efi, it's an efi application Microsoft mostly uses on test devices which allows you to do many things, here are the main highlights:
Note: if some people have a problem with getting this efi to display something, please use this one: https://forum.xda-developers.com/windows-10-mobile/exe-binaries-binaries-w10m-oem-kit-t3476453
Enter Mass Storage mode directly on the phone without the need of a computer.
Delete and dump the UEFI variable storage from the phone (be careful with this you can easily cause problems).
Tickle the battery to 0% (useful for re-calibration).
This EFI application is test signed, this means you must run it on an unlocked device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's also the latest available (from 15254.158).
You can create a new entry in BCD for a new bootapplication and reference it in the place you did put the efi. You also must make sure you turn on nointegritychecks on it because it's test signed.
For reference here's what Microsoft actually does to BCD when installing it (aside from nointegritychecks):
You must place the files attached in EFIESP\windows\system32\boot\
Provided are also the latest bmpx files which enables graphical status when you're in mass storage (also works when switched using WPInternals).
L630DS work fine but I don't see anythynk, just black screen.
PS: tried use different devmenu efi(from this post) and it work and display.
the_R4K_ said:
L630DS work fine but I don't see anythynk, just black screen.
PS: tried use different devmenu efi(from this post) and it work and display.
Click to expand...
Click to collapse
What doesn't display? The menu or when you enter the mass storage section? That efi should defintely work except maybe on rs2+, didn't check everything but I vaguely remember MS breaking feature manifest policies with rs2.
gus33000 said:
What doesn't display? The menu or when you enter the mass storage section? That efi should defintely work except maybe on rs2+, didn't check everything but I vaguely remember MS breaking feature manifest policies with rs2.
Click to expand...
Click to collapse
menu.
I can't say my build because my phone...
I have this configs:
w10m 15254.1(one big part)
winRt(small part in end of drive)
efiesp(maybe different version than system likely wp8...)
But intresting that another file work fine.
How about tutorial?
augustinionut said:
How about tutorial?
Click to expand...
Click to collapse
I can't actually make a tutorial now because each people have their own way of loading entries from bootmgr, but I have planned making a whole post about bootmgr and bcd entries and how to have multiple of them on a lumia device in the future, afterwards sure.
Please make tutorial using bcdedit
I have BSOD on 950
UPD: My fault, i had efi file on wrong partition
So I do have a question on this, it is the 'Reset your phone' inside "About" that we use to open this, right? (running 10586 on a htc one m8, trying to follow your guide on unlocking the bootloader)
update: nevermind, its a hard reset and not a factory reset
Hello all, I am trying to make a custom recovery for my new phone, the realme gt me rmx3363. However this is my first phone that is A/B partitioned so I don't know what to do fully. I am trying to extract the recovery.img because that is whats needed in order to make a custom recovery. However, when I look into the device firmware the only image files I see are: boot, bootloader, dbto, radio, vbmeta, vbmeta_system and vendor_boot. The system files are all seperated into "sparsechunks".
On a non-A/B device getting the recovery was as easy as downloading the stock firmware, extracting, and then recovery.img was right there. Now it seems to be different and I don't know what to do, I couldn't find anything on google about how to do this. I am sure it is easy enough though. Thank you in advance.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NextB said:
Hello all, I am trying to make a custom recovery for my new phone, the realme gt me rmx3363. However this is my first phone that is A/B partitioned so I don't know what to do fully. I am trying to extract the recovery.img because that is whats needed in order to make a custom recovery. However, when I look into the device firmware the only image files I see are: boot, bootloader, dbto, radio, vbmeta, vbmeta_system and vendor_boot. The system files are all seperated into "sparsechunks".
On a non-A/B device getting the recovery was as easy as downloading the stock firmware, extracting, and then recovery.img was right there. Now it seems to be different and I don't know what to do, I couldn't find anything on google about how to do this. I am sure it is easy enough though. Thank you in advance.View attachment 5549789
Click to expand...
Click to collapse
I have the same proble with my tecno camon 17 pro mediatek mt6587 helio g95 on android11. let me know if you find a solution.. thanks
Try
https://github.com/twrpdtgen/twrpdtgen
It says supports Android 12.
"Create a TWRP-compatible device tree only from an Android recovery image (or a boot image if the device uses non-dynamic partitions A/B) of your device's stock ROM It has been confirmed that this script supports images built starting from Android 4.4 up to Android 12"
@NextB Having the exact same issue on my Blackview BV8800.
The recovery partition is nowhere to be seen. Here's an Interesting article mentioning this scenario from the android docs. Basically, it says that the recovery code is shipped in boot_vendor.img !
@retiredtab Pardon me if I do not follow, how can mapping out a device tree help us here?
I have a feeling that this tool might help us get done: https://github.com/cfig/Android_boot_image_editor.
Basically, the flow I am thinking about is:
1. Grab vendor_boot.img unpack with it.
2. Grab twrp.img unpack with it.
3. Replace recovery code in 1 with the one in 2.
4. Repack boot_vendor.img.
5. Flash boot_vendor.img with fastboot.
Now, in my case with a mediatek processor, it's more complicated as I have to "port" twrp first, and to do that, I first need a vanilla recovery.img, so I will have to reconstruct that too at some point.
Just found an interesting method with Carliv Image Kitchen tool, seems very promising, and maybe that it the solution we seek: Here's a video demo'ing the method:
And according to the video above, the recovery code is in boot.img not boot_vendor.img!
Hi, i have rooted a few phones in the past without problems but it´s my first samsung and nothing seems to work... Read a lot a tutorials, tried a lot of things and for now, no success in any...
I'm on the latest version of Android (12) - ZTO-F415FUBS2CVF1
I did unlock the bootloader without problems... Extracted stock rom boot.img, patched it with magisk 22104. Put it inside a boot.tar, flashed it in Odin with success:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After the patch, i always go straight to stock recovery and wipe data...
It´s really weird, when i install magisk, after the flash, it only says this:
I also did try to follow magisk instructions and flash the whole stock rom with the AP patched but it gives me an vbmeta error, so i reverted to stock firmware and kept trying to patch only boot.img...
Also tried to revert to android 11 with Odin but it gives me an wrong version error on download mode...
I don´t know if i'm using the wrong magisk version, or something is missing in the tutorials... Also tried to find something here but nothing seems to work... Can someone help me ?
Same problem here. VBmeta is giving me a lot of trouble.
Loking foward for a solution...
Hi guys...
Anyone have any luck rooting this f.... android 12 on Samsung M21s? It sucks.
I cant hold it anymore...
A beg a little help .
A want my cell phone back. kkkk
Regards...
.
Hi! When you get that in magisk can you direct install?
ps. I do not have this device but I rooted Samsung so I may be able to help
RodrigoC82 said:
Hi, i have rooted a few phones in the past without problems but it´s my first samsung and nothing seems to work... Read a lot a tutorials, tried a lot of things and for now, no success in any...
I'm on the latest version of Android (12) - ZTO-F415FUBS2CVF1
I did unlock the bootloader without problems... Extracted stock rom boot.img, patched it with magisk 22104. Put it inside a boot.tar, flashed it in Odin with success:
View attachment 5700249
View attachment 5700251
After the patch, i always go straight to stock recovery and wipe data...
It´s really weird, when i install magisk, after the flash, it only says this:
View attachment 5700257
I also did try to follow magisk instructions and flash the whole stock rom with the AP patched but it gives me an vbmeta error, so i reverted to stock firmware and kept trying to patch only boot.img...
Also tried to revert to android 11 with Odin but it gives me an wrong version error on download mode...
I don´t know if i'm using the wrong magisk version, or something is missing in the tutorials... Also tried to find something here but nothing seems to work... Can someone help me ?
Click to expand...
Click to collapse
Can I see the error? It may be because flashing just the ap in the first place shrunk your space.