Hello,
I am looking for HTC Desire 816 Single SIM a5_ul:
boot.img and recovery.img for 1.60.401.1 (if it's important I have EastEurope)
Backup of newest version: Lollipop a5_ul.
I had a big problems with update so I tried to flash boot.img and recovery.img from newest OTA. Sadly, I can't launch my phone, I have one boot and next my phone is going to recovery. I have no idea how to fix it, so I think that back my boot.img can solve my problem.
Now I haven't a phone, so it's very important for me to fast reply.
Boot.img is the same for all variants?
Solution of problem:
- download ROM: http://forum.xda-developers.com/desire-816/development/26-nov-svhd-v1-0-0-t2953661
- open archive
- copy boot.img
- past into fastboot folder
- reboot phone into fastboot mode and connect to pc
- commend: fastboot flash boot boot.img
- reboot phone
But now I had a problem that I can't install update to Lollipop... Do you have stock recovery for EE version?
stock recovery EU 1.60 https://drive.google.com/file/d/0B_TNjOKpULbAUGVkWGJfclhjYU0/view?usp=sharing
This is version for EU, but in Poland we have EE (East Europe)
I have a red info "That build is..."
I think I have a wrong boot.img because still I have red triangle after 25%. Do you know what is the problem?
Now I understand what I need. I need boot.img from European version wich is in backup of original soft! Sadly I haven't this file (my HDD with it is damaged) so can anyone past here link to boot.img from his backup? European, 1.60.401.1
Related
To cut it short; let me describe what i've done to my victim RIO-L01
1- I was on RIO-L01B321C185D005 (6.0.1) (Middle East CUST version)
2- I used Firmware Finder application to update to RIO-L01B330C185D005 (OTA, 505 Megabytes) and it was updated successfully.
3- I found another B340C185D005 (OTA, about 167 Megabytes) and i installed it successfully.
4- Next, i thought to do a refresh to my phone by installing B330 again (Full Package, 1.3 GB) but it wasn't successful (i guess because it is a downgrade)
5- I flashed (using fastboot Boot.img, Recovery.img, System.img Successfully) B321C185D005 again and i said let's start from the beginning! And here is when i messed things up.
6- The B340 Updated the CUST version, but when i flashed the B321 didn't update the CUST so now i cannot receive any OTA updates or even use the Stock UPDATE.APP and Stock Recovery to restore any version.
Now, what i need is to restore everything back to it's original state.
Stock ROM (I'll Accept any version )
Stock Recovery
Stock CUST
Here is my current System with ProjectMenu:
Hardware Version: HL1RIOL01M
Bootloader Version: RIO-L01C185B321_APPSBOOT
Kernel Version: RIO-L01C185B321_KERNEL
AP Version: RIO-L01C185B321_SYSTEM
CP Version: RIO-L01C185B340_AMSS
Parameter Version: CVersion: C185, DVersion: D003!
this's my problem too
hope to find solution
kiro_koko said:
this's my problem too
hope to find solution
Click to expand...
Click to collapse
me too
I had the same issue with yours, but a little different.
I've installed C636B320 and forgot to create a backup then I've installed a custom rom and since no backup was created for the stock rom, I cannot go back to it's original state and manually flashing C636B10 works with some hiccups.
Here's what I did.
I went to the bootloader/fastboot section of the device and erased my system, recovery, boot, and userdata partitions and took my phone to a service center. I got my board replaced for free since it's under warranty.
Board replacement is only applicable if they will not be able to revive your phone by reinstalling any stock rom that they have. Don't worry they will not find out that you've unlocked your bootloader since they cannot access it via Volume Down+Power Key, it's not working for MM roms.
It sounds like a big hasssle, but it works!
Unfortunately, I've completed my warranty period. This means that i'll pay a lot to change the board. I think I only have 2 last hopes... First, is to get a new official update, which will be a higher version of the current CUST. Second, is to get an image of a similar phone with original cust and replace mine..
mooooorz1981 said:
To cut it short; let me describe what i've done to my victim RIO-L01
1- I was on RIO-L01B321C185D005 (6.0.1) (Middle East CUST version)
2- I used Firmware Finder application to update to RIO-L01B330C185D005 (OTA, 505 Megabytes) and it was updated successfully.
3- I found another B340C185D005 (OTA, about 167 Megabytes) and i installed it successfully.
4- Next, i thought to do a refresh to my phone by installing B330 again (Full Package, 1.3 GB) but it wasn't successful (i guess because it is a downgrade)
5- I flashed (using fastboot Boot.img, Recovery.img, System.img Successfully) B321C185D005 again and i said let's start from the beginning! And here is when i messed things up.
6- The B340 Updated the CUST version, but when i flashed the B321 didn't update the CUST so now i cannot receive any OTA updates or even use the Stock UPDATE.APP and Stock Recovery to restore any version.
Now, what i need is to restore everything back to it's original state.
Stock ROM (I'll Accept any version )
Stock Recovery
Stock CUST
Here is my current System with ProjectMenu:
Hardware Version: HL1RIOL01M
Bootloader Version: RIO-L01C185B321_APPSBOOT
Kernel Version: RIO-L01C185B321_KERNEL
AP Version: RIO-L01C185B321_SYSTEM
CP Version: RIO-L01C185B340_AMSS
Parameter Version: CVersion: C185, DVersion: D003!
Click to expand...
Click to collapse
Absolutely the same situation, same scenario, same versions as a result.
Have you finally solved this issue?
odemwingie said:
Absolutely the same situation, same scenario, same versions as a result.
Have you finally solved this issue?
Click to expand...
Click to collapse
No Still stuck in this version
anyone developer can help me ? i dont know what to do now icant use my phone
When Oreo edition will be released for our phone?
Hello everyone,
Recently, I was under the last android 6 update, unlocked, rooted and with TWRP recovery. ZenFone2 ZE551ML.
Then, I flashed a wrong custom Kernel from Jenkins and now I lost the USB data communication, so no data, no fast charging.
So I decided to flash full stock Rom and return back to zero, locked, unroot, android recovery.
Problem is, the kernel remained same there and now I'm without any possibility to flash anything. I'm back to Android 5 last update and I can only use stock system update from sd card (detect automatically)
Please, if someone could provide me with a flashable original Kernel to be flashed using stock system update from sd card. Then, once my USB is back, I will be able to root it again and most importantly, be able to fast charge the battery.
Thank you very much !
Nobody?
Download from the Asus website the latest firmware extracted BOOT.IMG and through fastboot you can flash it
Simple!
cieffe54 said:
Download from the Asus website the latest firmware extracted BOOT.IMG and through fastboot you can flash it
Simple!
Click to expand...
Click to collapse
firmware WW 20.40.206 from asus website not work fast charge also after 3 wipes from stock recovery. Bootloader locked , no root!
Francesco Liguoro said:
firmware WW 20.40.206 from asus website not work fast charge also after 3 wipes from stock recovery. Bootloader locked , no root!
Click to expand...
Click to collapse
Devi flashare da fastboot:
fastboot flash boot boot.img
cieffe54 said:
Devi flashare da fastboot:
fastboot flash boot boot.img
Click to expand...
Click to collapse
I think this is the right way. If you cannot use the USB data cable to flash the boot.img, you could try to flash a boot image with the flashily app (you need to be rooted).
This ZTE Blade V 20 Smart has the MTK6771 64 bit chipset. I have managed to get the bootloader unlocked, but I cannot get TWRP to flash, and I can't get the Magisk patched boot.img to flash either. I have tried using both fastboot commands and SPFT. When looking at the stock ROM back up, there are two files for boot that is just a regular "boot.img," and the other is labelled as "verified boot.img." The recovery uses two files listed similarly as well. So my question is, when running fastboot do I need to flash my custom .img files to boot_a.img and boot_b.img, as well as do the same for the recovery.img?
what version of your firmware?
Hello , i am new here .
I bought rooted red magic 5g
and i unrooted it
but i need the stock recovery
I searched everywhere on internet can't find it , hope i can find it here , thanks
Attached device info
YOU can take it from official rom update zip file and flash it from it i tried it with my phone RED magic 5s and it worked for me if you want me to downlead the update file if you have a cap in your internet i can and upload it in here tell me what region you are in
I am in saudi arebia and my phone is 5g not 5s , do you think it will not damage my phone ?
And can i add official rom on custom recovery ? Thank you
Sqeel said:
I am in saudi arebia and my phone is 5g not 5s , do you think it will not damage my phone ?
And can i add official rom on custom recovery ? Thank you
Click to expand...
Click to collapse
same as me i'm from Saudi Arabia just download official rom
http://rom.download.nubia.com/Europe/NX659J/V411/NX659J-update.zip
as your phone region and version EU just download and in it has official recovery.img in it extract it to minimal ADB and Fastboot folder and go to bootloader by :
adb reboot bootloader
flash it with :
fastboot flash recovery recovery.img
no you can't flash it custom recovery in my test in my phone it just boot you into recovery and dosen't boot
and your OS update is old try update after restore recovery
good day. i am a newbie. my phone is Red magic 5g bootloader is unlocked and want to go back to stock ROM because i want my phone updated using the "setting" system update". because of bootloader unlock I can't update my phone. maybe someone there can help me with the step by step tutorial on how to get back from stock ROM. attached file is my about phone. thank you so much.
Hello,
About a week ago I updated to MIUI 13 (13.0.2.0.SJEMIXM). My phone (Redmi Note 9T) was rooted and I had a custom recovery (Orange Fox) installed. I flashed the stock recovery and was then able to update. I left the stock recovery on the phone to make it easier to update down the line but did root my phone again.
This morning I was informed that there is a new update (13.0.3.0.SJEMIXM) so I download and installed it. All went well and the phone booted successfully.
I then wanted to have my phone rooted again (magisk) so I just took the boot.img from the previous version (13.0.2.0.SJEMIXM) to be patched since I did not have the factory Rom for the new version (13.0.3.0.SJEMIXM) to retrieve the boot.img file.
I then flashed the patched boot.img via fastboot (fastboot flash boot magisk_pached.img) and my phone started to bootloop.
I also tried flashing the unpatched boot.img but it is still the old one.
I don't know if I did something wrong or if it is just the old boot.img that I need to replace, pls help.
Ps: I have downloaded the OTA update (13.0.3.0.SJEMIXM) but it only contains a boot.img.p file.
Rubz_Mod said:
Hello,
About a week ago I updated to MIUI 13 (13.0.2.0.SJEMIXM). My phone (Redmi Note 9T) was rooted and I had a custom recovery (Orange Fox) installed. I flashed the stock recovery and was then able to update. I left the stock recovery on the phone to make it easier to update down the line but did root my phone again.
This morning I was informed that there is a new update (13.0.3.0.SJEMIXM) so I download and installed it. All went well and the phone booted successfully.
I then wanted to have my phone rooted again (magisk) so I just took the boot.img from the previous version (13.0.2.0.SJEMIXM) to be patched since I did not have the factory Rom for the new version (13.0.3.0.SJEMIXM) to retrieve the boot.img file.
I then flashed the patched boot.img via fastboot (fastboot flash boot magisk_pached.img) and my phone started to bootloop.
I also tried flashing the unpatched boot.img but it is still the old one.
I don't know if I did something wrong or if it is just the old boot.img that I need to replace, pls help.
Ps: I have downloaded the OTA update (13.0.3.0.SJEMIXM) but it only contains a boot.img.p file.
Click to expand...
Click to collapse
Flash the (13.0.3.0.SJEMIXM)boot.img with O.F .
Use Magisk app for rooting the phone.
I fixed the problem.
All I had to do was find new the boot.img and flash it via fastboot.
I then patched the new boot.img file and then I flashed the patched.img via fastboot.
Thanks for your help