Question A125u Stuck in brom - Samsung Galaxy A12

Got an a125u that i put into brom with mtk meta utility. After that i unlocked it and flashed twrp, and patched boot. After i put it in brom i cant get it out of brom for the life of me. just need some help thanks.

I'm stuck with same problem man. I've bought 4 of these phones DO Not I Repeat do not Flash TWRP It will mess the device tree up or something I'm thinking.

Mattinthahack said:
I'm stuck with same problem man. I've bought 4 of these phones DO Not I Repeat do not Flash TWRP It will mess the device tree up or something I'm thinking.
Click to expand...
Click to collapse
I just made a full dump of the rom and swapped out the recovery files, boot, and vbmeta. I wiped it then flashed it with mtkclient with the wl out command. It wont exit brom(i used mtkmeta utility for brom and not the TP and i think that messed it up). I sent the mtkclient devs a question and trying as many methods as i think of. A fix is bound to arise.

MTKMeta was your problem It states in the description that the tool might mess our phones up, the A12 is one of the phones listed to not use with the tool at this point in time. It breaks the phone Not sure why

Mattinthahack said:
MTKMeta was your problem It states in the description that the tool might mess our phones up, the A12 is one of the phones listed to not use with the tool at this point in time. It breaks the phone Not sure why
Click to expand...
Click to collapse
Yeah kinda missed that small print welp

I figured it out.extract all files in bl, ap, csc, cp(must be firmware you were on). convert from lz4 to img if need be theres a tool for it. In mtk client you have to flash the partitions individually. So python mtk printgpt to see all your partitions then flash all the files to their partitions(python mtk w boot exampleboot.img). I just made a script to install everything from the run.example. After you get it all installed i held volume down and power and it rebooted into download mode then just use odin after that.

Mattinthahack said:
MTKMeta was your problem It states in the description that the tool might mess our phones up, the A12 is one of the phones listed to not use with the tool at this point in time. It breaks the phone Not sure why
Click to expand...
Click to collapse
I fixed it

I have same issue but i can’t find firmware for att sm-a125u stuck firmware (a125usqs3bvb2) and cuurent firmware is a125usqs3bvbd6

ammaoui said:
I have same issue but i can’t find firmware for att sm-a125u stuck firmware (a125usqs3bvb2) and cuurent firmware is a125usqs3bvbd6
Click to expand...
Click to collapse
Did you format ur device with sp flasher? Bc that could be why your stuck in brom so your missing some files. I pm you so i can help you out.

gman6686 said:
Did you format ur device with sp flasher? Bc that could be why your stuck in brom so your missing some files. I pm you so i can help you out.
Click to expand...
Click to collapse
the device was stuck in download mode after ota update(a125usqs3bvd6 security patch 01.04.2022). I tried to flash in odin didn’t accept firmware so then i tried mtk_metautility and sp flash tool to flash and format with the firmware SM-A125U U3 OS11 Scatter Firmware [Dead Boot Repair] (A125USQS3BVA2).zip

Related

ulefone Power 2 Development and Support

