Hello, I am in dire need of assistance. I'm not sure what I did, but I think i soft bricked my Le Pro 3 LEX727. I was attempting to install a custom rom, I wiped Delvik,system,cache,data then proceeded to flash lineage. When I rebooted it quickled flashed Le Eco bootup then crashed or went to a black screen. Same thing with recovery, quickly flashes "Le Eco Recovery" then goes black. I can boot into Fastboot and the device shows up there, but when I attempt to do "fastboot oem unlock-go" I get "FAILED (remote: oem unlock is not allowed)". Please help me, I really need to fix my phone.
Sincerely,
A grateful person who messed up their phone.
It goes into recovery mode? power button + volume up button. redo the procedure and leaves everything in the options selected .. or I hope you made a backup beforehand, there are various discussions on how to recover
If you can access fastboot, youre golden. Just flash a stock rom
trizex said:
If you can access fastboot, youre golden. Just flash a stock rom
Click to expand...
Click to collapse
Can you help me out with where to go from there, or direct me to a thread? When I attempt to unlock oem so i can flash twrp it says "oem unlock is not allowed"
thank you very much.
Gynlemon said:
It goes into recovery mode? power button + volume up button. redo the procedure and leaves everything in the options selected .. or I hope you made a backup beforehand, there are various discussions on how to recover
Click to expand...
Click to collapse
No, it can only boot into fastboot.
Yewsif said:
No, it can only boot into fastboot.
Click to expand...
Click to collapse
https://forum.xda-developers.com/le-pro3/how-to/guide-to-install-stock-rom-custom-t3486600
Gynlemon said:
https://forum.xda-developers.com/le-pro3/how-to/guide-to-install-stock-rom-custom-t3486600
Click to expand...
Click to collapse
Thank you, but as I cant get into the devices OS, I cannot enable usb debugging and oem unlock. Only thing I can access is the fastboot menu.
Have you tried flashing the aboot file? from this thread
fastboot flash aboot emmc_appsboot.mbn
then
reboot
then
Fastboot mode using power-off + volume down.
then
fastboot oem unlock-go
then you can boot or flash into TWRP or whatever recovery
Joms_US said:
Have you tried flashing the aboot file? from this thread
fastboot flash aboot emmc_appsboot.mbn
then
reboot
then
Fastboot mode using power-off + volume down.
then
fastboot oem unlock-go
then you can boot or flash into TWRP or whatever recovery
Click to expand...
Click to collapse
No, I have not. What do you mean the aboot file.
Yewsif said:
No, I have not. What do you mean the aboot file.
Click to expand...
Click to collapse
http://newandroidbook.com/Articles/aboot.html
Joms_US said:
http://newandroidbook.com/Articles/aboot.html
Click to expand...
Click to collapse
Thank you for your time and help, but I have no idea what to do with that link, I understand the adb commands I need to put in. Is there anyway you can sort of walk me through it with steps?
Thank you.
You prolly have more experience than me so I am just pointing to you what I did to unlock the bootloader which seems to be the problem? ^_^
https://forum.xda-developers.com/showpost.php?p=71116203&postcount=8
I gave the instructions and link there already but here is the direct link that contains the aboot file.
https://www.androidfilehost.com/?fid=313042859668275431
joms_us said:
you prolly have more experience than me so i am just pointing to you what i did to unlock the bootloader which seems to be the problem? ^_^
https://forum.xda-developers.com/showpost.php?p=71116203&postcount=8
i gave the instructions and link there already but here is the direct link that contains the aboot file.
https://www.androidfilehost.com/?fid=313042859668275431
Click to expand...
Click to collapse
thank you so much, flashing the aboot file worked and made my custom rom run perfectly! I love you.
Yewsif said:
thank you so much, flashing the aboot file worked and made my custom rom run perfectly! I love you.
Click to expand...
Click to collapse
Thanks would be enough.
Joms_US said:
Have you tried flashing the aboot file? from this thread
fastboot flash aboot emmc_appsboot.mbn
then
reboot
then
Fastboot mode using power-off + volume down.
then
fastboot oem unlock-go
then you can boot or flash into TWRP or whatever recovery
Click to expand...
Click to collapse
I royally messed up my custom ROM install, this got me to boot again. Thank you.
This should be a sticky, or a part of any installation method. Why? If you upgrade to the latest official firmware (e.g. 21s+), your bootloader will no longer be unlocked with the oem unlock-go method. You *have* to flash this bootloader first so you can then unlock it and do all the other steps.
kaivorth said:
I royally messed up my custom ROM install, this got me to boot again. Thank you.
Click to expand...
Click to collapse
Glad this thread helped you.
Joms_US said:
Have you tried flashing the aboot file? from this thread
fastboot flash aboot emmc_appsboot.mbn
then
reboot
then
Fastboot mode using power-off + volume down.
then
fastboot oem unlock-go
then you can boot or flash into TWRP or whatever recovery
Click to expand...
Click to collapse
This works ! Thank you
Joms_US said:
Have you tried flashing the aboot file? from this thread
fastboot flash aboot emmc_appsboot.mbn
then
reboot
then
Fastboot mode using power-off + volume down.
then
fastboot oem unlock-go
then you can boot or flash into TWRP or whatever recovery
Click to expand...
Click to collapse
great thanks for you. I finally unbrick X727 with same way.
Related
I've been trying to push the bootloader and radio from the 4.2.2 factory image using fastboot using the commands below
fastboot flash radio "filename.img"
fastboot flash hboot "filename.img"
The radio works just fine, but while flashing the bootloader it gives me an error saying "partition table doesn't exist".
Any idea what this means and how it can be fixed?
AW: Fastboot - Partition table doesn't exist
Hboot is HTC. On Nexus 4 it is
Code:
fastboot flash bootloader bootloader.img
Sent from my Nexus 4 using xda premium
hboot is HTC. for N4 you use
fastboot flash boot boot.img
boot.img is whatever your bootloader image is. Please note:flashing wrong/corrupted boot.img is difficult to recover.
siddjazz said:
fastboot flash hboot "filename.img"
The radio works just fine, but while flashing the bootloader it gives me an error saying "partition table doesn't exist".
Any idea what this means and how it can be fixed?
Click to expand...
Click to collapse
Sent from my Nexus 4 in a Faraday cage
KyraOfFire said:
hboot is HTC. for N4 you use
fastboot flash boot boot.img
boot.img is whatever your bootloader image is. Please note:flashing wrong/corrupted boot.img is difficult to recover.
Sent from my Nexus 4 in a Faraday cage
Click to expand...
Click to collapse
No
boot is the kernel.
bootloader is the bootloader.
There is no "bootloader" partition. Good luck flashing on that. Nexus 4 mount point thread:
http://forum.xda-developers.com/showpost.php?p=34141701&postcount=1
Nuu~ said:
No
boot is the kernel.
bootloader is the bootloader.
Click to expand...
Click to collapse
Sent from my Nexus 4 in a Faraday cage
Nuu~ said:
No
boot is the kernel.
bootloader is the bootloader.
Click to expand...
Click to collapse
So the command would be fastboot flash bootloader "boot.img" ?
This is a bit confusing
siddjazz said:
So the command would be fastboot flash bootloader "boot.img" ?
This is a bit confusing
Click to expand...
Click to collapse
fastboot flash bootloader bootloader-mako-makoz10o.img
and for the radio:
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
KyraOfFire said:
There is no "bootloader" partition. Good luck flashing on that. Nexus 4 mount point thread:
http://forum.xda-developers.com/showpost.php?p=34141701&postcount=1
Click to expand...
Click to collapse
is that so? =)
even if there is no "bootloader" partition, fastboot still flashes the right partition when used with "flash bootloader".
KyraOfFire said:
hboot is HTC. for N4 you use
fastboot flash boot boot.img
boot.img is whatever your bootloader image is. Please note:flashing wrong/corrupted boot.img is difficult to recover.
Sent from my Nexus 4 in a Faraday cage
Click to expand...
Click to collapse
You're gonna make someone brick their device. Do us all a favor and stick to toolkits. Please.
It's definitely most ****ing definitely:
Code:
fastboot flash bootloader bootloader.img
KyraOfFire said:
hboot is HTC. for N4 you use
fastboot flash boot boot.img
boot.img is whatever your bootloader image is. Please note:flashing wrong/corrupted boot.img is difficult to recover.
Click to expand...
Click to collapse
NO!
Your advice above is totally wrong, and will brick a phone if it is followed. Boot is the kernel, NOT the bootloader.
Sent from my Nexus 4
starscream92 said:
You're gonna make someone brick their device. Do us all a favor and stick to toolkits. Please.
It's definitely most ****ing definitely:
Code:
fastboot flash bootloader bootloader.img
[/QUOTe
Lmfao
I guess toolkits do have a purpose
i gave you a thanks for the laugh
Click to expand...
Click to collapse
I followed his instructions
I followed his instructions and used fastboot flash boot boot.img
Is it hopeless and I need to buy a new phone or is their still hope?
Oddly, it seemed to allow me to use the correct method fastboot flash bootloader boot.img, bu I get stuck in a bootloop.
If anyone could help me that would be greatly appreciated.
qsylalyn said:
I followed his instructions and used fastboot flash boot boot.img
Is it hopeless and I need to buy a new phone or is their still hope?
Oddly, it seemed to allow me to use the correct method fastboot flash bootloader boot.img, bu I get stuck in a bootloop.
If anyone could help me that would be greatly appreciated.
Click to expand...
Click to collapse
boot = kernel
bootloader = bootloader
radio = modem
userdata = nand´s user data storage(/data)
system = system
cid = not used on n4
so for god sake
just install stock images
its pretty straitgh forward, just double click on .bat
qsylalyn said:
I followed his instructions and used fastboot flash boot boot.img
Is it hopeless and I need to buy a new phone or is their still hope?
Oddly, it seemed to allow me to use the correct method fastboot flash bootloader boot.img, bu I get stuck in a bootloop.
If anyone could help me that would be greatly appreciated.
Click to expand...
Click to collapse
Of course you're in a boot loop. You still have the bootloader image in your kernel because that's where you flashed it to!
Wouldn't the solution be to get a KERNEL image and flash that to the BOOT partition before you flash your bootloader image to its correct partition (bootloader) which is what you now doing?
You never posted back on where you ended up with your phone.
Found a way to reboot to edl mode from fastboot
All credits to @emuzychenko
1) Download modified fastboot file
2) Reboot your phone to fastboot
3) Double click on edl.cmd
4) You are on 9008/edl mode
5) Flash any fastboot image from Mi flash
You successfully unbricked your device
Hi
Try with that method also. It seams to work .
Next time I brick it again (trust me, it will happen) I will give those a try.
This is the solution www(dot)htcmania.com(/)showthread(dot)php?t=1163463
Cheked by me, the brick was to try to unlock the bootloader without the Xiaomi message.
Sorry for my english, bu ti hope to be helpful.
To restore the default Bootloader copy paste the emmc_appsboot.mbn from Fastboot Rom to the Adb foldee
and type command on cmd
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot reboot
For those who have failed and stuck on "HS USB 900E" and the bootloader stick locked here is the solution :
1. Enter fastboot by holding vol down + power
2. Plug your RN3Pro to PC
2. Flash original bootloader from official fastboot firmware
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
3. Type again :
fastboot reboot
and quickly hold volume up untuk it enter "sideload" mode
4. Install Mi PC Suite from this link en.miui.com/thread-225600-1-1.html
5. Let the Mi PC Suite download the latest chinese firmware, just sit and wait until it done
6. Lets Brick the beast again
parfetto said:
Hi
Try with that method also. It seams to work .
Click to expand...
Click to collapse
this method only works for few very people, everyone cant access adb through recovery.
apixbuanget said:
For those who have failed and stuck on "HS USB 900E" and the bootloader stick locked here is the solution :
1. Enter fastboot by holding vol down + power
2. Plug your RN3Pro to PC
2. Flash original bootloader from official fastboot firmware
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
3. Type again :
fastboot reboot
and quickly hold volume up untuk it enter "sideload" mode
4. Install Mi PC Suite from this link en.miui.com/thread-225600-1-1.html
5. Let the Mi PC Suite download the latest chinese firmware, just sit and wait until it done
6. Lets Brick the beast again
Click to expand...
Click to collapse
Have you tested this method yourself? I think this is for people who bricked the device but had stock recovery inside, what about people who has twrp and bricked the device? Also I dont think you can flash anything through fastboot in locked bootloader
IT WORKS
apixbuanget said:
For those who have failed and stuck on "HS USB 900E" and the bootloader stick locked here is the solution :
1. Enter fastboot by holding vol down + power
2. Plug your RN3Pro to PC
2. Flash original bootloader from official fastboot firmware
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
3. Type again :
fastboot reboot
and quickly hold volume up untuk it enter "sideload" mode
4. Install Mi PC Suite from this link en.miui.com/thread-225600-1-1.html
5. Let the Mi PC Suite download the latest chinese firmware, just sit and wait until it done
6. Lets Brick the beast again
Click to expand...
Click to collapse
Worked like a magic. I can confirm for sure. Was stuck at HS USB 900E with locked bootloader.
Rajdip said:
Have you tested this method yourself? I think this is for people who bricked the device but had stock recovery inside, what about people who has twrp and bricked the device? Also I dont think you can flash anything through fastboot in locked bootloader
Click to expand...
Click to collapse
Yeah i bricked mine with twrp .. and i cannot enter into recovery mode now.. only fastboot works and i cannot flash stock recovery too because the bootloader is locked :/ stupid Mi :/
Dharani_V said:
Yeah i bricked mine with twrp .. and i cannot enter into recovery mode now.. only fastboot works and i cannot flash stock recovery too because the bootloader is locked :/ stupid Mi :/
Click to expand...
Click to collapse
So, did you try above mentioned method?
amsmu said:
So, did you try above mentioned method?
Click to expand...
Click to collapse
Yes i did .. and its not allowing me to flash anything .. Getting Error Device is locked :/
failed bro, getting error device is locked using QFIL.:crying:
Guys, please mention the reason behind your device getting bricked too when you are reporting what worked and what didn't. Like whether during unlock bootloader process(without xiaomi's permission) or flashing custom ROM(most probably MIUI official updates) via twrp.
Dharani_V said:
Yes i did .. and its not allowing me to flash anything .. Getting Error Device is locked :/
Click to expand...
Click to collapse
What were you doing when it bricked?
Go to service center. They will repair it
mine happened same..... hard bricked my mobile after restoring original bootloader.......
QFIL cannot do a thing ..... all the eror i get is unable to go to EDl mode......
nothing for me except download mode and fastboot......
so toook to service centre and got it repaired for free in 2hrs
puli where do u live[emoji14]
Sent from my Redmi Note 3 using XDA-Developers mobile app
Rajdip said:
Have you tested this method yourself? I think this is for people who bricked the device but had stock recovery inside, what about people who has twrp and bricked the device? Also I dont think you can flash anything through fastboot in locked bootloader
Click to expand...
Click to collapse
i've tried this myself. In HS USB 900E you can flash aboot through fastboot whether you stock recovery or twrp before bricked.
Rajdip said:
I have found few ways by which people may unbrick from HS USB 900E state without test point, but those guides are for other devices, needs thorough testing for Redmi note 3.
Tools needed:-
1) QPST http://www.androidbrick.com/downloa...qcn-for-lollipop-android-5-0-6-0-marshmallow/
2)Nubia tool studio https://drive.google.com/folderview?id=0BwtoIMKf470SRUxfdHA5cU14ZTQ#
Now follow these guides for reference,
1)http://www.androidbrick.com/ultimat...ide-snapdragons-are-unbrickable-qhsusb_dload/
2)http://www.androidbrick.com/unbrick...-you-have-the-right-kind-of-rom-qhsusb_dload/
Only people with hardbrick(900E) and locked bootloader can this test methods, Please try and leave your feedback, maybe we will find a way to unbrick without opening the phone and voiding warranty. Good Luck
Click to expand...
Click to collapse
Does anyone success ? Please share a guide !
apixbuanget said:
i've tried this myself. In HS USB 900E you can flash aboot through fastboot whether you stock recovery or twrp before bricked.
Click to expand...
Click to collapse
wow!!! thats great, but before you flashed aboot through fastboot did you check whether your bootloader was locked or not?
Hi all,
I am in trouble with the PRO 5.
Actual situation:
No recovery mode available
The phone boots but when is time to go in the home screen, the screen becomes black and only the power button response so I only turn it off or restart.
Fastboot mode available but the bootloader is locked
I tried many time with the Multiupgrade tool and TestPCTool but the answer is "Token sign failed"
Could someone help me before to put the phone in the trash
Upppppp!!!!!
You could try to unlock it using "fastboot oem unlock", but if it works it probably wipes the userdata partition, and it may fail. If you manage to unlock it, just reflash the stock image, but without the bootloader.
If this doesn't work, there is a similar thread in a different forum which may help you:
https://forum.meizufans.eu/topic/5376/meizu-pro-5-have-rooted-rom-but-lost-recovery-phone-can-boot-pls-help
Daniel Abrecht said:
You could try to unlock it using "fastboot oem unlock", but if it works it probably wipes the userdata partition, and it may fail. If you manage to unlock it, just reflash the stock image, but without the bootloader.
If this doesn't work, there is a similar thread in a different forum which may help you:
https://forum.meizufans.eu/topic/53...rom-but-lost-recovery-phone-can-boot-pls-help
Click to expand...
Click to collapse
I know the italian guy of this 3D and I can tell u, "fastboot oem unlock" doesn't work unfortunately :crying:
Thanks Pycon.
He is right, no way to unlock the bootloader, at the moment
just try this. good luck man. http://forum.xda-developers.com/meizu-pro-5/how-to/meizu-customer-service-flash-tools-save-t3447678
tzzzz said:
just try this. good luck man. http://forum.xda-developers.com/meizu-pro-5/how-to/meizu-customer-service-flash-tools-save-t3447678
Click to expand...
Click to collapse
Thanks but tried many times: Token signature fail...
Have you tried flashing the whole system (20150923195421_demo_prd_stable) as described in the M86 firmware upgrade tutorial.pdf ?
st0rm77 said:
Have you tried flashing the whole system (20150923195421_demo_prd_stable) as described in the M86 firmware upgrade tutorial.pdf ?
Click to expand...
Click to collapse
Where is that tutorial?
DarginMahkum said:
Where is that tutorial?
Click to expand...
Click to collapse
It resides in the Meizu Tools post, but never mind that. I dove into the security and fastboot uses secure boot so unless there is an exploit your stuck.
Are you able to flash the boot partition ?
If so, you might be able to flash the recovery.img onto the boot (bootimg) partition. Then drop an update.zip into the root of userdata and reboot.
Good luck.
Hey Grumpy,
I extracted the kernel and ramdisk from the recovery image (flyme_5.6.1.19_daily). Unpack these files into a directory, then run
# fastboot boot kernel ramdisk
If it boots you can:
- erase to factory default
- maybe ?? flash /sdcard/update.zip ??
Good luck :good:
st0rm77 said:
Hey Grumpy,
I extracted the kernel and ramdisk from the recovery image (flyme_5.6.1.19_daily). Unpack these files into a directory, then run
# fastboot boot kernel ramdisk
If it boots you can:
- erase to factory default
- maybe ?? flash /sdcard/update.zip ??
Good luck :good:
Click to expand...
Click to collapse
Nope...
creating boot image...
creating boot image - 15699968 bytes
downloading 'boot.img'...
FAILED (remote: permission denied!)
finished. total time: 0.000s
This appears. I can not find anything on the internet and I do not know what to do.
KafkaG said:
This appears. I can not find anything on the internet and I do not know what to do.
Click to expand...
Click to collapse
Hi,
extract the original Firmware on your PC, look for boot.img and than in fastboot write "fastboot flash boot boot.img". Error1 disapers. :good:
Sent from my Mi A1 using XDA Labs
yorkberliner said:
Hi,
extract the original Firmware on your PC, look for boot.img and than in fastboot write "fastboot flash boot boot.img". Error1 disapers. :good:
Click to expand...
Click to collapse
Thanks, but how I can do it?
yorkberliner said:
Hi,
extract the original Firmware on your PC, look for boot.img and than in fastboot write "fastboot flash boot boot.img". Error1 disapers. :good:
Click to expand...
Click to collapse
but I have to extract it from the firmware of lineageos I installed or from the original one of stock? and how do I extract it?
Nobody can help me?
KafkaG said:
Nobody can help me?
Click to expand...
Click to collapse
Good evening,
please be patient. DLoad and extract with 7zip the firmware from here. Extract the firmware again. Now you have the original boot.img from MIUI.
In Fastboot flash the boot.img with "fastboot flash boot boot.img".
If above method won't work, re-download the rom file, this seems corrupt.
Next time try to fresh flash the rom instead of ota, some ota are broken and would have some issue like this.
tanapak1 said:
If above method won't work, re-download the rom file, this seems corrupt.
Next time try to fresh flash the rom instead of ota, some ota are broken and would have some issue like this.
Click to expand...
Click to collapse
I downloaded several times the same rom and more versions, the problem is the system
yorkberliner said:
Good evening,
please be patient. DLoad and extract with 7zip the firmware from here. Extract the firmware again. Now you have the original boot.img from MIUI.
In Fastboot flash the boot.img with "fastboot flash boot boot.img".
Click to expand...
Click to collapse
which of those rom? the first one, 8.1 almost destroyed the system (with the boot.img) and I had to put the boot.img back from the twrp backup, so which link is right?
Edit: I think, indeed, I'm sure I need the boot.img of the rom that I have or lineage, but I do not know how to extract it from the zip.
Hi,
okay. I think the best way is you flash first the original Firmware from here with Xiaomi Flash Tool. DLoad and install on your PC. DLoad and read this Site.
Now you have the original Firmware installed. Go to settings, about the Phone, Buildnumber. Tab 7 times on it and than go to the Developer. Open OEM and US-Debugging. Reboot into Fastboot. In ADB/Fastboot write "fastboot devices" and your device must recogniced. Than write "fastboot oem unlock". After this you get a reboot to system. Now look again iin settings, devoloper if oem and usb-debugging on. Reboot in fastboot your Phone. Now write again "fastboot devices". Is everythink okay than write "fastboot boot recovery-3.2.1-2-oreo.img". Now you have twrp installed. In twrp flash the twrp-recoveryinstaller-3.2.1-2-oreo.zip. After this you can flash your favoryte Custom Rom. Good Luck :good:
yorkberliner said:
Hi,
okay. I think the best way is you flash first the original Firmware from here with Xiaomi Flash Tool. DLoad and install on your PC. DLoad and read this Site.
Now you have the original Firmware installed. Go to settings, about the Phone, Buildnumber. Tab 7 times on it and than go to the Developer. Open OEM and US-Debugging. Reboot into Fastboot. In ADB/Fastboot write "fastboot devices" and your device must recogniced. Than write "fastboot oem unlock". After this you get a reboot to system. Now look again iin settings, devoloper if oem and usb-debugging on. Reboot in fastboot your Phone. Now write again "fastboot devices". Is everythink okay than write "fastboot boot recovery-3.2.1-2-oreo.img". Now you have twrp installed. In twrp flash the twrp-recoveryinstaller-3.2.1-2-oreo.zip. After this you can flash your favoryte Custom Rom. Good Luck :good:
Click to expand...
Click to collapse
No thanks, bye
Something went wrong flashing and it will not boot I get this screen any ideas how to fix?
Can you get to the fastboot menu?
Cozzeck said:
Can you get to the fastboot menu?
Click to expand...
Click to collapse
Yes I can
fezzy102 said:
Something went wrong flashing and it will not boot I get this screen any ideas how to fix?
Click to expand...
Click to collapse
You will need the MSM Download tools in the other thread.
Did you relock your bootloader? Flash magisk, you should be fine or fastboot flash a full firmware using the fastboot files, no need to do a full recovery with the msm tool.
Dark Nightmare said:
Did you relock your bootloader? Flash magisk, you should be fine or fastboot flash a full firmware using the fastboot files, no need to do a full recovery with the msm tool.
Click to expand...
Click to collapse
The MSM tool worked like a charm.