Hi folks,
I've got a new A52 5G and wanted it to root. TWRP couldn't be used, because each and every possible solution failed. I even got stuck at boot with a message that the recovery couldn't get startet, even if I just restarted the phone without pressing the keys and without plugged USB cable.
Even flashing the original firmware was not possible. Then I tried to lock the bootloader again and flashing of the firmware was going on with odin. Puh... Then I used the Magisk method without TWRP to change die boot.img with magisk and load it in Odin. Success! I had now root on the phone. Yesterday I read about uninstall Magisk and install it afterwards on the B partition for updating the firmware over OTA. But accidentally I pressed the button below "uninstall" and it performed imediately. Now my phone is dead again... With unlocked Bootloader it is stuck in a bootload and I can start the Samsung recovery mode to wipe the cache for example. I wiped the phone completely, but it is still stucked in a bootloop.
Then I tried my first method: Just lock the Bootloader again (in the download mode) and then flash the new firmware with odin. But Odin either crashes or is giving me instantly the message "failed".
When I'm trying to start the phone (it happened also after locking the bootloader) i'm getting the download screen and the message with a big red !
"partition boot
Reason boot: Hash of data does not match digest in descriptor. [2nd] (3)
Calculated Hash of (boot) : 23B8CFD554, (VEMETA) : D23E59ACD6
CUSTOM boot
VBMETA A526BXXU1AUCA, 38851814R"
Now I unlocked the bootloader again, to access the recovery mode so I can turn it off. Otherwise its stuck in the damn bootloop. Can't flash and wipe doesn't help either.
Please help me somehow -.-
why did you u
Insomnium_D said:
Hi folks,
I've got a new A52 5G and wanted it to root. TWRP couldn't be used, because each and every possible solution failed. I even got stuck at boot with a message that the recovery couldn't get startet, even if I just restarted the phone without pressing the keys and without plugged USB cable.
Even flashing the original firmware was not possible. Then I tried to lock the bootloader again and flashing of the firmware was going on with odin. Puh... Then I used the Magisk method without TWRP to change die boot.img with magisk and load it in Odin. Success! I had now root on the phone. Yesterday I read about uninstall Magisk and install it afterwards on the B partition for updating the firmware over OTA. But accidentally I pressed the button below "uninstall" and it performed imediately. Now my phone is dead again... With unlocked Bootloader it is stuck in a bootload and I can start the Samsung recovery mode to wipe the cache for example. I wiped the phone completely, but it is still stucked in a bootloop.
Then I tried my first method: Just lock the Bootloader again (in the download mode) and then flash the new firmware with odin. But Odin either crashes or is giving me instantly the message "failed".
When I'm trying to start the phone (it happened also after locking the bootloader) i'm getting the download screen and the message with a big red !
"partition boot
Reason boot: Hash of data does not match digest in descriptor. [2nd] (3)
Calculated Hash of (boot) : 23B8CFD554, (VEMETA) : D23E59ACD6
CUSTOM boot
VBMETA A526BXXU1AUCA, 38851814R"
Now I unlocked the bootloader again, to access the recovery mode so I can turn it off. Otherwise its stuck in the damn bootloop. Can't flash and wipe doesn't help either.
Please help me somehow -.-
Click to expand...
Click to collapse
why did you OTA update the rooted phone
it is clearly written that your phone might brick.
what happened to you is your boot.img file is replaced with the newer version try replacing with the boot.img file of previous version.
I didn't, because I get (as always, this is not my first rooted phone) the message, that the system has been changed. OTA is not working and I read that uninstall magisk, update the phone and BEFORE reboot install magisk again on partition B. But I accidentaly pressed the second option in magisk, complete uninstall or how its name is. Didn't expected, that its start instantly without a "Caution" message.
Uninstalling Magisk should not bring my phone into a bootloop anyway, even if I wipe the cache. Or am I wrong?
raja0408 said:
what happened to you is your boot.img file is replaced with the newer version try replacing with the boot.img file of previous version.
Click to expand...
Click to collapse
That is the problem how do I do that, when everything with odin stops imediately or odin crashes.
Does Odin give you any error messages? Are you patching all of the files for the firmware AP BL CP & CSC? Are you making sure to use the non home CSC? Have you tried using Samsung Smart Switch to recover your phone?
Smart Switch didn't recognize the phone. The only error on Odin was "succeed 0 / failed 1).
It worked with Windows 10 notebook and the USB C Port. However it didn't worked on Win 7 and regular USB Ports. Very strange. Well, but now I have the original firmware and again lots of bloatware. TWRP doesn't work, impossible to boot with it. How can I root the A52 with Magisk that way, to deactivate it - if needed - for firmware updates? The phone doesn't has A/B partition.
Same happened to me.
So, I have an A52 Indian version and want to flash the Canadian firmware. I downloaded different versions of the Canadian firmware and used Odin to flash. I followed the instructions on downloading the files, loading them into Odin,hit Start and it kept failing. It was giving an error message regarding a repartitioning error. Could this be due to having to tick "OEM Unlocking" in developer options which I hadn't done?
Hey, is your phone still stuck ?
SHAREit
Related
Hi,
Can someone help me? My Moto Z bricks itself:
I have a Moto Z XT1650-3. On January 31 the phone shutdown alone, after I unlocked teh screen with fingerprints then I restarted the phone and all fine. Then the phone shutdown again, when the phone restarted. It restarted in fastboot mode I switched to restart normally when it showed these message "Your device has failed verification and may not work properly".
I have my phone unusable. When my phone returned for the Moto Technical Support It only boots in fastmode. No recovery no OS (android). I've to say that I never try to root or unlocked the bootloader of my Phone it worked really smooth. I bought the Phone on October 4th 2016.
Finally I tried to reflash the Stock Firmware via fastboot and the problem continues . The phone only boots in fastboot again an again. I tried via fastboot the CMD: gtrvall and said tha warrantyavoid NO.
When I tried recovey mode the same message appears "Your device has failed verification and may not work properly" and I cant do anything.
I wonder someone can help me.
Regards
So you tried to reflash the firmware via fastboot and your device is still dead?
I had the same issue but flashing via RSDLite fixed it.
In your case, I may have to throw in the towel and assume that a critical block on your system partition is corrupted beyond recovery, possibly caused by a defective NAND module.
D13H4RD2L1V3 said:
So you tried to reflash the firmware via fastboot and your device is still dead?
I had the same issue but flashing via RSDLite fixed it.
In your case, I may have to throw in the towel and assume that a critical block on your system partition is corrupted beyond recovery, possibly caused by a defective NAND module.
Click to expand...
Click to collapse
Hi
Yes i tried to reflash via fastboot it didn't worked the phone boot until in fastboot mode and sometimes the Motos logo appears and then again fastboot mode?.
Thnks for answer but if it is this i think that its a hsrdware failure and the warranty must have to apply in this case because my phone is until in warranty I think that this problem its hardware from the first day and this message its like. Warning that something isn't right?
I will try again with Motorola warranty to replace the phone
Regards
Hello guys,
i wanted to upgrade my Ressurection Remix ROM and managed to softbrick my phone. While flashing the software (Flashing system partition unconditionally) TWRP got stuck.
My phone got an unlocked bootloader and i already tried to flash the global MIUI ROM via EDL and also fastboot. The flashing process is successfull but after i restart my phone i'm stuck at the MI Logo with the moving Android Circles for loading.
I let this run for ~6 hours, no progress at all.
I also tried flashing the Global DEV Rom, same as above.
Factory Reset via Recovery Mode (with MI Suite) also didn't do the trick.
I think something with the bootloader went wrong. Any ideas to unbrick it?
I can access Fastboot and EDL Mode, unlocked Bootloader. I also got a TWRP backup with System and Data Partition, but currently only the original Revocery is installed.
Any help is very much appreciated, thank you.
Did you tried using this guide to flash stock firmware/recovery?
http://en.miui.com/a-234.html
Yes, the problem is not to flash the Fastboot ROM, but after successfully flashing the ROM i got stuck at the MI Logo with the loading Android dots
That's weird.. this bootloop usually happens when you flash stock MIUI and still have TWRP installed, can you check if you have stock recovery after fastboot flash?
After i flashed the global DEV ROM i got the stock recovery where i can choose between Wiping Data, switch to MI Suite etc.
Edit: Its not really an bootloop, it just gets stuck there without doing anything
Update: Got TWRP back, now if i want to flash any ROM (doesn't matter if stock/custom) i'm stuck at TWRP saying: "Patching system unconditionally..." it stays there for hours.
Any advice in this case?
guys,, i was facing same problem. I also agree that 8012... status does not matter to unlocking bootloader. I was tried all but fail after granted permission. I was tried daily. after 5 days when I tried with old mi unlock tool I got error at 50%. After that restarted my phone and clicked on settings and in developer menu, I watched i clicked on allow unlock bootloader but I forgot to click on usg debbuging. after clicked it I went for fastboot with old unlock tool and I got success. thankyou.
Try my method you will get success. hit like. stay tune. tandob is here to help you guys.
tandob said:
guys,, i was facing same problem. I also agree that 8012... status does not matter to unlocking bootloader. I was tried all but fail after granted permission. I was tried daily. after 5 days when I tried with old mi unlock tool I got error at 50%. After that restarted my phone and clicked on settings and in developer menu, I watched i clicked on allow unlock bootloader but I forgot to click on usg debbuging. after clicked it I went for fastboot with old unlock tool and I got success. thankyou.
Try my method you will get success. hit like. stay tune. tandob is here to help you guys.
Click to expand...
Click to collapse
That has absolutely nothing to do with the problem mentioned above.
Hello,
I've Samsung Galaxy SM-J701F/DS and i did factory reset and started getting into panic mode. So, I tried to flash stock ROM through odin and I only selected AP and left other files like Bl, CP and CSC. Thus it took longer time without any result so, I closed the odin. Since then my phone only boots in download mode.
And while trying recovery or normal boot I get " Error Cannot Update Software ".
I used this ROM:
https://www.sammobile.com/firmwares/...-nxt/SM-J701F
And now my phone is showing as Samsung USB Modem while plugging in PC.
ok hear me out, I'm a newbie, and I missed up, plz help
I was trying to root my device following this tutorial, I flashed twrp and vbmeta and every thing went alright without errors, I booted the phone into recovery to continue as how the tutorial said, but it gave me the orange state error and it restarted into system but now the device is factory reset, I enabled usb debugging and went on to follow this tutorial, every thing went same as before and I couldn't boot into recovery, so I decided to flash the "orange_state_disabler_MTK Only.zip" with adb and every thing went downhill from there, It won't boot to recovery, bootloader nor system, It just stays at a blank screen after the logo and the orange state message, It is recognized by adb as "recovery" and I can do adb commands but I can't boot to bootloader to flash the stock firmware, I found this thread and tried using the tool mentioned there, Faced an error, solved it and the phone still won't boot to any thing.
so, is there any way I can get out of this situation ?
TLDR / what you should know/ idk ¯\_(ツ)_/¯
- did something wasn't supposed to do
- can't boot to recovery
- can't boot to bootloader
- device recognized by adb but can't do fastboot commands
- device is recognized by MTKAuthBypassToolV25
- can't shutdown nor restart using phone physical buttons
- don't know if the below screenshots would help with any thing, but here goes nothing
You have misunderstanding, Orange State does not cause anything. That is just notification that bootloader is unlocked, nothing more. Therefore the Orange State Disabler cannot fix anything. You don't need this at all.
But it seems it destroyed fastboot. flash lk from SP Flash Tool
aIecxs said:
You have misunderstanding, Orange State does not cause anything. That is just notification that bootloader is unlocked, nothing more. Therefore the Orange State Disabler cannot fix anything. You don't need this at all.
But it seems it destroyed fastboot. flash lk from SP Flash Tool
Click to expand...
Click to collapse
please explain, I don't know what IK is, and if I could flash things with SP flash tools, wouldn't I be able to flash stock firmware?
lk - little kernel. that is the partition where fastboot lives (and was modified by Orange State Disabler).
you need partition image from stock ROM and any flash tool to restore its original state.
i can't do that because i can't boot to bootloader
you don't need bootloader, only preloader or bootrom
ok turns out ima an idiot and misunderstood the entire situation , this is my first dealing with an mtk device so i thought sp flash tool is like odin and you need to be in download mode to flash things so i panicked, and didn't read well how to use the tool.
flashed stock firmware and the phone is up and running again
thanks for your help man really appreciate it and sorry for wasting your time
Man I never thought that I'd be in this situation but here I am, I tried updating my S21 to the latest FW that I've downloaded using Frija but after I finished plugging the files into ODIN and updating my phone I got stuck in a bootloop wit this error:
"Can’t load Android System your data may be corrupt"
Is there anyway I can restore or unbrick my phone without factory restoring it? - I made the stupid mistake of not backing up my files which I ALWAYS do and the only time I didn't I get this error.
This is the file that I've downloaded via Frija: SM-G991U_2_20220816092331_e4zyor31mz_fac
I'm able to boot into recovery mode and when I run the adb services the phone is detected on my machine but I can't access fastboot.