KW98 - twrp and rooting - Other SmartWatches

Hello,
I am using kingwear 98 (kw98)
https://www.smartwatchspecifications.com/Device/kingwear-kw98/
It's a smart watch based on MTK6580.
I am trying to understand what is the best method to install twrp on mediatek devices.
1. Is it by using the magic twrp installer ?
2. Or by manually porting twrp to our specific device , as seen in some tutorials here (porting twrp with same chipset into socket recovery)?
Well, actually I did try a 3rd option:[/B][/B]
3. I tried to use AllCall-W1_recovery recovery.img ( which has the same chipset).
https://mega.nz/#!kfgmmRRD!RcvPwf0Jc-BAwM4Sf9fYJrmF3DsTQTEYtE2LVeWyE10
Surprisingly it worked . Yet, after several days without issues, last week it became dead.
So, I don't understand how it worked in the first place (it is same chipset, but probably use totally different interface , and drivers ! ) , and if it became dead because something it might be wrong to put same recovery image of another device, without. proper porting.
So, should I flash same image (allcall W1 recovery) again on a new kw98 device that I will buy, or use one of the above methods (port twrp manually into my stock, or install magic twrp for mediatek).
Thank you,
ranran

Related

Kali NetHunter 3.0 on Nexus 7 (2013) - flo

