Related
Good evening Ladies & Gents.
Firstly can I say, this site has been my bible, and I am so very very grateful for all the work that everyone has put in to making this site what it is.
Now down to business.
I have an HOX+ and have been flashing for about a year now but still consider myself to be a complete nub! first with hox then i broke it and now hox+. Im in a bit of a predicament.
I flashed a version of aosp 4.4 onto the phone, installed from the zip file, cleared the cache, user data and dalvik.
rebooted, and got stuck in a boot loop.
So i went to my backup and restored from there...
boot loop again.
So i went back into bootloader, then fastboot, and reflashed the viper+ 2.0.1 that I had on before.
But when I got stuck on sending boot
Now im stuck in a boot loop, none of my backups will restore properly.
I fear I am hardbricked as I cant get anything to work...
Any help before I have to be back at work tomorrow would be very helpful! and even more appreciated!
Yours
A very frustrated and stressed British nub
Sorry, also, I have checked through xda and I cant seem to find anything that would explain why I am stuck!
flash the boot.img
from a welsh person who can't understand why people cannot flash rom's correctly
Fastboot
Lloir said:
flash the boot.img
from a welsh person who can't understand why people cannot flash rom's correctly
Click to expand...
Click to collapse
I used "fastboot flash boot boot.img" in my cmd, like i always have done, and this time it doesn't want to work...at all
ryutnm said:
I used "fastboot flash boot boot.img" in my cmd, like i always have done, and this time it doesn't want to work...at all
Click to expand...
Click to collapse
you tried fulling wiping? then just flashing the rom + bootimage after
thanks
Lloir said:
you tried fulling wiping? then just flashing the rom + bootimage after
Click to expand...
Click to collapse
No, does that require different fastboot commands?
i have cwm touch recovery installed. Would that make a difference?
Also, could I just say thank you in advance for your help sir!
ryutnm said:
No, does that require different fastboot commands?
i have cwm touch recovery installed. Would that make a difference?
Also, could I just say thank you in advance for your help sir!
Click to expand...
Click to collapse
Unless you mean the user data and cache wipe.
Then yeah i did that
ryutnm said:
Unless you mean the user data and cache wipe.
Then yeah i did that
Click to expand...
Click to collapse
Data/system/cache
Sent from my Nexus 5 using Tapatalk
ryutnm said:
Good evening Ladies & Gents.
Firstly can I say, this site has been my bible, and I am so very very grateful for all the work that everyone has put in to making this site what it is.
Now down to business.
I have an HOX+ and have been flashing for about a year now but still consider myself to be a complete nub! first with hox then i broke it and now hox+. Im in a bit of a predicament.
I flashed a version of aosp 4.4 onto the phone, installed from the zip file, cleared the cache, user data and dalvik.
rebooted, and got stuck in a boot loop.
So i went to my backup and restored from there...
boot loop again.
So i went back into bootloader, then fastboot, and reflashed the viper+ 2.0.1 that I had on before.
But when I got stuck on sending boot
Now im stuck in a boot loop, none of my backups will restore properly.
I fear I am hardbricked as I cant get anything to work...
Any help before I have to be back at work tomorrow would be very helpful! and even more appreciated!
Yours
A very frustrated and stressed British nub
Click to expand...
Click to collapse
Well the bootlooping has something to do with not flashing the boot.img stated by yourself and lloir. About that bug of "Sending boot.img", it happens to me but I fix it by running CMD as administrator , If that doesnt work, try using a different usb port. Preferably one directly to pc/laptop rather than using a hub. Try a 3.0usb port first, if that doesnt work then 2.0usb port.
P.S Without S-Off you can't become hardbricked. Till now I didn't see a single person who bricked their HOX+ unless he received an S-Off developer phone..
Lloir said:
Data/system/cache
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Im now only getting "waiting for device"
which I can only assume means my pc now doesnt even recognise the phone when its booted in bootloader/fastboot usb mode?
ryutnm said:
Im now only getting "waiting for device"
which I can only assume means my pc now doesnt even recognise the phone when its booted in bootloader/fastboot usb mode?
Click to expand...
Click to collapse
stop....Hammer time...
have you got a rom on the sdcard (in cwm) if yes
wipe data/system/cache
then
reboot into bootloader
fastboot flash boot boot.img
if not ----------
full wipe (as above)
adb sideload romname.zip
then reboot into bootloader as above
Lloir said:
stop....Hammer time...
have you got a rom on the sdcard (in cwm) if yes
wipe data/system/cache
then
reboot into bootloader
fastboot flash boot boot.img
if not ----------
full wipe (as above)
adb sideload romname.zip
then reboot into bootloader as above
Click to expand...
Click to collapse
I have the zip on the internal storage as i dont have "sd/ext" or what ever the extention is. When I bought the phone I never had the sd card. Never was able to save anything onto an sd card.
so should i try installing from the zip? even though the fastboot commands arent working?
or would a sideload skip the fastboot commands?
or am i just being completely retarded
Edt - just tried the sideload using the cmd, and i had error: device not found
so windows isnt recognising my phone...it was working this morning
ryutnm said:
I have the zip on the internal storage as i dont have "sd/ext" or what ever the extention is. When I bought the phone I never had the sd card. Never was able to save anything onto an sd card.
so should i try installing from the zip? even though the fastboot commands arent working?
or would a sideload skip the fastboot commands?
or am i just being completely retarded
Click to expand...
Click to collapse
Why am i being ignored you guys lol. Did you try my solution ?
Terribly Sorry
Ghand0ur said:
Why am i being ignored you guys lol. Did you try my solution ?
Click to expand...
Click to collapse
dude, im so sorry - i didnt even see the post!
i will try now!
sorry again
edt - still no joy as for some reason my phone is no longer being recognised by my pc =[
HTC sync uninstalled ?
you have killed adb (if on windows just kick open taskman and kill adb)
or in cmd\terminal adb kill-server
then do adb devices
reboot pc?
try a different usb cable (maybe the one from your charger if you are not using that one)
*edit the above is assuming you are in recovery
IF NOT in recovery, but fastboot_usb mode
then fastboot devices (but you cannot do jack apart from flash boot image)
IF in recovery, you got a few choices
wait 5-10minutes (don't ask, it's a common issue with the X+ and CWM\TWRP)
put the device in adb sideload for a minute or so (^ see above reason)
i have adb issues in CWM\TWRP myself, especially when i have no rom and so on, so i know your frustration, patience young padwan
looking good so far
Ghand0ur said:
Why am i being ignored you guys lol. Did you try my solution ?
Click to expand...
Click to collapse
Lloir said:
HTC sync uninstalled ?
you have killed adb (if on windows just kick open taskman and kill adb)
or in cmd\terminal adb kill-server
then do adb devices
reboot pc?
try a different usb cable (maybe the one from your charger if you are not using that one)
Click to expand...
Click to collapse
So I tried starting cmd in administrator mode [never had to before]
- Didnt work
- Plugged into a different usb slot as lloir suggested, didnt get the "windows does not recognise this device" this time
restarted cmd as admin like Ghandour suggested.
Just managed to install the viperx+ 2.0.1 rom and i am now setting it up!
THANK YOU SO FREAKING MUCH GUYS [and gals if either of you are female]!
do you know why I had to start using cmd as an administrator?
ryutnm said:
So I tried starting cmd in administrator mode [never had to before]
- Didnt work
- Plugged into a different usb slot as lloir suggested, didnt get the "windows does not recognise this device" this time
restarted cmd as admin like Ghandour suggested.
Just managed to install the viperx+ 2.0.1 rom and i am now setting it up!
THANK YOU SO FREAKING MUCH GUYS [and gals if either of you are female]!
do you know why I had to start using cmd as an administrator?
Click to expand...
Click to collapse
might be because of where you have the adb tools. and i'am 100% male
thanks
Lloir said:
might be because of where you have the adb tools. and i'am 100% male
Click to expand...
Click to collapse
well dude, thank you for your help!
I dont understand why though, ive been using this pc the whole time to flash recovery images and boot images and never had to use admin
Thank you
Also a thank you to Ghand0ur for your help as well!
So very much appreciated
ryutnm said:
Also a thank you to Ghand0ur for your help as well!
So very much appreciated
Click to expand...
Click to collapse
Glad you got it working. Just always try those common solutions:
-Restart PC
-Run as admin
-unplug replug
-reboot phone
-try different usb port
-try different usb cable.
I have tried recently to root my DNA running 3.06 and 4.2.2 with rumrunner. My phone gets to the bootloader screen from the rumrunner program, and then on the first step the program says waiting for fastboot but my phone just sits there. It isn't frozen and I can move it around but it doesn't do anything automatically like I know it should. Not sure if it maybe has something do do with ADB or anything along those lines. If anyone has any idea I could really use some help. This is my first android phone and my first root attempt. Thanks.
Mr.Schneider said:
I have tried recently to root my DNA running 3.06 and 4.2.2 with rumrunner. My phone gets to the bootloader screen from the rumrunner program, and then on the first step the program says waiting for fastboot but my phone just sits there. It isn't frozen and I can move it around but it doesn't do anything automatically like I know it should. Not sure if it maybe has something do do with ADB or anything along those lines. If anyone has any idea I could really use some help. This is my first android phone and my first root attempt. Thanks.
Click to expand...
Click to collapse
Sounds like a problem with ADB and or Fastboot.
Fix those and you should be fine.
sdamark said:
Sounds like a problem with ADB and or Fastboot.
Fix those and you should be fine.
Click to expand...
Click to collapse
I believe I fixed my adb, put it in my directory and the path settings. Everything still isn't working. I know fastboot is set up correctly because i can type it in the cmd line and all the info comes up, I'm just lost. Not sure if you know what to do from here.
Mr.Schneider said:
I believe I fixed my adb, put it in my directory and the path settings. Everything still isn't working. I know fastboot is set up correctly because i can type it in the cmd line and all the info comes up, I'm just lost. Not sure if you know what to do from here.
Click to expand...
Click to collapse
In a command prompt, type "adb devices'
response should be device serial # "[FA2CXXXX blah blah] device"
Next in a command prompt, type "adb reboot bootloader"
device should boot into bootloader Fastboot USB
Then type "fastboot devices"
response should be device serial # "[FA2CXXXX blah blah] fastboot"
Then type "fastboot reboot"
Device should reboot into android.
If all this works, then ADB and Fastboot are working. :good:
How is Rumrunner failing? Can you post a screenshot of your computer? Need more info to help.
I had a similar issue, but on step 2. Confirm before any reboots that both adb and fastboot work. If so, run the exe. If they stop working during the program running it could be usb cord or port
I am doing it on my windows 7 computer and everything is working perfectly so far. Thanks for all the help and ill post again if I run into more troubles. While Your'e here, does anyone know the commands to flash a custom recovery onto the devise after I have S-Off?
Thanks for all the help guys! It worked perfectly. Now all I have to do is install some roms and see what else I can do.
Sent from my HTC DROID DNA
Mr.Schneider said:
Thanks for all the help guys! It worked perfectly. Now all I have to do is install some roms and see what else I can do.
Sent from my HTC DROID DNA
Click to expand...
Click to collapse
Do you know how to do that or do you need help?
thayl0 said:
Do you know how to do that or do you need help?
Click to expand...
Click to collapse
I installed cyogen mod, but I'm having an issue wjere y data is being weird and I cannot send text messages. Anyone know any smooth running ROMs I could try? Preferably ones that look similar to stock android and not sense.
Mr.Schneider said:
I installed cyogen mod, but I'm having an issue wjere y data is being weird and I cannot send text messages. Anyone know any smooth running ROMs I could try? Preferably ones that look similar to stock android and not sense.
Click to expand...
Click to collapse
Cm is stable. So that could be another problem we have here
thayl0 said:
Cm is stable. So that could be another problem we have here
Click to expand...
Click to collapse
Would you Happen to have a link to the stable release you know of? Just to be sure I have an updated one? I'll attach a picture.
Mr.Schneider said:
Would you Happen to have a link to the stable release you know of? Just to be sure I have an updated one? I'll attach a picture.
Click to expand...
Click to collapse
You have the latest version for 10.2
ViperDNA is pretty much a stock Sense 5.0 JellyBean 4.2.2 ROM, with a million little things you can tweak on with Venom Tweaks and Venom Hub.
Find download here http://forum.xda-developers.com/showthread.php?t=2475739
This one is Sense 5.5 based, KitKat 4.4.2, pretty much 100% stock from the HTC One.
Find download here http://forum.xda-developers.com/showthread.php?p=50142710
Both are awesome.
Really glad you figured out how to S-Off. :good:
Welcome to the community.
I have a TF201 and have loved it. Earlier this year after cracking the screen I decided to unlock, root and play around a bit. Installed CM11. I liked it and didn't have an issues with it. I went back to a stock version 2 days ago. I have quickly seen how much better performance was on CM11. But now there are some other KK roms out there, and I read on a thread you can actually install TF300 roms on a TF201 as well. What ROM do you suggest I try next? Crombi-X, Crombi-kk, CM11 (newer build) or another.
JoanneDisFan said:
I have a TF201 and have loved it. Earlier this year after cracking the screen I decided to unlock, root and play around a bit. Installed CM11. I liked it and didn't have an issues with it. I went back to a stock version 2 days ago. I have quickly seen how much better performance was on CM11. But now there are some other KK roms out there, and I read on a thread you can actually install TF300 roms on a TF201 as well. What ROM do you suggest I try next? Crombi-X, Crombi-kk, CM11 (newer build) or another.
Click to expand...
Click to collapse
If you head over to the Crombi-kk thread there is a step by step to upgrade to be able to run a 4.4.x rom ....
We do have some small issue like the CAM not working for the last 2 releases, BUT we got it fixed and the next
release will have it working ...
I dont think that you would be unhappy with any of the tf300 ROMs available for your 201 after you follow the steps
in post number 4 here on this thread http://forum.xda-developers.com/showthread.php?t=2773812
It would open up a whole new set of roms for your flashing pleasure..
Thx Josh & Team CROMBI-kk
Thanks Josh.
I'm learning towards either the Cromi-X or Crombi-KK. Are both still being developed? Is there a benefit to sticking with the TF201 version rather than the tf300 version?
I like several of the asus apps. Can I install those on any of the KK versions?
Hubby was also wondering which kernel would give the best wifi and speed?
JoanneDisFan said:
Thanks Josh.
I'm learning towards either the Cromi-X or Crombi-KK. Are both still being developed? Is there a benefit to sticking with the TF201 version rather than the tf300 version?
I like several of the asus apps. Can I install those on any of the KK versions?
Hubby was also wondering which kernel would give the best wifi and speed?
Click to expand...
Click to collapse
I would say that Cromi-X is close to the end of is development life, but having said that if there are bugs I know @sbdags would take care of them
WIth this ROM everything would be just like it is now fully supported dock all the asus apps.. etc .....
With Crombi-kk is still very much under development. But things are not quite as refined in this one, the dock has some small bugs
and there is an Asus app zip that can be flashed and will give you the stock Asus back
If you decide to go with Cromi-X i would choose _that's kernel for sure ...
If going with Crombi-kk I think that Grimlocks kernel is a very good one ...
I think that answers all your questions , nice post thx for that :good:
and always Thx Josh
So I've decided to go with Crombi-KK for the 201. I'm following the install instructions on the link you posted but running into a problem. I have the BL installed at TWRP 2.7 but when I try and do ads push of the crombi I get an error: device not found but if I do fastboot devices I do find my device.
JoanneDisFan said:
So I've decided to go with Crombi-KK for the 201. I'm following the install instructions on the link you posted but running into a problem. I have the BL installed at TWRP 2.7 but when I try and do ads push of the crombi I get an error: device not found but if I do fastboot devices I do find my device.
Click to expand...
Click to collapse
are you running the adb command from recovery ?
lj50036 said:
are you running the adb command from recovery ?
Click to expand...
Click to collapse
Not sure. I try to do it at the screen that gives me recovery as well at android to boot into. How would I get into adb in twrp?
JoanneDisFan said:
Not sure. I try to do it at the screen that gives me recovery as well at android to boot into. How would I get into adb in twrp?
Click to expand...
Click to collapse
Can you boot into twrp ?
lj50036 said:
Can you boot into twrp ?
Click to expand...
Click to collapse
Yes I can get TWRP up.
JoanneDisFan said:
Yes I can get TWRP up.
Click to expand...
Click to collapse
Found ADB sideload under advanced. Used sideload rather than push and it's now moving
JoanneDisFan said:
Found ADB sideload under advanced. Used sideload rather than push and it's now moving
Click to expand...
Click to collapse
Okay I take that back. It load 2-3% then I get the error: failed to write data ' protocol fault <No status>'
JoanneDisFan said:
Found ADB sideload under advanced. Used sideload rather than push and it's now moving
Click to expand...
Click to collapse
Well we need to get adb and fastboot working ....
Have you ever used G+ to do screenshare ?
Let me know
Thx Josh
No never have done a screen share. I'm starting with making sure I have the current version of adb. Downlaoding SDK at the moment. Fastboot worked fine.
JoanneDisFan said:
No never have done a screen share. I'm starting with making sure I have the current version of adb. Downlaoding SDK at the moment. Fastboot worked fine.
Click to expand...
Click to collapse
If you would like any help with getting adb working shoot me a hangouts at
[email protected]
thx Josh
EDIT
Hey XDA, This one has me doing some reading, The driver would install and the adb devices would show the device, but when we tried to push it would give us a "failed protocol"
I am sure this is a windows issue and I am just not the best with windows. Yes we had the CMD opened as admin, and everything looks good ....
I am doing some more reading myself....
Thx Josh
A quick update whats been happening. Tried to install via sdcard only to have that not mount. So went to fastboot and loaded my stock boot loader. Went back into TWRP and it could find my sdcard. Installed from the SDcard the HB BL, then installed TWRP 2.7, then install crombi-kk. I'm still doing the install, but it's working.
I tried to update my oneplus x to a new version of resurrection remix (the android 7.1 version) by flashing through twrp. Long story short I tried to update the recovery twrp and also update my bootloader but it all went to **** and now my phone is bricked. If I try and boot the phone into either the OS or into recovery I get a boot loop where the oneplus logo appears, the phone vibrates then reboots. I can get into fastboot but when I try and flash either a rom or recovery it tells me I can't because my 'device is not unlocked'. I know my bootloader was unlocked previously but am thinking that by trying to install a new rom it has re-lock or something and I'm not sure if this means my phone is now a paper weight..
Any help would be greatly appreciated!
edit: This problem is fixed. However twrp won't flash/boot correctly now..
Follow this to the letter: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
I did basically the same thing you did and flashed a rom that was compatible with the old bootloader only and it "locked" my bootloader which made the recovery and ROM useless. It took me a few hours to get the device to actually be recognized correctly by the computer and program but it worked. You may also need to google since I remember needing to download basically the same program but from a different site.
Tanner1294 said:
Follow this to the letter: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
I did basically the same thing you did and flashed a rom that was compatible with the old bootloader only and it "locked" my bootloader which made the recovery and ROM useless. It took me a few hours to get the device to actually be recognized correctly by the computer and program but it worked. You may also need to google since I remember needing to download basically the same program but from a different site.
Click to expand...
Click to collapse
Thanks for the reply! I think I may have come across this but wasn't sure if I'd get myself into more trouble since my fastboot is working (it says it's for devices who have nothing). Rekcon it's still my best option?
Edit:
I tried it and worked perfectly. Thanks heaps!
lilfellabob said:
Thanks for the reply! I think I may have come across this but wasn't sure if I'd get myself into more trouble since my fastboot is working (it says it's for devices who have nothing). Rekcon it's still my best option?
Edit:
I tried it and worked perfectly. Thanks heaps!
Click to expand...
Click to collapse
You're welcome! Like I said I was in the same situation. It kept rebooting and when I got into fastboot my heart sank when it said "Device is locked"
So I now have recovery working as well as fastboot (unlocked this time). But I cannot for the life of me get twrp to work correctly. One version out of like 5 I've tried works but won't flash any roms; I read that could be from a bad version.. All others seem to flash from fastboot but when I try to boot I get the dtb not found error. I don't understand why I cant get it to work, this should be the easy part
lilfellabob said:
So I now have recovery working as well as fastboot (unlocked this time). But I cannot for the life of me get twrp to work correctly. One version out of like 5 I've tried works but won't flash any roms; I read that could be from a bad version.. All others seem to flash from fastboot but when I try to boot I get the dtb not found error. I don't understand why I cant get it to work, this should be the easy part
Click to expand...
Click to collapse
dtb not found error means its not compatiable with your bootloader. Did you try official twrp ? And you ever updated to new bootloader?
update your bootloader first, http://forum.xda-developers.com/onep...t3478917/page1
saurabh40629 said:
dtb not found error means its not compatiable with your bootloader. Did you try official twrp ? And you ever updated to new bootloader?
update your bootloader first, http://forum.xda-developers.com/onep...t3478917/page1
Click to expand...
Click to collapse
I'll give it a shot. I am using official twrp yeah - just seems weird because even the old one that used to work fine isn't working. That link doesn't work is this one ok?
http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Thanks for the help
lilfellabob said:
I'll give it a shot. I am using official twrp yeah - just seems weird because even the old one that used to work fine isn't working. That link doesn't work is this one ok?
http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Thanks for the help
Click to expand...
Click to collapse
Yeah... This is the link.
All working, everyones help is much appreciated! <3 thanks
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