My phone is stuck at Samsung Logo I have tried (Stock firmware, wipe data, factory reset nothing works) and the recovery gives the error mentioned in the title.
failed to mount /efs (invalid argument) . I have tried various methods but nothing worked. Anyone have idea how to solve this issue ?
Try smart switch also.
Punitverma2010 said:
Try smart switch also.
Click to expand...
Click to collapse
I have tried smart switch but i am not getting device initialization option in updated version. How ever i have downloaded an older version and found device initialization option it asked me for device model and serial number. I have entered correct information still it is giving me error invalid model number or serial Number.
fahad4210 said:
I have tried smart switch but i am not getting device initialization option in updated version. How ever i have downloaded an older version and found device initialization option it asked me for device model and serial number. I have entered correct information still it is giving me error invalid model number or serial Number.
Click to expand...
Click to collapse
I think going to Samsung service centre might help.
Do you have twrp installed?
Rooted.ndroid said:
Do you have twrp installed?
Click to expand...
Click to collapse
When i am installing TWRP it says Only official binaries are allowed to be flashed.
fahad4210 said:
When i am installing TWRP it says Only official binaries are allowed to be flashed.
Click to expand...
Click to collapse
tried downgrading to 8.1.0?
did your developer option have oem unlocking option? Its that even if unlock bootloader but if your developer option doesn't show oem is already unlocked then it says that to me as well.
But hey I don't know everything you have done, you might have done everything correctly still it screwed you. Best of luck bud.
if you dont mind what happens when you flash the firmware?
Rooted.ndroid said:
tried downgrading to 8.1.0?
did your developer option have oem unlocking option? Its that even if unlock bootloader but if your developer option doesn't show oem is already unlocked then it says that to me as well.
But hey I don't know everything you have done, you might have done everything correctly still it screwed you. Best of luck bud.
if you dont mind what happens when you flash the firmware?
Click to expand...
Click to collapse
My device is stuck at samsung logo and it is not booting. I have tried to downgrade it to 8.1.0 with odin and it was successfully done.
But issue remains the same. Hence it is not booting so i am not able to unlock OEM. I am getting error in recovery that is E: failed to mount /efs (invalid argument) . Somehow i found a threat with a solution and for that i need to install TWRP in my device.
fahad4210 said:
My device is stuck at samsung logo and it is not booting. I have tried to downgrade it to 8.1.0 with odin and it was successfully done.
But issue remains the same. Hence it is not booting so i am not able to unlock OEM. I am getting error in recovery that is E: failed to mount /efs (invalid argument) . Somehow i found a threat with a solution and for that i need to install TWRP in my device.
Click to expand...
Click to collapse
I needed to tweak date to make OEM unlocking: Bootloader is already unlocked on developer options after flashing stock rom of other region but for my exact region it appears each time and I dont need to boot to rom to flash twrp, I can flash the ROM and twrp simultaneously only in my device's original firmware(8.1.0) but not in rom of any other region and on pie.
I hope I'm not annoying you, could you try flashing 8.1.0 by unticking auto reboot ----- force reboot ---- odin --- twrp.
Edit: this thing doesn't make sense.
Rooted.ndroid said:
I needed to tweak date to make OEM unlocking: Bootloader is already unlocked on developer options after flashing stock rom of other region but for my exact region it appears each time and I dont need to boot to rom to flash twrp, I can flash the ROM and twrp simultaneously only in my device's original firmware(8.1.0) but not in rom of any other region and on pie.
I hope I'm not annoying you, could you try flashing 8.1.0 by unticking auto reboot ----- force reboot ---- odin --- twrp.
Click to expand...
Click to collapse
Thanks for guidance and for helping me. I will update you once it done. Hope this will resolve my problem
Rooted.ndroid said:
I needed to tweak date to make OEM unlocking: Bootloader is already unlocked on developer options after flashing stock rom of other region but for my exact region it appears each time and I dont need to boot to rom to flash twrp, I can flash the ROM and twrp simultaneously only in my device's original firmware(8.1.0) but not in rom of any other region and on pie.
I hope I'm not annoying you, could you try flashing 8.1.0 by unticking auto reboot ----- force reboot ---- odin --- twrp.
Click to expand...
Click to collapse
I have tried as you guided my but still i am not able to install TWRP in my device
Flash with odin the correct firmware be aware of U1 or U2 firmware i don't know what u have installed on ur phone.
if it doesn't work flash combination file u will get (factory binary) the u flash the original stock rom for ur smartphone.
Worked for me .:good:
Related
Hi Guys,
I stupidly did not realise my device (XT1072) was a different slightly different model to the moto g 2014.
I unlocked the bootloader and installed TWRP, then tried to install Cyanogenmod 12.1, this failed giving an error "Error executing updater binary in zip" Which I guess is due to it being a different model, right? After receiving this error I did some googling and found on a few sites that I should wipe data, system, cache & dalvik cache to resolve this. I did this and tried to flash it again, with the same error. Now my phone is stuck on the "warning bootloader unlocked screen" I can boot into fastboot mode, but is there any official Motorola images for my device anywhere? I have had a look online and cant find anything. :crying:
Any help would be much appreciated.
Thanks
Format system is completely wipe previous android version,
You need a custom ROM (I'm assuming you have custom recovery for your device model)
Or fastboot a original image for you're device
Hi
ohmygoddude said:
Hi Guys,
I stupidly did not realise my device (XT1072) was a different slightly different model to the moto g 2014.
I unlocked the bootloader and installed TWRP, then tried to install Cyanogenmod 12.1, this failed giving an error "Error executing updater binary in zip" Which I guess is due to it being a different model, right? After receiving this error I did some googling and found on a few sites that I should wipe data, system, cache & dalvik cache to resolve this. I did this and tried to flash it again, with the same error. Now my phone is stuck on the "warning bootloader unlocked screen" I can boot into fastboot mode, but is there any official Motorola images for my device anywhere? I have had a look online and cant find anything. :crying:
Any help would be much appreciated.
Thanks
Click to expand...
Click to collapse
Hi,
I am facing exactly the same problem here. Could you please let me know if you find any solution!!! please
Thanks
omarhowlader said:
Hi,
I am facing exactly the same problem here. Could you please let me know if you find any solution!!! please
Thanks
Click to expand...
Click to collapse
You might want to take a look at this thread: http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3054303
omarhowlader said:
Hi,
I am facing exactly the same problem here. Could you please let me know if you find any solution!!! please
Thanks
Click to expand...
Click to collapse
Hi,
I too faced this issue. I've seen this error mostly with the Team Win Recoveries(TWRP). Switch to philiz recovery touch.
Still no luck
kishorebvs said:
Hi,
I too faced this issue. I've seen this error mostly with the Team Win Recoveries(TWRP). Switch to philiz recovery touch.
Click to expand...
Click to collapse
Hi,
Thank you for your reply. I also tried with CWM_Touch_Titan_v2 recovery image. But when I tried to flash the stock rom RETGBALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml using mfastboot method, it shows on the phone screen "image too large".
As you have faced the same problem, would you be kind enough to give a step by step instruction to solve the issue. My phone is just stuck to unlocked bootloader warning screen for days.
My phone is Moto g XT1072 4G LTE.
Your help could save my days...
Thanks.
omarhowlader said:
Hi,
Thank you for your reply. I also tried with CWM_Touch_Titan_v2 recovery image. But when I tried to flash the stock rom RETGBALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml using mfastboot method, it shows on the phone screen "image too large".
As you have faced the same problem, would you be kind enough to give a step by step instruction to solve the issue. My phone is just stuck to unlocked bootloader warning screen for days.
My phone is Moto g XT1072 4G LTE.
Your help could save my days...
Thanks.
Click to expand...
Click to collapse
Why are u flashing an xml file? XML files are not rom files
The link provided above by mic_he has step by step instructions to restore phone back to stock
Your phone is not bricked. You deleted your system so there is no os to boot. The link should restore you back to stock
mic_he said:
You might want to take a look at this thread: http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3054303
Click to expand...
Click to collapse
Thank you,
I have tried those instruction earlier. when I enter "mfastboot flash bootloader bootloader.img" is says "Bootloader preflash validation failed" and when I enter "mfastboot flash system system.img_sparsechunk.0" onthe phone screen is says "Image too large". After going through all the steps when I reboot, it does not ever get past unlocked bootloader warning screen.
I really do not know which other option to try??
---------- Post added at 07:30 PM ---------- Previous post was at 07:26 PM ----------
Moto G User said:
Why are u flashing an xml file? XML files are not rom files
The link provided above by mic_he has step by step instructions to restore phone back to stock
Your phone is not bricked. You deleted your system so there is no os to boot. The link should restore you back to stock
Click to expand...
Click to collapse
I could not find any zip file of the stock rom. I downloaded the stock rom from that link but I am having error as i posted earlier.
Thanks
ohmygoddude said:
Hi Guys,
I stupidly did not realise my device (XT1072) was a different slightly different model to the moto g 2014.
I unlocked the bootloader and installed TWRP, then tried to install Cyanogenmod 12.1, this failed giving an error "Error executing updater binary in zip" Which I guess is due to it being a different model, right? After receiving this error I did some googling and found on a few sites that I should wipe data, system, cache & dalvik cache to resolve this. I did this and tried to flash it again, with the same error. Now my phone is stuck on the "warning bootloader unlocked screen" I can boot into fastboot mode, but is there any official Motorola images for my device anywhere? I have had a look online and cant find anything. :crying:
Any help would be much appreciated.
Thanks
Click to expand...
Click to collapse
Unmounting system before flashing usually stops that problem. What I like to do is wipe data, system, cache & dalvik then reboot to recovery before flashing the rom.
Sent from my GT-P5210 using Tapatalk
could you solve the problem with the XT1072?
hello sir! could you solve the problem with thw XT1072? Can you give me some instructions? cheers
It works!!!!! I could restore my system back with these steps!
Here´s the info
http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3054303
I followed the steps and when I was triyng to Flash each of the partitions in sequence using mfastboot get an error
I get an error with one of the files, (don´t remember now but I think was with the mfastboot flash logo logo.bin line
This give me an error, try to fix it and i couldn´t so I continue with the other files in the order listed and when the process was finished the phone was working again!!!!
Enter twrp recovery
Wipe system data cache dalvik
Put any rom like cm in microsd card or usb
And flash it using twrp
ohmygoddude said:
Hi Guys,
I stupidly did not realise my device (XT1072) was a different slightly different model to the moto g 2014.
I unlocked the bootloader and installed TWRP, then tried to install Cyanogenmod 12.1, this failed giving an error "Error executing updater binary in zip" Which I guess is due to it being a different model, right? After receiving this error I did some googling and found on a few sites that I should wipe data, system, cache & dalvik cache to resolve this. I did this and tried to flash it again, with the same error. Now my phone is stuck on the "warning bootloader unlocked screen" I can boot into fastboot mode, but is there any official Motorola images for my device anywhere? I have had a look online and cant find anything. :crying:
Any help would be much appreciated.
Thanks
Click to expand...
Click to collapse
Hi, I have facing this problem too on my XT1063. My phone do boot to system but all the app are getting FCs, so I decided to flash another ROM like usual and All of this give me that "Error executing updater binary in zip", so I trie to wipe AND format all partition from TWRP and FASTBOOT with no success. Via Fastboot says: "File system type raw not supported." So I cant change to a new ROM, I cannot even flash other recovery....
So if you guys find a solution of this problem very users like me will be very thankful.
Welcome everyone!
This thread has been created for extreme newbies/noobs and for their benefit. Not only noobs, but everyone is free to post questions and also give answers to those questions. Any type of question is allowed as long as it is related about the device. No off-topic discussions are allowed!
Hit Thanks if I Helped You!!!
Regards,
PoseidonKing
Honor 4x hanged (in some Indian kitkat version, not rooted) and after restart it is in bootloop. Honor logo appears then blue light starts to appear then restart.
Recovery mode and dload update not working.
After unlocking bootloader tried fastboot -w, still in bootloop.
Extracted Lollipop, Marshmallow, Kitkat - B161, B126 and flashed in fastboot. Possible to flash only recovery, boot, userdata & system. For others - failed : remote command not allowed. After flashing no change, still in bootloop.
Tried to boot to recovery from fastboot boot
- for lollipop and marshmallow recoveries it says "dtb not found"
- others including twrp, cm it is in bootloop.
Out of warranty.
Need help.
oppili said:
Honor 4x hanged (in some Indian kitkat version, not rooted) and after restart it is in bootloop. Honor logo appears then blue light starts to appear then restart.
Recovery mode and dload update not working.
After unlocking bootloader tried fastboot -w, still in bootloop.
Extracted Lollipop, Marshmallow, Kitkat - B161, B126 and flashed in fastboot. Possible to flash only recovery, boot, userdata & system. For others - failed : remote command not allowed. After flashing no change, still in bootloop.
Tried to boot to recovery from fastboot boot
- for lollipop and marshmallow recoveries it says "dtb not found"
- others including twrp, cm it is in bootloop.
Out of warranty.
Need help.
Click to expand...
Click to collapse
Oh ****, that seems like a frustrating situation. What made the device mess up so much? Have you gone to service centres?
Regards,
PoseidonKing
Not tried to flash or root. It just hanged while using.
Service centre said board gone (as always). MTK devices have a factory mode through which we can check working of all board parts. I did not find any way for this.
oppili said:
Not tried to flash or root. It just hanged while using.
Service centre said board gone (as always). MTK devices have a factory mode through which we can check working of all board parts. I did not find any way for this.
Click to expand...
Click to collapse
Sorry bro, can't help you out over here in this situation.... Best of Luck regarding your device. I would suggest pm'ing a forum moderator for your issue
Hit Thanks if I Helped You!!!
Regards,
PoseidonKing
HELP.!!Back to Stock Rom ????
I am struggling like anything to go back to stock rom. I am using Honor 4x Che1-L04 snapdragon. Pls send a link where can i find the instructions to do this. Or Better U expain.
EDIT:
Roll back to EMUI 4.0 success. Used the Hauwei update extractor and used CMD. Anyhow THANKS
NEW Problem:
How to enable ADOPTED STORAGE in honor 4x che1-L04 snapdragon edition.
In Xda they mentioned only about the kirin processor version.
Help!!!!!!!!!!
balongc52b311 after failing kangvip 6.7.1
hey there. will tell you my experience with failing to flashing kangvip 6.7.1 due to wiping problem
i wiped my cache, data, system even internal storage and yet failed to flashing kangvip 6.7.1 4 custom rom due to "cust" folder unable to mount giving me this:
error 1 can't mount /cust (Invalid argument)
so after failing to mount that folder and even deleting it by mistake,i got a new error:
error 1 can't mount cust no such file or directory
i lost hope and let my my honor 4x normally boot but it took too long and i was determined its stuck on bootloop :cyclops:
i woke up today finding it on 5% battery and giving me that first time setup as if all i did was a factory format BUT all in chinese. checked the build number and it was balongc52b311.
i tried mounting "cust" folder to r/w and rebooted into bootloader but it gave me the same first error. i tried deleting the folder and then rebooting into recovery and it gave me the 2nd error. created the folder "/cast" and then rebooted into recovery and it gave me the same first problem that the folder can't mount EVENTHO it was mounted successfully right before i rebooted into recovery (did this 3 times to make sure)
did some researching and found a solution for honor 4c http://forum.xda-developers.com/honor-4x/help/huawei-honor-4x-balong-hi6210sft-fixed-t3324335 or two BUT both for lolllipop and i'm marshmallow.
i'm already halfway at the method i mentioned above but i stopped after i realized it was for lollipop. i rooted my mobile and changed my build number to "Che2-L11C636B330". worth to mention that my model number remained already the same "Che2-L11".
the cust folder error is still there whenever i go to the bootloader
now i have no idea what to do, what firmware to download and if i have to downgrade first to lollipop and then upgrade to marshmallow again...
my marshmallow version was the middle east final version before this balong happened: Che2-L11C185B561 and i would like to go back to it again.. thank you in advance ( :
###*UPDATED BELOW*
fixed my problem trying the method here http://forum.xda-developers.com/honor-8/help/honor-8-rooted-twrp-modaco-rom-unable-t3462039/page2
>>>>worth to mention that i flashed my oeminfo for my UPDATE.APK REGION before flashing the extracted files from UPDATE.APP "wasn't mentioned in that method"
now i'm back to my original marshmallow version "middle east". good luck people.
abdurrahmanzaki said:
hey there. will tell you my experience with failing to flashing kangvip 6.7.1 due to wiping problem
i wiped my cache, data, system even internal storage and yet failed to flashing kangvip 6.7.1 4 custom rom due to "cust" folder unable to mount giving me this:
error 1 can't mount /cust (Invalid argument)
so after failing to mount that folder and even deleting it by mistake,i got a new error:
error 1 can't mount cust no such file or directory
i lost hope and let my my honor 4x normally boot but it took too long and i was determined its stuck on bootloop :cyclops:
i woke up today finding it on 5% battery and giving me that first time setup as if all i did was a factory format BUT all in chinese. checked the build number and it was balongc52b311.
i tried mounting "cust" folder to r/w and rebooted into bootloader but it gave me the same first error. i tried deleting the folder and then rebooting into recovery and it gave me the 2nd error. created the folder "/cast" and then rebooted into recovery and it gave me the same first problem that the folder can't mount EVENTHO it was mounted successfully right before i rebooted into recovery (did this 3 times to make sure)
did some researching and found a solution for honor 4c http://forum.xda-developers.com/honor-4x/help/huawei-honor-4x-balong-hi6210sft-fixed-t3324335 or two BUT both for lolllipop and i'm marshmallow.
i'm already halfway at the method i mentioned above but i stopped after i realized it was for lollipop. i rooted my mobile and changed my build number to "Che2-L11C636B330". worth to mention that my model number remained already the same "Che2-L11".
the cust folder error is still there whenever i go to the bootloader
now i have no idea what to do, what firmware to download and if i have to downgrade first to lollipop and then upgrade to marshmallow again...
my marshmallow version was the middle east final version before this balong happened: Che2-L11C185B561 and i would like to go back to it again.. thank you in advance ( :
###*UPDATED BELOW*
fixed my problem trying the method here http://forum.xda-developers.com/honor-8/help/honor-8-rooted-twrp-modaco-rom-unable-t3462039/page2
>>>>worth to mention that i flashed my oeminfo for my UPDATE.APK REGION before flashing the extracted files from UPDATE.APP "wasn't mentioned in that method"
now i'm back to my original marshmallow version "middle east". good luck people.
Click to expand...
Click to collapse
Thanks on the update about your success on restoring your phone. Surely some poor soul will get along the same problem and your post will help him out. Sorry for the late reply btw.
Hit Thanks if I Helped You!!!
Regards,
PoseidonKing
How to Root my honor 4x Che2-L11?
Hi everyone, I'm noob, so I need a step to step guide if there's such a thing
my android version is 6.0 and EMUI 4.0
I have bootloader code for unlocking the phone, thanks in advance guys, also happy new year :good:
Phone Honor 4x (che1-L04) Stuck in fastboot mode
My phone is stuck in fastboot mode. Couldn't get the bootloader unlock key online as it requires the product id which can be obtained by dialing a number which isn't possible. I have requested directly from the customer care number and the official chat portal as well but its been more than a week and still they are asking for 24 working hours. Is there any alternative method of getting the key or atleast the Product ID?
Model name :Che1-L04
Stuck in Fastboot & Rescue mode with the bootloader locked.
I got unlock key after 12 days. Honor 4x hanged after restart it is in bootloop.
3 button sd card update not working ?
oppili said:
I got unlock key after 12 days. Honor 4x hanged after restart it is in bootloop.
3 button sd card update not working ?
Click to expand...
Click to collapse
No the update.app isnt working I guess because I have already flashed the CM13 recovery image with the bootloader locked. However, I recieved the bootloader key yesterday from the email but when I tried unlocking by the fastboot command it said it is an invalid or wrong key. Is there any other way to take my phone back to stock condition atleast without actually unlocking the Bootloader?
Princeshubh said:
No the update.app isnt working I guess because I have already flashed the CM13 recovery image with the bootloader locked. However, I recieved the bootloader key yesterday from the email but when I tried unlocking by the fastboot command it said it is an invalid or wrong key. Is there any other way to take my phone back to stock condition atleast without actually unlocking the Bootloader?
Click to expand...
Click to collapse
1. Try "fastboot continue" it will directly boot without going to recovery.
2. If fastboot flash works flash recovery of the firmware installed in phone before bootloop.
3. If still not works flash boot, system, recovery (in this order) of firmware installed before bootloop.
Confirm unlock key with customer care if it is still locked.
I wanna know is there any other method to install xposed framework since the normal installation is not working for me.
Using Honor 4x Che1-l04 running on (stock ROM) Android marshmallow 6.0.1, have TWRP custom recovery and is rooted.
SumitGupta2442 said:
I wanna know is there any other method to install xposed framework since the normal installation is not working for me.
Using Honor 4x Che1-l04 running on (stock ROM) Android marshmallow 6.0.1, have TWRP custom recovery and is rooted.
Click to expand...
Click to collapse
no other way, unfortunatly.. one way or the other, you have to flash the zip...
ps: if you are on emui, first boot after flashing xposed will take a really long time.. mine took around 25 minutes to boot.. so dont consider it a boot loop, wait untill 30 minutes and you will be profitted
Mine was in boot screen for around 3 minutes and then rebooted into recovery. Same thing was happening again and again. So at last did the restore process from TWRP.
oppili said:
1. Try "fastboot continue" it will directly boot without going to recovery.
2. If fastboot flash works flash recovery of the firmware installed in phone before bootloop.
3. If still not works flash boot, system, recovery (in this order) of firmware installed before bootloop.
Confirm unlock key with customer care if it is still locked.
Click to expand...
Click to collapse
Its not working. Please help me I am still stuck....any way of installing the stock ROM back via fastboot mode with the phone showing 'Phone Locked'
Restoring TOO MUCH with twrp?
Can restoring too much with TWRP damage my phone?
jwalker9715 said:
Can restoring too much with TWRP damage my phone?
Click to expand...
Click to collapse
not really..
Is there anyway to flash TWRP as official binary? Gets blocked due to OEM lock
I messed up my Note8 SM-N950F, locked OEM flashed with odin to stock now in bootloop. Says EFS cant be mounted. DM-Verity error. I dont know what to do. :crying:
mohiminul said:
Is there anyway to flash TWRP as official binary? Gets blocked due to OEM lock
I messed up my Note8 SM-N950F, locked OEM flashed with odin to stock now in bootloop. Says EFS cant be mounted. DM-Verity error. I dont know what to do. :crying:
Click to expand...
Click to collapse
No you cant flash twrp as official binary. Can you get back to download mode and flash stock firmware?
sefrcoko said:
No you cant flash twrp as official binary. Can you get back to download mode and flash stock firmware?
Click to expand...
Click to collapse
Yes, but as soon as flashing is finished the device reboots to recovery and shows error failed to mount efs nd dm-verity verification failed. Downloaded firmware with Samfirm tool.
mohiminul said:
Yes, but as soon as flashing is finished the device reboots to recovery and shows error failed to mount efs nd dm-verity verification failed. Downloaded firmware with Samfirm tool.
Click to expand...
Click to collapse
Ok I see. Hmm not sure...I googled and found this thread that has a few solutions (Kies, Smart Switch, etc.) that seem to resolve the issue. If someone knows for sure they can chime in, but in the meantime I would start here (even though it's for Note 4...might still work, or at least point you in the right direction).
https://forum.xda-developers.com/note-4/help/dm-verity-verification-failed-recovery-t2945531
This thread may help.
https://forum.xda-developers.com/ga...-hard-bricked-note-8-sm-t3735009/post75195355
Hi guys. I tried to see other threads but I haven't fint anything. Probably there is but I'm beginner and I don't understand so much Anyway this is the problem:
model LLD-L31
build number LLD-L31 8.0.0.133(C432)
FPR unlocked
bootloader unloced
I tried to install root(Magisk-v16.4) in my device. So I unlocked bootloader, installed TWPR(Pretorian80 2.3.1) successfully but this error "Failed to unmount '/system'(Device or resource busy)" appeared. So I try to format data by recovery hoping that it could be able to read partitions after that. I couldn't yet flash file.Zip so I tried to upgrade Twpr in latest version installing it in recovey ramdisk.
After that I'm not able anymore to get into twpr cause this error appered:
[Func NO : 11 (recovery image) Error NO : 2 (load failed!)
Now, I fortunatly turn on the phone, using it with no problems. I can enter in fastboot and eRecovery. I tried to swipe data/reset but the same error appears.
Can I fix it easily? Tell me if you have any tips, thank you:good:
scugnizz said:
Hi guys. I tried to see other threads but I haven't fint anything. Probably there is but I'm beginner and I don't understand so much Anyway this is the problem:
model LLD-L31
build number LLD-L31 8.0.0.133(C432)
FPR unlocked
bootloader unloced
I tried to install root(Magisk-v16.4) in my device. So I unlocked bootloader, installed TWPR(Pretorian80 2.3.1) successfully but this error "Failed to unmount '/system'(Device or resource busy)" appeared. So I try to format data by recovery hoping that it could be able to read partitions after that. I couldn't yet flash file.Zip so I tried to upgrade Twpr in latest version installing it in recovey ramdisk.
After that I'm not able anymore to get into twpr cause this error appered:
[Func NO : 11 (recovery image) Error NO : 2 (load failed!)
Now, I fortunatly turn on the phone, using it with no problems. I can enter in fastboot and eRecovery. I tried to swipe data/reset but the same error appears.
Can I fix it easily? Tell me if you have any tips, thank you:good:
Click to expand...
Click to collapse
Hi, Not familiar with that Version of TWRP, can you link please?
Failure to unmount system usually means you have system set as "read only", try to change within twrp (when you get a working version flashed).
You say you tried to update TWRP to latest edition, exactly what edition did you flash?
Anyway eRecovery will rescue the phone back to when first turned on.
Sparkrite said:
Hi, Not familiar with that Version of TWRP, can you link please?
Failure to unmount system usually means you have system set as "read only",try to change within twrp (when you get a working version flashed).
You say you tried to update TWRP to latest edition, exactly what edition did you flash?
Anyway eRecovery will rescue the phone back to when first turned on.
Click to expand...
Click to collapse
Hi man thank you for your answer.
I flashed this versionhttps://dl.twrp.me/surnia/twrp-3.2.3-0-surnia.img.html
,try to change within twrp (when you get a working version flashed).
Click to expand...
Click to collapse
I can't enter anymore within TWPR, only in stock recovery.
What made you flash that version, where does it say its for the H9L ?
Try either of these, I use V.01 :-
https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306
Make sure you use the following command "fastboot flash recovery_ramdisk NAME.img"
When flashed, issue "fastboot reboot" while holding down Vol+, when bootloader page blanks immediately remove USB lead and continue to hold Vol+ until TWRP appears.
TWRP may stall for a while on LOGO page, be patient.
What made you flash that version, where does it say its for the H9L ?
Click to expand...
Click to collapse
I'm dumb man that's all:silly:
Anyway it's fixed now, I love you (thanks put, at least).
Failure to unmount system usually means you have system set as "read only",try to change within twrp
Click to expand...
Click to collapse
Last thing if you can..
On mount section the option mount system partition read-only is disactivated but, at opening, error appears in the same way so I don't know how to disable it definitively
Try formatting Data and then reboot to TWRP (recovery).
Man I'm a disaster:crying:
I formatted but I also had the brilliant idea to delete the whole system, without creating any backup by twpr, obviously. So now I have no OS in my device:good:
I had look for stock firmware with Firmware Finder and I have find one whit these files(bottom photo). Which have I to download?
Then I'll probably follow this thread(https://forum.xda-developers.com/9-lite/help/os-installed-t3787136) to continue. Is it right??
At this stage you are probably better off using eRecovery to bring your phone back to full stock.
From off press and hold Vol Up and connect USB, wait for eRecovery and select "Download latest version and recovery".
Needs WiFi.
savior
scugnizz said:
savior
Click to expand...
Click to collapse
Ah Great, good to hear.
Now, go and flash TWRP and Magisk, but follow the instructions EXACTLY !
Hello,
I am new to Samsung devices and have tried to install twrp on my note 9.
Firstly I enabled OEM Unlock in dev options and let the phone reset.
I then went into download mode and went to odin3 and selected the correct twrp file in AP and clicked Flash.
It passed and the phone rebooted to the system.
I then tried to get into twrp but it just took me to the stock recovery so I tried reflashing it and now I get the following error:
"Only official released binaries are allowed to be flashed(recovery)"
I have tried going back to dev options to make sure OEM unlock is enabled but it has completely disappeared!!!
I have tried completely reflashing the stock ROM using Odin with no luck!
Does anyone know what I'm doing wrong? This is getting super frustrating because I have never had this issue on any other android phone.
Any help is Very Appreciated Thank You.
VortexHD said:
Hello,
I am new to Samsung devices and have tried to install twrp on my note 9.
Firstly I enabled OEM Unlock in dev options and let the phone reset.
I then went into download mode and went to odin3 and selected the correct twrp file in AP and clicked Flash.
It passed and the phone rebooted to the system.
I then tried to get into twrp but it just took me to the stock recovery so I tried reflashing it and now I get the following error:
"Only official released binaries are allowed to be flashed(recovery)"
I have tried going back to dev options to make sure OEM unlock is enabled but it has completely disappeared!!!
I have tried completely reflashing the stock ROM using Odin with no luck!
Does anyone know what I'm doing wrong? This is getting super frustrating because I have never had this issue on any other android phone.
Any help is Very Appreciated Thank You.
Click to expand...
Click to collapse
ARE YOU EXYNOS OR SNAPDRAGON ?? Below guide is for EXYNOS!!
Did you follow this guide --> https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143 ??
And did you do step 3 ? 3.Download and copy N9_S9_Root_for_OEM_issue_devices_V*.zip to Ext SD card ??i haven't rooted my Note 9 yet but i think that's where you messed up!
Same problem I tray flash twrp say Only official released binaries are allowed to be flashed(recovery)
I flash FIRMWARE UK...and Germany...but not result...my drives N960f
rana14301 said:
Same problem I tray flash twrp say Only official released binaries are allowed to be flashed(recovery)
I flash FIRMWARE UK...and Germany...but not result...my drives N960f
Click to expand...
Click to collapse
read dr ketans guide in the general discussion thread.