Hello there !
After a long time of searching I wasn't able to find anywhere a proper guide to install Kali Nethunter on Nexus 7, mainly the lasted release of it (3.0) on newer androids (6.0+) or CM13, so I decided to make this quick guide to cover some aspects that it thought would be important if you wanna jump into this.
First things first:
Disclaimer: I AM NOT RESPONSIBLE FOR ANY LOST YOU HAVE, PLEASE REMEMBER TO ALWAYS BACKUP YOUR SENSITIVE INFORMATION AND PERSONAL DATA!
What is NetHunter: Kali nuthunter is based on Kali linux and has most of built-in tools to security audits and penetration testing. More information can be taken here: world wide web dot kali dot org/kali-linux-nethunter/
History: I've been trying to install nethunter on mu nexus 7 without succeed for the past 3 days. Last year I had already accomplished this task in another version of nethunter (1.2) and android (CM12). Recently, I decided to go back to security works and realize that offensive security have been working it's ass off and since than released a newer version, and I was already in stock Marshmallow (6.0.1) android, so downgrading wasn't an option for me.
I tried to install nethunter(Like in the past) with a tool called MultiRom (Available for free in PlayStore), that allows you to run multiple roms on your device (dual-boot feature like). But unfortunately I couldn't. I just couldn't and it was driving me crazy.
Got errors like:
Slow boot (on secondary rom - Nethunter)
Missing root (Supersu)
Freezing
So if you are facing this problems here is the solution I have to make it works.
Solution:
Install the last stock rom for your device (In my case, Nexus 7-flo that can be found at developers dot google dot com/android/nexus/images)
Then use fastboot to apply your stock rom (Attention: This step will format all your DATA!):
Code:
$ adb reboot bootloader
(Remember to enable USB DEBUG)
once in bootloader run:
Code:
./flash-all.sh
After flashing the stock rom, proceed to ROOT you device. (If you don't know how, you should not be messing with any of this, but if you want to anyways.... google it!)
Then, after rooting your device install busybox(for free in playStore)* and install its components.
Now, install a custom recovery (For this, I will use TWRP)
Go back to you bootloader screen with the comment before mentioned and run the following command:
Code:
fastboot flash recovery your_recovery.img
Then, copy the Nethunter file downloaded from world wide web dot offensive-security dot com/kali-linux-nethunter-download/[/url] to your device and flash it with the help of your recovery (TWRP or CM Recovery).
Luckily, if everything goes as expected you should succeed in installing nethunter 3.0 on your Nexus 7 device (May be applied to other Nexus devices)
Bottom Line: Try installing Nethunter on your stock rom, instead of a custom one. Then, if you want to, you always can install Multirom and install a secondary ROM like CM13 to be your daily use ROM.
Any Questions and suggestions are welcome, sorry in advance about any english mistake (Non-native speaker here!).
*: Optional Step, can be done later.
So your external card is detected? I wiped everything and reflashed about a gazillion times, all works fine except it simply won't detect my card. I guess I can try older Android version as i've only tried 6.0.1 so far... doubt that would do the trick though

Stock recovery extraced from BTV-W09C233B019 ROM - untested

Hi M3 users,
I'm a long time lurker and reader on XDA. Now it's time to give something back or at least participate
Following my recent M3 purchase a dugg a bit deeper into this topic and tried to get us the stock recovery for our devices.
I'm not really a dev. I just used the information I found here and in the russian forum where greatslon (thank you guy) is posting his work.
If you find an error in the process please let me know. The files have not been tested in any way. I have no idea if this would even work (encryption and so on).
So I managed to extract the recovery.img file from the chinese rom. This method will also work for the LTE variant.
Maybe @greatslon or @somboons can share their view on the topic or maybe @somboons can even use it in his tool.
Resources
http://4pda.ru/forum/index.php?showtopic=780572&st=120
http://forum.xda-developers.com/showthread.php?t=2433454
http://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder
Tools used
Huawei Firmware Finder (Team MT)
Huawei Update Extractor
Download
M3_BTV-W09C233B019_recovery.zip
Process
1. Start firmware finder (did use the android version)
2. Change device to BTV-W09C233
3. Downloaded the firmware B019 for BTV-W09C233 (no firmware for other variants present ATM)
4. Extracted and copied update.app to SD card
5. copy to PC
6. Extract recovery.img and recovery2.img using Huawei Update Extractor
Best regards,
Benjamin
Don't quite understand what's this for. First of all, recovery should be the same version as your ROM. I don't know if their mismatch will immediately lead to some malfunction, but some people on 4pda said they should match. Second - stock recovery's functions are limited to factory reset (wiping data, cache, etc.) and installing OTA updates. Without changing OEMINFO (and it's still unconfirmed), you won't be able to install any OTA except those, intented for your model and region, so again there's no need to install a higher version of recovery than your ROM is. But anyway, thank you for the extraction instruction.
P.S. I think there's no need to flash both recovery and recovery2. Recovery2 can be successfully replaced with TWRP and this combination is really great, cause you can launch TWRP by holding Volume Up button only.
And the only reason why you should keep recovery original is that it doesn't really wipe /data - it also creates some files there like custom.bin, containing your regional settings.
Hi Slavon,
Thanks for your highly appreciated comment. @somboons was looking for a stock recovery so I thought this might help.
Your given information are really helpful. I did not know that you could flash TWRP in recovery2 and replace erecovery Handy information.
I'm pretty new to the Huawei structure so always glad to learn something.
EDIT
A lot of good information can be found here: http://forum.xda-developers.com/honor-7/general/dual-recovery-honor-7-t3308398
Thank you very much,
sselpeelsxx
Giving Back
Benjamin,
I've also been a long time XDA lurker. Most of the devices I have owned were mainstream and thus already had a very active XDA developer community; Even if root had yet to be achieved, there would be hundreds of messages on the topic.
It seems the Mediapad M3 is just getting started. I am a developer of over 20 years, but very little android experience. However, I have recently spent a considerable amount of time (about 50-100 hours) working with the low level ADB protocol source code. And I have rooted and flashed no less than 50 devices, everything from cell phones to Android TV devices to routers.
I'm going to take this device on as my first real dev effort in this arena.
I have a few goals:
1. Get working backups for people that soft-brick or need to revert (including myself).
2. Recompile TWRP for the M3 to confirm greatslon's work, and better understand the process.
3. Release a stock rom that's pre-rooted and cleaned up (not that there was a lot of bloat on my device).
4. Release a custom rom that's not MIUI (perhaps based of CyanogenMod).
Since I have virtually no experience, I am sure these goals are quite lofty and will take some time. But hey, you got to have a plan, and I don't have anything else to work on right now.
Let me know if you want to work on anything together, or if you need any help with anything development related.
- 0D0A
Hey hey 0D0A,
I totally agree with you regarding the backups, I think once the first OTA update is pushed for the EU and US devices we have a good and safe way to go back.
Especially the US owners are struggling with greatslons TWRP version, that's the first thing we should tackle after the backup topic is cleared
I will contact you regarding possible work
Best regards,
Benjamin
can flash twrp via fastboot but get error saying and no recovery
hi, first thanks greatslon for doing the work on m3.
i seem to have succeeded in getting stuck and can't get it to boot into your custom twrp. adb on linux was working fine, but no longer. ditto for fastboot just get "waiting for devices" now. i switched to win10 and installed the hisuite app so i can use fastboot but still no adb. so i have tried to flash recovery and recovery2 but when i try to boot recovery i get error "Func NO: 11 (recovery image) ERROR NO: 2 (load failed)."
i then downloaded your custom rom and tried to flash the boot for that still no luck. i can't use adb so i am not sure how to just flash the custom rom with fastboot without being able to get into any recovery.
i did have this all rooted and working with your twrp but kept having issues with dpi and there was an ota update (b003) which wouldn't apply. so i tried to restore backup and it wen't south from there. basically now can't do much other than see the unlock "can't be trusted" page and bootloader.
any suggestions?
Desperately need stock recovery img, not sure exactly what when wrong, but it is stuck in a horrible boot loop. Tried Benjamin's recovery files and they seem to remove twrp and put it somewhat back to normal, but can only access the emui recovery and that fails to load the files. Put twrp back and tried greatslon's ROMs, they load but goes back to boot loop. Wipe and format everything, install my original backup through twrp recovery, it says it works, but again, back to boot loop... at this point I think I'm dead... any ideas, any word on the official recovery img? anything? Help!!
What device do you have? And what version were you on?
sselpeelsxx said:
What device do you have? And what version were you on?
Click to expand...
Click to collapse
I have the M3, BTV-W09, not sure what version, MM6.0 EMUI 4.1
Anyone have any other ideas on horrendous boot loop?
sselpeelsxx said:
Hey hey 0D0A,
I totally agree with you regarding the backups, I think once the first OTA update is pushed for the EU and US devices we have a good and safe way to go back.
Especially the US owners are struggling with greatslons TWRP version, that's the first thing we should tackle after the backup topic is cleared
I will contact you regarding possible work
Best regards,
Benjamin
Click to expand...
Click to collapse
Hello, I am unlocked, TWRPed, and rooted, but am trying to reverse all of that. My build number is BTV-W09C128B002. Is it safe to download the stock recovery from the OP for my device? Or do I really need the C128 version?
Hello and sorry for the late response, you would need the matching version for your C128 device.
I may be able to extract recovery from an update, I have to look into this tomorrow.
Regards
sselpeelsxx said:
Hello and sorry for the late response, you would need the matching version for your C128 device.
I may be able to extract recovery from an update, I have to look into this tomorrow.
Regards
Click to expand...
Click to collapse
Thanks! I have been able to use the Huawei Extractor to extract a recovery.img from OTA updates, but have been afraid to try flashing it. It has been recommended to hold off on trying that since that recovery.img is from an OTA and not a FULL update. Any thoughts?

twrp Porter/Maker for Mediatek MT67XX 64bit & new 32bit Phone

twrp Porter-
as we know there is no tool available to port twrp for mt67XX. Phone so here i create a Simple and user friendly tool to Manually Port twrp for the Mediatek MT67XX Phone also Work with MT65XX new 32 bit phone .
The tool is Not based on Source This is a manually Porting Method where we use Stock Recovery to Port a custom Recovery. i have Port twrp for almost all latest MT67XX Chip from source and you can use as a Port Recovery,[Link below]..
What you need
1. tool Download Here https://androidfilehost.com/?fid=962021903579481564
2. Stock recovery [dump using SP tool or using Miracle box] Rename it 'stock.img'
3. Ported twrp from same chip [ Here is My collection- https://www.androidfilehost.com/?w=files&flid=220042] select according your chip if not work try from other phone. rename it 'port.img'
Note- i have Not enable auto copy to keep work with all chip Manually copy Paste Require.
Instructions-
Place port.img and stock.img in tool folder
Run twrp Kitchen.exe and follow on screen instructions
Donation-
You can Donate Me http://paypal.me/droiddeveloper
Faq-
1. Touch Not Work-
it's due to kernel source try to port from other twrp,
final solution use OTG or compile from source.
2. unable to mount partition's-
check and fix fastab in ramdisk folder before hiting enter.
3,. is this Work on old MT65XX Phone-
yes you can use it for MT65XX phone.
4. is This Method work 100% on all Phone-
No it can't work 100% on all phone but work on up to 90% of Mediatek Phone.
5. is this Support Nougat and oreo Images-
yes this one Support oreo and Nougat Recovery Images.
XDA:DevDB Information
twrp porter , Tool/Utility for all devices (see above for details)
Contributors
XN Logos
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2017-09-30
Created 2017-10-01
Last Updated 2018-01-06
@XN Logos
Thanks for the tool.
I cannot download the recovery
MT6757 6.0 MM.rar
MT6757 Nougat helio P25 6GB RAM.zip
MT6797 Helio X27 6.0MM.rar
you can download from androidfilhost.
here is twrp for ulefone t1 ported using this tool base umi plus e. Helio p25, this tool not work on umidigi crystal 4GB/64GB i have tried but not success. https://androidfilehost.com/?fid=673368273298987398
Thank u for your great job, i think the recovery we obtain is called "image-new.img" (and not "recovery-new.img" as it's mentioned in the screen instruction). I successfully get this recovery but don't know how to flash it ( because my phone is locked and not rooted "LENOVO C2- k10a40-" ( MT6735 ). HELP PLZ and thanks again .
walid77dz said:
Thank u for your great job, i think the recovery we obtain is called "image-new.img" (and not "recovery-new.img" as it's mentioned in the screen instruction). I successfully get this recovery but don't know how to flash it ( because my phone is locked and not rooted "LENOVO C2- k10a40-" ( MT6735 ). HELP PLZ and thanks again .
Click to expand...
Click to collapse
You can flash it using SP flash tools, take scatter file from your ROM and then flash with SP tools...
Here is Fastboot Guide, but you can face adbd and large image error with fastboot.
Code:
fastboot oem unlock
fastboot flash recovery recovery-new.img
Please, help me to find usb vcom drivers for my device : LENOVO C2, k10a40, MT6735. Thank u again
walid77dz said:
Please, help me to find usb vcom drivers for my device : LENOVO C2, k10a40, MT6735. Thank u again
Click to expand...
Click to collapse
I beleive that any question not related to TWRP porter is OT here. Check driver v. 5.1632.
mod edit - needrom links removed not allowed due to registration required in order to download
Here is all Flash tools and drivers-
https://androidfilehost.com/?w=files&flid=216849
XN Logos said:
Here is all Flash tools and drivers-
https://androidfilehost.com/?w=files&flid=216849
Click to expand...
Click to collapse
You can get all news about Mediatek driver and tools (like Flashtool) here:
http://www.androidiani.com/forum/mo...l-flash-di-telefoni-con-chipset-mediatek.html
The latest driver (ADB + Preloader) is 5.1632 (the link that I posted), and is good fro XP up to Windows 10 and didn't rqeuire to disable driver sign.
The latest version for Flashtool (for Windows and Linux) is 5.1728
In the link that I posted are available Gogle Platform Tools (adb.exe/fastboot.exe) usefull for flash boot or recovery without using Flashtool.
base added for Helio X23 [Rename rk.bak to recovery.img]
https://androidfilehost.com/?fid=745849072291678959
Hi
great tool for mtk user y have à mt6797M ( elephone s7 4G )
if I understand correctly I need the recovery stock (I have) and a port recovery ( don't have ) but there are none in the link you give., I tried with MT6797 + helio + x25 + 6.0 but I have a MT6797M with android 7, I'm not sure try to flash .
is it possible for you to make a port of the MT6797M Helio X20 M ?
And my fil name: image-new.img not recovery-new.img it's normal ?
Thinking i got same request as Bradco but MT6753M chip Cubot Cheetah 2
I was not able to find the "1st kernel file", guessing it is xx.img-zImage file.
Here my device nougat stock recovery (or at page 4 device review)
With my device at the moment TWRP seems to work only on Marshmallow. It would be nice if someone like to share an updated recovery
BTW
It took me a few retries to check extracting recoveries requiers 3 or 4 times press enter instead of just a singel press any key
@toBsucht Psp @Bradco we have twrp for both Phone 1. Elephone S7 and 2.cubot cheetah 2 no need to Port again. search Forum..
XN Logos said:
@toBsucht Psp @Bradco we have twrp for both Phone 1. Elephone S7 and 2.cubot cheetah 2 no need to Port again. search Forum..
Click to expand...
Click to collapse
yes there is this twrp: TWRP 3.0.3 by Jemmini (I have it) available on needrom and xda
it works with android 6 without problem but not with android 7.
This TWRP 3.0.3 by Jemmini is based on rom: S7_4g_20170110092009_v1.9.zip which is a rom android 6: https://bbs.elephone.hk/thread-12895-1-1.html#.WdiBplu0OM
My rom got this one: s7_4g_20170814163417_v2.4.zip which android 7 v2.4
I tried this :
1. clean install the rom: s7_4g_20170814163417_v2.4.zip
2. start the phone
3. flash the twrp : TWRP_303_Elephone_S7_4g_v1.9
4. reboot the phone but it is blocking on the logo ( I access the recovery but can not start the phone )
5. y tried 2/3 times but once the recovery install it remains on the logo.
after searching I found only this recovery TWRP_303_Elephone_S7_4g_v1.9
I do not know if there is an update because all DROPbox links are down.
@Bradco
Please read carefully the object of this thread. It's only about TWRP porter.
Is not a thread of support for mod recovery about specific devices.
For this please post in the specific thread for the device. Thanks.
@XN Logos
I propose to add this as first object of firs post
- Scope of this thread
Scope of this thread is only to discuss about TWRP porter application.
Please don't discuss about support for recovery for specific devices.
For this please post in the specific thread for the devices.
bovirus said:
@Bradco
Please read carefully the object of this thread. It's only about TWRP porter.
Is not a thread of support for mod recovery about specific devices.
For this please post in the specific thread for the device. Thanks.
@XN Logos
I propose to add this as first object of firs post
- Scope of this thread
Scope of this thread is only to discuss about TWRP porter application.
Please don't discuss about support for recovery for specific devices.
For this please post in the specific thread for the devices.
Click to expand...
Click to collapse
yes sorry,
I explain just my situation, the subject of my post is well on the port of TWRP for processor MT6797M and not on elephone s7. I must speak well of the phone to explain the problem correctly.
Ps : y test this tuto : https://forum.xda-developers.com/showthread.php?p=32965365#post32965365
but y don't find the file BoardConfig.mk
Pretty much same here!
i took a look to default.prop it use a string:
ro.build.version.sdk=24 (stock v14 recovery)
ro.build.version.sdk=23 ( twrp recovery)
even more that needs to be updated in default.prop file from old TWRP to enable it on API24 i.g.
ro.build.fingerprint (seems to be a littel more work)
i stopped repacking TWRP since i note bad image maybe brick my phone.
Also someone told me marshmallow uses ID_creation code = MOB30J; Nougat uses ID_creation code = NHG47N .... idk
funny i removed a additioinal password request. Another user now got additional :highfive: and idk how it occur
Yes Guys, This thread is only for tool Not for Specific Device. So you can ask only for Port base [MT67XX] not for twrp. if you need twrp You can contact Me or create yourself using tool.
XN Logos said:
Yes Guys, This thread is only for tool Not for Specific Device. So you can ask only for Port base [MT67XX] not for twrp. if you need twrp You can contact Me or create yourself using tool.
Click to expand...
Click to collapse
ok I understand, I want to try to do it myself, can you make a port of MTK 6797M ?
( this is what I needed at the start, I came on this thread to do the twrp myself.
thank you in advance
As already written it is not that easy to use if some errors occur. Also i did not 100% on it which files i have to remove if tool say "delete following":
1. kernel (is it x.img-zImage?)
2. kernel offset (i guess i found)
and that flase "press ANY key" message! Just as a little sidenote for your update.

Newb needs help rooting, unlocking Bootloader and getting a Custom ROM for ALE-L21

Hey there,
I need help, hope you have some for me . I want to use the 6.0.1. OpenKirin OmniROM on my phone and struggle even figuring out a way to get there.
I just bought a used ALE-L21 DualSIM phone with the B602 Build and EMUI 4.0.3 installed. The device is not rooted, nor has its bootloader been unlocked. The EMUI update service does not offer me any patches.
Could someone please line out to me which steps I have to take in order to root my ALE-L21 and get this ROM to work?
Disclaimer: No, I'm not just a lazy moron who does not want to read other topics on this forum - I'm a mere user with less-than-average knowledge of Android development or stuff like that. And I just can't make complete sense of the various posts I've found, since English is not my mother tongue and there seems to be a whole bunch of ways to do certain things with a phone. Well, since obviously I don't want to brick my new phone, I'm not too sure how to best puzzle together the pieces this Forum offers me. It would be insanely helpful if I could get a list that reads out something like:
1. Action - Source (for needed files, e.g.) - Result, on to step 2
2. Action - Source (for needed files, e.g.) - Result, on to step 3
3. ... and so on...
Okay, just so you see that I'm not entirely lost, I'm gonna show you the picture which is currently in my mind.
From what I understand so far, there's the following steps to get there (please rectify or rearrange steps as far as needed):
1. Update the device to Vanilla EMUI 4.1, Build B895 or B896 (I am currently downloading the B896 Build from this forum - which one is recommended? My phone is DualSIM)
2. Unlock Bootloader (What's the best way to do it? Huawei CS? Heard it's not even sure you get an answer. DCUnlocker? Wants money... Please help me clarify)
3. get TWRP 3.1.1.0 (I already have the IMG file, how do I get it to run on my phone?)
4. Root the device (I'd like to go with MAGISK, does anyone have a link for a MAGISK build confirmedly working on ALE-L21?)
5. Do some magic with TWRP (Which steps exactly?)
6. Flash the ROM Zip file via TWRP
7. Flash Gapps via TWRP
Is that about it?
As I said, please feel free to add to/adjust my list!
Thanks in advance,
Pako
If you haven't already install minimal adb tools on computer (windows) found here :
http://bit.ly/2jxX4ya
You then need to unlock bootloader using minimal adb tools and the unlock code
Unlock Code:
http://bit.ly/2z9EFhV
Unlock Bootloader Method in this thread here:
http://bit.ly/2oIASBs
After you are done unlocking the bootloader
Install twrp find that here :
http://bit.ly/2ok9BTi
There was a tool that was here somewhere to install twrp but I will link to my copy here
http://bit.ly/2ATBgRP
What you do is put the twrp image file in data folder
then change the name of the twrp file to TWRP_3.1.1-0_ALICE.img or
edit the install.bat file line data\fastboot.exe flash recovery data\TWRP_3.1.1-0_ALICE.img to the name of your twrp file
Once twrp is installed then you can pick which rom you want
The 6.0 roms arent going to be supported anymore so i suggest going for 7.0 ROM
I'm on AOSPA which is the cleanest and has good battery life
To install 7.0 rom you need B895 or B896 found here on the first post:
http://bit.ly/2jypIij
this is installed through twrp (which is accessed when Phone is off by holding volume up + power then let go once it vibrates or connect the phone to the computer and then type adb devices then adb reboot recovery in minimal adb tool)
once in twrp you need to install the B895.zip or B896.zip file then reboot your phone will boot into emui
you need to install twrp again as B895 or B896 wipes it
After installing twrp you can then install any custom rom of your choice
let the rom boot and then go back into twrp and install gapps found here: "http://bit.ly/1JOWjUqi recommend nano or even pico pick am64 7.1
I would also recommend installing Galactic forced deepsleep http://bit.ly/2ANVdbS
Hey there,
thank you very, very much for your comprehensive walkthrough! (Almost*) everything worked to perfection and I am now a happy user of OpenKirin's OmniROM 6.0.3. mod! Yeah, no 7.x... but I'd prefer to wait with that until the "issues" section of AOSPA does not contain any relevant things anymore. OmniROM seems to have no issues anymore, so I'm content with my choice. I will now follow your last advice and flash the Deep Sleep Mod to improve my device's battery life, and then I'm just happy.
* = The only issue I encountered was when having flashed TWRP, the device booted to the crappy EMUI eRecovery instead of TWRP. I solved this issue using this advice from another thread.
So, once again, thank you! All you xdaDevs, keep on developing ways to improve people's lives with their android devices!
Cheers,
Pako

I think I bricked my x722 device? Any help would be appreciated!!

Hi! I'm fairly new to modding with Android, so please bear with me
I wanted to install LineageOS 15.1 on my x722 based Le Pro 3 Elite device, and basically all went well. I however didn't enjoy it fully.. I liked the old EUI better after using Lineage for about an hour. So I looked up a flash file, and attempted to flash it using TWRP. I have recently found out this was a bad idea. Basically when I flashed it, it had installed a chinese version of EUI. (I had purchased my device from Banggood, it didn't come with the chinese stuff). So I looked up a guide on here that would take me down to ver. 001D, and put me back to 020S by using a chinese .bat file after installing the 001D version of EUI. It didn't work, so I kept looking around and installing different things. Basically, where I am now is I am not able to boot into my phone. This was my daily driver, but sadly not anymore.
Whenever I try to access recovery, it will flash the recovery text, but then restart back into its boot loop. I am only able to access the blank screen (Hold down pwr, vol+ and vol-) and the Fastboot menu. Whenever I try to unlock the OEM, it tells me I cannot, and whenever I try to flash a stock recovery or a TWRP recovery, it tells me the device needs to be unlocked, or partition flashing is not allowed.
Is my device gone? or is there a way to get it back through something like FlashOne or somehow getting it back through fastboot or ADB?
Any help would be greatly appreciated, once again sorry if I sound like an idiot haha
Thanks!
First, never flash stock EUI in Recovery, it needs to be flashed from ADB.
You could try using the ALL In One Tool to restore you phone to stock, by flashing the current version of EUI ( the one that came with the phone)
Mauronofrio's tool is called: "TOOL ALL IN ONE"" and it's has a link to the stock Roms for many devices.
Install the program and setup PC first
After you install it, make sure to check for AIT updates, and ADB updates. Plus give ADB system wide privileges, I would suggest that you disable antivirus and firewall so the program can download drivers and software without issue.
Get it here:*https://toolaio.tk**
Go to theXDA page for Le pro 3 instructions: https://forum.xda-developers.com/le-...1#post71627491
Read how to use it within that thread. However, its fairly intuitive.
* The all is one tool is excellent and you can use it to install everything you want.
* You can use it to unlock the bootloader, if needed
* Remove Encryption, if needed
* Install TWRP, when needed
* Install your Rom, Gapps and Magisk etc., if or when needed
* The tool will also update your existing installation of ADB, Android Drivers, and provide system wide ADB privileges
At first I was going to tell you that no Qfil is available for the Elite X722, and your phone is not fixable. However, it sounds like maybe? Hoepfully you are lucky and probably not actually hard bricked? You say that you are able to boot into recovery and fastboot right?
If that is the case you should be able to recover your phone., and reflash the proper EUI.
I do not have a X722 , so you need to search XDA for others that have had this similar issue. Look for recent post, some of the older posts from early 2017 is now outdated or just incorrect, such as you finding the chinese version of EUI.
I would recommend that you go to a X722 thread and look for someone that has had a similar issue with their own X722.
Btw, there are plenty of fantastic roms that are much better than EUI but you need to be more careful about what you flash, and ensure that you know what you are doing first.
Try asking Gabronog in the AOSIP forum, I am pretty sure that he has a X722.
tsongming said:
First, never flash stock EUI in Recovery, it needs to be flashed from ADB.
You could try using the ALL In One Tool to restore you phone to stock, by flashing the current version of EUI ( the one that came with the phone)
Mauronofrio's tool is called: "TOOL ALL IN ONE"" and it's has a link to the stock Roms for many devices.
Install the program and setup PC first
After you install it, make sure to check for AIT updates, and ADB updates. Plus give ADB system wide privileges, I would suggest that you disable antivirus and firewall so the program can download drivers and software without issue.
Get it here:*https://toolaio.tk**
Go to theXDA page for Le pro 3 instructions: https://forum.xda-developers.com/le-...1#post71627491
Read how to use it within that thread. However, its fairly intuitive.
* The all is one tool is excellent and you can use it to install everything you want.
* You can use it to unlock the bootloader, if needed
* Remove Encryption, if needed
* Install TWRP, when needed
* Install your Rom, Gapps and Magisk etc., if or when needed
* The tool will also update your existing installation of ADB, Android Drivers, and provide system wide ADB privileges
At first I was going to tell you that no Qfil is available for the Elite X722, and your phone is not fixable. However, it sounds like maybe? Hoepfully you are lucky and probably not actually hard bricked? You say that you are able to boot into recovery and fastboot right?
If that is the case you should be able to recover your phone., and reflash the proper EUI.
I do not have a X722 , so you need to search XDA for others that have had this similar issue. Look for recent post, some of the older posts from early 2017 is now outdated or just incorrect, such as you finding the chinese version of EUI.
I would recommend that you go to a X722 thread and look for someone that has had a similar issue with their own X722.
Btw, there are plenty of fantastic roms that are much better than EUI but you need to be more careful about what you flash, and ensure that you know what you are doing first.
Try asking Gabronog in the AOSIP forum, I am pretty sure that he has a X722.
Click to expand...
Click to collapse
Thankyou so much for this!
One sad thing though, OEM is locked and I don't have a way of unlocking it. Recovery does attempt to launch and open, but it doesn't want to. I see the recovery screen, the screen you see when you try to load into it, but then it just reboots the phone. OEM is locked, and Recovery does not work.
Thanks!
VoiiDFX said:
Thankyou so much for this!
One sad thing though, OEM is locked and I don't have a way of unlocking it. Recovery does attempt to launch and open, but it doesn't want to. I see the recovery screen, the screen you see when you try to load into it, but then it just reboots the phone. OEM is locked, and Recovery does not work.
Thanks!
Click to expand...
Click to collapse
Does fast boot work?
If it does you can try these files : emmc_appsboot.mbn and xbl.elf using adb. You can get those files by unzipping the X722 firmware and then placing those files in your platform-tools folder.
If you cannot get into fastboot, then I am sorry your phone is hard bricked and unfortunately Leeco never released the Qfil for the X722 to the public..
Hard Bricked Options
Replace the motherboard with the motherboard from the X720 or X727 ( Yes, it will work)
Try to return the phone to Bangood under warranty, " It just stopped working" This has been a working option for some people. Worst case scenario maybe they have a way to fix it, or will send you an exchange replacement for a fee
Good Luck
I'm sorry to tell you that you can not do anything.
The fastboot does not work for you, because you do not have permissions, it can only be fixed with qfil, and it does not exist for X722.
Greetings.
Your device is bricked without a fix. I wish you read the sticky here and in the x722 development forum before doing anything.

Categories

Resources