Database Users

[PROB] Can't install recovery, Download mode (Write protection: Enable)

Hi folks,
Having searched the forums I couldn't find an answer.
The problem I'm getting is when I get into download mode. I see the normal green android icon but at the top there is a grey caption saying: Write protection: Enabled.
I've been trying to flash twrp custom recovery but odin tries to do it and at the end it tells me success:0 failed:0.
That's all strange enough as previosly I managed to root the s4 using chainfire's Autoroot.
Could anyone tell me why is this happening and how to jump over it and install TWRP recovery.
//edit
I didn't check before I rooted the device but now I can't access stock recovery.
Cheers.
Ps. the device is: rooted i9505 running XXUAMDC stock rom, network: Three UK.

Attached is a screenshot of what I mean.
Thank you.

Didn't the TWRP site suggest using GooManager to install if you're rooted? Maybe give that a shot.

My unbranded UK s4 also said write protection enabled however I've had no problem installing twrp recovery.
Flashed via odin after putting phone into download mode... Have twrp in pda and it's checked in the box next to it...
Sent from my GT-I9505 using xda premium

chalger said:
Hi folks,
Having searched the forums I couldn't find an answer.
The problem I'm getting is when I get into download mode. I see the normal green android icon but at the top there is a grey caption saying: Write protection: Enabled.
I've been trying to flash twrp custom recovery but odin tries to do it and at the end it tells me success:0 failed:0.
That's all strange enough as previosly I managed to root the s4 using chainfire's Autoroot.
Could anyone tell me why is this happening and how to jump over it and install TWRP recovery.
//edit
I didn't check before I rooted the device but now I can't access stock recovery.
Cheers.
Ps. the device is: rooted i9505 running stock rom, network: Three UK.
Click to expand...
Click to collapse
I have the same issue. I'm stock XXUAMDE with CF-ROOT.
I haven't tried to flash TWRP but I can't boot into stock recovery.
It says 'booting recovery' in blue but then just hangs.
Have you tried using Super SU app and unrooting?

Ok.
I tried using GOOmanager, it cannot find suitable recovery for my device (which is strange as you may find it through TWRP web page).
When I choose in GOO to reboot to recovery it actually gets me to stock recovery (I still can NOT get into recovery using power+home+UP)
When i try to flash TWRP using (newly discovered via GOO) stock recovery it looks like that:
There is a broken android icon (see 1st attached file) and the text
-reboot system now
-apply update via ADB
[.....]
# MANUAL MODE #
Applying Multi-CSC
Applied the CSC-Code : H3G (btw H3G is my carrier, three UK)
Successfully applied multi-CSC
when I choose the recovery file to flash I'm getting response that E:\signature verification failed
Again everything I've done with the phone was CFroot, that is it. No custom rom etc or other playing with it.
//edit
I have the same issue. I'm stock XXUAMDE with CF-ROOT.
I haven't tried to flash TWRP but I can't boot into stock recovery.
It says 'booting recovery' in blue but then just hangs.
Click to expand...
Click to collapse
I've got EXACTLY the same behaviour. I discovered GOO manager allowed me to boot into stock recovery.
Thanks for your interest.
chalger

If you're having problems check the thread here: http://forum.xda-developers.com/showthread.php?t=2266336
It's the same method I used to root my phone and flash TWRP. (I too have write protection enabled)

write protection enabled means nothing
I have the exact same thing written on mine.
I have CF-Auto-Rooted mine AND TWRP 2.5 placed on mine, both using ODIN method.
No issues at all - both work perfectly fine.

chalger said:
(I still can NOT get into recovery using power+home+UP)
Click to expand...
Click to collapse
Try using just the Vol Up+Power. Once the phone vibrates, let go of the power but keep holding the up key until you see something appear on the screen. That works on my non-rooted phone to get into recovery.

Hiya
Just for your information.
I've done factory reset, it preserved root access (which I found strange) and now I've managed to flash twrp recovery (which in my view is way too much touch sensitive )
Thanks for all the replies.

