Related
So. I deceided to join this forum in order to ask for some help from all those people I saw while searching the net.
I have to admit I am quite a noob with mobile systems, although I have gone way too far the last 3 days!
Here is the problem: I have an mt6575 processor phone in which want to add Greek Language settings. I have downloaded a folder form the manufacture's site, but it didn't contain any instructions. Just some .bin files (ALICE.BIN VIVA.bin, SANSTAR50_6464_11B_BOOTLOADER_V005_MT6250_MAUI_11B_W11_32_SP_V1.bin and ZIMAGE_ER.bin)and a scatter file that can not be read by flash tool (scatSANSTAR50_6464_11B.txt).
After a lot of reading around here and a lot of other forums and sites I realised that in order to do anything, I had to root my phone. I wasn't able to do it through superclick or mtk droid tools so I followed the instructions I found here:
http://forum.xda-developers.com/showthread.php?t=2160490&styleid=18
However, I am stuck on the final step.. I can't seem to get my phone on cwm mode... In fact I am not sure I know what exactly this is. I manage to open my phone on the android recovery utility but I am not able to make any choice. Everytime I press some of the menu's choises an android robot with an exclamation mark fills the screen and nothing happens...
Anyway..even if I manage to finalize the rooting process.. I still don't know what to do with the files I have... should I use them somehow on flash tool?
By the way.. The files come with a tool called Multiport Download Flash Tool which looks like Sp flash tool but has too many port options.
I'd be glad if someone helped me with this!
Thank you in advance,
Irene
1. Dump your stock recovery image then make a cwm or twrp (preferably twrp) from yueweng's thread for mediatek devices via old cwm or twrp port tool
2. Flash it via sp flash tool (download MTK 6575 scatter from internet)
3. Then reboot into recovery and if in twrp then reboot and it will ask you to root it or not
Or
If in cwm then download supersu Flash zip file and flash it
You have root access now
Press thanks if helped
Hey all.
Easy question I hope! I've been following the guide to unbrick MTK devices, and have managed to get an original factory ROM to flash to the phone, green tick in SP Flash Tools. However, the phone still won't power on at all, save for the light if plugged into usb.
The ROM I've been using is an original factory rom named "ONE-TOUCH-4015X_POP_C1_FULL_STOCK_BACKUP" which is readily available online. I'm not sure what I did to brick it in the first place, but it was within SP flashtool. I May have formatted accidentally.
If someone coudl help I'll try to provide all logs or files requested but please tell me where these could be found as I'm not that good with flash tool.
To confirm the phone won't boot into any mode, recovery is dead, fastboot is dead....
same problem hope somone help us
also share ur backup please
darkglobe87 said:
Hey all.
Easy question I hope! I've been following the guide to unbrick MTK devices, and have managed to get an original factory ROM to flash to the phone, green tick in SP Flash Tools. However, the phone still won't power on at all, save for the light if plugged into usb.
The ROM I've been using is an original factory rom named "ONE-TOUCH-4015X_POP_C1_FULL_STOCK_BACKUP" which is readily available online. I'm not sure what I did to brick it in the first place, but it was within SP flashtool. I May have formatted accidentally.
If someone coudl help I'll try to provide all logs or files requested but please tell me where these could be found as I'm not that good with flash tool.
To confirm the phone won't boot into any mode, recovery is dead, fastboot is dead....
Click to expand...
Click to collapse
Did you ever get the above rom to work? If so what did you do? Or did you find another method to unbrick the phone? Thanks.
Managed to unbrick my 4015 using Mobile Upgrade S 4.3.0 from the Alcatel Website.
http://www.alcatelonetouch.com/global-en/support/download/one_touch_idolx.html
Very simple to use, just install and follow instructions.
darren1 said:
Managed to unbrick my 4015 using Mobile Upgrade S 4.3.0 from the Alcatel Website.
http://www.alcatelonetouch.com/global-en/support/download/one_touch_idolx.html
Very simple to use, just install and follow instructions.
Click to expand...
Click to collapse
no work this version. yes 4015 but no 4015x
Sorry I should have put my phone is a 4015X not 4015. The application does say 4015 which I selected and all went well.
my 4015x no update, it not load, only work flash mode connected to pc and no work mobile upgrade.
4015X Partitions
the 4015x has a different set of partitions to the older (dual sim) 4015
i have a modded rom (kitkat), a modded stock recovery (as stock is also wrong, wont mount data) and a modded cwmrecovery.
i will be posting these soon
i will create a new post for the 4015x version
and will also be asking for other versions of the 4015 users to post me there partition trees and i will repack some recoverys and some roms for you all
note: there are 6 versions that i have seen and they may all have diff tables
hope these will help the pop c1 community
recoverys and rom
Stock Recovery (Fixed)
https://drive.google.com/file/d/0B4ZKFXlQiHioVUExRW1sZkdzSFk/view?usp=sharing
CWMRecovery (Fixed)
https://drive.google.com/file/d/0B4ZKFXlQiHioUTJqOTMtbUNPTEU/view?usp=sharing
kitkat-cm11-modROM.zip (Fixed)
https://drive.google.com/file/d/0B4ZKFXlQiHioUUI3V2Jsd0lTN1k/view?usp=sharing
(I am currently using this rom my self and all seems to be good except vibration, it also thinks its a dual sim but not causing a probb)
Hello!
This thread is quite old but near my case.
I have an Alcatel Pop C1 4015X (cpu MTK6572M) that can't start at all (only the power LED is ON).
I have a backup of this device made with "SP Flash Tool V5.1532.00" but I've error "not enough space" when
I try to restore it.
Same error when I try to restore just one file.
For example, I've tried to restore only the "Stock Recovery" you give above.
I do this:
- I start Flash_Tool v5.1532.00
- I open scatter file from my backup done with the same tool
- I unselect all pieces of the backup except "Recovery" and I browse to the "Stock Recovery" file I've dl
from this thread.
I've got this error : "not enough storage space (1011)"
What could be the problem ?
I makes me totally crazy !
By advance, thanks for your help.
Regards,
Freeman.
Fr33M4n! said:
Hello!
This thread is quite old but near my case.
I have an Alcatel Pop C1 4015X (cpu MTK6572M) that can't start at all (only the power LED is ON).
I have a backup of this device made with "SP Flash Tool V5.1532.00" but I've error "not enough space" when
I try to restore it.
Same error when I try to restore just one file.
For example, I've tried to restore only the "Stock Recovery" you give above.
I do this:
- I start Flash_Tool v5.1532.00
- I open scatter file from my backup done with the same tool
- I unselect all pieces of the backup except "Recovery" and I browse to the "Stock Recovery" file I've dl
from this thread.
I've got this error : "not enough storage space (1011)"
What could be the problem ?
I makes me totally crazy !
By advance, thanks for your help.
Regards,
Freeman.
Click to expand...
Click to collapse
What i did was i used SPFT to flash a backup i found online. Can't post links, just google "ot 4015X Original SPFT ROM", what i used was the algerian rom. Then i flashed the EE stock rom. My own backup didn't flash back correctly either, that's why i used that one i fould online.
4015X unbricked !
Hello,
I found a similar solution here (replace * with . to get a correct http link):
forum*gsmhosting*com/vbb/f317/ot-4015x-firmware-arabic-bulgaria-africa-kenya-1946694/index2.html
It took me hours to find good stock ROMs (bulgarian & arabian then french via OTU) !
You'll have to "play" with pro_info and scatter file...
Good luck to all to unbrick your 4015x !
Regards,
Freeman.
how to partition system storage space of onetouch pop c1?
This is for real, folks. The first working custom recovery for Asus ZenPad 8.0 Z380M and a method to flash it under a locked bootloader. This took quite a bit of work to make, partly due to having to find a way to bypass the locked bootloader. And because of a kernel configuration issue that limited the size of the initial ramdisk, which took some serious effort to weed out. @lss1977 helped to port it to this device. And of course, credits to TeamWin for TWRP.
In addition to this thread, the current Z300M/Z301M TWRP thread and the the old Z300M recovery/rooting thread may be helpful. These models share the same hardware and software base, so most things that apply to one tablet also apply to the other.
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
REQUIREMENTS
Windows PC
SP Flash Tool version 5.1532 (only this version will bypass security checks)*
MediaTek VCOM drivers (available through Windows Update)
Z380M scatter file, attached
Recovery image, attached
Z380M preloader file (optional), available inside the stock firmware download
ZenPad Z380M tablet upgraded to Android N
* If you prefer to use a more recent SP Flash Tool, check out the special image file below.
This won't be a guide on how to use SP Flash Tool. There are plenty of good guides out there like this one on how to set up drivers, load scatter files, flash and make backups with SP Flash Tool. If you're not familiar with this software or how to flash MediaTek devices in general, please do your research before attempting this. I will just get straight to the specifics about the ZenPad 8.
FIRST TIME INSTALLATION
For a locked bootloader:
At this point you should have your tablet powered off, the drivers installed, all of your data backed up, and SP Flash Tool v5.1532's Download tab open and loaded with the tablet's scatter file. Open the download agent file DA_PL.bin, replacing the default MTK_AllInOne_DA.bin. (You can use the AllInOne DA if you want, but the procedure involves extra steps as described below.) Load the extracted TWRP recovery image (twrp-3.2.1-0-z380m.img) under the recovery partition line in the partition table. Click the Download button inside SPFT. Now just connect the USB cable to your tablet and your computer's USB port. It should start the download process automatically and disconnect when finished.
Alternative Method:
If you're using MTK_AllInOne_DA.bin, you have to hold the Volume Up key as you insert the cable, which puts the device into an emergency download mode. In addition, you will need to have the stock preloader*.bin file loaded inside SPFT for it to be able to communicate with your tablet. The preloader is available inside the official zip file download. Do not flash the preloader (untick the box) or any partitions other than recovery. You just need to have a valid bin file selected under the Preloader line.
For an unlocked bootloader:
If you have used the Asus unlock tool to unlock your device, you will still not be able to use fastboot flash to install a custom recovery. However, you can do a "hot boot" or a tethered boot of TWRP. This method doesn't require SP Flash Tool. Download the TWRP image, put your tablet in fastboot mode and connect to PC. Then run this command to boot TWRP dynamically:
fastboot boot twrp-3.2.1-0-z380m.img
Once inside TWRP, flash twrp-3.2.1-0-z380m.img to Recovery using Install -> Install Image. Then reboot to recovery. You may be able to use TWRP in the tethered boot mode, but that could result in glitches due to different parameters passed by the bootloader to the kernel. That's why flashing is recommended.
To update from your installed TWRP version to a new one, just transfer the image to your tablet, then boot to TWRP and install it by going to Install -> Install Image and flashing to Recovery.
START RECOVERY
With the tablet powered off, hold the Volume Up and Power keys together until you get to a menu where you can select "recovery". Use Vol. Up to scroll and Vol. Dn to select. If you have a locked bootloader, it will show a Yellow State message because the recovery is not signed by the OEM. Just press volume up to boot it. On the welcome screen of TWRP it will ask you about modifying the system partition, I suggest you go with Keep System Read-only. Doing otherwise will complicate your OTA updates.
WARNING: Never start the stock recovery from the bootloader menu on this device. It is programmed by the bootloader to instantly wipe your data without any warning. Also, be aware that Android installs the stock recovery at every normal boot cycle. So you either have to flash the TWRP every time you want to run it, or disable the automatic recovery installation in the stock firmware. Any kind of mod to the boot image will prevent the automatic recovery installation. If you're not sure which recovery you have installed, you can always do a 'adb reboot recovery' from Android without risk of data loss.
What works: Basically everything... access to major partitions, decrypted userdata partition, decrypted adoptable storage, external SD card, ADB, USB-OTG, touch interface, splash screen, installing stock Asus OTA/web FW updates
What doesn't work: (no known problems yet, but please report any)
Not guaranteed to work: factory reset
DOWNLOAD
(Updated February 3, 2018: updated kernel to firmware 5.3.18; up-to-date TWRP 3.2.1 sources)
SP Flash Tool v5.1532
Z380M Scatter file for all storage sizes (right click, Save link as...)
Recovery image
Signed image for Flash Tool only -- may be flashed with recent SP Flash Tool versions -- DO NOT INSTALL USING ANY OTHER METHOD -- tested with SPFT 5.1736.
Development and experimental files
Source code
P.S. The thanks button doesn't bite.
Nice one now lets get some custom roms done.
Has anyone installed this yet? I see the file has been downloaded a few times. Any feedback is welcome.
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
lss1977 said:
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
Click to expand...
Click to collapse
The way I did it was to edit the init.rc file inside the boot ramdisk and comment out the service block that calls install_recovery.sh. I used the MTK boot image unpack/repack tools. I don't know, it seems like changing anything on the system partition will break OTA updates because of dm-verity. Because that depends on verifying each block of the file system. I have never even mounted the system as R/W in recovery.
how to create scater file from text posted? I copied all text to MT8163_Android_scatter.txt file but when open with splash tools give error "scatter file is invalid"
please atach your working scatter file to other atachments
PxYra said:
how to create scater file from text posted? I copied all text to MT8163_Android_scatter.txt file but when open with splash tools give error "scatter file is invalid"
please atach your working scatter file to other atachments
Click to expand...
Click to collapse
OK, I added the scatter file as a download. It was a pain in the ass to copy & paste. (But it did work.)
Problem fixed downloaded new version of flashtool 5.16 and scatter working
Ok I installed TWRP on Z380M P00A, and wanna say to other
1. Use VCOM drivers only from splash tool official site
2. To install VCOM drivers first need enter chinese recovery tablet, then in windows device manager you see USB device, install manualy drivers (don forget in windows disable driver signature)
3. Use only SP-Flash-Tool-v5.1532.00, newer or older version not properly working with this phone
Ok, thanks for the update, PxYra. Just to let you know, there are signed versions of VCOM drivers floating around so you don't need to mess with signature enforcement. Here's one: https://www.androidfilehost.com/?fid=24591000424943663. They are also updated by Windows so you can just let Windows Update install them.
Thanks for your work.
Flashing procedure works only with "MTK_AllInOne_DA.bin" method for me. But this is OK!
(Updated May 6, 2017: added kernel from firmware 5.3.7, source code cleanup)
Click to expand...
Click to collapse
is it possible to get the older versions? I need Android 6.x, because of xposed-Framework for my Zenpad 8.0 Z380M.
Greets Freisei
Hey freisei...
I never posted a version for Android 6. There was just one based on the 5.3.6 kernel, practically the same as the current one. That's why I didn't keep it. I could try to build one for you if you want, but I can't test it of course. Does this recovery not boot at all on the old firmware?
It's strange that the DA_PL.bin method didn't work for you. What happened when you tried it? I suppose the old preloader doesn't allow it(?).
hello guys, you think lineage os official version for asus z380kl (p024) will work on our z380m ?
---------- Post added at 08:19 PM ---------- Previous post was at 08:05 PM ----------
Can anyone help me? after selecting recovery img, pressing download and inserting usb cable, nothing happens. Thanks in advance
lss1977 said:
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
Click to expand...
Click to collapse
hello friend, can you please upload that file? I deleted it, but now I need it to revert to official recovery, as my zenpad is bricked! It would be of great help! thanks!
Pires_7 said:
hello friend, can you please upload that file? I deleted it, but now I need it to revert to official recovery, as my zenpad is bricked! It would be of great help! thanks!
Click to expand...
Click to collapse
Your ZenPad didn't brick because you deleted install_recovery.sh. It's because you modified the system partition. Making any mods to system is bad advice unless you know exactly what you're doing. Even mounting it in r/w mode can break it. That's because dm-verity has tripped and is blocking access to changed blocks of the file system. So you have 3 options: mod your boot image fstab file to disable dm-verity, restore the original system image block-for-block (either from backup or official firmware converted to an img file), or wipe userdata (lss reported that to work).
Pires_7 said:
hello guys, you think lineage os official version for asus z380kl (p024) will work on our z380m ?
Click to expand...
Click to collapse
Nope, no chance.
diplomatic said:
Your ZenPad didn't brick because you deleted install_recovery.sh. It's because you modified the system partition. Making any mods to system is bad advice unless you know exactly what you're doing. Even mounting it in r/w mode can break it. That's because dm-verity has tripped and is blocking access to changed blocks of the file system. So you have 3 options: mod your boot image fstab file to disable dm-verity, restore the original system image block-for-block (either from backup or official firmware converted to an img file), or wipe userdata (lss reported that to work).
Nope, no chance.
Click to expand...
Click to collapse
Ok. I made some real s*it, I think I deleted every partition except recovery. Can you provide me a twrp backup or some way around my problem?
What do you mean you deleted every partition except recovery? There's like 28 partitions. You would have to work hard to accomplish that.
My first suggestion is to extract a system.img from the Asus stock firmware zip using this. Then flash it with SP Flash Tool. You might also try to install a full firmware zip from TWRP. Although I have no idea if that will work or if it's even safe to try.
diplomatic said:
What do you mean you deleted every partition except recovery? There's like 28 partitions. You would have to work hard to accomplish that.
My first suggestion is to extract a system.img from the Asus stock firmware zip using this. Then flash it with SP Flash Tool. You might also try to install a full firmware zip from TWRP. Although I have no idea if that will work or if it's even safe to try.
Click to expand...
Click to collapse
i was able to extract system.new.dat from stock firmware zip, but it extracts to a system folder. How do I flash this through sp flash tool?
OK, the system folder you don't need. It should have produced a system.img file also. That's the file you need to flash. Just select it for the system partition row in the partition list and then Download. Hopefully that will be enough.
EDIT: I just looked at the script, and realized the system.img.img file gets deleted in the process. So what you need to do is start the extraction, then after it makes system.img.img, when it starts extracting individual files, hit Ctrl+C. Then you'll end up with the img file.
Thank you very much! it works! YOU are the BEST!
please tell me, in your scatter file, address partition_name: frp (0x80a5000) is correct? if i format this partition (frp), google account remove?
Hello,
I've been recently trying to root my Asus Zenfone 3 Max (ZC520TL) using SP Flash tool,
however, I haven't found the correct scatter file for my device. Does anyone know where
I could find a MT6737 scatter file? Thanks in advance!
Hi. From my experience, correct scatter files that work (not just any random scatter file) reside in a ROM/Firmware zip.
Doing a little searching, I found that you can download stock firmware for you device from Asus officially. They offer them in the support section.
Here is the link: https://www.asus.com/us/Phone/ZenFone-3-Max-ZC520TL/HelpDesk_Download/
Should you download the official firmware specific to your device and unzip the file, (in all probability) you will also find the correct scatter file which you are looking for (something like xxxxx_scatter_file.txt).
(also keeping in place a stock rom is never but never a bad idea )
However... You mentioned that you need the scatter file to root??? I have not any idea as to why you would need SP Flash tool for any other reason than flashing stock.
Unless you are flashing full custom rom which cannot be flashed through recovery perhaps?
Anyway... Good luck!!!
Thanks for the quick response!
r&xp said:
Hi. From my experience, correct scatter files that work (not just any random scatter file) reside in a ROM/Firmware zip.
Doing a little searching, I found that you can download stock firmware for you device from Asus officially. They offer them in the support section.
Here is the link:
Should you download the official firmware specific to your device and unzip the file, (in all probability) you will also find the correct scatter file which you are looking for (something like xxxxx_scatter_file.txt).
(also keeping in place a stock rom is never but never a bad idea )
However... You mentioned that you need the scatter file to root??? I have not any idea as to why you would need SP Flash tool for any other reason than flashing stock.
Unless you are flashing full custom rom which cannot be flashed through recovery perhaps?
Anyway... Good luck!!!
Click to expand...
Click to collapse
I needed the Flash tool because I was trying to flash TWRP, and from there install superuser. I did as you said, but when I tried loading the scatter file
the program recognized it as invalid. A huge thanks for the help though!!!
mcAlex42 said:
I needed the Flash tool because I was trying to flash TWRP, and from there install superuser. I did as you said, but when I tried loading the scatter file
the program recognized it as invalid. A huge thanks for the help though!!!
Click to expand...
Click to collapse
Ok... No worries!! We will probably figure it out in the end.
By the way, I am not sure I understand exactly how you were going to use SP Flashtool to flash TWRP. From my experience it does not work that way. You need platform tools (adb and fastboot).
platform tools here ----> https://developer.android.com/studio/releases/platform-tools.html
It is with these that you will unlock bootlader, and after bootloader is unlocked, first flash supersu, install busybox and lastly flash twrp.
Please look at my how-to root and twrp section. It is not for your device, but it will give you a good idea of the process: https://forum.xda-developers.com/android/help/lenovo-tab-3-8-tb3-850f-unbrick-root-t3598727
Please also check your private messages. I am sending you some links you might find helpful.
INFINIX HOT S 3 ROOTING PROCEDURE WITH LOCKED BOOTLOADER
Things You must First Do
1. Install Qualcomm drivers for your PC
2. Learn how to remove the device back cover:
3. Learn how to boot the device to EDL mode :
4. Learn how to backup your device full firmware with a box like miracle box or cracked version :
5. Learn how to flash firmware with QFIL tool version 2.0.1.9 :
PROCEDURE 1
1. Get hold of your device full stock firmware. Some build numbers do not have stock firmware especially my Hot S3 build number do not have correct stock firmware.
2. Install latest official magisk manager apk.
3. Copy stock boot.img to your device internal storage.
4. Launch magisk manager app, select install magisk 18.1v or any version that will appear, there will be an options select patch boot.img. Now locate where you stored your boot.img. After patch magisk will show you the location of the patched bootimg.
5. Copy the patched boot.img into the device firmware folder. Remove the original boot.img from the firmware folder and save it somewhere and rename the patched boot.img to boot.img.
6. Now launch the QFIL tool and flash using the previous procedure.
7. After successful flash, boot to the device recovery (Volume up + power button) wipe partition and factory wipe, then power off and reboot.
8. After reboot update Google play store and services sign into your account successfully to have a recognize certify device. Install magisk manager apk. Launch magisk manager app, update and install any other updates that will pop up. Every installed thing in magisk will show green.
9. Reboot. The device successfully rooted.
NOTE:
1. Those who have their correct official firmware and have tested and working correctly, there will be firehose file, patch0 file, rawprogram0 files, NON-HLOS file. These are the necessary files for the flashing.
2. Those who don't have the correct stock firmware use the backup firmware from the miracle and rename these files as;
boot= boot.img
Cache= cache.img
dummy= dummy.img
misc= misc.img
persist= persist.img
recovery= recovery.img
splash= splash.img
system= system.img
userdata= userdata.img
aboot= emmc_appsboot.mbn
Modem=NON-HLOS bin
The rest of the files add .mbn to it end.
You need:
patch0.xml
rawprogram0.xml
prog_emmc_firehose_8937_ddr.mbn
if you don't have these files I will upload my full prepared stock firmware so that you take all the necessary files from it into yours and flash.
But if you have any downloaded stock HOT S 3 firmware with only one system and vendor inside you can use it.
3. Those who have their stock firmware, if the system and vendor in the folder is in multiple form meaning more than one ( system and vendor are in parts) you can't use QFIL tool to flash, it require different flash tool. Use your backup firmware.
4. If any find things difficult I will upload my stock firmware so that all builds can use to create their own stock firmware.
Thank you.
5. After every flash try to remove battery cable and replace for some seconds when the device cover is opened.
6. At a point where the device refuse to boot or power off, long press power button to power off or reboot.
7. Do not be in haste, take your time to follow all these procedures to avoid the device going dead. Because a device does not go dead in my hands. It may brick but when you use good and required flash files everything will be okay.
With ease, convenience and future developments for the device I have created Facebook group for that because some informations are hard to come by. I have posted a lot of help in different forums, nobody seems to help, so this how far I have gone. Now trying to Port custom recovery like twrp for the device even though bootloader is locked.
Procedure 2
1. Follow procedure 1 to backup device
2. Patch boot.img with magisk manager
3. Copy patched image rename as boot.img into backup folder.
4. Flash only the patched boot.img by any supported tool.
5. Reboot device install magisk manager apk reboot and update magisk done.
Those who have already rooted or gone far with the device can join the facebook group or provide me better links. Thanks
Facebook Group Link: https://www.facebook.com/groups/324251668449205/
CREDITS
Thanks to XDA for creating this wonderful platform
The best App ever magisk
The best tool ever Miracle box
Hamenth Jabalpuri my best friend XDA Senior Member
Thanks to everyone.
CAUTION
If any want to use this information in his site, don't forget to credit XDA.
TWRP LINK
https://forum.xda-developers.com/android/development/unofficial-twrp-infinix-hot-s3-x573-t4064705
Skyhuppa said:
Hamenth Jabalpuri my best friend XDA Senior Member
Click to expand...
Click to collapse
Thank you too for sharing this.....
Great tutorial thx
i can't get into edl mode
i used the shorting method via the back cover.. the device was blinking... was detected in device manager but when i clicked on port inside miracle box... nothing happened
i am trying to dump the firmware
Skyhuppa said:
INFINIX HOT S 3 ROOTING PROCEDURE WITH LOCKED BOOTLOADER
Click to expand...
Click to collapse
aus7een said:
i used the shorting method via the back cover.. the device was blinking... was detected in device manager but when i clicked on port inside miracle box... nothing happened
i am trying to dump the firmware
Skyhuppa said:
INFINIX HOT S 3 ROOTING PROCEDURE WITH LOCKED BOOTLOADER
Click to expand...
Click to collapse
I'm not getting your device blinking well but;
1. Make sure your device driver 9008 in edl mode installed well. When you open device manager you must see driver 9008 for your device. Download driver
https://www.allmobitools.com/download/Qualcomm_HS_USB_QDLoader_9008_Driver_Download.zip
2. If you are using windows 10 make sure you disable driver signature before installing any driver on your computer
3. Make sure you disconnect and reconnect battery cable on the board before and after every connection.
4. Use the miracle tutorial when you see driver Qloader 9008 in device manager after connecting device.
5. You must connect the two edl points well. Poor connection boot to battery charge.
6. Use miracle 2.82 version
Click to expand...
Click to collapse
did you have TWRP for infinix hot s3?
Nice well done thanks for sharing
agnitoya said:
did you have TWRP for infinix hot s3?
Click to expand...
Click to collapse
Not yet unless bootloader is fully unlocked.
Flash???
which file should i flash it,becouse i dont have the file... and almost all my frimware have .bak at the end so which flasher i should use,QFIL or others? heres the link of the pic of it
Nthn_Knt said:
which file should i flash it,becouse i dont have the file... and almost all my frimware have .bak at the end so which flasher i should use,QFIL or others? heres the link of the pic of it
Click to expand...
Click to collapse
Where did you get the .bak firmware files? Qfil can't flash such firmware. Use mobilsea tool or emmc tool.
Skyhuppa said:
INFINIX HOT S 3 ROOTING PROCEDURE WITH LOCKED BOOTLOADER
Things You must First Do
1. Install Qualcomm drivers for your PC
2. Learn how to remove the device back cover:
3. Learn how to boot the device to EDL mode :
4. Learn how to backup your device full firmware with a box like miracle box or cracked version :
5. Learn how to flash firmware with QFIL tool version 2.0.1.9 :
PROCEDURE 1
1. Get hold of your device full stock firmware. Some build numbers do not have stock firmware especially my Hot S3 build number do not have correct stock firmware.
2. Install latest official magisk manager apk.
3. Copy stock boot.img to your device internal storage.
4. Launch magisk manager app, select install magisk 18.1v or any version that will appear, there will be an options select patch boot.img. Now locate where you stored your boot.img. After patch magisk will show you the location of the patched bootimg.
5. Copy the patched boot.img into the device firmware folder. Remove the original boot.img from the firmware folder and save it somewhere and rename the patched boot.img to boot.img.
6. Now launch the QFIL tool and flash using the previous procedure.
7. After successful flash, boot to the device recovery (Volume up + power button) wipe partition and factory wipe, then power off and reboot.
8. After reboot update Google play store and services sign into your account successfully to have a recognize certify device. Install magisk manager apk. Launch magisk manager app, update and install any other updates that will pop up. Every installed thing in magisk will show green.
9. Reboot. The device successfully rooted.
NOTE:
1. Those who have their correct official firmware and have tested and working correctly, there will be firehose file, patch0 file, rawprogram0 files, NON-HLOS file. These are the necessary files for the flashing.
2. Those who don't have the correct stock firmware use the backup firmware from the miracle and rename these files as;
boot= boot.img
Cache= cache.img
dummy= dummy.img
misc= misc.img
persist= persist.img
recovery= recovery.img
splash= splash.img
system= system.img
userdata= userdata.img
aboot= emmc_appsboot.mbn
Modem=NON-HLOS bin
The rest of the files add .mbn to it end.
You need:
patch0.xml
rawprogram0.xml
prog_emmc_firehose_8937_ddr.mbn
if you don't have these files I will upload my full prepared stock firmware so that you take all the necessary files from it into yours and flash.
But if you have any downloaded stock HOT S 3 firmware with only one system and vendor inside you can use it.
3. Those who have their stock firmware, if the system and vendor in the folder is in multiple form meaning more than one ( system and vendor are in parts) you can't use QFIL tool to flash, it require different flash tool. Use your backup firmware.
4. If any find things difficult I will upload my stock firmware so that all builds can use to create their own stock firmware.
Thank you.
5. After every flash try to remove battery cable and replace for some seconds when the device cover is opened.
6. At a point where the device refuse to boot or power off, long press power button to power off or reboot.
7. Do not be in haste, take your time to follow all these procedures to avoid the device going dead. Because a device does not go dead in my hands. It may brick but when you use good and required flash files everything will be okay.
With ease, convenience and future developments for the device I have created Facebook group for that because some informations are hard to come by. I have posted a lot of help in different forums, nobody seems to help, so this how far I have gone. Now trying to Port custom recovery like twrp for the device even though bootloader is locked.
Procedure 2
1. Follow procedure 1 to backup device
2. Patch boot.img with magisk manager
3. Copy patched image rename as boot.img into backup folder.
4. Flash only the patched boot.img by any supported tool.
5. Reboot device install magisk manager apk reboot and update magisk done.
Those who have already rooted or gone far with the device can join the facebook group or provide me better links. Thanks
Facebook Group Link: https://www.facebook.com/groups/324251668449205/
CREDITS
Thanks to XDA for creating this wonderful platform
The best App ever magisk
The best tool ever Miracle box
Hamenth Jabalpuri my best friend XDA Senior Member
Thanks to everyone.
CAUTION
If any want to use this information in his site, don't forget to credit XDA.
Click to expand...
Click to collapse
TWRP LINK
https://forum.xda-developers.com/android/development/unofficial-twrp-infinix-hot-s3-x573-t4064705