Hello.
I rooted my phone, flashed magisk etc.... everything worked fine until...
I flashed https://forum.xda-developers.com/oneplus-6/themes/magisk-aod-lockscreen-weather-mods-oos-t3847008
with magisk. Then rebooted and my start screen started flashing. I tried to reboot again, it shut down and now its dead.
Holding power button, does not do anyting
Holding volume down and power button, does not do anyting
Holding volume up and power button, does not do anyting.
What next? Its been charging for few hours.
PC makes a sound when I plug it in but adb devices shows nothing.
Ideas?
Thread moved to the proper section.
jorksx said:
Hello.
I rooted my phone, flashed magisk etc.... everything worked fine until...
I flashed https://forum.xda-developers.com/oneplus-6/themes/magisk-aod-lockscreen-weather-mods-oos-t3847008
with magisk. Then rebooted and my start screen started flashing. I tried to reboot again, it shut down and now its dead.
Holding power button, does not do anyting
Holding volume down and power button, does not do anyting
Holding volume up and power button, does not do anyting.
What next? Its been charging for few hours.
PC makes a sound when I plug it in but adb devices shows nothing.
Ideas?
Click to expand...
Click to collapse
Quite new to Magisk myself but managed to cause my own bootloop last night . You can get a Magisk Mod uninstaller that works through TWRP I found it using Google.. Maybe try removing your mod in TWRP and then if your still in a loop try flashing the zip that's in the instructions of the mod you've linked..
I'd installed a fingerprint mod which caused a similar result but managed to remove it with TWRP. I was still bootlooping so had to update from 9.0.7 to 9.0.11 and re-root so I didn't loose any data.
Sent from my [device_name] using XDA-Developers Legacy app
kaotik2k said:
Quite new to Magisk myself but managed to cause my own bootloop last night . You can get a Magisk Mod uninstaller that works through TWRP I found it using Google.. Maybe try removing your mod in TWRP and then if your still in a loop try flashing the zip that's in the instructions of the mod you've linked..
I'd installed a fingerprint mod which caused a similar result but managed to remove it with TWRP. I was still bootlooping so had to update from 9.0.7 to 9.0.11 and re-root so I didn't loose any data.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I dont know if I explained it badly but I cannot boot into TWRP.
Only thing I see is black screen. No vibrations.
holding any of the buttons over 2minutes wont do anything.
If I could get into twrp I can do at least full restore. But I cannot boot to anywhere.
jorksx said:
I dont know if I explained it badly but I cannot boot into TWRP.
Only thing I see is black screen. No vibrations.
holding any of the buttons over 2minutes wont do anything.
If I could get into twrp I can do at least full restore. But I cannot boot to anywhere.
Click to expand...
Click to collapse
AHH sorry for the misunderstanding.. I'm quite new to this phone coming from galaxy note 8 and so rooting and flashing is something I'm not really up to date on. I don't want to give you bad advice .. Hopefully somebody with a bit more experience will be able to respond
Sent from my [device_name] using XDA-Developers Legacy app
kaotik2k said:
AHH sorry for the misunderstanding.. I'm quite new to this phone coming from galaxy note 8 and so rooting and flashing is something I'm not really up to date on. I don't want to give you bad advice .. Hopefully somebody with a bit more experience will be able to respond
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
no problem, Any help is welcome. I've done rooting and changing roms many times in my life.
BUT I just noticed that I have flashed something for oneplus 6, not the 6t.
Thats why I posted this firstly in the oneplus 6 questions, not 6t.
I dont know if that bricked my phone or what did.
jorksx said:
no problem, Any help is welcome. I've done rooting and changing roms many times in my life.
BUT I just noticed that I have flashed something for oneplus 6, not the 6t.
Thats why I posted this firstly in the oneplus 6 questions, not 6t.
I dont know if that bricked my phone or what did.
Click to expand...
Click to collapse
Yeah definitetly sounds like a brick .. You said your computer makes a sound when you plug the phone in... Is anything showing in the PC device manager ?
Sent from my [device_name] using XDA-Developers Legacy app
kaotik2k said:
Yeah definitetly sounds like a brick .. You said your computer makes a sound when you plug the phone in... Is anything showing in the PC device manager ?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
yeah, pc makes sound, but device manager shows nothing
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
Try this
Yeah I was gonna also suggest the MSM tool. Choose the right one for your device. T-Mobile for T-Mobile version, or global for global. The thread also says you have to hold down BOTH volume keys before plugging in the phone, just noting that because I believe the 6 was different.
Also, if it doesn't work, is it possible it was a faulty display??? I doubt it but that's a possibility if MSM tool does nothing for ya.
Related
Hi so my lg g2 d801 is stuck on the lg boot logo and when i try going to recovery mode (twrp) it just turns into a black screen. Any idea how to get out of this please?
and when i connect the phone to the computer it pops up all these drives for some reason. really scared don't want to think that my phone just became paperweight
CrazzyBoy265 said:
and when i connect the phone to the computer it pops up all these drives for some reason. really scared don't want to think that my phone just became paperweight
Click to expand...
Click to collapse
check this thread out. I had the same thing.http://forum.xda-developers.com/showthread.php?t=2432476
this reverts you completely back to stock. You will lose all your data but you did back up regularly, right?
(edit) you only have to hold the volume UP key while plugging in the USB on a D801 to get into download mode.
Make sure you've disconnected usb when attempting to enter recovery. Hope the silence means you've sorted it out!
mooserov said:
check this thread out. I had the same thing.http://forum.xda-developers.com/showthread.php?t=2432476
this reverts you completely back to stock. You will lose all your data but you did back up regularly, right?
(edit) you only have to hold the volume UP key while plugging in the USB on a D801 to get into download mode.
Click to expand...
Click to collapse
im confused so im fashing stock rom normally?
yep. the phone will be the same as when you took it out of the box. What did you do to get to this point?
mooserov said:
yep. the phone will be the same as when you took it out of the box. What did you do to get to this point?
Click to expand...
Click to collapse
i felt like going back to stock from (was on cm11 nightlie) so i went on flashify and for some reason i tried restoring twrp and when it rebooted it messed it up bad -.-
I am able to get into TWRP to flash a ROM. I have tried the Stock Sprint Root ZV8 and it just reboots into TWRP. I was unable to get it to work with the LG Flash Tools.
Ikyo said:
I am able to get into TWRP to flash a ROM. I have tried the Stock Sprint Root ZV8 and it just reboots into TWRP. I was unable to get it to work with the LG Flash Tools.
Click to expand...
Click to collapse
well im downloading the rom as i write this hope it works for me. Do you got the same issue as i do?
CrazzyBoy265 said:
well im downloading the rom as i write this hope it works for me. Do you got the same issue as i do?
Click to expand...
Click to collapse
You have to get your phone in DOWNLOAD mode then use the thread posted above to get back to stock
RubbleTea said:
You have to get your phone in DOWNLOAD mode then use the thread posted above to get back to stock
Click to expand...
Click to collapse
ok i pressed up and down volume key its not doing anything am i doing something wrong?
CrazzyBoy265 said:
ok i pressed up and down volume key its not doing anything am i doing something wrong?
Click to expand...
Click to collapse
You hold vol up and plug in to PC.....or hold vol down and power same time.....nothing?
RubbleTea said:
You hold vol up and plug in to PC.....or hold vol down and power same time.....nothing?
Click to expand...
Click to collapse
worked perfectly with the volume up thing im unpacking the rom right now
i followed every step but when its unpacking the it says extract file error. Any ideas?
CrazzyBoy265 said:
i followed every step but when its unpacking the it says extract file error. Any ideas?
Click to expand...
Click to collapse
If you're trying to unpack the ROM try redownloading the rom.
You're saying that you have CM installed? I had this exact problem and I had PA installed.. it was a mess. I had to sideload the original ROM because to flash with that program your build.prop has to be the original information when you received the phone or else the program will throw a "different phone model"
Do you have the LG usb drivers? Install all proper USB drivers and try to sideload an original ROM.
BTW do you have any backups? Restoring also gets you out of this mess
never mind i opened the wrong folder thanks for everything guys it worked perfectly ^.^
xxxrichievxxx said:
If you're trying to unpack the ROM try redownloading the rom.
You're saying that you have CM installed? I had this exact problem and I had PA installed.. it was a mess. I had to sideload the original ROM because to flash with that program your build.prop has to be the original information when you received the phone or else the program will throw a "different phone model"
Do you have the LG usb drivers? Install all proper USB drivers and try to sideload an original ROM.
BTW do you have any backups? Restoring also gets you out of this mess
Click to expand...
Click to collapse
It worked perfectly but i guess i have to root my phone again so i think i lost all my backups from flashify
Didn't lose my root but now I've got some screen burn in because the phone wouldn't stay off.
Sent from my LG-D800 using XDA Premium 4 mobile app
LCD screen burn in
MerlinOfLore said:
Didn't lose my root but now I've got some screen burn in because the phone wouldn't stay off.
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
In case you don't know, you can supposedly get rid of it by displaying an all-white screen (with display brightness turned down to preserve bulb life).
MerlinOfLore said:
Didn't lose my root but now I've got some screen burn in because the phone wouldn't stay off.
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Really I found out how to turn my phone off when it was messed up I'm sorry to hear about that though
Sent from my LG-D801 using Tapatalk
I was trying to unlock my Nexus 10 with 4.4.2 through fastboot. First I booted into fastboot mode, and then issued the following command:
fastboot oem unlock
I saw on the tablet the status showed 'unlocked'. After that I just pushed the power button to try to reboot, but it keeps spinning. Even if I pushed the power button again, spinning remains. And I can't shut it down either. Is it hard bricked? What should I do now? Should I have waited for the tablet to reboot itself?
mj56gt said:
I was trying to unlock my Nexus 10 with 4.4.2 through fastboot. First I booted into fastboot mode, and then issued the following command:
fastboot oem unlock
I saw on the tablet the status showed 'unlocked'. After that I just pushed the power button to try to reboot, but it keeps spinning. Even if I pushed the power button again, spinning remains. And I can't shut it down either. Is it hard bricked? What should I do now? Should I have waited for the tablet to reboot itself?
Click to expand...
Click to collapse
You should be fine. Hold down the power button and both volume buttons until it restarts into the bootloader. Go into the Recovery Mode. Then, you'll see the little android on his back with a red exclamation mark over him. Don't panic. You need to hit power + volume down at the same time (no need to hold). It may take a few tries, but when successful, you'll see the recovery menu pop up. Do a factory data wipe. Then, after it does it's thing. Select reboot system and you're good to go.
charesa39 said:
You should be fine. Hold down the power button and both volume buttons until it restarts into the bootloader. Go into the Recovery Mode. Then, you'll see the little android on his back with a red exclamation mark over him. Don't panic. You need to hit power + volume down at the same time (no need to hold). It may take a few tries, but when successful, you'll see the recovery menu pop up. Do a factory data wipe. Then, after it does it's thing. Select reboot system and you're good to go.
Click to expand...
Click to collapse
Thanks a lot! Those steps fixed the problem... I really appreciate your help!!!
mj56gt said:
Thanks a lot! Those steps fixed the problem... I really appreciate your help!!!
Click to expand...
Click to collapse
No problem. Same thing happened to me on my N10 (and also my Nexus 5). Has something to do with it not properly wiping/formatting the data partition after unlock like it's supposed to, so you have to do it manually.
It was quite a scary experience for me! Thanks again for the kind help...
Also I just flashed TWRP 2.7.0.1, and then flashed SuperSU-v1.80 in TWRP. It said successful, but both Root Checker and Busybox indicate that it's not rooted. What did I do it wrong?
mj56gt said:
It was quite a scary experience for me! Thanks again for the kind help...
Also I just flashed TWRP 2.7.0.1, and then flashed SuperSU-v1.80 in TWRP. It said successful, but both Root Checker and Busybox indicate that it's not rooted. What did I do it wrong?
Click to expand...
Click to collapse
Hmm. That's odd. Unfortunately, I don't use TWRP, so probably couldn't help much there as I prefer Philz Recovery. I do know that SuperSU v1.80 is a pretty old version (may be some compatibility issues with 4.4.2). Have you tried downloading and flashing the latest SuperSU in TWRP? I believe it's v1.94. I would try that first.
charesa39 said:
I do know that SuperSU v1.80 is a pretty old version (may be some compatibility issues with 4.4.2). Have you tried downloading and flashing the latest SuperSU in TWRP? I believe it's v1.94. I would try that first.
Click to expand...
Click to collapse
You're absolutely right. Previously when I googled SuperSU, it came out with the version 1.80 for some reason. This time I used Google Play, sure enough it installed v1.94! And everything looks good now!
You made my day! Thanks a lot...
Sent from my Nexus 10 using xda app-developers app
mj56gt said:
You're absolutely right. Previously when I googled SuperSU, it came out with the version 1.80 for some reason. This time I used Google Play, sure enough it installed v1.94! And everything looks good now!
You made my day! Thanks a lot...
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
No problem. I, too, am familiar with that feeling you get in the pit of your stomach when you start to think you just ruined your not-so-cheap toy. Just glad I could help you get through it. Regards.
Sent from my Nexus 7 using xda app-developers app
Hi,
I had a rooted phone and TWRP and was using the latest Nougat release. However i decided to return to stock so using Kies i did a full factory reset.
It's working - however i've lost the vibrator functionality. I can hear a faint beep whenever the phone should vibrate. The only solution i can find here on xda seems to be downgrading the bootloader, so i'ved tried flashing everything through Odin with same results.
When I try to open the bootloader (volume up, power and home button) it shows the Android updating screen (installing system update) which after a while fails (exclamation mark) - and shows the Samsung bootloader where i can reset phone, clear cache etc.
Any ideas on how to fix the vibrator?
sessingø said:
Hi,
I had a rooted phone and TWRP and was using the latest Nougat release. However i decided to return to stock so using Kies i did a full factory reset.
It's working - however i've lost the vibrator functionality. I can hear a faint beep whenever the phone should vibrate. The only solution i can find here on xda seems to be downgrading the bootloader, so i'ved tried flashing everything through Odin with same results.
When I try to open the bootloader (volume up, power and home button) it shows the Android updating screen (installing system update) which after a while fails (exclamation mark) - and shows the Samsung bootloader where i can reset phone, clear cache etc.
Any ideas on how to fix the vibrator?
Click to expand...
Click to collapse
Buy a new vibrator and enjoy :laugh:
Flash last bootlader and radio.
Leejay1953 said:
Buy a new vibrator and enjoy :laugh:
Click to expand...
Click to collapse
are you kidding me, this same problem happened to me, what is the solution
Leejay1953 said:
Buy a new vibrator and enjoy [emoji23]
Click to expand...
Click to collapse
Lol. I think some didn't understand this.
Eye eye saucy! Lol
Sent from my SM-G935F using XDA-Developers mobile app
Leejay1953 said:
Buy a new vibrator and enjoy :laugh:
Click to expand...
Click to collapse
hahaha! this is a nice one! :laugh::good:
Waaat. I have the same issue. But I like it lol. It sounds nice. So I just kept it. And it randomly happens. Depends on what rom I use.
Must be upsetting having a broken vibrator
Ask your girlfriend where it is.
Gesendet von meinem SM-G935F mit Tapatalk
Rofl, bad boys !
....
Here's the solution!
sessingø said:
Hi,
I had a rooted phone and TWRP and was using the latest Nougat release. However i decided to return to stock so using Kies i did a full factory reset.
It's working - however i've lost the vibrator functionality. I can hear a faint beep whenever the phone should vibrate. The only solution i can find here on xda seems to be downgrading the bootloader, so i'ved tried flashing everything through Odin with same results.
When I try to open the bootloader (volume up, power and home button) it shows the Android updating screen (installing system update) which after a while fails (exclamation mark) - and shows the Samsung bootloader where i can reset phone, clear cache etc.
Any ideas on how to fix the vibrator?
Click to expand...
Click to collapse
Temporarily upgrade to Android 7 to fix the vibration issue then use odin to flash final version of android 6.0.1. You must flash all 4 files contained in the extracted (unzipped) firmware package but ignore the home_CSC file. IMPORTANT...tick the option in odin "phone bootloader update". This process will wipe all data on the phone full but will give you a fully functioning galaxy s7 with Android 6.0.1 marshmallow!
Leejay1953 said:
Buy a new vibrator and enjoy :laugh:
Click to expand...
Click to collapse
Hi,
I'm interested to learn how you downgraded your boot-loader from DRAG update? Can you please explain?
Thank you.
M T Coulibaly
Hello. I have an X727 model, which I didn't have problems (after I unlocked the bootloader and tested custom roms like Paranoid Android and RR and they all detected my device as LEX727) until I gave a shot with the latest cuoco92 stock rom. Then something weird happened: it wrote the start logo (from a plan "LeEco, powered by Android" to "LeEco, welcome to cuoco release") and it "converted it" to LEX720. I wasn't pleased with it, so I wanted to go to Oreo. But every ROM detected my device as X720.
First, I tried to go back to stock with the guide:
https://forum.xda-developers.com/le-pro3/how-to/guide-return-to-stock-lock-bootloader-t3539513
Using this file:
https://forum.xda-developers.com/le-pro3/development/le-eco-pro-3-x727-twrp-backup-clean-t3727920
It sorta worked, but no initial logo change and if I go to another custom ROM it goes back to X720 state.
So, I tried the steps described here:
https://forum.xda-developers.com/le-pro3/help/x727-x720-ideas-t3630908/
However, the links are down, so I have no idea what to do.
What else can I do?
Just edit your build prop.
Sent from my LEX727 using xda premium
mchlbenner said:
Just edit your build prop.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Just did it. But it did not work. Every rom i install (no matter which one) ends up being detected as LEX720
It's the dev-info partition. You'll want to download the SuperLuminal CM13 X727 patch. Lemme see if I can get link.
Try this link. Flash in TWRP.
http://www.teamsuperluminal.org/wp-content/uploads/2016/12/le_zl1_x727_mod.zip
Thanks. But I flashed it and still no changes from logo and the device still thinks as a X720.
And what's worse. Trying to flash a TWRP backup I had, now I have no OS and I have to revive it using the guide to return to stock
It's going to be a long ride...
horvman said:
Thanks. But I flashed it and still no changes from logo and the device still thinks as a X720.
And what's worse. Trying to flash a TWRP backup I had, now I have no OS and I have to revive it using the guide to return to stock
It's going to be a long ride...
Click to expand...
Click to collapse
Will your twrp recognize your computer
Sent from my LEX727 using xda premium
mchlbenner said:
Will your twrp recognize your computer
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Yes. Now TWRP recognizes my pc and I did restore to stock. In the process, I lost the IMEI but fortunately I made a backup with the EFS. So I have a frankenstein-esque eui 21s, but still appears the red LeEco logo (which it wasn't like that, it was a green and red mixture).
Now I have to test it with a custom rom.
UPDATE: Tested with Paranoid Android and the curious thing is even if the device is detected as X727, when I was looking at build.prop the "ro.product.model" feature was absent and the PC still detected as X720, not to mention the irregular behavior of copy pasting files from PC (the progress bar doesn't move and the files are not transfered). And when i go to TWRP it asks me for a password. Reflashing the recovery....
Its just a "Name". The X727 is USA version, just got update till 21S. But x727 and x720 are same phone <Except for Double Sim on x720> .... anyway, on Stock rom just change "X720" for "X727" on build.prop, that works for me many times and no problem at all.
kukuteku said:
Its just a "Name". The X727 is USA version, just got update till 21S. But x727 and x720 are same phone <Except for Double Sim on x720> .... anyway, on Stock rom just change "X720" for "X727" on build.prop, that works for me many times and no problem at all.
Click to expand...
Click to collapse
The thing that worries me is the persistance of "welcome to cuoco release" inital logo, along with the absence of "ro.product.model" (it's just not there, no value at all) in build.prop after i flashed the custom rom. Is that normal?
Also, is there another way to remove the password request everytime i boot into recovery?
horvman said:
The thing that worries me is the persistance of "welcome to cuoco release" inital logo, along with the absence of "ro.product.model" (it's just not there, no value at all) in build.prop after i flashed the custom rom. Is that normal?
Also, is there another way to remove the password request everytime i boot into recovery?
Click to expand...
Click to collapse
Yes you have to reformat data save what to keep backup on computer this will whipe all
Sent from my LEX727 using xda premium
mchlbenner said:
Yes you have to reformat data save what to keep backup on computer this will whipe all
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Thanks. With the backups I had along with the one provided in the 21s guide I am back on track with Paranoid Android (the 20180203 build, because it offers me loud sound in video recordings with GCam and phone calls on speaker work, unlike RR, onmirom, LOS, etc.) and I suppose the logo stuff can be ignored. But when I was installing magisk to install Dolby Atmos and testing the AINUR SAURON mod, I encountered another problem: if I poweroff the device and I want to go to TWRP (to give an example) the power button doesn't react unless I charge it (no worries about stock cable, I have an Benson Leung approved one). Did anyone have that problem?
If you have issues getting into recovery reboot and push up volume you don't need to hold down power button.
Sent from my LEX727 using xda premium
horvman said:
The thing that worries me is the persistance of "welcome to cuoco release" inital logo, along with the absence of "ro.product.model" (it's just not there, no value at all) in build.prop after i flashed the custom rom. Is that normal?
Also, is there another way to remove the password request everytime i boot into recovery?
Click to expand...
Click to collapse
Yes. Just like Horvman said. You must wipe Data, Cache, Davilk and System. But its very important to have a Recovery that support OTG or can see from PC. The old recoveries does not works, so, before you do all five Wipe, you should flash (Can do it from recovery) Codeworkx's recovery for Zl1 .... Then you already can flash any rom you want, stock or custom ... Nougat and Oreo...
Good luck!
kukuteku said:
Yes. Just like Horvman said. You must wipe Data, Cache, Davilk and System. But its very important to have a Recovery that support OTG or can see from PC. The old recoveries does not works, so, before you do all five Wipe, you should flash (Can do it from recovery) Codeworkx's recovery for Zl1 .... Then you already can flash any rom you want, stock or custom ... Nougat and Oreo...
Good luck!
Click to expand...
Click to collapse
Done it. Flashed codeworkx's TWRP for zl1 with no problems. BTW, is it normal to wait so long since I poweroff the device and I press the power button to turn it on? Let me explain:
1. I poweroff the device
2. Wait aprox. 70 seconds (if I press the power button before nothing happens)
3. Press the power button
4. Profit
horvman said:
Done it. Flashed codeworkx's TWRP for zl1 with no problems. BTW, is it normal to wait so long since I poweroff the device and I press the power button to turn it on? Let me explain:
1. I poweroff the device
2. Wait aprox. 70 seconds (if I press the power button before nothing happens)
3. Press the power button
4. Profit
Click to expand...
Click to collapse
Mmmmmm.... sometime happened. But no for long time... More or less 10-15 Seconds. The very first day I bought my Phone (Mint Condition) I turned off and then, do not turn on until I pressed Power button for 10-15 seconds...So, look like its a normal Situation,..
kukuteku said:
Mmmmmm.... sometime happened. But no for long time... More or less 10-15 Seconds. The very first day I bought my Phone (Mint Condition) I turned off and then, do not turn on until I pressed Power button for 10-15 seconds...So, look like its a normal Situation,..
Click to expand...
Click to collapse
Was your bootloader unlocked when you got it?
Sent from my LEX727 using xda premium
mchlbenner said:
Was your bootloader unlocked when you got it?
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
No. It came with eui 5.8.20s, so I had to manually update it to 21s. Then I unlocked the bootloader. But the long time to boot the phone never happened to me before.
horvman said:
No. It came with eui 5.8.20s, so I had to manually update it to 21s. Then I unlocked the bootloader. But the long time to boot the phone never happened to me before.
Click to expand...
Click to collapse
Usually after unlocking bootloader you flash twrp then reformat your device that is a long boot first time then flash root.
Sent from my LEX727 using xda premium
I have x720. In Windows: In 23s was detected as x720. Installed TWRP - ... detected there as x727. After install AICP 13.1 it's detected as Le Pro3. But in OS it's x720. Maybe it's the trouble.
mchlbenner said:
Was your bootloader unlocked when you got it?
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Yes.
Hi all,
So earlier this evening phone was only booting to TWRP I had made 2 recoveries before this started one on 5/26/19 and one 6/3/19. I tried last one I did and then tried booting it went to twrp again. I tried powering off through menu and tried powering back on and went back to twrp. wow is stuck in fastboot menu. I did the tmobile mod to international, installed xxnosxxx and smurf been running fine about 2 weeks. It won't go to recovery and just restarts back to fastboot. should I use msm tool and start from scratch ? or anything else I should try first ?
Fastboot showing it is unlocked if that helps
Thanks
Sand
sandrager said:
Hi all,
So earlier this evening phone was only booting to TWRP I had made 2 recoveries before this started one on 5/26/19 and one 6/3/19. I tried last one I did and then tried booting it went to twrp again. I tried powering off through menu and tried powering back on and went back to twrp. wow is stuck in fastboot menu. I did the tmobile mod to international, installed xxnosxxx and smurf been running fine about 2 weeks. It won't go to recovery and just restarts back to fastboot. should I use msm tool and start from scratch ? or anything else I should try first ?
Fastboot showing it is unlocked if that helps
Thanks
Sand
Click to expand...
Click to collapse
Any help would be appreciated thanks much
sandrager said:
Any help would be appreciated thanks much
Click to expand...
Click to collapse
Power off and when you turn it back on hold the vol down while powering it on. It should boot you to TWRP. If that doesn't work you might have to start over again but you don't need to use the T-Mobile msm tool. You can use international patched msm to be able to unlock again since it relocks the bootloader.
R800x_user said:
Power off and when you turn it back on hold the vol down while powering it on. It should boot you to TWRP. If that doesn't work you might have to start over again but you don't need to use the T-Mobile msm tool. You can use international patched msm to be able to unlock again since it relocks the bootloader.
Click to expand...
Click to collapse
thanks R800x for reply. Yup that is what I did and got it working using the international msm tool. Now trying to get all my settings back. Had my battery idle drain down to .5 per hour during the day. Need to backup app settings this time
R800x_user said:
Power off and when you turn it back on hold the vol down while powering it on. It should boot you to TWRP. If that doesn't work you might have to start over again but you don't need to use the T-Mobile msm tool. You can use international patched msm to be able to unlock again since it relocks the bootloader.
Click to expand...
Click to collapse
Not to steer the thread but you would not happen to have made your username based off the Xperia play r800x? That was a phone I used ages ago, still have now. Anyways, back to the thread
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app
ozzmanj1 said:
Not to steer the thread but you would not happen to have made your username based off the Xperia play r800x? That was a phone I used ages ago, still have now. Anyways, back to the thread
Click to expand...
Click to collapse
Yeah, my first phone I learned to root and overclock back in the day. Good times ?
R800x_user said:
Yeah, my first phone I learned to root and overclock back in the day. Good times ?
Click to expand...
Click to collapse
Same here. Still wish a decent XP phone was around. Cool to know there's an old Xperia play user here on 6t. (Modern combat 4 Xperia play reapers)
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app