problem rooting i9505
chalger said:
Hiya
Just for your information.
I've done factory reset, it preserved root access (which I found strange) and now I've managed to flash twrp recovery (which in my view is way too much touch sensitive )
Thanks for all the replies.
Click to expand...
Click to collapse
Hi All,
Just got my galaxy s4 i9505 with baseband XXUAME2. Have been trying to root this using CFROOT via odin numerous times but each time it fails. The error message includes "write operation failed" and "No PIT partion".
I have downloaded the correct PIT file and tried again but the same problem again.
I have further tried to flash pre-rooted firmware and another stock firmware but again - nothing I do seems to work.
Have tried the factory reset as well but again does not work.
Have tried flashing using motochopper method but also does not work.
Was hoping if someone could kindly extend his/her expertise - I am completely clueless at this point..

Ok for those getting the following error using Odin,
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Removed!!
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I was getting the same errors whenever I tried to flash anything and couldn't figure out why. Now I seem to have sorted it.
Try this.
DO NOT HAVE ODIN OPEN YET
Stop KIES on your PC if it is on.
1) Put your phone into Download mode, (Home, Vol Down, Power at same time).
2) Connect your USB to PC/Laptop and phone.
3) Press UP on your phone.
4) now, open ODIN. <---only open AFTER your have pressed UP on your phone. COM and "Added" should be showing.
5) Flash what you need to flash.
(I noticed previously when I had Odin open, then pressed UP, it would show as "Added" and a Com would show, but I would ALWAYS get the Pit error and a Red FAIL)
I have now tried this method several times on the trot, flashed CWM with success, (where as it was always failing previously), and re-flashed other ROMS with success each time.
Hope this helps others.

Still failing to flash anything usin odin
artnada said:
Ok for those getting the following error using Odin,
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Removed!!
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I was getting the same errors whenever I tried to flash anything and couldn't figure out why. Now I seem to have sorted it.
Try this.
DO NOT HAVE ODIN OPEN YET
Stop KIES on your PC if it is on.
1) Put your phone into Download mode, (Home, Vol Down, Power at same time).
2) Connect your USB to PC/Laptop and phone.
3) Press UP on your phone.
4) now, open ODIN. <---only open AFTER your have pressed UP on your phone. COM and "Added" should be showing.
5) Flash what you need to flash.
(I noticed previously when I had Odin open, then pressed UP, it would show as "Added" and a Com would show, but I would ALWAYS get the Pit error and a Red FAIL)
I have now tried this method several times on the trot, flashed CWM with success, (where as it was always failing previously), and re-flashed other ROMS with success each time.
Hope this helps others.
Click to expand...
Click to collapse
Hi i have tried the above. Same problem persists.
I do not have Kies on my pc. Have tried steps listed above as is but still no luck.
need help

Anjamil said:
Hi i have tried the above. Same problem persists.
I do not have Kies on my pc. Have tried steps listed above as is but still no luck.
need help
Click to expand...
Click to collapse
Me too i have the same problem .. any other method to flash back to original fiemware ?
cheers
Indra

problem solved
I used odin 1.85 and original usb cable that came in the
box. Problem solved am now able to flash all roms

I'm having exxcactly the same problem, but i can't boot the phone, it's just stuck on s4 screen, can someone help?
Thanks in advance.

Thanks for this. That solved my issue.
artnada said:
Ok for those getting the following error using Odin,
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Removed!!
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I was getting the same errors whenever I tried to flash anything and couldn't figure out why. Now I seem to have sorted it.
Try this.
DO NOT HAVE ODIN OPEN YET
Stop KIES on your PC if it is on.
1) Put your phone into Download mode, (Home, Vol Down, Power at same time).
2) Connect your USB to PC/Laptop and phone.
3) Press UP on your phone.
4) now, open ODIN. <---only open AFTER your have pressed UP on your phone. COM and "Added" should be showing.
5) Flash what you need to flash.
(I noticed previously when I had Odin open, then pressed UP, it would show as "Added" and a Com would show, but I would ALWAYS get the Pit error and a Red FAIL)
I have now tried this method several times on the trot, flashed CWM with success, (where as it was always failing previously), and re-flashed other ROMS with success each time.
Hope this helps others.
Click to expand...
Click to collapse

First time i tried to install a custom recovery on my S4 I9505 LTE. With Odin.. It didn't work..
I knew about heimdall.. And i gave that a try. And it worked perfectly. The one thing that's a bit weird.. After it first worked through heimdall. I could flash any custom recovery through Odin. But I think you should give heimdall a try..
Here is a link to how to install CWM on the cyanogenmod wiki: wiki.cyanogenmod.org/w/Install_CM_for_jfltexx#Installing_a_custom_recovery_on_Galaxy_S4_.28International_LTE.29 (I can't post links yet. So i just removed the http)

