Related
I was in the process of removing kingroot and installing supersu when my phone decided to reboot and now will not boot past the very first screen no matter how long I let it sit. I tried factory resetting it but that didn't change anything. I've searched high and low for firmware but have come up empty. Does anyone have stock firmware for the Alcatel Streak? Thanks.
archmagusdg said:
I was in the process of removing kingroot and installing supersu when my phone decided to reboot and now will not boot past the very first screen no matter how long I let it sit. I tried factory resetting it but that didn't change anything. I've searched high and low for firmware but have come up empty. Does anyone have stock firmware for the Alcatel Streak? Thanks.
Click to expand...
Click to collapse
Concur.
I had exactly the same problem. Alcatel Streak (40600) would not boot after I did KingRoot and superSu replacement.
There has been no activity on this or other Alcatel STREAK threads for some time, but for any members needing, I have a full stock ROM for the Cricket Alcatel STREAK (4060o), Android 6.0.1 Marshmallow. Any interested members please leave a comment and I will upload the ROM and post a download link.
i need the file for the streak 4060o
@Viva La Android
Viva La Android said:
There has been no activity on this or other Alcatel STREAK threads for some time, but for any members needing, I have a full stock ROM for the Cricket Alcatel STREAK (4060o), Android 6.0.1 Marshmallow. Any interested members please leave a comment and I will upload the ROM and post a download link.[/QUOT
Ive been able to aquire a stock firmware as well...the problem is after i flash with qfil it wont boot??? Qualcom qfil says download complete with no sahara errors..ive got the emmc programmer file if anyone needs... i just dont know what to do next to get it to boot
Click to expand...
Click to collapse
KtownJeff said:
@Viva La Android
Viva La Android said:
There has been no activity on this or other Alcatel STREAK threads for some time, but for any members needing, I have a full stock ROM for the Cricket Alcatel STREAK (4060o), Android 6.0.1 Marshmallow. Any interested members please leave a comment and I will upload the ROM and post a download link.[/QUOT
Ive been able to aquire a stock firmware as well...the problem is after i flash with qfil it wont boot??? Qualcom qfil says download complete with no sahara errors..ive got the emmc programmer file if anyone needs... i just dont know what to do next to get it to boot
Click to expand...
Click to collapse
I understand your dilemma. My stock ROM and firmware are installable via TWRP, which I have ported over from the Alcatel IDEAL (4060a). Flashing a firmware to this device without using a custom recovery is problematic to say the least. QFIL/QPST does not seem to work, and true to their typical protocol, TCL seems to have disabled fastboot mode on the 4060o. I will research this matter some more to see if I can help. There are reports of forcing the device into a hard brick by corrupting the /sbl1 bootloader partition. As such, Qualcomm's EDL (9008) mode is enabled which will allow for an emergency firmware installation per firehose protocol via QPST. But again, I'll try and research this more. Also, if you don't mind, could you share the firmware you have please? It sounds like you have an official package which I have not been able to locate. My ROM and firmware are both self compiled. Thank you.
Click to expand...
Click to collapse
awesome
Viva La Android said:
KtownJeff;80315069 [user=10059830 said:
@Viva La Android[/user]
I understand your dilemma. My stock ROM and firmware are installable via TWRP, which I have ported over from the Alcatel IDEAL (4060a). Flashing a firmware to this device without using a custom recovery is problematic to say the least. QFIL/QPST does not seem to work, and true to their typical protocol, TCL seems to have disabled fastboot mode on the 4060o. I will research this matter some more to see if I can help. There are reports of forcing the device into a hard brick by corrupting the /sbl1 bootloader partition. As such, Qualcomm's EDL (9008) mode is enabled which will allow for an emergency firmware installation per firehose protocol via QPST. But again, I'll try and research this more. Also, if you don't mind, could you share the firmware you have please? It sounds like you have an official package which I have not been able to locate. My ROM and firmware are both self compiled. Thank you.
Click to expand...
Click to collapse
https://mega.nz/#!BGwGFAgK!gW3ik2f_-oyI9MtER-PCrfSTQCio4CFzVWR6JVmSw_0
stock cricket Rom mm 6.0.1
@Viva La Android
...now let me tell you how this started to give you more info....I rooted with kingroot installed twrp for the 4060a with flashify and directly installed magisk 18 with twrp...somewhere in there i deleted king root...everything worked great..made a full back up through twrp..I had titanium backup installed deleated all the bloat and started on magisk mods..installed xposed as well...flashed viper4...well I got greedy and started trying to dirty flash pixie4 roms to get a higher os like oreo...fail fail fail...I had read in the forum not to tick fix permissions in TWRP but i did it anyway...never ending bootloop after that...i side loaded a custom rom for the 4060a ....hard brick...i guess thats when i was EDL mode because of the wrong bootloader...i tried to flash the cricket rom with qset\qfil and it would not work...then i flashed the stock 4060a and it worked...wouldn't boot past the splash screen...kinda weird though because the splash screen was split in half and reversed with a gap in the middle....ill figure out a way to screen shot later....but i was able to hook back into the pc and I have adb but unauthorized because the OS got factory wiped so no usb debugging...I do have fastboot access now...which is strange but since my oem unlock is not ticked in the OS every boot img recovery img or system img i try to flash acts all good then fail in fastboot....my realization is that I wiped my modem somewhere in there and it replaced it with a downgrade which forced the EDL mode...well I flashed wrong with the 4060a firmware so Im stuck is all I can figure...I cant get adb shell access either haven't tried
shell with ubuntu/python maybe i can get shell access to force feed super user and tick oem unlock for the bootloader...other than that Im stumped...Maybe DD commands and a good dump file to see where I stand...and as far as my TWRP backup goes..I got careless and deleated it when I formated my PC to remove all the crap Ive picked up trying to fix this mess off the MTK and GSM sites...
My main objective right now is to get my adb key authorized there has to be a way
Click to expand...
Click to collapse
Yeah I agree totally. If there was a way to enable the OEM Unlocking option from a shell environment, you would likely have total control of the device via fastboot protocol. Like you, I concur that there has to be a way. You have me perplexed enough to dig in and help find an answer. I have a working device and a bricked device, so I am free to experiment around on my brick using QFIL/QPST. I am impressed that you have been able to access fastboot. This is more progress than most people make, so congrats there. Nice work.
By the way @KtownJeff, if you need any partition dumps from my device, for example, /sbl1, /aboot, /rpm, /tz, etc., just let me know. Just a thought, but if you could push my /persist partition image to your device (my OEM Unlocking is enabled), I think your OEM Unlocking would tick enabled. I recall a Moto device where OEM Unlocking was enabled in a similar manner. @KtownJeff, if possible, please share a download link of the official firmware package to which you referred. I will be glad to share my self compiled firmware package and stock ROM. Thank you friend.
Viva La Android said:
Yeah I agree totally. If there was a way to enable the OEM Unlocking option from a shell environment, you would likely have total control of the device via fastboot protocol. Like you, I concur that there has to be a way. You have me perplexed enough to dig in and help find an answer. I have a working device and a bricked device, so I am free to experiment around on my brick using QFIL/QPST. I am impressed that you have been able to access fastboot. This is more progress than most people make, so congrats there. Nice work.
By the way @KtownJeff, if you need any partition dumps from my device, for example, /sbl1, /aboot, /rpm, /tz, etc., just let me know. Just a thought, but if you could push my /persist partition image to your device (my OEM Unlocking is enabled), I think your OEM Unlocking would tick enabled. I recall a Moto device where OEM Unlocking was enabled in a similar manner. @KtownJeff, if possible, please share a download link of the official firmware package to which you referred. I will be glad to share my self compiled firmware package and stock ROM. Thank you friend.
Click to expand...
Click to collapse
I actually stumbled on the fastboot accidentally!!...After I flashed the Stock 4060A firmware with the split up splash image I checked my driver to see if I was in qloader 9008 mode still and I saw the holy grail "Android Bootloader"...The phone screen didnt have anything showing on it like any moto mfastboot mode or like a samsung when hooked up to odin...just the frozen "half splash" Alcatel Logo..I had minimal adb/fastboot installed...I switched to the Android platform tools latest version and had better results...I had a lot of failures when it come down to recovery partition and system partition...I had some successes tho...Fastboot erase works but I dont know if thats standard and the OS reinstalls what I erased because of the lock..prob so just like no superuser access in ADB...I tried to re flash TWRP for like three days and gave up...I forgot to mention I have no stock recovery access.......Yes please I need a full phone dump of whatever you got... all the better..I might try shorting my board to get back to EDL so I can try flash the cricket 6.0.1 again...but I don't want to lose my fastboot access either....the 6040O aboot partion does not have fastboot... The Stock crickit 4060O rom link was posted earlier...I'm in the process of uploading to MEGA as we speak so here in a few I will post all my stuff for this phone...And please share yours as well...
stock Rom's and tools for Alcatel 4060A/O
@Viva La Android
TWRP Recovery https://mega.nz/#!QTwlESgJ!YSu6T5r93AonRiSxh6QQtov_ZDsxz95YW1RXYSuPJRQ
QSET/QSIL Qualcom all in one https://mega.nz/#!xSoSQCTK!MPQJytxtVUl4aHBXQp7wYbZb9o6ZpXX5wpTy3dqX7xA
Firehose Programmer file for QFIL/QSET https://mega.nz/#!EGQAXKBC!LfyE2zJzhXB15XeAgxB3H2HcL0OiXNa38V74ZodJf5I
Acatel Ideal 4060A AT&T Stock Firmware L 5.1.1
https://mega.nz/#!8ewAxCZS!sGURkuzmzcgbh6_AYOMyokzkx3VA74g50gYfZPFZOAA
Alcatel Streak 4060O Cricket Stock Firmware MM 6.0.1 https://mega.nz/#!BGwGFAgK!gW3ik2f_-oyI9MtER-PCrfSTQCio4CFzVWR6JVmSw_0
Fix BootLoop Alcatel Ideal
there´s any stock rom flashable for the alcatel ideal? i need unbrick my device because when i make a flashable stock rom the device boots and shows the screen for a second and after still bootlooping, i tried with QFIL but i have problems connecting the device, any way to fix? porting a rom with same chipset? or using another methods. PLZ i need unbrick my phone :crying:
KV2_URSS said:
there´s any stock rom flashable for the alcatel ideal? i need unbrick my device because when i make a flashable stock rom the device boots and shows the screen for a second and after still bootlooping, i tried with QFIL but i have problems connecting the device, any way to fix? porting a rom with same chipset? or using another methods. PLZ i need unbrick my phone :crying:
Click to expand...
Click to collapse
There was one here on XDA. It was a TWRP flashable Android 5.1.1 stock ROM I believe. The OP of the ROM is no longer on XDA and it appears that the download links are dead. I'll try to find you a copy of the ROM though.
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
KtownJeff said:
@Viva La Android
TWRP Recoveryhttps://mega.nz/#!QTwlESgJ!YSu6T5r93AonRiSxh6QQtov_ZDsxz95YW1RXYSuPJRQ
QSET/QSIL Qualcom all in onehttps://mega.nz/#!xSoSQCTK!MPQJytxtVUl4aHBXQp7wYbZb9o6ZpXX5wpTy3dqX7xA
Firehose Programmer file for QFIL/QSET https://mega.nz/#!EGQAXKBC!LfyE2zJzhXB15XeAgxB3H2HcL0OiXNa38V74ZodJf5I
Acatel Ideal 4060A AT&T Stock Firmware L 5.1.1
https://mega.nz/#!8ewAxCZS!sGURkuzmzcgbh6_AYOMyokzkx3VA74g50gYfZPFZOAA
Alcatel Streak 4060O Cricket Stock Firmware MM 6.0.1https://mega.nz/#!BGwGFAgK!gW3ik2f_-oyI9MtER-PCrfSTQCio4CFzVWR6JVmSw_0
Click to expand...
Click to collapse
Oh thank you very much. I was in need of the 4060o official firmware package. I'm in debt to you. Thanks for all the extras as well! Nice. I will upload my stock partition dump of my 4060o and get that posted ASAP. Have you tried using an insecure boot image for ADB superuser (ADBD) access? If you want I can set my stock boot image insecure with ADBD and upload that as well.
I'm found a copy of a stock 5.1.1 ROM for the 4060a that is TWRP flashable. I'm uploading it to Mega File now. I'll post the link when completed. I fixed the installer on this ROM and rewrote the Edify script.
4060a Stock ROM
TWRP Flashable Zip
Android 5.1.1 Lollipop
Build No. M5RUAR4
Root: SuperSU v2.82-SR5
Link: https://mega.nz/#!VEVUwaxB!sCsdYXPE-_ytsqKnXRJHhFLVLnn3jxCDY8bG7FP89nM
@KV2_URSS, if you have TWRP installed, this may unbrick your device.
Update: I dissected that ROM and discovered some syntax errors in the Edify script. I've rewritten the installer and fixed some bugs with the updater-script. I also just tested the ROM on my own 4060a and confirmed that it does work. I'll post the updated link to replace the other link in a few minutes.
Viva La Android said:
Update: I dissected that ROM and discovered some syntax errors in the Edify script. I've rewritten the installer and fixed some bugs with the updater-script. I also just tested the ROM on my own 4060a and confirmed that it does work. I'll post the updated link to replace the other link in a few minutes.
Click to expand...
Click to collapse
Thanks, this is a posibility for unbrick my phone, you now fixed the rom link? :good:
KV2_URSS said:
Thanks, this is a posibility for unbrick my phone, you now fixed the rom link? :good:
Click to expand...
Click to collapse
flashed but still bootlooping, i think my phone its broken Anyway: thanks for help!
KV2_URSS said:
flashed but still bootlooping, i think my phone its broken Anyway: thanks for help!
Click to expand...
Click to collapse
Did you download from the updated link? The ROM from the old link was bootlooping my 4060a also. I fixed the installer script and when I tried it again it worked. On the new one, I added my username to the installer script and removed the original dev's name. Is this the one you tried? Also, did you do a full wipe before installing? (/system, /cache, Dalvik, format /data)
---------- Post added at 01:22 PM ---------- Previous post was at 01:17 PM ----------
@KtownJeff I'll try to have the 4060o stock 6.0.1 ROM posted later today, and I'll post the dump files from my device. Thank you again for the official firmware.
Viva La Android said:
Did you download from the updated link? The ROM from the old link was bootlooping my 4060a also. I fixed the installer script and when I tried it again it worked. On the new one, I added my username to the installer script and removed the original dev's name. Is this the one you tried? Also, did you do a full wipe before installing? (/system, /cache, Dalvik, format /data)
Click to expand...
Click to collapse
i flashed the updated rom with your name in updater script and still bootlooping
KV2_URSS said:
i flashed the updated rom with your name in updater script and still bootlooping
Click to expand...
Click to collapse
Ok. My guess is your boot chain may be corrupt. I'll write you an installer to try and fix it. I'm fixing some things on the 4060o ROM, so I'll write you an installer for your 4060a when I get ready to upload the other ROM. In the installer, I'll place some of the bootloader partitions from the firmware package to be installed on your device.
Viva La Android said:
Did you download from the updated link? The ROM from the old link was bootlooping my 4060a also. I fixed the installer script and when I tried it again it worked. On the new one, I added my username to the installer script and removed the original dev's name. Is this the one you tried? Also, did you do a full wipe before installing? (/system, /cache, Dalvik, format /data)
---------- Post added at 01:22 PM ---------- Previous post was at 01:17 PM ----------
@KtownJeff I'll try to have the 4060o stock 6.0.1 ROM posted later today, and I'll post the dump files from my device. Thank you again for the official firmware.
Click to expand...
Click to collapse
@Viva La Android....no problem for the files my friend...please post the ROM and dump files...i went as far as test point into EDL mode and I cant get anything to download for some reason...Im gonna play around with QSET and see if there is a way to just wipe and manual install partitions that way
KtownJeff said:
@Viva La Android....no problem for the files my friend...please post the ROM and dump files...i went as far as test point into EDL mode and I cant get anything to download for some reason...Im gonna play around with QSET and see if there is a way to just wipe and manual install partitions that way
Click to expand...
Click to collapse
Ok friend. I'll expedite and get that done now. To clarify, you want a full partition dump of my 4060o, correct?
The partition dump files and MM stock ROM for 4060o are uploading now. @KtownJeff, I don't have the best signal tonight in terms of fast upload/download data speed, but the ROM and files you need are uploading and links will be posted here ASAP. For informational purposes, my partition dump is taken from a stock Android 6.0.1 Alcatel STREAK, Build No. A45UC50, Build Date: June 24, 2016; Security Patch Level June 1, 2016, Kernel Version: 3.10.49, and Baseband Version: MSM8909.12110.15W46. My ROM has been built from this firmware version as well.
Update: Link will be posted within the hour.
I want to port TWRP to the 5044T which I believe is a Alcatel U5 which was sold as an Optus X Spirit
I want to create a backup of the device using MTK Tools before I start destroying my IMEI etc.
The MTK Tools 2.5.3 when run on this phone using USB debugging reveals the following:
Hardware : MT6737M
Model : 5044T
Build number : MRA58K release-keys
Build date UTC : 20171103-051806
Android v : 6.0
Baseband v: MOLY.LR9.W1444.MD.LWTG.MP.V81.6.P59, 2017/11/03 13:15
Kernel v : 3.18.19 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP Fri Oct 27 10:41:26 CST 2017
But it also stops there saying the following on the right:
--->>> Connect to device <<<---
--- ERROR : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!
--- Unknown ROM structure, backup NOT possible!
ATTENTION! File /system/recovery-from-boot.p which restore factory recovery in case of phone switching on in a normal mode Is Found!
I think I need a scatter file or to understand how to build one in order to continue? Can anyone with experience help me? I can follow instructions so long as their windows 7 64 or ubuntu compatible? I would still need help with the porting process for TWRP, I read a few guides, one didn't tell explicitly what to do but gave a general overview and up to you to learn the steps individually. The other guide I read was specific but didn't tell you what the specific command entered would do.
Please help, I'd like to backup and root this device and i'm willing to by a couple more of them for testing/rooting/porting purposes.
ID10T_Error said:
I want to port TWRP to the 5044T which I believe is a Alcatel U5 which was sold as an Optus X Spirit
I want to create a backup of the device using MTK Tools before I start destroying my IMEI etc.
The MTK Tools 2.5.3 when run on this phone using USB debugging reveals the following:
Hardware : MT6737M
Model : 5044T
Build number : MRA58K release-keys
Build date UTC : 20171103-051806
Android v : 6.0
Baseband v: MOLY.LR9.W1444.MD.LWTG.MP.V81.6.P59, 2017/11/03 13:15
Kernel v : 3.18.19 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP Fri Oct 27 10:41:26 CST 2017
But it also stops there saying the following on the right:
--->>> Connect to device <<<---
--- ERROR : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!
--- Unknown ROM structure, backup NOT possible!
ATTENTION! File /system/recovery-from-boot.p which restore factory recovery in case of phone switching on in a normal mode Is Found!
I think I need a scatter file or to understand how to build one in order to continue? Can anyone with experience help me? I can follow instructions so long as their windows 7 64 or ubuntu compatible? I would still need help with the porting process for TWRP, I read a few guides, one didn't tell explicitly what to do but gave a general overview and up to you to learn the steps individually. The other guide I read was specific but didn't tell you what the specific command entered would do.
Please help, I'd like to backup and root this device and i'm willing to by a couple more of them for testing/rooting/porting purposes.
Click to expand...
Click to collapse
Well for starters is your device 64bit?
Pretty sure MTK root tools does not support x64 bit architecture
Also generating a scatter file is not an easy task(nor safe)
Ricky Divjakovski said:
Well for starters is your device 64bit?
Pretty sure MTK root tools does not support x64 bit architecture
Also generating a scatter file is not an easy task(nor safe)
Click to expand...
Click to collapse
Yes I believe the device is 64bit, 6.06gb used of 8gb so cpu must be 64bit? Also chipset MT6737M is 64bit capable.
So I now understand that MTK Tools incompatible with 64bit? Who wrote MTK Tools and how do I influence them to them to update it?(prolly somthing I should use search to figure out, and I will. And search yeilds that MTK tools thread is under new managment)
scatter file is listing of start memory addresses for the system images? Yeah I can see how finding them in memory without the actual pointers would be difficult but if I may ask for a brief overview of how this kind of dev is done? Do they search memory for partition table or ext2,3,4 innode or somthing? If ya don't have the time please disregard this request.
Also if I buy another Optus X Spirit and mail it to you will you join the fight to free the image from the manufacturers control?(Prolly gonna be white, never seen a black one yet. But i'll put it in a black case as consolation. (BYO SDCard, and you will need one because it starts out with 1gb free!)
ID10T_Error said:
Yes I believe the device is 64bit, 6.06gb used of 8gb so cpu must be 64bit? Also chipset MT6737M is 64bit capable.
So I now understand that MTK Tools incompatible with 64bit? Who wrote MTK Tools and how do I influence them to them to update it?(prolly somthing I should use search to figure out, and I will. And search yeilds that MTK tools thread is under new managment)
scatter file is listing of start memory addresses for the system images? Yeah I can see how finding them in memory without the actual pointers would be difficult but if I may ask for a brief overview of how this kind of dev is done? Do they search memory for partition table or ext2,3,4 innode or somthing? If ya don't have the time please disregard this request.
Also if I buy another Optus X Spirit and mail it to you will you join the fight to free the image from the manufacturers control?(Prolly gonna be white, never seen a black one yet. But i'll put it in a black case as consolation. (BYO SDCard, and you will need one because it starts out with 1gb free!)
Click to expand...
Click to collapse
There is a 64bit MTK tools thats experimental from my understanding, but last time i attempted use out of it, the tool failed miserably when trying to detect the device.
I have no idea, i havent looked into it, but im pretty sure i rooted a 64bit mtk device before with dirtycow(check out my github root repo for drammer), the tool provides a console output so you can see exactly whats being done, however it also depends on the kernel patch level as this was recently fixed finally after decades without even being heard of.
If your willing to donate a device then sure, im willing to give it a shot.
Ok will try and pick one up tomob i'll send you a pm when I get one to get an address to send it to.
Will probably take a week or so, i'm behind cash wise so I need a little time to catch up.
twrp for alcatel u5
I am looking for working twrp for alcatel u5? anyone can help
I am also interested in this; however, I can't even get the device to fastboot mode. Is it Power + Volume down? Because that just leads me to the battery charging screen. adb does not recognise the device.
Dont think you can
I think this is what your looking for. Never use to be there. so someone has discovered it hardreset.info/devices/alcatel/alcatel-optus-x-smart/fastboot-mode/
Che0063 said:
I am also interested in this; however, I can't even get the device to fastboot mode. Is it Power + Volume down? Because that just leads me to the battery charging screen. adb does not recognise the device.
Click to expand...
Click to collapse
Pajuatu said:
I think this is what your looking for. Never use to be there. so someone has discovered it hardreset.info/devices/alcatel/alcatel-optus-x-smart/fastboot-mode/
Click to expand...
Click to collapse
Is there no fastboot method? Because otherwise I will not know another way to flash a custom recovery.
Use NCK dongle to backup your rom and imei, i personally have done it,
But using nck dongle you will not get the pre loader and 1 or 2 other files also will be missing, but it backs up the main system etc and also give you a scatter file,
Dont try to flash U5 firmware to it either it will give you chip error mismatched,
Alternatively you can obtain a full backup of each partition with SP flash tools read back option,
To do this use NCK dongle, open it once open select chip type as MT6737 then on the same page click "boot info" now plug the device in switched off and it will read all of your partition adresses and save them in a txt file,
From the txt file enter each address into SP flash tools readback option and it will backup each partition perfectly including the preloader,
As for flashing TWRP you can use SP flasht tool just click on the recovery tab and select the TWRP image when available,
I havent had a full chance to have a look at if it has fastboot or not but it definitely does not have Meta connection to it only flash so far ive found,
With entering fastboot also have yous tried through adb,
Adb reboot bootloader
? Does that not work i have a chinaphone MT6572 that has no visual fastboot only a black screen but i can issue fastboot commands such as getvar and what not maybe worth a try ill be doing the same when i get some time to look at it only just got it to day
Hey all managed to have a look at it today,
Turns out the optus X spirit is not actually 5044T vit rather 5044D but flashing U5 firmware has been prohibited as optus have added something to it to prevent it from flashing,
As for fastboot mode thats a no go it dosent have it,
Dev options has OEM unlock but what goods that when nothing can be done with it and as its a production build it cannot be remounted to add SU binary or Magisk binary for root, and cant remount with adb insecure as it requires root to run,
All my other rooting apps have failed but ill keep delving into it to see if something can be done about it as fastboot can after all be added to it as its within the firmware and is more than likely disabled within the build.prop im thinking.
Es file explorer can access /system and all contents within aswell as copy from but nothing can be deleted or copied to /system without root privledge,
Matty1993 said:
Hey all managed to have a look at it today,
Turns out the optus X spirit is not actually 5044T vit rather 5044D but flashing U5 firmware has been prohibited as optus have added something to it to prevent it from flashing,
As for fastboot mode thats a no go it dosent have it,
Dev options has OEM unlock but what goods that when nothing can be done with it and as its a production build it cannot be remounted to add SU binary or Magisk binary for root, and cant remount with adb insecure as it requires root to run,
All my other rooting apps have failed but ill keep delving into it to see if something can be done about it as fastboot can after all be added to it as its within the firmware and is more than likely disabled within the build.prop im thinking.
Es file explorer can access /system and all contents within aswell as copy from but nothing can be deleted or copied to /system without root privledge,
Click to expand...
Click to collapse
Do you have any stock ROMs for Alcatel 5044r? If you do I am looking for stock rom Android 6.0 or 7.0 thank you.
Skrappy187 said:
Do you have any stock ROMs for Alcatel 5044r? If you do I am looking for stock rom Android 6.0 or 7.0 thank you.
Click to expand...
Click to collapse
5044r is at&t alcatel idealXCITE correct ?
Matty1993 said:
5044r is at&t alcatel idealXCITE correct ?
Click to expand...
Click to collapse
Yes it is it is also officialy called Element5 or Element 5 (I don't know if that space between the T and 5 changes anything) plus I see it called as you posted and also called something with a C. Can't remember. I will post device info by CPU Z screen shot will that help?
Skrappy187 said:
Yes it is it is also officialy called Element5 or Element 5 (I don't know if that space between the T and 5 changes anything) plus I see it called as you posted and also called something with a C. Can't remember. I will post device info by CPU Z screen shot will that help?
Click to expand...
Click to collapse
Hope this helps....my device is not a MTK device rt?
Skrappy187 said:
Hope this helps....my device is not a MTK device rt?
Click to expand...
Click to collapse
Hey mate,
Your right out of luck there unfortunately i cant find firmware anywhere for it which is very unusual theres no reference to the model number anywhere for firmware
Wow these phones are absolute peices of ****,
So there's OEM unlock in developer options, BUT
Theres no fastboot at all, and also when pulling a backup of the friggen firmware it cant be flashed back optus have done something to it so it wont pull the preloader and a few other files, and what files it does pull wont flash back with SP Flash tool anyway gives an error & when trying to load the scatter file after the failed flash it cant be loaded again gives alot of errors with the file and nothing can be loaded to be flashed,
Also with the model number these are actually 5044T as SP flash tool confirmed this but also compatible with 5044D firmware as i used the .exe for 5044D to try and flash it and it would have if optus didnt block the international code to block the flash from happening,
Ill keep stabbing at it but im thinking the OEM unlock is purely there for asthetic purposes only unfortunately so without being able to flash anything back to it its not even worth editing the recovery and packing it with TWRP ramdisk as it cant even be flashed
---------- Post added at 03:59 AM ---------- Previous post was at 03:57 AM ----------
Skrappy187 said:
Hope this helps....my device is not a MTK device rt?
Click to expand...
Click to collapse
Look for other versions of firmware for it that sre qualcomm and not mediatek,
These mediatek can traditionally use T & D firmwsee if it wasnt for the flash block,
Just make sure they are qualcomm worth a try as i still cant find a firmware for your model but if i do find one ill get the link to you here
Matty1993 said:
Wow these phones are absolute peices of ****,
So there's OEM unlock in developer options, BUT
Theres no fastboot at all, and also when pulling a backup of the friggen firmware it cant be flashed back optus have done something to it so it wont pull the preloader and a few other files, and what files it does pull wont flash back with SP Flash tool anyway gives an error & when trying to load the scatter file after the failed flash it cant be loaded again gives alot of errors with the file and nothing can be loaded to be flashed,
Also with the model number these are actually 5044T as SP flash tool confirmed this but also compatible with 5044D firmware as i used the .exe for 5044D to try and flash it and it would have if optus didnt block the international code to block the flash from happening,
Ill keep stabbing at it but im thinking the OEM unlock is purely there for asthetic purposes only unfortunately so without being able to flash anything back to it its not even worth editing the recovery and packing it with TWRP ramdisk as it cant even be flashed
---------- Post added at 03:59 AM ---------- Previous post was at 03:57 AM ----------
Look for other versions of firmware for it that sre qualcomm and not mediatek,
These mediatek can traditionally use T & D firmwsee if it wasnt for the flash block,
Just make sure they are qualcomm worth a try as i still cant find a firmware for your model but if i do find one ill get the link to you here
Click to expand...
Click to collapse
Thank you bro....it looks like you gave it your all....thank you again.
---------- Post added at 05:05 AM ---------- Previous post was at 05:02 AM ----------
Matty1993 said:
Hey mate,
Your right out of luck there unfortunately i cant find firmware anywhere for it which is very unusual theres no reference to the model number anywhere for firmware
Click to expand...
Click to collapse
I did find a PC root method for this device do that help? If so let me know. Also the Linux to Dos explot do reboot my device if a home brewed root needs to be done.
Skrappy187 said:
Thank you bro....it looks like you gave it your all....thank you again.
---------- Post added at 05:05 AM ---------- Previous post was at 05:02 AM ----------
I did find a PC root method for this device do that help? If so let me know. Also the Linux to Dos explot do reboot my device if a home brewed root needs to be done.
Click to expand...
Click to collapse
Yeah go on ill get details and give it a whirl if i can get root shell access i can push my TWRP i made to it through ADB shell thats all thats stopping me from trying that,
Also made a philz_recovery.img for it but cant test it as the scatter wont load to flash the recovery im trying to build a scatter as i found it wont load due to illegal information within the scatter.file itself through some investigation, i just have to find the illegal info & remove it to allow flash hopefully
But if i can get root & root shell i can just push it and if all works i can just upload the method here on how to do it until i work the scatter out
Had a bit of success,
Ive finally managed to pull the preloader and all other missing files,
Now i can make a scatter file that will work for it hopefully and i can port a recovery to it for rooting,
Ill update progress as i go
I have an Alcatel Tetra running Android 8.1, June 2018 update, and I would like to root it. It was only released in September 2018, though, so there seems to be no common solution.
Some specs are:
480x854 resolution on 5" screen @ 70hz
1.1ghz MediaTek MT6739WM CPU
2gb ram
4G LTE GSM on AT&T
WIFI A/B/G/N 2.4ghz
Bluetooth 4.2 LE
Android 8.1, June 2018 update
16gb internal storage with support for 128gb sd card
GE8100 GPU
5MP front camera & 2MP back
USB 2.0 port, 3.5mm jack
Root
clcombs262 said:
I have an Alcatel Tetra running Android 8.1, June 2018 update, and I would like to root it. It was only released in September 2018, though, so there seems to be no common solution.
Some specs are:
480x854 resolution on 5" screen @ 70hz
1.1ghz MediaTek MT6739WM CPU
2gb ram
4G LTE GSM
WIFI A/B/G/N 2.4ghz
Android 8.1, June 2018 update
16gb internal storage with support for 128gb sd card
GE8100 GPU
5MP front camera & 2MP back
Click to expand...
Click to collapse
I have one also id like to root
I also have this phone. Almost cobbled together a twrp but just need the correct recovery-kernel & offset file to repack it. As it stands right now the twrp build will boot loop, but I know all the other pieces are solid ( correct resolution set, correct prop.default, fstab files, .rc files and so on) unfortunately so flash tools is useless until we can get a custom DA file that works with the Tetra. This whole process has been quite a pain lol but I'm close. If I can get it figured out I'll make a thread here upload all relevant files
Update: I'm currently using a few different RATs to pull any and all files possible while also trying to see what exploits (if any) I may be able to leverage with them. currently still lacking the recovery.fstab, but all other files needed for the ramdisk folder section of the recovery.img is set (put together the prop.default from scratch as I can't pull it from the phone). Still need all files outside of the ramdisk folder though (mostly just a proper recovery-kernel and offset, think I may be able to substitute the other files from a similar Alcatel MT6739 phone, the 3x/5058, which I have a stock firmware for). I also have the source code for the 4.4.95+ kernel that's on the Tetra, digging through it to see if I can use anything from it. If anyone has any thoughts about what could be done with all this stuff I have please feel free to share, as I could use some fresh eyes on this.
MICHAEL(SMHOS.ORG) said:
Just use magisk to root ,or ONE click root for PC is easy bro??
Click to expand...
Click to collapse
#1. There is no publicly available fw for this device as of this moment to patch with Magisk.
#2. Sp flash tool cannot currently readback or download to this phone, as the necessary DA file is unavailable. That means no way to get the boot.img or recovery.img to make magisk root/port TWRP
#3. NO ROOTING APPS WHETHER THEY BE APK OR PC BASED, WORK WHATSOEVER ON THIS PHONE, AND 80% OF THEM ARE BORDERLINE MALICIOUS (HERE'S LOOKING AT YOU KINGROOT)
#4 please kindly ****post elsewhere.
Root Alcatel Tetra
MICHAEL(SMHOS.ORG) said:
Just use magisk to root ,or ONE click root for PC is easy bro
Click to expand...
Click to collapse
I know for a fact One Click Root has no support, and Magisk is unreliable in my experience. I think I may have a way to apply a root patch, but obviously I need the patch first. I believe I can exploit the "apply update from sd card" function but haven't really tested it.
MICHAEL(SMHOS.ORG) said:
OK try it and check if any patch or so,because I use Flashing tools like Gsm alladin cracked or android adb multi tool since it support adb function for root
Click to expand...
Click to collapse
There is currently no adb exploit to gain root that works on this device. Trust me, I've tried. There is not an easy fix for this phone. The only options I see, is for someone who has access to the most recent NCK box, or Miracle thunder MT2 ( which added support for the mt6739 chip set) to dump the firmware and share It with the public, or for the Download Assistant file for this phone to be released, at which point SP flashtools can be used to dump the firmware, at which point a custom TWRP can be ported, root can be gained, and bob's your uncle. I've spent the last month going over every possible way to crack this phone open, and aside from finding/developing an as of yet unknown exploit, the only options available require a firmware dump (which currently can only be made with the 2 aforementioned box tools). I've been using every method I can think of to get a functioning TWRP without the stock recovery, with no luck yet. Ive taken every possible amount of info and files accessable from the phone using adb shells, mtk based tools, and RATs. I've got ahold of pretty much all publicly available firmwares and TWRPs for other Mt6739 phones that are already cracked, to see if I could take the files/Info and modify them to fill in the gaps and get a functional TWRP. Hasn't worked yet and while I've narrowed the reasons why down, those reasons seem to be hard blocks that could only be overcome through root access/access to the Tetras specific firmware. Which as you see is a catch 22 where you would need root to get root. I've even tried to get ahold of an ota update directly from AT&Ts cdn to try and exploit. I have the dl address but am not sure how to use it, as trying to connect to it from phone browser or PC just returns as forbidden. I'm honestly a little burnt out with it at the moment and am gonna go mess with some other phones I have and come back to this later when/if hopefully some new resources become available.
Tlr ; the easy and common solutions aren't gonna cut it, so save your breath
cthulu_rises said:
There is currently no adb exploit to gain root that works on this device. Trust me, I've tried. There is not an easy fix for this phone. The only options I see, is for someone who has access to the most recent NCK box, or Miracle thunder MT2 ( which added support for the mt6739 chip set) to dump the firmware and share It with the public, or for the Download Assistant file for this phone to be released, at which point SP flashtools can be used to dump the firmware, at which point a custom TWRP can be ported, root can be gained, and bob's your uncle. I've spent the last month going over every possible way to crack this phone open, and aside from finding/developing an as of yet unknown exploit, the only options available require a firmware dump (which currently can only be made with the 2 aforementioned box tools). I've been using every method I can think of to get a functioning TWRP without the stock recovery, with no luck yet. Ive taken every possible amount of info and files accessable from the phone using adb shells, mtk based tools, and RATs. I've got ahold of pretty much all publicly available firmwares and TWRPs for other Mt6739 phones that are already cracked, to see if I could take the files/Info and modify them to fill in the gaps and get a functional TWRP. Hasn't worked yet and while I've narrowed the reasons why down, those reasons seem to be hard blocks that could only be overcome through root access/access to the Tetras specific firmware. Which as you see is a catch 22 where you would need root to get root. I've even tried to get ahold of an ota update directly from AT&Ts cdn to try and exploit. I have the dl address but am not sure how to use it, as trying to connect to it from phone browser or PC just returns as forbidden. I'm honestly a little burnt out with it at the moment and am gonna go mess with some other phones I have and come back to this later when/if hopefully some new resources become available.
Tlr ; the easy and common solutions aren't gonna cut it, so save your breath
Click to expand...
Click to collapse
/
+1 on the no easy solutions. In theory, there is a utility built in to flash an update from an sd card from fastboot menu, or if you have an activity launcher.... exploitable, maybe?
Also, you must remember that those people are just people like you and me, with more experience. Since this phone was released September of this year, it may be awhile. So we may be on our own since the Tetra is a lower end device. I got a system dump, which I know can be used ro make firmware, but am not sure how to do so
clcombs262 said:
/
+1 on the no easy solutions. In theory, there is a utility built in to flash an update from an sd card from fastboot menu.
I got a system dump
Click to expand...
Click to collapse
Only way to use stock sideload would require you to sign the zip with the manufacturer private keys. I did pull some keys & certs from the phone but never got a chance to see if they were the proper ones.
And pls upload your system dump
Dont use this, see next post
Last post was the wrong file.
Here you'll find:
*DA file
*Auth file
*Preloader
*.mbn
*.sca
All specific for the 5041c, direct from Alcatel
https://drive.google.com/file/d/1FS0MFuoFSRlSncuUUtsZM808fqypUmue/view?usp=drivesdk
Yo OP what's up with that system dump?
cthulu_rises said:
Yo OP what's up with that system dump?
Click to expand...
Click to collapse
It ll be awhile. My ssd took a dump and died last night and I don't get paid for 2 weeks, so can't afford a new one.
That zip wasn't backed up unfortunately. So right now I have no pc
clcombs262 said:
It ll be awhile. My ssd took a dump and died last night and I don't get paid for 2 weeks, so can't afford a new one.
That zip wasn't backed up unfortunately. So right now I have no pc
Click to expand...
Click to collapse
Dang sorry to hear that brotha. Do you remember what method you used to get the system dump? I can try my hand at it
cthulu_rises said:
Dang sorry to hear that brotha. Do you remember what method you used to get the system dump? I can try my hand at it
Click to expand...
Click to collapse
See next post
cthulu_rises said:
Dang sorry to hear that brotha. Do you remember what method you used to get the system dump? I can try my hand at it
Click to expand...
Click to collapse
The primary code I used was
Code:
adb pull /system
adb pull /data
I may have used other code; I don't remember. It's been awhile.
Also, so my friends will stop asking, will you post how to root/flash recovery with what you provided? It'll be easier to link to the post then explain it 500 times, since I end up their IT guy a lot. Thanks in advance
Take the Da file, auth file, and scatter file provided and load them in the latest version of SP Flash Tool, use the readback function to dump the recovery img. If memory serves me correctly, mmcblk0p18 is the location for it. (use the scatter file to locate the begining address and the length for it). Once you have the stock recovery img, manually port twrp to it using carliv image kitchen. Then fastboot to flash twrp. If you did it right then you can boot into twrp and flash supersu or magisk for root. Make sure to boot directly into recovery after flashing, because the recovery gets replaced by stock after a normal boot
---------- Post added at 09:12 PM ---------- Previous post was at 09:11 PM ----------
I would have posted more already but have no access to PC for a while. I haven't even had a chance to do this for myself yet
cthulu_rises said:
Take the Da file, auth file, and scatter file provided and load them in the latest version of SP Flash Tool, use the readback function to dump the recovery img. If memory serves me correctly, mmcblk0p18 is the location for it. (use the scatter file to locate the begining address and the length for it). Once you have the stock recovery img, manually port twrp to it using carliv image kitchen. Then fastboot to flash twrp. If you did it right then you can boot into twrp and flash supersu or magisk for root. Make sure to boot directly into recovery after flashing, because the recovery gets replaced by stock after a normal boot
---------- Post added at 09:12 PM ---------- Previous post was at 09:11 PM ----------
I would have posted more already but have no access to PC for a while. I haven't even had a chance to do this for myself yet
Click to expand...
Click to collapse
I have access to a library pc, but youre not allowed to install anything. No adb or sp flash tool. Though i do have a theory about using stock recovery...
Probably wont work, but hey. YOLO. Still waiting for my ssd to be in stock
Well here's the stock ROM. Cut SP flash Tool and all its hassles out and use this. Just extract the recovery.img and port twrp, or extract boot.img and patch with magisk. Am gonna do this when I get home, I have a beater laptop I can use but no internet there, so I'll post my work the next time I can come to town and get cell service.
https://mega.nz/#!dpFmBIgI!4FXN0VYjTYSyMp608BCCDOtEVABHqOwoJPBx_OkaKrE
This zip contains the magisk patched boot.img, happy rooting!
After many searches for the best help on my new Asus ZenFone V V520KL, I have no way to unlock the bootloader. Asus doesn't provide any support for this 2017 model, nor does Verizon, the company the phone was made for.
It comes stock with Nougat 7.0 OS, 32 GB ROM & 4 GB RAM. It's got a decent size screen and runs not too too bad.
I'm wondering if one of the tech people here would be so kind as to help me with not only unlocking the bootloader so I can then install a custom recovery image, preferrably TWRP, since I have used this type of program before on my other ZenFone 3 Zoom.
I already have ADB tools on my Windows 7 notebook (32-bit). I used it to install the last root on my other aforementioned phone so it will work.
What I'm wondering about is the bootloader unlock tool, custom recovery image (TWRP), and a way to root the bastard. Hopefully we can relock the bootloader after the job's done because it's annoying on my other phone to always have to bypass the "Can't check for corruption." screen before the phone actually boots. Again this is for the Asus ZenFone V V520KL model. There is really no information anywhere right now I know of that gets this job done.
Having a custom Pie 9.0 ROM upgrade would be the best if possible once we root the device.
My name is Andrew, S.D. from Canada.
Thanks and blessings.
Root
Did you find a way to root it?
No, I still need help with the original post. I can root the ZenFone 3 Zoom ZE553KL but they already tell us how to do that in another forum.
the Bootloader for v520kl is already unlock by ENG Firmware
Just serch it in forums
You're talking to a noob. Give me the location of ENG firmware.
Hi friend, in the other post de link for downloading de ENG Firmware is broken
[email protected] said:
Hi friend, in the other post de link for downloading de ENG Firmware is broken
Click to expand...
Click to collapse
This is the link
http://www.mediafire.com/file/lc17b75qbvy018z/Asus_Zenfone_V_V520KL_All_WW_ENG_T3.3.15.zip
I tried to flash it did not work for me..
---------- Post added at 10:55 PM ---------- Previous post was at 10:43 PM ----------
Doctor Andrew said:
You're talking to a noob. Give me the location of ENG firmware.
Click to expand...
Click to collapse
Here is the link:
https://forum.xda-developers.com/showpost.php?p=78833735&postcount=52
Hi friend,
It's de the same rom for this page
https:
www
hardreset.info/devices/asus/asus-v520kl/faq/firmware/ because, the size of this rom is 813MB
and the size of the rom of the link that you provide is 775.53 MB and the files is the same name.
or this rom has been updated.
someone know what version of android have this rom
Okay so we now have a link to just the ROM it looks like. Do we have a way to unlock the bootloader yet and install TWRP first? What about the TWRP image file, do we have one of those as well?
Doctor Andrew said:
Okay so we now have a link to just the ROM it looks like. Do we have a way to unlock the bootloader yet and install TWRP first? What about the TWRP image file, do we have one of those as well?
Click to expand...
Click to collapse
To flash the ENG rom, you do not need to unlock the bootloader. Just the Asus flash tool.
Once you flash it, you can reboot to fastboot mode(adb reboot bootloader) and use fastboot oem unlock to unlock bootloader. Be warned though the ENG firmware is very basic. No web browser, no google play, you can't pull down the notification bar etc. (Great battery life though with about 7-10 days since I am not using it at all).
As of right now, there is no TWRP for it that i know of. In fact, I can't even boot into recovery atm. I also am unable to get boot.img file form the .raw file so the various methods to root it seem to be out of reach for the moment.
I've absolutely no interest in the ENG firmware. Still looking for a solution to the original post that people can understand and use easily.
Doctor Andrew said:
I've absolutely no interest in the ENG firmware. Still looking for a solution to the original post that people can understand and use easily.
Click to expand...
Click to collapse
Well, ENG is the only way i could figure it out but I finally manged to get root on the phone with magisk. Still have some work to do to get play store and everything else running properly, but for now, hardest part is done.
oh my god - rooooot
faericia said:
Well, ENG is the only way i could figure it out but I finally manged to get root on the phone with magisk. Still have some work to do to get play store and everything else running properly, but for now, hardest part is done.
Click to expand...
Click to collapse
Good time of day, Faericia, this is just great news. You can share the experience of getting root with magisk?
Regarding Google Play and all that, where you need Google, using a bunch of microG and Aurora store.
MicroG is the core of Google services, which allows you to pass authorization through Google, synchronize and do it all without any garbage code, according to my observations, the expense is not much spent.
Aurora shop, as an analogue of Google Play, the application, the ability to save apk.
Due to the lack of binding to your Google account.
I think this connection may be relevant and rooted.
The initial partition should appear as root, it intends to resolve all the problems that I have in my phone. for asus applications, after I have done my best, several attempts have already been made.
It was possible to look in read mode using root explorer.
Perhaps you can somehow remove the protection of verizon on the bootloader.
PS the most hardcore variation of raw firmware, a hex editor, search in that between code, boot, recovery, system, etc. Very large empty spaces. previously there were 100 miles earlier.
I think this is part of verizon jokes.
This article should be cut and placed in img.
Thanks so much in advance.
hello when you finish you could share through a tutorial what you did I have my asus v with verizon rom and only data but if I can make it functional with the rom eng then better
Okay, Here are the steps. Before anything else though, I should warn you that I have not been able to get safetynet to pass. So if you have apps that require safetynet to pass, this may not be the way to go.
First you will need the ENG firmware:
https://mega.nz/#!l7wBlQ4B!uB63yH5Rir24GaSfDMWKowqdz-N_sc6SJ-q1WuuGiqM/
Also Asus Flash tools v 1.0.0.72:
https://drive.google.com/file/d/11rcjOgdpJhpK97GzbhYK6cYEIWOtzKE9/view
I am assuming you know adb and such. If not, search the forums and get the adb tools.
Using adb, Reboot to bootloader. ( adb reboot bootloader )
Load the .raw file in the asus flash tool, select v520KL and flash.
Once flash is done, unlock bootloader by going into bootloader (adb reboot bootloader) then type (fastboot oem unlock.)
Here is the patched_boot.img I used if you want to just try to flash that and see if it will work. This is for the eng firmware.
https://drive.google.com/file/d/1fUxGc27lrodR3ro9MIspde73G8Xg9VlW/view?usp=sharing
Go into bootloader and flash. (fastboot flash boot patched_boot.img)
Install magisk manager and test it out.
If you wish to patch the img yourself, the steps are below (still working on it):
So now we have the phone unlocked, and the software is very basic. We also need the boot.img file to patch since we do not have TWRP. Since I couldn't get it from the raw file (the extracted file is invalid with a size of 0 bytes) I decided to extract it from the phone. But to extract from the phone we need root. So for this next step, temporary root will have to do.
You can get temp root by using KingoRoot. Use the PC version and you will get root. This is just so we can extract the files from the phone itself.
I need to find the steps for the next steps again, but the basics is, extract boot.img from the phone. Patch it using magisk manager and then flash the patched_boot.img in bootloader mode. I had google play working(chinese version) but once i removed kingoroot it kept crashing. I currently have magisk and it gives me the root permissions but safetynet fails. I will retry this tomorrow and see if I can fix the safetynet issue and update this post with the steps.
Also I seem to have borken recovery mode on my phone. That may be because I tried flashing bunch of other stuff before I managed to root it so I do not know if it will be the same situation to you or not. I believe after I flashed ENG firmware, i had access to recovery mode at one point, but I may have just messed it up. Either way, Expect updates in the near future.
asus recovery
A huge over many thanks.
I also tried to get a temporary root, via the kingoroot pc version, it did not work, I suspect it because I installed eng, but did not oem unloock, when I did unlock, I somehow managed to get the boot out of the firmware, the user from 4pda was patched, but said that this boot is from 8 android, I thought that I had schizophrenia because later on trying to get boot I also got 0mb, this was due to the unexpected end of the archive.
In general, by flashing this boot, I also found a recovery mode and even a recovery mode, but going into recovery a message from Verizon was displayed, standard, when you roll the eng firmware for 5 seconds, hold something, etc. Well, you understand. And the whole laugh is that it was in a circle.
I suspect that asus had any plans for this device or for this amount of components. In other words, it was some kind of blank that was abandoned, maybe asus thought that this exclusive for verizon will make a trap, and then they say on the basis of v520kl we will make a non-exclusive open device, but alas, a huge member between two rolls.
Therefore, fortunately or unfortunately, recovery was not broken by you, most likely it was not working initially, but this is only a guess.
Daniel.Sim said:
A huge over many thanks.
I also tried to get a temporary root, via the kingoroot pc version, it did not work, I suspect it because I installed eng, but did not oem unloock, when I did unlock, I somehow managed to get the boot out of the firmware, the user from 4pda was patched, but said that this boot is from 8 android, I thought that I had schizophrenia because later on trying to get boot I also got 0mb, this was due to the unexpected end of the archive.
In general, by flashing this boot, I also found a recovery mode and even a recovery mode, but going into recovery a message from Verizon was displayed, standard, when you roll the eng firmware for 5 seconds, hold something, etc. Well, you understand. And the whole laugh is that it was in a circle.
I suspect that asus had any plans for this device or for this amount of components. In other words, it was some kind of blank that was abandoned, maybe asus thought that this exclusive for verizon will make a trap, and then they say on the basis of v520kl we will make a non-exclusive open device, but alas, a huge member between two rolls.
Therefore, fortunately or unfortunately, recovery was not broken by you, most likely it was not working initially, but this is only a guess.
Click to expand...
Click to collapse
I know recovery mode was working with VZW firmware. I know this because I tried installing using adb sideload several times. I might be mistaken on getting there once i flashed eng firmware but again, it has been a month or two since I tried it and all I know is, it won't go into the recovery screen now. Oh well, not my main phone so irrelevant.
I have installed patched boot img with fastboot. Now have root. But there a lot of apps not working. No Google apps at all. And no way to install them.
---------- Post added at 06:23 PM ---------- Previous post was at 06:15 PM ----------
Have installed patched boot img by faericia. Now I got root. But eng version doesn't have Google apps, so no play store, no Google pay, no accounts, no Gmail. And I don't know how to install it.
game #1 said:
I have installed patched boot img with fastboot. Now have root. But there a lot of apps not working. No Google apps at all. And no way to install them.
---------- Post added at 06:23 PM ---------- Previous post was at 06:15 PM ----------
Have installed patched boot img by faericia. Now I got root. But eng version doesn't have Google apps, so no play store, no Google pay, no accounts, no Gmail. And I don't know how to install it.
Click to expand...
Click to collapse
The only time I had Google apps was when I had kingoroot root still int he system. I then downloaded the Chinese google apps installer and used that to get it. Once i removed kingoroot google framwork kept crashing making it unusable.. If you don't need to pass safetynet, that might be the way. Othewise, I am still trying to work on it.
faericia said:
The only time I had Google apps was when I had kingoroot root still int he system. I then downloaded the Chinese google apps installer and used that to get it. Once i removed kingoroot google framwork kept crashing making it unusable.. If you don't need to pass safetynet, that might be the way. Othewise, I am still trying to work on it.
Click to expand...
Click to collapse
I found out how to stop frameworks from crashing. Just make it a system app. I use link2sd for this.
Now all gapps work nice.
As far as I know the bootloader for this phone is unlockable, but I've successfully rooted the L38041. I'll include the steps below. Please note, I'm only relating how I did this. There are probably more efficient methods, but, for me, this worked. I'm not responsible if you hardbrick your device.
Requirements:
a. Latest QPST from qpstflash (sorry, can't post links yet. Just google it).
b. Magisk Manager
c. Stock L38041 rom. I used the global version from FirmwareX.
d. ADB and Fastboot tools.
This method uses Qualcomm flashing, so if you've never heard of that, read as much as you can before you try this.
Steps
1. Download and extract the ROM to your PC.
2. Attach your adb enabled device via usb and copy the boot.img file from the extracted folder to your device storage.
3. Install and open magisk manager on your device, then install magisk via 'patch stock boot image'. Navigate to where you put the stock boot.img and select it.
4. Once completed, take the patched_boot.img, rename it back to boot.img, and put it back in the extracted ROM folder on your PC. Make sure you've backed up your stock boot. because you'll be replacing it with the patched.
5. Install the QPST package on your PC and run QFIL. Select Flat build, then navigate the programmer path to your ROM folder. Select the prog_emmc_ufs_firehose_Sdm660_ddr.elf as your programmer path. Next, load XMLs RawProgram0.xml and patch0.xml.
6. At this point, run the adb command "adb reboot edl." This will put your device into emergency download mode, in which you will be able to use QFIL . QFIL should go from 'No Port' to 'Qualcomm HS-USB QDLoader 9008'. Immediately after you see this pop up, select 'Download'. This will completely reset your device.
7. If flashing was successful, wait a bit then boot your device. You should see a little warning complaining that the software has been altered. Wait a little bit more. You can install magisk manager at this point if it didn't show up after the flash. Reboot the device again.
8. Et voila, you should have a rooted device now. Due to the locked bootloader, you still can't (or at least I couldn't) use a custom recovery, were there even one available.
Note: if you get a sahara error in the flashing process, it's probably because you waited too long to hit download.
Hope this helps for those of you with rooting your K5 Pro
edit: There is a way to unlock the bootloader! User KiiKeEp has posted a guide on the method, which also contains a usable TWRP for the global rom. Here's a more streamlined version adapted from his tutorial. Make sure you have oem unlocking enabled in developer options.
1. Go to "zui.com/iunlock" and fill in the boxes.
a. First input your IMEI1 which can be found by dialing *#06# or going to the "about phone" section in the settings.
b. Second, input your phone's serial number. You can find this by enabling debugging in your developer options menu, then using the adb command "adb reboot bootloader"
c. Input your email into the third box.
d. Type the displayed 4 digit number into the 4th box and then submit.
2. You'll receive an email containing a download link for an unlock .img called "sn.img". Download it.
3. Flash the unlock image in fastboot. Use the command "fastboot flash unlock", drag and drop the sn.img into the command window, hit enter, then follow the onscreen command.
4. If this is done correctly, you can flash the twrp.img that KiiKeEp included in his post. "fastboot flash recovery twrp.img"
Hello, Thanks for the information. I have bought this phone in November last year, and i like it. I bought it from Sunsky, i have the global version zui 5.0.066 st. Could you post or send me a video in how to do this please. I'm new in flashing phones. I only have flashes a Lenovo K5 note in the past (the 2016) version, it was easy because lenovo post the firmware and the instructions, i did it to upgrade the phone from Lollipop to Marshmallow. But i didn't root it. The K5 note is my father's phone.
I see how the Chinnese firmware looks, could i install the chinese firmware to my phone without any compatibility issues?, also i saw that the chinnese firmware has been updated to zui 5.0.163 st, with improvements and sound stability. And in the Lenovo Chinnese official club also there is a similar steps for rooting the device. Could you help me please to confirm these, and teach me how to do it, please?
Also, i have both firmwares, the CN lastest version; i downloaded it from the lenovo's chinnese official club (zui 5.0.163 st). And I also have the ROW version i don't remember where i downloaded it but this is the name of the file: L38041_ROW_OPEN_USER_Q00020.0_O_ZUI_5.0.117_ST_181225.rar
I have downloaded the QPFIL tool and lenovo drivers too. So i'm ready to learn. It would be great if you can make a video, please if you could. I only have install global versions, in the K5 note i install the global version. I could install the CN version in my K5 Pro without any issues? Thanks in advanced.
Julio2019 said:
Hello, Thanks for the information. I have bought this phone in November last year, and i like it. I bought it from Sunsky, i have the global version zui 5.0.066 st. Could you post or send me a video in how to do this please. I'm new in flashing phones. I only have flashes a Lenovo K5 note in the past (the 2016) version, it was easy because lenovo post the firmware and the instructions, i did it to upgrade the phone from Lollipop to Marshmallow. But i didn't root it. The K5 note is my father's phone.
I see how the Chinnese firmware looks, could i install the chinese firmware to my phone without any compatibility issues?, also i saw that the chinnese firmware has been updated to zui 5.0.163 st, with improvements and sound stability. And in the Lenovo Chinnese official club also there is a similar steps for rooting the device. Could you help me please to confirm these, and teach me how to do it, please?
Also, i have both firmwares, the CN lastest version; i downloaded it from the lenovo's chinnese official club (zui 5.0.163 st). And I also have the ROW version i don't remember where i downloaded it but this is the name of the file: L38041_ROW_OPEN_USER_Q00020.0_O_ZUI_5.0.117_ST_181225.rar
I have downloaded the QPFIL tool and lenovo drivers too. So i'm ready to learn. It would be great if you can make a video, please if you could. I only have install global versions, in the K5 note i install the global version. I could install the CN version in my K5 Pro without any issues? Thanks in advanced.
Click to expand...
Click to collapse
Sorry, I don't really have the time or the facilities to make a tutorial video, but the Chinese instructions follow the same process, only breaking up the process into a few more steps. Both achieve the same result. My thinking is that you might be able to install the Chinese firmware, but some forum discussions suggest that you will have some modem and IMEI issues if you do. There are ways to back these up using QPSTs software download application. My guess is that it'll probably work, but that it won't work flawlessly. Let me know how it turns out if you try it.
If you want to update your software without rooting, simply follow the process from step 5, using the new L38041_ROW ROM without swapping the boot.img. The link below shows the flashing process pretty well, but you'll need the later versions of QPST since you'll be using .elf programming paths and not .mbn. Once again, that will wipe your phone entirely.
"https://www.youtube.com/watch?v=W9Cz4LwAzLg"
Hello! Don't worry i'm going to follow your steps. By the way, about the CN firmware, would there be a way to back up my rom, my actual ROM with the modem and imei configuration? Is to prevent in bric the phone. I have read the warnings about the issues you talked about, and apparently these setteings are store in the nvram. There is a way to do a recovery image or ROM of my current firmware?
---------- Post added at 04:17 PM ---------- Previous post was at 04:14 PM ----------
And what version is your ZUI now? When i bought the phone, i tried to convince the provider to not install the custom global firmware, but he told me that lenovo technician said that they have to intall that global firmware. So, i accepted to buy the phone with the global version. I was trying to avoid all the gapps that the majority of phones have.
---------- Post added at 04:20 PM ---------- Previous post was at 04:17 PM ----------
Could you tell me how to uninstall the gapps, please?. I only want to have running the only and minimal google processes. And the other reason is because i like the clock widget with weather that the CN version have. There are other things that the CN have that the global version doesn't have.
---------- Post added at 04:21 PM ---------- Previous post was at 04:20 PM ----------
Another question, do you know what enshrine is? Is in the wallpaper submenu but it doesn't do anything in my case. And theres a folder with images that i think are the wallpapers of the CN firmware. Thanks in advance
---------- Post added at 04:29 PM ---------- Previous post was at 04:21 PM ----------
If I flash i need to install gapps or the gapps installs themeselve?
Julio2019 said:
Hello! Don't worry i'm going to follow your steps. By the way, about the CN firmware, would there be a way to back up my rom, my actual ROM with the modem and imei configuration? Is to prevent in bric the phone. I have read the warnings about the issues you talked about, and apparently these setteings are store in the nvram. There is a way to do a recovery image or ROM of my current firmware?
---------- Post added at 04:17 PM ---------- Previous post was at 04:14 PM ----------
And what version is your ZUI now? When i bought the phone, i tried to convince the provider to not install the custom global firmware, but he told me that lenovo technician said that they have to intall that global firmware. So, i accepted to buy the phone with the global version. I was trying to avoid all the gapps that the majority of phones have.
---------- Post added at 04:20 PM ---------- Previous post was at 04:17 PM ----------
Could you tell me how to uninstall the gapps, please?. I only want to have running the only and minimal google processes. And the other reason is because i like the clock widget with weather that the CN version have. There are other things that the CN have that the global version doesn't have.
---------- Post added at 04:21 PM ---------- Previous post was at 04:20 PM ----------
Another question, do you know what enshrine is? Is in the wallpaper submenu but it doesn't do anything in my case. And theres a folder with images that i think are the wallpapers of the CN firmware. Thanks in advance
---------- Post added at 04:29 PM ---------- Previous post was at 04:21 PM ----------
If I flash i need to install gapps or the gapps installs themeselve?
Click to expand...
Click to collapse
There probably is a way of completely backing up your current stock ROM, and I see tutorials on here about how to do it, but I couldn't figure out how to backup mine. I already had both Chinese and ROW roms, so I wasn't too worried. You CAN use QFIL to backup your IMEI, Modem, etc, however. It's in the tools drawer as "QCN backup restore"
I'm using 5.0.117 from FirmwareX ("https://firmwarex.net/lenovo-k5-pro-l38041-android-8-1-official-firmware/"). Honestly I'm unsure what release I was using before the flash. The new ROW rom will have a full google suite, but once you obtain root you can remove whichever apps you don't like. There's a whole host of information on xda and other forums about removing system apps on a rooted phone. Hell, there are even apps that do it for you. Magisk has a module as well which uses terminal commands. A quick and dirty method is to use a root explorer like Mixplorer and delete the /system/app/xxxx folder that you don't want.
I have no idea what enshrine is. My wallpaper menu just has static, dynamic, and album selections, with an option for HD desktop.
My thinking is that the Chinese version won't have gapps, in which you could potentially flash open gapps using an app like flashify. I'm not sure, as I've only used the ROW 5.0.117. Remember that this device as yet has no TWRP and prevents boot of an unauthorized recovery, so any sort of flashing has to be done via qualcomm flashing, or in system after gaining root access.
rlb596 said:
There probably is a way of completely backing up your current stock ROM, and I see tutorials on here about how to do it, but I couldn't figure out how to backup mine. I already had both Chinese and ROW roms, so I wasn't too worried. You CAN use QFIL to backup your IMEI, Modem, etc, however. It's in the tools drawer as "QCN backup restore"
I'm using 5.0.117 from FirmwareX ("https://firmwarex.net/lenovo-k5-pro-l38041-android-8-1-official-firmware/"). Honestly I'm unsure what release I was using before the flash. The new ROW rom will have a full google suite, but once you obtain root you can remove whichever apps you don't like. There's a whole host of information on xda and other forums about removing system apps on a rooted phone. Hell, there are even apps that do it for you. Magisk has a module as well which uses terminal commands. A quick and dirty method is to use a root explorer like Mixplorer and delete the /system/app/xxxx folder that you don't want.
I have no idea what enshrine is. My wallpaper menu just has static, dynamic, and album selections, with an option for HD desktop.
My thinking is that the Chinese version won't have gapps, in which you could potentially flash open gapps using an app like flashify. I'm not sure, as I've only used the ROW 5.0.117. Remember that this device as yet has no TWRP and prevents boot of an unauthorized recovery, so any sort of flashing has to be done via qualcomm flashing, or in system after gaining root access.
Click to expand...
Click to collapse
Hello, thank for your patience and teachings. Here are the image of the Enshrine Menu i talked about:
("https://drive.google.com/open?id=1FFgx5pmM6mIQUhrOLN2cjgyfOvFTV83s")
and here is when i select this option:
("https://drive.google.com/open?id=1L34tjYpiPmjAU443sjHCcM8TM8JyOY-o")
Oh, and also i want to ask you what does this application call AppDaily from Lenovo, i don't understand how to use it, here the image:
("https://drive.google.com/open?id=1z6swpSxTPw4JeodwZ-OvkKUav9FWEOsZ")
Hearing all you teach me, then i think it would be safe for the moment to only upgrade my system with the zui 5.0.117. It would be safe to make this upgrade. Do you recommend me to root after the upgrade?. Or wait more time for other solution. I think that first it would be better to upgrade with the ROW firmware. How do you feel the last ROW update. Although is strange because i have only see zui 5.0.066 and zui 5.0.088 global versions. Maybe only few phones receive the update. What do you think about?, What do you recommend? If only i upgrade the phone with the ROW there wouldn't be any modem and imei issues? Thanks in advance.
Julio2019 said:
Hello, thank for your patience and teachings. Here are the image of the Enshrine Menu i talked about:
("https://drive.google.com/open?id=1FFgx5pmM6mIQUhrOLN2cjgyfOvFTV83s")
and here is when i select this option:
("https://drive.google.com/open?id=1L34tjYpiPmjAU443sjHCcM8TM8JyOY-o")
Oh, and also i want to ask you what does this application call AppDaily from Lenovo, i don't understand how to use it, here the image:
("https://drive.google.com/open?id=1z6swpSxTPw4JeodwZ-OvkKUav9FWEOsZ")
Hearing all you teach me, then i think it would be safe for the moment to only upgrade my system with the zui 5.0.117. It would be safe to make this upgrade. Do you recommend me to root after the upgrade?. Or wait more time for other solution. I think that first it would be better to upgrade with the ROW firmware. How do you feel the last ROW update. Although is strange because i have only see zui 5.0.066 and zui 5.0.088 global versions. Maybe only few phones receive the update. What do you think about?, What do you recommend? If only i upgrade the phone with the ROW there wouldn't be any modem and imei issues? Thanks in advance.
Click to expand...
Click to collapse
Remember, I'm just telling you how I did it. Your experiences might vary, but I've had no problems with this latest ROW in any aspect. It runs well, is pretty intuitive, and I notice very little change from the previous stock rom. If you want to try out either ROM before rooting, I'd suggest that you not customize your phone very much, or have any personal files on the built in storage, as these will be lost will each qualcomm flash. I'd recommend that if you're going to update, you might as well try rooting now to save yourself those issues. If you're uneasy about rooting and aren't having any issues with your current ROM, I'd suggest you wait until you have some pressing issue, as many of the included apps on this phone can be disabled or uninstalled. My purpose for rooting was that I became used to root-requiring apps like AdAway and some magisk extensions. The apps you're talking about are included with this system as well, but I never used them. Before the root, I disabled them. After the root, I deleted them.
This is a very new phone, so I wouldn't be surprised if there's more development 6 months in the future. Keep an eye on 4pda and club.lenovo's discussion forum for this device, as I anticipate their being the forerunners.
rlb596 said:
Remember, I'm just telling you how I did it. Your experiences might vary, but I've had no problems with this latest ROW in any aspect. It runs well, is pretty intuitive, and I notice very little change from the previous stock rom. If you want to try out either ROM before rooting, I'd suggest that you not customize your phone very much, or have any personal files on the built in storage, as these will be lost will each qualcomm flash. I'd recommend that if you're going to update, you might as well try rooting now to save yourself those issues. If you're uneasy about rooting and aren't having any issues with your current ROM, I'd suggest you wait until you have some pressing issue, as many of the included apps on this phone can be disabled or uninstalled. My purpose for rooting was that I became used to root-requiring apps like AdAway and some magisk extensions. The apps you're talking about are included with this system as well, but I never used them. Before the root, I disabled them. After the root, I deleted them.
This is a very new phone, so I wouldn't be surprised if there's more development 6 months in the future. Keep an eye on 4pda and club.lenovo's discussion forum for this device, as I anticipate their being the forerunners.
Click to expand...
Click to collapse
Agree. Hope they focus more in the subject we are talking. By the way, i have checked the club.lenovo's, and they got another new update with more improvements and a fix for their wechat app. , Now they are on zui 5.0.188 st. Could you show me images of the zui 5.0.117 interface, if you could. If not, don't worry i'm going to google it. But leaving this aside, i'm satisfy with the phone, in my opinion, is a great phone!, I like it, has excellent performance, a cool design, is slim, have a nice display, and good cameras. Have a nice day, hope we could talk again soon. If i get any more news, be sure i'm going to share it. Here in xda, i think we are the only ones who are talking about this phone. Hope more people and xda developers join us. Thanks. God blessed you.
Latest .188 st ZUI's interface changes a lot, but is the chinesse variant of the ROM, it comes with chinesse apps and only english and chinesse languages installed. Deleting the chinesse bloatware is easy, there is a folder named "preloaded" or preinstalled (something like that) in /system/ get root rights and delete the entire directory.
please create forum
rlb596 said:
As far as I know the bootloader for this phone is unlockable, but I've successfully rooted the L38041. I'll include the steps below. Please note, I'm only relating how I did this. There are probably more efficient methods, but, for me, this worked. I'm not responsible if you hardbrick your device.
Requirements:
a. Latest QPST from qpstflash (sorry, can't post links yet. Just google it).
b. Magisk Manager
c. Stock L38041 rom. I used the global version from FirmwareX.
d. ADB and Fastboot tools.
This method uses Qualcomm flashing, so if you've never heard of that, read as much as you can before you try this.
Steps
1. Download and extract the ROM to your PC.
2. Attach your adb enabled device via usb and copy the boot.img file from the extracted folder to your device storage.
3. Install and open magisk manager on your device, then install magisk via 'patch stock boot image'. Navigate to where you put the stock boot.img and select it.
4. Once completed, take the patched_boot.img, rename it back to boot.img, and put it back in the extracted ROM folder on your PC. Make sure you've backed up your stock boot. because you'll be replacing it with the patched.
5. Install the QPST package on your PC and run QFIL. Select Flat build, then navigate the programmer path to your ROM folder. Select the prog_emmc_ufs_firehose_Sdm660_ddr.elf as your programmer path. Next, load XMLs RawProgram0.xml and patch0.xml.
6. At this point, run the adb command "adb reboot edl." This will put your device into emergency download mode, in which you will be able to use QFIL . QFIL should go from 'No Port' to 'Qualcomm HS-USB QDLoader 9008'. Immediately after you see this pop up, select 'Download'. This will completely reset your device.
7. If flashing was successful, wait a bit then boot your device. You should see a little warning complaining that the software has been altered. Wait a little bit more. You can install magisk manager at this point if it didn't show up after the flash. Reboot the device again.
8. Et voila, you should have a rooted device now. Due to the locked bootloader, you still can't (or at least I couldn't) use a custom recovery, were there even one available.
Note: if you get a sahara error in the flashing process, it's probably because you waited too long to hit download.
Hope this helps for those of you with rooting your K5 Pro
edit: There is a way to unlock the bootloader! User KiiKeEp has posted a guide on the method, which also contains a usable TWRP for the global rom. Here's a more streamlined version adapted from his tutorial. Make sure you have oem unlocking enabled in developer options.
1. Go to "zui.com/iunlock" and fill in the boxes.
a. First input your IMEI1 which can be found by dialing *#06# or going to the "about phone" section in the settings.
b. Second, input your phone's serial number. You can find this by enabling debugging in your developer options menu, then using the adb command "adb reboot bootloader"
c. Input your email into the third box.
d. Type the displayed 4 digit number into the 4th box and then submit.
2. You'll receive an email containing a download link for an unlock .img called "sn.img". Download it.
3. Flash the unlock image in fastboot. Use the command "fastboot flash unlock", drag and drop the sn.img into the command window, hit enter, then follow the onscreen command.
4. If this is done correctly, you can flash the twrp.img that KiiKeEp included in his post. "fastboot flash recovery twrp.img"
Click to expand...
Click to collapse
Greetings Mr rl596!
So, what order do you recommend, i have downloaded KiiKeEp files, and successfully have receive my unlock image from lenovo, but in with order do i need do thinks. Is the following order correct?
1.- unlock bootloader
2.- Install zui 5.0.117 st ROM
3.- Install TWRP image
4.- Root device
Is this order correct?, I have the CN ROM in hand too, tha latest one is .188 st. But i need to make an EFS backup with the QPST tool, just in case. I have ask KiiKeEp, i'm waiting for his answer too. I want to make a video tutorial, so more K5 pro users could get benefit of this, and use all the potential this phone has. But what benefits does a unlock bootloader have?, Oh, and I almost forgot, for the QPST tool, do i have to install the driver that shows in the Device Manager as L38041 or the one that shows as QUALCOMM?
. Thanks in advanced.
Hi.
Thank you very much for the instruction - I successfully got root on my phone.
The only difference is I didn't use ADB, I just entered Download mode via the buttons: hold the volume + and - and power down until the logo flash.
:good:
Hi guys,
I tried but i have an error "Download Fail:FireHose Fail:FHLoader Fail:Le fichier spécifié est introuvable"
log :
13: E:\Téléchargements\[TuserHp.com]_L38041_ROW_OPEN_USER_Q00020.0_O_ZUI_5.0.117_ST_181225_qpst\[TuserHp.com]_L38041_ROW_OPEN_USER_Q00020.0_O_ZUI_5.0.117_ST_181225_qpst\prog_emmc_ufs_firehose_Sdm660_ddr.elf
00:25:31: Requested ID 13, file: "E:\Téléchargements\[TuserHp.com]_L38041_ROW_OPEN_USER_Q00020.0_O_ZUI_5.0.117_ST_181225_qpst\[TuserHp.com]_L38041_ROW_OPEN_USER_Q00020.0_O_ZUI_5.0.117_ST_181225_qpst\prog_emmc_ufs_firehose_Sdm660_ddr.elf"
00:25:32: 622900 bytes transferred in 0.203000 seconds (2.9263MBps)
00:25:32: File transferred successfully
00:25:32: Sahara protocol completed
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:False
Use Verbose:False
***** Working Folder:C:\Users\denis\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
Download Fail:FireHose Fail:FHLoader Fail:Le fichier spécifié est introuvable (The specified file is not found)
Finish Download
do you have any idea ?
thx in advance
I was wondering if there is a difference between CN version and global version regarding future update which device should i get for better support or root
Hi, I have unlokced the bootloader and install magisk via twrp. Is there custom roms for this phone
O meu lenovo apresentar "Qualcum crushdump mode" alguém com isso?
---------- Post added at 05:04 AM ---------- Previous post was at 04:54 AM ----------
O meu lenovo fica no final do processo com "Qualcum crushdump mode" alguém conseguiu resolver isso?
Help! I do the first process but now i can´t enter phone because tell from password on encryption screen.
EDIT: I enter to EDL mode (Press Vol- and Vol+ at the same time and conect to the usb) and flash with QFIL with the original boot.img and the phone turn on normally.
Lenovo K5 Pro ROM
Hi.
Are you have good working ROM for Lenovo K5 Pro?
This is an awesome, awesome phone. I rooted it with Magisk boot image patching on PC, without TWRP and even installed GCam on it to improve the camera massively - can now take photos with Night Sight. The specs of this phone are AMAZING for its price. And the best part is it is without any notches, holes, pop-up cameras and retains the traditional clean design.
I tried the unlock bootloader (official) way to root the device but got stuck here:
Code:
C:\minimal_adb_fastboot_v1.4.3>fastboot flash unlock sn.img
target didn't report max-download-size
sending 'unlock' (5 KB)...
then nothing happens (waited for like 10 minutes).
Tried to install QPST 2.7 (3 different versions, same error) but setup gives me the following message:
Code:
the installer was interrupted before QPST 2.7 could be installed
SOLUTION: Download QPST Portable
---------- Post added at 08:25 ---------- Previous post was at 07:57 ----------
Getting Sahara error but not because I've waited too long! Any solutions? Getting desperate now.