Related
Maze Alpha RED State (Bootloop) solution:
I have a second alpha, so I have made it again step by step.
SP_Flash_Tool_exe_Windows_v5.1728.00.000.
1. unlocked bootloader
2. flash TWRP
3. rooting
4. fastboot locking bootloader
result: red state and bootloop.
countermeasure:
1. flash Maze_Alpha_V05_20170816:
SP_Flash_Tool_exe_Windows_v5.1728.00.000.
download agent: MTK_AllInOne_DA.bin
Menu point at SP flash tool -> Download:
Download without bootloader.
Scatter and rom -> Maze_Alpha_V05_20170816
klick download.
Connect USB cable.
result: ERROR: STATUS_INSUFFICIENT_BUFFER (0xC0010007)
or
second attempt: ERROR: STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003)
if the popup window with the error notices emerges,
Be quick
The popup must be close promptly and press again download or format. It must go very quickly.
thats it.
Wish you created this thread in the Maze Alpha section, would be nice to keep all topics together.
In your original post (before you changed it), you mentioned that you lost your IMEI info. This is because you ran SP Flash Tools in "format all + download" mode, which damaged/overwrote/wiped the "NVRAM" partition (the place where IMEI, MAC addresses, and serial # are stored, among other things). If you look closely, you'll see that your serial number was also reset, and you probably have a NVRAM error in your list of available WIFI networks.
No amount of wiping or flashing will fix this. To fix, you need to restore the NVRAM partition from a TWRP backup (if you have one), or use the official MTK "Maui META" tool:
https://androidmtk.com/download-sp-meta-tool
Then, follow this tutorial:
https://forum.hovatek.com/thread-12328.html
The only change to the tutorial is that you can opt to autosearch for the CustomAppSrcP file on your device, instead of browsing to the buried version in the unzipped official 08/16 ROM.
After all this, install the 09/13 update, which should resolve the WIFI NVRAM error and provide consistent static MAC addresses for Bluetooth & WIFI.
Maui META can also be used to reapply your specific serial number, if you know it (see tutorial above).
Also:
1. To make sure that your PC can communicate with the Alpha and to avoid errors, the official Android SDK USB drivers and USB debugging are not enough, especially on a dead/bricked phone. Make sure you install the MTK USB drivers (chipset 65xx works for 67xx):
installation & tutorial:
https://tehnotone.com/windows-10-mtk-vcom-usb-drivers-for-32-64-bit-drivers-installation-tutorial/
or
http://thefirmwarehub.com/install-mt65xx-usb-preloader-drivers-in-windows-7/
http://thefirmwarehub.com/install-mt65xx-usb-preloader-drivers-in-windows-8-8-1-10/
Auto installer:
http://mtkusballdriver.com/
SP Flash Tools errors & fixes:
https://forum.hovatek.com/thread-439.html?tid=439
2. Do not flash TWRP as you mention in your post! As dreambo originally stated, there is a touch screen response issue yet to be resolved when installed to the recovery partition. Use fastboot to boot the TWRP img when needed.
jobo jobo said:
Maze Alpha RED State (Bootloop)
solution:
I have a second alpha, so I have made it again step by step.
SP_Flash_Tool_exe_Windows_v5.1728.00.000.
1. unlocked bootloader
2. flash TWRP
3. rooting
4. fastboot locking bootloader
result: red state and bootloop.
countermeasure:
1. flash Maze_Alpha_V05_20170816:
SP_Flash_Tool_exe_Windows_v5.1728.00.000.
download agent: MTK_AllInOne_DA.bin
Menu point at SP flash tool -> Download:
Download without bootloader.
Scatter and rom -> Maze_Alpha_V05_20170816
klick download.
Connect USB cable.
result: ERROR: STATUS_INSUFFICIENT_BUFFER (0xC0010007)
or
second attempt: ERROR: STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003)
if the popup window with the error notices emerges,
Be quick
The popup must be close promptly and press again download or format. It must go very quickly.
thats it.
Click to expand...
Click to collapse
The "Be quick" trick saved my Doogee Y6!
Thanks
It didn't work for me, I've performed the oem unlock command and the bootloader returned to orange state.
What can we do to change the orange state back to the green state?
If I perform the 'fastboot flashing lock' will work?
dimmebd said:
It didn't work for me, I've performed the oem unlock command and the bootloader returned to orange state.
What can we do to change the orange state back to the green state?
If I perform the 'fastboot flashing lock' will work?
Click to expand...
Click to collapse
don;t lock it.. it will again go to red state.
i am wondering how to wondering how to get this back to fastboot prompt.
its completely in boot loop and no keys are responding to me on this to reach to boot menu.
Using SP tool I was able to get my device to factory default. It's working good again.
Sarvesh.huddedar said:
Using SP tool I was able to get my device to factory default. It's working good again.
Click to expand...
Click to collapse
Please how did you get it to start working again. I am in red state after trying to lock bootloader
Pyandroid said:
Please how did you get it to start working again. I am in red state after trying to lock bootloader
Click to expand...
Click to collapse
Use SP tool as suggested by vendor.
Does not matter what state is your device into.
I was able to recover my device from red state. Nothing to worry. It works well after successful download.
Sarvesh.huddedar said:
Use SP tool as suggested by vendor.
Does not matter what state is your device into.
I was able to recover my device from red state. Nothing to worry. It works well after successful download.
Click to expand...
Click to collapse
Thanks, I was so scared of losing my Device...I got it working again. Thank you. what ROM are u on Now?
Pyandroid said:
Thanks, I was so scared of losing my Device...I got it working again. Thank you. what ROM are u on Now?
Click to expand...
Click to collapse
Great to hear that you are back to green State..
Current working on Oukitel k6000 plus and on 8.0 custom rom.
Hello to all... my maze alpha is on red state with bootloop after I relock bootloader, I cant get to fastboot with button compination (so I cant flash anything), I cant get to recovery, adb doesnt recognize it, maze flash tool gives me DA ERROR, flash tool windows gives me DA HASH MISHMATCH, flash tool linux random errors. Device manager see the phone as usb vrom, mediatek usb or unknown device as it reboots. Any help will be apriciated... thanks.
Maze Alpha Orange state dopo flash rwrp provato All flash win 10,win7 tuti driver plr
ianto:
jobo jobo said:
Maze Alpha RED State (Bootloop) solution:
I have a second alpha, so I have made it again step by step.
SP_Flash_Tool_exe_Windows_v5.1728.00.000.
1. unlocked bootloader
2. flash TWRP
3. rooting
4. fastboot locking bootloader
result: red state and bootloop.
countermeasure:
1. flash Maze_Alpha_V05_20170816:
SP_Flash_Tool_exe_Windows_v5.1728.00.000.
download agent: MTK_AllInOne_DA.bin
Menu point at SP flash tool -> Download:
Download without bootloader.
Scatter and rom -> Maze_Alpha_V05_20170816
klick download.
Connect USB cable.
result: ERROR: STATUS_INSUFFICIENT_BUFFER (0xC0010007)
or
second attempt: ERROR: STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003)
if the popup window with the error notices emerges,
Be quick
The popup must be close promptly and press again download or format. It must go very quickly.
thats it.
Click to expand...
Click to collapse
Sarvesh.huddedar said:
Great to hear that you are back to green State..
Current working on Oukitel k6000 plus and on 8.0 custom rom.
Click to expand...
Click to collapse
Hello friend ..Please how stable is the Oreo Rom? Does it affects battery life positively. Any bug effects that makes it hard to use?
Please say me hi on whatsapp here. thank you plust 234 Eight1six951666two. thank you.
Sarvesh.huddedar said:
Great to hear that you are back to green State..
Current working on Oukitel k6000 plus and on 8.0 custom rom.[/QUOTE
Anche io ragazzi o questo problema con il mio Maze Alpha 4 gb ram,sono riuscito a instalare la twrp e dopo non sono riuscito a instalare niente con la twrp ,o provato la v5,v8,poi non ero più bono di tornare indietro ,forse o cancellato qualche partizione o tutte perché adesso sono in Orange state,.O provato di tuto è di più,flashare con Windows 10,poi con Windows 7
Tante versioni dis SP flash ,anche solo botloader alla volta ,anche tuto,download ,agiorn firmware,il cambiato tanti driver,ci viene fuori questi errori:S_BROM_CMD_SEND_DA_FAIL,DA_HASH_MISMATCH,No n riesco a sistemarlo in nessuna maniera e lo appena comprato da un mese,se qualcuno ragazzi si intende di più e mi può dare una mano le sarei tanto grato vi ringrazio in anticipo,io volevo solo la twrp perché mi piaceva ancora dai tempi di HTC titan perché si poteva mettere sia Windows mobile che android
Click to expand...
Click to collapse
Maze Alpha Orange state
Privato anche senza botloader niente da fare,errore prima S_BROM_CMD_SEND_DA_FAIL, e dopo DA_HASH_MISMATCH cosa col dire?grazie.ianto:
ragazi sono riuscito a fare partire maze alpha 4g flash sptool 5.1708,o flashato la v9,senza bootload ,problemae che bisogna selezionare DA_PL.bin, e non MTK_AllInOne_DA.bin,finalmente sono riuscito mama mia quanto lavoro ,quante prove,
Thank you so much!!! This saved my phone, now fully working. Got the ROM from drive.google.com/file/d/0B8XLZxEJR8alUGVtYTJYQ2ZVak0
-SOLVED-Hi everyone, I bricked my phone trying to downgrade from Oreo to Nougat.
I extracted the img. files from UPDATE app with Huawei extractor. and flashed via fastboot
But the same error still there.
fastboot flash kernel
fastboot flash ramdisk
fastboot flash recovery_ramdisk
The same ERROR MODE still there. plus I bought some credits on DC Phoenix and did not help at all
I download all the files but I got this error:: -FAIL Command not allowed-
I attached some pictures of the errors.
My phone is totally dead, I will really appreciate your help guys
thanks
osk4rin said:
Hi everyone, I bricked my phone trying to downgrade from Oreo to Nougat.
I extracted the img. files from UPDATE app with Huawei extractor. and flashed via fastboot
But the same error still there.
fastboot flash kernel
fastboot flash ramdisk
fastboot flash recovery_ramdisk
The same ERROR MODE still there. plus I bought some credits on DC Phoenix and did not help at all
I download all the files but I got this error:: -FAIL Command not allowed-
I attached some pictures of the errors.
My phone is totally dead, I will really appreciate your help guys
thanks
Click to expand...
Click to collapse
Fastboot flash the files from the system that you were on before you bricked it or flash twrp then use hwota8 or hurupdater to flash back to stock 8.0.
ajsmsg78 said:
Fastboot flash the files from the system that you were on before you bricked it or flash twrp then use hwota8 or hurupdater to flash back to stock 8.0.
Click to expand...
Click to collapse
I tried all the files that I mentioned and nothing happened, the error still there, TWRP is flashable but won't boot in recovery.
ajsmsg78 said:
Fastboot flash the files from the system that you were on before you bricked it or flash twrp then use hwota8 or hurupdater to flash back to stock 8.0.
Click to expand...
Click to collapse
I flashed the stock recovery_ ramdisk ramdis img. From the stock system 8.0 Oreo where the phone was.
And is stuck on - Your device is booting-
And I see no progress. After that the same Upgrade your system ERROR is back again.
osk4rin said:
I flashed the stock recovery_ ramdisk ramdis img. From the stock system 8.0 Oreo where the phone was.
And is stuck on - Your device is booting-
And I see no progress. After that the same Upgrade your system ERROR is back again.
Click to expand...
Click to collapse
Did you try the recovery from Nougat since that's what you were trying to downgrade to before you bricked it?
ajsmsg78 said:
Did you try the recovery from Nougat since that's what you were trying to downgrade to before you bricked it?
Click to expand...
Click to collapse
I did too, but won't let me flash the Recovery img. from Nougat, just the Oreo recovery
look:
osk4rin said:
Hi everyone, I bricked my phone trying to downgrade from Oreo to Nougat.
I extracted the img. files from UPDATE app with Huawei extractor. and flashed via fastboot
But the same error still there.
fastboot flash kernel
fastboot flash ramdisk
fastboot flash recovery_ramdisk
The same ERROR MODE still there. plus I bought some credits on DC Phoenix and did not help at all
I download all the files but I got this error:: -FAIL Command not allowed-
I attached some pictures of the errors.
My phone is totally dead, I will really appreciate your help guys
thanks
Click to expand...
Click to collapse
Te recomiendo que mejor flashear un rom de Openkirin para que puedas recuperar el celular, y si vas bajar a 7. 0 tendrías que haber bajada las 3 cremalleras que utiliza para hacerlo por medio de hwt8 para que lo flashes por bat. Espero te funcione
franciscojavi31 said:
Te recomiendo que mejor flashear un rom de Openkirin para que puedas recuperar el celular, y si vas bajar a 7. 0 tendrías que haber bajada las 3 cremalleras que utiliza para hacerlo por medio de hwt8 para que lo flashes por bat. Espero te funcione
Click to expand...
Click to collapse
Hola ,gracias por tu respuesta.
Que ROM the Open Kirin?Treble Project?de Oreo?
Gracias!
edited:Ya trate y no ahi algun Progreso.
use erecovery back to that firmware
---------- Post added at 09:42 AM ---------- Previous post was at 09:37 AM ----------
Vol up plus power.approve firmware for imei but using dns as suggested hicloud.doing from another phone or pc. older version firmware before pie supported.
luck2ang said:
use erecovery back to that firmware
---------- Post added at 09:42 AM ---------- Previous post was at 09:37 AM ----------
Vol up plus power.approve firmware for imei but using dns as suggested hicloud.doing from another phone or pc. older version firmware before pie supported.
Click to expand...
Click to collapse
I tried to flashed the recovery from that firmware, but.. Won't flash any Nougat img. Just Oreo
fastboot flash recovery_ramdisk recovery ramdis img.
Won't flash - fastboot flash recovery img.
By the time whe recovery_ramdisk is flashed I did power & volume up to boot into recovery, and it just goes to the message - Your device is booting -
It stays on a bootloop.
osk4rin said:
I tried to flashed the recovery from that firmware, but.. Won't flash any Nougat img. Just Oreo
fastboot flash recovery_ramdisk recovery ramdis img.
Won't flash - fastboot flash recovery img.
By the time whe recovery_ramdisk is flashed I did power & volume up to boot into recovery, and it just goes to the message - Your device is booting -
It stays on a bootloop.
Click to expand...
Click to collapse
Try doing it in command prompt instead of PowerShell.
ajsmsg78 said:
Try doing it in command prompt instead of PowerShell.
Click to expand...
Click to collapse
I tried but can't flash the Nougat recovery img.
osk4rin said:
I tried but can't flash the Nougat recovery img.
Click to expand...
Click to collapse
You have an Oreo partition table at the moment.
You aren't going to be able to flash the Nougat recovery - the N recovery image is a traditional Android boot image (kernel + ramdisk), the O recovery image is just the ramdisk; the O recovery_ramdisk partition is half the size of the N recovery partition.
irony_delerium said:
You have an Oreo partition table at the moment.
You aren't going to be able to flash the Nougat recovery - the N recovery image is a traditional Android boot image (kernel + ramdisk), the O recovery image is just the ramdisk; the O recovery_ramdisk partition is half the size of the N recovery partition.
Click to expand...
Click to collapse
I know, Oreo partition is on it.but the Build system is MHA-L29C432B126 that is why I could not flash any Recovery img from Nougat. and my Original Model is MHA-L29C567 (Oreo)
That means that my phone is dead.
osk4rin said:
I know, Oreo partition is on it.but the Build system is MHA-L29C432B126 that is why I could not flash any Recovery img from Nougat. and my Original Model is MHA-L29C567 (Oreo)
That means that my phone is dead.
Click to expand...
Click to collapse
I haven't yet gone looking too closely into this, but check the P10 guides board - there's a set of instructions there along with some scripts which you can probably use or tweak to revive your device back with Oreo at least. If you were on a recent O security patch you won't be able to roll back to Nougat anyway. (Xloader & fastboot updates in newer security patches cause downgrades to brick.)
Also, the underlying tools (hikey_idt) does work provided you've got suitable sec_usb_xoader/lpm3/fastboot images, which look to be included there.
irony_delerium said:
I haven't yet gone looking too closely into this, but check the P10 guides board - there's a set of instructions there along with some scripts which you can probably use or tweak to revive your device back with Oreo at least. If you were on a recent O security patch you won't be able to roll back to Nougat anyway. (Xloader & fastboot updates in newer security patches cause downgrades to brick.)
Also, the underlying tools (hikey_idt) does work provided you've got suitable sec_usb_xoader/lpm3/fastboot images, which look to be included there.
Click to expand...
Click to collapse
The bootloader is Unlocked as you see on the pic, but Well, I'll keep searching for a solution or just give up with this.
Thanks.
osk4rin said:
The bootloader is Unlocked as you see on the pic, but Well, I'll keep searching for a solution or just give up with this.
Thanks.
Click to expand...
Click to collapse
Bootloader unlock is different than full fastboot unlock. A full fastboot unlock allows for the flashing of any partition (including the partition table itself) via fastboot, a normal bootloader unlock only allows you to flash a selected handful of partitions.
Unfortunately, I only know of 3 ways to get that unlock:
* The backdoor used by DC Unlocker and the like
* NVME patching
* USB xloader from a board firmware package, loaded via testpoints.
If you were ever on a newer security patch, the backdoor doesn't work any longer as the key used for generating the backdoor token was changed; and since you don't have a working system or recovery, you can't do the NVME patch.
irony_delerium said:
Bootloader unlock is different than full fastboot unlock. A full fastboot unlock allows for the flashing of any partition (including the partition table itself) via fastboot, a normal bootloader unlock only allows you to flash a selected handful of partitions.
Unfortunately, I only know of 3 ways to get that unlock:
* The backdoor used by DC Unlocker and the like
* NVME patching
* USB xloader from a board firmware package, loaded via testpoints.
If you were ever on a newer security patch, the backdoor doesn't work any longer as the key used for generating the backdoor token was changed; and since you don't have a working system or recovery, you can't do the NVME patch.
Click to expand...
Click to collapse
Yes, I cant able to flash the recovery from the Nougat system. Just Oreo.
Pretty much can't do anything.
osk4rin said:
Yes, I cant able to flash the recovery from the Nougat system. Just Oreo.
Pretty much can't do anything.
Click to expand...
Click to collapse
No, you can't flash a Nougat recovery on an Oreo partition table. Absolutely won't work.
You HAVE to flash an Oreo recovery, and you probably need to make sure you've got a suitable kernel image as well in the 'kernel' partition. (As has been said before - recent security patch CANNOT roll back to Nougat. You will brick. There is no workaround, it will fail, as you have discovered. Usually the brick is worse - you don't even get fastboot. You just get the serial port in download mode waiting for a sec signed xloader & such to come down.)
This was coming to mind when you posted that:
From an Oreo package, you might try flashing the following:
kernel
recovery_ramdisk
recovery_vendor
recovery_vbmeta
Then try booting recovery. I don't remember whether fastboot will allow you to flash the other two, but at the very least I know you need a working kernel and recovery image - if flashing those will get you booting to recovery, you can probably load up an Oreo TWRP from there and possibly use hurupdater or hwota8 to flash the full system back.
irony_delerium said:
No, you can't flash a Nougat recovery on an Oreo partition table. Absolutely won't work.
You HAVE to flash an Oreo recovery, and you probably need to make sure you've got a suitable kernel image as well in the 'kernel' partition. (As has been said before - recent security patch CANNOT roll back to Nougat. You will brick. There is no workaround, it will fail, as you have discovered. Usually the brick is worse - you don't even get fastboot. You just get the serial port in download mode waiting for a sec signed xloader & such to come down.)
This was coming to mind when you posted that:
From an Oreo package, you might try flashing the following:
kernel
recovery_ramdisk
recovery_vendor
recovery_vbmeta
Then try booting recovery. I don't remember whether fastboot will allow you to flash the other two, but at the very least I know you need a working kernel and recovery image - if flashing those will get you booting to recovery, you can probably load up an Oreo TWRP from there and possibly use hurupdater or hwota8 to flash the full system back.
Click to expand...
Click to collapse
I flashed those commands and nothing happened.
Power +Volume Up trying to boot into Recovery.
My device is Just:
Your Device is booting now....
-Bootloop-
Also Same error, Please update your system
Error!
Func NO: 11 (recovery image)
Func NO: 2 (load failed!)
Hi guys:
Once again it's me... I have tried with no success to "covert" my Axon 10 Pro from Mexico (Guess US model, 855A03 no NA 855A03_NA) to EU, I have downloaded several zip files from XDA and other sites. I have tried with QFIL, MiFlash and the EDL tool as well.
But none of them work, do you know if this is possible or a guide to do it?
MiFlash: Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
QFIL: Error (can't remember right now)
EDL: Error (can't remember right now)
Or maybe a way to recover fastboot to try the Lineage ROM, since I don't have it... I tried with adb reboot bootloader (no go, the phone restarts and goes directly to the carrier logo, no fastboot) I have tried with the vol - and power keys (no go, the same).
Ooooooorrr.... Maybe a way to install TWRP from EDL since I haven't fastboot, I've tried with emmcdl:
emmcdl -p COM4 -f prog_ufs_firehose_sdm855.elf -b recovery twrp.img
It appears to flash it, but after that it reboots and the old recovery is there.
Kind regards!
So... I've finally installed TWRP using a ROM from other forum, but in the end it didn't end as expected, I could install recovery, then I tried to install lineage but... Bootloop.
I´ll try again later.
JUst to let you know, is possible to install TWRP. I'll post my tutorial later. Regards
zparallax said:
Hi guys:
Once again it's me... I have tried with no success to "covert" my Axon 10 Pro from Mexico (Guess US model, 855A03 no NA 855A03_NA) to EU, I have downloaded several zip files from XDA and other sites. I have tried with QFIL, MiFlash and the EDL tool as well.
But none of them work, do you know if this is possible or a guide to do it?
MiFlash: Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
QFIL: Error (can't remember right now)
EDL: Error (can't remember right now)
Or maybe a way to recover fastboot to try the Lineage ROM, since I don't have it... I tried with adb reboot bootloader (no go, the phone restarts and goes directly to the carrier logo, no fastboot) I have tried with the vol - and power keys (no go, the same).
Ooooooorrr.... Maybe a way to install TWRP from EDL since I haven't fastboot, I've tried with emmcdl:
emmcdl -p COM4 -f prog_ufs_firehose_sdm855.elf -b recovery twrp.img
It appears to flash it, but after that it reboots and the old recovery is there.
Kind regards!
Click to expand...
Click to collapse
I have the same version (telcel) es una lástima que Telcel ni ZTE le den seguimiento para actualizar, si pudiste cambiarlo a la versión de EU o internacional, agradecer
I have just brought a samsung galaxy a03 core...My conclusion on rooting the device ...
1 other sites say rooter like kingo or kingroot work this is rubbish only one app I found that rooted the samsung a03 core was Magisk and it has to be the magisk canary version but even even patching the boot image coursed boot loops .....My way that only used two apps 1 7zip and Odin...
2 First use 7zip to copy all the contents of AP_A032FXXU1AVA1 to a new folder (it has be copy to in 7zip...once this done copy boot image to storage on phone next use magisk to patch file ....
3 next remove boot image from AP_A032FXXU1AVA1 and replace it with patched file after renaming it boot
4 copy all files from the AP_A032FXXU1AVA1 folder (not the folder save as a tar file when done use odin to flash it in AP ...
When it finnish you will need to go straight into recovery mode and do a factory reset or you will get a boot loop lastly it will still say no root on root checher so just install the super su root checker and it finnishes the rooting..So now the samsung galaxy a03 core is rooted...
Conclusion ....What good is rooting the samsung galaxy a03 core when you cannot get a custom recovery or any custom roms yet ........
I got the same phone and i have to say, it's terrible using android 11 go. Even terrible when it's modified by samsung. I'm crazy looking for a lineage os rom for this phone and looks like no one is interested into making one. Sad
sPokeySz said:
I got the same phone and i have to say, it's terrible using android 11 go. Even terrible when it's modified by samsung. I'm crazy looking for a lineage os rom for this phone and looks like no one is interested into making one. Sad
Click to expand...
Click to collapse
yes I find that people post;;;;;;How to install TWRP or Custom rom when at this pressant moment there is neither is just a waste of time...So till a custom comes out all you can do is root it...
samsung a03 core Will leave it as it is till the TWRP and custom rom are developed ......Lastly does anyone know how get rid of bootloader warning when the phone is rooted
j.p.s 1950 said:
samsung a03 core Will leave it as it is till the TWRP and custom rom are developed ......Lastly does anyone know how get rid of bootloader warning when the phone is rooted
Click to expand...
Click to collapse
I would like to know also
j.p.s 1950 said:
I have just brought a samsung galaxy a03 core...My conclusion on rooting the device ...
1 other sites say rooter like kingo or kingroot work this is rubbish only one app I found that rooted the samsung a03 core was Magisk and it has to be the magisk canary version but even even patching the boot image coursed boot loops .....My way that only used two apps 1 7zip and Odin...
2 First use 7zip to copy all the contents of AP_A032FXXU1AVA1 to a new folder (it has be copy to in 7zip...once this done copy boot image to storage on phone next use magisk to patch file ....
3 next remove boot image from AP_A032FXXU1AVA1 and replace it with patched file after renaming it boot
4 copy all files from the AP_A032FXXU1AVA1 folder (not the folder save as a tar file when done use odin to flash it in AP ...
When it finnish you will need to go straight into recovery mode and do a factory reset or you will get a boot loop lastly it will still say no root on root checher so just install the super su root checker and it finnishes the rooting..So now the samsung galaxy a03 core is rooted...
Conclusion ....What good is rooting the samsung galaxy a03 core when you cannot get a custom recovery or any custom roms yet ........
Click to expand...
Click to collapse
Hello, please explain step 4. I didn't understand
j.p.s 1950 said:
Conclusion ....What good is rooting the samsung galaxy a03 core when you cannot get a custom recovery or any custom roms yet ........
Click to expand...
Click to collapse
Well, at least you can fiddle with the bloatware the stock ROM comes with.
Mahianyu said:
Hello, please explain step 4. I didn't understand
Click to expand...
Click to collapse
Forget the 4th step the OP mentioned. You just need to select the patched boot.img (magisk will output the patched file with a different file name), rename it into boot.img, archive it into boot.tar using 7zip, and use that .tar file to flash with Odin in AP field. Remember to unselect reboot after download/flash in Odin's option, because you need to enter recovery mode after flashing, and do a factory reset (wipe cache and data partition) following the flashing procedure.
Do you have firmware For A3 core sm-A-13g .I need for africa region .When i instal soft from azja this change menu in phone from "GALAXY A3 core" to "Galaxy A1 core .Now i have a bootloop .I have open bootloader but i cant find a recovery twrp in this model .PLease help
BangRegar said:
Olvídese del cuarto paso que mencionó el OP. Solo necesita seleccionar el boot.img parcheado (magisk generará el archivo parcheado con un nombre de archivo diferente), cámbiele el nombre a boot.img, archívelo en boot.tar usando 7zip y use ese archivo .tar para flashear con Odin en el campo AP. Recuerde anular la selección de reiniciar después de descargar/flashear en la opción de Odin, porque necesita ingresar al modo de recuperación después de flashear y hacer un restablecimiento de fábrica (borrar caché y partición de datos) siguiendo el procedimiento de flasheo.
j.p.s 1950 said:
Acabo de traer un samsung galaxy a03 core... Mi conclusión sobre rootear el dispositivo...
1 otros sitios dicen que rooter como kingo o kingroot funciona, esto es basura, solo una aplicación que encontré que rooteó el núcleo de samsung a03 era Magisk y tiene que ser la versión canary de magisk, pero incluso parchear la imagen de arranque cursó bucles de arranque ..... Mi camino que solo usó dos aplicaciones 1 7zip y Odin...
2 Primero use 7zip para copiar todo el contenido de AP_A032FXXU1AVA1 a una nueva carpeta (se debe copiar en 7zip... una vez hecho esto, copie la imagen de arranque al almacenamiento en el teléfono y luego use magisk para parchear el archivo...
3 a continuación, elimine la imagen de inicio de AP_A032FXXU1AVA1 y reemplácela con un archivo parcheado después de cambiarle el nombre de inicio
4 copie todos los archivos de la carpeta AP_A032FXXU1AVA1 (no guarde la carpeta como un archivo tar cuando termine, use odin para actualizarlo en AP ...
Cuando finalice, deberá ir directamente al modo de recuperación y hacer un restablecimiento de fábrica o obtendrá un bucle de arranque, por último, seguirá diciendo que no hay root en root checher, así que simplemente instale el super su root checker y finaliza el enraizamiento ... Entonces ahora el samsung galaxy a03 core esta rooteado...
Conclusión ... ¿De qué sirve rootear el Samsung Galaxy A03 Core cuando aún no puede obtener una recuperación personalizada o ninguna ROM personalizada ........
Click to expand...
Click to collapse
Hola bro como dentro en modo fastboot en a03 core bro ? Lo necesito para rootear mi cell
Click to expand...
Click to collapse
@El insano👻👻 Hola bro como dentro en modo fastboot en a03 core bro ? Lo necesito para rootear mi cell
------------------------------------------------------------------------------------
First off, English is required in XDA.
Samsung has not fastboot mode enabled, instead you should go to bootloader/download mode, to can flash the patched boot image using Odin tool.
To enter the download mode, you have at least three ways of:
- Using hardware buttons, from the device off, press volume down while connect to the PC using a USB cable, when you have the main screen, press volume up, if you want to continue, or volume down, if you want to cancel.
- Going to recovery mode, either through hardware buttons (pressing volume up + PWR) or through command adb reboot recovery, then in the recovery menu choose Reboot to bootloader from.
- And the easier, through command adb reboot bootloader
SubwayChamp said:
@El insano
First off, English is required in XDA.
Samsung has not fastboot mode enabled, instead you should go to bootloader/download mode, to can flash the patched boot image using Odin tool.
To enter the download mode, you have at least three ways of:
- Using hardware buttons, from the device off, press volume down while connect to the PC using a USB cable, when you have the main screen, press volume up, if you want to continue, or volume down, if you want to cancel.
- Going to recovery mode, either through hardware buttons (pressing volume up + PWR) or through command adb reboot recovery, then in the recovery menu choose Reboot to bootloader from.
- And the easier, through command adb reboot bootloader
Click to expand...
Click to collapse
Mod translated:
if someone creates a TWRP image, it would be possible to install a GSI on it, because it is compatible with Treble
*****************
se alguém criar uma imagem TWRP, seria possível instalar um GSI nela, porque é compatível com o Treble
SrMatheus said:
Mod translated:
if someone creates a TWRP image, it would be possible to install a GSI on it, because it is compatible with Treble
*****************
se alguém criar uma imagem TWRP, seria possível instalar um GSI nela, porque é compatível com o Treble
Click to expand...
Click to collapse
Well I got one but you have to work on it to boot proper
Pisamman said:
What do you have? are you developing a TWRP image for the Samsung A03 Core?
Click to expand...
Click to collapse
yes i have a working custom twrp recovery for that devices but this time am not going to give any links to my projects like i use to do
Since December I bought the tablet and in the process of unlocking the boot the tablet bricked, since then it's stuck in fastboot mode, I've tried several things and nothing has worked until today, if anyone can help me I'm grateful.
I couldn't install twrp
TB-J716F
Ну давай тут каждый будет на своём языке писать. Язык форума - английский.
Это не рекавери вообще, это fastboot.
Модель планшета укажи, балбес. TB-???
f1tm0t said:
Ну давай тут каждый будет на своём языке писать. Язык форума - английский.
Это не рекавери вообще, это fastboot.
Модель планшета укажи, балбес. TB-???
Click to expand...
Click to collapse
I used the translator, sorry if I'm not as smart as you, smartass
Are you tried turn off tablet and put it in EDL mode? It works?
If EDL working, you can flash some firmware via RSA or QFIL.
f1tm0t said:
Are you tried turn off tablet and put it in EDL mode? It works?
If EDL working, you can flash some firmware via RSA or QFIL.
Click to expand...
Click to collapse
Now the tablet simply doesn't turn on anymore, when I connect it to the computer it gives this image error, I try to put it in EDL but it always gives the error
I have already updated all possible USB drives
You need install QPST: https://qpsttool.com/qpst-tool-v2-7-496
It installs needed drivers.
You must to see QDLoader 9008 port
f1tm0t said:
You need install QPST: https://qpsttool.com/qpst-tool-v2-7-496
It installs needed drivers.
You must to see QDLoader 9008 port
Click to expand...
Click to collapse
after a long time I managed to put it in EDL, I can install the rom without problems, but I always fall into this image error.
The entire installation process in qfil runs smoothly.
I couldn't install TWRP, can you help me?
You have some problem with /data partition, stock recovery can't fix it.
Go to my post: https://forum.xda-developers.com/t/tb-j716f-twrp-for-android-12-zui-14.4523577/
Download latest twrp.
Turn tablet into fastboot mode.
On PC run command:
Code:
fastboot flash recovery TWRP_J716F_A12_DD. img
then
Code:
fastboot reboot recovery
You need format data from TWRP.
Wipe - Format data - type "yes".
PS. If your had flashed A11 firmware - you need TWRP for A11 - take it in this topic^ https://forum.xda-developers.com/t/tb-j716f-latest-twrps-for-a11-and-a12.4533223/
f1tm0t said:
You have some problem with /data partition, stock recovery can't fix it.
Go to my post: https://forum.xda-developers.com/t/tb-j716f-twrp-for-android-12-zui-14.4523577/
Download latest twrp.
Turn tablet into fastboot mode.
On PC run command:
Code:
fastboot flash recovery TWRP_J716F_A12_DD. img
then
Code:
fastboot reboot recovery
You need format data from TWRP.
Wipe - Format data - type "yes".
PS. If your had flashed A11 firmware - you need TWRP for A11 - take it in this topic^ https://forum.xda-developers.com/t/tb-j716f-latest-twrps-for-a11-and-a12.4533223/
Click to expand...
Click to collapse
I installed twrp as you instructed, but in the last code the tablet does not restart, it gives this message "C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot recovery
fastboot: usage: recovery from unknown reboot destination"
Another thing I noticed that the tablet serial has changed, it is no longer with the serial that came with the tablet
Show me screenshot with "fastboot reboot" command execution.
Tablet's s/n - is not my deal, nothing about s/n changing in my instructions.
SN can be changed only with replacing fpinfo partition inside the tablet or restoring of twrp backup, taken from other tablet.
You can reboot from fastboot mode to recovery(TWRP) mode by tablet's buttons.
Volume buttons are choice, Power button is confirming.
f1tm0t said:
Mostre-me a captura de tela com a execução do comando "fastboot reboot".
S/n do tablet - não é meu negócio, nada sobre s/n mudando nas minhas instruções.
O SN pode ser alterado apenas substituindo a fpinfo considerável dentro do tablet ou restaurando o backup twrp, obtendo de outro tablet.
Você pode reiniciar do modo de inicialização rápida para o modo de recuperação (TWRP) pelos botões do tablet.
Os botões de volume são escolhidos, o botão liga / desliga está confirmando.
Click to expand...
Click to collapse
Meu amigo, vou descrever o que fiz com o tablet desde que ele chegou.
1. quando o tablet chegou vi que estava em L3 e sem pesquisar nada tentei bloquear o boot, e fiz isso mas não sabia que iria brickar o aparelho.
2. depois de pesquisar vi que tinha um método HAHAHAHA e tentei muito resolver, depois de muito tempo tentando consegui, mas quando usei o qfil a imagem rodou mas foi para onde diz que está corrompida
3. Até então não tinha conseguido instalar o TWRP e com sua orientação consegui instalar o twrp, baixei o roons via OTA e renomeei para update.zip
4. Tentei o wipe conforme instruído, mas deu alguns erros como podem ver na imagem, mas a instalação foi um sucesso até o reset do tablet ficou em loop infinito, tentei as duas versões OTA e todas estavam em um Loop infinito
5. Agora quando tento instalar novamente o twrp não consigo mais, o comando para reiniciar o aparelho não funciona, como podem ver na imagem.
6. Usando outro tutorial aqui do fórum consegui retornar o serial válido, porém sem sucesso no qfil
4.
5.
Thanks for everyone's help, especially my friend f1tm0t, with your tips I managed to revive my tablet, I put the zui14 CN, I live in Brazil, but for those who didn't have anything, it's great.
You can close the topic.