So I got really desperate right after I unlocked my poco X2 bootloader, started flashing beta and and all sorts of xiaomi eu k30 and poco builds. And now no matter what stable or any build or rom I go to, my front and rear primary cameras doesn't work. And there's a black screen. And it also shows " can't connect to camera" and basically camera UI is frozen.
I can access wide and Macro on gcam. But the rest don't work. And until 2 days ago, the front camera worked. But now, that too isn't working, and somehow the "wide angle" shifted to 2x camera in gcam, whereas before it would be at 0.6x. and 1x would freeze, but now 1x is macro in gcam.
I want to edl or QFIL flash, but those are limited to factory folk or unless I can find a cracked elf file I'm pretty stuck. I tried all sorts of unbricking methods, reflashed persist from mi fastboot file, reflashed mi fastboot roms all the way from 11.0 till 12.1.3 all stable builds. Nothing has worked. Im sure that it's the partition fault, bc this happened randomly without any physical occurences that can cause damage or effect the camera to go bad. I don't game much either.
I've also done CIT and tried calibrating, just crashed and not able to capture. It says "error : cameralist not match
Hope these details help. Please provide with any tip or any input, I'll take anything at this point.
And I've run out of warranty, or else I'd go to mi service directly. Is there something I can change in the build prop or root files?
I think u messed up your persist partition ... Flash latest fastboot rom using miflash.... Recover persist partition using this link
[Guide] About repairing/fixing the persist partition
Disclaimer: I am not responsible for the results of any of these operations. Everyone knows that the persist partition is responsible for sonsors and carrier network etc. Once this partition is failed or lost, your phone will go wrong. I just...
forum.xda-developers.com
. If it doesnt work dont waste time .... Lock your bootloader and take it to service centre
saginesht said:
I think u messed up your persist partition ... Flash latest fastboot rom using miflash.... Recover persist partition using this link
[Guide] About repairing/fixing the persist partition
Disclaimer: I am not responsible for the results of any of these operations. Everyone knows that the persist partition is responsible for sonsors and carrier network etc. Once this partition is failed or lost, your phone will go wrong. I just...
forum.xda-developers.com
. If it doesnt work dont waste time .... Lock your bootloader and take it to service centre
Click to expand...
Click to collapse
Throws an error 7, Doesn't support phoenix device only for gingko devices.
I did try flashing persist img from latest fastboot rom to persist slot.
bythelaw said:
Throws an error 7, Doesn't support phoenix device only for gingko devices.
I did try flashing persist img from latest fastboot rom to persist slot.
Click to expand...
Click to collapse
Dont flash the zip its for note8.... Follow the guide using adb
{
"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"
}
Our persist is /dev/block/sdf7
Persistbak is /dev/block/sdf8
In terminal run this commands
su
dd if=/dev/block/sdf8 of=/dev/block/sdf7
Another method is u can dump your persistbak using this command
dd if=/dev/block/sdf8 of=/sdcard/persist.img
Then flash the persist.img via recovery or fastboot
Thank you, i will try both and report back.
saginesht said:
Another method is u can dump your persistbak using this command
dd if=/dev/block/sdf8 of=/sdcard/persist.img
Then flash the persist.img via recovery or fastboot
Click to expand...
Click to collapse
Did both successfully. neither worked. im sure this is because of flashing beta eu roms i.e k30 roms. i think it made changes to many other system files.
will locking bootloader and taking it to the mi vendor mean that they will edl or qfil flash and check? so if theres an issue with the software, would it be fixed with qfil/edl flash?
the urge to fastboot eraze all and flashing mi firmware freshly is high, but im sure that'll cause more problems and might not even work.
bythelaw said:
Did both successfully. neither worked. im sure this is because of flashing beta eu roms i.e k30 roms. i think it made changes to many other system files.
will locking bootloader and taking it to the mi vendor mean that they will edl or qfil flash and check? so if theres an issue with the software, would it be fixed with qfil/edl flash?
the urge to fastboot eraze all and flashing mi firmware freshly is high, but im sure that'll cause more problems and might not even work.
Click to expand...
Click to collapse
Try fastboot erase all once
That will properly brick my phone. Thank anyways tho. If you have a modified elf file or anyone does, please share
saginesht said:
Try fastboot erase all once
Click to expand...
Click to collapse
Hey i figured out the issue, apparently its because i was flashing the lastest beta xaiomi eu firmware roms, and i flashed it again yesterday, now my touch screen and sd card doesnt work both are dead now. flashing fastboot rom didnt change this. im 100% sure its the xaiomi eu beta rom that did this. please help fix this.
Related
So I just revived my brother's dead S4 clone earlier today, and until now I am still flummoxed by how I did it.
It was an S4 from a company called Shengda, running JB 4.2.2 over a 3.4.5 kernel and a baseband that calls itself 'MOLY.WR8.W1315.MD.WG.MP.V1.P8, 2013/07/12 16:41'.
The phone started bootlooping when I changed the Dalvik heap size from 128m to 64m, which seemed to upset the VM as early-boot logs indicate it complaining about a bad heap size.
So naturally I tried to push a fixed build.prop thru ADB, but then I remembered I hadn't approved ADB su requests on the phone before.
I then tried reflashing Android (yes, I was sane enough to take a backup before, thank God) using multiple versions of SP Flash Tool to no avail. It would just slap me with errors, which I can't find fixes for from Googling.
Then I tried recovery, but to nobody's surprise, the phone was using 3e. So no dice on third-party ROMs.
Convinced it was a hopeless case, I decided to just play around with it since I thought there wasn't anything else to lose.
I used ADB to reboot into the bootloader, expecting it to just do a normal boot. @bgcngm himself said this:
{
"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"
}
So you could imagine my surprise when I saw the words "fastboot mode" at the bottom of the screen. I was like, "Impossible!" But there it was, staring at me amidst a black screen.
With euphoria washing over me, I tried "fastboot flash system system.img" with the prepared image I was gonna use for SPFT. Believe it or not, it worked - everything was intact when I rebooted, except for the loss of root. (Still a piece of cake to root.)
So now my question is, who else has seen Fastboot on their MTK device?
Would appreciate it if anyone else chimed in. :thumbsup:
Sent from my GT-I8730 using Tapatalk
Reserved.
Btw the phone was MT6572, pretending to be a 6589
Sent from my GT-I8730 using Tapatalk
How to use your method on MT6572 S4 clone device if device cannot open, dont go in cwm and only see usb mtk/preloader etc.?
I have used the fastboot directly to install cwm recovery and boot.img in 6589 Micromax A210
I have ported that in one of my custom Rom port
Sent from my Spice Mi-535
uboc said:
How to use your method on MT6572 S4 clone device if device cannot open, dont go in cwm and only see usb mtk/preloader etc.?
Click to expand...
Click to collapse
If your device doesn't actually turn on, then I would say that your only hope is to use SP Flash Tool.
fastboot is on Elephone P7000 (MTK MT6752 8-core)
My Elephone P7000 definitely has fastboot, but not all of the commands that I have on my Nexus 5. For example fastboot boot recovery recovery.img doesn't work. fastboot devices, flash, etc commands work but I could not load a temporary (ram only) custom recovery from fastboot, like I can on the Nexus 5.Rather a pity, really ... all that 3gb ram and can't use it from fastboot in this instance.
Anyone have any clues whether an update / cutomization is available for the MTK fastboot?
trevh said:
My Elephone P7000 definitely has fastboot, but not all of the commands that I have on my Nexus 5. For example fastboot boot recovery recovery.img doesn't work. fastboot devices, flash, etc commands work but I could not load a temporary (ram only) custom recovery from fastboot, like I can on the Nexus 5.Rather a pity, really ... all that 3gb ram and can't use it from fastboot in this instance.
Anyone have any clues whether an update / cutomization is available for the MTK fastboot?
Click to expand...
Click to collapse
Not sure about this, as my MTK device boots from RAM just fine. Maybe you have to unlock bootloader first? I don't know if that will brick your phone, so I don't recommend you do it.
I have issue with fastboot which get hangs on erasing. Can't it work with mediatek 6572 ?
C:\Users\ransh>fastboot devices
0123456789ABCDEF fastboot
C:\Users\ransh>fastboot flash system system.img
target didn't report max-download-size
erasing 'system'...
And now nothing. It hangs...
Is it the same issue as you've mentioned here ?
Thanks, Ran
Hell yeah...i have fastboot on my mt6582 device! I entered fastboot today while playing around with the vol & power keys.
It Enters Fastboot mode!!! Fastboot On an MTK!!!!!!!!!!!:laugh:
This is quite a bump, but both my MTK devices have fastboot - I have a Lenovo Tab 3 7" Essential (aka TB3-710F) and a ZTE Blade V6 (aka T660). Both have fastboot, but I can't use "fastboot boot" on my ZTE. I haven't tried on my Lenovo.
lenovos650
hi, can you please help me how to conenect mtk6582 in fastboot mode . i want to install a custom recovery using fastboot mode
in my lenovo s650 plz help me ......
Akhil99 said:
Hell yeah...i have fastboot on my mt6582 device! I entered fastboot today while playing around with the vol & power keys.
It Enters Fastboot mode!!! Fastboot On an MTK!!!!!!!!!!!:laugh:
Click to expand...
Click to collapse
how did you do it? I just can't!
AgustinH said:
how did you do it? I just can't!
Click to expand...
Click to collapse
plug in USB charging cable simultaneously pressing power & vol.down keys.
ranchu-panchu said:
I have issue with fastboot which get hangs on erasing. Can't it work with mediatek 6572 ?
C:\Users\ransh>fastboot devices
0123456789ABCDEF fastboot
C:\Users\ransh>fastboot flash system system.img
target didn't report max-download-size
erasing 'system'...
And now nothing. It hangs...
Is it the same issue as you've mentioned here ?
Thanks, Ran
Click to expand...
Click to collapse
Hey mate i know its an old post but i noticed your devices serial number was 0123456789ABCDEF is your device an R11 max MT6572_NAND by any chance is it ?
If so do you have a security backup at all for it as all R11 Use the same imei 3582089****6228 and serial 0123456789ABCDEF ive lost my radios :crying: imei is still there and is listed as working but not appearing and no sim card showing also deleted the only working backup i had that worked all the previous times,
Ive built a super smooth and really nice rom for it but all i need now is the security backup as ive got no radios in it and its done
sorry if not lol
Who ever you are, i don't care how old this thread is, I LOVE YOU. I've been trying to do this for literally ONE YEAR. THANK YOUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
tegnkush said:
Who ever you are, i don't care how old this thread is, I LOVE YOU. I've been trying to do this for literally ONE YEAR. THANK YOUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
Click to expand...
Click to collapse
Thanks very much OP for this thread, I have a Vertu Aster P clone, which has an MT6755 chip. Booted into fastboot perfectly! Thank you!
Chris
is it possible to relock bootloader while using custom rom and recovery installed ?
i am asking this because it will make phone more secure while running it on custom recovery as all of us know how to remove screen lock with use of custom recovery
put password on recovery so no one can open it and if we relock bootloader then no one can reflash recovery in it and then there will less chance that our data may get out from phone or can be used if it get stolen or lost.
I am also trying to get rid of the annoying bootloader prompt that says the security of the device might have been compromised....
Please explain how...
Yes i have already flashed the device.
No. Just no.
If you want to brick your phone, just do it.
No, unlocking the bootloader is what allows you to run a custom ROM, that's why the phone is okay with it being custom. You can't just delete a password if you have an encrypted data partition.
Locked bootloaders only accept roms from vendor by certificate.
So If you lock is you will brick your device.
Not sure if hardbrick tools will work...?
This does kind of exist for the OnePlus 5T; see here. It is quite complex, but once you have root under a locked bootloader you can reflash everything (with SIGNED recoveries and boot images). If you fail to sign everything correctly your phone will become more bricked than usual, with no possibility of reflashing except using the MSM Download Tool.
However, before you get any ideas, hold on. The OnePlus 7 is not only an A/B device, but a system-as-root device, neither of which the 5T is. There is no recovery partition that you can easily overwrite. I believe it's still possible to get a twrp-installer zip to do your bidding, if you're able to get Magisk correctly with a locked bootloader. And before you ask, I don't know if it's possible to sign the boot.img with Magisk/TWRP already installed.
This is all pure speculation on my part and I've yet to try any of this with my 7 Pro. I know that no matter what happens, I can always use MSM Download Tool to restore my phone to working software. Then I'll have to start over, installing Magisk and then TWRP to restore my backup. I'm waiting for more input on this from people who know what they are doing, before attempting anything myself.
This was possible on the Redmi Note 3 pro. Someone created a mod where you could flash recovery directly using the MiFlash tool (Xiaomi's equivalent of MSTOOL). This was great because I had a locked bootloader and used orange fox recovery to lock the recovery... A theoretically fully secure rooted device
The anwser is no. You can try it like I did but it will tell you you have to format the device. I just learned the button combo. Thats what my problem was. Everytime I wanted to restart my phone I would always forget to shutdown completly because you have to do the button combo to enter rooted state. I just got used to it.
Edit: but I did manage to stop upgrade to the ugly Andriod 11 and managed to get my gear sport to work on my rooted rom. Thats all I wanted was Call recorder and for my watch to work.
So far no,I have been working on it and rebuilt a ops file with patched boot.and get this new error lol. If any one knows what I should try let me know. I am able to fully unpack and repack the ops files and flash.have been able to disable quite a few checks in the flashing with MSM tool.
{
"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 was attempting to root my OnePlus 7 so that I could increase the volume limits (I'm hearing impaired) via TWRP and then eventually Magisk, however it seems many things went wrong along the way. I managed to get TWRP working on my phone but then it wasn't finding any of my stored memory and therefore the TWRP Zip file I needed to finally root the phone. In my efforts to correct that I have bricked my phone (not sure if it's hard bricked or soft bricked) but currently it will only boot into the fastboot menu and selecting any option brings me right back to the fastboot menu again.
I tried getting back to the TWRP but no luck when I try to boot it I get the error message FAILED (remote: Failed to load/authenticate boot image: Load Error)
{
"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 reading online for a bit of help I thought it might be hard bricked so I tried to use the MSM tool but again I had no luck due to Param Preload - Device not match image
I have attached screenshots for both issues, I've also tried guides for soft bricked OP7P and despite showing as successful they reboot right back into the fastboot menu as if nothing has happened.
Please I'd really appreciate some help I've been trying for days to fix this mess!
Darhk Citadel said:
I was attempting to root my OnePlus 7 so that I could increase the volume limits (I'm hearing impaired) via TWRP and then eventually Magisk, however it seems many things went wrong along the way. I managed to get TWRP working on my phone but then it wasn't finding any of my stored memory and therefore the TWRP Zip file I needed to finally root the phone. In my efforts to correct that I have bricked my phone (not sure if it's hard bricked or soft bricked) but currently it will only boot into the fastboot menu and selecting any option brings me right back to the fastboot menu again.
I tried getting back to the TWRP but no luck when I try to boot it I get the error message FAILED (remote: Failed to load/authenticate boot image: Load Error)
After reading online for a bit of help I thought it might be hard bricked so I tried to use the MSM tool but again I had no luck due to Param Preload - Device not match image
I have attached screenshots for both issues, I've also tried guides for soft bricked OP7P and despite showing as successful they reboot right back into the fastboot menu as if nothing has happened.
Please I'd really appreciate some help I've been trying for days to fix this mess!
Click to expand...
Click to collapse
How did you unlock the boot loader?
tech_head said:
How did you unlock the boot loader?
Click to expand...
Click to collapse
I enabled USB Debugging on my phone and then used "Shift + Right Click" from within the folder with twrp file and used the command "fastboot oem unlock"
Was in this situation. If you have an unlocked bootloader, try to search for the fastboot ROMs on xda. Not sure if there is a 5g version though. With a try. Best of luck.
Darhk Citadel said:
I enabled USB Debugging on my phone and then used "Shift + Right Click" from within the folder with twrp file and used the command "fastboot oem unlock"
Click to expand...
Click to collapse
Look here https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
toonstra said:
Look here https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Click to expand...
Click to collapse
Thanks, I tried that this morning perhaps I did it wrong, but when I used the same cmd window as I did to "unlock" the bootloader nothing happened. It went through the process and finally finished with no errors and said "press any key to exit" -But as for my phone it did not reboot in fact there was no change at all, it remained on the bootloader screen as normal. When I tried to reboot for a normal load it looped back to the bootloader, when I tried to reboot to recovery it booted back to recovery. It was as if the fastboot ROM was completely ineffective.
Darhk Citadel said:
Thanks, I tried that this morning perhaps I did it wrong, but when I used the same cmd window as I did to "unlock" the bootloader nothing happened. It went through the process and finally finished with no errors and said "press any key to exit" -But as for my phone it did not reboot in fact there was no change at all, it remained on the bootloader screen as normal. When I tried to reboot for a normal load it looped back to the bootloader, when I tried to reboot to recovery it booted back to recovery. It was as if the fastboot ROM was completely ineffective.
Click to expand...
Click to collapse
So I just tried to flash a recovery.img and I got this error "failed (remote (recovery_a) no such partition)" which leads me to believe that my phone is a lot worse than I originally thought...
Any help would be greatly appreciated I fully accept that I messed this up BIG TIME!
Darhk Citadel said:
So I just tried to flash a recovery.img and I got this error "failed (remote (recovery_a) no such partition)" which leads me to believe that my phone is a lot worse than I originally thought...
Any help would be greatly appreciated I fully accept that I messed this up BIG TIME!
Click to expand...
Click to collapse
Ok so I finally managed to get to the root of the problem and my phone is now back up and running without any issues, I completely missed the correct MSM too package that I needed for my phone and region as I have a UK OnePlus Pro 7 5G I needed to use this specific package to reset my phone back to stock: [OP7PRO 5G EU][OOS 9.5.11 GM27BA]
Appreciate all the help everyone hopefully someone else can use this to avoid making the same mistake I did!
[SOLVED] Please read through, hopefully this helps someone!
Ive tried numerous threads and followed the steps always end up with some sort of error.
Device manager shows:
Kedacom USB Device>Android Bootloader Interface
errors:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
fastboot: error: Could not check if partition xbl has slot all
fastboot: error: Could not check if partition xbl_config has slot all
and continues with this error for what ever its trying to flash "has slot all"
flashing logical patitions error:
no such partition or partition not found
I keep researching and every video that shows what to do or posts, i can only get so far before my results dont match and there is no option or description for what to do if getting an error.
edit: adb devices shows nothing, but fastboot devices shows serial.
TIA
I think you have the wrong drivers, try these and check in windows update if your Qualcomm drivers are up to date in the optional updates. Also if fastboot is working and the bootloader is unlocked, you can download the latest full oos 12 and flash it all.
LaviLev said:
Ive tried numerous threads and followed the steps always end up with some sort of error.
Device manager shows:
Kedacom USB Device>Android Bootloader Interface
errors:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
fastboot: error: Could not check if partition xbl has slot all
fastboot: error: Could not check if partition xbl_config has slot all
and continues with this error for what ever its trying to flash "has slot all"
flashing logical patitions error:
no such partition or partition not found
I keep researching and every video that shows what to do or posts, i can only get so far before my results dont match and there is no option or description for what to do if getting an error.
edit: adb devices shows nothing, but fastboot devices shows serial.
TIA
Click to expand...
Click to collapse
If you need the latest oos I can link it here.
Nimiskiv said:
If you need the latest oos I can link it here.
Click to expand...
Click to collapse
Please do! currently DLing the drivers posted Thank you!
https://android.googleapis.com/packages/ota-api/package/435fc808f603bbc8a63ce30fd944676a65a61d6f.zip
LaviLev said:
Please do! currently DLing the drivers posted Thank you!
Click to expand...
Click to collapse
Oh but be careful that's for kebab 2005
Here's the repo
[OnePlus 8T][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
Added 11.0.5.6 KB05AA full zip from support website to OP
forum.xda-developers.com
Nimiskiv said:
Oh but be careful that's for kebab 2005
Here's the repo
[OnePlus 8T][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
Added 11.0.5.6 KB05AA full zip from support website to OP
forum.xda-developers.com
Click to expand...
Click to collapse
Anything with "kebab" in the beginning is OOS 12
Nimiskiv said:
https://android.googleapis.com/packages/ota-api/package/435fc808f603bbc8a63ce30fd944676a65a61d6f.zip
Click to expand...
Click to collapse
ok ty, looks like is c11 the first android 12 update for the OP8T, downloading now. Hopefully i can get it to flash.
LaviLev said:
ok ty, looks like is c11 the first android 12 update for the OP8T, downloading now. Hopefully i can get it to flash.
Click to expand...
Click to collapse
Use the MSM tool first
Nimiskiv said:
Use the MSM tool first
Click to expand...
Click to collapse
can not get phone to edl stuck in fastboot only. tried all the commands and physical button configs and still only get fastboot. Any workarounds?
I downloaded Fastboot Enhance, which allowed me to flash a bin file, but the phone still wont boot. I had to check ignore unknown partitions for it to flash. Now i can access fastbootd and when choose boot to recovery it loads what looks to a limited recovery similiar to fastbootd.
Any advice?
{
"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"
}
LaviLev said:
I downloaded Fastboot Enhance, which allowed me to flash a bin file, but the phone still wont boot. I had to check ignore unknown partitions for it to flash. Now i can access fastbootd and when choose boot to recovery it loads what looks to a limited recovery similiar to fastbootd.
Any advice?
View attachment 5683905
Click to expand...
Click to collapse
That's a stock OOS recovery you're seeing.
BillGoss said:
That's a stock OOS recovery you're seeing.
Click to expand...
Click to collapse
Any advice or known methods to get me running from here?
LaviLev said:
Any advice or known methods to get me running from here?
Click to expand...
Click to collapse
Run the MSM tool in edl, since now it should work fine. Also did the drivers work? If not you need to uninstall them in windows device manager, then reinstall them
LaviLev said:
Any advice or known methods to get me running from here?
Click to expand...
Click to collapse
Well, you've never said in your initial post what it was that you were trying to do.
Now that you are in the stock recovery you can select Advanced> reboot fastboot.
This will put you into fastbootd mode where you can do things like flash partitions and, more importantly, flash the logical partitions.
But, if you don't know how to do this and get out of whatever mess you're in , then use MSM Tool to reset your phone.
BillGoss said:
Well, you've never said in your initial post what it was that you were trying to do.
Now that you are in the stock recovery you can select Advanced> reboot fastboot.
This will put you into fastbootd mode where you can do things like flash partitions and, more importantly, flash the logical partitions.
But, if you don't know how to do this and get out of whatever mess you're in , then use MSM Tool to reset your phone.
Click to expand...
Click to collapse
I just reread my initial post, damn I started typing mid thought.. my bad!
I tried msmtool, but it doesn't load up a com port. All the listed methods with holding both vol buttons after already hitting start then plugging in did not work as I don't think it sees it at all.
Haven't found a thread with fastboot instructions that didn't require something I couldn't get to, to restore the phone. other methods fail writing to numerous areas when flashing.
trying this...
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
LaviLev said:
trying this...
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
Click to expand...
Click to collapse
OK was able to execute the first 4 fastboot commands, the it hung on the first flash --slot=all
In the end i just boot the phone in fasbootd using fastboot enhance and then using the flash bin file option in FE to flash the OOS 12 FILE @Nimiskiv shared.
Final boots into OOS, hope all works I will be testing to see for a day or two before i switch back from the 6, also before all this the 8T went a12_c11 to a12_c33
right now update for c20 came up!?
Any additional insight or final thoughts appreciated. Thanks again all!
LaviLev said:
OK was able to execute the first 4 fastboot commands, the it hung on the first flash --slot=all
In the end i just boot the phone in fasbootd using fastboot enhance and then using the flash bin file option in FE to flash the OOS 12 FILE @Nimiskiv shared.
Final boots into OOS, hope all works I will be testing to see for a day or two before i switch back from the 6, also before all this the 8T went a12_c11 to a12_c33
right now update for c20 came up!?
Any additional insight or final thoughts appreciated. Thanks again all!
Click to expand...
Click to collapse
check if EDL is working now, its very important for edl to work, because if something happens in the future, you need edl to reset.
i tried to install twrp , root and degoogle my galaxy a12, i have no experience at all and nearly bricked my phone
i unlocked my bootloader, go into download mode, i tried flashing twrp 3.7.0 image i downloaded on the official website, it didn't work and everytime i reboot it got into download mode again
i flashed the stock rom again, go to the support thread of twrp on the galaxy 12 here, i did like the tutorial but i cannot flash the rom with the re partition and nand erase because odin will just froze and the progress bar wont appear
after that i tried flashing it like the post said. put the twrp image in the AP box, and the vbmeta.img.md5(i extracted the vbmeta.zip file since i cannot put the zip file into the box) into userdata box, then start, restarted the phone and after that it got the "An ERROR Has Occured While Updating Device Software" with the teal background, i freaked out but luckily i fixed it with the frp hijack software.
after that i'm just too scared to continue, does anyone know what i did wrong? my guess is that it's at the vbmeta file but the support post give that file only and i just extracted it and put the md5 file in the userdata box.
I assume that you flashed twrp recovery with vbmeta and you had One Ui 4.0 (Android 12) on stock. It's just that I had a similar thing when I flashed it on TWRP.
Note: WHEN YOU HAVE INSTALLED THE VBMETA AND TWRP FILE AND YOU ARE USING THE STOCK FIRMWARE THEN DO NOT LOGIN TO YOUR SAMSUNG ACCOUNT. YOUR PHONE WILL BE BLOCKED. AND WHEN TURNED ON, IT WILL PROVIDE THE FOLLOWING.
{
"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"
}
lil_kyrick said:
I assume that you flashed twrp recovery with vbmeta and you had One Ui 4.0 (Android 12) on stock. It's just that I had a similar thing when I flashed it on TWRP.
Note: WHEN YOU HAVE INSTALLED THE VBMETA AND TWRP FILE AND YOU ARE USING THE STOCK FIRMWARE THEN DO NOT LOGIN TO YOUR SAMSUNG ACCOUNT. YOUR PHONE WILL BE BLOCKED. AND WHEN TURNED ON, IT WILL PROVIDE THE FOLLOWING.
View attachment 5789287
Click to expand...
Click to collapse
no, it is the android 11 version with the A127FXXU5AVC4 stock firmware (vietnam region) and no i didn't login to anything after unlocking bootloader, and the warning shows something like this image here
but without the 2 last line, instead it has a korean and japanese translation below that first 2 english lines
i think i messed up at the vbmeta part, i though my phone was hard bricked but i managed to fix it and flashed a the stock firmware again
Oh ****. So connect your phone to your computer and use the "Emegency Software Recovery" function in the Smart Switch program.
What was your mistake? Yes, the fact is that you have SM-A127F, and you set it for SM-125F. And you need to repair the device now, otherwise, contact the nearest service center. Here is a link to the guide you need for your device.
lil_kyrick said:
Oh ****. So connect your phone to your computer and use the "Emegency Software Recovery" function in the Smart Switch program.
What was your mistake? Yes, the fact is that you have SM-A127F, and you set it for SM-125F. And you need to repair the device now, otherwise, contact the nearest service center. Here is a link to the guide you need for your device.
Click to expand...
Click to collapse
ah i already fixed it myself with frp hijacker, thank you for your consideration
az_r08 said:
ah i already fixed it myself with frp hijacker, thank you for your consideration
Click to expand...
Click to collapse
Can you send a ss of the odin you are using and the settings?
What I assume is you need to use patched odin or you device is encrypted.