Ulefone power 2 Development and Support-
Basic Device Details-
Display- 5.5 inch
OS- android 7.0 Nougat
Chipset - MT6757T
RAM- 4GB
Disclaimer-
Code:
i am not Responsible for any damage to Your Device..
official Firmware-
https://drive.google.com/drive/folders/0B8NC4kBpjQhYV1lWOEtYWThRRms
twrp Recovery-
https://drive.google.com/open?id=0B1aXJDZjE8bvM0h0aTVEOEdBS1U
SP Flash tools and Driver-
https://drive.google.com/folderview?id=0B6O3B5Tc7Wr9ZzgxQmcyNmNoX00
Magisk-
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
No verity opt-Encrypt-
https://www.androidfilehost.com/?fid=673368273298927206
extras-
Greenify for Battery-
http://m.hiapphere.com/apk-com.oasisfeng.greenify
Build.prop tweaks-
[Must Backup official before try-
https://forum.xda-developers.com/attachment.php?attachmentid=4248841&stc=1&d=1503381757
Guide-
Flash Firmware-
1. Install Vcom Driver Run SP flash tools, Load Scatter File , Check Everything and then click Download, as soon as connect your Switched off Phone.
Flash twrp-
Code:
fastboot oem unlock
fastboot flash recovery recovery.img
or use inbuild script
if you have Scatter then you can Flash with SP flash tools.
Root-
flash Magisk via twrp or you can also use Supersu 2.78XX.
Mod-
Will be added Soon....:good:
version- 3.00XX
Credit- XN Logos
Donation- https://Paypal.me/droiddeveloper
Please Don't create mirror Without the Link of This Page.
I tried it but it didn't work. twrp is installed but my phone doesn't boot into the system anymore. When I reboot it goes back to Twrp and then the touchscreen doesn't work anymore. I have to connect an USB-mouse. But it still doesn't boot.
When I try to flash or wipe sth it says "unable to mount"
I had to flash the original software again with SP Flash Tools
No flash No verity encrypt to Disable boot verification
XN Logos said:
No flash No verity encrypt to Disable boot verification
Click to expand...
Click to collapse
sorry but what does that mean?
So i used your TWRP Recovery, normally it should work and it does but why is my data shown as 0.
Thank you too. Please help
where is the scatter file?
gasperoni said:
where is the scatter file?
Click to expand...
Click to collapse
no Scatter included use Fastboot, or You can take scatter from ROM.
Ok but where is the recovery image file to flash via SP Flash Tools? I only see an exe-file saying "flash recovery" and a 12.6MB file called "rk" but it's shown me as a mp4-file
it worked!!! Thank yoU!! @gasperoni, just start "Flash Recovery.exe" and do what is written in the window. It's really easy.
i have include a Script which have ability to unlock bootloader and then flash twrp, if you flash with SP flash tool your Device not bootup because bootloader is Loacked. so Simply use Given Instruction Not SP flash.
any custom ROM
non yet
hm..i install twrp with your "flash recovery.exe", my phone reboots, i have to press "volume up" to unlock my bootloader. then trwp starts.
until here everything works fine. But when i am installing Superuser and restart my phone, it writes sth like "orange mode, your phone is untrusted" and just boots into twrp, touchscreen isnt working. So i have to flash it again, but i didnt achieve twrp of course :S
Unlucky25 said:
hm..i install twrp with your "flash recovery.exe", my phone reboots, i have to press "volume up" to unlock my bootloader. then trwp starts.
until here everything works fine. But when i am installing Superuser and restart my phone, it writes sth like "orange mode, your phone is untrusted" and just boots into twrp, touchscreen isnt working. So i have to flash it again, but i didnt achieve twrp of course :S
Click to expand...
Click to collapse
Same issue for me.
I tried twice to install the recovery with the .exe file. Both times I bricked the phone. Why?
kylebutler said:
Same issue for me.
I tried twice to install the recovery with the .exe file. Both times I bricked the phone. Why?
Click to expand...
Click to collapse
Same result here. But how did you get the factory rom to flash on the phone? I first got some checksum error and had to find a checksum generator and now the silly multiport flash software says:
" Warning maybe error as follows: 1 com port number repetitive or invalid 2 brom and preloader have the same comport number! Please modify them in INI file or scan again."
I think i did everything correctly (installed the drivers and stuff as it says on the ulefone download page) but i haven't flashed any mediatek devices in a long time and i would be very thankful if someone can tell me what i'm doing wrong. I don't mind it getting bricked as i know that is always a risk with mediatek, but i do need to be able to flash the stock rom.
ml11ML said:
Same result here. But how did you get the factory rom to flash on the phone? I first got some checksum error and had to find a checksum generator and now the silly multiport flash softwhttps://forum.xda-developers.com/usercp.phpare says:
" Warning maybe error as follows: 1 com port number repetitive or invalid 2 brom and preloader have the same comport number! Please modify them in INI file or scan again."
I think i did everything correctly (installed the drivers and stuff as it says on the ulefone download page) but i haven't flashed any mediatek devices in a long time and i would be very thankful if someone can tell me what i'm doing wrong. I don't mind it getting bricked as i know that is always a risk with mediatek, but i do need to be able to flash the stock rom.
Click to expand...
Click to collapse
I had also issues using the flash tool provided on the Ulefone website, the same as you say (with the checksum). None of checksum-generating software worked for me, so I was searching long for an alternative and found this flash tool: https://spflashtool.com/. Using this tool, flashing worked for me perfectly even without having to bother with checksums.
Good luck!
pavelmracek said:
I had also issues using the flash tool provided on the Ulefone website, the same as you say (with the checksum). None of checksum-generating software worked for me, so I was searching long for an alternative and found this flash tool: https://spflashtool.com/. Using this tool, flashing worked for me perfectly even without having to bother with checksums.
Good luck!
Click to expand...
Click to collapse
Thank you very much for this! That tool works flawlessly unlike the ulefone garbage.
On another note... anyone know if there is source code for the power 2 to be found somewhere or did the dev just port another recovery somehow? I tried a while back just porting twrp by swapping files but i couldn't get the image to repack with the kitchen tool so i gave up.
ml11ML said:
Same result here. But how did you get the factory rom to flash on the phone? I first got some checksum error and had to find a checksum generator and now the silly multiport flash software says:
" Warning maybe error as follows: 1 com port number repetitive or invalid 2 brom and preloader have the same comport number! Please modify them in INI file or scan again."
I think i did everything correctly (installed the drivers and stuff as it says on the ulefone download page) but i haven't flashed any mediatek devices in a long time and i would be very thankful if someone can tell me what i'm doing wrong. I don't mind it getting bricked as i know that is always a risk with mediatek, but i do need to be able to flash the stock rom.
Click to expand...
Click to collapse
hey, how did you set your IMEIs after bricking? I usually used Engineer Mode to set them, but thats not working since i am missing "CDS Information"
Unlucky25 said:
hey, how did you set your IMEIs after bricking? I usually used Engineer Mode to set them, but thats not working since i am missing "CDS Information"
Click to expand...
Click to collapse
Uh, i never even bothered to think about imei as it just worked without doing anything.
ml11ML said:
Uh, i never even bothered to think about imei as it just worked without doing anything.
Click to expand...
Click to collapse
ok nevermind, i found a solution..yeyy
so if anybody stumples across here, who has no IMEI set, CDS information in MTK mode and no rooted phone... u can set your IMEI in MTK engineering mode under "GPRS"!

I tried rooting RMX2040

Disclaimers:
> I am NOT encouraging anyone to do this. I'm not responsible for anything that happens to your device once you've rooted it already. I did this out of curiosity and I'm just sharing my experience.
> Also yeah, Rmx2040. Not Rmx2040EU.
> It's doable, but it is NOT stable. It boots but you can't use the phone normally. You know, like how you'd normally use a phone.
> I SOFTBRICKED MY PHONE.
Bugs:
UI Restarts every time you go landscape and go back to portrait
Can't open camera
UI Restarts every time you scroll on playstore or anywhere with lots of images
Phone lags, actually no, it restarts all the damn time
NOTES:
@Kraitos was looking for boot.img files so i decided to do a little digging too. I saw in a post somewhere that you need vbmeta.img and a patched (via magisk) boot.img from the device itself.
The "vbmeta.img" I used here was from a Realme 5. I figured all they 'kinda' looked the same plus I don't know if the file is also patched. I tried patching it in magisk but it didn't work, so I just grabbed a (patched?) vbmeta.img (from Realme 5 somewhere in the internet) and used that for our device which is, Rmx2040 (6i)
I grabbed the boot.img from the official ozip file in realme's site (From version A.27, I couldn't find any boot.img for A.31 because they haven't updated the link in the site yet). I opened it up, looked for it, grabbed it and patched it using magisk. Thankfully, it worked.
I used both the vbmeta.img (again, idk if it's patched) and the patched boot.img to root my device. I doubted it too, I thought it'll give me a bootloop or something, but it didn't.
If you want to do it, here are the steps:
Unlock your bootloader. Go here:
https://forum.xda-developers.com/realme-6i/how-to/unlocking-bootloader-realme-6i-rmx-2040-t4174255
Credits to @Kraitos for this awesome guide on how to unlock Rmx2040's bootloader.
If you're done unlocking your bootloader, download these files:
boot.img:
https://drive.google.com/file/d/1D7S9JGwDusyL6hJ6pWrFRBLo_9DdQLGR/view?usp=sharing
vbmeta.img:
https://drive.google.com/file/d/1Do2SfGI_Tp2jERcO77Vh1vEfjiQ6Xxe9/view?usp=sharing
Portable adb fastboot (if you don't have it yet):
https://drive.google.com/file/d/1m78UIsabMQlCvNIIv2e4xI19pN9b1otw/view?usp=sharing
Put all in one folder, it doesn't have to have a name.
Extract the zip file (minimal_adb_fastboot_1.4.3_portable.zip)
*Your folders should have the ff:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
boot.img
cmd-here.exe
Disclaimer.txt
fastboot.exe
vbmeta.img
Enable USB debugging in your phone.
Connect your phone to your pc.
Double click "cmd-here.exe"
Type the following in CMD:
adb reboot bootloader
If it displays a text in the middle, type "fastboot devices" on cmd. You SHOULD your phone's code there. If it doesn't display anything, replug the type C cable on your phone and type it again, do this until it shows.
Copy this and paste it in CMD:
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
Then press enter.
once it's done, copy this next:
fastboot flash boot boot.img
Then press enter.
Reboot your device by typing this in CMD:
fastboot reboot
If you've made it this far, you should install the latest Magisk Manager after you've unlocked the bootloader though. Or do it last, whatever you prefer works.
Viola, now you have an unstable phone.
I'm gonna try locking my bootloader later to flash the A.27 ozip later, I hope going back to "stock and unrooted" fixes the bugs I've experienced :|
I don't really know anything besides trying stuff out, I just wanted to see if it'll work properly with root. If anyone here noticed that I've done something wrong, please do tell me. I wanna try all the methods we can think of just so we can root this device.
Have a wonderful day y'all
Edit:
Everything went bad. I locked the bootloader because I needed access to stock recovery. It gave me a "red state"
I don't know how to fix this problem :|
Awesome guide and thanks for mention you know some people do that if you pay them to unlock bootloader and rooting device so this thread will be a savior to alot of people , I'll do testing in a couple of days asap i get a laptop relocking bootloader is mostly the same when you unlocked bootloader so it should be easy to flash stock again
Alright, so, quick update:
I tried to lock the bootloader while it had root (in my case, magisk). When I did, the phone went to "red state" (For those who don't know, it's basically bootloop wherein the phone never goes to recovery no matter what you do. Not even in stock).
Now, my phone is broken. It bootloops. I don't know what to do with this problem except going to a service center and have this fixed. Does anyone know how much it costs for reflashing stock rom to realme devices?
Sidenote: I tried the volume + down/up method to get into fastboot mode or stock recovery, but it never works. And honestly speaking, I don't think it will. To get into fastboot mode the bootloader needs to be unlocked, so that's crossed out AND I can't get into stock recovery because the phone restarts every 5 seconds because of that pesky "red state" thingy at the start.
Joesh.lucas said:
Alright, so, quick update:
I tried to lock the bootloader while it had root (in my case, magisk). When I did, the phone went to "red state" (For those who don't know, it's basically bootloop wherein the phone never goes to recovery no matter what you do. Not even in stock).
Now, my phone is broken. It bootloops. I don't know what to do with this problem except going to a service center and have this fixed. Does anyone know how much it costs for reflashing stock rom to realme devices?
Sidenote: I tried the volume + down/up method to get into fastboot mode or stock recovery, but it never works. And honestly speaking, I don't think it will. To get into fastboot mode the bootloader needs to be unlocked, so that's crossed out AND I can't get into stock recovery because the phone restarts every 5 seconds because of that pesky "red state" thingy at the start.
Click to expand...
Click to collapse
The problems you faced after rooting the phone is because you flashed an older version of boot.img thats why it wasn't working with latest rom and caused instability in system... And the second problem that you faced that red state thing..!! it was your fault you shouldn't relocked the bootloader with a patched boot img.. and if you wanted to boot the stock recovery you should have used the command " fastboot reboot recovery " this command in fastboot mode reboots the phone to recovery mode... Well i want to know what happend did your phone survived??
mehdi.shah said:
The problems you faced after rooting the phone is because you flashed an older version of boot.img thats why it wasn't working with latest rom and caused instability in system... And the second problem that you faced that red state thing..!! it was your fault you shouldn't relocked the bootloader with a patched boot img.. and if you wanted to boot the stock recovery you should have used the command " fastboot reboot recovery " this command in fastboot mode reboots the phone to recovery mode... Well i want to know what happend did your phone survived??
Click to expand...
Click to collapse
Thanks for the information, I now understand that I should use the same boot.img. It was worth the experiment tho, I just hoped I did it better so I wouldn't have to go through this process again.
My phone is here with me. It's still stuck on red state and I haven't went to a service center to have it fixed yet. I went to Hovatek to look for some ways to fix this problem. I tried using miracle box and the SP flashtool method but the latter had problems with the scatter file and the former didn't get past this:
Waiting for USB Port...
Set OPPO PreLoader USB VCOM (Android) (COM4)
>>Please Hold "ON" to connect with the phone...
I also looked a little bit more into it and I found out that I can use the OFP file and the flasher application here: https://firmwarex.net/realme-6i-rmx2040-official-firmware/
But unfortunately, I can't use the application because it's asking for an OPPO ID or something. Either I bring this phone to a service center or I'll just let it be this way until I decide to sell it somewhere. I hope I'll be able to fix this on my own tho, at least, someday.
Edit:
You can read more of my experience here:
Rmx2040 (realme 6i) scatter file
Hi guys, I'm trying to get the scatter file in this and so far I found this on the ozip file: preloader 0x0 pgpt 0x0 recovery_a 0x8000 misc 0x2008000 para 0x2088000 opporeserve1 0x2108000 opporeserve2
forum.hovatek.com
I'm subma rine13.
Joesh.lucas said:
Thanks for the information, I now understand that I should use the same boot.img. It was worth the experiment tho, I just hoped I did it better so I wouldn't have to go through this process again.
My phone is here with me. It's still stuck on red state and I haven't went to a service center to have it fixed yet. I went to Hovatek to look for some ways to fix this problem. I tried using miracle box and the SP flashtool method but the latter had problems with the scatter file and the former didn't get past this:
Waiting for USB Port...
Set OPPO PreLoader USB VCOM (Android) (COM4)
>>Please Hold "ON" to connect with the phone...
I also looked a little bit more into it and I found out that I can use the OFP file and the flasher application here: https://firmwarex.net/realme-6i-rmx2040-official-firmware/
But unfortunately, I can't use the application because it's asking for an OPPO ID or something. Either I bring this phone to a service center or I'll just let it be this way until I decide to sell it somewhere. I hope I'll be able to fix this on my own tho, at least, someday.
Edit:
You can read more of my experience here:
Rmx2040 (realme 6i) scatter file
Hi guys, I'm trying to get the scatter file in this and so far I found this on the ozip file: preloader 0x0 pgpt 0x0 recovery_a 0x8000 misc 0x2008000 para 0x2088000 opporeserve1 0x2108000 opporeserve2
forum.hovatek.com
I'm subma rine13.
Click to expand...
Click to collapse
Hey buddy i just rooted my realme 6i (RMX 2040) on build number A.37... everything went smooth and working flawlessly.... No system instabilities at all... Btw sorry to hear that your phone is still in brick state.. actually thing is oppo does not allow the users to flash stock rom on locked bl devices that why flasher tool asks for oppo authorized account in order to flash the device... And about SP flash tool.. it will not work either we have to wait for the patched rom that can be flashed on locked devices with sp flash tool
mehdi.shah said:
Hey buddy i just rooted my realme 6i (RMX 2040) on build number A.37... everything went smooth and working flawlessly.... No system instabilities at all... Btw sorry to hear that your phone is still in brick state.. actually thing is oppo does not allow the users to flash stock rom on locked bl devices that why flasher tool asks for oppo authorized account in order to flash the device... And about SP flash tool.. it will not work either we have to wait for the patched rom that can be flashed on locked devices with sp flash tool
Click to expand...
Click to collapse
Woah, is it true you've rooted it? How did you manage to pull it off? Is it similar to what I did except with different files?
Oh and yeah, I think I'll need to bring this to an authorized service center to have it fixed. In your currency, how much do you think it costs to flash the stock rom back to the phone? This has been a question that's been bothering me for months. I do hope it isn't pricey, because if it is then maybe I'll never have it fixed.
Joesh.lucas said:
Woah, is it true you've rooted it? How did you manage to pull it off? Is it similar to what I did except with different files?
Oh and yeah, I think I'll need to bring this to an authorized service center to have it fixed. In your currency, how much do you think it costs to flash the stock rom back to the phone? This has been a question that's been bothering me for months. I do hope it isn't pricey, because if it is then maybe I'll never have it fixed.
Click to expand...
Click to collapse
Yeah the procedure was the same as yours... I unlocked the bootloader i was on A27 build... And i downloaded the latest ozip file from the official site and i opened it up in file manager it asked if i want to update the software i clicked yes.. and it rebooted to stock recovery and started updating the device.. after successful update i opend up the ozip file by renaming it to .zip and extracted the boot.img and vbmeta.img. i patched the boot.img with latest magisk manager and tha than flashed those files in fastboot mode... With same commands that u used... And everything went well and its all good and rooted no problem at all..
And yeah the service center thing.. if its the software issue than the charge around 1.5 to 2k rupees in my country...which is around 9.34 to12.4 US dollars..
mehdi.shah said:
Yeah the procedure was the same as yours... I unlocked the bootloader i was on A27 build... And i downloaded the latest ozip file from the official site and i opened it up in file manager it asked if i want to update the software i clicked yes.. and it rebooted to stock recovery and started updating the device.. after successful update i opend up the ozip file by renaming it to .zip and extracted the boot.img and vbmeta.img. i patched the boot.img with latest magisk manager and tha than flashed those files in fastboot mode... With same commands that u used... And everything went well and its all good and rooted no problem at all..
And yeah the service center thing.. if its the software issue than the charge around 1.5 to 2k rupees in my country...which is around 9.34 to12.4 US dollars..
Click to expand...
Click to collapse
Does root work as it should?
Russian community guys reported that root exists in the system but not works at all. Rooting procedure looks the same.
sqzd0 said:
Does root work as it should?
Russian community guys reported that root exists in the system but not works at all. Rooting procedure looks the same.
Click to expand...
Click to collapse
Yeah it is working like it should work... I tried many things... Different magisk modules.. even changed boot animation with root file manager every thing works like charm..
mehdi.shah said:
Yeah it is working like it should work... I tried many things... Different magisk modules.. even changed boot animation with root file manager every thing works like charm..
Click to expand...
Click to collapse
I don't mean to be rude but, can you make a thread for that? Some rmx 2040 owners want to root their device and I think i just gave them a recipe for disaster.
Oh and by the way, thanks for answering my question. I have another one, will it be okay to update your device whilst rooted? If so then how do you stop the auto update?
(Sorry for the questions man hahahaha I wanted the same outcome but I failed miserably :| )
mehdi.shah said:
Yeah it is working like it should work... I tried many things... Different magisk modules.. even changed boot animation with root file manager every thing works like charm..
Click to expand...
Click to collapse
Bro give me boot.img a37
mehdi.shah said:
Yeah it is working like it should work... I tried many things... Different magisk modules.. even changed boot animation with root file manager every thing works like charm..
Click to expand...
Click to collapse
Give me boot.img of a37 version
mehdi.shah said:
Hey buddy i just rooted my realme 6i (RMX 2040) on build number A.37... everything went smooth and working flawlessly.... No system instabilities at all... Btw sorry to hear that your phone is still in brick state.. actually thing is oppo does not allow the users to flash stock rom on locked bl devices that why flasher tool asks for oppo authorized account in order to flash the device... And about SP flash tool.. it will not work either we have to wait for the patched rom that can be flashed on locked devices with sp flash tool
Click to expand...
Click to collapse
If you rooted dump the stock recovery and boot.img through terminal emulator I will try to port twrp
Boot.img and Vbmeta file can now be accessed by clicking the text above
Do is still need to relock my bootloader inorder to downgrade to A.27 update ? Thanks
mehdi.shah said:
Yeah it is working like it should work... I tried many things... Different magisk modules.. even changed boot animation with root file manager every thing works like charm..
Click to expand...
Click to collapse
Bro i tried the rooting process and i didnt check the boot and i rooted my phone the wifi,blueooth, camera, etc doesnt work anymore. If POSSIBLE can i revert it back to normal?
Can anyone provide me a twrp recovery file for realme 6i rmx2040 A.47 plsss

OP8 T-Mobile SMT download faild

I tried to restore my op8 tmobile 5g using t-mobile msm tool
its done flashing but then shows error screen on phone
SMT Download failed!
So i tried many versions of msm tool and all works but still cant boot
i can access to fastboot and recovery but bootloader is locked so cant do anything
Hi there. U did not flash properly. U need to do it again carefully. Don't interrupt. Wait until it reboot itself
Hardeep Kang said:
Hi there. U did not flash properly. U need to do it again carefully. Don't interrupt. Wait until it reboot itself
Click to expand...
Click to collapse
I did many and its download complete with green color in MSM tool and reboot by it self and many version i tried but no luck : (
Thank you
brsteej said:
I did many and its download complete with green color in MSM tool and reboot by it self and many version i tried but no luck : (
Thank you
Click to expand...
Click to collapse
There's only 3 possibilities.
1.) You're using the wrong MSM tool. This is the correct one for TMO device.
2.) You're device isn't a T-Mobile device. You're either mistaken, or were given incorrect information
3.) You need to troubleshoot the flashing itself. Try different USB ports, a different computer if you can. If MSM really finished the whole process and said complete with a green bar, than this is unlikely, and 1 or 2 is your answer.
brsteej said:
I tried to restore my op8 tmobile 5g using t-mobile msm tool
its done flashing but then shows error screen on phone
SMT Download failed!
So i tried many versions of msm tool and all works but still cant boot
i can access to fastboot and recovery but bootloader is locked so cant do anything
Click to expand...
Click to collapse
hello r u found solutions ? i have same problem my device oP7t :HD1900

Can a "Hard-bricked" android phone be restored if there's still access to Download mode?

I accidentally installed the wrong ROM on my phone, and now it's unresponsive (nothing happens when I try to turn it on, not even a vibration)
But I managed to access Download Mode (aka EDL, right?).
Can I restore it if I have the Scatter file and the Stock ROM?
Thanks in advance
MediaTek devices have preloader mode, EDL mode is for Qualcomm
Not sure what device you're talking about, but try to look for an "unbrick tool" or an "unbrick guide"
I "semi hard-bricked" my OnePlus 3T a while ago, and there was this leaked Qualcomm tool that you could use to flash the factory ROM the phone came with from Download Mode.
aIecxs said:
MediaTek devices have preloader mode, EDL mode is for Qualcomm
Click to expand...
Click to collapse
Does the fact that I can communicate and flash via Download Mode (SP Flash Tool) mean that I didn't lose my preloader? I'm kinda stuck trying to flash the Stock ROM (demanding verified image files, even though I'm using the original firmware for flashing... probably)
Lada333 said:
Not sure what device you're talking about, but try to look for an "unbrick tool" or an "unbrick guide"
I "semi hard-bricked" my OnePlus 3T a while ago, and there was this leaked Qualcomm tool that you could use to flash the factory ROM the phone came with from Download Mode.
Click to expand...
Click to collapse
I'll check the guides online, hopefully I'll find one that'll help.
mouradsme said:
demanding verified image files, even though I'm using the original firmware for flashing
Click to expand...
Click to collapse
I've also had issues previously with trying to flash stock images on Samsung phones. Not sure if you have country-specific images, if you do, try giving all of them a shot. I'm from Hungary, and a locally bought Samsung phone only came to life after flashing a Spanish factory image.
you need to (by)pass SLA/DAA authentication
Now I managed to bypass protection, and got the successful flash message from SP Flash Tool.
But I still can't solve the issue (Phone still only responsive from BROM)
For reference I'm using the global version of RMX3171 (Realme Narzo 30A) based on MT6768, and the Stock ROM is available online.
I flashed every partition (Provided in the Stock ROM), and Now it is booting, showing the logo + a message "Download not completed Error Code 0x992566 " and then it reboots after a minute or so -_-
I think that means you did not flash all partitions (some not included in Download)
In the other thread someone mentioned "Format All + Download" very bad idea never do this.
did you try unlocking bootloader from mtkclient like suggested in that thread?
mouradsme said:
Hello,
Can someone share their nvdata & nvram + oppo_custom?
I seem to have formatted mine, and need them to recover my Narzo 30A.
Click to expand...
Click to collapse
https://androidmtk.com/use-sn-write-tool
https://www.hovatek.com/forum/thread-116.html
aIecxs said:
https://androidmtk.com/use-sn-write-tool
https://www.hovatek.com/forum/thread-116.html
Click to expand...
Click to collapse
I came across the tool, but I failed to enter into Meta Mode.
I'm trying to make my phone boot to the system, then I'll try restoring my IMEI's using MTK Engineering app.
Thanks for links though
mouradsme said:
I accidentally installed the wrong ROM on my phone, and now it's unresponsive (nothing happens when I try to turn it on, not even a vibration)
But I managed to access Download Mode (aka EDL, right?).
Can I restore it if I have the Scatter file and the Stock ROM?
Thanks in advance
Click to expand...
Click to collapse
There is no such thing as a "hard bricked" device that can still boot into TWRP. A hard bricked device is completely dead and shows no kind of activity or function. It won't charge, it won't boot into any kind of mode and can't make a connection to PC, makes no sound when connecting to PC and it won't appear in device manager when connected to PC.
A device that can boot into download mode but not its other modes is just a softbricked device.

Question How to unbrick One Plus Nord CE 2 Lite ?

I have bricked this device (One Plus Nord CE 2 Lite) by flashing the unofficial twrp image for this device. Device bootloops in TWRP.
Previously, I had succesfully unlocked the bootloader and rooted this device by flashing the patched magisk boot.img by following the method mentioned in this post (https://forum.xda-developers.com/t/rooting-oneplus-nord-2-ce-lite.4500297/)
How to restore the factory image and recover from this?
Any help is appreciated.
Thanks
...reboot to fastboot, flash the original boot and vbmeta and you're done ...maybe you have to change back the slot, but it's almost impossible to brick the device
...don't mess around with "Recovery" ...this device has already the newest partitioning system and there is no recovery partition
best regards
I messed up by flashing the wrong twrp image made. (Device was stuck on 1+ logo screen)
Thanks to your post i was able to rescue this device.
I used Oxygen Updater App, payload-dumper-gui and minimal adb fastboot.
Flashed boot and vbmeta with stock img files.
Restarting the device now will boot into fastboot mode.
Changing slots helped a lot.
(fastboot set-active=a/b)
After that, Device booted normally into OS.
... you're very welcome, Sir ...but really, don't mess around with "old school" recovery systems ...they are not needed anymore and furthermore they can't handle the "dynamic super partitioning" ...and again: nobody needs them after the year 2015 anymore
...best regards
NickR01 said:
I messed up by flashing the wrong twrp image made. (Device was stuck on 1+ logo screen)
Thanks to your post i was able to rescue this device.
I used Oxygen Updater App, payload-dumper-gui and minimal adb fastboot.
Flashed boot and vbmeta with stock img files.
Restarting the device now will boot into fastboot mode.
Changing slots helped a lot.
(fastboot set-active=a/b)
After that, Device booted normally into OS.
Click to expand...
Click to collapse
Hey can you help me pls, I am in the exact same situation as you but I can't get the stock img files, whenever I use payload-dumper it just gives me system.img and nothing else, could you maybe share your img files ?
Edit: I manged to get some files but still not the boot.img, I don't undestand why it just refuses to give them to me, I redownloaded everything at least 3 times...
Use Payload-Dumper-GUI instead of Payload-Dumper-Go
Hey @NickR01 if possible can you send me an boot.img and vbmeta
I don’t have windows pc so can’t use Payload-Dumper
It will also help future users to unbrick device.
NickR01 said:
Use Payload-Dumper-GUI instead of Payload-Dumper-Go
Click to expand...
Click to collapse
@vikas_anakin What's your device version?
cph2381 cph2409
NickR01 said:
@vikas_anakin What's your device version?
cph2381 cph2409
Click to expand...
Click to collapse
cph2381
@vikas_anakin I have files for eu variant, can't help you there bud. If flashed it can mess up your device.
If you are stuck with payload.bin extraction... try it with an android device.
Here's the tool for Android.
Payload-Dumper-Android
Here's the guide for it.
XDA Guide
Newb Guide
Follow the guide and download this app to extract the .bin file
Termux App: Termux Github
After the extraction, type fastboot (pc required) commands to flash and change current active slots from A to B if it's stuck in bootloop after flashing.
I hope this helps you recover your device.
NickR01 said:
@vikas_anakin I have files for eu variant, can't help you there bud. If flashed it can mess up your device.
If you are stuck with payload.bin extraction... try it with an android device.
Here's the tool for Android.
Payload-Dumper-Android
Here's the guide for it.
XDA Guide
Newb Guide
Follow the guide and download this app to extract the .bin file
Termux App: Termux Github
After the extraction, type fastboot (pc required) commands to flash and change current active slots from A to B if it's stuck in bootloop after flashing.
I hope this helps you recover your device.
Click to expand...
Click to collapse
Extracting the payload.bin is not an issue, The issue is I don't have stock firmware.
I used https://www.getdroidtips.com/oneplus-nord-ce-2-lite-5g-firmware-flash-file/ but my wifi and Bluetooth are not working after installing it.
Do you have any suggestions on how can i resolve these issues?
@vikas_anakin Download authentic firmware from this app. Files are pulled from OnePlus servers.
Google Playstore: Oxygen Updater
Oxygen Updater Settings -> Enable Advanced Mode
Select device region.
Latest update for holi is CPH2381_11_A.13 as of now.
I extracted the images from the payload.bin found in the Oxygen Updater file (that I had actually successfully used to update my device) and flashed 2 partitions:
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
I then rebooted and now it's stuck in a boot loop & I can't even access fastboot anymore. Can someone please help?
Thanks
EDIT:
I managed to access fastboot & flash the rest of the partitions to fix it.
Hi everyone, just to piggy back on this thread, I also have the same device, and I have unofficial twrp and boot loader unlocked, however I have no back up rom and just want to get the phone back to normal really. Ive been following guides all over the place, but could someone point me in the right direction ? can I just download a rom for the OP nord ce 2 lite 5g, put it on my phone and have twrp install it? could someone guide me please. many thanks!
lemonmuffs said:
Hi everyone, just to piggy back on this thread, I also have the same device, and I have unofficial twrp and boot loader unlocked, however I have no back up rom and just want to get the phone back to normal really. Ive been following guides all over the place, but could someone point me in the right direction ? can I just download a rom for the OP nord ce 2 lite 5g, put it on my phone and have twrp install it? could someone guide me please. many thanks!
Click to expand...
Click to collapse
Yes, that will work.
vikas_anakin said:
Yes, that will work.
Click to expand...
Click to collapse
Or else you can extract img files from the oneplus rom file.
and flash them using fastboot.
Okay thank you for the reply, would you be able to point me to a official img file ? Or maybe someone has one extracted I could use please? I have looked online, but the ones I have gotten don't seem to work. I have also looked on the oneplus website for an official img but I could not find one.
So after a little more research, I can use another android device with the app Oxygen updater, download the full img.... So I am currently doing that and then ill try use fastboot or twrp to flash. Just wanted to spread info incase anyone else is having issues getting latest official roms for this device.
Hey guys, i have bricked my Oneplus Nord ce 2 lite 5g (Cph2381)
I tried using the fastboot enhance tool to flash a payload.bin file i thought was the right one for the device ..the device went to blackscreen..ive tried switching it on but its not working..ive done alittle research and found out that i should use an msm tool to force flash the initial stock firmware so that it can boot up ...problem is i cant seem to find the right msm tool for Oneplus nord ce 2 lite 5g , which msm tool can i use ? help please
Jazzyjuis said:
Hey guys, i have bricked my Oneplus Nord ce 2 lite 5g (Cph2381)
I tried using the fastboot enhance tool to flash a payload.bin file i thought was the right one for the device ..the device went to blackscreen..ive tried switching it on but its not working..ive done alittle research and found out that i should use an msm tool to force flash the initial stock firmware so that it can boot up ...problem is i cant seem to find the right msm tool for Oneplus nord ce 2 lite 5g , which msm tool can i use ? help please
Click to expand...
Click to collapse
Hey man, I would suggest not going with msm tool or anything.
Just download the latest update file of your device using oneplus updater app, or you can ask for the file if some of your friends has the same device.
use this tool to extract payload files https://github.com/vm03/payload_dumper
Now you can follow the same procedure as here https://forum.xda-developers.com/t/...ock-oxygenos-firmware-on-oneplus-10r.4465077/

Categories

Resources