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
Related
Hi guys,
I recently bought an Ideos X5 that was 2 months in use and it seems like I can't boot into stock recovery with it.
My device is definitely not rooted (Checked it with the app RootChecker). When I got it, I did a factory reset right after in stock recovery. I was able do get there with VOL+, HomeButton and Power. Neither this nor VOL+/VOL- and Power works now. I do not just reboot but boot when the phone is turned off. Android-Version is 2.3.5, Kernel 2.6.35.7, Build-Number ...B522... All I did so far was the factory reset.
Sorry I'm still not used to all this stuff although I read a lot, but seems like the more I read the more I get confused. Maybe it's totally easy but I tried a lot of things and none worked
Thanks a lot.
Try first holding down vol+ then power and then hold both of them until it either gets into recovery or its fully booted, depending if it works or not.
Sent from my U8800 using Tapatalk 2
MrTeflon said:
Hi guys,
I recently bought an Ideos X5 that was 2 months in use and it seems like I can't boot into stock recovery with it.
My device is definitely not rooted (Checked it with the app RootChecker). When I got it, I did a factory reset right after in stock recovery. I was able do get there with VOL+, HomeButton and Power. Neither this nor VOL+/VOL- and Power works now. I do not just reboot but boot when the phone is turned off. Android-Version is 2.3.5, Kernel 2.6.35.7, Build-Number ...B522... All I did so far was the factory reset.
Sorry I'm still not used to all this stuff although I read a lot, but seems like the more I read the more I get confused. Maybe it's totally easy but I tried a lot of things and none worked
Thanks a lot.
Click to expand...
Click to collapse
Should locked bootloader cause this? Because 522 has a locked bootloader. Atleast try to unlock the bootloader. There was a tutorial about this, search the forum
Sent from my U8800
I already found this tutorial,
http://forum.xda-developers.com/showthread.php?t=1457490
but the phone has to be rooted to do that or you have to get to stock recovery, so it didn't work obv.
I tried VOL+/Power, didn't work as well.
Thanks though. Any more ideas?
MrTeflon said:
I already found this tutorial,
http://forum.xda-developers.com/showthread.php?t=1457490
but the phone has to be rooted to do that or you have to get to stock recovery, so it didn't work obv.
I tried VOL+/Power, didn't work as well.
Thanks though. Any more ideas?
Click to expand...
Click to collapse
By did not work, do you mean it booted Android instead? If you don't want to root your device, you should reflash the firmware, but back up your things first.
Yes it booted normally. Maybe I'm gonna do that... Weird thing is that I did nothing but a factory reset and 3 or 4 apps like games and whatsapp.
aaaahhhh I got it. Had to untick "fast boot" in settings. Didn't really know that this is activated... anyway, thanks.
MrTeflon said:
aaaahhhh I got it. Had to untick "fast boot" in settings. Didn't really know that this is activated... anyway, thanks.
Click to expand...
Click to collapse
Looo
Sent from my U8800pro using xda premium
[SOLVED]
Hello, so i followed the guide on here to go back to the stock rom from LOS(Lineage OS). I had done that right. Then i tried relocking the bootloader. I did that successfully. Now, i have 2 problems i have run into.
1) there is no recovery mode
i tried booting into recovery and all it does is flash the ZTE logo for a second than turn off. This keeps happening. I am not sure how to flash the recovery image since the bootloader is locked and i have no recovery mode.
2) when i boot my device, it asks for a password (a 3x3 grid).
I tried typing in the password i used for TWRP and it didn't work. I tried a bunch of old passwords but so far nothing has worked. I would like to know how to get the password and turn this off. I found this very annoying on LOS.
Please help me as i am not sure what to do!!
edit: i cannot seem to get the device to conect to the computer using adb or fastboot.
if you can can we excahnge phone numbers to fix this faster?
Have you tried returning to stock using th3 axon 7 toolkit?I literally just did this today.had to restore using edl mode and all has been restored 100% stock
dcpyro1394 said:
Have you tried returning to stock using th3 axon 7 toolkit?I literally just did this today.had to restore using edl mode and all has been restored 100% stock
Click to expand...
Click to collapse
no i have not. Are there instructions for this
zman441 said:
no i have not. Are there instructions for this
Click to expand...
Click to collapse
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Nik2424 said:
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Click to expand...
Click to collapse
thanks. Can i get your email/phone number just to ask questions if i get stuck? its fine if you dont
zman441 said:
thanks. Can i get your email/phone number just to ask questions if i get stuck? its fine if you dont
Click to expand...
Click to collapse
Glad you got it back alive.
Good morning all,
I am throwing this out here hoping someone can please help.
Woke up yesterday to the Essential phone logo screen powered by Android... Unresponsive. Restarted with no luck. Went into recovery mode and factory reset. Went to start up animation for an hour but nothing. Device is locked (bootloader locked) and running on the latest build from Essential (7.1.1/NMJ88C/464). I have never unlocked nor flashed anything on the phone, only OTA updates directly from Essential. Just started it up again today and says your device is corrupt. Factory reset again and now cycling between logo screen and erasing circle.
Any ideas to fix the phone? Reached out to Essential but haven't heard back yet.
Thanks all!
Sent from my A0001 using Tapatalk
trsargent said:
Good morning all,
I am throwing this out here hoping someone can please help.
Woke up yesterday to the Essential phone logo screen powered by Android... Unresponsive. Restarted with no luck. Went into recovery mode and factory reset. Went to start up animation for an hour but nothing. Device is locked (bootloader locked) and running on the latest build from Essential (7.1.1/NMJ88C/464). I have never unlocked nor flashed anything on the phone, only OTA updates directly from Essential. Just started it up again today and says your device is corrupt. Factory reset again and now cycling between logo screen and erasing circle.
Any ideas to fix the phone? Reached out to Essential but haven't heard back yet.
Thanks all!
Click to expand...
Click to collapse
do you have an adb option in your recovery ?
nicoconepala said:
do you have an adb option in your recovery ?
Click to expand...
Click to collapse
Yes, I can get to an adb option in recovery
Sent from my A0001 using Tapatalk
trsargent said:
Yes, I can get to an adb option in recovery
Click to expand...
Click to collapse
ok then you should try to flash stock rom from essential
nicoconepala said:
ok then you should try to flash stock rom from essential
Click to expand...
Click to collapse
Am I able to do that with the device locked? Oem unlocking is not turned on I believe. I have never flashed anything on a phone before
Sent from my A0001 using Tapatalk
trsargent said:
Am I able to do that with the device locked? Oem unlocking is not turned on I believe. I have never flashed anything on a phone before
Click to expand...
Click to collapse
You don't need to be unlocked to adb sideload the Oreo beta builds from essentials website.
Just follow their instructions
Wrong section.
NaterTots said:
You don't need to be unlocked to adb sideload the Oreo beta builds from essentials website.
Just follow their instructions
Click to expand...
Click to collapse
Gave it a try, but it didn't resolve the issue. Got the your device is corrupt message. Any other ideas? Thanks!
Sent from my A0001 using Tapatalk
I'm searching for answers too! My essential is doing the dotted box to the dotted circle spin back & forth over & over ! I saw the dead robot with exclamation mark . The only thing on the essential website is to wipe phone ! Help. If the person that made this phone do this to people dies please let me know, so I can smile during this stressful time . If they r still alive I hope they are in agony over something thx!
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.
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.