Develop Bugs

Can't update to B512

Hey guys. I was on Kitkat Beta CN with TWRP. I wanted to update to B512 so I reverted to the original recovery B506CN recovery (downloaded it from here http://forum.xda-developers.com/showthread.php?t=2709353)
Once I pressed local update the phone reboots but I get the following error message:
Huawei SD card update fail.....
The update is /dload/update.app
Why do I get this error message and how to fix it in order to update to B512

try one of these http://forum.xda-developers.com/ascend-p6/help/p6-u06-common-issues-fixes-t2843810#post54736765 or http://forum.xda-developers.com/ascend-p6/development/diy-rom-b510-based-add-want-t2843511

Tried many different combinations and nothing helped seems this problem is binded to my SD card. I tried different recovery versions and tried to update when I had 3 different roms. It seems I can't update with the stock recovery no matter what I do. I tried doing that in the internal storage but still the same mistake? Why should it access the SD card for an update in the internal storage?

When I enter recovery manually (without going at update section in settings) I see at first screen this message and I have to restart to enter at the recovery
ro.build.version.release = 4.4.2
ro.product.name = VEDGE
Current build version release is not 4.2 - don't need move.
USB Update Enter...
HUAWEI SDCARD&USB UPDATE AGENT VERSION 2.0
This phone is secureboot phone.
This phone is unlock state
Do you also see it or is this a clue?

Igano said:
When I enter recovery manually (without going at update section in settings) I see at first screen this message and I have to restart to enter at the recovery
ro.build.version.release = 4.4.2
ro.product.name = VEDGE
Current build version release is not 4.2 - don't need move.
USB Update Enter...
HUAWEI SDCARD&USB UPDATE AGENT VERSION 2.0
This phone is secureboot phone.
This phone is unlock state
Do you also see it or is this a clue?
Click to expand...
Click to collapse
You should unplug your device from usb and then reboot to recovery because u can read there "USB Update Enter" that means your device is pluged to a pc

Igano said:
Tried many different combinations and nothing helped seems this problem is binded to my SD card. I tried different recovery versions and tried to update when I had 3 different roms. It seems I can't update with the stock recovery no matter what I do. I tried doing that in the internal storage but still the same mistake? Why should it access the SD card for an update in the internal storage?
Click to expand...
Click to collapse
Have you tried using the file to downgrade back to Jelly bean from KitKat?
https://mega.co.nz/#!8kcVADpB!JKeDlX4WQhmAP3mclNTfIzIjVllw5sMhnrj-3KSpSc4
Download the file, and place the dload folder onto your sd card, and do a local update as usual. When that is done, your phone will reboot normally. Just replace the dload folder with the one from B512, and try updating again. If it still doesn't work, I'd suggest doing a forced update using the 3-button method (power button & volume keys).

dl this first http://www.androidfilehost.com/?fid=23252070760973625
extract it's file in your adb dir
You also could try this > run cmd on your pc >use
adb reboot bootloader
fastboot flash recovery "full name of the file extracted from the downloaded file inc it's extension"
fastboot reboot
then you could try flashing again

astrit1 said:
You should unplug your device from usb and then reboot to recovery because u can read there "USB Update Enter" that means your device is pluged to a pc
Click to expand...
Click to collapse
Yes I tried and it's still the same fails.
miz_pimp said:
Have you tried using the file to downgrade back to Jelly bean from KitKat?
https://mega.co.nz/#!8kcVADpB!JKeDlX4WQhmAP3mclNTfIzIjVllw5sMhnrj-3KSpSc4
Download the file, and place the dload folder onto your sd card, and do a local update as usual. When that is done, your phone will reboot normally. Just replace the dload folder with the one from B512, and try updating again. If it still doesn't work, I'd suggest doing a forced update using the 3-button method (power button & volume keys).
Click to expand...
Click to collapse
Did with your file and just any other rom I could find in the forum, still the same error
digijedi007 said:
dl this first http://www.androidfilehost.com/?fid=23252070760973625
extract it's file in your adb dir
You also could try this > run cmd on your pc >use
adb reboot bootloader
fastboot flash recovery "full name of the file extracted from the downloaded file inc it's extension"
fastboot reboot
then you could try flashing again
Click to expand...
Click to collapse
I tried and this recovery causes a constant vibrating when in recovery mode, apart from that I still get the same errors.
My only fast and easy solution would be if someone uploaded a B512 repack for TWRP. That would be awesome, right now I just use the B513 repack. I don't think I can find the fix to this any more.

[Q] Red Triangle error durin lolipop update due to mismatching build fingerprints

Hello you guys I have a s-on rooted M8,I am trying to apply an OTA update halfway through red triangle appears. When I go to the menu I can see the following error:
Package expects build fingerprint of htc/vodafone_uk/htc_m8:4.4.4/KTU84P/392065.9:user/release-keys or htc/vodafone_uk/htc_m8:5.0.1/LRX22C/457188:2user/release keys; this device has (my device's code)
As far as I can understand there is a mismatch of build fingerprints.
Without going s-off how can I fix it.
PS:I am still rooted but flashed custom recovery..
Many thanks in advance

Flash stock recovery..

It is stock recovery or let me say that way it is the recovery image which I used to apply last OTA

daneland said:
It is stock recovery or let me say that way it is the recovery image which I used to apply last OTA
Click to expand...
Click to collapse
You need the right stock recovery as mentioned in error log:
Package expects build fingerprint of htc/vodafone_uk/htc_m8:4.4.4/KTU84P/392065.9:user/release-keys or htc/vodafone_uk/htc_m8:5.0.1/LRX22C/457188:2user/release keys; this device has (my device's code)
this device has (my device's code) is not helping much without full description.
I suspect that your device has htc/vodafone_uk/htc_m8:4.4.4/KTU84P/392065.5 when the OTA needs 392065.9
Just use htc/vodafone_uk/htc_m8:5.0.1/LRX22C/457188:2 which you can get from the OTA.zip itself.
Copy the OTA.zip (sdcard\Download\) to PC, open it with 7-zip, then open firmware.zip, extract out the recovery.img from it. This is the one that you need.

ckpv5 said:
Just use htc/vodafone_uk/htc_m8:5.0.1/LRX22C/457188:2 which you can get from the OTA.zip itself.
Click to expand...
Click to collapse
Thank you so much for your reply.I dont want to be a pain but how can I download it manually or locate it after I downloaded through normal way of software update?

Copy the OTA.zip (sdcard\Download\) to PC, open it with 7-zip, then open firmware.zip, extract out the recovery.img from it. This is the one that you need.​
sdcard/Download is where the location of OTA.zip is downloaded to.
Download as usual with software update, when it ask to install select install later, then copy the OTA.zip to PC
Boot to bootloader (you know how to) to flash the extracted recovery.img
Reboot - do software update checking again (it will ask to download again, select download but actually it won't go the download process again .. the complete one will pop-up and ask to install now or later, select install now .. done

ckpv5 said:
Copy the OTA.zip (sdcard\Download\) to PC, open it with 7-zip, then open firmware.zip, extract out the recovery.img from it. This is the one that you need.​
sdcard/Download is where the location of OTA.zip is downloaded to.
Download as usual with software update, when it ask to install select install later, then copy the OTA.zip to PC
Boot to bootloader (you know how to) to flash the extracted recovery.img
Reboot - do software update checking again (it will ask to download again, select download but actually it won't go the download process again .. the complete one will pop-up and ask to install now or later, select install now .. done
Click to expand...
Click to collapse
I have the same issue, did the thing you said, didn't work..

Ricky757 said:
I have the same issue, did the thing you said, didn't work..
Click to expand...
Click to collapse
You may have different issue.
At the red triangle, press and hold volume button and tap power button once. You'll see error log
Read this : http://forum.xda-developers.com/htc-one-m8/help/failure-to-update-to-lollipop-t3016953

ckpv5 said:
You may have different issue.
At the red triangle, press and hold volume button and tap power button once. You'll see error log
Read this : http://forum.xda-developers.com/htc-one-m8/help/failure-to-update-to-lollipop-t3016953
Click to expand...
Click to collapse
I had the exact same errormessage. But apparently I relocked the bootloader so that was the reason I couldn't flash the stock recovery.. Silly me! haha anyway my problem is fixed. Thank you for your time and help!

[Q] Need some help to update

Hello,
if someone can help me a bit to upgrade my Zenfone 2 (Z008)
I used the one click tools to root it 2 months ago and now I want update the firmware.
So i used again the tool to unroot my phone and downloaded the last version of firmware : Z008-WW-2.19.40.23
I restart on recovery mode, get the error robot and restart recovery mode again
I chose "apply update from ADB" . I see my device when I type : adb devices but when I do : sideload myfile.zip I have a problem 'error: protocol fault'
EDIT: Finnaly its worked for the sideload but now i got an error with /system/app/asusbrower/asusbrower.ap .. during the verification -.-"
maybe because i have deleted some useless system apps :/ ?
what should i do? thanks

ERROR MODE Attention! Please update system again.

Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!

Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system

mrmazak said:
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
Click to expand...
Click to collapse
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore

Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
I give my phone to a friend to work on it. If he can't fix it I try new multi tools version to flash phone.

Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk

Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
I ever have similiar problem with you dude, but it's solved now, if you always stuck on " its OK but when my phone want to start its stuck on google page "just a sec...", its call google accont verification, i'll by bypass with this script, save as to .bat and put on adb folder
adb devices
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
adb shell am start -n com.google.android.gsf.login/
adb shell am start -n com.google.android.gsf.login.LoginActivity
pause
in fastboot type:
fastboot -w
after all it's works to me to bypass google account verification
and if now your problem is
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
i solve with re-flash system from this
https://androidfilehost.com/?fid=673956719939830152
fastboot flash system system.img
and doing TWRP Flashing
https://forum.xda-developers.com/devdb/project/?id=25826#downloads
fastboot flash recovery_ramdisk complete_twrp_ramdisk.img
and voila my problem solved..

mrmazak said:
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Click to expand...
Click to collapse
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (

Mohammadreza76646 said:
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Click to expand...
Click to collapse
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595

mrmazak said:
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
Click to expand...
Click to collapse
It have stock recovery.

Mohammadreza76646 said:
It have stock recovery.
Click to expand...
Click to collapse
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)

mrmazak said:
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
Click to expand...
Click to collapse
No. System boot successfully!
I will send you screenshot:

Mohammadreza76646 said:
No. System boot successfully!
I will send you screenshot:
Click to expand...
Click to collapse
here you are

Mohammadreza76646 said:
here you are
Click to expand...
Click to collapse
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.

mrmazak said:
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
Click to expand...
Click to collapse
Thanks )
I'm so sorry for my posts, it's because I don't have a stable connection and I can't see notification of my thread.
I gave my phone to friend an he fix IMEI (I don't know how)
But OEM is steel lock.
I think he did it with using special box.

Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!![/QUOTE
Are u able.to boot into twrp ?
Click to expand...
Click to collapse

Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?

IonDEfeso said:
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
Click to expand...
Click to collapse
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)

mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.

mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Do you know what the boot.img files name is after extraction?
I have extracted all 3 update zips and cannot find anything called boot.img
By the way, thank you.. After updating magisk I have been dealing with failed recovery and failed boot for over a week and this is the first reply anywhere that looks promising

IonDEfeso said:
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
Click to expand...
Click to collapse
if you were on oreo. then there is not a boot.img, instaed there is seperate ramdisk.img and kernel.img.
i have all the files already extracted for oreo and a backup from nougat as well.
https://androidfilehost.com/?w=files&flid=265998
make sure you know what you are doing before flashing.
for example. on oreo the boot and recovery share one kernel image. SO if kernel is messed up you will not be able to boot "boot" or "recovery"

How to Root Your Samsung Galaxy A10 + Install Twrp

READ EVERYTHING CAREFULLY!
1.Your phone warranty will be void after this tutorial!
2.Any small mistake and your phone is bricked/bootlooped!
3.All of your data will be lost so back it up somewhere
Click to expand...
Click to collapse
(Fixed the tutorial my bad.)
Click to expand...
Click to collapse
Hey Guys Im Back! Thank you for the support and how it blew up. I have tested this on Android 10 UI 2.0 and it works better then ever!
Also installed lineage os : https://forum.xda-developers.com/galaxy-a10/development/rom-lineage-os-a10-a105f-t4078093
So i tried using afaneh92's tutorial which will be linked here : https://forum.xda-developers.com/galaxy-a10/how-to/magisk-root-galaxy-a10-series-t3963822
Which lead to me bootlooping or softbricking and my storage was reduced from 32 gb to 16Gb so i decided to work on my own method!
Credits go to afaneh92 for the Twrp!
BEFORE YOU START YOU SHOULD HAVE
1.Samsung Drivers installed
2.Odin Installed
3.7zip Installed
4.A data transfer cable
5.A Proper working brain
If you have all of those lets start!
A: Phone settings
1.Go in settings>about phone>software information>build number tap that 5 times until it says "You are a developer now" then you will have Developer options unlocked
2.Then go in developer functions and find OEM unlocking tick that on scroll down until you see Usb Debugging and tick that also Disable Auto Updates option
B: Download TWRP and 2 other important files
1.Dial *#1234# and it will show the AP and some others, focus on AP paste it on google and get the download for it
2.After downloaded move the AP to your download folder in your android device
3.You will get a magisk_patched.tar after its been offically converted
4.Get the twrp for a10
Download the twrp file here : https://mega.nz/#!OU1WhSDZ!vQz5K1wpqBhg0hCD59aziaHPxFlUsT_2WG8SgT8p6iY
5.After you got everything open the .tar archive and extract vbmeta.img, boot.img and you should already have recovery.img on your Desktop
6.Grab all the 3 .img files and archive them into a .tar using 7zip, Now continue to step C,
C :Unlocking The Bootloader and Getting Into Download Mode (THE PART WHERE YOU RESET YOUR PHONE)
1.Turn Off your phone
1.2.Put your data cable into your PC(dont connect your phone to it yet)
1.3.Hold Volume Up and Down then insert the cable into your phone
1.4.When you see a bluescreen let go
1.5.Hold vol up until you see another screen then let go for 1 second and hold vol up again
2.Your device will reset itself and reboot
2.1.After the device has booted in into the setup take the cable out after Turn off your phone
2.2.Hold Vol Up and Down again and connect the cable
2.3.Let go when a blue screen appears then press vol up until you are in download mode
D: Flashing TWRP
1.Open Odin
2.Press on AP then find Desktop.tar and press open
3.Press start and let it do its thing
4.After your Phone has rebooted you oficially have TWRP installed
5.If you want to know hoe to root go to step E
E: Installing Magisk
Since magisk is counted as the best rooting option rn i will be using it in this tutorial(Sorry supersu fans)
1.Install Magisk Manager
2.Press on Install (first one) then press install again and after that press Install Zip Only
3.Then go into Twrp by doing the steps below
3.1.Turn off your device
3.2.Hold vol up and power button untill you see TWRP logo
4.Press install
4.1.Find magisk-v20.4(20400).zip
4.2Swipe right on the bottom to flash it then press reboot system now.
5.Now you have TWRP,Root and Magisk Congratulations!
What happens if something goes wrong.
1.SV Error Device 1 library 0 - You installed the wrong firmware look for the right firmware.To check go in recovery mode and look at the A105XXXXXX and then look for a download. Remider AP->AP BL->BL CP->CP HOME_CSC->CSC
2.vbmeta.img error - you have the wrong vbmeta.img file. Redownload the original firmware and take out the right vbmeta.img next time you try flashing. Reminder AP->AP BL->BL CP->CP HOME_CSC->CSC
3.A blue screen telling you to use samsung switch emergency update. That wont work so just flash the original firmware and try flashing twrp again.
4.When i try to boot in it gets me into TWRP - Thats just because that your data is corrupted and to fix it while in TWRP mode press wipe then swipe after its done press Reboot To System. That should be a fix
5.My internal storage is just full of weird numbers and I can't download anything on it! Go in TWRP then wipe,press advanced wipe, click on internal storage and data, swipe. That should fix the error
6.Boootlooping or Bricked! Installed corrupted firmware or the recovery was f-ed up. Then install the right firmware and redo the steps!
If you have issues during the process send it in the comment ill try to respond as fast as i can!

i notice thread title says exynos only.. u do know they are all exynos including a102u and a102u1 right?

Oh. Alright thanks for telling me.

Press on app? I have nothing in odin saying that, do you mean ap?
Edit: guess not....i'm bricked, stuck on galaxy logo, device not recognized by pc, holoding power button wont force reboot, nothing lol.
Edit2: can force reboot holding volume down and power but instantly stuck on logo again, cannot power off or enter download, nothing...bricked. Followed this guide to the letter. I assumed when you said app in odin you meant ap since there is no app button. My bootloader unlocked then I went to flash in odin the tar i made with patched boot and vbmeta, along with recovery linked. I used matching firmware to what my A10 has also. Would not mind if i could get back into download mode, but that looks impossible now.
Edit3: Managed to get download mode but had to be so quick...hopefully I can reflash stock now.

Cupcake 1.5 said:
Press on app? I have nothing in odin saying that, do you mean ap?
Edit: guess not....i'm bricked, stuck on galaxy logo, device not recognized by pc, holoding power button wont force reboot, nothing lol.
Edit2: can force reboot holding volume down and power but instantly stuck on logo again, cannot power off or enter download, nothing...bricked. Followed this guide to the letter. I assumed when you said app in odin you meant ap since there is no app button. My bootloader unlocked then I went to flash in odin the tar i made with patched boot and vbmeta, along with recovery linked. I used matching firmware to what my A10 has also. Would not mind if i could get back into download mode, but that looks impossible now.
Edit3: Managed to get download mode but had to be so quick...hopefully I can reflash stock now.
Click to expand...
Click to collapse
Im sorry for that and yes i meant AP.
If you wanted to reboot you had to hold vol up vol down and power at the same time and you sure that you unlocked the bootloader and used the right firmware?
Also tell me the AP and from which source have you downloaded it :laugh:

cmz6996 said:
Im sorry for that and yes i meant AP.
If you wanted to reboot you had to hold vol up vol down and power at the same time and you sure that you unlocked the bootloader and used the right firmware?
Also tell me the AP and from which source have you downloaded it :laugh:
Click to expand...
Click to collapse
All sorted now, back on stock with twrp and root It was a schoolboy error by me, the firmware downloaded was corrupted lol.

Cupcake 1.5 said:
All sorted now, back on stock with twrp and root It was a schoolboy error by me, the firmware downloaded was corrupted lol.
Click to expand...
Click to collapse
Oh! Im happy to hear that!

Cupcake 1.5 said:
All sorted now, back on stock with twrp and root It was a schoolboy error by me, the firmware downloaded was corrupted lol.
Click to expand...
Click to collapse
Could you also tell me from where have you downloaded the corrupted firmware so i can warn the others?

cmz6996 said:
Could you also tell me from where have you downloaded the corrupted firmware so i can warn the others?
Click to expand...
Click to collapse
The corruption was my side, I was using a download manager, but when I downloaded through chrome it was all good. As I said, schoolboy error on my part for not checking md5. I used sammobile site for the firmware.

Cupcake 1.5 said:
The corruption was my side, I was using a download manager, but when I downloaded through chrome it was all good. As I said, schoolboy error on my part for not checking md5. I used sammobile site for the firmware.
Click to expand...
Click to collapse
Alr thanks.

Can you upload it to Mediafire? Mega marks a "temporal error"...

Kyua said:
Can you upload it to Mediafire? Mega marks a "temporal error"...
Click to expand...
Click to collapse
At me it works?

Works on a105m?

Axeggus said:
Works on a105m?
Click to expand...
Click to collapse
Yes

i receive message that i running samsumg not official firmware after odin install recovery.tar

not work
cmz6996 said:
So i tried using afaneh92's tutorial which will be linked here : https://forum.xda-developers.com/galaxy-a10/how-to/magisk-root-galaxy-a10-series-t3963822
Which lead to me bootlooping or softbricking and my storage was reduced from 32 gb to 16Gb so i decided to work on my own method!
Credits go to afaneh92 for the Twrp!
BEFORE YOU START YOU SHOULD HAVE
1.Samsung Drivers installed
2.Odin Installed
3.7zip Installed
4.A data transfer cable
5.A Proper working brain
If you have all of those lets start!
A: Phone settings
1.Go in settings>about phone>software information>build number tap that 5 times until it says "You are a developer now" then you will have Developer options unlocked
2.Then go in developer functions and find OEM unlocking tick that on scroll down until you see Usb Debugging and tick that also Disable Auto Updates option
B: Download Your firmware and TWRP
1.Go in your calls app and dial *#1234# Then You will receive some details about your AP, CP etc. look at the AP then download the firmware by searching it on google and (download it from sites like sammobile etc)
2.After you got your firmware connect your device to your pc after its connected send the entire firmware to the device in the Downloads folder
2.1. Install Magisk Manager
3.After you're in magisk manager press on install (first one) then press install again then press Select and Patch a File
3.1.Chose the firmware you saved on the Downloads folder
3.2.After you tap on it it should've already started modifying it
4.After it finished go back to your pc and move the magisk_patched.tar back to your desktop (It should be located in Downloads)
5.From the magisk_patched.tar extract boot.img and vbmeta.img to your desktop
5.1.Download the twrp file here : https://mega.nz/#!OU1WhSDZ!vQz5K1wpqBhg0hCD59aziaHPxFlUsT_2WG8SgT8p6iY
5.2.After recovery.img(TWRP) has been downloaded move it to your desktop
5.3.Select all those three items(vbmeta.img,recovery.img,boot.img) right click then Find 7Zip then press add to archive
5.4.Rename the Archive name to recovery.tar and make sure the archive format is .tar
6.After the Archive has been downloaded follow the steps in C
C :Unlocking The Bootloader and Getting Into Download Mode (THE PART WHERE YOU RESET YOUR PHONE)
1.Turn Off your phone
1.2.Put your data cable into your PC(dont connect your phone to it yet)
1.3.Hold Volume Up and Down then insert the cable into your phone
1.4.When you see a bluescreen let go
1.5.Hold vol up until you see another screen then let go for 1 second and hold vol up again
2.Your device will reset itself and reboot
2.1.After the device has booted in into the setup take the cable out after Turn off your phone
2.2.Hold Vol Up and Down again and connect the cable
2.3.Let go when a blue screen appears then press vol up until you are in download mode
D: Flashing TWRP
1.Open Odin
2.Press on AP then find recovery.tar and press open
3.Press start and let it do its thing
4.After your Phone has rebooted you oficially have TWRP installed
5.If you want to know hoe to root go to step E
E: Installing Magisk
Since magisk is counted as the best rooting option rn i will be using it in this tutorial(Sorry supersu fans)
1.Install Magisk Manager
2.Press on Install (first one) then press install again and after that press Install Zip Only
3.Then go into Twrp by doing the steps below
3.1.Turn off your device
3.2.Hold vol up and power button untill you see TWRP logo
4.Press install
4.1.Find magisk-v20.4(20400).zip
4.2Swipe right on the bottom to flash it then press reboot system now.
5.Now you have TWRP,Root and Magisk Congratulations!
What happens if something goes wrong.
1.SV Error Device 1 library 0 - You installed the wrong firmware look for the right firmware.To check go in recovery mode and look at the A105XXXXXX and then look for a download. Remider AP->AP BL->BL CP->CP HOME_CSC->CSC
2.vbmeta.img error - you have the wrong vbmeta.img file. Redownload the original firmware and take out the right vbmeta.img next time you try flashing. Reminder AP->AP BL->BL CP->CP HOME_CSC->CSC
3.A blue screen telling you to use samsung switch emergency update. That wont work so just flash the original firmware and try flashing twrp again.
4.When i try to boot in it gets me into TWRP - Thats just because that your data is corrupted and to fix it while in TWRP mode press wipe then swipe after its done press Reboot To System. That should be a fix
5.My internal storage is just full of weird numbers and I can't download anything on it! Go in TWRP then wipe,press advanced wipe, click on internal storage and data, swipe. That should fix the error
6.Boootlooping or Bricked! Installed corrupted firmware or the recovery was f-ed up. Then install the right firmware and redo the steps!
If you have issues during the process send it in the comment ill try to respond as fast as i can!
Click to expand...
Click to collapse
hi guy... very good guide but it not work for my galaxy a10 ....i only have unlock the bootloader... if i try to get patched recovery ... it not work.... i have device blocked black screen for samsung software... or i cant go recovery mode it say me a error of vbmeta)

andrea2o18 said:
hi guy... very good guide but it not work for my galaxy a10 ....i only have unlock the bootloader... if i try to get patched recovery ... it not work.... i have device blocked black screen for samsung software... or i cant go recovery mode it say me a error of vbmeta)
Click to expand...
Click to collapse
You installed the wrong fir.ware check your right firmware.

BlueFolks said:
i receive message that i running samsumg not official firmware after odin install recovery.tar
Click to expand...
Click to collapse
Be cause you modified the firmware ignore that message

have you fixed the storage reduced to 16gb problem?

I have a Samsung galaxy sm-a10. I've tried everything here, even combination files. The error I ALWAYS get is 'failed flashing ROM... OEM lock'
Of course I have unlocked OEM in developer options, but still I get this error in the bootloader.
Any ideas?