i flashed modern , and, it is fail, what wrong
[/url][/IMG]
my phone have this entry : "write protection : enable"

on my phone is also 'write protected- enable' but odin and cwm work fine

[Q] Recovery Loop using Kingo

Hi there
I have a 900W8 note 3. I upgraded to the newest firmware via kies. it worked perfectly then i wanted to root it.
Instead of using Odin i used Kingo and now my phone is stuck on a recovery loop.
I try and access recovery up+home+ power and nothing happens it simply keeps looping
I can access download down+power+home.
any suggestions how i can get out of this?
Thank you!
I followed these instructions to the dot
androidrootzDOTCOM/2013/10/how-to-unrootunbrick-galaxy-note-3.html
and it failed
what i did:
1) it was detected o: (com4)
2PDA selected was tar.md5
3) deselected F. Reset Time
i clicked start and "FAIL"
phone says SW REV CHECK FAIL: (SB(1) Fused 2> Binary 1
computer says:
FAIL! (auth)
all threads completed (succeed 0 / failed 0)

What does newst firmware mean? KK? If yes you need to use the correct recovery or autoroot image for kk or below kk it seems you flashed the wrong version
/edit it seems you try to downgrade

Hundsbuah said:
What does newst firmware mean? KK? If yes you need to use the correct recovery or autoroot image for kk or below kk it seems you flashed the wrong version
/edit it seems you try to downgrade
Click to expand...
Click to collapse
Yeah it was Kitkat. I had to flash recovery and it worked.

[Q] Please Help Note 3

I was using android 4.4.2 (N9005XXUGNG1), and i tried to upgrade to lollipop 5.0(N9005XXUGBOA5), i've followed the steps from the sammobile.com and everytime odin fails to install 5.0 . I tried even with a original rom from android 4.4.2(N9005XXUGNG1) and still fails... what can i do please ?

hi there,
what error are you getting? and at which time are you getting it?

eliohanna said:
hi there,
what error are you getting? and at which time are you getting it?
Click to expand...
Click to collapse
I'm in the same situation.
Tried several odin versions 3.07, 3.09, 3.10 (Windows 7, vmware)
every version stucks on
PHP:
<ID:0/003> Complete(Write) operation failed.
I think I've ruined PIT, because on mac heimdall stucks on
PHP:
Downloading device's PIT file...
ERROR: libusb error -7 whilst sending packet. Retrying..
and during my first trials I've selected PIT file from the Sammobile archive and checked Re-partition (my Note3 is 32Gb).

are you able to access recovery? If yes, go to recovery wipe data wipe cache.. remove battery for 10 secs reboot to download mode and try to reflash the firmware. Also always start odin as an administrator.
also ma11k, vmware seems to cause some issues. If you can run windows natively or install it through parallels it would be better.

hey
i resolved
i installed this http://forum.xda-developers.com/galaxy-note-3/general/guide-t2983873 and it's working gr8 !

sorindoc said:
i resolved
i installed this http://forum.xda-developers.com/galaxy-note-3/general/guide-t2983873 and it's working gr8 !
Click to expand...
Click to collapse
For me it didn't work...
It stucked just where it did with every other firmware I tried to install...
Code:
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
are you able to access recovery? If yes, go to recovery wipe data wipe cache.. remove battery for 10 secs reboot to download mode and try to reflash the firmware.​
What do you mean by "recovery"? Yes I can access download mode

ma11k said:
What do you mean by "recovery"? Yes I can access download mode
Click to expand...
Click to collapse
Turn off your phone. Press the home, power and volume up buttons simultaneously until you see the samsung logo. Release the power button and keep pressing the home and volume up buttons till you enter recovery mode. You can scroll up and down using the volume up and volume down, the power button is used to confirm your selection. Wipe data(this will wipe all of your phone content), wipe cache. Turn off your phone. After it's completely off remove the battery for 10 secs. Re-insert the battery. Go to download mode and reflash the firmware.

eliohanna said:
Turn off your phone. Press the home, power and volume up buttons simultaneously until you see the samsung logo. Release the power button and keep pressing the home and volume up buttons till you enter recovery mode.
Click to expand...
Click to collapse
Oh, now I understand. No, unfortunately the phone shows "firmware upgrade encountered an issue" screen on UP+Menu+Power...
Maybe the problem is in the wrong partition table?..
I get
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
on EVERY firmware I try to flash (tried various 5.0, 4.4...)
Have not tried Parallels yet though...

That's because of the size mismatch. You need to flash a ROM according to your phone's size, by size I mean memory, 16 or 32 GB, whatever you have. For example, I could not flash German LP ROM on my 32 GB phone, had the same error, but the Polish version worked just fine.

first of all are you sure you are using the correct firmware for your device? What variant of the note 3 are you using?
second of all, try odin on native windows; disable the antivirus, disable kies if you have it installed, run odin as administrator.
I have an sm-n900 note 3 and had a similar problem. Someone suggested that i try several times as these errors seem to happen randomly. I suggest you flash the lollipop firmware bcz a lot of people are unable to downgrade from ll to kk due to the baseband flash.

eliohanna said:
also ma11k, vmware seems to cause some issues. If you can run windows natively or install it through parallels it would be better.
Click to expand...
Click to collapse
After 2 days of frustration, I finally did it!
One word — PARALLELS!
Thanks eliohanna, it was unobvious, but I did as you've said and could flash my Note 3 at once!
For those, who experience the same problems with <ID:0/003> Complete(Write) operation failed. i suggest using Parallels
(If it matters, i tried (and failed) VmWare 7 with Windows 7)
Successful configuration is:
Parallels 10 with Windows XP
Installed clean Win XP,
plugged Note3 in,
allowed Windows to install the drivers on it's own.
Opened Odin 3.09
and flashed the rom N9005XXUGBNL8 5.0 from Sammobile

ma11k said:
After 2 days of frustration, I finally did it!
One word — PARALLELS!
Thanks eliohanna, it was unobvious, but I did as you've said and could flash my Note 3 at once!
For those, who experience the same problems with <ID:0/003> Complete(Write) operation failed. i suggest using Parallels
(If it matters, i tried (and failed) VmWare 7 with Windows 7)
Successful configuration is:
Parallels 10 with Windows XP
Installed clean Win XP,
plugged Note3 in,
allowed Windows to install the drivers on it's own.
Opened Odin 3.09
and flashed the rom N9005XXUGBNL8 5.0 from Sammobile
Click to expand...
Click to collapse
Congrats!!! Please hit the thanks button and add [SOLVED] before the thread's name so that we can help anyone who is having similar issues.

[SOLVED] Recovery is not seandroid enforcing SM-G900F

So I tried rooting for the first time today, and after trying it (and failing) it shows this message briefly with the "Samsung Galaxy S5" startup screen, then turns off again. Then, I noticed I had used a CF Auto Root for 4.4.2, when I was running 5.0. I downloaded one for 5.0 and ran it with Odin. After that I get the same screen, but it stays on that screen forever. It says "Recovery booting... Recovery is not seandroid enforcing. Set warranty bit: recovery" In the top left corner.
Anyone know a fix for this? Not being able to use your phone is kind of sad

Flash a stock ROM from sammobile . com with ODIN, instructions under the download on their site

*Detection* said:
Flash a stock ROM from sammobile . com with ODIN, instructions under the download on their site
Click to expand...
Click to collapse
It fails when I try to flash it!
In Odin it says:
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the phone it says:
"Volume size is too mig 61440 < 122880
ODIN: Invalid ext4 image"

Flash the PIT file for your model S5 along with the ROM (Together)

*Detection* said:
Flash the PIT file for your model S5 along with the ROM (Together)
Click to expand...
Click to collapse
This doesn't work either, it gives me "Fail (size)" instead of ext4 now.

Burgermis said:
This doesn't work either, it gives me "Fail (size)" instead of ext4 now.
Click to expand...
Click to collapse
Could all of this be because I forgot to turn USB Debugging on? Or would that have made no difference?

Same Problem
I have the same problem with you yesterday. What I did is flash a TWRP Recovery that is compatible with my SM-G900F model I downloaded it on the TWRP site and I choose the KLTE version. And BOOM it fixes the problem Tell me if still stuck on it.

ginofakes said:
I have the same problem with you yesterday. What I did is flash a TWRP Recovery that is compatible with my SM-G900F model I downloaded it on the TWRP site and I choose the KLTE version. And BOOM it fixes the problem Tell me if still stuck on it.
Click to expand...
Click to collapse
I tried this as well, but it did not work for me.
What did work though was trying out a bunch of different PIT files with the Stock ROM until it eventually worked!
Thanks for your guys' help!

It would have worked first time if you'd used the correct PIT file for your specific model S5 first, maybe you are mistaken on which model it is, check under the battery and in the Settings > About screen

*Detection* said:
It would have worked first time if you'd used the correct PIT file for your specific model S5 first, maybe you are mistaken on which model it is, check under the battery and in the Settings > About screen
Click to expand...
Click to collapse
I did use the correct one, with the correct amount of gigs as well, I don't know why it didn't work.

Downgrade MM to LLP

How to downgrade MM to LLP for SS J5 2015?
Thanks <3

kysieucute said:
How to downgrade MM to LLP for SS J5 2015?
Thanks <3
Click to expand...
Click to collapse
Hi maybe this helps
https://forum.xda-developers.com/galaxy-j5/how-to/6-0-1-5-1-1-bootloader-modem-j500xx-t3566801

Vmb265 said:
Hi maybe this helps
https://forum.xda-developers.com/galaxy-j5/how-to/6-0-1-5-1-1-bootloader-modem-j500xx-t3566801
Click to expand...
Click to collapse
I have read but still do not understand because I am a new member and not very familiar with something like this. Can you tell me more about downgrade MM to LP?
Thanks

kysieucute said:
I have read but still do not understand because I am a new member and not very familiar with something like this. Can you tell me more about downgrade MM to LP?
Thanks
Click to expand...
Click to collapse
Okay so do you just want to downgrade to LLP for flashing so other Rom or you actually want to use LLP as your daily driver?:cyclops:

Vmb265 said:
Okay so do you just want to downgrade to LLP for flashing so other Rom or you actually want to use LLP as your daily driver?:cyclops:
Click to expand...
Click to collapse
sorry you. I am a Vietnamese person so I do not know much about English. I have to google translate. Please do not abbreviate or anything. I do not understand. sorry to bother you. Can you give me specific instructions on how to downgrade from MM to LP. If you can write more specifically thank you. thank you

Okay so assuming that you actually want to use Lollipop version on your j5,here Ive tried to provide some steps to do that:
NOTE: This will erase your data so make a backup
Step 1: Find your device model(like j500f/m/fn/h) and download the lollipop rom accordingly from herehttps://www.sammobile.com/firmwares/
Just search the model number
Step 2:Get Odin3 on your computer from here http://odin3.en.lo4d.com
Step 3:After downloading all files, now you need to set your j5 into download mode- Just switch off and the hold Vol down+Home+Power at the same time
Step 4:Connect your device via USB(UniversalSerialBuzz )cable to your computer and open odin application,the dialog box should show 'Added!'
Step 5: Select AP option and browse the ROM file you downloaded previously
Step 6: Let it verify things and after a while hit the Start button and let it do its thing!
Step 7: After the process is complete the device should boot up in lollipop (it'll take a while!)
Step 8:Enjoy Lollipop!
I hope that helps,also if you need anymore assistance feel free to ask!

Vmb265 said:
Okay so assuming that you actually want to use Lollipop version on your j5,here Ive tried to provide some steps to do that:
NOTE: This will erase your data so make a backup
Step 1: Find your device model(like j500f/m/fn/h) and download the lollipop rom accordingly from herehttps://www.sammobile.com/firmwares/
Just search the model number
Step 2:Get Odin3 on your computer from here http://odin3.en.lo4d.com
Step 3:After downloading all files, now you need to set your j5 into download mode- Just switch off and the hold Vol down+Home+Power at the same time
Step 4:Connect your device via USB(UniversalSerialBuzz )cable to your computer and open odin application,the dialog box should show 'Added!'
Step 5: Select AP option and browse the ROM file you downloaded previously
Step 6: Let it verify things and after a while hit the Start button and let it do its thing!
Step 7: After the process is complete the device should boot up in lollipop (it'll take a while!)
Step 8:Enjoy Lollipop!
I hope that helps,also if you need anymore assistance feel free to ask!
Click to expand...
Click to collapse
Is this normal like flash ROM 6.0?
I tried flashing the stock 5.1.1 LP and it crashed in the aboot.mbn section

kysieucute said:
Is this normal like flash ROM 6.0?
I tried flashing the stock 5.1.1 LP and it crashed in the aboot.mbn section
Click to expand...
Click to collapse
Yes it is the same process,maybe try to install Samsung drivers or update then from control panel settings.

Vmb265 said:
Yes it is the same process,maybe try to install Samsung drivers or update then from control panel settings.
Click to expand...
Click to collapse
error file aboot.mbn !!!!
driver OK
how to fix ?
Everything is full .... until the flash is defective. I think samsung blocked this !!!
Thank you for the fast reply tried to install the LL version through Odin but it shows me some errors
**Whenever i try to downgrade i get the same error about aboot.mbn and on the phone screen sw rev check fail labootlfused 2 binary 1**
-HERE IS THE LOG-
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1100).
<ID:0/004> File analysis
<ID:0/004> SetupConnection..
<ID 0/004. Initialzation..
<ID:0/004> Get PITT for mapping.
<ID:0/004> Firmware update start.
<ID:0/004> SingleDownload.
<ID 0/004> aboot. mbn
<ID 0/004 NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID: 01004
<ID:0/004> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 failed 1)
END

Hey...
Goto Settings-->About Phone--> Tap on Build number 5-6 times..
Then goto settings --> Developer options--> enable oem unlocking..
Remove screen lock protection example pattern or pin code and flash Lollipop Firmware with any Flasher Odin recommended

afaqktk2 said:
Hey...
Goto Settings-->About Phone--> Tap on Build number 5-6 times..
Then goto settings --> Developer options--> enable oem unlocking..
Remove screen lock protection example pattern or pin code and flash Lollipop Firmware with any Flasher Odin recommended
Click to expand...
Click to collapse
when flashing error in aboot.mbn file

kysieucute said:
when flashing error in aboot.mbn file
Click to expand...
Click to collapse
Try other firmware.. i mean doqnload firmware again from another site

afaqktk2 said:
Try other firmware.. i mean doqnload firmware again from another site
Click to expand...
Click to collapse
I have tried with a lot of different versions and still have errors on that file. I think samsung blocked downgrade the android version

kysieucute said:
I have tried with a lot of different versions and still have errors on that file. I think samsung blocked downgrade the android version
Click to expand...
Click to collapse
After enabling developer options u can flash it.. enable developer options and try
---------- Post added at 07:24 AM ---------- Previous post was at 07:16 AM ----------
If this doesnt work try to flash other partitions except aboot.

afaqktk2 said:
After enabling developer options u can flash it.. enable developer options and try
Click to expand...
Click to collapse
Why do I see everyone saying that flash fw LP as normal !! I made a full error in the file aboot.mbn !!! unlock oem + driver is full
ROM 4 file or 1 file or 5 file same thing

kysieucute said:
Why do I see everyone saying that flash fw LP as normal !! I made a full error in the file aboot.mbn !!! unlock oem + driver is full
ROM 4 file or 1 file or 5 file same thing
Click to expand...
Click to collapse
That something tricky .. dont know why..
But aboot.mbn error comes when FRP lock is enabled...

afaqktk2 said:
That something tricky .. dont know why..
But aboot.mbn error comes when FRP lock is enabled...
Click to expand...
Click to collapse
I have activated it since I knew naughty the phone. and rom flash 5.1.1 still get error at aboot.mbn

kysieucute said:
I have activated it since I knew naughty the phone. and rom flash 5.1.1 still get error at aboot.mbn
Click to expand...
Click to collapse
In download mode there is written FRP lock...
What is FRP lock status if it is ON then itll give aboot.mbn

afaqktk2 said:
In download mode there is written FRP lock...
What is FRP lock status if it is ON then itll give aboot.mbn
Click to expand...
Click to collapse
I am a new member so I do not understand. Can you now write down the steps that will help me? thank you very much !!

The error u mentioning i mean aboot.mbn failed is mostly because of when FRP lock is enabled..
So if u press vol down + power combo then vol up..
In download mode there will be text see there FRP lock is enabled or disabled