My phone is 10 months old and began bootlooping a few hours ago. I've kept it in a bootloop but it never booted neither system nor recovery.
It's still under warranty but I'll keep it a few days to try a few things. I'm going on vacation next week so I'll be without phone 10 months is just unacceptable from a QA point of view from Huawei and Google. Anyway...
Up to now I get mixed results: I can boot in recovery but can't fully boot. I'll try a few others way (either kernels or parameters) later during the weekend and update this post.
Boot image includes the kernel from O DP3 and recovery image the kernel from twrp 3.1.0.0. Current method is to limit the kernel to use less cores.
If your device is affected by the Boot Loop Of Death, you might try flashing this image to backup your data.
Twrp image:
twrp_3.1.1-bootloop (four cores)
Source code - Local manifest
https://github.com/architek/omnirom-twrp-angler_local-manifest
How to flash:
Reboot into bootloader mode (hold power + volume down)
unzip
fastboot flash recovery omni-7.1-twrp_3.1.1-bootloop.img
Feedback:
Tell me if that works out for you. Thanks.
Update
14th August : Binary link
21th August : Source code link
rchtk said:
My phone is 10 months old and began bootlooping a few hours ago. I've kept it in a bootloop but it never booted neither system nor recovery.
It's still under waranty but I'll keep it a few days to try a few things. I'm going on vacation next week so I'll be without phone 10 months is just unacceptable from a QA point of view from Huawei and Google. Anyway...
Up to now I get mixed results: I can boot in recovery but can't fully boot. I'll try a few others way (either kernels or parameters) later during the weekend and update this post.
Boot image includes the kernel from O DP3 and recovery image the kernel from twrp 3.1.0.0. Current method is limiting the kernel to use 1 cpu.
Urls:
Xtwrp-3.1.0-0-angler.img
Xboot-opp3.170518.006-0bc919b4.img
How to use:
Reboot into bootloader mode (hold power + volume down)
fastboot boot Ximage.img
Will boot you either in recovery or system depending on the image you use.
Feedback:
Tell me if that works out for you. Thanks.
Click to expand...
Click to collapse
The best thing to do is to follow this method at either step 9 or step 10. https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
DEVILOPS 007 said:
The best thing to do is to follow this method at either step 9 or step 10. https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Explain how it is better than what I posted.
rchtk said:
Explain how it is better than what I posted.
Click to expand...
Click to collapse
Because you didn't share what link you were using information from and you didn't say that you tried following everything like flashing the system, boot, recovery, bootloader, vendor etc as that is what needed to fix bigger bricks. Also, you didn't take into account different factors like some things might not work making your method impossible. I'm not saying your method won't work for that certain situation but the link I posted is to one of the biggest people on xda as far as I know with an almost foolproof plan to fix bricks unless it is the blod.
DEVILOPS 007 said:
Because you didn't share what link you were using information from and you didn't say that you tried following everything like flashing the system, boot, recovery, bootloader, vendor etc as that is what needed to fix bigger bricks. Also, you didn't take into account different factors like some things might not work making your method impossible. I'm not saying your method won't work for that certain situation but the link I posted is to one of the biggest people on xda as far as I know with an almost foolproof plan to fix bricks unless it is the blod.
Click to expand...
Click to collapse
Yes, obviously, my post is for people experiencing blod. If you don't then you don't need these images.
The recovery image is not even flashed, its executed in RAM and allowed me to access my filesystem.
The system image goes up to moving dots but doesn't finish booting.
rchtk said:
Yes, obviously, my post is for people experiencing blod. If you don't then you don't need these images.
The recovery image is not even flashed, its executed in RAM and allowed me to access my filesystem.
The system image goes up to moving dots but doesn't finish booting.
Click to expand...
Click to collapse
If it was a blod then your method wouldn't actually work. Your post helps with with something worse than a soft brick but not the infamous proper hard brick blod.
DEVILOPS 007 said:
If it was a blod then your method wouldn't actually work. Your post helps with with something worse than a soft brick but not the infamous proper hard brick blod.
Click to expand...
Click to collapse
The whole post is not about if it works or not. IT DOES WORK to get to recovery on my device which has a BLOD :silly:
Got it?
If you don't need these images, respects others and just don't post in this thread. I'm waiting for feedback on if it works on others too.
rchtk said:
The whole post is not about if it works or not. IT DOES WORK to get to recovery on my device which has a BLOD :silly:
Got it?
If you don't need these images, respects others and just don't post in this thread. I'm waiting for feedback on if it works on others too.
Click to expand...
Click to collapse
I'm just saying that it doesn't work that often lying and the blod doesn't even let you get to recovery anyway but whatever. Believe whatever, believe what you want.
rchtk said:
My phone is 10 months old and began bootlooping a few hours ago. I've kept it in a bootloop but it never booted neither system nor recovery.
It's still under waranty but I'll keep it a few days to try a few things. I'm going on vacation next week so I'll be without phone 10 months is just unacceptable from a QA point of view from Huawei and Google. Anyway...
Up to now I get mixed results: I can boot in recovery but can't fully boot. I'll try a few others way (either kernels or parameters) later during the weekend and update this post.
Boot image includes the kernel from O DP3 and recovery image the kernel from twrp 3.1.0.0. Current method is to limit the kernel to use less cores.
Urls:
Xtwrp-3.1.0-0-2-angler.img
Xboot-opp3.170518.006-0bc919b4.img
How to use:
Reboot into bootloader mode (hold power + volume down)
fastboot boot Ximage.img
Will boot you either in recovery or system depending on the image you use.
Feedback:
Tell me if that works out for you. Thanks.
Click to expand...
Click to collapse
Ok, so I got it booted to the TWRP 3.1.0.0 from your post but I can't see any of my files. I had TWRP 3.0.3.0 installed.
What do I do next?
I haven't tried the other image yet. I'm just excited to see what my battery percentage is so I know if I'm in the 6-9% range as mentioned in the other thread about this problem.
---------- Post added at 06:45 PM ---------- Previous post was at 06:25 PM ----------
Ok, so I just tried the opp file and it's booted up to the Google logo and stops.
outbackpaul said:
Ok, so I got it booted to the TWRP 3.1.0.0 from your post but I can't see any of my files. I had TWRP 3.0.3.0 installed.
What do I do next?
I haven't tried the other image yet. I'm just excited to see what my battery percentage is so I know if I'm in the 6-9% range as mentioned in the other thread about this problem.
Click to expand...
Click to collapse
Glad it also works for you. Well that's weird that you don't see your files under /data .
Can you try to mount /data (and maybe open shell and issue dmesg) ? Were you encrypted?
That looks similar to me. Mine was encrypted and it actually failed to decrypt it. So I formated it in the hope that it would help to boot.
---------- Post added at 06:45 PM ---------- Previous post was at 06:25 PM ----------
Click to expand...
Click to collapse
Ok, so I just tried the opp file and it's booted up to the Google logo and stops.
Click to expand...
Click to collapse
With a modified ramdisk to remove ciphering and dm-verity, mine fails right away. With the boot img I posted, the moving dots show for like 5 minutes (creating cipher metadata?) so most of the partitions are mounted but it cannot fully boot.
I did a simple check of the emmc (dding mmc to /dev/null) which is ok but I actually need to compile a pattern write and read to confirm that.
Unfortunatly, I have no USB to serial device to see eventual kernel logs.
psycho-punk said:
Also, what are the modifications done to this recovery and boot image?
Click to expand...
Click to collapse
"Boot image includes the kernel from O DP3 and recovery image the kernel from twrp 3.1.0.0. Current method is to limit the kernel to use less cores."
I have several kernels with different modifications but the original ones are actually the ones that work better. These are original kernels but called with a maxcpus parameters (isolcpu would fit better but doesn't seem to do the job).
The recovery I posted is 5 cpus IIRC, its fast enough and works from RAM but not always when flashed. Flashing a recovery when cpu is lowered to 1 always works.
Again, on MY device, might not be the same for you.
Edit: links worked with proxy
Click to expand...
Click to collapse
Weird that going through a proxy helps. Whatever.
I'll try a few others things in the next days but I'm sending the device on Thursday at the latest... I'll try to get in touch with some kernel devs. Any idea is welcome!
psycho-punk said:
Tried booting the images. Unfortunately, both of them didn't work for me.
Sent from my XT1092 using Tapatalk
Click to expand...
Click to collapse
You fastboot boot Xrecovery and it didn't boot? fastboot flash followed by rebooting into recovery might not work.
This evening, I'll post one which limits to only one core.
For the system one, it has more requirements. Not sure if there is backward compatiblity (being able to start an old ROM/vendor with a very recent kernel).
I tried so many things. Only not the oven yet
rchtk said:
Glad it also works for you. Well that's weird that you don't see your files under /data .
Can you try to mount /data (and maybe open shell and issue dmesg) ? Were you encrypted?
That looks similar to me. Mine was encrypted and it actually failed to decrypt it. So I formated it in the hope that it would help to boot.
With a modified ramdisk to remove ciphering and dm-verity, mine fails right away. With the boot img I posted, the moving dots show for like 5 minutes (creating cipher metadata?) so most of the partitions are mounted but it cannot fully boot.
I did a simple check of the emmc (dding mmc to /dev/null) which is ok but I actually need to compile a pattern write and read to confirm that.
Unfortunatly, I have no USB to serial device to see eventual kernel logs.
Click to expand...
Click to collapse
I'm pretty sure I was encrypted. I don't have the phone with me at the moment.
So, if it's encrypted am I out of luck?
When it booted to TWRP it asked for a passcode. I just hit cancel. Is that what will let me see my data?
outbackpaul said:
I'm pretty sure I was encrypted. I don't have the phone with me at the moment.
So, if it's encrypted am I out of luck?
When it booted to TWRP it asked for a passcode. I just hit cancel. Is that what will let me see my data?
Click to expand...
Click to collapse
So you're in the same boat as me (hope you had backups like me).
Twrp 3.1 should be able to decrypt /data with the correct password. I guess it first tries with default_password and if a known pattern is not detected it asks for your passcode (pin to boot by default) until it succeeds.
But for me (encrypted with pin to boot), twrp wasn't able to decrypt. In my tests once I format /data, it gets encrypted again and twrp again fails to decrypt the partition.
Can you try with pass "default_password" (without quotes) or your pin to boot if you had set one?
Also do the same after flashing the one core version I just posted and rebooting into it.
psycho-punk said:
Eagerly waiting to try the one core only recovery.
Click to expand...
Click to collapse
http://dl.free.fr/oIkytaKDF
outbackpaul said:
I'm pretty sure I was encrypted. I don't have the phone with me at the moment.
So, if it's encrypted am I out of luck?
When it booted to TWRP it asked for a passcode. I just hit cancel. Is that what will let me see my data?
Click to expand...
Click to collapse
You should also try to *flash* the one core version and see if you're able to decrypt your data with it.
rchtk said:
So you're in the same boat as me (hope you had backups like me).
Twrp 3.1 should be able to decrypt /data with the correct password. I guess it first tries with default_password and if a known pattern is not detected it asks for your passcode (pin to boot by default) until it succeeds.
But for me (encrypted with pin to boot), twrp wasn't able to decrypt. In my tests once I format /data, it gets encrypted again and twrp again fails to decrypt the partition.
Can you try with pass "default_password" (without quotes) or your pin to boot if you had set one?
Also do the same after flashing the one core version I just posted and rebooting into it.
Click to expand...
Click to collapse
I don't even remember putting in a pin but I've tried every one that I remember ever using.
psycho-punk said:
One core version didn't work either. Guess I'm out of options.
Sent from my XT1092 using Tapatalk
Click to expand...
Click to collapse
It would be interesting to start from the same configuration by using the O DP3 factory image script flash-all.sh (removing -w if you want to keep your data).
Progress:
The fact that twrp can't decrypt data with the correct password is not understood. I'm getting a KM_ERROR_KEY_NOT_YET_VALID error message. Which is rather weird.
KM_TAG_ACTIVE_DATETIME requires comparison with a trusted UTC time source. If the current date and time is prior to the tag value, the method must return KM_ERROR_KEY_NOT_YET_VALID.
So I've formated /data, disabled encryption and verify and twrp sees my /data which is populated during system boot.
Regarding boot img, I've tried several things but I still fail to get past the jumping dots. It could be a consequence of the twrp problem about communication error with the keystore which has nothing to do with big cluster disabling (so there may be a general HW failure). I've tried playing a bit with big cluster settings but my attempts fail. Still a lot of things to try but I won't have much time in the next days.
Nexus 6p bootlooping just
Tried both did not work
command used
Fastboot flash boot Xboot-opp3.170518.006-0bc919b4.img
Fastboot flash recovery Xtwrp-3.1.0-0-angler.img
and
Fastboot boot Xtwrp-3.1.0-0-angler.img
not working
RIP
Game is over for me: I've let the phone charge at home and when trying to power it back, I just get a red blinking led. I always managed to power it back but this time not.
Which brings me to the conclusion that it looks power related. Battery, soldering, IC, motherboard (components are more prone to fail stop failures).
In the end, I've mostly changed kernel stuffs (and discovered a few kernel inconsistencies btw) but didn't have time to try a lot of things in userland nor investigate on the decryption failure.
My goal was just to get users to get back their data before throwing/sending back the brick.
So I'd suggest users to decrypt their /data before BLOD happens.
A bit frustrating but was fun anyway. Thanks to @Dees_Troy for the chat on IRC
Related
Installing now...
having a problem reinstalling TWRP. I followed all the commands and here is a copy of what Happens when I flash
C:\Users\Robert\Desktop\files\TWRP_for_mate2\TWRP_for_mate2>fastboot flash recovery twrp.img
target reported max download size of 804257792 bytes
sending 'recovery' (14382 KB)...
OKAY [ 0.469s]
writing 'recovery'...
OKAY [ 0.328s]
finished. total time: 0.797s
but when I try to boot into it it starts up the stock recovery. Any suggestions on how to install TWRP and make it stick or how to gain root because I mainly use TWRP for root.
I also get this screen sometimes when trying to boot into boot loader. The phone doesn't seem to vibrate like it does when it boots normally or loads recovery and boot loader.
http://imgur.com/IQlBmP1
The usb is connected but I haven't tried to send anything to the phone or told anything other than to reboot system when it boots into stock recovery. If I leave it , it just sits there doing nothing so I rebooted and it boots just fine. Should I try to reflash stock recovery and then flash TWRP?
Found a way to at least let the phone get using TWRP without apparently being able to boot into it for some reason. Don't know if you can backup and restore backups using this method but at least its a temporary workaround. I found it at this site https://aubykhan.wordpress.com/2013...t-into-twrp-or-cwm-recovery-without-flashing/. below is the guide copied from the site.
Prerequisites
•An unlocked bootloader – It is just a command away on Nexus devices. Google will give you very useful links depending on your device type.
•ADB with Fastboot – Check out this link: http://www.jailbreakeye.com/android/install-adb-fastboot
•A custom recovery image – TWRP or CWM (check the Download recovery or Download touch recovery columns)
Guide
1.Copy the downloaded recovery image (.img file) to the folder where you have placed your ADB and Fastboot.
2.Launch terminal (or command prompt on Windows).
3.Navigate to the directory where you have placed the ADB, Fastboot and .img file together.
4.Shut down your phone and reboot into boot loader. For nexus devices, simply hold volume down + power to start up the phone.
5.Connect your phone to your computer.
6.On terminal (or command prompt) window, write fastboot boot <img file name>, e.g. fastboot boot twrp.img.
7.Your phone will restart and will boot into the recovery mode.
That’s it. As simple as it can get!
Hopefully this will help out those who are having trouble getting into TWRP after updating to B321.
what new on the b321 updated
dizwikedcbr said:
what new on the b321 updated
Click to expand...
Click to collapse
It's very stable. Lots of things are now fixed. Getting 3rd party launcher to stick after reboot is now working. Actually, I have been using it as my daily driver for several days. Not even rebooted since install. This may be released to public, at least as the next preview.
Which launcher?
kimtyson said:
It's very stable. Lots of things are now fixed. Getting 3rd party launcher to stick after reboot is now working. Actually, I have been using it as my daily driver for several days. Not even rebooted since install. This may be released to public, at least as the next preview.
Click to expand...
Click to collapse
Which launcher are you using?
I installed B321 ...phone rebooted and is stuck on huawei logo screen. I can't get to fastboot or recovery. Help.
kimtyson said:
It's very stable. Lots of things are now fixed. Getting 3rd party launcher to stick after reboot is now working. Actually, I have been using it as my daily driver for several days. Not even rebooted since install. This may be released to public, at least as the next preview.
Click to expand...
Click to collapse
Nope. Still quite a few issues with notifications, led issues and issues with losing APN settings at random requiring a reboot. Sounds like you've just been lucky.
Have to consider user error. How many of those having issue are stock. Not rooted and LCD density changed etc. Not all issues are the fault of the rom. I am sure Huawei is taking that into consideration.
gale2000 said:
I installed B321 ...phone rebooted and is stuck on huawei logo screen. I can't get to fastboot or recovery. Help.
Click to expand...
Click to collapse
same happened with me. did the b321 ota and got stuck on boot screen. had to go back to b309 and now cant get back to b320.
How long did you let it run. It can take a good while on first boot...
I let it sit there so long i had forgotten about it all together. so at least 10-15 min on huawei splash screen. not the emul loading screen. i dont think a 30-40mb upgrade should take longer that it takes to load a complete image
---------- Post added at 01:17 AM ---------- Previous post was at 01:16 AM ----------
And when i search for updates now I get nothing... stuck on b309 i guess.
Moody66 said:
Have to consider user error. How many of those having issue are stock. Not rooted and LCD density changed etc. Not all issues are the fault of the rom. I am sure Huawei is taking that into consideration.
Click to expand...
Click to collapse
My phone is stock. Nothing added and no root. The issues are apparent and have been reported by other users, so the issues I have posted are NOT user error. A number of them have been confirmed as being fixed in the next release. 321 won't be the next release to the general public.
Confirmed fix in next release? Who is running the "next release"?
The b321 ota might be a good thing, but it's new enough that I am wary. I just upgraded to b320 less than a week ago and still haven't gotten everything situated on the phone. I've had some issues with Nova Prime launcher on power up. I have one question, er maybe two. What improvements if any make this new update a good choice and will I once again have to reload everything back onto my phone?
Moody66 said:
How long did you let it run. It can take a good while on first boot...
Click to expand...
Click to collapse
Overnight. If I power it off it turns itself right back on. Still stuck on splash screen...can't get to fastboot or recovery. Boo.
gale2000 said:
Overnight. If I power it off it turns itself right back on. Still stuck on splash screen...can't get to fastboot or recovery. Boo.
Click to expand...
Click to collapse
You have to put b320 or 309 update on the root of your sd card in folder named dload. do the three finger reset ( vol + vol- and PWR ) it will then install b320.
My guess is that you were still rooted when you updated, you have to be stock.
Davinci50 said:
You have to put b320 or 309 update on the root of your sd card in folder named dload. do the three finger reset ( vol + vol- and PWR ) it will then install b320.
My guess is that you were still rooted when you updated, you have to be stock.
Click to expand...
Click to collapse
Yes, I was rooted. Thanks for your help.
Harris.S.Newman said:
Which launcher are you using?
Click to expand...
Click to collapse
I am using Nova but Apex also stuck after reboot.
gale2000 said:
I installed B321 ...phone rebooted and is stuck on huawei logo screen. I can't get to fastboot or recovery. Help.
Click to expand...
Click to collapse
Sorry for your headaches. I have had no issues but I am using a clean install with no root or other magical add-ons.
TheIgster said:
Nope. Still quite a few issues with notifications, led issues and issues with losing APN settings at random requiring a reboot. Sounds like you've just been lucky.
Click to expand...
Click to collapse
You are correct about the notifications but that is an EMUI thing and they have no intentions (so far) of changing EMUI, so deal with it or get a notification add-on app. (Sorry for my bluntness.)
What LED issues?
My APN has been perfect. I am on ATT. Not sure what your APN issue might be but I'm not seeing others with APN issues.
No reboots for me and no need for reboots.
So, yeah, I'm lucky I guess. Or maybe I have a clean install without root. Or maybe I just know what I'm doing.
Moody66 said:
Confirmed fix in next release? Who is running the "next release"?
Click to expand...
Click to collapse
Confirmed on the Huawei website I've been posting on as well.
kimtyson said:
You are correct about the notifications but that is an EMUI thing and they have no intentions (so far) of changing EMUI, so deal with it or get a notification add-on app. (Sorry for my bluntness.)
What LED issues?
My APN has been perfect. I am on ATT. Not sure what your APN issue might be but I'm not seeing others with APN issues.
No reboots for me and no need for reboots.
So, yeah, I'm lucky I guess. Or maybe I have a clean install without root. Or maybe I just know what I'm doing.
Click to expand...
Click to collapse
Notifications were working fine on JB. There are issues since the update that need to be addressed. EMUI had it working just fine prior to the update to L.
There are no LED notifications for some notifications at times and I have yet to get a notification via the LED for Facebook. With and without a third party app.
The APN issues are documented and reported by other users. It is being fixed in the next release.
My install, yes, was not clean, but only an upgrade from 309. I have never had root. Yes, of course, you and Moody are experts and the rest of us are idiots. You both sure like to insinuate that in your posts. It's a little tiresome, but if it makes you feel better, I guess feel free.
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
I've been meaning to write this guide for a little while now, but I've only just gotten around to it. Basically, I had wanted to try the N preview, but TWRP didn't play nice with it, so until now, it has been impossible to run N with encryption, root, and without wiping your data. In the interest of full disclosure, I found the basis for this solution while down a Reddit rabbit hole in a very short post at the end of some thread that I've been unable to find again, so I can't take full credit. Many thanks to this random Redditor.
I originally posted this solution in another thread, but the tl;dr version is this: you have to wait to flash the vendor image from N until you're all done with twrp, but other than that, it's just like you're updating with a monthly security patch. This doesn't require any sort of toolkits or anything else either, so that's always a plus. I'm assuming this would work on the N5X as well, but I don't have one to test this on.
1. Download the factory image of DP4 from here.
2. We're basically going to be following step 9 of @Heisenberg 's guide. So unzip the download as you normally would to update your security patch, and put it in the directory you normally would.
3. Now flash everything EXCEPT the recovery and vendor image. I've copied the code from Heisenberg's guide here for your convenience so you don't have to keep switching pages. If you're going to copy and paste that into your command prompt, don't forget to take out the images I listed.
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
Click to expand...
Click to collapse
4. Now that that's done, we're going to go to your phone. Use the fastboot menu to boot into twrp. At this point, you should be able to enter your lock pattern/pin/whatever, and then flash SuperSu as you normally would. IIRC, you'll need v2.74 or higher, which you can download from here.
5. Now using twrp, reboot back into your bootloader. Fastboot flash the DP4 vendor image that we left out earlier, otherwise your phone won't boot.
That's it! You can now boot into system, and you'll be running Nougat DP4! The first boot took a while, and looped a couple timed for me, but it worked, and I've been running DP4 without wiping my data, without decrypting, and with root for a couple weeks. Remember, twrp won't work with the N vendor image installed, so if you want to use twrp again, you'll have to reflash the M vendor image, and then reflash the N one after you're all done. I haven't tried this yet, but that's what I intend to do when it comes time to update to DP5, whenever Google releases that. Happy flashing!
UPDATE: Confirmed, this method does work to update to DP5 from DP4.
Reserved
I'm going to try this.
Really want root on my sh**t.
But, theoretically, when DP5 is out, you'll have to do everything again, but with the Vendor image from DP5?
asj0422 said:
3. Now flash everything EXCEPT the recovery and vendor image. I've copied the code from Heisenberg's guide here for your convenience so you don't have to keep switching pages. If you're going to copy and paste that into your command prompt, don't forget to take out the images I listed.
Click to expand...
Click to collapse
By how some people roll around these forums, I'd remove the lines from the copy/paste box-thingy you did... haha.
Edit: fell on my a**. Reminder for me to be more helpful
Quite honestly if someone needs a guide they don't need to be flashing.
They need to do the proper research and understand what each image is. Just my opinion
Sent from my Nexus 6P using Tapatalk
superchilpil said:
Quite honestly if someone needs a guide they don't need to be flashing.
They need to do the proper research and understand what each image is. Just my opinion
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I agree on this, but you know how it is, people just come in, ask, find, copy/paste and that's it.
1day old accounts with 2/3 posts.
Edit: fell from my pedestal, note to self: be more helpful.
asj0422 said:
I've been meaning to write this guide for a little while now, but I've only just gotten around to it. Basically, I had wanted to try the N preview, but TWRP didn't play nice with it, so until now, it has been impossible to run N with encryption, root, and without wiping your data. In the interest of full disclosure, I found the basis for this solution while down a Reddit rabbit hole in a very short post at the end of some thread that I've been unable to find again, so I can't take full credit. Many thanks to this random Redditor.
I originally posted this solution in another thread, but the tl;dr version is this: you have to wait to flash the vendor image from N until you're all done with twrp, but other than that, it's just like you're updating with a monthly security patch. This doesn't require any sort of toolkits or anything else either, so that's always a plus. I'm assuming this would work on the N5X as well, but I don't have one to test this on.
1. Download the factory image of DP4 from here.
2. We're basically going to be following step 9 of @Heisenberg 's guide. So unzip the download as you normally would to update your security patch, and put it in the directory you normally would.
3. Now flash everything EXCEPT the recovery and vendor image. I've copied the code from Heisenberg's guide here for your convenience so you don't have to keep switching pages. If you're going to copy and paste that into your command prompt, don't forget to take out the images I listed.
4. Now that that's done, we're going to go to your phone. Use the fastboot menu to boot into twrp. At this point, you should be able to enter your lock pattern/pin/whatever, and then flash SuperSu as you normally would. IIRC, you'll need v2.74 or higher, which you can download from here.
5. Now using twrp, reboot back into your bootloader. Fastboot flash the DP4 vendor image that we left out earlier, otherwise your phone won't boot.
That's it! You can now boot into system, and you'll be running Nougat DP4! The first boot took a while, and looped a couple timed for me, but it worked, and I've been running DP4 without wiping my data, without decrypting, and with root for a couple weeks. Remember, twrp won't work with the N vendor image installed, so if you want to use twrp again, you'll have to reflash the M vendor image, and then reflash the N one after you're all done. I haven't tried this yet, but that's what I intend to do when it comes time to update to DP5, whenever Google releases that. Happy flashing!
Click to expand...
Click to collapse
Kudos. Always good to have a write up with steps for folks. Thanks for contributing. [emoji6]
Thanks for this post; I think it really helps having a quick reference for something like this. I can confirm that if you need to re-access TWRP, you can just flash the marshmallow vendor.img over adb, boot to TWRP, do what you have to do, return to bootloader, flash the nougat vendor.img in adb, and continue using your device. I had to use TWRP to flash the Adaway systemless support zip and doing that sequence I listed above worked as expected. It's not as ideal as having TWRP function with an encrypted device as it does on marshmallow, but at least it works.
superchilpil said:
Quite honestly if someone needs a guide they don't need to be flashing.
They need to do the proper research and understand what each image is. Just my opinion
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
benleonheart said:
I agree on this, but you know how it is, people just come in, ask, find, copy/paste and that's it.
1day old accounts with 2/3 posts.
Click to expand...
Click to collapse
I hope you guys don't fall off your pedestal way up there above everyone else.
Everyone has to learn somewhere and the guide above is a nice start for the noobiez on the forum.
SyCoREAPER said:
I hope you guys don't fall off your pedestal way up there above everyone else.
Everyone has to learn somewhere and the guide above is a nice start for the noobiez on the forum.
Click to expand...
Click to collapse
Worry not, dear friend as I was also a noob back in '08/'09.
We all learn new things every day. I'm just saying that there are dedicated threads to help with newcomers and guide them step by step.
Edit: You're right. Thanks.
When booting into twrp, will it prompt you for a pin/password? I never set one and I'm afraid it will make me have to completely wipe my phone.
Sent from my Nexus 6P using XDA-Developers mobile app
Sweet! This was easy peasy and didn't lose my data. No serious issues, either. Thanks for sharing this info.
Cheers
Sent from my Nexus 6P using XDA-Developers mobile app
crossen0 said:
When booting into twrp, will it prompt you for a pin/password? I never set one and I'm afraid it will make me have to completely wipe my phone.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
To be honest, I'm not sure. I've never had to deal with twrp and no password. I wouldn't think it would reset anything; I assume you just won't have to enter a password..?
What do you normally do for twrp?
thanks for the guide. Do you think if I'm already on DP4 I could flash the vendor image from an M build and continue from there?
edit: it worked!
Thank you this worked like a charm! Switched from a rooted+busybox stock build to rooted DP4. Now waiting for DP5
No problem! Glad it worked for you!
asj0422 said:
No problem! Glad it worked for you!
Click to expand...
Click to collapse
Just upgraded from my stock M + rooted + busy boxed + xposed build to DP5. TWRP and SU both working. Thanks for the guide.
Just updated to DP5 using this method (all flashes but vendor and recovery, flash M vendor, boot into TWRP, root, reboot to bootloader, flash DP5 vendor). Works perfect.
Works on un-encrypted as well. Flashed bootloader, radio, boot, cache and system, reboot TWRP to allow modification-back to bootloader and flashed modified boot.img. Then boot to TWRP, adb sideload SuperSU-2.76, reboot bootloader and flash vendor.img then reboot system. Profit! Still unencrypted with no loss of data and root retained.
mtw4991 said:
Works on un-encrypted as well. Flashed bootloader, radio, boot, cache and system, reboot TWRP to allow modification-back to bootloader and flashed modified boot.img. Then boot to TWRP, adb sideload SuperSU-2.76, reboot bootloader and flash vendor.img then reboot system. Profit! Still unencrypted with no loss of data and root retained.
Click to expand...
Click to collapse
Thanks for the extra info!
Question: doesn't twrp work with N as it did with M if you're not encrypted? I thought the issue with twrp and N was due to twrp's code not being able to decrypt - and that was the whole reason people were using the modified boot.img and decrypting was so twrp would work.
I can also confirm that this works with DP5. Will be updating OP shortly.
So I have a twrp that will boot but has no touch on mouse support right now I only boot it do not install it it will boot loop your device use fastboot boot recovery.img
svoc said:
So I have a twrp that will boot but has no touch on mouse support right now I only boot it do not install it it will boot loop your device use fastboot boot recovery.img
Click to expand...
Click to collapse
Thank you so much!! Very happy to finally have write access to /system! Nice work!
I'm just hoping we get some ROM support on this phone. I always run gappless. Lol.
svoc said:
So I have a twrp that will boot but has no touch on mouse support right now I only boot it do not install it it will boot loop your device use fastboot boot recovery.img
Click to expand...
Click to collapse
Yo just curious can you explain to me how you built this i cant seem to get it build rigjt or send me your source files
svoc said:
So I have a twrp that will boot but has no touch on mouse support right now I only boot it do not install it it will boot loop your device use fastboot boot recovery.img
Click to expand...
Click to collapse
Sorry, but I have to ask. You say it's working but if it has no touch then how does it work? Command line?
arkansawdave74 said:
Sorry, but I have to ask. You say it's working but if it has no touch then how does it work? Command line?
Click to expand...
Click to collapse
would be presumably by way of a USB connected hub to attach a mouse and maybe a keyboard too, though there is another version of TWRP 3.5 which I've just gotten working on my xt2114-7 running 11. I also used it to flash magisk which appears installed but has yet to prompt me to give root perms to anything.... which seems odd. hmm.... anyway there's another TWRP in these forums that may do the trick https://forum.xda-developers.com/t/...o-android-11-based-updated-11-4-2021.4354855/ as far as I can tell this is only working on 11 currently and seems a bit touchy about the touchscreen driver when it first boots, but I did a fastboot flash magisk_boot.img and then did a fastboot boot into the TWRP, and from there I actually flashed the TWRP file from within the booted TWRP environment. That sounded more complicated than it is...
Here is a updated TWRP with everything working use at your own risk
treesus said:
would be presumably by way of a USB connected hub to attach a mouse and maybe a keyboard too, though there is another version of TWRP 3.5 which I've just gotten working on my xt2114-7 running 11. I also used it to flash magisk which appears installed but has yet to prompt me to give root perms to anything.... which seems odd. hmm.... anyway there's another TWRP in these forums that may do the trick https://forum.xda-developers.com/t/...o-android-11-based-updated-11-4-2021.4354855/ as far as I can tell this is only working on 11 currently and seems a bit touchy about the touchscreen driver when it first boots, but I did a fastboot flash magisk_boot.img and then did a fastboot boot into the TWRP, and from there I actually flashed the TWRP file from within the booted TWRP environment. That sounded more complicated than it is...
Click to expand...
Click to collapse
Oh. My bad, man. I had misread the dude's typo. It says, "no touch on mouse support," and I thought he'd meant to say "or," but I later realized that he'd meant to say "only." It apparently has mouse support.I broke my Power 2021 right after I got it, but I did get it rooted using this twrp in an adb shell to pull my kernel because the kernels in the lolinet firmwares, after patching, caused the 2021 to lose touch functionality completely. But, even though it's the same damned kernel, when you pull it with:
"adb shell"
"twrp backup B"
it will make a backup in the usual spot in internal storage (/sdcard/TWRP). Go in there and find the file and rename it to boot.img (or something like twrpdboot.img to keep it from being confused with the other boot images) and if you patch that one with magisk it will boot fine and your touch screen will work. The only reason I haven't told others about that is because of two reasons. For one, everyone's using some windows program that sources its downloads from a different spot than lolinet, and those kerels, I assume, work ( I wouldn't touch windows with my worst enemies computer, myself, so I had to find another way using Linux). And for two, I broke my Moto G power 2021 just a day after I got it. This TWRP in here won't work with all these commands but some of them do work. Backup sure does.
TWRP Commandline Guide
</style>CLIENT SIDE/SCRIPTinstall FILENAME : install FILENAME zip file.
twrp.me
I now have the phone I meant to get in the first place, the Moto G9 Power with an official TWRP build.
arkansawdave74 said:
Oh. My bad, man. I had misread the dude's typo. It says, "no touch on mouse support," and I thought he'd meant to say "or," but I later realized that he'd meant to say "only." It apparently has mouse support.I broke my Power 2021 right after I got it, but I did get it rooted using this twrp in an adb shell to pull my kernel because the kernels in the lolinet firmwares, after patching, caused the 2021 to lose touch functionality completely. But, even though it's the same damned kernel, when you pull it with:
"adb shell"
"twrp backup B"
it will make a backup in the usual spot in internal storage (/sdcard/TWRP). Go in there and find the file and rename it to boot.img (or something like twrpdboot.img to keep it from being confused with the other boot images) and if you patch that one with magisk it will boot fine and your touch screen will work. The only reason I haven't told others about that is because of two reasons. For one, everyone's using some windows program that sources its downloads from a different spot than lolinet, and those kerels, I assume, work ( I wouldn't touch windows with my worst enemies computer, myself, so I had to find another way using Linux). And for two, I broke my Moto G power 2021 just a day after I got it. This TWRP in here won't work with all these commands but some of them do work. Backup sure does.
TWRP Commandline Guide
</style>CLIENT SIDE/SCRIPTinstall FILENAME : install FILENAME zip file.
twrp.me
Click to expand...
Click to collapse
I used lolinet files on my 2021, no touch issues, but mine uses the Ilitek display. But since you seem to be familiar with Linux as you put it, you could unpack and repack yours and ramdisk, having pulled files like I outline in https://ilitekforum.xda-developers....ased-updated-11-4-2021.4354855/#post-85885471, so you may be able to make your TWRP have touch, unless you meant damaged so much that's broken too.
I posted a fixed twrp file for you all
svoc said:
I posted a fixed twrp file for you all
Click to expand...
Click to collapse
which version of TWRP is this one? Can I find a changelog to check out somewhere?
Onoitsu2 said:
unless you meant damaged so much that's broken too.
Click to expand...
Click to collapse
It's out of there. I'lI maybe get another one though because I really want to try Visible Wireless Service and this G9 Power doesn't have esim capability. True unlimited with no hotspot cap for $40/month. Maybe too good to be true, but I gotta check it out. Until then, Check ya laters borneo dudes.
treesus said:
which version of TWRP is this one? Can I find a changelog to check out somewhere?
Click to expand...
Click to collapse
I dont make change logs this is twrp 3.4
svoc said:
I dont make change logs this is twrp 3.4
Click to expand...
Click to collapse
I build for myself then when it working I give it away I do t keep track of what I do to get it working I just get it working then give it out sorry I'm working on LineageOS right now I got the device trees working last night I got my first build working but still a lot to test out before release
Excited to follow development for the Borneo. Thank you.
If you have any features you would like let me know when I build a rock I make it 100% Google stock no anything extra so let me know if you want any fluff
svoc said:
If you have any features you would like let me know when I build a rock I make it 100% Google stock no anything extra so let me know if you want any fluff
Click to expand...
Click to collapse
No fluff - just stock. thanks for your hard work.
svoc said:
I posted a fixed twrp file for you all
Click to expand...
Click to collapse
Is there a way to get this working on the G Power (2021) model XT2117-4 (OS is android 11)? I tried running fastboot boot twrp_fixed.img and it just sent me back to the boot loader. Also if its important for me to post my touchscreen stuff, here it is.
Code:
borneo:/ $ cd /sys/class/touchscreen
borneo:/sys/class/touchscreen $ ls
ft8009
4xc7xy said:
Is there a way to get this working on the G Power (2021) model XT2117-4 (OS is android 11)? I tried running fastboot boot twrp_fixed.img and it just sent me back to the boot loader. Also if its important for me to post my touchscreen stuff, here it is.
Code:
borneo:/ $ cd /sys/class/touchscreen
borneo:/sys/class/touchscreen $ ls
ft8009
Click to expand...
Click to collapse
Did you 'fastboot reboot bootloader' first before the boot attempt? You need be in the Fastbootd, not the normal Fastboot screen. I know it's odd, but that's how I got mine. Because apparently fastboot itself won't boot even my TWRP but fastbootd does. The device being an A/B device is the only reason to ever use fastboot (not fastbootd), to flash the sparsed system image is my understanding.
Onoitsu2 said:
Did you 'fastboot reboot bootloader' first before the boot attempt? You need be in the Fastbootd, not the normal Fastboot screen. I know it's odd, but that's how I got mine. Because apparently fastboot itself won't boot even my TWRP but fastbootd does. The device being an A/B device is the only reason to ever use fastboot (not fastbootd), to flash the sparsed system image is my understanding.
Click to expand...
Click to collapse
No I did not, let me try that right now and then do a follow up reply to tell you how it goes