So this a new modified emmc_appsboot.mbn for unlocking bootloader via unofficial way.
Whats changed?
Fixed the bug of red LED blinking continuously during charging.
For those who unlocked bootloader via unofficial way from this thread http://forum.miui.co.in/forum/mi-de...5165-redmi-note-3-snapdragon-unlock-the-beast, just use this method to flash the new emmc file:-
1) Reboot to fastboot mode
2) Open CMD and type
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
The emmc file must inside the anf folder
For new comers, you can use the same method as the previous one by MAGDAG, just use this new emmc file instead of his.
This new emmc file needs thorough testing, maybe this will also cause hardbricks if MIUI roms are flashed without deleting their default emmc file (inside their rom), maybe this will not cause any such issues but nobody will take the risk of testing that. Just use this new emmc with precautions just like the previous one. How to flash MIUI roms via TWRP after unofficially unlocking bootloader? follow this guide made by me http://en.miui.com/thread-256464-1-1.html
This is not the edited version of MAGDAG's emmc file. This one's is new and needs to be tested.
I'M NOT RESPONSIBLE FOR ANY BRICKED DEVICES.
Please provide feedback if this worked for you.
How to revert back to locked state ?
fcukmayank said:
How to revert back to locked state ?
Click to expand...
Click to collapse
flash any fastboot rom in edl mode using miflash
Rajdip said:
flash any fastboot rom in edl mode using miflash
Click to expand...
Click to collapse
Will it not hardbrick if i have twrp and root ?
fcukmayank said:
Will it not hardbrick if i have twrp and root ?
Click to expand...
Click to collapse
no, I tested it
Cool . thanks for the info
But i hv global stable 7.2.3.0 and modified boot image is not yet available
I tried downgrading to 7.1.8.0 but it bootlooped at mi logo
I had to flash 7.1.8.0 again
This all drama when i have permission to unlock the xiaomi but stuck at 50% error
fcukmayank said:
Cool . thanks for the info
But i hv global stable 7.2.3.0 and modified boot image is not yet available
I tried downgrading to 7.1.8.0 but it bootlooped at mi logo
I had to flash 7.1.8.0 again
This all drama when i have permission to unlock the xiaomi but stuck at 50% error
Click to expand...
Click to collapse
I can understand, If I find the link for full 7.2.3 recovery rom today, I'll post it, if you need modified boot.img you have to first downgrade to 7.1.3.0 and use updater app, it will give a full recovery rom of 1gb for update, find the boot.img of 7.2.3.0 from that zip and modify it then flash.
P.S:- never forget to delete the original emmc_appsboot file in each rom.
Rajdip said:
I can understand, If I find the link for full 7.2.3 recovery rom today, I'll post it, if you need modified boot.img you have to first downgrade to 7.1.3.0 and use updater app, it will give a full recovery rom of 1gb for update, find the boot.img of 7.2.3.0 from that zip and modify it then flash.
P.S:- never forget to delete the original emmc_appsboot file in each rom.
Click to expand...
Click to collapse
I can downgrade to 7.1.8.0 but i hv to flash twice to overcome bootloop
Just scared of using this unofficial method as last time i bricked it and the service center had to replace the motherboard
fcukmayank said:
I can downgrade to 7.1.8.0 but i hv to flash twice to overcome bootloop
Just scared of using this unofficial method as last time i bricked it and the service center had to replace the motherboard
Click to expand...
Click to collapse
it will brick if you forget to delete the emmc_appsboot file from each rom you are flashing, otherwise you are safe to go. guide to flash without harbrick is in OP
Rajdip said:
it will brick if you forget to delete the emmc_appsboot file from each rom you are flashing, otherwise you are safe to go. guide to flash without harbrick is in OP
Click to expand...
Click to collapse
Yes
That i realised after hardbricking
Wanted root for adblocker but now i found this app called adguard
So trying to live without root
fcukmayank said:
Yes
That i realised after hardbricking
Wanted root for adblocker but now i found this app called adguard
So trying to live without root
Click to expand...
Click to collapse
:good:
Rajdip said:
:good:
Click to expand...
Click to collapse
I think i have solved the problem of 50%error
Gonna try it and apply for unlocking again
Only sd?
Sent from my Redmi Note 3 using XDA-Developers mobile app
qweewq22 said:
Only sd?
Sent from my Redmi Note 3 using XDA-Developers mobile app
Click to expand...
Click to collapse
yeah this is for snapdragon variant
Rajdip said:
yeah this is for snapdragon variant
Click to expand...
Click to collapse
Name of the zip rom : miui_HMNote3ProGlobal_V7.2.3.0.LHOMIDA_74136dde89_5.1.zip
fcukmayank said:
I think i have solved the problem of 50%error
Gonna try it and apply for unlocking again
Click to expand...
Click to collapse
Is the process of removing emmc file also required for bootloaders which have been unlocked officially ?
And hv u compared the 2 files of unofficial and official method
fcukmayank said:
Is the process of removing emmc file also required for bootloaders which have been unlocked officially ?
And hv u compared the 2 files of unofficial and official method
Click to expand...
Click to collapse
no only for unofficial method, and I compared both the official and unofficial file they are different but I know of a way by which we can unlock bootloader unofficially but it'll work just like the official way. Need someone who unlocked via official way, then flash twrp version 3.0.0-0(other versions wont work) and reboot to twrp and select backup and then scroll down and select aboot and abootbak, we can use that aboot for us and solve all problems of hardbrick, but no one's helping me :crying:
Rajdip said:
no only for unofficial method, and I compared both the official and unofficial file they are different but I know of a way by which we can unlock bootloader unofficially but it'll work just like the official way. Need someone who unlocked via official way, then flash twrp version 3.0.0-0(other versions wont work) and reboot to twrp and select backup and then scroll down and select aboot and abootbak, we can use that aboot for us and solve all problems of hardbrick, but no one's helping me :crying:
Click to expand...
Click to collapse
I have got permission twice from 2 different accounts but still stuck at 50%error
I bricked my device and the motherboard had to be replaced which took 8 days :/
---------- Post added at 04:04 PM ---------- Previous post was at 03:48 PM ----------
Keep working
The moment my official unlock happens i m gonna pull these files for u
Rajdip said:
So this a new modified emmc_appsboot.mbn for unlocking bootloader via unofficial way.
Whats changed?
Fixed the bug of red LED blinking continuously during charging.
For those who unlocked bootloader via unofficial way from this thread http://forum.miui.co.in/forum/mi-de...5165-redmi-note-3-snapdragon-unlock-the-beast, just use this method to flash the new emmc file:-
1) Reboot to fastboot mode
2) Open CMD and type
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
The emmc file must inside the anf folder.........................................)
Click to expand...
Click to collapse
Thx for mod
my redmi n3p have lock bootloader now
Reacap:
1- flash the global stable 7.1.8 (Magdag metod) with repalce emmc_appsboot.mbn modified by you
2- flash twrp
2- update rom to twrp but deleting the stock emmc_appsboot.mbn inside zip file
It's all correct?
To return to original stock rom flash the latest global stable via EDL?
fcukmayank said:
I have got permission twice from 2 different accounts but still stuck at 50%error
I bricked my device and the motherboard had to be replaced which took 8 days :/
---------- Post added at 04:04 PM ---------- Previous post was at 03:48 PM ----------
Keep working
The moment my official unlock happens i m gonna pull these files for u
Click to expand...
Click to collapse
thanks a lot man
Related
DISCLAIMER
I'm not responsible for any damage, bootloop, bricked or broken handsets.
Notice
The recovery can't be flashed to the handset with locked bootloader! Unlock it first!
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom and stock (with some remarks) ROMs to your device, repair broken file systems, and root your device.
Update 01.04.2016 (it is not a joke )
First stable release
Have fixed screen flickering and UI lagging
Update 29.03.2016
It's alive! First experimental working build published at internal 4pda Russian board.
Download
TWRP 3.0 M86 fastboot flashable image
TWRP 3.0 M86 flashable zip
Stock Recovery flashable zip
Unlocked BL flashable zip
Install
With BL unlocked reboot into fastboot mode and flash:
Code:
fastboot flash recovery TWRP_3.0_m86.img
Cautions
Before flashing stock rom with TWRP replace bootloader file with unlocked one inside rom archive!!!!
Another method is to flash unlocked BL and TWRP zips immediately after flashing stock rom (need testing)
JUST IN CASE this is an April fools.... I'll wait ?
Great mate, u've stolen my idea in the end, right ?!
Gooooood work, thank u very much ! Testing wip :highfive:
---------- Post added at 09:09 AM ---------- Previous post was at 09:04 AM ----------
Nein, first step doesn't work
Flashing unlocked BL through stock recovery, I get always the same result :
FIRMWARE CORRUPT
Click to expand...
Click to collapse
faust93 said:
Update 01.04.2016 (it is not a joke )
First stable release
Have fixed screen flickering and UI lagging
Click to expand...
Click to collapse
*Working fine
PYCON said:
Nein, first step doesn't work
Click to expand...
Click to collapse
Didn't we discuss it yesterday ? No official zip signature => not flashable with locked bootloader...
toms157 said:
Didn't we discuss it yesterday ? No official zip signature => not flashable with locked bootloader...
Click to expand...
Click to collapse
Ahahah yes yes but the purpose of BL_UNLOCKED.ZIP is to unlock bootloader. But in order to flash it correctly... we've to have the bootloader already unlocked
Damn it, it's really stupid, right ?
PYCON said:
Damn it, it's really stupid, right ?
Click to expand...
Click to collapse
Filename could lead to confusion, sure... It's needed for this :
Another method is to flash unlocked BL and TWRP zips immediately after flashing stock rom (need testing)"
Click to expand...
Click to collapse
Meanning flash 3 files from custom recovery without rebooting
Anyway this is not a catch-22, leaked beta from tutorial is the entry point
Will this work on a device that was originally the Chinese variant but changed to the international one after editing the proinfo file? I'm really eager to try this but I'd hate to jump in blindly and brick...
showofdeth said:
Will this work on a device that was originally the Chinese variant but changed to the international one after editing the proinfo file? I'm really eager to try this but I'd hate to jump in blindly and brick...
Click to expand...
Click to collapse
ID is only checked while using stock recovery .... Anyway it's safe, i'm in the same case and worked
naboleo said:
ID is only checked while using stock recovery .... Anyway it's safe, i'm in the same case and worked
Click to expand...
Click to collapse
Oh man that's great to hear! Thanks. Bought myself a laptop specifically to get my PRO 5 all TWRP'd up.
One last thing. I have updated firmwares many times in the last couple of months with full factory wipes each time, currently on the latest test version. Will the bootloader unlock in the tutorial still work? Meizu can't have patched anything. Right?
showofdeth said:
One last thing. I have updated firmwares many times in the last couple of months with full factory wipes each time, currently on the latest test version. Will the bootloader unlock in the tutorial still work? Meizu can't have patched anything. Right?
Click to expand...
Click to collapse
Never had troubles to downgrade to leaked beta
naboleo said:
Never had troubles to downgrade to leaked beta
Click to expand...
Click to collapse
Brilliant. Thanks a lot. Can't wait to hear people's experiences with this.
mate problem solved..now finally i can go into twrp it's fantastic but there is a problem...when i try to put a update.zip (nodified with unlock bootloader) the pc give me an error: impossible transfer file and the phone reboot
That TWRP works perfectly for me, backup nandroid, restore it, flash ZIP rom and ZIP other ( Xposed, etc ), no problem at all :highfive:
Good job !!! Great, thx !!!
Thank you so much for this!!! could i ask you how you managed to create a recovery for the pro5?
Solitario88 said:
mate problem solved..now finally i can go into twrp it's fantastic but there is a problem...when i try to put a update.zip (nodified with unlock bootloader) the pc give me an error: impossible transfer file and the phone reboot
Click to expand...
Click to collapse
I assume youare still on 5.6.1.19: Thats an error with this version.... put the updatefile manually (in the PC) on the external sd and flash via TWRP... you should later update your modified Pro 5 to 5.1.3.0, the error ist gone then...
Solitario88 said:
mate problem solved..now finally i can go into twrp it's fantastic but there is a problem...when i try to put a update.zip (nodified with unlock bootloader) the pc give me an error: impossible transfer file and the phone reboot
Click to expand...
Click to collapse
Copy UPDATE.ZIP from PC to phone BUT CONNECTING THE PHONE WHEN IT'S OPENED TWRP
MTP mode works great, even u'r on 5.6.1.19 :highfive:
Sometimes... Rarely... A strange thing happens :
I go to INSTALL in order to flash a ZIP of something but... NO MEMORY SEEMS TO BE ACCESSIBLE
If I reboot another time into recovery, all my memory contents is perfect and visible... :silly: Really strange !!!
PYCON said:
Sometimes... Rarely... A strange thing happens :
I go to INSTALL in order to flash a ZIP of something but... NO MEMORY SEEMS TO BE ACCESSIBLE
If I reboot another time into recovery, all my memory contents is perfect and visible... :silly: Really strange !!!
Click to expand...
Click to collapse
Have you installed the updated TWRP (20-04-16) : http://xep.8800.org/pro5/
I tried the old (30-03-16), and I noticed some bugs, like flash screen when touching the screen buttons...
Maybe I helped you :laugh:
cedric3 said:
Have you installed the updated TWRP (20-04-16) : http://xep.8800.org/pro5/
I tried the old (30-03-16), and I noticed some bugs, like flash screen when touching the screen buttons...
Maybe I helped you :laugh:
Click to expand...
Click to collapse
Uh I didn't know that a new version was released... Maybe, I could be. I download it again and try... Thx man ! :highfive:
The last version can't read the micro sd.
hi there it's been a loooong time search on the internet and ... no answers to my problems so yeah hello !
I have a Zenfone 2 laser ZE500KL and a custom recovery (twrp 2.8.7.7) and my phone have no OS installed (i don't know why) i tried many times to install the asus marshmallow update from fastboot, adb push, adb sideload, but nothing work and i have a little word saying "This package is for WW_phone devices; this is a omni_Z00E" followed by "Updater process ended with ERROR: 7" and "Error installing zip finle '/sdcard/UL-ASUS_Z00E-WW-13.10.7.2-user.zip'" i don't know what this mean and i want to know because i am a little lost.
thanks
alex
edit of 19/06/2016
YAY finally it finished after days of "no my phone wil never work again" it's finally over with a big YAY
so thanks to @sziraqui for his help and @tanker456 for the last help he gives me before i give up you two guys are the best !
so for more info and help i give you these two guys that are awesome !
contents box
http://forum.xda-developers.com/zenfone-2-laser/help/unable-update-to-marshmallow-via-ota-t3389876
Sziraqui
What are you trying to flash? Custom kernel? Stock boot.img?
Either the .img is corrupt/incompletely downloaded OR you have unlocked boot loader using unofficial method.
1. Download the boot.img and try again
2. If it still gives error, you do not have a proper bootloader unlock. Try flashing twrp that is confirmed working by you, to verify if bootloader is properly unlocked or not.
Tanker456
try this firmware called backtostock here
http://forum.xda-developers.com/zenf...flash-t3365237
it will work for sure. but if it dosen't
you can go with this one too
http://forum.xda-developers.com/zenf...550kl-t3236264
Alex07060 there is boot image of 1.13 firmware, u can try that
LuK1447 post that saved my life too
http://forum.xda-developers.com/zen...50kl-ze551kl-zd551kl-ze600kl-ze601kl-t3333482
Click to expand...
Click to collapse
Hi have the same problame i have searched and you can flash http://androiding.how/install-ota-update-twrp-zenfone-2/ try this method please and say if it work or no
Alex070609 said:
hi there it's been a loooong time search on the internet and ... no answers to my problems
"This package is for WW_phone devices; this is a omni_Z00E" followed by "Updater process ended with ERROR: 7" and "Error installing zip finle '/sdcard/UL-ASUS_Z00E-WW-13.10.7.2-user."
Click to expand...
Click to collapse
If you had spent enough time searching on xda, you would have got the solution. I posted a solution to this here http://forum.xda-developers.com/zenfone-2-laser/help/unable-update-to-marshmallow-via-ota-t3389876 And the thread is marked "solved" which means it worked.
sziraqui said:
Apparently, your current recovery version does not match with your current firmware version. There are two possible workarounds-
1. Wipe system by executing "fastboot erase system" in fastboot mode. Then reflash latest official asus lollipop ROM. This will fix the recovery and firmware mismatch and you will then be able to flash MM via stock recovery.
2. If you are experienced with edit8ng updater-script, Extract all contents of MM ota. Open updater-script and remove all asserts and lines that say "abort". Then compress the contents again. (You can't edit without extracting coz zip is signed). Flash this modified ota zip via TWRP.
If you still can't flash it or you are unable to edit updater-script, pm me, I have downloaded the MM ROM, I will send you modified updater-script.
I can even convert this ota into .imgs so that you can flash directly via fastboot
Click to expand...
Click to collapse
Click on the small "play" icon in below quote and you will be redirected to the original post where I uploaded updater-script. This also answers @ericpeacock79 's question on flashing stock rom on twrp.
sziraqui said:
alright, download the updater-script from attachment. Flash via TWRP.
Detailed instructions-
First extract entire ota zip. Delete the original updater-script.
Then extract "updater-script_modified.zip"
Copy the extracted "updater-script" to extracted ota at the right location. (META-INF/com/google/android)
Compress the ota files as a zip using 7zip or winrar. Compression level "normal" . DONT USE ANY ANDROID APP FOR COMPRESSING, USE WINDOWS/LINUX APP ONLY.
Flash the modified zip via TWRP recovery
Click to expand...
Click to collapse
@sziraqui You are awesome. Thank you.
Click on the small "play" icon in below quote and you will be redirected to the original post where I uploaded updater-script. This also answers @ericpeacock79 's question on flashing stock rom on twrp.[/QUOTE]
Feels good when sum1 helps even if there is a repeated question. Most people will say "search before you post/ don't bump the forum/ etc. and provide links which are difficult for new users to follow. You are one of the few devs who are offer REAL help. Hatts off!
sziraqui said:
If you had spent enough time searching on xda, you would have got the solution. I posted a solution to this here http://forum.xda-developers.com/zenfone-2-laser/help/unable-update-to-marshmallow-via-ota-t3389876 And the thread is marked "solved" which means it worked.
Click on the small "play" icon in below quote and you will be redirected to the original post where I uploaded updater-script. This also answers @ericpeacock79 's question on flashing stock rom on twrp.
Click to expand...
Click to collapse
Hi i have the same problame problame and i have the stock firmware as a zip file do you can help me
@sziraqui Yes it works the installation is done BUT i got an new error "ERROR: Can't load invalid boot image" i need a little bit more help and many thanks for the help give to me right now its fantastic
Alex
Alex070609 said:
@sziraqui Yes it works the installation is done BUT i got an new error "ERROR: Can't load invalid boot image" i need a little bit more help and many thanks for the help give to me right now its fantastic
Alex
Click to expand...
Click to collapse
Hey please if you can do it for me and upload the Rom modified because my computer is broken
Alex070609 said:
@sziraqui Yes it works the installation is done BUT i got an new error "ERROR: Can't load invalid boot image" i need a little bit more help and many thanks for the help give to me right now its fantastic
Alex
Click to expand...
Click to collapse
What are you trying to flash? Custom kernel? Stock boot.img?
Either the .img is corrupt/incompletely downloaded OR you have unlocked boot loader using unofficial method.
1. Download the boot.img and try again
2. If it still gives error, you do not have a proper bootloader unlock. Try flashing twrp that is confirmed working by you, to verify if bootloader is properly unlocked or not.
My bootloader is unlocked unofficial and i need to flash the stock Rom using twrp
---------- Post added at 01:56 PM ---------- Previous post was at 01:56 PM ----------
sziraqui said:
What are you trying to flash? Custom kernel? Stock boot.img?
Either the .img is corrupt/incompletely downloaded OR you have unlocked boot loader using unofficial method.
1. Download the boot.img and try again
2. If it still gives error, you do not have a proper bootloader unlock. Try flashing twrp that is confirmed working by you, to verify if bootloader is properly unlocked or not.
Click to expand...
Click to collapse
My bootloader is unlocked unofficial and i need to flash the stock Rom using twrp
i have actually a right bootloader (official) but each time i triying to flash a boot.img it says file corrupted so i don't know how to do it do you have a boot.img correct to do that ?
thanks in advance
alex
sziraqui said:
What are you trying to flash? Custom kernel? Stock boot.img?
Either the .img is corrupt/incompletely downloaded OR you have unlocked boot loader using unofficial method.
1. Download the boot.img and try again
2. If it still gives error, you do not have a proper bootloader unlock. Try flashing twrp that is confirmed working by you, to verify if bootloader is properly unlocked or not.
Click to expand...
Click to collapse
Hey please does this method work a full Rom
hu what ?
@sziraqui Okey news of the day i find a correct boot.img but i get a bootloop yeah ! so what can i do now ?
alex
The problem u must do is find stock recovery of firmware 6.0 then u can sideload stock rom 6.0 ^^
I use ze500kg same ur phone, maybe i can help you
Contact me facebook: [email protected]
mohamedelkholy said:
My bootloader is unlocked unofficial and i need to flash the stock Rom using twrp
---------- Post added at 01:56 PM ---------- Previous post was at 01:56 PM ----------
My bootloader is unlocked unofficial and i need to flash the stock Rom using twrp
Click to expand...
Click to collapse
try this firmware called backtostock here
http://forum.xda-developers.com/zen...guide-how-to-revert-to-stock-reflash-t3365237
it will work for sure. but if it dosen't
you can go with this one too
http://forum.xda-developers.com/zenfone-2-laser/general/root-ze550kl-t3236264
Alex07060 there is boot image of 1.13 firmware, u can try that
well with your indications a get a bootloop something else could help ? @tanker456
Alex070609 said:
well with your indications a get a bootloop something else could help ? @tanker456
Click to expand...
Click to collapse
i didn't understand what said,
did u get a bootloop or
are say that u would get a bootloop
Sent from my ASUS_Z00LD using XDA-Developers mobile app
look i had a bootloop ~20 mins and retry with a second link post and voila ! i get a phone that work it's done
Alex070609 said:
look i had a bootloop ~20 mins and retry with a second link post and voila ! i get a phone that work it's done
Click to expand...
Click to collapse
hmm good to hear it
Sent from my ASUS_Z00LD using XDA-Developers mobile app
Hello.
With hexeditor, I've seen that:
MM aboot:
Code:
fastboot mode.
dload mode key sequence detected
%s%sINFO%sFAILCould not allocate memory for fastboot buffer
.app/aboot/fastboot.cunknown reasonunknown commandOKAYdata too largeDATA%08xdwcUSB30 needs to be enabled for this target.
getvar:download:version0.5fastboot
LP aboot:
Code:
fastboot mode.
dload mode key sequence detected
oem read_regoem read_pmicflash:erase:continuerebootreboot-bootloaderoem unlockoem lockoem verifiedoem device-infopreflashoem enable-charger-screenoem disable-charger-screenoem select-display-paneloem boot-cpusoem big-freqoem small-freq boot_cpus= androidboot.earlyboot_cpus=%s%sCould not allocate memory for fastboot buffer
.app/aboot/fastboot.c
You can see the difference ?
All commands are erased on MM aboot so, no chance for us to unlock or using fastboot on our phone with MM
murigny64 said:
Hello.
With hexeditor, I've seen that:
MM aboot:
Code:
fastboot mode.
dload mode key sequence detected
%s%sINFO%sFAILCould not allocate memory for fastboot buffer
.app/aboot/fastboot.cunknown reasonunknown commandOKAYdata too largeDATA%08xdwcUSB30 needs to be enabled for this target.
getvar:download:version0.5fastboot
LP aboot:
Code:
fastboot mode.
dload mode key sequence detected
oem read_regoem read_pmicflash:erase:continuerebootreboot-bootloaderoem unlockoem lockoem verifiedoem device-infopreflashoem enable-charger-screenoem disable-charger-screenoem select-display-paneloem boot-cpusoem big-freqoem small-freq boot_cpus= androidboot.earlyboot_cpus=%s%sCould not allocate memory for fastboot buffer
.app/aboot/fastboot.c
You can see the difference ?
All commands are erased on MM aboot so, no chance for us to unlock or using fastboot on our phone with MM
Click to expand...
Click to collapse
Did you try to modify Mm aboot?
No can't modify, it's RSA signed.
But, if you see more, there is %s%sINFO%sFAIL after "detected", and OKAYa little further. That is not present in LP aboot.
Perhaps, we have to enter a "magic keyword" to decrypt some features ?
I know, santa clause doesn't no exist
maybe @Unjustified Devcan be our santa, where is he
yash_rathore25 said:
maybe @Unjustified Devcan be our santa, where is he
Click to expand...
Click to collapse
or waiting for info from Alcatel (sending mail)
murigny64 said:
or waiting for info from Alcatel (sending mail)
Click to expand...
Click to collapse
@Alek Dev and myself also sent mail to them but no reply till date
yash_rathore25 said:
@Alek Dev and myself also sent mail to them but no reply till date
Click to expand...
Click to collapse
Yes i sent 3 emails but there's no reply
Alek Dev said:
Yes i sent 3 emails but there's no reply
Click to expand...
Click to collapse
yeah so wierd ?
---------- Post added at 06:48 PM ---------- Previous post was at 06:46 PM ----------
Looks like instead of waiting for unlock, i have to do whole process to gain root.
which will cost me heavy
Alek Dev said:
Yes i sent 3 emails but there's no reply
Click to expand...
Click to collapse
Can you create a "petition" thread with info to send a mail to alcatel to unlock phone and fastboot ?
more mails, more bored :cyclops::silly:
murigny64 said:
Can you create a "petition" thread with info to send a mail to alcatel to unlock phone and fastboot ?
more mails, more bored :cyclops::silly:
Click to expand...
Click to collapse
LOL
HERE'S
link to thread
You want MM with fastboot? All you need to do is backup your existing MM via twrp. Use mobile q to downgrade your device to 5.0.2. Unlock bootloader and flash twrp then restore your backup of system/boot. You will be just like the non 6045i variants..on mm with full fastboot and twrp.
famewolf said:
You want MM with fastboot? All you need to do is backup your existing MM via twrp. Use mobile q to downgrade your device to 5.0.2. Unlock bootloader and flash twrp then restore your backup of system/boot. You will be just like the non 6045i variants..on mm with full fastboot and twrp.
Click to expand...
Click to collapse
Doesn't work..i tested..it will stay at alcatel powered by android because again THE system to boot needs adintional new partitions
famewolf said:
You want MM with fastboot? All you need to do is backup your existing MM via twrp. Use mobile q to downgrade your device to 5.0.2. Unlock bootloader and flash twrp then restore your backup of system/boot. You will be just like the non 6045i variants..on mm with full fastboot and twrp.
Click to expand...
Click to collapse
Yes, everybody know that. But when mobile upgradeQ are released with MM, how can you do
We have to think to future.
murigny64 said:
Yes, everybody know that. But when mobile upgradeQ are released with MM, how can you do
We have to think to future.
Click to expand...
Click to collapse
Then I'd use the panasonic eluga software and flash a locally saved copy. In future I won't be installing Alcatel updates directly. I'll grab the update.zip and remove any code for partitions other than system/boot. Should allow retention. Your point is still understood however. The first time I've ever used mobile q was tonight and ironically it was because I was trying to build a flashable zip to restore the old partitions so users could restore fastboot without having to run mobile Q. I managed to turn it into a paperweight then recovered it but decided to go ahead and use mobile q to downgrade while I was at it. I'm a linux user so I had to set up a windows laptop for this purpose.
Flashable zips for MM and Fastboot
How about this then......flashable zips for MM and fastboot.
Install the first one and you get TWRP 3.0 as well as the files you need to restore fastboot access. TWRP will let you boot straight to the bootloader.
Restore the 2nd one and you get TWRP 3.0 as well as the files you need to boot a mm rom.
You can swap between them as needed. You should not even have to mess with your mm rom if you just need quick fastboot access. The files are from a 6045i but should work for any of the variants.
Contents: twrp 3.0, aboot,spl1,hyp,rpm and tz. Does not overwrite modem.
famewolf said:
How about this then......flashable zips for MM and fastboot.
Install the first one and you get TWRP 3.0 as well as the files you need to restore fastboot access. TWRP will let you boot straight to the bootloader.
Restore the 2nd one and you get TWRP 3.0 as well as the files you need to boot a mm rom.
You can swap between them as needed. You should not even have to mess with your mm rom if you just need quick fastboot access. The files are from a 6045i but should work for any of the variants.
Click to expand...
Click to collapse
how can i directly flash on MM, stock recovery will not detect it. Previously i was trying to supersu directly from stock MM recovery but it wa not detecting it.
i have to use mobile upgrade q n downgrade n do the whole process
yash_rathore25 said:
how can i directly flash on MM, stock recovery will not detect it. Previously i was trying to supersu directly from stock MM recovery but it wa not detecting it.
i have to use mobile upgrade q n downgrade n do the whole process
Click to expand...
Click to collapse
Stock recovery won't flash anything that isn't signed by Alcatel. You HAVE to use TWRP.
It depends...I'm not sure if they left the fastboot boot command in which just boots a file without installing it....it would allow you to boot twrp and THEN use it to flash my zips.
famewolf said:
Stock recovery won't flash anything that isn't signed by Alcatel. You HAVE to use TWRP.
It depends...I'm not sure if they left the fastboot boot command in which just boots a file without installing it....it would allow you to boot twrp and THEN use it to flash my zips.
Click to expand...
Click to collapse
no it is not letting twrp even to boot.
famewolf said:
How about this then......flashable zips for MM and fastboot.
Install the first one and you get TWRP 3.0 as well as the files you need to restore fastboot access. TWRP will let you boot straight to the bootloader.
Restore the 2nd one and you get TWRP 3.0 as well as the files you need to boot a mm rom.
You can swap between them as needed. You should not even have to mess with your mm rom if you just need quick fastboot access. The files are from a 6045i but should work for any of the variants.
Contents: twrp 3.0, aboot,spl1,hyp,rpm and tz. Does not overwrite modem.
Click to expand...
Click to collapse
Hello @famewolf
I'm becoming lost with all these discussions and things to flash.
I want to flash a MM ROM (material by The Marionette). Py phone is running stock rooted 5.0.2, with fastboot commands working.
Which files do I need to make the MM ROM boot, and not lose fastboot command ? If I do understand, I just need to flash the second zip you provided and flash mm rom. Then , if I lose fastboot, I flash the first one. Do I have understood well ?
frankee207 said:
Hello @famewolf
I'm becoming lost with all these discussions and things to flash.
I want to flash a MM ROM (material by The Marionette). Py phone is running stock rooted 5.0.2, with fastboot commands working.
Which files do I need to make the MM ROM boot, and not lose fastboot command ? If I do understand, I just need to flash the second zip you provided and flash mm rom. Then , if I lose fastboot, I flash the first one. Do I have understood well ?
Click to expand...
Click to collapse
If you want to boot a marshmallow rom then you need the file that says it's to boot a marshmallow rom. You WILL lost fastboot...you however will keep twrp. If you ever NEED fastboot you can flash the other one to temporarily downgrade and then access bootloader/fastboot via TWRP..then when done with fastboot flash the 1st one again to boot a mm rom.
Ok folks you're here because you have the need to root​MM 6 or Nougat 7.0 Only
As of February 2017 you need 3 things
Unlocked Bootloader
Motorola Device Manger (drivers):Download
1) TWRP ( Recovery)
2) Modified kernel (F2FS fixes)
3) SuperSu 2.79 R3 systemless root
TWRP can be found Here: TWRP
Modified Kernel can be found here:TWRP & Modified kernel
Download both the modified kernel, either the MM one Or Nougat 7.0, depending on which OS you are using and download the modified kernel to your internal sd card ( Our external sdcard can't be read by TWRP, so all flashable zips must be in your internal sdcard)
Flash recovery through fastboot Code: fastboot flash recovery (name of recovery).img
Do not reboot but use the volume buttons on the phone to select recovery from the menu on the fastboot screen.
Now we can flash the Modified Kernel which you have previously downloaded to your internal sd card.
Flash the Kernel.
Now download SuperSu
SuperSu:SuperSu 2.79 R3
NEW FOR NOUGAT 7.1.1 ONLY
Unlocked bootloader
Motorola device manager Download:Download["]Moto Device Manager
Twrp recovery downloaded into the same folder as fastboot
Gaining root differs from 7.0 or 6.0, you can only root with magisks 13 or above if you are running any stock based rom or custom based rom that doesn't have built in root, you no longer need to flash the F2FS fixed kernel on 7.1.1
Magisks Thread :Magisks Thread
You need to flash Magisks to disable dm-verity otherwise your phone will not boot this is because the stock kernel checks for any modifications to the system
That's it
Thanks to @Alberto97 & @tomparr
Will be useful for noobies
Enviado desde mi XT1635-02 mediante Tapatalk
Do you suggest disabling force encryption. I'm rooted but encrypted currently. If disabling would make significant speed boost I'm willing to take the pain of setting-up apps and stuff from scratch and format userdata
Nil253259 said:
Do you suggest disabling force encryption. I'm rooted but encrypted currently. If disabling would make significant speed boost I'm willing to take the pain of setting-up apps and stuff from scratch and format userdata
Click to expand...
Click to collapse
I'm unecrytped and see real no gain, I think it's more of a placebo effect.
is that superSU better than Magisk?
Do you still need official bootloader unlocking ? aka no more warranty ? Thanks
razorsbk said:
Do you still need official bootloader unlocking ? aka no more warranty ? Thanks
Click to expand...
Click to collapse
Yes
Thank you.
Sent from my XT1635-02 using Tapatalk
Will all this work with Windows 10?
shawnsac2000 said:
Will all this work with Windows 10?
Click to expand...
Click to collapse
It will if you have the right drivers installed
punkerEVO said:
is that superSU better than Magisk?
Click to expand...
Click to collapse
It's confirmed that you'll have root with SuperSu 2.79 R3, Magisk's may cause Issues under certain circumstances.
I'ver tried to keep as simple as possible because there's 2 other threads with root method's that are not up to date.
Thanks
dedraks said:
Thanks
Click to expand...
Click to collapse
Lol OK I can see where this could get confusing now.
Thanks flashallthetime.
I misread your instructions though and I am in trouble. I misread the bit about copying the modified kernel to internal SD card; instead I copied to external SD card (as I have always done with previous devices). I now can't flash the modified kernel because the newly flashed TWRP 3.0.2 doesn't have access to the external SD card.
The current state of the device is that it is stuck at the unlocked warning screen. It says "ID: bad key", but after flashing a recovery, it says "ID: N/A".
Is this consistent with the kernel not being flashed, or do I have another issue?
If I get an OTG cable, can I flash the modified kernel that way with TWRP? Can this version of TWRP access an OTG USB device on Moto Z Play?
Anyone? Thanks so much!!
You can use fastboot to flash boot.img.
---------- Post added at 02:28 PM ---------- Previous post was at 02:25 PM ----------
punkerEVO said:
Lol OK I can see where this could get confusing now.
Click to expand...
Click to collapse
How?
dedraks said:
You can use fastboot to flash boot.img.
Click to expand...
Click to collapse
Is that to me? Which boot.img, where do I find it? Thanks!
raymosaurus said:
Is that to me? Which boot.img, where do I find it? Thanks!
Click to expand...
Click to collapse
Yes.
Extract from the ROM in this post:
https://forum.xda-developers.com/moto-z-play/development/rom-stock-7-0-t3553213
raymosaurus said:
If I get an OTG cable, can I flash the modified kernel that way with TWRP? Can this version of TWRP access an OTG USB device on Moto Z Play?
Click to expand...
Click to collapse
Should do fine. Did not test with this version, but using Chinese twrp I could mount and afterwards access OTG partition. Don't see a reason why this one should behave differently.
If you want to use fastboot, the command should be (from memory): fastboot flash boot boot.img
tag68 said:
Should do fine. Did not test with this version, but using Chinese twrp I could mount and afterwards access OTG partition. Don't see a reason why this one should behave differently.
If you want to use fastboot, the command should be (from memory): fastboot flash boot boot.img
Click to expand...
Click to collapse
For God's sake people , don't use the Chinese TWRP. 2 people that I know have mistakenly wiped their IMEI with that junk.
dedraks said:
You can use fastboot to flash boot.img.
---------- Post added at 02:28 PM ---------- Previous post was at 02:25 PM ----------
How?
Click to expand...
Click to collapse
I have a flashable zip of the Nougat stock boot.img
Here https://www.androidfilehost.com/?fid=457095661767138793
Here's the patched boot.img for OnePlus 8T Android 13 KB2005_11_F.13 and F.15
Bootloader must be unlocked
(Have the img on your PC)
Instructions:
1: Reboot to bootloader "adb reboot bootloader"
2: Run CMD "fastboot flash boot" ~name of img~
Profit!
You're now rooted.
I've also attached the stock boot.img just in case anyone wants it.
Boot - Google Drive
drive.google.com
Thank's
BobbyLynn said:
Here's the patched boot.img for OnePlus 8T Android 13 KB2005_11_F.13
Bootloader must be unlocked
(Have the img on your PC)
Instructions:
1: Reboot to bootloader "adb reboot bootloader"
2: Run CMD "fastboot flash boot magisk_patched-25200_575Sf.img"
You're now rooted.
I've also attached the stock boot.img just in case anyone wants it.
Boot - Google Drive
drive.google.com
Click to expand...
Click to collapse
what if there is ota update?
MevishL said:
what if there is ota update?
Click to expand...
Click to collapse
I highly doubt there'll be another OTA until next month. Check with the developer of the unofficial orange fox recovery, he'll most likely release a new version for A13. If not, I'll pull the boot.img and patch it again and post it here.
MevishL said:
what if there is ota update?
Click to expand...
Click to collapse
Nevermind he's already released a version for A13. Here it is
Thread '[RECOVERY][UNOFFICIAL] OrangeFox Recovery Project [OnePlus 8t / 9r] [13-Nov-2022]' https://forum.xda-developers.com/t/...ry-project-oneplus-8t-9r-13-nov-2022.4391139/
BobbyLynn said:
I highly doubt there'll be another OTA until next month. Check with the developer of the unofficial orange fox recovery, he'll most likely release a new version for A13. If not, I'll pull the boot.img and patch it again and post it here.
Click to expand...
Click to collapse
okay thx , much appreciated
BobbyLynn said:
Nevermind he's already released a version for A13. Here it is
Thread '[RECOVERY][UNOFFICIAL] OrangeFox Recovery Project [OnePlus 8t / 9r] [13-Nov-2022]' https://forum.xda-developers.com/t/...ry-project-oneplus-8t-9r-13-nov-2022.4391139/
Click to expand...
Click to collapse
what if i bricked my phone , how do i flash stock file. do i need to download it in oxygen updater , and then?
MevishL said:
what if i bricked my phone , how do i flash stock file. do i need to download it in oxygen updater , and then?
Click to expand...
Click to collapse
Lol don't tell me you've bricked it!!! You can probably flash the stock boot.img and that might fix it. Otherwise you'll have to use the msm tool to reflash the firmware.
BobbyLynn said:
Lol don't tell me you've bricked it!!! You can probably flash the stock boot.img and that might fix it. Otherwise you'll have to use the msm tool to reflash the firmware.
Click to expand...
Click to collapse
no i didn't ! i'm just scared i might brick it cuz oneplus is harder to deal with than my previous phones . thnks for helping
MevishL said:
no i didn't ! i'm just scared i might brick it cuz oneplus is harder to deal with than my previous phones . thnks for helping
Click to expand...
Click to collapse
Well if you're worried about bricking it then before you start making modifications, be sure to have the latest msm for it on your PC, and also take a full backup using Orange Fox recovery, and also have the stock boot.img on your PC. And if anything goes wrong just flash the stock boot.img. And if that doesn't fix it then restore the backup, and if that still doesn't work then you'll have to do a complete restore using a msm tool
BobbyLynn said:
Well if you're worried about bricking it then before you start making modifications, be sure to have the latest msm for it on your PC, and also take a full backup using Orange Fox recovery, and also have the stock boot.img on your PC. And if anything goes wrong just flash the stock boot.img. And if that doesn't fix it then restore the backup, and if that still doesn't work then you'll have to do a complete restore using a msm tool
Click to expand...
Click to collapse
BobbyLynn said:
Well if you're worried about bricking it then before you start making modifications, be sure to have the latest msm for it on your PC, and also take a full backup using Orange Fox recovery, and also have the stock boot.img on your PC. And if anything goes wrong just flash the stock boot.img. And if that doesn't fix it then restore the backup, and if that still doesn't work then you'll have to do a complete restore using a msm tool
Click to expand...
Click to collapse
now u made it clear in my head , thx for all
MevishL said:
now u made it clear in my head , thx for all
Click to expand...
Click to collapse
No problem. If you run into any problems just let me know and I'll do what I can to figure out the simplest solution
I flash this boot.img and work like a charm easy root. Don't forget to post boot for next updates for KB2005. Thanks
Can these instructions be used for the KB2007?
kevinco1 said:
Can these instructions be used for the KB2007?
Click to expand...
Click to collapse
If it's Android 13 11_F.13 then yes. But Orange Fox has a working recovery for A13 on our phone. So you can always flash Magisk that way if you want
MrOnizuka said:
I flash this boot.img and work like a charm easy root. Don't forget to post boot for next updates for KB2005. Thanks
Click to expand...
Click to collapse
As long as I have this phone I'll continue to post the patched boot.img after each update
BobbyLynn said:
As long as I have this phone I'll continue to post the patched boot.img after each update
Click to expand...
Click to collapse
It is your time to shine again, good sir F.15 is upon us!
Thank you, kindly.
BobbyLynn said:
As long as I have this phone I'll continue to post the patched boot.img after each update
Click to expand...
Click to collapse
i have kb2005 but when i install ota update f.15 , it says installation failed at 26% . before that , i fastboot flashed stock boot.img. What should i do ?
Marduc said:
It is your time to shine again, good sir F.15 is upon us!
Thank you, kindly.
Click to expand...
Click to collapse
Thanks for reminding me. I'll upload the new boot.img shortly
MevishL said:
i have kb2005 but when i install ota update f.15 , it says installation failed at 26% . before that , i fastboot flashed stock boot.img. What should i do ?
Click to expand...
Click to collapse
You did flash unmodified boot.img before trying to update? Well, honestly idk why it won't install. Maybe you should try a different method of installing the update, like manually installing it