I have a RN4 on Global Stable ROM 8.5.8.0 NCMFIED.. I want to switch to global beta so I tried using fastboot method.. But I get flash modem error in MiFlash tool.. Any solutions??
It seems that something is wrong with the fastboot syntax(from log).. MiFlash log attached....
Solved it.. Turns out the flash_all.bat script is not built to handle path with white spaces in them as it does not use quotation marks(" ") for path.. For eg.. you cannot extract the downloaded fastboot ROM to C:\New Folder\xyz due to white space... To resolve this just place the downloaded ROM in a path with no white space..
I wish you could have written this in plain English, I do not understand what you mean by white space. and i am having this same problem
fixed solution
copy the fastboot flash file in local disk c directly and then flash problem solved, also rename the flash file in short name like mido only
dont put fast boot flash file in desktop or anywhere else put only in 1st page of local disk c (system disk)
thx very much , its work
Didn't worked
:crying:I tried exactly you said . But the same error comes again.
unlock the bootloader and try again....
unlock the boot in miui and try again it will flash
Unlocked
It is already unlocked by the seller
Bk201___ said:
It is already unlocked by the seller
Click to expand...
Click to collapse
it's late reply but now i am having the same problem, i solved it when i put the phone in edl mode, mine is redmi 5 plus (MEG7).... i hope it helps.
Related
Hi guys,
yesterday I received my Note 3 Pro Kenzo (SD) from Gearbest.
There was an old MIUI-version installed that wasn't really localized to German (maybe a shop-ROM), so I decided to install an up-to-date version of MIUI.
I downloaded the "Redmi Note 3 Qualcomm Latest Global Stable Version Fastboot File Download" from here, which seems to be V8.0.1.0.LHOMIDG (MIUI8), put my phone in fastboot mode (in EDL-mode it didn't work, MiFlash didn't find my phone) and installed the ROM with MiFlash. Everything is working now, localization is perfect and the phone runs smooth.
The only strange thing is, that I haven't been able to unlock the bootloader officially yet, wether with the "old" ROM-version nor with the latest Global Stable MIUI8.
On MIUI7 the unlock-tool said, I don't need an unlock(?), on MIUI8 it says my phone is not permitted (or something similiar), even if I have the confirmation-SMS from Xiaomi (that was on August 19th) and I'm logged in into my Mi-account on the phone and in the unlock-tool.
Am I doing something wrong? Here it's said that it should be possible to unlock using the offical way with my new ROM.
Or do I have to be on another ROM to unlock my bootloader?
Background is that I want to try out different ROMs, so I need to install TWRP first - and I absolutely need root-access!
Can I flash TWRP over adb without unlocking?
Any help from you is really much appreciated.
Thanks a lot and best regards
Mischa
You need unlocked bootloader to flash TWRP to the device
Did you follow the steps here?
http://en.miui.com/thread-280561-1-1.html
Thanks for the link, this looks really useful!
Is it right that I can stay on my Global Stable (Fastboot) ROM? Or do I have to flash the Global Beta Recovery ROM?
Guys, I need some help!
My phone is only found from MiFlash when it's in Fastboot-mode. When I put it in EDL-mode MiFlash can't find it.
EDIT: BTW, I just found this in my MiFlash-log:
Code:
[23:16:02]:install driver C:\Program Files (x86)\MiFlash\Source\ThirdParty\Google\Driver\android_winusb.inf to ,result False,GetLastWin32Error Unknown error (0xe000024b)
What does it mean? My phone is found with "adb devices" and the adb-drivers seems to be okay
The "Qualcomm HS-USB QDLoader 9008"-driver is installed and shown in the device manager when I executed "adb reboot edl".
My phone seems to be in EDL-mode with black screen and blinking red LED.
Right now I'm running Global Stable (Fastboot) V8.0.1.0.
I had to install this ROM also when I was in Fastboot-mode, cause only then MiFlash found my phone (same problem), not in EDL-mode.
Do you have any idea what went wrong?
Worst thing is that I can't flash any ROM using this way anymore, cause MiFlash now says "phone is locked" when I try to flash anything in fastboot mode. Also recovery ROMs are not usable with updater-app (maybe because my bootloader is still locked).
So, seems like I'm caught: I can't unlock my bootloader, I can't flash any other ROM, I can't root and can't install TWRP - I'm stuck on Global Stable V8.0.1.0
I really appreciate any help from you!
Best regards and thanks a lot
Mischa
EDIT: SUCCESS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
It finally worked
What I did? I used MiFlash V2016.04.01 (instead of the lastest version from August 30th), which I got from here: http://xiaomitips.com/download-in-progress/?dlm-dp-dl=1474 (I hope it's allowed to post links here, otherwise PM me for downloading it from my Google Drive).
After I installed it, it re-installed the Qualcomm-drivers - and with this version I was finally able to see my phone in EDL-mode.
I also found out that only with this version you could set the advanced settings in MiFlash, cause in the newest version this option is not available anymore.
BTW, after every attemp to unlock the bootloader officially failed, I now unlocked it successfully using the unofficial way.
Best regards
Mischa
My Redmi Note 5A Prime came with unlocked bootloader with a fake rom. so I flashed official developer fastboot rom. After that my IMEI broke and bootloader locked. Unable to open diag mode. Unable to add MI Account on the phone. I search the internet but sadly couldn't find anything. what I have found needs unlocked bootloader. Can anyone please help me to unlock the bootloader?
You have to apply here: http://en.miui.com/unlock/ in order to unlock your bootloader (can take a bit to get verified)
In addition add the phone number you apply with to your mi clound & login to your mi account on your phone.
Download the software for windows --> login --> connect your phone via fastboot --> hit unlock.
If it still does not work, please go ahead and flash the latest china developer rom on your phone and try everything again.
Good luck and please tell me if it worked
you can unlock unofficial bootloader with edl mode:
http://en.miui.com/thread-2049615-1-1.html
Thanks a lot for this solution ada12, it looks promissing.
I suppose that what they mean on your link by "REBOOT YOUR PHONE TO EDL MODE ( Testpoint )" is that i need to unmount the phone like in this video, right?
I havn't tried the hardware method yet, and when I try to use myflash with what is in RNote5_unlock.zip it says it cannot find the file flash_all.bat. So I tried different things:
- used the bach scripts contained in ugglite_global_images_8.4.12_20180412.0000.00_7.1_global but it fails saying cannot find the file tz.mbn... for sure it's not there
- added what was in the zip to the folder ugglite_global_images_8.4.12_20180412.0000.00_7.1_global but then i get the same error that i have been getting for the past several hours "Flash tz error" in mi flash...
What am I doing wrong?
Today, when I try to access the thread on the miui forum i get this error message :/
Sorry, you don't have the permission to access this thread.
[ Xiaomi MIUI Official Forum Home ]
Can you still see it ada12?
parpagnas said:
Thanks a lot for this solution ada12, it looks promissing.
I suppose that what they mean on your link by "REBOOT YOUR PHONE TO EDL MODE ( Testpoint )" is that i need to unmount the phone like in this video, right?
I havn't tried the hardware method yet, and when I try to use myflash with what is in RNote5_unlock.zip it says it cannot find the file flash_all.bat. So I tried different things:
- used the bach scripts contained in ugglite_global_images_8.4.12_20180412.0000.00_7.1_global but it fails saying cannot find the file tz.mbn... for sure it's not there
- added what was in the zip to the folder ugglite_global_images_8.4.12_20180412.0000.00_7.1_global but then i get the same error that i have been getting for the past several hours "Flash tz error" in mi flash...
What am I doing wrong?[/QUOTE
You try different rom to flashing,I mean your device is RN5A Prime(Ugg)not Ugglite
Sent from my ugg using XDA Labs
Click to expand...
Click to collapse
[Help] Flash global rom my redmi note 5a that i recently bought is tampered
can you please help me to flash a global rom ? i bought a redmi note 5a but i found out that my rom is tampered not global. after searching i found out that i need to unlock the bootloader. but it sucks at 99% . anyone please help me.
godexgaming said:
can you please help me to flash a global rom ? i bought a redmi note 5a but i found out that my rom is tampered not global. after searching i found out that i need to unlock the bootloader. but it sucks at 99% . anyone please help me.
Click to expand...
Click to collapse
Did you try bounding mi account?If yes try 3 day to try agains to UBL and dont forget to visit mi community,in there many guides to UBL your devices,good luck..
Sent from my ugg using XDA Labs
godexgaming said:
can you please help me to flash a global rom ? i bought a redmi note 5a but i found out that my rom is tampered not global. after searching i found out that i need to unlock the bootloader. but it sucks at 99% . anyone please help me.
Click to expand...
Click to collapse
I had the same problem - the phone came with a 'fake' global rom installed and it was impossible to bind the phone and account. The way I got around it was to flash the latest Chinese stable rom (it isn't possible to flash the global rom while the bootloader is locked) onto the phone and then I was able to bind the phone and account. Once I got to this stage I was then able to request unlock permission which now takes 360 hours (15 days). Once the 15 days have elapsed the bootloader can be unlocked and you are then free to install the latest global rom.
To fix IMEI problem:
1.) Reboot to fastboot mode
2.) Run command: fastboot erase modemst1
3.) Run command: fastboot erase modemst2
4.) IMEI fixed!
For bootloader unlock,if you cant add Mi account to your phone,it is problem,becouse you have to submit phone to unlock request (via developer mode).
Try this: Go to Developer settings,check "Allow OEM unlock" option and then try add MiAccount via next option "Mi unlock status"
lazynkox said:
To fix IMEI problem:
1.) Reboot to fastboot mode
2.) Run command: fastboot erase modemst1
3.) Run command: fastboot erase modemst2
4.) IMEI fixed!
For bootloader unlock,if you cant add Mi account to your phone,it is problem,becouse you have to submit phone to unlock request (via developer mode).
Try this: Go to Developer settings,check "Allow OEM unlock" option and then try add MiAccount via next option "Mi unlock status"
Click to expand...
Click to collapse
I agree with everything here, good job. Just want to add something to "unlock bootloader": if you recieve some error "it can't be added", download a VPN with the location in china. There is one app (at least) where you can create an fake account (e.g. 10 minute mail) and have 1 day of premium. Point it onto china and try to add your mi account again, that should do the trick.
Good luck and have fun ^^ ask if you have some problems!
---------- Post added at 02:11 PM ---------- Previous post was at 02:03 PM ----------
parpagnas said:
Thanks a lot for this solution ada12, it looks promissing.
I suppose that what they mean on your link by "REBOOT YOUR PHONE TO EDL MODE ( Testpoint )" is that i need to unmount the phone like in this video, right?
I havn't tried the hardware method yet, and when I try to use myflash with what is in RNote5_unlock.zip it says it cannot find the file flash_all.bat. So I tried different things:
- used the bach scripts contained in ugglite_global_images_8.4.12_20180412.0000.00_7.1_global but it fails saying cannot find the file tz.mbn... for sure it's not there
- added what was in the zip to the folder ugglite_global_images_8.4.12_20180412.0000.00_7.1_global but then i get the same error that i have been getting for the past several hours "Flash tz error" in mi flash...
What am I doing wrong?
Click to expand...
Click to collapse
The answer is: NANOMACHINES, SON!
Just kidding, you have to point onto the root folder, if the system can't find the "flash.bat" you might be one folder too deep. If you get an error message during flashing then you might have a problem in terms of compatibility.
I still don't know yet, what the NSF means by mentioning the computer system with the "blue face for an interface" as an solution to xiaomis bootloader incompatibility issue. It seems suspicious, that some valuable forum posts have gone missing... wondering what the NSF is up to.
:highfive:
md.safayat said:
My Redmi Note 5A Prime came with unlocked bootloader with a fake rom. so I flashed official developer fastboot rom. After that my IMEI broke and bootloader locked. Unable to open diag mode. Unable to add MI Account on the phone. I search the internet but sadly couldn't find anything. what I have found needs unlocked bootloader. Can anyone please help me to unlock the bootloader?
Click to expand...
Click to collapse
Hi to all. i have problem with redmi note 5a after remove micloud wifi and bluetooth unaviable. i try many official roms, but no luck. Please help to resolve this problem.
lazynkox said:
To fix IMEI problem:
1.) Reboot to fastboot mode
2.) Run command: fastboot erase modemst1
3.) Run command: fastboot erase modemst2
4.) IMEI fixed!
For bootloader unlock,if you cant add Mi account to your phone,it is problem,becouse you have to submit phone to unlock request (via developer mode).
Try this: Go to Developer settings,check "Allow OEM unlock" option and then try add MiAccount via next option "Mi unlock status"
Click to expand...
Click to collapse
How will you run these commands on a locked bootloader? And no erasing modemst1-2 won't fix imei's.
Hello together,
today i wanted to rebrand my honor 9 from STF-L00 to STF-L09 and everything worked fine for me at the beginning. I unlock my bootloader and then i used the update.bat and follow the instructions. It installed TWRP. After a while nothing happened and i was still in the fastboot mode. In the fastboot mode i saw that my bootloader is locked again.
Now i have no OS and cannot used adb via fastboot, it does not recognize any device detected.
I downloaded MultiTool and it says i have installed STF-L09 now on my phone.
Info:
According to MultiTool is STF-L09 installed
Bootloader and FRP are locked
I just have Huawei eRecovery, but this is not working (Pacakge info fails)
I have no rom, because my phone is booting only in eRecovery
adb fastboot does not get recognized my phone.
Have all drivers needed on pc for adb to work.
HiSuite doesn't support recovery on this device.
Please help me, i don't know what i should do and i really start to despair. :crying::crying::crying:
Thank you very much
I have pretty much the exact same problem. The only difference is I was trying to rebrand from AL10 to L09. Got the same error in the same stage of rebranding, can access the exact same things as you, same goddamn FRP lock etc. Same all the way through except for starting from AL10 in stead of L00.
I have not found any free solution, the best I could find is DC Phoenix whose program claims that it "Can write firmware by fastboot with locked bootloader and locked FRP!" The thing is, it will cost 15 Euros to use this function in their program, and after paying etc. it is only available for 72 hours. At this moment I don't have access to a computer for the next 72 hours, so I have decided to wait a short while until I have a computer available for a 72-hour period. While I guess it would only take a short time, I realise now that nothing is ever as easy as it seems with Huawei and their absolute **** software... hence I want to wait for being able to use all 72 hours before paying.
This link has their guide to what needs to be done:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
If you want to give it a try, it's the one possible solution I've found after MUCH googling. Though I remain hopeful that someone else on this forum might have a better (free) solution!
Hello Sanktgoran,
at first thank you very much for your help.
I have a question about the DC Unlocker. When i use this and write a new firmware by DC Unlocker, then i don't have to rebrand again?
Which rom do i should use to write on my phone?
Should i use the STF-AL00 rom or STF-L09 rom or it doens't matter?
Multitool says that i have STF-L09 on my phone, but my phone have no OS, because it doesn't boot.
Thanks
I'm not sure actually which one to use. I think you should go with the L09, since that is what the phone "thinks" it is at the moment. If it works to instll the L09 Firmware via DC unlocker, I think that would be the rebranding done as well. The way I understand this situation we are both in, our phones are rebranded to L09, just the actual L09 OS isn't really installed properly, and the FRP lock prevents us from unlocking bootloader, which in turn prevents us from completing the installation of L09. So by using the DC Unlocker to bypass the locks and installing the firmware, the process should then be complete.
I'm not sure about this though, it's just how i think it is. It might be that using DC will install the firmware stably and all is well, and it might be that it will install some of it and then the phone can at least boot into an incomplete OS where we could disable the FRP and bootloader locks, and thus be able to use the Update function in the HWOTA script to get things finished. Either way, I'm 99% sure that using the DC Unlocker will get us further along the path to a european Honor 9 than we are at this stage. I'm going to attempt it later today or perhaps tomorrow I think. After all, 15 euros is a small amount to spend compared to the cost of the actual phone...
Did you also copy an OEMinfo file for L09 into your adb/fastboot folder and run this command before using the HWOTA script?
ADB push oeminfo /tmp/oeminfo
ADB shell "dd if=/tmp/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo"
I did, I'm not 100% sure what it does/is supposed to do, but I think it has made it so that the phone thinks it's done and rebranded, and tries to boot into L09, but since the L09 installation wasn't completed in the HWOTA script, it can't boot because firmware stuff is missing. That has me thinking that it's the L09 and not AL00 which you should use with DC Unlocker.
Did you check https://forum.xda-developers.com/honor-9/help/soft-bricked-honor-9-trying-to-root-t3737967 ?
Finally, it worked for me everything fine.
Here is one tip from me:
I downloaded at first the rom from a website and started to flash, but it failed.
After a long time of searching and asking, i got help.
You have to download directly from the DC Phoenix the rom (with the custominization file) and flash.
When you don't know how, just post here and i will write a short guide.
Thanks for helping. :good:
That's great, glad things worked out for you! Was it the full firmware file you downloaded from DC Phoenix, the ~4 gigabyte update.app file? Or the three .zip files, update.zip, update_data_full_public.zip and update_full_stf-L09_hw_eu? Do you download it from their website or through the DC Unlocker program? How big was the entire download? I'm on a limited monthly data kind of thing, just curious how big the download is.
Sanktgoran said:
That's great, glad things worked out for you! Was it the full firmware file you downloaded from DC Phoenix, the ~4 gigabyte update.app file? Or the three .zip files, update.zip, update_data_full_public.zip and update_full_stf-L09_hw_eu? Do you download it from their website or through the DC Unlocker program? How big was the entire download? I'm on a limited monthly data kind of thing, just curious how big the download is.
Click to expand...
Click to collapse
I use the download function from DC Phoenix.
When you open DC Phoenix, just click "Download Files" and a website will open, where you can search for the rom.
Search for "STF-L09" and you will get all roms for the STF-L09. I prefer to use this rom:
Stanford-L09_C432B130_Firmware_Belgium_Germany_France_Netherlands_Portugal_Switzerland_Spain_Italy_Aus
And for every rom you should download the customization file. They are directly together:
Stanford-L09_C432B130_update_data_customization_hw_eu.APP
You have to download both .APP files and the both files are in total almost 3,2 GB.
You open DC Phoenix and open the files there.
The Firmware you open in "Update File"
The customization file you open in "Customization File (optional)"
You connect your phone via fastboot and then you can start to update.
I don't know from which country you are, so i don't know which version of rom do you need.
When you download the rom which i downloaded before, you have just the B130 Version. But theres is already B182 existing. You can download the new rom via your phone in the settings.
Here is also the same guide from DC Unlocker (except of the part how you can download the rom).
https://www.dc-unlocker.com/huawei-phone-flashing-in-fastboot
Somehow its possible to flash firmware in dc Phoenix and having a locked Bootloader.
Shouldnt it be possible to use config.txt and flash twrp as recovery and then flash ur full stock?
Im asking cause i m not able to unlock the bootloader. The V+ Button is broke ( Mainboard related) and i cant agree to unlock after entering my code.
I got my phone bricked. I tried to flash global rom and switched back to China using Realme Flash Tool which is a bat file I found here. I cannot enter recovery/fastboot/edl. How am I going to fix it? I have downloaded the original firmware file along with msm download tool. Any way to access to msm? Please help me.
same issue here , my phone stuck with bootloop
my phone came with the chianes rom so i unlock the bootloader and install the global one from here then everything were fine but when i try to re-lock the bootloader again this happen
Link:
VEED - video-1658817419.mp4
Make stunning videos with a single click. Cut, trim, crop, add subtitles and more. Online, no account needed. Try it now, free. VEED
www.veed.io
beacuse you tried flashing with locked bootloader. Only hope is service center. or MSM download tool. Some guys are selling code for 3-10 USD. I dont have contact. So dont PM me.
I've already unlocked bootloader. Pc doesn't seem to detect it. I don't know what to do. Only if I can enter edl mode, maybe I can flash it once again
Zarni96 said:
I've already unlocked bootloader. Pc doesn't seem to detect it. I don't know what to do. Only if I can enter edl mode, maybe I can flash it once again
Click to expand...
Click to collapse
go to service center ,You did not restore boot
My A03s isnt showing the OEM Unlock option is developer settings, even though its unlocked
Which model?
Swyen said:
My A03s isnt showing the OEM Unlock option is developer settings, even though its unlocked
Click to expand...
Click to collapse
Is it the mediatek one? Oem unlock doesn't matter anyway. I've had 2 of these phones and you can just plug it in to a tool like mtkclient and boom you've unlocked the bootloader with no oem option. Unlocktool can also network unlock that phone too.
r1pp3d2 said:
Is it the mediatek one? Oem unlock doesn't matter anyway. I've had 2 of these phones and you can just plug it in to a tool like mtkclient and boom you've unlocked the bootloader with no oem option. Unlocktool can also network unlock that phone too.
Click to expand...
Click to collapse
Which sim unlock tool do you recommend? Thanks.
magi44ken said:
Which sim unlock tool do you recommend? Thanks.
Click to expand...
Click to collapse
Unlocktool can network unlock it for sure. I've done two of the A03s's with it.
r1pp3d2 said:
Unlocktool can network unlock it for sure. I've done two of the A03s's with it.
Click to expand...
Click to collapse
You mean this web site: https://unlocktool.net?
magi44ken said:
You mean this web site: https://unlocktool.net?
Click to expand...
Click to collapse
Yep, that's the one. It's a really good tool for cheap.
r1pp3d2 said:
Is it the mediatek one? Oem unlock doesn't matter anyway. I've had 2 of these phones and you can just plug it in to a tool like mtkclient and boom you've unlocked the bootloader with no oem option. Unlocktool can also network unlock that phone too.
Click to expand...
Click to collapse
how did you manage to boot it into BROM? I cant seem to get it into BROM.
Swyen said:
how did you manage to boot it into BROM? I cant seem to get it into BROM.
Click to expand...
Click to collapse
I don't know if you figured it out but to get into brom you do exactly as the mtkclient tells you too. I didn't get it working in windows but I used the boot DVD that is listed on the github mtkclient page. My model is sm-a037u from MetroPCS. The software tells you to power off the phone. Then plug the USB cable into the computer and then before you insert the USB cable into your phone hold down both volume buttons at the same time. I did get the bootloader unlocked with mtkclient but kept getting an error about the vbmeta or something so I had to flash back my backup I made with mtkclient. I think I just flashed back the boot.img and the vbmeta. I have not messed with it since. I tried flashing the magisk patched bootloader but got the same error I believe. Make sure you do a full backup except for maybe the user data partition to save time. I read another thread here on xda about I think the f instead of u model in where they patched the whole stock rom image with magisk or a certain part of it. If I ever try it again I will do a write up about it. Also to speed up the backup use a USB 3 port on your computer.
DaRkSkYxP said:
I don't know if you figured it out but to get into brom you do exactly as the mtkclient tells you too. I didn't get it working in windows but I used the boot DVD that is listed on the github mtkclient page. My model is sm-a037u from MetroPCS. The software tells you to power off the phone. Then plug the USB cable into the computer and then before you insert the USB cable into your phone hold down both volume buttons at the same time. I did get the bootloader unlocked with mtkclient but kept getting an error about the vbmeta or something so I had to flash back my backup I made with mtkclient. I think I just flashed back the boot.img and the vbmeta. I have not messed with it since. I tried flashing the magisk patched bootloader but got the same error I believe. Make sure you do a full backup except for maybe the user data partition to save time. I read another thread here on xda about I think the f instead of u model in where they patched the whole stock rom image with magisk or a certain part of it. If I ever try it again I will do a write up about it. Also to speed up the backup use a USB 3 port on your computer.
Click to expand...
Click to collapse
Try installing libusb. When you run it, (with mediatek drivers installed), plug in your phone from a powered off state. Do NOT hold any buttons.
If using a laptop, you might want to use a mouse.
To install the filter, you need to see it in the list and it will only appear for about 2 seconds. You need to quickly select it then install.
Once you do that, search for the A03 frp tool which will include your scatter file and an app that crashes and allows to erase a partition with frp system files. But i think it also gives you flashing capability. I am going to try it now.
If you have issues you need to turn off anti virus (anyone with some experience should know the basics and how to deal with issues such as tossing computer into large inferno etc). Use windows 10. 11 may not work.
Ok so I was able to successfully flash the modified (magisk patched) boot.img and I replaced it in the firmware package found here:
Samsung A037F U1 (A037FXXU1AUI7) Dead Boot Repair Scatter EMMC Dump File
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
I used this set of files to make the process possible:
Samsung A03s FRP All Android version.rar
drive.google.com
In the photo you'll notice things seemed to have gone well... but the phone now just boots to download mode.
I changed connection from UART to USB in the provided flash tool. Maybe that was my mistake. I must admit i am not too good at doing this stuff and am usually taking advantage of other people's ideas. Any help would be appreciated. I will continue to work on this and see if I can make it work. The phone I am using is SM-A037W and it has the latest firmware available that is available at the time of this posting
I'm thinking maybe I need to flash vbmeta with a certain flag but only recall doing that from powershell... somehow.
mindlery said:
Ok so I was able to successfully flash the modified (magisk patched) boot.img and I replaced it in the firmware package found here:
Samsung A037F U1 (A037FXXU1AUI7) Dead Boot Repair Scatter EMMC Dump File
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
I used this set of files to make the process possible:
Samsung A03s FRP All Android version.rar
drive.google.com
In the photo you'll notice things seemed to have gone well... but the phone now just boots to download mode.
I changed connection from UART to USB in the provided flash tool. Maybe that was my mistake. I must admit i am not too good at doing this stuff and am usually taking advantage of other people's ideas. Any help would be appreciated. I will continue to work on this and see if I can make it work. The phone I am using is SM-A037W and it has the latest firmware available that is available at the time of this posting
I'm thinking maybe I need to flash vbmeta with a certain flag but only recall doing that from powershell... somehow.
Click to expand...
Click to collapse
Try fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
r1pp3d2 said:
Try fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
Click to expand...
Click to collapse
Just use the original vbmeta.img from the backup? Don't need to edit it?