i found this trwp recovery floating around i dont know who made it.
it boots fine but no touch screen hopefully someone can fix it
https://www.androidfilehost.com/?fid=457095661767138152
kvip60 said:
i found this trwp recovery floating around i dont know who made it.
it boots fine but no touch screen hopefully someone can fix it
https://www.androidfilehost.com/?fid=457095661767138152
Click to expand...
Click to collapse
What's the easiest way to install this?
I didn't install it I just used" fastboot boot image-name"
kvip60 said:
I didn't install it I just used" fastboot boot image-name"
Click to expand...
Click to collapse
Ok Thanks. I am in and generating a backup. The touch screen was working for me mostly. It won't let me select Micro SDCard to save my backup.
Yeah like I said it need some repair I am pretty sure the mount points aren't perfect and I didn't compile it I had to use an otg and mouse to navigate
kvip60 said:
Yeah like I said it need some repair I am pretty sure the mount points aren't perfect and I didn't compile it I had to use an otg and mouse to navigate
Click to expand...
Click to collapse
What I did to navigate was I had to push the power button then it would bring the screen up where you can swipe the bottom to unlock the screen and use touchscreen. Navigating the storage was odd because it shows it is stuck on Internal storage, but If i click on SDCard, it will take me to that directory. I hope there is a nice update to this is the near future, so we don't have to access it through "adb reboot recovery"
You can flash it if you like I just don't trust this copy yet waiting for an update before I flash it
You can use" fastboot flash recovery twrp.img" to flash rather than "fastboot boot twrp.img " to boot it
kvip60 said:
You can flash it if you like I just don't trust this copy yet waiting for an update before I flash it
You can use" fastboot flash recovery twrp.img" to flash rather than "fastboot boot twrp.img " to boot it
Click to expand...
Click to collapse
Oh man you were so right. I had it flashed and it caused me all kinds of problems, like booting the screen upside down etc. I was finally able to find the recovery.img in another thread and get back the stock recovery. I think I will also wait until there is a more stable TWRP version.
I always use boot to test and I always backup my recovery before flashing because I had that happen to me before
Any idea on when a decent working custom recovery will be available?
blahforme said:
Any idea on when a decent working custom recovery will be available?
Click to expand...
Click to collapse
Probably when someone will have the will & time to work on it.
Maybe you'd like to take on this topic?
Lol. I hear you. I have very little understanding of Linux I have tried to make one but there aren't enough information about compiling device /vendor tree for a new device to go on
Just visit this page and you will get TWRP for Z016D. It's a Taiwan website with Chinese but you can see the blue link marked as "TWRP" and there you are.
https://www.asus.com/zentalk/tw/thread-214217-1-1.html
lssong99 said:
Just visit this page and you will get TWRP for Z016D. It's a Taiwan website with Chinese but you can see the blue link marked as "TWRP" and there you are.
https://www.asus.com/zentalk/tw/thread-214217-1-1.html
Click to expand...
Click to collapse
Thanks for this. Posting the Mega so people don't have to make an Asus account to grab it.
https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
The 20170218 recovery works perfectly with my phone (6/64gb, 820). The first one posted in the OP worked, but was a bit glitchy. The updated one has working SD reading and touchscreen works without having to lock it first.
Could someone please tell me why twrp is booting upside down on my device, and how do I fix it? I just tried to run it in fastboot boot twrp-3.0.3-0-Z016D-20170218.img and once again it loads upside down, however the touch screen is where it normally is suppose to be, which makes it very difficult to navigate the menus. It is very frustrating. This has happened to me multiple times this week. I can't seem to get it to boot/load properly.
blahforme said:
Could someone please tell me why twrp is booting upside down on my device, and how do I fix it? I just tried to run it in fastboot boot twrp-3.0.3-0-Z016D-20170218.img and once again it loads upside down, however the touch screen is where it normally is suppose to be, which makes it very difficult to navigate the menus. It is very frustrating. This has happened to me multiple times this week. I can't seem to get it to boot/load properly.
Click to expand...
Click to collapse
Are you using the Snapdragon 821 version by any chance? Cause people with the s820 seem to be working fine.
I am using 821 my screen is flipped and no touch even after locking it
Huffy1 said:
Are you using the Snapdragon 821 version by any chance? Cause people with the s820 seem to be working fine.
Click to expand...
Click to collapse
No, I am using the sd820.
---------- Post added at 08:25 PM ---------- Previous post was at 08:07 PM ----------
I really don't want to wipe everything and start all over from scratch because everything else is working great right now. I guess if there is no easy solution, then I will just leave it alone. I ran it with fastboot and then made a backup and saved it on my microSD card. But I am worried if I wipe everything and start all over again, then I will have to call my bank again to verify my cards for Android pay. I am running the stock firmware version 1698, with stock recovery, an unlocked bootloader, & rooted. Also have Magisk & Titanium Pro installed, and I verified that Andoid pay works for me. (I already bought something using Android pay).
blahforme said:
No, I am using the sd820.
---------- Post added at 08:25 PM ---------- Previous post was at 08:07 PM ----------
I really don't want to wipe everything and start all over from scratch because everything else is working great right now. I guess if there is no easy solution, then I will just leave it alone. I ran it with fastboot and then made a backup and saved it on my microSD card. But I am worried if I wipe everything and start all over again, then I will have to call my bank again to verify my cards for Android pay. I am running the stock firmware version 1698, with stock recovery, an unlocked bootloader, & rooted. Also have Magisk & Titanium Pro installed, and I verified that Andoid pay works for me. (I already bought something using Android pay).
Click to expand...
Click to collapse
How did you install Magisk having stock recovery? Using the in-app installation?
---------- Post added at 01:08 PM ---------- Previous post was at 01:05 PM ----------
It seems @EypCnn is the developer of this TWRP builds...
sebastiandg7 said:
How did you install Magisk having stock recovery? Using the in-app installation?
Click to expand...
Click to collapse
I flashed Magisk v11.1 with TWRP, then installed Magisk Manager from the Google Play Store, after I rebooted my device. I did that by booting in to TWRP with fastboot to flash the .zip file. I did not flash TWRP to install Magisk.
Related
Hard brick for OPT happens when you change critical partitions. It will follow improper firmware flash or accidental erase of certain partitions. The phone won't show any response when hardbricked.
The solution for OPT is similar to OPO - you just need a Qualcomm driver and a recover package. The only full recovery package available is very big and it restore the phone to Hyrdogen OS, with everything wiped. So it would not be very attractive.
Fortunately, thanks to this post from Chinese supporting forum, a minimal version of restore package is provided. It does not wipe user data and guarantee a recovery entry. you would normally be freed using this package. if not, please use the full package in the end of the post
Download link for driver
Download link for Recovery tool
uncompress the files to a local folder.
First step, turn off drive signature enforcement in windows 8/8.1/10. Tutorial Here
Second step, hold the power key for 20 seconds to force turn off power. connect OPT to usb, hold volume+ and power until your PC finds a new hardware (if it doesn't work, try hold volume+ and volume- together)
Third step, go to device manager in your PC, find the new "QUALCOMM-HS USB Diagnostics 9006" device. Update its driver in property page using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder).
Fourth step, when the driver is installed properly, run MSM8994DownloadTool.exe in the recover tools folder, using admin privileges . Clear start in top left corner and wait for it to finish.
Now your OPT should be able to enter TWRP recovery. It still won't boot but you can manually flash anything again (like the full Oxygen OS package).
The procedure is tested by me twice. Enjoy!
p.s: sorry the recovery image in the A2001_save_brick_mini.rar is Chinese. Please download this file, change the name to recovery.img and substitute the file in the recovery tool before flashing.
UPDATE：full Oxygen OS 150805 restoration package for those who experience recovery entry problem. Note that this package wipes everything including internal storage!
Awesome, I will go ahead and make a full recovery tool that includes these files as well as the latest version of OxygenOS as I did with the Oneplus one.
You write about a full Oxygen Package? What do you mean with it? a flashable .zip or fastboot .img?
CoreGaming said:
You write about a full Oxygen Package? What do you mean with it? a flashable .zip or fastboot .img?
Click to expand...
Click to collapse
Like i did before with my mod of the toolkit
https://forums.oneplus.net/threads/...ol-restore-stock-cm11s-fix-bricks-etc.237827/
okay and were can i get this package for the OPT?
CoreGaming said:
okay and were can i get this package for the OPT?
Click to expand...
Click to collapse
Havn't made it yet, still need to work on it. It is a little different than OPO so it might take some time.
okay this will be great. Take your time i'm ready
Hi,
anyone knows how I can force the OnePlus Two to enter QUALCOMM-HS mode?
I have a "semi-bricked" OP2.
It can boot, but the recovery is broken and I cannot enter it anymore. Worse enough, the bootloader is locked and I cannot unlock it anymore.
So I am kinda stuck and thought this manual would bring me back recovery. But - I cannot get it to enter this specific emergency recovery mode as boot loaders are intact.
Any idea?
Thanks
Andi
Lord Boeffla said:
Hi,
anyone knows how I can force the OnePlus Two to enter QUALCOMM-HS mode?
I have a "semi-bricked" OP2.
It can boot, but the recovery is broken and I cannot enter it anymore. Worse enough, the bootloader is locked and I cannot unlock it anymore.
So I am kinda stuck and thought this manual would bring me back recovery. But - I cannot get it to enter this specific emergency recovery mode as boot loaders are intact.
Any idea?
Thanks
Andi
Click to expand...
Click to collapse
Hmm, I may be able to help. Do you got a hangouts we can talk on so it could be easier? If so PM me your email so I can add you.
Zyxxeil said:
Hmm, I may be able to help. Do you got a hangouts we can talk on so it could be easier? If so PM me your email so I can add you.
Click to expand...
Click to collapse
Hi,
ok, I am one step further now.
I could bring the device in that mode, flashed via this recovery tool. All partitions were flashed but still no recovery. How can that be? ooops.
I did that many time on my OPO already successfully. But of course with the full recovery package.
So question is, I would not mind starting from scratch... anybody knows where the "big" recovery package that erases everything is available?
Thanks
Andi
Lord Boeffla said:
Hi,
ok, I am one step further now.
I could bring the device in that mode, flashed via this recovery tool. All partitions were flashed but still no recovery. How can that be? ooops.
I did that many time on my OPO already successfully. But of course with the full recovery package.
So question is, I would not mind starting from scratch... anybody knows where the "big" recovery package that erases everything is available?
Click to expand...
Click to collapse
I'm in a similar situation to you. I lost my recovery and somehow my boot loader is locked again. I can't set OEM unlock as I am on the old version of OxygenOS.
I tried the above instructions but they don't work. The phone reboots as normal, not in to recovery. If you solve this then let me know.
EDIT: I think flashing hydrogenos using this method is the best idea. We can then select the OEM unlock from developer settings, use fastboot to unlock the bootloader and flash a new recovery. The question is how? @qwsdert4
khr0n0s said:
I'm in a similar situation to you. I lost my recovery and somehow my boot loader is locked again. I can't set OEM unlock as I am on the old version of OxygenOS.
I tried the above instructions but they don't work. The phone reboots as normal, not in to recovery. If you solve this then let me know.
EDIT: I think flashing hydrogenos using this method is the best idea. We can then select the OEM unlock from developer settings, use fastboot to unlock the bootloader and flash a new recovery. The question is how? @qwsdert4
Click to expand...
Click to collapse
I am on Oxygen 2.0.1 and still do not have the option. Something is really odd...
Andi
Lord Boeffla said:
Hi,
ok, I am one step further now.
I could bring the device in that mode, flashed via this recovery tool. All partitions were flashed but still no recovery. How can that be? ooops.
I did that many time on my OPO already successfully. But of course with the full recovery package.
So question is, I would not mind starting from scratch... anybody knows where the "big" recovery package that erases everything is available?
Thanks
Andi
Click to expand...
Click to collapse
Hi, I got the "big recovery package" in question from OP support centre in China. It will recover your OPT to factory Hydrogen OS from which you could start over. I'll upload it onto Mega very soon so stay tuned.
Lord Boeffla said:
I am on Oxygen 2.0.1 and still do not have the option. Something is really odd...
Click to expand...
Click to collapse
HydrogenOS definitely has the option because it is how I flashed TWRP in the first place
khr0n0s said:
I'm in a similar situation to you. I lost my recovery and somehow my boot loader is locked again. I can't set OEM unlock as I am on the old version of OxygenOS.
I tried the above instructions but they don't work. The phone reboots as normal, not in to recovery. If you solve this then let me know.
EDIT: I think flashing hydrogenos using this method is the best idea. We can then select the OEM unlock from developer settings, use fastboot to unlock the bootloader and flash a new recovery. The question is how? @qwsdert4
Click to expand...
Click to collapse
Without recovery how do you flash hydrogenOS?
---------- Post added at 06:55 PM ---------- Previous post was at 06:54 PM ----------
qwsdert4 said:
Hi, I got the "big recovery package" in question from OP support centre in China. It will recover your OPT to factory Hydrogen OS from which you could start over. I'll upload it onto Mega very soon so stay tuned.
Click to expand...
Click to collapse
Wow thanks, I was trying to do it with the one you posted but I couldn't since it was missing the info for system sectors. Now i can make my tool
Zyxxeil said:
Without recovery how do you flash hydrogenOS?
Click to expand...
Click to collapse
Using this tool and the full recovery package? Or am I missing something here?
khr0n0s said:
Using this tool and the full recovery package? Or am I missing something here?
Click to expand...
Click to collapse
The tool posted does not contain a system, but he is going to post the full one soon.
Zyxxeil said:
The tool posted does not contain a system, but he is going to post the full one soon.
Click to expand...
Click to collapse
Precisely, that is exactly what I meant. Fingers crossed that will solve this.
It could be I successfully recoverd following a hint by user @Zyxxeil (many thanks for the help).
If all works I will post soon what I did.
But - have everything running now again. Next I try to flash twrp again and root. If that worked, I will post the steps.
Andi
qwsdert4 said:
Hi, I got the "big recovery package" in question from OP support centre in China. It will recover your OPT to factory Hydrogen OS from which you could start over. I'll upload it onto Mega very soon so stay tuned.
Click to expand...
Click to collapse
Very nice. Wait for it...
Is a Version with Oxygen OS also aviable?
Welcome to Twrp 3.0.0.0 for our Zenwatch 2's
This release I was able to flash the recovery, flash the supersu zip, and flash some others, so far I have not encountered our wild soft brick madness.
Thanks to @acbka for showing me how to get into log files, essentially helping me figure out why the partitions were not mounting correctly when I compiled and recompiled.
Here is TWRP 3.0.0.0
Directions:
Get into fastboot, either by enabling adb by enabling developer options going into settings, about, and taping the Build number 8 times, and going back, down to developer options and enable ADB Debugging.
Then you can type into your CMD or terminal adb reboot-bootloader or by powering down by holding the button or power down in settings, when the screen goes black, repress and hold the button and swipe the screen from the upper left down to the lower right and that should bring up the ASUS logo with CSC Fastboot Mode! on the screen
continue to boot the recovery by typing fastboot flash recovery twrp3.img
OR load up your tethered twrp and flash the image under that.
Hope you guys enjoy! So far I have not encountered soft bricks so it should be safe and sound
thank you, will test now
---------- Post added at 09:21 PM ---------- Previous post was at 09:01 PM ----------
Works perfectly, my zenwatch 2 is now rooted
thank you, you`re amazing
Thank you very much! I hope this will be one of the first steps into advanced development for our watches! Does this work for WI502Q? But what's a benefit of rooting this watch?
okaay3D said:
Thank you very much! I hope this will be one of the first steps into advanced development for our watches! Does this work for WI502Q? But what's a benefit of rooting this watch?
Click to expand...
Click to collapse
That im not sure, it might, wouldnt hurt to fastboot boot it and see if itll start twrp. I have the 501
Root will go with modifying the Momentum kernel so you wont have much lag on the watch, and any other root modifications that can go with it, like maybe xposed?
Next step in development is fixing twrp so it can be flashed, then maybe modifying the wear os? Or maybe porting some stuff
T10NAZ said:
As far as I understand people are able to get backups of their watch in order to preserve OTA's before rooting
Click to expand...
Click to collapse
I want to test it. But how do I backup my watch and restore it to get updates? And is there something like a KNOX-counter to tell whether the device was modified?
matze19999 said:
Works perfectly, my zenwatch 2 is now rooted
thank you, you`re amazing
Click to expand...
Click to collapse
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Awesome! Got supersu flashed and was able to use Advanced Settings to disable some of the built-in bloatware apps. I'll have to try out the kernel but I'm currently at work and don't want to spend all day messing around with my watch (well... I want to, but I like not getting fired).
4RK4N said:
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Click to expand...
Click to collapse
I do have the 5.0.1 wear downloaded and installed! And as far as i know, Its working ok
okaay3D said:
I want to test it. But how do I backup my watch and restore it to get updates? And is there something like a KNOX-counter to tell whether the device was modified?
Click to expand...
Click to collapse
You can tell twrp to preserve the system protection, back every single thing up that you can in the twrp option, push that backup to your computer, and then you can disable system protection. twrp itself wont do anything, however playing with options will modify the watch.
OR you can fastboot pull things off the watch, the system.img and boot.img yourself, in case the ones uploaded in my general thread didnt have the protection enabled.
If you want to hang tight until 1.4 comes out, that can be a good thing too
And im not sure if there is something like that on the watch. I have not seen anything about it before
My attempt was a failure on my WI502Q. I got the following messages. And, OP, how do you pull system.img from a device through fastboot? I thought you needed root permission to do that through adb.
"
C:\adb\zw2>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.381s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.834s
"
Thanks for this! I was losing hope on any development for this watch but now we have the most crucial component to modifying anything on android, a custom recovery. Going to perform a backup, root and flash your custom kernel you kindly released as well!
T10NAZ said:
Hello everyone, I have been working hard last night to make twrp run on our watches, and this I think is a good representation on what itll be like with actual development going on
As far as I understand people are able to get backups of their watch in order to preserve OTA's before rooting, and I was able to flash some zips and kernels successfully, and I fixed the UI to look better and actually usable on the watch
Also, I was able to flash this puppy, and I got android wear to boot with it flashed, however most of the time, it goes haywire and only boots into recovery. Same thing applies, this shall be a Tethered recovery only until I know why its going crazy.
As always, problems can arise on your watch, so be careful!
read the entire instructions, This is a known way to get system protection off, and to flash zips/kernels when need be. Do not flash please.
Here is the link to the updated twrp
Get into fastboot, either by enabling adb by enabling developer options going into settings, about, and taping the Build number 8 times, and going back, down to developer options and enable ADB Debugging.
Then you can type into your CMD or terminal adb reboot-bootloader or by powering down by holding the button or power down in settings, when the screen goes black, repress and hold the button and swipe the screen from the upper left down to the lower right and that should bring up the ASUS logo with CSC Fastboot Mode! on the screen
continue to boot the recovery by typing fastboot boot recovery.img like the other one.
I also have a kernel underway if people would like to try it out and test it in the next couple days
Click to expand...
Click to collapse
What are the Advantages of installing TWRP in Zenwatch 2 WI501Q..???
does it allow to uninstall stock apps..!!
yash92duster said:
What are the Advantages of installing TWRP in Zenwatch 2 WI501Q..???
does it allow to uninstall stock apps..!!
Click to expand...
Click to collapse
it could lead to that, yea, since this is the only root method basically, it adds a few extra steps to do it
can we root with regular supersu .zip, or do we need a special build for wear devices?
slothdabski said:
can we root with regular supersu .zip, or do we need a special build for wear devices?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view?usp=sharing there ya go. dunno if the regular supersu works. havent tried that out. this one does. and alrdy has a busybox installer wear app included which u need anyway sooner or later.
there is no supersu manager app in it though like on phones. apps requiring root just have it. tested advanced settings so far for disabling built-in stuff and a reboot option. but maybe there is a supersu-wear.apk somewhere?
not my link. taken from here: http://forum.xda-developers.com/showpost.php?p=65759835&postcount=14 he took it from the G watch R forums iirc.
zenwatch2
hi dear freind
after the flash twrp recovery
after the wipe
my watch was brick and hang on asus logo
help me plase
mehdi.ahmadi said:
hi dear freind
after the flash twrp recovery
after the wipe
my watch was brick and hang on asus logo
help me plase
Click to expand...
Click to collapse
Let me know the steps you took from when you downloaded it, to when it sits on the asus logo, and do you have the 502 or the 501 watch?
mehdi.ahmadi said:
after the flash twrp recovery
Click to expand...
Click to collapse
guess that means he flashed it. now his watch is bricked. not that it hasent been mentioned NOT to flash it just fastboot boot ...
flash the stock images via fastboot or tethered (NOT flashed) twrp and you should get your watch working again.
4RK4N said:
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Click to expand...
Click to collapse
I flashed this zip file
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view
matze19999 said:
I flashed this zip file
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view
Click to expand...
Click to collapse
found it about 2 weeks ago somewhere here on xda and alrdy linked it to several ppl here in the thread.
but thx
Just got an update on my watch and, as always, pulled the update.zip for you guys!
If you're having troubles installing this ZIP please refer to this post here: http://forum.xda-developers.com/showpost.php?p=67403296&postcount=19
----------
Quick Install "Guide" if it's still failing for you:
1) Install TWRP from THIS THREAD HERE
2) Reboot into fastboot mode by turning the watch off and on again and while the black screen shows up constantly swipe from the left upper corner to the lower right corner.
3) Flash the TWRP provided above and reboot into recovery, then push the unpacked TWRP backup into "/sdcard/TWRP/BACKUPS/xxxxxxxxxxx/" (to get the last folder simply make a backup of only your boot partition first, it's the fastest)
4) Restore the backup provided IN THIS POST HERE onto your watch via the in 1 flashed TWRP
1) MUCH EASIER: Flash these instead the TWRP way, far far easier!
2) Let the OTA update install automatically
----------
ZIP MD5: 6844d45bf6d4a1e1d6b15e908579d354
>> DROPBOX <<
>> GOOGLE DRIVE <<
>> OneDrive <<
EpicLPer said:
Just got an update on my watch and, as always, pulled the update.zip for you guys!
ZIP MD5: 6844d45bf6d4a1e1d6b15e908579d354
>> DROPBOX <<
>> GOOGLE DRIVE <<
Click to expand...
Click to collapse
I've got TWRP 3.0.?? on the watch and it refuses to flash, error is
Code:
Unable to statfs '/system/.'.
I've flashed the stock recovery in LG G Watch tools. It went fine, so I've proceeded to install the update the standard way. It seemed to be fine, but than it stopped, with the "Dead Android" image. After using the reset button the built in recovery is dead, but the watch boots. Any ideas?
EDIT: TWRP won't mount /system for some reason, you tap the checkbox and nothing happens. Not even as RO.
kokesh said:
I've got TWRP 3.0.?? on the watch and it refuses to flash, error is
I've flashed the stock recovery in LG G Watch tools. It went fine, so I've proceeded to install the update the standard way. It seemed to be fine, but than it stopped, with the "Dead Android" image. After using the reset button the built in recovery is dead, but the watch boots. Any ideas?
EDIT: TWRP won't mount /system for some reason, you tap the checkbox and nothing happens. Not even as RO.
Click to expand...
Click to collapse
You have to use the edited one on my '' how to root guide'' as the official TWRP those not support squashfs
Xmaster24 said:
You have to use the edited one on my '' how to root guide'' as the official TWRP those not support squashfs
Click to expand...
Click to collapse
Thank you. Your recovery mounts /system, but I am still getting the same error.
kokesh said:
Thank you. Your recovery mounts /system, but I am still getting the same error.
Click to expand...
Click to collapse
yeah it can't write to it, you have to use the stock recovery for that. You are able to write to it but you must first format the partition as writable and then flash your system image/ backup. I'm getting the usual "old keys" error of TWRP not error you mentioned, just means The TWRP is too old base
---------- Post added at 11:13 AM ---------- Previous post was at 11:02 AM ----------
Those anyone have a link to the 6.0.1 stock recovery?
Those anyone have a link to the 6.0.1 stock recovery?
Click to expand...
Click to collapse
Isn't it possible to get it from the 6.0.1 OTA?
kokesh said:
Isn't it possible to get it from the 6.0.1 OTA?
Click to expand...
Click to collapse
No, its stored in a propietary .dat file so good luck with that. Hopefully someone wasn't as foolish as me and deleted their recovery backup
Xmaster24 said:
No, its stored in a propietary .dat file so good luck with that. Hopefully someone wasn't as foolish as me and deleted their recovery backup
Click to expand...
Click to collapse
We could try flashing an older version of Android Wear (the one provided with the one Toolbox someone made here) and let it update to the latest version again.
EpicLPer said:
We could try flashing an older version of Android Wear (the one provided with the one Toolbox someone made here) and let it update to the latest version again.
Click to expand...
Click to collapse
Nope I found it thank god. I had kept a backup of the awful stock kernel just in case when I was initially testing invisiblek's kernel. Luckily its still there in all its awful glory and I will share it here as when you boot up with the stock kernel the system auto flashes the stock recovery because thats how stock is for everything
Xmaster24 said:
Nope I found it thank god. I had kept a backup of the awful stock kernel just in case when I was initially testing invisiblek's kernel. Luckily its still there in all its awful glory and I will share it here as when you boot up with the stock kernel the system auto flashes the stock recovery because thats how stock is for everything
Click to expand...
Click to collapse
Btw. I tried going back to stock yesterday (without locking the bootloader tho) but I may have used a wrong or too old stock recovery version.
Also the only reason why the OTA is reporting an issue while flashing the package with the squashfs enabled TWRP is because the script gets a string back that's not identical with the one it expects. Maybe someone could "hack out" that check and make it TWRP flashable.
EpicLPer said:
Btw. I tried going back to stock yesterday (without locking the bootloader tho) but I may have used a wrong or too old stock recovery version.
Also the only reason why the OTA is reporting an issue while flashing the package with the squashfs enabled TWRP is because the script gets a string back that's not identical with the one it expects. Maybe someone could "hack out" that check and make it TWRP flashable.
Click to expand...
Click to collapse
No the problem is the TWRP was built on an old base of the LG G watch specifically the last 5.1.1 update so the zip thinks the whole system is still on 5.1.1 as TWRP is still on that. I don't think the 6.0.1 source has been released yet so I don't think a recovery could be built with a 6.0.1 base of the lg g watch.
Xmaster24 said:
No the problem is the TWRP was built on an old base of the LG G watch specifically the last 5.1.1 update so the zip thinks the whole system is still on 5.1.1 as TWRP is still on that.
Click to expand...
Click to collapse
That's exactly what I mean with the check and the "wrong" string it gets back I have no clue on how to disable this check inside the ZIP-script tho.
EpicLPer said:
That's exactly what I mean with the check and the "wrong" string it gets back I have no clue on how to disable this check inside the ZIP-script tho.
Click to expand...
Click to collapse
it's not worth it, just flash the stock boot.img once I upload it, waiting for the ART cache to build now
---------- Post added at 12:10 PM ---------- Previous post was at 12:05 PM ----------
xmaster24 said:
it's not worth it, just flash the stock boot.img once i upload it, waiting for the art cache to build now
Click to expand...
Click to collapse
omfg the new kernel actually has a hotplug!!!!!!!!!!!!!!!!!! Finally more than 1 core on stock!!!!!!!!!!!!!
Xmaster24 said:
it's not worth it, just flash the stock boot.img once I upload it, waiting for the ART cache to build now
---------- Post added at 12:10 PM ---------- Previous post was at 12:05 PM ----------
omfg the new kernel actually has a hotplug!!!!!!!!!!!!!!!!!! Finally more than 1 core on stock!!!!!!!!!!!!!
Click to expand...
Click to collapse
You mean the new OTA kernel or the 6.X kernels?
EpicLPer said:
You mean the new OTA kernel or the 6.X kernels?
Click to expand...
Click to collapse
the stock kernel and nvm it was just AIDA64 glitching out, actually thought more than one core was in use The upside it thought the reboot button is back! don't know why they ever removed it but collio
Xmaster24 said:
nvm it was just AIDA64 glitching out, actually thought more than one core was in use ;-(
Click to expand...
Click to collapse
I actually think there are more than 1 cores activate at a time now, the watch has gotten pretty fast with the latest updates and so on, I don't even feel the need for a custom kernel anymore since that.
EpicLPer said:
I actually think there are more than 1 cores activate at a time now, the watch has gotten pretty fast with the latest updates and so on, I don't even feel the need for a custom kernel anymore since that.
Click to expand...
Click to collapse
Nope after about 1 minute after boot the phone locks to 787mhz with userspace governor and I can confirm there is no CPU hotplug aswell. I don't know how you survive with the abysmal lag but ok cool. During the first minute of boot for whatever reason it uses 2 cores and ondemand, would rather have that always lol.
EpicLPer said:
We could try flashing an older version of Android Wear (the one provided with the one Toolbox someone made here) and let it update to the latest version again.
Click to expand...
Click to collapse
Tried, didn't work. My guess is that it didn't handle squash FS. I was left with dead Android guy on the screen
For everyone to enjoy HERE is the stock kernel, @EpicLPer add this to the op to save everyone some trouble. NOTE: you have to boot to system once before the stock recovery is restored. Also it is a twrp backup so you have to adb push it to /sdcard/TWRP/BACKUPS/ to use it. If someone could just get the boot.img raw that would be great, I was too lazy to do it lel.
Xmaster24 said:
Nope after about 1 minute after boot the phone locks to 787mhz with userspace governor and I can confirm there is no CPU hotplug aswell. I don't know how you survive with the abysmal lag but ok cool. During the first minute of boot for whatever reason it uses 2 cores and ondemand, would rather have that always lol.
Click to expand...
Click to collapse
Actually... mine's running pretty well, no lag, no freezing animations, apps take 1 second to open and scrolling is smooth too.
Either I have some leftovers of an old kernel (which I don't think, or, hope) or I'm having a magic LG Watch
XDA:DevDB Information
[STOCK] Official Moto G5 Cedric firmwares [TWRP], ROM for the Moto G5
Contributors
Livi-Tech
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP or TWRP 64 bit
Based On: Stock
Version Information
Status: Testing
Created 2018-02-03
Last Updated 2018-02-03
--Requirements--
TWRP or TWRP 64 bit
--Downloads--
( waiting for upload )
--Setting up--
Power off your Moto G5 device
hold volume down and power button to boot into bootloader
press volume down twice till it says RECOVERY MODE
press the power button to select
wait for twrp to start up
tap wipe
tap advanced wipe
tap Dalvik / ART cache
tap System
tap Data
tap Cache
drag the blue arrow to the right to wipe
tap back
tap the <I button to go back
tap the <I again to go back
--Installing--
tap Install
tap select storage
tap internal storage or sd card depending where you downloaded your twrp zip file
tap the zip file
drag the blue arrow to the right to confirm flash
( Testing Status by the way, i've only tested on my device so would like some others to test this method, if something does go wrong I have a Fastboot install method that has been confirmed working on different variations of the G5 Cedric
What's the point of this? Does it do something different?
aaronboy205 said:
What's the point of this? Does it do something different?
Click to expand...
Click to collapse
TWRP is a portable way
some people are scared of using fastboot + this way they can keep twrp without the firmware not liking it + the TWRP installation is much faster but this method is mainly for people who want to keep twrp without needing to modify anything, are scared of fastboot or want to do a quick install
aaronboy205 said:
What's the point of this? Does it do something different?
Click to expand...
Click to collapse
Sometimes people don't want to do all the steps for going back to stock so having a flashable zip it's a bit faster and easier.
@Livi-Tech when I did flashable stock people had issues getting zip booted so I disabled dm verity and force encrypt from kernel but you can attach this to the main post so people don't run into the same issues.
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.0.zip
Fedray said:
Sometimes people don't want to do all the steps for going back to stock so having a flashable zip it's a bit faster and easier.
Click to expand...
Click to collapse
It is, I wouldn't create something that didn't have a point to it, me personally I hate using fastboot because watching all the commands run kind of scares me a bit knowing something could go wrong
Fastboot
1) got to connect usb cable, open up command prompt, make sure the device is recognized
2) wrong command could mess stuff up
3) take ages
4) got to type in loads of commands
TWRP
1) portable method
2) automatic install
3) system doesn't play if you make modifications, flash any system modifying files, etc
4) much much faster than fastboot by miles
Fedray said:
Sometimes people don't want to do all the steps for going back to stock so having a flashable zip it's a bit faster and easier.
@Livi-Tech when I did flashable stock people had issues getting zip booted so I disabled dm verity and force encrypt from kernel but you can attach this to the main post so people don't run into the same issues.
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.0.zip
Click to expand...
Click to collapse
My TWRP versions have boot.img files with dm-verity already turned off and disabled, thank you though
Livi-Tech said:
TWRP is a portable way
some people are scared of using fastboot + this way they can keep twrp without the firmware not liking it + the TWRP installation is much faster but this method is mainly for people who want to keep twrp without needing to modify anything, are scared of fastboot or want to do a quick install
Click to expand...
Click to collapse
Oh okay thanks! ?
WAITING
I´m waiting for this.
Download links ??
Reserve threads arent allowed on xda afaik. Hurry up or thread gets blocked
Sonisudhanshu said:
Download links ??
Click to expand...
Click to collapse
My internet cut out last night so still uploading
I'm uploading directly to XDA that's why no download links are available yet
Thread closed, place holders NOT permitted. PM me when you are ready to post a download link.
Waiting download link yet... :/
Do you have link to this firmware please?
jason13v8 said:
Do you have link to this firmware please?
Click to expand...
Click to collapse
I already have a fastboot tutorial
go onto my profile
click on thread started by livi-tech
you should find one that says official moto G5 Cedric firmwares [Fastboot]
jason13v8 said:
Do you have link to this firmware please?
Click to expand...
Click to collapse
I'm shutting this thread down for a while
unless there is someone willing to test my twrp version
Livi-Tech said:
I'm shutting this thread down for a while
unless there is someone willing to test my twrp version
Click to expand...
Click to collapse
I'll look for link to twrp version and test it for you today. There's already a debloated stock zip file here on XDA I flashed yesterday. I'll let you know how it goes thanks
---------- Post added at 09:44 AM ---------- Previous post was at 09:35 AM ----------
Livi-Tech said:
I'm shutting this thread down for a while
unless there is someone willing to test my twrp version
Click to expand...
Click to collapse
You don't seem to have a twrp version for me to test, the only one I see in your profile is fastboot which I avoid at all cost.
jason13v8 said:
I'll look for link to twrp version and test it for you today. There's already a debloated stock zip file here on XDA I flashed yesterday. I'll let you know how it goes thanks
---------- Post added at 09:44 AM ---------- Previous post was at 09:35 AM ----------
You don't seem to have a twrp version for me to test, the only one I see in your profile is fastboot which I avoid at all cost.
Click to expand...
Click to collapse
why do you avoid fastboot ( I already know some reasons someone might but curious about your reasons )
you've used fastboot before to unlock bootloader?
I've even tried fastboot erase all and all it wiped was data, System, cache so my device was perfectly okay,the Moto G5 bootloader seems more protected than other phones
and no I don't I was going to upload one but I bumped into problems on my device ( unrelated )
Livi-Tech said:
why do you avoid fastboot ( I already know some reasons someone might but curious about your reasons )
you've used fastboot before to unlock bootloader?
I've even tried fastboot erase all and all it wiped was data, System, cache so my device was perfectly okay,the Moto G5 bootloader seems more protected than other phones
and no I don't I was going to upload one but I bumped into problems on my device ( unrelated )
Click to expand...
Click to collapse
I have used fastboot a few times with sumsung devices but at present I have windows 10 and seem to get nowhere with it and yes I unlocked my bootloader I used one click root company to root and flash twrp £29 i think it's an XDA set up thing you give them permission to take over your computer and even their engineer nearly gave up after about 2 hours. I have used kingroot and Odin many time and persisted until success but with Moto G5 I surrendered and got help for the sake of time and energy. Plus your original post I thought said it was for people who struggle with fastboot. Like I said there is a stock zip available and it worked via twrp. If you can't upload them should you not delete the thread? Thanks:good:
jason13v8 said:
I have used fastboot a few times with sumsung devices but at present I have windows 10 and seem to get nowhere with it and yes I unlocked my bootloader I used one click root company to root and flash twrp £29 i think it's an XDA set up thing you give them permission to take over your computer and even their engineer nearly gave up after about 2 hours. I have used kingroot and Odin many time and persisted until success but with Moto G5 I surrendered and got help for the sake of time and energy. Plus your original post I thought said it was for people who struggle with fastboot. Like I said there is a stock zip available and it worked via twrp. If you can't upload them should you not delete the thread? Thanks:good:
Click to expand...
Click to collapse
I need someone to test ( not just the normal it boots up test because I already know it boots up and everything works )
My bootloader already says status: modified and right now I have an IMEI problem which is preventing me from making and receiving calls/texts, I won't upload my versions until I know they aren't going to trip the bootloader status or cause the same call/text problems I have for people who flash it
which is why i'm looking for a tester who doesn't care if their bootloader changes from official to modified and doesn't care if they lose ability to call and text.
with your fastboot Issue, could you have a look on my instructions in my [fastboot] thread and tell me if you get fastboot to recognize your phone, i'm not asking you to flash anything, just asking if you could use those instructions and see if fastboot picks up your Moto G5, ( i'm curious as to why your having so much trouble as I am also on windows 10 ) also currently what rom are you using on your Moto G5?
Here's the deal,
1. I was on resurrection remix 7.1 custom rom with TWSRP recovery installed.
2. Wanted to go back to stock huawei honor 5x OS so I downloaded it on the internet, since I live in Malaysia, I searched for "Huawei Honor 5x Stock Rom Malaysia Variant"
3. Flash the rom, got EMUI 2.0 instead of the written EMUI 3.1 on the file (the file name is KIW-L22_C636B130_Firmware_Android 5.1_EMUI 3.1_Malaysia.zip"
4. Flashed HONOR_5X_Firmware_KIW-L22_Android 6.0.1_EMUI 4.0.1_C675B360CUSTC675D002.zip that I got from huawei's website
5. Stuck in bootloop.
6. I went into TWRP recovery and tried to do something but I couldn't use the touchscreen for some odd reason
7. Went and browsed XDA for around 2 hours and found that I can install another recovery that uses the volume buttons and the power buttons to navigate, thus I installed a recovery called "carliwm touch recovery"
8. Was happy could finally do something, successfully flashed the recovery. Went and downloaded Lineage OS rom based on my mistakes that I've done and never want to go back to stock rom.
9. The recovery has an option to mount the external sd card (my sd card in my phone, dont know why it's called as such), so I did, I still couldn't navigate using the touchscreen as it's disfunctional still but can still navigate using volume and power buttons.
10. Wiped all data, flashed Lineage OS, flashed GAPPS.
11. Stuck in recovery for some reason, can't get into my phone. I've re-flashed it many times
For those who want to know my phone model, it's KIW-L22. When it had stock rom it was EMUI 4 something, can't remember as it's very vague. I think it was marshmallow
Please help
EDIT:
I use Huawei Update Extractor to get into the stock rom that had EMUI 2.0, extracted the System and Recovery images
Used this video ( https://www.youtube.com/watch?v=EoZQHTidnGA&t=629s ) to flash back to stock rom that had EMUI 2.0
The only way to get out of the recovery is to reboot the phone
In the bootloader, it says "PHONE Unlocked" and "FRP Unlock"
UPDATE:
I've tried to follow the video again and re-flashed the stock rom with EMUI 2.0 and it still doesn't work
I've wiped everything in the phone using the recovery (wiped data and factory reset), going to sleep as it's 4:37 AM
This is what happens when you dont read the guides that are posted all over this forum, we have seen it so many times I have lost count and also the inclination to help sort out the mess, I would never ever in my life download any firmware that wasn't posted on XDA or flash a phone without reading guides on here first as they usually not only give the correct information but usually point to the correct firmware.
Beauty fades but stupid is forever...Judge Judy !
swukjay said:
This is what happens when you dont read the guides that are posted all over this forum, we have seen it so many times I have lost count and also the inclination to help sort out the mess, I would never ever in my life download any firmware that wasn't posted on XDA or flash a phone without reading guides on here first as they usually not only give the correct information but usually point to the correct firmware.
Beauty fades but stupid is forever...Judge Judy !
Click to expand...
Click to collapse
Well, sorry for my stupidity man, not everyone's perfect. Am I forever stuck like this?
TurtleKicks said:
Well, sorry for my stupidity man, not everyone's perfect. Am I forever stuck like this?
Click to expand...
Click to collapse
Your touchscreen isn't working and your getting a bootloop because you probably have the wrong boot.image this is clealy the case as your touch screen isn't working, if you search through my guides for al10 which i cant be bothered to get the link for now one of them has a link to a twrp image of what i rhink is l22, anyway its a twrp image, you can flash that using twrp and it should restore your phone, good luck
---------- Post added at 04:03 AM ---------- Previous post was at 03:56 AM ----------
https://forum.xda-developers.com/honor-5x/how-to/solution-to-downgrade-netcom-al10-3gb-t3718355
This is for the AL10 but should be of use to you, download the twrp image, you will need to make a backup first of your phone then follow the instructions, you cant restore using a update.app as you have wrecked the system image and ruined the version check so this is your best hope to reatore tour phone and install lineage, good luck
---------- Post added at 04:04 AM ---------- Previous post was at 04:03 AM ----------
swukjay said:
Your touchscreen isn't working and your getting a bootloop because you probably have the wrong boot.image this is clealy the case as your touch screen isn't working, if you search through my guides for al10 which i cant be bothered to get the link for now one of them has a link to a twrp image of what i rhink is l22, anyway its a twrp image, you can flash that using twrp and it should restore your phone, good luck
---------- Post added at 04:03 AM ---------- Previous post was at 03:56 AM ----------
https://forum.xda-developers.com/honor-5x/how-to/solution-to-downgrade-netcom-al10-3gb-t3718355
This is for the AL10 but should be of use to you, download the twrp image, you will need to make a backup first of your phone then follow the instructions, you cant restore using a update.app as you have wrecked the system image and ruined the version check so this is your best hope to reatore tour phone and install lineage, good luck
Click to expand...
Click to collapse
In your case tick everything including modem But dont tick EFS
swukjay said:
Your touchscreen isn't working and your getting a bootloop because you probably have the wrong boot.image this is clealy the case as your touch screen isn't working, if you search through my guides for al10 which i cant be bothered to get the link for now one of them has a link to a twrp image of what i rhink is l22, anyway its a twrp image, you can flash that using twrp and it should restore your phone, good luck
---------- Post added at 04:03 AM ---------- Previous post was at 03:56 AM ----------
https://forum.xda-developers.com/honor-5x/how-to/solution-to-downgrade-netcom-al10-3gb-t3718355
This is for the AL10 but should be of use to you, download the twrp image, you will need to make a backup first of your phone then follow the instructions, you cant restore using a update.app as you have wrecked the system image and ruined the version check so this is your best hope to reatore tour phone and install lineage, good luck
---------- Post added at 04:04 AM ---------- Previous post was at 04:03 AM ----------
In your case tick everything including modem But dont tick EFS
Click to expand...
Click to collapse
sorry but im using a CWM based recovery right now, its this one https://forum.xda-developers.com/showthread.php?t=2471479 cause i cant touch anything i read somewhere that they recommend using this when theres no touch functionality
EDIT: I've done what you told me based on your guide, still doesn't work, probably cause I'm using the CWM based recovery
Dan Ger said:
Hey man im from Malaysia too,im sorry for you because right now you got bricked your device.. eventually when you already flash 4.1 emui you cant go back to stock rom...
And you have flash wrong system number for our Malaysian version..i cant help
Click to expand...
Click to collapse
So there's no hope for me? If I were to send it to a phone repair shop, it won't do anything?
TurtleKicks said:
sorry but im using a CWM based recovery right now, its this one https://forum.xda-developers.com/showthread.php?t=2471479 cause i cant touch anything i read somewhere that they recommend using this when theres no touch functionality
Click to expand...
Click to collapse
Then you will need to use adb to flash the boot partition, you have a major job on your hands which will be especially difficult for a noob, this is why its best to read the guides !
swukjay said:
Then you will need to use adb to flash the boot partition, you have a major job on your hands which will be especially difficult for a noob, this is why its best to read the guides !
Click to expand...
Click to collapse
is this website trustable? https://android.****************/ho...actory-images-android-using-fastboot-0175277/ as a guide
huh nevermind, its censored, then do you have any idea how to flash the boot partition?
This will be my last instructions then the rest is down to you..
Download minimal adb and unzip it
Download Huawei extractor tool
Download stock update.apo for any honor 5x
Use huawei extractor and open update.app with it
Extract boot.img
Place e boot.img in minimal adb folder
Download hiapp from web
Install hiapp
Plug phone into computer in adb mode
Open adb command window
Type adb devices to check its there
Type fastboot flash boot boot.img
Then install twrp
Fastboot flash recovery twrp.img "or whatever file name it is"
No fastboot reboot recovery
Now install lineage
Now hit the thanks button and write a guide on why guides are important
swukjay said:
This will be my last instructions then the rest is down to you..
Download minimal adb and unzip it
Download Huawei extractor tool
Download stock update.apo for any honor 5x
Use huawei extractor and open update.app with it
Extract boot.img
Place e boot.img in minimal adb folder
Download hiapp from web
Install hiapp
Plug phone into computer in adb mode
Open adb command window
Type adb devices to check its there
Type fastboot flash boot boot.img
Then install twrp
Fastboot flash recovery twrp.img "or whatever file name it is"
No fastboot reboot recovery
Now install lineage
Now hit the thanks button and write a guide on why guides are important
Click to expand...
Click to collapse
I did everything that you told me but I still dont have touchscreen functions in TWRP. I used the boot.img from HONOR_5X_Firmware_KIW-L22_Android 6.0.1_EMUI 4.0.1_C675B360CUSTC675D002
TurtleKicks said:
I did everything that you told me but I still dont have touchscreen functions in TWRP. I used the boot.img from HONOR_5X_Firmware_KIW-L22_Android 6.0.1_EMUI 4.0.1_C675B360CUSTC675D002
Click to expand...
Click to collapse
Your last option is e-recovery
swukjay said:
Your last option is e-recovery
Click to expand...
Click to collapse
im very sorry but what's e-recovery?
https://m.youtube.com/watch?v=CHjL2AIQXKw
Follow the instructions and use erecovery to dowload latest rom
---------- Post added at 08:21 AM ---------- Previous post was at 08:21 AM ----------
Bet you wish you read those guides now !
swukjay said:
https://m.youtube.com/watch?v=CHjL2AIQXKw
Follow the instructions and use erecovery to dowload latest rom
---------- Post added at 08:21 AM ---------- Previous post was at 08:21 AM ----------
Bet you wish you read those guides now !
Click to expand...
Click to collapse
boy i wish i read those guides. Okay I got into e-recovery and im using the power buttons to navigate through the menu, I use my power button to select the "Download latest version and recovery." and got into the wifi section, pressed download recovery and its starting to Connect to Wifi. Now I'm stuck in selecting wifi. I cant even use my power buttons to choose my wifi but i can choose the back option using the volume and power keys, what do i do now?
TurtleKicks said:
boy i wish i read those guides. Okay I got into e-recovery and im using the power buttons to navigate through the menu, I use my power button to select the "Download latest version and recovery." and got into the wifi section, pressed download recovery and its starting to Connect to Wifi. Now I'm stuck in selecting wifi. I cant even use my power buttons to choose my wifi but i can choose the back option using the volume and power keys, what do i do now?
Click to expand...
Click to collapse
Probably not working because boot.img is messed up, you cant have flashed it right, you only option is to try flashing each partition with the extracted files and hope it works and if it doesnt return it to a service center, im out of ideas im afraid, i flashed my boot.img before and it worked when i had no touch screen, didnt you make a backup before you messed with the phone ? Could end up being a expensive mistake, maybe try other boot.img or ask someone on here with a l24 for a copy of their boot.img but without that your screwed as it cant load the touchscreen drivers.
---------- Post added at 08:38 AM ---------- Previous post was at 08:36 AM ----------
swukjay said:
Probably not working because boot.img is messed up, you cant have flashed it right, you only option is to try flashing each partition with the extracted files and hope it works and if it doesnt return it to a service center, im out of ideas im afraid, i flashed my boot.img before and it worked when i had no touch screen, didnt you make a backup before you messed with the phone ? Could end up being a expensive mistake, maybe try other boot.img or ask someone on here with a l24 for a copy of their boot.img but without that your screwed as it cant load the touchscreen drivers.
Click to expand...
Click to collapse
Doesnt the touchscreen work now to select the wifi? If you can see it you should be able to select it, i cant suggest any more its down to you now
swukjay said:
Probably not working because boot.img is messed up, you cant have flashed it right, you only option is to try flashing each partition with the extracted files and hope it works and if it doesnt return it to a service center, im out of ideas im afraid, i flashed my boot.img before and it worked when i had no touch screen, didnt you make a backup before you messed with the phone ? Could end up being a expensive mistake, maybe try other boot.img or ask someone on here with a l24 for a copy of their boot.img but without that your screwed as it cant load the touchscreen drivers.
Click to expand...
Click to collapse
sorry but what's the L24? You've mentioned that for a while now. I'm using the Huawei Honor 5X, model KIW-L22, not L24. Nevertheless, does that affect what I'm doing right now?
swukjay said:
Probably not working because boot.img is messed up, you cant have flashed it right, you only option is to try flashing each partition with the extracted files and hope it works and if it doesnt return it to a service center, im out of ideas im afraid, i flashed my boot.img before and it worked when i had no touch screen, didnt you make a backup before you messed with the phone ? Could end up being a expensive mistake, maybe try other boot.img or ask someone on here with a l24 for a copy of their boot.img but without that your screwed as it cant load the touchscreen drivers.
---------- Post added at 08:38 AM ---------- Previous post was at 08:36 AM ----------
Doesnt the touchscreen work now to select the wifi? If you can see it you should be able to select it, i cant suggest any more its down to you now
Click to expand...
Click to collapse
Touchscreen doesn't work at all, can't do anything except for navigating using the power buttons
TurtleKicks said:
sorry but what's the L24? You've mentioned that for a while now. I'm using the Huawei Honor 5X, model KIW-L22, not L24. Nevertheless, does that affect what I'm doing right now?
Click to expand...
Click to collapse
Should all be the same, all use the same cpu so drivers should all be the same, as i said I cant do any more now if erecovery isnt working and you have no touch screen after flashing boot.img your in the poop, send it to a service center
---------- Post added at 08:44 AM ---------- Previous post was at 08:42 AM ----------
Personally i dont think you flashed the boot.img correctly but there we go
---------- Post added at 08:49 AM ---------- Previous post was at 08:44 AM ----------
swukjay said:
Should all be the same, all use the same cpu so drivers should all be the same, as i said I cant do any more now if erecovery isnt working and you have no touch screen after flashing boot.img your in the poop, send it to a service center
---------- Post added at 08:44 AM ---------- Previous post was at 08:42 AM ----------
Personally i dont think you flashed the boot.img correctly but there we go
Click to expand...
Click to collapse
L22
https://www.hihonor.com/in/support/details/
---------- Post added at 08:52 AM ---------- Previous post was at 08:49 AM ----------
May also help,
https://www.google.co.uk/amp/s/foru...ds-to-stock-rom-flashing-custom-t3358468/amp/
Cant do no more now its down to you... get that boot.img to flash and your touchscreen will work then your problem is solved.... Good luck !
swukjay said:
Should all be the same, all use the same cpu so drivers should all be the same, as i said I cant do any more now if erecovery isnt working and you have no touch screen after flashing boot.img your in the poop, send it to a service center
---------- Post added at 08:44 AM ---------- Previous post was at 08:42 AM ----------
Personally i dont think you flashed the boot.img correctly but there we go
---------- Post added at 08:49 AM ---------- Previous post was at 08:44 AM ----------
L22
https://www.hihonor.com/in/support/details/
---------- Post added at 08:52 AM ---------- Previous post was at 08:49 AM ----------
May also help,
https://www.google.co.uk/amp/s/foru...ds-to-stock-rom-flashing-custom-t3358468/amp/
Cant do no more now its down to you... get that boot.img to flash and your touchscreen will work then your problem is solved.... Good luck !
Click to expand...
Click to collapse
Oh my God! I rebooted the phone, pressed the volume up button then BAM the phone boots into Lineage OS! Touchscreen is working, everything is working! Thanks for your help! Making the guide on why reading guides are important haha!
TurtleKicks said:
Oh my God! I rebooted the phone, pressed the volume up button then BAM the phone boots into Lineage OS! Touchscreen is working, everything is working! Thanks for your help! Making the guide on why reading guides are important haha!
Click to expand...
Click to collapse
Nice one glad its working
---------- Post added at 12:02 PM ---------- Previous post was at 12:00 PM ----------
Dont forget to MAKE A BACKUP !