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.
Related
I exhausted everything by this point so im relying on this forum.
If anyone knows a way to install custom recovery on this phone or just some info in general would be appreciated..
Here's more detailed specs:
LG K8 (K350n)
SoC MediaTek MT6735
CPU Quad-core 1.3 GHz Cortex-A53
GPU Mali-T720
1.5GB Ram
Android 6.0
Help me xda , you're my only hope
Laitas said:
I exhausted everything by this point so im relying on this forum.
If anyone knows a way to install custom recovery on this phone or just some info in general would be appreciated..
Here's more detailed specs:
LG K8 (K350n)
SoC MediaTek MT6735
CPU Quad-core 1.3 GHz Cortex-A53
GPU Mali-T720
1.5GB Ram
Android 6.0
Help me xda , you're my only hope
Click to expand...
Click to collapse
I don't have a solution for you, but I can tell you what I've tried (I have the K350N also) and what doesn't work, for me anyway, so that you don't have to waste a week trying them yourself and get extremely frustrated like I did.
You need a scatter file, so that tools for MTK chips can copy your phone's boot and recovery images. One for the MT6735 exists but is not for the K8 and won't work. Supposedly you can create your own by using block info given by MTK Droid Tools, and manually editing the scatter file, but even the latest version (2.5.3d) does not support the MT6735 and does not give the info needed.
SP Flash Tool needs correct address info (which is gotten from a scatter file), it doesn't seem to take it from your phone. Without it, you'd not be able to pull the correct parts which make up your boot.img and recovery.img, so it's useless without the exact scatter file for your phone (whether it's the same SoC or not).
If you can get Miracle Box to stay connected to your phone, you can try its "Read" function. That didn't work for me, even after dozens and dozens of tries and messing about with different drivers.
Your best bet is probably to try using ADB to get the block/address/size info of the internal partitions, and editing that into a scatter file. Also, apparently the K8 uses a "standard Android" header, not MTK header like older MediaTek chipsets do. (Not quite sure what it means, but knowing so will probably be useful).
That's what I plan to try anyways, and if I manage to do it, I'll post again.
Aerieana said:
I don't have a solution for you, but I can tell you what I've tried (I have the K350N also) and what doesn't work, for me anyway, so that you don't have to waste a week trying them yourself and get extremely frustrated like I did.
You need a scatter file, so that tools for MTK chips can copy your phone's boot and recovery images. One for the MT6735 exists but is not for the K8 and won't work. Supposedly you can create your own by using block info given by MTK Droid Tools, and manually editing the scatter file, but even the latest version (2.5.3d) does not support the MT6735 and does not give the info needed.
SP Flash Tool needs correct address info (which is gotten from a scatter file), it doesn't seem to take it from your phone. Without it, you'd not be able to pull the correct parts which make up your boot.img and recovery.img, so it's useless without the exact scatter file for your phone (whether it's the same SoC or not).
If you can get Miracle Box to stay connected to your phone, you can try its "Read" function. That didn't work for me, even after dozens and dozens of tries and messing about with different drivers.
Your best bet is probably to try using ADB to get the block/address/size info of the internal partitions, and editing that into a scatter file. Also, apparently the K8 uses a "standard Android" header, not MTK header like older MediaTek chipsets do. (Not quite sure what it means, but knowing so will probably be useful).
That's what I plan to try anyways, and if I manage to do it, I'll post again.
Click to expand...
Click to collapse
Well i spend best part of this morning trying to a different aproach , i managed to find a ROM file (in kdz format, whitch woulve been useless for mtk tools anyway) whitch i extracted for a Recovery.img and tried to port the various recovieries with no awail for now. From what i've seen the filesystem inside the rom is a mess some of the files have the MTK headers others have the android ones and I'm trying to make this work entirely by trial and error.. If I'll manage to boot into the recovery I'll let you know. Wish me luck
Ok I managed to make a port from K10 that actually boots to recovery. I'll post updates as I work on it (all trial and error~)
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery : https://www.mediafire.com/?xopqenbvgrswgxm
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Laitas said:
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery : https://www.mediafire.com/?xopqenbvgrswgxm
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Click to expand...
Click to collapse
what K8 do you have? MTK or Qualcomm Version?
Laitas said:
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery :
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Click to expand...
Click to collapse
how you extract the recovery img from the kdz? thanks.
tomi.gutierrez.i said:
how you extract the recovery img from the kdz? thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2600575
Was using this . At this point only thing left is to wait for SuperSU update as it doesnt work on K8 yet
Laitas said:
http://forum.xda-developers.com/showthread.php?t=2600575
Was using this . At this point only thing left is to wait for SuperSU update as it doesnt work on K8 yet
Click to expand...
Click to collapse
i flash the image you give, and it cant mount system, so it cant flash supersu, the lg k10 have the same problem that this recovery (it might be for the port), so we have to wait a super su version for lg k10 and k8 and a functional TWRP
Laitas said:
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery : LINK
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Click to expand...
Click to collapse
Can you please show me how to install this recovery on my LG K8 (K350z)
and did you have any luck rooting this phone
all i want is Xposed installed and working but apparently i need root and recovery to install it
Yasser Da Silva said:
Can you please show me how to install this recovery on my LG K8 (K350z)
and did you have any luck rooting this phone
all i want is Xposed installed and working but apparently i need root and recovery to install it
Click to expand...
Click to collapse
I need the same thing like you :c
I dont know how to root my LG K8 in order to install Xposed
Have u found a way to root a lg k8
Maveroik said:
I need the same thing like you :c
I dont know how to root my LG K8 in order to install Xposed
Click to expand...
Click to collapse
Have u found a way to root a lg k8
Declan nalced said:
Have u found a way to root a lg k8
Click to expand...
Click to collapse
Nope man :'c
Laitas said:
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery : xxxxxxxxxxxxxxxx
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Click to expand...
Click to collapse
did u managed to unlock your bootloader? From the strategy of rooting HTC, LG also need a bootloader unlock before you having some privilege in flashing recovery... or rooting...
hackwilliam said:
did u managed to unlock your bootloader? From the strategy of rooting HTC, LG also need a bootloader unlock before you having some privilege in flashing recovery... or rooting...
Click to expand...
Click to collapse
That was step 1 you have to go to fastboot form adb and unlock it from there
I've got the k8 us375 model today and its running 6.0 with an update waiting to install. I'm sure it won't matter much but I'm going to avoid updating anytime soon.
With little research into the device I'm reading people trying kingroot and getting stuck with a semi brick and error. From what I've read about marshmallow is the root needs to be accepted from the boot.img which also needs to be insecure.
So unlocking the bootloader is first.
Second is modifying the kernel and
Then recovery needs to be made so that superSu can be flashed.
I'm no expert but neither am i a newbie to this process, however I'm a little rusty. If anyone knows a better way to describe the processes needed please enlighten me. I'll be away from my PC till this weekend but have a laptop i can tinker with tonight. Until i completely understand what needs to be done I'll continue to do research. Thanks
Sent from my LGUS375 using Tapatalk
justlovejoy said:
If anyone knows a better way to describe the processes needed please enlighten me.
Sent from my LGUS375 using Tapatalk
Click to expand...
Click to collapse
I've been trying to root my k8 (k350n) - european version the last few weeks... so far i got:
(here i try to post a url i can't yet... you can find my topic on chinaphonearena - i describe everything there - search "lg k8 k350n twrp" on google - it will be the second result)
the twrp boots but i'm afraid it's not a perfect port so it migth not handling the partitions well... i mean when i try to install supersu i think it cannot find the boot.img (it seems to find but can't patch it).
The newest supersu supposed to patch the boot.img automatically so i believe the only thing we should manage to get a working twrp...
if you want to try i have to warn you that sometimes when i mess with the twrp i have to make a hard reset the get my phone working again. When you boot to the twrp it asks if you want to make your system writeable - you don't have to do that in order to install supersu - however if you allow twrp to make your system writeable you might lose data (i only lost data if i did a format in the twrp but only writeability doesnt clear data in my case...)
edit1:
so i found that supersu can only patch boot images compress by "gzip". The boot im. of our k8 is compress using "lz4" method. I also realized that my twrp works so far as the supersu tries to decompress the boot image... so
We either wait till supersu deals with lz4 or if we could somehow take (dump to pc) the boot image in fastboot "re"compress to gzip - flash back to the device - restart twrp (not boot to android yet - which obviously would not work), install supersu - restart to fastboot take the boot image "re"compress to lz4 and flash the patched boot.img back to the device.
well it's just an idea which actually stucks at dumping the image without root and who knows what other reasons...
or if we knew what tweaks needs to be done to the boot image and we could just make it on pc and flash it in fastboot (i have the stock boot image - i have the whole firmware actually)...
Any advice would be appriciated
Here we go guys...
http://forum.xda-developers.com/lg-k10/how-to/twrp-root-lg-k8-k350n-t3475807
I actually had to return it. It was brand new in the box but the imei was linked to a delinquent account and I couldnt activate it. I'm subscribed if anything.
Hello guys,
I have a problem with my OnePlus X, and it would be lovely if I could get some help or advice from you guys.
> To provide some slight background, I purchased this off of eBay to complete my OnePlus collection. Most listings were above what OnePlus originally sold the phone for, but I found one for $125 in good condition by a seller with a good rating. It was advertised as soft-bricked, with Fastboot in working order. I thought "no problem, I'll just reflash it and be on my merry way."
Now onto the issue. I received it, charged it up, and attempted flashing the official recovery provided by OnePlus, but something is not working. I've been tinkering with Android for a number of years now, so I troubleshooted as much as I could, but to no avail.
1. Starting with device unplugged and powered off, boot into fastboot
2. Plugged into the computer, and ran `fastboot devices` to ensure it's recognized. After that, I flashed the recovery.img that was on my desktop with `fastboot flash recovery recovery.img` (yes I was in the correct directory). It looked successful. Picture of cmd response text at the following imgur album: /a/25DEQ (sorry I cannot post full links yet, had to create a new xda profile, forgot my old one :/
3. Unplugged the phone, powered off, Volume Down + Power to attempt boot into recovery. Failure. It just turns on with the 1+ logo, and quickly flashes the 'android' logo at the bottom. It stays like this until I manually power off.
I'm a bit stumped I have to admit. I would greatly appreciate any input you folks have. Thank you.
AndriyEtch said:
Hello guys,
I have a problem with my OnePlus X, and it would be lovely if I could get some help or advice from you guys.
> To provide some slight background, I purchased this off of eBay to complete my OnePlus collection. Most listings were above what OnePlus originally sold the phone for, but I found one for $125 in good condition by a seller with a good rating. It was advertised as soft-bricked, with Fastboot in working order. I thought "no problem, I'll just reflash it and be on my merry way."
Now onto the issue. I received it, charged it up, and attempted flashing the official recovery provided by OnePlus, but something is not working. I've been tinkering with Android for a number of years now, so I troubleshooted as much as I could, but to no avail.
1. Starting with device unplugged and powered off, boot into fastboot
2. Plugged into the computer, and ran `fastboot devices` to ensure it's recognized. After that, I flashed the recovery.img that was on my desktop with `fastboot flash recovery recovery.img` (yes I was in the correct directory). It looked successful. Picture of cmd response text at the following imgur album: /a/25DEQ (sorry I cannot post full links yet, had to create a new xda profile, forgot my old one :/
3. Unplugged the phone, powered off, Volume Down + Power to attempt boot into recovery. Failure. It just turns on with the 1+ logo, and quickly flashes the 'android' logo at the bottom. It stays like this until I manually power off.
I'm a bit stumped I have to admit. I would greatly appreciate any input you folks have. Thank you.
Click to expand...
Click to collapse
Which recovery u tried? Did u knOw the previous os version details?
And try this after flashing recovery in fastboot, boot into it directly by giving a cmd "fastboot boot recovery.img"
cva_kabil said:
Which recovery u tried? Did u knOw the previous os version details?
And try this after flashing recovery in fastboot, boot into it directly by giving a cmd "fastboot boot recovery.img"
Click to expand...
Click to collapse
Hi! Thank you for your reply
I posted this same question on the /r/oneplus subreddit, and received a quick and helpful walkthrough. Turns out part of the problem was that the micro-usb port on the phone itself is a bit unreliable. I haven't investigated too deeply, but it took a while to find a position for the wire to maintain a stable connection. I suspect this may be why the device was bricked in the first place (disconnect when flashing rom/kernel/etc.)
Anyways, for some reason flashing the stock recovery to the phone was just not working. The guy on reddit recommended trying TWRP, and that worked immediately. However, at that point, I had no idea what the history of the phone was or what OS was on it before, what firmware it had. I tried installing the official CM13 and then Sultan's CM13 with no luck. What *did* work was Oxygen OS 2.2.6.
At this point I'm stuck yet again though... The Marshmallow OTA (3.1.3) in the OS shows as available for download, but when I try to install the download only gets to 22% and then stops. Flashing the 3.1.3 OTA.zip available on OnePlus' support site doesn't work in TWRP, and when I try to flash stock recovery, it doesn't work.. don't know what else to try.
AndriyEtch said:
Hi! Thank you for your reply
I posted this same question on the /r/oneplus subreddit, and received a quick and helpful walkthrough. Turns out part of the problem was that the micro-usb port on the phone itself is a bit unreliable. I haven't investigated too deeply, but it took a while to find a position for the wire to maintain a stable connection. I suspect this may be why the device was bricked in the first place (disconnect when flashing rom/kernel/etc.)
Anyways, for some reason flashing the stock recovery to the phone was just not working. The guy on reddit recommended trying TWRP, and that worked immediately. However, at that point, I had no idea what the history of the phone was or what OS was on it before, what firmware it had. I tried installing the official CM13 and then Sultan's CM13 with no luck. What *did* work was Oxygen OS 2.2.6.
At this point I'm stuck yet again though... The Marshmallow OTA (3.1.3) in the OS shows as available for download, but when I try to install the download only gets to 22% and then stops. Flashing the 3.1.3 OTA.zip available on OnePlus' support site doesn't work in TWRP, and when I try to flash stock recovery, it doesn't work.. don't know what else to try.
Click to expand...
Click to collapse
Root your device using twrp or kingoroot method then install flashify and try to flash stock recovery using flashify. .. Tht may work.
Flashing 3.1.3 via official twrp ll not work... Cos ur bootloader version, U can do it only with stock recovery or u need to edit meta data file. Or u can flash stock recovery img file by twrp
cva_kabil said:
Root your device using twrp or kingoroot method then install flashify and try to flash stock recovery using flashify. .. Tht may work.
Flashing 3.1.3 via official twrp ll not work... Cos ur bootloader version, U can do it only with stock recovery or u need to edit meta data file. Or u can flash stock recovery img file by twrp
Click to expand...
Click to collapse
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
AndriyEtch said:
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
Click to expand...
Click to collapse
I dont think so... I hv not tried... But as of i know if u edit it wrongly, u will not be able to flash that file. . Try others methods first... Hope it works
AndriyEtch said:
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
Click to expand...
Click to collapse
Hi OP, sorry for joining late to the party
So the thing is the OnePlus X is at opposites now since the official MM release on 29th September. The thing is if you are running the old bootloader (OxygenOS 2.x.x) or any ROM based on it, then the New TWRP will not boot, neither will the Stock Recovery that is hosted on the OnePlus download section for the X, which is where i assume you download the stock recovery from, right ? Also note that the official recovery hosted on the TWRP website is also yet to be updated, we're working on that.
So you are on the old Bootloader. Simple stuff. I have posted my guide a lot of time around the forums, its gained a lot of merit. You could follow it for your update process. I'll leave a link below. In case you wanna verify that the old bootloader is causing the issue my Index Thread pinned in the general section has a link for the Stock recovery for Old bootloader, try flashing that via fastboot, if it successfully boots then you're set.
Comprehensive guide to Update to Marshmallow Bootloader
The above guide is centered to the thread i have posted it on but the process is 99% the same. In the end, you could just stay with Oxygen OS 3.1.3, or flash any custom ROM based on the new Bootloader.
Now regarding your query about editing the META of the ROM, well Yes to an extent it IS risky if you ain't careful because my guide guides you to delete the one single line that removes the device check, so as long as you use the modified zip on OnePlus X only, there will be no issues.
Let me know for any further clarifications, also you're welcome to join our support group on Telegram, all of our developers are active there. Ping me (@ mellogang_unite) for an invite
The phone allows you to enable bootloader unlocking in the developer options. So, I was wondering what command is needed to enable it?
I have no clue, I've been searching high and low, trying to figure out a way to root this device and I've hit a wall at every turn. Any help would be appreciated
Zte firmware needed
If someone can find the zte firmware/stock rom i can install magisk into it untill someone can build a twrp recovery for it
---------- Post added at 01:50 AM ---------- Previous post was at 01:49 AM ----------
If someone finds the firmware i can root it untill someone can build twrp for it
uni-android unlock tool will unlock bootloader so you can root the n9137 and many other devices... it cost 50 bucks and its good for a year of unlimited unlocking. GOOD LUCK!
Any progress on this front? I have a ZTE Tempo X N9137 HW1.0 from Assurance Wireless (Free Gov't phone).
I Just want to root this phone, so I can run rooted apps. I am not interested in installing other ROMs (I am not sure, but my feeling is that I have to leave the original ROM alone in order for this phone to continue to work w Assurance Wireless under the gov't lifeline free cell program - someone correct me if I am wrong and it is confirmed that I can actually ROM better ROMs into this ZTE and continue to work normally with Assurance Wireless.)
Do I need to install TWRP or CWM in order to root the ZTE, or can I use ADB and Fastboot to unlock the bootloader and install Magisk or SuperSU to allow root?
I googled around, but I can't find TWRP or CWM for the ZTE N9137.
Any help or link to guides specifically for the ZTE Tempo X N9137 is greatly welcomed and needed,
Thanks
What is needed?
I have this phone as well. You still need the firmware? DO you need the version or the actual firmware file?
SP6RK said:
If someone can find the zte firmware/stock rom i can install magisk into it untill someone can build a twrp recovery for it
---------- Post added at 01:50 AM ---------- Previous post was at 01:49 AM ----------
If someone finds the firmware i can root it untill someone can build twrp for it
Click to expand...
Click to collapse
Root ZTE Tempo X N9137 Assurance Phone
sketchscarz said:
I have this phone as well. You still need the firmware? DO you need the version or the actual firmware file?
Click to expand...
Click to collapse
Any luck rooting this phone using KingRoot?
Has the Bootloader been unlocked yet?
If I ever get this phone rooted,. will I be able to replace the ROM?what will happen to the Assurance portion of it? WIll it still work as a free gov't phone, or does it need to have the Assurance software to work as the free government phone?
I need to root this phone so I can run rooted app to expand the very limited built in storage space. I cannot install any new app because there is no more storage space. The solution is to allow App2SD or other app that install apps into the SD card, but this requires root access.'
any help greatly appreciated
Hey guys - I good news to report. I successfully rooted my ZTE X N9137. Running Android 7.1.1 build version N9137V1.0.0B08 which is the most current. My phone came with a Sprint SIM and the phone service is Q-Link I have screenshots of the installed root apps I used and also all the bloatware removed gone from the Apps Drawer. I rooted using KingRoot but not via the apk. I am working on a guide and also going to recreate to verify the steps. I used the combo of scripts that I found from site that I linked below. The requires an account to download but it's free. A couple of things I discovered
Start with the phone in EDL Mode:
The phone needs to be in EDL mode (blank screen but is still powered on).
from adb run this command
adb reboot edl
Or run the edl.bat from the /root/ folder
Root / Unlock
Script used was : Unlock ZTE-N9137_1_DEVICE.bat
The script requires many reboots and it was after UNLOCKING PHONE STEP 3 is when Kingroot was installed.
This is when I debloated . During this step my wifi was inaccessible (firmware mismatch I suspect)
The script then performed another reboot and I lost root and recovery is non accessible
Mirror of the script package:
https://www.filehosting.org/file/de...ucion de Desbloqueo 100% TESTED Halabtech.rar
Original script package:
https://support.halabtech.com/index.php?a=downloads&b=folder&id=33472
Stock Firmware Site:
https://combinefile.com/index.php?a=downloads&b=folder&id=15471
I was able to download one from their site before having to pay money. YMMV
https://drive.google.com/drive/folders/1GhQof56lwMZvAsk25J-ONo-DEesXliQ3
This guy has an older version: N9137V1.0.0B04
How to flash ZTE roms:
https://www.leakite.com/how-to-flash-zte-stock-rom-firmware-via/
Service Mode - Enter this dial:
*983*0#
Here are screenshots of my ZTE N9137 without all the bloat! "Kingroot - Remove Bloatware" removed
40 pre-installed apps which most were installed as a service which requires to root to remove.
Everything runs some much smoother now.
Based on the overwhelming response with my previous posts, I am continuing ahead. I was again successful at getting root. Attached a couple of pics.
Since I have been unable to unlock the bootloader, the process is only temp
Unlock hotspot, add to APN internet.. APN type default,dun,mms,hipri. Use by4 setting editor to unlock hotspot
Link to mirror of the script is broken. Anyone have a copy? I have found a copy of the script. I can confirm it works. If anyone needs it let me know
I have ordered one of these phones, in the meantime here is the N9137 Firehose and support files (rawprogram0.xml and patch0.xml)
https://www.androidfilehost.com/?fid=1395089523397897020
QFIL flashable V1.0.0B23 Sprint/Boost Firmware
https://www.androidfilehost.com/?fid=1395089523397897018
A guide to flash the firmware (Replace the firmware in the guide with the one above) and individual images.
https://forum.xda-developers.com/maven-3/how-to/how-to-return-to-stock-flash-images-qpst-t3901510
Nice to see things advancing. Any progress with TWRP yet? Looks like you've been working on it based on your GitHub deadman...
Help Rooting ZTE N9137
Hi! I'm kind of a newb at the rooting process so I was hoping someone had a guide on how to root this phone. My version of this phone is from Qlink Wireless with a Sprint SIM installed. Thank you in advance!
Flashing always faults out with a read error once it gets to carrier.img. Any ideas?
CivicObligation said:
Flashing always faults out with a read error once it gets to carrier.img. Any ideas?
Click to expand...
Click to collapse
That happens when the img is 0 bytes, remove any of the imgs that are 0bytes from the rawprogram0.xml. Then restart your device to edl again and restart your flashing program and try again.
deadman96385 said:
That happens when the img is 0 bytes, remove any of the imgs that are 0bytes from the rawprogram0.xml. Then restart your device to edl again and restart your flashing program and try again.
Click to expand...
Click to collapse
Thank you! Seems so obvious after you explained. Any suggestions or advice on FH loader errors? The log says my device is not on the current port once it tries to actually write to the device.
deadman96385 said:
I have ordered one of these phones, in the meantime here is the N9137 Firehose and support files (rawprogram0.xml and patch0.xml)
https://www.androidfilehost.com/?fid=1395089523397897020
QFIL flashable V1.0.0B23 Sprint/Boost Firmware
https://www.androidfilehost.com/?fid=1395089523397897018
A guide to flash the firmware (Replace the firmware in the guide with the one above) and individual images.
https://forum.xda-developers.com/maven-3/how-to/how-to-return-to-stock-flash-images-qpst-t3901510
Click to expand...
Click to collapse
Can you confirm if this technique will network-unlock an N9137 linked to Assurance Wireless? Or is this not possible yet?
Thank you
---------- Post added at 11:46 PM ---------- Previous post was at 11:10 PM ----------
n2locarz said:
Root / Unlock
Script used was : Unlock ZTE-N9137_1_DEVICE.bat
The script requires many reboots and it was after UNLOCKING PHONE STEP 3 is when Kingroot was installed.
This is when I debloated . During this step my wifi was inaccessible (firmware mismatch I suspect)
The script then performed another reboot and I lost root and recovery is non accessible
Mirror of the script package:
filehosting.org link
Original script package:
hablatech.com link
Click to expand...
Click to collapse
Both of the above links don't work. The filehosting.org link is broken or dead and the hablatech.com download is behind a paywall, even if you create a free account on their site.
Does anyone have a link to this script? Also if successful, will this approach network-unlock my phone?
PS. I'm not allowed to post links with a new account so I had to edit them out of the above quote. However you can find them in the original post.
Hello again,
I've proceeded to try Deadman's strategy to install the stock rom he provided. I've implemented the fix to remove references to empty '.img' files in the rawprogram0.xml. The helper files and the rom have been unzipped to the same folder, such that Deadman's rawprogram0.xml and patch0.xml have overwritten those provided in the firmware image folder, which I believe is the correct method.
When I reboot my phone into EDL mode using adb, the QFIL application recognizes the phone as "Qualcomm HS-USB QDLoader 9008 (COM6)" and I can begin the flash.
However, the flashing hangs or stops when it reaches the following stage:
Code:
2019-04-15 12:42:34.015 12:42:33: INFO: {percent files transferred 2.78%}
2019-04-15 12:42:34.016 12:42:33: INFO: In handleProgram('recovery.img')
2019-04-15 12:42:34.016 12:42:33: INFO: Looking for file 'recovery.img'
2019-04-15 12:42:34.017 12:42:33: INFO: =======================================================
So it appears that there is an issue with the recovery.img file. However this file is both present in the same folder and non-empty. What could be the issue here?
Cheers.
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1......
Click to expand...
Click to collapse
This specific device and Chipset is fairly new and there's very little on the forum that's specific to your device.
With that stated...
You have a Mediatek MT6739 (64 Bit) device that can be very helpful in that aspect.
Though I had located a few threads that won't be very helpful for you but, the following thread is about the best that your possibly going to find for your device at this point in time.
https://forum.xda-developers.com/showthread.php?t=2701283
It does take some time for developments to pop up on the forum for newer Mediatek Chipsets but, where there's a developer (with the same Chipset device), there's always a way depending on the level of difficulty.
I wish you the best of luck with your search!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Click to expand...
Click to collapse
I'm also looking for that. But if I can get TWRP on it I'd probably try SU.
How did you get to install the TWRP? I found a few posts but was apprehensive about whether I can use SPFT to flash original stock ROM if things go wrong. I suppose that would be the easiest way.
For what I paid for the phone, it's a decent enough device.
Using SD card as internal memory always result in the total capacity being reported wrongly..256GB becomes 512GB with 50% occupied, 200GB becomes 256GB with 64GB occupied. Still waiting for their tech support to reply but unlikely they would.
Cheers!
I have rooted it several times and flashed the stock image several times too without a problem. Haven't used SU though I used Magisk.
.stupdroid.com/2018/07/Ulefone-Armor-X-root-twrp-.html
I do not have your issue with storage but my wireless charging mat today stopped charging but still lights up. Phone will still charge via cable. Trying to get a replacement mat.
I installed using SP flash tools on windows and Linux just to see the difference.
If you do a Google for Install TWRP ulefone armor x then you will get some information and relevant files.
Unlocking the bootloader via ADB is straightforward on Windows and Linux too. And then relocking it.
Regards
Charlie
Ibuprophen said:
This specific device and Chipset is fairly new and there's very little on the forum that's specific to your device.
With that stated...
You have a Mediatek MT6739 (64 Bit) device that can be very helpful in that aspect.
Though I had located a few threads that won't be very helpful for you but, the following thread is about the best that your possibly going to find for your device at this point in time.
https://forum.xda-developers.com/showthread.php?t=2701283
It does take some time for developments to pop up on the forum for newer Mediatek Chipsets but, where there's a developer (with the same Chipset device), there's always a way depending on the level of difficulty.
I wish you the best of luck with your search!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
Thanks for the input I will have a read.
Charlie-Boy said:
I have rooted it several times and flashed the stock image several times too without a problem. Haven't used SU though I used Magisk.
.stupdroid.com/2018/07/Ulefone-Armor-X-root-twrp-.html
I do not have your issue with storage but my wireless charging mat today stopped charging but still lights up. Phone will still charge via cable. Trying to get a replacement mat.
I installed using SP flash tools on windows and Linux just to see the difference.
If you do a Google for Install TWRP ulefone armor x then you will get some information and relevant files.
Unlocking the bootloader via ADB is straightforward on Windows and Linux too. And then relocking it.
Regards
Charlie
Click to expand...
Click to collapse
Thanks for the info.
Cheers!
chooks06 said:
Thanks for the info.
Cheers!
Click to expand...
Click to collapse
No problem.
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Click to expand...
Click to collapse
Where did you get the TWRP for Ulefone Armor X. I've been trying to search it all over and haven't found anything. If possible can you please share a link? TIA
abhijeet715 said:
Where did you get the TWRP for Ulefone Armor X. I've been trying to search it all over and haven't found anything. If possible can you please share a link? TIA
Click to expand...
Click to collapse
Code:
https://www.needrom.com/download/twrp-armox-x/
There are other places listed on Google.
Anyone had this in recovery mode?
Had also tried flashing the TWRP but it just didn't stick and was asking for a password on first launch.
Edit.. all links I tried point to the same location to download. Same files.
chooks06 said:
Anyone had this in recovery mode?
Had also tried flashing the TWRP but it just didn't stick and was asking for a password on first launch.
Edit.. all links I tried point to the same location to download. Same files.
Click to expand...
Click to collapse
im also facing the same issue... kindly someone help.. ive explained my issue below:
Can someone confirm? My device is encrypted by default, so whenever i install TWRP it says to decrypt device. I tried the pattern, changed it to password, and pin still my device doesnt decrypt in twrp. I feel its a twrp bug, because when i set the device to ask pattern during boot, the same pattern/pin/password is accepted, but not in twrp.
I want to know 3 things:
1. Are your devices encrypted by default (i dont remember encrypting my device, I dont know how it is encrypted)
2. Are you facing this same issue of entering password when you reboot into recovery?
3. What is the purpose of the boot.img in the twrp zip? am i required to flash it before flashing the recovery, or does it remove encryption?
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Click to expand...
Click to collapse
Charlie, could share how you got the TWRP working?
Have been fiddling around until battery showed -1%.. Had to go back to stock.
Thanks mate!
Choo ks
In the folder containing the TWRP recovery there are 3 files, boot.img, scatter, and recovery. You only flash recovery, you have flashed the boot image, ensure the checkbox is unticked after loading from scatter in SP tools. That is what I think you have done to get that result.
Follow the guide here. I did it a few times before success as I followed a guide from another site.
https://www.stupdroid.com/2018/07/Ulefone-Armor-X-root-twrp-.html
Click to expand...
Click to collapse
I think I installed magisk using this method, clearing dalvik and cache.
https://www.stupdroid.com/2018/02/magisk-16.0-download.html
Click to expand...
Click to collapse
Charlie-Boy said:
In the folder containing the TWRP recovery there are 3 files, boot.img, scatter, and recovery. You only flash recovery, you have flashed the boot image, ensure the checkbox is unticked after loading from scatter in SP tools. That is what I think you have done to get that result.
Click to expand...
Click to collapse
That's what I did, using the downloaded scatter file. Was experimenting.
---------- Post added at 06:49 PM ---------- Previous post was at 06:44 PM ----------
Charlie-Boy said:
Follow the guide here. I did it a few times before success as I followed a guide from another site.
I think I installed magisk using this method, clearing dalvik and cache.
Click to expand...
Click to collapse
Used the same guide. But TWRP came up with the decrypt data issue.
Did you have that issue?
chooks06 said:
Anyone had this in recovery mode?
Had also tried flashing the TWRP but it just didn't stick and was asking for a password on first launch.
Edit.. all links I tried point to the same location to download. Same files.
Click to expand...
Click to collapse
You ignore the password and change the language to English from Russian. Just don't enter a password at all. The recovery won't stick as Android replaces it when you reboot. After you've completed other steps maybe OEM unlocking then it stays, or so I read somewhere.
chooks06 said:
That's what I did, using the downloaded scatter file. Was experimenting.
---------- Post added at 06:49 PM ---------- Previous post was at 06:44 PM ----------
Used the same guide. But TWRP came up with the decrypt data issue.
Did you have that issue?
Click to expand...
Click to collapse
All of them are encrypted by default now. The password in TWRP should be ignored and just change the language and select storage etc.
abhijeet715 said:
im also facing the same issue... kindly someone help.. ive explained my issue below:
Can someone confirm? My device is encrypted by default, so whenever i install TWRP it says to decrypt device. I tried the pattern, changed it to password, and pin still my device doesnt decrypt in twrp. I feel its a twrp bug, because when i set the device to ask pattern during boot, the same pattern/pin/password is accepted, but not in twrp.
I want to know 3 things:
1. Are your devices encrypted by default (i dont remember encrypting my device, I dont know how it is encrypted)
2. Are you facing this same issue of entering password when you reboot into recovery?
3. What is the purpose of the boot.img in the twrp zip? am i required to flash it before flashing the recovery, or does it remove encryption?
Click to expand...
Click to collapse
Yes all are encrypted.
Yes I get the same request for password which I ignored and selected language and carried on.
I do not know why boot.img is included it just gets in the way.
After installing TWRP unlocking OEM bootloader and all the rest including rooting it I decided it would be better to wait for a new ROM. All we need is a working TWRP and an unlocked bootloader to flash a new ROM and we have that. It doesn't work very smoothly and I felt it could be better which is why I went back to stock.
When I posted this request I didn't imagine others would try installing Magisk etc, waste of time really as you won't stay with it either. Best wait for a ROM I think.
Charlie-Boy said:
Yes all are encrypted.
Yes I get the same request for password which I ignored and selected language and carried on.
I do not know why boot.img is included it just gets in the way.
After installing TWRP unlocking OEM bootloader and all the rest including rooting it I decided it would be better to wait for a new ROM. All we need is a working TWRP and an unlocked bootloader to flash a new ROM and we have that. It doesn't work very smoothly and I felt it could be better which is why I went back to stock.
When I posted this request I didn't imagine others would try installing Magisk etc, waste of time really as you won't stay with it either. Best wait for a ROM I think.
Click to expand...
Click to collapse
Im also unlocked and flashed twrp. I ignored the encryption message and proceeded, hit the storage sizes show 0, and neither can i access the storage to flash anything nor can i take backups. can you go to settings>security in your device, and tell me if your encryption says enabled? Tia
abhijeet715 said:
Im also unlocked and flashed twrp. I ignored the encryption message and proceeded, hit the storage sizes show 0, and neither can i access the storage to flash anything nor can i take backups. can you go to settings>security in your device, and tell me if your encryption says enabled? Tia
Click to expand...
Click to collapse
Mine is the same encryption is enabled. I select external SD storage and I am shown the contents using the same procedure as yourself, I cannot tell you why this is so. I am using the same technique, same phone, same settings, same TWRP, maybe we have different SD card?
That is all I can think of by way of an explanation. It works perfectly for me. I also made a backup which I can select and restore without a problem.
Credit to @user_ScoTTT
1. First of all, you need to sign up and login on the official website of Oppo in China. (Use Google Translate if you need to)
https://bbs.coloros.net/graphic?id=1498611
2. Follow the links and download the unlock program of Oppo Find x2 /x2 pro
3. Install the apk on your phone
4. Ensure your device has the latest version of your ROM installed.
5. Click "Start Applying" on the Unlock App. You will need to wait about a month. After a month, open the application, and if "Approved" is displayed, please go to the next step.
If not, Force Close the Application several times over and over, and maybe it will display "Approved".(Some Chinese citizens reported a similar situation.)If you still can't, please contact oppo online customer service, they can solve this problem for you.
6. Next, please back up your data.
7. After receiving the 'Approval' in the app.
Go to Settings - about mobile phone - version information - version number Click here five times.
Go to settings - other settings - Developer options then Check OEM unlock.
8. Once again, open the Deep Test application and click "Start the Depth Test". The phone will automatically restart and enter Bootloader mode.
9. Connect your phone to the computer.
10. Open the command prompt browse to your adb/fastboot location and enter
"fastboot flashing unlock"
then confirm. At this time, the mobile phone will give some warning information. Please read it carefully before making a decision.
If you decide, choose "unlock the bootloader" and press the power key to restart. It is worth noting that the phone will be formatted here. If you have opened "find my phone" before, you need to enter your oppo account password to start your phone.
11. You now setup your phone as normal though with an unlocked bootloader.
12. If you wish to Root then please see this guide: https://forum.xda-developers.com/find-x2-pro/how-to/magisk-root-install-unlocked-bootloader-t4157327
can i flash global rom after unlocked bootloader ?
i was wondering the same thing. i dont see why not. give it a shot and let us know. you have nothing to lose it will simply not let you flash if it doesnt work and your existing ROM/Phone will be unaffected.
Ok, so I've unlocked my Chinese Find X2 Pro using the official method, which is by using the depth testing app and waiting for approval, then unlocking via Fastboot.
But I still can't flash the global ROM using the stock ColorOS recovery. I've tried various versions, just either get the 'Installation failed' or 'The installed version is lower than current' error.
Do I need to wait until TWRP is available for the X2 Pro or is there another way? I don't want to root, just install the stock ROM from another region. Will Magisk allow me to do this?
Was really hoping unlocking the bootloader would do it, guess it's a good start
bugger.. it would appear that the ColorOS Recovery is preventing the install. So yes you would need TWRP or someone to hack the ColorOS recovery to flash without the check.
though with an unlocked bootloader you can flash TWRP as soon as it's been developed by someone.. or risk flashing a twrp from a similiar phone?
Bugger indeed, I've bricked it! Tried various ways to do it as really need to get rid of this Chinese ROM. I flashed a Boot image from a global version, didn't work. Then flashed the Chinese version back.
So then in a bold (stupid) move I tried to flash other images from the global ROM - now won't load into recovery at all. With nothing to lose I tried loading TWRP recovery from one of the latest Realme phones this morning, didn't fix it.
What is weird is in Oppo / Realme ROMs there is no recovery image - not sure if it's part of the boot image?
Does anyone know how to obtain a recovery image? I think this is what I'm missing. Thinking maybe it's not part of the ROM on these devices.
---------- Post added at 04:27 PM ---------- Previous post was at 04:22 PM ----------
And FYI, I've been using a python tool to decrypt the ozip files. Have looked in multiple ROMs, beta and standard, Chinese and global and even a few Realme ROMs.
I'm starting to hate Oppo, it's even more of a pain in the ass than Samsung! :silly:
I bought a Xiaomi Mi Mix 3 5G yesterday off eBay just to get me by for the time being, it was a carrier version and I managed to get the stock global ROM with MI12 on it in 30 minutes using fastboot and flashing all the images. Refreshingly easy
klanbo78 said:
Bugger indeed, I've bricked it! Tried various ways to do it as really need to get rid of this Chinese ROM. I flashed a Boot image from a global version, didn't work. Then flashed the Chinese version back.
So then in a bold (stupid) move I tried to flash other images from the global ROM - now won't load into recovery at all. With nothing to lose I tried loading TWRP recovery from one of the latest Realme phones this morning, didn't fix it.
What is weird is in Oppo / Realme ROMs there is no recovery image - not sure if it's part of the boot image?
Does anyone know how to obtain a recovery image? I think this is what I'm missing. Thinking maybe it's not part of the ROM on these devices.
---------- Post added at 04:27 PM ---------- Previous post was at 04:22 PM ----------
What method were you using to flash mate?
I had a look at the extract of the Global ROM and can see a heap of img files.. though your right there is no obvious Recovery image file.
That is strange. As the device has a Recovery mode. It would be very strange to make it part of the Boot Image. Surely Oppo has a recover tool that just puts everything back to default?
Click to expand...
Click to collapse
Sage said:
What method were you using to flash mate?
Click to expand...
Click to collapse
Just using the adb toools via command prompt on my PC and phone on fastboot mode.
I.e. fastboot flash boot boot.img
There's no system image either, only vbmeta_system.img which I don't think it's the same thing. Watching YouTube videos and searching the internet now to try and figure out
Finally managed to get the phone back up and running after brushing up on Linux and downloading various tools. Basically this thread saved me!! https://forum.xda-developers.com/realme-x50-pro/help/stock-recovery-image-t4111477/page6
As mentioned, the recovery image is not to be found in the firmware. So once you decrypt the Ozip file (using python tool like the one in the above post), you'll see the boot.img file along with various others, but no system, vendor or recovery images. Using the UR-Tool mentioned and a simple linux command I managed to create a recovery image.
Flased it using fastboot and now all working - still on Chinese ROM though. Next step is to try to flash the global image onto this Chinese variant - expect I'll brick it again
klanbo78 said:
Finally managed to get the phone back up and running after brushing up on Linux and downloading various tools. Basically this thread saved me!! https://forum.xda-developers.com/realme-x50-pro/help/stock-recovery-image-t4111477/page6
As mentioned, the recovery image is not to be found in the firmware. So once you decrypt the Ozip file (using python tool like the one in the above post), you'll see the boot.img file along with various others, but no system, vendor or recovery images. Using the UR-Tool mentioned and a simple linux command I managed to create a recovery image.
Flased it using fastboot and now all working - still on Chinese ROM though. Next step is to try to flash the global image onto this Chinese variant - expect I'll brick it again
Click to expand...
Click to collapse
Impressive mate well done! And thanks for posting the solution! With a recovery.img file you are now free to experiment! I hope you get the Global Working! Please keep us up to date!
Can you upload the recovery.img to help the community?
Sage said:
Impressive mate well done! And thanks for posting the solution! With a recovery.img file you are now free to experiment! I hope you get the Global Working! Please keep us up to date!
Can you upload the recovery.img to help the community?
Click to expand...
Click to collapse
You will be the first person in the world to have an unlocked bootloader on the Global ROM!
surely with some combination of Global and Chinese it will work!
Chinese Recovery -> Global Boot -> Global ROM -> Chinese Vendor
Global Recovery -> Global Boot -> Global System -> Chinese Vendor
Chinese Recovery -> Chinese Boot -> Global System -> Global Vendor
etc
etc
Sage said:
You will be the first person in the world to have an unlocked bootloader on the Global ROM!
surely with some combination of Global and Chinese it will work!
Chinese Recovery -> Global Boot -> Global ROM -> Chinese Vendor
Global Recovery -> Global Boot -> Global System -> Chinese Vendor
Chinese Recovery -> Chinese Boot -> Global System -> Global Vendor
etc
etc
Click to expand...
Click to collapse
Thanks for your support
I'll upload the recovery images for the global and Chinese variants once I'm back on my desktop later.
So the issue I'm facing now is it this phone doesn't have a system, vendor or product partition. My assumption is that I need to flash the global system image, as that's the one that basically contains the OS.
I think that these images are contained within the "super" partition which appears to be a dynamically resizable partition. I have no idea how to flash to these!
I'm trying to make sense of it all but fastbootd has come up a few times, which apparently is needed to flash to userspace which is where this super partition resides.
I can see in the ROM there is an updater script file that refers to these images, create groups in the super partition and resizes them as necessary. It seems to use the vb_meta_system image in some way. I have no idea how to replicate this script in fastboot though or if it's even possible?
Can anyone help?
---------- Post added at 08:59 AM ---------- Previous post was at 08:46 AM ----------
A bit of info on dynamic partitions...
https://source.android.com/devices/tech/ota/dynamic_partitions/implement
vbmeta.img removes the boot verification so you definitely want to use that. see this thread for its use.
https://forum.xda-developers.com/find-x2-pro/how-to/magisk-root-install-unlocked-bootloader-t4157327
I downloaded the depth testing app but the submit application is greyed out. Any tips on what to do?
golemagg said:
I downloaded the depth testing app but the submit application is greyed out. Any tips on what to do?
Click to expand...
Click to collapse
I know they have a monthly quota, perhaps it's been reached this month.
Or maybe the servers are down? there were a few days during my application that I couldn't check the status, just assumed the server was offline - perhaps it's something like that.
Maybe just wait a few days and see.
Where is you download the app from? And do you have the Chinese variant?
klanbo78 said:
I know they have a monthly quota, perhaps it's been reached this month.
Or maybe the servers are down? there were a few days during my application that I couldn't check the status, just assumed the server was offline or something like that - perhaps it's something like that.
Maybe just wait a few days and see.
Where is you download the app from? And do you have the Chinese variant?
Click to expand...
Click to collapse
Understood. I'll keep monitoring it. Thanks a lot for the information.
klanbo78 said:
Finally managed to get the phone back up and running after brushing up on Linux and downloading various tools. Basically this thread saved me!! https://forum.xda-developers.com/realme-x50-pro/help/stock-recovery-image-t4111477/page6
As mentioned, the recovery image is not to be found in the firmware. So once you decrypt the Ozip file (using python tool like the one in the above post), you'll see the boot.img file along with various others, but no system, vendor or recovery images. Using the UR-Tool mentioned and a simple linux command I managed to create a recovery image.
Flased it using fastboot and now all working - still on Chinese ROM though. Next step is to try to flash the global image onto this Chinese variant - expect I'll brick it again
Click to expand...
Click to collapse
Can you please upload the recovery.img for people to use?
any other progress to report?
Sage said:
Can you please upload the recovery.img for people to use?
any other progress to report?
Click to expand...
Click to collapse
Yeah, that would be really nice. I couldn't boot also in recovery after android 11 beta:silly:
Sage said:
Can you please upload the recovery.img for people to use?
any other progress to report?
Click to expand...
Click to collapse
Here's the link to the recovery (and boot) images, have zipped them as they're quite large. I've included both variants (so PDEM30 and CPH2025).
https://drive.google.com/drive/folders/1HkNeQSuzsPDdue4KqRbDWLah0YH-CSwb?usp=sharing
In terms of progress, there is none. I got a bit adventurous and decided to flash all of the partitons on my PDEM30 with the images from the CPH2025 (manaully as there is no "flash-all.bat" file in the OTA ROM). I think it would have worked as it has for phones I've flashed this way in the past, but as I now know phones that launced with Android 10 are quite different due to having a dynamic "super" partition. This super partition contains the system, product, vendor image, etc. It should not (can't be) be flashed from fastboot as it's held in the "user space" of the phone and fastboot doesn't know how to deal with these partition types.
Pixel devices have a program called fastbootd which I think can be used for this, but Oppo doesn't appear to have that mode. Basically the phone now won't boot to recovery at all, I can only get into fastboot mode.
Not even worth holding out for TWRP as as of right now, TWRP doesn't support these dynamic partions (so any phone launced with Android 10). I contacted Oppo UK support and they said I could send in for repair, but then got told by the company who would be doing the repair (SBE UK) that they only support UK and EU devices. So looks like it might be going back to China for a repair (just need to find a freind who speaks Chinese )
Before that though I'm going to see if I can edit the recovery.img in Android Kitchen, to see if I can find the bit that's responsible for it not booting into recovery mode. I think at this point I have nothing to lose!!
I can't download unlock program of Oppo Find x2 / x2 pro, can you help me download it, thanks