Database Develop

[HELP THREAD] Ask any questions [NOOB FRIENDLY]

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..

HELP: No support SINGLE-SKU dm-verity error failed code : 0x02

Hi, a friend gives me his S6 920T (T-Mobile variant) because he has a lot of problems (UI crash all time and another process to) and I decided to install Nougat with ODIN 3.12.7. I downloaded the rom on Sammobile and the flash was succesfull but when the phones reboot, in the blue screen, I saw the DRK error but then the phone rebooted and enter to the stock recovery with this message:
No support SINGLE-SKU
Supported API: 3
dm-verity error...
failed code : 0x02
Im searching on but I can find the solution. I tried doing full wipe and reboot but nothing. I flashed again, but no solution. Any idea? Thanks!
Sorry for my bad english!

KbZonFS said:
Hi, a friend gives me his S6 920T (T-Mobile variant) because he has a lot of problems (UI crash all time and another process to) and I decided to install Nougat with ODIN 3.12.7. I downloaded the rom on Sammobile and the flash was succesfull but when the phones reboot, in the blue screen, I saw the DRK error but then the phone rebooted and enter to the stock recovery with this message:
No support SINGLE-SKU
Supported API: 3
dm-verity error...
failed code : 0x02
Im searching on but I can find the solution. I tried doing full wipe and reboot but nothing. I flashed again, but no solution. Any idea? Thanks!
Sorry for my bad english!
Click to expand...
Click to collapse
download from autochainfire your root file and flash..ur problem willl solve

Emmaugoh said:
download from autochainfire your root file and flash..ur problem willl solve
Click to expand...
Click to collapse
No this didn't fix it need help

Block - Base OTA , can't update funtion

I bought a new one from person,who is using M20 for 1 month.
I checked : ROM & recover is stock
when I tried to choose Downloan update manual function . it always display " failed to update software " ( normal it should say your device is latest )
when I access into bootloader it also dispaly :
#reboot recover cause is BL:recovery mode set by key]#
support SINGE-SKU
Block-Based OTA
Supported API : 3
Manual mode V1.0.00
anybody know about this issued?
have any solution?
I also tried flash stock firmware (checked run AP/PCA in Odin only) but it still same issued

crownvn said:
I bought a new one from person,who is using M20 for 1 month.
I checked : ROM & recover is stock
when I tried to choose Downloan update manual function . it always display " failed to update software " ( normal it should say your device is latest )
when I access into bootloader it also dispaly :
#reboot recover cause is BL:recovery mode set by key]#
support SINGE-SKU
Block-Based OTA
Supported API : 3
Manual mode V1.0.00
anybody know about this issued?
have any solution?
I also tried flash stock firmware (checked run AP/PCA in Odin only) but it still same issued
Click to expand...
Click to collapse
I do have a same problem......
Anyone here..any solutions..

Factory reset or flash firmware with odin

Can't download mode....heres my scenario,i flashed a rom in odin but forgot to tick unlock oem in dev option....now my phone is dead (

Did you follow the flashing guide? Added all files to their respective fields in Odin?

M20
Always on display link for m20

Failed to mount /efs (Invalid argument) Samsung M205F

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:

Note 8 Ask for help bootloop

Hello dear friends. For the time being, I apologize for my English. I have the following problem. I bought Used a Note 8 N950f. the seller has not specified any of the defect problem. I have the following problem. the device does not start. I'm going to recovery and download mode. I have already successfully flashed the current firmware via odin. I have also deleted several times in recovery wipe data and cache no success. the device does not start just up samsung android Note 8. I use the current odin version. I have read some articles here in the forum and tried this without success. Please help me what else can I try and do.
This comes in the recovery menu below.. something is not right.
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is UNKNOWN
No Support SINGLE-SKU
File-Based OTA
E:failed to mount /efs (Invalid argument)
supported API: 3
E: unknown volume for path [/ odm]
E: unknown volume for path [/ vendor]
dm verity verification failed
E: [libfs_mgr] is_dt_compatible (): firmware info was not valid : '/ proc / device-tree / firmware / android / compatible': No such file or directory.

Claim defective device and demand a refund!

I tried. Without success.. Maybe there is someone who can help me. I would be very happy about that.

Is there no one who has an idea solution? Thank you already

?? :crying:

hello, im wondering if u have already found a solution to this problem. my friend's Note 8 also got the same exact problem as yours. tried flashing latest firmware using odin but to no avail.

i have the same problem. do you, by any chance, have found a solution?

alyffluqman said:
i have the same problem. do you, by any chance, have found a solution?
Click to expand...
Click to collapse
Did any of you try flashing the pit file too?

Try manually reinstalling the OS. That should resolve your issue. If not then take it to a Samsung Service Centre

I am stuck in the same situation basically, I tried 4 frimwares from different regions and nothing helped.
SM-G950FD
Exynos version
S8:crying:
If you have oem unlock then install twrp and flash no verity opt encrypt then it will be working :laugh: