-please read the whole thread-
:The point of this thread.
Find a way to get flash mode to stay active longer, Gives you more time to work and experiment"
The point of basing it on on the newer driver is that there may be something in them that will give us access to Fastboot"
Hopefully use that to get to the boot loader.
:--
I noticed today that there is a bug in the x10 flash driver that forcefully ejects the device from flash mode after a delay if it does not get initialized.
I am looking for someone that can make that driver stop ejecting the device.
"This is for real.."
Do not spam here "there is method to my madness"
Perhaps even act more like the driver used to unlock the newer phones.
But for the x10.
The file i attached may be useful.
It ejects when flash mode isn't used i think.
Sent from my X10i
jockep said:
It ejects when flash mode isn't used i think.
Sent from my X10i
Click to expand...
Click to collapse
No.
please just listen to me.
If any developer is interested in this PM me and i will explain.
Just a note but you may want to mention which version of the flash tool you are having issues with.
exsulis said:
Just a note but you may want to mention which version of the flash tool you are having issues with.
Click to expand...
Click to collapse
Please.. as i said DEVELOPERS ONLY.
PLEASE DON'T spam.
I'm not talking about the flash tool.
i don't think it has anything to do with the driver, as much as the phone's flashmode behavior itself.
ie the computer recognises the device device differently whether its in regular usb mode, debugging, mounted, flashmode, etc.
i think what it's experiencing is flashmode turns off if there's a delay, and changes usb mode. the computer sees the change as "device A" no longer there and "device B" now there. the computer will see the different usb modes as separate devices since there will be separate ID's for the mode.
if there was a way to keep the phone in flashmode, this would fix the problem. but there's no way of doing that without changing and reflashing fastboot/bootloader.
Then perhaps a driver that acts more like the drivers for the newer phones.
I think.. Fast boot could easily be accessed this way.
And all we need is for it to load that driver and to test using this command.
fastboot.exe -i 0x0fce getvar version
This is all speculation.. but call it a lucky hunch.
If i am wrong then the mods may delete this thread and XDA may ridicule me.
If anyone does manage to do this.
The credit is all yours.
No.. now i am sure the X10's driver may be buggy.
Hold the flash button and insert your charging lead using the wall charger.
You will notice it stays in flash mode for much longer.
I may be wrong.. but test it.
that's because the data signal sent doesn't receive an answer at all.
in simple as possible terms:
when plugged into a computer, it sends the signal that it's flashmode, computer resonds "ok", device signals back "instruct", if the computer responds, it flashes, if there's no response in the defined time, the phone reboots out of flashmode.
i doubt that this could be used as an exploit, else we would have been able to fake SEUS or PCC into flashing a custom bootloader.
but don't get me wrong, if you or any devs know of a way to exploit it, by all means go to it!
svtfmook said:
that's because the data signal sent doesn't receive an answer at all.
in simple as possible terms:
when plugged into a computer, it sends the signal that it's flashmode, computer resonds "ok", device signals back "instruct", if the computer responds, it flashes, if there's no response in the defined time, the phone reboots out of flashmode.
i doubt that this could be used as an exploit, else we would have been able to fake SEUS or PCC into flashing a custom bootloader.
Click to expand...
Click to collapse
I know this.. But i would like to get a few more developer opinions on this.
OmegaRED^ said:
I know this.. But i would like to get a few more developer opinions on this.
Click to expand...
Click to collapse
no doubt. would be cool if it could be exploited.
svtfmook said:
no doubt. would be cool if it could be exploited.
Click to expand...
Click to collapse
I hope.. that i am right.
But my gut tells me something is there.
If anyone does achieve this
"no need to credit me"
OmegaRED^ said:
I hope.. that i am right.
But my gut tells me something is there.
If anyone does achieve this
"no need to credit me"
Click to expand...
Click to collapse
Never head that on the x10 forums
Sent from my X10i using XDA App
rtblittlebrown said:
Never head that on the x10 forums
Sent from my X10i using XDA App
Click to expand...
Click to collapse
This is not about me... but us the x10 users.
I hope that a few developers will pay attention to this idea.
Weird.. for some reason now when ever i reboot my phone it goes into flash mode automatically.
OmegaRED^ said:
This is not about me... but us the x10 users.
I hope that a few developers will pay attention to this idea.
Click to expand...
Click to collapse
If other devs had that attitude they may already have picked this thread up
Seems you may have fallen foul of someones temper tantrum
Sorry for the spam
OmegaRED^ said:
Weird.. for some reason now when ever i reboot my phone it goes into flash mode automatically.
Click to expand...
Click to collapse
If your plugged into your charger that happens on older rom's with charge when off problems
Sent from my X10 using XDA App
OmegaRED^ said:
I noticed today that there is a bug in the x10 flash driver that forcefully ejects the device from flash mode after a delay if it does not get initialized.
I am looking for someone that can make that driver stop ejecting the device.
"This is for real.."
Do not spam here "there is method to my madness"
Perhaps even act more like the driver used to unlock the newer phones.
But for the x10.
The file i attached may be usefull.
Click to expand...
Click to collapse
Not to throw a spanner in the works BUT! Just so you know the driver you have installed is designed for the later Xperia Phones like the play etc perhaps if you removed the driver deleted the software that goes with it then re-installed the CORRECT driver then you would have less of a "Buggy" driver as you put it! Sorry for the put down but dont wanna get you carried away!
Edit: also some more research it indicates the its the android generic open driver inf
asmanthebell said:
Not to throw a spanner in the work BUT! Just so you know the driver you have installed is designed for the later Xperia Phones like the play etc perhaps if you removed the driver deleted the software that goes with it then re-installed the CORRECT driver then you would have less of a "Buggy" driver as you put it! Sorry for the put down but dont wanna get you carried away!
Click to expand...
Click to collapse
Um.. no.
I think you misunderstood.
Currently i have the X10 driver installed on my system.
Maybe you should re read the whole thread.
I am not asking for help on how to install drivers.
or what drivers to install.
This is why i asked for developers only to reply.
OmegaRED^ said:
Um.. no.
I think you misunderstood.
Currently i have the X10 driver installed on my system.
Maybe you should re read the whole thread.
I am not asking for help on how to install drivers.
or what drivers to install.
Click to expand...
Click to collapse
Sigh!
1. Do you know and understand what an .inf file is?
2. Do you know how interacts with an operation system?
3. Can you post the rest of driver i.e the .cat file and .sys to go with the inf?
Related
My Xperia X10 is currently not working (see previous thread http://forum.xda-developers.com/showthread.php?t=993785) and I still haven't been able to fix it.
I'm trying to use Flashtool to flash the generic X10 Firmware to my phone although
it's taking up to 4+ hours and then my phone battery dies and the flash is unsuccessful.
Why is Flashtool taking so long to flash a firmware to my X10? I've tried a few different computers and still the same problem.
Please Help. Thank you.
Have you checked, >development >USB debugging in the applications menu?
gogogu said:
Have you checked, >development >USB debugging in the applications menu?
Click to expand...
Click to collapse
I cannot access my phone as of now, it's pretty much a brick. Holding the on button brings only a vibrate and thats it.
what about flashing a rom that you know worked on your phone, making sure you flash the right Baseband for that particular rom first.
EDIT: Sorry just read through you posts and you have probably tried this if you have flashed a rom to it!
gogogu said:
what about flashing a rom that you know worked on your phone, making sure you flash the right Baseband for that particular rom first.
EDIT: Sorry just read through you posts and you have probably tried this if you have flashed a rom to it!
Click to expand...
Click to collapse
Is it possible to turn USB Debugging on without accessing the device??
not assuming you're silly. but you are making sure you have your finger firmly on the back button when you plug in the phone when flashing yeah? the simplest are often the ones that get you.
gogogu said:
not assuming you're silly. but you are making sure you have your finger firmly on the back button when you plug in the phone when flashing yeah? the simplest are often the ones that get you.
Click to expand...
Click to collapse
Yes, It's not that lol. So where do I go from here, my phones pretty much bricked then?
it wont charge via usb or regular charger?
aval1392 said:
it wont charge via usb or regular charger?
Click to expand...
Click to collapse
Read previous thread in original post.
The phone has crashed for some reason whilst using the FreeX10 Beta4 Rom and I cannot access the phone. It charges fine although I cannot turn on/access my phone.
not sure why the flash is taking so long. attempt to flash a different firmware possibly? Also do you have the latest flashtool?
Impossible to brick so you're not out of luck yet. Try flashing with latest flashtool 2.9.1
I'll attempt now with the Flashtool 2.9.1 beta. It's a shame that as soon as they unlock the bootloader my X10 decides to stop working.
EDIT:
'turn on Unknown Sources and Debugging' - It's impossible to access my phone to turn on USB debugging and unknown sources. What do I do now?
bump, anyone??
Attempt repairing your phone via Sony Ericsson Update Service. If that fails put a compatible basebrand and firmware on your phone. Make sure user data is wiped
aval1392 said:
Attempt repairing your phone via Sony Ericsson Update Service. If that fails put a compatible basebrand and firmware on your phone. Make sure user data is wiped
Click to expand...
Click to collapse
Sony Ericsson Update Service does not recognise the product.
Not that I haven't attempted this but I put a compatible baseband and firmware and it took 7 hours in which it only flashed 4 items and then the rest flashed instantly which the phone displays blinking red light.
It's not working. Whats wrong???
Bump for resolution.
foxhound494 said:
Bump for resolution.
Click to expand...
Click to collapse
mine does exactly same as yours, every time is prompt Error Flashing, aborted.....alway stop at kernel.sin or boot.sin
I cannot access my phone as of now, it's pretty much a brick. Holding the on button brings only a vibrate and thats it.
Click to expand...
Click to collapse
Try to use SEUS to repair phone if you can't boot your phone. Do not use PC Companion cause' it will try to detect your phone everytime you use it but your phone can't boot so PC Companion now useless. If you can't repair your phone, you have to bring it to SE service.
Sony Ericsson Update Service does not recognise the product.
Click to expand...
Click to collapse
It will not detect your phone dude. You must select your phone from the list supported. It will tell you to plug your phone in while holding BACK key and after searching for update, you will have a notice about update or repairing.
I sincerely hope this is not in the wrong place, but i do not know where else to put it. I tried to update my x10 running wbcm6 to tw007.2, but apparently in my sleep-deprived haze, downloaded the wrong bb version. when i tried to restart after install, i lost xrecovery, and had no signal and had an unknown bb version. after many attempts to recover, finally resorted to rolling back all the way to stock 2.1 and starting over. was able to succesfully flash at&t 2.1 rom according to flashtool, but now i am stuck in a reboot loop after the boot animation. cannot get seus pc companion to recognize, and neither will flashtool. i am at the end of my wits, this my only phone, and it is currently unuseable...
anyone who has any recommendations would be greatly appreciated. let me know if i can provide any further information...
My turn!
WRONG SECTION AAAAHHHHH!!!!!
This is the meanest forum on XDA.
bobdallama said:
I sincerely hope this is not in the wrong place, but i do not know where else to put it. I tried to update my x10 running wbcm6 to tw007.2, but apparently in my sleep-deprived haze, downloaded the wrong bb version. when i tried to restart after install, i lost xrecovery, and had no signal and had an unknown bb version. after many attempts to recover, finally resorted to rolling back all the way to stock 2.1 and starting over. was able to succesfully flash at&t 2.1 rom according to flashtool, but now i am stuck in a reboot loop after the boot animation. cannot get seus pc companion to recognize, and neither will flashtool. i am at the end of my wits, this my only phone, and it is currently unuseable...
anyone who has any recommendations would be greatly appreciated. let me know if i can provide any further information...
Click to expand...
Click to collapse
Sounds like what happend to me when flashing custom kernels to MIUI ROMs.
Something wrong with the chargemon with the problem I was having.
But for you. Dunno.
You've tried re-flashing firmware but cannot get flashtool to recognize your phone?
Try taking the battery out, then get flashtool set up, plug everything in and hold the back button, and then put the battery back in and continue to hold the back button.
Sometimes, it takes a bit for the 'puter to recognize the phone with flashtool because it's had the USB ID re-assigned. Mine (on windows 7) will re-install the USB driver when I'm having severe issues.
andrewddickey said:
Sounds like what happend to me when flashing custom kernels to MIUI ROMs.
Something wrong with the chargemon with the problem I was having.
But for you. Dunno.
You've tried re-flashing firmware but cannot get flashtool to recognize your phone?
Try taking the battery out, then get flashtool set up, plug everything in and hold the back button, and then put the battery back in and continue to hold the back button.
Sometimes, it takes a bit for the 'puter to recognize the phone with flashtool because it's had the USB ID re-assigned. Mine (on windows 7) will re-install the USB driver when I'm having severe issues.
Click to expand...
Click to collapse
the battery trick worked. i too am running windows 7 (64) and when i was finally able to get flashtool to recognize the phone, then it went without a problem. thank you so much! back up and running wb cm6 tw008! faster than ever!
bobdallama said:
the battery trick worked. i too am running windows 7 (64) and when i was finally able to get flashtool to recognize the phone, then it went without a problem. thank you so much! back up and running wb cm6 tw008! faster than ever!
Click to expand...
Click to collapse
WOO-HOO! for solving a problem in the dev section before moved or anyone else hootin'&hollerin'!
Wrong section, dude
letterman12 said:
Wrong section, dude
Click to expand...
Click to collapse
See what I mean?
It is funny to me when people just say "wrong section" but offer no useful advice. Seems just as easy to say nothing and just let us work it out. And who knows? Maybe someone who is dealing with an issue caused by android development (see current section) will think to look in the same place for a solution. It's a big circle!
Sent from my X10i using XDA App
bobdallama said:
It is funny to me when people just say "wrong section" but offer no useful advice. Seems just as easy to say nothing and just let us work it out. And who knows? Maybe someone who is dealing with an issue caused by android development (see current section) will think to look in the same place for a solution. It's a big circle!
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Amen brotha!
...now I'm just spamming......WRONG SECTION!!!!!
MODS>>>>>PLEASE MOVE TO Q&A!!!!!!AHHHHHHHHH!
wow. solved before it got moved ? :L
also, i was gonna suggest reboot your darn x64 bit comp, and the take out your ****fy battery, and then plug your usb cable in the hole and hold the back button and reflash with flashtool, but when it says flashing, then insert battery while still holding the back button. its a common issue after one flash for x64. happened to me several times, when the x64 bit comp won't detect, so i had to reboot.
now, MOD PLEASE MOVE
Moved to proper forum.
that is interesting information to know. i will definitely keep that in mind when flashing in the future. appreciate that
My x10i keeps showing android system not responding after i flashed a xperiaTW custom ROM by wolfbreak. I tried to flash a stock firmware using flashtool but it kept saying, ERROR , please install or reInstall Drivers. I assume that the computer could not detect that my phone is in flashmode. The point now is, i tried using PC companion to repair the drivers, they asked me to Drag the notification bar down and click Mount, but my phone system is not responding. if i click wait or force close, it will pop back up again. and it wont respond to my touches at all. So im like stuck at the home page. Is my phone like dead now or what?
isaacpeh said:
My x10i keeps showing android system not responding after i flashed a xperiaTW custom ROM by wolfbreak. I tried to flash a stock firmware using flashtool but it kept saying, ERROR , please install or reInstall Drivers. I assume that the computer could not detect that my phone is in flashmode. The point now is, i tried using PC companion to repair the drivers, they asked me to Drag the notification bar down and click Mount, but my phone system is not responding. if i click wait or force close, it will pop back up again. and it wont respond to my touches at all. So im like stuck at the home page. Is my phone like dead now or what?
Click to expand...
Click to collapse
Look in Device manager while your phone is plugged...is there some device with an error.
Maybe its the usb drivers or ADB drivers. Look and tell what is the device that have problems. Maybe I can guide you how to install it's drivers.
Possible solution
Hi.
Actually, I believe the solution is very simple.
Just install "Sony Ericsson Update Service" (alias SEUS) from Sony Ericsson website and it will install the needed drivers.
It happened to me, and I solved it that way.
Good luck!
proyectomx said:
Hi.
Actually, I believe the solution is very simple.
Just install "Sony Ericsson Update Service" (alias SEUS) from Sony Ericsson website and it will install the needed drivers.
It happened to me, and I solved it that way.
Good luck!
Click to expand...
Click to collapse
The installing of SEUS will not do the trick, he has to put the phone in flashmode in order to SEUS to install the driver.
But, SEUS installs only usb drivers. If the problem is ADB101 driver it will not help!
Look inside the flashtool folder, you will see a drivers folder and inside that there's a installer for drivers.
Sent from my X10x using XDA App
I think the guy is not reading at all
G-FACE said:
I think the guy is not reading at all
Click to expand...
Click to collapse
You talking about me G or the OP?
Lockon Stratos said:
You talking about me G or the OP?
Click to expand...
Click to collapse
Talk about the OP, man. How could you think i meant you?
G-FACE said:
Talk about the OP, man. How could you think i meant you?
Click to expand...
Click to collapse
My apologies G...just had a rough day.
Anyway yeah OP doesn't like to read. He/she got another thread or 2 in here about the flashtool. I pointed OP to the tutorial that Reindero made, which IMO is idiot proof, but the questions that get asked are mind blowing. We were all noobs at one point and I mean I understand if what you are asking is NOT well documented but common....did you even bother reading any of the steps??? Anyway that's my rant for the today.
Hello great people of XDA. Ok I have a major problem. I'm not sure what classification my phone state is in, but this is the issue. I turn it on it loads up and displays the Sony, xperia and the existenz logos. But after all this it freezes up at the purple wave. Tried booting into recovery no go. So now I've tried to flash it, here is another issue. When I try to get it into flash mode first the notification light turns green for a split second and then turns off completely. But I still try anyways, now flash tool will say device connected through flash mode yet it will not read the data of the device at all, so I'm like ok no problem I'll see if I can bypass this by inputting the actual phone in the flash menu. So I do that select the stock file and try to flash, it gets stuck on reading device. I am wanting to maybe use the flashboot mode but I don't know how to use that mode. Sooooooooo what do I do because I've beaten myself trying to figure this all out, so can someone point me in the right way. Also if I need to clarify more of this issue please let me know. Also I am using Windows 10 already ran into issues figuring out how to use drivers, but I fixed that.
Have you made sure its charged?
I maybe wrong but I am pretty sure you have to put it into fastboot mode first (blue light) then flashmode to use Flashtool.
tried sony pc companion?
nimicitor said:
Have you made sure its charged?
I maybe wrong but I am pretty sure you have to put it into fastboot mode first (blue light) then flashmode to use Flashtool.
Click to expand...
Click to collapse
It's fully charged. So I know it can't be that.
Lasantha said:
tried sony pc companion?
Click to expand...
Click to collapse
No I actually haven't. Can you explain how I should go about that?
http://support.sonymobile.com/global-en/tools/pc-companion/ downlod from here use repair mode folow instructions in it ..all the best
Lasantha said:
http://support.sonymobile.com/global-en/tools/pc-companion/ downlod from here use repair mode folow instructions in it ..all the best
Click to expand...
Click to collapse
Ok I'm like going crazy here, I've tried and tried and yes tried some more. There is no way at all I am going to get this phone in flashmode it is am absolutely no go. So can I be pointed somewhere that I can just use flashboot because I can get into that mode no problems, I just don't know where the correct files are. Thank you for your time.
Wraith512 said:
Ok I'm like going crazy here, I've tried and tried and yes tried some more. There is no way at all I am going to get this phone in flashmode it is am absolutely no go. So can I be pointed somewhere that I can just use flashboot because I can get into that mode no problems, I just don't know where the correct files are. Thank you for your time.
Click to expand...
Click to collapse
The answer is very simple.SCREW WINDOWS 10.
Just use another pc with windows 7,manually install xperia z2 drivers and do the drill with the flashtool.
Thank me when your done.
Turn off Windows 10 driver signature enforcement and then install the drivers again.
http://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/
nimicitor said:
Turn off Windows 10 driver signature enforcement and then install the drivers again.
http://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/
Click to expand...
Click to collapse
That's not the problem, I'll admit that was an issue at the beginning but I was able to install drivers. So it's not a driver issue.
Does anyone have any ideas on what I can do? Please
Just use the sony companion, it will work, had the same issue. If for some reason it fails, use windows 7 instead.
Check out this video
https://m.youtube.com/watch?v=PiaFGbeGOr0
I'm stuck on waiting for all devices in adb.. My phone screen has a menu with three choices, one of them is flash unlock.bin. Should I keep waiting for all devices for how long in adb?
What procedure are you using to unlock? The WTF process is the one that I believe has worked the best for most people... and that doesn't have anything special on the phone screen, so I'm thinking you're using some app or script?
dsk1000 said:
I'm stuck on waiting for all devices in adb.. My phone screen has a menu with three choices, one of them is flash unlock.bin. Should I keep waiting for all devices for how long in adb?
Click to expand...
Click to collapse
Yea, I'm following that one. I read somewhere about AMD PCs causing problems. My phone shows when I use adb devices. So should I be a little more patient or what?
No, the processes are quick. AMD Ryzens typically have issues, but it's only because of the USB driver they use. I've heard a few Intels have issues sometimes as well.
The key is, you just need to try other computers... this is the "hardest" thing to do, but it's really the only solution to that issue. The process takes under a second, so it's not a patience issue.
For the record, my older laptop with an AMD A9 CPU did the process fine... so, again, it's not a CPU issue, but a driver issue for the USB, apparently...
schwinn8 said:
No, the processes are quick. AMD Ryzens typically have issues, but it's only because of the USB driver they use. I've heard a few Intels have issues sometimes as well.
The key is, you just need to try other computers... this is the "hardest" thing to do, but it's really the only solution to that issue. The process takes under a second, so it's not a patience issue.
For the record, my older laptop with an AMD A9 CPU did the process fine... so, again, it's not a CPU issue, but a driver issue for the USB, apparently...
Click to expand...
Click to collapse
Thanks for the reply..I'm super new to adb..but I am following wtf instructions. I will keep researching..and asking questions. Thanks. PS I haven't rooted anything since my lg g3..
dsk1000 said:
Thanks for the reply..I'm super new to adb..but I am following wtf instructions. I will keep researching..and asking questions. Thanks. PS I haven't rooted anything since my lg g3..
Click to expand...
Click to collapse
Some people had to use 2 or 3 computers. An older one with Intel CPU works best (especially if it has USB 2.0), but yes an AMD can work. As noted by @schwinn8 Ryzens are no go. One guy was upset because he had superfast gaming computer and we kept telling him to try another computer. He borrowed his brother's mediocre laptop and BOOM, worked. Another guy dug some old laptop out of his closet and it worked.
Thanks for the reply...i was just reading about adb making sure it wasn't something i was doing wrong. Even tried on an old iMac that i had installed linux on. "Waiting for device..." So..still reading and learning to be patient. Thank you
dsk1000 said:
Thanks for the reply...i was just reading about adb making sure it wasn't something i was doing wrong. Even tried on an old iMac that i had installed linux on. "Waiting for device..." So..still reading and learning to be patient. Thank you
Click to expand...
Click to collapse
Also, try the steps mentioned in Wtf troubleshooting section.
Other than that you may have to mess around in the device manager section to see if the phone is detected properly or not.
(if there's a problem with the driver the device will show up as unknown android device or something)
dsk1000 said:
Thanks for the reply...i was just reading about adb making sure it wasn't something i was doing wrong. Even tried on an old iMac that i had installed linux on. "Waiting for device..." So..still reading and learning to be patient. Thank you
Click to expand...
Click to collapse
You said "patient"... just to reiterate, this process doesn't take longer on a computer that says "waiting for device". It's a fast process, so if it's not happening within a few seconds, it won't work on that setup, period. Don't waste your time waiting - get another machine/cable/etc (check the troubleshooting steps to find other possible issues... the computer is usually the biggest problem to overcome, but the most successful).
Good news, i unlocked my phone and installed twrp, then i had to stop the process (wtf)
i still need to make a backup in TWRP and flash two more files from wtf notes. I cannot seem to be able to reboot into TWRP from ADB. thanks in advance
The oem is greyed out in developer mode and says its unlocked. Idk?
Glad to hear you got it unlocked.
In the WTF post it says that the developer mode may remain grayed out after being flipped... this is normal. It comes back after some time. Of course, you don't want to toggle it again anyway, since you're unlocked...
When i go to use an app to boot into twrp..it tells me its not rooted.
dsk1000 said:
When i go to use an app to boot into twrp..it tells me its not rooted.
Click to expand...
Click to collapse
Used getvar..unlocked.
Well its done..used an old hp A6 with linuxmint. I found linux to be straightforward and easy when trying to root my phone. No jumping thru hoops and juggling stuff.
Any recommendations for remodeling the phone? Boot to twrp..roms..ect?
dsk1000 said:
When i go to use an app to boot into twrp..it tells me its not rooted.
Click to expand...
Click to collapse
Bootloader unlocked is not rooted. It's just the prerequisite to being rooted. Then you install TWRP custom recovery and then use that to flash Magisk. It's all in the WTF Instructions. Also be sure to use the version of Magisk in the WTF Instructions, at least initially.
Thanks..ive got magisk from the instructions. It wants to update..should?
Once you are booted into Android, you can update Magisk to some degree. I forget the last version I had but I recall I could go to 20.x or something without issue. But there is always a risk of having issues if you update to the latest version... so be prepared to go back to the one on the WTF thread if the phone has issues. In other words, don't do this last minute or without a PC to work from... because it could fail.
The only time you have to use the old Magisk is during that first boot with it... once you're booted through, you have been able to update to newer versions. But unless you need some specific feature of the newest version, I might suggest leaving it alone...
I read somewhere..when i upgrade on US 998 20b, i need to move up to 20c?
Also, do i use the "twrp version. 20c"?